Community
Participate
Working Groups
Because we needed to put Maven through CQ (approaching deadlines), we put Maven 3.0.2 since Maven 3.0.3 has not yet been released. However this forced us to take a copy of a few Maven 3.0.3 classes for integration with m2e. This is an intermediary situation until we find a way to update to Maven 3.0.3. This bug is track the classes that we took a copy of. DefaultLifecycleExecutor.java DefaultSchedules.java LifecycleExecutor.java DefaultLifecycleExecutionPlanCalculator.java LifecycleExecutionPlanCalculator.java LifecycleTaskSegmentCalculator.java DefaultMavenPluginManager.java
Not sure if this makes any difference, but these are maven 3.0.2 sources with my patches applied to them.
Since 3.0.3 has been released, can you please update the plug-in to 3.0.3 as soon as possible? 3.0.2 doesn't handle importing dependencies in a dependencyManagement element properly and I need that to release m4e (Tools to build Maven repos from Eclipse releases).
Don't hold your breath on that one. For something like that to be released, Maven 3.0.3 needs to be put through the Eclipse legal process.
maven runtime 3.0.3 can be installed from m2e marketplace (preferences->maven->discovery)
hit enter to early. My point is that it will likely take a while to go through. In the meantime you can get Maven 3.0.3 from the m2e discovery ui
embedded runtime has been updated to maven 3.0.4 and all copied classes have been removed.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/