[jira] Commented: (MSUREFIRE-157) ClassNotFoundException or NoClassDefFoundError executing maven2 install
[ http://jira.codehaus.org/browse/MSUREFIRE-157?page=comments#action_71829
]
Francesc Xavier commented on MSUREFIRE-157:
---
Now, it's works fine!!!
the problem was done by the description element in the pom.xml that was too
long and with several whitespaces, and the Specification-Title attribute (which
it's mapped) in the MANIFEST.MF was not well-formed. In J2se 1.4.2_x
the classloader found this problem and that's not load this jar without any
comment (?). Nevertheless in j2se 5.0 found the problem and report the
problem!!!
Obviusly, it is not a bug in your plugin!
thanks a lot
Francesc
> ClassNotFoundException or NoClassDefFoundError executing maven2 install
> ---
>
> Key: MSUREFIRE-157
> URL: http://jira.codehaus.org/browse/MSUREFIRE-157
> Project: Maven 2.x Surefire Plugin
> Issue Type: Wish
> Environment: eclipse 3.2, windows XP and j2se 1.4.2
>Reporter: Francesc Xavier
>
> Hey,
> first all congratultions for your execellent job. We are using Maven2 in
> order to develop a project. This project has several modules with
> dependencies among them, reflected in their pom's. When we try to execute a
> test from the project root in command line (typing mvn test) all works fine,
> but when we try to execute 'mvn install', all the tests of modules that have
> dependencies with other modules (in our case, the core module) begins to fail
> throwing a java.lang.NoClassDefFoundError. Moreover, when we try to execute
> the same tests to the specific module the same error is produced.
> Pom parent has the following definitons
>
>xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns="http://maven.apache.org/POM/4.0.0";>
> 4.0.0
> com.nextret.frwk
> openfrwk-all
> pom
> NexTReT Open Framework
> 2006
> 0.1-SNAPSHOT
>
> 2.0.4
>
>
> openfrwk-core
> openfrwk-instrument
> openfrwk-mock
> openfrwk-ejbgateway
> openfrwk-security
> openfrwk-persistence
> openfrwk-tasks
> openfrwk-services
> openfrwk-services-jboss
>
> ..
> (we have not included the dependencies that all are correctly retrieved from
> repository) and every pom module chlid has
>
> 4.0.0
>
> com.nextret.frwk
> openfrwk-all
> 0.1-SNAPSHOT
>
> com.nextret.frwk
> openfrwk-core
> jar
> Core
> (also including the dependency of core module in dependencies element)
>
>
> ${project.groupId}
> openfrwk-core
> 0.1-SNAPSHOT
>
> ...
>
> any suggestion ?? we have to skip all the tests (currently executed in
> eclipse), but we realize that are not the best way!!
> Thanks a lot!!
> Francesc Xavier
--
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: (MNG-2458) [Patch] maven-docck-plugin proxy support
[ http://jira.codehaus.org/browse/MNG-2458?page=all ] Denis Cabasson closed MNG-2458. --- Resolution: Fixed Thanks for applying this Vincent! > [Patch] maven-docck-plugin proxy support > > > Key: MNG-2458 > URL: http://jira.codehaus.org/browse/MNG-2458 > Project: Maven 2 > Issue Type: Improvement > Components: Plugins and Lifecycle >Reporter: Denis Cabasson > Assigned To: Vincent Siveton > Attachments: maven-docck-plugin-dcabasson-2.txt, > maven-docck-plugin-dcabasson.txt > > > Here is a patch for proxy support in the maven-docck-plugin (reported here, > as I don't think there is yet a JIRA entry for this plugin). > Looks like I had some problems with presentation. > Will try to re-upload a cleaner version -- 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: (CONTINUUM-777) Handle filesystem problems when adding a pom
[ http://jira.codehaus.org/browse/CONTINUUM-777?page=all ] Lester Ecarma updated CONTINUUM-777: Attachment: CONTINUUM-777.patch The attached patch (CONTINUUM-777.patch) only covers AddMavenTwoProjectAction. I'm not sure if I got it right, so I'll wait for comments before I work on the other classes. > Handle filesystem problems when adding a pom > > > Key: CONTINUUM-777 > URL: http://jira.codehaus.org/browse/CONTINUUM-777 > Project: Continuum > Issue Type: Sub-task >Reporter: Carlos Sanchez > Assigned To: Lester Ecarma > Attachments: CONTINUUM-777.patch > > > I see in the logs > 61589439 [SocketListener0-5] INFO org.apache.maven.continuum.Continuum - > Could not download > https://svn.simulalabs.net/svn/repos/BEA-DotNet/trunk/pom.xml: /tmp/continuum/ > svn/repos/BEA-DotNet/trunk/pom.xml (No such file or directory) > 6 > we should check that file error and show an internal error page instead of > current > Could not download > https://svn.simulalabs.net/svn/repos/BEA-DotNet/trunk/pom.xml: > /tmp/continuum/svn/repos/BEA-DotNet/trunk/pom.xml (No such file or directory) > Check the logs for more details. -- 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: (MEV-430) Fix dependencies of commons-httpclient (add test scope for junit)
Fix dependencies of commons-httpclient (add test scope for junit) - Key: MEV-430 URL: http://jira.codehaus.org/browse/MEV-430 Project: Maven Evangelism Issue Type: Bug Components: Invalid POM Reporter: Jim Downing consider changing junit junit 3.8 to junit junit 3.8 test -- 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: (MJAVADOC-82) 'sourcepath' should not be mandatory when using 'subpackages' configuration
'sourcepath' should not be mandatory when using 'subpackages' configuration
---
Key: MJAVADOC-82
URL: http://jira.codehaus.org/browse/MJAVADOC-82
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.0
Reporter: Damien Lecan
It is impossible to use 'subpackages' configuration without specifying
'sourcepath' directory.
This works :
maven-javadoc-plugin
${basedir}/src/main/java
my.package:my.package2
but this one doesn't works (without sourcepath with sources default path)
maven-javadoc-plugin
my.package:my.package2
--
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-33) Website documentation incorrect/out-of-date
Website documentation incorrect/out-of-date --- Key: MDEP-33 URL: http://jira.codehaus.org/browse/MDEP-33 Project: Maven 2.x Dependency Plugin Issue Type: Bug Affects Versions: 1.0 Environment: n/a Reporter: Gwyn Evans When starting at http://mojo.codehaus.org/dependency-maven-plugin/ (as a result of a previous usages, Google searches, etc), there's no indication that the documention there is out of date and there's updated information at http://maven.apache.org/plugins/maven-dependency-plugin. I only managed to get there by following the link to the SVN pages, then following the (now incorrect) link to the repository, then working out the correct link, which led to the readme.txt that informed the project had moved... It would be rather better if the main page at codehaus was replaced by at least a mention of the move! /Gwyn -- 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-134) Incorrect link to issue tracker
Incorrect link to issue tracker --- Key: MASSEMBLY-134 URL: http://jira.codehaus.org/browse/MASSEMBLY-134 Project: Maven 2.x Assembly Plugin Issue Type: Bug Environment: n/a Reporter: Gwyn Evans The project's "Issue Tracking" page at http://maven.apache.org/plugins/maven-assembly-plugin/issue-tracking.html links to http://jira.codehaus.org/browse/MPA (the Maven Project Administration JIRA) rather than where it should, i.e. here (http://jira.codehaus.org/browse/MASSEMBLY) /Gwyn -- 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-135) Clarify the addition of dependancies in assembly:assembly
Clarify the addition of dependancies in assembly:assembly - Key: MASSEMBLY-135 URL: http://jira.codehaus.org/browse/MASSEMBLY-135 Project: Maven 2.x Assembly Plugin Issue Type: Improvement Affects Versions: 2.1 Environment: n/a Reporter: Gwyn Evans It was unclear to me for quite a while that the assembly plugin could pack dependancies The documentation suggested that it should, by default, do so, but when trying wth the built-in "bin" descriptor, nothing happened. I worked around it for a while by having the dependancy plugin copy the jars into my target folder, until I came back to it today. What I found was that if I took the built-in 'bin', created my own[1] and simply added then I got the behaviour I wanted. I'd suggest two changes - (1) some comment (in the descriptor format description) about how dependancies are not included without the above and (2) an additional pre-defined descriptior, e.g. "bin-with-dependancies", as that seems to be a common requirement, judging from the M2 mailing list. /Gwyn [1] By the way, I couldn't find any documentation that explained the correct syntax for this - http://maven.apache.org/plugins/maven-assembly-plugin/howto.html just uses & http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html mentions be only by trial & error do you find what it should contain (OK, convention suggests it would , but the description said files, which I first read as the filepath & was marked as depreciated. ) -- 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-2488) Version range does not select latest version present in local repository unless used in offline mode
Version range does not select latest version present in local repository unless
used in offline mode
-
Key: MNG-2488
URL: http://jira.codehaus.org/browse/MNG-2488
Project: Maven 2
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.0.4
Environment: Linux 2.6.8-1-686-smp #1 SMP Thu Nov 25 04:55:00 UTC 2004
i686 GNU/Linux
Reporter: Stefan Seidel
When a version range for a dependency ist specified, M2 look in the given
remote repositories only and ignores a newer version in the local repository.
For example, I use the release plugin to release version 1.0.0 of artifact A
(and deploy it to a remote repository), then move on locally to 1.0.1-SNAPSHOT.
I continue developing this and do a "mvn install" because I do not necessarily
want to deploy a snapshot immediately. If I then build a project B with
mygroup
A
[1.0.0,)
Maven will look in the remote repository and find version 1.0.0, but will
ignore my locally installed 1.0.1-SNAPSHOT. However, when using offline mode
("mvn -o package"), 1.0.1-SNAPSHOT is used.
Workarounds include using offline mode - thus excluding the possibility to
retrieve changes in other dependencies, using a fixed version (not very
helpful) or deploying each and every snapshot (not helpful because other
developers do not need to see snapshots that I use for testing only).
--
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: (CONTINUUM-800) Use maven-user project for user management
[ http://jira.codehaus.org/browse/CONTINUUM-800?page=all ] Henry S. Isidro updated CONTINUUM-800: -- Attachment: CONTINUUM-800-continuum-webapp.patch File Attached: CONTINUUM-800-continuum-webapp.patch I keep getting an NPE. It seems that the getPersistenceManager() method from DefaultUserManager returns a null. Is it a problem with injection from plexus? > Use maven-user project for user management > -- > > Key: CONTINUUM-800 > URL: http://jira.codehaus.org/browse/CONTINUUM-800 > Project: Continuum > Issue Type: Sub-task >Reporter: Carlos Sanchez > Attachments: CONTINUUM-800-continuum-webapp.patch, > CONTINUUM-800-maven-user-webapp.patch, CONTINUUM-800-maven-user.patch > > > Added a first version of user management in > https://svn.apache.org/repos/asf/maven/shared/trunk/maven-user > We have to move user code from Continuum there and use it instead -- 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: (MEV-430) Fix dependencies of commons-httpclient (add test scope for junit)
[ http://jira.codehaus.org/browse/MEV-430?page=all ] Carlos Sanchez closed MEV-430. -- Assignee: Carlos Sanchez Resolution: Won't Fix We can't change already deployed poms, see https://issues.apache.org/jira/browse/HTTPCLIENT-595 for future versions > Fix dependencies of commons-httpclient (add test scope for junit) > - > > Key: MEV-430 > URL: http://jira.codehaus.org/browse/MEV-430 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid POM >Reporter: Jim Downing > Assigned To: Carlos Sanchez > > consider changing > > > junit > junit > 3.8 > > > to > > > junit > junit > 3.8 > test > > -- 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: (MAVEN-1410) pom.artifactId is missing from XML schema and pom.id should be removed
[ http://jira.codehaus.org/browse/MAVEN-1410?page=all ] Lukas Theussl updated MAVEN-1410: - Assignee: Lukas Theussl Fix Version/s: (was: 1.1-beta-1) 1.1-rc1 > pom.artifactId is missing from XML schema and pom.id should be removed > -- > > Key: MAVEN-1410 > URL: http://jira.codehaus.org/browse/MAVEN-1410 > Project: Maven > Issue Type: Bug > Components: model >Affects Versions: 1.0 >Reporter: Dennis Lundberg > Assigned To: Lukas Theussl > Fix For: 1.1-rc1 > > Attachments: maven-project-3.xsd.patch, > maven-project.xsd-1_0-BRANCH.patch, xdocs-artifactId-version2.patch, > xdocs-artifactId.patch > > > After some discussion on the dev-list "pom.id versus pom.artifactId - which > is correct?" there seems to be some inconsistencies in the 1.0 release. > The discussion resulted in the following conclusions: > 1. The element project.id should be removed from the XML schema > 2. The element project.artifactId should be added to the XML schema > 3. Documentation needs to be updated to reflect the above issues > 1 and 2 should probably be done by one of the core developers, including > decisions regarding version numbers for the XML schema. I can make a patch > for it if you think that's ok. > I can make patches for the xdocs to fix 3. On which branch should I create > the patches? -- 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: (MPGENAPP-27) Generated poms contain deprecated id elements
Generated poms contain deprecated id elements - Key: MPGENAPP-27 URL: http://jira.codehaus.org/browse/MPGENAPP-27 Project: maven-genapp-plugin Issue Type: Bug Reporter: Lukas Theussl Assigned To: Lukas Theussl Fix For: 2.3.1 Replace by artifactId -- 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: (MAVEN-1776) Upgrade maven-genapp-plugin to v 2.3.1
Upgrade maven-genapp-plugin to v 2.3.1 -- Key: MAVEN-1776 URL: http://jira.codehaus.org/browse/MAVEN-1776 Project: Maven Issue Type: Sub-task Reporter: Lukas Theussl -- 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: (MAVEN-1776) Upgrade maven-genapp-plugin to v 2.3.1
[ http://jira.codehaus.org/browse/MAVEN-1776?page=all ] Lukas Theussl updated MAVEN-1776: - Description: http://jira.codehaus.org/browse/MPGENAPP?report=com.atlassian.jira.plugin.system.project:roadmap-panel Fix Version/s: 1.1-rc1 > Upgrade maven-genapp-plugin to v 2.3.1 > -- > > Key: MAVEN-1776 > URL: http://jira.codehaus.org/browse/MAVEN-1776 > Project: Maven > Issue Type: Sub-task >Reporter: Lukas Theussl > Fix For: 1.1-rc1 > > > http://jira.codehaus.org/browse/MPGENAPP?report=com.atlassian.jira.plugin.system.project:roadmap-panel -- 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: (MECLIPSE-145) Add support for building Eclipse workspaces
Add support for building Eclipse workspaces --- Key: MECLIPSE-145 URL: http://jira.codehaus.org/browse/MECLIPSE-145 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Reporter: Curt Cox The ability to generate Eclipse project files is very handy: mvn eclipse:eclipse After this is done, the developer launches Eclipse and imports the project created into the Eclipse workspace. It would be more convenient, if the workspace was built for the developer. Many developers are already in the habit of explicitly specifying a workspace to Eclipse via the -data option. So, the developer would use something like: mvn eclipse:data eclipse -data workspace This would create an Eclipse workspace with separate projects for main and test, then launch Eclipse. One of the main reasons to use the -data option to specify a workspace is so that one can easily switch between different Eclipse releases. Is there any reason why Maven can't manage Eclipse releases. After all, if the project is developed with Eclipse, then Eclipse is a dependency. So, then how about: mvn eclipse:start Which would start Eclipse specifying the appropriate project workspace. If the workspace didn't exist, it would be created. -- 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: (MANTLR-6) Support for grammar inheritance
[ http://jira.codehaus.org/browse/MANTLR-6?page=all ] Ersin Er updated MANTLR-6: -- Attachment: maven_antlr_plugin_grammar_inheritance_support.patch The patch provides support for Antlr Grammar Inheritance. When the patch applied the plugin assumes all grammar files except the one being processed as candidates for super grammar source files and passes their paths to the antlr tool for the actual processed .g file. The patch has been particularly tested within ApacheDS codebase. > Support for grammar inheritance > --- > > Key: MANTLR-6 > URL: http://jira.codehaus.org/browse/MANTLR-6 > Project: Maven 2.x Antlr Plugin > Issue Type: New Feature >Reporter: Piotr Kaminski > Attachments: maven_antlr_plugin_grammar_inheritance_support.patch > > > maven-antlr-plugin does not support grammar inheritance (-glib argument). > See http://jira.codehaus.org/browse/MPANTLR-4 -- 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: (MANTLR-6) Support for grammar inheritance
[ http://jira.codehaus.org/browse/MANTLR-6?page=all ] Ersin Er updated MANTLR-6: -- Attachment: maven_antlr_plugin_grammar_inheritance_support.patch The previous attachment was a bad one due to subclipse.. The new one is the correct one. Sorry for inconvinience. > Support for grammar inheritance > --- > > Key: MANTLR-6 > URL: http://jira.codehaus.org/browse/MANTLR-6 > Project: Maven 2.x Antlr Plugin > Issue Type: New Feature >Reporter: Piotr Kaminski > Attachments: maven_antlr_plugin_grammar_inheritance_support.patch, > maven_antlr_plugin_grammar_inheritance_support.patch > > > maven-antlr-plugin does not support grammar inheritance (-glib argument). > See http://jira.codehaus.org/browse/MPANTLR-4 -- 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-1034) missing spring poms
missing spring poms --- Key: MAVENUPLOAD-1034 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1034 Project: maven-upload-requests Issue Type: Improvement Reporter: Rainer Wasserfuhr many versions at http://www.ibiblio.org/maven2/org/springframework/spring/ do not have poms, e.g. http://www.ibiblio.org/maven2/org/springframework/spring/1.2/ or http://www.ibiblio.org/maven2/org/springframework/spring/2.0-rc2/ 2.0-rc2 is missing metadata.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] Created: (MPJCOVERAGE-36) Coverage report showing more than 100% coverage for few packages/classes
Coverage report showing more than 100% coverage for few packages/classes Key: MPJCOVERAGE-36 URL: http://jira.codehaus.org/browse/MPJCOVERAGE-36 Project: maven-jcoverage-plugin Issue Type: Bug Affects Versions: 1.0.5 Reporter: Yogesh The Coverage report is showing more than 100% coverage for few packages. Some of the files are indicating coverage of over 140%. I am not able to debug the issue so far. I have report generated for two projects and I merge their jcoverage.ser files with the one generted on server after Junit execution. The report statistics appeared correct some time back and look very doubtful to me now. -- 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
Assembly - profile bug
Dear All, when using assembly plugin, profiles with activeByDefault set to true are not honored. This is really annoying! Thanks, Mike -- View this message in context: http://www.nabble.com/Assembly---profile-bug-tf2074724.html#a5713406 Sent from the Maven - Issues forum at Nabble.com.
[jira] Commented: (MEAR-35) Generate id for modules in application.xml
[ http://jira.codehaus.org/browse/MEAR-35?page=comments#action_71874 ] Stephane Nicoll commented on MEAR-35: - applicable to which J2EE spec? I don't see this as mandatory so please provide more details / reference / sample. > Generate id for modules in application.xml > -- > > Key: MEAR-35 > URL: http://jira.codehaus.org/browse/MEAR-35 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Reporter: Manikandan Balasubramanian > > When the ear plugin generates application.xml, it should generate an "id" > with each module. This "id" is according to application.xml schema. > This would help eclipse plugin to generate correct eclipse metedata. -- 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-2489) New Maven-Shared-Jar - jar internals discovery component
New Maven-Shared-Jar - jar internals discovery component Key: MNG-2489 URL: http://jira.codehaus.org/browse/MNG-2489 Project: Maven 2 Issue Type: New Feature Reporter: Joakim Erdfelt Attachments: maven-shared-jar.tar.gz Uploading a new maven-shared-jar component to allow for discovering the internals of jar files. * Packages. * Class names. * Imports. * JDK Revision. * Classes have Debug Enabled. * File List. * Taxonomy. * Sealed Jar Indicator. Useful for Maven Repository Manager and Maven Project Info Report. (patches for those comming soon). -- 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: (MDOAP-2) link to maven page on JIRA MDOAP broken
link to maven page on JIRA MDOAP broken --- Key: MDOAP-2 URL: http://jira.codehaus.org/browse/MDOAP-2 Project: Maven 2.x DOAP Plugin Issue Type: Bug Reporter: Rainer Wasserfuhr Priority: Trivial The page http://jira.codehaus.org/browse/MDOAP points to http://maven.apache.org/plugins/doap which is 404. -- 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: (MRM-146) Updates to MRM-Util's Digester to support incremental hashcodes/checksums
Updates to MRM-Util's Digester to support incremental hashcodes/checksums - Key: MRM-146 URL: http://jira.codehaus.org/browse/MRM-146 Project: Maven Repository Manager Issue Type: Improvement Reporter: Joakim Erdfelt Attachments: MRM-DIGESTER.diff In order to support a more robust checksum routine needed for automatic jar discovery operations in MRM and MPIR, a set of new functions to allow for incremental digester calculations have been created. These routines are in use by MNG-2489 to produce a bytecode checksum needed for a more accurate way to identify unknown artifacts. -- 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-2489) New Maven-Shared-Jar - jar internals discovery component
[ http://jira.codehaus.org/browse/MNG-2489?page=comments#action_71875 ] Joakim Erdfelt commented on MNG-2489: - Required Digester Patch MRM-146 is needed for this patch to work. > New Maven-Shared-Jar - jar internals discovery component > > > Key: MNG-2489 > URL: http://jira.codehaus.org/browse/MNG-2489 > Project: Maven 2 > Issue Type: New Feature >Reporter: Joakim Erdfelt > Attachments: maven-shared-jar.tar.gz > > > Uploading a new maven-shared-jar component to allow for discovering the > internals of jar files. > * Packages. > * Class names. > * Imports. > * JDK Revision. > * Classes have Debug Enabled. > * File List. > * Taxonomy. > * Sealed Jar Indicator. > Useful for Maven Repository Manager and Maven Project Info Report. (patches > for those comming soon). -- 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: (MWAR-33) jars with differents versions can be in WEB-INF/lib with war as dependencies
[ http://jira.codehaus.org/browse/MWAR-33?page=comments#action_71877 ] Andres Bernasconi commented on MWAR-33: --- I believe this is a blocker too. In my (automatically generated) WEB-INF/lib dir I have duplicate jar files with different version which are causing me application errors. I would expect that jars on the WEB-INF/lib directory be the same as the ones generated with eclipse:eclipse plugin, but no. Even those dependencies that I exclude in the pom.xml file are included in the war, so you must understand that it is breaking havoc for me. This makes maven unusable for war projects, at least for me. > jars with differents versions can be in WEB-INF/lib with war as dependencies > > > Key: MWAR-33 > URL: http://jira.codehaus.org/browse/MWAR-33 > Project: Maven 2.x War Plugin > Issue Type: Bug > Environment: all >Reporter: Olivier Lamy > Fix For: 2.1 > > Original Estimate: 15 minutes > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > > My pom has the following dependencies : > - log4j:log4j:1.2.13 > - a war with log4j:log4j:1.2.11 included > Result the two jars are in WEB-INF/lib. -- 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: (MDOAP-2) link to maven page on JIRA MDOAP broken
[ http://jira.codehaus.org/browse/MDOAP-2?page=all ] Dennis Lundberg closed MDOAP-2. --- Resolution: Fixed > link to maven page on JIRA MDOAP broken > --- > > Key: MDOAP-2 > URL: http://jira.codehaus.org/browse/MDOAP-2 > Project: Maven 2.x DOAP Plugin > Issue Type: Bug >Reporter: Rainer Wasserfuhr > Assigned To: Dennis Lundberg >Priority: Trivial > > The page http://jira.codehaus.org/browse/MDOAP > points to http://maven.apache.org/plugins/doap which is 404. -- 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-1035) POM for wstx-asl-2.9.3 is missing
POM for wstx-asl-2.9.3 is missing - Key: MAVENUPLOAD-1035 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1035 Project: maven-upload-requests Issue Type: Bug Reporter: Jochen Wiedmann The directory http://repo1.maven.org/maven2/woodstox/wstx-asl/2.9.3 does not contain a POM. This jar file is referenced by popular applications like Axis2-1.0. -- 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-1036) Upload axiom-1.0
Upload axiom-1.0 Key: MAVENUPLOAD-1036 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1036 Project: maven-upload-requests Issue Type: Improvement Reporter: Jochen Wiedmann Axiom 1.0 is used by popular packages like Axis2-1.0. -- 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-1037) Upload neethi-1.0
Upload neethi-1.0 - Key: MAVENUPLOAD-1037 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1037 Project: maven-upload-requests Issue Type: Improvement Reporter: Jochen Wiedmann Neethi 1.0 is used by popular packages like Axis2-1.0. -- 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-1037) Upload neethi-1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1037?page=all ] Jochen Wiedmann closed MAVENUPLOAD-1037. Resolution: Incomplete Sorry, I have picked the wrong version number. Recreating this request with 1.0.1. > Upload neethi-1.0 > - > > Key: MAVENUPLOAD-1037 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1037 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: Jochen Wiedmann > > Neethi 1.0 is used by popular packages like Axis2-1.0. -- 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-1038) Upload neethi-1.0.1
Upload neethi-1.0.1 --- Key: MAVENUPLOAD-1038 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1038 Project: maven-upload-requests Issue Type: Improvement Reporter: Jochen Wiedmann Neethi 1.0.1 is used by popular packages like Axis2-1.0 -- 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: (MDEP-31) ERROR: Cannot override read-only parameter: scope in goal: dependency:copy-dependencies
[ http://jira.codehaus.org/browse/MDEP-31?page=all ]
David J. M. Karlsen updated MDEP-31:
Attachment: AbstractDependencyFilterMojo-MDEP-31.java
Removes the @readonly clause declared on the variable
> ERROR: Cannot override read-only parameter: scope in goal:
> dependency:copy-dependencies
>
>
> Key: MDEP-31
> URL: http://jira.codehaus.org/browse/MDEP-31
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
>Reporter: David J. M. Karlsen
> Attachments: AbstractDependencyFilterMojo-MDEP-31.java
>
>
> http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html
>
> states that is a valid (and writable) configuration element, but the
> following configuration:
>
>
> maven-dependency-plugin
> 2.0-SNAPSHOT
>
>
> copy-dependencies
> package
>
>
> copy-dependencies
>
>
>
> true
> compile
>
>
>
>
>
> will fail with:
> [snip...]
> Building index for all classes...
> Generating
> C:/dnbnorapi/kildekode/utvikling/dnbnorapi-client/target/site/apidocs\allclasses-frame.html...
> Generating
> C:/dnbnorapi/kildekode/utvikling/dnbnorapi-client/target/site/apidocs\allclasses-noframe.html...
> Generating
> C:/dnbnorapi/kildekode/utvikling/dnbnorapi-client/target/site/apidocs\index.html...
> Generating
> C:/dnbnorapi/kildekode/utvikling/dnbnorapi-client/target/site/apidocs\help-doc.html...
> Generating
> C:/dnbnorapi/kildekode/utvikling/dnbnorapi-client/target/site/apidocs\stylesheet.css...
> [INFO] Building jar:
> C:\dnbnorapi\kildekode\utvikling\dnbnorapi-client\target\dnbnorapi-client-1.0-SNAPSHOT-javadoc.jar
> [INFO] [jar:test-jar {execution: default}]
> [INFO] Building jar:
> C:\dnbnorapi\kildekode\utvikling\dnbnorapi-client\target\dnbnorapi-client-1.0-SNAPSHOT-tests.jar
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error configuring: org.apache.maven.plugins:maven-dependency-plugin.
> Reason: ERROR: Cannot override read-only par
> ameter: scope in goal: dependency:copy-dependencies
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 1 minute 3 seconds
> [INFO] Finished at: Wed Aug 02 13:09:21 CEST 2006
> [INFO] Final Memory: 13M/27M
> [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: (MDOAP-3) include scm in pom.xml
include scm in pom.xml -- Key: MDOAP-3 URL: http://jira.codehaus.org/browse/MDOAP-3 Project: Maven 2.x DOAP Plugin Issue Type: Wish Reporter: Rainer Wasserfuhr Priority: Minor include scm section in the pom: scm:svn:http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-doap-plugin/ scm:svn:https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-doap-plugin/ http://svn.apache.org/viewvc/maven/plugins/trunk/maven-doap-plugin/ jira http://jira.codehaus.org/browse/MDOAP -- 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: (MASSEMBLY-99) dependencySets in a descriptor doesn't work anymore
[ http://jira.codehaus.org/browse/MASSEMBLY-99?page=all ] John Casey closed MASSEMBLY-99. --- Assignee: John Casey Resolution: Fixed I've verified that this issue is fixed in the snapshot version of the assembly plugin that's on the apache.snapshots repository right now (I just deployed it). > dependencySets in a descriptor doesn't work anymore > --- > > Key: MASSEMBLY-99 > URL: http://jira.codehaus.org/browse/MASSEMBLY-99 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: all >Reporter: Olivier Lamy > Assigned To: John Casey >Priority: Blocker > Fix For: 2.2 > > Attachments: descriptor.xml > > > I attached my descriptor file. > > > lib > false > runtime > > > > unzip -l on the assembly file show empty lib directory. > Olivier -- 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: (WAGONHTTP-6) The https protocol is implemented by the LightweightHttpWagon component which does not support https proxy
[ http://jira.codehaus.org/browse/WAGONHTTP-6?page=comments#action_71885 ] Matthias Weßendorf commented on WAGONHTTP-6: Is there any issue with this patch ? > The https protocol is implemented by the LightweightHttpWagon component which > does not support https proxy > -- > > Key: WAGONHTTP-6 > URL: http://jira.codehaus.org/browse/WAGONHTTP-6 > Project: wagon-http > Issue Type: Bug >Affects Versions: 1.0-alpha-6, 1.0-alpha-7 > Environment: windows xp sp1|2 > maven 2.0.2 > jdk 1.4.2 >Reporter: Thomas Recloux > Attachments: WAGONHTTP-6-patch > > > I need to access an https repository behind a proxy. > I got this error : "java.net.ConnectException: Connection timed out: > connect" which makes me think that the request is send directly to the remote > server and not to the proxy. > These docs : > http://java.sun.com/j2se/1.4.2/docs/guide/security/jsse/samples/README.txt > http://java.sun.com/j2se/1.5.0/docs/guide/net/proxies.html > describe the "https.proxyHost" and "https.proxyPort" properties. > I tried them on the 1.4.2 Jdk and it works. > Do you want me to post a patch ? > Thanks, Thomas -- 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: (MANTRUN-57) merge issue from parent causing executions to be run multiple times
merge issue from parent causing executions to be run multiple times
---
Key: MANTRUN-57
URL: http://jira.codehaus.org/browse/MANTRUN-57
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Affects Versions: 1.1
Environment: Linux Fedora Core 5, SUN JDK 1.5
Reporter: Hung Le
Fix For: 1.1
Attachments: antrun-testcase.zip, epom.xml
Has parent/child project
parent
child1
in parent's pom.xml, define a "run"
maven-antrun-plugin
e1
generate-sources
run
In child,'s pom.xml, define another "run"
maven-antrun-plugin
e2
generate-sources
run
Expect the two declaration to be merged so that during the generate-sources
phase for the child I will see
ant e1
ant e2
what happens right now
[INFO] [antrun:run {execution: e1}]
[INFO] Executing tasks
[echo] ant e1
[INFO] Executed tasks
[INFO] [antrun:run {execution: e2}]
[INFO] Executing tasks
[echo] ant e2
[INFO] Executed tasks
[INFO] [antrun:run {execution: e1}]
[INFO] Executing tasks
[echo] ant e1
[INFO] Executed tasks
[INFO] [antrun:run {execution: e2}]
[INFO] Executing tasks
[echo] ant e2
help:effective-pom shows the merged pom at the child with merge but duplicated
antrun plugin declaration
...
maven-antrun-plugin
e1
generate-sources
run
e2
generate-sources
run
maven-antrun-plugin
e1
generate-sources
run
e2
generate-sources
run
..
Attached please find
. *.zip has a sample parent/child example, you can go to child1 and do
mvn compile
. epom.xml is the output of 'mvn help:effective-pom' for the child project
--
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-2123) NullPointerException when a dependency uses version range and another uses an actual version incompatible with that range
[ http://jira.codehaus.org/browse/MNG-2123?page=comments#action_71891 ] Edwin Punzalan commented on MNG-2123: - As Brett suggested, I'm just going to make RELEASE as the default recommendationVersion so that it will be returned for conflicting VersionRanges. I've now made the unit tests pass and will be doing intensive tests on it for the different projects I have. > NullPointerException when a dependency uses version range and another uses an > actual version incompatible with that range > - > > Key: MNG-2123 > URL: http://jira.codehaus.org/browse/MNG-2123 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.3, 2.0.2, 2.0.4 >Reporter: Carlos Sanchez > Assigned To: Edwin Punzalan > Fix For: 2.0.5 > > Attachments: pom.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Struts 1.2.7 depends on commons-digester 1.6 and jasperreports 1.1.1 in [1.7,) > Build fails with a null pointer exception that is not very explanatory > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Unnamed - test:test:jar:1.0-SNAPSHOT > [INFO]task-segment: [test] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:361) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:222) > at > org.apache.maven.artifact.resolver.ResolutionNode.getDependencyTrail(ResolutionNode.java:115) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:88) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:223) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:211) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:182) > at > org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1117) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:366) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > 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] > > [INFO] Total time: 1 second > [INFO] Finished at: Sun Mar 05 23:26:16 PST 2006 > [INFO] Final Memory: 3M/5M > [INFO] > --
[jira] Created: (MPARTIFACT-70) java.lang.IllegalAccessException in artifact:artifact-install
java.lang.IllegalAccessException in artifact:artifact-install - Key: MPARTIFACT-70 URL: http://jira.codehaus.org/browse/MPARTIFACT-70 Project: maven-artifact-plugin Issue Type: Bug Reporter: dion gillard I get the following when installing a plugin: --- Nested Exception --- java.lang.IllegalAccessException: org/apache/maven/MavenUtils at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:41) at java.lang.reflect.Method.invoke(Method.java:386) at org.apache.maven.artifact.PomRewriter.getRewrittenModel(PomRewriter.j ava:85) at org.apache.maven.artifact.PomRewriter.getRewrittenPom(PomRewriter.jav a:50) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleInst all(DefaultArtifactDeployer.java:165) >From reading >http://svn.apache.org/viewvc/maven/maven-1/plugins/trunk/artifact/src/main/org/apache/maven/artifact/PomRewriter.java?view=markup > PomRewriter calls MavenUtils.getNonJellyProject and >MavenUtils.getJellyProject, of which both are declared as private static -- 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: (MEV-431) axis-jaxrpc and axis-saaj both version 1.4 have no POM
axis-jaxrpc and axis-saaj both version 1.4 have no POM -- Key: MEV-431 URL: http://jira.codehaus.org/browse/MEV-431 Project: Maven Evangelism Issue Type: Bug Components: Invalid POM Reporter: Aede Both axis-saaj and axis-jaxrpc (which specified as dependencies in axis:axis:pom:1.4) do not have a pom of their own. This will cause maven to use stubs and not store de deps in its local repo. axis-saaj would need a pom (axis-saaj-1.4.pom) with the following content: 4.0.0 axis axis-saaj 1.4 axis-saaj would need a pom (axis-jaxrpc-1.4.pom) with the following content: 4.0.0 axis axis-jaxrpc 1.4 -- 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: (MJAR-41) Cannot specify additional classpath entries in jar manifest when using addClasspath
[ http://jira.codehaus.org/browse/MJAR-41?page=comments#action_71897 ] Fredrik Vraalsen commented on MJAR-41: -- This has now been fixed in maven-archiver 2.2-SNAPSHOT, so the dependencies in maven-jar-plugin should be updated accordingly. > Cannot specify additional classpath entries in jar manifest when using > addClasspath > --- > > Key: MJAR-41 > URL: http://jira.codehaus.org/browse/MJAR-41 > Project: Maven 2.x Jar Plugin > Issue Type: Bug >Affects Versions: 2.0, 2.1 > Environment: Maven 2.0.4, maven-jar-plugin 2.0 and 2.1-SNAPSHOT, JDK > 1.5.0_06, Windows XP >Reporter: Fredrik Vraalsen > > The plugin configuration snippet below leads to the generation of an illegal > jar manifest file, as it contains two Class-Path entries. This works in > Maven 1.1b2 by adding the following to project.properties: > maven.jar.manifest.classpath.add=true > maven.jar.classpath=help/ resources/ > For more information, please see > http://www.nabble.com/classpath-in-jar-manifest-t1582724.html > > org.apache.maven.plugins > maven-jar-plugin > > > > true > > > help/ resources/ > > > > -- 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: (MJAR-41) Cannot specify additional classpath entries in jar manifest when using addClasspath
[ http://jira.codehaus.org/browse/MJAR-41?page=all ] Fredrik Vraalsen updated MJAR-41: - Attachment: MJAR-41.patch patch to update maven-archiver dependency to 2.2-SNAPSHOT > Cannot specify additional classpath entries in jar manifest when using > addClasspath > --- > > Key: MJAR-41 > URL: http://jira.codehaus.org/browse/MJAR-41 > Project: Maven 2.x Jar Plugin > Issue Type: Bug >Affects Versions: 2.0, 2.1 > Environment: Maven 2.0.4, maven-jar-plugin 2.0 and 2.1-SNAPSHOT, JDK > 1.5.0_06, Windows XP >Reporter: Fredrik Vraalsen > Attachments: MJAR-41.patch > > > The plugin configuration snippet below leads to the generation of an illegal > jar manifest file, as it contains two Class-Path entries. This works in > Maven 1.1b2 by adding the following to project.properties: > maven.jar.manifest.classpath.add=true > maven.jar.classpath=help/ resources/ > For more information, please see > http://www.nabble.com/classpath-in-jar-manifest-t1582724.html > > org.apache.maven.plugins > maven-jar-plugin > > > > true > > > help/ resources/ > > > > -- 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-1577) dependencyManagement does not work for transitive dependencies
[ http://jira.codehaus.org/browse/MNG-1577?page=comments#action_71899 ] Craig McClanahan commented on MNG-1577: --- This issue messes up the Maven2 based Shale builds too. The bottom line is that it puts the stability of Shale builds totally at the mercy of the creators of downstream dependencies ... there is no current way to override those settings and say "darn it ... I don't care *what* you say, use *this* version of the "foo" depency.". > dependencyManagement does not work for transitive dependencies > -- > > Key: MNG-1577 > URL: http://jira.codehaus.org/browse/MNG-1577 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0 >Reporter: Joerg Schaible > Fix For: 2.1 > > > The dependencyManagement does not work for transient dependencies. The > specified version is ignored. > Use case: > Main POM defines commons-digester-1.6 and commons-beanutils-1.7.0, A-SNAPSHOT > and B-SNAPSHOT > Project A is child of Main and depends directly on commons-beanutils (version > inherited from Main) > Project B is child of Main and depends directly on commons-digester (version > inherited from Main) > Project C is child of Main and depends directly on A & B (versions inherited > from Main) > A is compiled and tests are run using commons-beanutils-1.7.0 > B is compiled and tests are run using commons-digester-1.6 and > commons-beanutils-1.6, since digester is dependend on this > C is compiled and tests are run using commons-beanutils-1.7.0 > Integration tests of B did not verify, that B is behaving as expected in this > scenario. B might fail with 1.7.0 and it is not even recognized. > If I add beanutils also as direct dependency to B, it works fine, but then > are transitive dependency useless. It should be possible to define at least > in the dependencyManagement, that the versions of transient dependencies also > defined in the dependencyManagement have priority. > - Jörg -- 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: (MNG-1955) null pointer exception in profile if pluginManagement section exists in pom
[ http://jira.codehaus.org/browse/MNG-1955?page=all ] Maria Odea Ching closed MNG-1955. - Resolution: Fixed Already fixed in svn. When I executed mvn in the attached sample pom using maven-2.0.2, the "null" exception showed up. But when I executed it using maven-2.0.4 and maven-2.1-SNAPSHOT, the "null" exception has already been fixed. > null pointer exception in profile if pluginManagement section exists in pom > --- > > Key: MNG-1955 > URL: http://jira.codehaus.org/browse/MNG-1955 > Project: Maven 2 > Issue Type: Bug > Components: POM >Affects Versions: 2.0.1 > Environment: windows xp, java 1.4 >Reporter: Chris Funk > Assigned To: Maria Odea Ching > Fix For: 2.0.5 > > Attachments: pom.xml > > Time Spent: 3 hours > Remaining Estimate: 0 minutes > > TO TEST simply run mvn projecthelp:effective-pom -Dbark=true with the > attached pom > the attached pom appears to be legal, but complains of a null pointer > exception: > if the plugin management section is removed then the null pointer goes away > and the plugins are added as expected; > here is the trace: > C:\ditech\workspace\barks>mvn projecthelp:effective-pom -Dbark=true > [INFO] Scanning for projects... > [INFO] > - > --- > [ERROR] FATAL ERROR > [INFO] > - > --- > [INFO] null > [INFO] > - > --- > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.project.injection.DefaultProfileInjector.injectPlugi > ns(DefaultProfileInjector.java:147) > at > org.apache.maven.project.injection.DefaultProfileInjector.injectBuild > (DefaultProfileInjector.java:134) > at > org.apache.maven.project.injection.DefaultProfileInjector.inject(Defa > ultProfileInjector.java:80) > at > org.apache.maven.project.DefaultMavenProjectBuilder.injectActiveProfi > les(DefaultMavenProjectBuilder.java:1037) > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D > efaultMavenProjectBuilder.java:838) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave > nProjectBuilder.java:594) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi > le(DefaultMavenProjectBuilder.java:304) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave > nProjectBuilder.java:274) > at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) > at > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.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.main(Launcher.java:375) > [INFO] > - > --- > [INFO] Total time: < 1 second > [INFO] Finished at: Wed Jan 11 16:26:16 MST 2006 > [INFO] Final Memory: 1M/2M > [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] Closed: (MJAR-41) Cannot specify additional classpath entries in jar manifest when using addClasspath
[ http://jira.codehaus.org/browse/MJAR-41?page=all ] Emmanuel Venisse closed MJAR-41. Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 2.1 Applied. Thanks > Cannot specify additional classpath entries in jar manifest when using > addClasspath > --- > > Key: MJAR-41 > URL: http://jira.codehaus.org/browse/MJAR-41 > Project: Maven 2.x Jar Plugin > Issue Type: Bug >Affects Versions: 2.0, 2.1 > Environment: Maven 2.0.4, maven-jar-plugin 2.0 and 2.1-SNAPSHOT, JDK > 1.5.0_06, Windows XP >Reporter: Fredrik Vraalsen > Assigned To: Emmanuel Venisse > Fix For: 2.1 > > Attachments: MJAR-41.patch > > > The plugin configuration snippet below leads to the generation of an illegal > jar manifest file, as it contains two Class-Path entries. This works in > Maven 1.1b2 by adding the following to project.properties: > maven.jar.manifest.classpath.add=true > maven.jar.classpath=help/ resources/ > For more information, please see > http://www.nabble.com/classpath-in-jar-manifest-t1582724.html > > org.apache.maven.plugins > maven-jar-plugin > > > > true > > > help/ resources/ > > > > -- 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
