[jira] [Commented] (MNG-5871) make url inheritance algorithm more visible

[ https://issues.apache.org/jira/browse/MNG-5871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700455#comment-14700455 ] Hudson commented on MNG-5871: - SUCCESS: Integrated in maven-3.x #1104 (See [https://builds.apac

[jira] [Commented] (MENFORCER-224) Regression from 1.3.1 to 1.4 with bannedDependencies rule

[ https://issues.apache.org/jira/browse/MENFORCER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700192#comment-14700192 ] Jason Dillon commented on MENFORCER-224: Still no release? > Regression from 1

[jira] [Updated] (ARCHETYPE-486) create-from-project should filter out the archetype plugin from the created archetype

[ https://issues.apache.org/jira/browse/ARCHETYPE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated ARCHETYPE-486: --- Description: A common scenario for the archetype plugin is to create a sample proje

[jira] [Updated] (ARCHETYPE-486) create-from-project should filter out the archetype plugin from the created archetype

[ https://issues.apache.org/jira/browse/ARCHETYPE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated ARCHETYPE-486: --- Attachment: archetype-486.patch Patch with new feature implemented. Added "removeAr

[jira] [Created] (ARCHETYPE-486) create-from-project should filter out the archetype plugin from the created archetype

Jordan Zimmerman created ARCHETYPE-486: -- Summary: create-from-project should filter out the archetype plugin from the created archetype Key: ARCHETYPE-486 URL: https://issues.apache.org/jira/browse/ARCHETYPE-

[jira] [Closed] (MNG-5871) make url inheritance algorithm more visible

[ https://issues.apache.org/jira/browse/MNG-5871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MNG-5871. -- Resolution: Fixed Fix Version/s: 3.3.7 merged in master in [200d2f99|http://git-wip-us.apache.org/

[jira] [Commented] (MCOMPILER-249) Maven gives successful Build message and creates empty jar and fails to find compile time issues.

[ https://issues.apache.org/jira/browse/MCOMPILER-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699806#comment-14699806 ] vijay commented on MCOMPILER-249: - I found the link. Please ignore previous comment. Th

[jira] [Updated] (MRESOURCES-204) Maven gives successful Build message and creates empty jar if pom is configured for executing copy-resources goal with phase process-resources.

[ https://issues.apache.org/jira/browse/MRESOURCES-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] vijay updated MRESOURCES-204: - Attachment: MyAnnotation.zip The zip file contains maven project MyAnnotation. > Maven gives successf

[jira] [Created] (MRESOURCES-204) Maven gives successful Build message and creates empty jar if pom is configured for executing copy-resources goal with phase process-resources.

vijay created MRESOURCES-204: Summary: Maven gives successful Build message and creates empty jar if pom is configured for executing copy-resources goal with phase process-resources. Key: MRESOURCES-204 URL: https:/

[jira] [Commented] (MCOMPILER-249) Maven gives successful Build message and creates empty jar and fails to find compile time issues.

[ https://issues.apache.org/jira/browse/MCOMPILER-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699708#comment-14699708 ] vijay commented on MCOMPILER-249: - I am facing another issue which I want to highlight.

[jira] [Commented] (MCOMPILER-249) Maven gives successful Build message and creates empty jar and fails to find compile time issues.

[ https://issues.apache.org/jira/browse/MCOMPILER-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699699#comment-14699699 ] vijay commented on MCOMPILER-249: - Thanks Hervé. I tested with JDK 1.8 with same result

[jira] [Updated] (MWAR-353) Manifest still not written to exploded location

[ https://issues.apache.org/jira/browse/MWAR-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Bochenski updated MWAR-353: - Description: If I have no manifest files I don't get anything in the exploded location. If I put a {

[jira] [Updated] (MWAR-353) Manifest still not written to exploded location

[ https://issues.apache.org/jira/browse/MWAR-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Bochenski updated MWAR-353: - Description: If I have no manifest files I don't get anything in the exploded location. If I put a {

[jira] [Updated] (MWAR-353) Manifest still not written to exploded location

[ https://issues.apache.org/jira/browse/MWAR-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Bochenski updated MWAR-353: - Affects Version/s: (was: 2.1-alpha-1) 2.6 > Manifest still not written to

[jira] [Created] (MWAR-353) Manifest still not written to exploded location

Jakub Bochenski created MWAR-353: Summary: Manifest still not written to exploded location Key: MWAR-353 URL: https://issues.apache.org/jira/browse/MWAR-353 Project: Maven WAR Plugin Issue Ty

[jira] [Created] (MDEP-499) Excluded transitive dependencies of dependency should be overriden by other transitive dependency

Stefan Fussenegger created MDEP-499: --- Summary: Excluded transitive dependencies of dependency should be overriden by other transitive dependency Key: MDEP-499 URL: https://issues.apache.org/jira/browse/MDEP-499

[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699138#comment-14699138 ] Stephen Connolly commented on MPIR-234: --- Maven is opinionated with its defaults... but