Maven 2 support (POMs) [SPR-1484]

[spring-projects-issues]

Aleksander Blomskøld opened SPR-1484 and commented

Maven 2 POMs with dependencies is missing for Spring. It's a lot of extra job for maven 2 users to find out which dependencies Spring needs, and to have to include them manually.

---

Attachments:

• buildsources.sh (590 bytes)
• spring-maven.tgz (10.81 kB)
• spring-poms-1.2.8.zip (22.40 kB)

Issue Links:

• maven pom hosed on repo1.maven.org [SPR-1510] #6209 maven pom hosed on repo1.maven.org ("is duplicated by")
• Missing m2 POMs at ibiblio.net [SPR-1839] #6533 Missing m2 POMs at ibiblio.net ("is duplicated by")

121 votes, 60 watchers

[spring-projects-issues]

Aleksander Blomskøld commented

Doh! Just found that the poms I was looking for were at http://www.ibiblio.org/maven2/org/springframework/ and not http://www.ibiblio.org/maven2/springframework/. Anyway, poms for 1.2.6 seems to be missng..

[spring-projects-issues]

Andreas Schildbach commented

This issue is still present for the 2.0 milestones. Those are also missing the sources (and javadocs).

[spring-projects-issues]

Carlos Sanchez commented

Lastest poms i've working with

[spring-projects-issues]

Wesslan commented

Does someone have POM's for 2.0-RC1 (sp I don't have to make them myself ;) yet?

[spring-projects-issues]

Andreas Schildbach commented

And sources, and javadocs?

[spring-projects-issues]

Wesslan commented

Sources and JavaDocs are included in the "official" (IE not snapshots) releases but maybe you already knew that. :)

[spring-projects-issues]

Andreas Schildbach commented

I'm afraid this is not true. See for example Spring 1.2.8

http://www.ibiblio.org/maven2/org/springframework/spring-beans/1.2.8/

This also only contains the jars.

[spring-projects-issues]

Wesslan commented

You're certainly right Andreas, my mistake.
On the other hand, should releases in Ibiblio (or some other Maven-repo) contain sources and docs? I should vote no to that. :-)
If I want sources and/or docs for a project, I'd go to their site and get it. :-)
Cheers

[spring-projects-issues]

Andreas Schildbach commented

I vote for yes, at least the sources (JavaDocs are debatable, as they can be generated from the sources on the fly).

The reason is that you can do "mvn -DdownloadSources=true eclipse:eclipse" in your project, and the sources of all dependencies (and transitive dependencies) are automatically downloaded and attached to the binary jars. This is extremely convenient and can save hours of work.

[spring-projects-issues]

Arik Kfir commented

Actually they should contain sources+javadocs, as the maven IDE plugins know to fetch them automatically and create the appropriate IDE project files with links to the downloaded sources/javadocs. This is very useful for maven users, as all you need to do is run "mvn idea" and violla! -> you have a working IDEA project file with spring libraries defined, and linked to the spring binaries....

[spring-projects-issues]

Wesslan commented

You convinced me guys. :-)

[spring-projects-issues]

Nicolas Peeters commented

Does anybody know when this is going to be available on ibiblio (or any other mirror)?

Thanks!

[spring-projects-issues]

Colin Sampaleanu commented

I've checked in the last set of POMs from Carlos.

I've done a bit of tweaking to get spring-beans building including tests, but at this point there are still issues as early as spring-aop, since there is a cyclical dependency between aop and context at the test class level.

This will probably only be resolved by moving that code to be tested as part of context. That's not incredibly lean now, but would be even less clean when/if the build is actually properly split up with different projects and source trees.

Colin

[spring-projects-issues]

Carlos Sanchez commented

I worked around that issues excluding them in the module they are and including them in a higher level one.
eg. that aop test can be excluded in spring-aop and included in spring-context

[spring-projects-issues]

Colin Sampaleanu commented

In this case I've talked to Mark F. and he'll just redo that test to not use the context (it can use an XmlBeanFactory). For sure though for some pieces of code it will just be easier to do some tests as part of another module than what they are theoretically in by area of functionality.