[jira] (MSITE-709) relativizeDecorationLinks=false seems to be ignored
Archimedes Trajano created MSITE-709: Summary: relativizeDecorationLinks=false seems to be ignored Key: MSITE-709 URL: https://jira.codehaus.org/browse/MSITE-709 Project: Maven Site Plugin Issue Type: Bug Components: relative links Affects Versions: 3.3 Reporter: Archimedes Trajano I am trying to prevent the site plugin from using the "incorrectly implemented" pathutils and use the links I have put in myself. However, setting relativizeDecorationLinks=false seems to have no effect. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRRESOURCES-74) maven remote resources plugin not compatible with Java 8
[ https://jira.codehaus.org/browse/MRRESOURCES-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRRESOURCES-74. - Resolution: Fixed Fix Version/s: 1.6 Assignee: Robert Scholte Fixed by MRRESOURCES-73 > maven remote resources plugin not compatible with Java 8 > > > Key: MRRESOURCES-74 > URL: https://jira.codehaus.org/browse/MRRESOURCES-74 > Project: Maven Remote Resources Plugin > Issue Type: Bug >Reporter: Robert Scholte >Assignee: Robert Scholte > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRRESOURCES-74) maven remote resources plugin not compatible with Java 8
Robert Scholte created MRRESOURCES-74: - Summary: maven remote resources plugin not compatible with Java 8 Key: MRRESOURCES-74 URL: https://jira.codehaus.org/browse/MRRESOURCES-74 Project: Maven Remote Resources Plugin Issue Type: Bug Reporter: Robert Scholte -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRRESOURCES-73) remote resources depends on unavailable maven filtering verison
[ https://jira.codehaus.org/browse/MRRESOURCES-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRRESOURCES-73. - Resolution: Fixed Fix Version/s: 1.6 Assignee: Olivier Lamy fixed in [r1587129|http://svn.apache.org/r1587129] > remote resources depends on unavailable maven filtering verison > --- > > Key: MRRESOURCES-73 > URL: https://jira.codehaus.org/browse/MRRESOURCES-73 > Project: Maven Remote Resources Plugin > Issue Type: Bug >Reporter: Noa Resare >Assignee: Olivier Lamy > Fix For: 1.6 > > > since maven-filtering 1.2 has been released, the current dependency as of > ec10c9caf2170fb5ec3ba227c3585b0da44fa77a of 1.2-SNAPSHOT breaks the build of > maven-remote-resources-plugin. > The fix is trivial, just remove -SNAPSHOT (and the comment) from line 64 of > maven-remote-resources-plugin/pom.xml > I think this is important, as it breaks compilation of maven-plugins -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-696) Internal Regexp Error with Windows Paths
[
https://jira.codehaus.org/browse/MASSEMBLY-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345114#comment-345114
]
Karl-Heinz Marbaise commented on MASSEMBLY-696:
---
First thanks for your issue, but can you please define a [SHA1
sum|https://github.com/apache/maven-plugins/commits/trunk] or [SVN revision
number|http://svn.apache.org/repos/asf/maven/plugins/trunk/] which can be found
in one of those locations which i currently can't...
Furthermore can you give a complete use case for that issue. Fortunately you
have created a patch with an appropriate unit test. You have added log output
with failures which is very good, but it would be better having a complete use
case which can be integrated as an integration test as well..and of course
gives other committers the chance to verify this behaviour. BTW. Have you
checked this with the last release of maven-assembly-plugin (2.4) instead of
2.5-SNAPSHOT ?
> Internal Regexp Error with Windows Paths
>
>
> Key: MASSEMBLY-696
> URL: https://jira.codehaus.org/browse/MASSEMBLY-696
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.5
> Environment: Windows 7
> maven-assembly-plugin trunk@e785abb
>Reporter: Kenney Westerhof
> Attachments: MASSEMBLY-696.patch
>
>
> On windows the Assembly plugin shows this error:
> {code}
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-assembly-plugin:2.5-SNAPSHOT:single
> (default-cli) on project myproject: Execution default-cli of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.5-SNAPSHOT:single failed:
> Unexpected internal error near index 1
> \
> ^
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
>
> Caused by: java.util.regex.PatternSyntaxException: Unexpected internal error
> near index 1
> \
> ^
> at java.util.regex.Pattern.error(Pattern.java:1924)
> at java.util.regex.Pattern.compile(Pattern.java:1671)
> at java.util.regex.Pattern.(Pattern.java:1337)
> at java.util.regex.Pattern.compile(Pattern.java:1022)
> at java.lang.String.split(String.java:2313)
> at java.lang.String.split(String.java:2355)
> at
> org.apache.maven.plugin.assembly.utils.AssemblyFormatUtils.fixRelativeRefs(AssemblyFormatUtils.java:509)
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-697) Repository assembly does not include project jar
[
https://jira.codehaus.org/browse/MASSEMBLY-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345113#comment-345113
]
Karl-Heinz Marbaise commented on MASSEMBLY-697:
---
First thank you for reporting this issue. The project jar is missing which is
correct but based on the docs:
{quote}This example demonstrates the creation of repository artifacts in an
assembly so that the archive can easily be used to update an internal
repository with the artifacts used by your project.{quote}
it is correct. The last part of the setenences
{quote}...used by your project{quote}
but not the project itself...So from my point of view i don't see a bug here.
May be the documentation should be updated or made more clear here.
> Repository assembly does not include project jar
>
>
> Key: MASSEMBLY-697
> URL: https://jira.codehaus.org/browse/MASSEMBLY-697
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.4
> Environment: Windows / Any
> Maven 3.2.1
>Reporter: Kenney Westerhof
> Attachments: MASSEMBLY-697.tar.gz
>
>
> The example on
> http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/using-repositories.html
> does not produce the advertised results, as it copies the pom into the
> repository archive, but omits the project .jar.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-697) Repository assembly does not include project jar
[ https://jira.codehaus.org/browse/MASSEMBLY-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MASSEMBLY-697: -- Affects Version/s: (was: 2.5) > Repository assembly does not include project jar > > > Key: MASSEMBLY-697 > URL: https://jira.codehaus.org/browse/MASSEMBLY-697 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 2.4 > Environment: Windows / Any > Maven 3.2.1 >Reporter: Kenney Westerhof > Attachments: MASSEMBLY-697.tar.gz > > > The example on > http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/using-repositories.html > does not produce the advertised results, as it copies the pom into the > repository archive, but omits the project .jar. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-684) Parallel Execution w Custom Assembly Descriptor Fails
[ https://jira.codehaus.org/browse/MASSEMBLY-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345112#comment-345112 ] Karl-Heinz Marbaise commented on MASSEMBLY-684: --- Unfortunately i can acknowledge this behaviour. > Parallel Execution w Custom Assembly Descriptor Fails > - > > Key: MASSEMBLY-684 > URL: https://jira.codehaus.org/browse/MASSEMBLY-684 > Project: Maven Assembly Plugin > Issue Type: Bug > Components: component descriptor >Affects Versions: 2.4 > Environment: Maven 3.0.5, JDK 1.6, Windows 7 64-bit >Reporter: Chris Rompot > Attachments: maven-assembly-plugin-error.log, pom.xml, > src-zip-only-assembly.xml > > > When using a custom assembly descriptor and building in parallel (-T > threaded), the error below results. It does not occur when using 1) a > pre-defined descriptor in parallel or 2) a custom descriptor in a sequential > (non-threaded) build. Attached are the error log, pom.xml, and custom > assembly descriptor. > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-assembly-plugin:2.4:single (make-assembly) on > project db-account-ga: Failed to create assembly: Error creating assembly > archive src: You must set at least one file. -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single > (make-assembly) on project db-account-ga: Failed to create assembly: Error > creating assembly archive src: You must set at least one file. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:171) > at > org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:139) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:440) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:139) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909) > at java.lang.Thread.run(Thread.java:662) > Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create > assembly: Error creating assembly archive src: You must set at least one file. > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:495) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 13 more > Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: > Error creating assembly archive src: You must set at least one file. > at > org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:190) > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:436) > ... 15 more > Caused by: org.codehaus.plexus.archiver.ArchiverException: You must set at > least one file. > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:246) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:222) > at > org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:910) > at > org.apache.maven.plugin.assembly.archive.archiver.AssemblyProxyArchiver.createArchive(AssemblyProxyArchiver.java:512) > at > org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:186) > ... 16 more -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPLUGIN-191) plugin-info.html is not created
[
https://jira.codehaus.org/browse/MPLUGIN-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MPLUGIN-191.
--
Resolution: Fixed
Fix Version/s: 3.3
Fixed in [r1588642|http://svn.apache.org/r1588642]
> plugin-info.html is not created
> ---
>
> Key: MPLUGIN-191
> URL: https://jira.codehaus.org/browse/MPLUGIN-191
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 2.9
> Environment: Maven 3.x
>Reporter: Balazs Zsoldos
>Assignee: Robert Scholte
>Priority: Critical
> Fix For: 3.3
>
>
> During running maven-plugin-plugin:report the following exception occurs:
> {noformat}Caused by: java.lang.NoClassDefFoundError:
> org/apache/maven/doxia/module/xhtml/decoration/render/RenderingContext
> at
> org.apache.maven.reporting.sink.SinkFactory.createSink(SinkFactory.java:59)
> at
> org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:85)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> ... 20 more
> Caused by: java.lang.ClassNotFoundException:
> org.apache.maven.doxia.module.xhtml.decoration.render.RenderingContext
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
> ... 23 more{noformat}
> After some debugging it seams to me that the cause is the version of
> maven-reporting-impl dependency which is now 2.0.5. I made it work with the
> following snippet in my pom.xml:
> {code:xml}
> org.apache.maven.plugins
> maven-plugin-plugin
> 2.9
>
>
> report
> pre-site
>
> report
>
>
>
>
>
>
> org.apache.maven.reporting
>
> maven-reporting-impl
> 2.2
>
>
> {code}
> After this setting the plugin-info.html file is generated at
> target/generated-site/xdoc directory. However nothing is copied to
> target/site as the output file should be moved to target/generated-site/xhtml
> and it should have the extension .xhtml.vm.
> I made the workaround that I copy and rename the html file to
> src/site/xhtml/plugin-info.xhtml.vm.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5621) Transitive dependency for both compile and test
[
https://jira.codehaus.org/browse/MNG-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MNG-5621.
---
Resolution: Duplicate
Assignee: Robert Scholte
Duplicate of MNG-1378, Also read [this
blog|http://rfscholte.wordpress.com/2010/09/05/how-to-create-a-jar-containing-reusableabstract-testclasses-with-maven/]
to understand the current behavior.
> Transitive dependency for both compile and test
> ---
>
> Key: MNG-5621
> URL: https://jira.codehaus.org/browse/MNG-5621
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Dependencies
>Affects Versions: 3.2.1
> Environment: Apache Maven 3.2.1
> (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-15T02:37:52+09:00)
> Maven home: /usr/local/Cellar/maven/3.2.1/libexec
> Java version: 1.8.0, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.9.2", arch: "x86_64", family: "mac"
>Reporter: Jin Kwon
>Assignee: Robert Scholte
>Priority: Trivial
>
> * artifact `B` depends on `A` in test scope.
> * artifact 'C' depends on 'B' in compile scope and test scope with test-jar
> {code:xml}
> B
>
>
> A
> test
>
>
> {code}
> {code:xml}
> C
>
>
> B
> compile
>
>
> B
> test-jar
> test
>
>
> {code}
> {{expected: artifact 'C''s classpath contains 'A'}}
> {{actual : 'A' is unknown in 'C''s test time}}
> Is this normal behaviour or {{test-jar with test}} overrides {{compile}}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5621) Transitive dependency for both compile and test
[
https://jira.codehaus.org/browse/MNG-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MNG-5621:
--
Description:
* artifact `B` depends on `A` in test scope.
* artifact 'C' depends on 'B' in compile scope and test scope with test-jar
{code:xml}
B
A
test
{code}
{code:xml}
C
B
compile
B
test-jar
test
{code}
{{expected: artifact 'C''s classpath contains 'A'}}
{{actual : 'A' is unknown in 'C''s test time}}
Is this normal behaviour or {{test-jar with test}} overrides {{compile}}
was:
* artifact `B` depends on `A` in test scope.
* artifact 'C' depends on 'B' in compile scope and test scope with test-jar
{code:xml}
B
A
test
{code}
{code:xml}
C
B
compile
B
test-jar
test
{code}
{{expected: artifact 'C''s classpath contains 'A'}}
{{actual : 'A' is unknown in 'C''s test time}}
> Transitive dependency for both compile and test
> ---
>
> Key: MNG-5621
> URL: https://jira.codehaus.org/browse/MNG-5621
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Dependencies
>Affects Versions: 3.2.1
> Environment: Apache Maven 3.2.1
> (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-15T02:37:52+09:00)
> Maven home: /usr/local/Cellar/maven/3.2.1/libexec
> Java version: 1.8.0, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.9.2", arch: "x86_64", family: "mac"
>Reporter: Jin Kwon
>Priority: Trivial
>
> * artifact `B` depends on `A` in test scope.
> * artifact 'C' depends on 'B' in compile scope and test scope with test-jar
> {code:xml}
> B
>
>
> A
> test
>
>
> {code}
> {code:xml}
> C
>
>
> B
> compile
>
>
> B
> test-jar
> test
>
>
> {code}
> {{expected: artifact 'C''s classpath contains 'A'}}
> {{actual : 'A' is unknown in 'C''s test time}}
> Is this normal behaviour or {{test-jar with test}} overrides {{compile}}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5621) Transitive dependency for both compile and test
[
https://jira.codehaus.org/browse/MNG-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MNG-5621:
--
Description:
* artifact `B` depends on `A` in test scope.
* artifact 'C' depends on 'B' in compile scope and test scope with test-jar
{code:xml}
B
A
test
{code}
{code:xml}
C
B
compile
B
test-jar
test
{code}
{{expected: artifact 'C''s classpath contains 'A'}}
{{actual : 'A' is unknown in 'C''s test time}}
was:
1. artifact `B` depends on `A` in test scope.
2. artifact 'C' depends on 'B' in compile scope and test scope with test-jar
expected: artifact 'C''s classpath contains 'A'
actual : 'A' is unknown in 'C''s test time.
> Transitive dependency for both compile and test
> ---
>
> Key: MNG-5621
> URL: https://jira.codehaus.org/browse/MNG-5621
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Dependencies
>Affects Versions: 3.2.1
> Environment: Apache Maven 3.2.1
> (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-15T02:37:52+09:00)
> Maven home: /usr/local/Cellar/maven/3.2.1/libexec
> Java version: 1.8.0, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.9.2", arch: "x86_64", family: "mac"
>Reporter: Jin Kwon
>Priority: Trivial
>
> * artifact `B` depends on `A` in test scope.
> * artifact 'C' depends on 'B' in compile scope and test scope with test-jar
> {code:xml}
> B
>
>
> A
> test
>
>
> {code}
> {code:xml}
> C
>
>
> B
> compile
>
>
> B
> test-jar
> test
>
>
> {code}
> {{expected: artifact 'C''s classpath contains 'A'}}
> {{actual : 'A' is unknown in 'C''s test time}}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5621) Transitive dependency for both compile and test
Jin Kwon created MNG-5621: - Summary: Transitive dependency for both compile and test Key: MNG-5621 URL: https://jira.codehaus.org/browse/MNG-5621 Project: Maven 2 & 3 Issue Type: Improvement Components: Dependencies Affects Versions: 3.2.1 Environment: Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-15T02:37:52+09:00) Maven home: /usr/local/Cellar/maven/3.2.1/libexec Java version: 1.8.0, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.9.2", arch: "x86_64", family: "mac" Reporter: Jin Kwon Priority: Trivial 1. artifact `B` depends on `A` in test scope. 2. artifact 'C' depends on 'B' in compile scope and test scope with test-jar expected: artifact 'C''s classpath contains 'A' actual : 'A' is unknown in 'C''s test time. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
