[jira] Commented: (MNG-3584) possible new memory leak in Maven 2.0.9
[ http://jira.codehaus.org/browse/MNG-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135355#action_135355 ] Brett Porter commented on MNG-3584: --- I wonder if the plexus-utils upgrade is related? > possible new memory leak in Maven 2.0.9 > --- > > Key: MNG-3584 > URL: http://jira.codehaus.org/browse/MNG-3584 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0.9 >Reporter: Brett Porter > Fix For: 2.0.10 > > > see thread: > http://mail-archives.apache.org/mod_mbox/maven-users/200805.mbox/[EMAIL > PROTECTED] > There seems to be some evidence of a change in 2.0.9 that has increased > memory consumption. -- 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: (MNG-3584) possible new memory leak in Maven 2.0.9
[ http://jira.codehaus.org/browse/MNG-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3584: -- Fix Version/s: 2.0.10 > possible new memory leak in Maven 2.0.9 > --- > > Key: MNG-3584 > URL: http://jira.codehaus.org/browse/MNG-3584 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0.9 >Reporter: Brett Porter > Fix For: 2.0.10 > > > see thread: > http://mail-archives.apache.org/mod_mbox/maven-users/200805.mbox/[EMAIL > PROTECTED] > There seems to be some evidence of a change in 2.0.9 that has increased > memory consumption. -- 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: (MDOCCK-10) Use proper file encoding when checking site descriptor
[
http://jira.codehaus.org/browse/MDOCCK-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MDOCCK-10.
-
Assignee: Dennis Lundberg
Resolution: Fixed
Fix Version/s: 1.0-beta-3
Fixed in r657785.
> Use proper file encoding when checking site descriptor
> --
>
> Key: MDOCCK-10
> URL: http://jira.codehaus.org/browse/MDOCCK-10
> Project: Maven 2.x Documentation Checker Plugin
> Issue Type: Bug
>Affects Versions: 1.0-beta-2
>Reporter: Benjamin Bentmann
>Assignee: Dennis Lundberg
> Fix For: 1.0-beta-3
>
>
> This is not working reliably:
> {code:java}
> String siteHtml = FileUtils.fileRead(
> siteXml.getAbsolutePath() );
> {code}
> See also [Common
> Bugs|http://www.nabble.com/Common-Bugs-to14783703s177.html#a15919795].
--
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: (DOXIA-242) Echo macro outputs internal params
[ http://jira.codehaus.org/browse/DOXIA-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-242. --- Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: 1.0-beta-1 > Echo macro outputs internal params > -- > > Key: DOXIA-242 > URL: http://jira.codehaus.org/browse/DOXIA-242 > Project: Maven Doxia > Issue Type: Bug > Components: Core >Affects Versions: 1.0-beta-1 >Reporter: Lukas Theussl >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > > The Apt and XdocParsers are adding some "parser" and "sourceContent" params > to the map of macro parameters (which I think are used only by the TOC > macro), these are output as strings by the echo macro. We either need to > define what macro parameters are reserved for internal use, or find a general > way to distinguish such internal parameters from params passed in from the > source document. -- 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: (MINSTALL-50) provide property filtering on .pom files placed in local repo
[
http://jira.codehaus.org/browse/MINSTALL-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Armbruster updated MINSTALL-50:
--
Attachment: MNG-maven-install.patch
updated version of patch, also resolved properties in pom-type artifacts
> provide property filtering on .pom files placed in local repo
> -
>
> Key: MINSTALL-50
> URL: http://jira.codehaus.org/browse/MINSTALL-50
> Project: Maven 2.x Install Plugin
> Issue Type: New Feature
>Affects Versions: 2.3
> Environment: independent
>Reporter: Stefan Armbruster
> Attachments: MNG-maven-install.patch, MNG-maven-install.patch
>
>
> When maven installs an artifact, it's pom is also copied into the artifact's
> directory. Unfortunately, if the pom contains a property reference (e.g.
> ${myprop}), this will not be replaced upon copying the pom file.
> I've created a patch for the install plugin that switches on property
> filtering by setting a mojo parameter "filteringEnabled". Since this defaults
> to "false", backward compatibility is kept 100%.
> Some implementation notes:
> * the dirty work is done in FilteredProjectArtifactMetadata.java, the
> property resolution code has been inspired by ResourcesMojo.
> * I've added a unit test, that replaces ${basedir} with the value of a system
> property.
> * since "svn diff" does not handle binary files,
> src/test/resources/unit/basic-install-test-with-filtering/target/maven-install-test-1.0-SNAPSHOT.jar
> is not included in the patch. This file is the same as
> src/test/resources/unit/basic-install-test/target/maven-install-test-1.0-SNAPSHOT.jar
> Since my knowledge of Maven API is more than limited, there might be a more
> elegant way to provide this feature ... but it works! I'd be happy to see
> this in a future release of 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] Issue Comment Edited: (MINSTALL-50) provide property filtering on .pom files placed in local repo
[
http://jira.codehaus.org/browse/MINSTALL-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135379#action_135379
]
darthvader edited comment on MINSTALL-50 at 5/19/08 8:15 AM:
Uploaded a updated version of patch, please use only the latest one. Following
Samuel's request, property resolution also occurs in pom-type artifacts.
was (Author: darthvader):
updated version of patch, also resolved properties in pom-type artifacts
> provide property filtering on .pom files placed in local repo
> -
>
> Key: MINSTALL-50
> URL: http://jira.codehaus.org/browse/MINSTALL-50
> Project: Maven 2.x Install Plugin
> Issue Type: New Feature
>Affects Versions: 2.3
> Environment: independent
>Reporter: Stefan Armbruster
> Attachments: MNG-maven-install.patch, MNG-maven-install.patch
>
>
> When maven installs an artifact, it's pom is also copied into the artifact's
> directory. Unfortunately, if the pom contains a property reference (e.g.
> ${myprop}), this will not be replaced upon copying the pom file.
> I've created a patch for the install plugin that switches on property
> filtering by setting a mojo parameter "filteringEnabled". Since this defaults
> to "false", backward compatibility is kept 100%.
> Some implementation notes:
> * the dirty work is done in FilteredProjectArtifactMetadata.java, the
> property resolution code has been inspired by ResourcesMojo.
> * I've added a unit test, that replaces ${basedir} with the value of a system
> property.
> * since "svn diff" does not handle binary files,
> src/test/resources/unit/basic-install-test-with-filtering/target/maven-install-test-1.0-SNAPSHOT.jar
> is not included in the patch. This file is the same as
> src/test/resources/unit/basic-install-test/target/maven-install-test-1.0-SNAPSHOT.jar
> Since my knowledge of Maven API is more than limited, there might be a more
> elegant way to provide this feature ... but it works! I'd be happy to see
> this in a future release of 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] Commented: (MSITE-262) site.xml not inherited if build run from parent
[ http://jira.codehaus.org/browse/MSITE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135384#action_135384 ] Martin Burger commented on MSITE-262: - Duplicate of MSITE-293 and MSITE-297? I have similar problems with 2.0-beta-6 and current 2.0-beta-7-SNAPSHOT from SVN (Revision: 657789). In 2.0-beta-5 the children's site.xml is respected, but in the other versions it is completely ignored: All menus defined in parent POM are shown in submodules (but should not). Furthermore, all other tags like bannerLeft and poweredBy are not overwritable in submodule's POM. > site.xml not inherited if build run from parent > --- > > Key: MSITE-262 > URL: http://jira.codehaus.org/browse/MSITE-262 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Cameron Jones > Attachments: MSITE-262.zip > > > I've seen that the site.xml is not being inherited in a module when the build > is run from the parent - when run from the module itself the inheritance > works correctly. -- 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-293) Submodule inherit menu but this should not happend
[ http://jira.codehaus.org/browse/MSITE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135385#action_135385 ] Martin Burger commented on MSITE-293: - Duplicate of MSITE-262 and MSITE-297? I have similar problems with 2.0-beta-6 and current 2.0-beta-7-SNAPSHOT from SVN (Revision: 657789). In 2.0-beta-5 the children's site.xml is respected, but in the other versions it is completely ignored: All menus defined in parent POM are shown in submodules (but should not). Furthermore, all other tags like bannerLeft and poweredBy are not overwritable in submodule's POM. > Submodule inherit menu but this should not happend > -- > > Key: MSITE-293 > URL: http://jira.codehaus.org/browse/MSITE-293 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 > Environment: maven 2.0.8 > jdk 1.6 > windows >Reporter: Andreas Höhmann >Priority: Critical > > Projectstructur: > modul > | pom.xml > | src/site/site.xml > | src/site/xdoc/index.xml > +-- submodul 1 > | pom.xml > | src/site/xdoc/index.xml > +-- submodul 2 > | pom.xml > | src/site/xdoc/index.xml > modul :: site.xml > ... > > > > > > > > > > > > > >href="http://lp2p067c:82/maven2/repositories/"; /> > > > > > > ... > after "mvn clean install site" each submodules has a menu "Maven" ... but i > want this only for the "main-modul". > whats wrong? > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html > ... Inheritance ... "By default, only the basic settings are inherited. From > the body, only the links are inherited, and these accumulate to contain all > the parents' site descriptor links." -- 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-297) Child site.xml not used from parent + inheritance
[ http://jira.codehaus.org/browse/MSITE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135386#action_135386 ] Martin Burger commented on MSITE-297: - Duplicate of MSITE-262 and MSITE-293? I have similar problems with 2.0-beta-6 and current 2.0-beta-7-SNAPSHOT from SVN (Revision: 657789). In 2.0-beta-5 the children's site.xml is respected, but in the other versions it is completely ignored: All menus defined in parent POM are shown in submodules (but should not). Furthermore, all other tags like bannerLeft and poweredBy are not overwritable in submodule's POM. > Child site.xml not used from parent + inheritance > - > > Key: MSITE-297 > URL: http://jira.codehaus.org/browse/MSITE-297 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: multi module >Affects Versions: 2.0-beta-6 >Reporter: Ramon Havermans > > When using a parent child project building from the parent, the child > site.xml is not used. Instead I get the parent lay-out with menu's I don't > want and links that 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] Created: (MNG-3585) nonProxyHosts separator is wrong in the default settings.xml
nonProxyHosts separator is wrong in the default settings.xml Key: MNG-3585 URL: http://jira.codehaus.org/browse/MNG-3585 Project: Maven 2 Issue Type: Bug Components: Documentation: General Environment: Maven 2.0.8 and 2.0.9 Reporter: Matthieu Lux In the default settings.xml of the Maven package, the example for proxy configuration contain this : The separator for nonProxyHosts is wrong, it must be a "|". It is defined here : http://maven.apache.org/ref/2.0.8/maven-settings/settings.html#class_proxy -- 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-293) Submodule inherit menu but this should not happend
[ http://jira.codehaus.org/browse/MSITE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135389#action_135389 ] Michael Osipov commented on MSITE-293: -- Martin, downgrade to beta-5 same as I did! > Submodule inherit menu but this should not happend > -- > > Key: MSITE-293 > URL: http://jira.codehaus.org/browse/MSITE-293 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 > Environment: maven 2.0.8 > jdk 1.6 > windows >Reporter: Andreas Höhmann >Priority: Critical > > Projectstructur: > modul > | pom.xml > | src/site/site.xml > | src/site/xdoc/index.xml > +-- submodul 1 > | pom.xml > | src/site/xdoc/index.xml > +-- submodul 2 > | pom.xml > | src/site/xdoc/index.xml > modul :: site.xml > ... > > > > > > > > > > > > > >href="http://lp2p067c:82/maven2/repositories/"; /> > > > > > > ... > after "mvn clean install site" each submodules has a menu "Maven" ... but i > want this only for the "main-modul". > whats wrong? > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html > ... Inheritance ... "By default, only the basic settings are inherited. From > the body, only the links are inherited, and these accumulate to contain all > the parents' site descriptor links." -- 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: (MSITE-262) site.xml not inherited if build run from parent
[ http://jira.codehaus.org/browse/MSITE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MSITE-262: Component/s: inheritance > site.xml not inherited if build run from parent > --- > > Key: MSITE-262 > URL: http://jira.codehaus.org/browse/MSITE-262 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: inheritance >Affects Versions: 2.0-beta-6 >Reporter: Cameron Jones > Attachments: MSITE-262.zip > > > I've seen that the site.xml is not being inherited in a module when the build > is run from the parent - when run from the module itself the inheritance > works correctly. -- 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: (MSHADE-23) ${basedir} is wrong after running shade plugin
[
http://jira.codehaus.org/browse/MSHADE-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135390#action_135390
]
Max Bowsher commented on MSHADE-23:
---
I found this in another context (shade+eclipse), and mused about it on #maven:
Apr 22 14:53:53 I've found a bit of an odd bug. I ran "mvn install
eclipse:eclipse" in a project using the shade plugin and the eclipse files were
placed into the target/ directory incorrectly
Apr 22 14:54:11 This is because the shade plugin reset the project's
file.
Apr 22 14:54:20 But I'm not sure where to file the bug
Apr 22 14:54:28 The shade plugin is working as designed
Apr 22 14:55:09 The eclipse plugin is using
project.getFile().getParentFile() to find the dir to write in
Apr 22 14:55:33 This is arguably a bit odd... but this is exactly what
project.getBasedir() does internally too :-(
Apr 22 14:56:16 I guess I could file a MNG bug suggesting that
project.getBasedir() be decoupled from project.getFile(), and a MECLIPSE bug
suggesting that the plugin should use getBasedir().
I never did get around to filing a bug, because of the above-mentioned
difficulties in figuring out which project was actually at fault. I guess the
sad truth is that the shade plugin is playing with undocumented features by
resetting the project's file, and things are breaking as a result. Of course,
I'm not quite sure how else the shade plugin could do its job, so no "fix" is
immediately apparent.
> ${basedir} is wrong after running shade plugin
> --
>
> Key: MSHADE-23
> URL: http://jira.codehaus.org/browse/MSHADE-23
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Environment: Maven version: 2.0.8
> Java version: 1.5.0_06
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Andreas Schouten
>Assignee: Daniel Kulp
>
> After the shade plugin has run, the ${basedir} points to target.
--
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: (MSITE-262) site.xml not inherited if build run from parent
[ http://jira.codehaus.org/browse/MSITE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MSITE-262: Affects Version/s: 2.0-beta-6 > site.xml not inherited if build run from parent > --- > > Key: MSITE-262 > URL: http://jira.codehaus.org/browse/MSITE-262 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: inheritance >Affects Versions: 2.0-beta-6 >Reporter: Cameron Jones > Attachments: MSITE-262.zip > > > I've seen that the site.xml is not being inherited in a module when the build > is run from the parent - when run from the module itself the inheritance > works correctly. -- 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: (MSHADE-23) ${basedir} is wrong after running shade plugin
[
http://jira.codehaus.org/browse/MSHADE-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135392#action_135392
]
Daniel Kulp commented on MSHADE-23:
---
Well, it's partially my fault.In one of the alphas, I moved the dependency
reduced pom into the target directory to make sure it got properly cleaned.
That's what caused this. However, I wanted the reduced pom left there so I
can see it.
The fix is going to be to do that, but then copy it into the basedir, set the
file to delete on exit, and set the project file to that file. Thus, the
reduced pom will still be left in target (for me), but the "runtime" will use
the version in basedir so the paths don't get screwed up. The delete on exit
will make sure the reduced pom is not left in the basedir to keep that
directory clean.
> ${basedir} is wrong after running shade plugin
> --
>
> Key: MSHADE-23
> URL: http://jira.codehaus.org/browse/MSHADE-23
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Environment: Maven version: 2.0.8
> Java version: 1.5.0_06
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Andreas Schouten
>Assignee: Daniel Kulp
>
> After the shade plugin has run, the ${basedir} points to target.
--
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: (MSHADE-23) ${basedir} is wrong after running shade plugin
[
http://jira.codehaus.org/browse/MSHADE-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135394#action_135394
]
Benjamin Bentmann commented on MSHADE-23:
-
A possible short-term solution might be to have the Shade Plugin write the
modified POM always next to the original POM instead of {{target}}. This way,
the base directory would at least stay the same.
bq. I guess the sad truth is that the shade plugin is playing with undocumented
features
If you have a look at
[{{MavenProject}}|http://maven.apache.org/ref/current/maven-project/apidocs/org/apache/maven/project/MavenProject.html],
it's fair to say that quite every non-trivial plugin is using undocumented
features... That somehow frightens me and I hope the day will arive when the
core guys realize that a complex beast like Maven needs a thorough API as its
foundation.
> ${basedir} is wrong after running shade plugin
> --
>
> Key: MSHADE-23
> URL: http://jira.codehaus.org/browse/MSHADE-23
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Environment: Maven version: 2.0.8
> Java version: 1.5.0_06
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Andreas Schouten
>Assignee: Daniel Kulp
>
> After the shade plugin has run, the ${basedir} points to target.
--
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: (MANTTASKS-87) Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a "Error downloading parent pom" error
[ http://jira.codehaus.org/browse/MANTTASKS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135403#action_135403 ] Pino Silvaggio commented on MANTTASKS-87: - Is this sufficient for reopening this bug? > Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml > will cause a "Error downloading parent pom" error > - > > Key: MANTTASKS-87 > URL: http://jira.codehaus.org/browse/MANTTASKS-87 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: POM Integration >Affects Versions: 2.0.7 > Environment: WindowsXP > Ant version 1.7.0 >Reporter: Jeff Campbell >Assignee: Herve Boutemy >Priority: Blocker > Fix For: 2.0.8 > > Attachments: CASE.tar.gz > > > Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml > will cause a "Error downloading parent pom" error. > This WAS NOT a bug with version 2.0.6 of the maven-ant-tasks (new issue to > maven-ant-tasks-2.0.7.jar and still an issue with the latest > maven-ant-tasks-2.0.8-SNAPSHOT.jar (as of the writting of this bug)). > Just to see if I had done something wrong with the pom.xml file I tried to > run a Maven goal against the pom.xml file. I found that if I run "mvn clean" > from this same directory (where the build.xml and pom.xml file is located), > using Maven-2.0.7, I get a build successfull (it was able to find the parent > pom.xml file... so this seems to be isolated to JUST the maven-ant-task not > being able to find the parent pom.xml) > Sample of the pom.xml file > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > intuit.sbconnect > sbclogin > 1.0.3 > SBCLogin > > > mygroup > CommonPOM > 1.0.2 > > > > > myothergroup > myartifact > 1.0 > > > > Line in Ant build.xml file that causes the error: > > Error that occurs when this line is executed in ant: > Error downloading parent pom: Missing: > -- > 1) mygroup:CommonPOM:pom:1.0.2 > Path to dependency: > 1) unspecified:unspecified:jar:0.0 > 2) mygroup:CommonPOM:pom:1.0.2 > -- > 1 required artifact is missing. > for artifact: > unspecified:unspecified:jar:0.0 > from the specified remote repositories: > central (http://repo1.maven.org/maven2) -- 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] Work started: (MSHADE-23) ${basedir} is wrong after running shade plugin
[
http://jira.codehaus.org/browse/MSHADE-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MSHADE-23 started by Daniel Kulp.
> ${basedir} is wrong after running shade plugin
> --
>
> Key: MSHADE-23
> URL: http://jira.codehaus.org/browse/MSHADE-23
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Environment: Maven version: 2.0.8
> Java version: 1.5.0_06
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Andreas Schouten
>Assignee: Daniel Kulp
> Fix For: 1.1
>
>
> After the shade plugin has run, the ${basedir} points to target.
--
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-167) Include parent poms in the dependency tree.
Include parent poms in the dependency tree. --- Key: MDEP-167 URL: http://jira.codehaus.org/browse/MDEP-167 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: tree Reporter: Paul Gier Assignee: Brian Fox There should be a way to show parent poms in the dependency tree. The parent poms of the current project and the dependency projects are downloaded during a build just like transitive dependencies. It would be helpful in some cases to be able to see where these poms are in the tree. -- 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: (MSHADE-23) ${basedir} is wrong after running shade plugin
[
http://jira.codehaus.org/browse/MSHADE-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp closed MSHADE-23.
-
Resolution: Fixed
Fix Version/s: 1.1
> ${basedir} is wrong after running shade plugin
> --
>
> Key: MSHADE-23
> URL: http://jira.codehaus.org/browse/MSHADE-23
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Environment: Maven version: 2.0.8
> Java version: 1.5.0_06
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Andreas Schouten
>Assignee: Daniel Kulp
> Fix For: 1.1
>
>
> After the shade plugin has run, the ${basedir} points to target.
--
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] Work stopped: (MSHADE-23) ${basedir} is wrong after running shade plugin
[
http://jira.codehaus.org/browse/MSHADE-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MSHADE-23 stopped by Daniel Kulp.
> ${basedir} is wrong after running shade plugin
> --
>
> Key: MSHADE-23
> URL: http://jira.codehaus.org/browse/MSHADE-23
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Environment: Maven version: 2.0.8
> Java version: 1.5.0_06
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Andreas Schouten
>Assignee: Daniel Kulp
> Fix For: 1.1
>
>
> After the shade plugin has run, the ${basedir} points to target.
--
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: (MSHADE-31) When promoteTransitiveDependencies=true, all are stripped from the dependency-reduced-pom
[ http://jira.codehaus.org/browse/MSHADE-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp closed MSHADE-31. - Resolution: Fixed Fix Version/s: 1.1 > When promoteTransitiveDependencies=true, all are stripped from > the dependency-reduced-pom > -- > > Key: MSHADE-31 > URL: http://jira.codehaus.org/browse/MSHADE-31 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.0.1 > Environment: Maven 2.0.9, Linux. >Reporter: Max Bowsher >Assignee: Daniel Kulp > Fix For: 1.1 > > Attachments: pom.xml > > > When promoteTransitiveDependencies=true, all are stripped from > the dependency-reduced-pom. -- 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-2040) rsync_ssh request for domdrides.sourceforge.net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135427#action_135427 ] James Carman commented on MAVENUPLOAD-2040: --- What is the normal turn-around time on these things? I'm not complaining. I was just getting ready to give a code demo to someone and I need to tell them how to get the code if this isn't set up. > rsync_ssh request for domdrides.sourceforge.net > --- > > Key: MAVENUPLOAD-2040 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2040 > Project: maven-upload-requests > Issue Type: Wish >Reporter: James Carman > > "org.domdrides","[EMAIL > PROTECTED]:/home/groups/d/do/domdrides/htdocs/m2repo/releases","rsync_ssh","James > Carman","[EMAIL PROTECTED]",, -- 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: (MINSTALL-52) install:install-file should default to a pom file found in the jar if available
install:install-file should default to a pom file found in the jar if available --- Key: MINSTALL-52 URL: http://jira.codehaus.org/browse/MINSTALL-52 Project: Maven 2.x Install Plugin Issue Type: New Feature Affects Versions: 2.1 Reporter: David Smiley If I do mvn install:install-file -Dfile=foo.jar then the plugin should attempt to see if this jar contains a pom.xml as a fallback since I didn't specify such information on the command line. In the case of getting a plugin from the web such as here: http://code.google.com/p/maven-overview-plugin/ this would be really nice. -- 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-3586) jaxws mojo wsgen failure with maven 2.1
jaxws mojo wsgen failure with maven 2.1
Key: MNG-3586
URL: http://jira.codehaus.org/browse/MNG-3586
Project: Maven 2
Issue Type: Bug
Components: Embedding
Affects Versions: 2.1
Environment: Windows XP / Java 5 or 6
Reporter: Henri Gomez
Attachments: sample-wsgen.zip
I can build jar projects using the jaxws wsgen mojo (1.9) under maven
2.0.x but it failed under m2eclipse (0.9.3) when using maven 2.1
embedded (it works if I switch m2eclipse to use the maven 2.0.9 on my
system).
I tried with various JVM (Sun and IBM 5 and 6) but still got the
problem with maven 2.1 embedded (maven 2.1-620417 and 2.1-655675):
error is :
>From file: C:\workspace\xxx-er-go\pom.xml
Reason: Failed to execute wsgen
java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174)
at
org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at com.sun.tools.ws.WsGen.doMain(WsGen.java:69)
at
org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:91)
at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:577)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
at
org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
at
org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:903)
at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
Any idea or fixes ?
my pom.xml wsgen is standard :
maven-compiler-plugin
1.5
1.5
compile
compile
initialize
org.codehaus.mojo
jaxws-maven-plugin
go-wsgen
wsgen
generate-sources
${project.build.directory}/classes/com/mycorp/service/resources/wsdl
com.mycorp.service.MyService
true
false
[jira] Closed: (SCM-356) clearcase implementation does not allow id of more than 8 characters.
[ http://jira.codehaus.org/browse/SCM-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed SCM-356. Assignee: Emmanuel Venisse Resolution: Fixed Fixed. > clearcase implementation does not allow id of more than 8 characters. > - > > Key: SCM-356 > URL: http://jira.codehaus.org/browse/SCM-356 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-clearcase >Affects Versions: 1.0 > Environment: OS : Windows and LInux Suse > Hardware : x86 >Reporter: Jean-Philippe Hautin >Assignee: Emmanuel Venisse >Priority: Critical > Fix For: 1.1 > > Attachments: maven-scm-provider-clearcase-SCM-356.patch > > > developer ID are not limited in clearcase. > So, we are used to use the standard pattern _ > But when using changelog report, we got an empty developer activity report. > Looking at the source code, I see that the the arguments of the cleartool > command generated force the maximum length of 8 characters. > In the class ClearCaseChangeLogCommand, line 114, we can see that the > cleartool argument is : > "USER:%-8.8u\\n" > I think it should be more like : > "USER:%u\\n" -- 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: (ARCHETYPE-171) maven-archetype-quickstart:1.0 is not configured
maven-archetype-quickstart:1.0 is not configured Key: ARCHETYPE-171 URL: http://jira.codehaus.org/browse/ARCHETYPE-171 Project: Maven Archetype Issue Type: Bug Components: Plugin Affects Versions: 2.0-alpha-3 Environment: mvn 2.0.9 jdk 1.7.0 Reporter: Andreas Höhmann Priority: Critical [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:generate] (aggregator-style) [INFO] [INFO] Preparing archetype:generate [INFO] No goals needed for project - skipping [INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus .velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on => 'false'. [INFO] Setting property: resource.loader => 'classpath'. [INFO] Setting property: resource.manager.logwhenfound => 'false'. [INFO] [archetype:generate] [INFO] Generating project in Batch mode [INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven. archetypes:maven-archetype-quickstart:1.0) [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] : org.apache.maven.archetype.exception.ArchetypeNotConfigured: Archetype org.apache.maven.archetypes:maven-archetype-quickstart:1.0 is not configured Archetype org.apache.maven.archetypes:maven-archetype-quickstart:1.0 is not conf igured Archetype org.apache.maven.archetypes:maven-archetype-quickstart:1.0 is not conf igured [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Mon May 19 22:48:34 CEST 2008 [INFO] Final Memory: 8M/15M [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] Commented: (MANTTASKS-87) Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a "Error downloading parent pom" error
[ http://jira.codehaus.org/browse/MANTTASKS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135438#action_135438 ] Herve Boutemy commented on MANTTASKS-87: I checked the testcase: I have the same output. But this message is only a warning, and nothing blocks the build to go further. Is there an tangible impact of this message on your build, or only the message is causing some questions? > Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml > will cause a "Error downloading parent pom" error > - > > Key: MANTTASKS-87 > URL: http://jira.codehaus.org/browse/MANTTASKS-87 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: POM Integration >Affects Versions: 2.0.7 > Environment: WindowsXP > Ant version 1.7.0 >Reporter: Jeff Campbell >Assignee: Herve Boutemy >Priority: Blocker > Fix For: 2.0.8 > > Attachments: CASE.tar.gz > > > Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml > will cause a "Error downloading parent pom" error. > This WAS NOT a bug with version 2.0.6 of the maven-ant-tasks (new issue to > maven-ant-tasks-2.0.7.jar and still an issue with the latest > maven-ant-tasks-2.0.8-SNAPSHOT.jar (as of the writting of this bug)). > Just to see if I had done something wrong with the pom.xml file I tried to > run a Maven goal against the pom.xml file. I found that if I run "mvn clean" > from this same directory (where the build.xml and pom.xml file is located), > using Maven-2.0.7, I get a build successfull (it was able to find the parent > pom.xml file... so this seems to be isolated to JUST the maven-ant-task not > being able to find the parent pom.xml) > Sample of the pom.xml file > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > intuit.sbconnect > sbclogin > 1.0.3 > SBCLogin > > > mygroup > CommonPOM > 1.0.2 > > > > > myothergroup > myartifact > 1.0 > > > > Line in Ant build.xml file that causes the error: > > Error that occurs when this line is executed in ant: > Error downloading parent pom: Missing: > -- > 1) mygroup:CommonPOM:pom:1.0.2 > Path to dependency: > 1) unspecified:unspecified:jar:0.0 > 2) mygroup:CommonPOM:pom:1.0.2 > -- > 1 required artifact is missing. > for artifact: > unspecified:unspecified:jar:0.0 > from the specified remote repositories: > central (http://repo1.maven.org/maven2) -- 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: (MCOMPILER-30) Compiler fork executable fails when the path has spaces
[
http://jira.codehaus.org/browse/MCOMPILER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135447#action_135447
]
Greg Hengeli commented on MCOMPILER-30:
---
I too am encountering this error. As (what I consider) a temporary solution,
you can declare the dependency on plexus-utils to be version 1.5.1 in the
plugin. My question is why isn't this version of the dependency declared in
the maven-compiler-plugin's pom?! Is there another solution I am missing?
org.apache.maven.plugins
maven-compiler-plugin
2.0.2
1.5
1.5
true
${JAVA5_HOME}/bin/javac
1.5
org.codehaus.plexus
plexus-utils
1.5.1
> Compiler fork executable fails when the path has spaces
> ---
>
> Key: MCOMPILER-30
> URL: http://jira.codehaus.org/browse/MCOMPILER-30
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 2.0.1
>Reporter: Carlos Sanchez
>Assignee: Carlos Sanchez
> Fix For: 2.0.2
>
>
> JAVA_1_3_HOME=C:\Program Files\Java\jdk1.3.1_18
>
> maven-compiler-plugin
>
> true
> 1.3
> ${JAVA_1_3_HOME}/bin/javac
>
>
> Fails with
> Failure executing javac, but could not parse the error:
> 'C:\Program' is not recognized as an internal or external command,
> operable program or batch file.
--
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: (MCOMPILER-74) build failure when executable path contains spaces
build failure when executable path contains spaces -- Key: MCOMPILER-74 URL: http://jira.codehaus.org/browse/MCOMPILER-74 Project: Maven 2.x Compiler Plugin Issue Type: Bug Affects Versions: 2.0.2, 2.1 Environment: windows xp, maven 2.0.9 Reporter: Greg Hengeli When compiling a project with an executable that has spaces in its path, a build failure is encountered. This can be reproduced by following the exact example given on the Maven Compiler Plugin home page (http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html) This seems to be already mentioned in MCOMPILER-30 (which is closed) but there is a comment after it was closed stating it still doesn't work. One potential solution I have found is to use version 1.5.1 of plexus-utils - should this be updated in the maven-compiler-plugin's pom or is there a better solution? [INFO] - [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure Failure executing javac, but could not parse the error: 'C:\Program' is not recognized as an internal or external command, operable program or batch file. Failure executing javac, but could not parse the error: 'C:\Program' is not recognized as an internal or external command, operable program or batch file. [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Compilation failure Failure executing javac, but could not parse the error: 'C:\Program' is not recognized as an internal or external command, operable program or batch file. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579) 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:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) 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.CompilationFailureException: Compilation failure Failure executing javac, but could not parse the error: 'C:\Program' is not recognized as an internal or external command, operable program or batch file. at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:562) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:115) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) ... 17 more [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Mon May 19 16:54:59 CDT 2008 [INFO] Final Memory: 6M/19M [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: (MNG-3587) Strange warnings while building a project
Strange warnings while building a project - Key: MNG-3587 URL: http://jira.codehaus.org/browse/MNG-3587 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.9 Reporter: Seva Popov Attachments: maven-warning.txt We've switched from Maven 2.0.7 to Maven 2.0.9 and started observing strange warnings happening in different contexts in our builds: Example: [WARNING] Attempting to build MavenProject instance for Artifact (com.tvworks.tva.maven.plugins:maven-license-plugin:3.3-20080508.052638-16) of type: maven-plugin; constructing POM artifact instead. [WARNING] Attempting to build MavenProject instance for Artifact (com.tvworks.tva.common:tva-common-logging:3.3-20080513.211757-62) of type: jar; constructing POM artifact instead. More details in this thread: http://www.mail-archive.com/[EMAIL PROTECTED]/msg85248.html -- 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: (WAGON-109) Refactor Wagon HTTP and Wagon WebDav
[ http://jira.codehaus.org/browse/WAGON-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135451#action_135451 ] Brett Porter commented on WAGON-109: I've added my vote to https://issues.apache.org/jira/browse/JCR-1310, and will look at just importing the required classes from xerces since it only uses it for serialization > Refactor Wagon HTTP and Wagon WebDav > > > Key: WAGON-109 > URL: http://jira.codehaus.org/browse/WAGON-109 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-http, wagon-webdav >Reporter: James William Dumay >Assignee: Brett Porter > Fix For: 1.0-beta-3 > > Attachments: webdav-http-dav-refactor.patch, > webdav-http-dav-refactor.patch, webdav-http-dav-refactor.patch > > > This patch includes the following: > * Webdav wagon is now using Jackrabbits webdav client implementation over the > Apache Slide client library (now defunct) > * Inclusion of a commons HttpClient abstract wagon for code reuse between > Wagon Http and Wagon Dav. > * Improved consistency of http parameters across Wagon HTTP and Wagon Webdav > methods -- 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-2066) rsync EasyMock to maven central repository
rsync EasyMock to maven central repository -- Key: MAVENUPLOAD-2066 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2066 Project: maven-upload-requests Issue Type: Task Reporter: Henri Tremblay Please configure the rsync with the easymock repository. The rsync line: "org.easymock","[EMAIL PROTECTED]:/home/groups/e/ea/easymock/htdocs/maven/repository","rsync_ssh","Henri Tremblay","[EMAIL PROTECTED]",, The question might be dumb but do I need any particular rights on the repository? (a+r?) And if I remove something from my repo, will it disappear from the central repository? Lastly, can I synchronise projects with another group id? (I'm thinking about Objenesis here) -- 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: (MANTTASKS-87) Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a "Error downloading parent pom" error
[ http://jira.codehaus.org/browse/MANTTASKS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135452#action_135452 ] Pino Silvaggio commented on MANTTASKS-87: - In this case it's a warning but when important info is contained in parent like properties the build will fail. This case is just to show that the parent pom is not used. As I stated, it differ from maven behavior. The problem seems to be the model constructed with the XML (pom) reader which doesn't take into account settings.xml. I patched our version here by constructing a Pom object with the model info and it now works great. However do not think it's the proper way of fixing this. So I am not going to submit the patch. Since I have limited time to put on this. But the question is why use a different way of dealing with poms when it's a parent? I mean there's a Pom class but here we use another type which in principle should represent the same thing... > Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml > will cause a "Error downloading parent pom" error > - > > Key: MANTTASKS-87 > URL: http://jira.codehaus.org/browse/MANTTASKS-87 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: POM Integration >Affects Versions: 2.0.7 > Environment: WindowsXP > Ant version 1.7.0 >Reporter: Jeff Campbell >Assignee: Herve Boutemy >Priority: Blocker > Fix For: 2.0.8 > > Attachments: CASE.tar.gz > > > Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml > will cause a "Error downloading parent pom" error. > This WAS NOT a bug with version 2.0.6 of the maven-ant-tasks (new issue to > maven-ant-tasks-2.0.7.jar and still an issue with the latest > maven-ant-tasks-2.0.8-SNAPSHOT.jar (as of the writting of this bug)). > Just to see if I had done something wrong with the pom.xml file I tried to > run a Maven goal against the pom.xml file. I found that if I run "mvn clean" > from this same directory (where the build.xml and pom.xml file is located), > using Maven-2.0.7, I get a build successfull (it was able to find the parent > pom.xml file... so this seems to be isolated to JUST the maven-ant-task not > being able to find the parent pom.xml) > Sample of the pom.xml file > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > intuit.sbconnect > sbclogin > 1.0.3 > SBCLogin > > > mygroup > CommonPOM > 1.0.2 > > > > > myothergroup > myartifact > 1.0 > > > > Line in Ant build.xml file that causes the error: > > Error that occurs when this line is executed in ant: > Error downloading parent pom: Missing: > -- > 1) mygroup:CommonPOM:pom:1.0.2 > Path to dependency: > 1) unspecified:unspecified:jar:0.0 > 2) mygroup:CommonPOM:pom:1.0.2 > -- > 1 required artifact is missing. > for artifact: > unspecified:unspecified:jar:0.0 > from the specified remote repositories: > central (http://repo1.maven.org/maven2) -- 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: (MSTAGE-3) The stage plugin only supports copying from http(s) to scp urls
[ http://jira.codehaus.org/browse/MSTAGE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Akolkar updated MSTAGE-3: --- Attachment: MSTAGE-3.patch I discovered this in trying to move a staged release today. The attached patch fixes it for me (I used scpexe:// for the target repo, which fails without the patch and succeeds with the patch). The earlier cast to ScpWagon for the lines in question seems overly restrictive and exclusionary. > The stage plugin only supports copying from http(s) to scp urls > --- > > Key: MSTAGE-3 > URL: http://jira.codehaus.org/browse/MSTAGE-3 > Project: Maven 2.x Stage Plugin > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Maria Odea Ching > Attachments: MSTAGE-3.patch > > -- 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-25) mvn site:deploy and site:stage-deploy ignores server configuration in settings.xml
[ http://jira.codehaus.org/browse/MSITE-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135460#action_135460 ] Rahul Akolkar commented on MSITE-25: Thanks, I can confirm that the 2.0-beta-7-20080419.180515-7 SNAPSHOT works for me. I also tried building the trunk (and that works as well for site-deploy, site:deploy and site:stage-deploy). If someone else can verify soon-ish, that'd be nice. In any case, it'd help a lot to get a new release of the plugin that includes this fix. Given that deploying the site is also part of the default goals of the release plugin, this puts a dent in the ability to cut releases. > mvn site:deploy and site:stage-deploy ignores server configuration in > settings.xml > -- > > Key: MSITE-25 > URL: http://jira.codehaus.org/browse/MSITE-25 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Alan Cabrera >Assignee: Dennis Lundberg >Priority: Critical > Fix For: 2.0-beta-7 > > Attachments: MSITE-25-01.patch, MSITE-25-02.patch, MSITE-25-03.patch, > MSITE-25.sample.pom.xml, MSITE-25.settings.xml.fragment.txt, MSITE-25.txt, > patch-MSITE-25-artifact-manager.diff, patch-MSITE-25-site-plugin.diff > > > mvn site:site ignores parts of my settings.xml: > > livetribe-website > 664 > 775 > > plink > pscp > > livetribe > > It uses the username when ssh but does not invoke plink. > [INFO] [site:deploy] > Using private key: C:\Documents and Settings\adc\.ssh\id_dsa > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Opened > Executing command: ssh -i "C:\Documents and Settings\adc\.ssh\id_dsa" -o > "BatchMode yes" [EMAIL PROTECTED] "mkdir -p > /home/projects/livetribe/public_html/maven/." > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Disconnecting > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Disconnected -- 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: (WAGON-109) Refactor Wagon HTTP and Wagon WebDav
[ http://jira.codehaus.org/browse/WAGON-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-109. -- Resolution: Fixed > Refactor Wagon HTTP and Wagon WebDav > > > Key: WAGON-109 > URL: http://jira.codehaus.org/browse/WAGON-109 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-http, wagon-webdav >Reporter: James William Dumay >Assignee: Brett Porter > Fix For: 1.0-beta-3 > > Attachments: webdav-http-dav-refactor.patch, > webdav-http-dav-refactor.patch, webdav-http-dav-refactor.patch > > > This patch includes the following: > * Webdav wagon is now using Jackrabbits webdav client implementation over the > Apache Slide client library (now defunct) > * Inclusion of a commons HttpClient abstract wagon for code reuse between > Wagon Http and Wagon Dav. > * Improved consistency of http parameters across Wagon HTTP and Wagon Webdav > methods -- 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: (WAGON-104) File handle leak in the WebDavWagon.put method
[ http://jira.codehaus.org/browse/WAGON-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-104. -- Assignee: Brett Porter Resolution: Fixed fixed during WAGON-109 > File handle leak in the WebDavWagon.put method > -- > > Key: WAGON-104 > URL: http://jira.codehaus.org/browse/WAGON-104 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-webdav >Affects Versions: 1.0-beta-2 >Reporter: Kohsuke Kawaguchi >Assignee: Brett Porter > Fix For: 1.0-beta-3 > > > PutInputStream created at line 286 is never closed. (commons-httpclient > doesn't close it, either, at least as of 3.1) > A finally block is needed here to properly dispose the InputStream. This > affects the long-running process like Hudson, and eventually cause the file > descriptor shortage. -- 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-3242) It's not possible to get a property with unescaped & sign for urls
[ http://jira.codehaus.org/browse/MNG-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135465#action_135465 ] Joel Marsden commented on MNG-3242: --- It is possible to work around this issue by using & in the property > It's not possible to get a property with unescaped & sign for urls > -- > > Key: MNG-3242 > URL: http://jira.codehaus.org/browse/MNG-3242 > Project: Maven 2 > Issue Type: Bug > Components: General >Affects Versions: 2.0.6 >Reporter: Nils Eckert > Fix For: 2.0.x > > Attachments: mvntest-20080327.zip > > > I found no way to create a property with a not escaped ampersand (&-sign). > This is needed for a MySQL jdbc-connection String with some connection > variabled and should be filtered in a properties file during compile phase. > It tried to escape it with & This leeds to following error: Project build > error Cannot read project model from interpolating filter of serialized > version. > It is no option to use a double escaping with &. Here I get a & > in my connection url. > I also tried to use a <[CDATA[ ... ]]> with the same problems. It's not > possible to use & sign. And if I use & this escaped tag appears in my > properties file after filtering. -- 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-3242) It's not possible to get a property with unescaped & sign for urls
[ http://jira.codehaus.org/browse/MNG-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135466#action_135466 ] Joel Marsden commented on MNG-3242: --- My comment came out incorrect (due to the html escape!) - it is possible to work around using "& amp;" in the property (no space / quotes) > It's not possible to get a property with unescaped & sign for urls > -- > > Key: MNG-3242 > URL: http://jira.codehaus.org/browse/MNG-3242 > Project: Maven 2 > Issue Type: Bug > Components: General >Affects Versions: 2.0.6 >Reporter: Nils Eckert > Fix For: 2.0.x > > Attachments: mvntest-20080327.zip > > > I found no way to create a property with a not escaped ampersand (&-sign). > This is needed for a MySQL jdbc-connection String with some connection > variabled and should be filtered in a properties file during compile phase. > It tried to escape it with & This leeds to following error: Project build > error Cannot read project model from interpolating filter of serialized > version. > It is no option to use a double escaping with &. Here I get a & > in my connection url. > I also tried to use a <[CDATA[ ... ]]> with the same problems. It's not > possible to use & sign. And if I use & this escaped tag appears in my > properties file after filtering. -- 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-3588) ${maven.repo.local} in settings.xml doesn't work.
${maven.repo.local} in settings.xml doesn't work.
-
Key: MNG-3588
URL: http://jira.codehaus.org/browse/MNG-3588
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.9
Reporter: Marcin Kuthan
Priority: Minor
I can't use ${maven.repo.local} parameter inside settings.xml file. The
parameter is simply ignored.
c:\base_repo_location
my-profile
C:\alternative_repo_location
When I run
"mvn -P my-profile package"
all downloaded artifacts are stored under "c:\base_repo_location" not
"C:\alternative_repo_location".
When I run
"mvn -Dmaven.repo.local=C:\alternative_repo_location package" package
artifacts are stored under "C:\alternative_repo_location" as I expected.
--
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: (WAGON-79) ConcurrentModificationException : TransferEventSupport needs synchronization
[ http://jira.codehaus.org/browse/WAGON-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-79. - Assignee: Brett Porter Resolution: Fixed applied the main patch - I think the thread safety test is problematic due to timing and threading, so we can just retain the primitives. I used the method level syncs from the patch since it would be equivalent to blocks that sync on listeners > ConcurrentModificationException : TransferEventSupport needs synchronization > > > Key: WAGON-79 > URL: http://jira.codehaus.org/browse/WAGON-79 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-provider-api >Affects Versions: 1.0-beta-3 > Environment: archiva Snapshot >Reporter: nicolas de loof >Assignee: Brett Porter > Fix For: 1.0-beta-3 > > Attachments: WAGON-79-testcase.patch, WAGON-79.patch > > > I get some thraead-safety issues with maven archiva : > 2007-04-02 10:11:25,392 [http--1] ERROR [RepositoryServlet]- > "Servlet.service()" pour la servlet RepositoryServlet a généré une exception > java.util.ConcurrentModificationException > at java.util.AbstractList$Itr.checkForComodification(Unknown Source) > at java.util.AbstractList$Itr.next(Unknown Source) > at > org.apache.maven.wagon.events.TransferEventSupport.fireTransferProgress > (TransferEventSupport.java:117) > at > org.apache.maven.wagon.AbstractWagon.fireTransferProgress(AbstractWagon.java:350) > There is a thread-safety issue in Wagon TransferEventSupport > The listeners list is an ArrayList and add/remove/fireEvent methods are not > synchronized. > This requires either synchronization or use of a CopyOnWriteArrayList (java5 > or backport). -- 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-3242) It's not possible to get a property with unescaped & sign for urls
[ http://jira.codehaus.org/browse/MNG-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135468#action_135468 ] Joel Marsden commented on MNG-3242: --- Aasssaargh - third time's a charm - to work around use this: & > It's not possible to get a property with unescaped & sign for urls > -- > > Key: MNG-3242 > URL: http://jira.codehaus.org/browse/MNG-3242 > Project: Maven 2 > Issue Type: Bug > Components: General >Affects Versions: 2.0.6 >Reporter: Nils Eckert > Fix For: 2.0.x > > Attachments: mvntest-20080327.zip > > > I found no way to create a property with a not escaped ampersand (&-sign). > This is needed for a MySQL jdbc-connection String with some connection > variabled and should be filtered in a properties file during compile phase. > It tried to escape it with & This leeds to following error: Project build > error Cannot read project model from interpolating filter of serialized > version. > It is no option to use a double escaping with &. Here I get a & > in my connection url. > I also tried to use a <[CDATA[ ... ]]> with the same problems. It's not > possible to use & sign. And if I use & this escaped tag appears in my > properties file after filtering. -- 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
