[
https://issues.apache.org/jira/browse/MNG-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14704482#comment-14704482
]
Jan Sievers commented on MNG-5855:
--
I have to second Hervé: evidence are detailed steps
[
https://issues.apache.org/jira/browse/MNG-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14701473#comment-14701473
]
Jan Sievers commented on MNG-5855:
--
you can easily test this by using sample project
[
https://issues.apache.org/jira/browse/MNG-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14506994#comment-14506994
]
Jan Sievers commented on MNG-5797:
--
I have verified that this is fixed now with staged
[
https://issues.apache.org/jira/browse/WAGON-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14502536#comment-14502536
]
Jan Sievers commented on WAGON-432:
---
@Jason AFAICT the stacktrace seems unrelated to the
[
https://issues.apache.org/jira/browse/WAGON-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14499826#comment-14499826
]
Jan Sievers commented on WAGON-432:
---
pull request including unit tests:
[
https://issues.apache.org/jira/browse/WAGON-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14499900#comment-14499900
]
Jan Sievers commented on WAGON-432:
---
@Michael yes I know. To fix the issue in general for
[
https://jira.codehaus.org/browse/MNG-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=366005#comment-366005
]
Jan Sievers commented on MNG-5797:
--
concatenating the header values for multiple headers with the
Jan Sievers created MNG-5797:
Summary: 'mvn deploy' sends HTTP User-Agent twice
Key: MNG-5797
URL: https://jira.codehaus.org/browse/MNG-5797
Project: Maven
Issue Type: Bug
Components:
[
https://jira.codehaus.org/browse/MNG-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=366026#comment-366026
]
Jan Sievers commented on MNG-5797:
--
just found this is reported as
[
https://jira.codehaus.org/browse/MNG-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=366035#comment-366035
]
Jan Sievers commented on MNG-5797:
--
this happened using an internal Nexus, version 2.11.1-01
I saw
Jan Sievers created MNG-5792:
Summary: mvn.bat renamed to mvn.cmd - maven-invoker-plugin:run
fails
Key: MNG-5792
URL: https://jira.codehaus.org/browse/MNG-5792
Project: Maven
Issue Type: Bug
[
https://jira.codehaus.org/browse/MNG-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Sievers updated MNG-5346:
-
Attachment: plugin-annotation-sample.zip
the problem is still there, see sample project attached.
Also, the
Jan Sievers created MNG-5440:
Summary: default-value on mojo parameter of type collection or
array effectively make parameter read-only
Key: MNG-5440
URL: https://jira.codehaus.org/browse/MNG-5440
[
https://jira.codehaus.org/browse/MNG-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=320467#comment-320467
]
Jan Sievers commented on MNG-5440:
--
I'm using maven 3.0.4
default-value on mojo
[
https://jira.codehaus.org/browse/MNG-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=320467#comment-320467
]
Jan Sievers edited comment on MNG-5440 at 2/25/13 9:01 AM:
---
I'm using maven
[
https://jira.codehaus.org/browse/MCOMPILER-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=318901#comment-318901
]
Jan Sievers commented on MCOMPILER-178:
---
IMHO the existing mojo parameters String
[
https://jira.codehaus.org/browse/SUREFIRE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301621#comment-301621
]
Jan Sievers commented on SUREFIRE-876:
--
patch includes a unit test...
Jan Sievers created SUREFIRE-876:
Summary: surefire-junit47 does not work in an OSGi classloader
environment
Key: SUREFIRE-876
URL: https://jira.codehaus.org/browse/SUREFIRE-876
Project: Maven
[
https://jira.codehaus.org/browse/SUREFIRE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301222#comment-301222
]
Jan Sievers commented on SUREFIRE-876:
--
I created pull request
[
https://jira.codehaus.org/browse/SUREFIRE-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Sievers updated SUREFIRE-825:
-
Attachment: 0001-SUREFIRE-825-Add-null-check-for-runWith-field.patch
git patch v2 (now with unit
[
https://jira.codehaus.org/browse/SUREFIRE-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291637#comment-291637
]
Jan Sievers commented on SUREFIRE-825:
--
I will add a test to the patch
NPE
[
https://jira.codehaus.org/browse/SUREFIRE-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=290475#comment-290475
]
Jan Sievers commented on SUREFIRE-825:
--
If you think this issue is valid, I am willing to
Jan Sievers created SUREFIRE-824:
Summary: SpecificTestClassFilterTest currently fails on windows
Key: SUREFIRE-824
URL: https://jira.codehaus.org/browse/SUREFIRE-824
Project: Maven Surefire
Jan Sievers created SUREFIRE-825:
Summary: NPE in JUnit4TestChecker if org.junit.runner.RunWith
class can't be loaded by testClassloader
Key: SUREFIRE-825
URL: https://jira.codehaus.org/browse/SUREFIRE-825
[
https://jira.codehaus.org/browse/SUREFIRE-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Sievers updated SUREFIRE-825:
-
Attachment: 0001-SUREFIRE-825-Add-null-check-for-runWith-field.patch
git patch
[
https://jira.codehaus.org/browse/MNG-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=285101#comment-285101
]
Jan Sievers commented on MNG-5206:
--
Thanks Stuart!
I can confirm the patch MNG-5206.20111206.patch
[
https://jira.codehaus.org/browse/MNG-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=284997#comment-284997
]
Jan Sievers commented on MNG-5206:
--
yes, I can confirm that mojos which implement Disposable are
[
https://jira.codehaus.org/browse/MNG-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=284904#comment-284904
]
Jan Sievers commented on MNG-5206:
--
I tried the above steps to reproduce with a locally built
plexus container never disposed
---
Key: MNG-5206
URL: https://jira.codehaus.org/browse/MNG-5206
Project: Maven 2 3
Issue Type: Bug
Components: Plugin API
Affects Versions: 3.0.3
[
https://jira.codehaus.org/browse/SUREFIRE-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Sievers updated SUREFIRE-761:
-
Attachment: SUREFIRE-761.patch
patch including unit test which should fix the issue.
[
https://jira.codehaus.org/browse/SUREFIRE-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=276465#comment-276465
]
Jan Sievers commented on SUREFIRE-761:
--
forgot to mention, all other unit tests and ITs pass
[
http://jira.codehaus.org/browse/WAGON-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=266064#action_266064
]
Jan Sievers commented on WAGON-308:
---
The only workaround we found is to use the commons http wagon
[
http://jira.codehaus.org/browse/MRELEASE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=230293#action_230293
]
Jan Sievers commented on MRELEASE-536:
--
no this is different I think.
It's about non-case
[maven 3.x] configuration not recognized on executions level
--
Key: MENFORCER-93
URL: http://jira.codehaus.org/browse/MENFORCER-93
Project: Maven 2.x Enforcer Plugin
Issue Type:
34 matches
Mail list logo
