[
https://jira.codehaus.org/browse/MNG-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MNG-5535.
-------------------------------
Resolution: Not A Bug
Assignee: Robert Scholte
It's there already for a long time.
Some related parts from {{mvn -h}} or {{mvn --help}}
{noformat}
usage: mvn [options] [<goal(s)>] [<phase(s)>]
Options:
-am,--also-make If project list is specified, also
build projects required by the
list
-amd,--also-make-dependents If project list is specified, also
build projects that depend on
projects on the list
-pl,--projects <arg> Comma-delimited list of specified
reactor projects to build instead
of all projects. A project can be
specified by [groupId]:artifactId
or by its relative path.
{noformat}
> support sparse build
> --------------------
>
> Key: MNG-5535
> URL: https://jira.codehaus.org/browse/MNG-5535
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Bootstrap & Build, Dependencies
> Environment: maven 3.1
> Reporter: Jigar Joshi
> Assignee: Robert Scholte
> Priority: Minor
>
> h2. background
> I have maven project structure of around 220 projects in a big maven
> hierarchy, to build some I don't need to build all of them but only some
> which are really required via dependency reachout
> for example
> {code}
> root
> |
> |---a
> | |---a1 (needs b1)
> |
> |---b
> | |---b1 (needs b2)
> | |---b2 (needs nothing)
> |
> |---c
> {code}
> In My case I am using assembly plugin to create fat jar of a1 which includes
> a1,b1,b2 and some other third party jars
> what I have to do now is
> clean install on b1, b2
> clean install -Ppackage on a (artifact)
> (or else I can go with the costlier approach where I let full project tree
> build first and then let it package )
> package profile is configured to generate far jar packing b1, b2 & some third
> party jars inside
> this is just a minimal example
> It would be great if maven could detect b1 & b2 (in this case) and installs
> them first before packaging a1
> Thanks!
> Jigar
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
