PLEASE get Spring 2.0 jars into central Maven2 repository (spring-portlet.jar)

[robottaway]

Hi I am working on setting up the 'petportal' example as a Maven2 project. The benefit being that users will be able to download the example and quickly compile and deploy it to their portlet container! I would like this example to have 'wide' portability. By wide I mean that anyone could easily download and compile the app without needing to find the dependencies. For this to work I need a newer version of the Spring 2.0 framework in the Maven2 repository housed by Ibiblio.

Right now a very incomplete version seems to be in Central. The spring-portlet.jar that I got (the only one in there) does not even have the correctly named classes. It also did not contain the 'mulipart' package! The dependency I got from central was spring-portlet-2.0-m1.jar.

Please upload a newer version of the 2.0 framework. I will be happy to help whoever would take on this task. I will write up a article to go with the petportal Maven2 project once I can complete it. The benefit to the Spring community will be Maven's ability to let users quickly jump into Spring and start using it. There is no time wasted in trying to get the correct dependencies together so code compiles.

Thanks,
Rob Ottaway

[Costin Leau]

Hey Rob.
This issue has been reported and the team is aware of its importance - you can find some talks on the topic here:http://forum.springframework.org/showthread.php?t=24373
Ofc,contributions are welcomed since that speeds the process.

P.S. this is the Spring-Modules forum - Spring core topics go here.

[robottaway]

To do so I will need to get a little help from someone on the Spring team. The guys over at Codehaus want some proof of the person uploading the dependencies connection to the project. I'm not on the project but would like to help get the up to date Spring jars into central. So I may need some help convincing people I'm justified.

Besides that, which release would be best to get into central for now? My guess is 2.0-rc3. I could get those jars up and in central...and then I can get my petportal Maven project working

[Costin Leau]

Thanks for the contribution. Take a look at the thread I posted above - you should find some issues on JIRA about the maven support. Please upload the maven pom there (no need to add the jar also).
Thanks!

[robottaway]

Costin, I am working on those poms for rc3 release. Could you please help me by answering some questions:

I need to have a scm location, from the Spring source forge hosting. I put together:

scm:cvsserver:anonymous:@springframework.cvs.sourceforge. net:/cvsroot/springframework:spring

I found the info to put this together from:

http://maven.apache.org/ref/current/...del/maven.html
http://sourceforge.net/cvs/?group_id=73357

Next up is a license. I need a url to your guys license. Or if more than one to a set of licenses being used. I believe this should suffice for the POM's:

<licenses>
<license>
<name>The Apache Software License, Version 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
<distribution>repo</distribution>
</license>
</licenses>

Last but not least, where can I find the dependencies? I used a set of poms for the m4 release found in Maven's central repos:

http://www.ibiblio.org/maven/org.springframework/poms/

The set of poms I found there does not cover every module in spring. I will post later on which ones I need info on.

I excluded all optional and test dependencies, seeing how these shouldn't be included. But the thing is the list is a little short. For spring-core the only dependencies are:

<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
<version>1.0.4</version>
</dependency>
<dependency>
<groupId>commons-collections</groupId>
<artifactId>commons-collections</artifactId>
<version>3.1</version>
</dependency>

Is this right? How could I find out. I want to make sure that when a user checks out the release they get all the needed Spring dependencies. When you guys release the final 2.0 I can upload poms for that release. It will be easier if everything is right this time, so next time it is a snap.

I am attaching the spring-core-2.0-rc3 pom I have put together, so that you may peer review it (if you like).

I should zip up the collection of poms and put them on JIRA when I finish? I will have a number of poms, one for each spring jar that I am doing.

Sorry bout the long post.

[Costin Leau]

Thanks for the contribution but I'm really not the person to discuss the maven stuff. Besides the links I've already posted maybe this one will help: http://blog.interface21.com/main/200...e-in-the-jira/

[Ben Hale]

For anyone still lurking that wouldn't mind some quick sanity testing, drop me a PM and we'll see about getting you involved.