[ 
http://jira.codehaus.org/browse/MNG-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229804#action_229804
 ] 

Robert Munteanu commented on MNG-4633:
--------------------------------------

The plugin is the maven-compiler-plugin , and it's bound to two executions : 
once in generate-sources, another in default-compiler. And yes, module B 
depends on the classes from module A. It's worth mentioning that all execution 
so far was done on a single thread, judging from the thread names.

Also, I get some warnings regarding n...@threadsafe plugins. Should I worry 
about these:

{code}
[WARNING] The following plugins are not marked @threadSafe in ...:
[WARNING] org.apache.maven.plugins:maven-surefire-plugin:2.5
[WARNING] org.codehaus.mojo:build-helper-maven-plugin:1.5
[WARNING] org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1
{code}

Since I'm running a SNAPSHOT build I need to skip the enforcer plugin. I've 
also tried with the tests skipped, but that made no difference.

> Make weave mode work reliably
> -----------------------------
>
>                 Key: MNG-4633
>                 URL: http://jira.codehaus.org/browse/MNG-4633
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>    Affects Versions: 3.0-beta-1
>            Reporter: Kristian Rosenvold
>            Assignee: Kristian Rosenvold
>             Fix For: 3.0-beta-2
>
>
> m3 trunk currently contains two different concurrent-build implementations; 
> parallel and weave. The main target for m3 is for production quality 
> "parallel" to be  ready; there are numerous plugins that will need to adjust 
> to this functionality. 
> Alongside this activity weave mode will also be fine-tuned and evaluated; due 
> to the generally tighter concurrency in this model, weave mode is more likely 
> to reveal concurrency related issues in both maven, plugins, libraries and 
> the jdk. 
> This task is used to collect all commits related to making weave mode work 
> reliably. The final evaluation of weave mode will be taken at a later stage.
> In the event that Weave mode is to be abandoned, the class 
> LifecycleWeaveBuilder contains instructions on how/what can be removed from 
> m3 core.

-- 
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

        

Reply via email to