Problem Executing Application With Maven
I am new to Spring amp; Maven. I have properly installed maven in my machine. Also able to compile the project code. But when I execute the java class using following command.. mvn -e exec:java -Dexec.mainClass=com.test.beg.Calculate -Dexec.args=3000 3It gives error like... + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'exec'. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Invalid task 'ûDexec.args=ö3000': you must specify a valid lifecycle phas e, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginV ersion:goal [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Invalid task 'ûDexec.args=ö3000': you mu st specify a valid lifecycle phase, or a goal in the format plugin:goal or plugi nGroupId:pluginArtifactId:pluginVersion:goal at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor (DefaultLifecycleExecutor.java:1830) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListBy AggregationNeeds(DefaultLifecycleExecutor.java:462) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:175) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6 0) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.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) [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Jan 10 15:48:43 IST 2011 [INFO] Final Memory: 2M/3M [INFO] Please help.
Re: Problem Executing Application With Maven
Eh, did you read my response to your same question the other day? http://maven.40175.n5.nabble.com/Problem-Executing-Application-With-Maven-td3349323.html /Anders On Fri, Jan 21, 2011 at 10:41, Chintan Sanghavi sanghav...@rediffmail.comwrote: I am new to Spring amp; Maven. I have properly installed maven in my machine. Also able to compile the project code. But when I execute the java class using following command.. mvn -e exec:java -Dexec.mainClass=com.test.beg.Calculate -Dexec.args=3000 3It gives error like... + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'exec'. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Invalid task 'ûDexec.args=ö3000': you must specify a valid lifecycle phas e, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginV ersion:goal [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Invalid task 'ûDexec.args=ö3000': you mu st specify a valid lifecycle phase, or a goal in the format plugin:goal or plugi nGroupId:pluginArtifactId:pluginVersion:goal at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor (DefaultLifecycleExecutor.java:1830) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListBy AggregationNeeds(DefaultLifecycleExecutor.java:462) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:175) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6 0) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.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) [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Jan 10 15:48:43 IST 2011 [INFO] Final Memory: 2M/3M [INFO] Please help.
Re: Help referencing profile properties/attributes...
Still not sure why you need deployment or test configurations in your applications You are not the first person to build an N-tiered web application with many servers. Why can you not put debugging levels and BaseURLs in JNDI? Those seem pretty simple things to deal with. You are not the first person to try to use/misuse profiles for this. I am not trying to be mean or disrespectful of your intentions, I am just trying point out some reasons why there is no answer to what you want to do. It is not a good way to do things and Maven is not designed to solve this problem. You are looking at Maven for the right reasons but Maven is not Ant. Maven is designed to make it easy to do the right thing and it make make it hard or impossible to do other things. I didn't write Maven but I had to deal with the same thing. We didn't get started out right either and had to change. I have also read dozens of long conversations here with people more determined than you to try to find a way to make Maven do what you want. You also have had advice from others here who are the best Maven experts in the world (committers to the project ) and you might have observed that they have not given you a solution. It is not because they are trying to annoy you or tease you. Ron On 20/01/2011 5:18 PM, Jeff wrote: I don't want to debate our architecture or processes since I have little to do with defining them, but its an N-tiered web application comprising from one to dozens of servers. Many of the tests are Selenium Integration tests on Windows clients hitting remote servers that are mostly Linux. We have dev and test instances that we hit during development. One of the key properties that changes is the baseURL used by selenium, as well as debugging levels. The integration test code is not currently part of the source for the application. The tests never run on the app servers directly (I've never seen anyone do that anyway...our build servers don't run the web app.), particularly the integration tests as they are client-based. We are running the tests from dev workstations for now but will eventually expand to running a subset of integration tests via Hudson. We are leveraging as much of Maven through the entire process as possible in order to maximize reuse, portability and integration moving forward. Anything else I can clarify? On Jan 20, 2011 2:24 PM, Ron Wheelerrwhee...@artifact-software.com wrote: - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Odd behaviour in dependency management with plugins
Hi,
I'm having some trouble with how maven resolves dependencies in my
project. The project has many sub-projects, and one of the
sub-projects does not build correctly when I build the whole project.
This problematic project is a WAR project which contains my app's web
services. In this project, I need two dependencies: one for the
project containing classes generated by wsimport, and an EJB project.
The pom has these relevant parts:
-- wsgen plugin
plugin
--groupIdorg.codehaus.mojo/groupId
--artifactIdjaxws-maven-plugin/artifactId
--version1.12/version
--...
--executions
execution
--idgenerate-wsdl/id
--phasepre-integration-test/phase
--goals
goalwsgen/goal
--/goals
/execution
--/executions
--dependencies
dependency
--groupId${project.groupId}/groupId
--artifactIdEJB-Project/artifactId
--version${project.version}/version
--typeejb/type
/dependency
dependency
--groupId${project.groupId}/groupId
--artifactIdWS-Classes/artifactId
--version${project.version}/version
--typejar/type
/dependency
--/dependencies
/plugin
...
/build
dependencies
dependency
--groupId${project.groupId}/groupId
--artifactIdEJB-Project/artifactId
--version${project.version}/version
--typeejb/type
--scopeprovided/scope
/dependency
dependency
--groupId${project.groupId}/groupId
--artifactIdWS-Classes/artifactId
--version${project.version}/version
--typejar/type
/dependency
/dependencies
If I build this WAR project alone, the build is successfull. However,
when I issue the build on the Big Project, it fails by not finding
some classes in the EJB project (which has scope compile for the
plugin but cannot go in the WEB-INF/lib dir of the WAR, so it has
provided scope out of the plugin).
If I change the EJB project's scope to compile, the build succeeds,
but then the EJB project and all of it's dependencies end up in the
lib directory of the WAR. This breaks stuff when I package them into
an EAR, though.
Is there something I'm overlooking? What should I do?
TIA,
--
Khristian
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
maven-release-plugin
I have the following problem releasing a project with the maven-release-plugin (version 2.1). I’m using the maven release plugin in batch-mode. When using the release plugin in interactive mode, the plugin prompts for the new versions of snapshot dependencies. How can I populate the versions (development + release) of snapshot dependencies running the mvn release:prepare command in batch-mode? I 've tried something like this: call mvn -B release:prepare -Dtag=0.4.0 \ -DdevelopmentVersion=0.5.0-SNAPSHOT -DreleaseVersion=0.4.0 \ -Ddependency.org.sonatype.mavenbook:project-a.release=0.4.0 \ -Ddependency.org.sonatype.mavenbook:project-a.development=0.5.0-SNAPSHOT and the pom content of project-b is as follows: http://maven.40175.n5.nabble.com/file/n3351425/pom.xml pom.xml -- View this message in context: http://maven.40175.n5.nabble.com/maven-release-plugin-tp3351425p3351425.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Odd behaviour in dependency management with plugins
It smells like a reactor issue. Are you using Maven 2.x? Could you try Maven
3.0.2? Maven 3 has bug improvements (fixes) to reactor builds.
/Anders
On Fri, Jan 21, 2011 at 14:11, Smirnegger Steihnhoff
smirneg...@gmail.comwrote:
Hi,
I'm having some trouble with how maven resolves dependencies in my
project. The project has many sub-projects, and one of the
sub-projects does not build correctly when I build the whole project.
This problematic project is a WAR project which contains my app's web
services. In this project, I need two dependencies: one for the
project containing classes generated by wsimport, and an EJB project.
The pom has these relevant parts:
-- wsgen plugin
plugin
--groupIdorg.codehaus.mojo/groupId
--artifactIdjaxws-maven-plugin/artifactId
--version1.12/version
--...
--executions
execution
--idgenerate-wsdl/id
--phasepre-integration-test/phase
--goals
goalwsgen/goal
--/goals
/execution
--/executions
--dependencies
dependency
--groupId${project.groupId}/groupId
--artifactIdEJB-Project/artifactId
--version${project.version}/version
--typeejb/type
/dependency
dependency
--groupId${project.groupId}/groupId
--artifactIdWS-Classes/artifactId
--version${project.version}/version
--typejar/type
/dependency
--/dependencies
/plugin
...
/build
dependencies
dependency
--groupId${project.groupId}/groupId
--artifactIdEJB-Project/artifactId
--version${project.version}/version
--typeejb/type
--scopeprovided/scope
/dependency
dependency
--groupId${project.groupId}/groupId
--artifactIdWS-Classes/artifactId
--version${project.version}/version
--typejar/type
/dependency
/dependencies
If I build this WAR project alone, the build is successfull. However,
when I issue the build on the Big Project, it fails by not finding
some classes in the EJB project (which has scope compile for the
plugin but cannot go in the WEB-INF/lib dir of the WAR, so it has
provided scope out of the plugin).
If I change the EJB project's scope to compile, the build succeeds,
but then the EJB project and all of it's dependencies end up in the
lib directory of the WAR. This breaks stuff when I package them into
an EAR, though.
Is there something I'm overlooking? What should I do?
TIA,
--
Khristian
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-release-plugin
I think what you want is something like: mvn -B release:prepare -Dtag=0.4.0 -DdevelopmentVersion=0.5.0-SNAPSHOT -DreleaseVersion=0.4.0 -DautoVersionSubmodules=true autoVersionSubmodules could be configured in your pom (in the pluginManagement section), so that you don't have to specify it each time (if you always want all modules to have the same version). /Anders On Fri, Jan 21, 2011 at 14:44, milewc claudia.mi...@bmw.de wrote: I have the following problem releasing a project with the maven-release-plugin (version 2.1). I’m using the maven release plugin in batch-mode. When using the release plugin in interactive mode, the plugin prompts for the new versions of snapshot dependencies. How can I populate the versions (development + release) of snapshot dependencies running the mvn release:prepare command in batch-mode? I 've tried something like this: call mvn -B release:prepare -Dtag=0.4.0 \ -DdevelopmentVersion=0.5.0-SNAPSHOT -DreleaseVersion=0.4.0 \ -Ddependency.org.sonatype.mavenbook:project-a.release=0.4.0 \ -Ddependency.org.sonatype.mavenbook:project-a.development=0.5.0-SNAPSHOT and the pom content of project-b is as follows: http://maven.40175.n5.nabble.com/file/n3351425/pom.xml pom.xml -- View this message in context: http://maven.40175.n5.nabble.com/maven-release-plugin-tp3351425p3351425.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-release-plugin
No, it's a very simple project structure without any submodules. The problem are not any submodules, the problem is, that the dependency to project-a has a snaphot version at release time and needs to be updated to a release version. -- View this message in context: http://maven.40175.n5.nabble.com/maven-release-plugin-update-dependency-snapshots-to-versions-in-batch-mode-tp3351425p3351456.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Odd behaviour in dependency management with plugins
Hi,
Smirnegger Steihnhoff wrote:
Hi,
I'm having some trouble with how maven resolves dependencies in my
project. The project has many sub-projects, and one of the
sub-projects does not build correctly when I build the whole project.
This problematic project is a WAR project which contains my app's web
services. In this project, I need two dependencies: one for the
project containing classes generated by wsimport, and an EJB project.
The pom has these relevant parts:
-- wsgen plugin
plugin
--groupIdorg.codehaus.mojo/groupId
--artifactIdjaxws-maven-plugin/artifactId
--version1.12/version
--...
--executions
execution
--idgenerate-wsdl/id
--phasepre-integration-test/phase
--goals
goalwsgen/goal
--/goals
/execution
--/executions
--dependencies
dependency
--groupId${project.groupId}/groupId
--artifactIdEJB-Project/artifactId
--version${project.version}/version
--typeejb/type
/dependency
dependency
--groupId${project.groupId}/groupId
--artifactIdWS-Classes/artifactId
--version${project.version}/version
--typejar/type
/dependency
--/dependencies
/plugin
...
/build
dependencies
dependency
--groupId${project.groupId}/groupId
--artifactIdEJB-Project/artifactId
--version${project.version}/version
--typeejb/type
--scopeprovided/scope
/dependency
dependency
--groupId${project.groupId}/groupId
--artifactIdWS-Classes/artifactId
--version${project.version}/version
--typejar/type
/dependency
/dependencies
If I build this WAR project alone, the build is successfull. However,
when I issue the build on the Big Project, it fails by not finding
some classes in the EJB project (which has scope compile for the
plugin but cannot go in the WEB-INF/lib dir of the WAR, so it has
provided scope out of the plugin).
If I change the EJB project's scope to compile, the build succeeds,
but then the EJB project and all of it's dependencies end up in the
lib directory of the WAR. This breaks stuff when I package them into
an EAR, though.
Is there something I'm overlooking? What should I do?
I guess this is normal ;-)
Remember, that Maven loads every plugin (with its classpath) only once. I
simply suppose that you use the jaxws-plugin in your big project elsewhere
first, where those two deps are not declared ... voilá!
The real culprit though is the wsgen-plugin, since it does not add artifacts
of scope priovided to its classpath used for compilation. This violates the
POM definition and I'd consider this as bug.
Unfortunately this does not help you. What I do is generating the WSDL in
the WebService project itself and add those stuff as an attached artifact
with classifier wsdl. That way you don't have the need at all to generate
the WSDL later on somewhere, because you can refer it as dependency.
- Jörg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Odd behaviour in dependency management with plugins
Or switch to Maven 3. :-)
/Anders
On Fri, Jan 21, 2011 at 15:11, Jörg Schaible joerg.schai...@gmx.de wrote:
Hi,
Smirnegger Steihnhoff wrote:
Hi,
I'm having some trouble with how maven resolves dependencies in my
project. The project has many sub-projects, and one of the
sub-projects does not build correctly when I build the whole project.
This problematic project is a WAR project which contains my app's web
services. In this project, I need two dependencies: one for the
project containing classes generated by wsimport, and an EJB project.
The pom has these relevant parts:
-- wsgen plugin
plugin
--groupIdorg.codehaus.mojo/groupId
--artifactIdjaxws-maven-plugin/artifactId
--version1.12/version
--...
--executions
execution
--idgenerate-wsdl/id
--phasepre-integration-test/phase
--goals
goalwsgen/goal
--/goals
/execution
--/executions
--dependencies
dependency
--groupId${project.groupId}/groupId
--artifactIdEJB-Project/artifactId
--version${project.version}/version
--typeejb/type
/dependency
dependency
--groupId${project.groupId}/groupId
--artifactIdWS-Classes/artifactId
--version${project.version}/version
--typejar/type
/dependency
--/dependencies
/plugin
...
/build
dependencies
dependency
--groupId${project.groupId}/groupId
--artifactIdEJB-Project/artifactId
--version${project.version}/version
--typeejb/type
--scopeprovided/scope
/dependency
dependency
--groupId${project.groupId}/groupId
--artifactIdWS-Classes/artifactId
--version${project.version}/version
--typejar/type
/dependency
/dependencies
If I build this WAR project alone, the build is successfull. However,
when I issue the build on the Big Project, it fails by not finding
some classes in the EJB project (which has scope compile for the
plugin but cannot go in the WEB-INF/lib dir of the WAR, so it has
provided scope out of the plugin).
If I change the EJB project's scope to compile, the build succeeds,
but then the EJB project and all of it's dependencies end up in the
lib directory of the WAR. This breaks stuff when I package them into
an EAR, though.
Is there something I'm overlooking? What should I do?
I guess this is normal ;-)
Remember, that Maven loads every plugin (with its classpath) only once. I
simply suppose that you use the jaxws-plugin in your big project elsewhere
first, where those two deps are not declared ... voilá!
The real culprit though is the wsgen-plugin, since it does not add
artifacts
of scope priovided to its classpath used for compilation. This violates the
POM definition and I'd consider this as bug.
Unfortunately this does not help you. What I do is generating the WSDL in
the WebService project itself and add those stuff as an attached artifact
with classifier wsdl. That way you don't have the need at all to generate
the WSDL later on somewhere, because you can refer it as dependency.
- Jörg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-release-plugin
are not any submodules, the problem is, that the dependency to project-a has a snaphot version at release time and needs to be updated to a release version. versions-maven-plugin (codehaus) may be worth taking a look at to help with versioning issues. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Odd behaviour in dependency management with plugins
Anders Hammar wrote: Or switch to Maven 3. :-) We can build our tree with M2 and M3, so I have no proof yet :D - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-site-plugin 3.0-beta-3 and maven-checkstyle-plugin 2.6 gives Unable to instantiate PackageHtml
Hi I am using maven 3.0.2 and I get an error like this: "[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site (default-site) on project commons: Error during page generation: Error rendering Maven report: Failed during checkstyle configuration: cannot initialize module PackageHtml - Unable to instantiate PackageHtml: Unable to instantiate PackageHtmlCheck - [Help 1]" when doing 'mvn site'. I have maven-site-plugin 3.0-beta-3 and maven-checkstyle-plugin 2.6 There seems to have been some issue around PackageHtmlCheck, see http://jira.codehaus.org/browse/SONAR-1545?page=com.atlassian.jira.plugin.system.issuetabpanels%3Achangehistory-tabpanel But I can not really understand what the trick is. And yes I have my own rules. Basically it is similar to the Sun one. Sure I can remove module name="PackageHtml"/ but then I get "Failed during checkstyle configuration: cannot initialize module TreeWalker - TreeWalker is not allowed as a parent of FileLength - [Help 1]" Thanks Lucas -- Lucas Persson | Principal Member of Technical Staff Phone: +4684773644 | | | Mobile: +46730946656 Oracle Communications Platform ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm Oracle Svenska AB, Kronborgsgrnd 17, S-164 28 KISTA, reg.no. 556254-6746 Oracle is committed to developing practices and products that help protect the environment
Re: maven-site-plugin 3.0-beta-3 and maven-checkstyle-plugin 2.6 gives Unable to instantiate PackageHtml
With new checkstyle, 5.x, some of the old checkstyle checks have been replaced with new ones. See checkstyle release notes http://checkstyle.sourceforge.net/releasenotes.html for details on new checks. Replace them accordingly in your custom checkstyle configuration. Regards, Stevo. On Fri, Jan 21, 2011 at 5:15 PM, Lucas Persson lucas.pers...@oracle.comwrote: Hi I am using maven 3.0.2 and I get an error like this: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site (default-site) on project commons: Error during page generation: Error rendering Maven report: Failed during checkstyle configuration: cannot initialize module PackageHtml - Unable to instantiate PackageHtml: Unable to instantiate PackageHtmlCheck - [Help 1] when doing 'mvn site'. I have maven-site-plugin 3.0-beta-3 and maven-checkstyle-plugin 2.6 There seems to have been some issue around PackageHtmlCheck, see http://jira.codehaus.org/browse/SONAR-1545?page=com.atlassian.jira.plugin.system.issuetabpanels%3Achangehistory-tabpanel But I can not really understand what the trick is. And yes I have my own rules. Basically it is similar to the Sun one. Sure I can remove module name=PackageHtml/ but then I get Failed during checkstyle configuration: cannot initialize module TreeWalker - TreeWalker is not allowed as a parent of FileLength - [Help 1] Thanks Lucas -- [image: Oracle] http://www.oracle.com Lucas Persson | Principal Member of Technical Staff Phone: +4684773644 tel:+4684773644 | | | Mobile: +46730946656tel:+46730946656 Oracle Communications Platform ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746 [image: Green Oracle] http://www.oracle.com/commitment Oracle is committed to developing practices and products that help protect the environment
Maven project packaging
Hey guys, We have a large multi-module maven project. We need to ship it to a remote site where the client has no internet access. What is the easiest way to package our source code and all dependencies/plugins etc.? Thanks.
Re: Dependencies get unpacked over and over again
Ok, I'll try to see if I can figure it out :) On Wed, Jan 19, 2011 at 2:20 PM, Anders Hammar and...@hammar.net wrote: Briefly looking through the comments it looks like an integration test is missing for the patch to be accepted. Can you provide one? /Anders On Wed, Jan 19, 2011 at 21:59, Phillip Hellewell ssh...@gmail.com wrote: Has anyone else run into this? I run into it all the time. It appears to be because unpack-dependencies is not updating the timestamp on the marker files like it should. I found this bug which seems to be exactly my problem: http://jira.codehaus.org/browse/MDEP-225 I contacted the developer about it but got no response. What should I do now? Phillip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
pdf plugin broken in maven3?
Is the PDF plugin expected to work in Maven3? I see this bug report [http://jira.codehaus.org/browse/MPDF-41], but it doesn't look like there has been a new release [or even that the issue has been resolved]. Does anyone know the timing for a new release? Thanks Andrew # mvn -v Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500) Java version: 1.6.0_20, vendor: Sun Microsystems Inc. Java home: /usr/java/jdk1.6.0_20/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 2.6.9-42.elsmp, arch: i386, family: unix # mvn pdf:pdf ... [INFO] --- maven-pdf-plugin:1.1:pdf (default-cli) @ test --- [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2.750s [INFO] Finished at: Fri Jan 21 11:58:52 EST 2011 [INFO] Final Memory: 11M/110M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-pdf-plugin:1.1:pdf (default-cli) on project test: Execution default-cli of goal org.apache.maven.plugins:maven-pdf-plugin:1.1:pdf failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pdf-plugin:1.1:pdf: java.lang.NoSuchMethodError: org.apache.maven.plugin.PluginManager.verifyReportPlugin(Lorg/apache/maven/model/ReportPlugin;Lorg/apache/maven/project/MavenProject;Lorg/apache/maven/execution/MavenSession;)Lorg/apache/maven/plugin/descriptor/PluginDescriptor; - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Help referencing profile properties/attributes...
Either I'm not explaining things well enough or you are assuming something
different and I think that is the confusion ... I am not building or using
the application projects or source code. I'm not dealing with application
deployment, they are already deployed via other means and processes that I
am not directly plugged into.
My maven project is currently a set of Selenium-based, TestNG-driven,
stand-alone integration tests for 3 different applications, one that is
MediaWiki-based, one built on vBulletin and one that is a custom J2EE-based
web service. These tests run on client machines.
Profiles are curently working great for me...I merely hoped to find a way
to simplify them a bit.
I believe I am using maven exactly as stated in the maven profile intro at
http://maven.apache.org/guides/introduction/introduction-to-profiles.html where
it states:
Profiles are specified using a subset of the elements available in the POM
itself (plus one extra section), and are triggered in any of a variety of
ways. *They modify the POM at build time*, and are meant to be used in
*complementary
sets* to give *equivalent-but-different parameters for a set of target
environments* (providing, for example, the *path of the appserver root* in
the development, testing, and production environments).
this is exactly what I'm trying to do for my project, target different
appserver roots for the different dev, test and prod environments for the 3
different applications I test, independently of the application build
process.
The test environment information is all *stored in property files* outside
of the source code. The tests are generic in that regard. The maven
profiles simply help determine which properties file the test uses/loads via
a call to getResourceAsStream(profileID+.properties). I don't see
how this is anti-Maven.
So for what I am doing, JNDI seems like overkill to set the application root
or affect run-time debugging levels.
Even if I do use JNDI, how does JNDI solve the problem of determining which
environment/settings are used at run-time? Seems like I'd still need
profiles or something to tell my tests at run-time which environment to use,
regardless of whether they are stored in property files or in some database
somewhere.
As mentioned, the profiles are working great for me. I just hoped I could
simplify the profile a bit to eliminate the duplicate, hard-coded config
value in each profile by doing something like *config${profile.id
}/config* instead of *configstaging/config *or *configdev/config.*
As an alternative to setting a system property via the surefire plugin, I
also wondered if there is any other way to communicate to my tests which
profile(s) is(are) loaded?
On Thu, Jan 20, 2011 at 4:27 PM, Ron Wheeler rwhee...@artifact-software.com
wrote:
designed
--
Jeff Vincent
predato...@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
Re: Artifacts with License Notice Distribution Requirements and Maven the build tool
Many artifacts assembled via maven (again, the tool and not the repository) require that a license notice accompany the downloaded artifact(s). Such licenses should be contained within the jar files themselves, and this should be sufficient from a legal standpoint (IANAL). In this manner, it is wholly impossible to access the jar file without receiving the license notice. (a) Does maven allow this today? (And, please, don't mention any maven license plugins -- it must be part of the box standard build) There has been some discussion of this a few times on the Users list and on the Dev list, but I'm unaware of any specific functionality that exists which addresses your concerns. As an aside, you must not really understand how Maven works if you say this can't be part of a plugin -- nearly everything in Maven exists as a plugin. You can't even compile a project with what is distributed as Maven version 3.0.2 downloadable from the website. (b) If not possible, don't you agree that this is the real requirement? Who's requirement?? Yours? If so, feel free to alter the Maven core code and submit a contribution that may or may not be accepted for inclusion in a future Maven release. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: License collection
I'm trying to automate licensing collection for my product. What I want is simple: collect (i.e. download) all licenses of my dependencies and store them in a folder. This is not as simple as you may think. How exactly do you plan to do this? Where will you download all licenses for your dependencies from? Hint: they are not necessarily stored in Central along with your jars -- this is pretty rare from what I've seen, unless they are packaged along with the jar file (which is also not particularly common). Does anyone know if there's a plugin that does what I'm trying to accomplish? I've heard about license-maven-plugin ( http://mojo.codehaus.org/license-maven-plugin/ ) but I couldn't even download it. This plugin is in the Sandbox, so you can't simply download and use it. Follow the directions on the Mojo site: http://mojo.codehaus.org/using-sandbox-plugins.html Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: License collection
Maybe you'll find these plugins useful: http://code.google.com/p/maven-license-plugin/ http://community.jboss.org/wiki/Howtoaddlicenseinfotoprojects https://wiki.jasig.org/display/LIC/maven-notice-plugin Regards, Stevo. On Fri, Jan 21, 2011 at 7:30 PM, Wayne Fay wayne...@gmail.com wrote: I'm trying to automate licensing collection for my product. What I want is simple: collect (i.e. download) all licenses of my dependencies and store them in a folder. This is not as simple as you may think. How exactly do you plan to do this? Where will you download all licenses for your dependencies from? Hint: they are not necessarily stored in Central along with your jars -- this is pretty rare from what I've seen, unless they are packaged along with the jar file (which is also not particularly common). Does anyone know if there's a plugin that does what I'm trying to accomplish? I've heard about license-maven-plugin ( http://mojo.codehaus.org/license-maven-plugin/ ) but I couldn't even download it. This plugin is in the Sandbox, so you can't simply download and use it. Follow the directions on the Mojo site: http://mojo.codehaus.org/using-sandbox-plugins.html Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven project packaging
Hi CassUser, On Fri, Jan 21, 2011 at 11:55 AM, CassUser CassUser cassu...@gmail.com wrote: We have a large multi-module maven project. We need to ship it to a remote site where the client has no internet access. What is the easiest way to package our source code and all dependencies/plugins etc.? The maven-assembly-plugin would be the best fit. http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: License collection
As Wayne mentioned, most of the modules contain an url to a license rather than have it checked in. Perhaps you just need the license report instead? The dependencies report of the mpir plugin has had a license section for quite some time, I use it all the time. See e.g. the dependency report of the mpir plugin itself: http://maven.apache.org/plugins/maven-project-info-reports-plugin/dependencies.html. Kalle On Fri, Jan 21, 2011 at 9:30 AM, Rui Vilão rpvi...@gmail.com wrote: Hi all, I'm trying to automate licensing collection for my product. What I want is simple: collect (i.e. download) all licenses of my dependencies and store them in a folder. Does anyone know if there's a plugin that does what I'm trying to accomplish? I've heard about license-maven-plugin ( http://mojo.codehaus.org/license-maven-plugin/ ) but I couldn't even download it. Thanks in advance, Rui - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven project packaging
On 21/01/2011 11:55 AM, CassUser CassUser wrote: Hey guys, We have a large multi-module maven project. We need to ship it to a remote site where the client has no internet access. What is the easiest way to package our source code and all dependencies/plugins etc.? Thanks. Give them a copy of your Nexus repo. Give them a copy of your project source files(Source Repo or a zip of your Eclipse workspace with all your projects on-line). Ron - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Help referencing profile properties/attributes...
On 21/01/2011 1:19 PM, Jeff wrote:
Either I'm not explaining things well enough or you are assuming something
different and I think that is the confusion ... I am not building or using
the application projects or source code. I'm not dealing with application
deployment, they are already deployed via other means and processes that I
am not directly plugged into.
My maven project is currently a set of Selenium-based, TestNG-driven,
stand-alone integration tests for 3 different applications, one that is
MediaWiki-based, one built on vBulletin and one that is a custom J2EE-based
web service. These tests run on client machines.
Profiles are curently working great for me...I merely hoped to find a way
to simplify them a bit.
I believe I am using maven exactly as stated in the maven profile intro at
http://maven.apache.org/guides/introduction/introduction-to-profiles.html where
it states:
Profiles are specified using a subset of the elements available in the POM
itself (plus one extra section), and are triggered in any of a variety of
ways. *They modify the POM at build time*, and are meant to be used in
*complementary
sets* to give *equivalent-but-different parameters for a set of target
environments* (providing, for example, the *path of the appserver root* in
the development, testing, and production environments).
this is exactly what I'm trying to do for my project, target different
appserver roots for the different dev, test and prod environments for the 3
different applications I test, independently of the application build
process.
The test environment information is all *stored in property files* outside
of the source code. The tests are generic in that regard. The maven
profiles simply help determine which properties file the test uses/loads via
a call to getResourceAsStream(profileID+.properties). I don't see
how this is anti-Maven.
So for what I am doing, JNDI seems like overkill to set the application root
or affect run-time debugging levels.
Even if I do use JNDI, how does JNDI solve the problem of determining which
environment/settings are used at run-time? Seems like I'd still need
profiles or something to tell my tests at run-time which environment to use,
regardless of whether they are stored in property files or in some database
somewhere.
As mentioned, the profiles are working great for me. I just hoped I could
simplify the profile a bit to eliminate the duplicate, hard-coded config
value in each profile by doing something like *config${profile.id
}/config* instead of *configstaging/config *or *configdev/config.*
As an alternative to setting a system property via the surefire plugin, I
also wondered if there is any other way to communicate to my tests which
profile(s) is(are) loaded?
I can't answer that but you certainly have the right guys in the forum
who can tell you for sure.
Good luck
Ron
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: pdf plugin broken in maven3?
I haven't actually tried with maven 3 but as I understand from Olivier's comments at MPDF-41, it should work apart from the reports inclusion. I have just re-deployed the current 1.2-SNAPSHOT, if you can test it, I will attempt a release next week (I was planning to release it during the Xmas holydays but Santa Claus brought me another toy...) Thanks, -Lukas Andrew Geery wrote: Is the PDF plugin expected to work in Maven3? I see this bug report [http://jira.codehaus.org/browse/MPDF-41], but it doesn't look like there has been a new release [or even that the issue has been resolved]. Does anyone know the timing for a new release? Thanks Andrew # mvn -v Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500) Java version: 1.6.0_20, vendor: Sun Microsystems Inc. Java home: /usr/java/jdk1.6.0_20/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 2.6.9-42.elsmp, arch: i386, family: unix # mvn pdf:pdf ... [INFO] --- maven-pdf-plugin:1.1:pdf (default-cli) @ test --- [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2.750s [INFO] Finished at: Fri Jan 21 11:58:52 EST 2011 [INFO] Final Memory: 11M/110M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-pdf-plugin:1.1:pdf (default-cli) on project test: Execution default-cli of goal org.apache.maven.plugins:maven-pdf-plugin:1.1:pdf failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pdf-plugin:1.1:pdf: java.lang.NoSuchMethodError: org.apache.maven.plugin.PluginManager.verifyReportPlugin(Lorg/apache/maven/model/ReportPlugin;Lorg/apache/maven/project/MavenProject;Lorg/apache/maven/execution/MavenSession;)Lorg/apache/maven/plugin/descriptor/PluginDescriptor; - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Help referencing profile properties/attributes...
This sounds very simmilar to the setup we have here -- everything was
already in property files. I found the key to simplifying things is to have
and enforce a standardized naming convention. Since that was already in
place when I looked into maven, picking the correct property file was
trivial:
build
filters
filter${PomRoot}/${envType}Config.properties/filter
/filters
..
/build
then I have a few properties:
properties
envTypedev/envType !-- Default Environment value --
PomRootC:\MavenProject\POC/PomRoot
/properties
the only part I dont like is having to add the PomRoot property, but thats
required if you ever build projects not at the top level -- otherwise it
cant find the properties file. (if anyone knows a better solution - please
speak up)
when you want to build for a different environment:
mvn install -DenvType=QA
mvn install -DenvType=StressTest
I find that very simple to use.
On Fri, Jan 21, 2011 at 11:39 AM, Ron Wheeler
rwhee...@artifact-software.com wrote:
On 21/01/2011 1:19 PM, Jeff wrote:
Either I'm not explaining things well enough or you are assuming something
different and I think that is the confusion ... I am not building or using
the application projects or source code. I'm not dealing with application
deployment, they are already deployed via other means and processes that I
am not directly plugged into.
My maven project is currently a set of Selenium-based, TestNG-driven,
stand-alone integration tests for 3 different applications, one that is
MediaWiki-based, one built on vBulletin and one that is a custom
J2EE-based
web service. These tests run on client machines.
Profiles are curently working great for me...I merely hoped to find a way
to simplify them a bit.
I believe I am using maven exactly as stated in the maven profile intro at
http://maven.apache.org/guides/introduction/introduction-to-profiles.htmlwhere
it states:
Profiles are specified using a subset of the elements available in the
POM
itself (plus one extra section), and are triggered in any of a variety of
ways. *They modify the POM at build time*, and are meant to be used in
*complementary
sets* to give *equivalent-but-different parameters for a set of target
environments* (providing, for example, the *path of the appserver root* in
the development, testing, and production environments).
this is exactly what I'm trying to do for my project, target different
appserver roots for the different dev, test and prod environments for the
3
different applications I test, independently of the application build
process.
The test environment information is all *stored in property files* outside
of the source code. The tests are generic in that regard. The maven
profiles simply help determine which properties file the test uses/loads
via
a call to getResourceAsStream(profileID+.properties). I don't see
how this is anti-Maven.
So for what I am doing, JNDI seems like overkill to set the application
root
or affect run-time debugging levels.
Even if I do use JNDI, how does JNDI solve the problem of determining
which
environment/settings are used at run-time? Seems like I'd still need
profiles or something to tell my tests at run-time which environment to
use,
regardless of whether they are stored in property files or in some
database somewhere.
As mentioned, the profiles are working great for me. I just hoped I could
simplify the profile a bit to eliminate the duplicate, hard-coded config
value in each profile by doing something like *config${profile.id
}/config* instead of *configstaging/config *or
*configdev/config.*
As an alternative to setting a system property via the surefire plugin, I
also wondered if there is any other way to communicate to my tests which
profile(s) is(are) loaded?
I can't answer that but you certainly have the right guys in the forum
who can tell you for sure.
Good luck
Ron
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Enum mojo params
Can mojo parameters be enums? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Enum mojo params
Benson Margulies wrote: Can mojo parameters be enums? One of the smaller improvements that went into Maven 3: http://jira.codehaus.org/browse/MNG-4292 Benjamin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Adding systemProperty to parent plugin definition
Is there a way to extend a parent pom's plugin configuration? I have a situation where the parent pom configures the surefire plugin a great deal. I want to add one more systemProperty but I don't have to copy the whole configuration of that plugin down because 1. I feel that is against the concept of having the configuration in the parent pom as if more things have to be changed, my override will not be aware of those changes. 2. It's got a large amount of configurations and I don't want to replicate all of it. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
: Archetype multi module
Hello,
I'm developing a multi module archetype. But i would like to offer to users
of my archetypes a option to choose which modules wants use, on runtime.
For example, when the user execute:
mvn archetype:generate
I could ask to user whats modules he wants use.
I'm trying do it modifying my archetype multi module, making modifications
on this files:
archetype\src\main\resources\archetype-resources\pom.xml
...
#if($useWebModule == true)
moduleweb/module
#end
...
archetype\src\main\resources\META-INF\maven\archetype-metadata.xml
...
requiredProperty key=useWebModule /
...
#if($useWebModule == true)
module id=${rootArtifactId}.web dir=web name=${rootArtifactId}.web
#end
...
What do you think about? Why this way does not work.
Thanks,
Marcus Vinicius A. Silva
Re: Adding systemProperty to parent plugin definition
Tim wrote: Is there a way to extend a parent pom's plugin configuration? I have a situation where the parent pom configures the surefire plugin a great deal. I want to add one more systemProperty but I don't have to copy the whole configuration of that plugin down because Potentially helpful resources: http://jira.codehaus.org/browse/SUREFIRE-548 http://www.sonatype.com/people/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects/ Benjamin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Adding systemProperty to parent plugin definition
Thanks! Wow that really should be documented in maven FAQs. :P On Fri, Jan 21, 2011 at 5:55 PM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Tim wrote: Is there a way to extend a parent pom's plugin configuration? I have a situation where the parent pom configures the surefire plugin a great deal. I want to add one more systemProperty but I don't have to copy the whole configuration of that plugin down because Potentially helpful resources: http://jira.codehaus.org/browse/SUREFIRE-548 http://www.sonatype.com/people/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects/ Benjamin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AUTO: Andreas Schlosser is out of the office. (returning 02/02/2011)
I am out of the office until 02/02/2011. This message is not forwarded. I will respond to your message when I return. In urgent cases please contact mcommerce-supp...@sybase.com Regards Andreas Schlosser Note: This is an automated response to your message Adding systemProperty to parent plugin definition sent on 1/21/2011 11:47:38 PM. This is the only notification you will receive while this person is away. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: License collection
Hi, Thank you all for replying. As Stevo mentioned I'm using maven-license-plugin to generate headers as well. But I need to include the licenses of the dependencies I'm using in order to distribute my software. I believe it would be great if developers include the license in the license tag in order for plugins to collect and download them. The behavior would be something like the described here: http://mojo.codehaus.org/license-maven-plugin/ like Wayne mentioned. As far as I can see there's no simple approach to do this, so I believe I will use the report plugin and collect them myself with my bare hands :p Anyway, thank you for your time! -- Rui On Fri, Jan 21, 2011 at 7:26 PM, Kalle Korhonen kalle.o.korho...@gmail.comwrote: As Wayne mentioned, most of the modules contain an url to a license rather than have it checked in. Perhaps you just need the license report instead? The dependencies report of the mpir plugin has had a license section for quite some time, I use it all the time. See e.g. the dependency report of the mpir plugin itself: http://maven.apache.org/plugins/maven-project-info-reports-plugin/dependencies.html . Kalle On Fri, Jan 21, 2011 at 9:30 AM, Rui Vilão rpvi...@gmail.com wrote: Hi all, I'm trying to automate licensing collection for my product. What I want is simple: collect (i.e. download) all licenses of my dependencies and store them in a folder. Does anyone know if there's a plugin that does what I'm trying to accomplish? I've heard about license-maven-plugin ( http://mojo.codehaus.org/license-maven-plugin/ ) but I couldn't even download it. Thanks in advance, Rui - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
