Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Problem with surefire tests & exploded bundle


I have the same constraint in one of my plugins. I use only the Eclipse-BundleShape directive.
I had no problems but I have to check if one of my tests is using this feature.


On Tue, May 28, 2013 at 8:37 AM, Laurent PETIT <laurent.petit@xxxxxxxxx> wrote:
Nobody encountered this problem before ?

Le dimanche 26 mai 2013, Laurent PETIT a écrit :


My project requires that my core bundle be exploded to work.

Unit tests which work from my Development environment neither work
locally via mvn command, neither externally on travis-ci.

I have taken care of doing the following:

- originally (for user deployment time), my feature declares that the
bundle must be unpacked
- I have also added an
sufire configuration to the pom of my tests
- I have also added an Eclipse specific META-INF directive,
"Eclipse-BundleShape: dir", to my core plugin, as suggested somewhere
(in the FAQ I guess ? Or was it on StackOverflow, don't remember).

I have made the last 2 additions incrementally, so I had first tested
without both, then with the <explodedBundles>, then with the MANIFEST
Eclipse specific directive.

on Travis-ci (Ubuntu Server 12.04, the build fails with this root exception:
 "Caused by: org.codehaus.plexus.archiver.ArchiverException: chmod
exit code was: 2"

on my local machine, same chmod issue, but the exit code is 1 instead
of 2 (I have a Mac Book Air with OS X Lion)

link to the failed build on travis:
link to the project on github:

Any idea ?

Thanks in advance,


tycho-user mailing list


"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

Back to the top