maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Commented: (MNG-249) compile and package should be reactor-aware
Date Tue, 05 Apr 2005 15:31:56 GMT
     [ ]
Brett Porter commented on MNG-249:

I think this is possible, and a good idea.

the compile phase does not require the resources of the other projects - just their classes.
So when getting the classpath elements in maven-core, anything inside the reactor for compile
can be passed back as target/classes directories, etc.

My only problem with this is if too much hardwiring of phase <-> code occurs in maven-core.
That would need some investigation, but in theory this is a good idea.

It will also be a little faster, and makes the compile step somewhat more atomic (if compile
fails, nothing is installed, for example)

> compile and package should be reactor-aware
> -------------------------------------------
>          Key: MNG-249
>          URL:
>      Project: m2
>         Type: Improvement
>   Components: maven-core
>  Environment: any
>     Reporter: Kenney Westerhof
>      Fix For: 1.0-alpha-2
>  Attachments: m2test.tgz
> Original Estimate: 4 hours
>         Remaining: 4 hours
> When compiling or packaging a project consisting of subprojects
> where one depends on another, maven should first check the build environment
> for existing jars or classes (in target/ directories) from the dependent subproject,
> rather than always looking in the local and remote repositories for jar artifacts.
> Attached is a very simple test-case with 2 subprojects, where one depends
> on the other.
> Only m2 install works; m2 compile and m2 package should also work.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message