[DOCU-549] Make sure documentation projects build for ce-users Created: 23/Jan/15  Updated: 05/Feb/15  Resolved: 05/Feb/15

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Christoph Meier Assignee: Christoph Meier
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

Make sure that all documentation projects build for ce-users
(except for documentation-trait-tutorial which requires ee-license and appropriate ee-user maven settings.)
If they undergo releases, it is okay when they use magnolia parent pom.

Only the example project should NOT use magnolia parent pom, since it is explicit explained that it was created with the magnolia archetype.


old description:

When using the magnolia-parent-pom-community, the build depends on some magnolia maven plugins, for which <pluginRepositories/> is required (depending on the maven settings of the user).

Demo-projects explaining users how to do their stuff should NOT rely on magnolia parent poms.

=> Fix the poms removing that parent pom for:
– documentation-reuse-content
– documentation-trait-tutorial
– example-project
– flickr-integration-parent
– fs-browser-app
– using-resources-parent

Note that some of these projects also must released.



 Comments   
Comment by Christoph Meier [ 26/Jan/15 ]

documentation-check-maven-settings is just to test ee-user maven settings.

Comment by Christoph Meier [ 26/Jan/15 ]

documentation-reuse-content builds fine (for a ce-user). No changes required.

Comment by Christoph Meier [ 26/Jan/15 ]

documentation-trait-tutorial build with maven settings for an ee-user.

Beside that, module has been updated - raise magnolia version to 5.3.6 and personalization version to 1.1 - and released (and doc updated).

Comment by Christoph Meier [ 26/Jan/15 ]

example-project never gets released.
But here i had to remove the magnolia parent pom, since in the documentation (see http://documentation.magnolia-cms.com/display/DOCS/Creating+a+custom+bundle) it is said the the project was created with magnolia-archetype.

Comment by Christoph Meier [ 26/Jan/15 ]

Fixed pom for flickr-integration (and its submodules) and released 1.0.4.

Comment by Christoph Meier [ 26/Jan/15 ]

fs-browser-app builds fine. No reason to change atm.

Generated at Mon Feb 12 01:10:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.