Comments on: Spring Framework Maven Artifacts

By: Jean Louis Boudart

Jean Louis Boudart — Tue, 03 Feb 2009 16:38:44 +0000

Hi,

I'm currently working on a new open source build system named EasyAnt.
Easyant is a toolbox focusing on easing project build processes.
It's based on Apache Ant and Apache Ivy, and allows for maximum flexibily, improved integration in existing build systems and provides conventions and guidelines.

Our goals are :

* to simplify build process by providing a set of ready to use build scripts (or modules) to ease the implementation of build system.
* to provide conventions and guidelines
* to leverage your ant knowledge (no need to learn another language)
* to remain adaptable :
o what about conventions ? : Even if Easyant comes with a lot of conventions, we never lock you in.
o what about modules ? : You can easily adapt it to your projects. The architecture of Easyant allows you to easily extends existing modules and to provide your own one.
o what if you already have an existing project ? Since Easyant is fully based on top of ant, you can keep your existing project along with the "old school" ant scripts. This should ease the migration to Easyant.

Any feedback would be really appreciated, i'm sure you can give us good idea of what a good and flexible build system must implement.

Cheers,
Jean Louis Boudart

By: Ben Hale

Ben Hale — Mon, 04 Feb 2008 11:17:08 +0000

Actually haven't moved our build systems over, we only create Maven artifacts. There are a couple of projects in the Spring Portfolio that use Maven, but not all of them do. Going forward the new portfolio projects are using a build system that is based on ANT and Ivy. Maven certainly has come on a bit, but there are still enough issues with it, that we feel a unified build system based on ANT and Ivy is more useful to us. However, each situation is different and I encourage you to evaluate based on your own projects.

By: Matt T

Matt T — Mon, 04 Feb 2008 11:01:50 +0000

I was just wondering how you found your transition from your previous build system to using Maven. I have seens lots of discussion about use of ANT Ivy instead of Maven, and was wondering what your position was? I am currently implementing the building of all my companies products in Maven, but was challenged by a colleague as to why I am not using the ANT Ivy combination instead. I didn't really have an answer, which is partly the reason for me posting here. The articles I have read however were over a year old, so, my personal opinion is that Maven has come on a lot over that time. It has transitive dependencies now, which it did not have in earlier incarnations… etc, etc.

Any thoughts would be greatly appreciated.

By: Blair

Blair — Mon, 26 Nov 2007 20:44:54 +0000

I've noticed spring richclient isn't there, will it be put there?

What (if anything) is happening with that project?

By: Martin Bengl

Martin Bengl — Mon, 26 Nov 2007 15:35:03 +0000

"somebody" found a way to change the spring-2.5-sources.jar at repo1. Thanks for that!

By: Ben Hale

Ben Hale — Mon, 26 Nov 2007 13:12:52 +0000

Once an artifact is uploaded to repo1, it can never be changed. The more granular artifacts are fine, so you could use those until the 2.5.1 release which is coming shortly. As well, you can just use the current snapshots that this post talks about.

By: Martin Bengl

Martin Bengl — Mon, 26 Nov 2007 09:41:37 +0000

Hi Alex,

could you please update the spring-2.5-sources.jar at http://repo1.maven.org/maven2/org/springframework/spring/2.5/.
It currently contains just the source for spring aop.

Thanks!

Martin