Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] tycho-compiler vs tycho-packaging when building multiple jars with

I would absolutely love to get rid of the nested jars. But there are a litany of other issues with the codebase(s) that prevent building each jar as a separate [fragment] bundle to a common host bundle. Fortunately the other issues are resolved in a future release so we will be switching to decent long-term solution with proper bundles and features. I just wanted to make sure that in this release where I have to go with nested jars I haven’t overcomplicated the implementation. And it sounds like I haven’t.


From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Sievers, Jan
Sent: Wednesday, March 05, 2014 3:02 AM
To: Tycho user list
Subject: Re: [tycho-user] tycho-compiler vs tycho-packaging when building multiple jars with


As Igor said, try to avoid nested jars.

this behaviour is basically due to the limitation of bin.includes which demands the same filesystem structure in the project basedir as packaged in the bundle jar.


If you have to, there are two things you can do


1. configure maven-clean-plugin to wipe the generated jars during clean phase, see [1]

2. add generated jars to .gitignore (or similar for your SCM)







From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Justin Georgeson
Sent: Dienstag, 4. März 2014 18:43
To: tycho-user@xxxxxxxxxxx
Subject: [tycho-user] tycho-compiler vs tycho-packaging when building multiple jars with


When I use the source.<lib> properties in the tycho-compiler plugin outputs to ${}/<lib>-classes, but tycho-packaging:package-plugin outputs to ${basedir}/<lib>. Is that because the bin.includes are relative to ${basedir}? I like to standardize on having all build-process generated output created under a known folder, so that developers universally know they can delete that folder to force a full clean rebuild. But this inconsistency between compiler and packaging is making that configuration a bit cumbersome. I can use the additionalFileSets instead of bin.includes to include the jar files in my plugin, but using “” means I then need to use “${}/target/…” when staging files for each source.<lib> in my pom.xml, because there is no bin.includes.<lib> I can put in my (at least not according to


So while I _can_ get it configured and working, the inconsistency between tycho-compiler and tycho-packaging is a bit cumbersome to work with (if keeping all your build output under the target folder is important to you). Am I overcomplicating the configuration somewhere? Can there be better consistency in a future release?


This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.

Back to the top