Re: Build definitions which exceed the default length
Can we know values you use in this screen? Emmanuel Morgovsky, Alexander (US - Glen Mills) a écrit : Sure. On the Add/Edit Build Definition page, after entering the definition, I receive this error: org.apache.maven.continuum.ContinuumException: Error while executing the action 'update-build-definition-from-project-group' The Stack Trace contains: Caused by: javax.jdo.JDOFatalUserException: Attempt to store value my definition in column ARGUMENTS that has maximum length of 256. Please correct your data! at org.jpox.store.rdbms.mapping.CharRDBMSMapping.setString(CharRDBMSMapping .java:214) at org.jpox.store.mapping.SingleFieldMapping.setString(SingleFieldMapping.j ava:203) at org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeStringField(Param eterSetter.java:122) at org.jpox.state.StateManagerImpl.providedStringField(StateManagerImpl.jav a:2757) at org.apache.maven.continuum.model.project.BuildDefinition.jdoProvideField (BuildDefinition.java) at org.apache.maven.continuum.model.project.BuildDefinition.jdoProvideField s(BuildDefinition.java) at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115 ) at org.jpox.store.rdbms.request.UpdateRequest.execute(UpdateRequest.java:25 9) at org.jpox.store.rdbms.table.ClassTable.update(ClassTable.java:2573) at org.jpox.store.StoreManager.update(StoreManager.java:967) at org.jpox.state.StateManagerImpl.flush(StateManagerImpl.java:4928) at org.jpox.AbstractPersistenceManager.flush(AbstractPersistenceManager.jav a:3217) at org.jpox.store.rdbms.RDBMSNonmanagedTransaction.commit(RDBMSNonmanagedTr ansaction.java:397) at org.codehaus.plexus.jdo.PlexusJdoUtils.updateObject(PlexusJdoUtils.java: 163) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti nuumStore.java:794) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti nuumStore.java:786) at org.apache.maven.continuum.store.JdoContinuumStore.storeBuildDefinition( JdoContinuumStore.java:707) at org.apache.maven.continuum.core.action.AbstractBuildDefinitionContinuumA ction.updateBuildDefinitionInList(AbstractBuildDefinitionContinuumAction .java:181) at org.apache.maven.continuum.core.action.UpdateBuildDefinitionFromProjectG roupAction.execute(UpdateBuildDefinitionFromProjectGroupAction.java:51) at org.apache.maven.continuum.DefaultContinuum.executeAction(DefaultContinu um.java:2432) ... 81 more -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Saturday, November 24, 2007 9:34 PM To: continuum-users@maven.apache.org Subject: Re: Build definitions which exceed the default length On Nov 24, 2007 7:23 PM, Morgovsky, Alexander (US - Glen Mills) [EMAIL PROTECTED] wrote: Continuum does not allow build definitions to be longer than a specified length. What is the suggested work-around for this issue? Thank you. There are several fields on the add/edit build definition page. Is one of the fields too short, or is it accepting your input and then complaining later? Please explain the steps needed to reproduce the problem.
RE: Build definitions which exceed the default length
It is more than 300 characters of custom properties with their values set using -D parameters. However, I decided to use less characters, thus I am fine for now. Thank you. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Monday, November 26, 2007 7:30 AM To: continuum-users@maven.apache.org Subject: Re: Build definitions which exceed the default length Can we know values you use in this screen? Emmanuel Morgovsky, Alexander (US - Glen Mills) a écrit : Sure. On the Add/Edit Build Definition page, after entering the definition, I receive this error: org.apache.maven.continuum.ContinuumException: Error while executing the action 'update-build-definition-from-project-group' The Stack Trace contains: Caused by: javax.jdo.JDOFatalUserException: Attempt to store value my definition in column ARGUMENTS that has maximum length of 256. Please correct your data! at org.jpox.store.rdbms.mapping.CharRDBMSMapping.setString(CharRDBMSMapping .java:214) at org.jpox.store.mapping.SingleFieldMapping.setString(SingleFieldMapping.j ava:203) at org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeStringField(Param eterSetter.java:122) at org.jpox.state.StateManagerImpl.providedStringField(StateManagerImpl.jav a:2757) at org.apache.maven.continuum.model.project.BuildDefinition.jdoProvideField (BuildDefinition.java) at org.apache.maven.continuum.model.project.BuildDefinition.jdoProvideField s(BuildDefinition.java) at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115 ) at org.jpox.store.rdbms.request.UpdateRequest.execute(UpdateRequest.java:25 9) at org.jpox.store.rdbms.table.ClassTable.update(ClassTable.java:2573) at org.jpox.store.StoreManager.update(StoreManager.java:967) at org.jpox.state.StateManagerImpl.flush(StateManagerImpl.java:4928) at org.jpox.AbstractPersistenceManager.flush(AbstractPersistenceManager.jav a:3217) at org.jpox.store.rdbms.RDBMSNonmanagedTransaction.commit(RDBMSNonmanagedTr ansaction.java:397) at org.codehaus.plexus.jdo.PlexusJdoUtils.updateObject(PlexusJdoUtils.java: 163) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti nuumStore.java:794) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti nuumStore.java:786) at org.apache.maven.continuum.store.JdoContinuumStore.storeBuildDefinition( JdoContinuumStore.java:707) at org.apache.maven.continuum.core.action.AbstractBuildDefinitionContinuumA ction.updateBuildDefinitionInList(AbstractBuildDefinitionContinuumAction .java:181) at org.apache.maven.continuum.core.action.UpdateBuildDefinitionFromProjectG roupAction.execute(UpdateBuildDefinitionFromProjectGroupAction.java:51) at org.apache.maven.continuum.DefaultContinuum.executeAction(DefaultContinu um.java:2432) ... 81 more -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Saturday, November 24, 2007 9:34 PM To: continuum-users@maven.apache.org Subject: Re: Build definitions which exceed the default length On Nov 24, 2007 7:23 PM, Morgovsky, Alexander (US - Glen Mills) [EMAIL PROTECTED] wrote: Continuum does not allow build definitions to be longer than a specified length. What is the suggested work-around for this issue? Thank you. There are several fields on the add/edit build definition page. Is one of the fields too short, or is it accepting your input and then complaining later? Please explain the steps needed to reproduce the problem. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
Re: Build definitions which exceed the default length
it would be better to use a profile instead of to use all properties on the command line. Emmanuel Morgovsky, Alexander (US - Glen Mills) a écrit : It is more than 300 characters of custom properties with their values set using -D parameters. However, I decided to use less characters, thus I am fine for now. Thank you. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Monday, November 26, 2007 7:30 AM To: continuum-users@maven.apache.org Subject: Re: Build definitions which exceed the default length Can we know values you use in this screen? Emmanuel Morgovsky, Alexander (US - Glen Mills) a écrit : Sure. On the Add/Edit Build Definition page, after entering the definition, I receive this error: org.apache.maven.continuum.ContinuumException: Error while executing the action 'update-build-definition-from-project-group' The Stack Trace contains: Caused by: javax.jdo.JDOFatalUserException: Attempt to store value my definition in column ARGUMENTS that has maximum length of 256. Please correct your data! at org.jpox.store.rdbms.mapping.CharRDBMSMapping.setString(CharRDBMSMapping .java:214) at org.jpox.store.mapping.SingleFieldMapping.setString(SingleFieldMapping.j ava:203) at org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeStringField(Param eterSetter.java:122) at org.jpox.state.StateManagerImpl.providedStringField(StateManagerImpl.jav a:2757) at org.apache.maven.continuum.model.project.BuildDefinition.jdoProvideField (BuildDefinition.java) at org.apache.maven.continuum.model.project.BuildDefinition.jdoProvideField s(BuildDefinition.java) at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115 ) at org.jpox.store.rdbms.request.UpdateRequest.execute(UpdateRequest.java:25 9) at org.jpox.store.rdbms.table.ClassTable.update(ClassTable.java:2573) at org.jpox.store.StoreManager.update(StoreManager.java:967) at org.jpox.state.StateManagerImpl.flush(StateManagerImpl.java:4928) at org.jpox.AbstractPersistenceManager.flush(AbstractPersistenceManager.jav a:3217) at org.jpox.store.rdbms.RDBMSNonmanagedTransaction.commit(RDBMSNonmanagedTr ansaction.java:397) at org.codehaus.plexus.jdo.PlexusJdoUtils.updateObject(PlexusJdoUtils.java: 163) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti nuumStore.java:794) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti nuumStore.java:786) at org.apache.maven.continuum.store.JdoContinuumStore.storeBuildDefinition( JdoContinuumStore.java:707) at org.apache.maven.continuum.core.action.AbstractBuildDefinitionContinuumA ction.updateBuildDefinitionInList(AbstractBuildDefinitionContinuumAction .java:181) at org.apache.maven.continuum.core.action.UpdateBuildDefinitionFromProjectG roupAction.execute(UpdateBuildDefinitionFromProjectGroupAction.java:51) at org.apache.maven.continuum.DefaultContinuum.executeAction(DefaultContinu um.java:2432) ... 81 more -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Saturday, November 24, 2007 9:34 PM To: continuum-users@maven.apache.org Subject: Re: Build definitions which exceed the default length On Nov 24, 2007 7:23 PM, Morgovsky, Alexander (US - Glen Mills) [EMAIL PROTECTED] wrote: Continuum does not allow build definitions to be longer than a specified length. What is the suggested work-around for this issue? Thank you. There are several fields on the add/edit build definition page. Is one of the fields too short, or is it accepting your input and then complaining later? Please explain the steps needed to reproduce the problem. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
RE: Build definitions which exceed the default length
Thanks, I will try this. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Monday, November 26, 2007 8:27 AM To: continuum-users@maven.apache.org Subject: Re: Build definitions which exceed the default length it would be better to use a profile instead of to use all properties on the command line. Emmanuel Morgovsky, Alexander (US - Glen Mills) a écrit : It is more than 300 characters of custom properties with their values set using -D parameters. However, I decided to use less characters, thus I am fine for now. Thank you. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Monday, November 26, 2007 7:30 AM To: continuum-users@maven.apache.org Subject: Re: Build definitions which exceed the default length Can we know values you use in this screen? Emmanuel Morgovsky, Alexander (US - Glen Mills) a écrit : Sure. On the Add/Edit Build Definition page, after entering the definition, I receive this error: org.apache.maven.continuum.ContinuumException: Error while executing the action 'update-build-definition-from-project-group' The Stack Trace contains: Caused by: javax.jdo.JDOFatalUserException: Attempt to store value my definition in column ARGUMENTS that has maximum length of 256. Please correct your data! at org.jpox.store.rdbms.mapping.CharRDBMSMapping.setString(CharRDBMSMapping .java:214) at org.jpox.store.mapping.SingleFieldMapping.setString(SingleFieldMapping.j ava:203) at org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeStringField(Param eterSetter.java:122) at org.jpox.state.StateManagerImpl.providedStringField(StateManagerImpl.jav a:2757) at org.apache.maven.continuum.model.project.BuildDefinition.jdoProvideField (BuildDefinition.java) at org.apache.maven.continuum.model.project.BuildDefinition.jdoProvideField s(BuildDefinition.java) at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115 ) at org.jpox.store.rdbms.request.UpdateRequest.execute(UpdateRequest.java:25 9) at org.jpox.store.rdbms.table.ClassTable.update(ClassTable.java:2573) at org.jpox.store.StoreManager.update(StoreManager.java:967) at org.jpox.state.StateManagerImpl.flush(StateManagerImpl.java:4928) at org.jpox.AbstractPersistenceManager.flush(AbstractPersistenceManager.jav a:3217) at org.jpox.store.rdbms.RDBMSNonmanagedTransaction.commit(RDBMSNonmanagedTr ansaction.java:397) at org.codehaus.plexus.jdo.PlexusJdoUtils.updateObject(PlexusJdoUtils.java: 163) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti nuumStore.java:794) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti nuumStore.java:786) at org.apache.maven.continuum.store.JdoContinuumStore.storeBuildDefinition( JdoContinuumStore.java:707) at org.apache.maven.continuum.core.action.AbstractBuildDefinitionContinuumA ction.updateBuildDefinitionInList(AbstractBuildDefinitionContinuumAction .java:181) at org.apache.maven.continuum.core.action.UpdateBuildDefinitionFromProjectG roupAction.execute(UpdateBuildDefinitionFromProjectGroupAction.java:51) at org.apache.maven.continuum.DefaultContinuum.executeAction(DefaultContinu um.java:2432) ... 81 more -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Saturday, November 24, 2007 9:34 PM To: continuum-users@maven.apache.org Subject: Re: Build definitions which exceed the default length On Nov 24, 2007 7:23 PM, Morgovsky, Alexander (US - Glen Mills) [EMAIL PROTECTED] wrote: Continuum does not allow build definitions to be longer than a specified length. What is the suggested work-around for this issue? Thank you. There are several fields on the add/edit build definition page. Is one of the fields too short, or is it accepting your input and then complaining later? Please explain the steps needed to reproduce the problem. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
Re: Build Definitions Question
Hi, No, you can have only one. -- Olivier 2007/11/26, Morgovsky, Alexander (US - Glen Mills) [EMAIL PROTECTED] : Is it possible to have more than build definition in the same project group to be set to default? Thank you. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
Re: Not able to pass multiple arguments to javac
Thanks, that works. Sahoo Wayne Fay wrote: Try this, Sahoo: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration compilerArgument-nowarn/compilerArgument compilerArgument-verbose/compilerArgument /configuration /plugin On 11/22/07, Sahoo [EMAIL PROTECTED] wrote: As suggested in [1], I tried configuring maven-compiler-plugin like this: compilerArgument-nowarn -verbose/compilerArgument But it causes compilation failure. Details given below: Failure executing javac, but could not parse the error: javac: invalid flag: -nowarn -verbose How can I pass multiple arguments to javac? Thanks, Sahoo [1] http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html - 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: Dependency Browser Tool
Thanks Jake. I wasn't suggesting you move away from the GUI, I just wasn't aware that you couldn't lauch a GUI from a Maven plugin. It would just be nice for something like this to be part of the dependency plugin. mvn dependency:resolve is great, mvn dependency:resolve-gui would be even better. - Original message - From: jake pezaro [EMAIL PROTECTED] To: users@maven.apache.org Date: Sun, 25 Nov 2007 13:38:50 -0800 (PST) Subject: Re: Dependency Browser Tool there are a couple of reasons why this is not a maven plugin. 1. we found it much easier to understand the dependency tree when it was displayed in a GUI (ie being able open and close branches, see paths being highlighted etc). if this were to be a plugin it would need to display text output, which we couldn't make as easy to understand (although if you have any ideas here then please send me an example). 2. maven reactor already provides a more static version of this information in it's convergence reports. we didn't want to replicate that functionality, we just wanted a simple tool to track down rouge transitive dependencies. Martin Gilday wrote: Is there any reason this isn't a Maven plugin though? --repository could be taken from settings.xml --workspace could just be the current directory where you run mvn xx:xx. -- View this message in context: http://www.nabble.com/Dependency-Browser-Tool-tf4870799s177.html#a13940274 Sent from the Maven - Users mailing list archive at Nabble.com. - 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]
maven goal deploy:deploy-file skips the authentication?
Hello, gentlemen, we are using Artifactory to hold the modules we're using in Maven, for some weird reason we can't upload an artifact to the repository. For example I want to deploy the artifact with such command: mvn deploy:deploy-file -DgroupId=org.apache.hadoop \ -DartifactId=hadoop-core \ -Dversion=0.14.3 \ -Dpackaging=jar \ -Dfile=hadoop-0.14.3-core.jar \ -DpomFile=/home/user/tmp/hadoop-0.14.3/hadoop-pom.xml \ -DrepositoryId=ourrepository \ -Durl=http://our.domain.com:8080/artifactory/[EMAIL PROTECTED] in the ~/.m2/settings.xml I have: settings servers server idourrepository/id usernameusername/username passwordpassword/password /server /servers /settings and when doing the dump of server request/response I can see following: request== PUT /artifactory/[EMAIL PROTECTED]/org/apache/hadoop/hadoop-core/0.14.3/hadoop-core-0.14.3.jar HTTP/1.1 User-Agent: Java/1.6.0_03-p3 Host: our.domain.com:8080 Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive Content-Length: 1360922 /request= ===response== HTTP/1.1 401 Authentication_is_required WWW-Authenticate: Basic realm=Artifactory Realm Content-Type: text/html; charset=iso-8859-1 Content-Length: 1481 Server: Jetty(6.1.4) html head meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1/ titleError 401 /title /head bodyh2HTTP ERROR: 401/h2preAuthentication is required./pre pRequestURI=/artifactory/[EMAIL PROTECTED]/org/apache/hadoop/hadoop-core/0.14.3/hadoop-core-0.14.3.jar/p pismalla href=http://jetty.mortbay.org/;Powered by Jetty:///a/small/i/pbr/ ===/response= So it looks like the authentication credentials were not even sent to the server. I double checked the repositoryId used in the command line and in the settings.xml and found there's no typo. So could somebody please explain what else I could miss and how to fix the problem or what do I need to do to provide more details? Thank you in advance! -- Eugene N Dzhurinsky pgpXBkjmsNAXE.pgp Description: PGP signature
RE: maven goal deploy:deploy-file skips the authentication?
If I recall correctly, there is a bug in the settings. When you have a repository and a server with the same id, Maven gets confused. So, do you also have a repository configured with id ourrepository? Normally I postfix every server id with .server, so in this case the server id becomes ourrepository.server. Hth, Nick Stolwijk -Original Message- From: Eugeny N Dzhurinsky [mailto:[EMAIL PROTECTED] Sent: Mon 11/26/2007 11:07 AM To: users@maven.apache.org Subject: maven goal deploy:deploy-file skips the authentication? Hello, gentlemen, we are using Artifactory to hold the modules we're using in Maven, for some weird reason we can't upload an artifact to the repository. For example I want to deploy the artifact with such command: mvn deploy:deploy-file -DgroupId=org.apache.hadoop \ -DartifactId=hadoop-core \ -Dversion=0.14.3 \ -Dpackaging=jar \ -Dfile=hadoop-0.14.3-core.jar \ -DpomFile=/home/user/tmp/hadoop-0.14.3/hadoop-pom.xml \ -DrepositoryId=ourrepository \ -Durl=http://our.domain.com:8080/artifactory/[EMAIL PROTECTED] in the ~/.m2/settings.xml I have: settings servers server idourrepository/id usernameusername/username passwordpassword/password /server /servers /settings and when doing the dump of server request/response I can see following: request== PUT /artifactory/[EMAIL PROTECTED]/org/apache/hadoop/hadoop-core/0.14.3/hadoop-core-0.14.3.jar HTTP/1.1 User-Agent: Java/1.6.0_03-p3 Host: our.domain.com:8080 Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive Content-Length: 1360922 /request= ===response== HTTP/1.1 401 Authentication_is_required WWW-Authenticate: Basic realm=Artifactory Realm Content-Type: text/html; charset=iso-8859-1 Content-Length: 1481 Server: Jetty(6.1.4) html head meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1/ titleError 401 /title /head bodyh2HTTP ERROR: 401/h2preAuthentication is required./pre pRequestURI=/artifactory/[EMAIL PROTECTED]/org/apache/hadoop/hadoop-core/0.14.3/hadoop-core-0.14.3.jar/p pismalla href=http://jetty.mortbay.org/;Powered by Jetty:///a/small/i/pbr/ ===/response= So it looks like the authentication credentials were not even sent to the server. I double checked the repositoryId used in the command line and in the settings.xml and found there's no typo. So could somebody please explain what else I could miss and how to fix the problem or what do I need to do to provide more details? Thank you in advance! -- Eugene N Dzhurinsky
latest version of maven-dependency-plugin - missing excludes on ArtifactItem
Hi,
I'm trying to use maven-dependency-plugin with excludes tag in my
configuration part:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idget-resources/id
phaseprocess-resources/phase
goals
goalcopy/goal
/goals
configuration
artifactItems
artifactItem
groupIdmy.company.groupid/groupId
artifactIdmyartifact/artifactId
version${my.version}/version
excludes**/*.class/excludes
classifierfoo/classifier
destFileNamemy-foo.zip/destFileName
typezip/type
/artifactItem
...
/plugin
But, I get this error:
[INFO] Using default encoding to copy filtered resources.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to configure plugin parameters for:
org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4
Cause: Cannot find setter nor field in
org.apache.maven.plugin.dependency.fromConfiguration.ArtifactItem for
'excludes'
Looking at javadoc and sources of maven-dependency-plugin I can see
setExcludes(String excludes).
In which version does excludes cofniguration is available and how
can I get it?
Thanks,
Erez.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ARCHETYPE - CUSTOM PARAMETERS]
Hi, João, Ludovic This feature is part of the upcomming new archetype plugin Regards, Raphaël 2007/11/11, Ludovic Claude [EMAIL PROTECTED]: Hi João, I've tried to do that as well, and I never found a way to make this work. If you find a solution, please let me know! Regards, Ludovic Claude João Kreuzberg a écrit : Hello guys, is there anyway to add custom parameters on archetype:create and recover them within the velocity context? ex.: -DuserName=ivanirjoao and then on velocity $userName Any help is appreciated. Best regards, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Solved]Re: Active a profile if another is not activated
Ok my problem are solved, because I haven't understand that defining a profiles List on command line (-P) overrides actived By Default profiles configuration Wendy Smoak-3 wrote: On Nov 23, 2007 10:03 AM, Saloucious [EMAIL PROTECTED] wrote: Is it possible to activate a profile if a profile is or is not activated ? Not directly, but what problem are you trying to solve? If you need to activate exactly one of a set of profiles, you can do it with the absence/presence or value of a system property. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Active-a-profile-if-another-is-not-activated-tf4862672s177.html#a13947580 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Solved]Re: Active a profile if another is not activated
Ok my problem is solved, -- Sorry Saloucious wrote: Ok my problem are solved, because I haven't understand that defining a profiles List on command line (-P) overrides actived By Default profiles configuration Wendy Smoak-3 wrote: On Nov 23, 2007 10:03 AM, Saloucious [EMAIL PROTECTED] wrote: Is it possible to activate a profile if a profile is or is not activated ? Not directly, but what problem are you trying to solve? If you need to activate exactly one of a set of profiles, you can do it with the absence/presence or value of a system property. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Active-a-profile-if-another-is-not-activated-tf4862672s177.html#a13947581 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven goal deploy:deploy-file skips the authentication?
Please don't address the list as gentlemen! It isn't nice for the gentlewomen who are on the list too :-) Nicole On 26/11/2007, Eugeny N Dzhurinsky [EMAIL PROTECTED] wrote: Hello, gentlemen, we are using Artifactory to hold the modules we're using in Maven, for some weird reason we can't upload an artifact to the repository. For example I want to deploy the artifact with such command: mvn deploy:deploy-file -DgroupId=org.apache.hadoop \ -DartifactId=hadoop-core \ -Dversion=0.14.3 \ -Dpackaging=jar \ -Dfile=hadoop-0.14.3-core.jar \ -DpomFile=/home/user/tmp/hadoop-0.14.3/hadoop-pom.xml \ -DrepositoryId=ourrepository \ -Durl=http://our.domain.com:8080/artifactory/[EMAIL PROTECTED] in the ~/.m2/settings.xml I have: settings servers server idourrepository/id usernameusername/username passwordpassword/password /server /servers /settings and when doing the dump of server request/response I can see following: request== PUT /artifactory/[EMAIL PROTECTED] /org/apache/hadoop/hadoop-core/0.14.3/hadoop-core-0.14.3.jar HTTP/1.1 User-Agent: Java/1.6.0_03-p3 Host: our.domain.com:8080 Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive Content-Length: 1360922 /request= ===response== HTTP/1.1 401 Authentication_is_required WWW-Authenticate: Basic realm=Artifactory Realm Content-Type: text/html; charset=iso-8859-1 Content-Length: 1481 Server: Jetty(6.1.4) html head meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1/ titleError 401 /title /head bodyh2HTTP ERROR: 401/h2preAuthentication is required./pre pRequestURI=/artifactory/[EMAIL PROTECTED] /org/apache/hadoop/hadoop-core/0.14.3/hadoop-core-0.14.3.jar/p pismalla href=http://jetty.mortbay.org/;Powered by Jetty:///a/small/i/pbr/ ===/response= So it looks like the authentication credentials were not even sent to the server. I double checked the repositoryId used in the command line and in the settings.xml and found there's no typo. So could somebody please explain what else I could miss and how to fix the problem or what do I need to do to provide more details? Thank you in advance! -- Eugene N Dzhurinsky
Re: maven goal deploy:deploy-file skips the authentication?
On Mon, Nov 26, 2007 at 11:13:43AM +0100, [EMAIL PROTECTED] wrote: If I recall correctly, there is a bug in the settings. When you have a repository and a server with the same id, Maven gets confused. So, do you also have a repository configured with id ourrepository? Normally I postfix every server id with .server, so in this case the server id becomes ourrepository.server. No, I don't have any repository with same ID defined in settings.xml. -- Eugene N Dzhurinsky pgpg8Az7XaaMT.pgp Description: PGP signature
Using scnm command with maven.
Hi We are using maven2.0.6. I am using assembly plugin for generating the release package. In that i am using fileset tag. but i need to give the location from SVN address so that i could get the files directly from SVN repository. In ant i know tag is available as src= target= username= password= But in maven how can i do that. Regards Vishal.
Re: maven goal deploy:deploy-file skips the authentication?
On Mon, Nov 26, 2007 at 12:28:44PM +0100, Nicole Lacoste wrote: Please don't address the list as gentlemen! It isn't nice for the gentlewomen who are on the list too :-) Ouch, please excuse me, I didn't mind to offend you ;) Probably I had to use Gentlehomo? ;) -- Eugene N Dzhurinsky pgps0BJpxfU0B.pgp Description: PGP signature
RE: Using scnm command with maven.
Try using the SCM plugin [1] to checkout the files you want into the target directory. From there the assembly plugin can use them. Hth, Nick Stolwijk [1] http://maven.apache.org/scm/plugins/ -Original Message- From: Vishal Pahwa [mailto:[EMAIL PROTECTED] Sent: Mon 11/26/2007 12:52 PM To: users@maven.apache.org Subject: Using scnm command with maven. Hi We are using maven2.0.6. I am using assembly plugin for generating the release package. In that i am using fileset tag. but i need to give the location from SVN address so that i could get the files directly from SVN repository. In ant i know tag is available as src= target= username= password= But in maven how can i do that. Regards Vishal.
Re: Translation for Chinese Users
Hi Thanks for your help. Here is a first step that could help you http://maven.apache.org/plugins/maven-site-plugin/i18n.html Cheers, Vincent 2007/11/23, Juven Xu [EMAIL PROTECTED]: Hi, guys: I'm a maven user from China and I do the build work for my company which is in Shanghai. Now I find that I've already been attracted by this powerful project management tool and I really want to do something to contribute. So, how about letting me do some translation work for Chinese users? Anyone agree with me? Thanks. Juven - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Maven team needs help from translators
Hi, Denneis: I can take the zh_CN translation and finish it in this week. On Nov 26, 2007 3:35 PM, Milos Kleint [EMAIL PROTECTED] wrote: it's in mojo's sandbox https://svn.codehaus.org/mojo/trunk/sandbox/l10n-maven-plugin/ Milos On 11/26/07, Wim Deblauwe [EMAIL PROTECTED] wrote: Nice plugin report. Is this plugin freely available? regards, Wim 2007/11/25, Dennis Lundberg [EMAIL PROTECTED]: Lukas Theussl has updated the German resource bundle. I have uploaded an updated localization status report: http://people.apache.org/~dennisl/maven-project-info-reports-plugin/l10n-status.htmlhttp://people.apache.org/%7Edennisl/maven-project-info-reports-plugin/l10n-status.html Dennis Lundberg wrote: Hi all We are preparing the next release of the maven-project-info-reports-plugin. The current localizations are lacking translations for lots of resources. We need your help improving this. Have a look at this report, and see if you are skilled in any of the listed languages: http://people.apache.org/~dennisl/maven-project-info-reports-plugin/l10n-status.htmlhttp://people.apache.org/%7Edennisl/maven-project-info-reports-plugin/l10n-status.html If so please create a patch and attach it to this issue in JIRA: http://jira.codehaus.org/browse/MPIR-34 Make sure you use unicode escape sequences for non-ascii characters. You can see how this is done in the current localizations. For more info on internationalization/localization in Maven plugins, see this page: http://maven.apache.org/plugins/maven-site-plugin/i18n.html If you have any questions about this, please don't hesitate to ask here on the list. Thanks for your cooperation -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Vigilog - an open source log file viewer: http://vigilog.sourceforge.net Blog: http://www.jroller.com/page/Fester
Re: Translation for Chinese Users
Thank you, Vincent: I've checked out the maven-site-plugin and maven-project-info-reports-plugin, starting doing translation for zh_CN. I have to say it's a fantastic experience to make contributions for Maven and I hope I can do more. On Nov 26, 2007 8:04 PM, Vincent Siveton [EMAIL PROTECTED] wrote: Hi Thanks for your help. Here is a first step that could help you http://maven.apache.org/plugins/maven-site-plugin/i18n.html Cheers, Vincent 2007/11/23, Juven Xu [EMAIL PROTECTED]: Hi, guys: I'm a maven user from China and I do the build work for my company which is in Shanghai. Now I find that I've already been attracted by this powerful project management tool and I really want to do something to contribute. So, how about letting me do some translation work for Chinese users? Anyone agree with me? Thanks. Juven - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Maven team needs help from translators
2007/11/26, Milos Kleint [EMAIL PROTECTED]: it's in mojo's sandbox https://svn.codehaus.org/mojo/trunk/sandbox/l10n-maven-plugin/ Very interesting ! Any chance to see it out of the sandbox soon ? Thanks Damien Lecan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Not able to pass multiple arguments to javac
Ignore my earlier email. The suggestion actually does *not* work. When I run with -X option, it shows only the last compilerArgument. See the following output: [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile' -- [DEBUG] (f) basedir = /tmp/my-app [DEBUG] (f) buildDirectory = /tmp/my-app/target [DEBUG] (f) classpathElements = [/tmp/my-app/target/classes] [DEBUG] (f) compileSourceRoots = [/tmp/my-app/src/main/java] [DEBUG] (f) compilerArgument = -verbose [DEBUG] (f) compilerId = javac [DEBUG] (f) debug = true [DEBUG] (f) failOnError = true [DEBUG] (f) fork = false [DEBUG] (f) optimize = false [DEBUG] (f) outputDirectory = /tmp/my-app/target/classes [DEBUG] (f) outputFileName = my-app-1.0-SNAPSHOT [DEBUG] (f) projectArtifact = com.mycompany.app:my-app:jar:1.0-SNAPSHOT [DEBUG] (f) showDeprecation = false [DEBUG] (f) showWarnings = false [DEBUG] (f) staleMillis = 0 [DEBUG] (f) verbose = false [DEBUG] -- end configuration -- Thanks, Sahoo Sahoo wrote: Thanks, that works. Sahoo Wayne Fay wrote: Try this, Sahoo: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration compilerArgument-nowarn/compilerArgument compilerArgument-verbose/compilerArgument /configuration /plugin On 11/22/07, Sahoo [EMAIL PROTECTED] wrote: As suggested in [1], I tried configuring maven-compiler-plugin like this: compilerArgument-nowarn -verbose/compilerArgument But it causes compilation failure. Details given below: Failure executing javac, but could not parse the error: javac: invalid flag: -nowarn -verbose How can I pass multiple arguments to javac? Thanks, Sahoo [1] http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Maven team needs help from translators
Hi, I will try to help with the italian translations. Giancarlo 2007/11/24, Dennis Lundberg [EMAIL PROTECTED]: Hi all We are preparing the next release of the maven-project-info-reports-plugin. The current localizations are lacking translations for lots of resources. We need your help improving this. Have a look at this report, and see if you are skilled in any of the listed languages: http://people.apache.org/~dennisl/maven-project-info-reports-plugin/l10n-status.html If so please create a patch and attach it to this issue in JIRA: http://jira.codehaus.org/browse/MPIR-34 Make sure you use unicode escape sequences for non-ascii characters. You can see how this is done in the current localizations. For more info on internationalization/localization in Maven plugins, see this page: http://maven.apache.org/plugins/maven-site-plugin/i18n.html If you have any questions about this, please don't hesitate to ask here on the list. Thanks for your cooperation -- Dennis Lundberg - 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]
maven-js-plugin 1.3 release
Hey all, We have released the 1.3 final version of the maven-js-plugin. Please see http://ossi.mobilvox.com/maven-js-plugin for full release details and documentation on the plugin. Also, the project can be found at http://sourceforge.net/projects/maven-js-plugin Thanks, Adam Altemus Software Engineer, MobilVox http://www.mobilvox.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Not able to pass multiple arguments to javac
Try this approach: configuration forktrue/fork maxmem1024m/maxmem showDeprecationtrue/showDeprecation showWarningstrue/showWarnings etc... /configuration To know element names to use, use the Name found in the Optional Parameters section of this page: http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sahoo Sent: Monday, November 26, 2007 8:25 AM To: Maven Users List Subject: Re: Not able to pass multiple arguments to javac Ignore my earlier email. The suggestion actually does *not* work. When I run with -X option, it shows only the last compilerArgument. See the following output: [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile' -- [DEBUG] (f) basedir = /tmp/my-app [DEBUG] (f) buildDirectory = /tmp/my-app/target [DEBUG] (f) classpathElements = [/tmp/my-app/target/classes] [DEBUG] (f) compileSourceRoots = [/tmp/my-app/src/main/java] [DEBUG] (f) compilerArgument = -verbose [DEBUG] (f) compilerId = javac [DEBUG] (f) debug = true [DEBUG] (f) failOnError = true [DEBUG] (f) fork = false [DEBUG] (f) optimize = false [DEBUG] (f) outputDirectory = /tmp/my-app/target/classes [DEBUG] (f) outputFileName = my-app-1.0-SNAPSHOT [DEBUG] (f) projectArtifact = com.mycompany.app:my-app:jar:1.0-SNAPSHOT [DEBUG] (f) showDeprecation = false [DEBUG] (f) showWarnings = false [DEBUG] (f) staleMillis = 0 [DEBUG] (f) verbose = false [DEBUG] -- end configuration -- Thanks, Sahoo Sahoo wrote: Thanks, that works. Sahoo Wayne Fay wrote: Try this, Sahoo: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration compilerArgument-nowarn/compilerArgument compilerArgument-verbose/compilerArgument /configuration /plugin On 11/22/07, Sahoo [EMAIL PROTECTED] wrote: As suggested in [1], I tried configuring maven-compiler-plugin like this: compilerArgument-nowarn -verbose/compilerArgument But it causes compilation failure. Details given below: Failure executing javac, but could not parse the error: javac: invalid flag: -nowarn -verbose How can I pass multiple arguments to javac? Thanks, Sahoo [1] http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass- compiler-arguments.html - 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] - 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]
Surefire System Properties not set?
Hi,
Im trying to pass a system property into surefire to override a coherence
cluster address, I have my surefire plugin configured as per..
http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdsurefire-report-maven-plugin/artifactId
configuration
systemProperties
property
nametangosol.coherence.clusteraddress/name
value${tangosol.coherence.clusteraddress}/value
/property
property
nametangosol.coherence.clusterport/name
value${tangosol.coherence.clusterport}/value
/property
/systemProperties
/configuration
/plugin
And when my tests run, these properties are nowhere to be seen (see below),
causing my tests to fail.
Am I missing something here? I have tries setting the properties in
./m2/settings.xml and using -D at the mvn command line with no joy. Has
someone else overridden a coherence cluster address in maven run unit tests?
?xml version=1.0 encoding=UTF-8 ?
testsuite errors=4 skipped=0 tests=4 time=5.463 failures=0
name=com.willhill.bcs.persistency.tangosol.LiabilityCacheDAOImplTest
properties
property value=Java(TM) 2 Runtime Environment, Standard Edition
name=java.runtime.name/
property value=C:\Java\jdk1.5.0_12\jre\bin
name=sun.boot.library.path/
property value=1.5.0_12-b04 name=java.vm.version/
property value=Sun Microsystems Inc. name=java.vm.vendor/
property value=http://java.sun.com/; name=java.vendor.url/
property value=; name=path.separator/
property value=Java HotSpot(TM) Client VM name=java.vm.name/
property value=sun.io name=file.encoding.pkg/
property value=GB name=user.country/
property value=SUN_STANDARD name=sun.java.launcher/
property value= name=sun.os.patch.level/
property value=Java Virtual Machine Specification
name=java.vm.specification.name/
property value=C:\dev\whbcs\whbcs-liability\whbcs-liability-core
name=user.dir/
property value=1.5.0_12-b04 name=java.runtime.version/
property value=sun.awt.Win32GraphicsEnvironment
name=java.awt.graphicsenv/
property value=C:\dev\whbcs\whbcs-liability\whbcs-liability-core
name=basedir/
property value=C:\Java\jdk1.5.0_12\jre\lib\endorsed
name=java.endorsed.dirs/
property value=x86 name=os.arch/
property value=C:\Users\gustardj\AppData\Local\Temp\
name=java.io.tmpdir/
property value=
name=line.separator/
property value=Sun Microsystems Inc.
name=java.vm.specification.vendor/
property value= name=user.variant/
property value=Windows Vista name=os.name/
property value=Cp1252 name=sun.jnu.encoding/
property
value=C:\Java\jdk1.5.0_12\jre\bin;.;C:\Windows\system32;C:\Windows;C:\Java\jdk1.5.0_12\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program
Files\Common Files\Roxio Shared\DLLShared\;C:\Program
Files\OpenSSH\bin;C:\Program
Files\Subversion\bin;C:\Java\jdk1.5.0_12\bin;C:\maven-2.0.6\bin;C:\Program
Files\TortoiseSVN\bin name=java.library.path/
property value=Java Platform API Specification
name=java.specification.name/
property value=49.0 name=java.class.version/
property value=HotSpot Client Compiler
name=sun.management.compiler/
property value=6.0 name=os.version/
property value=C:\Users\gustardj name=user.home/
property value=Europe/London name=user.timezone/
property value=sun.awt.windows.WPrinterJob
name=java.awt.printerjob/
property value=Cp1252 name=file.encoding/
property value=1.5 name=java.specification.version/
property value=gustardj name=user.name/
property
value=C:\Users\gustardj\.m2\repository\org\codehaus\plexus\plexus-archiver\1.0-alpha-7\plexus-archiver-1.0-alpha-7.jar;C:\Users\gustardj\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar;C:\Users\gustardj\.m2\repository\org\apache\maven\surefire\surefire-api\2.3\surefire-api-2.3.jar;C:\Users\gustardj\.m2\repository\org\codehaus\plexus\plexus-container-default\1.0-alpha-8\plexus-container-default-1.0-alpha-8.jar;C:\Users\gustardj\.m2\repository\classworlds\classworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar;C:\Users\gustardj\.m2\repository\org\codehaus\plexus\plexus-utils\1.1\plexus-utils-1.1.jar;C:\Users\gustardj\.m2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;C:\Users\gustardj\.m2\repository\org\apache\maven\surefire\surefire-booter\2.3\surefire-booter-2.3.jar
name=java.class.path/
property value=1.0
RE: Not able to pass multiple arguments to javac
According to the web page [1], this should be:
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
compilerArguments
verbose /
bootclasspath${java.home}\lib\rt.jar/bootclasspath
/compilerArguments
/configuration
/plugin
/plugins
So can you try that?
Hth,
Nick Stolwijk
[1]
http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html
-Original Message-
From: Jeff Jensen [mailto:[EMAIL PROTECTED]
Sent: Mon 11/26/2007 3:32 PM
To: 'Maven Users List'
Subject: RE: Not able to pass multiple arguments to javac
Try this approach:
configuration
forktrue/fork
maxmem1024m/maxmem
showDeprecationtrue/showDeprecation
showWarningstrue/showWarnings
etc...
/configuration
To know element names to use, use the Name found in the Optional Parameters
section of this page:
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Sahoo
Sent: Monday, November 26, 2007 8:25 AM
To: Maven Users List
Subject: Re: Not able to pass multiple arguments to javac
Ignore my earlier email. The suggestion actually does *not* work. When I
run with -X option, it shows only the last compilerArgument. See the
following output:
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile' --
[DEBUG] (f) basedir = /tmp/my-app
[DEBUG] (f) buildDirectory = /tmp/my-app/target
[DEBUG] (f) classpathElements = [/tmp/my-app/target/classes]
[DEBUG] (f) compileSourceRoots = [/tmp/my-app/src/main/java]
[DEBUG] (f) compilerArgument = -verbose
[DEBUG] (f) compilerId = javac
[DEBUG] (f) debug = true
[DEBUG] (f) failOnError = true
[DEBUG] (f) fork = false
[DEBUG] (f) optimize = false
[DEBUG] (f) outputDirectory = /tmp/my-app/target/classes
[DEBUG] (f) outputFileName = my-app-1.0-SNAPSHOT
[DEBUG] (f) projectArtifact = com.mycompany.app:my-app:jar:1.0-SNAPSHOT
[DEBUG] (f) showDeprecation = false
[DEBUG] (f) showWarnings = false
[DEBUG] (f) staleMillis = 0
[DEBUG] (f) verbose = false
[DEBUG] -- end configuration --
Thanks,
Sahoo
Sahoo wrote:
Thanks, that works.
Sahoo
Wayne Fay wrote:
Try this, Sahoo:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
compilerArgument-nowarn/compilerArgument
compilerArgument-verbose/compilerArgument
/configuration
/plugin
On 11/22/07, Sahoo [EMAIL PROTECTED] wrote:
As suggested in [1], I tried configuring maven-compiler-plugin like
this:
compilerArgument-nowarn -verbose/compilerArgument
But it causes compilation failure. Details given below:
Failure executing javac, but could not parse the error:
javac: invalid flag: -nowarn -verbose
How can I pass multiple arguments to javac?
Thanks,
Sahoo
[1]
http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-
compiler-arguments.html
-
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]
-
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: Surefire System Properties not set?
You are configuring the wrong plugin:
On the webpage:
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
In your code:
groupIdorg.codehaus.mojo/groupId
artifactIdsurefire-report-maven-plugin/artifactId
Hth,
Nick Stolwijk
-Original Message-
From: Jimbog [mailto:[EMAIL PROTECTED]
Sent: Mon 11/26/2007 3:40 PM
To: users@maven.apache.org
Subject: Surefire System Properties not set?
Hi,
Im trying to pass a system property into surefire to override a coherence
cluster address, I have my surefire plugin configured as per..
http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdsurefire-report-maven-plugin/artifactId
configuration
systemProperties
property
nametangosol.coherence.clusteraddress/name
value${tangosol.coherence.clusteraddress}/value
/property
property
nametangosol.coherence.clusterport/name
value${tangosol.coherence.clusterport}/value
/property
/systemProperties
/configuration
/plugin
And when my tests run, these properties are nowhere to be seen (see below),
causing my tests to fail.
Am I missing something here? I have tries setting the properties in
/m2/settings.xml and using -D at the mvn command line with no joy. Has
someone else overridden a coherence cluster address in maven run unit tests?
?xml version=1.0 encoding=UTF-8 ?
testsuite errors=4 skipped=0 tests=4 time=5.463 failures=0
name=com.willhill.bcs.persistency.tangosol.LiabilityCacheDAOImplTest
properties
property value=Java(TM) 2 Runtime Environment, Standard Edition
name=java.runtime.name/
property value=C:\Java\jdk1.5.0_12\jre\bin
name=sun.boot.library.path/
property value=1.5.0_12-b04 name=java.vm.version/
property value=Sun Microsystems Inc. name=java.vm.vendor/
property value=http://java.sun.com/; name=java.vendor.url/
property value=; name=path.separator/
property value=Java HotSpot(TM) Client VM name=java.vm.name/
property value=sun.io name=file.encoding.pkg/
property value=GB name=user.country/
property value=SUN_STANDARD name=sun.java.launcher/
property value= name=sun.os.patch.level/
property value=Java Virtual Machine Specification
name=java.vm.specification.name/
property value=C:\dev\whbcs\whbcs-liability\whbcs-liability-core
name=user.dir/
property value=1.5.0_12-b04 name=java.runtime.version/
property value=sun.awt.Win32GraphicsEnvironment
name=java.awt.graphicsenv/
property value=C:\dev\whbcs\whbcs-liability\whbcs-liability-core
name=basedir/
property value=C:\Java\jdk1.5.0_12\jre\lib\endorsed
name=java.endorsed.dirs/
property value=x86 name=os.arch/
property value=C:\Users\gustardj\AppData\Local\Temp\
name=java.io.tmpdir/
property value=
name=line.separator/
property value=Sun Microsystems Inc.
name=java.vm.specification.vendor/
property value= name=user.variant/
property value=Windows Vista name=os.name/
property value=Cp1252 name=sun.jnu.encoding/
property
value=C:\Java\jdk1.5.0_12\jre\bin;.;C:\Windows\system32;C:\Windows;C:\Java\jdk1.5.0_12\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program
Files\Common Files\Roxio Shared\DLLShared\;C:\Program
Files\OpenSSH\bin;C:\Program
Files\Subversion\bin;C:\Java\jdk1.5.0_12\bin;C:\maven-2.0.6\bin;C:\Program
Files\TortoiseSVN\bin name=java.library.path/
property value=Java Platform API Specification
name=java.specification.name/
property value=49.0 name=java.class.version/
property value=HotSpot Client Compiler
name=sun.management.compiler/
property value=6.0 name=os.version/
property value=C:\Users\gustardj name=user.home/
property value=Europe/London name=user.timezone/
property value=sun.awt.windows.WPrinterJob
name=java.awt.printerjob/
property value=Cp1252 name=file.encoding/
property value=1.5 name=java.specification.version/
property value=gustardj name=user.name/
property
Deploying Non-Maven Created Jar
I have a jar from a third party that I want to use in my maven project. I was wondering if there is an easy way to setup a maven project so that I can replace the jar and have it deploy to the server using mvn deploy. Does anyone have any instructions or samples of doing this? I know I can create the directory structure and files manually, but would really rather have maven do that. Any suggestions. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Deploying Non-Maven Created Jar
If it is only a jar file you wish to deploy: mvn deploy:deploy-file [1] Hth, Nick Stolwijk [1] http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html -Original Message- From: Thomas Jackson [mailto:[EMAIL PROTECTED] Sent: Mon 11/26/2007 3:36 PM To: Maven Users Subject: Deploying Non-Maven Created Jar I have a jar from a third party that I want to use in my maven project. I was wondering if there is an easy way to setup a maven project so that I can replace the jar and have it deploy to the server using mvn deploy. Does anyone have any instructions or samples of doing this? I know I can create the directory structure and files manually, but would really rather have maven do that. Any suggestions. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: The Maven team needs help from translators
I would like to help you with the Spanish translation. When would you need it? Regards, Alejandro Uriza -Original Message- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: November 24, 2007 1:03 PM To: Maven Users List Subject: The Maven team needs help from translators Hi all We are preparing the next release of the maven-project-info-reports-plugin. The current localizations are lacking translations for lots of resources. We need your help improving this. Have a look at this report, and see if you are skilled in any of the listed languages: http://people.apache.org/~dennisl/maven-project-info-reports-plugin/l10n -status.html If so please create a patch and attach it to this issue in JIRA: http://jira.codehaus.org/browse/MPIR-34 Make sure you use unicode escape sequences for non-ascii characters. You can see how this is done in the current localizations. For more info on internationalization/localization in Maven plugins, see this page: http://maven.apache.org/plugins/maven-site-plugin/i18n.html If you have any questions about this, please don't hesitate to ask here on the list. Thanks for your cooperation -- Dennis Lundberg - 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: Surefire System Properties not set?
Hi,
yes, we were only using the reports plugin, ive added the
maven-surefire-plugin and the system properties get passed through, I would
have thought the reports plugin would pass them in.
nicklist wrote:
You are configuring the wrong plugin:
On the webpage:
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
In your code:
groupIdorg.codehaus.mojo/groupId
artifactIdsurefire-report-maven-plugin/artifactId
Hth,
Nick Stolwijk
-Original Message-
From: Jimbog [mailto:[EMAIL PROTECTED]
Sent: Mon 11/26/2007 3:40 PM
To: users@maven.apache.org
Subject: Surefire System Properties not set?
Hi,
Im trying to pass a system property into surefire to override a coherence
cluster address, I have my surefire plugin configured as per..
http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdsurefire-report-maven-plugin/artifactId
configuration
systemProperties
property
nametangosol.coherence.clusteraddress/name
value${tangosol.coherence.clusteraddress}/value
/property
property
nametangosol.coherence.clusterport/name
value${tangosol.coherence.clusterport}/value
/property
/systemProperties
/configuration
/plugin
And when my tests run, these properties are nowhere to be seen (see
below),
causing my tests to fail.
Am I missing something here? I have tries setting the properties in
/m2/settings.xml and using -D at the mvn command line with no joy. Has
someone else overridden a coherence cluster address in maven run unit
tests?
?xml version=1.0 encoding=UTF-8 ?
testsuite errors=4 skipped=0 tests=4 time=5.463 failures=0
name=com.willhill.bcs.persistency.tangosol.LiabilityCacheDAOImplTest
properties
property value=Java(TM) 2 Runtime Environment, Standard Edition
name=java.runtime.name/
property value=C:\Java\jdk1.5.0_12\jre\bin
name=sun.boot.library.path/
property value=1.5.0_12-b04 name=java.vm.version/
property value=Sun Microsystems Inc. name=java.vm.vendor/
property value=http://java.sun.com/; name=java.vendor.url/
property value=; name=path.separator/
property value=Java HotSpot(TM) Client VM name=java.vm.name/
property value=sun.io name=file.encoding.pkg/
property value=GB name=user.country/
property value=SUN_STANDARD name=sun.java.launcher/
property value= name=sun.os.patch.level/
property value=Java Virtual Machine Specification
name=java.vm.specification.name/
property value=C:\dev\whbcs\whbcs-liability\whbcs-liability-core
name=user.dir/
property value=1.5.0_12-b04 name=java.runtime.version/
property value=sun.awt.Win32GraphicsEnvironment
name=java.awt.graphicsenv/
property value=C:\dev\whbcs\whbcs-liability\whbcs-liability-core
name=basedir/
property value=C:\Java\jdk1.5.0_12\jre\lib\endorsed
name=java.endorsed.dirs/
property value=x86 name=os.arch/
property value=C:\Users\gustardj\AppData\Local\Temp\
name=java.io.tmpdir/
property value=
name=line.separator/
property value=Sun Microsystems Inc.
name=java.vm.specification.vendor/
property value= name=user.variant/
property value=Windows Vista name=os.name/
property value=Cp1252 name=sun.jnu.encoding/
property
value=C:\Java\jdk1.5.0_12\jre\bin;.;C:\Windows\system32;C:\Windows;C:\Java\jdk1.5.0_12\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program
Files\Common Files\Roxio Shared\DLLShared\;C:\Program
Files\OpenSSH\bin;C:\Program
Files\Subversion\bin;C:\Java\jdk1.5.0_12\bin;C:\maven-2.0.6\bin;C:\Program
Files\TortoiseSVN\bin name=java.library.path/
property value=Java Platform API Specification
name=java.specification.name/
property value=49.0 name=java.class.version/
property value=HotSpot Client Compiler
name=sun.management.compiler/
property value=6.0 name=os.version/
property value=C:\Users\gustardj name=user.home/
property value=Europe/London name=user.timezone/
property value=sun.awt.windows.WPrinterJob
name=java.awt.printerjob/
property value=Cp1252 name=file.encoding/
property value=1.5 name=java.specification.version/
property value=gustardj name=user.name/
property
RE: Surefire System Properties not set?
No, the surefire plugin runs your tests, and is by default enabled for most
packagings, so if you want to pass in properties you have to override the
configuration. The report plugin only does that, the reporting. It takes the
results from target/surefire-reports and creates the html files from them.
With regards,
Nick Stolwijk
-Original Message-
From: Jimbog [mailto:[EMAIL PROTECTED]
Sent: Mon 11/26/2007 4:42 PM
To: users@maven.apache.org
Subject: RE: Surefire System Properties not set?
Hi,
yes, we were only using the reports plugin, ive added the
maven-surefire-plugin and the system properties get passed through, I would
have thought the reports plugin would pass them in.
nicklist wrote:
You are configuring the wrong plugin:
On the webpage:
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
In your code:
groupIdorg.codehaus.mojo/groupId
artifactIdsurefire-report-maven-plugin/artifactId
Hth,
Nick Stolwijk
-Original Message-
From: Jimbog [mailto:[EMAIL PROTECTED]
Sent: Mon 11/26/2007 3:40 PM
To: users@maven.apache.org
Subject: Surefire System Properties not set?
Hi,
Im trying to pass a system property into surefire to override a coherence
cluster address, I have my surefire plugin configured as per..
http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdsurefire-report-maven-plugin/artifactId
configuration
systemProperties
property
nametangosol.coherence.clusteraddress/name
value${tangosol.coherence.clusteraddress}/value
/property
property
nametangosol.coherence.clusterport/name
value${tangosol.coherence.clusterport}/value
/property
/systemProperties
/configuration
/plugin
And when my tests run, these properties are nowhere to be seen (see
below),
causing my tests to fail.
Am I missing something here? I have tries setting the properties in
/m2/settings.xml and using -D at the mvn command line with no joy. Has
someone else overridden a coherence cluster address in maven run unit
tests?
?xml version=1.0 encoding=UTF-8 ?
testsuite errors=4 skipped=0 tests=4 time=5.463 failures=0
name=com.willhill.bcs.persistency.tangosol.LiabilityCacheDAOImplTest
properties
property value=Java(TM) 2 Runtime Environment, Standard Edition
name=java.runtime.name/
property value=C:\Java\jdk1.5.0_12\jre\bin
name=sun.boot.library.path/
property value=1.5.0_12-b04 name=java.vm.version/
property value=Sun Microsystems Inc. name=java.vm.vendor/
property value=http://java.sun.com/; name=java.vendor.url/
property value=; name=path.separator/
property value=Java HotSpot(TM) Client VM name=java.vm.name/
property value=sun.io name=file.encoding.pkg/
property value=GB name=user.country/
property value=SUN_STANDARD name=sun.java.launcher/
property value= name=sun.os.patch.level/
property value=Java Virtual Machine Specification
name=java.vm.specification.name/
property value=C:\dev\whbcs\whbcs-liability\whbcs-liability-core
name=user.dir/
property value=1.5.0_12-b04 name=java.runtime.version/
property value=sun.awt.Win32GraphicsEnvironment
name=java.awt.graphicsenv/
property value=C:\dev\whbcs\whbcs-liability\whbcs-liability-core
name=basedir/
property value=C:\Java\jdk1.5.0_12\jre\lib\endorsed
name=java.endorsed.dirs/
property value=x86 name=os.arch/
property value=C:\Users\gustardj\AppData\Local\Temp\
name=java.io.tmpdir/
property value=
name=line.separator/
property value=Sun Microsystems Inc.
name=java.vm.specification.vendor/
property value= name=user.variant/
property value=Windows Vista name=os.name/
property value=Cp1252 name=sun.jnu.encoding/
property
value=C:\Java\jdk1.5.0_12\jre\bin;.;C:\Windows\system32;C:\Windows;C:\Java\jdk1.5.0_12\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program
Files\Common Files\Roxio Shared\DLLShared\;C:\Program
Files\OpenSSH\bin;C:\Program
Files\Subversion\bin;C:\Java\jdk1.5.0_12\bin;C:\maven-2.0.6\bin;C:\Program
Files\TortoiseSVN\bin name=java.library.path/
property value=Java Platform API Specification
name=java.specification.name/
property value=49.0 name=java.class.version/
property value=HotSpot Client Compiler
xdoc : problem with links to xml file with maven -site-plugin 2.0-beta-6-SNAPSHOT
Hi, I've just noticed a problem with maven -site-plugin 2.0-beta-6-SNAPSHOT : simple relative links to xml files are transformed into internal links , so that lt;a href=link.xmlgt;link.xmllt;/agt; in the xdoc file becomes lt;a href=#link.xmlgt;link.xmllt;/agt; in the generated html file This occurs with the latest version of the plugin. Outputs from 2.0-beta-5 are correct, however I am using 2.0-beta-6-SNAPSHOT in order to use the TOC macro. I enclose a index.xml file that exhibits the problem. Absolute links, or links to html files are not corrupt, only relative links to xml files.tyhank you in advance, Anne http://www.nabble.com/file/p13952437/index.xml index.xml -- View this message in context: http://www.nabble.com/xdoc-%3A-problem-with-links-to-xml-file-with-maven--site-plugin-2.0-beta-6-SNAPSHOT-tf4875997s177.html#a13952437 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Not able to pass multiple arguments to javac
Yes, I knew that approach, but the options I actually want to pass are not supported by the mojo. nowarn and verbose were just used as examples; I want to pass -proc:none and -implicit. They are not supported by javac. There are many such options which are not supported by the mojo. I thought compilerArgument is the way to use them. But, it is *not* working. Thanks, Sahoo Jeff Jensen wrote: Try this approach: configuration forktrue/fork maxmem1024m/maxmem showDeprecationtrue/showDeprecation showWarningstrue/showWarnings etc... /configuration To know element names to use, use the Name found in the Optional Parameters section of this page: http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sahoo Sent: Monday, November 26, 2007 8:25 AM To: Maven Users List Subject: Re: Not able to pass multiple arguments to javac Ignore my earlier email. The suggestion actually does *not* work. When I run with -X option, it shows only the last compilerArgument. See the following output: [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile' -- [DEBUG] (f) basedir = /tmp/my-app [DEBUG] (f) buildDirectory = /tmp/my-app/target [DEBUG] (f) classpathElements = [/tmp/my-app/target/classes] [DEBUG] (f) compileSourceRoots = [/tmp/my-app/src/main/java] [DEBUG] (f) compilerArgument = -verbose [DEBUG] (f) compilerId = javac [DEBUG] (f) debug = true [DEBUG] (f) failOnError = true [DEBUG] (f) fork = false [DEBUG] (f) optimize = false [DEBUG] (f) outputDirectory = /tmp/my-app/target/classes [DEBUG] (f) outputFileName = my-app-1.0-SNAPSHOT [DEBUG] (f) projectArtifact = com.mycompany.app:my-app:jar:1.0-SNAPSHOT [DEBUG] (f) showDeprecation = false [DEBUG] (f) showWarnings = false [DEBUG] (f) staleMillis = 0 [DEBUG] (f) verbose = false [DEBUG] -- end configuration -- Thanks, Sahoo Sahoo wrote: Thanks, that works. Sahoo Wayne Fay wrote: Try this, Sahoo: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration compilerArgument-nowarn/compilerArgument compilerArgument-verbose/compilerArgument /configuration /plugin On 11/22/07, Sahoo [EMAIL PROTECTED] wrote: As suggested in [1], I tried configuring maven-compiler-plugin like this: compilerArgument-nowarn -verbose/compilerArgument But it causes compilation failure. Details given below: Failure executing javac, but could not parse the error: javac: invalid flag: -nowarn -verbose How can I pass multiple arguments to javac? Thanks, Sahoo [1] http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass- compiler-arguments.html - 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] - 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: Maven release plugin: Address already in use!
I still can't resolve this issue. I am using Maven 2.0.7. This is a major blocker issue for me so I would really appreciate any help. Does anyone at least know what port the release plugin uses ? Thanks, Bashar Jawad wrote: I am trying to use the maven-release-plugin to prepare and perform a release. I simply created a new empty maven 2 project and added the required scm information in the POM. However any time I run the command: mvn release:clean release:prepare maven asks me for release/tag/developement version information and then exists with the following error: [INFO] Transforming 'Unnamed - ReleasePluginDemo:ReleasePluginDemo:jar:1.0-SNAPSHOT'... [INFO] Not generating release POMs [INFO] Executing goals 'clean verify'... [INFO] Executing: mvn clean verify --no-plugin-updates -P default ERROR: transport error 202: bind failed: Address already in use [transport.c,L41] FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113) ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) [debugInit.c,L500] JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Maven execution failed, exit code: '1' [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Maven execution failed, exit code: '1' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) 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:224) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Maven execution failed, exit code: '1' at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:131) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more Caused by: org.apache.maven.shared.release.ReleaseExecutionException: Maven execution failed, exit code: '1' at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:66) at org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.execute(RunPrepareGoalsPhase.java:42) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:131) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:94) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:127) ... 18 more Caused by: org.apache.maven.shared.release.exec.MavenExecutorException: Maven execution failed, exit code: '1' at org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.java:103) at org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.java:121) at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:59) ... 23 more [INFO] [INFO] Total time: 7 seconds [INFO] Finished at: Wed Nov 21 14:37:09 MST 2007 [INFO] Final Memory:
[m2] Need assembly, tag, release, deploy help.
I need some help understanding the final tag, release, assemble process with continuum ans remote subversion. Here is my scenario: I have a remote SVN that all developers use. Then I have a continuum box, that also has our remote repository. Each time we build on the build server, I want this to be a deployable candidate. But our deployable's are delivered as tar's from our assembly. So it seems I am confused as to how to setup continuum to run. Do I run install, prepare-release, release, assemble? Can someone please help me tie all this together or at least point me somewhere that I can get a book or whitepaper? ;;) please :-) -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/djmick_dot_com http://www.myspace.com/sexybeotches http://www.thumpradio.com ---
Re: Maven release plugin: Address already in use!
I've seen this happening when MAVEN_OPTS is set to enable remote debugging. What happens is that the release plugin invokes a system exec of some sort of mvn which then tries to use the same MAVEN_OPTS and fails because the debug port is already taken. Makes sense? Jorg On Nov 26, 2007 5:11 PM, Bashar Jawad [EMAIL PROTECTED] wrote: I still can't resolve this issue. I am using Maven 2.0.7. This is a major blocker issue for me so I would really appreciate any help. Does anyone at least know what port the release plugin uses ? Thanks, Bashar Jawad wrote: I am trying to use the maven-release-plugin to prepare and perform a release. I simply created a new empty maven 2 project and added the required scm information in the POM. However any time I run the command: mvn release:clean release:prepare maven asks me for release/tag/developement version information and then exists with the following error: [INFO] Transforming 'Unnamed - ReleasePluginDemo:ReleasePluginDemo:jar:1.0-SNAPSHOT'... [INFO] Not generating release POMs [INFO] Executing goals 'clean verify'... [INFO] Executing: mvn clean verify --no-plugin-updates -P default ERROR: transport error 202: bind failed: Address already in use [transport.c,L41] FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113) ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) [debugInit.c,L500] JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Maven execution failed, exit code: '1' [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Maven execution failed, exit code: '1' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:564) 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:224) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Maven execution failed, exit code: '1' at org.apache.maven.plugins.release.PrepareReleaseMojo.execute( PrepareReleaseMojo.java:131) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:539) ... 16 more Caused by: org.apache.maven.shared.release.ReleaseExecutionException: Maven execution failed, exit code: '1' at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute( AbstractRunGoalsPhase.java:66) at org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.execute( RunPrepareGoalsPhase.java:42) at org.apache.maven.shared.release.DefaultReleaseManager.prepare( DefaultReleaseManager.java:194) at org.apache.maven.shared.release.DefaultReleaseManager.prepare( DefaultReleaseManager.java:131) at org.apache.maven.shared.release.DefaultReleaseManager.prepare( DefaultReleaseManager.java:94) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute( PrepareReleaseMojo.java:127) ... 18 more Caused by: org.apache.maven.shared.release.exec.MavenExecutorException: Maven execution failed, exit code: '1' at
Re: Dependency Browser Tool
I don't think there is anything stopping anyone to wrap a plugin/MOJO-interface around the maven-dependency-browser to achieve what you suggest :) - Rune Martin Gilday wrote: Thanks Jake. I wasn't suggesting you move away from the GUI, I just wasn't aware that you couldn't lauch a GUI from a Maven plugin. It would just be nice for something like this to be part of the dependency plugin. mvn dependency:resolve is great, mvn dependency:resolve-gui would be even better. - Original message - From: jake pezaro [EMAIL PROTECTED] To: users@maven.apache.org Date: Sun, 25 Nov 2007 13:38:50 -0800 (PST) Subject: Re: Dependency Browser Tool there are a couple of reasons why this is not a maven plugin. 1. we found it much easier to understand the dependency tree when it was displayed in a GUI (ie being able open and close branches, see paths being highlighted etc). if this were to be a plugin it would need to display text output, which we couldn't make as easy to understand (although if you have any ideas here then please send me an example). 2. maven reactor already provides a more static version of this information in it's convergence reports. we didn't want to replicate that functionality, we just wanted a simple tool to track down rouge transitive dependencies. Martin Gilday wrote: Is there any reason this isn't a Maven plugin though? --repository could be taken from settings.xml --workspace could just be the current directory where you run mvn xx:xx. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven release plugin: Address already in use!
What does your SCM configuration look like? Which protocol are you using? Please give some more information. With regards, Nick Stolwijk -Original Message- From: Bashar Jawad [mailto:[EMAIL PROTECTED] Sent: Mon 11/26/2007 5:11 PM To: Maven Users List Subject: Re: Maven release plugin: Address already in use! I still can't resolve this issue. I am using Maven 2.0.7. This is a major blocker issue for me so I would really appreciate any help. Does anyone at least know what port the release plugin uses ? Thanks, Bashar Jawad wrote: I am trying to use the maven-release-plugin to prepare and perform a release. I simply created a new empty maven 2 project and added the required scm information in the POM. However any time I run the command: mvn release:clean release:prepare maven asks me for release/tag/developement version information and then exists with the following error: [INFO] Transforming 'Unnamed - ReleasePluginDemo:ReleasePluginDemo:jar:1.0-SNAPSHOT'... [INFO] Not generating release POMs [INFO] Executing goals 'clean verify'... [INFO] Executing: mvn clean verify --no-plugin-updates -P default ERROR: transport error 202: bind failed: Address already in use [transport.c,L41] FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113) ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) [debugInit.c,L500] JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Maven execution failed, exit code: '1' [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Maven execution failed, exit code: '1' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) 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:224) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Maven execution failed, exit code: '1' at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:131) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more Caused by: org.apache.maven.shared.release.ReleaseExecutionException: Maven execution failed, exit code: '1' at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:66) at org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.execute(RunPrepareGoalsPhase.java:42) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:131) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:94) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:127) ... 18 more Caused by: org.apache.maven.shared.release.exec.MavenExecutorException: Maven execution failed, exit code: '1' at org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.java:103)
RE: Version moving up fast
I don't remember exactly (and my list of mvn bookmarks aren't working as well as they used to), but my recollection is if you put nothing for version number, it depends on the metadata stored in your internal repository (as long as that is kept up to date). Or was there a way to say use the release version, again, relying on your metadata.xml file in your internal repository -Original Message- From: Borut Bolčina [mailto:[EMAIL PROTECTED] Sent: Monday, November 26, 2007 2:32 AM To: Maven Subject: Version moving up fast Hello maven users, if one of our in-house jars (lets call it A.jar) is progressing fast in terms of artifact version numbers (several times per week: 2.1 - 2.2 - 2.3- ... - 2.678 - 2.679 - ...), what is the best way for other artifacts which depend on this fast one to always use the last one? All the artifacts which depend on the A, would have to have their poms modified to 2.1-SNAPSHOT, 2.2-SNAPSHOT etc. because the SNAPSHOT version is in the trunk. This is error prone. I haven't looked into the release plugin yet, but I don't think it addresses this issue. One solution might be to name the A's version to something like 999-SNAPSHOT and then all the other jars would have their dependencies to this version. This smells like a dead fish in the sewer to me. What do you say? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JavaDoc Warnings
Hi all, I was just building my site again (to check if everything is still okay for an upcoming release) and I saw all those ugly JavaDoc warnings fly by. I've been thinking about this before, but never got around to posting: Is there a taglet or something that I can use for my Maven-plugins? Atm I get all my warnings because of tags like '@goal', '@phase' and the other Maven-tags. If nothing exists yet, I might write something myself (which will probably end up being donated to the community), but if somehting already exists, I can save myself the time and effort! -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Version moving up fast
that only works for plugins, not for compile dependencies... I have the same problem, but I do my versioning slightly different. When I release my 1.0.0-SNAPSHOT, I'll make the release version 1.0.0.v20071126, and keep the development version at 1.0.0-SNAPSHOT... Tom On Nov 26, 2007 5:32 PM, EJ Ciramella [EMAIL PROTECTED] wrote: I don't remember exactly (and my list of mvn bookmarks aren't working as well as they used to), but my recollection is if you put nothing for version number, it depends on the metadata stored in your internal repository (as long as that is kept up to date). Or was there a way to say use the release version, again, relying on your metadata.xml file in your internal repository -Original Message- From: Borut Bolčina [mailto:[EMAIL PROTECTED] Sent: Monday, November 26, 2007 2:32 AM To: Maven Subject: Version moving up fast Hello maven users, if one of our in-house jars (lets call it A.jar) is progressing fast in terms of artifact version numbers (several times per week: 2.1 - 2.2 - 2.3- ... - 2.678 - 2.679 - ...), what is the best way for other artifacts which depend on this fast one to always use the last one? All the artifacts which depend on the A, would have to have their poms modified to 2.1-SNAPSHOT, 2.2-SNAPSHOT etc. because the SNAPSHOT version is in the trunk. This is error prone. I haven't looked into the release plugin yet, but I don't think it addresses this issue. One solution might be to name the A's version to something like 999-SNAPSHOT and then all the other jars would have their dependencies to this version. This smells like a dead fish in the sewer to me. What do you say? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
1.1-beta-4 to 1.1 final data migration
While trying to migrate our data from 1.1-beta-4, I'm getting the following error trying to export data out of the beta install: 0 [main] INFO org.apache.maven.continuum.management.DataManagementCli - Processing Continuum database... Exception in thread main org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) javax.resource:connector:jar:1.0 Try downloading the file manually from: http://java.sun.com/j2ee/connector/download.html Then, install it using the command: mvn install:install-file -DgroupId=javax.resource -DartifactId=connector \ -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) dummy:dummy:pom:1.0 2) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-4 3) jpox:jpox:jar:1.1.6 4) javax.resource:connector:jar:1.0 2) javax.transaction:jta:jar:1.0.1B Try downloading the file manually from: http://java.sun.com/products/jta Then, install it using the command: mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta \ -Dversion=1.0.1B -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) dummy:dummy:pom:1.0 2) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-4 3) jpox:jpox:jar:1.1.6 4) javax.transaction:jta:jar:1.0.1B -- 2 required artifacts are missing. for artifact: dummy:dummy:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:243) at org.apache.maven.continuum.management.DataManagementCli.downloadArtifact(DataManagementCli.java:304) at org.apache.maven.continuum.management.DataManagementCli.processDatabase(DataManagementCli.java:185) at org.apache.maven.continuum.management.DataManagementCli.main(DataManagementCli.java:158) - I've installed the two missing artifacts and still continue to get the above error. Any suggestions where to look or what to run? Thanks, Johnathan
Re: maven rebuild dependency
Thanks a lot Wayne Wouldn't it be a good feature to be able to specify that all dependencies for a particular project needs to be rebuilt or not according to the requirements? That way we do not have to worry about a dependent project being modified and us not having the latest version when our project is being built. Wayne Fay wrote: If they share a parent, and are declared as in the parent pom, then you can build from the parent directory and it will build, package, install etc all modules. If they are simply 2 projects in 2 different directories, then no. Maven will simply use the latest deployed artifact in your local repo cache. Wayne On 11/21/07, LinaTomy wrote: Maven dependency plugin has a goal copy-dependencies which has this parameter overWriteIfNewer Overwrite artifacts that don't exist or are older than the source. Similarly I was wondering whether it would be able to compare project with latest source and if modified recompile it. If not just a property that can be set so as to force an install of dependencies for a project. Juven Xu wrote: I'm wondering how can Maven konw project B has been modified or updated. Juven On Nov 22, 2007 8:29 AM, LinaTomy wrote: I have a project A that is Dependant on project B. When i build and package project A I want it to recompile and package project B if it has been modified or updated. Is this possible? Thanks a lot Lina -- View this message in context: http://www.nabble.com/maven-rebuild-dependency-tf4853620s177.html#a1349 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/maven-rebuild-dependency-tf4853620s177.html#a13889529 Sent from the Maven - Users mailing list archive at Nabble.com. - 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] -- View this message in context: http://www.nabble.com/maven-rebuild-dependency-tf4853620s177.html#a13953566 Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Version moving up fast
If you are releasing something, I think it's wrong to force your clients to move onto the new versions. If the client modules using your module would be in control of what they use, they'd update versions in their own schedule, even skip some. I haven't tried, but I wonder if it'd work to use both unique and non-unique versions. If you release for archiving purposes, you could could just post a unique snapshot, otherwise you'd use non-unique snapshots. You'd need to check if dependency resolution works correctly in all cases with this approach. Kalle On 11/25/07, Borut Bolčina [EMAIL PROTECTED] wrote: Hello maven users, if one of our in-house jars (lets call it A.jar) is progressing fast in terms of artifact version numbers (several times per week: 2.1 - 2.2 - 2.3- ... - 2.678 - 2.679 - ...), what is the best way for other artifacts which depend on this fast one to always use the last one? All the artifacts which depend on the A, would have to have their poms modified to 2.1-SNAPSHOT, 2.2-SNAPSHOT etc. because the SNAPSHOT version is in the trunk. This is error prone. I haven't looked into the release plugin yet, but I don't think it addresses this issue. One solution might be to name the A's version to something like 999-SNAPSHOT and then all the other jars would have their dependencies to this version. This smells like a dead fish in the sewer to me. What do you say?
Re: 1.1-beta-4 to 1.1 final data migration
Hmm, weird. As a workaround, I think you can use datamanagement 1.1 to migrate your data because we don't have db schema (if I remember it correctly between 1.1-beta-4 and 1.1 final) Emmanuel Johnathan Gifford a écrit : While trying to migrate our data from 1.1-beta-4, I'm getting the following error trying to export data out of the beta install: 0 [main] INFO org.apache.maven.continuum.management.DataManagementCli - Processing Continuum database... Exception in thread main org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) javax.resource:connector:jar:1.0 Try downloading the file manually from: http://java.sun.com/j2ee/connector/download.html Then, install it using the command: mvn install:install-file -DgroupId=javax.resource -DartifactId=connector \ -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) dummy:dummy:pom:1.0 2) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-4 3) jpox:jpox:jar:1.1.6 4) javax.resource:connector:jar:1.0 2) javax.transaction:jta:jar:1.0.1B Try downloading the file manually from: http://java.sun.com/products/jta Then, install it using the command: mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta \ -Dversion=1.0.1B -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) dummy:dummy:pom:1.0 2) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-4 3) jpox:jpox:jar:1.1.6 4) javax.transaction:jta:jar:1.0.1B -- 2 required artifacts are missing. for artifact: dummy:dummy:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:243) at org.apache.maven.continuum.management.DataManagementCli.downloadArtifact(DataManagementCli.java:304) at org.apache.maven.continuum.management.DataManagementCli.processDatabase(DataManagementCli.java:185) at org.apache.maven.continuum.management.DataManagementCli.main(DataManagementCli.java:158) - I've installed the two missing artifacts and still continue to get the above error. Any suggestions where to look or what to run? Thanks, Johnathan
Re: Maven ear problem: Jboss can't find datasource file
Any help guys? On Nov 23, 2007 3:29 PM, CasMeiron [EMAIL PROTECTED] wrote: Hi guys, Im trying to create a full ear project with maven2. Entities module, Ejb3 module, war modules etc... In my ejb3 module, i have the file my-app-ds.xml inside src/main/resources/META-INF In my ear module pom, i have the follow: jboss version4/version data-sources data-source my-app-ds.xml /data-source /data-sources /jboss The problem is: when i try to deploy my EAR, jboss says: org.jboss.deployment.DeploymentException: Failed to find module file: my-app -ds.xml Why jboss can't find the file? Is the wrong place to put my *ds archive? Another question, how can i change the jndi name for my ear? Cause if i need to get a instance of remote bean in SE enviroment, im doing this: jndiContext.lookup(my-app.ear-VERSION/Bean/...); I wanna config something like: myapp:Bean/... Tkz. -- Paulo Cesar Silva Reis --- Powered by GMAIL -- Paulo Cesar Silva Reis --- Powered by GMAIL
can Java2wsdl goal be used to generate artifacts for multiple java service classes
Hi, Can Java2wsdl goal be used to generate artifacts for multiple java service classes. I have my maven project, which contains multiple service implementation classes which i need to expose as webervices. I'm using java2wsdl, wsdl2java and admin goals all together to publish webservices. The problem is, how can i use java2wsdl with multiple classOfPortType to generate artifacts for multiple servce classes regards taran -- View this message in context: http://www.nabble.com/can-Java2wsdl-goal-be-used-to-generate-artifacts-for-multiple-java-service-classes-tf4876608s177.html#a13954583 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven ear problem: Jboss can't find datasource file
CasMeiron wrote: Any help guys? I would suggest using application.xml to point in the datasource file in the EAR with: module javapath/to/my/myapp-ds.xml/java /module Now, to include this in the EAR during the build is another issue. You could add the file in ear-project/src/main/application/APP-INF/classes, I think this should add it in the EAR by default, so the following should work: module javaAPP-INF/classes/myapp-ds.xml/java /module I may be missing something here but hopefully this will get you in the right direction. Cheers, Manos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Not able to pass multiple arguments to javac
I've found the problem. Plexus (which runs the compiler and commandline) is
quoting each argument. So for this configuration:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
target1.6/target
source1.6/source
compilerArguments
verbose /
bootclasspath${java.home}/lib/rt.jar/bootclasspath
/compilerArguments
compilerArgument-implicit:none -proc:none/compilerArgument
forktrue/fork
/configuration
/plugin
/plugins
/build
mvn clean compile -X gives the following output:
[DEBUG] Command line options:
[DEBUG] -d /home/nick/workspace/buildserver-test-project/trunk/target/classes
-classpath /home/nick/workspace/buildserver-test-project/trunk/target/classes:
/home/nick/workspace/buildserver-test-project/trunk/src/main/java/nl/iprofs/sandbox/buildservertest/App.java
-g -nowarn -target 1.6 -source 1.6 -bootclasspath
/usr/lib/jvm/java-6-sun-1.6.0.00/jre/lib/rt.jar -verbose -implicit:none
-proc:none
[INFO] Compiling 1 source file to
/home/nick/workspace/buildserver-test-project/trunk/target/classes
While it is actually executing:
/usr/lib/jvm/java-6-sun-1.6.0.00/bin/javac -d
/home/nick/workspace/buildserver-test-project/trunk/target/classes -classpath
/home/nick/workspace/buildserver-test-project/trunk/target/classes:
/home/nick/workspace/buildserver-test-project/trunk/src/main/java/nl/iprofs/sandbox/buildservertest/App.java
-g -nowarn -target 1.6 -source 1.6 -bootclasspath
/usr/lib/jvm/java-6-sun-1.6.0.00/jre/lib/rt.jar -verbose -implicit:none
-proc:none
(Much more quotes, but just for the idea) If I execute this myself, javac
indeed gives the error as described.
I guess, this should be a feature request for the maven-compiler-plugin, to
indeed accept multiple compilerArgument options. Maybe something like this:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
target1.6/target
source1.6/source
compilerArguments
verbose /
bootclasspath${java.home}/lib/rt.jar/bootclasspath
compilerArgument-implicit:none/compilerArgument
compilerArgument-prox:none/compilerArgument
/compilerArguments
forktrue/fork
/configuration
/plugin
/plugins
/build
Hth,
Nick Stolwijk
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Mon 11/26/2007 5:34 PM
To: Maven Users List
Subject: RE: Not able to pass multiple arguments to javac
The fault message you see is actually from javac itself. You're trying to add
options that are not supported by javac. All javac options are supported by
the mojo, it simply passes them to javac.
Why would you want to add options to javac which are not supported by javac?
With regards,
Nick Stolwijk
-Original Message-
From: [EMAIL PROTECTED] on behalf of Sahoo
Sent: Mon 11/26/2007 5:12 PM
To: Maven Users List
Subject: Re: Not able to pass multiple arguments to javac
Yes, I knew that approach, but the options I actually want to pass are
not supported by the mojo. nowarn and verbose were just used as
examples; I want to pass -proc:none and -implicit. They are not
supported by javac. There are many such options which are not supported
by the mojo. I thought compilerArgument is the way to use them. But, it
is *not* working.
Thanks,
Sahoo
Jeff Jensen wrote:
Try this approach:
configuration
forktrue/fork
maxmem1024m/maxmem
showDeprecationtrue/showDeprecation
showWarningstrue/showWarnings
etc...
/configuration
To know element names to use, use the Name found in the Optional Parameters
section of this page:
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Sahoo
Sent: Monday, November 26, 2007 8:25 AM
To: Maven Users List
Subject: Re: Not able to pass multiple arguments to javac
Ignore my earlier email. The suggestion actually does *not* work. When I
run with -X option, it shows only the last compilerArgument. See the
following output:
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile' --
[DEBUG] (f) basedir = /tmp/my-app
[DEBUG] (f) buildDirectory = /tmp/my-app/target
[DEBUG] (f) classpathElements = [/tmp/my-app/target/classes]
[DEBUG] (f) compileSourceRoots = [/tmp/my-app/src/main/java]
[DEBUG] (f) compilerArgument = -verbose
[DEBUG] (f) compilerId = javac
[DEBUG] (f) debug = true
[DEBUG] (f) failOnError = true
[DEBUG] (f) fork = false
[DEBUG] (f) optimize = false
[DEBUG] (f) outputDirectory = /tmp/my-app/target/classes
[DEBUG] (f)
Re: Not able to pass multiple arguments to javac
I doubt those message come from javac. They were printed by maven when I ran it with -X option. Tell me what is the option that is *not* supported by javac. AFAIK, all the options that I want to pass are very much supported by javac. Check out the documentation [1] of javac that comes with Sun JDK 6. More over, JDK 6 compiler allows to provide plugins to javac. In order to configure the plugin user may have to pass options that are *not* meant for javac itself, instead they are meant for the javac plugin. Such options will never be supported by maven-javac-plugin, hence compilerArgument is the only way to use them. In case of Sun JDK, any javac option starting -A is passed onto the plugin. An example is available at [2]. I actually faced all my maven issues while developing that plugin. My observation is that when multiple compilerArgument is used, only the last one is considered. Thanks, Sahoo [1] http://java.sun.com/javase/6/docs/technotes/tools/solaris/javac.html [2] http://weblogs.java.net/blog/ss141213/archive/2007/11/a_javac_plugin_1.html [EMAIL PROTECTED] wrote: The fault message you see is actually from javac itself. You're trying to add options that are not supported by javac. All javac options are supported by the mojo, it simply passes them to javac. Why would you want to add options to javac which are not supported by javac? With regards, Nick Stolwijk -Original Message- From: [EMAIL PROTECTED] on behalf of Sahoo Sent: Mon 11/26/2007 5:12 PM To: Maven Users List Subject: Re: Not able to pass multiple arguments to javac Yes, I knew that approach, but the options I actually want to pass are not supported by the mojo. nowarn and verbose were just used as examples; I want to pass -proc:none and -implicit. They are not supported by javac. There are many such options which are not supported by the mojo. I thought compilerArgument is the way to use them. But, it is *not* working. Thanks, Sahoo Jeff Jensen wrote: Try this approach: configuration forktrue/fork maxmem1024m/maxmem showDeprecationtrue/showDeprecation showWarningstrue/showWarnings etc... /configuration To know element names to use, use the Name found in the Optional Parameters section of this page: http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sahoo Sent: Monday, November 26, 2007 8:25 AM To: Maven Users List Subject: Re: Not able to pass multiple arguments to javac Ignore my earlier email. The suggestion actually does *not* work. When I run with -X option, it shows only the last compilerArgument. See the following output: [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile' -- [DEBUG] (f) basedir = /tmp/my-app [DEBUG] (f) buildDirectory = /tmp/my-app/target [DEBUG] (f) classpathElements = [/tmp/my-app/target/classes] [DEBUG] (f) compileSourceRoots = [/tmp/my-app/src/main/java] [DEBUG] (f) compilerArgument = -verbose [DEBUG] (f) compilerId = javac [DEBUG] (f) debug = true [DEBUG] (f) failOnError = true [DEBUG] (f) fork = false [DEBUG] (f) optimize = false [DEBUG] (f) outputDirectory = /tmp/my-app/target/classes [DEBUG] (f) outputFileName = my-app-1.0-SNAPSHOT [DEBUG] (f) projectArtifact = com.mycompany.app:my-app:jar:1.0-SNAPSHOT [DEBUG] (f) showDeprecation = false [DEBUG] (f) showWarnings = false [DEBUG] (f) staleMillis = 0 [DEBUG] (f) verbose = false [DEBUG] -- end configuration -- Thanks, Sahoo Sahoo wrote: Thanks, that works. Sahoo Wayne Fay wrote: Try this, Sahoo: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration compilerArgument-nowarn/compilerArgument compilerArgument-verbose/compilerArgument /configuration /plugin On 11/22/07, Sahoo [EMAIL PROTECTED] wrote: As suggested in [1], I tried configuring maven-compiler-plugin like this: compilerArgument-nowarn -verbose/compilerArgument But it causes compilation failure. Details given below: Failure executing javac, but could not parse the error: javac: invalid flag: -nowarn -verbose How can I pass multiple arguments to javac? Thanks, Sahoo [1] http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass- compiler-arguments.html - 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: 1.1-beta-4 to 1.1 final data migration
Now down to one artifact when using the data-management-cli-1.1-app.jar migration tool: 0 [main] INFO org.apache.maven.continuum.management.DataManagementCli - Processing Continuum database... Exception in thread main org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) javax.resource:connector:jar:1.0 Try downloading the file manually from: http://java.sun.com/j2ee/connector/download.html Then, install it using the command: mvn install:install-file -DgroupId=javax.resource -DartifactId=connector \ -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) dummy:dummy:pom:1.0 2) org.apache.maven.continuum:data-management-jdo:jar:1.1 3) jpox:jpox:jar:1.1.6 4) javax.resource:connector:jar:1.0 -- 1 required artifact is missing. for artifact: dummy:dummy:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:243) at org.apache.maven.continuum.management.DataManagementCli.downloadArtifact(DataManagementCli.java:401) at org.apache.maven.continuum.management.DataManagementCli.processDatabase(DataManagementCli.java:200) at org.apache.maven.continuum.management.DataManagementCli.main(DataManagementCli.java:170) --- The jar is in the local maven repository and the above listed command was used to put it in the repository. The box is running Windows XP. Maven reports this information when running the --version if that is of any help: Maven version: Maven version: 2.0.7 Java version: 1.6.0_03 OS name: windows xp version: 5.1 arch: x8
Re: 1.1-beta-4 to 1.1 final data migration
Hi, Just do what is asked (you need to have maven 2 installed), go to those url's, download the needed jar and add it to your local repository using the mvn install:install-file command. Apache can not host those files in their repository because of licensing issues... If you have a company-wide repository you can add them there using the deploy:deploy-file command As alternative option I suppose you can add the sun maven/maven2 repo to your ~/.m2/settings.xml (not sure) Francis On 11/26/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: Hmm, weird. As a workaround, I think you can use datamanagement 1.1 to migrate your data because we don't have db schema (if I remember it correctly between 1.1-beta-4 and 1.1 final) Emmanuel Johnathan Gifford a écrit : While trying to migrate our data from 1.1-beta-4, I'm getting the following error trying to export data out of the beta install: 0 [main] INFO org.apache.maven.continuum.management.DataManagementCli - Processing Continuum database... Exception in thread main org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) javax.resource:connector:jar:1.0 Try downloading the file manually from: http://java.sun.com/j2ee/connector/download.html Then, install it using the command: mvn install:install-file -DgroupId=javax.resource -DartifactId=connector \ -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) dummy:dummy:pom:1.0 2) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-4 3) jpox:jpox:jar:1.1.6 4) javax.resource:connector:jar:1.0 2) javax.transaction:jta:jar:1.0.1B Try downloading the file manually from: http://java.sun.com/products/jta Then, install it using the command: mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta \ -Dversion=1.0.1B -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) dummy:dummy:pom:1.0 2) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-4 3) jpox:jpox:jar:1.1.6 4) javax.transaction:jta:jar:1.0.1B -- 2 required artifacts are missing. for artifact: dummy:dummy:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:243) at org.apache.maven.continuum.management.DataManagementCli.downloadArtifact(DataManagementCli.java:304) at org.apache.maven.continuum.management.DataManagementCli.processDatabase(DataManagementCli.java:185) at org.apache.maven.continuum.management.DataManagementCli.main(DataManagementCli.java:158) - I've installed the two missing artifacts and still continue to get the above error. Any suggestions where to look or what to run? Thanks, Johnathan -- http://www.somatik.be Microsoft gives you windows, Linux gives you the whole house.
Re: Maven release plugin: Address already in use!
Yup, that was the problem, removing the remote debug args fixed it. Should I file a Jira issue about it? Bashar Jorg Heymans wrote: I've seen this happening when MAVEN_OPTS is set to enable remote debugging. What happens is that the release plugin invokes a system exec of some sort of mvn which then tries to use the same MAVEN_OPTS and fails because the debug port is already taken. Makes sense? Jorg On Nov 26, 2007 5:11 PM, Bashar Jawad [EMAIL PROTECTED] wrote: I still can't resolve this issue. I am using Maven 2.0.7. This is a major blocker issue for me so I would really appreciate any help. Does anyone at least know what port the release plugin uses ? Thanks, Bashar Jawad wrote: I am trying to use the maven-release-plugin to prepare and perform a release. I simply created a new empty maven 2 project and added the required scm information in the POM. However any time I run the command: mvn release:clean release:prepare maven asks me for release/tag/developement version information and then exists with the following error: [INFO] Transforming 'Unnamed - ReleasePluginDemo:ReleasePluginDemo:jar:1.0-SNAPSHOT'... [INFO] Not generating release POMs [INFO] Executing goals 'clean verify'... [INFO] Executing: mvn clean verify --no-plugin-updates -P default ERROR: transport error 202: bind failed: Address already in use [transport.c,L41] FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113) ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) [debugInit.c,L500] JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Maven execution failed, exit code: '1' [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Maven execution failed, exit code: '1' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:564) 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:224) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Maven execution failed, exit code: '1' at org.apache.maven.plugins.release.PrepareReleaseMojo.execute( PrepareReleaseMojo.java:131) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:539) ... 16 more Caused by: org.apache.maven.shared.release.ReleaseExecutionException: Maven execution failed, exit code: '1' at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute( AbstractRunGoalsPhase.java:66) at org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.execute( RunPrepareGoalsPhase.java:42) at org.apache.maven.shared.release.DefaultReleaseManager.prepare( DefaultReleaseManager.java:194) at org.apache.maven.shared.release.DefaultReleaseManager.prepare( DefaultReleaseManager.java:131) at org.apache.maven.shared.release.DefaultReleaseManager.prepare( DefaultReleaseManager.java:94) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute( PrepareReleaseMojo.java:127) ... 18 more
Re: Dependency Browser Tool
Hi,
+1 for the idea of making a dependency:resolve-gui goal; it would be
nice :-)
I have a problem testing your tool : it doesn't seem to properly manage
properties.
I don't know if it comes from your code or maven-model but there's an
issue having in a pom.xml something like this :
...
properties
module1.version1.0-SNAPSHOT/module1.version
/properties
modules
modulemodule1/module
modulemodule2/module
/modules
dependencyManagement
dependencies
dependency
groupIdgroup1/groupId
artifactIdmodule1/artifactId
version${module1.version}/version
/dependency
/dependencies
/dependencyManagement
Both module1 and module2 use this pom as parent and module2 has module1
as a dependency.
I get the following error and, running it from eclipse, I can see the
tool finds two versions for module1 : 1.0-SNAPSHOT and
${module1.version}.
Exception in thread AWT-EventQueue-0 java.lang.NullPointerException
at java.io.File.init(File.java:277)
at
org.maven.dependencybrowser.implementations.local.LocalDiskRepository.resolveFile(LocalDiskRepository.java:29)
at
org.maven.dependencybrowser.controller.ArtifactResolver.resolveFile(ArtifactResolver.java:93)
at
org.maven.dependencybrowser.controller.ArtifactResolver.resolveArtifact(ArtifactResolver.java:64)
at
org.maven.dependencybrowser.controller.Controller.resolveArtifact(Controller.java:109)
at
org.maven.dependencybrowser.model.PomFile.resolveDependencies(PomFile.java:26)
at
org.maven.dependencybrowser.model.RootPom.resolveDependencies(RootPom.java:35)
at
org.maven.dependencybrowser.controller.Controller.loadPom(Controller.java:50)
at
org.maven.dependencybrowser.gui.DependencyBrowserGui$4.actionPerformed(DependencyBrowserGui.java:136)
...
I've tested on multiple projects (all defined in a similar way and got
the same result); of course, the projects I tested your tool on are
working with maven and most plugins.
Rune Flobakk a écrit :
I don't think there is anything stopping anyone to wrap a
plugin/MOJO-interface around the maven-dependency-browser to achieve
what you suggest :)
- Rune
Martin Gilday wrote:
Thanks Jake. I wasn't suggesting you move away from the GUI, I just
wasn't aware that you couldn't lauch a GUI from a Maven plugin. It
would just be nice for something like this to be part of the dependency
plugin. mvn dependency:resolve is great, mvn dependency:resolve-gui
would be even better.
- Original message -
From: jake pezaro [EMAIL PROTECTED]
To: users@maven.apache.org
Date: Sun, 25 Nov 2007 13:38:50 -0800 (PST)
Subject: Re: Dependency Browser Tool
there are a couple of reasons why this is not a maven plugin.
1. we found it much easier to understand the dependency tree when it
was
displayed in a GUI (ie being able open and close branches, see paths
being
highlighted etc). if this were to be a plugin it would need to display
text output, which we couldn't make as easy to understand (although if
you
have any ideas here then please send me an example).
2. maven reactor already provides a more static version of this
information
in it's convergence reports. we didn't want to replicate that
functionality, we just wanted a simple tool to track down rouge
transitive
dependencies.
Martin Gilday wrote:
Is there any reason this isn't a Maven plugin though? --repository
could
be taken from settings.xml
--workspace could just be the current directory where you run mvn
xx:xx.
-
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: Version moving up fast
Unfortunately what I suggested doesn't work because of http://jira.codehaus.org/browse/MDEPLOY-44 - setting uniqueVersion from the command line doesn't work together with deploy:deploy, only with deploy:deploy-file - of course you could use the latter but it gets even more cumbersome. Kalle On 11/26/07, Kalle Korhonen [EMAIL PROTECTED] wrote: If you are releasing something, I think it's wrong to force your clients to move onto the new versions. If the client modules using your module would be in control of what they use, they'd update versions in their own schedule, even skip some. I haven't tried, but I wonder if it'd work to use both unique and non-unique versions. If you release for archiving purposes, you could could just post a unique snapshot, otherwise you'd use non-unique snapshots. You'd need to check if dependency resolution works correctly in all cases with this approach. Kalle On 11/25/07, Borut Bolčina [EMAIL PROTECTED] wrote: Hello maven users, if one of our in-house jars (lets call it A.jar) is progressing fast in terms of artifact version numbers (several times per week: 2.1 - 2.2 - 2.3- ... - 2.678 - 2.679 - ...), what is the best way for other artifacts which depend on this fast one to always use the last one? All the artifacts which depend on the A, would have to have their poms modified to 2.1-SNAPSHOT , 2.2-SNAPSHOT etc. because the SNAPSHOT version is in the trunk. This is error prone. I haven't looked into the release plugin yet, but I don't think it addresses this issue. One solution might be to name the A's version to something like 999-SNAPSHOT and then all the other jars would have their dependencies to this version. This smells like a dead fish in the sewer to me. What do you say?
Re: 1.1-beta-4 to 1.1 final data migration
Just do what is asked (you need to have maven 2 installed), go to those url's, download the needed jar and add it to your local repository using the mvn install:install-file command. Already done that, that's why I'm posting this thread. Apache can not host those files in their repository because of licensing issues... Understand completely. If you have a company-wide repository you can add them there using the deploy:deploy-file command It's in my local repository and the paths are there. Maven is pointing to the local as the first (and only) lookup location. As alternative option I suppose you can add the sun maven/maven2 repo to your ~/.m2/settings.xml (not sure) Not a bad idea, but still didn't work. I added the following in the path settings/profiles/repositories to the conf/settings.xml file for Maven2: repository idjava.net/id urlhttp://download.java.net/maven/1/url layoutlegacy/layout /repository That is how Sun instructed to set this up at their site (https://maven-repository.dev.java.net/).
Re: Not able to pass multiple arguments to javac
My first assumption was indeed wrong, because I used java 1.5 to check for the existence of those properties. Also, your description (They are not supported by javac.) set me on the wrong track. See my other mail for the how and why of this error. And indeed, in the current implementation, when you have multiple compilerArgument elements only one is taken. I guess it just runs setCompilerArgument multiple times. With regards, Nick Stolwijk Sahoo wrote: I doubt those message come from javac. They were printed by maven when I ran it with -X option. Tell me what is the option that is *not* supported by javac. AFAIK, all the options that I want to pass are very much supported by javac. Check out the documentation [1] of javac that comes with Sun JDK 6. More over, JDK 6 compiler allows to provide plugins to javac. In order to configure the plugin user may have to pass options that are *not* meant for javac itself, instead they are meant for the javac plugin. Such options will never be supported by maven-javac-plugin, hence compilerArgument is the only way to use them. In case of Sun JDK, any javac option starting -A is passed onto the plugin. An example is available at [2]. I actually faced all my maven issues while developing that plugin. My observation is that when multiple compilerArgument is used, only the last one is considered. Thanks, Sahoo [1] http://java.sun.com/javase/6/docs/technotes/tools/solaris/javac.html [2] http://weblogs.java.net/blog/ss141213/archive/2007/11/a_javac_plugin_1.html [EMAIL PROTECTED] wrote: The fault message you see is actually from javac itself. You're trying to add options that are not supported by javac. All javac options are supported by the mojo, it simply passes them to javac. Why would you want to add options to javac which are not supported by javac? With regards, Nick Stolwijk -Original Message- From: [EMAIL PROTECTED] on behalf of Sahoo Sent: Mon 11/26/2007 5:12 PM To: Maven Users List Subject: Re: Not able to pass multiple arguments to javac Yes, I knew that approach, but the options I actually want to pass are not supported by the mojo. nowarn and verbose were just used as examples; I want to pass -proc:none and -implicit. They are not supported by javac. There are many such options which are not supported by the mojo. I thought compilerArgument is the way to use them. But, it is *not* working. Thanks, Sahoo Jeff Jensen wrote: Try this approach: configuration forktrue/fork maxmem1024m/maxmem showDeprecationtrue/showDeprecation showWarningstrue/showWarnings etc... /configuration To know element names to use, use the Name found in the Optional Parameters section of this page: http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sahoo Sent: Monday, November 26, 2007 8:25 AM To: Maven Users List Subject: Re: Not able to pass multiple arguments to javac Ignore my earlier email. The suggestion actually does *not* work. When I run with -X option, it shows only the last compilerArgument. See the following output: [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile' -- [DEBUG] (f) basedir = /tmp/my-app [DEBUG] (f) buildDirectory = /tmp/my-app/target [DEBUG] (f) classpathElements = [/tmp/my-app/target/classes] [DEBUG] (f) compileSourceRoots = [/tmp/my-app/src/main/java] [DEBUG] (f) compilerArgument = -verbose [DEBUG] (f) compilerId = javac [DEBUG] (f) debug = true [DEBUG] (f) failOnError = true [DEBUG] (f) fork = false [DEBUG] (f) optimize = false [DEBUG] (f) outputDirectory = /tmp/my-app/target/classes [DEBUG] (f) outputFileName = my-app-1.0-SNAPSHOT [DEBUG] (f) projectArtifact = com.mycompany.app:my-app:jar:1.0-SNAPSHOT [DEBUG] (f) showDeprecation = false [DEBUG] (f) showWarnings = false [DEBUG] (f) staleMillis = 0 [DEBUG] (f) verbose = false [DEBUG] -- end configuration -- Thanks, Sahoo Sahoo wrote: Thanks, that works. Sahoo Wayne Fay wrote: Try this, Sahoo: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration compilerArgument-nowarn/compilerArgument compilerArgument-verbose/compilerArgument /configuration /plugin On 11/22/07, Sahoo [EMAIL PROTECTED] wrote: As suggested in [1], I tried configuring maven-compiler-plugin like this: compilerArgument-nowarn -verbose/compilerArgument But it causes compilation failure. Details given below: Failure executing javac, but could not parse the error: javac: invalid flag: -nowarn -verbose How can I pass multiple arguments to javac? Thanks, Sahoo [1] http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-
User id for SCP
How do I set the user id maven uses when deploying via scp? -- Esse Quam Videre To Be, rather than to Seem
Re: User id for SCP
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
version1.0-rc1/version
configuration
*username${scm.username}/username
password${scm.password}/password*
/configuration
/plugin
On Nov 26, 2007 11:37 AM, Jon Strayer [EMAIL PROTECTED] wrote:
How do I set the user id maven uses when deploying via scp?
--
Esse Quam Videre
To Be, rather than to Seem
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/BLiNCMagazine
http://tahoe.baselogic.com
---
Re: Not able to pass multiple arguments to javac
I haven't looked at the code, but based on some historical emails on this list it seemed like multiple compilerArgument tags were the way to go. One possible fix would be to take away the quoting of these arguments, but I'm not sure if this wouldn't create some new unintended side-effects. It certainly sounds like this is something that could stand to be improved. Wayne On 11/26/07, Nick Stolwijk [EMAIL PROTECTED] wrote: My first assumption was indeed wrong, because I used java 1.5 to check for the existence of those properties. Also, your description (They are not supported by javac.) set me on the wrong track. See my other mail for the how and why of this error. And indeed, in the current implementation, when you have multiple compilerArgument elements only one is taken. I guess it just runs setCompilerArgument multiple times. With regards, Nick Stolwijk Sahoo wrote: I doubt those message come from javac. They were printed by maven when I ran it with -X option. Tell me what is the option that is *not* supported by javac. AFAIK, all the options that I want to pass are very much supported by javac. Check out the documentation [1] of javac that comes with Sun JDK 6. More over, JDK 6 compiler allows to provide plugins to javac. In order to configure the plugin user may have to pass options that are *not* meant for javac itself, instead they are meant for the javac plugin. Such options will never be supported by maven-javac-plugin, hence compilerArgument is the only way to use them. In case of Sun JDK, any javac option starting -A is passed onto the plugin. An example is available at [2]. I actually faced all my maven issues while developing that plugin. My observation is that when multiple compilerArgument is used, only the last one is considered. Thanks, Sahoo [1] http://java.sun.com/javase/6/docs/technotes/tools/solaris/javac.html [2] http://weblogs.java.net/blog/ss141213/archive/2007/11/a_javac_plugin_1.html [EMAIL PROTECTED] wrote: The fault message you see is actually from javac itself. You're trying to add options that are not supported by javac. All javac options are supported by the mojo, it simply passes them to javac. Why would you want to add options to javac which are not supported by javac? With regards, Nick Stolwijk -Original Message- From: [EMAIL PROTECTED] on behalf of Sahoo Sent: Mon 11/26/2007 5:12 PM To: Maven Users List Subject: Re: Not able to pass multiple arguments to javac Yes, I knew that approach, but the options I actually want to pass are not supported by the mojo. nowarn and verbose were just used as examples; I want to pass -proc:none and -implicit. They are not supported by javac. There are many such options which are not supported by the mojo. I thought compilerArgument is the way to use them. But, it is *not* working. Thanks, Sahoo Jeff Jensen wrote: Try this approach: configuration forktrue/fork maxmem1024m/maxmem showDeprecationtrue/showDeprecation showWarningstrue/showWarnings etc... /configuration To know element names to use, use the Name found in the Optional Parameters section of this page: http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sahoo Sent: Monday, November 26, 2007 8:25 AM To: Maven Users List Subject: Re: Not able to pass multiple arguments to javac Ignore my earlier email. The suggestion actually does *not* work. When I run with -X option, it shows only the last compilerArgument. See the following output: [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile' -- [DEBUG] (f) basedir = /tmp/my-app [DEBUG] (f) buildDirectory = /tmp/my-app/target [DEBUG] (f) classpathElements = [/tmp/my-app/target/classes] [DEBUG] (f) compileSourceRoots = [/tmp/my-app/src/main/java] [DEBUG] (f) compilerArgument = -verbose [DEBUG] (f) compilerId = javac [DEBUG] (f) debug = true [DEBUG] (f) failOnError = true [DEBUG] (f) fork = false [DEBUG] (f) optimize = false [DEBUG] (f) outputDirectory = /tmp/my-app/target/classes [DEBUG] (f) outputFileName = my-app-1.0-SNAPSHOT [DEBUG] (f) projectArtifact = com.mycompany.app:my-app:jar:1.0-SNAPSHOT [DEBUG] (f) showDeprecation = false [DEBUG] (f) showWarnings = false [DEBUG] (f) staleMillis = 0 [DEBUG] (f) verbose = false [DEBUG] -- end configuration -- Thanks, Sahoo Sahoo wrote: Thanks, that works. Sahoo Wayne Fay wrote: Try this, Sahoo: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration compilerArgument-nowarn/compilerArgument
using assembly to create a war file
Using maven 2.0.7 - I have a project that creates a war file. I want to
modify the war file and rename some of the files based on the current
project version. So my assembly.xml looks like:
assembly
iddistribution/id
formats
formatwar/format
/formats
files
file
filteredtrue/filtered
sourcesrc/main/webapp/scripts/shared.js/source
destNamescripts/shared-${project.version}.js/destName
/file
file
filteredtrue/filtered
sourcesrc/main/webapp/scripts/global.js/source
destNamescripts/global-${project.version}.js/destName
/file
/files
fileSets
fileSet
directorytarget/cp-${project.version}//directory
outputDirectory//outputDirectory
includes
include**/*/include
excludescripts/global.js/exclude
excludescripts/shared.js/exclude
/includes
/fileSet
/fileSets
/assembly
All this works fine and creates a new war file except for two issues
1 - The new war file created by assembly has an extra directory level at
the top, in the listing below I want everything below cp0-1.1.0-SNAPSHOT,
just like the war file that is initially created by maven
Archive: target//cp-1.1.0-SNAPSHOT-distribution.war
Length Date TimeName
0 11-26-07 11:57 META-INF/
110 11-26-07 11:57 META-INF/MANIFEST.MF
0 11-26-07 11:57 cp-1.1.0-SNAPSHOT/
0 11-26-07 11:57 cp-1.1.0-SNAPSHOT/scripts/
0 11-26-07 11:57 cp-1.1.0-SNAPSHOT/scripts/maps/
0 11-26-07 11:57 cp-1.1.0-SNAPSHOT/scripts/thirdparty/
0 11-26-07 11:57 cp-1.1.0-SNAPSHOT/scripts/yui/
0 11-26-07 11:57 cp-1.1.0-SNAPSHOT/scripts/ga/
0 11-26-07 11:57 cp-1.1.0-SNAPSHOT/scripts/hardcore/
0 11-26-07 11:57 cp-1.1.0-SNAPSHOT/scripts/hardcore/dtree/
0 11-26-07 11:57 cp-1.1.0-SNAPSHOT/scripts/hardcore/webeditor/
0 11-26-07 11:57
cp-1.1.0-SNAPSHOT/scripts/hardcore/webeditor/dtree/
0 11-26-07 11:57 cp-1.1.0-SNAPSHOT/scripts/hardcore/upload/
2 - the exclude statements are not working, those files are still included
in the newly assembled war file
Any ideas??
thanks, Lee
--
View this message in context:
http://www.nabble.com/using-assembly-to-create-a-war-file-tf4877643s177.html#a13957672
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Build Definitions Question
Is it possible to have more than build definition in the same project group to be set to default? Thank you. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
Maven2 and Selenium problem / anyone could help?
hi all,
i am trying out Maven2 with selenium plugin, but i am getting alwasy
same error and i was wondering if anyone else here came across
same situation...
here's my test
( i had my own url but as i kept on getting
exceptions i tried with a well known one
public class LoginTest extends SeleneseTestCase {
public void testLogin() throws Exception {
selenium.open(http://www.google.com;);
verifyTrue(selenium.isTextPresent(Google));//Hello and
Welcome to
BudgetWeb V2 Application));
}
}
*** here's my pom (only relevant part) ***
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.0.1/version
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdselenium-maven-plugin/artifactId
executions
execution
idstart/id
phasepre-integration-test/phase
goals
goalstart-server/goal
/goals
configuration
backgroundtrue/background
logOutputtrue/logOutput
multiWindowtrue/multiWindow
/configuration
/execution
execution
idstop/id
phasepost-integration-test/phase
goals
goalstop-server/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.codehaus.cargo/groupId
artifactIdcargo-maven2-plugin/artifactId
version0.3-SNAPSHOT/version
configuration
waitfalse/wait
container
containerIdjetty6x/containerId
typeembedded/type
/container
/configuration
executions
execution
idstart-container/id
phasepre-integration-test/phase
goals
goalstart/goal
goaldeploy/goal
/goals
/execution
execution
idstop-container/id
phasepost-integration-test/phase
goals
goalstop/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
excludes
exclude**/uattests/*Test.java/exclude
/excludes
systemProperties
property
namenet.sourceforge.cobertura.datafile/name
valuetarget/cobertura/cobertura.ser/value
/property
/systemProperties
/configuration
executions
execution
idintegration-tests/id
phaseintegration-test/phase
goals
goaltest/goal
/goals
configuration
skipfalse/skip
excludes
excludenone/exclude
/excludes
Re: The Maven team needs help from translators
Thanks! Juven Xu wrote: Hi, Denneis: I can take the zh_CN translation and finish it in this week. On Nov 26, 2007 3:35 PM, Milos Kleint [EMAIL PROTECTED] wrote: it's in mojo's sandbox https://svn.codehaus.org/mojo/trunk/sandbox/l10n-maven-plugin/ Milos On 11/26/07, Wim Deblauwe [EMAIL PROTECTED] wrote: Nice plugin report. Is this plugin freely available? regards, Wim 2007/11/25, Dennis Lundberg [EMAIL PROTECTED]: Lukas Theussl has updated the German resource bundle. I have uploaded an updated localization status report: http://people.apache.org/~dennisl/maven-project-info-reports-plugin/l10n-status.htmlhttp://people.apache.org/%7Edennisl/maven-project-info-reports-plugin/l10n-status.html Dennis Lundberg wrote: Hi all We are preparing the next release of the maven-project-info-reports-plugin. The current localizations are lacking translations for lots of resources. We need your help improving this. Have a look at this report, and see if you are skilled in any of the listed languages: http://people.apache.org/~dennisl/maven-project-info-reports-plugin/l10n-status.htmlhttp://people.apache.org/%7Edennisl/maven-project-info-reports-plugin/l10n-status.html If so please create a patch and attach it to this issue in JIRA: http://jira.codehaus.org/browse/MPIR-34 Make sure you use unicode escape sequences for non-ascii characters. You can see how this is done in the current localizations. For more info on internationalization/localization in Maven plugins, see this page: http://maven.apache.org/plugins/maven-site-plugin/i18n.html If you have any questions about this, please don't hesitate to ask here on the list. Thanks for your cooperation -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Vigilog - an open source log file viewer: http://vigilog.sourceforge.net Blog: http://www.jroller.com/page/Fester -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Maven team needs help from translators
People who have volunteered seem to want about one week to work on this. So I don't plan to make the release this week. If you need more time than a week, let us know how much and we'll see if we can adapt the release date to your requirements. Thanks! Jose Alejandro Uriza Zepahua wrote: I would like to help you with the Spanish translation. When would you need it? Regards, Alejandro Uriza -Original Message- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: November 24, 2007 1:03 PM To: Maven Users List Subject: The Maven team needs help from translators Hi all We are preparing the next release of the maven-project-info-reports-plugin. The current localizations are lacking translations for lots of resources. We need your help improving this. Have a look at this report, and see if you are skilled in any of the listed languages: http://people.apache.org/~dennisl/maven-project-info-reports-plugin/l10n -status.html If so please create a patch and attach it to this issue in JIRA: http://jira.codehaus.org/browse/MPIR-34 Make sure you use unicode escape sequences for non-ascii characters. You can see how this is done in the current localizations. For more info on internationalization/localization in Maven plugins, see this page: http://maven.apache.org/plugins/maven-site-plugin/i18n.html If you have any questions about this, please don't hesitate to ask here on the list. Thanks for your cooperation -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 and Selenium problem / anyone could help?
Copied from [1]:
The quick answer is that because of cross-site scripting security built
into JavaScript engines in all browsers, you can't edit the content of a
web page from another domain. The foreign page will probably load
correctly and be visible in the test runner window, but Selenium won't
be able to query or edit its contents.
In other words, you can't run selenium on foo.com and run a test that
edits values and clicks buttons against bar.com. So, in its current
form, you can't script google.com because your script isn't currently
hosted on google.com. When Selenium and the application you are testing
is hosted on the same domain, however, you do not run into the
cross-site scripting security feature/limitation.
You can read more about cross-site scripting here: Dev Articles [2]
Hth,
Nick Stolwijk
[1] http://wiki.openqa.org/display/SEL/Selenium+Core+FAQ
[2] http://www.devarticles.com/c/a/JavaScript/JavaScript-Security/
http://www.devarticles.com/c/a/JavaScript/JavaScript-Security/
Marco Mistroni wrote:
hi all,
i am trying out Maven2 with selenium plugin, but i am getting alwasy
same error and i was wondering if anyone else here came across
same situation...
here's my test
( i had my own url but as i kept on getting
exceptions i tried with a well known one
public class LoginTest extends SeleneseTestCase {
public void testLogin() throws Exception {
selenium.open(http://www.google.com;);
verifyTrue(selenium.isTextPresent(Google));//Hello and
Welcome to
BudgetWeb V2 Application));
}
}
*** here's my pom (only relevant part) ***
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.0.1/version
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdselenium-maven-plugin/artifactId
executions
execution
idstart/id
phasepre-integration-test/phase
goals
goalstart-server/goal
/goals
configuration
backgroundtrue/background
logOutputtrue/logOutput
multiWindowtrue/multiWindow
/configuration
/execution
execution
idstop/id
phasepost-integration-test/phase
goals
goalstop-server/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.codehaus.cargo/groupId
artifactIdcargo-maven2-plugin/artifactId
version0.3-SNAPSHOT/version
configuration
waitfalse/wait
container
containerIdjetty6x/containerId
typeembedded/type
/container
/configuration
executions
execution
idstart-container/id
phasepre-integration-test/phase
goals
goalstart/goal
goaldeploy/goal
/goals
/execution
execution
idstop-container/id
phasepost-integration-test/phase
goals
goalstop/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
excludes
exclude**/uattests/*Test.java/exclude
/excludes
systemProperties
property
overriding jspc-maven-plugin
Hi
I have a super-parent POM that all of my projects inherit...
90% of the projects are WAR files and few are multi module JARs
I would like to define a JSPC compile plugin at the super-parent POM level but
the problem arises when building non-WAR projects
How can I redefine specific project's POMs (the ones that are JARs) not to
consider JSPC plugin?
The obvious solution is not to define jspc-maven-plugin at the super-parent POM
level but in each project individually...
But that means I have to specify something like this in multiple places which I
am trying to avoid:
plugin
groupIdorg.codehaus.mojo.jspc/groupId
artifactIdjspc-maven-plugin/artifactId
version2.0-alpha-1/version
executions
execution
goals
goalcompile/goal
/goals
/execution
/executions
dependencies
dependency
groupIdorg.codehaus.mojo.jspc/groupId
artifactIdjspc-compiler-tomcat5/artifactId
version2.0-alpha-1/version
/dependency
/dependencies
configuration
sources
directory${basedir}/src/main/resources//directory
includes
include**/*.jsp/include
/includes
/sources
source1.6/source
target1.6/target
verbose1/verbose
/configuration
/plugin
Is there a way to do this? Currently I get following error when I try to build
one of my JAR projects:
[WARNING] Compiled JSPs will not be added to the project and web.xml will not
be modified, either because includeInProject is set to false or because the
project's packaging is not 'war'.
[INFO] Created dir:
C:\mycompany\project\COOLP\mycompany-common\target\jsp-source
[INFO] Created dir: C:\mycompany\project\COOLP\mycompany-common\target\classes
[INFO] Compiling JSP source files to
C:\mycompany\project\COOLP\mycompany-common\target/jsp-source
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] The -uriroot option must specify a pre-existing directory
[INFO]
[INFO] Trace
org.apache.jasper.JasperException: The -uriroot option must specify a
pre-existing directory
Re: Version moving up fast
It sounds odd to have that many release version per day. Version range notation would be perfect for what you need.. i.e., [2.1, ) Having said that I found a number of problems with using version range and I am stuck with 2.0.6 because 2.0.7 gives me NPE when it tries to resolve conflict between version ranges. Cheers, rOnn c. Borut Bolčina [EMAIL PROTECTED] 11/26/2007 06:31 PM Please respond to Maven Users List users@maven.apache.org To Maven users@maven.apache.org cc Subject Version moving up fast Hello maven users, if one of our in-house jars (lets call it A.jar) is progressing fast in terms of artifact version numbers (several times per week: 2.1 - 2.2 - 2.3- ... - 2.678 - 2.679 - ...), what is the best way for other artifacts which depend on this fast one to always use the last one? All the artifacts which depend on the A, would have to have their poms modified to 2.1-SNAPSHOT, 2.2-SNAPSHOT etc. because the SNAPSHOT version is in the trunk. This is error prone. I haven't looked into the release plugin yet, but I don't think it addresses this issue. One solution might be to name the A's version to something like 999-SNAPSHOT and then all the other jars would have their dependencies to this version. This smells like a dead fish in the sewer to me. What do you say? ## DISCLAIMER: This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorized to copy or disclose all or any part of it without the prior written consent of Toyota. Opinions expressed in this email and any attachments are those of the sender and not necessarily the opinions of Toyota. Please scan this email and any attachment(s) for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. ##
Re: Dependency issue (war and jar) in multimodule project
Hi, Anand: If child2 has a dependency on child1 war, I think you don't need to make dependency on child1 jar. Cause all the xml file and class file will be inherited. Thanks, Juven On Nov 26, 2007 3:34 PM, Anand Rathi [EMAIL PROTECTED] wrote: Hi, I have a multimodule project as shown below: - parent (pom) - child1 (war) - child2 (war) child2 project has a dependency on child1 jar as well as war. This is required because child1 war contains some xml files which I need at the child2 war creation time. I am building this project from parent folder using 'mvn clean install' command. It builds child1 module successfully and installs jar as well as war in repository. But while building child2 module, it fails because while expanding war files, it is expanding child1 jar file instead of child1 war file. Following message shown in log file [DEBUG] Processing: child1-1.0-SNAPSHOT.war [INFO] Expanding: D:\temp\child1\target\child1-1.0-SNAPSHOT.jar into D:\temp\child2\target\war\work\child1-1.0-SNAPSHOT thanks, Anand Chat on a cool, new interface. No download required. Go to http://in.messenger.yahoo.com/webmessengerpromo.php
Re: overriding jspc-maven-plugin
Many plugins offer a skip configuration option. Check the plugin
docs to see if jspc-m-p does, and if it does not, file a JIRA to
request that someone else add it or do it yourself. Then you could
simply add the plugin in the parent, and declare it with
skiptrue/skip in the non-WAR children projects.
Wayne
On 11/26/07, Amir Mistric [EMAIL PROTECTED] wrote:
Hi
I have a super-parent POM that all of my projects inherit...
90% of the projects are WAR files and few are multi module JARs
I would like to define a JSPC compile plugin at the super-parent POM level
but the problem arises when building non-WAR projects
How can I redefine specific project's POMs (the ones that are JARs) not to
consider JSPC plugin?
The obvious solution is not to define jspc-maven-plugin at the super-parent
POM level but in each project individually...
But that means I have to specify something like this in multiple places which
I am trying to avoid:
plugin
groupIdorg.codehaus.mojo.jspc/groupId
artifactIdjspc-maven-plugin/artifactId
version2.0-alpha-1/version
executions
execution
goals
goalcompile/goal
/goals
/execution
/executions
dependencies
dependency
groupIdorg.codehaus.mojo.jspc/groupId
artifactIdjspc-compiler-tomcat5/artifactId
version2.0-alpha-1/version
/dependency
/dependencies
configuration
sources
directory${basedir}/src/main/resources//directory
includes
include**/*.jsp/include
/includes
/sources
source1.6/source
target1.6/target
verbose1/verbose
/configuration
/plugin
Is there a way to do this? Currently I get following error when I try to
build one of my JAR projects:
[WARNING] Compiled JSPs will not be added to the project and web.xml will not
be modified, either because includeInProject is set to false or because the
project's packaging is not 'war'.
[INFO] Created dir:
C:\mycompany\project\COOLP\mycompany-common\target\jsp-source
[INFO] Created dir: C:\mycompany\project\COOLP\mycompany-common\target\classes
[INFO] Compiling JSP source files to
C:\mycompany\project\COOLP\mycompany-common\target/jsp-source
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] The -uriroot option must specify a pre-existing directory
[INFO]
[INFO] Trace
org.apache.jasper.JasperException: The -uriroot option must specify a
pre-existing directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Not able to pass multiple arguments to javac
An improvement request is filed: http://jira.codehaus.org/browse/MCOMPILER-62 Sahoo Wayne Fay wrote: I haven't looked at the code, but based on some historical emails on this list it seemed like multiple compilerArgument tags were the way to go. One possible fix would be to take away the quoting of these arguments, but I'm not sure if this wouldn't create some new unintended side-effects. It certainly sounds like this is something that could stand to be improved. Wayne On 11/26/07, Nick Stolwijk [EMAIL PROTECTED] wrote: My first assumption was indeed wrong, because I used java 1.5 to check for the existence of those properties. Also, your description (They are not supported by javac.) set me on the wrong track. See my other mail for the how and why of this error. And indeed, in the current implementation, when you have multiple compilerArgument elements only one is taken. I guess it just runs setCompilerArgument multiple times. With regards, Nick Stolwijk Sahoo wrote: I doubt those message come from javac. They were printed by maven when I ran it with -X option. Tell me what is the option that is *not* supported by javac. AFAIK, all the options that I want to pass are very much supported by javac. Check out the documentation [1] of javac that comes with Sun JDK 6. More over, JDK 6 compiler allows to provide plugins to javac. In order to configure the plugin user may have to pass options that are *not* meant for javac itself, instead they are meant for the javac plugin. Such options will never be supported by maven-javac-plugin, hence compilerArgument is the only way to use them. In case of Sun JDK, any javac option starting -A is passed onto the plugin. An example is available at [2]. I actually faced all my maven issues while developing that plugin. My observation is that when multiple compilerArgument is used, only the last one is considered. Thanks, Sahoo [1] http://java.sun.com/javase/6/docs/technotes/tools/solaris/javac.html [2] http://weblogs.java.net/blog/ss141213/archive/2007/11/a_javac_plugin_1.html [EMAIL PROTECTED] wrote: The fault message you see is actually from javac itself. You're trying to add options that are not supported by javac. All javac options are supported by the mojo, it simply passes them to javac. Why would you want to add options to javac which are not supported by javac? With regards, Nick Stolwijk -Original Message- From: [EMAIL PROTECTED] on behalf of Sahoo Sent: Mon 11/26/2007 5:12 PM To: Maven Users List Subject: Re: Not able to pass multiple arguments to javac Yes, I knew that approach, but the options I actually want to pass are not supported by the mojo. nowarn and verbose were just used as examples; I want to pass -proc:none and -implicit. They are not supported by javac. There are many such options which are not supported by the mojo. I thought compilerArgument is the way to use them. But, it is *not* working. Thanks, Sahoo Jeff Jensen wrote: Try this approach: configuration forktrue/fork maxmem1024m/maxmem showDeprecationtrue/showDeprecation showWarningstrue/showWarnings etc... /configuration To know element names to use, use the Name found in the Optional Parameters section of this page: http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sahoo Sent: Monday, November 26, 2007 8:25 AM To: Maven Users List Subject: Re: Not able to pass multiple arguments to javac Ignore my earlier email. The suggestion actually does *not* work. When I run with -X option, it shows only the last compilerArgument. See the following output: [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile' -- [DEBUG] (f) basedir = /tmp/my-app [DEBUG] (f) buildDirectory = /tmp/my-app/target [DEBUG] (f) classpathElements = [/tmp/my-app/target/classes] [DEBUG] (f) compileSourceRoots = [/tmp/my-app/src/main/java] [DEBUG] (f) compilerArgument = -verbose [DEBUG] (f) compilerId = javac [DEBUG] (f) debug = true [DEBUG] (f) failOnError = true [DEBUG] (f) fork = false [DEBUG] (f) optimize = false [DEBUG] (f) outputDirectory = /tmp/my-app/target/classes [DEBUG] (f) outputFileName = my-app-1.0-SNAPSHOT [DEBUG] (f) projectArtifact = com.mycompany.app:my-app:jar:1.0-SNAPSHOT [DEBUG] (f) showDeprecation = false [DEBUG] (f) showWarnings = false [DEBUG] (f) staleMillis = 0 [DEBUG] (f) verbose = false [DEBUG] -- end configuration -- Thanks, Sahoo Sahoo wrote: Thanks, that works. Sahoo Wayne Fay wrote: Try this, Sahoo: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration compilerArgument-nowarn/compilerArgument
Interpolation of Pom Properties in Assembly Descriptor
I was using maven-assembly-plugin 2.2-SNAPSHOT and tried to switch to
2.2-beta-2-SNAPSHOT but encountered a problem.
I reference properties from my pom in the assembly descriptor, like this:
project
...
properties
my.pathmyapp/WEB-INF/my.path
/properties
..
/project
assembly
...
files
file
source${basedir}/target/config/somefile.conf/source
outputDirectory${my.path}/etc/outputDirectory
/file
/files
...
/assembly
In 2.2-SNAPSHOT, the value was substituted but in 2.2-beta-2-SNAPSHOT the
literal ${my.path} is used. Is this a regression, a removed feature, or has
the syntax for doing this changed?
-- Mark R
Re: Dependency issue (war and jar) in multimodule project
Hi Juven, I removed child1 jar dependency and only kept child1 war dependency but while building child2 project, it is still expanding child1 jar file instead of child1 war file. Also it is picking up 'child1-1.0-SNAPSHOT.jar' from 'child1\target' folder instead of repository. This is happening only in multi-module build environment. If I build child2 seperately, it is building successfully. Following message is shown in log: [DEBUG] Processing: child1-1.0-SNAPSHOT.war [INFO] Expanding: D:\temp\child1\target\child1-1.0-SNAPSHOT.jar into D:\temp\child2\target\war\work\child1-1.0-SNAPSHOT thanks, Anand - Original Message From: Juven Xu [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Tuesday, 27 November, 2007 7:01:59 AM Subject: Re: Dependency issue (war and jar) in multimodule project Hi, Anand: If child2 has a dependency on child1 war, I think you don't need to make dependency on child1 jar. Cause all the xml file and class file will be inherited. Thanks, Juven On Nov 26, 2007 3:34 PM, Anand Rathi [EMAIL PROTECTED] wrote: Hi, I have a multimodule project as shown below: - parent (pom) - child1 (war) - child2 (war) child2 project has a dependency on child1 jar as well as war. This is required because child1 war contains some xml files which I need at the child2 war creation time. I am building this project from parent folder using 'mvn clean install' command. It builds child1 module successfully and installs jar as well as war in repository. But while building child2 module, it fails because while expanding war files, it is expanding child1 jar file instead of child1 war file. Following message shown in log file [DEBUG] Processing: child1-1.0-SNAPSHOT.war [INFO] Expanding: D:\temp\child1\target\child1-1.0-SNAPSHOT.jar into D:\temp\child2\target\war\work\child1-1.0-SNAPSHOT thanks, Anand Chat on a cool, new interface. No download required. Go to http://in.messenger.yahoo.com/webmessengerpromo.php Download prohibited? No problem. CHAT from any browser, without download. Go to http://in.messenger.yahoo.com/webmessengerpromo.php/
Re: Dependency issue (war and jar) in multimodule project
In your dependency declaration, did you include typewar/type for the child1 dep in the child2 pom? Or how are you declaring the dependency? Perhaps show us your pom(s). Wayne On 11/26/07, Anand Rathi [EMAIL PROTECTED] wrote: Hi Juven, I removed child1 jar dependency and only kept child1 war dependency but while building child2 project, it is still expanding child1 jar file instead of child1 war file. Also it is picking up 'child1-1.0-SNAPSHOT.jar' from 'child1\target' folder instead of repository. This is happening only in multi-module build environment. If I build child2 seperately, it is building successfully. Following message is shown in log: [DEBUG] Processing: child1-1.0-SNAPSHOT.war [INFO] Expanding: D:\temp\child1\target\child1-1.0-SNAPSHOT.jar into D:\temp\child2\target\war\work\child1-1.0-SNAPSHOT thanks, Anand - Original Message From: Juven Xu [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Tuesday, 27 November, 2007 7:01:59 AM Subject: Re: Dependency issue (war and jar) in multimodule project Hi, Anand: If child2 has a dependency on child1 war, I think you don't need to make dependency on child1 jar. Cause all the xml file and class file will be inherited. Thanks, Juven On Nov 26, 2007 3:34 PM, Anand Rathi [EMAIL PROTECTED] wrote: Hi, I have a multimodule project as shown below: - parent (pom) - child1 (war) - child2 (war) child2 project has a dependency on child1 jar as well as war. This is required because child1 war contains some xml files which I need at the child2 war creation time. I am building this project from parent folder using 'mvn clean install' command. It builds child1 module successfully and installs jar as well as war in repository. But while building child2 module, it fails because while expanding war files, it is expanding child1 jar file instead of child1 war file. Following message shown in log file [DEBUG] Processing: child1-1.0-SNAPSHOT.war [INFO] Expanding: D:\temp\child1\target\child1-1.0-SNAPSHOT.jar into D:\temp\child2\target\war\work\child1-1.0-SNAPSHOT thanks, Anand Chat on a cool, new interface. No download required. Go to http://in.messenger.yahoo.com/webmessengerpromo.php Download prohibited? No problem. CHAT from any browser, without download. Go to http://in.messenger.yahoo.com/webmessengerpromo.php/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to rebuild modules that depend on a changed module?
Hi, I'm working on a multimodule project and after making a change in a module X, I would like to do the following: - mvn clean install on all modules in the project that have compile dependencies on X; - mvn test on all modules in the project that have runtime and test dependencies on X. Any idea of how I can automate that process? Is there any plugin or product integrated with Maven that will help me do that? Thanks -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
