[BUILD-14] Provide simple-bundle assembly Created: 04/Jun/09  Updated: 13/Apr/17  Resolved: 17/Dec/09

Status: Closed
Project: Build
Component/s: Build Tools, Poms
Affects Version/s: None
Fix Version/s: Module Assembly 1.2.3, POMs 15

Type: New Feature Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing BUILD-51 Fix "simple" bundles so they don't ne... Closed
dependency
is depended upon by MGNLNEWSLETTER-18 Bundle shouldn't include unnecessary ... Closed
is depended upon by MGNLSTK-520 Bundle shouldn't include unnecessary ... Closed
relation
is related to MGNLEE-150 bundling : since update of maven-asse... Closed
is related to BUILD-26 bundle: have processed AND unprocesse... Closed
is related to BUILD-19 Build tools improvements Closed
Template:
Acceptance criteria:
Empty

 Description   

In STK or newsletter, for instance, we want to generate simple bundles with appropriate README.txt files etc. There is currently an issue with our default assembly if these bundle projects use the pom packaging (which is why they use the jar packaging, which then produces an empty jar in the bundle, which not exactly sexy)

See



 Comments   
Comment by Magnolia International [ 08/Jun/09 ]

Using useProjectArtifact in the assembly descriptor might help with this issue. We'd then probably need a different assembly descriptor for those "ad-hoc bundles" (as opposed to the single-module ones like dms or data module)

Comment by Magnolia International [ 11/Nov/09 ]

If your bundle should not include it's own artifact (in the case of a "simple" bundle as mentioned above), you need to add the <bundleIncludingSelf>false</bundleIncludingSelf> to your pom's <properties> section.

"simple" bundle projects should stick to the jar packaging, otherwise README and other files aren't generated (because the maven-remote-resource-plugin doesn't get triggered in the pom build lifecycle)

Comment by Magnolia International [ 17/Dec/09 ]

pom v13 completely broke regular module bundles. (i.e only works with modules setting bundleIncludingSelf to true...)

Comment by Magnolia International [ 17/Dec/09 ]

Modules which need a regular bundle don't have anything to do. Can upgrade to parent pom v14.
Modules which needed to set the bundleIncludingSelf property to false should now use this instead:

  <defaultAssemblyDescriptor>simple-assembly-descriptor</defaultAssemblyDescriptor>

The default value for this property is module-assembly-descriptor, which corresponds to the assembly descriptor where useProjectArtifact is set to true. simple-assembly-descriptor is identical, except that its useProjectArtifact is set to false.

Generated at Sun Feb 11 23:37:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.