2 Replies Latest reply on Aug 7, 2007 11:24 AM by pgier

jboss-aop-mc-int-2.0.0-SNAPSHOT POM broken

manik Aug 7, 2007 4:59 AM

The POM for jboss-aop-mc-int-2.0.0-SNAPSHOT has a dependency on jboss-commons-core-2.0.4.Alpha2.

This, in turn, has a dependency on jboss-commons-logging-spi-2.0.2, which is not available in the repository (there's only 2.0.4.GA in http://repository.jboss.org/maven2/jboss/jboss-common-logging-spi/) and causes any project depending on jboss-aop-mc-int-2.0.0-SNAPSHOT to break.

The actual break, I suspect, is in the jboss-aop-mc-int POM which specifies that it requires commons-core-2.0.4.Alpha2 and this prevents maven from using commons-core-2.0.4.GA.

http://repository.jboss.org/maven2/jboss/jboss-aop-mc-int/2.0.0-SNAPSHOT/jboss-aop-mc-int-2.0.0-20070213.133620-1.pom

1. Re: jboss-aop-mc-int-2.0.0-SNAPSHOT POM broken

pgier Aug 7, 2007 11:19 AM (in response to manik)

Hey Manik,
That is an old snapshot of aop-mc-int. You should use the one here instead:
http://snapshots.jboss.org/maven2/org/jboss/microcontainer/jboss-aop-mc-int/2.0.0-SNAPSHOT/

Anything that is a snapshot version should be in the snapshots repository, and not in the regular repo. I'll remove that version from repository.jboss.org, since it shouldn't be in there.
Actions
2. Re: jboss-aop-mc-int-2.0.0-SNAPSHOT POM broken

pgier Aug 7, 2007 11:24 AM (in response to manik)

There are some other 2.0.0-SNAPSHOT versions of microcontainer components in the releases repository (container, kernel, dependency, etc). I'm going to remove those also as long as no one has any objections.
Actions