I was wondering whether this was a problem with the snapshots that are deployed to the apache snapshot repo. It seems there is something funny going on because while the build for the new ...default.local.platform module passed, there is a problem in the output [1] and a snapshot of this module hasn't been deployed to the snapshot repo. Investigating.
[1] https://hudson.apache.org/hudson/job/Aries/703/org.apache.aries.application$org.apache.aries.application.default.local.platform/console Cheers, Jeremy On 13 October 2010 15:55, Jeremy Hughes <[email protected]> wrote: > Hi, I did a mvn dependency:go-offline to get my .m2 populated with all > the dependencies. It downloads 0.3-incubating-SNAPSHOT builds too but > barfed on finding a snapshot of > org.apache.aries.application:org.apache.aries.application.default.local.platform:jar:0.3-incubating-SNAPSHOT > > The full error is: > Missing: > ---------- > 1) > org.apache.aries.application:org.apache.aries.application.default.local.platform:jar:0.3-incubating-SNAPSHOT > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.aries.application > -DartifactId=org.apache.aries.application.default.local.platform > -Dversion=0.3-i > ncubating-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file there: > mvn deploy:deploy-file -DgroupId=org.apache.aries.application > -DartifactId=org.apache.aries.application.default.local.platform > -Dversion=0.3-inc > ubating-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] > -DrepositoryId=[id] > > Path to dependency: > 1) > org.apache.aries.application:org.apache.aries.application.runtime.isolated.itests:jar:0.3-incubating-SNAPSHOT > 2) > org.apache.aries.application:org.apache.aries.application.default.local.platform:jar:0.3-incubating-SNAPSHOT > > ---------- > > which I believe means a 0.3-incubating-SNAPSHOT of > ...application.runtime.isolated.itests was published that depends on > the default.local.platform snapshot without that snapshot having been > published. I can fix - I just wanted to highlight this so we avoid the > situation in the future. > > Cheers, > Jeremy >
