[BUILD-58] site-deploy on ce && ee bundle does not work without skipping clover Created: 06/Dec/10  Updated: 28/Jun/12  Resolved: 28/Jun/12

Status: Closed
Project: Build
Component/s: None
Affects Version/s: POMs 19
Fix Version/s: POMs 24

Type: Improvement Priority: Minor
Reporter: Daniel Lipp Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File CLV-5796 Maven plugin can't seem to be able to completely skip Clover execution build forking wh.webarchive    
Issue Links:
duplicate
is duplicated by BUILD-90 Separate parent poms for builds using... Closed
supersession
is superseded by BUILD-110 Add a way to completely skip Clover Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When running "mvn clean package site-deploy" on ce or ee bundle you get something like:

[INFO] [jar:jar

{execution: default-jar}

]
[INFO] Building jar: /Users/daniellipp/Downloads/ce-bundle-4.4.1/magnolia-integration-tests/tests/target/clover/magnolia-integration-tests-4.4.1-clover.jar
[INFO] [cargo:start

{execution: start}

]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Artifact [info.magnolia:magnolia-test-webapp:war] is not a dependency of the project.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------

You currently have to disable clover in order to get it run.

Release-Wiki-Page (http://wiki.magnolia-cms.com/display/DEVINT/Release+process) got adapted accordingly.



 Comments   
Comment by Magnolia International [ 03/Nov/11 ]

"For more information, run Maven with the -e switch". Yes, please do that !
Or even with -X to get full debug output (don't forget to push the output into a file, you don't want to have to copy paste all that)

Comment by Magnolia International [ 03/Nov/11 ]

Can't investigate this without more info.

Comment by Magnolia International [ 11/Apr/12 ]

I just got some feedback on the support issue I reported a while ago with Atlassian (CLV-5796), and they proposed a solution that seems to make sense. Not sure why we haven't done it like that in the past. Essentially, the whole clover configuration is moved into a specific profile, and the key is that that profile is activated via a property (and a certain value). Remains to be seen if this works when said property is defined in the pom.

Comment by Magnolia International [ 11/Apr/12 ]

See CLV-5796 in attachment as well as http://stackoverflow.com/questions/1501294/maven-skip-parent-project-build/1502322#1502322 - we might have to activate the property via the presence/absence of a "marker" file.

Comment by Magnolia International [ 28/Jun/12 ]

Please see BUILD-110 for summary and proposed solution.

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