[jira] Created: (MAVENUPLOAD-2712) dnsjnio 1.0.3
dnsjnio 1.0.3 - Key: MAVENUPLOAD-2712 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2712 Project: Maven Upload Requests Issue Type: Wish Reporter: Stefano Bagnara dnsjnio 1.0.3 I'm not the author of dnsjnio (even if I'm a contributor). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2711) dnsjava 2.0.8
dnsjava 2.0.8 - Key: MAVENUPLOAD-2711 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2711 Project: Maven Upload Requests Issue Type: Wish Reporter: Stefano Bagnara dnsjava 2.0.8 I'm not the author of dnsjava, but I already uploaded the 2.0.1 to 2.0.6 bundles, so here we are with newer bundles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2713) jvyaml 0.2.1
jvyaml 0.2.1 Key: MAVENUPLOAD-2713 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2713 Project: Maven Upload Requests Issue Type: Wish Reporter: Stefano Bagnara jvyaml 0.2.1 I'm not the author of jvyaml. It is a dependency for an ASF project (Apache JAMES jSPF) and I'm uploading the dependencies that are not in central, yet) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2711) dnsjava 2.0.8
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211410#action_211410 ] Stefano Bagnara commented on MAVENUPLOAD-2711: -- I don't understand. You accepted all of the previous dnsjava versions done exactly the same way. Here http://maven.apache.org/guides/mini/guide-central-repository-upload.html it says: "***If*** you want to include a jar with java sources in your upload (recommended, unless your license doesn't allow sources to be redistributed) the command to run is:" And dnsjava does not provide source and javadoc artifacts: am I supposed to create the jar for them manually? We (apache james project) need this artifact (and also MAVENUPLOAD-2713 and MAVENUPLOAD-2712) to make a release: I know we are not in ASF here, but you are an ASF member: how are we supposed to make a release depending on that jars if we cannot upload them to central in an easy way? > dnsjava 2.0.8 > - > > Key: MAVENUPLOAD-2711 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2711 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Stefano Bagnara >Assignee: Juven Xu > > dnsjava 2.0.8 > I'm not the author of dnsjava, but I already uploaded the 2.0.1 to 2.0.6 > bundles, so here we are with newer bundles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2711) dnsjava 2.0.8
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217524#action_217524 ] Stefano Bagnara commented on MAVENUPLOAD-2711: -- Well, everything landed on central without any check for years, I'm happy to see now there is some control, but I don't like too much the new rules. BTW, The only URL I found about uploading third party JARs to central does not give any hint about what are the new rules, so before I waste cycles can you point me to some decent checklist? E.g: 1) As you ask sources and javadocs jar I decided that it was easier for me to siply write a full pom and build from sources the projects. Should I upload my own compiled binary jar or the original distribution one? (I'd prefer the original...). 2) It seems you now require PGP signatures: should I only sign the bundle or every jar/pom like it was a release from me? Is there anything else I should know before starting this pain? Yes, it's a pain because most dnsjava depending maven projects around still make use of an insicure and outdated dnsjava simply because a newer one is not on central. And please, update the mini guide as it obviously contains misleading informations. > dnsjava 2.0.8 > - > > Key: MAVENUPLOAD-2711 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2711 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Stefano Bagnara >Assignee: Juven Xu > > dnsjava 2.0.8 > I'm not the author of dnsjava, but I already uploaded the 2.0.1 to 2.0.6 > bundles, so here we are with newer bundles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2763) dnsjava 2.0.8
dnsjava 2.0.8 - Key: MAVENUPLOAD-2763 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2763 Project: Maven Upload Requests Issue Type: Wish Reporter: Stefano Bagnara dnsjava 2.0.8 I'm not the author of dnsjava, but I already uploaded the 2.0.1 to 2.0.6 bundles, so here we are with newer bundles. This is built from original 2.0.8 sources, just added my own pom, built and bundled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2765) jvyaml 0.2.1
jvyaml 0.2.1 Key: MAVENUPLOAD-2765 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2765 Project: Maven Upload Requests Issue Type: Wish Reporter: Stefano Bagnara jvyaml 0.2.1 I'm not the author of jvyaml. It is a dependency for an ASF project (Apache JAMES jSPF) and I'm uploading the dependencies that are not in central, yet) This is built from original sources, just added my own pom, built and bundled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2764) dnsjnio 1.0.3
dnsjnio 1.0.3 - Key: MAVENUPLOAD-2764 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2764 Project: Maven Upload Requests Issue Type: Wish Reporter: Stefano Bagnara dnsjnio 1.0.3 I'm not the author of dnsjnio (even if I'm a contributor). This is built from original sources, just added my own pom, built and bundled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2765) jvyaml 0.2.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217530#action_217530 ] Stefano Bagnara commented on MAVENUPLOAD-2765: -- Contributor URL should have been "NOT A DEVELOPER" but when I hit enter for autocompletion the issue has been submitted (no edit). > jvyaml 0.2.1 > > > Key: MAVENUPLOAD-2765 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2765 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Stefano Bagnara > > jvyaml 0.2.1 > I'm not the author of jvyaml. It is a dependency for an ASF project (Apache > JAMES jSPF) and I'm uploading the dependencies that are not in central, yet) > This is built from original sources, just added my own pom, built and bundled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2711) dnsjava 2.0.8
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218856#action_218856 ] Stefano Bagnara commented on MAVENUPLOAD-2711: -- Hi Juven, I'm not the author of that projects, so I'm not sure that the instructions you pointed me are ok. I'm an ASF committer and our maven2 project have dependencies that cannot be found on any existing m2 repository. The few times it happened in past we simply created issues here and it was easy. I guess I will have to check with ASF people how we are supposed to deal with 3rd party stuff now (I understand I can't argue with Sonatype or Codehaus if mantaining an ASF project is getting more difficult with time). I created 3 new issues here with the 3 artifacts including sources/javadocs hoping this can still be done this way. > dnsjava 2.0.8 > - > > Key: MAVENUPLOAD-2711 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2711 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Stefano Bagnara >Assignee: Juven Xu > > dnsjava 2.0.8 > I'm not the author of dnsjava, but I already uploaded the 2.0.1 to 2.0.6 > bundles, so here we are with newer bundles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2763) dnsjava 2.0.8
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefano Bagnara closed MAVENUPLOAD-2763. Resolution: Won't Fix Weird thing. You rejected MAVENUPLOAD-2711 so I opened this (MAVENUPLOAD-2763) but now I see that here: http://repo1.maven.org/maven2/dnsjava/dnsjava/2.0.8/ on Feb 24th you also deployed the bundle (despite the original issue was rejected). Closing this one. Thank you. > dnsjava 2.0.8 > - > > Key: MAVENUPLOAD-2763 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2763 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Stefano Bagnara > > dnsjava 2.0.8 > I'm not the author of dnsjava, but I already uploaded the 2.0.1 to 2.0.6 > bundles, so here we are with newer bundles. > This is built from original 2.0.8 sources, just added my own pom, built and > bundled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2711) dnsjava 2.0.8
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219061#action_219061 ] Stefano Bagnara commented on MAVENUPLOAD-2711: -- Weird thing. You rejected this (MAVENUPLOAD-2711) so I opened MAVENUPLOAD-2763 but now I see that here: http://repo1.maven.org/maven2/dnsjava/dnsjava/2.0.8/ on Feb 24th you also deployed the bundle (despite this issue has been rejected). Thank you. > dnsjava 2.0.8 > - > > Key: MAVENUPLOAD-2711 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2711 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Stefano Bagnara >Assignee: Juven Xu > > dnsjava 2.0.8 > I'm not the author of dnsjava, but I already uploaded the 2.0.1 to 2.0.6 > bundles, so here we are with newer bundles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2764) dnsjnio 1.0.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefano Bagnara closed MAVENUPLOAD-2764. Resolution: Won't Fix Weird thing. You rejected this (MAVENUPLOAD-2712) so I opened MAVENUPLOAD-2764 but now I see that here: http://repo1.maven.org/maven2/uk/nominet/dnsjnio/1.0.3/ on Feb 24th you also deployed the bundle (despite this issue has been rejected). Thank you. > dnsjnio 1.0.3 > - > > Key: MAVENUPLOAD-2764 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2764 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Stefano Bagnara > > dnsjnio 1.0.3 > I'm not the author of dnsjnio (even if I'm a contributor). > This is built from original sources, just added my own pom, built and bundled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2713) jvyaml 0.2.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219064#action_219064 ] Stefano Bagnara commented on MAVENUPLOAD-2713: -- Weird thing. You rejected this (MAVENUPLOAD-2713) so I opened MAVENUPLOAD-2764 but now I see that here: http://repo1.maven.org/maven2/uk/nominet/dnsjnio/1.0.3/ on Feb 24th you also deployed the bundle (despite this issue has been rejected). Thank you. > jvyaml 0.2.1 > > > Key: MAVENUPLOAD-2713 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2713 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Stefano Bagnara >Assignee: Juven Xu > > jvyaml 0.2.1 > I'm not the author of jvyaml. It is a dependency for an ASF project (Apache > JAMES jSPF) and I'm uploading the dependencies that are not in central, yet) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2712) dnsjnio 1.0.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219066#action_219066 ] Stefano Bagnara commented on MAVENUPLOAD-2712: -- Weird thing. You rejected this (MAVENUPLOAD-2712) so I opened MAVENUPLOAD-2764 but now I see that here: http://repo1.maven.org/maven2/uk/nominet/dnsjnio/1.0.3/ on Feb 24th you also deployed the bundle (despite this issue has been rejected). Thank you. > dnsjnio 1.0.3 > - > > Key: MAVENUPLOAD-2712 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2712 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Stefano Bagnara >Assignee: Juven Xu > > dnsjnio 1.0.3 > I'm not the author of dnsjnio (even if I'm a contributor). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2765) jvyaml 0.2.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefano Bagnara closed MAVENUPLOAD-2765. Resolution: Fixed Somehow the file is there now http://repo1.maven.org/maven2/net/java/dev/jvyaml/0.2.1/ and with an old date (I was almost sure it wasn't there.. maybe some rsync from the java.net repo fixed it) > jvyaml 0.2.1 > > > Key: MAVENUPLOAD-2765 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2765 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Stefano Bagnara > > jvyaml 0.2.1 > I'm not the author of jvyaml. It is a dependency for an ASF project (Apache > JAMES jSPF) and I'm uploading the dependencies that are not in central, yet) > This is built from original sources, just added my own pom, built and bundled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-37) Dependency report fails on system-scope dependencies
[ http://jira.codehaus.org/browse/MPIR-37?page=comments#action_71104 ]
Stefano Bagnara commented on MPIR-37:
-
This is not fixed in 2.0.4!
It should be reopened!
> Dependency report fails on system-scope dependencies
>
>
> Key: MPIR-37
> URL: http://jira.codehaus.org/browse/MPIR-37
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Helge Olav Aarstein
> Assigned To: Brett Porter
>
> Dependency to local weblogic.jar causes the dependency project report to
> fail.
> Error caused by following dependency setting in the pom.xml -file:
>
> com.bea.weblogic
> webservices
> 9.1.0
> system
> ${wls910.server.lib}/weblogic.jar
>
> If I put weblogic.jar into the repository the dependency report seems to work
> fine, but then my compile fails (but that's a completely different story and
> should not affect this problem).
> Stacktrace follows:
> [INFO] Generate "Dependencies" report.
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:82)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:386)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:351)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.getMavenProjectFromRepository(DependenciesReport.java:362)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.renderBody(DependenciesReport.java:242)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
> at
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:157)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98)
> at
> org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.java:802)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:47
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-289) Deployed site xml does not preserve license header (and much more)
Deployed site xml does not preserve license header (and much more) -- Key: MRELEASE-289 URL: http://jira.codehaus.org/browse/MRELEASE-289 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-6, 2.0-beta-5 Reporter: Stefano Bagnara I just noticed that during release/deployment we lose our site.xml license header! (furthermore it changes the encoding, loose the declared namespaces, and many other informations written in the site.xml) I don't know what is the plugin that rewrites the site.xml . I wrote to [EMAIL PROTECTED] list but received no answer/pointer, so I open the issue in the release plugin (I guess this is the one writing the release poms/xmls descriptors) Here is our original site.xml: http://svn.apache.org/repos/asf/james/project/tags/james-project-1.2/src/site/site.xml And here how it's been deployed: http://people.apache.org/~norman/staging-repository/org/apache/james/james-project/1.2/james-project-1.2-site.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-223) Generated pom.xml has invalid chars (does not correctly handle xml entities)
[
http://jira.codehaus.org/browse/MRELEASE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135953#action_135953
]
Stefano Bagnara commented on MRELEASE-223:
--
I'm not sure I understand the "specify your desired charset in the XML
declartion" suggestion:
How can I use chinese and sweden chars to specify the name of a sweden
committer and a chinese committer working on the project team ?
> Generated pom.xml has invalid chars (does not correctly handle xml entities)
>
>
> Key: MRELEASE-223
> URL: http://jira.codehaus.org/browse/MRELEASE-223
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-4
>Reporter: Stefano Bagnara
>Assignee: Benjamin Bentmann
> Fix For: 2.0-beta-8
>
>
> In our main pom we have this entry:
> {code:xml}
>
> hilmer
> Søren Hilmer
> sh at widetrail.dk
>
>
> Developer
>
>
> {code}
> in the resulting pom.xml the entity is converted to the real value, and the
> next time I try to use the pom it results in invalid output.
> {code:xml}
>
> hilmer
> Søren Hilmer
> sh at widetrail.dk
>
>
> Developer
>
>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-330) LICENSE/NOTICE modification/generation based on included dependencies
LICENSE/NOTICE modification/generation based on included dependencies - Key: MASSEMBLY-330 URL: http://jira.codehaus.org/browse/MASSEMBLY-330 Project: Maven 2.x Assembly Plugin Issue Type: New Feature Affects Versions: 2.2-beta-2 Reporter: Stefano Bagnara I create jar, javadoc-jar and sources-jar using maven jar plugin. The maven remote resources plugin together with the apache-jar-resource-bundle allow me to have a good LICENSE/NOTICE file for that jars. The problem is that I also have a src\assemble\src.xml and src\assemble\bin.xml files to create a sources + compile/test/runtime dependencies (all of them) zip file and a binary + runtime dependencies zip file. Assembly plugin make a grea job in allowing me using this for the binary dependencies: dependencySets> /lib/ runtime For the src distribution I instead copy files manually not using the dependencies (because I need them in the same structure I already have), and this is another issue, but let's fix one issue at a time. currently I put a LICENSE/NOTICE files in the zips by adding this: target/maven-shared-archive-resources/META-INF/ / NOTICE LICENSE But they are now wrong for a binary distribution including the runtime dependencies. It would be cool to have the assembly plugin automatically manage this (I don't even know how) by altering (or interacting with the remote resources plugin) to add snippets related to the included dependencies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-330) LICENSE/NOTICE modification/generation based on included dependencies
[ http://jira.codehaus.org/browse/MASSEMBLY-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138996#action_138996 ] Stefano Bagnara commented on MASSEMBLY-330: --- Daniel, great point! It would be cool if this could be someway be managed automatically by a collaboration between the remote-resources-plugin and the assembly-plugin. I think this would give us an very good out-of-the-box solution! I don't know maven so I don't know if it is easy/feasible for 2 plugins to collaborate for a given result, but this would be cool for sure... Maybe the assembly plugin could invoke the remote-resources-plugin with configurations given by his assembly descriptor? > LICENSE/NOTICE modification/generation based on included dependencies > - > > Key: MASSEMBLY-330 > URL: http://jira.codehaus.org/browse/MASSEMBLY-330 > Project: Maven 2.x Assembly Plugin > Issue Type: New Feature >Affects Versions: 2.2-beta-2 >Reporter: Stefano Bagnara > > I create jar, javadoc-jar and sources-jar using maven jar plugin. > The maven remote resources plugin together with the > apache-jar-resource-bundle allow me to have a good LICENSE/NOTICE file for > that jars. > The problem is that I also have a src\assemble\src.xml and > src\assemble\bin.xml files to create a sources + compile/test/runtime > dependencies (all of them) zip file and a binary + runtime dependencies zip > file. > Assembly plugin make a grea job in allowing me using this for the binary > dependencies: > dependencySets> > > /lib/ > runtime > > > For the src distribution I instead copy files manually not using the > dependencies (because I need them in the same structure I already have), and > this is another issue, but let's fix one issue at a time. > currently I put a LICENSE/NOTICE files in the zips by adding this: > > target/maven-shared-archive-resources/META-INF/ > / > > NOTICE > LICENSE > > > But they are now wrong for a binary distribution including the runtime > dependencies. > It would be cool to have the assembly plugin automatically manage this (I > don't even know how) by altering (or interacting with the remote resources > plugin) to add snippets related to the included dependencies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEP-174) mvn dependency:resolve-plugins look for plugins in standard dependency repositories
mvn dependency:resolve-plugins look for plugins in standard dependency repositories --- Key: MDEP-174 URL: http://jira.codehaus.org/browse/MDEP-174 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: resolve-plugins Affects Versions: 2.0 Reporter: Stefano Bagnara Assignee: Brian Fox I have a very strict list containing only my direct dependencies. A standard build correctly download plugins from other repositories and the project dependencies from my repository. If I use dependency:resolve the artifact from my repository is copied to the local repository. If I use dependency:resolve-plugins it looks in my repository instead of the plugin repository <--- WRONG. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-234) Maven skin / version as plugin parameters
[
http://jira.codehaus.org/browse/MSITE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143361#action_143361
]
Stefano Bagnara commented on MSITE-234:
---
Dennis: I'm not an m2 guru, but that's what I expected. It's the same of having
a dependency between the 2 modules. Currently the "direct" dependency would be
updated while the skin dependency is ignored.
> Maven skin / version as plugin parameters
> -
>
> Key: MSITE-234
> URL: http://jira.codehaus.org/browse/MSITE-234
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
>Affects Versions: 2.0-beta-5
>Reporter: Stefano Bagnara
>
> I have an m2 reactor project where one of the modules is the skin used
> by one of the other modules (and every of its children).
> {noformat}
> root
> |- maven-skin
> '- module1 (using maven-skin)
> {noformat}
> The problem is that module1 declare the skin in its site.xml file and
> this way the version is not updated when I use the release:prepare to
> update my poms.
> So I checked the site plugin searching for a way to declare the skin in
> the plugin configuration instead of the site.xml descriptor but there is
> no such option.
> I think that a good solution would be to use something like the remote
> resource plugin (used for LICENSE/NOTICE) also for the skin declaration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-347) Site plugin install the wrong site.xml descriptor in local repository since 2.0-beta-6
Site plugin install the wrong site.xml descriptor in local repository since 2.0-beta-6 -- Key: MSITE-347 URL: http://jira.codehaus.org/browse/MSITE-347 Project: Maven 2.x Site Plugin Issue Type: Bug Components: multi module Affects Versions: 2.0-beta-7, 2.0-beta-6 Reporter: Stefano Bagnara Attachments: site-plugin-test.zip I just tryed to build an old project and I found that it was no more working. After investigating this I see that now maven ends up installing a wrong site.xml (the one from the parent) instead of the right one. I attach a simple multimodule project to reproduce this issue. If you run an "mvn install site" from the root you see that in the com.example/project/1.0-SNAPSHOT folder the project-1.0-SNAPSHOT-site.xml is instead the site.xml for the "parent" artifact and not the one that I have in the "project" artifact. This seems a critical issue. Try uncommenting the pluginManagement where I declare site 2.0-beta-5 and everything will work fine! I don't know how to setup the environment to be able to create an it test to submit to the site plugin developers, hope the test is good enough. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-348) bannerLeft not correctly overriden from the inherited one since 2.0-beta-6 in a reactor build
bannerLeft not correctly overriden from the inherited one since 2.0-beta-6 in a reactor build - Key: MSITE-348 URL: http://jira.codehaus.org/browse/MSITE-348 Project: Maven 2.x Site Plugin Issue Type: Bug Components: multi module Affects Versions: 2.0-beta-7, 2.0-beta-6 Reporter: Stefano Bagnara Attachments: site-plugin-test.zip I just tryed to build an old project and I found that it was no more working. After investigating this I see that now maven ends up installing a wrong site.xml (the one from the parent) instead of the right one. I attach a simple multimodule project to reproduce this issue. If you run an "mvn install site" from the root you see that in the If you see in site-plugin-test/project/module/target/site/index.html it references the banner declared in site-plugin-test/src/site/site.xml and not the one from site-plugin-test/project/module/src/site/site.xml. Try uncommenting the pluginManagement where I declare site 2.0-beta-5 and everything will work fine! I don't know how to setup the environment to be able to create an it test to submit to the site plugin developers, hope the test is good enough. Probably this is related to MSITE-347 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-348) Configuration option to define a different extension.
Configuration option to define a different extension. - Key: MASSEMBLY-348 URL: http://jira.codehaus.org/browse/MASSEMBLY-348 Project: Maven 2.x Assembly Plugin Issue Type: Improvement Affects Versions: 2.2-beta-2 Reporter: Stefano Bagnara I have to create a "Avalon Phoenix" SAR file. It is a zip/jar, with a different extension. The assembly plugin allow me to create a zip or a jar, let me choose the name, but I cannot alter the extension. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MASSEMBLY-348) Configuration option to define a different extension.
[ http://jira.codehaus.org/browse/MASSEMBLY-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefano Bagnara updated MASSEMBLY-348: -- Attachment: MASSEMBLY-348.diff This upgrade the mdo version to 1.1.1 adding the property to the assmebly descriptor. During the read it throw an error if customExtension is used in combination with multiple formats. I added 2 test cases for the added property and tested it for Apache JAMES Server and it works fine. > Configuration option to define a different extension. > - > > Key: MASSEMBLY-348 > URL: http://jira.codehaus.org/browse/MASSEMBLY-348 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.2-beta-2 >Reporter: Stefano Bagnara > Attachments: MASSEMBLY-348.diff > > > I have to create a "Avalon Phoenix" SAR file. It is a zip/jar, with a > different extension. > The assembly plugin allow me to create a zip or a jar, let me choose the > name, but I cannot alter the extension. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-348) Configuration option to define a different extension.
[
http://jira.codehaus.org/browse/MASSEMBLY-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145894#action_145894
]
Stefano Bagnara commented on MASSEMBLY-348:
---
@John: I guess this is the META-INF/plexus/components.xml file with something
like this:
{code:xml}
org.codehaus.plexus.archiver.Archiver
sar
org.codehaus.plexus.archiver.bzip2.JarArchiver
per-lookup
org.codehaus.plexus.archiver.UnArchiver
sar
org.codehaus.plexus.archiver.zip.ZipUnArchiver
per-lookup
org.codehaus.plexus.components.io.resources.PlexusIoResourceCollection
sar
org.codehaus.plexus.components.io.resources.PlexusIoZipFileResourceCollection
per-lookup
{code}
will this work also for already defined extensions? (e.g: use the ziparchiver
to create a file with a war extension)
> Configuration option to define a different extension.
> -
>
> Key: MASSEMBLY-348
> URL: http://jira.codehaus.org/browse/MASSEMBLY-348
> Project: Maven 2.x Assembly Plugin
> Issue Type: Improvement
>Affects Versions: 2.2-beta-2
>Reporter: Stefano Bagnara
> Fix For: 2.2-beta-3
>
> Attachments: MASSEMBLY-348.diff
>
>
> I have to create a "Avalon Phoenix" SAR file. It is a zip/jar, with a
> different extension.
> The assembly plugin allow me to create a zip or a jar, let me choose the
> name, but I cannot alter the extension.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MASSEMBLY-348) Configuration option to define a different extension.
[ http://jira.codehaus.org/browse/MASSEMBLY-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefano Bagnara updated MASSEMBLY-348: -- Attachment: plexus-archiver-sar-support-1.0.jar The "sar" enabler I'm trying... > Configuration option to define a different extension. > - > > Key: MASSEMBLY-348 > URL: http://jira.codehaus.org/browse/MASSEMBLY-348 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.2-beta-2 >Reporter: Stefano Bagnara > Fix For: 2.2-beta-3 > > Attachments: MASSEMBLY-348.diff, plexus-archiver-sar-support-1.0.jar > > > I have to create a "Avalon Phoenix" SAR file. It is a zip/jar, with a > different extension. > The assembly plugin allow me to create a zip or a jar, let me choose the > name, but I cannot alter the extension. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-348) Configuration option to define a different extension.
[
http://jira.codehaus.org/browse/MASSEMBLY-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147587#action_147587
]
Stefano Bagnara commented on MASSEMBLY-348:
---
I added the components.xml as described above in a jar and added it to my
assembly configuration:
{code}
maven-assembly-plugin
2.2-beta-2
org.apache.james
plexus-archiver-sar-support
1.0
{code}
When I run my "package" for a "sar" format I get this output:
{code}
[INFO] [jar:jar]
[INFO] [jar:test-jar {execution: default}]
[INFO] [assembly:attached {execution: make-my-assembly}]
-
this realm =
app0.child-container[org.apache.maven.plugins:maven-assembly-plugin]
urls[0] =
file:/C:/Users/bago/.m2/repository/org/apache/maven/plugins/maven-assembly-plugin/2.2-beta-2/maven-assembly-plugin-2.2-beta-2.jar
urls[1] =
file:/C:/Users/bago/.m2/repository/org/apache/james/plexus-archiver-sar-support/1.0/plexus-archiver-sar-support-1.0.jar
urls[2] =
file:/C:/Users/bago/.m2/repository/aspectj/aspectjrt/1.5.3/aspectjrt-1.5.3.jar
urls[3] =
file:/C:/Users/bago/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-10/plexus-archiver-1.0-alpha-10.jar
urls[4] =
file:/C:/Users/bago/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar
urls[5] =
file:/C:/Users/bago/.m2/repository/org/codehaus/plexus/plexus-io/1.0-alpha-2/plexus-io-1.0-alpha-2.jar
urls[6] =
file:/C:/Users/bago/.m2/repository/org/apache/maven/shared/file-management/1.1/file-management-1.1.jar
urls[7] =
file:/C:/Users/bago/.m2/repository/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.jar
urls[8] =
file:/C:/Users/bago/.m2/repository/org/codehaus/plexus/plexus-active-collections/1.0-beta-2/plexus-active-collections-1.0-beta-2.jar
urls[9] =
file:/C:/Users/bago/.m2/repository/org/apache/maven/maven-archiver/2.2/maven-archiver-2.2.jar
urls[10] =
file:/C:/Users/bago/.m2/repository/org/apache/maven/shared/maven-repository-builder/1.0-alpha-2/maven-repository-builder-1.0-alpha-2.jar
urls[11] =
file:/C:/Users/bago/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/1.0/maven-common-artifact-filters-1.0.jar
urls[12] =
file:/C:/Users/bago/.m2/repository/org/apache/maven/shared/maven-plugin-testing-harness/1.1/maven-plugin-testing-harness-1.1.jar
Number of imports: 6
import: [EMAIL PROTECTED]
import: [EMAIL PROTECTED]
import: [EMAIL PROTECTED]
import: [EMAIL PROTECTED]
import: [EMAIL PROTECTED]
import: [EMAIL PROTECTED]
this realm = plexus.core
urls[0] = file:/c:/Program Files/Java/maven/bin/../lib/maven-2.0.9-uber.jar
Number of imports: 6
import: [EMAIL PROTECTED]
import: [EMAIL PROTECTED]
import: [EMAIL PROTECTED]
import: [EMAIL PROTECTED]
import: [EMAIL PROTECTED]
import: [EMAIL PROTECTED]
-
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to create assembly: Unable to obtain archiver for extension 'sar'
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create
assembly: Unable to obtain archiver for extension 'sar'
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.m
[jira] Updated: (MASSEMBLY-348) Configuration option to define a different extension.
[ http://jira.codehaus.org/browse/MASSEMBLY-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefano Bagnara updated MASSEMBLY-348: -- Attachment: plexus-archiver-sar-support-1.0.jar Fixed file > Configuration option to define a different extension. > - > > Key: MASSEMBLY-348 > URL: http://jira.codehaus.org/browse/MASSEMBLY-348 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.2-beta-2 >Reporter: Stefano Bagnara > Fix For: 2.2-beta-3 > > Attachments: MASSEMBLY-348.diff, plexus-archiver-sar-support-1.0.jar, > plexus-archiver-sar-support-1.0.jar > > > I have to create a "Avalon Phoenix" SAR file. It is a zip/jar, with a > different extension. > The assembly plugin allow me to create a zip or a jar, let me choose the > name, but I cannot alter the extension. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-348) Configuration option to define a different extension.
[ http://jira.codehaus.org/browse/MASSEMBLY-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147592#action_147592 ] Stefano Bagnara commented on MASSEMBLY-348: --- Here again. The issue was that I had a bad declaration in my components.xml (I was declaring org.codehaus.plexus.archiver.bzip2.JarArchiver as the implementation and it does not exist.. it must have been a typo..). I fixed it and now I'm able to build sar files! I've attached the fixed file so anyone else reading this issue later will have a good example. One last question: is there a way to declare a new plexus component directly in my module sources instead of having to create a jar for this declaration? > Configuration option to define a different extension. > - > > Key: MASSEMBLY-348 > URL: http://jira.codehaus.org/browse/MASSEMBLY-348 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.2-beta-2 >Reporter: Stefano Bagnara > Fix For: 2.2-beta-3 > > Attachments: MASSEMBLY-348.diff, plexus-archiver-sar-support-1.0.jar, > plexus-archiver-sar-support-1.0.jar > > > I have to create a "Avalon Phoenix" SAR file. It is a zip/jar, with a > different extension. > The assembly plugin allow me to create a zip or a jar, let me choose the > name, but I cannot alter the extension. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2896) ${basedir} used in a repository url does not work for parent pom lookup
${basedir} used in a repository url does not work for parent pom lookup
---
Key: MNG-2896
URL: http://jira.codehaus.org/browse/MNG-2896
Project: Maven 2
Issue Type: Wish
Components: POM
Affects Versions: 2.0.5
Reporter: Stefano Bagnara
I use something like this to store locally the dependencies.
-
parent-james-stage-m1
James stage repository
file://${basedir}/stage
legacy
true
ignore
true
ignore
Everything works fine but the parent resolution: my main pom.xml has a parent
and it is not looked up in this repository.
Well, it is lookedup, but ${basedir} is not expanded and this way the lookup
does not work.
If I replace the ${basedir} with my full path everything works fine, but I
cannot obviously do that as the local repository is part of the svn tree (by
our choice to not use remote repositories).
Furthermore: is there a variable to be used instead of ${basedir} that always
reference to its own pom.xml folder? I ask this because I have multiple modules
inside this project and I had to add another repository to this pom using
file://${basedir}/../stage (notice the ..) so that submodules will use the same
repository for the lookups, but this sound like an hack.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-1958) we need a var that always points to the root direcotry in multi module builds
[
http://jira.codehaus.org/browse/MNG-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90975
]
Stefano Bagnara commented on MNG-1958:
--
This is somehow related to MNG-2896
Both are needed to make full use of a project-local repository-like folder.
> we need a var that always points to the root direcotry in multi module builds
> -
>
> Key: MNG-1958
> URL: http://jira.codehaus.org/browse/MNG-1958
> Project: Maven 2
> Issue Type: Improvement
>Reporter: Mark Proctor
> Fix For: 2.1.x
>
>
> ${basedir} always points to the local module. There are cases, when having a
> local relative repository, when it would be usefull to have a var that always
> pointed to the root project, ${rootdir}.
> In such a case you may want to think of having the names ${rootdir}
> ${moduledir}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-222) Wrong default tag name when used in a reactor environment
Wrong default tag name when used in a reactor environment - Key: MRELEASE-222 URL: http://jira.codehaus.org/browse/MRELEASE-222 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-4 Reporter: Stefano Bagnara Priority: Critical In JAMES project we have this structure (): root (james-project) - maven-skin (maven-skin) - server (james-server-root) - 2.2.0 (james-server-site-2-2-0) All of them are in the org.apache.james groupId. The main project have a site.xml declaring "maven-skin" as its own skin. You can look at the real current poms here: http://svn.apache.org/viewvc/james/project/trunk/pom.xml?revision=524429&view=markup http://svn.apache.org/viewvc/james/project/trunk/maven-skin/pom.xml?revision=451625&view=markup http://svn.apache.org/viewvc/james/project/trunk/server/pom.xml?revision=475214&view=markup http://svn.apache.org/viewvc/james/project/trunk/server/2.2.0/pom.xml?revision=451625&view=markup When I try to run "mvn release:prepare -DdryRun=true" it ask me the following: - [INFO] Checking dependencies and plugins for snapshots ... What is the release version for "JAMES Skin"? (org.apache.james:maven-skin) 1.1: : What is the release version for "Apache JAMES Project"? (org.apache.james:james-project) 1.1: : What is the release version for "JAMES Server"? (org.apache.james:james-server-root) 1.0: : What is the release version for "JAMES Server 2.2.0 Documentation"? (org.apache.james:james-server-site-2-2-0) 1.0: : What is SCM release tag or label for "JAMES Skin"? (org.apache.james:maven-skin) maven-skin-1.1: : What is the new development version for "JAMES Skin"? (org.apache.james:maven-skin) 1.2-SNAPSHOT: : What is the new development version for "Apache JAMES Project"? (org.apache.james:james-project) 1.2-SNAPSHOT: : What is the new development version for "JAMES Server"? (org.apache.james:james-server-root) 1.1-SNAPSHOT: : What is the new development version for "JAMES Server 2.2.0 Documentation"? (org.apache.james:james-server-site-2-2-0) 1.1-SNAPSHOT: : - Why do it asks me the SCM release tag for "JAMES Skin" and not for James project? Why my james-project pom.xml was: http://svn.apache.org/viewvc/james/project/trunk and in the pom.xml.tag I find http://svn.apache.org/viewvc/james/project/tags/maven-skin-1.1 The urls for the sub modules pom.xml.tag are instead correct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-223) Generated pom.xml has invalid chars (does not correctly handle xml entities)
Generated pom.xml has invalid chars (does not correctly handle xml entities)
Key: MRELEASE-223
URL: http://jira.codehaus.org/browse/MRELEASE-223
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-4
Reporter: Stefano Bagnara
In our main pom we have this entry:
{code:xml}
hilmer
Søren Hilmer
sh at widetrail.dk
Developer
{code}
in the resulting pom.xml the entity is converted to the real value, and the
next time I try to use the pom it results in invalid output.
{code:xml}
hilmer
Søren Hilmer
sh at widetrail.dk
Developer
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-223) Generated pom.xml has invalid chars (does not correctly handle xml entities)
[
http://jira.codehaus.org/browse/MRELEASE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94261
]
Stefano Bagnara commented on MRELEASE-223:
--
Well, I used the xml entities so to not have to use the charset.
But when it build the output pom.xml it should take care to correctly escape
data.
The problem is not my editor, but the mvn site plugin.
The website created after the release plugin "mungled" my pom.xml does no more
contain the correct char.
So this is all about maven: I don't use third party editors or anything else.
Just mvn release and mvn site.
I don't know how to test the 2.0-beta5-SNAPSHOT plugin instead of the 2.0-beta4
automatically used by mvn.
> Generated pom.xml has invalid chars (does not correctly handle xml entities)
>
>
> Key: MRELEASE-223
> URL: http://jira.codehaus.org/browse/MRELEASE-223
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-4
>Reporter: Stefano Bagnara
>
> In our main pom we have this entry:
> {code:xml}
>
> hilmer
> Søren Hilmer
> sh at widetrail.dk
>
>
> Developer
>
>
> {code}
> in the resulting pom.xml the entity is converted to the real value, and the
> next time I try to use the pom it results in invalid output.
> {code:xml}
>
> hilmer
> Søren Hilmer
> sh at widetrail.dk
>
>
> Developer
>
>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-228) Try and unable to resolve org.apache.maven.skins:maven-default-skin:jar:RELEASE when another skin is specified
Try and unable to resolve org.apache.maven.skins:maven-default-skin:jar:RELEASE
when another skin is specified
--
Key: MSITE-228
URL: http://jira.codehaus.org/browse/MSITE-228
Project: Maven 2.x Site Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-5
Reporter: Stefano Bagnara
1) My project does not use external repositories for dependencies but only for
plugins.
2) For dependencies I have a "stage" folder that is a "legacy structured" local
repository I reference this way:
{code}
local-james-stage-m1
Local James stage repository
file://c:/lab/void/projects/server-trunk-modular/stage
legacy
true
ignore
true
ignore
{code}
3) in my site.xml I have this:
{code}
org.apache.james
maven-skin
1.1-SNAPSHOT
{code}
4) and in my local stage repository I have the
org.apache.james/poms/maven-skin-1.1-SNAPSHOT.pom and
org.apache.james/jars/maven-skin-1.1-SNAPSHOT.jar files.
If I try to build the project, package it, run tests and everything else it
works, but when I try to build "mvn site" if fails with this error:
{code}
[DEBUG] maven-default-skin: using locally installed snapshot
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] The skin does not exist: Unable to determine the release version
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin \
-Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
org.apache.maven.skins:maven-default-skin:jar:RELEASE
[INFO]
[DEBUG] Trace
org.apache.maven.BuildFailureException: The skin does not exist: Unable to
determine the release version
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin \
-Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
org.apache.maven.skins:maven-default-skin:jar:RELEASE
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoFailureException: The skin does not
exist: Unable to determine the release version
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin \
-Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
org.apache.maven.skins:maven-default-skin:jar:RELEASE
at
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getSkinArtifactFile(AbstractSiteRenderingMojo.java:372)
at
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:442)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:108)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.Defaul
[jira] Commented: (MSITE-228) Try and unable to resolve org.apache.maven.skins:maven-default-skin:jar:RELEASE when another skin is specified
[
http://jira.codehaus.org/browse/MSITE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94414
]
Stefano Bagnara commented on MSITE-228:
---
I found a workaround for this.
Let me explain my full scenario and how I fixed it so maybe it will more clear
to you where the bug belongs.
My pom structure is:
{code}
james-parent
|- maven-skin
'- james-root
|- james-server-root
| |- james-server-2.2.0
| '- james-server:3.0-SNAPSHOT
| |- module1
| |- module2
| '
|- jspf
'.
{code}
The site.xml for james-root is the one specifying the use of the maven-skin as
default skin for the project.
I cannot add this directive to james-parent because james-parent is also the
parent for maven-skin and it would be a recursive dependency.
I get the error above while trying to build "james-server:3.0-SNAPSHOT".
Adding a site.xml to james-parent and specifying:
{code}
org.apache.maven.skins
maven-default-skin
1.0
{code}
and then placing in my local "stage" folder the jar and pom for the default
skin made the trick.
Probably the bug is that maven is searching for the skin even if the parent
artifacts do not need a site generation (they didn't have a site.xml at all).
I don't like too much having to place the maven-default-skin jar (that I don't
use) in the james-server:3.0-SNAPSHOT dependencies stage repository, but I can
live with it as a workaround.
I hope this give you enough information for fixing this issue.
> Try and unable to resolve
> org.apache.maven.skins:maven-default-skin:jar:RELEASE when another skin is
> specified
> --
>
> Key: MSITE-228
> URL: http://jira.codehaus.org/browse/MSITE-228
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-5
>Reporter: Stefano Bagnara
>
> 1) My project does not use external repositories for dependencies but only
> for plugins.
> 2) For dependencies I have a "stage" folder that is a "legacy structured"
> local repository I reference this way:
> {code}
> local-james-stage-m1
> Local James stage repository
> file://c:/lab/void/projects/server-trunk-modular/stage
> legacy
>
> true
> ignore
>
>
> true
> ignore
>
> {code}
> 3) in my site.xml I have this:
> {code}
> org.apache.james
> maven-skin
> 1.1-SNAPSHOT
> {code}
> 4) and in my local stage repository I have the
> org.apache.james/poms/maven-skin-1.1-SNAPSHOT.pom and
> org.apache.james/jars/maven-skin-1.1-SNAPSHOT.jar files.
> If I try to build the project, package it, run tests and everything else it
> works, but when I try to build "mvn site" if fails with this error:
> {code}
> [DEBUG] maven-default-skin: using locally installed snapshot
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] The skin does not exist: Unable to determine the release version
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.skins
> -DartifactId=maven-default-skin \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
> org.apache.maven.skins:maven-default-skin:jar:RELEASE
> [INFO]
>
> [DEBUG] Trace
> org.apache.maven.BuildFailureException: The skin does not exist: Unable to
> determine the release version
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.skins
> -DartifactId=maven-default-skin \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
> org.apache.maven.skins:maven-default-skin:jar:RELEASE
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(De
[jira] Created: (MNG-2969) Unable to exclude a dependency from a needed plugin
Unable to exclude a dependency from a needed plugin --- Key: MNG-2969 URL: http://jira.codehaus.org/browse/MNG-2969 Project: Maven 2 Issue Type: Bug Components: Dependencies Affects Versions: 2.0.6 Reporter: Stefano Bagnara When we add a "standard" dependency we can tune its dependency list using the exclusions directive. THis is not possible with plugins. Let's say I add javacc-maven-plugin to my build/plugins section and the plugin declared in its pom: org.codehaus.plexus plexus-utils 1.0.4 And I know that this dependency is a compile dependency and I won't need it, how can I tune my plugin inclusion so to not download plexus-utils? in I can add new dependencies to plugin (WHY is this needed?) but I cannot exclude existing dependencies: isn't this a bug? I can add a new dependency to the plugin and add exclusions for this new dependency but I cannot add an exclusion for the top-level dependencies. Am I missing something? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2477) Implement repository security improvements for verification of downloaded artifacts
[ http://jira.codehaus.org/browse/MNG-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94418 ] Stefano Bagnara commented on MNG-2477: -- Now that the pgp signing plugin allow us to automatically gpg sign deployed artifact, isn't it possible to add the possibility to specify that a given dependency must be signed and that you expect a given fingerprint for that artifact? We use only local folders for direct dependencies to ensure that our final package include only "verified" jars, but I would like also to ensure that the build is done using the very plugins I chose and I want to be able to check their signatures. A much less secure but still a step forward would be to be able to specify the md5 in addition to version when declaring the dependency, so that we can check that we are using the same artifact. (althought md5 is cracked and this won't be much secure) > Implement repository security improvements for verification of downloaded > artifacts > --- > > Key: MNG-2477 > URL: http://jira.codehaus.org/browse/MNG-2477 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts, Artifacts and Repositories, Dependencies, > Deployment, Design, Patterns & Best Practices, Repositories >Reporter: Brett Porter > > http://docs.codehaus.org/display/MAVEN/Repository+Security+Improvements -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2969) Unable to exclude a dependency from a needed plugin
[
http://jira.codehaus.org/browse/MNG-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94583
]
Stefano Bagnara commented on MNG-2969:
--
Brian: ok, but Why are you allowed to add new dependencies to a plugin via
dependencyManager? and why you can do exclusions for standard dependencies? If
we trust third party authors and original dependencies then we wouldn't need
the depependency/exclusion system at all.
About the specific issue one of our PMC members is concerned about security and
would like to build the project fully offline and without using artifact
previously downloaded to the repository. We do this by declaring a "stage"
repository that have a "file://${basedir}/stage" url and placing there every
dependency we have.
Unfortunately some plugin have plenty of dependencies and sometimes they forgot
to declare that a dependency is only needed at compile time, so the list of
jars needed is almost double that the jars actually being used.
> Unable to exclude a dependency from a needed plugin
> ---
>
> Key: MNG-2969
> URL: http://jira.codehaus.org/browse/MNG-2969
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 2.0.6
>Reporter: Stefano Bagnara
>
> When we add a "standard" dependency we can tune its dependency list using the
> exclusions directive.
> THis is not possible with plugins.
> Let's say I add javacc-maven-plugin to my build/plugins section and the
> plugin declared in its pom:
>
> org.codehaus.plexus
> plexus-utils
> 1.0.4
>
> And I know that this dependency is a compile dependency and I won't need it,
> how can I tune my plugin inclusion so to not download plexus-utils?
> in I can add new dependencies to plugin (WHY is this
> needed?) but I cannot exclude existing dependencies: isn't this a bug?
> I can add a new dependency to the plugin and add exclusions for this new
> dependency but I cannot add an exclusion for the top-level dependencies.
> Am I missing something?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2969) Unable to exclude a dependency from a needed plugin
[ http://jira.codehaus.org/browse/MNG-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94594 ] Stefano Bagnara commented on MNG-2969: -- Currently after I built the project I end up with 5 different version of plexus-utils in my repository: 1.0.4, 1.0.5, 1.1, 1.2, 1.3. It would be cool if I could override the default dependency and define what exactly will be used (by limiting jar prolification). But the main issue is with "non-marked-as-optional" dependencies. I think this is the same as for transitive dependencies for standard/non-plugin dependencies (the same considerations applies). E.g: plexus-utils 1.0.4 has only junit in test scope. 1.0.5 has classwordls,1.1+ have no dependencies. I think it would be cool to have a clear overview about why I have a specific plugin dependency (like I have for standard dependencies) and to be able to tune it up: this is also true because I may want to "replace" a plugin dependency with a "trusted" jar, instead of using the declared dependency. One solution to me is to change the pom for the plugin files I place in the "stage" repository, but I bet this will create much more problem than solving them. our "custom" poms will end up in the user's m2 repository and may conflict/brake other builds. > Unable to exclude a dependency from a needed plugin > --- > > Key: MNG-2969 > URL: http://jira.codehaus.org/browse/MNG-2969 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.6 >Reporter: Stefano Bagnara > > When we add a "standard" dependency we can tune its dependency list using the > exclusions directive. > THis is not possible with plugins. > Let's say I add javacc-maven-plugin to my build/plugins section and the > plugin declared in its pom: > > org.codehaus.plexus > plexus-utils > 1.0.4 > > And I know that this dependency is a compile dependency and I won't need it, > how can I tune my plugin inclusion so to not download plexus-utils? > in I can add new dependencies to plugin (WHY is this > needed?) but I cannot exclude existing dependencies: isn't this a bug? > I can add a new dependency to the plugin and add exclusions for this new > dependency but I cannot add an exclusion for the top-level dependencies. > Am I missing something? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-300) NPE in SurefirePlugin.constructSurefireBooter()
[
http://jira.codehaus.org/browse/SUREFIRE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94999
]
Stefano Bagnara commented on SUREFIRE-300:
--
Is there a workaround for this? Any parameter or configuration we can add to
the pom to avoid the NPE?
{code}
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.plugin.surefire.SurefirePlugin.constructSurefireBooter(SurefirePlugin.java:594)
at
org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:391)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
{code}
> NPE in SurefirePlugin.constructSurefireBooter()
> ---
>
> Key: SUREFIRE-300
> URL: http://jira.codehaus.org/browse/SUREFIRE-300
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Niklas Gustavsson
>Assignee: Brett Porter
> Fix For: 2.3.1
>
> Attachments: maven-npe.log, npe.log
>
>
> SurefirePlugin.constructSurefireBooter() throws NPE when no testcases are
> present in the project. The log attached is from building FtpServer admin-gui
> using the 2.3 version of maven-surefire-plugin:
> http://svn.apache.org/repos/asf/incubator/ftpserver/trunk/admin-gui/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRRESOURCES-6) Remote resources are not added to test jars
[
http://jira.codehaus.org/browse/MRRESOURCES-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95001
]
Stefano Bagnara commented on MRRESOURCES-6:
---
I think this should be done only if tests are really present.
Now there is a new bug: if the project does not have any test I have this error:
{code}
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.plugin.surefire.SurefirePlugin.constructSurefireBooter(SurefirePlugin.java:594)
at
org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:391)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
{code}
And this is because the NOTICE and LICENSE have been copied in the output test
folder and surefire thinks there are tests to be executed!
> Remote resources are not added to test jars
> ---
>
> Key: MRRESOURCES-6
> URL: http://jira.codehaus.org/browse/MRRESOURCES-6
> Project: Maven 2.x Remote Resources Plugin
> Issue Type: Bug
>Affects Versions: 1.0-alpha-1
>Reporter: Daniel Kulp
>Assignee: Daniel Kulp
> Fix For: 1.0-alpha-2
>
>
> Generated remote-resources should also be added to the test jar create with
> jar:test-jar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-300) NPE in SurefirePlugin.constructSurefireBooter()
[ http://jira.codehaus.org/browse/SUREFIRE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95003 ] Stefano Bagnara commented on SUREFIRE-300: -- Ignore my last comment: the real issue is http://jira.codehaus.org/browse/MRRESOURCES-6 The remote resource plugin is copying a NOTICE and LICENSE file in the test folders even if my project does not have any test.. therefore I hit this NPE.. I leave to you and MRRESOURCE now, to decide wether MRRESOURCE must take care to not copy the files or SURFIRE must try to ignore NOTICE and LICENSE before returning this error. > NPE in SurefirePlugin.constructSurefireBooter() > --- > > Key: SUREFIRE-300 > URL: http://jira.codehaus.org/browse/SUREFIRE-300 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Niklas Gustavsson >Assignee: Brett Porter > Fix For: 2.3.1 > > Attachments: maven-npe.log, npe.log > > > SurefirePlugin.constructSurefireBooter() throws NPE when no testcases are > present in the project. The log attached is from building FtpServer admin-gui > using the 2.3 version of maven-surefire-plugin: > http://svn.apache.org/repos/asf/incubator/ftpserver/trunk/admin-gui/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRRESOURCES-6) Remote resources are not added to test jars
[ http://jira.codehaus.org/browse/MRRESOURCES-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95030 ] Stefano Bagnara commented on MRRESOURCES-6: --- The property solution works. Btw IMHO it would be good if the plugin allow configurability on whether to apply the files to both main and tests or only to main (if this cannot be autodetermined) > Remote resources are not added to test jars > --- > > Key: MRRESOURCES-6 > URL: http://jira.codehaus.org/browse/MRRESOURCES-6 > Project: Maven 2.x Remote Resources Plugin > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Daniel Kulp >Assignee: Daniel Kulp > Fix For: 1.0-alpha-2 > > > Generated remote-resources should also be added to the test jar create with > jar:test-jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRRESOURCES-23) Introduce a parameter to define the scopes of the libraries to be included in the NOTICE licensing.
Introduce a parameter to define the scopes of the libraries to be included in
the NOTICE licensing.
---
Key: MRRESOURCES-23
URL: http://jira.codehaus.org/browse/MRRESOURCES-23
Project: Maven 2.x Remote Resources Plugin
Issue Type: Improvement
Affects Versions: 1.0-alpha-5
Reporter: Stefano Bagnara
Priority: Minor
I use the assembly plugin to create the following artifacts:
1) a source package including the whole source tree (including ALL the
dependencies: also test dep).
2) a binary jar only package
3) a binary + runtime dependencies package
I currently include the NOTICE/LICENSE by adding
{code}
target/maven-shared-archive-resources/META-INF/
/
NOTICE
LICENSE
{code}
it would be cool if the remote resource plugin could "better" collaborate with
the assembly plugin by including a correct NOTICE depending on assembled
depenendencies, but for basic usage it would be enough to have a parameter to
define what is the scope of the dependencies to be listed.
E.g: in my jar only distribution I don't need to make a list of runtime
depenendecies (I don't include them), in the binary package I only need to
include the runtime dependencies, in the complete-source distribution I need to
include test/compile/runtime dependencies disclaimers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2166) Provide the help listing as default when no arguments are provided
[ http://jira.codehaus.org/browse/MNG-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95903 ] Stefano Bagnara commented on MNG-2166: -- I was just adding a similar bug report. Having at least an informative "mvn help" would really help. I keep adding "BUILDING.txt" files to my projects to tell people what mvn commands they have to use to create the site, to create the package, to run some other plugin I configured in specific profiles and so on. Even a simple plugin (maven-help-plugin) that answer by default a text written in the pom would be a big step forward, then having a property for a default target to be invoked (defaulting to the "maven-help-plugin", but possibily overridable with package, site:stage or anything wirtten in the pom) would be a great solution (similar to what we had in ant) this "maven-help-plugin" could support inline text or a reference to a file to be shown or any other more advanced feature (automatically output help for the more common goals). > Provide the help listing as default when no arguments are provided > -- > > Key: MNG-2166 > URL: http://jira.codehaus.org/browse/MNG-2166 > Project: Maven 2 > Issue Type: New Feature > Components: Command Line >Affects Versions: 2.0, 2.0.1, 2.0.2 > Environment: Any >Reporter: Andre Ranvik >Priority: Minor > Fix For: 2.2.x > > > When just writing "mvn" with no arguments on the command line I get a message > such as this: > >mvn > [INFO] Scanning for projects... > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] You must specify at least one goal. Try 'install' > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: < 1 second > [INFO] Finished at: Wed Mar 22 09:15:04 CET 2006 > [INFO] Final Memory: 1M/2M > [INFO] > > Many new users to maven or any other such tools are used to getting at least > some basic info of what is expected. How about just displaying the listing > that shows up when a user writes "mvn -h" as default when no arguments are > privided? This is also a feature that most other similar products have. I > also would suggest printing a URL for where they can get basic information > for how to use maven. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-234) Maven skin / version as plugin parameters
Maven skin / version as plugin parameters - Key: MSITE-234 URL: http://jira.codehaus.org/browse/MSITE-234 Project: Maven 2.x Site Plugin Issue Type: Improvement Affects Versions: 2.0-beta-5 Reporter: Stefano Bagnara I have an m2 reactor project where one of the modules is the skin used by one of the other modules (and every of its children). root |- maven-skin '- module1 (using maven-skin) The problem is that module1 declare the skin in its site.xml file and this way the version is not updated when I use the release:prepare to update my poms. So I checked the site plugin searching for a way to declare the skin in the plugin configuration instead of the site.xml descriptor but there is no such option. I think that a good solution would be to use something like the remote resource plugin (used for LICENSE/NOTICE) also for the skin declaration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-234) Maven skin / version as plugin parameters
[ http://jira.codehaus.org/browse/MSITE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97736 ] Stefano Bagnara commented on MSITE-234: --- Sorry.. the tree has been changed by the JIRA formater | root (1.0-SNAPSHOT) | - maven-skin (1.1-SNAPSHOT) | - module1 (using maven-skin - 1.1-SNAPSHOT) > Maven skin / version as plugin parameters > - > > Key: MSITE-234 > URL: http://jira.codehaus.org/browse/MSITE-234 > Project: Maven 2.x Site Plugin > Issue Type: Improvement >Affects Versions: 2.0-beta-5 >Reporter: Stefano Bagnara > > I have an m2 reactor project where one of the modules is the skin used > by one of the other modules (and every of its children). > root > |- maven-skin > '- module1 (using maven-skin) > The problem is that module1 declare the skin in its site.xml file and > this way the version is not updated when I use the release:prepare to > update my poms. > So I checked the site plugin searching for a way to declare the skin in > the plugin configuration instead of the site.xml descriptor but there is > no such option. > I think that a good solution would be to use something like the remote > resource plugin (used for LICENSE/NOTICE) also for the skin declaration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-671) implement a license clickthrough
[ http://jira.codehaus.org/browse/MNG-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98418 ] Stefano Bagnara commented on MNG-671: - JavaMail and Activation are now distributed under the CDDL license, and this don't need the license clickthrough as we can bundle CDDL libraries within ASF products. Btw I still think that this feature would be useful for LGPL or any other not compatible license. > implement a license clickthrough > > > Key: MNG-671 > URL: http://jira.codehaus.org/browse/MNG-671 > Project: Maven 2 > Issue Type: New Feature >Reporter: Brett Porter > Fix For: 2.1.x > > Attachments: maven-artifact-manager-patch-2.txt, > maven-artifact-manager-patch.txt, maven-artifact-patch-2.txt, > maven-license-patches-3.zip, maven-settings-patch-2.txt, > maven-settings-patch.txt > > > we need some basic license acceptance policy for downloadable artifacts. For > now, this can just be a Y/N that is saved forever. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-671) implement a license clickthrough
[ http://jira.codehaus.org/browse/MNG-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98420 ] Stefano Bagnara commented on MNG-671: - "Closed" is supposed to be used when the issue has been fixed. Isn't "Won't Fix" better suited for this issue? (otherwise in the JIRA changelog we'll think it has been resolved and we have this feature). > implement a license clickthrough > > > Key: MNG-671 > URL: http://jira.codehaus.org/browse/MNG-671 > Project: Maven 2 > Issue Type: New Feature >Reporter: Brett Porter > Fix For: 2.1.x > > Attachments: maven-artifact-manager-patch-2.txt, > maven-artifact-manager-patch.txt, maven-artifact-patch-2.txt, > maven-license-patches-3.zip, maven-settings-patch-2.txt, > maven-settings-patch.txt > > > we need some basic license acceptance policy for downloadable artifacts. For > now, this can just be a Y/N that is saved forever. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2622) dnsjava 2.0.7
dnsjava 2.0.7 - Key: MAVENUPLOAD-2622 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2622 Project: Maven Upload Requests Issue Type: Wish Reporter: Stefano Bagnara dnsjava 2.0.7 I'm not the author of dnsjava, but I already uploaded the 2.0.1 bundle, so here we are with newer bundles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2623) dnsjava 2.0.6
dnsjava 2.0.6 - Key: MAVENUPLOAD-2623 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2623 Project: Maven Upload Requests Issue Type: Wish Reporter: Stefano Bagnara dnsjava 2.0.6 I'm not the author of dnsjava, but I already uploaded the 2.0.1 bundle, so here we are with newer bundles. PS: this is my second bundle in a row. THe Repository Upload tells me to use a single issue but it was not clear what I'm supposed to insert in the "Bundle URL" (it speaks about an empty line somewhere, but I don't understand it), so I did 2 separate issues. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2624) Sun's javax.activation 1.1.1
Sun's javax.activation 1.1.1 Key: MAVENUPLOAD-2624 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2624 Project: Maven Upload Requests Issue Type: Wish Reporter: Stefano Bagnara central only includes the 1.1 release. This is the updated 1.1.1 release. The jar is distributed under the CDDL license. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2625) not-yet-commons-ssl-0.3.11 bundle
not-yet-commons-ssl-0.3.11 bundle - Key: MAVENUPLOAD-2625 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2625 Project: Maven Upload Requests Issue Type: Wish Reporter: Stefano Bagnara not-yet-commons-ssl-0.3.11 I'm not the author of not-yet-commons-ssl. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2693) Validator.nu HTML parser 1.2.1 bundle
Validator.nu HTML parser 1.2.1 bundle - Key: MAVENUPLOAD-2693 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2693 Project: Maven Upload Requests Issue Type: Task Reporter: Stefano Bagnara htmlparser-1.2.1 I'm not the author of Validator.nu HTML parser. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-884) dnsjava 2.0.1 bundle import
dnsjava 2.0.1 bundle import --- Key: MAVENUPLOAD-884 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-884 Project: maven-upload-requests Type: Task Reporter: Stefano Bagnara I added few informations (license, url) to the pom.xml that is already in maven2 repository for old releases. I left the dnsjava groupid to be consistent with previous releases. If you prefer I can resubmit this in the "org.xbill" groupid (same of the package) or "org.dnsjava" groupid (as the sitename). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
