[jira] [Commented] (MNG-5836) logging config is overwritten by $M2_HOME/lib/ext/*.jar

[ https://issues.apache.org/jira/browse/MNG-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574120#comment-14574120 ] Michael Osipov commented on MNG-5836: - I think it is correct. Because logging should be

[jira] [Comment Edited] (MNG-5836) logging config is overwritten by $M2_HOME/lib/ext/*.jar

[ https://issues.apache.org/jira/browse/MNG-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574120#comment-14574120 ] Michael Osipov edited comment on MNG-5836 at 6/5/15 8:28 AM: - I

[jira] [Commented] (MNG-5840) relativePath is used if the groupId and artifactId match irrespective of the version

[ https://issues.apache.org/jira/browse/MNG-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574209#comment-14574209 ] Stephen Connolly commented on MNG-5840: --- Here is the test case working on maven 3.2.5

[jira] [Created] (MNGSITE-240) FAQ contains inaccurate description regarding the site life cycle

Karl Heinz Marbaise created MNGSITE-240: --- Summary: FAQ contains inaccurate description regarding the site life cycle Key: MNGSITE-240 URL: https://issues.apache.org/jira/browse/MNGSITE-240

[jira] [Moved] (MSITE-746) FAQ contains inaccurate description regarding the site life cycle

[ https://issues.apache.org/jira/browse/MSITE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise moved MNGSITE-240 to MSITE-746: --- Key: MSITE-746 (was: MNGSITE-240) Project: Maven Site

[jira] [Updated] (MNG-5840) relativePath is used if the groupId and artifactId match irrespective of the version

[ https://issues.apache.org/jira/browse/MNG-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5840: -- Attachment: mng-5840-testcase.tar.gz Attached testcase reproduces the issue relativePath is

[jira] [Comment Edited] (MNG-5839) site target doesn't invoke post-site phase

[ https://issues.apache.org/jira/browse/MNG-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574192#comment-14574192 ] Karl Heinz Marbaise edited comment on MNG-5839 at 6/5/15 9:27 AM:

[jira] [Commented] (MNG-5839) site target doesn't invoke post-site phase

[ https://issues.apache.org/jira/browse/MNG-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574192#comment-14574192 ] Karl Heinz Marbaise commented on MNG-5839: -- The [site life cycle comprises of four

[jira] [Created] (MNG-5840) relativePath is used if the groupId and artifactId match irrespective of the version

Stephen Connolly created MNG-5840: - Summary: relativePath is used if the groupId and artifactId match irrespective of the version Key: MNG-5840 URL: https://issues.apache.org/jira/browse/MNG-5840

[jira] [Commented] (MNG-5840) relativePath is used if the groupId and artifactId match irrespective of the version

[ https://issues.apache.org/jira/browse/MNG-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574292#comment-14574292 ] Stephen Connolly commented on MNG-5840: --- with fix applied {code} [stephenc@stevo

[jira] [Updated] (MSITE-746) FAQ contains inaccurate description regarding the site life cycle

[ https://issues.apache.org/jira/browse/MSITE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSITE-746: -- Fix Version/s: 3.4.1 FAQ contains inaccurate description regarding the site life cycle

[jira] [Updated] (MNG-5840) relativePath is used if the groupId and artifactId match irrespective of the version

[ https://issues.apache.org/jira/browse/MNG-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5840: -- Attachment: mng-5840-testcase.tar.gz removed extra files from testcase relativePath is used if

[jira] [Updated] (MNG-5840) relativePath is used if the groupId and artifactId match irrespective of the version

[ https://issues.apache.org/jira/browse/MNG-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5840: -- Attachment: (was: mng-5840-testcase.tar.gz) relativePath is used if the groupId and

[jira] [Commented] (MNG-5840) relativePath is used if the groupId and artifactId match irrespective of the version

[ https://issues.apache.org/jira/browse/MNG-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574303#comment-14574303 ] Stephen Connolly commented on MNG-5840: --- Some people asked on the mailing list for a

[jira] [Updated] (MNG-5840) relativePath is used if the groupId and artifactId match irrespective of the version

[ https://issues.apache.org/jira/browse/MNG-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5840: -- Fix Version/s: 3.3.4 relativePath is used if the groupId and artifactId match irrespective of

[jira] [Closed] (MNG-5839) site target doesn't invoke post-site phase

[ https://issues.apache.org/jira/browse/MNG-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MNG-5839. Resolution: Not A Problem Assignee: Karl Heinz Marbaise Hi Gabor, so this is not really

[jira] [Closed] (MNG-5082) Regression: Could not resolve dependencies for project

[ https://issues.apache.org/jira/browse/MNG-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MNG-5082. Resolution: Won't Fix Based on comments of Robert Scholte this will be closed. Regression:

[jira] [Commented] (MNG-5840) relativePath is used if the groupId and artifactId match irrespective of the version

[ https://issues.apache.org/jira/browse/MNG-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574280#comment-14574280 ] Hudson commented on MNG-5840: - SUCCESS: Integrated in maven-3.x #1082 (See

[jira] [Resolved] (MNG-5840) relativePath is used if the groupId and artifactId match irrespective of the version

[ https://issues.apache.org/jira/browse/MNG-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly resolved MNG-5840. --- Resolution: Fixed Assignee: Stephen Connolly

[jira] [Commented] (MSHADE-189) Null Pointer Exception when minimizeJar set to true (Maven 3.3.1)

[ https://issues.apache.org/jira/browse/MSHADE-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574482#comment-14574482 ] Karl Heinz Marbaise commented on MSHADE-189: Do you have a project by which

[jira] [Closed] (MNG-5836) logging config is overwritten by $M2_HOME/lib/ext/*.jar

[ https://issues.apache.org/jira/browse/MNG-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko closed MNG-5836. --- Resolution: Won't Fix You didn't provide an example that shows why moving conf/logging to the top of

[jira] [Commented] (MINVOKER-191) “Artifact is not fully assembled” error with maven-invoker-plugin in parallel build

[ https://issues.apache.org/jira/browse/MINVOKER-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574997#comment-14574997 ] Tavian Barnes commented on MINVOKER-191: Full reproducer here:

[jira] [Created] (MINVOKER-191) “Artifact is not fully assembled” error with maven-invoker-plugin in parallel build

Tavian Barnes created MINVOKER-191: -- Summary: “Artifact is not fully assembled” error with maven-invoker-plugin in parallel build Key: MINVOKER-191 URL: https://issues.apache.org/jira/browse/MINVOKER-191

[jira] [Commented] (MSOURCES-8) maven-source-plugin causes generate-sources phase to execute twice

[ https://issues.apache.org/jira/browse/MSOURCES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574975#comment-14574975 ] Hudson commented on MSOURCES-8: --- SUCCESS: Integrated in tobago-trunk #1382 (See

[jira] [Created] (MJAVADOC-430) Pick up documentation and integration it into plugin docs

Karl Heinz Marbaise created MJAVADOC-430: Summary: Pick up documentation and integration it into plugin docs Key: MJAVADOC-430 URL: https://issues.apache.org/jira/browse/MJAVADOC-430 Project:

[jira] [Commented] (MJAR-193) Allow other mojos to contribute to the manifest

[ https://issues.apache.org/jira/browse/MJAR-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574723#comment-14574723 ] Carsten Ziegeler commented on MJAR-193: --- Right, the bundle plugin today creates the

[jira] [Commented] (SUREFIRE-1067) Nested causes conflated with wrapper exception

[ https://issues.apache.org/jira/browse/SUREFIRE-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574796#comment-14574796 ] ASF GitHub Bot commented on SUREFIRE-1067: -- GitHub user Tibor17 opened a pull

[jira] [Closed] (MSITE-746) FAQ contains inaccurate description regarding the site life cycle

[ https://issues.apache.org/jira/browse/MSITE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSITE-746. - Resolution: Fixed Assignee: Karl Heinz Marbaise Fixed in

[jira] [Updated] (MNG-5821) Documentation of the element parent.relativePath wrong in XSD

[ https://issues.apache.org/jira/browse/MNG-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MNG-5821: - Fix Version/s: waiting-for-feedback Documentation of the element parent.relativePath wrong

[jira] [Commented] (MNG-5821) Documentation of the element parent.relativePath wrong in XSD

[ https://issues.apache.org/jira/browse/MNG-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574252#comment-14574252 ] Karl Heinz Marbaise commented on MNG-5821: -- Are you really using Maven 3.0.3 ? Then

[jira] [Commented] (SUREFIRE-1158) Remove startup logs of the plugin and TestNG configurator

[ https://issues.apache.org/jira/browse/SUREFIRE-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575265#comment-14575265 ] ASF GitHub Bot commented on SUREFIRE-1158: -- Github user asfgit closed the pull

[jira] [Closed] (SUREFIRE-1158) Remove startup logs of the plugin and TestNG configurator

[ https://issues.apache.org/jira/browse/SUREFIRE-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1158. -- Resolution: Fixed Fix Version/s: 2.19 commit

[jira] [Commented] (MNG-5839) site target doesn't invoke post-site phase

[ https://issues.apache.org/jira/browse/MNG-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575249#comment-14575249 ] Gabor Liptak commented on MNG-5839: --- [~khmarbaise] Thank you for the quick response and

[jira] [Commented] (MINVOKER-191) “Artifact is not fully assembled” error with maven-invoker-plugin in parallel build

[ https://issues.apache.org/jira/browse/MINVOKER-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575299#comment-14575299 ] Karl Heinz Marbaise commented on MINVOKER-191: -- Which maven version do you

[jira] [Closed] (MSHARED-418) Verifier should not use hard coded CLI options without possibility to modify them

[ https://issues.apache.org/jira/browse/MSHARED-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed MSHARED-418. Resolution: Fixed commited in SVN #1683964

[jira] [Commented] (MSHARED-418) Verifier should not use hard coded CLI options without possibility to modify them

[ https://issues.apache.org/jira/browse/MSHARED-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575190#comment-14575190 ] ASF GitHub Bot commented on MSHARED-418: Github user Tibor17 closed the pull

[jira] [Commented] (MSOURCES-8) maven-source-plugin causes generate-sources phase to execute twice

[ https://issues.apache.org/jira/browse/MSOURCES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575252#comment-14575252 ] Hudson commented on MSOURCES-8: --- SUCCESS: Integrated in tobago-trunk #1383 (See

[jira] [Comment Edited] (MDEPLOY-196) As a user, I would like to be to specify the licenses for a generated default pom

[ https://issues.apache.org/jira/browse/MDEPLOY-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575543#comment-14575543 ] Kyle Holohan edited comment on MDEPLOY-196 at 6/6/15 3:20 AM:

[jira] [Comment Edited] (MDEPLOY-196) As a user, I would like to be to specify the licenses for a generated default pom

[ https://issues.apache.org/jira/browse/MDEPLOY-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575543#comment-14575543 ] Kyle Holohan edited comment on MDEPLOY-196 at 6/6/15 3:22 AM:

[jira] [Updated] (MDEPLOY-196) As a user, I would like to be to specify the licenses for a generated default pom

[ https://issues.apache.org/jira/browse/MDEPLOY-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyle Holohan updated MDEPLOY-196: - Description: It would be nice to be able to specify the licenses that we want to include in the

[jira] [Created] (MDEPLOY-196) As a user, I would like to be to specify the licenses for a generated default pom

Kyle Holohan created MDEPLOY-196: Summary: As a user, I would like to be to specify the licenses for a generated default pom Key: MDEPLOY-196 URL: https://issues.apache.org/jira/browse/MDEPLOY-196

[jira] [Commented] (MDEPLOY-196) As a user, I would like to be to specify the licenses for a generated default pom

[ https://issues.apache.org/jira/browse/MDEPLOY-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575543#comment-14575543 ] Kyle Holohan commented on MDEPLOY-196: -- I was able to achieve this by: