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: 姜宁willem On November 5, 2014 at 4:52:57 AM, Christian Müller (christian.muel...@gmail.com) wrote: > 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-mueller/11/551/642 > > On Tue, Nov 4, 2014 at 10:02 AM, vasilievip wrote: > > > > > 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 with daily build configuration? > > > > no_sources.PNG > > > > > > > > > > -- > > View this message in context: > > http://camel.465427.n5.nabble.com/Camel-2-15-SNAPSHOT-dependency-missing-sources-in-repo-tp5758495.html > > > > Sent from the Camel - Users mailing list archive at Nabble.com. > > >
