I think in general we need to discuss 286 branch management before
moving too far with shuffling bits of code around between the branch and
trunk.
E.g. if 286 is going to be promoted to trunk, then svn-wise it may be
problematic to port forward stuff from trunk into 286, then later try to
promote it to trunk.
It may be easier to port the patches from the 286 branch back to the
trunk; along the way you will get assembly for free.
Craig Doremus (JIRA) wrote:
Copy assembly module from trunk to 286-COMPATIBILITY branch
-----------------------------------------------------------
Key: PLUTO-395
URL: https://issues.apache.org/jira/browse/PLUTO-395
Project: Pluto
Issue Type: Improvement
Components: build system
Affects Versions: 1.1-286-COMPATIBILITY
Reporter: Craig Doremus
Assignee: Craig Doremus
Fix For: 1.1-286-COMPATIBILITY
Copy assembly module from trunk to 286-COMPATIBILITY branch. This will also
involve merging other code -- primarily in the maven plugin module -- that will
allow us to build releases using maven 2 without having to change version
numbers in multiple places.
