Re: DecoderException
on some installations of windows, the CLASSPATH environment variable is defined, and may even point to non-spec compliant partial implementations of java. I have seen javadoc blow up in these cases. check your environment variables. btw quick time can sometimes set the environment variable - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 4 Feb 2011 16:21, Randall Fidler randall.fid...@testadvantagesoftware.com wrote:
NPE from org.apache.maven.archetype.DefaultArchetypeManager of archetype-common-2.0.jar
Hi All, I'm trying to use maven archetypes programmatically to create a maven project. While I'm looking at the source code of the class *DefaultArchetypeManager*of *archetype-common-2.0.jar*, I see possible NPEs from the *generateProjectFromArchetype *method and *createArchetypeFromProject *method. The causes are, these methods try to invoke methods on *ArchetypeGenerator *and *ArchetypeCreator *references without instantiating them. Is this a known situation or a bug? Thanks and Regards, Harshana Martin -- Harshana Eranga Martin Software Engineer, WSO2 Inc. Web: http://wso2.com http://wso2.org ECF Committer: http://www.eclipse.org/ecf/ Blog: http://harshana05.blogspot.com Profile: https://www.google.com/profiles/harshana05
Release plugin and properties node
Hi,
I'm using property node to set the version of the project dependencies.
properties
aaa-version1.1.17-SNAPSHOT/aaa-version
bbb-version1.1.14-SNAPSHOT/bbb-version
/properties
dependencies
dependency
groupIdcom.aaa.common/groupId
artifactIdaaa/artifactId
version${aaa-version}/version
/dependency
dependency
groupIdcom.bbb.common/groupId
artifactIdbbb/artifactId
version${bbb-version}/version
/dependency
dependencies
When I execute the release:prepare command the plugin updates the version in
the dependency node and not in the property node for both the next
development pom and the released pom.
Released POM:
properties
aaa-version1.1.17-SNAPSHOT/aaa-version
bbb-version1.1.14-SNAPSHOT/bbb-version
/properties
dependencies
dependency
groupIdcom.aaa.common/groupId
artifactIdaaa/artifactId
version1.1.17/version
/dependency
dependency
groupIdcom.bbb.common/groupId
artifactIdbbb/artifactId
version1.1.14/version
/dependency
dependencies
Next dev POM:
properties
aaa-version1.1.17-SNAPSHOT/aaa-version
bbb-version1.1.14-SNAPSHOT/bbb-version
/properties
dependencies
dependency
groupIdcom.aaa.common/groupId
artifactIdaaa/artifactId
version1.1.18-SNAPSHOT/version
/dependency
dependency
groupIdcom.bbb.common/groupId
artifactIdbbb/artifactId
version1.1.15-SNAPSHOT/version
/dependency
dependencies
Is there any way I can instruct the plugin to update the versions in the
property node?
Thanks
Igal
--
View this message in context:
http://maven.40175.n5.nabble.com/Release-plugin-and-properties-node-tp3372090p3372090.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Maven Eclipse Plugin - how to remove M2_REPO classpath variable
Does anyone know a way to remove the M2_REPO classpath variable that was added using mvn -Declipse.workspace=pathtoworkspace eclipse:configure-workspace? (I'm created another workspace and would like to clean up the first workspace.) I've tried running mvn eclipse:clean before re-running eclipse:configure-workspace again but that doesn't do it. Also, M2_REPO is marked (non modifiable), so I'm unable to remove it manually using menu Window Preferences Java Build Path Classpath Variables. Searched past 12 month archives but didn't see anything on this topic... Thank you -CL
Re: Maven Eclipse Plugin - how to remove M2_REPO classpath variable
Does anyone know a way to remove the M2_REPO classpath variable that was added using mvn -Declipse.workspace=pathtoworkspace eclipse:configure-workspace? I don't know how (or even if) you can do this with the Eclipse plugin, but nothing is stopping you from doing it manually by editing the dot files (.classpath, .project, etc) in your project directory with Notepad or another editor. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Maven Eclipse Plugin - how to remove M2_REPO classpath variable
I don’t know how to remove it. But in eclipse you can go to preferences - maven - user settings and “reindex” the location. Perhaps that helps depending on what the problem is. /Ludwig From: Wayne Fay [mailto:wayne...@gmail.com] Sent: den 5 februari 2011 16:25 To: Maven Users List Subject: Re: Maven Eclipse Plugin - how to remove M2_REPO classpath variable Does anyone know a way to remove the M2_REPO classpath variable that was added using mvn -Declipse.workspace=pathtoworkspace eclipse:configure-workspace? I don't know how (or even if) you can do this with the Eclipse plugin, but nothing is stopping you from doing it manually by editing the dot files (.classpath, .project, etc) in your project directory with Notepad or another editor. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1204 / Virus Database: 1435/3423 - Release Date: 02/04/11
Jetty Plugin Error:
[INFO] Scanning for projects... [INFO] [INFO] [INFO] Building simple-webapp Maven Webapp 1.0-SNAPSHOT [INFO] [INFO] [INFO] maven-jetty-plugin:6.1.10:run (default-cli) @ simple-webapp .. .. [INFO] maven-jetty-plugin:6.1.10:run (default-cli) @ simple-webapp [INFO] [INFO] --- maven-jetty-plugin:6.1.10:run (default-cli) @ simple-webapp --- [INFO] Configuring Jetty for project: simple-webapp Maven Webapp [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1.513s [INFO] Finished at: Sat Feb 05 12:47:58 EST 2011 [INFO] Final Memory: 3M/15M [INFO] [ERROR] Failed to execute goal org.mortbay.jetty:maven-jetty-plugin:6.1.10:run (default-cli) on project simple-webapp: Webapp source directory C:\Users\jondemaagd\MavenProjects\simple-webapp\src\main\webapp does not exist - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException POM.xml .. .. plugins plugin groupIdorg.mortbay.jetty/groupId artifactIdmaven-jetty-plugin/artifactId version6.1.10/version /plugin /plugins Followed Maven By Example and http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin Followed examples on site for command mvn jetty:run Results were still same! Please Help! Thanks!
Failed to execute goal with jetty-plugin
[ERROR] Failed to execute goal org.mortbay.jetty:maven-jetty-plugin:6.1.22:run (default-cli) on project simple-webapp: Webapp source directory C:\Users\jondemaagd\MavenProjects\simple-webapp\src\main\webapp does not exist - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException Have tried several sources and results are the same Any lead? Thanks again.
Re: Jetty Plugin Error:
[ERROR] Failed to execute goal org.mortbay.jetty:maven-jetty-plugin:6.1.10:run (default-cli) on project simple-webapp: Webapp source directory C:\Users\jondemaagd\MavenProjects\simple-webapp\src\main\webapp does not exist - [Help 1] Did you read the error? It says blah\src\main\webapp does not exist. Fix that and try again. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Jetty Plugin Error:
My understanding is that these directories and files are created by default. Is this not true? From commandmvn jetty:run -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Saturday, February 05, 2011 10:58 PM To: Maven Users List Subject: Re: Jetty Plugin Error: [ERROR] Failed to execute goal org.mortbay.jetty:maven-jetty-plugin:6.1.10:run (default-cli) on project simple-webapp: Webapp source directory C:\Users\jondemaagd\MavenProjects\simple-webapp\src\main\webapp does not exist - [Help 1] Did you read the error? It says blah\src\main\webapp does not exist. Fix that and try again. Wayne - 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: Jetty Plugin Error:
My understanding is that these directories and files are created by default. Is this not true? From commandmvn jetty:run Having this directory or not depends entirely on what archetype you used when you built your project. If you didn't create a war (webapp) project, then you probably don't have a src/main/webapp directory -- and given the error you're seeing, I'm guessing this is what's going on. You can fix this error by simply creating that directory yourself, and maybe copying a few files into it. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
