[jira] [Commented] (MNG-7627) Sonatype Staging plugin does not plug into deploy lifecycle correctly w/ Maven 4

[ https://issues.apache.org/jira/browse/MNG-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17655843#comment-17655843 ] Peter lynch commented on MNG-7627: -- https://issues.sonatype.org/browse/NEXUS-36533 is visible to public

[jira] [Commented] (MRESOLVER-308) HTTP transport showdown

[ https://issues.apache.org/jira/browse/MRESOLVER-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653725#comment-17653725 ] Peter lynch commented on MRESOLVER-308: --- hey [~cstamas] - I have no good reason for asking other

[jira] [Commented] (MASSEMBLY-947) fileSet lineEnding crlf does not convert old mac cr line endings

[ https://issues.apache.org/jira/browse/MASSEMBLY-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17254927#comment-17254927 ] Peter lynch commented on MASSEMBLY-947: --- The issue was noticed when stray cr line endings caused

[jira] [Created] (MASSEMBLY-947) fileSet lineEnding crlf does not convert old mac cr line endings

Peter lynch created MASSEMBLY-947: - Summary: fileSet lineEnding crlf does not convert old mac cr line endings Key: MASSEMBLY-947 URL: https://issues.apache.org/jira/browse/MASSEMBLY-947 Project:

[jira] [Commented] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore

[ https://issues.apache.org/jira/browse/MNG-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16943859#comment-16943859 ] Peter lynch commented on MNG-6584: -- PR up at https://github.com/apache/maven-wagon/pull/56 for review >

[jira] [Commented] (WAGON-541) Command Line Not Showing ReasonPhrase for Errors

[ https://issues.apache.org/jira/browse/WAGON-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16943858#comment-16943858 ] Peter lynch commented on WAGON-541: --- PR up https://github.com/apache/maven-wagon/pull/56 > Command Line

[jira] [Commented] (WAGON-541) Command Line Not Showing ReasonPhrase for Errors

[ https://issues.apache.org/jira/browse/WAGON-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16764891#comment-16764891 ] Peter lynch commented on WAGON-541: --- just an update - I have the main code changes in place for adjusted

[jira] [Commented] (WAGON-541) Command Line Not Showing ReasonPhrase for Errors

[ https://issues.apache.org/jira/browse/WAGON-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760210#comment-16760210 ] Peter lynch commented on WAGON-541: --- [~michael-o] a system property or anything that makes reason phrase

[jira] [Commented] (MDEPLOY-244) maven deploy plugin 3.0.0-M1 breaks RPM deploys

[ https://issues.apache.org/jira/browse/MDEPLOY-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659914#comment-16659914 ] Peter lynch commented on MDEPLOY-244: - [~khmarbaise] i can confirm at least 1 reporter wss using an

[jira] [Commented] (MDEPLOY-244) maven deploy plugin 3.0.0-M1 breaks RPM deploys

[ https://issues.apache.org/jira/browse/MDEPLOY-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643750#comment-16643750 ] Peter lynch commented on MDEPLOY-244: - [~khmarbaise] I've done a spot check. One was while

[jira] [Commented] (MDEPLOY-244) maven deploy plugin 3.0.0-M1 breaks RPM deploys

[ https://issues.apache.org/jira/browse/MDEPLOY-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643455#comment-16643455 ] Peter lynch commented on MDEPLOY-244: - Sonatype has reports from several customers that the 3.0.0-M1

[jira] [Commented] (MJAVADOC-431) Allow Javadoc Jar to contain Maven descriptor

[ https://issues.apache.org/jira/browse/MJAVADOC-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081891#comment-15081891 ] Peter lynch commented on MJAVADOC-431: -- [~michael-o] Thanks for the MSHARED ticket link - I am

[jira] [Commented] (MJAVADOC-431) allow javadoc jar to contain Maven descriptor

[ https://issues.apache.org/jira/browse/MJAVADOC-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14994497#comment-14994497 ] Peter lynch commented on MJAVADOC-431: -- [~michael-o] PR updated - can you take a look? > allow

[jira] [Comment Edited] (MJAVADOC-431) allow javadoc jar to contain Maven descriptor

[ https://issues.apache.org/jira/browse/MJAVADOC-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943681#comment-14943681 ] Peter lynch edited comment on MJAVADOC-431 at 10/5/15 5:14 PM: ---

[jira] [Commented] (MJAVADOC-431) allow javadoc jar to contain Maven descriptor

[ https://issues.apache.org/jira/browse/MJAVADOC-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943681#comment-14943681 ] Peter lynch commented on MJAVADOC-431: -- [~michael-o] The javadoc plugin accepts a generic archiver

[jira] [Created] (MSOURCES-81) allow sources jar to contain Maven descriptor

Peter lynch created MSOURCES-81: --- Summary: allow sources jar to contain Maven descriptor Key: MSOURCES-81 URL: https://issues.apache.org/jira/browse/MSOURCES-81 Project: Maven Source Plugin

[jira] [Created] (MJAVADOC-431) allow javadoc jar to contain Maven descriptor

Peter lynch created MJAVADOC-431: Summary: allow javadoc jar to contain Maven descriptor Key: MJAVADOC-431 URL: https://issues.apache.org/jira/browse/MJAVADOC-431 Project: Maven Javadoc Plugin

[jira] (MNG-5467) intermittent ProtocolException: The server failed to respond with a valid HTTP response

[ https://jira.codehaus.org/browse/MNG-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=329936#comment-329936 ] Peter Lynch commented on MNG-5467: -- This applies to 3.1.0 as well. This fails every other build for

[jira] (MNG-5467) intermittent ProtocolException: The server failed to respond with a valid HTTP response

[ https://jira.codehaus.org/browse/MNG-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MNG-5467: - Priority: Critical (was: Major) intermittent ProtocolException: The server failed to respond with a valid

[jira] (MNG-5467) intermittent ProtocolException: The server failed to respond with a valid HTTP response

[ https://jira.codehaus.org/browse/MNG-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MNG-5467: - Affects Version/s: 3.1.0 intermittent ProtocolException: The server failed to respond with a valid HTTP

[jira] (MINDEXER-69) Severe keyword search performance regression

[ https://jira.codehaus.org/browse/MINDEXER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MINDEXER-69: Summary: Severe keyword search performance regression (was: Severe keyword serach performance

[jira] (SUREFIRE-917) [junit] category simple name matching fails throwing ClassNotFoundException

[ https://jira.codehaus.org/browse/SUREFIRE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=312611#comment-312611 ] Peter Lynch commented on SUREFIRE-917: -- Hmm, even though all existing tests pass with these

[jira] (SUREFIRE-917) [junit] category simple name matching fails throwing ClassNotFoundException

[ https://jira.codehaus.org/browse/SUREFIRE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=312549#comment-312549 ] Peter Lynch commented on SUREFIRE-917: -- Not sure if it is suitable to warn. Consider that in

[jira] (SUREFIRE-917) [junit] category simple name matching fails throwing ClassNotFoundException

[ https://jira.codehaus.org/browse/SUREFIRE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=312554#comment-312554 ] Peter Lynch commented on SUREFIRE-917: -- Anders, if I give surefire {{-Dgroups=Slow}} ( using

[jira] (SUREFIRE-917) [junit] category simple name matching fails throwing ClassNotFoundException

[ https://jira.codehaus.org/browse/SUREFIRE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=312565#comment-312565 ] Peter Lynch commented on SUREFIRE-917: -- IMO this whole thing is missing surefire killer

[jira] (SUREFIRE-916) surefire.junit4.upgradecheck fails with ClassCastException: java.lang.Class cannot be cast to java.lang.String

Peter Lynch created SUREFIRE-916: Summary: surefire.junit4.upgradecheck fails with ClassCastException: java.lang.Class cannot be cast to java.lang.String Key: SUREFIRE-916 URL:

[jira] (SUREFIRE-917) [junit] category simple name matching fails throwing ClassNotFoundException

Peter Lynch created SUREFIRE-917: Summary: [junit] category simple name matching fails throwing ClassNotFoundException Key: SUREFIRE-917 URL: https://jira.codehaus.org/browse/SUREFIRE-917 Project:

[jira] (MINDEXER-50) Logging of parsing exceptions should be handled consistently in org.apache.maven.index.creator.MavenPluginArtifactInfoIndexCreator

Peter Lynch created MINDEXER-50: --- Summary: Logging of parsing exceptions should be handled consistently in org.apache.maven.index.creator.MavenPluginArtifactInfoIndexCreator Key: MINDEXER-50 URL:

[jira] (MINDEXER-50) Logging of parsing exceptions should be handled consistently in org.apache.maven.index.creator.MavenPluginArtifactInfoIndexCreator

[ https://jira.codehaus.org/browse/MINDEXER-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MINDEXER-50: Affects Version/s: 4.1.2 Logging of parsing exceptions should be handled consistently in

[jira] Updated: (SUREFIRE-446) Surefire fails to capture TestNG results when forkMode=always

[ https://jira.codehaus.org/browse/SUREFIRE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated SUREFIRE-446: - Fix Version/s: (was: Backlog) 2.9 Surefire fails to capture TestNG results

[jira] Issue Comment Edited: (SUREFIRE-446) Surefire fails to capture TestNG results when forkMode=always

[ https://jira.codehaus.org/browse/SUREFIRE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=274765#comment-274765 ] Peter Lynch edited comment on SUREFIRE-446 at 8/1/11 10:42 AM: ---

[jira] Created: (MNG-4812) deploy:deploy-file cannot deploy anymore with Maven 3

deploy:deploy-file cannot deploy anymore with Maven 3 - Key: MNG-4812 URL: http://jira.codehaus.org/browse/MNG-4812 Project: Maven 2 3 Issue Type: Bug Components: Deployment

[jira] Closed: (MNG-4812) deploy:deploy-file cannot deploy anymore with Maven 3

[ http://jira.codehaus.org/browse/MNG-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch closed MNG-4812. Resolution: Not A Bug Problem seems to have resolved itself and was probably due to a bug in the wrapper script

[jira] Commented: (MNG-4564) Location (and name) for settings-security.xml has changed in Maven 3

[ http://jira.codehaus.org/browse/MNG-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=228208#action_228208 ] Peter Lynch commented on MNG-4564: -- In case someone is needs to cross reference, this is fixed in

[jira] Created: (MDEP-274) unpack mojo suffers from PLXUTILS-64

unpack mojo suffers from PLXUTILS-64 Key: MDEP-274 URL: http://jira.codehaus.org/browse/MDEP-274 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: unpack Affects Versions:

[jira] Reopened: (MNG-4564) Location (and name) for settings-security.xml has changed in Maven 3

[ http://jira.codehaus.org/browse/MNG-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch reopened MNG-4564: -- There appears to be some regression here I have a ~/.m2/settings-security.xml and am running maven 3.0-beta-1

[jira] Commented: (MRELEASE-356) depreate the automated release profile

[ http://jira.codehaus.org/browse/MRELEASE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=221499#action_221499 ] Peter Lynch commented on MRELEASE-356: -- Can someone include a link here to a mailing list

[jira] Updated: (MECLIPSE-601) to-maven mojo install source plugins as ordinay plugins. It should install the source plugins as classified as 'sources'

[ http://jira.codehaus.org/browse/MECLIPSE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MECLIPSE-601: - Assignee: (was: Peter Lynch) to-maven mojo install source plugins as ordinay plugins. It should

[jira] Commented: (MNG-4523) [Regression] Plugin model inheritance different when a mojo goal is explicitly called from cmd line

[ http://jira.codehaus.org/browse/MNG-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=207019#action_207019 ] Peter Lynch commented on MNG-4523: -- Related discussion going on

[jira] Commented: (MNG-3078) artifact of packaging 'tar.gz' / dependency of type 'tar.gz downloaded, but not saved to local repository

[ http://jira.codehaus.org/browse/MNG-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=206808#action_206808 ] Peter Lynch commented on MNG-3078: -- I did create an integration test but using Maven 2.2.9 and Maven 3

[jira] Created: (MNG-4523) [Regression] Plugin model inheritance different when a mojo goal is explicitly called from cmd line

[Regression] Plugin model inheritance different when a mojo goal is explicitly called from cmd line - Key: MNG-4523 URL:

[jira] Commented: (MNG-4523) [Regression] Plugin model inheritance different when a mojo goal is explicitly called from cmd line

[ http://jira.codehaus.org/browse/MNG-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=205966#action_205966 ] Peter Lynch commented on MNG-4523: -- Added integration test which demonstrates the problem. This test

[jira] Updated: (MNG-4523) [Regression] Plugin model inheritance different when a mojo goal is explicitly called from cmd line

[ http://jira.codehaus.org/browse/MNG-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MNG-4523: - Attachment: mng-4523-IT.zip [Regression] Plugin model inheritance different when a mojo goal is explicitly

[jira] Created: (MECLIPSE-633) [Maven 3] j2ee-simple integration test fails

[Maven 3] j2ee-simple integration test fails Key: MECLIPSE-633 URL: http://jira.codehaus.org/browse/MECLIPSE-633 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core :

[jira] Updated: (MPJAVADOC-74) [ Junit plugin ] Add javadoc for the junit tests

[ http://jira.codehaus.org/browse/MPJAVADOC-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MPJAVADOC-74: - Assignee: (was: Peter Lynch) [ Junit plugin ] Add javadoc for the junit tests

[jira] Updated: (MPAPPSERVER-4) Added support for Orion appserver 2.0.2

[ http://jira.codehaus.org/browse/MPAPPSERVER-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MPAPPSERVER-4: -- Assignee: (was: Peter Lynch) Added support for Orion appserver 2.0.2

[jira] Created: (MNG-4514) Loading resource from plugin dependency using Plexus ResourceManager fails with leading slash

Loading resource from plugin dependency using Plexus ResourceManager fails with leading slash - Key: MNG-4514 URL: http://jira.codehaus.org/browse/MNG-4514

[jira] Commented: (MNG-4514) Loading resource from plugin dependency using Plexus ResourceManager fails with leading slash

[ http://jira.codehaus.org/browse/MNG-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204942#action_204942 ] Peter Lynch commented on MNG-4514: -- Added integration test for mng-4514 that passes Maven 2.2.1 and

[jira] Updated: (MNG-4514) Loading resource from plugin dependency using Plexus ResourceManager fails with leading slash

[ http://jira.codehaus.org/browse/MNG-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MNG-4514: - Attachment: mng-4514-IT.zip Loading resource from plugin dependency using Plexus ResourceManager fails with

[jira] Updated: (MNG-4514) Loading resource from plugin dependency using Plexus ResourceManager fails with leading slash

[ http://jira.codehaus.org/browse/MNG-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MNG-4514: - Testcase included: yes Loading resource from plugin dependency using Plexus ResourceManager fails with

[jira] Commented: (MECLIPSE-601) to-maven mojo install source plugins as ordinay plugins. It should install the source plugins as classified as 'sources'

[ http://jira.codehaus.org/browse/MECLIPSE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204947#action_204947 ] Peter Lynch commented on MECLIPSE-601: -- Providing the integration tests is next in my queue.

[jira] Issue Comment Edited: (MECLIPSE-601) to-maven mojo install source plugins as ordinay plugins. It should install the source plugins as classified as 'sources'

[ http://jira.codehaus.org/browse/MECLIPSE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204947#action_204947 ] Peter Lynch edited comment on MECLIPSE-601 at 1/3/10 3:57 AM: --

[jira] Commented: (MNG-4514) Loading resource from plugin dependency using Plexus ResourceManager fails with leading slash

[ http://jira.codehaus.org/browse/MNG-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204968#action_204968 ] Peter Lynch commented on MNG-4514: -- I will add then that a user of Maven who upgrades to Maven 3.x and

[jira] Created: (MECLIPSE-631) [Maven 3] Inegration test project-44 fails with Unable to resolve resource location: /checkstyle-config.xml

[Maven 3] Inegration test project-44 fails with Unable to resolve resource location: /checkstyle-config.xml --- Key: MECLIPSE-631 URL:

[jira] Updated: (MECLIPSE-631) [Maven 3] Integration test project-44 fails with Unable to resolve resource location: /checkstyle-config.xml

[ http://jira.codehaus.org/browse/MECLIPSE-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MECLIPSE-631: - Summary: [Maven 3] Integration test project-44 fails with Unable to resolve resource location:

[jira] Updated: (MECLIPSE-631) [Maven 3] Integration test project-44 fails with Unable to resolve resource location: /checkstyle-config.xml

[ http://jira.codehaus.org/browse/MECLIPSE-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MECLIPSE-631: - Attachment: MECLIPSE-631.patch [Maven 3] Integration test project-44 fails with Unable to resolve

[jira] Updated: (MECLIPSE-631) [Maven 3] Integration test project-44 fails with Unable to resolve resource location: /checkstyle-config.xml

[ http://jira.codehaus.org/browse/MECLIPSE-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MECLIPSE-631: - Patch Submitted: [Yes] [Maven 3] Integration test project-44 fails with Unable to resolve resource

[jira] Commented: (MECLIPSE-631) [Maven 3] Integration test project-44 fails with Unable to resolve resource location: /checkstyle-config.xml

[ http://jira.codehaus.org/browse/MECLIPSE-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204977#action_204977 ] Peter Lynch commented on MECLIPSE-631: -- Patch attached that resolves the integration test

[jira] Updated: (MECLIPSE-626) Upgrade Maven dependencies from 2.0.8 to at least 2.0.9 to match minimum version required to build

[ http://jira.codehaus.org/browse/MECLIPSE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MECLIPSE-626: - Attachment: MECLIPSE-626.patch Patch to pom.xml enforcing minimum Maven version of 2.0.9 for

[jira] Commented: (MECLIPSE-626) Upgrade Maven dependencies from 2.0.8 to at least 2.0.9 to match minimum version required to build

[ http://jira.codehaus.org/browse/MECLIPSE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=202018#action_202018 ] Peter Lynch commented on MECLIPSE-626: -- Summary of the problems, the maven prerequisites are

[jira] Issue Comment Edited: (MECLIPSE-626) Upgrade Maven dependencies from 2.0.8 to at least 2.0.9 to match minimum version required to build

[ http://jira.codehaus.org/browse/MECLIPSE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=202018#action_202018 ] Peter Lynch edited comment on MECLIPSE-626 at 12/9/09 10:08 PM:

[jira] Created: (MECLIPSE-626) Upgrade Maven dependencies from 2.0.8 to at least 2.0.9 to match minimum version required to build

Upgrade Maven dependencies from 2.0.8 to at least 2.0.9 to match minimum version required to build -- Key: MECLIPSE-626 URL:

[jira] Work started: (MECLIPSE-601) to-maven mojo install source plugins as ordinay plugins. It should install the source plugins as classified as 'sources'

[ http://jira.codehaus.org/browse/MECLIPSE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MECLIPSE-601 started by Peter Lynch. to-maven mojo install source plugins as ordinay plugins. It should install the source plugins as classified as 'sources'

[jira] Work stopped: (MECLIPSE-601) to-maven mojo install source plugins as ordinay plugins. It should install the source plugins as classified as 'sources'

[ http://jira.codehaus.org/browse/MECLIPSE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MECLIPSE-601 stopped by Peter Lynch. to-maven mojo install source plugins as ordinay plugins. It should install the source plugins as classified as 'sources'

[jira] Commented: (MECLIPSE-601) to-maven mojo install source plugins as ordinay plugins. It should install the source plugins as classified as 'sources'

[ http://jira.codehaus.org/browse/MECLIPSE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=201699#action_201699 ] Peter Lynch commented on MECLIPSE-601: -- Hi Hasan I've applied and tested the patch locally.

[jira] Commented: (MNG-4001) Unable to resolve Dashboard mojo from Central

[ http://jira.codehaus.org/browse/MNG-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200043#action_200043 ] Peter Lynch commented on MNG-4001: -- Try this for extra wackiness: Define your plugin configuration

[jira] Issue Comment Edited: (MNG-4001) Unable to resolve Dashboard mojo from Central

[ http://jira.codehaus.org/browse/MNG-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200043#action_200043 ] Peter Lynch edited comment on MNG-4001 at 11/30/09 12:51 PM: - Try this for

[jira] Commented: (MNG-4001) Unable to resolve Dashboard mojo from Central

[ http://jira.codehaus.org/browse/MNG-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=199899#action_199899 ] Peter Lynch commented on MNG-4001: -- Perhaps when this is fixed, adding an DEBUG log message indicating

[jira] Created: (MNG-3078) artifact of packaging 'tar.gz' / dependency of type 'tar.gz downloaded, but not saved to local repository

artifact of packaging 'tar.gz' / dependency of type 'tar.gz downloaded, but not saved to local repository - Key: MNG-3078 URL:

[jira] Commented: (MASSEMBLY-195) unpackOptions ignored

[ http://jira.codehaus.org/browse/MASSEMBLY-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100880 ] Peter Lynch commented on MASSEMBLY-195: --- FYI - using 2.2-beta-1, excludes inside unpackOptions are working fine for

[jira] Updated: (MNG-3078) artifact of packaging 'tar.gz' / dependency of type 'tar.gz downloaded, but not saved to local repository

[ http://jira.codehaus.org/browse/MNG-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MNG-3078: - Description: Using mvn deploy:deploy-file you can successfully upload a 'tar.gz' artifact to a repository.

[jira] Commented: (SUREFIRE-298) Problem using -javaagent

[ http://jira.codehaus.org/browse/SUREFIRE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99965 ] Peter Lynch commented on SUREFIRE-298: -- it is likely a problem with classloading...true. try this configuration with

[jira] Commented: (MSOURCES-10) Attached source artifact should not be added for artifacts with classifier

[ http://jira.codehaus.org/browse/MSOURCES-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92473 ] Peter Lynch commented on MSOURCES-10: - I think this patch highlights a nasty side effect. Of course since classifier

[jira] Created: (MECLIPSE-234) [PATCH] EclipsePlugin.extractResourceDirs() reuses String method argument causing maven-eclipse.xml copy-resources problems

[PATCH] EclipsePlugin.extractResourceDirs() reuses String method argument causing maven-eclipse.xml copy-resources problems --- Key: MECLIPSE-234

[jira] Created: (MNG-2815) Parent POM defined profile dependencyManagement dependency version overrides child pom explicit dependency

Parent POM defined profile dependencyManagement dependency version overrides child pom explicit dependency -- Key: MNG-2815 URL: