You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicemix.apache.org by "Krzysztof Sobkowiak (JIRA)" <ji...@apache.org> on 2015/05/07 18:24:01 UTC
[jira] [Comment Edited] (SM-2547) Perform some housekeeping in poms
[ https://issues.apache.org/jira/browse/SM-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532936#comment-14532936 ]
Krzysztof Sobkowiak edited comment on SM-2547 at 5/7/15 4:23 PM:
-----------------------------------------------------------------
Following changes have been performed
* root and parent poms re-formatted
* dependency management moved to parent pom
* parameters sorted
* some plugins moved to parent
The differences between the poms in {{master}} and {{servicemix-5.4.x}} checked with diff. No changes which could make problems with merges between the both branches
was (Author: sobkowiak):
Following changes have been performed
* root and parent poms re-formatted
* dependency management moved to parent pom
* some plugins moved to parent
The differences between the poms in {{master}} and {{servicemix-5.4.x}} checked with diff. No changes which could make problems with merges between the both branches
> Perform some housekeeping in poms
> ---------------------------------
>
> Key: SM-2547
> URL: https://issues.apache.org/jira/browse/SM-2547
> Project: ServiceMix
> Issue Type: Task
> Reporter: Krzysztof Sobkowiak
> Assignee: Krzysztof Sobkowiak
> Fix For: 5.4.1, 5.5.0, 6.0.0.M2, 6.0.0
>
>
> Our root and parent pom became a bit messy, e.g. properties are defined in either in root or in parent, they are unsorted. There are also some no more existing dependencies in dependency management.
> We should do some housekeeping before we create new branches. It makes the state of {{master}} and {{servicemix-5.4.x}} poms a bit incompatible with the previous versions but I don't expect a lot of merges from {{servicemix-5.4.x}} into the previous branches and we can simply manually make the changes. It's important to have a clear state in the branches we are focusing now
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)