RE: Using Maven on a very large integration project - how far can Maven go?
dependency groupIdplexus/groupId artifactIdplexus-runtime/artifactId version1.0/version typezip/type /dependency I think this would be very useful for what I am planning to do with Maven. I like the concept. Once you finish testing it, I'd be very interested in testing it out on my project. Michael -- This E-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return E-mail. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Extending project and inheriting project.properties
I have subprojects with project.xml extending a base project.xml
project
extend${basedir}/../../common/project.xml/extend
But properties defined in the superproject' project.properties are not
available to subprojects.
The only way to do this was define properties in the base maven.xml with
j:set
j:set var=maven.compile.executablejikes/j:set
But then they can't be overriden by the project.properties in the
subprojects. I think that it can be solved with a j:if for each property but
is there an easy way?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Simian = OutOfMemory
Actually, I have encountered the same problem when I used Maven-1.0-rc1. I have updated the java VM memory to 3000xs, but still does not work. And finally I cancelled the simian report generation from the project.xml. Best, Beiting. -Message d'origine- De : Sri Sankaran [mailto:[EMAIL PROTECTED] Envoyé : vendredi 9 avril 2004 03:45 À : Maven Users List Objet : Simian = OutOfMemory Using: Maven 1.0 rc2 OS: Windows XP Professional I am unable to complete the generation of a multiproject:site due to an OutOfMemoryError Everytime attempt to correct this error has failed and each time while Maven is executing the simian plugin report (Hence the correlation on the subject line). Handing Maven all the memory I have available (via MAVEN_OPTS) has proved of no avail. Here's where the story gets bizarre. When pushing up the memory didn't help I decided to disable simian. However no matter *how* I deregister the report it is quite persistent and runs! I have tried to deregister via * as a preGoal to site:generrate * as a postGoal to xdoc:register-reports * as a postGoal to maven-simian-plugin:register (this I thought would be the clincher!) I still can't shake loose of this monkey :) As a last ditch I fiddled with the maven.simian.include property and set it to some bogus file pattern. That leads to some other unrelated error. My questions are: * Is there a known problem with Simian with rc2? I know of one other report (http://marc.theaimsgroup.com/?l=turbine-maven-userm=108055397222466w=2). If http://marc.theaimsgroup.com/?l=turbine-maven-userm=108055397222466w=2). If so is there a known workaround * How can I find disable the running of Simian Thanks Sri - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to configure ANT_HOME for ant task run within Jelly?
I'm trying to run an ant task in a separate ant file from a maven goal, but the ant task doesn't work unless it's run with ant 1.6 using a specific set of libraries for running beanshell scripts. My goal is defined with an ant call like the following: goal name=checkout ant:ant antFile=build.xml target=build_dependancies/ /goal And the specific error I get is that the script task cannot be created: Could not create task or type of type: script. Ant could not find the task or a class this task relies upon. This is common and has a number of causes; the usual solutions are to read the manual pages then download and install needed JAR files, or fix the build file: - You have misspelt 'script'. Fix: check your spelling. - The task needs an external JAR file to execute and this is not found at the right place in the classpath. Fix: check the documentation for dependencies. Fix: declare the task. - The task is an Ant optional task and optional.jar is absent Fix: look for optional.jar in ANT_HOME/lib, download if needed - The task was not built into optional.jar as dependent libraries were not found at build time. Fix: look in the JAR to verify, then rebuild with the needed libraries, or download a release version from apache.org - The build file was written for a later version of Ant Fix: upgrade to at least the latest release version of Ant - The task is not an Ant core or optional task and needs to be declared using taskdef. Remember that for JAR files to be visible to Ant tasks implemented in ANT_HOME/lib, the files must be in the same directory or on the classpath Thanks Jason Williams *** The contents of this communication are intended only for the addressee and may contain confidential and/or privileged material. If you are not the intended recipient, please do not read, copy, use or disclose this communication and notify the sender. Opinions, conclusions and other information in this communication that do not relate to the official business of my company shall be understood as neither given nor endorsed by it. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Default/bootstrap Classpath
Hi, I am new Maven user. So please excuse me if this is a very naive/dump question: I have created a small project which refers to Xerces classes and in the project.xml I have not specified the xerces.jar as the dependency and when I do a jar:jar goal it compiles and creates a jar with my classes. So, I am assuming that there is a certain default classpath which maven has - Can someone throw some light on this. Thanks, --Venkat. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Default/bootstrap Classpath
If you want to look for yourself, you can find the path setup in the
$MAVEN_HOME/bin/{maven.bat,maven} scripts. These basically setup the
classpath to be $MAVEN_HOME/lib and the endorsed classpath to be
$MAVEN_HOME/lib/endorsed.
If you look at the endorsed classpath dir, you should find a version of
xerces in there, I think.
Cheers,
John
On Fri, 2004-04-09 at 11:38, Sonnathi, Venkat wrote:
Hi,
I am new Maven user. So please excuse me if this is a very naive/dump
question:
I have created a small project which refers to Xerces classes and in the
project.xml I have not specified the xerces.jar as the dependency and when I
do a jar:jar goal it compiles and creates a jar with my classes. So, I am
assuming that there is a certain default classpath which maven has - Can
someone throw some light on this.
Thanks,
--Venkat.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
John Casey
[EMAIL PROTECTED]
CommonJava Open Components Project
http://www.commonjava.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Stopping on unit test failures
Using: Maven 1.0-rc2 OS: Windows XP Professional Problem: Maven doesn't stop at the first unit test that fails I am finding that even though I have set maven.test.failure.ignore=false the build continues despite errors in running unit tests. What would cause this error? Sri
