[jira] Updated: (MNG-3645) Maven doesn't do strict model validation for POMs in the current reactor
[
http://jira.codehaus.org/browse/MNG-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-3645:
---
Affects Version/s: 2.0.5
2.0.8
> Maven doesn't do strict model validation for POMs in the current reactor
>
>
> Key: MNG-3645
> URL: http://jira.codehaus.org/browse/MNG-3645
> Project: Maven 2
> Issue Type: Bug
> Components: POM, Reactor and workspace
>Affects Versions: 2.0.5, 2.0.8, 2.0.9
>Reporter: John Casey
>Assignee: John Casey
> Fix For: 2.0.10, 2.1.0-M1
>
>
> For example, adding a dependencyManagement section like the following doesn't
> result in a parser/validation error:
> {code:xml}
>
>
> org.group
> foo
> 1
>
>
> {code}
> Hint: It's missing the dependency element to contain the
> groupId/artifactId/version.
> This is probably a duplicate, but if so it looks like the original is buried
> somewhere deep...I can't find it.
--
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-3898) can't generate Maven site: modello fails at xsd generation step due to a Boolean field in model
can't generate Maven site: modello fails at xsd generation step due to a Boolean field in model --- Key: MNG-3898 URL: http://jira.codehaus.org/browse/MNG-3898 Project: Maven 2 Issue Type: Bug Components: Sites & Reporting Affects Versions: 2.0.10 Reporter: Herve Boutemy -- 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-3898) can't generate Maven site: modello fails at xsd generation step due to a Boolean field in model
[ http://jira.codehaus.org/browse/MNG-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-3898: --- Fix Version/s: 2.0.10 > can't generate Maven site: modello fails at xsd generation step due to a > Boolean field in model > --- > > Key: MNG-3898 > URL: http://jira.codehaus.org/browse/MNG-3898 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 2.0.10 >Reporter: Herve Boutemy > Fix For: 2.0.10 > > -- 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-3898) can't generate Maven site: modello fails at xsd generation step due to a Boolean field in model
[ http://jira.codehaus.org/browse/MNG-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-3898. -- Assignee: Herve Boutemy Resolution: Fixed fixed in r726188 > can't generate Maven site: modello fails at xsd generation step due to a > Boolean field in model > --- > > Key: MNG-3898 > URL: http://jira.codehaus.org/browse/MNG-3898 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 2.0.10 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 2.0.10 > > -- 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-296) XML DTD assembly.xsd is obsolete
[ http://jira.codehaus.org/browse/MASSEMBLY-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MASSEMBLY-296. - Assignee: Vincent Siveton Resolution: Fixed I redeployed files from tags to http://maven.apache.org/xsd/ : - assembly-1.0.0.xsd and component-1.0.0.xsd from maven-assembly-plugin-2.1 tag - assembly-1.1.0.xsd and component-1.1.0.xsd from maven-assembly-plugin-2.2-beta-2 tag Apply chmod a+rx, chmod g+w and chmod 664 for each files. Need to sync. > XML DTD assembly.xsd is obsolete > > > Key: MASSEMBLY-296 > URL: http://jira.codehaus.org/browse/MASSEMBLY-296 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-2 > Environment: Files obsolete on http server >Reporter: Jean-Paul GUIGUI >Assignee: Vincent Siveton >Priority: Minor > > The DTD file for the assembly descriptor is not correct. > The http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd and > http://maven.apache.org/xsd/assembly-1.0.0.xsd are dating from 16-Dec-2006 > and are not up to date. > For instance the element is missing from these DTD > files. > It's not convenient when editing the descriptor with an XMLEditor, we are not > able to know the new options and completion. -- 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: (DOXIA-270) Review doxia-converter artefact to respect ASF rules
Review doxia-converter artefact to respect ASF rules Key: DOXIA-270 URL: http://jira.codehaus.org/browse/DOXIA-270 Project: Maven Doxia Issue Type: Bug Affects Versions: 1.0-beta-1 Reporter: Vincent Siveton Priority: Blocker apache-doxia-1.0-SNAPSHOT-jar-with-dependencies.jar contains binary code from dependencies. Verify licenses according http://www.apache.org/legal/3party.html itext MPL icu4j ICU License -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MJAVADOC-223) mvn javadoc:javadoc does not support chinese?
[ http://jira.codehaus.org/browse/MJAVADOC-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-3896 to MJAVADOC-223: - Affects Version/s: (was: 2.0.9) Key: MJAVADOC-223 (was: MNG-3896) Project: Maven 2.x Javadoc Plugin (was: Maven 2) > mvn javadoc:javadoc does not support chinese? > - > > Key: MJAVADOC-223 > URL: http://jira.codehaus.org/browse/MJAVADOC-223 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Reporter: zha zhengyin > Attachments: chinese-version.png > > -- 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: (MJAVADOC-223) mvn javadoc:javadoc does not support chinese?
[ http://jira.codehaus.org/browse/MJAVADOC-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MJAVADOC-223. -- Assignee: Benjamin Bentmann Resolution: Incomplete Please keep in mind that a question along with a screenshot is hardly a bug report. For questions about Maven and its plugins, the [Maven User List|http://maven.apache.org/mail-lists.html] is a better place to go. Your issue sounds like a misconfiguration of file encoding. In particular, check that the Javadoc Plugin's [encoding|http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#encoding] parameter matches the character encoding of your source files and that the Site Plugin's [outputEncoding|http://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#outputEncoding] parameter can handle your character set. > mvn javadoc:javadoc does not support chinese? > - > > Key: MJAVADOC-223 > URL: http://jira.codehaus.org/browse/MJAVADOC-223 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Reporter: zha zhengyin >Assignee: Benjamin Bentmann > Attachments: chinese-version.png > > -- 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-2303) please add to repo1 for automatic syncing
please add to repo1 for automatic syncing - Key: MAVENUPLOAD-2303 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2303 Project: Maven Upload Requests Issue Type: Wish Reporter: jay colson "org.synchronoss","sncrbu...@shell.sourceforge.net/home/groups/c/cp/cpo/htdocs/sf-cpo-releases","rsync_ssh","Jay Colson","jcol...@users.sourceforge.net",, Proof of domain ownership: jay.col...@synchronoss.com (synchronoss.org redrects to .com) maven public key has already been added to the sf user sncrbuild -- 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-3899) Inheritance does not merge extensions with same gid and aid
Inheritance does not merge extensions with same gid and aid
---
Key: MNG-3899
URL: http://jira.codehaus.org/browse/MNG-3899
Project: Maven 2
Issue Type: Bug
Components: Inheritance and Interpolation
Affects Versions: 2.1.0-M1, 2.0.9
Reporter: Benjamin Bentmann
Priority: Minor
Parent POM snippet:
{code:xml}
org.apache.maven.wagon
wagon-webdav
1.0-beta-1
{code}
Child POM snippet:
{code:xml}
org.apache.maven.wagon
wagon-webdav
1.0-beta-2
{code}
Effective child POM:
{code:xml}
org.apache.maven.wagon
wagon-webdav
1.0-beta-2
org.apache.maven.wagon
wagon-webdav
1.0-beta-1
{code}
i.e. there is no conflict resolution and both versions of the extension are
loaded.
--
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-612) Bad checksums for org.codehaus.plexus:plexus-lang:1.1
Bad checksums for org.codehaus.plexus:plexus-lang:1.1
-
Key: MEV-612
URL: http://jira.codehaus.org/browse/MEV-612
Project: Maven Evangelism
Issue Type: Bug
Components: Checksum Failure
Reporter: Benjamin Bentmann
{noformat}
Downloading:
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-lang/1.1/plexus-lang-1.1.pom
2K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'9d8f550e0115aed8be989ee48064e8212b1b7ca5'; remote =
'da39a3ee5e6b4b0d3255bfef95601890afd80709' - RETRYING
Downloading:
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-lang/1.1/plexus-lang-1.1.pom
2K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'9d8f550e0115aed8be989ee48064e8212b1b7ca5'; remote =
'da39a3ee5e6b4b0d3255bfef95601890afd80709' - IGNORING
Downloading:
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-lang/1.1/plexus-lang-1.1.jar
12K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'0fe38d248d8c98518ddf8173d9152c10d0a8be0c'; remote =
'da39a3ee5e6b4b0d3255bfef95601890afd80709' - RETRYING
Downloading:
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-lang/1.1/plexus-lang-1.1.jar
12K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'0fe38d248d8c98518ddf8173d9152c10d0a8be0c'; remote =
'da39a3ee5e6b4b0d3255bfef95601890afd80709' - IGNORING
{noformat}
--
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-3639) Ant 1.7.0 Task not found after upgrading from Maven 2.0.8 to 2.0.9
[ http://jira.codehaus.org/browse/MNG-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-3639: --- Component/s: (was: Ant tasks) Dependencies Class Loading > Ant 1.7.0 Task not found after upgrading from Maven 2.0.8 to 2.0.9 > -- > > Key: MNG-3639 > URL: http://jira.codehaus.org/browse/MNG-3639 > Project: Maven 2 > Issue Type: Bug > Components: Class Loading, Dependencies >Affects Versions: 2.0.8 >Reporter: Niall Pemberton >Assignee: John Casey > Fix For: 2.0.10, 2.1.0-M1 > > Attachments: mvn-2.0.8-output.txt, mvn-2.0.9-output.txt, pom.xml > > > Apache Commons has a maven ant plugin (called commons-build-plugin[1]) which > has a dependency on Ant 1.7.0 and uses the loadresource task (which was added > to Ant in version 1.7.0). The plugin works fine for maven 2.0.8, but after > upgrading to 2.0.9 fails with the message "Could not create task or type of > type: loadresource." (see attached output). > This has been raised on the maven dev list in the following thread: > http://markmail.org/message/tv37c37fjyzx6l6k > I am attaching a simple pom.xml that reproduces this problem with the > following command: > mvn commons:jira-page > (N.B. create either a "xdocs" or "src/xdoc" directory in the project) > [1] > http://svn.apache.org/viewvc/commons/proper/commons-build-plugin/tags/commons-build-plugin-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: (MNG-3899) Inheritance does not merge extensions with same gid and aid
[
http://jira.codehaus.org/browse/MNG-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-3899.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.1.0-M2
2.0.11
Fixed in [r726244|http://svn.apache.org/viewvc?view=rev&revision=726244] and
[r726247|http://svn.apache.org/viewvc?view=rev&revision=726247], respectively.
> Inheritance does not merge extensions with same gid and aid
> ---
>
> Key: MNG-3899
> URL: http://jira.codehaus.org/browse/MNG-3899
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 2.0.9, 2.1.0-M1
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 2.0.11, 2.1.0-M2
>
>
> Parent POM snippet:
> {code:xml}
>
>
> org.apache.maven.wagon
> wagon-webdav
> 1.0-beta-1
>
>
> {code}
> Child POM snippet:
> {code:xml}
>
>
> org.apache.maven.wagon
> wagon-webdav
> 1.0-beta-2
>
>
> {code}
> Effective child POM:
> {code:xml}
>
>
> org.apache.maven.wagon
> wagon-webdav
> 1.0-beta-2
>
>
> org.apache.maven.wagon
> wagon-webdav
> 1.0-beta-1
>
>
> {code}
> i.e. there is no conflict resolution and both versions of the extension are
> loaded.
--
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-3086) NullPointerException in ResolutionNode.getTrail(ResolutionNode.java:136)
[ http://jira.codehaus.org/browse/MNG-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-3086: --- Component/s: (was: Ant tasks) Dependencies > NullPointerException in ResolutionNode.getTrail(ResolutionNode.java:136) > > > Key: MNG-3086 > URL: http://jira.codehaus.org/browse/MNG-3086 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.7 >Reporter: Thomas Leonard >Assignee: Brian Fox > Fix For: 2.0.9 > > > After upgrading from 2.0.6 to 2.0.7, our build fails with: > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.artifact.resolver.ResolutionNode.getTrail(ResolutionNode.java:136) > at > org.apache.maven.artifact.resolver.ResolutionNode.filterTrail(ResolutionNode.java:211) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:89) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:284) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272) > at > org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) > 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) > Thanks, -- 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] Moved: (MANTRUN-102) Problem parsing XML in code run using antrun plugin
[ http://jira.codehaus.org/browse/MANTRUN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-2459 to MANTRUN-102: Affects Version/s: (was: 2.0.4) Component/s: (was: Ant tasks) Key: MANTRUN-102 (was: MNG-2459) Project: Maven 2.x Antrun Plugin (was: Maven 2) > Problem parsing XML in code run using antrun plugin > --- > > Key: MANTRUN-102 > URL: http://jira.codehaus.org/browse/MANTRUN-102 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug > Environment: Red Hat Enterprise Linux WS release 4 (Nahant Update 3) > java version "1.5.0_06" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) > Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing) >Reporter: Kris Nuttycombe >Assignee: Carlos Sanchez > Attachments: antrun-log4j-xml-test.tgz > > > I'm not certain whether this is an antrun problem or a log4j problem, but > considering that the same application run from the command line has no > problems, I'm going to point to antrun as the first possible culprit. > This error occurs when I attempt to use the antrun plugin to run a standalone > Java program that is, for deployment, packaged as a jar-with-dependencies jar > using the assembly plugin. I use antrun during development for the purpose of > giving me the benefit of the classpath information from the POM; if there's a > better way of doing this I'd be happy to work around the problem. > The error appears to occur when log4j attempts to parse an XML configuration > file using the DOMConfigurator. It appears that the DocumentBuilderFactory > package name is being prepended with "com.sun." when the application is run > using the antrun plugin. Is there some aspect of Maven or of the antrun > plugin that is altering the XML parsing environment? > [java] javax.xml.parsers.FactoryConfigurationError: Provider > com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl could not > be instantiated: java.lang.NullPointerException > [java] at > org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:180) > [java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:710) > [java] at > org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178) > [java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:84) > [java] at > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) > [java] at org.apache.tools.ant.Task.perform(Task.java:364) > [java] at org.apache.tools.ant.Target.execute(Target.java:341) > [java] at > org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:108) > [java] at > org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83) > [java] at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > [java] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > [java] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488) > [java] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) > [java] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > [java] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > [java] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > [java] at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > [java] at > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > [java] at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [java] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [java] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [java] at java.lang.reflect.Method.invoke(Method.java:585) > [java] at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > [java] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > [java] at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > [java] at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [java] Caused by: javax.xml.parsers.FactoryConfigurationError: Provider > com.sun.org.apache.xerces.internal
[jira] Updated: (MNG-3780) in plugin configuration doesn't override maven-antrun-plugin classpath
[
http://jira.codehaus.org/browse/MNG-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3780:
---
Component/s: (was: Ant tasks)
Plugins and Lifecycle
> in plugin configuration doesn't override maven-antrun-plugin
> classpath
> ---
>
> Key: MNG-3780
> URL: http://jira.codehaus.org/browse/MNG-3780
> Project: Maven 2
> Issue Type: Sub-task
> Components: Plugins and Lifecycle
>Affects Versions: 2.0.7, 2.0.9
> Environment: Windows XP SP2, JSDK 1.5.1_12
>Reporter: Alex Dubrovsky
>
> I have multimodule project, in one of the child pom files defined custom
> profile, which updates DB via separate Ant build file:
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> populate-db
> process-classes
>
>
> antfile="${basedir}/data_build.xml" target="populate.db" inheritAll="true"
> inheritRefs="true">
>
>
>
>
> run
>
>
>
>
>
> org.apache.ant
> ant
> 1.7.0
>
>
> org.apache.ant
> ant-nodeps
> 1.7.0
>
>
> org.apache.ant
> ant-parent
> 1.7.0
>
>
> org.apache.ant
> ant-launcher
> 1.7.0
>
>
>
>
> Anyway build seems to load ant 1.6.5 in parent pom file (it has some plugins,
> that require Ant 1.6.5), so I am getting this:
> Embedded error: The following error occurred while executing this line:
> data_build.xml:39: The type doesn't support the "expandproperties"
> attribute.
> "expandproperties" attribute was added in Ant 1.7. I have no Ant 1.6
> installed in my system, only jars in Maven repository. env.ANT_HOME is set to
> Ant 1.7, PATH variable also contains Ant 1.7.
> I've tried to add any variants of the ant 1.7 packages to task dependecies
> with no luck.
> Any ideas?
--
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] Moved: (MANTTASKS-125) Ant remote repository conflicts with pom definition
[ http://jira.codehaus.org/browse/MANTTASKS-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-364 to MANTTASKS-125: - Affects Version/s: (was: 2.0-alpha-1) 2.0-alpha-1 Component/s: (was: Ant tasks) (was: POM) dependencies task Key: MANTTASKS-125 (was: MNG-364) Project: Maven 2.x Ant Tasks (was: Maven 2) > Ant remote repository conflicts with pom definition > --- > > Key: MANTTASKS-125 > URL: http://jira.codehaus.org/browse/MANTTASKS-125 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: dependencies task >Affects Versions: 2.0-alpha-1 >Reporter: Brett Porter > > something interesting I'm noticing about the way remote repositories come up > through the pom and super pom is that you can start switching around if > you've selected a different one as you traverse into the inherited poms and > transitive dependencies. > The key is probably to declare your "mirror" for "central", and the ant tasks > should also have a notion of that. -- 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] Moved: (MANTTASKS-126) Exception "parser must be on START_TAG or TEXT to read text" in MavenXpp3Reader for model-3.0.0 POMs.
[ http://jira.codehaus.org/browse/MANTTASKS-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-667 to MANTTASKS-126: - Affects Version/s: (was: 2.0-alpha-3) 2.0-alpha-3 Component/s: (was: Ant tasks) dependencies task Key: MANTTASKS-126 (was: MNG-667) Project: Maven 2.x Ant Tasks (was: Maven 2) > Exception "parser must be on START_TAG or TEXT to read text" in > MavenXpp3Reader for model-3.0.0 POMs. > - > > Key: MANTTASKS-126 > URL: http://jira.codehaus.org/browse/MANTTASKS-126 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: dependencies task >Affects Versions: 2.0-alpha-3 > Environment: Not of importance. >Reporter: Davy Toch > > I have an ANT script using maven antlib (alpha-3) as follows: >... > >id="remote.repository" url="http://172.16.40.249/ourrepo"; > layout="legacy"/> > > > > > > ... > I already posted a problem http://jira.codehaus.org/browse/MNG-666 when > model-3.0.0 POMs are validated. This was temporarily solved by adding an > element in the POM. However an additional problem is that the > POM contains several dependencies with a subelement, e.g.: > > commons-lang > commons-lang > 2.0 > > true > > > The fact that subelements are present in causes the following > exception: > --- Nested Exception --- > org.apache.maven.artifact.resolver.TransitiveArtifactResolutionException: > Unable to read the metadata file > sis2:sis2-common:0.1:jar > from the specified remote repositories: > http://172.16.40.249/ourrepo > Path to dependency: > 1) unspecified:unspecified:jar:0.0 > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:164) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:66) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:173) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:199) > at > org.apache.maven.artifact.ant.DependenciesTask.execute(DependenciesTask.java:115) > at > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) > at org.apache.tools.ant.Task.perform(Task.java:364) > at org.apache.tools.ant.Target.execute(Target.java:341) > at org.apache.tools.ant.Target.performTasks(Target.java:369) > at > org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) > at org.apache.tools.ant.Project.executeTarget(Project.java:1185) > at > org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) > at org.apache.tools.ant.Project.executeTargets(Project.java:1068) > at org.apache.tools.ant.Main.runBuild(Main.java:668) > at org.apache.tools.ant.Main.startAnt(Main.java:187) > at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) > at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) > Caused by: > org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable > to read the metadata file > at > org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:88) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:151) > ... 16 more > Caused by: org.apache.maven.project.ProjectBuildingException: Failed to parse > model from file 'C:\Documents and > Settings\dto\.m2\repository\sis2\sis2-common\0.1\sis2-common-0.1.pom'. > Error: 'TEXT must be immediately followed by END_TAG and not START_TAG > (position: START_TAG seen ...\n > ... @31:33) ' > at > org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:525) > at > org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:244) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:218) > at > org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:81) > ... 17 more > Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: TEXT > must be immediately followed by END_TAG and not START_TAG (position: > START_TAG seen ...\n spath>... @31:33) > at > org.codehaus.plexus.util.xml.pull.MXParser.nextText(MXParser.java:1059) >
[jira] Moved: (MANTTASKS-127) The Maven antlib task should also be able to retrieve artifacts that don't have a POM.
[ http://jira.codehaus.org/browse/MANTTASKS-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-668 to MANTTASKS-127: - Affects Version/s: (was: 2.0-alpha-3) 2.0-alpha-3 Component/s: (was: Ant tasks) dependencies task Key: MANTTASKS-127 (was: MNG-668) Project: Maven 2.x Ant Tasks (was: Maven 2) > The Maven antlib task should also be able to retrieve > artifacts that don't have a POM. > -- > > Key: MANTTASKS-127 > URL: http://jira.codehaus.org/browse/MANTTASKS-127 > Project: Maven 2.x Ant Tasks > Issue Type: Improvement > Components: dependencies task >Affects Versions: 2.0-alpha-3 > Environment: Not of importance. >Reporter: Davy Toch >Assignee: Brett Porter > > It is a good idea of having an ANT plugin to retrieve dependencies from a > Maven repository. However, the task apparently needs > to find a POM for every artifact it needs to retrieve. > A solution for dependencies that don't have a POM is to use another > dependency manager (Ivy, Savant, ...), but the problem with this is that the > ANT scripting becomes more cumbersome (use Maven Antlib for dependency A, use > Ivy for dependency B, ...). > I think it would be a great improvement in the Maven antlib (currently > alpha-3) to have an optional attribute for every that would > indicate that only the dependency should be retrieved and that for example > POM retrieval & validation shouldn't be done, as illustrated in the following > extract of my ANT script: > > ... > > > > >nopom="true" /> > > ... > Regards, > Davy Toch -- 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] Moved: (MANTTASKS-130) NPE when trying to use
[ http://jira.codehaus.org/browse/MANTTASKS-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-1165 to MANTTASKS-130: -- Affects Version/s: (was: 2.0-beta-3) 2.0-beta-3 Component/s: (was: Ant tasks) deploy task Key: MANTTASKS-130 (was: MNG-1165) Project: Maven 2.x Ant Tasks (was: Maven 2) > NPE when trying to use > --- > > Key: MANTTASKS-130 > URL: http://jira.codehaus.org/browse/MANTTASKS-130 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: deploy task >Affects Versions: 2.0-beta-3 > Environment: Ant1.7alpha; java1.5 >Reporter: Steve Loughran >Assignee: Brett Porter >Priority: Critical > > I cannot get to work, it just NPEs on me. All the files exist; local > install works > > >privateKey="C:\\bin\\PuTTY\\.ssh\\id_rsa"/> > > > > java.lang.NullPointerException > at org.apache.maven.artifact.ant.DeployTask.execute(DeployTask.java:69) > at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) -- 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] Moved: (MANTTASKS-129) Add scope attribute to
[ http://jira.codehaus.org/browse/MANTTASKS-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-1149 to MANTTASKS-129: -- Affects Version/s: (was: 2.0-beta-3) 2.0-beta-3 Component/s: (was: Ant tasks) dependencies task Key: MANTTASKS-129 (was: MNG-1149) Project: Maven 2.x Ant Tasks (was: Maven 2) > Add scope attribute to > -- > > Key: MANTTASKS-129 > URL: http://jira.codehaus.org/browse/MANTTASKS-129 > Project: Maven 2.x Ant Tasks > Issue Type: Improvement > Components: dependencies task >Affects Versions: 2.0-beta-3 > Environment: Ant1.7alpha, java1.5.05 >Reporter: Steve Loughran >Assignee: Brett Porter > > Can the dependencies task add a scope attribute, so that I can use the same > pom for setting up the build, test and run paths? In ant I need to run > three times to do this, but cannot use the same pom unless i > can control the scope. -- 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] Moved: (MANTTASKS-128) Bad handling of unsupported (i.e maven1) pom files
[ http://jira.codehaus.org/browse/MANTTASKS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-892 to MANTTASKS-128: - Component/s: (was: Ant tasks) dependencies task Key: MANTTASKS-128 (was: MNG-892) Project: Maven 2.x Ant Tasks (was: Maven 2) > Bad handling of unsupported (i.e maven1) pom files > -- > > Key: MANTTASKS-128 > URL: http://jira.codehaus.org/browse/MANTTASKS-128 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: dependencies task > Environment: java 1.5 on linux >Reporter: Steve Loughran >Assignee: Brett Porter > > I'm trying to pull down something that depends on > geronimo-spec-javamail/1.3.1-rc5 > Ths file is in the legacy cvs pom, which the ant tasks fail on. > 1. no message identifying the .pom at fault is show, except in -verbose. All > you get is "Unable to resolve artifact" without any more details. Please show > the exception text at the bottom. > 2. maybe the fact that pom isnt very clean doesnt help; it refers to > ../project.xml and uses property settings from there to define its own > dependencies. but the underlying error is > Unrecognised tag: 'pomVersion' (position: START_TAG seen ...\r\n > ... @22:17) > this is just something pulled from a legacy filestore. If you dont handle the > old layout/pom, then it should be rejected more cleanly. -- 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] Moved: (MANTTASKS-131) Add a task to run maven in a directory
[ http://jira.codehaus.org/browse/MANTTASKS-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-1575 to MANTTASKS-131: -- Component/s: (was: Ant tasks) Key: MANTTASKS-131 (was: MNG-1575) Project: Maven 2.x Ant Tasks (was: Maven 2) > Add a task to run maven in a directory > -- > > Key: MANTTASKS-131 > URL: http://jira.codehaus.org/browse/MANTTASKS-131 > Project: Maven 2.x Ant Tasks > Issue Type: New Feature >Reporter: Steve Loughran >Assignee: Brett Porter >Priority: Minor > > Now that you have ant tasks, why not add one that can run maven in a > specified directory, passing down parameters of choice, failing the build if > there was an error. This lets ant delegate to maven2 when it needs to, -- 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] Moved: (MANTTASKS-133) indirect snapshot dependency not in fileset
[ http://jira.codehaus.org/browse/MANTTASKS-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-1946 to MANTTASKS-133: -- Affects Version/s: (was: 2.0) 2.0 Component/s: (was: Ant tasks) dependencies task Key: MANTTASKS-133 (was: MNG-1946) Project: Maven 2.x Ant Tasks (was: Maven 2) > indirect snapshot dependency not in fileset > --- > > Key: MANTTASKS-133 > URL: http://jira.codehaus.org/browse/MANTTASKS-133 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: dependencies task >Affects Versions: 2.0 > Environment: Java 1.5 >Reporter: Michael Hartmeier > Attachments: build.xml > > > I use > > > > http://myCompany/repository/";> > > > > > to fetch "first" and all dependent jar files. First's pom contains > > myGroup > second > 0.5-SNAPSHOT > > Problem: the "second" jar file is in not in the fileset. > Note 1: Everything work's fine if "second"'s version is 0.5. > Note 2: I can work-around the problem by adding a second dependencies call > > version="0.5-SNAPSHOT"> > > http://myCompany/repository/";> > > > > > to my build file (and use to fileset references). However, having a single > dependencies > call with two dependency lines does *not* help. -- 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] Moved: (MANTTASKS-132) maven.* project references no longer resolve in ant tasks.
[ http://jira.codehaus.org/browse/MANTTASKS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-1860 to MANTTASKS-132: -- Affects Version/s: (was: 2.0.1) 2.0.1 Component/s: (was: Ant tasks) POM Integration Key: MANTTASKS-132 (was: MNG-1860) Project: Maven 2.x Ant Tasks (was: Maven 2) > maven.* project references no longer resolve in ant tasks. > -- > > Key: MANTTASKS-132 > URL: http://jira.codehaus.org/browse/MANTTASKS-132 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: POM Integration >Affects Versions: 2.0.1 >Reporter: John Casey >Assignee: John Casey >Priority: Blocker > > from original email: > The following reference in ant run used to work. Now it resolves to > null.null. Did something fundamental change or is this a bug? >dest="target/classes"> > > From follow-up email: > changing to pom.* fixes the problem -- 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] Moved: (MANTTASKS-134) Exclusions in dependencies should not exclude a direct dependency
[ http://jira.codehaus.org/browse/MANTTASKS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-2138 to MANTTASKS-134: -- Affects Version/s: (was: 2.0.2) (was: 2.0.1) (was: 2.0) 2.0 2.0.1 2.0.2 Component/s: (was: Ant tasks) dependencies task Key: MANTTASKS-134 (was: MNG-2138) Project: Maven 2.x Ant Tasks (was: Maven 2) > Exclusions in dependencies should not exclude a direct dependency > - > > Key: MANTTASKS-134 > URL: http://jira.codehaus.org/browse/MANTTASKS-134 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: dependencies task >Affects Versions: 2.0.2, 2.0.1, 2.0 > Environment: Any (tested on windows) >Reporter: Bruce Brouwer >Assignee: Carlos Sanchez >Priority: Minor > > Here's the situation: My pom declares a dependency on artifact B, but > excludes the transitive dependency on C. This same pom also directly depends > on C. When getting the dependencies, C does not show up in the list, even > though it is a direct dependency. Here is the relevant section of the pom: > > > > groupB > artifactB > > > groupC > artifactC > > > > > groupC > artifactC > > > > Then using that ant task: > pomrefid="maven.project" > pathId="compile.classpath" > verbose="true" > useScope="compile" /> -- 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] Moved: (MANTTASKS-135) Maven Tasks for Ant should provide an Ant task to launch Maven
[ http://jira.codehaus.org/browse/MANTTASKS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-2139 to MANTTASKS-135: -- Affects Version/s: (was: 2.0.2) (was: 2.0.3) (was: 2.0.1) (was: 2.0) 2.0 2.0.1 2.0.2 2.0.3 Component/s: (was: Ant tasks) Key: MANTTASKS-135 (was: MNG-2139) Project: Maven 2.x Ant Tasks (was: Maven 2) > Maven Tasks for Ant should provide an Ant task to launch Maven > -- > > Key: MANTTASKS-135 > URL: http://jira.codehaus.org/browse/MANTTASKS-135 > Project: Maven 2.x Ant Tasks > Issue Type: Wish >Affects Versions: 2.0.3, 2.0.2, 2.0.1, 2.0 > Environment: Windows makes this especially troublesome >Reporter: Dan Fabulich >Assignee: Brett Porter > > Due to bug MNG-2127, it can be tricky to launch Maven from within Ant > correctly and extract the correct exit value on all operating systems. A > great solution would be to implement a task in the Maven Tasks for > Ant. This code would be able to correctly and simply construct Maven's > classpath (using the classes already baked into maven-artifact-ant-*-dep.jar) > and execute arbitrary goals on arbitrary POMs. -- 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] Moved: (MANTTASKS-136) Deploy Ant task doesn't handle -SNAPSHOT
[ http://jira.codehaus.org/browse/MANTTASKS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-2269 to MANTTASKS-136: -- Component/s: (was: Ant tasks) deploy task Key: MANTTASKS-136 (was: MNG-2269) Project: Maven 2.x Ant Tasks (was: Maven 2) > Deploy Ant task doesn't handle -SNAPSHOT > > > Key: MANTTASKS-136 > URL: http://jira.codehaus.org/browse/MANTTASKS-136 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: deploy task >Reporter: Dan Fabulich >Assignee: Carlos Sanchez > > Use the Maven "deploy" ant task with the version "1.0-SNAPSHOT". It will be > deployed to the artifact repository as "1.0-SNAPSHOT"; it won't have its > -SNAPSHOT replaced with a proper qualified name (timestamp, build number, > etc.). > Ideally there would be a way for users to specify their own qualifier in the > Ant task, by specifying a special attribute. That would allow Ant scripters > to use Ant's task or to use any other arbitrary build number as > needed. -- 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] Moved: (MANTTASKS-138) Default value for 'file' attribute of install/deploy tasks should be available.
[
http://jira.codehaus.org/browse/MANTTASKS-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann moved MNG-2358 to MANTTASKS-138:
--
Affects Version/s: (was: 2.0.4)
2.0.4
Component/s: (was: Ant tasks)
install task
deploy task
Key: MANTTASKS-138 (was: MNG-2358)
Project: Maven 2.x Ant Tasks (was: Maven 2)
> Default value for 'file' attribute of install/deploy tasks should be
> available.
> ---
>
> Key: MANTTASKS-138
> URL: http://jira.codehaus.org/browse/MANTTASKS-138
> Project: Maven 2.x Ant Tasks
> Issue Type: Improvement
> Components: deploy task, install task
>Affects Versions: 2.0.4
> Environment: Not of importance.
>Reporter: Davy Toch
>
> It would be useful to have a default value for the 'file' attribute in the
> install/deploy tasks of the M2 ant tasks, based on the POM settings.
>xmlns:m="antlib:org.apache.maven.artifact.ant">
>
> ...
>
>
>
> value="${POM.build.directory}/${POM.artifactId}-${POM.version}.${POM.packaging}"/>
> ...
>
>
>
>
>
>
>
>
--
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] Moved: (MANTTASKS-137) task gives a bad pathId when downloading a deployed SNAPSHOT
[ http://jira.codehaus.org/browse/MANTTASKS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-2273 to MANTTASKS-137: -- Affects Version/s: (was: 2.0.4) 2.0.4 Component/s: (was: Ant tasks) dependencies task Key: MANTTASKS-137 (was: MNG-2273) Project: Maven 2.x Ant Tasks (was: Maven 2) > task gives a bad pathId when downloading a deployed SNAPSHOT > --- > > Key: MANTTASKS-137 > URL: http://jira.codehaus.org/browse/MANTTASKS-137 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: dependencies task >Affects Versions: 2.0.4 >Reporter: Dan Fabulich >Assignee: Brett Porter >Priority: Blocker > > Deploy a -SNAPSHOT build using the deploy:deploy-file goal. (Don't do it > with the Ant task; that doesn't work, per bug MNG-2060.) The file > will be deployed into a -SNAPSHOT directory, but the file itself will contain > a build number, not the word SNAPSHOT. > Now delete the SNAPSHOT from your local repository and attempt to use > to acquire it. The task will claim to succeed, but the pathId > will contain an incorrect file path. > For example, I deployed selenium-server-0.7.2-SNAPSHOT.jar; on the remote > repo it was called selenium-server-0.7.2-20060505.015135-1.jar. When the Ant > task pulled it into my local repo it was in > selenium-server\0.7.2-SNAPSHOT\selenium-server-0.7.2-20060505.015135-1.jar. > But finally when I ran the Ant task, the classpath it gave me pointed to > selenium-server\0.7.2-20060505.015135-1\selenium-server-0.7.2-20060505.015135-1.jar, > which is clearly wrong. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MANTTASKS-139) Ant needs to be upgraded to 1.7.0
[
http://jira.codehaus.org/browse/MANTTASKS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann moved MNG-3083 to MANTTASKS-139:
--
Component/s: (was: Ant tasks)
Key: MANTTASKS-139 (was: MNG-3083)
Project: Maven 2.x Ant Tasks (was: Maven 2)
> Ant needs to be upgraded to 1.7.0
> -
>
> Key: MANTTASKS-139
> URL: http://jira.codehaus.org/browse/MANTTASKS-139
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
>Reporter: Brian Topping
>Priority: Critical
>
> Moving an Ant 1.7.0 build to Maven is currently impossible because there are
> dependencies on 1.6.5 all around Maven and the groupId of Ant has changed
> from {{ant}} to {{org.apache.ant}}. This precludes upgrading the dependency
> through graph distance override.
> In order to fix this, dependencies on Ant 1.6.5 need to be upgraded to 1.7.0.
> Fixing MANTRUN-68 would be nice, but is not as big a deal because it can be
> rebuilt locally.
--
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] Moved: (MANTTASKS-140) missing dependent class org/codehaus/classworlds/DuplicateRealmException
[ http://jira.codehaus.org/browse/MANTTASKS-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-589 to MANTTASKS-140: - Affects Version/s: (was: 2.0-alpha-3) 2.0-alpha-3 Component/s: (was: Ant tasks) Key: MANTTASKS-140 (was: MNG-589) Project: Maven 2.x Ant Tasks (was: Maven 2) > missing dependent class org/codehaus/classworlds/DuplicateRealmException > > > Key: MANTTASKS-140 > URL: http://jira.codehaus.org/browse/MANTTASKS-140 > Project: Maven 2.x Ant Tasks > Issue Type: Bug >Affects Versions: 2.0-alpha-3 > Environment: ant1.7alpha on winxpsp2 >Reporter: Steve Loughran > > having just uploaded to the alpha3 library, I am now getting errrors about a > missing exception class > C:\Java\Apache\Ant\fetch.xml:70: The following error occurred while executing > this line: > jar:file:/C:/Java/Apache/Ant/lib/maven-artifact-ant-2.0-alpha-3.jar!/org/apache/maven/artifact/ant/antlib.xml:4: > taskdef A class needed by class > org.apache.maven.artifact.ant.DependenciesTask cannot be found: > org/codehaus/classworlds/DuplicateRealmException -- 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-3900) [regression] Properties defined by active profiles are not used for POM interpolation
[regression] Properties defined by active profiles are not used for POM
interpolation
-
Key: MNG-3900
URL: http://jira.codehaus.org/browse/MNG-3900
Project: Maven 2
Issue Type: Bug
Components: Inheritance and Interpolation, Profiles
Affects Versions: 3.0-alpha-1
Reporter: Benjamin Bentmann
For the POM snippet
{code:xml}
FAILED
${test}
interpolation-profile
PASSED
{code}
and the activated profile "interpolation-profile" the effective value of
{{${property}}} will be {{FAILED}} Instead of {{PASSED}}.
--
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-2304) please upload DynamicJasper 3.0.2
please upload DynamicJasper 3.0.2 - Key: MAVENUPLOAD-2304 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2304 Project: Maven Upload Requests Issue Type: Task Reporter: Juan Manuel Alvarez I am DynamicJasper's project leader, please upload. DynamicJasper (DJ) is an API that hides the complexity of Jasper Reports, it helps developers to save time when designing simple/medium complexity reports generating the layout of the report elements automatically. It creates reports dynamically, defining at runtime the columns, column width (auto width), groups, variables, fonts, charts, crosstabs, sub reports (that can also be dynamic), page size and everything else that you can define at design time. -- 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-3855) release mercury 1.0.0-alpha-2
[ http://jira.codehaus.org/browse/MNG-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-3855. -- Resolution: Fixed Mercury alpha-2 is now released. > release mercury 1.0.0-alpha-2 > - > > Key: MNG-3855 > URL: http://jira.codehaus.org/browse/MNG-3855 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories, Dependencies >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 3.0-alpha-2 > > -- 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-3901) Merge all project building code into a single component
[ http://jira.codehaus.org/browse/MNG-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3901: --- Fix Version/s: 3.0-alpha-2 > Merge all project building code into a single component > --- > > Key: MNG-3901 > URL: http://jira.codehaus.org/browse/MNG-3901 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-2 > > > Right now we have the new project builder being used by the old project > builder code. We need to collapse everything into the one new component and > remove all dead components. I can see that the pathTranslator isn't being > used any more. There are probably references to some other dead bits that > need to be cleaned up. -- 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-3901) Merge all project building code into a single component
Merge all project building code into a single component --- Key: MNG-3901 URL: http://jira.codehaus.org/browse/MNG-3901 Project: Maven 2 Issue Type: Task Reporter: Jason van Zyl Fix For: 3.0-alpha-2 Right now we have the new project builder being used by the old project builder code. We need to collapse everything into the one new component and remove all dead components. I can see that the pathTranslator isn't being used any more. There are probably references to some other dead bits that need to be cleaned up. -- 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-3902) Remove visibility MavenProjectBuilder#buildStandaloneSuperProject
Remove visibility MavenProjectBuilder#buildStandaloneSuperProject - Key: MNG-3902 URL: http://jira.codehaus.org/browse/MNG-3902 Project: Maven 2 Issue Type: Task Reporter: Jason van Zyl This method does not need to be exposed beyond the project building code. It's used currently in two places: 1) To provide a default model when you execute a goal that has no POM. Here we have to deal gracefully without its presence because there may actually be times we need to know when there is no POM available. The null pattern here cause the exposure of this method and propagated lots of internal logic that can no longer differentiate when a project is present or not. 2) To get the default remote repositories. These should be placed somewhere else as simple values so that we don't have to invoke such a big piece of machinery just to extract those values. Need to find all the plugins that may rely on this method, as almost every method in the project builder is being misused in one plugin or another. -- 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-1792) finish openpgp support
[ http://jira.codehaus.org/browse/MNG-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-1792. -- Resolution: Fixed Superceded by work completed in Mercury. > finish openpgp support > -- > > Key: MNG-1792 > URL: http://jira.codehaus.org/browse/MNG-1792 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Reporter: Brett Porter > Fix For: 3.x > > Attachments: MNG-1792 > > > what is left to do: > - appropriate integration with the wagon manager - deployment and checking on > retrieval > - some form of optional inclusion (would like to make it download once > enabled) > - password checking in a useful fashion for deployers (type each time, only > type once per build, but don't keep it in memory too long if possible) -- 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-3487) The POM model should support not only but also
[ http://jira.codehaus.org/browse/MNG-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-3487. -- Resolution: Won't Fix We're not going to include references to external resources. > The POM model should support not only but also > -- > > Key: MNG-3487 > URL: http://jira.codehaus.org/browse/MNG-3487 > Project: Maven 2 > Issue Type: New Feature > Components: POM >Reporter: Eduardo Martins > Fix For: 3.x > > > Currently there is no support for properties files in the POM, users often > need this feature and use plugins to achieve that, but plugins can't touch > elements in the POM which use a property to define some value, simply because > that is defined before any phase is done. > I recommend adding a new element, , which can have > childs. Maven will load all properties in this file (no xml, > usual format of property.name=property.value) the same way if they were > defined inside . -- 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-3066) Allow the specification of modules with project coordinates
[ http://jira.codehaus.org/browse/MNG-3066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-3066. -- Resolution: Won't Fix Modules are defined as being in scope at the file system level. We're not looking for modules in repositories. > Allow the specification of modules with project coordinates > --- > > Key: MNG-3066 > URL: http://jira.codehaus.org/browse/MNG-3066 > Project: Maven 2 > Issue Type: New Feature >Affects Versions: 2.0.6 >Reporter: Steven Cummings > Fix For: 3.x > > > Currently, modules can only be specified by the parent POM as "simple paths", > i.e., relative to the current project, like "module-a" and "../module-a". > This explicit filesystem relation between parent project and modules can > cause issues like CONTINUUM-1163. > It makes sense to allow modules to be specified with project coordinates, > like: > > module-a > com.mygroup > > This way no explicit filesystem or SCM relation has to exist. The only > requirement would be that the parent project is able to locate the specified > artifact in one of its defined repositories (or repositories from > settings.xml), and the artifact's POM contain an SCM section so that it can > check out the code. > From there, maven can decide what temporary space to check out and build the > "child" project in, perhaps .m2-workspace or .m2-modules-temp in the > user-home. Perhaps this also could be configured in settings.xml just like > the local repository location. > The value of this would be: > * Parent projects no longer have to exist "one level above" or relative to > all of its modules in SCM and the checkout filesystem. > * When SCM is organized such that not all of the module projects are in the > same folder, project coordinates could be simpler than relative paths. > * When not all of the projects are in the same SCM repos, then the current > module scheme won't even work. > * It would be nice to have the ability to create ad-hoc parent POMs just for > the purpose of executing arbitrary group builds. The modules can't specify > more than one parent, but there may be more than one grouping from the > top-down perspective. > ** A good example is where a team has several groupIds that all of their > projects are grouped into. Perhaps they don't want use parent POMs, or each > group has unique configuration and so each has a different parent POM for its > projects to inherit. Then, the group wants to run a global dashboard > (dashboard-maven-plugin) report on all projects in all groups but not really > use this new parent POM for inheritance or settings, only for the > aggregation. They'd like this so that there is one place to go to observe the > health of the team's projects. > * Finally, some operating systems (to remained un-named because this is their > defect...) have path limits of around 255 characters. Sometimes forcing > modules to exist under or relative to their parent causes the checkouts for > the group to surpass this limit. If there are projects already close to this > limit, the path of the parent project can push paths of package directories > and long class-names on over that limit. -- 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-2255) Use a external XML Pull parser instead of plexus one
[ http://jira.codehaus.org/browse/MNG-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2255. -- Resolution: Fixed We are now using the StAX parser from the Woodstox project. > Use a external XML Pull parser instead of plexus one > > > Key: MNG-2255 > URL: http://jira.codehaus.org/browse/MNG-2255 > Project: Maven 2 > Issue Type: Improvement > Components: POM >Affects Versions: 2.0.4 >Reporter: Carlos Sanchez >Priority: Critical > Fix For: 3.0 > > > To avoid maintaining the plexus XMLPullParser we should move to a standard > implementation like StaX > As mentioned in DOXIA-60: > There's a performance white paper > http://java.sun.com/performance/reference/whitepapers/StAX-1_0.pdf > The best implementation seems to be http://woodstox.codehaus.org/ > Another nice set of utilities at > http://wiki.java.net/bin/view/Javawsxml/StaxUtilsProject > The indentator could be used instead of the PrettyPrintXMLWriter -- 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-3363) MavenEmbedder can not be instanciated
[
http://jira.codehaus.org/browse/MNG-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl closed MNG-3363.
--
Resolution: Fixed
> MavenEmbedder can not be instanciated
> -
>
> Key: MNG-3363
> URL: http://jira.codehaus.org/browse/MNG-3363
> Project: Maven 2
> Issue Type: Bug
> Components: Embedding
>Affects Versions: 3.0-alpha-1
>Reporter: bajir
>Priority: Critical
> Fix For: 3.0
>
>
> The embedder is throwing an error while calling its constructor [new
> MavenEmbedder(configuration);]
> Version: maven-embedder-2.1-20080107.182656-29.jar (2.1-SNAPSHOT tree)
> Code fragment:
> import org.apache.maven.artifact.Artifact;
> import org.apache.maven.artifact.repository.ArtifactRepository;
> import org.apache.maven.artifact.repository.DefaultArtifactRepository;
> import org.apache.maven.artifact.repository.layout.ArtifactRepositoryLayout;
> import org.apache.maven.artifact.repository.layout.DefaultRepositoryLayout;
> import org.apache.maven.artifact.repository.layout.LegacyRepositoryLayout;
> import org.apache.maven.artifact.resolver.ArtifactNotFoundException;
> import org.apache.maven.artifact.resolver.ArtifactResolutionException;
> import org.apache.maven.embedder.Configuration;
> import org.apache.maven.embedder.ConfigurationValidationResult;
> import org.apache.maven.embedder.DefaultConfiguration;
> import org.apache.maven.embedder.MavenEmbedder;
> import org.apache.maven.settings.Profile;
> import org.apache.maven.settings.Repository;
> import org.apache.maven.settings.Settings;
> import org.apache.maven.settings.SettingsUtils;
> import org.apache.maven.settings.TrackableBase;
> import org.apache.maven.settings.io.xpp3.SettingsXpp3Reader;
> import org.codehaus.plexus.util.IOUtil;
> import org.codehaus.plexus.util.xml.pull.XmlPullParserException;
> ...
> DefaultConfiguration configuration = new DefaultConfiguration();
> configuration.setLocalRepository(_localRepFile);
> configuration.setGlobalSettingsFile(globalSettingsFiles);
> ConfigurationValidationResult validationResult =
> MavenEmbedder.validateConfiguration( configuration );
> if ( validationResult.isValid() )
> {
> try
> {
>MavenEmbedder embedder = new MavenEmbedder(configuration);
> Stack trace:
> java.lang.UnsupportedOperationException: You cannot modify this list. This
> list is a requirement of role:
> 'org.apache.maven.artifact.transform.ArtifactTransformationManager',
> implementation:
> 'org.apache.maven.artifact.transform.DefaultArtifactTransformationManager',
> role hint: 'default' and managed by the container.
> at
> org.codehaus.plexus.component.collections.ComponentList.remove(ComponentList.java:91)
> at
> org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.initialize(DefaultArtifactTransformationManager.java:45)
> at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase.execute(InitializePhase.java:33)
> at
> org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:97)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:136)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:126)
> at
> org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:96)
> at
> org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:147)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:494)
> at
> org.codehaus.plexus.component.composition.AbstractComponentComposer.findRequirement(AbstractComponentComposer.java:204)
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:72)
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirement(FieldComponentComposer.java:62)
> at
> org.codehaus.plexus.component.composition.AbstractComponentComposer.assembleComponent(AbstractComponentComposer.java:101)
> at
> org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:76)
> at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:46)
> at
> org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:97)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:136)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstanc
[jira] Updated: (MNG-2766) Refactor DefaultLifecycleExecutor
[ http://jira.codehaus.org/browse/MNG-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2766: --- Affects Version/s: (was: 3.0) 3.0-alpha-3 > Refactor DefaultLifecycleExecutor > - > > Key: MNG-2766 > URL: http://jira.codehaus.org/browse/MNG-2766 > Project: Maven 2 > Issue Type: Task > Components: Plugins and Lifecycle >Affects Versions: 3.0-alpha-3 >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0 > > > Another large beast that needs to be broken up. -- 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-2765) Refactor DefaultPluginManager
[ http://jira.codehaus.org/browse/MNG-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2765: --- Affects Version/s: (was: 3.0) 3.0-alpha-1 Fix Version/s: (was: 3.0) 3.0-alpha-3 > Refactor DefaultPluginManager > - > > Key: MNG-2765 > URL: http://jira.codehaus.org/browse/MNG-2765 > Project: Maven 2 > Issue Type: Task > Components: Plugins and Lifecycle >Affects Versions: 3.0-alpha-1 >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > This beast needed to be broken down and the call graph simplified. We could > also create a lookup( role[-hint], configuration ) in plexus to keep from > exposing configurators. -- 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-2765) Refactor DefaultPluginManager
[ http://jira.codehaus.org/browse/MNG-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2765: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-2 > Refactor DefaultPluginManager > - > > Key: MNG-2765 > URL: http://jira.codehaus.org/browse/MNG-2765 > Project: Maven 2 > Issue Type: Task > Components: Plugins and Lifecycle >Affects Versions: 3.0-alpha-1 >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-2 > > > This beast needed to be broken down and the call graph simplified. We could > also create a lookup( role[-hint], configuration ) in plexus to keep from > exposing configurators. -- 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-2766) Refactor DefaultLifecycleExecutor
[ http://jira.codehaus.org/browse/MNG-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2766: --- Affects Version/s: (was: 3.0-alpha-3) 3.0-alpha-1 Fix Version/s: (was: 3.x) 3.0-alpha-2 > Refactor DefaultLifecycleExecutor > - > > Key: MNG-2766 > URL: http://jira.codehaus.org/browse/MNG-2766 > Project: Maven 2 > Issue Type: Task > Components: Plugins and Lifecycle >Affects Versions: 3.0-alpha-1 >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-2 > > > Another large beast that needs to be broken up. -- 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-3849) Integrate Mercury into Maven
[ http://jira.codehaus.org/browse/MNG-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3849: --- Affects Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 Summary: Integrate Mercury into Maven (was: Integrate Mercury Alpha-2 into Maven) > Integrate Mercury into Maven > > > Key: MNG-3849 > URL: http://jira.codehaus.org/browse/MNG-3849 > Project: Maven 2 > Issue Type: Task >Reporter: Brian Fox > Fix For: 3.0-alpha-3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3849) Integrate Mercury into Maven
[ http://jira.codehaus.org/browse/MNG-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3849: --- Affects Version/s: (was: 3.0-alpha-3) Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > Integrate Mercury into Maven > > > Key: MNG-3849 > URL: http://jira.codehaus.org/browse/MNG-3849 > Project: Maven 2 > Issue Type: Task >Reporter: Brian Fox > Fix For: 3.0-alpha-3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3849) Integrate Mercury into Maven
[ http://jira.codehaus.org/browse/MNG-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3849: --- Description: I think we need to battle test mercury in the ant tasks and a few plugins first before we try this in the core. I also think we need to prepare the core with some refactoring and the design of the facade that will do all artifact handling in the core. > Integrate Mercury into Maven > > > Key: MNG-3849 > URL: http://jira.codehaus.org/browse/MNG-3849 > Project: Maven 2 > Issue Type: Task >Reporter: Brian Fox > Fix For: 3.0-alpha-3 > > > I think we need to battle test mercury in the ant tasks and a few plugins > first before we try this in the core. I also think we need to prepare the > core with some refactoring and the design of the facade that will do all > artifact handling in the core. -- 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-3903) Create a Maven specific abstraction for Artifact use within Maven
Create a Maven specific abstraction for Artifact use within Maven - Key: MNG-3903 URL: http://jira.codehaus.org/browse/MNG-3903 Project: Maven 2 Issue Type: Task Reporter: Jason van Zyl There's no point in just flipping all references from Maven Artifact to Mercury without protecting ourselves from this sort of thing in the future. This will also allow us to remove the few straggling bits in Mercury that are Maven specific like scopes and classifiers. -- 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-3903) Create a Maven specific abstraction for Artifact use within Maven
[ http://jira.codehaus.org/browse/MNG-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3903: --- Description: There's no point in just flipping all references from Maven Artifact to Mercury without protecting ourselves from this sort of thing in the future. This will also allow us to remove the few straggling bits in Mercury that are Maven specific like scopes and classifiers. Once this is created then we can seriously consider plugging in Mercury behind it. We have a complete and total clusterfuck as it stands as the components for artifact manipulation and the use of Artifact are just used scatter shot through out the whole codebase. A direct transition to Mercury would make for a goat fuck we can avoid. was:There's no point in just flipping all references from Maven Artifact to Mercury without protecting ourselves from this sort of thing in the future. This will also allow us to remove the few straggling bits in Mercury that are Maven specific like scopes and classifiers. Fix Version/s: 3.0-alpha-2 > Create a Maven specific abstraction for Artifact use within Maven > - > > Key: MNG-3903 > URL: http://jira.codehaus.org/browse/MNG-3903 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl > Fix For: 3.0-alpha-2 > > > There's no point in just flipping all references from Maven Artifact to > Mercury without protecting ourselves from this sort of thing in the future. > This will also allow us to remove the few straggling bits in Mercury that are > Maven specific like scopes and classifiers. > Once this is created then we can seriously consider plugging in Mercury > behind it. We have a complete and total clusterfuck as it stands as the > components for artifact manipulation and the use of Artifact are just used > scatter shot through out the whole codebase. A direct transition to Mercury > would make for a goat fuck we can avoid. -- 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-3860) Make sure Nexus builds with Maven 3.x
[ http://jira.codehaus.org/browse/MNG-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157920#action_157920 ] Jason van Zyl commented on MNG-3860: Nexus integration tests are failing because of a nasty interpolation problem in the 2nd phase of interpolation. This is going to bite other projects I'm sure so this needs to be fixed. > Make sure Nexus builds with Maven 3.x > - > > Key: MNG-3860 > URL: http://jira.codehaus.org/browse/MNG-3860 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Shane Isbell > Fix For: 3.0-alpha-1 > > -- 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-3904) Fix interpolation of recursively nested build properties
Fix interpolation of recursively nested build properties
Key: MNG-3904
URL: http://jira.codehaus.org/browse/MNG-3904
Project: Maven 2
Issue Type: Bug
Reporter: Jason van Zyl
Nexus integration tests specify a property as:
fake-central = ${project.build.testOutputDirectory}/fake-central
where
${project.build.testOutputDirectory} is defined as
${project.build.directory}/test-classes
where
${project.build.directory} is defined as ${project.basedir}/target
We are getting ${project.build.testOutputDirectory} being evaluated and then
${project.basedir} stuck on the front.
--
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-3904) Fix interpolation of recursively nested build properties
[
http://jira.codehaus.org/browse/MNG-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3904:
---
Fix Version/s: 3.0-alpha-1
> Fix interpolation of recursively nested build properties
>
>
> Key: MNG-3904
> URL: http://jira.codehaus.org/browse/MNG-3904
> Project: Maven 2
> Issue Type: Bug
>Reporter: Jason van Zyl
> Fix For: 3.0-alpha-1
>
>
> Nexus integration tests specify a property as:
> fake-central = ${project.build.testOutputDirectory}/fake-central
> where
> ${project.build.testOutputDirectory} is defined as
> ${project.build.directory}/test-classes
> where
> ${project.build.directory} is defined as ${project.basedir}/target
> We are getting ${project.build.testOutputDirectory} being evaluated and then
> ${project.basedir} stuck on the front.
--
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-3905) Collect all repository processing logic in MavenTools, RepositoryHelper, and MavenExecutionRequestPopulator into one component
Collect all repository processing logic in MavenTools, RepositoryHelper, and MavenExecutionRequestPopulator into one component -- Key: MNG-3905 URL: http://jira.codehaus.org/browse/MNG-3905 Project: Maven 2 Issue Type: Task Reporter: Jason van Zyl Fix For: 3.0-alpha-1 We have artifact manipulation code in big chunks in three components. I'm going to stick it all into MavenTools. I'm also trying to do this to create a better test harness for spec validation of POM construction. -- 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-3905) Collect all repository processing logic in MavenTools, RepositoryHelper, and MavenExecutionRequestPopulator into one component
[ http://jira.codehaus.org/browse/MNG-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3905: --- Fix Version/s: 3.0-alpha-1 > Collect all repository processing logic in MavenTools, RepositoryHelper, and > MavenExecutionRequestPopulator into one component > -- > > Key: MNG-3905 > URL: http://jira.codehaus.org/browse/MNG-3905 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl > Fix For: 3.0-alpha-1 > > > We have artifact manipulation code in big chunks in three components. I'm > going to stick it all into MavenTools. I'm also trying to do this to create a > better test harness for spec validation of POM construction. -- 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
