I get an Cannot create virtual machine error when trying to Install maven

Hello,   I have follow the step for installation word for word and I still can install mavem. When I run the test mvn --version in the command prompt I get the following error:   Unrecognized option: - Could not create the Java virtual machine.   Does anyone know what this means? I have copied

custom goal or phase?

Hello, I'm a Maven newbie and I'm having some difficulties understanding some concepts, so I hope you can help me... In an Ant build.xml, I could create a target in which I could call tasks: target name=targetA task1 / task2 / /target I've read about the lifecycle concepts of Maven, and I

RE: Simpler way....

No, it's not. Have a look at the maven pom xsd and you'll see it's not possible. http://maven.apache.org/maven-v4_0_0.xsd If you use a good IDE (Eclipse, Netbeans ?), put this on the beginning of your pom.xml : project xmlns=http://maven.apache.org/POM/4.0.0;

Re: Simpler way....

On Fri, Jun 27, 2008 at 4:09 PM, Marvin Froeder [EMAIL PROTECTED] wrote: Now my question, is there any simpler way to do that? May be like this: plugin artifactIdmaven-source-plugin/artifactId goaljar/goal /plugin POM XML is pretty

Multiple Checkstyle Executions

Hi All, I was wondering whether anyone understands the checkstyle plugin / mojos enough to explain why the following configuration is executing the same checkstyle rules twice, rather than the 2 different configurations I have provided? plugin

Re: Simpler way....

Another question. There is no way to define a default goal for one plugin? Then, if one plugin is add to plugin list and nothing is specify it will run the goal XYZ. Will be more CoC =P VELO On Sun, Jun 29, 2008 at 10:49 AM, MATHUS Baptiste [EMAIL PROTECTED] wrote: No, it's not. Have a

annotations are not supported in -source 1.3

Hi, I've executed junit tests with Maven and get such error: 'annotations are not supported in -source 1.3 use -source 5 or higher to enable annotations @Before' Which source is meant here? How can I solve this? Thanks beforehand, regards, buters -- View this message in context:

Re: annotations are not supported in -source 1.3

Buters, Ahh, thats because annotations are 1.5 only. You might want to configure the source and target parameters of the compiler plugin in your build like the following: build plugins plugin artifactIdmaven-compiler-plugin/artifactId

Re: Maven WebSphere 6.1

Hi Jon, Not to my knowledge. I used the list that RSA V7 uses as the WebSphere Application Server v6.1 Runtime classpath container, so that is what RSA uses itself to compile against. Which from Maven's point of view, it should be all that we need. I've not run into issues

problem with clover

Thank you very much, James William. But I have a new problem. I want create Test Coverage report with clover plugin, but I get such error: [INFO] [clover:instrumentInternal] Clover Version 1.3.13, built on September 04 2006 loaded from:

Re: problem with clover

Buters, That is a known issue that has been fixed in the latest release of clover. Have a look at: http://confluence.atlassian.com/display/CLOVER/Clover-for-Maven+2+User's +Guide If this does not solve your problem please contact our support department. Thanks! James On Sun, 2008-06-29 at

No Jsp in the work directory after run mvn jetty:run-war?!

hi,all after mvn jetty:run-war , i found there is no on other file in work directory except a lib directory which contains many dependencies. Then i got the 404 NOT_FOUND error When i visit the url,any way to solve this problem? here is my coniguration: plugin

Manipulation of ibm-webservices-bnd.xmi

Hi All. I don't mind not having this file generated, but I do need to manipulate it. The issue arises with the name attribute of the routerModules element. It needs the name of the war file that hosts the router modules. ?xml version=1.0 encoding=UTF-8?

Sorry for my last mail,i can view other files after refresh the work directory!

but still got 404 NOT_FOUND error!_ oliver.lee 2008-06-30

Need to run process-resources phase in pom packaging

Hi all, I'm in the process of migrating a project from ant build to Maven. The packaging of project's artifacts involves creating nested zip files that are two levels deep. I use assembly descriptors to for zipping artifacts from the child modules. At each level of nesting, the zip files also

fatal dependency management flaw in maven?

I recently asked this list about segregating project dependencies based on scope type, i.e. for e.g., ensuring that maven only downloads test dependencies from one repository and other normal dependencies from another repository. I did not get an answer - which can only mean 1 of 3 things: 1. It