[
https://issues.apache.org/jira/browse/SLIDER-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235512#comment-14235512
]
Billie Rinaldi commented on SLIDER-655:
---------------------------------------
No, actually. It did initially seem like that was the problem, but the real
issue is that we're using mvn versions:set in the build process. This runs at
the top level and modifies the versions in all the poms it knows about. Then
when we go to build app packages, they can't find a parent that has the old
version. Running versions:set again in app-packages fails, also because it
can't find the parent.
> split app packages out of slider POM for independent releases
> -------------------------------------------------------------
>
> Key: SLIDER-655
> URL: https://issues.apache.org/jira/browse/SLIDER-655
> Project: Slider
> Issue Type: Improvement
> Components: app-package
> Affects Versions: Slider 0.60
> Reporter: Steve Loughran
> Assignee: Steve Loughran
>
> the app-packages/* projects are set up as sub-projects of slider, yet they
> have their own independent versions set by maven properties. This broken the
> release process, and will complicate releasing app packages independently.
> proposed:
> make each app package an independent build, depending on slider components,
> but in their own builds
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)