Maven2ized site alpha (with javadocs)

[wireframe]

I think this is a great start, and you've got to start somewhere. Once these smaller modules are in place, it should become clear if there are any other componets that could be pulled out as well.

I also think that this modularization could be a big help for the developers that run the spring-rcp project. There's been a lot of talk lately about needing a strong lead developer to take hold of the project, but it would be much more effective to have multiple smaller projects with multiple stake holders. One single "dictator" for the project is not going to be effective. Spring-RCP is a lot like the main springframework. There are multiple components and there's no single developer that owns or knows the entire project. it's more of a loose collaboration of developers, each with their own expertise.

I'm no spring-rcp expert, but if the project was componatized, I would feel much more comfortable digging in and contributing to the pieces that I use and enhance the most...

[benoitx]

If any componentization was to occur, it would be good to do it along dependencies line as Spring RC is quite "heavy" when it comes to the extra required jars... like aopappliance/jxr/caucho/swingx...

Thanks!

[ge0ffrey]

There's been a lot of talk lately about needing a strong lead developer to take hold of the project, but it would be much more effective to have multiple smaller projects with multiple stake holders. One single "dictator" for the project is not going to be effective.

I believe we need an overall strong leader (and don't see anyone doing a better job then Ollie at this time), but deviding reponsibility more would be a good idea.
If the maven2ization would be accepted, I 'd gladly take reponsiblity for keeping the build process consistent.
The rule "no part of the code is sacred" should be changed into "no part of the code is sacred, but the module's leader will warn you to keep the code consistent if you mess up".

[ge0ffrey]

If any componentization was to occur, it would be good to do it along dependencies line as Spring RC is quite "heavy" when it comes to the extra required jars... like aopappliance/jxr/caucho/swingx...

Thanks!

The maven2ization makes full use of maven2's dependency properties (transitive, required/optional, etc) and every dependency is documented on the maven generated site.

[benoitx]

Indeed it is very useful information but what I'm getting at is that by looking at the Spring RC CORE:
http://users.telenet.be/geoffrey/Del...endencies.html

The transitive dependencies are rather scary! A massive amount of them and... in my project, I do not need half of them... So my suggestion would be to release different jars and introduce new dependencies only when absolutely required... (like encache only when one uses Hibernate on the client!) etc

My £0.02-worth suggestion...

Benoit

[ge0ffrey]

You're partially right.

The main reason is the dependency on spring (instead of spring-cor etc specifically), I 'll fix that.

Another reason is that that report doesn't mention which dependencies are optional: required at compile time but only if some classes are used required at runtime: for example Javamail (you can't use spring without sending a mail).
That report should mention that, I 'll post an issue at maven.

[ge0ffrey]

that report doesn't mention which dependencies are optional:

http://jira.codehaus.org/browse/MPIR-11

[Ben Alex]

Some of the dependencies spring-richtclient needs aren't in ibiblio, so I 've made a remote repository in my ${basedir} (untill I can put that online somewhere). Have you had this problem in acegi and how did you fix it?

Made a new repo at http://acegisecurity.sourceforge.net/maven. You can easily add this under your project_home/htdocs directory on the shell.sourceforge.net server.

Is Spring (besides acegi) going the maven2 way (I noticed some project.xml's in their sources)?

project.xml is Maven 1.x. pom.xml is Maven 2.x. I would not think Spring core will shift to Maven 2.x within the foreseeable future, due to the investment in the existing Ant-based build system.

Does spring have any conventions on their maven2 repositories?

Carlos Sanchez would be the best person to ask. Carlos is a Maven developer, and also assists with Acegi Security's Maven build maintenance and initial migration. I know Carlos offered to assist the Spring team more to Maven 2.x on the developer list, but I don't recall there being any replies. If you do establish a Maven 2 build, you might consider running a nightly Maven build to publish to your project home page. We do this, which is why http://acegisecurity.org always reflects the latest CVS code. This is useful for the project team to see code coverage, demonstrate that the unit tests work to people who are having difficulty running them locally etc.

[ge0ffrey]

If you do establish a Maven 2 build, you might consider running a nightly Maven build to publish to your project home page. We do this

You got a public continuum up an running?
If so, could spring-rich use it if the maven2ization would be accepted?
I am using a company continuum for my company projects, but it's not accessible from the outside. It's easy and great with maven2 projects (haven't tested my older maven 1 and ant builds yet).

[wireframe]

any update on this? I'd love to see some spring-rcp snapshots starting to get published regularly.