[jira] (MRESOURCES-201) Add Parameter for not ignore directories with a leading dot.
Felix Köhler created MRESOURCES-201: --- Summary: Add Parameter for not ignore directories with a leading dot. Key: MRESOURCES-201 URL: https://jira.codehaus.org/browse/MRESOURCES-201 Project: Maven Resources Plugin Issue Type: Improvement Components: filtering Affects Versions: 2.7 Reporter: Felix Köhler Add Parameter like to configure (de-)activate for system default excludes. In my situation I want to copy a .metadata directory and maven resources plugin ignores it. The situation is explained here from an other user http://stackoverflow.com/questions/25422298/maven-resources-plugin-wont-copy-metadata-folder -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRESOURCES-201) Add Parameter for not ignore directories with a leading dot.
[ https://jira.codehaus.org/browse/MRESOURCES-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Köhler updated MRESOURCES-201: Description: Add Parameter like to configure (de-)activate for system default excludes. In my situation I want to copy a .metadata directory and maven resources plugin ignores it. So it would be very nice if the resources-plugin can do the work for me. The situation is explained here from an other user http://stackoverflow.com/questions/25422298/maven-resources-plugin-wont-copy-metadata-folder was: Add Parameter like to configure (de-)activate for system default excludes. In my situation I want to copy a .metadata directory and maven resources plugin ignores it. The situation is explained here from an other user http://stackoverflow.com/questions/25422298/maven-resources-plugin-wont-copy-metadata-folder > Add Parameter for not ignore directories with a leading dot. > > > Key: MRESOURCES-201 > URL: https://jira.codehaus.org/browse/MRESOURCES-201 > Project: Maven Resources Plugin > Issue Type: Improvement > Components: filtering >Affects Versions: 2.7 >Reporter: Felix Köhler > > Add Parameter like to configure (de-)activate for system > default excludes. > In my situation I want to copy a .metadata directory and maven resources > plugin ignores it. So it would be very nice if the resources-plugin can do > the work for me. > The situation is explained here from an other user > http://stackoverflow.com/questions/25422298/maven-resources-plugin-wont-copy-metadata-folder -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-435) Key exchange negotiation failure with newer version of openssl
Ceki Gulcu created WAGON-435: Summary: Key exchange negotiation failure with newer version of openssl Key: WAGON-435 URL: https://jira.codehaus.org/browse/WAGON-435 Project: Maven Wagon Issue Type: Bug Affects Versions: 2.6 Reporter: Ceki Gulcu As described in [jsch bug 79|http://sourceforge.net/p/jsch/bugs/79/], newer versions of openssh have diffie-hellman exchange disabled by default. Since jsch does not seem to support key exchange algorithms other then Diffie-Hellman, the scp provider fails for servers using newer versions of openssl. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-435) Key exchange negotiation failure with newer versions of openssl
[ https://jira.codehaus.org/browse/WAGON-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ceki Gulcu updated WAGON-435: - Summary: Key exchange negotiation failure with newer versions of openssl (was: Key exchange negotiation failure with newer version of openssl) > Key exchange negotiation failure with newer versions of openssl > --- > > Key: WAGON-435 > URL: https://jira.codehaus.org/browse/WAGON-435 > Project: Maven Wagon > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Ceki Gulcu > > As described in [jsch bug 79|http://sourceforge.net/p/jsch/bugs/79/], newer > versions of openssh have diffie-hellman exchange disabled by default. Since > jsch does not seem to support key exchange algorithms other then > Diffie-Hellman, the scp provider fails for servers using newer versions of > openssl. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-435) Key exchange negotiation failure with newer versions of openssl
[ https://jira.codehaus.org/browse/WAGON-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ceki Gulcu updated WAGON-435: - Priority: Critical (was: Major) > Key exchange negotiation failure with newer versions of openssl > --- > > Key: WAGON-435 > URL: https://jira.codehaus.org/browse/WAGON-435 > Project: Maven Wagon > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Ceki Gulcu >Priority: Critical > > As described in [jsch bug 79|http://sourceforge.net/p/jsch/bugs/79/], newer > versions of openssh have diffie-hellman exchange disabled by default. Since > jsch does not seem to support key exchange algorithms other then > Diffie-Hellman, the scp provider fails for servers using newer versions of > openssl. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRELEASE-901) Goal stage should take parameter localCheckout as well.
Mirko Friedenhagen created MRELEASE-901:
---
Summary: Goal stage should take parameter localCheckout as well.
Key: MRELEASE-901
URL: https://jira.codehaus.org/browse/MRELEASE-901
Project: Maven Release Plugin
Issue Type: New Feature
Components: stage
Affects Versions: 2.5.1
Reporter: Mirko Friedenhagen
This will work with DCVS only!
Especially when using the {{stage}} goal instead of {{perform}}, I do set
{{pushChanges}} to {{false}} and want to use {{localCheckout}} because the
modified POMs and the tag only exist on the machine running {{prepare}}.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SCM-497) Please improve documentation on http://maven.apache.org/scm/guide/usage.html
[
https://jira.codehaus.org/browse/SCM-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated SCM-497:
Fix Version/s: (was: 1.x)
> Please improve documentation on http://maven.apache.org/scm/guide/usage.html
>
>
> Key: SCM-497
> URL: https://jira.codehaus.org/browse/SCM-497
> Project: Maven SCM
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 1.2
> Environment: dependencies: org.apache.maven:maven-embedder:2.0.4 and
> org.apache.maven.scm:maven-scm-api:1.2
>Reporter: Albert Kurucz
> Attachments: TestEmbedder.java
>
>
> Trying to use Maven-SCM in my application I have selected the "With Plexus
> IOC" method as provided on http://maven.apache.org/scm/guide/usage.html.
> I have made this to a small unit test (attached to this issue), which failed
> as:
> {noformat}Testsuite: com.jtstand.TestEmbedder
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
> at org.codehaus.plexus.embed.Embedder.lookup(Embedder.java:78)
> at com.jtstand.TestEmbedder.(TestEmbedder.java:24)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at junit.framework.TestSuite.createTest(TestSuite.java:54)
> at junit.framework.TestSuite.addTestMethod(TestSuite.java:280)
> at junit.framework.TestSuite.(TestSuite.java:140)
> at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:481)
> at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1031)
> at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:888)
> ))
> Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.032 sec{noformat}
> Please improve usage doc on http://maven.apache.org/scm/guide/usage.html.
> Please provide me help getting started in this direction.
> Thx.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-185) Cannot run invoker ITs on Windows with Maven 3.3.1
[
https://jira.codehaus.org/browse/MINVOKER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MINVOKER-185.
---
Resolution: Fixed
Fix Version/s: 1.9.1
Fixed in [r1668997|http://svn.apache.org/r1668997]
> Cannot run invoker ITs on Windows with Maven 3.3.1
> --
>
> Key: MINVOKER-185
> URL: https://jira.codehaus.org/browse/MINVOKER-185
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.9
> Environment: Apache Maven 3.3.1
> (cab6659f9874fa96462afef40fcf6bc033d58c1c; 2015-03-13T20:10:27+00:00)
> Java version: 1.8.0_31, vendor: Oracle Corporation
> Default locale: en_GB, platform encoding: Cp1251
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
>Reporter: Sergei Ivanov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 1.9.1
>
>
> {{mvn.bat}} has been renamed to {{mvn.cmd}} in Maven 3.3.1, and that appears
> to have broken the assumption in {{maven-invoker-plugin}}. I am unable to run
> integration tests under the new version of Maven.
> {noformat}
> [INFO] Building: TEST-9\pom.xml
> [INFO] ..FAILED (0.0 s)
> [INFO] Maven invocation failed. Error configuring command-line. Reason:
> Maven executable not found at: C:\Java\apache-maven-3.3.1\bin\mvn.bat
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (DOXIASITETOOLS-69) ConcurrentModificationException when using site:run
[
https://jira.codehaus.org/browse/DOXIASITETOOLS-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=365637#comment-365637
]
Christopher Tubbs commented on DOXIASITETOOLS-69:
-
Saw this, too, using Maven 3.2.3 and maven-plugin-plugin versions 3.2, 3.3, and
3.4.
> ConcurrentModificationException when using site:run
> ---
>
> Key: DOXIASITETOOLS-69
> URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-69
> Project: Maven Doxia Sitetools
> Issue Type: Bug
> Components: Site renderer
>Affects Versions: 1.2
> Environment: Maven 2.2.1 with maven-site-plugin 3.0
>Reporter: Christof Schöll
> Attachments: testmvnsite.zip
>
>
> When using maven with site:run I get the following exception, which seem to
> originate from the Doxia Site Renderer
> {noformat}2012-04-04 12:27:07.653:WARN::/css/maven-theme.css
> java.util.ConcurrentModificationException
> at
> java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
> at java.util.AbstractList$Itr.next(AbstractList.java:343)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.locateDocumentFiles(DefaultSiteRenderer.java:149)
> at
> org.apache.maven.plugins.site.webapp.DoxiaFilter.doFilter(DoxiaFilter.java:174)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
> at
> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:440)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:926)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> 2012-04-04 12:27:07.656:WARN::/images/logos/maven-feather.png
> java.util.ConcurrentModificationException
> at
> java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
> at java.util.AbstractList$Itr.next(AbstractList.java:343)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.locateDocumentFiles(DefaultSiteRenderer.java:149)
> at
> org.apache.maven.plugins.site.webapp.DoxiaFilter.doFilter(DoxiaFilter.java:174)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
> at
> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:440)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:926)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582){noformat}
> The following source code in
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer (line 149) seems to
> contain the problem:
> {code:java}149 for ( File siteDirectory :
> siteRenderingContext.getSiteDirectories() )
> 150
[jira] (DOXIASITETOOLS-69) ConcurrentModificationException when using site:run
[
https://jira.codehaus.org/browse/DOXIASITETOOLS-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=365639#comment-365639
]
Christopher Tubbs commented on DOXIASITETOOLS-69:
-
My last comment also pertains to doxia-site-renderer 1.4 (and the line number
is now 144).
> ConcurrentModificationException when using site:run
> ---
>
> Key: DOXIASITETOOLS-69
> URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-69
> Project: Maven Doxia Sitetools
> Issue Type: Bug
> Components: Site renderer
>Affects Versions: 1.2
> Environment: Maven 2.2.1 with maven-site-plugin 3.0
>Reporter: Christof Schöll
> Attachments: testmvnsite.zip
>
>
> When using maven with site:run I get the following exception, which seem to
> originate from the Doxia Site Renderer
> {noformat}2012-04-04 12:27:07.653:WARN::/css/maven-theme.css
> java.util.ConcurrentModificationException
> at
> java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
> at java.util.AbstractList$Itr.next(AbstractList.java:343)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.locateDocumentFiles(DefaultSiteRenderer.java:149)
> at
> org.apache.maven.plugins.site.webapp.DoxiaFilter.doFilter(DoxiaFilter.java:174)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
> at
> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:440)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:926)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> 2012-04-04 12:27:07.656:WARN::/images/logos/maven-feather.png
> java.util.ConcurrentModificationException
> at
> java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
> at java.util.AbstractList$Itr.next(AbstractList.java:343)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.locateDocumentFiles(DefaultSiteRenderer.java:149)
> at
> org.apache.maven.plugins.site.webapp.DoxiaFilter.doFilter(DoxiaFilter.java:174)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
> at
> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:440)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:926)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582){noformat}
> The following source code in
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer (line 149) seems to
> contain the problem:
> {code:java}149 for ( File siteDirectory :
> siteRenderingContext.getSiteDirectories() )
[jira] (MNG-5788) Version 3.2.5 disappeared from the download page
[ https://jira.codehaus.org/browse/MNG-5788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Schroevers closed MNG-5788. --- Resolution: Fixed This has been fixed by now, so I'll close the ticket. Some links on the download page are still incorrect, though. I opened [PR #2|https://github.com/apache/maven-site/pull/2] for that. > Version 3.2.5 disappeared from the download page > > > Key: MNG-5788 > URL: https://jira.codehaus.org/browse/MNG-5788 > Project: Maven > Issue Type: Bug > Components: General >Affects Versions: 3.2.5 > Environment: Any >Reporter: Stephan Schroevers >Priority: Critical > > The [Maven download page|https://maven.apache.org/download.cgi] currently > lists versions 3.3.1, 3.1.1 and 3.0.5. Version 3.2.5 is missing. I guess this > happened y accident when 3.3.1 was made available. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-745) -Dtest supports multiple test classes but not multiple test methods
[ https://jira.codehaus.org/browse/SUREFIRE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reopened SUREFIRE-745: --- Assignee: Tibor Digana (was: Olivier Lamy) Multiple Classes and Methods, regex, non-regex support for JUnit4, JUnit47+, TestNG providers. https://github.com/apache/maven-surefire/pull/83 > -Dtest supports multiple test classes but not multiple test methods > --- > > Key: SUREFIRE-745 > URL: https://jira.codehaus.org/browse/SUREFIRE-745 > Project: Maven Surefire > Issue Type: Improvement > Environment: Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500) > Java version: 1.6.0_24, vendor: Apple Inc. > Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home > Default locale: en_CA, platform encoding: MacRoman > OS name: "mac os x", version: "10.6.7", arch: "x86_64", family: "mac" >Reporter: reid holmes >Assignee: Tibor Digana >Priority: Minor > Fix For: 2.12.1 > > Attachments: multipleMethods.patch, multipleMethods-v2.patch, > multipleMethods-v3.patch, multipleMethods-v4.patch, SUREFIRE-745.patch, > SUREFIRE-745-v2.patch > > > The -Dtest parameter is very handy for running a specific test class or test > method. It also supports running multiple test classes. Unfortunately, it > does not permit specifying running multiple test methods. It would be great > if this were possible. > The examples below are from the Apache Commons project. > WORKS: Run multiple test classes: > mvn test -Dtest=ImmutablePairTest,StopWatchTest > WORKS: Run a specific test method: > mvn test -Dtest=ImmutablePairTest#testBasic > DOES NOT WORK: > mvn test > -Dtest=StopWatchTest#testStopWatchSimple,StopWatchTest#testStopWatchSimpleGet > mvn test -Dtest=ImmutablePairTest#testBasic,StopWatchTest#testLang315 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1126) Discrepancy between test exclusion docs and plugin behavior
[ https://jira.codehaus.org/browse/SUREFIRE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1126: --- Fix Version/s: 2.19 > Discrepancy between test exclusion docs and plugin behavior > --- > > Key: SUREFIRE-1126 > URL: https://jira.codehaus.org/browse/SUREFIRE-1126 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.18 >Reporter: Dima Spivak >Assignee: Tibor Digana > Fix For: 2.19 > > > According to [Surefire > documentation|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#test], > tests can be excluded on the command line by prefixing with an exclamation > mark. Is this expected behavior that's currently broken, or did someone jump > the gun with the docs? -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1126) Discrepancy between test exclusion docs and plugin behavior
[ https://jira.codehaus.org/browse/SUREFIRE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=365642#comment-365642 ] Tibor Digana commented on SUREFIRE-1126: Since of 2.19 the exclamation mark (!) is applicable to regex and non-regex format. Additionally available Multiple Classes and Methods, regex, non-regex support for JUnit4, JUnit47+, TestNG providers. https://github.com/apache/maven-surefire/pull/83 > Discrepancy between test exclusion docs and plugin behavior > --- > > Key: SUREFIRE-1126 > URL: https://jira.codehaus.org/browse/SUREFIRE-1126 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.18 >Reporter: Dima Spivak >Assignee: Tibor Digana > Fix For: 2.19 > > > According to [Surefire > documentation|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#test], > tests can be excluded on the command line by prefixing with an exclamation > mark. Is this expected behavior that's currently broken, or did someone jump > the gun with the docs? -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-745) -Dtest supports multiple test classes but not multiple test methods
[ https://jira.codehaus.org/browse/SUREFIRE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-745: -- Fix Version/s: 2.19 > -Dtest supports multiple test classes but not multiple test methods > --- > > Key: SUREFIRE-745 > URL: https://jira.codehaus.org/browse/SUREFIRE-745 > Project: Maven Surefire > Issue Type: Improvement > Environment: Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500) > Java version: 1.6.0_24, vendor: Apple Inc. > Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home > Default locale: en_CA, platform encoding: MacRoman > OS name: "mac os x", version: "10.6.7", arch: "x86_64", family: "mac" >Reporter: reid holmes >Assignee: Tibor Digana >Priority: Minor > Fix For: 2.12.1, 2.19 > > Attachments: multipleMethods.patch, multipleMethods-v2.patch, > multipleMethods-v3.patch, multipleMethods-v4.patch, SUREFIRE-745.patch, > SUREFIRE-745-v2.patch > > > The -Dtest parameter is very handy for running a specific test class or test > method. It also supports running multiple test classes. Unfortunately, it > does not permit specifying running multiple test methods. It would be great > if this were possible. > The examples below are from the Apache Commons project. > WORKS: Run multiple test classes: > mvn test -Dtest=ImmutablePairTest,StopWatchTest > WORKS: Run a specific test method: > mvn test -Dtest=ImmutablePairTest#testBasic > DOES NOT WORK: > mvn test > -Dtest=StopWatchTest#testStopWatchSimple,StopWatchTest#testStopWatchSimpleGet > mvn test -Dtest=ImmutablePairTest#testBasic,StopWatchTest#testLang315 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-760) dependencySet unpack + zip assembly produces zip file without permissions
Rafael Chaves created MASSEMBLY-760: --- Summary: dependencySet unpack + zip assembly produces zip file without permissions Key: MASSEMBLY-760 URL: https://jira.codehaus.org/browse/MASSEMBLY-760 Project: Maven Assembly Plugin Issue Type: Bug Components: dependencySet Affects Versions: 2.5.3 Environment: Linux Reporter: Rafael Chaves If an assembly unpacks a zip dependency and produces a new zip file, the rezipped files will have no read permissions. Version 2.4 does not have this issue. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
