book module is broken

[GoogleCodeExporter]

During the build (in maven command line, or in eclipse), the book doesn't 
generate a jar file.

From the mailing list:

In order to get consistent behavior for code and test modules, a lot of 
behavior is defined in the root pom. Unfortunately, this makes the archiving 
(jar-ing, bundle-ing) of the book module fail. I ought to be able to disable 
this in the book pom, but all my efforts to date have been unsuccessful. The 
workaround, for now, is to set the module to <packaging>pom</packaging>. This 
is wrong, but it lets the build succeed. The things causing problems are the 
maven-jar-plugin and maven-bundle-plugin bits in the root pom (manifest 
generation, jar naming and stuff).

Original issue reported on code.google.com by aale...@gmail.com on 29 Aug 2012 at 2:05

[GoogleCodeExporter]

I know how to fix this, but it's kinda drastic.

It's failing because behavior is defined on the root pom. If the root pom 
points at a code-module-root pom and a sort of miscellaneous-root pom, then we 
can continue putting the bndtools cnf project as a sibling to all of the 
projects that it needs to be sibling to, and the shared behavior would move 
into the code-module-root pom.

Unfortunately, that means another big shift in locations, which sucks (it will 
also break people's IDEs, yet again). I wish bndtools did not have the location 
restriction.

Original comment by aale...@gmail.com on 26 Oct 2012 at 7:34

[GoogleCodeExporter]

Change milestone

Original comment by aale...@gmail.com on 24 Oct 2013 at 5:17

• Added labels: Milestone-Release1.1
• Removed labels: Milestone-Release1.0