https://repository.apache.org/content/repositories/snapshots/org/apache/camel/camel-core/2.15-SNAPSHOT/
If you take a look at latest snapshot build - it does not contain sources,
sources as published for the previous snapshot, but maven sees that there
newest build and ignores sources.
Something w
Maybe because the build failed because the source artifact was published.
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-muel
I just kicked the CI build of Camel trunk, the deployment[1] is OK now.
[1]https://builds.apache.org/job/Camel.trunk.notest/2212/
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo
There is still no sources for latest build only for previous one. I guess
this has something to do with set of profiles enabled for "no tests" build
and "all tests" build.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-2-15-SNAPSHOT-dependency-missing-sources-in-repo-
It looks the Jenkins deploy the projects twice.
I just did some change on the Camel.trunk.notest job of the Jenkins, now I just
kicked another build, to see if the change works.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://j
I see some snapshot sources now.
Thanks!
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-2-15-SNAPSHOT-dependency-missing-sources-in-repo-tp5758495p5758541.html
Sent from the Camel - Users mailing list archive at Nabble.com.
