[jira] Commented: (MNG-3999) validation of Id's too restrictive
[ http://jira.codehaus.org/browse/MNG-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163066#action_163066 ] Sven Pressler commented on MNG-3999: It's not mandatory for me to retain the file names, that's true. And I do not have to support a legacy Maven 1 repository since I'm creating a Maven 2 repository. But I have a lot of files like that. The plugin that creates a pom.xml from a maven 1 project.xml doesn't have any validation for ID's, which is good, but it should at least tell me in a warning that the newly created pom.xml contains some ID's which are not valid anymore. So apart from having to change a lot of Ids when installing the files in my new repository I have to check all of the pom.xml's for now invalid dependencies, which is a bit annoying. But my main question is still unanswered: Why is the validation so restrictive in the first place? In MNG-801 there was a request that no / should be allowed in an Id, which is ok, but the validation that was created goes far beyond that and I don't really see why this was necessary. > validation of Id's too restrictive > -- > > Key: MNG-3999 > URL: http://jira.codehaus.org/browse/MNG-3999 > Project: Maven 2 > Issue Type: Improvement > Components: POM > Environment: xp, SAP NetWeaver, maven 2.x >Reporter: Sven Pressler > Attachments: pom.xml > > > I guess the validation of the Id's were introduced after issue MNG-801. > I think the validation is too strong. > The problem is that a lot of valid filenames are not validated as true. > The problem is caused by the DefaultModelValidator: private static final > String ID_REGEX = "[A-Za-z0-9_\\-.]+"; > This regular expression is far too restrictive since something like > "x=+%$§~!#^.jar" would be a valid filename on a windows operating system > I stumbled upon this because I'm developing tools for SAP NetWeaver, > currently we still use maven 1 to build our projects but we're in the process > of upgrading to maven 2. > maven 1 doesn't have this problem, since Id's didn't get validated like that. > Problem is SAP have a lot of libraries that have '~' in their names, like > 'tc~epbc~pcm~adminapi~java-5.x.y.jar'. Doesn't look any good, I don't like > it, I didn't make it like that but I have to work with it. > Maybe someone can explain why it's a good idea to be that restrictive about > the Ids, but as far as I see it, it's more like: before MNG-801 there was no > validation, and after MNG-801 there was some validation, and until now, there > was not too much complaining about it. > Attached is a pom which produces the following when trying to run mvn install: > Project ID: group:com~company~my~project > Validation Messages: > [0] 'artifactId' with value 'com~company~my~project' does not match a > valid id pattern. > Reason: Failed to validate POM for project group:com~company~my~project at > C:\test\validate\pom.xml > [INFO] > > [INFO] Trace > org.apache.maven.reactor.MavenExecutionException: Failed to validate POM for > project group:com~company~my~project at C:\test\validate\pom.xml > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.project.InvalidProjectModelException: Failed to > validate POM for project group:com~company~my~project at > C:\test\validate\pom.xml > at > org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:1108) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:878) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198) > at org.apache.maven.DefaultMaven.getProject(Defa
[jira] Commented: (WAGON-45) Unable to deploy site to svn, html files contain inconsistent new lines
[ http://jira.codehaus.org/browse/WAGON-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163073#action_163073 ] Aaron Zeckoski commented on WAGON-45: - Adding the files a second time does not seem to work using svn 1.5.5 (it appears to be more strict) > Unable to deploy site to svn, html files contain inconsistent new lines > --- > > Key: WAGON-45 > URL: http://jira.codehaus.org/browse/WAGON-45 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-scm >Affects Versions: 1.0-beta-1 >Reporter: Carlos Sanchez >Assignee: Carlos Sanchez > Fix For: 1.0-beta-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] Commented: (MSITE-121) Generated html files contain inconsistent new lines
[ http://jira.codehaus.org/browse/MSITE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163074#action_163074 ] Aaron Zeckoski commented on MSITE-121: -- Reproducing this is easy. Here are the steps (using OSX 10.5.6) dhcp-91:entitybus-1.0.0 azeckoski$ mvn site:site [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Entity Bus [INFO] Entity Bus API [INFO] Entity Bus Utilities [INFO] Entity Bus Mock Objects [INFO] Entity Bus Manager Implementation [INFO] Entity Bus REST Implementation [INFO] Searching repository for plugin with prefix: 'site'. [INFO] [INFO] Building Entity Bus [INFO]task-segment: [site:site] [INFO] [INFO] [site:site] [INFO] Generating "Plugin Management" report. [INFO] Generating "Mailing Lists" report. [INFO] Generating "Continuous Integration" report. ... (snip) [INFO] Entity Bus REST Implementation SUCCESS [19.505s] [INFO] [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 1 minute 14 seconds [INFO] Finished at: Thu Jan 29 10:29:39 GMT 2009 [INFO] Final Memory: 33M/254M [INFO] dhcp-91:tmp azeckoski$ svn checkout https://entitybus.googlecode.com/svn/maven/ eb-maven --username azeckoski Checked out revision 9. dhcp-91:tmp azeckoski$ cd eb-maven dhcp-91:eb-maven azeckoski$ cp -R /tmp/entitybus/site . dhcp-91:eb-maven azeckoski$ ls -al total 0 drwxr-xr-x 4 azeckoski wheel 136 29 Jan 10:38 . drwxrwxrwt 23 root wheel 782 29 Jan 10:38 .. drwxr-xr-x 9 azeckoski wheel 306 29 Jan 10:38 .svn drwxr-xr-x 23 azeckoski wheel 782 29 Jan 10:38 site dhcp-91:eb-maven azeckoski$ svn add site A site A site/css A site/css/maven-base.css A site/css/maven-theme.css A site/css/print.css A site/css/site.css svn: File 'site/dependencies.html' has inconsistent newlines svn: Inconsistent line ending style dhcp-91:eb-maven azeckoski$ svn help add add: Put files and directories under version control, scheduling them for addition to repository. They will be added in next commit. usage: add PATH... dhcp-91:eb-maven azeckoski$ svn --version svn, version 1.5.5 (r34862) compiled Jan 5 2009, 12:30:39 Copyright (C) 2000-2008 CollabNet. Subversion is open source software, see http://subversion.tigris.org/ This product includes software developed by CollabNet (http://www.Collab.Net/). The following repository access (RA) modules are available: * ra_neon : Module for accessing a repository via WebDAV protocol using Neon. - handles 'http' scheme - handles 'https' scheme * ra_svn : Module for accessing a repository using the svn network protocol. - with Cyrus SASL authentication - handles 'svn' scheme * ra_local : Module for accessing a repository on local disk. - handles 'file' scheme * ra_serf : Module for accessing a repository via WebDAV protocol using serf. - handles 'http' scheme - handles 'https' scheme dhcp-91:eb-maven azeckoski$ mvn --version Maven version: 2.0.9 Java version: 1.5.0_16 OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" > Generated html files contain inconsistent new lines > --- > > Key: MSITE-121 > URL: http://jira.codehaus.org/browse/MSITE-121 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 >Reporter: Carlos Sanchez > Fix For: 2.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] Closed: (MPIR-131) NPE in printArtifactsLocations() for blacklisted repo
[ http://jira.codehaus.org/browse/MPIR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-131. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.2 Fixed in [r738829|http://svn.apache.org/viewvc?rev=738829&view=rev], snapshot deployed. Thanks everybody! > NPE in printArtifactsLocations() for blacklisted repo > - > > Key: MPIR-131 > URL: http://jira.codehaus.org/browse/MPIR-131 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 2.1 > Environment: Linux (Sun JDK 1.6), Windows (IBM VM 1.4). No direct > Internet access; going through local Artifactory repository. >Reporter: Klaus Brunner >Assignee: Vincent Siveton >Priority: Critical > Fix For: 2.2 > > Attachments: screenshot-1.jpg > > > I'm getting NPEs when running the reports plugin at this location: > [INFO] Generating "Dependencies" report. > [WARNING] The repository url 'http://repo1.maven.org/maven2' is invalid - > Repository 'central' will be blacklisted. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printArtifactsLocations(DependenciesRenderer.java:1182) > at > org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyRepositoryLocations(DependenciesRenderer.java:641) > at > org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:274) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65) > at > org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:239) > Taking a brief look with the debugger, it appears that the totalByRepo map in > DependenciesRenderer.printArtifactsLocations() is empty - so looking up any > entry will of course return null and result in an NPE here: > totalRow[idnum++] = totalByRepo.get( repokey ).toString(); > Note that this used to work fine before the 2.1 release. -- 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: (ARCHETYPE-125) Enhance internal catalog
[ http://jira.codehaus.org/browse/ARCHETYPE-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163113#action_163113 ] Tamás Cservenák commented on ARCHETYPE-125: --- Raphael, I'd like to point you to new Nexus plugin, that will come alive with the release of latest Nexus 1.3: https://docs.sonatype.com/display/NX/Nexus+MAC+Plugin The plugin is unfinished, and I'd like to ask a few questions about catalog XML doco. I see the one shipped with the archetype plugin here: http://svn.apache.org/viewvc/maven/archetype/trunk/archetype-common/src/main/resources/archetype-catalog.xml?view=markup - There are a lot of "RELEASE" versioned ones, bot others are not. Why? - There is only one "archetype" entry for distinct GA, i believe for the latest V. Why? (i know that the list would be bloated, but what if someone needs for some purpose an older archetype?) The plugin is in very raw stage, and using the central index download from today, generates output like this: http://s3.cservenak.net/maven/central/archetype-catalog.xml I'd like to know, is there something we can tweak together? For example, the URLs are of course pointing back to my Nexus instance, that could be driven by a switch, and have "original" URLs in case of proxy reposes, and Nexus URLs for hosted reposes. Also, making the plugin list the GA's only with latest V is pretty much easy (using the grouped search feature on Nexus Indexer API). And in that case, could I use the latest real version number (since the catalog is generated on-the-fly) or should i use the "RELEASE"? The former looks more logical to me. Thanks for responses! > Enhance internal catalog > > > Key: ARCHETYPE-125 > URL: http://jira.codehaus.org/browse/ARCHETYPE-125 > Project: Maven Archetype > Issue Type: Bug >Affects Versions: 2.0-alpha-1 >Reporter: Raphaël Piéroni > > Enhance to current wiki page: > http://docs.codehaus.org/display/MAVENUSER/Archetypes+List > Don't forget to add cocoon archetypes on that list -- 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-4015) Expression in Archetype ${package.replace('.','/')} not a valida reference in JDK 1.4.2
Expression in Archetype ${package.replace('.','/')} not a valida reference in
JDK 1.4.2
---
Key: MNG-4015
URL: http://jira.codehaus.org/browse/MNG-4015
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.9
Environment: Windows Vista 32bit
Java 1.4.2
Maven 2.0.9
Reporter: Nestor Boscan
Priority: Minor
I have many templates with applicationContext.xml that I need to reference
other files using the package replacing "." for "/". So I have many templates
with the expression ${package.replace('.','/')}. Using Maven with JDK 1.4.2 it
shows:
${package.replace('.', '/')} is not a valid reference
--
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] Reopened: (MAVENUPLOAD-2261) Automatic upload of mockito versions.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Brakkee reopened MAVENUPLOAD-2261: --- Rsync is not working anymore. Looking at the system log file /var/log/messages, it appears that the last rsync attempt was at Jan 27th 00:41 CET. Also, there are no failed login attempts after that, so apparently the automatic rsync has stopped working. Here are the last relevant entries from the log file: Jan 25 00:40:36 shikra sshd[28364]: Accepted publickey for mockito from 38.97.124.18 port 41183 ssh2 Jan 25 00:40:39 shikra sshd[28401]: Accepted publickey for mockito from 38.97.124.18 port 41184 ssh2 Jan 26 00:44:02 shikra sshd[2145]: Accepted publickey for mockito from 38.97.124.18 port 54213 ssh2 Jan 26 00:44:06 shikra sshd[2185]: Accepted publickey for mockito from 38.97.124.18 port 54216 ssh2 Jan 27 00:41:08 shikra sshd[11529]: Accepted publickey for mockito from 38.97.124.18 port 56208 ssh2 Jan 27 00:41:12 shikra sshd[11566]: Accepted publickey for mockito from 38.97.124.18 port 56212 ssh2 > Automatic upload of mockito versions. > - > > Key: MAVENUPLOAD-2261 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2261 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Erik Brakkee >Assignee: Carlos Sanchez > > Authenticity > = > Please contact Szczepan Faber for information about the authenticity of this > request. He is the owner of the mockito.org domain. > Also, my name will appear shortly on the mockito wiki at > http://code.google.com/p/mockito/. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MANTRUN-106) Maven dependency bug can lead to very confusing failures
Maven dependency bug can lead to very confusing failures Key: MANTRUN-106 URL: http://jira.codehaus.org/browse/MANTRUN-106 Project: Maven 2.x Antrun Plugin Issue Type: Improvement Affects Versions: 1.3 Reporter: benson margulies The purpose of this report is to suggest an FAQ entry or other web content, as follows. Using the Maven Antrun Plugin in multiple projects in the Reactor In Maven 2.0.x, there is a significant bug that can lead to very perplexing failures with the antrun plugin. There are two conditions that you have to meet to get into this problem. 1) You have to use the plugin in two projects that are loaded into the reactor via . 2) You have to require additional plugin dependencies on the plugin. In Maven 2.0.x, the dependencies of the first project into the reactor win, and all the others are entirely ignored. Concretely, if your first project uses the plugin with no special dependencies, and your second one tries to use ant-trax, the second antrun execution will fail, and complain that it can't find the classes in ant-trax. The only solution to this is to ensure that, in all of the places where you use the plugin, you list the same dependencies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3951) Hide drive-relative paths from plugins
[ http://jira.codehaus.org/browse/MNG-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3951: -- Fix Version/s: (was: 2.0.x) 2.1.0-M3 2.0.11 > Hide drive-relative paths from plugins > -- > > Key: MNG-3951 > URL: http://jira.codehaus.org/browse/MNG-3951 > Project: Maven 2 > Issue Type: Improvement > Components: Plugins and Lifecycle >Affects Versions: 2.0.9, 2.1.0-M1 > Environment: Windows >Reporter: Benjamin Bentmann >Priority: Minor > Fix For: 2.0.11, 2.1.0-M3 > > > Take this nice path: /tmp (note the leading slash). This is an absolute path > on Unix derivates but a drive-relative path on a Windows box. Drive-relative > paths are resolved by prepending the drive of the current directory, not the > entire current directory. > This notation of a drive-relative path is not well-known, even among Windows > users, and in particular not easy going for cross-platform Java tools. A Java > developer usually assumes that a path is either (directory-)relative or > absolute. > To avoid unnecessary complications as seen on our own multi-OS CI grid (cf. > dev@ thread [CI Grid, Windows and > Paths|http://www.nabble.com/CI-Grid%2C-Windows-and-Paths-to21153292.html]) > and as reported by users (e.g. MECLIPSE-404), the core should not only align > directory-relative paths but also resolve drive-relative paths. -- 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: (ARCHETYPE-226) Expression in Archetype ${package.replace('.','/')} not a valida reference in JDK 1.4.2
[
http://jira.codehaus.org/browse/ARCHETYPE-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MNG-4015 to ARCHETYPE-226:
-
Affects Version/s: (was: 2.0.9)
Key: ARCHETYPE-226 (was: MNG-4015)
Project: Maven Archetype (was: Maven 2)
> Expression in Archetype ${package.replace('.','/')} not a valida reference in
> JDK 1.4.2
> ---
>
> Key: ARCHETYPE-226
> URL: http://jira.codehaus.org/browse/ARCHETYPE-226
> Project: Maven Archetype
> Issue Type: Bug
> Environment: Windows Vista 32bit
> Java 1.4.2
> Maven 2.0.9
>Reporter: Nestor Boscan
>Priority: Minor
>
> I have many templates with applicationContext.xml that I need to reference
> other files using the package replacing "." for "/". So I have many templates
> with the expression ${package.replace('.','/')}. Using Maven with JDK 1.4.2
> it shows:
> ${package.replace('.', '/')} is not a valid reference
--
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-45) Unable to deploy site to svn, html files contain inconsistent new lines
[ http://jira.codehaus.org/browse/WAGON-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163157#action_163157 ] Brett Porter commented on WAGON-45: --- could you please raise this as a new issue Aaron? > Unable to deploy site to svn, html files contain inconsistent new lines > --- > > Key: WAGON-45 > URL: http://jira.codehaus.org/browse/WAGON-45 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-scm >Affects Versions: 1.0-beta-1 >Reporter: Carlos Sanchez >Assignee: Carlos Sanchez > Fix For: 1.0-beta-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-3957) [regression] For artifact {stax:stax-api:null:jar}: The version cannot be empty.
[
http://jira.codehaus.org/browse/MNG-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3957:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-4
> [regression] For artifact {stax:stax-api:null:jar}: The version cannot be
> empty.
> -
>
> Key: MNG-3957
> URL: http://jira.codehaus.org/browse/MNG-3957
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 3.0-alpha-1
>Reporter: Jorg Heymans
> Fix For: 3.0-alpha-4
>
> Attachments: pom.xml
>
>
> A module in my build includes a dep to spring-ws:
> {code}
>
> org.springframework.ws
> spring-ws-core
> 1.5.5
>
>
> org.springframework
> spring-context
>
>
> org.springframework
> spring-aop
>
>
> org.springframework
> spring-web
>
>
> org.springframework
> spring-webmvc
>
>
> org.springframework
> spring-core
>
>
> org.springframework
> spring-beans
>
>
>
> {code}
> doing clean install i get this exception:
> {code}
> constituent[0]: file:/d:/tools/maven2/lib/bcpg-jdk15-140.jar
> constituent[1]: file:/d:/tools/maven2/lib/bcprov-jdk15-140.jar
> constituent[2]: file:/d:/tools/maven2/lib/commons-cli-1.0.jar
> constituent[3]: file:/d:/tools/maven2/lib/commons-logging-api-1.1.jar
> constituent[4]: file:/d:/tools/maven2/lib/doxia-sink-api-1.0-alpha-9.jar
> constituent[5]: file:/d:/tools/maven2/lib/google-collect-snapshot-20080530.jar
> constituent[6]: file:/d:/tools/maven2/lib/jetty-6.1.12.jar
> constituent[7]: file:/d:/tools/maven2/lib/jetty-client-6.1.12.jar
> constituent[8]: file:/d:/tools/maven2/lib/jetty-sslengine-6.1.12.jar
> constituent[9]: file:/d:/tools/maven2/lib/jetty-util-6.1.12.jar
> constituent[10]: file:/d:/tools/maven2/lib/jsch-0.1.38.jar
> constituent[11]: file:/d:/tools/maven2/lib/log4j-1.2.12.jar
> constituent[12]: file:/d:/tools/maven2/lib/maven-compat-3.0-alpha-1.jar
> constituent[13]: file:/d:/tools/maven2/lib/maven-core-3.0-alpha-1.jar
> constituent[14]: file:/d:/tools/maven2/lib/maven-distribution-3.0-alpha-1.jar
> constituent[15]: file:/d:/tools/maven2/lib/maven-embedder-3.0-alpha-1.jar
> constituent[16]: file:/d:/tools/maven2/lib/maven-lifecycle-3.0-alpha-1.jar
> constituent[17]: file:/d:/tools/maven2/lib/maven-mercury-3.0-alpha-1.jar
> constituent[18]: file:/d:/tools/maven2/lib/maven-model-3.0-alpha-1.jar
> constituent[19]: file:/d:/tools/maven2/lib/maven-plugin-api-3.0-alpha-1.jar
> constituent[20]: file:/d:/tools/maven2/lib/maven-project-3.0-alpha-1.jar
> constituent[21]:
> file:/d:/tools/maven2/lib/maven-project-builder-3.0-alpha-1.jar
> constituent[22]: file:/d:/tools/maven2/lib/maven-reporting-api-3.0-alpha-1.jar
> constituent[23]: file:/d:/tools/maven2/lib/maven-toolchain-3.0-alpha-1.jar
> constituent[24]: file:/d:/tools/maven2/lib/mercury-artifact-1.0.0-alpha-2.jar
> constituent[25]:
> file:/d:/tools/maven2/lib/mercury-crypto-api-1.0.0-alpha-2.jar
> constituent[26]:
> file:/d:/tools/maven2/lib/mercury-crypto-basic-1.0.0-alpha-2.jar
> constituent[27]: file:/d:/tools/maven2/lib/mercury-event-1.0.0-alpha-2.jar
> constituent[28]: file:/d:/tools/maven2/lib/mercury-external-1.0.0-alpha-2.jar
> constituent[29]: file:/d:/tools/maven2/lib/mercury-logging-1.0.0-alpha-2.jar
> constituent[30]: file:/d:/tools/maven2/lib/mercury-md-sat-1.0.0-alpha-2.jar
> constituent[31]: file:/d:/tools/maven2/lib/mercury-md-shared-1.0.0-alpha-2.jar
> constituent[32]: file:/d:/tools/maven2/lib/mercury-plexus-1.0.0-alpha-2.jar
> constituent[33]: file:/d:/tools/maven2/lib/mercury-repo-api-1.0.0-alpha-2.jar
> constituent[34]:
> file:/d:/tools/maven2/lib/mercury-repo-cache-fs-1.0.0-alpha-2.jar
> constituent[35]:
> file:/d:/tools/maven2/lib/mercury-repo-local-m2-1.0.0-alpha-2.jar
> constituent[36]:
> file:/d:/tools/maven2/lib/mercury-repo-remote-m2-1.0.0-alpha-2.jar
> constituent[37]:
> file:/d:/tools/maven2/lib/mercury-repo-virtual-1.0.0-alpha-2.jar
> constituent[38]:
> file:/d:/tools/maven2/lib/mercury-transport-api-1.0.0-alpha-2.jar
> constituent[39]:
> file:/d:/tools/maven2/lib/mercury-transport-http-1.0.0-alpha-2.jar
> constituent[40]: file:/d:/tools/maven2/lib/mercury-util-1.0.0-alpha-2.jar
> constituent[41]: file:/d:/tools/maven2/lib/model-builder-1.0.jar
> constituent[42]: file:/d:/tools/maven2/lib/nekohtml-1.9.6.2.jar
> constituent[43]: file:/d:/tools/maven2/lib/org.sat4j.core-2.0.4.jar
> constituent[44]: file:/d:/tools/maven2/lib/org.sat4j.pb-2.0.4.jar
> constituent[45]:
> file:/d:/tools/maven2/lib/plexus-component-annotations-1.0-beta-3.0.1.jar
> constituent[46]:
> file:/d:/tools/maven2/lib/plexus-container-
[jira] Updated: (MNG-3018) pluginManagement configurations are not honoured when plugin is silently included
[ http://jira.codehaus.org/browse/MNG-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3018: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > pluginManagement configurations are not honoured when plugin is silently > included > - > > Key: MNG-3018 > URL: http://jira.codehaus.org/browse/MNG-3018 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 3.0-alpha-1 >Reporter: Michael Semb Wever > Fix For: 3.0-alpha-4 > > > Read http://jira.codehaus.org/browse/MEVENIDE-532 > In my top parent pom.xml i've define the maven-compiler-plugin configuration > like: > > > > > maven-compiler-plugin > > 1.5 > 1.5 > UTF-8 > > ... > since not all my subprojects require the plugin, and when they do they > silently include the plugin, it makes more sense to define it within the > tag. > But when i use mevenide-netbeans all my projects are marked uncompilable > since the maven embedder does not report the above defined configuration for > the maven-compiler-plugin. -- 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-3013) The plugin manager incorrectly caches plugin versions between embedder calls
[ http://jira.codehaus.org/browse/MNG-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3013: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > The plugin manager incorrectly caches plugin versions between embedder calls > > > Key: MNG-3013 > URL: http://jira.codehaus.org/browse/MNG-3013 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 3.0-alpha-1 >Reporter: Carlos Sanchez >Assignee: Carlos Sanchez > Fix For: 3.0-alpha-4 > > > If you call the embedder once with a project and then change a plugin version > in the pom and run the same embedder the old version is used. > DefaultPluginManager.java lines 386-391 in revision 541121 > https://svn.apache.org/viewvc/maven/components/trunk/maven-core/src/main/java/org/apache/maven/plugin/DefaultPluginManager.java?annotate=536027 > was added in revision 498048 > https://svn.apache.org/viewvc/maven/components/trunk/maven-core/src/main/java/org/apache/maven/plugin/DefaultPluginManager.java?view=diff&r1=498047&r2=498048 > Any problem with removing that if block ? -- 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-2693) Error executing post-site: java.util.MissingResourceException: Can't find bundle for base name site-plugin, locale en
[ http://jira.codehaus.org/browse/MNG-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2693: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > Error executing post-site: java.util.MissingResourceException: Can't find > bundle for base name site-plugin, locale en > - > > Key: MNG-2693 > URL: http://jira.codehaus.org/browse/MNG-2693 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 2.0-alpha-1 >Reporter: Stepan Roh > Fix For: 3.0-alpha-4 > > > I use Maven 2.1 embedder - if I build it from current SVN HEAD of > maven-components (together with all components), I get this exception if I > try to execute post-site: > Caused by: org.apache.maven.reactor.MavenExecutionException: Error executing > project within the reactor > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:214) > at > org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:797) > ... 19 more > Caused by: java.util.MissingResourceException: Can't find bundle for base > name site-plugin, locale en > at > org.codehaus.plexus.i18n.DefaultI18N.cacheBundle(DefaultI18N.java:394) > at org.codehaus.plexus.i18n.DefaultI18N.getBundle(DefaultI18N.java:157) > at org.codehaus.plexus.i18n.DefaultI18N.getString(DefaultI18N.java:206) > at > org.apache.maven.plugins.site.AbstractSiteMojo.populateReportsMenu(AbstractSiteMojo.java:400) > at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.locateDocuments(AbstractSiteRenderingMojo.java:587) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:438) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:391) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:178) > ... 21 more > If I try revision 480835, it works. I see that there are some classworlds and > container changes since that revision, so it can be related to 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] Updated: (MNG-3281) Revisit backwards compat of extensions (IT 0114)
[ http://jira.codehaus.org/browse/MNG-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3281: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > Revisit backwards compat of extensions (IT 0114) > > > Key: MNG-3281 > URL: http://jira.codehaus.org/browse/MNG-3281 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 3.0-alpha-1 >Reporter: Brett Porter >Assignee: Jason van Zyl > Fix For: 3.0-alpha-4 > > > currently, it 0114 doesn't pass due to the removal of extension support > we need to either: > - restore some form of backwards compat by loading the extension into the > expected place > - provide a graceful failure instead -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3683) [regression] Help plugin does not work
[
http://jira.codehaus.org/browse/MNG-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3683:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-4
> [regression] Help plugin does not work
> --
>
> Key: MNG-3683
> URL: http://jira.codehaus.org/browse/MNG-3683
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin Requests
>Reporter: Brett Porter
>Assignee: Jason van Zyl
> Fix For: 3.0-alpha-4
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> The following command:
> mvn help:describe -Dplugin=site
> Gives the error:
> [ERROR]
> Maven encountered an error while configuring one of the mojos for your build.
> Mojo:
> Group-Id: org.apache.maven.plugins
> Artifact-Id: maven-help-plugin
> Version: 2.0.2
> Mojo: describe
> brought in via: Direct invocation
> While building project:
> Group-Id: org.apache.continuum
> Artifact-Id: continuum-docs
> Version: 1.2-SNAPSHOT
> From file: /Users/brett/scm/continuum/continuum/continuum-docs/pom.xml
> Here is the configuration it attempted to apply to the mojo:
> ${artifactId}
> ${full}
> ${groupId}
> ${localRepository}
> ${medium}
> ${mojo}
> ${output}
> ${plugin}
> ${project}
> ${session}
> ${settings}
> ${version}
>
> Error
> message:org.codehaus.plexus.component.configurator.ComponentConfigurationException:
> Invalid parameter supplied while setting
> 'org.apache.maven.plugin.mojoexecut...@a2f216' to
> org.apache.maven.plugins.help.DescribeMojo.setMojo( java.lang.Class )
--
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-3686) [regression] Can't build Wagon webdav provider
[ http://jira.codehaus.org/browse/MNG-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3686: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > [regression] Can't build Wagon webdav provider > -- > > Key: MNG-3686 > URL: http://jira.codehaus.org/browse/MNG-3686 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 3.0-alpha-1 >Reporter: Brett Porter >Assignee: Shane Isbell > Fix For: 3.0-alpha-4 > > > Wagon trunk r680097 fails to build in the webdav module when built with mvn > -Dmaven.test.skip=true from the top level due to: > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/commons/httpclient/methods/RequestEntity > at java.lang.Class.getDeclaredConstructors0(Native Method) > at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357) > at java.lang.Class.getConstructors(Class.java:1446) > at > com.thoughtworks.qdox.JavaDocBuilder.createBinaryClass(JavaDocBuilder.java:183) > at > com.thoughtworks.qdox.JavaDocBuilder.getClassByName(JavaDocBuilder.java:119) > at > com.thoughtworks.qdox.model.ClassLibrary.getClassByName(ClassLibrary.java:37) > at com.thoughtworks.qdox.model.Type.getJavaClass(Type.java:98) > at > com.thoughtworks.qdox.model.JavaClass.getSuperJavaClass(JavaClass.java:86) > at > org.codehaus.plexus.cdc.gleaner.QDoxComponentGleaner.findRequirements(QDoxComponentGleaner.java:343) > at > org.codehaus.plexus.cdc.gleaner.QDoxComponentGleaner.glean(QDoxComponentGleaner.java:193) > at > org.codehaus.plexus.maven.plugin.SourceComponentDescriptorExtractor.extract(SourceComponentDescriptorExtractor.java:100) > at > org.codehaus.plexus.maven.plugin.SourceComponentDescriptorExtractor.extract(SourceComponentDescriptorExtractor.java:74) > at > org.codehaus.plexus.maven.plugin.AbstractDescriptorMojo.generateDescriptor(AbstractDescriptorMojo.java:131) > at > org.codehaus.plexus.maven.plugin.PlexusDescriptorMojo.execute(PlexusDescriptorMojo.java:60) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:638) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:521) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:288) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:214) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:172) > at > org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) > at > org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:303) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:303) > 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 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351) -- 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-3919) NPE in DefaultLifecycleBindingManager
[
http://jira.codehaus.org/browse/MNG-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3919:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-4
> NPE in DefaultLifecycleBindingManager
> -
>
> Key: MNG-3919
> URL: http://jira.codehaus.org/browse/MNG-3919
> Project: Maven 2
> Issue Type: Bug
> Components: Errors
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0-alpha-4
>
> Attachments: pom.xml
>
>
> Running "mvn validate" on the attached POM delivers:
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.maven.lifecycle.binding.DefaultLifecycleBindingManager.getProjectCustomBindings(DefaultLifecycleBindingManager.java:251)
> at
> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan(DefaultBuildPlanner.java:104)
> at
> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlan(DefaultBuildPlanner.java:72)
> at
> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlans(DefaultBuildPlanner.java:61)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:157)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:207)
> at
> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:851)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:169)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
> 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:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:31)
> {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-3995) Configuration Property Lost In Join of PluginManagement/Plugin
[ http://jira.codehaus.org/browse/MNG-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3995: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > Configuration Property Lost In Join of PluginManagement/Plugin > -- > > Key: MNG-3995 > URL: http://jira.codehaus.org/browse/MNG-3995 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 3.0-alpha-2 >Reporter: Shane Isbell >Assignee: Shane Isbell > Fix For: 3.0-alpha-4 > > > If a pluginManagement section contains an execution/configuration/, > and is joined with a plugin, then one only property is retained. For example: > > > > > becomes: > > > -- 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-3976) raw POM retrieval
[
http://jira.codehaus.org/browse/MNG-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3976:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-4
> raw POM retrieval
> -
>
> Key: MNG-3976
> URL: http://jira.codehaus.org/browse/MNG-3976
> Project: Maven 2
> Issue Type: New Feature
> Components: Inheritance and Interpolation
>Affects Versions: 3.0-alpha-1
>Reporter: Oleg Gusakov
>Assignee: Shane Isbell
> Fix For: 3.0-alpha-4
>
>
> Add an new interface and implementation to maven-mercury component
> The interface shall look like:
> {code}
> interface PomProcessor
> {
> public List
> getRawPom( ArtifactBasicMetadata bmd
> , MetadataReader mdReader
> , Map env
> , Map sysProps
> )
> throws MetadataReaderException, PomException;
> }
> {code}
> Implementation will use callback to correctly interpolate the POM and return
> back the full POM contents. The client can the process the contents, define
> their own models, etc.
> This functionality is required for better tools integration
--
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-3422) [regression] deploy:deploy-file does not work
[ http://jira.codehaus.org/browse/MNG-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3422: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > [regression] deploy:deploy-file does not work > - > > Key: MNG-3422 > URL: http://jira.codehaus.org/browse/MNG-3422 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 3.0-alpha-1 >Reporter: Brett Porter >Assignee: Jason van Zyl > Fix For: 3.0-alpha-4 > > > mvn deploy:deploy-file -Dfile=test.sh -DrepositoryId=testing > -DartifactId=artifactId -DgroupId=groupId -Dversion=1.0 -Dpackaging=jar > -Durl=http://vesuvius.devzuz.com/private/devzuz/releases > [INFO] Searching repository for plugin with prefix: 'deploy'. > [INFO] Attempting to resolve a version for plugin: > org.apache.maven.plugins:maven-deploy-plugin using meta-version: LATEST > [INFO] Using version: 2.3 of plugin: > org.apache.maven.plugins:maven-deploy-plugin > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Maven Default Project > [INFO] > [INFO] Id: org.apache.maven:super-pom:jar:2.1 > [INFO] task-segment: [deploy:deploy-file] (aggregator-style) > [INFO] > > [INFO] [deploy:deploy-file] > [INFO] artifact groupId:artifactId: checking for updates from testing > --- > constituent[0]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/aspectjrt-1.5.3.jar > constituent[1]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/backport-util-concurrent-3.0.jar > constituent[2]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/commons-cli-1.0.jar > constituent[3]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/doxia-sink-api-1.0-alpha-9.jar > constituent[4]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/jsch-0.1.27.jar > constituent[5]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/jtidy-4aug2000r7-dev.jar > constituent[6]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-artifact-3.0-SNAPSHOT.jar > constituent[7]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-core-2.1-SNAPSHOT.jar > constituent[8]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-embedder-2.1-SNAPSHOT.jar > constituent[9]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-lifecycle-2.1-SNAPSHOT.jar > constituent[10]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-model-2.1-SNAPSHOT.jar > constituent[11]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-plugin-api-2.1-SNAPSHOT.jar > constituent[12]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-profile-2.1-SNAPSHOT.jar > constituent[13]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-project-2.1-SNAPSHOT.jar > constituent[14]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-reporting-api-2.1-SNAPSHOT.jar > constituent[15]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-container-default-1.0-alpha-44.jar > constituent[16]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-interactivity-api-1.0-alpha-6.jar > constituent[17]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-utils-1.5.1.jar > constituent[18]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/retrotranslator-runtime-1.2.1.jar > constituent[19]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-file-1.0-beta-2.jar > constituent[20]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-http-lightweight-1.0-beta-2.jar > constituent[21]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-http-shared-1.0-beta-2.jar > constituent[22]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-provider-api-1.0-beta-2.jar > constituent[23]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-1.0-beta-2.jar > constituent[24]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-common-1.0-beta-2.jar > constituent[25]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-external-1.0-beta-2.jar > --- > java.lang.NullPointerException > at > org.apache.maven.artifact.repository.DefaultArtifactRepository.pathOfRemoteRepositoryMetadata(DefaultArtifactRepository.java:123) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:390) > at > org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolveAlways(DefaultRepositoryMetadataManager.java:349) > at > org.apache.maven.artifact.repository.metadat
[jira] Updated: (MNG-3917) Complete the POM construction tests which will be the validation for the specification
[ http://jira.codehaus.org/browse/MNG-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3917: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > Complete the POM construction tests which will be the validation for the > specification > -- > > Key: MNG-3917 > URL: http://jira.codehaus.org/browse/MNG-3917 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-4 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (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: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > 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-4 > > > 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: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > 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-4 > > > 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] Updated: (MNG-3913) Figure out why MavenEmbedderExampleTest fails on the grid and reenable when fixed.
[ http://jira.codehaus.org/browse/MNG-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3913: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > Figure out why MavenEmbedderExampleTest fails on the grid and reenable when > fixed. > -- > > Key: MNG-3913 > URL: http://jira.codehaus.org/browse/MNG-3913 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-4 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3803) [regression] System properties not working any more
[
http://jira.codehaus.org/browse/MNG-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3803:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-4
> [regression] System properties not working any more
> ---
>
> Key: MNG-3803
> URL: http://jira.codehaus.org/browse/MNG-3803
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 3.0-alpha-1
>Reporter: Amélie Deltour
>Priority: Minor
> Fix For: 3.0-alpha-4
>
>
> Passing system properties to surefire-plugin used to work fine with Maven
> 2.0.9:
> {code:xml}
>
> maven-surefire-plugin
>
>
>
> my.property
> my.value
>
>
>
>
> {code}
> Now I use Maven 2.1-SNAPSHOT as Embedder launched with m2eclipse.
> The properties are not defined any more.
> In the logs with Maven 2.0.9 in debug mode I see:
> [DEBUG] Setting system property [my.property]=[my.value]
> This line is not present in the logs with Maven 2.1.
> This compatibility issue is quite annoying...
--
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-3935) Get the Maven Integration Testing Hudson plugin installed on the grid
[ http://jira.codehaus.org/browse/MNG-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3935: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > Get the Maven Integration Testing Hudson plugin installed on the grid > - > > Key: MNG-3935 > URL: http://jira.codehaus.org/browse/MNG-3935 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: John Casey > Fix For: 3.0-alpha-4 > > > I want to use this plugin to swap in new versions of Maven so I can build all > the real-world projects and touchstones projects. I know from testing > manually everything is working except Nexus Pro, but I'm ready to add XWiki > and CXF and this will be beyond manual tracking shortly. This needs to be > setup before the alpha-1 rolls out. -- 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-3854) switch dependency plugin to use Mercury
[ http://jira.codehaus.org/browse/MNG-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3854: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > switch dependency plugin to use Mercury > > > Key: MNG-3854 > URL: http://jira.codehaus.org/browse/MNG-3854 > Project: Maven 2 > Issue Type: Task > Components: Dependencies >Affects Versions: 3.0-alpha-1 > Environment: all >Reporter: Oleg Gusakov > Fix For: 3.0-alpha-4 > > > As a step towards integrating Mercury into Maven - replace dependency > resolution layer in dep. plugin with Mercury APIs -- 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-3954) Remove the RuntimeInfo required in the setting.mdo
[ http://jira.codehaus.org/browse/MNG-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3954: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > Remove the RuntimeInfo required in the setting.mdo > -- > > Key: MNG-3954 > URL: http://jira.codehaus.org/browse/MNG-3954 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-4 > > > This addition to the code segments was required to make the release plugin > work. Until plugins are refactored not to require the direct use of settings > we will need to keep this around. -- 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-3858) Use new plexus plugin manager component to load extensions
[ http://jira.codehaus.org/browse/MNG-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3858: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > Use new plexus plugin manager component to load extensions > -- > > Key: MNG-3858 > URL: http://jira.codehaus.org/browse/MNG-3858 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-4 > > > I have created a generalized component for loading extensions/plugins in > plexus-based applications which works in conjunction with the changes that we > have made to plexus to simplify dynamically loading and executing components. -- 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-3900) [regression] Properties defined by active profiles are not used for POM interpolation
[
http://jira.codehaus.org/browse/MNG-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3900:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-4
> [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
> Fix For: 3.0-alpha-4
>
>
> 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] 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: (was: 3.0-alpha-3) 3.0-alpha-4 > 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-4 > > > 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] Updated: (MNG-4009) [regression] Effects of active profiles from parent are not inherited by children.
[
http://jira.codehaus.org/browse/MNG-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-4009:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-4
> [regression] Effects of active profiles from parent are not inherited by
> children.
> --
>
> Key: MNG-4009
> URL: http://jira.codehaus.org/browse/MNG-4009
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
> Fix For: 3.0-alpha-4
>
>
> Parent POM snippet:
> {code:xml}
>
>
> parent-profile
>
>
> PASSED
>
>
>
> {code}
> The effective child POM is missing the property parentProfileProperty
> although the profile "parent-profile" has been activated from CLI.
--
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-3927) [regression] Configuration of custom plugin execution using default id pollutes configuration of default plugin executions introduced by packaging
[ http://jira.codehaus.org/browse/MNG-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3927: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > [regression] Configuration of custom plugin execution using default id > pollutes configuration of default plugin executions introduced by packaging > -- > > Key: MNG-3927 > URL: http://jira.codehaus.org/browse/MNG-3927 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 3.0-alpha-1 >Reporter: Max Powers >Assignee: Brian Fox > Fix For: 3.0-alpha-4 > > Attachments: pom.xml > > > Seems that maven is allowing pom writers to define new values for parameters > that a plugin has marked as readOnly. I have attached a pom that overrides > the resources parameter in the maven-resources-plugin. This is allowed in > 2.0.9, but fails (as it should) in 3.x (see line 89) > I would've expected to see this error (as i do in 3.x) > [ERROR] > ERROR: Cannot override read-only parameter: resources in goal: > resources:resources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3850) Integrate new Profile Activators
[ http://jira.codehaus.org/browse/MNG-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3850: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > Integrate new Profile Activators > > > Key: MNG-3850 > URL: http://jira.codehaus.org/browse/MNG-3850 > Project: Maven 2 > Issue Type: Task > Components: Profiles >Affects Versions: 3.0-alpha-2 >Reporter: Brian Fox >Assignee: Shane Isbell > Fix For: 3.0-alpha-4 > > > This is a complete replacement for the old profile activators. The new > framework uses maven-shared-model component, with model containers, model > data source and model properties for determining active profiles. -- 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-3862) Remove all plugin configuration manipulation from the plugin manager
[ http://jira.codehaus.org/browse/MNG-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3862: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > Remove all plugin configuration manipulation from the plugin manager > - > > Key: MNG-3862 > URL: http://jira.codehaus.org/browse/MNG-3862 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-4 > > > All of this work is being done by the new model framework and the rules for > manipulating the model properties. All of the requirements for plugin > configuration inheriting and merging are taken care of. We need to detangle > the plugin configuration from execution. This will pave the way to use the > new plexus plugin manager to load and execute plugins. -- 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-3925) [regression] Wrong order of plugin executions after merge with executions inherted from parent
[
http://jira.codehaus.org/browse/MNG-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3925:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-4
> [regression] Wrong order of plugin executions after merge with executions
> inherted from parent
> --
>
> Key: MNG-3925
> URL: http://jira.codehaus.org/browse/MNG-3925
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
>Assignee: Shane Isbell
> Fix For: 3.0-alpha-4
>
>
> In Maven 2.x, plugin executions defined by the child are appended to the list
> of executions inherited from the parent. Maven 3.x breaks this behavior
> (currently also depending on the usage of {{}}.
--
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-3836) [regression] Inherited collection from plugin configuration is merged with configuration from child whereas child config should completely override collection
[ http://jira.codehaus.org/browse/MNG-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3836: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > [regression] Inherited collection from plugin configuration is merged with > configuration from child whereas child config should completely override > collection > -- > > Key: MNG-3836 > URL: http://jira.codehaus.org/browse/MNG-3836 > Project: Maven 2 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 3.0-alpha-1 >Reporter: Benjamin Bentmann > Fix For: 3.0-alpha-4 > > > If both the parent and a child module define collection-valued plugin > parameters, these parameters end up being merged. However, the child config > should be the sole source for a plugin parameter if present. -- 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-3902) Remove visibility MavenProjectBuilder#buildStandaloneSuperProject
[ http://jira.codehaus.org/browse/MNG-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3902: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > Remove visibility MavenProjectBuilder#buildStandaloneSuperProject > - > > Key: MNG-3902 > URL: http://jira.codehaus.org/browse/MNG-3902 > Project: Maven 2 > Issue Type: Task >Affects Versions: 3.0-alpha-1 >Reporter: Jason van Zyl > Fix For: 3.0-alpha-4 > > > 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] Updated: (MNG-3732) [regression] project.getActiveProfiles() has not the same behaviour
[ http://jira.codehaus.org/browse/MNG-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3732: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > [regression] project.getActiveProfiles() has not the same behaviour > --- > > Key: MNG-3732 > URL: http://jira.codehaus.org/browse/MNG-3732 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 3.0-alpha-1 >Reporter: Vincent Siveton > Fix For: 3.0-alpha-4 > > > See MPH-38 -- 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-3947) [regression] Configuration of plugin execution with id "default" pollutes configuration of standalone plugin execution from CLI
[
http://jira.codehaus.org/browse/MNG-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3947:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-4
> [regression] Configuration of plugin execution with id "default" pollutes
> configuration of standalone plugin execution from CLI
> ---
>
> Key: MNG-3947
> URL: http://jira.codehaus.org/browse/MNG-3947
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0-alpha-4
>
>
> Something like
> {code:xml}
>
> default
>
> bar
>
>
> {code}
> affects the configuration of standalone goal executions from the CLI, e.g.
> {{prefix:goal}} will pick up {{foo=bar}} from the configuration for the POM
> execution. In contrast, Maven 2.x configures CLI goals only from
> {{/}} and never from {{/}}.
--
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-3853) [regression] Distribution Management injected by profile is not reflected by MavenProject
[
http://jira.codehaus.org/browse/MNG-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3853:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-4
> [regression] Distribution Management injected by profile is not reflected by
> MavenProject
> -
>
> Key: MNG-3853
> URL: http://jira.codehaus.org/browse/MNG-3853
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories, Profiles
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
> Fix For: 3.0-alpha-4
>
>
> The cause of the user reported issue [Tycho: problem with
> distributionManagement in
> profile|http://www.nabble.com/Tycho%3A-problem-with-distributionManagement-in-profile-to20490017.html]
> is that the aritfact repos are created in the constructor of
> {{MavenProject}} but the the profiles are injected in a later step.
> There is other setup code in the constructor which most likely is also
> affected.
--
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-4008) [regression] Build filters are collapsed
[
http://jira.codehaus.org/browse/MNG-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-4008:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-4
> [regression] Build filters are collapsed
>
>
> Key: MNG-4008
> URL: http://jira.codehaus.org/browse/MNG-4008
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
> Fix For: 3.0-alpha-4
>
>
> Input POM snippet:
> {code:xml}
>
>
> src/main/filters/a.properties
> src/main/filters/c.properties
> src/main/filters/b.properties
> src/main/filters/d.properties
>
>
> {code}
> Effective POM:
> {code:xml}
>
>
> src/main/filters/a.properties
>
>
> {code}
> i.e. only one filter definition survives.
--
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-3782) [regression] Variable substition not performed in transitive dependency using value from active profile
[ http://jira.codehaus.org/browse/MNG-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3782: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > [regression] Variable substition not performed in transitive dependency using > value from active profile > --- > > Key: MNG-3782 > URL: http://jira.codehaus.org/browse/MNG-3782 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.0-alpha-1 > Environment: Java version: 1.6.0_07 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Robert Varttinen > Fix For: 3.0-alpha-4 > > Attachments: build.log, example.zip, MavenCli.java, > MyEclipseArtifactResolver.zip, settings.xml > > > When invoking the 'mvn compile' command and a profile is active, defined in > settings.xml, a variable substitution is not performed in a transitive > dependency. > In the example provided the project to be built, C, depends on B which in its > turn depends on A. The versions of B and A to be used are defined in a > profile, the POM-files defines a variable indicating the versions. The > profile in question is defined in the settings.xml and is always active > (check with command 'mvn help:active-profiles'). The results of project A and > B are successfully built and installed in the local repository. > Invoking a build for project C using a command line parameter indicating, > 'mvn compile -Dparentversion=0.0.1-SNAPSHOT, the versions render a successful > build. The transitive dependency is resolved correctly. > This problem is also visible in Eclipse, m2eclipse, as the project C in the > example provided, does not build (error indication). The example provided > includes Eclipse projects displaying this (version 0.9.7.20081001-2217 of the > Eclipse plugin is used). > The settings.xml and a build log are provided as attachments to this issue. -- 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-4 > 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-4 > > > 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-3932) Remove all mirror, authentication, and proxy handling out of WagonManager and into a neutral Maven implementation
[ http://jira.codehaus.org/browse/MNG-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3932: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > Remove all mirror, authentication, and proxy handling out of WagonManager and > into a neutral Maven implementation > - > > Key: MNG-3932 > URL: http://jira.codehaus.org/browse/MNG-3932 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-4 > > > We need to protect ourselves from the underlying transport implementation. > Mercury will only touch Maven inside one component, so this is what I'm going > to create on a branch where Wagon only touches Maven inside one component. I > can't really implement the plugin manager properly without hardcoding because > I can't get the correct mirror information to Mercury without wiring in the > WagonManager which I'm not going to do. I'm just going to do it properly. We > won't have extension support in alpha-1. Oh well. -- 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-4005) Throw Validation Error if pom contains a dependency with two different versions.
[ http://jira.codehaus.org/browse/MNG-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-4005: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > Throw Validation Error if pom contains a dependency with two different > versions. > > > Key: MNG-4005 > URL: http://jira.codehaus.org/browse/MNG-4005 > Project: Maven 2 > Issue Type: Improvement > Components: Inheritance and Interpolation >Affects Versions: 3.0-alpha-2 >Reporter: Shane Isbell >Assignee: Shane Isbell > Fix For: 3.0-alpha-4 > > > Throw a validation error if a pom contains the same dependency with two > different versions. -- 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-3848) [regression] Inheritance of project/site/scm URLs does not take child's relative location to parent into account
[
http://jira.codehaus.org/browse/MNG-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3848:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-4
> [regression] Inheritance of project/site/scm URLs does not take child's
> relative location to parent into account
>
>
> Key: MNG-3848
> URL: http://jira.codehaus.org/browse/MNG-3848
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0-alpha-4
>
>
> For a multi-module layout like
> {noformat}
> parent/
> pom.xml
> child/
> pom.xml
> {noformat}
> and a project URL like "http://foo.org/parent"; inherited from the parent, the
> child is expected to end up with the URL "http://foo.org/child"; instead of
> "http://foo.org/parent/child";, i.e. the child's relative location to the
> parent should be considered during inheritance.
--
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-3918) NPE in CLIReportingUtils
[
http://jira.codehaus.org/browse/MNG-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3918:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-4
> NPE in CLIReportingUtils
>
>
> Key: MNG-3918
> URL: http://jira.codehaus.org/browse/MNG-3918
> Project: Maven 2
> Issue Type: Bug
> Components: Errors
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0-alpha-4
>
> Attachments: pom.xml
>
>
> Running "mvn validate" on the attached POM delivers:
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.maven.cli.CLIReportingUtils.handleLifecycleExecutionException(CLIReportingUtils.java:270)
> at
> org.apache.maven.cli.CLIReportingUtils.buildErrorMessage(CLIReportingUtils.java:217)
> at
> org.apache.maven.cli.CLIReportingUtils.showError(CLIReportingUtils.java:162)
> at
> org.apache.maven.cli.CLIReportingUtils.showError(CLIReportingUtils.java:138)
> at
> org.apache.maven.cli.CLIReportingUtils.logResult(CLIReportingUtils.java:80)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:171)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
> 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:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:31)
> {noformat}
> While the POM is indeed invalid, the original error message doesn't make it
> to the user.
> The {{LifecycleExecutionException}} to report has no project instance. In
> this particular case, the exception is created in
> {{DefaultLifecycleExecutor}} by wrapping a
> {{LifecycleSpecificationException}}. This raises the question whether the
> class {{LifecycleException}} should provide a field to carry a
> {{MavenProject}} instance, which could then be propagated to the wrapping
> exception.
--
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: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > 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 >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > 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] 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-4) 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-3013) The plugin manager incorrectly caches plugin versions between embedder calls
[ http://jira.codehaus.org/browse/MNG-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3013: --- Issue Type: Sub-task (was: Bug) Parent: MNG-2765 > The plugin manager incorrectly caches plugin versions between embedder calls > > > Key: MNG-3013 > URL: http://jira.codehaus.org/browse/MNG-3013 > Project: Maven 2 > Issue Type: Sub-task > Components: Embedding >Affects Versions: 3.0-alpha-1 >Reporter: Carlos Sanchez >Assignee: Carlos Sanchez > Fix For: 3.0-alpha-4 > > > If you call the embedder once with a project and then change a plugin version > in the pom and run the same embedder the old version is used. > DefaultPluginManager.java lines 386-391 in revision 541121 > https://svn.apache.org/viewvc/maven/components/trunk/maven-core/src/main/java/org/apache/maven/plugin/DefaultPluginManager.java?annotate=536027 > was added in revision 498048 > https://svn.apache.org/viewvc/maven/components/trunk/maven-core/src/main/java/org/apache/maven/plugin/DefaultPluginManager.java?view=diff&r1=498047&r2=498048 > Any problem with removing that if block ? -- 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-3862) Remove all plugin configuration manipulation from the plugin manager
[ http://jira.codehaus.org/browse/MNG-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3862: --- Issue Type: Sub-task (was: Task) Parent: MNG-2765 > Remove all plugin configuration manipulation from the plugin manager > - > > Key: MNG-3862 > URL: http://jira.codehaus.org/browse/MNG-3862 > Project: Maven 2 > Issue Type: Sub-task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-4 > > > All of this work is being done by the new model framework and the rules for > manipulating the model properties. All of the requirements for plugin > configuration inheriting and merging are taken care of. We need to detangle > the plugin configuration from execution. This will pave the way to use the > new plexus plugin manager to load and execute plugins. -- 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-3935) Get the Maven Integration Testing Hudson plugin installed on the grid
[ http://jira.codehaus.org/browse/MNG-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3935: --- Fix Version/s: (was: 3.0-alpha-4) 3.0-alpha-3 > Get the Maven Integration Testing Hudson plugin installed on the grid > - > > Key: MNG-3935 > URL: http://jira.codehaus.org/browse/MNG-3935 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: John Casey > Fix For: 3.0-alpha-3 > > > I want to use this plugin to swap in new versions of Maven so I can build all > the real-world projects and touchstones projects. I know from testing > manually everything is working except Nexus Pro, but I'm ready to add XWiki > and CXF and this will be beyond manual tracking shortly. This needs to be > setup before the alpha-1 rolls out. -- 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-3925) [regression] Wrong order of plugin executions after merge with executions inherted from parent
[
http://jira.codehaus.org/browse/MNG-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3925:
---
Fix Version/s: (was: 3.0-alpha-4)
3.0-alpha-3
> [regression] Wrong order of plugin executions after merge with executions
> inherted from parent
> --
>
> Key: MNG-3925
> URL: http://jira.codehaus.org/browse/MNG-3925
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
>Assignee: Shane Isbell
> Fix For: 3.0-alpha-3
>
>
> In Maven 2.x, plugin executions defined by the child are appended to the list
> of executions inherited from the parent. Maven 3.x breaks this behavior
> (currently also depending on the usage of {{}}.
--
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-3858) Use new plexus plugin manager component to load extensions
[ http://jira.codehaus.org/browse/MNG-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3858: --- Fix Version/s: (was: 3.0-alpha-4) 3.0-alpha-3 > Use new plexus plugin manager component to load extensions > -- > > Key: MNG-3858 > URL: http://jira.codehaus.org/browse/MNG-3858 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > I have created a generalized component for loading extensions/plugins in > plexus-based applications which works in conjunction with the changes that we > have made to plexus to simplify dynamically loading and executing components. -- 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-3683) [regression] Help plugin does not work
[
http://jira.codehaus.org/browse/MNG-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3683:
---
Fix Version/s: (was: 3.0-alpha-4)
3.0-alpha-3
> [regression] Help plugin does not work
> --
>
> Key: MNG-3683
> URL: http://jira.codehaus.org/browse/MNG-3683
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin Requests
>Reporter: Brett Porter
>Assignee: Jason van Zyl
> Fix For: 3.0-alpha-3
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> The following command:
> mvn help:describe -Dplugin=site
> Gives the error:
> [ERROR]
> Maven encountered an error while configuring one of the mojos for your build.
> Mojo:
> Group-Id: org.apache.maven.plugins
> Artifact-Id: maven-help-plugin
> Version: 2.0.2
> Mojo: describe
> brought in via: Direct invocation
> While building project:
> Group-Id: org.apache.continuum
> Artifact-Id: continuum-docs
> Version: 1.2-SNAPSHOT
> From file: /Users/brett/scm/continuum/continuum/continuum-docs/pom.xml
> Here is the configuration it attempted to apply to the mojo:
> ${artifactId}
> ${full}
> ${groupId}
> ${localRepository}
> ${medium}
> ${mojo}
> ${output}
> ${plugin}
> ${project}
> ${session}
> ${settings}
> ${version}
>
> Error
> message:org.codehaus.plexus.component.configurator.ComponentConfigurationException:
> Invalid parameter supplied while setting
> 'org.apache.maven.plugin.mojoexecut...@a2f216' to
> org.apache.maven.plugins.help.DescribeMojo.setMojo( java.lang.Class )
--
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-3995) Configuration Property Lost In Join of PluginManagement/Plugin
[ http://jira.codehaus.org/browse/MNG-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3995: --- Fix Version/s: (was: 3.0-alpha-4) 3.0-alpha-3 > Configuration Property Lost In Join of PluginManagement/Plugin > -- > > Key: MNG-3995 > URL: http://jira.codehaus.org/browse/MNG-3995 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 3.0-alpha-2 >Reporter: Shane Isbell >Assignee: Shane Isbell > Fix For: 3.0-alpha-3 > > > If a pluginManagement section contains an execution/configuration/, > and is joined with a plugin, then one only property is retained. For example: > > > > > becomes: > > > -- 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-3422) [regression] deploy:deploy-file does not work
[ http://jira.codehaus.org/browse/MNG-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3422: --- Fix Version/s: (was: 3.0-alpha-4) 3.0-alpha-3 > [regression] deploy:deploy-file does not work > - > > Key: MNG-3422 > URL: http://jira.codehaus.org/browse/MNG-3422 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 3.0-alpha-1 >Reporter: Brett Porter >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > mvn deploy:deploy-file -Dfile=test.sh -DrepositoryId=testing > -DartifactId=artifactId -DgroupId=groupId -Dversion=1.0 -Dpackaging=jar > -Durl=http://vesuvius.devzuz.com/private/devzuz/releases > [INFO] Searching repository for plugin with prefix: 'deploy'. > [INFO] Attempting to resolve a version for plugin: > org.apache.maven.plugins:maven-deploy-plugin using meta-version: LATEST > [INFO] Using version: 2.3 of plugin: > org.apache.maven.plugins:maven-deploy-plugin > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Maven Default Project > [INFO] > [INFO] Id: org.apache.maven:super-pom:jar:2.1 > [INFO] task-segment: [deploy:deploy-file] (aggregator-style) > [INFO] > > [INFO] [deploy:deploy-file] > [INFO] artifact groupId:artifactId: checking for updates from testing > --- > constituent[0]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/aspectjrt-1.5.3.jar > constituent[1]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/backport-util-concurrent-3.0.jar > constituent[2]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/commons-cli-1.0.jar > constituent[3]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/doxia-sink-api-1.0-alpha-9.jar > constituent[4]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/jsch-0.1.27.jar > constituent[5]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/jtidy-4aug2000r7-dev.jar > constituent[6]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-artifact-3.0-SNAPSHOT.jar > constituent[7]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-core-2.1-SNAPSHOT.jar > constituent[8]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-embedder-2.1-SNAPSHOT.jar > constituent[9]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-lifecycle-2.1-SNAPSHOT.jar > constituent[10]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-model-2.1-SNAPSHOT.jar > constituent[11]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-plugin-api-2.1-SNAPSHOT.jar > constituent[12]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-profile-2.1-SNAPSHOT.jar > constituent[13]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-project-2.1-SNAPSHOT.jar > constituent[14]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-reporting-api-2.1-SNAPSHOT.jar > constituent[15]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-container-default-1.0-alpha-44.jar > constituent[16]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-interactivity-api-1.0-alpha-6.jar > constituent[17]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-utils-1.5.1.jar > constituent[18]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/retrotranslator-runtime-1.2.1.jar > constituent[19]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-file-1.0-beta-2.jar > constituent[20]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-http-lightweight-1.0-beta-2.jar > constituent[21]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-http-shared-1.0-beta-2.jar > constituent[22]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-provider-api-1.0-beta-2.jar > constituent[23]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-1.0-beta-2.jar > constituent[24]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-common-1.0-beta-2.jar > constituent[25]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-external-1.0-beta-2.jar > --- > java.lang.NullPointerException > at > org.apache.maven.artifact.repository.DefaultArtifactRepository.pathOfRemoteRepositoryMetadata(DefaultArtifactRepository.java:123) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:390) > at > org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolveAlways(DefaultRepositoryMetadataManager.java:349) > at > org.apache.maven.artifact.repository.metadat
[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: (was: 3.0-alpha-4) 3.0-alpha-3 > 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-3 > > > 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] Updated: (MNG-3927) [regression] Configuration of custom plugin execution using default id pollutes configuration of default plugin executions introduced by packaging
[ http://jira.codehaus.org/browse/MNG-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3927: --- Fix Version/s: (was: 3.0-alpha-4) 3.0-alpha-3 > [regression] Configuration of custom plugin execution using default id > pollutes configuration of default plugin executions introduced by packaging > -- > > Key: MNG-3927 > URL: http://jira.codehaus.org/browse/MNG-3927 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 3.0-alpha-1 >Reporter: Max Powers >Assignee: Brian Fox > Fix For: 3.0-alpha-3 > > Attachments: pom.xml > > > Seems that maven is allowing pom writers to define new values for parameters > that a plugin has marked as readOnly. I have attached a pom that overrides > the resources parameter in the maven-resources-plugin. This is allowed in > 2.0.9, but fails (as it should) in 3.x (see line 89) > I would've expected to see this error (as i do in 3.x) > [ERROR] > ERROR: Cannot override read-only parameter: resources in goal: > resources:resources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3954) Remove the RuntimeInfo required in the setting.mdo
[ http://jira.codehaus.org/browse/MNG-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3954: --- Fix Version/s: (was: 3.0-alpha-4) 3.0-alpha-3 > Remove the RuntimeInfo required in the setting.mdo > -- > > Key: MNG-3954 > URL: http://jira.codehaus.org/browse/MNG-3954 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > This addition to the code segments was required to make the release plugin > work. Until plugins are refactored not to require the direct use of settings > we will need to keep this around. -- 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-3932) Remove all mirror, authentication, and proxy handling out of WagonManager and into a neutral Maven implementation
[ http://jira.codehaus.org/browse/MNG-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3932: --- Fix Version/s: (was: 3.0-alpha-4) 3.0-alpha-3 > Remove all mirror, authentication, and proxy handling out of WagonManager and > into a neutral Maven implementation > - > > Key: MNG-3932 > URL: http://jira.codehaus.org/browse/MNG-3932 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > We need to protect ourselves from the underlying transport implementation. > Mercury will only touch Maven inside one component, so this is what I'm going > to create on a branch where Wagon only touches Maven inside one component. I > can't really implement the plugin manager properly without hardcoding because > I can't get the correct mirror information to Mercury without wiring in the > WagonManager which I'm not going to do. I'm just going to do it properly. We > won't have extension support in alpha-1. Oh well. -- 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-3862) Remove all plugin configuration manipulation from the plugin manager
[ http://jira.codehaus.org/browse/MNG-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3862: --- Fix Version/s: (was: 3.0-alpha-4) 3.0-alpha-3 > Remove all plugin configuration manipulation from the plugin manager > - > > Key: MNG-3862 > URL: http://jira.codehaus.org/browse/MNG-3862 > Project: Maven 2 > Issue Type: Sub-task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > All of this work is being done by the new model framework and the rules for > manipulating the model properties. All of the requirements for plugin > configuration inheriting and merging are taken care of. We need to detangle > the plugin configuration from execution. This will pave the way to use the > new plexus plugin manager to load and execute plugins. -- 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-3872) Profiles not being activated for relocated POMs
[ http://jira.codehaus.org/browse/MNG-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3872: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-4 > Profiles not being activated for relocated POMs > --- > > Key: MNG-3872 > URL: http://jira.codehaus.org/browse/MNG-3872 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 3.0-alpha-1 >Reporter: Shane Isbell >Assignee: Shane Isbell >Priority: Minor > Fix For: 3.0-alpha-4 > > > Profiles are not being activated for relocated POMs. This causes certain POMs > to throw a validation error. -- 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: (MEAR-100) Support altDeploymentDescriptor for J2EE 1.4
Support altDeploymentDescriptor for J2EE 1.4 Key: MEAR-100 URL: http://jira.codehaus.org/browse/MEAR-100 Project: Maven 2.x Ear Plugin Issue Type: Bug Affects Versions: 2.3.1 Reporter: Shelley Baker The altDeploymentDescriptor is only supported by the maven-ear-plugin for Java EE 5 [1], but the alt-dd element is available in previous versions of J2EE [2,3,4]. Can this element be applied to all Java EE versions? [1] http://maven.apache.org/plugins/maven-ear-plugin/modules.html [2] http://java.sun.com/j2ee/dtds/application_1_2.dtd [3] http://java.sun.com/dtd/application_1_3.dtd [4] http://java.sun.com/xml/ns/j2ee/application_1_4.xsd -- 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: (MPMD-92) Using JDK 1.6 causes "ParseException: Can't use generics unless running in JDK 1.5 mode! " unless set targetJdk to 1.5, not 1.6
[ http://jira.codehaus.org/browse/MPMD-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163180#action_163180 ] Paul Sundling commented on MPMD-92: --- You were totally right! MNG-3385 was what was really causing the problem! If I would have known that it would have saved me the time of creating a use case. Guess I'll have to add versions in the reporting section. > Using JDK 1.6 causes "ParseException: Can't use generics unless running in > JDK 1.5 mode! " unless set targetJdk to 1.5, not 1.6 > --- > > Key: MPMD-92 > URL: http://jira.codehaus.org/browse/MPMD-92 > Project: Maven 2.x PMD Plugin > Issue Type: Bug > Components: PMD >Affects Versions: 2.4 >Reporter: Paul Sundling >Assignee: Benjamin Bentmann > Attachments: minimal.zip, MPMD-92.zip > > > Related to http://jira.codehaus.org/browse/MPMD-67 , although they asked me > to open a new issue and since this affects a new version. > This error does not appear when invoking 'mvn pmd:pmd', but only when doing > 'mvn site:site site:deploy'. > It generates at least two types of warnings and related stacktraces: > 1. Caused by: net.sourceforge.pmd.ast.ParseException: ERROR: Can't use enum > as a keyword in pre-JDK 1.5 target > 2. Caused by: net.sourceforge.pmd.ast.ParseException: Can't use generics > unless running in JDK 1.5 mode! > The following zip replicates the problem. > Use JDK 1.6 and use 1.6 and it should fail, even if > you set the compiler to be 1.5. Change to 1.5 and it > should work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3989) Simple handling of external jars
[ http://jira.codehaus.org/browse/MNG-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163208#action_163208 ] Jason van Zyl commented on MNG-3989: In what case can't you make it easier for your users by putting it in a repository? What's the case that made you ask for this? > Simple handling of external jars > > > Key: MNG-3989 > URL: http://jira.codehaus.org/browse/MNG-3989 > Project: Maven 2 > Issue Type: New Feature >Affects Versions: 2.0.9 >Reporter: Greg Wilkins > > For whatever reason, there will always be jars that don't exist in a maven > repository. > There are numerous techniques for these - installing them in your local repo > (either manually or with > some bootstrap.sh script or special profile activation). Checking in the > jars into a local maven repository that is checked into svn > and then point to it from your settings.xml and/or top level pom (with aid of > an env variable). > But all these methods lack a very important features. You can just do: "svn > co http:/myproj.com/foo; cd foo; mvn" > If the jars change, you can't just do "svn up; mvn", you have to re-run > whatever script/profile installed the repo. > It's all rather a PITA. > What I want, is some way to have a module of a project that contains some > non-maven jars that when I > do a "mvn install" in that project, install those jars in my local repository > for use by my other modules. If the > jars are not updated, then nothing is done. > With something like this, projects that have external dependencies could > describe them to maven and > make them available for use, without manual steps and special scripts. -- 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: (MDEP-194) ArchiverException when using maven dependency plugin in multi-module projects
[
http://jira.codehaus.org/browse/MDEP-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163226#action_163226
]
Pailin Suttiwirairat commented on MDEP-194:
---
This issue also occur in unpack goal when I try to import the projects to
eclipse (The projects has structure like above). But the exceptions are
difference.
An error message in maven console :
{quote}
Build errors for example-project;
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the
plugin manager executing goal
'org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack': Mojo
execution failed.
{quote}
The exception :
{quote}
Error log:
!ENTRY org.maven.ide.eclipse 4 0 2009-01-26 17:49:41.784
!MESSAGE Build errors for example-project
!STACK 0
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the
plugin manager executing goal
'org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack': Mojo
execution failed.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505)
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:904)
at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl$MavenExecutor.execute(MavenProjectManagerImpl.java:1041)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl$1.execute(MavenProjectManagerImpl.java:1075)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.execute(MavenProjectManagerImpl.java:997)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.execute(MavenProjectManagerImpl.java:1072)
at
org.maven.ide.eclipse.internal.project.MavenProjectFacade.execute(MavenProjectFacade.java:316)
at
org.maven.ide.eclipse.internal.builder.MavenBuilder.executePostBuild(MavenBuilder.java:173)
at
org.maven.ide.eclipse.internal.builder.MavenBuilder.build(MavenBuilder.java:87)
at
org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
at
org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309)
at
org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341)
at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140)
at
org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.apache.maven.plugin.PluginExecutionException: Mojo execution
failed.
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:601)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
... 28 more
Caused by: org.apache.maven.plugin.MojoExecutionException: Unknown archiver type
at
org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:236)
at
org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.unpackArtifact(UnpackMojo.java:103)
at
org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.execute(UnpackMojo.java:74)
at
org.apache.maven.plugin.DefaultPluginManager.execut
[jira] Issue Comment Edited: (MDEP-194) ArchiverException when using maven dependency plugin in multi-module projects
[
http://jira.codehaus.org/browse/MDEP-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163226#action_163226
]
Pailin Suttiwirairat edited comment on MDEP-194 at 1/30/09 12:50 AM:
-
This issue also occur in unpack goal when I try to import the projects to
eclipse (The projects has structure like above). But the exceptions are
difference.
An error message in maven console :
{noformat}
Build errors for example-project;
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the
plugin manager executing goal
'org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack': Mojo
execution failed.
{noformat}
The exception :
{noformat}
Error log:
!ENTRY org.maven.ide.eclipse 4 0 2009-01-26 17:49:41.784
!MESSAGE Build errors for example-project
!STACK 0
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the
plugin manager executing goal
'org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack': Mojo
execution failed.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505)
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:904)
at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl$MavenExecutor.execute(MavenProjectManagerImpl.java:1041)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl$1.execute(MavenProjectManagerImpl.java:1075)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.execute(MavenProjectManagerImpl.java:997)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.execute(MavenProjectManagerImpl.java:1072)
at
org.maven.ide.eclipse.internal.project.MavenProjectFacade.execute(MavenProjectFacade.java:316)
at
org.maven.ide.eclipse.internal.builder.MavenBuilder.executePostBuild(MavenBuilder.java:173)
at
org.maven.ide.eclipse.internal.builder.MavenBuilder.build(MavenBuilder.java:87)
at
org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
at
org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309)
at
org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341)
at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140)
at
org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.apache.maven.plugin.PluginExecutionException: Mojo execution
failed.
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:601)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
... 28 more
Caused by: org.apache.maven.plugin.MojoExecutionException: Unknown archiver type
at
org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:236)
at
org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.unpackArtifact(UnpackMojo.java:103)
at
org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.execute(UnpackMojo.java:74)
[jira] Issue Comment Edited: (MDEP-194) ArchiverException when using maven dependency plugin in multi-module projects
[
http://jira.codehaus.org/browse/MDEP-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163226#action_163226
]
Pailin Suttiwirairat edited comment on MDEP-194 at 1/30/09 12:53 AM:
-
This issue also occur in unpack goal when I try to import the projects to
eclipse (The projects has structure like above). But the exceptions are
difference.
An error message in maven console :
{noformat}
Build errors for example-project;
org.apache.maven.lifecycle.LifecycleExecutionException:
Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack':
Mojo execution failed.
{noformat}
The exception :
{noformat}
Error log:
!ENTRY org.maven.ide.eclipse 4 0 2009-01-26 17:49:41.784
!MESSAGE Build errors for example-project
!STACK 0
org.apache.maven.lifecycle.LifecycleExecutionException:
Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack': Mojo
execution failed.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505)
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:904)
at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl$MavenExecutor.execute(MavenProjectManagerImpl.java:1041)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl$1.execute(MavenProjectManagerImpl.java:1075)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.execute(MavenProjectManagerImpl.java:997)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.execute(MavenProjectManagerImpl.java:1072)
at
org.maven.ide.eclipse.internal.project.MavenProjectFacade.execute(MavenProjectFacade.java:316)
at
org.maven.ide.eclipse.internal.builder.MavenBuilder.executePostBuild(MavenBuilder.java:173)
at
org.maven.ide.eclipse.internal.builder.MavenBuilder.build(MavenBuilder.java:87)
at
org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
at
org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309)
at
org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341)
at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140)
at
org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.apache.maven.plugin.PluginExecutionException: Mojo execution
failed.
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:601)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
... 28 more
Caused by: org.apache.maven.plugin.MojoExecutionException: Unknown archiver type
at
org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:236)
at
org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.unpackArtifact(UnpackMojo.java:103)
at
org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.execute(UnpackMojo.java:74)
[jira] Issue Comment Edited: (MDEP-194) ArchiverException when using maven dependency plugin in multi-module projects
[
http://jira.codehaus.org/browse/MDEP-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163226#action_163226
]
Pailin Suttiwirairat edited comment on MDEP-194 at 1/30/09 1:29 AM:
This issue also occur in unpack goal when I try to import the projects to
eclipse (The projects has structure like above). But the exceptions are
difference.
An error message in maven console :
{noformat}
Build errors for example-project;
org.apache.maven.lifecycle.LifecycleExecutionException:
Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack':
Mojo execution failed.
{noformat}
The exception :
{noformat}
Error log:
!ENTRY org.maven.ide.eclipse 4 0 2009-01-26 17:49:41.784
!MESSAGE Build errors for example-project
!STACK 0
org.apache.maven.lifecycle.LifecycleExecutionException:
Internal error in the plugin manager executing goal
org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack': Mojo
execution failed.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505)
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:904)
at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl$MavenExecutor.execute(MavenProjectManagerImpl.java:1041)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl$1.execute(MavenProjectManagerImpl.java:1075)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.execute(MavenProjectManagerImpl.java:997)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.execute(MavenProjectManagerImpl.java:1072)
at
org.maven.ide.eclipse.internal.project.MavenProjectFacade.execute(MavenProjectFacade.java:316)
at
org.maven.ide.eclipse.internal.builder.MavenBuilder.executePostBuild(MavenBuilder.java:173)
at
org.maven.ide.eclipse.internal.builder.MavenBuilder.build(MavenBuilder.java:87)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.apache.maven.plugin.PluginExecutionException: Mojo execution
failed.
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:601)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
... 28 more
Caused by: org.apache.maven.plugin.MojoExecutionException: Unknown archiver type
at
org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:236)
at
org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.unpackArtifact(UnpackMojo.java:103)
at
org.apache.maven.plugin.dependency.fromConfiguration.UnpackMojo.execute(UnpackMojo.java:74)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
... 29 more
Caused by: org.codehaus.plexus.archiver.manager.NoSuchArchiverException: No
such archiver: ''.
at
org.codehaus.plexus.archiver.manager.DefaultArchiverManager.getUnArchiver(DefaultArchiverManager.java:80)
at
org.codehaus.plexus.archiver.manager.DefaultArchiverManager.getUnArchiver(DefaultArchiverManager.java:114)
at
org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:221)
... 32 more
{noformat}
was (Author: pailin):
This issue also occur in unpack goa
