Hi, My comment inline －－－－－－－－－－－－－ Freeman(Yue) Fang
Red Hat, Inc. FuseSource is now part of Red Hat Web: http://fusesource.com | http://www.redhat.com/ Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: @Freeman小屋 www.camelone.org : The open source integration conference: On 2013-5-10, at 下午7:30, Daniel Pocock wrote: > On 10/05/13 10:45, Freeman Fang wrote: >> Hi, >> >> My comment inline >> －－－－－－－－－－－－－ >> Freeman(Yue) Fang >> >> Red Hat, Inc. >> FuseSource is now part of Red Hat >> Web: http://fusesource.com | http://www.redhat.com/ >> Twitter: freemanfang >> Blog: http://freemanfang.blogspot.com >> http://blog.sina.com.cn/u/1473905042 >> weibo: @Freeman小屋 >> >> www.camelone.org : The open source integration conference: >> >> On 2013-5-10, at 下午4:25, Daniel Pocock wrote: >> >>> Hi, >>> >>> I would like to do an offline source build of the ServiceMix stack >>> (including dependencies and essential plugins required during the build). >>> >>> I had a look at the web site and it suggests letting Maven obtain >>> dependencies in binary form >>> http://servicemix.apache.org/developers/source.html >>> >>> I looked at the Apache instance of Jenkins and it is not clear whether >>> that is also building dependencies or just fetching some of them in >>> binary form. Is there a convenient way to replicate the Jenkins >>> configuration to a local Jenkins instance and use that to build >>> everything up from source? >> Jenkins build also use maven to download the binary jar >>> Can anybody clarify how to get all the necessary sources without >>> manually downloading each project? >> You probably can use >> mvn eclipse:eclipse -DdownloadSources=true >> to build the Servicemix which can download source jar of each dependency to >> your local maven repo > > If I understand correctly (this has been discussed on the maven-users > list too at the moment), using downloadSources doesn't retrieve enough > data to build the dependencies, as the source JARs in Maven repositories > are just for the convenience of debugging tools. right, this is the most easy way that I know to collect src from dependencies, though the source jar may miss the files/scirpts for build, considering we can have several ways to build the jars(maven, graddle, etc) > > >>> Also, where are the tags kept? I looked at SVN and only found what >>> appears to be a trunk, no tags or branches directories: >>> http://svn.apache.org/repos/asf/servicemix/smx4/all/ >> The tags are in each sub-projects under >> http://svn.apache.org/repos/asf/servicemix/smx4/ > > When a single ServiceMix "Full assembly" tarball is distributed (e.g. > 4.5.1 on the web site now), how is that derived from those tags? Take a look the issue[1] which track servicemix release, you can get more concrete idea how Servicemix get released, several dependencies are sub projects in SMX and released separately [1]https://issues.apache.org/jira/browse/SMX4-1257
