I pulled those parts out and replaced them with ... to make the example
smaller. I didn't think those parts relevant, but apparently they are since the
following suggested by Stuart McCulloch does work:
Include-Resource{maven-resources},
Hi,
I am currently working on a project which has required us to branch
[0] Gora trunk and begin some slight APi refactoring to accommodate
the added functionality we intend to implement.
I have one question though. If I do a clean checkout of the code then
run mvn clean compile I get a failure
On 2012-08-12 18:34, Lewis John Mcgibbney wrote:
Hi,
Hi
I am currently working on a project which has required us to branch
[0] Gora trunk and begin some slight APi refactoring to accommodate
the added functionality we intend to implement.
I have one question though. If I do a clean
from now on we're going to rely on you... as our BND expert!
Glad to hear that worked
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
Hi Dennis
On Sun, Aug 12, 2012 at 7:28 PM, Dennis Lundberg denn...@apache.org wrote:
No. My gut feeling is that you have something wrong in your dependency
tree regarding your internal modules. Looking at the parent pom.xml you
seem to be using test jars in two different ways. Either
If you use the packagingbundle/packaging style in your pom, then its bnd
that does the actual jar creation, and NOT the traditional jar plugin.
We hit this same issue awhile ago when including compiled coffee-script into
our jars, just putting them directly in target/classes doesn't just work.
Greetings,
When I update from 3.0 to 3.1 I get the error below. I've reproduced it on a
couple projects, but here is a relatively simple POM that manifests the issue
when updated:
https://github.com/themadcreator/rabinfingerprint/blob/447cd065825b97e62a9b100f080ba217ba821de7/pom.xml
Is this
