[jira] Created: (MASSEMBLY-469) Version for artifacts in dependencies section are resolved wrong
Version for artifacts in dependencies section are resolved wrong
Key: MASSEMBLY-469
URL: http://jira.codehaus.org/browse/MASSEMBLY-469
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-3
Environment: Windows, Java6, maven-2.2.1
Reporter: Christoph Panwinkler
Dependencies to artifacts are resolved wrongly when using maven-assembly-plugin
2.2-beta-2 (this still exists in Version 2.2-beta-5):
a) Goal mvn assembly:assembly
b) Descriptor
assembly
idservice-wrapper/id
formats
formatzip/format
/formats
baseDirectory${project.name}/baseDirectory
includeBaseDirectorytrue/includeBaseDirectory
dependencySets
dependencySet
unpackfalse/unpack
scopecompile/scope
outputDirectorylib/outputDirectory
/dependencySet
/dependencySets
...
/assembly
e.g.
We have version test-1.0.jar in parent pom.
We overwrite this version with test-1.1.jar in current pom
1) 2.2-beta-3 = maven-assembly-plugin = 2.2-beta-5
test-1.0.jar is packaged in zip-File
2) maven-assembly-plugin 2.2-beta-2
test-1.1.jar is packaged in zip-File
= Artifact test in this case should always be resolved to test-1.1.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: (MASSEMBLY-469) Version for artifacts in dependencies section are resolved wrong
[
http://jira.codehaus.org/browse/MASSEMBLY-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=209922#action_209922
]
Christoph Panwinkler commented on MASSEMBLY-469:
affects versions 2.2-beta-3 to 2.2-beta-5
Version for artifacts in dependencies section are resolved wrong
Key: MASSEMBLY-469
URL: http://jira.codehaus.org/browse/MASSEMBLY-469
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-3
Environment: Windows, Java6, maven-2.2.1
Reporter: Christoph Panwinkler
Dependencies to artifacts are resolved wrongly when using
maven-assembly-plugin 2.2-beta-2 (this still exists in Version 2.2-beta-5):
a) Goal mvn assembly:assembly
b) Descriptor
assembly
idservice-wrapper/id
formats
formatzip/format
/formats
baseDirectory${project.name}/baseDirectory
includeBaseDirectorytrue/includeBaseDirectory
dependencySets
dependencySet
unpackfalse/unpack
scopecompile/scope
outputDirectorylib/outputDirectory
/dependencySet
/dependencySets
...
/assembly
e.g.
We have version test-1.0.jar in parent pom.
We overwrite this version with test-1.1.jar in current pom
1) 2.2-beta-3 = maven-assembly-plugin = 2.2-beta-5
test-1.0.jar is packaged in zip-File
2) maven-assembly-plugin 2.2-beta-2
test-1.1.jar is packaged in zip-File
= Artifact test in this case should always be resolved to test-1.1.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: (MPWAR-74) webapp-cache.xml schema available online
webapp-cache.xml schema available online Key: MPWAR-74 URL: http://jira.codehaus.org/browse/MPWAR-74 Project: Maven 1.x War Plugin Issue Type: Improvement Affects Versions: 1.6.3 Environment: Any - it is a validation problem so it is not affected by operational systems or IDEs, but the issue was primarily detected on the Eclipse IDE version 3.5. Reporter: Felipe Gaúcho When packaging a web-application, maven-war-plugin generates a cache file, as described here: http://maven.apache.org/plugins/maven-war-plugin/exploded-mojo.html#cacheFile This cache file is an XML file but the generated file doesn't contains an Schema or DTD declaration on its header. This makes impossible to validate such file, generating warnings in the most common Java IDEs. Since it is an XML file I believe it should has a model specification somewhere (a XSD Schema I hope), eventually just not released for public usage. So, please publish the XSD Schema (or dtd) of the cache file in order to give the developers a chance to detect potential bugs before to deploy their web-application. -- 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-492) The svn tag command failed
[
http://jira.codehaus.org/browse/MRELEASE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=209925#action_209925
]
Baptiste MATHUS commented on MRELEASE-492:
--
For the record, one solution might be to use switch svn provider to full java
implementation (svnkit).
See http://jira.codehaus.org/browse/MRELEASE-344
The svn tag command failed
--
Key: MRELEASE-492
URL: http://jira.codehaus.org/browse/MRELEASE-492
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.0-beta-9
Environment: ubuntu 9.04 ,
Apache Maven 2.1.0 (r755702; 2009-03-19 00:40:27+0530)
Java version: 1.6.0_13
Java home: /usr/lib/jvm/java-6-sun-1.6.0.13/jre
Default locale: en_IN, platform encoding: UTF-8
OS name: linux version: 2.6.28-15-server arch: i386 Family: unix
Reporter: Sridher Jakku
when i run the mvn release:prepare this error comming
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.584
sec
[INFO] Running com.ipleanty.accure.module.orm.AppTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018
sec
[INFO]
[INFO] Results :
[INFO]
[INFO] Tests run: 27, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] [INFO] [antrun:run {execution: default}]
[INFO] [INFO] Executing tasks
[INFO] [echo]
[INFO] [echo] r2093 | js | 2009-10-13 20:02:29 +0530 (Tue, 13 Oct 2009)
[INFO] [echo]
[INFO] [echo] Your orm Revision number : 2073
[INFO] [INFO] Executed tasks
[INFO] [INFO] [jar:jar]
[INFO] [INFO] Building jar: /home/sridher/maven/svn/orm/target/orm-0.7.jar
[INFO] [INFO]
[INFO] [INFO] BUILD SUCCESSFUL
[INFO] [INFO]
[INFO] [INFO] Total time: 26 seconds
[INFO] [INFO] Finished at: Tue Oct 13 20:03:30 IST 2009
[INFO] [INFO] Final Memory: 25M/114M
[INFO] [INFO]
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /home/sridher/maven/svn/orm svn --username
js --password '*' --non-interactive commit --file
/tmp/maven-scm-327676631.commit --targets
/tmp/maven-scm-7485856893453511468-targets
[INFO] Working directory: /home/sridher/maven/svn/orm
[INFO] Tagging release with the label orm-0.7...
[INFO] Executing: /bin/sh -c cd /home/sridher/maven/svn/orm svn --username
js --password '*' --non-interactive copy --file
/tmp/maven-scm-895863680.commit .
scm:svn:svn://192.168.1.10/Accure/orm/tags/orm-0.7
[INFO] Working directory: /home/sridher/maven/svn/orm
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Local, non-commit operations do not take a log message or revision
properties
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 41 seconds
[INFO] Finished at: Tue Oct 13 20:03:32 IST 2009
[INFO] Final Memory: 12M/119M
[INFO]
--
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: (MSHADE-75) Package maven multimodule project with shade plugin : error in opening zip on directory
Package maven multimodule project with shade plugin : error in opening zip on directory --- Key: MSHADE-75 URL: http://jira.codehaus.org/browse/MSHADE-75 Project: Maven 2.x Shade Plugin Issue Type: Bug Affects Versions: 1.3.1 Environment: Ubuntu 9.04 - Jaunty Jackalope -, Eclispse (Galileo), java 1.6.0_16 Reporter: Yoann Yonnet Attachments: patch-maven-shade-plugin.txt Hello, I make a maven aggregator project with two modules. The first module is a dependency of the second. The first module is build with the install goal. The second with the shade plugin during the package phase. The first module build runs successfully and install resulting jar file in the maven local repository. The second module build fails with this error : [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error creating shaded jar: error in opening zip file /home/yoann/workspace/maven.1265640716107/trunk/tcx-ws-client/module1/target/classes [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 10 seconds [INFO] Finished at: Fri Feb 12 10:39:29 CET 2010 [INFO] Final Memory: 59M/583M [INFO] It's due to the shade plugin whose tries to reference first module classes from target/classes repository instead of the jar file previously build. Therefore, it seems that the shade plugin doesn't work with a maven multimodules project. I manage to build my maven aggregator project by applying the attached patch (patch-maven-shade-plugin.txt) on the class ShadeMojo.java -- 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: (MCHANGES-190) HTML in changes.xml stopped working
[ http://jira.codehaus.org/browse/MCHANGES-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=209929#action_209929 ] Joerg Schaible commented on MCHANGES-190: - This *is* really a major regression. I had to detect now that roughly 50 change reports for our last release cycle are simply rubbish! We added HTML for years in CDATA sections without any problems. This was valid XML and conforming to the schema. HTML in changes.xml stopped working --- Key: MCHANGES-190 URL: http://jira.codehaus.org/browse/MCHANGES-190 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: changes-report Affects Versions: 2.3 Environment: Maven version: 2.0.10 Java version: 1.5.0_17 OS name: linux version: 2.6.32-686 arch: i386 Family: unix Reporter: Christian Schulte Priority: Critical Attachments: changes.xml, changes.xml, MCHANGES-190.zip The fix for MCHANGES-189 does not seem to be correct. A changes.xml file containing HTML-Tags got rendered correctly using version 2.2. Starting with version 2.3, HTML-Tags will be encoded using HTML entities for the '' and '' characters leading to the actual tags getting shown in the report. See the attached example changes.xml file containing HTML no longer working with version 2.3. -- 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-2741) OWL ART API (Sesame2 Impl) Project request for upload on Maven Central
OWL ART API (Sesame2 Impl) Project request for upload on Maven Central --- Key: MAVENUPLOAD-2741 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2741 Project: Maven Upload Requests Issue Type: Wish Reporter: Armando Stellato http://owlart-sesame2.googlecode.com/files/owlart-sesame2impl-1.0.1-bundle.jar http://art.uniroma2.it/owlart: this is the main site of the project @ our university (this is the owl art project, though this sesame2 implementation of owl art API is hosted on the same site) http://art.uniroma2.it/owlart/team: this is where my picture and email is available and where I'm reported as the author of this lib http://code.google.com/p/owlart-sesame2: this is the google project site for this same project (here too u can find my email which is the google account of the project owner) -- 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-2742) Upload UrlRewriteFilter 3.2.0 to Central
Upload UrlRewriteFilter 3.2.0 to Central Key: MAVENUPLOAD-2742 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2742 Project: Maven Upload Requests Issue Type: Wish Reporter: Matt Raible Attachments: urlrewrite-3.2.0-bundle.zip Please upload the 3.2.0 release of UrlRewriteFilter to central. Because it's awesome. -- 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: (MENFORCER-92) RequirePluginVersions fails when POM artifactId contains an expression referring to a POM property
RequirePluginVersions fails when POM artifactId contains an expression
referring to a POM property
--
Key: MENFORCER-92
URL: http://jira.codehaus.org/browse/MENFORCER-92
Project: Maven 2.x Enforcer Plugin
Issue Type: Bug
Components: Standard Rules
Affects Versions: 1.0-beta-1
Reporter: John Casey
{code}
git clone git://github.com/torquebox/torquebox
cd torquebox-docs/en-US
mvn install
{code}
This build will fail because the artifactId of the POM is:
torquebox-docs-${translation}
There is a POM property: translation == en_US
The enforcer plugin will fail (even if I update the version to 1.0-beta-1 in a
pluginManagement section) saying it cannot find the torquebox-docs-en-US
POM...which is the one being built.
--
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: (MCLEAN-42) followSymlinks documentation incorrectly says default value is 'false'
followSymlinks documentation incorrectly says default value is 'false' -- Key: MCLEAN-42 URL: http://jira.codehaus.org/browse/MCLEAN-42 Project: Maven 2.x Clean Plugin Issue Type: Bug Affects Versions: 2.4 Reporter: John Casey setting value to false in plugin configuration works to stop following symlinks, which seems to imply the documentation is 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] Closed: (MCLEAN-42) followSymlinks documentation incorrectly says default value is 'false'
[ http://jira.codehaus.org/browse/MCLEAN-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MCLEAN-42. Resolution: Cannot Reproduce Assignee: John Casey conducting more tests, seems like the followSymlinks default value is correctly documented. followSymlinks documentation incorrectly says default value is 'false' -- Key: MCLEAN-42 URL: http://jira.codehaus.org/browse/MCLEAN-42 Project: Maven 2.x Clean Plugin Issue Type: Bug Affects Versions: 2.4 Reporter: John Casey Assignee: John Casey setting value to false in plugin configuration works to stop following symlinks, which seems to imply the documentation is 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] Updated: (MCLEAN-42) followSymlinks documentation incorrectly says default value is 'false'
[ http://jira.codehaus.org/browse/MCLEAN-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MCLEAN-42: - Fix Version/s: 2.5 followSymlinks documentation incorrectly says default value is 'false' -- Key: MCLEAN-42 URL: http://jira.codehaus.org/browse/MCLEAN-42 Project: Maven 2.x Clean Plugin Issue Type: Bug Affects Versions: 2.4 Reporter: John Casey Assignee: John Casey Fix For: 2.5 setting value to false in plugin configuration works to stop following symlinks, which seems to imply the documentation is 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] Deleted: (MCLEAN-42) followSymlinks documentation incorrectly says default value is 'false'
[ http://jira.codehaus.org/browse/MCLEAN-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey deleted MCLEAN-42: - followSymlinks documentation incorrectly says default value is 'false' -- Key: MCLEAN-42 URL: http://jira.codehaus.org/browse/MCLEAN-42 Project: Maven 2.x Clean Plugin Issue Type: Bug Reporter: John Casey Assignee: John Casey setting value to false in plugin configuration works to stop following symlinks, which seems to imply the documentation is 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-462) Broken module links
[ http://jira.codehaus.org/browse/MSITE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=209997#action_209997 ] Dennis Lundberg commented on MSITE-462: --- The URLs should be the ones where the site will eventually appear at, once the staging site has been verified. The Site Plugin uses these URLs when calculating links in the generated site. If a link is determined to be within the same site - a relative link is created. In your project you have told the Site Plugin that the parent and child will end up at the *same* URL. This will cause the Site Plugin to create strange links. More info about relative links at: http://maven.apache.org/plugins/maven-site-plugin/faq.html#Why_do_my_absolute_links_get_translated_into_relative_links Broken module links --- Key: MSITE-462 URL: http://jira.codehaus.org/browse/MSITE-462 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.1 Reporter: Frederic Müller Attachments: project.tar.gz The goal site:stage always leads to the same broken links no matter what I do. I created the most simple project layout under /home/fmu01/Projekte/test-parent and still it won't work. -- 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: (MPWAR-74) webapp-cache.xml schema available online
[ http://jira.codehaus.org/browse/MPWAR-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=209998#action_209998 ] Dennis Lundberg commented on MPWAR-74: -- Isn't this issue for the WAR Plugin for *Maven 2*? webapp-cache.xml schema available online Key: MPWAR-74 URL: http://jira.codehaus.org/browse/MPWAR-74 Project: Maven 1.x War Plugin Issue Type: Improvement Affects Versions: 1.6.3 Environment: Any - it is a validation problem so it is not affected by operational systems or IDEs, but the issue was primarily detected on the Eclipse IDE version 3.5. Reporter: Felipe Gaúcho When packaging a web-application, maven-war-plugin generates a cache file, as described here: http://maven.apache.org/plugins/maven-war-plugin/exploded-mojo.html#cacheFile This cache file is an XML file but the generated file doesn't contains an Schema or DTD declaration on its header. This makes impossible to validate such file, generating warnings in the most common Java IDEs. Since it is an XML file I believe it should has a model specification somewhere (a XSD Schema I hope), eventually just not released for public usage. So, please publish the XSD Schema (or dtd) of the cache file in order to give the developers a chance to detect potential bugs before to deploy their web-application. -- 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-462) Broken module links
[ http://jira.codehaus.org/browse/MSITE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=210011#action_210011 ] Frederic Müller commented on MSITE-462: --- Well since I didn't supply any url at all I somehow expexted the plugin to use urls that represent the project's file structure. Maybe generating pseudo urls like http://localhost/test-parent and http://localhost/test-parent/test-module would do the trick. I'm most likely never even going to publish anywhere. I'm simply trying to generate the site to easily create human readable reports. Does my idea seem reasonable? Broken module links --- Key: MSITE-462 URL: http://jira.codehaus.org/browse/MSITE-462 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.1 Reporter: Frederic Müller Attachments: project.tar.gz The goal site:stage always leads to the same broken links no matter what I do. I created the most simple project layout under /home/fmu01/Projekte/test-parent and still it won't work. -- 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-2742) Upload UrlRewriteFilter 3.2.0 to Central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=210025#action_210025 ] Dan Tran commented on MAVENUPLOAD-2742: --- This bundle has dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopecompile/scope /dependency as dependency? Upload UrlRewriteFilter 3.2.0 to Central Key: MAVENUPLOAD-2742 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2742 Project: Maven Upload Requests Issue Type: Wish Reporter: Matt Raible Attachments: urlrewrite-3.2.0-bundle.zip Please upload the 3.2.0 release of UrlRewriteFilter to central. Because it's awesome. -- 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
