[ http://jira.codehaus.org/browse/MASSEMBLY-62?page=comments#action_56682 ]
Dan Tran commented on MASSEMBLY-62:
-----------------------------------
Entry into each subassembly is a filename relative to ${basedir}. User can
specify fullpath.
The DependencySets, FileSets, and FileItems if each subassembly will be
appended to the main one, the Assembly itself.
Parsing and processing of subassemblies should not be any different from the
main one.
To go into details, the Assembly will have 3 sections
Assembly
// Header
id
formats
includeBaseDirectory
includeSiteDirectory
// Body
List of DependencySet
List of FileItems
List of FileSets
List of SubAssemblyDescriptor
SubAssemblyDescriptorFileName
List of DependencySet <--------- This
subassembly will be appended to the main Body when we loadup the Assembly
List of FileItems
List of FileSets
In this case, I can have a bunch of fixed sub assemblies that main assembly can
pick and ad its own in the body.
This is the same concept of installanywhere where they call Components ( vs
subassembly)
Sorry I am not sure how to visualize the single <parentDescriptor> concept, Are
you suggesting inheritent set?
> Ability to share DependencySets, FileSets, FileItems
> ----------------------------------------------------
>
> Key: MASSEMBLY-62
> URL: http://jira.codehaus.org/browse/MASSEMBLY-62
> Project: Maven 2.x Assembly Plugin
> Type: New Feature
> Versions: 2.0
> Environment: xp, linux
> Reporter: Dan Tran
>
>
> My assembly project can produce multiple assemblies thru mutliple
> descriptors. I need ability to have multiple descriptor to share common
> elements
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
