[jira] (MSITE-724) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-site-plugin:3.4:jar
Christian Schulte created MSITE-724:
---
Summary: An API incompatibility was encountered while executing
org.apache.maven.plugins:maven-site-plugin:3.4:jar
Key: MSITE-724
URL: https://jira.codehaus.org/browse/MSITE-724
Project: Maven Site Plugin
Issue Type: Bug
Affects Versions: 3.4
Reporter: Christian Schulte
Priority: Blocker
{code}
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-jar of goal org.apache.maven.plugins:maven-site-plugin:3.4:jar failed:
An API incompatibility was encountered while executing
org.apache.maven.plugins:maven-site-plugin:3.4:jar:
java.lang.NoSuchMethodError:
org.codehaus.plexus.archiver.jar.Manifest.getMainSection()Lorg/codehaus/plexus/archiver/jar/Manifest$Section;
{code}
{code}
Caused by: java.lang.NoSuchMethodError:
org.codehaus.plexus.archiver.jar.Manifest.getMainSection()Lorg/codehaus/plexus/archiver/jar/Manifest$Section;
at
org.apache.maven.archiver.MavenArchiver.getManifest(MavenArchiver.java:102)
at
org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:513)
at
org.apache.maven.plugins.site.render.SiteJarMojo.createArchive(SiteJarMojo.java:201)
at
org.apache.maven.plugins.site.render.SiteJarMojo.execute(SiteJarMojo.java:130)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
... 20 more
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCLEAN-38) Allow a global set of include and exclude filters
[ https://jira.codehaus.org/browse/MCLEAN-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MCLEAN-38. - Resolution: Won't Fix Assignee: Karl-Heinz Marbaise What about http://maven.apache.org/plugins/maven-clean-plugin/examples/delete_additional_files.html ? Does that fit ? If not don't hesitate to reopen the issue. > Allow a global set of include and exclude filters > - > > Key: MCLEAN-38 > URL: https://jira.codehaus.org/browse/MCLEAN-38 > Project: Maven Clean Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Nick Pellow >Assignee: Karl-Heinz Marbaise > Attachments: MCLEAN-38-maven-clean-plugin.patch > > > I am about to submit a patch to the maven-clean-plugin which will allow a > global includes and excludes patterns to be configured. > Currently, it is not possibly to easily do a clean and have specific files in > the default output directories preserved. > The patch will allow a comma separated list of exclusions and inclusions to > use when removing the default output directories. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCLEAN-55) maven clean seems to use old java.io API to clean the target directory
[ https://jira.codehaus.org/browse/MCLEAN-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349545#comment-349545 ] Karl-Heinz Marbaise commented on MCLEAN-55: --- Unfortunately the example project does not work, cause it uses a dependency which does not exist. [WARNING] The POM for de.mstier:shared:jar:1.0-SNAPSHOT is missing, no dependency information available Could clean up this project..? > maven clean seems to use old java.io API to clean the target directory > -- > > Key: MCLEAN-55 > URL: https://jira.codehaus.org/browse/MCLEAN-55 > Project: Maven Clean Plugin > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Mark > Fix For: 2.6 > > > Problem: the old java.io API cannot handle filenames that have a bad > encoding, ie. iso-8859-1 encoded umlauts when running with LC_ALL=*.UTF-8. > To reproduce the problem do: > git clone https://github.com/jjYBdx4IL/filenameenc.git > cd filenameenc > mvn test > mvn clean # <- produces an error when trying to remove target/ > The example itself demonstrates the problem and shows a solution by using > java.nio.Files.newDirectoryStream(). -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRRESOURCES-75) Currently running -Prun-its clean verify - fails
Karl-Heinz Marbaise created MRRESOURCES-75: -- Summary: Currently running -Prun-its clean verify - fails Key: MRRESOURCES-75 URL: https://jira.codehaus.org/browse/MRRESOURCES-75 Project: Maven Remote Resources Plugin Issue Type: Bug Affects Versions: 1.6 Environment: ALL Reporter: Karl-Heinz Marbaise Attachments: mvn.log Currently tested with Maven 2.2.1, Maven 3.0.5. Attached a log file with the message for further anlysis. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRRESOURCES-75) Currently running -Prun-its clean verify - fails
[ https://jira.codehaus.org/browse/MRRESOURCES-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MRRESOURCES-75: --- Fix Version/s: 1.6 > Currently running -Prun-its clean verify - fails > > > Key: MRRESOURCES-75 > URL: https://jira.codehaus.org/browse/MRRESOURCES-75 > Project: Maven Remote Resources Plugin > Issue Type: Bug >Affects Versions: 1.6 > Environment: ALL >Reporter: Karl-Heinz Marbaise > Fix For: 1.6 > > Attachments: mvn.log > > > Currently tested with Maven 2.2.1, Maven 3.0.5. Attached a log file with the > message for further anlysis. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-182) upgrade to last 5.1.0
[ https://jira.codehaus.org/browse/MPMD-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349526#comment-349526 ] Zlika commented on MPMD-182: Great workaround, thanks! > upgrade to last 5.1.0 > - > > Key: MPMD-182 > URL: https://jira.codehaus.org/browse/MPMD-182 > Project: Maven PMD Plugin > Issue Type: Improvement >Reporter: Olivier Lamy > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-1378) Make dependencies of test-jars transitive
[ https://jira.codehaus.org/browse/MNG-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349524#comment-349524 ] Anders Kr. Andersen commented on MNG-1378: -- In my eyes tests are not public by any way It is interfaces and implementation that makes an artifact Therefore extending test cases is not something I would do. Not only should you make correct interfaces and implementation, now you also need to consider making tests so they can be extended .. This pattern would add complexity to an artifact. I find the system is designed correct as it is ! -1 > Make dependencies of test-jars transitive > - > > Key: MNG-1378 > URL: https://jira.codehaus.org/browse/MNG-1378 > Project: Maven > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0 >Reporter: Mark Hobson > Fix For: Issues to be reviewed for 3.x > > Attachments: mng1378.tar.gz > > > test-jar transitive dependencies are calculated as per compile scope rather > than test scope. > The situation is demonstrated nicely in it0077: > * module sub1 has a test-scoped dependency of commons-lang > * module sub2 has a test-scoped dependency of sub1 test-jar > sub2 tests should inherit the commons-lang transitive dependency. For > example: > Index: > maven-core-it/it0077/sub2/src/test/java/org/apache/maven/it0077/PersonTwoTest.java > === > --- > maven-core-it/it0077/sub2/src/test/java/org/apache/maven/it0077/PersonTwoTest.java > (revision > 328307) > +++ > maven-core-it/it0077/sub2/src/test/java/org/apache/maven/it0077/PersonTwoTest.java > (working > copy) > @@ -1,6 +1,7 @@ > package org.apache.maven.it0077; > import junit.framework.TestCase; > +import org.apache.commons.lang.BooleanUtils; > public class PersonTwoTest > extends PersonTest > Results in: > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Compilation failure > c:\maven-components\maven-core-it\it0077\sub2\src\test\java\org\apache\maven\it0077\PersonTwoTest.java:[4,31] > package org.apache.commons.lang does not exist -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-238) ConcurrentModificationException
[ https://jira.codehaus.org/browse/MCHECKSTYLE-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349509#comment-349509 ] Michael Osipov commented on MCHECKSTYLE-238: Cannot be fixed right now, see link. Leaving as unresolved. > ConcurrentModificationException > --- > > Key: MCHECKSTYLE-238 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-238 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.12.1 > Environment: maven 3.1.1, jdk 170_25 >Reporter: Jorg Heymans > > in a mutithreaded build (-T3C on a quad core) i am rather often, but not > consistently seeing this > maven-checkstyle-plugin:2.12.1:check failed. ConcurrentModificationException > I dont have a better stacktrace, seems that -X lowers the odds of this > happening significantly. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-238) ConcurrentModificationException
Jorg Heymans created MCHECKSTYLE-238: Summary: ConcurrentModificationException Key: MCHECKSTYLE-238 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-238 Project: Maven Checkstyle Plugin Issue Type: Bug Affects Versions: 2.12.1 Environment: maven 3.1.1, jdk 170_25 Reporter: Jorg Heymans in a mutithreaded build (-T3C on a quad core) i am rather often, but not consistently seeing this maven-checkstyle-plugin:2.12.1:check failed. ConcurrentModificationException I dont have a better stacktrace, seems that -X lowers the odds of this happening significantly. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
