[jira] (MASSEMBLY-743) not correct

[ https://jira.codehaus.org/browse/MASSEMBLY-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359073#comment-359073 ] Jean-Eric Cuendet commented on MASSEMBLY-743: - Thanks a lot! When will it be release

[jira] (MRELEASE-895) Update message on JIRA summary page

Stephan Schroevers created MRELEASE-895: --- Summary: Update message on JIRA summary page Key: MRELEASE-895 URL: https://jira.codehaus.org/browse/MRELEASE-895 Project: Maven Release Plugin

[jira] (SUREFIRE-995) Support searching superclass for JUnit @Category

[ https://jira.codehaus.org/browse/SUREFIRE-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-995. - Resolution: Fixed commit 6c8bab59ab8908b13817052d514c02bc800b4db3 > Support searching superclass f

[jira] (MPIR-322) Dependencies Files Details should reuse installed jars instead of target/classes

[ https://jira.codehaus.org/browse/MPIR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPIR-322. -- Resolution: Fixed Fix Version/s: 2.8 Assignee: Herve Boutemy done in [r1645539|http://svn.apac

[jira] (MPIR-322) Dependencies Files Details should reuse installed jars instead of target/classes

[ https://jira.codehaus.org/browse/MPIR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPIR-322: --- Attachment: MPIR-322.zip here is an IT to easily reproduce the problem now we need IMHO a hack to detect su

[jira] (MPIR-322) Dependencies Files Details should reuse installed jars instead of target/classes

Herve Boutemy created MPIR-322: -- Summary: Dependencies Files Details should reuse installed jars instead of target/classes Key: MPIR-322 URL: https://jira.codehaus.org/browse/MPIR-322 Project: Maven Proj

[jira] (MNG-5736) ProjectSorter invalid duplication checking

John Patrick created MNG-5736: - Summary: ProjectSorter invalid duplication checking Key: MNG-5736 URL: https://jira.codehaus.org/browse/MNG-5736 Project: Maven Issue Type: Bug Component

[jira] (MPLUGIN-279) improve jdk requirement when m-compiler-p not explicitely configured: use default properties

[ https://jira.codehaus.org/browse/MPLUGIN-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359068#comment-359068 ] Herve Boutemy edited comment on MPLUGIN-279 at 12/14/14 1:40 PM: -

[jira] (MPLUGIN-279) improve jdk requirement when m-compiler-p not explicitely configured: use default properties

[ https://jira.codehaus.org/browse/MPLUGIN-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359068#comment-359068 ] Herve Boutemy commented on MPLUGIN-279: --- bq. If I understood you correctly, this would solve

[jira] (MPLUGIN-279) improve jdk requirement when m-compiler-p not explicitely configured: use default properties

[ https://jira.codehaus.org/browse/MPLUGIN-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359067#comment-359067 ] Michael Osipov edited comment on MPLUGIN-279 at 12/14/14 1:14 PM: --

[jira] (MPLUGIN-279) improve jdk requirement when m-compiler-p not explicitely configured: use default properties

[ https://jira.codehaus.org/browse/MPLUGIN-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359067#comment-359067 ] Michael Osipov commented on MPLUGIN-279: If I understood you correctly, this would solve e

[jira] (MENFORCER-219) Add m2e mapping

[ https://jira.codehaus.org/browse/MENFORCER-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise reopened MENFORCER-219: --- I need to improve that cause currently in eclipse you get only a stack trace and a

[jira] (MPLUGIN-280) remove xdoc goal since the content is generated during report

[ https://jira.codehaus.org/browse/MPLUGIN-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPLUGIN-280. - Resolution: Fixed Fix Version/s: 3.4 Assignee: Herve Boutemy done in [r1645484|http:/

[jira] (MPLUGIN-280) remove xdoc goal since the content is generated during report

Herve Boutemy created MPLUGIN-280: - Summary: remove xdoc goal since the content is generated during report Key: MPLUGIN-280 URL: https://jira.codehaus.org/browse/MPLUGIN-280 Project: Maven Plugin Tool

[jira] (MPIR-301) Update plexus-interpolation to 1.21 to avoid thread safety issues

[ https://jira.codehaus.org/browse/MPIR-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPIR-301: --- Summary: Update plexus-interpolation to 1.21 to avoid thread safety issues (was: Update plexus-interpolatio

[jira] (MPLUGIN-279) improve jdk requirement when m-compiler-p not explicitely configured: use default properties

[ https://jira.codehaus.org/browse/MPLUGIN-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359064#comment-359064 ] Herve Boutemy commented on MPLUGIN-279: --- bq. How can I make use of that in MPIR and MPMD? a

[jira] (MPLUGIN-279) improve jdk requirement when m-compiler-p not explicitely configured: use default properties

[ https://jira.codehaus.org/browse/MPLUGIN-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359063#comment-359063 ] Herve Boutemy edited comment on MPLUGIN-279 at 12/14/14 11:15 AM: --

[jira] (MPLUGIN-279) improve jdk requirement when m-compiler-p not explicitely configured: use default properties

[ https://jira.codehaus.org/browse/MPLUGIN-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359063#comment-359063 ] Herve Boutemy commented on MPLUGIN-279: --- let's explain: getting configuration from compiler

[jira] (MPLUGIN-279) improve jdk requirement when m-compiler-p not explicitely configured: use default properties

[ https://jira.codehaus.org/browse/MPLUGIN-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359062#comment-359062 ] Herve Boutemy commented on MPLUGIN-279: --- algorithm fixed in [r1645468|http://svn.apache.org/

[jira] (SUREFIRE-995) Support searching superclass for JUnit @Category

[ https://jira.codehaus.org/browse/SUREFIRE-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-995: -- Fix Version/s: 2.18.1 > Support searching superclass for JUnit @Category > ---

[jira] (SUREFIRE-995) Support searching superclass for JUnit @Category

[ https://jira.codehaus.org/browse/SUREFIRE-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359058#comment-359058 ] Tibor Digana edited comment on SUREFIRE-995 at 12/14/14 10:33 AM: -

[jira] (SUREFIRE-995) Support searching superclass for JUnit @Category

[ https://jira.codehaus.org/browse/SUREFIRE-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359058#comment-359058 ] Tibor Digana edited comment on SUREFIRE-995 at 12/14/14 10:34 AM: -

[jira] (MJAVADOC-310) compiler plugin settings aren't inherited from parent tor linking Java API links

[ https://jira.codehaus.org/browse/MJAVADOC-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359061#comment-359061 ] Michael Osipov commented on MJAVADOC-310: - Let's discuss this in MPLUGIN-279, maybe we ca

[jira] (MPLUGIN-279) improve jdk requirement when m-compiler-p not explicitely configured: use default properties

[ https://jira.codehaus.org/browse/MPLUGIN-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359060#comment-359060 ] Michael Osipov commented on MPLUGIN-279: This looks promising. How can I make use of that

[jira] (MJAVADOC-310) compiler plugin settings aren't inherited from parent tor linking Java API links

[ https://jira.codehaus.org/browse/MJAVADOC-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359059#comment-359059 ] Herve Boutemy commented on MJAVADOC-310: notice that we have code for that in Maven Plugi

[jira] (SUREFIRE-995) Support searching superclass for JUnit @Category

[ https://jira.codehaus.org/browse/SUREFIRE-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359058#comment-359058 ] Tibor Digana commented on SUREFIRE-995: --- This already works with JUnit 4.12 (Released on De

[jira] (SUREFIRE-1074) Should Surefire-api scan InnerClasses for Test Classes

[ https://jira.codehaus.org/browse/SUREFIRE-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1074. -- Resolution: Not A Bug Closed as Not A Bug. Apply JUnit Runner "Enclosed.class" in your project us

[jira] (MPIR-267) With Maven 3, "Dependency Repository Locations" links artifacts with my local repository manager id and url instead of public repository info

[ https://jira.codehaus.org/browse/MPIR-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359056#comment-359056 ] Michael Osipov commented on MPIR-267: - Thanks for the update. How does the appropriate look like?

[jira] (MPIR-263) Add parameter 'targetJavaVersion' and inject ${maven.compiler.target}

[ https://jira.codehaus.org/browse/MPIR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359055#comment-359055 ] Michael Osipov commented on MPIR-263: - Hervé, I understand your point. I had a lengthly discussio

[jira] (MPIR-263) Add parameter 'targetJavaVersion' and inject ${maven.compiler.target}

[ https://jira.codehaus.org/browse/MPIR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359054#comment-359054 ] Herve Boutemy edited comment on MPIR-263 at 12/14/14 8:25 AM: -- I'm not c

[jira] (MPIR-263) Add parameter 'targetJavaVersion' and inject ${maven.compiler.target}

[ https://jira.codehaus.org/browse/MPIR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359054#comment-359054 ] Herve Boutemy commented on MPIR-263: I'm not convinced: I think this should be detected the same

[jira] (MPIR-267) With Maven 3, "Dependency Repository Locations" links artifacts with my local repository manager id and url instead of public repository info

[ https://jira.codehaus.org/browse/MPIR-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359050#comment-359050 ] Herve Boutemy commented on MPIR-267: yes, it is still failing: I added a check in [r1645436|http

[jira] (ARCHETYPE-435) Bad link to old docs in usage page

[ https://jira.codehaus.org/browse/ARCHETYPE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359047#comment-359047 ] Karl-Heinz Marbaise edited comment on ARCHETYPE-435 at 12/14/14 4:08 AM: -

[jira] (ARCHETYPE-467) Removed unused maven-war-plugin dependency.

[ https://jira.codehaus.org/browse/ARCHETYPE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated ARCHETYPE-467: -- Summary: Removed unused maven-war-plugin dependency. (was: Removed unused maven-

[jira] (ARCHETYPE-467) Removed unused maven-war-plugin dependency.

[ https://jira.codehaus.org/browse/ARCHETYPE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed ARCHETYPE-467. - Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1645432|http://svn

[jira] (ARCHETYPE-467) Removed unused maven-war-plugin depedency.

[ https://jira.codehaus.org/browse/ARCHETYPE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated ARCHETYPE-467: -- Fix Version/s: 2.3 > Removed unused maven-war-plugin depedency. > ---

[jira] (ARCHETYPE-467) Removed unused maven-war-plugin depedency.

Karl-Heinz Marbaise created ARCHETYPE-467: - Summary: Removed unused maven-war-plugin depedency. Key: ARCHETYPE-467 URL: https://jira.codehaus.org/browse/ARCHETYPE-467 Project: Maven Archetype

[jira] (MENFORCER-219) Add m2e mapping

[ https://jira.codehaus.org/browse/MENFORCER-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359045#comment-359045 ] Karl-Heinz Marbaise edited comment on MENFORCER-219 at 12/14/14 3:58 AM: -

[jira] (ARCHETYPE-435) Bad link to old docs in usage page

[ https://jira.codehaus.org/browse/ARCHETYPE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated ARCHETYPE-435: -- Fix Version/s: (was: 3.0) 2.3 > Bad link to old docs in us

[jira] (ARCHETYPE-435) Bad link to old docs in usage page

[ https://jira.codehaus.org/browse/ARCHETYPE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359047#comment-359047 ] Karl-Heinz Marbaise commented on ARCHETYPE-435: --- So either we fix the link to the

[jira] (ARCHETYPE-466) Upgrade maven-invoker 2.0.11 to 2.1.1

[ https://jira.codehaus.org/browse/ARCHETYPE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed ARCHETYPE-466. - Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1645430|http://svn

[jira] (ARCHETYPE-466) Upgrade maven-invoker 2.0.11 to 2.1.1

[ https://jira.codehaus.org/browse/ARCHETYPE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated ARCHETYPE-466: -- Fix Version/s: 2.3 > Upgrade maven-invoker 2.0.11 to 2.1.1 >

[jira] (ARCHETYPE-466) Upgrade maven-invoker 2.0.11 to 2.1.1

Karl-Heinz Marbaise created ARCHETYPE-466: - Summary: Upgrade maven-invoker 2.0.11 to 2.1.1 Key: ARCHETYPE-466 URL: https://jira.codehaus.org/browse/ARCHETYPE-466 Project: Maven Archetype

[jira] (MENFORCER-219) Add m2e mapping

[ https://jira.codehaus.org/browse/MENFORCER-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MENFORCER-219. - Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1645429|http://svn

[jira] (MENFORCER-219) Add m2e mapping

[ https://jira.codehaus.org/browse/MENFORCER-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MENFORCER-219: -- Description: Just adding a simple mapping just to ignore the plugin during increm

[jira] (MPIR-268) Add Gradle dependency information

[ https://jira.codehaus.org/browse/MPIR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359044#comment-359044 ] Herve Boutemy commented on MPIR-268: :) > Add Gradle dependency information > --

[jira] (MENFORCER-219) Add m2e mapping

[ https://jira.codehaus.org/browse/MENFORCER-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MENFORCER-219: -- Summary: Add m2e mapping (was: Added m2e mapping) > Add m2e mapping > --