Eclipse 3.7 release comes with Maven support built in
See: http://s.apache.org/m2eblog Niall - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: ${version} in 3.0
On Sun, Oct 10, 2010 at 1:18 AM, Jason Chaffee jchaf...@ebates.com wrote:
I am getting this warning for every module, yet I am not using this variable
any of the poms. Some poms do have ${project.version} but some of them don't
have any variable expressions at all and it is still outputting this warning.
Does this warning just get output regardless of what is the the pom?
[WARNING] The expression ${version} is deprecated. Please use
${project.version} instead.
What about other places like assembly plugin config files?
Niall
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Correcting a groupID
On Tue, Aug 24, 2010 at 7:37 PM, sebb seb...@gmail.com wrote: On 24 August 2010 19:17, EJ Ciramella ecirame...@casenetinc.com wrote: No, we didn't realize the relocation poms existed until it was too late. We wanted to match up in source control/java package/groupId/artifactId so that they were uniform. Which is great because from just about any angle (stacktrace, source path, package name in IDE) you know exactly where to look elsewhere to find something (say, you wanna look at local disk or source browser, etc). The main problem was communication. There was a lot of hate mail as older modules that hadn't been touched in a long time were dredged up for something or another and when people tried to point at newer version of the relocated libraries, things were missing, etc. There were maybe, 50 or more versions for any of the moved modules floating around that all would need these silly relocation poms to support older builds. What do you mean here? Are you saying that if the groupId is changed for a new release, one also needs to change all existing releases to add relocation poms? I thought one only had to add the relocation POMs for the new releases? Everything is possible given an endless amount of time/energy/etc. We wound up having to branch things just to update groupIds, blah blah blah - it was a mess. This is a massive generalization. Keep it stupid simple, right? Don't move things around... I'm not proposing moving anything around; just changing the groupId going forward. Is that likely to cause any problems? Yes - the problem is going to be users getting more than one copy of an artefact on their classpath. its been discussed a few times on the Commons dev list - I found the following thread. http://markmail.org/message/tky6c734r2dia2gd AIUI relocation can't really help with this Niall -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Tuesday, August 24, 2010 2:08 PM To: Maven Users List Subject: Re: Correcting a groupID On 24 August 2010 18:44, EJ Ciramella ecirame...@casenetinc.com wrote: Yeah, I know - hate to cross-pollinate here but the Nexus bible states the repo is for deposits only. Essentially backing up the just change NEW snapshots/releases, leave the old ones where they are sentiment. OK In another life, I casually agreed we should change the groupId of an artifact and all hell broke loose... Did you use relocation POMs? What were the exact problems? Could they have been avoided, and if so, how? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [FATAL ERROR] SiteMojo#execute() caused a linkage error (NoClassDefFoundError: org/apache/commons/lang/ArrayUtils)
On Fri, Oct 23, 2009 at 9:03 PM, Jörg Schaible joerg.schai...@gmx.de wrote:
Hi Niall,
Niall Pemberton wrote:
Merci Beaucoup - thats fixed it. Still not sure why it just started
happening though.
It seems the version of the plugin is not locked:
We had it specified in the reporting section, but not
pluginManagement - adding it to pluginManagement (without the lang
dependency) does seem to fix it. Don't know why this matters in 2.1+
and why a reporting plugin needs it - perhaps because the site
plugin is a *specical citizen* in Maven2
Anyway, I'll update the pom
Thanks
Niall
% =
~/src/Commons/proper/beanutils $ mvn versions:display-plugin-updates
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'versions'.
[INFO]
[INFO] Building Commons BeanUtils
[INFO] task-segment: [versions:display-plugin-updates]
[INFO]
[INFO] [versions:display-plugin-updates {execution: default-cli}]
[INFO]
[INFO] All plugins with a version specified are using the latest versions.
[INFO]
[WARNING] The following plugins do not have their version specified:
[WARNING] maven-resources-plugin .. (from super-pom)
2.2
[WARNING] maven-site-plugin (from super-pom)
2.0-beta-5
[INFO]
[INFO]
% =
Nevertheless strange, since it should have inherited the version from the
parent. With Maven 2.1.0 you get the same result. However, for Maven 2.0.10
the site plugin seems suddenly locked. Maybe a regression in Maven 2.1.x
and upwards ??
- Jörg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[FATAL ERROR] SiteMojo#execute() caused a linkage error (NoClassDefFoundError: org/apache/commons/lang/ArrayUtils)
I'm getting the following error when I try to run mvn site on Commons Beanutils[1] I'm using maven 2.2.1 - it was working fine a week or so ago. I've been playing with maven 3.x though and have just switched back to 2.2.1, so I'm wondering if thats the cause. Any ideas I've searched the archives and this type of error seems to come up quite a but, but Niall [1] http://svn.apache.org/repos/asf/commons/proper/beanutils/trunk/ [INFO] Generating Project Team report. [FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused a linkage error (java.lang.NoClassDefFoundError) and may be out-of-date. Check the realms: [FATAL ERROR] Plugin realm = app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.0.1] urls[0] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.0.1/maven-site-plugin-2.0.1.jar urls[1] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar urls[2] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.0/doxia-module-xhtml-1.0.jar urls[3] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-core/1.0/doxia-core-1.0.jar urls[4] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.0/doxia-decoration-model-1.0.jar urls[5] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.0/doxia-site-renderer-1.0.jar urls[6] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar urls[7] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.7/plexus-velocity-1.1.7.jar urls[8] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar urls[9] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar urls[10] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/commons-lang/commons-lang/2.1/commons-lang-2.1.jar urls[11] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar urls[12] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.0/doxia-module-apt-1.0.jar urls[13] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.0/doxia-module-fml-1.0.jar urls[14] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.0/doxia-module-xdoc-1.0.jar urls[15] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar urls[16] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar urls[17] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar urls[18] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/mortbay/jetty/jetty/6.1.5/jetty-6.1.5.jar urls[19] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/mortbay/jetty/jetty-util/6.1.5/jetty-util-6.1.5.jar urls[20] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/mortbay/jetty/servlet-api-2.5/6.1.5/servlet-api-2.5-6.1.5.jar [FATAL ERROR] Container realm = plexus.core urls[0] = file:/C:/j/maven-2.2.1/lib/maven-2.2.1-uber.jar [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org/apache/commons/lang/ArrayUtils org.apache.commons.lang.ArrayUtils [INFO] [INFO] Trace java.lang.NoClassDefFoundError: org/apache/commons/lang/ArrayUtils at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:143) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203) at org.apache.velocity.runtime.parser.node.ASTReference.evaluate(ASTReference.java:396) at org.apache.velocity.runtime.parser.node.ASTOrNode.evaluate(ASTOrNode.java:99) at org.apache.velocity.runtime.parser.node.ASTExpression.evaluate(ASTExpression.java:64) at org.apache.velocity.runtime.parser.node.ASTNotNode.evaluate(ASTNotNode.java:64) at org.apache.velocity.runtime.parser.node.ASTExpression.evaluate(ASTExpression.java:64) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:86) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74) at
Re: [FATAL ERROR] SiteMojo#execute() caused a linkage error (NoClassDefFoundError: org/apache/commons/lang/ArrayUtils)
Merci Beaucoup - thats fixed it. Still not sure why it just started happening though. Niall On Fri, Oct 23, 2009 at 8:18 PM, Tony Chemit che...@codelutin.com wrote: Le Fri, 23 Oct 2009 20:04:32 +0100, Niall Pemberton niall.pember...@gmail.com a écrit : I'm getting the following error when I try to run mvn site on Commons Beanutils[1] I'm using maven 2.2.1 - it was working fine a week or so ago. I've been playing with maven 3.x though and have just switched back to 2.2.1, so I'm wondering if thats the cause. Any ideas I've searched the archives and this type of error seems to come up quite a but, but Niall Hi, I already had this problem, There is a pb with the dependency of commons-lang used somewhere in site plugin dependencies, I just add a dependency to site-plugin with a version of commons-lang which include the method (the version 2.4 works fine). Tony. [1] http://svn.apache.org/repos/asf/commons/proper/beanutils/trunk/ [INFO] Generating Project Team report. [FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused a linkage error (java.lang.NoClassDefFoundError) and may be out-of-date. Check the realms: [FATAL ERROR] Plugin realm = app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.0.1] urls[0] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.0.1/maven-site-plugin-2.0.1.jar urls[1] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar urls[2] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.0/doxia-module-xhtml-1.0.jar urls[3] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-core/1.0/doxia-core-1.0.jar urls[4] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.0/doxia-decoration-model-1.0.jar urls[5] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.0/doxia-site-renderer-1.0.jar urls[6] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar urls[7] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.7/plexus-velocity-1.1.7.jar urls[8] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar urls[9] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar urls[10] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/commons-lang/commons-lang/2.1/commons-lang-2.1.jar urls[11] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar urls[12] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.0/doxia-module-apt-1.0.jar urls[13] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.0/doxia-module-fml-1.0.jar urls[14] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.0/doxia-module-xdoc-1.0.jar urls[15] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar urls[16] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar urls[17] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar urls[18] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/mortbay/jetty/jetty/6.1.5/jetty-6.1.5.jar urls[19] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/mortbay/jetty/jetty-util/6.1.5/jetty-util-6.1.5.jar urls[20] = file:/C:/Documents and Settings/niall.pemberton/.m2/repository/org/mortbay/jetty/servlet-api-2.5/6.1.5/servlet-api-2.5-6.1.5.jar [FATAL ERROR] Container realm = plexus.core urls[0] = file:/C:/j/maven-2.2.1/lib/maven-2.2.1-uber.jar [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org/apache/commons/lang/ArrayUtils org.apache.commons.lang.ArrayUtils [INFO] [INFO] Trace java.lang.NoClassDefFoundError: org/apache/commons/lang/ArrayUtils at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:143) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203) at org.apache.velocity.runtime.parser.node.ASTReference.evaluate(ASTReference.java:396
Plugin configuration in pluginManagement?
Apache commons has a parent pom[1] used by the 34 or so components
that are part of that project.
We had some configuration for the maven-compiler-plugin in the
build/plugins section, but this has been moved to the
build/pluginManagement/plugins section [2] and I'm wondering what the
implications (if any) there are of this.
So for example, we had something like the following:
build
plugins
plugin
artifactIdmaven-compiler-plugin/artifactId
configuration
source${maven.compile.source}/source
target${maven.compile.target}/target
/configuration
/plugin
/plugins
/build
..and now we have
build
pluginManagement
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
source${maven.compile.source}/source
target${maven.compile.target}/target
encoding${commons.encoding}/encoding
/configuration
/plugin
/pluginManagement
plugins
plugin
artifactIdmaven-compiler-plugin/artifactId
/plugin
/plugins
/build
Anyone know what the implications are of moving the configuration to
the pluginManagement section?
Niall
[1] http://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk/pom.xml
[2] http://svn.apache.org/viewvc?view=revrevision=613456
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Specifying a plugin's dependency version
On Feb 12, 2008 9:24 AM, VUB Stefan Seidel [EMAIL PROTECTED] wrote: Actually, this is a bug. I didn't have time to file it yet, but from Maven 2.0.7 to 2.0.8 dependencies within the plugin definition suddenly are ignored in multi-module projects. Try to declare your dependency as a normal dependency in your parent pom. Or use Maven 2.0.7. OK thanks for confirming this is an issue. I can workaround it for now using the snapshot version as Stuart suggests. Niall regards, Stefan Niall Pemberton wrote: I'm using the vsersion 1.2.0 of the maven-bundle-plugin from the felix project - it has a dependency on version 0.0.227 of bndlib (groupId biz.aQute) and I wanted to try the plugin out with version 0.0.236 of bndlib. I tried specifying this in the plugin's dependencies both in the dependencyManagement section and in the plugin config in the build section: plugin groupIdorg.apache.felix/groupId artifactIdmaven-bundle-plugin/artifactId version1.2.0/version inheritedtrue/inherited dependencies dependency groupIdbiz.aQute/groupId artifactIdbndlib/artifactId version0.0.236/version /dependency /dependencies /plugin netiher seem to have any effect - it still used version 0.0.227 of bndlib. The docs seem to indicate that this should work - does it, or is this a bug? http://maven.apache.org/pom.html#Plugins Niall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ant plugin fails after ugrading from maven 2.0.7 to 2.0.8
Thanks - that does resolve the issue :) Although it seems like a bug that spaces in the path to the repository causes an issue. Niall On Feb 11, 2008 9:31 PM, Lee Meador [EMAIL PROTECTED] wrote: Looks to me like the same error you pointed to in JIRA. You can move your repository from the standard location under Documents and Settings\.m2 to somewhere else without a space in any folder name along the path to it. Here is what I put in my setting.xml (which I have not tried to move so its still in c:\Documents and Settings\.m2. settings localRepositoryd:\.m2\repository/localRepository ... /settings That one line, at the top of the settings.xml file will tell maven where to expect the repository so the new version of ant will be happy with where its jar is. Make sure the path you pick doesn't have any spaces in it. If you move the repository, you might want to move all the contents to the new location. If you don't, Maven will have to download everything one more time. Also, you will have to install anything interesting that can't be downloaded. Just an idea occurred to me. I'm not sure it will work but you might try it and it's unlikely to mess anything up. You could go to your c: root folder in a dos box and type dir /X to show the short name for the Documents and Settings folder. On my machine it's DOCUME~1 but it might be different on your machine. Then put the localRepository/ entry in your settings.xml showing the path to the repository, without moving it, but including the short name for that one folder. On my machine that would be: settings localRepositoryc:\DOCUME~1\.m2\repository/localRepository ... /settings Buy your short name, again, might be different. -- Lee On Feb 11, 2008 1:59 PM, Niall Pemberton [EMAIL PROTECTED] wrote: No-one any ideas on this? Niall On Feb 4, 2008 7:17 PM, Niall Pemberton [EMAIL PROTECTED] wrote: Perhaps related, but still don't know how I resolve this or why it occurs after upgrading: http://jira.codehaus.org/browse/MANTRUN-68 Niall On Feb 4, 2008 6:51 PM, Niall Pemberton [EMAIL PROTECTED] wrote: I've been working on an ant plugin here: http://svn.apache.org/viewvc/commons/sandbox/commons-build-plugin/ It was working fine on maven 2.0.7 but after I upgraded to maven 2.0.8 it started throwing an IllegalArgumentException (see stack trace below) when I try to run any of the three goals. Any ideas Niall [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'commons'. [INFO] [INFO] Building Commons Chain [INFO]task-segment: [commons:jira-page] [INFO] [INFO] [commons:jira-page] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null Illegal character in path at index 18: file:/C:/Documents and Settings/Niall Pemberton/.m2/repository/org/apache/ant/ant/1.7.0/ant- 1.7.0.jar [INFO] [INFO] Trace java.lang.IllegalArgumentException at java.net.URI.create(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.tools.ant.launch.Locator.fromURI(Locator.java :162) at org.apache.tools.ant.launch.Locator.getResourceSource( Locator.java:119) at org.apache.tools.ant.launch.Locator.getClassSource( Locator.java:90) at org.apache.tools.ant.Project.setAntLib(Project.java:313) at org.apache.tools.ant.Project.initProperties(Project.java :309) at org.apache.tools.ant.Project.init(Project.java:295) at org.codehaus.plexus.component.factory.ant.AntScriptInvoker.initializeProject (AntScriptInvoker.java:251) at org.codehaus.plexus.component.factory.ant.AntScriptInvoker.invoke( AntScriptInvoker.java:174) at org.apache.maven.script.ant.AntMojoWrapper.execute( AntMojoWrapper.java:52) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal( DefaultLifecycleExecutor.java:493
Re: Ant plugin fails after ugrading from maven 2.0.7 to 2.0.8
No-one any ideas on this? Niall On Feb 4, 2008 7:17 PM, Niall Pemberton [EMAIL PROTECTED] wrote: Perhaps related, but still don't know how I resolve this or why it occurs after upgrading: http://jira.codehaus.org/browse/MANTRUN-68 Niall On Feb 4, 2008 6:51 PM, Niall Pemberton [EMAIL PROTECTED] wrote: I've been working on an ant plugin here: http://svn.apache.org/viewvc/commons/sandbox/commons-build-plugin/ It was working fine on maven 2.0.7 but after I upgraded to maven 2.0.8 it started throwing an IllegalArgumentException (see stack trace below) when I try to run any of the three goals. Any ideas Niall [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'commons'. [INFO] [INFO] Building Commons Chain [INFO]task-segment: [commons:jira-page] [INFO] [INFO] [commons:jira-page] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null Illegal character in path at index 18: file:/C:/Documents and Settings/Niall Pemberton/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar [INFO] [INFO] Trace java.lang.IllegalArgumentException at java.net.URI.create(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162) at org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:119) at org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90) at org.apache.tools.ant.Project.setAntLib(Project.java:313) at org.apache.tools.ant.Project.initProperties(Project.java:309) at org.apache.tools.ant.Project.init(Project.java:295) at org.codehaus.plexus.component.factory.ant.AntScriptInvoker.initializeProject(AntScriptInvoker.java:251) at org.codehaus.plexus.component.factory.ant.AntScriptInvoker.invoke(AntScriptInvoker.java:174) at org.apache.maven.script.ant.AntMojoWrapper.execute(AntMojoWrapper.java:52) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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: java.net.URISyntaxException: Illegal character in path at index 18: file:/C:/Documents and Settings/Niall Pemberton/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar at java.net.URI$Parser.fail(Unknown Source) at java.net.URI$Parser.checkChars(Unknown Source) at java.net.URI$Parser.parseHierarchical(Unknown Source) at java.net.URI$Parser.parse(Unknown Source) at java.net.URI.init(Unknown Source) ... 32 more [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Feb 04 18:45:53 GMT 2008 [INFO] Final Memory: 4M/8M [INFO
Re: Specifying a plugin's dependency version
No-one any ideas on this? Niall On Feb 4, 2008 6:34 AM, Niall Pemberton [EMAIL PROTECTED] wrote: I'm using the vsersion 1.2.0 of the maven-bundle-plugin from the felix project - it has a dependency on version 0.0.227 of bndlib (groupId biz.aQute) and I wanted to try the plugin out with version 0.0.236 of bndlib. I tried specifying this in the plugin's dependencies both in the dependencyManagement section and in the plugin config in the build section: plugin groupIdorg.apache.felix/groupId artifactIdmaven-bundle-plugin/artifactId version1.2.0/version inheritedtrue/inherited dependencies dependency groupIdbiz.aQute/groupId artifactIdbndlib/artifactId version0.0.236/version /dependency /dependencies /plugin netiher seem to have any effect - it still used version 0.0.227 of bndlib. The docs seem to indicate that this should work - does it, or is this a bug? http://maven.apache.org/pom.html#Plugins Niall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Access to commons group
I have a continuum logon (niallp) - can I get admin rights to maintain the Apache Commons builds please http://vmbuild.apache.org/continuum/projectGroupSummary.action?projectGroupId=22 Niall
Re: Access to commons group
On Feb 7, 2008 12:16 PM, Brett Porter [EMAIL PROTECTED] wrote: done - by the way these requests should go through the normal infrastructure channels Thanks Niall On 07/02/2008, Niall Pemberton [EMAIL PROTECTED] wrote: I have a continuum logon (niallp) - can I get admin rights to maintain the Apache Commons builds please http://vmbuild.apache.org/continuum/projectGroupSummary.action?projectGroupId=22 Niall
Ant plugin fails after ugrading from maven 2.0.7 to 2.0.8
I've been working on an ant plugin here: http://svn.apache.org/viewvc/commons/sandbox/commons-build-plugin/ It was working fine on maven 2.0.7 but after I upgraded to maven 2.0.8 it started throwing an IllegalArgumentException (see stack trace below) when I try to run any of the three goals. Any ideas Niall [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'commons'. [INFO] [INFO] Building Commons Chain [INFO]task-segment: [commons:jira-page] [INFO] [INFO] [commons:jira-page] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null Illegal character in path at index 18: file:/C:/Documents and Settings/Niall Pemberton/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar [INFO] [INFO] Trace java.lang.IllegalArgumentException at java.net.URI.create(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162) at org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:119) at org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90) at org.apache.tools.ant.Project.setAntLib(Project.java:313) at org.apache.tools.ant.Project.initProperties(Project.java:309) at org.apache.tools.ant.Project.init(Project.java:295) at org.codehaus.plexus.component.factory.ant.AntScriptInvoker.initializeProject(AntScriptInvoker.java:251) at org.codehaus.plexus.component.factory.ant.AntScriptInvoker.invoke(AntScriptInvoker.java:174) at org.apache.maven.script.ant.AntMojoWrapper.execute(AntMojoWrapper.java:52) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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: java.net.URISyntaxException: Illegal character in path at index 18: file:/C:/Documents and Settings/Niall Pemberton/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar at java.net.URI$Parser.fail(Unknown Source) at java.net.URI$Parser.checkChars(Unknown Source) at java.net.URI$Parser.parseHierarchical(Unknown Source) at java.net.URI$Parser.parse(Unknown Source) at java.net.URI.init(Unknown Source) ... 32 more [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Feb 04 18:45:53 GMT 2008 [INFO] Final Memory: 4M/8M [INFO] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ant plugin fails after ugrading from maven 2.0.7 to 2.0.8
Perhaps related, but still don't know how I resolve this or why it occurs after upgrading: http://jira.codehaus.org/browse/MANTRUN-68 Niall On Feb 4, 2008 6:51 PM, Niall Pemberton [EMAIL PROTECTED] wrote: I've been working on an ant plugin here: http://svn.apache.org/viewvc/commons/sandbox/commons-build-plugin/ It was working fine on maven 2.0.7 but after I upgraded to maven 2.0.8 it started throwing an IllegalArgumentException (see stack trace below) when I try to run any of the three goals. Any ideas Niall [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'commons'. [INFO] [INFO] Building Commons Chain [INFO]task-segment: [commons:jira-page] [INFO] [INFO] [commons:jira-page] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null Illegal character in path at index 18: file:/C:/Documents and Settings/Niall Pemberton/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar [INFO] [INFO] Trace java.lang.IllegalArgumentException at java.net.URI.create(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162) at org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:119) at org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90) at org.apache.tools.ant.Project.setAntLib(Project.java:313) at org.apache.tools.ant.Project.initProperties(Project.java:309) at org.apache.tools.ant.Project.init(Project.java:295) at org.codehaus.plexus.component.factory.ant.AntScriptInvoker.initializeProject(AntScriptInvoker.java:251) at org.codehaus.plexus.component.factory.ant.AntScriptInvoker.invoke(AntScriptInvoker.java:174) at org.apache.maven.script.ant.AntMojoWrapper.execute(AntMojoWrapper.java:52) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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: java.net.URISyntaxException: Illegal character in path at index 18: file:/C:/Documents and Settings/Niall Pemberton/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar at java.net.URI$Parser.fail(Unknown Source) at java.net.URI$Parser.checkChars(Unknown Source) at java.net.URI$Parser.parseHierarchical(Unknown Source) at java.net.URI$Parser.parse(Unknown Source) at java.net.URI.init(Unknown Source) ... 32 more [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Feb 04 18:45:53 GMT 2008 [INFO] Final Memory: 4M/8M [INFO] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven java2wsdl...
On Feb 5, 2008 2:25 AM, Fernando da Motta Hildebrand
[EMAIL PROTECTED] wrote:
Well thanks anyway
From a quick glance - looks like the the name you've used in your
taskdef is different from the one your trying to then use (taskdef
name is axis-jjava2wsdl but your using ant:axis-java2wsdl - seems
to be an extra j in the taskdef name).
If that doesn't work then you could get it working as an ant file and
then call the ant file from maven.xml
Niall
2008/1/28, Wayne Fay [EMAIL PROTECTED]:
Perhaps try sending a new email here with [m1] in the subject. Then
people who are using Maven1 might be more likely to see it and reply.
But as Daniel said, there's just not a whole ton of people using M1
these days, it seems.
Wayne
On 1/28/08, Fernando da Motta Hildebrand [EMAIL PROTECTED]
wrote:
Thanks man,
But I really can´t afford to upgrade do maven2. That would require the
kind
of efford I can´t spend my team with now.
So... Does anyone have any sugestion? Besides going for maven2... Using
ant
tasks maybe?
2008/1/28, Allen, Daniel [EMAIL PROTECTED]:
(By the way, when I say it might be because, I mean maybe no one's
responding because, not that using Maven 1 might be your problem)
-Original Message-
From: Allen, Daniel
Sent: Monday, January 28, 2008 4:22 PM
To: Maven Users List
Subject: RE: Maven java2wsdl...
It might be because you're using Maven 1. I get the impression that
most
of the people on the User List have moved on to Maven 2. There is some
documentation around on WSDL and Axis in Maven 2. I believe the
example
system in Better Builds With Maven (free PDF book) uses those, so if
you wanted to migrate to the newer version, that might help. I have
little to no idea of the intricacies of Maven 1, though.
-Original Message-
From: Fernando da Motta Hildebrand [mailto:
[EMAIL PROTECTED]
Sent: Monday, January 28, 2008 2:55 PM
To: users@maven.apache.org
Subject: Re: Maven java2wsdl...
No one? Please?
2008/1/11, Fernando da Motta Hildebrand [EMAIL PROTECTED]
:
Hi,
I'm using Maven 1.x with Axis 1, here's below my maven.xml
?xml version=1.0 encoding=UTF-8?
project xmlns:j=jelly:core xmlns:maven=jelly:maven
xmlns:ant=jelly:ant xmlns:u=jelly:util default=radar:build
preGoal name=java:compile
mkdir dir=${maven.build.dir}/xdoclet/webdoclet/WEB-INF /
attainGoal name=xdoclet:webdoclet /
attainGoal name=wsdl /
ant:path id= axis.src.set
ant:pathelement location=${maven.axis.build.dir} /
/ant:path
maven:addPath id=maven.compile.src.set refid=axis.src.set/
/preGoal
preGoal name=war:webapp
j:set var=webapp.build.webinf value=${maven.war.webapp.dir
}/WEB-INF/
j:set var=webapp.build.metainf value=${maven.war.webapp.dir
}/META-INF/
ant:mkdir dir=${webapp.build.webinf}/
ant:mkdir dir=${webapp.build.metainf}/
ant:echoCopying server-config.wsdd and context.xml..
./ant:echo
ant:copy todir=${webapp.build.webinf}
preservelastmodified=true
ant:fileset dir=${maven.src.dir}/conf
includes=server-config.wsdd
/ant:fileset
/ant:copy
ant:copy todir=${webapp.build.metainf}
preservelastmodified=true
ant:fileset dir=${ maven.src.dir}/conf
includes=context.xml
/ant:fileset
/ant:copy
/preGoal
!-- Goal that generates the wsdl for the target class --
pregoal name=wsdl
!-- mkdir dir=${maven.build.dir}/wsdl / --
path id=compile.classpath
pathelement path=${ maven.build.dir}/classes /
/path
taskdef name=axis-jjava2wsdl classname=
org.apache.axis.tools.ant.wsdl.Java2WsdlAntTask
classpath refid= compile.classpath /
classpath refid=maven.dependency.classpath /
/taskdef
ant:axis-java2wsdl
classname=
br.com.siliconstrategy.radar.io.service.CorrelationRemoteService
style=rpc
namespace=urn:${pom.artifactId}
location=
http://localhost:8080/${pom.artifactId}/soap/${pom.artifactId}
http://localhost:8080/$%7Bpom.artifactId%7D/soap/$%7Bpom.artifactId%7D
output=${maven.src.dir}\webapp\${pom.artifactId}.wsdl
/ant:axis-java2wsdl
/pregoal
goal name=radar:build prereqs=clean,wsdl,war:install/
goal name=radar:deploy
prereqs=clean,tomcat:undeploy,tomcat:deploy/
/project
But I can't get it to work, it doesn't generate any wsdl files.
Can anyone give a hint here?
Thanks.
--
Specifying a plugin's dependency version
I'm using the vsersion 1.2.0 of the maven-bundle-plugin from the felix project - it has a dependency on version 0.0.227 of bndlib (groupId biz.aQute) and I wanted to try the plugin out with version 0.0.236 of bndlib. I tried specifying this in the plugin's dependencies both in the dependencyManagement section and in the plugin config in the build section: plugin groupIdorg.apache.felix/groupId artifactIdmaven-bundle-plugin/artifactId version1.2.0/version inheritedtrue/inherited dependencies dependency groupIdbiz.aQute/groupId artifactIdbndlib/artifactId version0.0.236/version /dependency /dependencies /plugin netiher seem to have any effect - it still used version 0.0.227 of bndlib. The docs seem to indicate that this should work - does it, or is this a bug? http://maven.apache.org/pom.html#Plugins Niall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Referencing a plugin configuration attribute in another plugin
I'm trying to reference a plugin configuration attribute in another
plugin's configuration in maven2. Can anyone point me in the right
direction?
Specifically I want to output two config attributes (source target
JVM) from the compile in the jar's manifest file, so I have the
following:
plugin
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.3/source
target1.3/target
/configuration
/plugin
plugin
artifactIdmaven-jar-plugin/artifactId
configuration
archive
manifestEntries
Source-JDK${maven.compile.source}/Source-JDK
Target-JDK${maven.compile.target}/Target-JDK
/manifestEntries
/archive
/configuration
/plugin
I have used property values ${maven.compile.target} in maven1 - is
there anyway I can reference the source/target configuration values
for maven-compiler-plugin in the maven-jar-plugin confiuration
items?
Niall
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Referencing a plugin configuration attribute in another plugin
Thanks for the suggestion - that worked, although it isn't ideal. I'm
looking at this with Jakarta Commons in mind, where (possibly) many
components would inherit from a main pom.xml. Using this approach a
component could override the maven-compiler-plugin configuration and
then what was being output to the manifest would not be the values the
compiler actually used. Is there no way of getting a reference to the
compiler plugin and accesssing its configuration values?
Niall
On 2/14/06, dan tran [EMAIL PROTECTED] wrote:
Create a property set
properties
source1.3/source
target1.3/target
/properties
Look up the Pom descriptor to where to place it.
Then you can use ${source} and ${target} both plugin configurations
-D
On 2/13/06, Niall Pemberton [EMAIL PROTECTED] wrote:
I'm trying to reference a plugin configuration attribute in another
plugin's configuration in maven2. Can anyone point me in the right
direction?
Specifically I want to output two config attributes (source target
JVM) from the compile in the jar's manifest file, so I have the
following:
plugin
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.3/source
target1.3/target
/configuration
/plugin
plugin
artifactIdmaven-jar-plugin/artifactId
configuration
archive
manifestEntries
Source-JDK${maven.compile.source}/Source-JDK
Target-JDK${maven.compile.target}/Target-JDK
/manifestEntries
/archive
/configuration
/plugin
I have used property values ${maven.compile.target} in maven1 - is
there anyway I can reference the source/target configuration values
for maven-compiler-plugin in the maven-jar-plugin confiuration
items?
Niall
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
