[
https://issues.apache.org/jira/browse/SLING-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661543#action_12661543
]
Felix Meschberger commented on SLING-815:
-----------------------------------------
I have tested a full build on my (linux) box:
* removed all sling artifacts from my local m2 repository
* run mvn clean in the root folder
--> reactor seems clean extensions/threaddump before launchpad
* run mvn clean install in the root folder
--> reactor seems to build threaddump before launchpad
So it seems, that if the module is registered in the root pom (as I have done
in Rev. 732275) and no further dependency registration is thus required.
Other observations are welcome.
> Launchpad/app build fails due to missing threaddump artifact
> ------------------------------------------------------------
>
> Key: SLING-815
> URL: https://issues.apache.org/jira/browse/SLING-815
> Project: Sling
> Issue Type: Bug
> Components: Launchpad
> Affects Versions: Launchpad App 3, Launchpad Webapp 3, Launchpad App 4,
> Launchpad Webapp 4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Launchpad App 4, Launchpad Webapp 4
>
>
> I have added the extensions/threaddump module to the build reactor and the
> launchpad/app project to be included in the standalone app and webapp.
> Since the "dependency" is not list in the standard dependency section of the
> pom but in the configuration of the dependency plugin, the maven reactor does
> not seem to correctly resolve the build order and does not build the
> threaddump artifact before the launchpad/app artifact.
> As a workaround, I will add the extensions/threaddump artifact as an explicit
> dependency to the launchpad/app to help the reactor.
> See also
> http://markmail.org/message/hc7kwforfblvxjzr
> http://markmail.org/message/n6rclxsgaeoijajh
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
