Access to m4 snapshot via maven?

[mm04]

Regarding the time it took to figure out the artifactIds - were you using ...

I did eventually find that site, but as I said, it's not entirely obvious how to map the old names to the new ones in all cases even with the repository open in front of you. I figured it out eventually, so no problem there.

Still, I suspect some users might not be able to do so as easily due to certain restrictions. In the worst case scenario they may not even notice for some time that javaconfig pulled in the duplicates - my application worked just fine with the duplicated jars being deployed onto the web server, I only noticed it after looking at the maven dependency graph.

[jlillesand]

Bear with me if I'm misunderstanding something here, but it appears that the artifact IDs of dependencies in javaconfig's pom.xml isn't following the common practice. For example, the AOP dependency is expressed as follows:

    <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>org.springframework.aop</artifactId>
      <version>2.5.6</version>
      <optional>true</optional>
    </dependency>

The dependency syntax used other places (for example spring-ws) is the following:

   <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>spring-aop</artifactId>
   </dependency>

The consequence of these different practices is that all transient dependencies shared between javaconfig and other libraries are duplicated on the classpath by maven.

[Chris Beams]

Hi jlillesand,

You're quite right to point out what you're seeing. It's an unfortunate growing pain as we move each of the Spring portfolio projects from Maven Central to the SpringSource Enterprise Bundle Repository - some have updated and some have not. I've spoken with Arjen (author of spring-ws) about this, and he says he'll update the POM accordingly in the 1.5.6 timeline.

I've also created an issue to track this - you may want to add yourself as a watcher and/or vote for it: http://jira.springframework.org/browse/SWS-451

In the meantime, as you've probably figured out, everything should still work for you, you'll just be stuck with an irritating duplicate dependency (or a few) on the classpath. All Spring projects going forward will be using the artifactId nomenclature that JavaConfig M4 is currently using, so this problem will go away over time.

Thanks,

- Chris

[jlillesand]

Thanks for your response, Chris. As you correctly point out, everything works fine. I've both voted and added myself as a watcher, and hopefully we'll see this rectified in the future. Thanks for your help and your efforts with JC.

[azeckoski]

You're quite right to point out what you're seeing. It's an unfortunate growing pain as we move each of the Spring portfolio projects from Maven Central to the SpringSource Enterprise Bundle Repository - some have updated and some have not. I've spoken with Arjen (author of spring-ws) about this, and he says he'll update the POM accordingly in the 1.5.6 timeline.

Stupid question here. Does that mean all artifacts going forward (in the maven2 central repos etc.) will be using this syntax:

        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>org.springframework.context.support</artifactId>
        </dependency>

or this syntax?

        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>context-support</artifactId>
        </dependency>

Or are we talking about using seperate artifactIds in the different repos?

Also, just to be slightly argumentative this format seems to break from the one used by pretty much everyone else (as shown on the maven2 site). Is there a reason for this change? (just point me to a faq or whatever if I am being dense)

<project>
  <groupId>com.mycompany.app</groupId>
  <artifactId>my-module</artifactId>
  <version>1</version>
</project>

Thanks :-)

[nharward]

Wherever possible, the best plan is to always fetch dependencies out of the SpringSource repository. artifactIds, etc are always internally consistent within. I realize this can be a bit of a pain at first. I've directed our build team to take a look at this thread and add any additional comments.

Can this issue be solved for both of you by updating your poms to retrieve everything from our repository? If so, is that an acceptable solution? If not, please detail why (either way it's useful feedback for us).

Thanks,

- C

It would be very helpful to have that link and information on the main page, and in particular at (static dot springframework dot org) /spring-javaconfig/docs/1.0.0.M4/reference/html/ch01s08.html#jars-nightly-build-maven. Forgive the non-link, since this is my first post I am apparently not allowed to put links in my comment.

As a newcomer to Spring it took me a lot of time and pain to finally find this forum post, particular given that the solution is so simple.

Please consider adding information to the maven instructions that the main Spring repository should (additionally) be used, right now only the snapshot and externals repositories are given.