Got it.
As the "source" issue is there since the beginning, I would let this
vote finish and I will prepare the "source fix" for the next bundles
release.
Regards
JB
On 05/21/2012 09:53 PM, Gert Vanthienen wrote:
L.S.,
Unfortunately, I don't really think that the included pom.xml is enough.
In order to rebuild a bundle from source, a user would have to extract
that pom.xml file, copy that to a directory and also copy the
bundle.infofile into the project again to get something that can be
built.
Personally, I'd like to avoid having two separate artifacts (a -source
file containing the original sources and another source assembly with the
original source tree contents) as well, but there's probably no way around
that.
Anyway, the real question is: how do we want to continue with this vote
thread? Should we cancel it pending a solution for the sources artifacts
or can we continue with the vote and fix this for the next set of bundles
to be released?
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Mon, May 21, 2012 at 9:14 PM, Jean-Baptiste Onofré<[email protected]>wrote:
It's already included.
If you take a look in the sources jar, our pom is included, etc.
It's merge between the original artifact sources and our sources.
Regards
JB
On 05/21/2012 08:41 PM, Gert Vanthienen wrote:
Jean-Baptiste,
I think Andreas is talking about releasing our source code, i.e. the POM
file we use to build the bundle. This is the same problem as with the
specs release last week, where we already have the sources jar that
contains the actual spec source files, but we don't ship the sources for
our own POM files/bundle.info files/... yet, i.e. the archive that people
can download and build themselves to reproduce our artifacts.
We could add that to every single bundle as a separate
-source-assembly.zip
file or something, but that seems like a lot of artifacts just to release
a
wrapped bundle and those source artifacts would only contain one or two
files. Perhaps we could somehow build a single source artifact for every
set of bundles we release, e.g. by creating a single unified release build
to release all bundles to be released in one go?
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.**blogspot.com/<http://gertvanthienen.blogspot.com/>
On Mon, May 21, 2012 at 6:50 PM, Jean-Baptiste Onofré<[email protected]
wrote:
Hi Andreas,
The bundle source distributions are also available, when the underlying
project provide it.
For instance:
http://repo.maven.apache.org/****maven2/org/apache/servicemix/****<http://repo.maven.apache.org/**maven2/org/apache/servicemix/**>
bundles/org.apache.servicemix.****bundles.commons-codec/1.3_5/****
org.apache.servicemix.bundles.****commons-codec-1.3_5-sources.****jar<
http://repo.maven.**apache.org/maven2/org/apache/**
servicemix/bundles/org.apache.**servicemix.bundles.commons-**
codec/1.3_5/org.apache.**servicemix.bundles.commons-**
codec-1.3_5-sources.jar<http://repo.maven.apache.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.commons-codec/1.3_5/org.apache.servicemix.bundles.commons-codec-1.3_5-sources.jar>
So it's already done ;)
Regards
JB
On 05/21/2012 06:14 PM, Andreas Pieber wrote:
+ 1 non binding.
Nevertheless we should definitely try to provide source releases. At
least
for the parts done at smx
Kind regards, Andreas
On May 19, 2012 3:22 PM, "Jean-Baptiste Onofré"<[email protected]>
wrote:
Hi all,
I submit a new ServiceMix Bundles release to your vote.
This release includes:
- bundles-pom 9
- ezmorph 1.0.6_1
- hadoop-core 0.20.203.0_2
- hadoop-core 1.0.0_2
- json-lib 2.4_1
- lucene 3.6.0_1
- qpid 0.14_1
- saxon 9.3.0.11_2
- saxon 9.4.0.1_2
- solr-solrj 3.6.0_1
These bundles are especially needed by Camel and fix issues.
Staging repository:
https://repository.apache.org/******content/repositories/**<https://repository.apache.org/****content/repositories/**>
<ht**tps://repository.apache.org/****content/repositories/**<https://repository.apache.org/**content/repositories/**>
orgapacheservicemix-102/<**https**://repository.apache.**org/**<http://repository.apache.org/**>
content/repositories/****orgapacheservicemix-102/<https**
://repository.apache.org/**content/repositories/**
orgapacheservicemix-102/<https://repository.apache.org/content/repositories/orgapacheservicemix-102/>
Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Do not approve the release (please provide specific comments)
This vote will be open for 72 hours.
Thanks,
Regards
JB
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
