scm:bootstrap-project not working quite right.
Hello I have a multiproject project set up something like this: /root-project maven.xml project.xml project.properties /sub-projects /sub-project-one maven.xml project.xml project.properties /sub-project-two maven.xml project.xml project.properties etc.. The root's project.properties defines a couple of (system-dependent) properties (let's say, windows.jboss.home, solaris.jboss.home); a goal within its maven.xml then picks the right one (depending on the OS) and puts them into a third property (say, jboss.home). The sub-projects then use this third property. This all works fine (whether it be ideal or not I don't know. I inherited the layout and am unwilling to rearrange things without good reason). What I would like to do is to be able to use scm:bootstrap-project to check out the project and run the default goal. Here's where the problem lies, using both rc1 and rc2. The checkout happens normally, and the project begins building. It then reaches a part that depends on the property dynamically set at runtime -- jboss.home, and promptly fails. echoing the variable shows that it's blank. It gets set fine in the root maven.xml but goals in the subproject maven.xml can no longer see it. If I traverse to the checkout directory and run the same goal from there, it works fine; the jboss.home property gets correctly set and is accessible to the subprojects. It only seems to be when run from scm:boostrap-project that it doesn't seem visible. Does anyone know why this value isn't getting inherited properly when using scm:bootstrap-project? Should the project even work in the first place? I apologize in advance if I'm omitted any necessary details; I'm not really sure what else needs to be said. Peter *** This message contains information that may be privileged or confidential and is the property of Orbian Management Limited. It is intended solely for the named addressee(s) and may not be used or disclosed except for the purpose for which it has been sent. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you have received this message in error, please notify the sender immediately and delete the message and any attached documents. Any opinions, conclusions and other information expressed in this message are those of the individual sender and are not given or endorsed by Orbian unless otherwise clearly indicated. Orbian has scanned this e-mail for viruses but accepts no liability or responsibility for any onward transmission or use of emails and attachments having left the Orbian domain. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RC2 Torque Plugin
On Wednesday 24 March 2004 12:08, Joe Taylor wrote: RC2 doesn't seem to have the torque plugin. From earlier posts it looks like this has been migrated into the torque project but I cant find a download for it. Do i need to build this from CVS? or have i missed something else along the way?? see http://db.apache.org/torque/maven-howto.html#Installation you have to build the maven torque plugin from cvs regards, Joachim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Goal [java:compile] has no action definition
I am sorry... I meant to say attainGoal name=test:test/. So, to recap: Project structure Root | +-- sub-project-1 | +-- sub-project-2 Root's maven.xml: goal name=root_project:build-all maven:reactor .../ attainGoal name=test:test/ -- Causes the error /goal -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 23, 2004 9:35 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition IS this a real example? test:test/ doesn't exist. You must mean attainGoal name=test:test / If you run just java:compile on its own does it work? When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Wednesday, 24 March 2004 1:28 PM To: [EMAIL PROTECTED] Subject: Goal [java:compile] has no action definition Using : Maven 1.0 rc2 OS: Windows XP Professional At the end of a reactor build I invoke test:test to run integration tests on my entire project. The entire reactor build runs successfully. However, the call to test:test fails with the message Goal [java:compile] has no action definition I have scoured this list and tried some of the recommendations (such as wiping out the plugins cache) to no avail. Can you help? Sri Details: Project structure Root | +-- sub-project-1 | +-- sub-project-2 Root's maven.xml: goal name=root_project:build-all maven:reactor .../ test:test/ -- Causes the error /goal - 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]
having troubles with maven RC2
Hello,
I'm trying to use maven RC2 on some of our projects that are using RC1.
Everything looks good (build, test, cactus with new cactus-maven
plugin...), but I get some troubles with maven-eclipse plugin :
maven eclipse:generate-classpath fails with this error :
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc2
Could not find the class: org.apache.commons.jelly.tags.xml.XMLTagLibrary
java.lang.ClassNotFoundException:
org.apache.commons.jelly.tags.xml.XMLTagLibrary
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
I added commons-jelly-tags-xml-20030211.142705.jar to my
${maven-home}/bin and it works
Has it been omitted from mavenRC2 dist or are eclipse-plugin
dependencies broken with RC2 ?
I used windows Exe installer to get maven RC2.
Nico.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: having troubles with maven RC2
this jar must be place in your folder
${MAVEN_HOME_LOCAL}/repository/commons-jelly/jars/ and not in folder where maven is
installed.
-Message d'origine-
De : nicolas De Loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 24 mars 2004 14:46
À : Maven Users List
Objet : having troubles with maven RC2
Hello,
I'm trying to use maven RC2 on some of our projects that are using RC1.
Everything looks good (build, test, cactus with new cactus-maven
plugin...), but I get some troubles with maven-eclipse plugin :
maven eclipse:generate-classpath fails with this error :
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc2
Could not find the class: org.apache.commons.jelly.tags.xml.XMLTagLibrary
java.lang.ClassNotFoundException:
org.apache.commons.jelly.tags.xml.XMLTagLibrary
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
I added commons-jelly-tags-xml-20030211.142705.jar to my
${maven-home}/bin and it works
Has it been omitted from mavenRC2 dist or are eclipse-plugin
dependencies broken with RC2 ?
I used windows Exe installer to get maven RC2.
Nico.
-
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: having troubles with maven RC2
OK about that, but didn't maven dependency ensure this when runing the
eclipse plugin ?
I re-installed maven RC2 and deleted my local repo for test.
without the cactus plugin, eclipse:generate-classpath goal works fine
with cactus plugin 1.6dev-20040226, I get this ClassNotFoundException
Do I need to use and earlier cactus plugin version ?
Nico.
Barbier Gabriel a écrit :
this jar must be place in your folder ${MAVEN_HOME_LOCAL}/repository/commons-jelly/jars/ and not in folder where maven is installed.
-Message d'origine-
De : nicolas De Loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 24 mars 2004 14:46
À : Maven Users List
Objet : having troubles with maven RC2
Hello,
I'm trying to use maven RC2 on some of our projects that are using RC1.
Everything looks good (build, test, cactus with new cactus-maven
plugin...), but I get some troubles with maven-eclipse plugin :
maven eclipse:generate-classpath fails with this error :
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc2
Could not find the class: org.apache.commons.jelly.tags.xml.XMLTagLibrary
java.lang.ClassNotFoundException:
org.apache.commons.jelly.tags.xml.XMLTagLibrary
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
I added commons-jelly-tags-xml-20030211.142705.jar to my
${maven-home}/bin and it works
Has it been omitted from mavenRC2 dist or are eclipse-plugin
dependencies broken with RC2 ?
I used windows Exe installer to get maven RC2.
Nico.
-
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: having troubles with maven RC2
I tryied the 3 cactus-maven-plugin versions that I found on ibiblio.
Using 1.6dev-20040115, eclipse plugin works fine. with the 2 newers one,
I got this ClassNotFoundException.
Is this a known bug ? Iis it any api change in cactus plugin that
causes this exception ? Do I need to open a new bug for this ?
Nico.
nicolas De Loof a écrit :
OK about that, but didn't maven dependency ensure this when runing the
eclipse plugin ?
I re-installed maven RC2 and deleted my local repo for test.
without the cactus plugin, eclipse:generate-classpath goal works fine
with cactus plugin 1.6dev-20040226, I get this ClassNotFoundException
Do I need to use and earlier cactus plugin version ?
Nico.
Barbier Gabriel a écrit :
this jar must be place in your folder
${MAVEN_HOME_LOCAL}/repository/commons-jelly/jars/ and not in folder
where maven is installed.
-Message d'origine-
De : nicolas De Loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 24 mars 2004 14:46
À : Maven Users List
Objet : having troubles with maven RC2
Hello,
I'm trying to use maven RC2 on some of our projects that are using RC1.
Everything looks good (build, test, cactus with new cactus-maven
plugin...), but I get some troubles with maven-eclipse plugin :
maven eclipse:generate-classpath fails with this error :
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc2
Could not find the class:
org.apache.commons.jelly.tags.xml.XMLTagLibrary
java.lang.ClassNotFoundException:
org.apache.commons.jelly.tags.xml.XMLTagLibrary
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
I added commons-jelly-tags-xml-20030211.142705.jar to my
${maven-home}/bin and it works
Has it been omitted from mavenRC2 dist or are eclipse-plugin
dependencies broken with RC2 ?
I used windows Exe installer to get maven RC2.
Nico.
-
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: having troubles with maven RC2
I verified in maven rc2, and I didn't find this jar in default distribution (ie in lib
folder).
-Message d'origine-
De : nicolas De Loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 24 mars 2004 14:55
À : Maven Users List
Objet : Re: having troubles with maven RC2
OK about that, but didn't maven dependency ensure this when runing the
eclipse plugin ?
I re-installed maven RC2 and deleted my local repo for test.
without the cactus plugin, eclipse:generate-classpath goal works fine
with cactus plugin 1.6dev-20040226, I get this ClassNotFoundException
Do I need to use and earlier cactus plugin version ?
Nico.
Barbier Gabriel a écrit :
this jar must be place in your folder
${MAVEN_HOME_LOCAL}/repository/commons-jelly/jars/ and not in folder where maven is
installed.
-Message d'origine-
De : nicolas De Loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 24 mars 2004 14:46
À : Maven Users List
Objet : having troubles with maven RC2
Hello,
I'm trying to use maven RC2 on some of our projects that are using RC1.
Everything looks good (build, test, cactus with new cactus-maven
plugin...), but I get some troubles with maven-eclipse plugin :
maven eclipse:generate-classpath fails with this error :
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc2
Could not find the class: org.apache.commons.jelly.tags.xml.XMLTagLibrary
java.lang.ClassNotFoundException:
org.apache.commons.jelly.tags.xml.XMLTagLibrary
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
I added commons-jelly-tags-xml-20030211.142705.jar to my
${maven-home}/bin and it works
Has it been omitted from mavenRC2 dist or are eclipse-plugin
dependencies broken with RC2 ?
I used windows Exe installer to get maven RC2.
Nico.
-
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: RC2 Torque Plugin
That did the trick cheers On Wed, 2004-03-24 at 11:28, Joachim Bader wrote: On Wednesday 24 March 2004 12:08, Joe Taylor wrote: RC2 doesn't seem to have the torque plugin. From earlier posts it looks like this has been migrated into the torque project but I cant find a download for it. Do i need to build this from CVS? or have i missed something else along the way?? see http://db.apache.org/torque/maven-howto.html#Installation you have to build the maven torque plugin from cvs regards, Joachim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This E-mail transmission may contain confidential or legally privileged information that is intended for the addressee only. Any views or opinions presented are solely those of the author and do not necessarily represent those of CNM Limited. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or reliance upon the contents of this E-mail is strictly prohibited. If you have received this E-mail transmission in error, please notify the sender immediately, so that CNM Limited may arrange for its proper delivery. Please then delete the message from your inbox. This email has been scanned for all viruses by the MessageLabs SkyScan service. For more information on a proactive anti-virus service working around the clock, around the globe, visit http://www.messagelabs.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: having troubles with maven RC2
It seems this dependency is only needed when using latest versions of
cactus plugin.
Using 1.6dev-20040115, eclipse plugin works fine.
Nico.
Barbier Gabriel a écrit :
I verified in maven rc2, and I didn't find this jar in default distribution (ie in lib folder).
-Message d'origine-
De : nicolas De Loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 24 mars 2004 14:55
À : Maven Users List
Objet : Re: having troubles with maven RC2
OK about that, but didn't maven dependency ensure this when runing the
eclipse plugin ?
I re-installed maven RC2 and deleted my local repo for test.
without the cactus plugin, eclipse:generate-classpath goal works fine
with cactus plugin 1.6dev-20040226, I get this ClassNotFoundException
Do I need to use and earlier cactus plugin version ?
Nico.
Barbier Gabriel a écrit :
this jar must be place in your folder ${MAVEN_HOME_LOCAL}/repository/commons-jelly/jars/ and not in folder where maven is installed.
-Message d'origine-
De : nicolas De Loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 24 mars 2004 14:46
À : Maven Users List
Objet : having troubles with maven RC2
Hello,
I'm trying to use maven RC2 on some of our projects that are using RC1.
Everything looks good (build, test, cactus with new cactus-maven
plugin...), but I get some troubles with maven-eclipse plugin :
maven eclipse:generate-classpath fails with this error :
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc2
Could not find the class: org.apache.commons.jelly.tags.xml.XMLTagLibrary
java.lang.ClassNotFoundException:
org.apache.commons.jelly.tags.xml.XMLTagLibrary
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
I added commons-jelly-tags-xml-20030211.142705.jar to my
${maven-home}/bin and it works
Has it been omitted from mavenRC2 dist or are eclipse-plugin
dependencies broken with RC2 ?
I used windows Exe installer to get maven RC2.
Nico.
-
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]
AW: EJB Deployment descriptor configuration
Hi Wil,
thanks for the hint you got in the XDoclet mailing list (I didn't take a
closer look at it right now, but I definitely will...).
As mentioned before do we not use arch4j but XSLT.
Our plugin contains the following two goals for merging DDs. Here's the
Jelly script part for merging ejb-jar.xml files (jboss.xml and
jbosscmp-jdbc.xml are very similar).
!--
jabba:_collect-dds
=
--
goal name=jabba:_collect-dds
description=Internal Goal! Retrieves the deployment descriptor
fragments out of
those jar files that have the 'jabba.dd.merge' property
set to true in the POM.
It takes these fragments out of the jabba-conf
directory.
ant:mkdir dir=${maven.jabba.conf.dir}/
ant:mkdir dir=${maven.jabba.temp.dir}/dds/
ant:mkdir dir=${maven.jabba.gen.dds.dir}/
!-- unpack jabb-conf dir of marked artifacts --
j:forEach var=lib items=${pom.artifacts}
j:set var=dep value=${lib.dependency}/
j:if test=${dep.getProperty('jabba.dd.merge')=='true'}
ant:unzip
dest=${maven.jabba.temp.dir}/dds/${lib.file.name}
patternset
include name=jabba-conf/**/*.*/
/patternset
fileset dir=${lib.file.parent}
include name=${lib.file.name}/
/fileset
/ant:unzip
/j:if
/j:forEach
!-- find all ejb-jar.xml files and write them into
ejb-jar-files.xml --
ant:fileScanner var=ejbJarFiles
ant:fileset dir=${maven.jabba.temp.dir}/dds
ant:patternset
ant:include name=**/ejb-jar.xml/
/ant:patternset
/ant:fileset
/ant:fileScanner
j:file name=${maven.jabba.temp.dir}/dds/ejb-jar-files.xml
outputMode=xml
prettyPrint=true
encoding=UTF-8
x:element name=files
j:forEach var=file items=${ejbJarFiles.iterator()}
x:element name=file${file.toString()}/x:element
/j:forEach
/x:element
/j:file
/goal
!--
jabba:_merge-dds
=
--
goal name=jabba:_merge-dds
description=Internal Goal! Merges the deployment descriptor
fragments of the dependent jars
that are located in the jabba-conf directory.
prereqs=jabba:_collect-dds
!-- set JAXP XSL transformer: --
j:invoke var=${systemScope} method=setProperty
on=${systemScope}
j:arg type=java.lang.String
value=javax.xml.transform.TransformerFactory /
j:arg type=java.lang.String
value=org.apache.xalan.processor.TransformerFactoryImpl /
/j:invoke
!-- merge ejb-jar.xml deployment descriptors --
ant:xslt
in=${maven.jabba.temp.dir}/dds/ejb-jar-files.xml
out=${maven.jabba.gen.dds.dir}/ejb-jar.xml
style=${plugin.resources}/merge-ejb-jar.xsl
xmlcatalog
dtd publicId=-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN
location=${plugin.resources}/ejb-jar_2_0.dtd/
/xmlcatalog
/ant:xslt
/goal
The following xsl style sheet is used for the merge process (very simple
approach that contains no validations or other merge logic:
?xml version=1.0?
xsl:stylesheet xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
version=1.0
!-- !DOCTYPE ejb-jar PUBLIC -//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN http://java.sun.com/dtd/ejb-jar_2_0.dtd; --
xsl:output method=xml encoding=UTF-8
doctype-system=http://java.sun.com/dtd/ejb-jar_2_0.dtd;
doctype-public=-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
2.0//EN
cdata-section-elements=description ejb-ql/
xsl:template match=/
ejb-jar
description![CDATA[No Description.]]/description
display-nameGenerated by XDoclet/display-name
!-- List of all EJBs --
xsl:commentList of all EJBs/xsl:comment
enterprise-beans
!-- Session Beans --
xsl:commentSession Beans/xsl:comment
xsl:for-each select=files/file
xsl:variable name=file select=document(text())/
xsl:copy-of
select=$file/ejb-jar/enterprise-beans/session/
/xsl:for-each
!-- Entity Beans --
xsl:commentEntity Beans/xsl:comment
Re: having troubles with maven RC2
I've take a look on cactus plugin.jelly for 1.6dev-20040226 version
It uses xmlns:x=jelly:xml tags, but doesn't declare dependency on it
in project.xml.
It seems to be a cactus-maven-plugin bug ! I've posted a ticket on
cactus-maven-integration for this.
Nico.
Barbier Gabriel a écrit :
I verified in maven rc2, and I didn't find this jar in default distribution (ie in lib folder).
-Message d'origine-
De : nicolas De Loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 24 mars 2004 14:55
À : Maven Users List
Objet : Re: having troubles with maven RC2
OK about that, but didn't maven dependency ensure this when runing the
eclipse plugin ?
I re-installed maven RC2 and deleted my local repo for test.
without the cactus plugin, eclipse:generate-classpath goal works fine
with cactus plugin 1.6dev-20040226, I get this ClassNotFoundException
Do I need to use and earlier cactus plugin version ?
Nico.
Barbier Gabriel a écrit :
this jar must be place in your folder ${MAVEN_HOME_LOCAL}/repository/commons-jelly/jars/ and not in folder where maven is installed.
-Message d'origine-
De : nicolas De Loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 24 mars 2004 14:46
À : Maven Users List
Objet : having troubles with maven RC2
Hello,
I'm trying to use maven RC2 on some of our projects that are using RC1.
Everything looks good (build, test, cactus with new cactus-maven
plugin...), but I get some troubles with maven-eclipse plugin :
maven eclipse:generate-classpath fails with this error :
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc2
Could not find the class: org.apache.commons.jelly.tags.xml.XMLTagLibrary
java.lang.ClassNotFoundException:
org.apache.commons.jelly.tags.xml.XMLTagLibrary
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
I added commons-jelly-tags-xml-20030211.142705.jar to my
${maven-home}/bin and it works
Has it been omitted from mavenRC2 dist or are eclipse-plugin
dependencies broken with RC2 ?
I used windows Exe installer to get maven RC2.
Nico.
-
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: having troubles with maven RC2
Thanks for help, I've posted a ticket on cactus bugzilla for this.
Nico.
[EMAIL PROTECTED] a écrit :
It is probably a problem in the maven cactus plugin.
To solve it you can add the next dependance to the
~/.maven/plugins/cactus-maven-1.6dev-20040226/project.xml
dependency
groupIdcommons-jelly/groupId
artifactIdcommons-jelly-tags-xml/artifactId
version20030211.142705/version
/dependency
Is it true ?
Nicolas,
nicolas De Loof [EMAIL PROTECTED]
24/03/2004 15:48
Veuillez répondre à Maven Users List
Pour : Maven Users List [EMAIL PROTECTED]
cc :
Objet : Re: having troubles with maven RC2
It seems this dependency is only needed when using latest versions of
cactus plugin.
Using 1.6dev-20040115, eclipse plugin works fine.
Nico.
Barbier Gabriel a écrit :
I verified in maven rc2, and I didn't find this jar in default
distribution (ie in lib folder).
-Message d'origine-
De : nicolas De Loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 24 mars 2004 14:55
À : Maven Users List
Objet : Re: having troubles with maven RC2
OK about that, but didn't maven dependency ensure this when runing the
eclipse plugin ?
I re-installed maven RC2 and deleted my local repo for test.
without the cactus plugin, eclipse:generate-classpath goal works fine
with cactus plugin 1.6dev-20040226, I get this ClassNotFoundException
Do I need to use and earlier cactus plugin version ?
Nico.
Barbier Gabriel a écrit :
this jar must be place in your folder
${MAVEN_HOME_LOCAL}/repository/commons-jelly/jars/ and not in folder where
maven is installed.
-Message d'origine-
De : nicolas De Loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 24 mars 2004 14:46
À : Maven Users List
Objet : having troubles with maven RC2
Hello,
I'm trying to use maven RC2 on some of our projects that are using RC1.
Everything looks good (build, test, cactus with new cactus-maven
plugin...), but I get some troubles with maven-eclipse plugin :
maven eclipse:generate-classpath fails with this error :
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc2
Could not find the class:
org.apache.commons.jelly.tags.xml.XMLTagLibrary
java.lang.ClassNotFoundException:
org.apache.commons.jelly.tags.xml.XMLTagLibrary
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
I added commons-jelly-tags-xml-20030211.142705.jar to my
${maven-home}/bin and it works
Has it been omitted from mavenRC2 dist or are eclipse-plugin
dependencies broken with RC2 ?
I used windows Exe installer to get maven RC2.
Nico.
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
HTTPS bug? / workaround
Ive setup a remote repository using https ~/build.properties maven.repo.remote=https://myServer.edu/maven,http://www.ibiblio.org/mave n Using this setup causes maven to search for dependencies using only one slash. Maven output: Error retrieving artifact from [https:/myServer.edu/maven/] The work around appears to be to use three slashes in my build.properties. maven.repo.remote=https:///myServer.edu/maven Is this a bug? Or is maven supposed to behave this manner? --Jâsõñ Mà©þh뮧òñ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTPS bug? / workaround
J$ Mh$ wrote: Ive setup a remote repository using https ~/build.properties maven.repo.remote=https://myServer.edu/maven,http://www.ibiblio.org/mave n Using this setup causes maven to search for dependencies using only one slash. Maven output: Error retrieving artifact from [https:/myServer.edu/maven/] The work around appears to be to use three slashes in my build.properties. maven.repo.remote=https:///myServer.edu/maven Is this a bug? Or is maven supposed to behave this manner? --Js Mh I used to have the same problem with maven-1.0-rc1 until it was fixed in CVS. I have not tried rc2 yet, but I guess that fix should have made it into this version. Ie. unless nobody wrote a test for it and the bug got re-introduced somehow. Are you using rc2? Edmund - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Determining current OS
I am trying to convert an Ant script that I have that needs to know which OS it is currently running on. I took the statements condition property=isUnix os family=unix/ /condition condition property=isWindows os family=windows/ /condition and put them in my maven.xml as ant:condition property=isUnix ant:os family=unix/ /ant:condition ant:condition property=isWindows ant:os family=windows/ /ant:condition But when I run, neither property is being set. I've scanned the plugin.jelly files and none are using this condition. Is there a better way to determine what OS is being used? The reason for the test is that I need to run the Ant task pathconvert which needs to know the target OS. -- Erik Husby Team Lead for Software Quality Automation Genome Center at MIT Rm. 2192 320 Charles St Cambridge, MA 02141-2023 mobile: 781.354.6669 office: 617.258.9227 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Anyone working on WebSphere AppServer 5.0 Plugin?
Michele, See http://maven-plugins.sourceforge.net/maven-was5-plugin/index.html It appears to be a new plugin by Richard Lewis-Shell. Thanks for the work Richard. Works a treat. I'm sure the sourceforge maven-plugins main page will be updated to include it soon. Al Digital Union UK [EMAIL PROTECTED] www.digitalunion.com t: +44 (0) 1483 889482 m:+44 (0) 7713 631367 f: +44 (0) 1483 889450 The information in this email and in any attachment(s) is confidential. If you are not the named addressee(s) or if you receive this email in error then any distribution, copying or use of this communication or the information in it is strictly prohibited. While attachments are virus checked, Digital Union UK Limited does not accept any liability in respect of any virus which is not detected. [EMAIL PROTECTED] 24/03/2004 13:22 Please respond to Maven Users List [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Maven Users List [EMAIL PROTECTED] Subject Re: Anyone working on WebSphere AppServer 5.0 Plugin? Hello dion, Following your advice I wanted to give a look at the stutus of the current plugin for WAS50, but the link is pointing to the maven-plugins page where only the maven plugin for was4.0 is present. Or am I missing something ? In case can someone from the audience point me to the rigth location of this plugin ? Michele |-+ | | [EMAIL PROTECTED]| | | m.au | | || | || | | 10/03/2004 22:17 | | | Please respond to| | | Maven Users | | | List| | || |-+ --| | | | | | | | | | | |To: Maven Users List [EMAIL PROTECTED] | |cc: (bcc: Michele Forte/SwissRe) | |bcc:Michele Forte/SwissRe | |Subject:Re: Anyone working on WebSphere AppServer 5.0 Plugin? | --| There's now a working was50 plugin as part of http://maven-plugins.sourceforge.net. If you need a built version let me know. -- dIon Gillard, Multitask Consulting [EMAIL PROTECTED] wrote on 11/03/2004 05:03:25 AM: I have one working with wsadmin. It can start/stop server, application, deploy and undeploy ear, list, and status. Basically, anything supported by wsadmin can be added easily. It works for a local or remote instance. Now the kicker... Waiting to working out our corporate open source policy before I can make it available outside. Its basic structure is on the WAS4, just changing the executable and command line options. If you take a look at WAS5's documentation of migrating from the old wscp to wsadmin, it's not too difficult, with some minor tricks you need to know, such as using $$ when you have to pass a string into the command line with $ and such. Jun Ying |-+ | | [EMAIL PROTECTED]| | | m.au | | || | | 03/04/2004 06:32 | | | PM | | | Please respond to| | | Maven Users | | | List| |-+ | || | To: Maven Users List [EMAIL PROTECTED]| | cc:| | Subject: Re: Anyone working on WebSphere AppServer 5.0 Plugin? | | Not AFAIK, [EMAIL PROTECTED] wrote on 05/03/2004 12:48:58 AM: Is anyone working on a WebSphere AppServer 5.0 plugin? - Tom But if you wanted to start one, come over and join the AppServer 4.0 plugin team on http://maven-plugins.sf.net. -- dIon Gillard, Multitask Consulting
RE: Determining current OS
Perhaps something such as
j:choose
j:when test=${systemScope['os.name'].startsWith('Windows')}
j:set var=isWindows value=true/
j:set var=isUnix value=false/
ant:echoThe operating system is Windows/ant:echo
/j:when
j:otherwise
j:set var=isWindows value=false/
j:set var=isUnix value=true/
ant:echoThe operating system is Unix/ant:echo
/j:otherwise
/j:choose
-Original Message-
From: Erik Husby [mailto:[EMAIL PROTECTED]
Sent: 24 March 2004 16:37
To: [EMAIL PROTECTED]
Subject: Determining current OS
I am trying to convert an Ant script that I have that needs to know
which OS it is currently running on. I took the statements
condition property=isUnix
os family=unix/
/condition
condition property=isWindows
os family=windows/
/condition
and put them in my maven.xml as
ant:condition property=isUnix
ant:os family=unix/
/ant:condition
ant:condition property=isWindows
ant:os family=windows/
/ant:condition
But when I run, neither property is being set.
I've scanned the plugin.jelly files and none are using this condition.
Is there a better way to determine what
OS is being used?
The reason for the test is that I need to run the Ant task pathconvert
which needs to know the target OS.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Understanding Maven Reactor
Maven will always try to download dependencies from the project.xml in the directory from where you run Maven before it attempts to execute any goals. You should only specify the dependencies for the subprojects that need them. The top level project.xml should only contain dependencies that all of its subprojects need. WM --- Daniel Frey [EMAIL PROTECTED] wrote: Hi there, Newbie question: I've read the introduction to maven as described in http://maven.apache.org/reference/user-guide.html#Multi_Project_Builds_and_t he_Reactor. Then I copied from another source a new goal into my maven.xml. goal name=all:java:compile maven:reactor basedir=.. includes=ch.*/**/project.xml goals=java:compile banner=Compiling: ignoreFailures=false/ /goal Build fails with the following messages: __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc2 Attempting to download ch.xmatrix.resource-api-1.0.jar. WARNING: Failed to download ch.xmatrix.resource-api-1.0.jar. Attempting to download ch.xmatrix.gui.splash-api-1.0.jar. WARNING: Failed to download ch.xmatrix.gui.splash-api-1.0.jar. The build cannot continue because of the following unsatisfied dependencies: ch.xmatrix.resource-api-1.0.jar (no download url specified) ch.xmatrix.gui.splash-api-1.0.jar (no download url specified) My multi-project structure consists of: ch.xmatrix.application ch.xmatrix.resource-api ch.xmatrix.resource-impl ch.xmatrix.gui.splash-impl ch.xmatrix.gui.splash-api The two ch.*-apis are dependencies of (the main) application. I hoped that reactor would sort these out an build these first, as they are part of my multi-project directory structure. Why does maven -- before starting the reactor -- try to download these dependent libraries? Instead of building them? Thanks for any hints. Daniel Frey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Anyone working on WebSphere AppServer 5.0 Plugin?
Thanks for the feedback. Are you using WAS5.0 or 5.1? Richard - Original Message - From: Al Robertson [EMAIL PROTECTED] To: Maven Users List [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, March 25, 2004 3:46 AM Subject: Re: Anyone working on WebSphere AppServer 5.0 Plugin? Michele, See http://maven-plugins.sourceforge.net/maven-was5-plugin/index.html It appears to be a new plugin by Richard Lewis-Shell. Thanks for the work Richard. Works a treat. I'm sure the sourceforge maven-plugins main page will be updated to include it soon. Al Digital Union UK [EMAIL PROTECTED] www.digitalunion.com t: +44 (0) 1483 889482 m:+44 (0) 7713 631367 f: +44 (0) 1483 889450 The information in this email and in any attachment(s) is confidential. If you are not the named addressee(s) or if you receive this email in error then any distribution, copying or use of this communication or the information in it is strictly prohibited. While attachments are virus checked, Digital Union UK Limited does not accept any liability in respect of any virus which is not detected. [EMAIL PROTECTED] 24/03/2004 13:22 Please respond to Maven Users List [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Maven Users List [EMAIL PROTECTED] Subject Re: Anyone working on WebSphere AppServer 5.0 Plugin? Hello dion, Following your advice I wanted to give a look at the stutus of the current plugin for WAS50, but the link is pointing to the maven-plugins page where only the maven plugin for was4.0 is present. Or am I missing something ? In case can someone from the audience point me to the rigth location of this plugin ? Michele |-+ | | [EMAIL PROTECTED]| | | m.au | | || | || | | 10/03/2004 22:17 | | | Please respond to| | | Maven Users | | | List| | || |-+ --- ---| | | | | | | | | | | |To: Maven Users List [EMAIL PROTECTED] | |cc: (bcc: Michele Forte/SwissRe) | |bcc:Michele Forte/SwissRe | |Subject:Re: Anyone working on WebSphere AppServer 5.0 Plugin? | --- ---| There's now a working was50 plugin as part of http://maven-plugins.sourceforge.net. If you need a built version let me know. -- dIon Gillard, Multitask Consulting [EMAIL PROTECTED] wrote on 11/03/2004 05:03:25 AM: I have one working with wsadmin. It can start/stop server, application, deploy and undeploy ear, list, and status. Basically, anything supported by wsadmin can be added easily. It works for a local or remote instance. Now the kicker... Waiting to working out our corporate open source policy before I can make it available outside. Its basic structure is on the WAS4, just changing the executable and command line options. If you take a look at WAS5's documentation of migrating from the old wscp to wsadmin, it's not too difficult, with some minor tricks you need to know, such as using $$ when you have to pass a string into the command line with $ and such. Jun Ying |-+ | | [EMAIL PROTECTED]| | | m.au | | || | | 03/04/2004 06:32 | | | PM | | | Please respond to| | | Maven Users | | | List| |-+ -- -- | || | To: Maven Users List [EMAIL PROTECTED]| | cc:| | Subject: Re: Anyone working on WebSphere AppServer 5.0 Plugin? |
Maven Jira Report plugin in RC2?
New maven release candidate refers to jira plugin but i don't see any references to it anywhere else on maven site. Is there such a plugin and where could I find some documentation about it? thanks vlad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
war:webapp goal not working in RC2
When I run war:webapp goal in maven RC2 I get an error saying that java:compile goal does not exist. I also tried removing and rebuilding maven repo from scratch but I still get same behaviour. thanks vlad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Goal [java:compile] has no action definition
Just recapping my Q's to see what is happening here: 1) If you run just java:compile on its own does it work? 2) When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 12:27 AM To: Maven Users List Subject: RE: Goal [java:compile] has no action definition I am sorry... I meant to say attainGoal name=test:test/. So, to recap: Project structure Root | +-- sub-project-1 | +-- sub-project-2 Root's maven.xml: goal name=root_project:build-all maven:reactor .../ attainGoal name=test:test/ -- Causes the error /goal -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 23, 2004 9:35 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition IS this a real example? test:test/ doesn't exist. You must mean attainGoal name=test:test / If you run just java:compile on its own does it work? When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Wednesday, 24 March 2004 1:28 PM To: [EMAIL PROTECTED] Subject: Goal [java:compile] has no action definition Using : Maven 1.0 rc2 OS: Windows XP Professional At the end of a reactor build I invoke test:test to run integration tests on my entire project. The entire reactor build runs successfully. However, the call to test:test fails with the message Goal [java:compile] has no action definition I have scoured this list and tried some of the recommendations (such as wiping out the plugins cache) to no avail. Can you help? Sri Details: Project structure Root | +-- sub-project-1 | +-- sub-project-2 Root's maven.xml: goal name=root_project:build-all maven:reactor .../ test:test/ -- Causes the error /goal - 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: webapp goal not working in RC2
Seems to be the same problem as another thread on the list. Can you answer these questions to help diagnose the problem: 1) If you run just java:compile on its own does it work? 2) When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: VLADIMIR TERZIC [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 9:19 AM To: [EMAIL PROTECTED] Subject: war:webapp goal not working in RC2 When I run war:webapp goal in maven RC2 I get an error saying that java:compile goal does not exist. I also tried removing and rebuilding maven repo from scratch but I still get same behaviour. thanks vlad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven Jira Report plugin in RC2?
Some of the plugin documentation has not been published yet. I will aim to do this today. - Brett -Original Message- From: VLADIMIR TERZIC [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 9:05 AM To: [EMAIL PROTECTED] Subject: Maven Jira Report plugin in RC2? New maven release candidate refers to jira plugin but i don't see any references to it anywhere else on maven site. Is there such a plugin and where could I find some documentation about it? thanks vlad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: bootstrap-project not working quite right.
Hi Peter, Inheritence handling in 1.0 is not the best, but is something we'll work on in future versions of maven. What actually happens is that maven.xml goals are inherited, but properties are not. So what is probably happening is that the goal is being inherited when you run a subproject and resetting the property to what it finds in the subproject: that being nothing. How have you defined the goal in the root project? It is weird that this would only affect bootstrap, because while in RC2 it is done via an internal call, in RC1 it was a forked maven instance that should be identical to running from the command line. Is there a reason you can't set jboss.home in ~/build.properties? This makes more sense to me. - Brett -Original Message- From: Peter Bright [mailto:[EMAIL PROTECTED] Sent: Wednesday, 24 March 2004 10:34 PM To: Maven Users List (E-mail) Subject: scm:bootstrap-project not working quite right. Hello I have a multiproject project set up something like this: /root-project maven.xml project.xml project.properties /sub-projects /sub-project-one maven.xml project.xml project.properties /sub-project-two maven.xml project.xml project.properties etc.. The root's project.properties defines a couple of (system-dependent) properties (let's say, windows.jboss.home, solaris.jboss.home); a goal within its maven.xml then picks the right one (depending on the OS) and puts them into a third property (say, jboss.home). The sub-projects then use this third property. This all works fine (whether it be ideal or not I don't know. I inherited the layout and am unwilling to rearrange things without good reason). What I would like to do is to be able to use scm:bootstrap-project to check out the project and run the default goal. Here's where the problem lies, using both rc1 and rc2. The checkout happens normally, and the project begins building. It then reaches a part that depends on the property dynamically set at runtime -- jboss.home, and promptly fails. echoing the variable shows that it's blank. It gets set fine in the root maven.xml but goals in the subproject maven.xml can no longer see it. If I traverse to the checkout directory and run the same goal from there, it works fine; the jboss.home property gets correctly set and is accessible to the subprojects. It only seems to be when run from scm:boostrap-project that it doesn't seem visible. Does anyone know why this value isn't getting inherited properly when using scm:bootstrap-project? Should the project even work in the first place? I apologize in advance if I'm omitted any necessary details; I'm not really sure what else needs to be said. Peter ** * This message contains information that may be privileged or confidential and is the property of Orbian Management Limited. It is intended solely for the named addressee(s) and may not be used or disclosed except for the purpose for which it has been sent. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you have received this message in error, please notify the sender immediately and delete the message and any attached documents. Any opinions, conclusions and other information expressed in this message are those of the individual sender and are not given or endorsed by Orbian unless otherwise clearly indicated. Orbian has scanned this e-mail for viruses but accepts no liability or responsibility for any onward transmission or use of emails and attachments having left the Orbian domain. ** * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: webapp goal not working in RC2
I'm working at automatically correcting this in further releases. -Original Message- From: VLADIMIR TERZIC [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 9:49 AM To: [EMAIL PROTECTED] Subject: RE: webapp goal not working in RC2 stupid me...i removed .maven/repository not ./maven/plugins works fine if you remove right one ;-) thanks vlad [EMAIL PROTECTED] 03/24/04 03:38PM Seems to be the same problem as another thread on the list. Can you answer these questions to help diagnose the problem: 1) If you run just java:compile on its own does it work? 2) When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: VLADIMIR TERZIC [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 9:19 AM To: [EMAIL PROTECTED] Subject: war:webapp goal not working in RC2 When I run war:webapp goal in maven RC2 I get an error saying that java:compile goal does not exist. I also tried removing and rebuilding maven repo from scratch but I still get same behaviour. thanks vlad - 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: webapp goal not working in RC2
stupid me...i removed .maven/repository not ./maven/plugins works fine if you remove right one ;-) thanks vlad [EMAIL PROTECTED] 03/24/04 03:38PM Seems to be the same problem as another thread on the list. Can you answer these questions to help diagnose the problem: 1) If you run just java:compile on its own does it work? 2) When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: VLADIMIR TERZIC [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 9:19 AM To: [EMAIL PROTECTED] Subject: war:webapp goal not working in RC2 When I run war:webapp goal in maven RC2 I get an error saying that java:compile goal does not exist. I also tried removing and rebuilding maven repo from scratch but I still get same behaviour. thanks vlad - 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: Goal [java:compile] has no action definition
Answer 1: java:compile works fine on its own. test:test works fine on its own Answer 2: I have tried with just *.cache removed. Then I tried with the entire plugins directory wiped out. Same failure in both cases. Sri -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 5:31 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition Just recapping my Q's to see what is happening here: 1) If you run just java:compile on its own does it work? 2) When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 12:27 AM To: Maven Users List Subject: RE: Goal [java:compile] has no action definition I am sorry... I meant to say attainGoal name=test:test/. So, to recap: Project structure Root | +-- sub-project-1 | +-- sub-project-2 Root's maven.xml: goal name=root_project:build-all maven:reactor .../ attainGoal name=test:test/ -- Causes the error /goal -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 23, 2004 9:35 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition IS this a real example? test:test/ doesn't exist. You must mean attainGoal name=test:test / If you run just java:compile on its own does it work? When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Wednesday, 24 March 2004 1:28 PM To: [EMAIL PROTECTED] Subject: Goal [java:compile] has no action definition Using : Maven 1.0 rc2 OS: Windows XP Professional At the end of a reactor build I invoke test:test to run integration tests on my entire project. The entire reactor build runs successfully. However, the call to test:test fails with the message Goal [java:compile] has no action definition I have scoured this list and tried some of the recommendations (such as wiping out the plugins cache) to no avail. Can you help? Sri Details: Project structure Root | +-- sub-project-1 | +-- sub-project-2 Root's maven.xml: goal name=root_project:build-all maven:reactor .../ test:test/ -- Causes the error /goal - 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: Goal [java:compile] has no action definition
Thanks. This is odd. Did this work on rc1 or is it a new installation? Do you have a small sample project that shows the problem? If so, post it to JIRA. Thanks, Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 12:15 PM To: Maven Users List Subject: RE: Goal [java:compile] has no action definition Answer 1: java:compile works fine on its own. test:test works fine on its own Answer 2: I have tried with just *.cache removed. Then I tried with the entire plugins directory wiped out. Same failure in both cases. Sri -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 5:31 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition Just recapping my Q's to see what is happening here: 1) If you run just java:compile on its own does it work? 2) When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 12:27 AM To: Maven Users List Subject: RE: Goal [java:compile] has no action definition I am sorry... I meant to say attainGoal name=test:test/. So, to recap: Project structure Root | +-- sub-project-1 | +-- sub-project-2 Root's maven.xml: goal name=root_project:build-all maven:reactor .../ attainGoal name=test:test/ -- Causes the error /goal -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 23, 2004 9:35 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition IS this a real example? test:test/ doesn't exist. You must mean attainGoal name=test:test / If you run just java:compile on its own does it work? When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Wednesday, 24 March 2004 1:28 PM To: [EMAIL PROTECTED] Subject: Goal [java:compile] has no action definition Using : Maven 1.0 rc2 OS: Windows XP Professional At the end of a reactor build I invoke test:test to run integration tests on my entire project. The entire reactor build runs successfully. However, the call to test:test fails with the message Goal [java:compile] has no action definition I have scoured this list and tried some of the recommendations (such as wiping out the plugins cache) to no avail. Can you help? Sri Details: Project structure Root | +-- sub-project-1 | +-- sub-project-2 Root's maven.xml: goal name=root_project:build-all maven:reactor .../ test:test/ -- Causes the error /goal - 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: Goal [java:compile] has no action definition
I've been using rc2 for a while now (built Maven from CVS HEAD) and so haven't tried it on rc1. I will a) try it on the official rc2 release b) if (a) is not successful create a small project and try and recreate the problem. Sri -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 8:20 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition Thanks. This is odd. Did this work on rc1 or is it a new installation? Do you have a small sample project that shows the problem? If so, post it to JIRA. Thanks, Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 12:15 PM To: Maven Users List Subject: RE: Goal [java:compile] has no action definition Answer 1: java:compile works fine on its own. test:test works fine on its own Answer 2: I have tried with just *.cache removed. Then I tried with the entire plugins directory wiped out. Same failure in both cases. Sri -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 5:31 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition Just recapping my Q's to see what is happening here: 1) If you run just java:compile on its own does it work? 2) When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 12:27 AM To: Maven Users List Subject: RE: Goal [java:compile] has no action definition I am sorry... I meant to say attainGoal name=test:test/. So, to recap: Project structure Root | +-- sub-project-1 | +-- sub-project-2 Root's maven.xml: goal name=root_project:build-all maven:reactor .../ attainGoal name=test:test/ -- Causes the error /goal -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 23, 2004 9:35 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition IS this a real example? test:test/ doesn't exist. You must mean attainGoal name=test:test / If you run just java:compile on its own does it work? When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Wednesday, 24 March 2004 1:28 PM To: [EMAIL PROTECTED] Subject: Goal [java:compile] has no action definition Using : Maven 1.0 rc2 OS: Windows XP Professional At the end of a reactor build I invoke test:test to run integration tests on my entire project. The entire reactor build runs successfully. However, the call to test:test fails with the message Goal [java:compile] has no action definition I have scoured this list and tried some of the recommendations (such as wiping out the plugins cache) to no avail. Can you help? Sri Details: Project structure Root | +-- sub-project-1 | +-- sub-project-2 Root's maven.xml: goal name=root_project:build-all maven:reactor .../ test:test/ -- Causes the error /goal - 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: Goal [java:compile] has no action definition
Ok, now it makes more sense. This bug existed on HEAD for some time - the fix was only merged in Tuesday. You might like to refer to the wiki or my earlier email today that details the current CVS status. Cheers, Bret -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 2:24 PM To: Maven Users List Subject: RE: Goal [java:compile] has no action definition I've been using rc2 for a while now (built Maven from CVS HEAD) and so haven't tried it on rc1. I will a) try it on the official rc2 release b) if (a) is not successful create a small project and try and recreate the problem. Sri -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 8:20 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition Thanks. This is odd. Did this work on rc1 or is it a new installation? Do you have a small sample project that shows the problem? If so, post it to JIRA. Thanks, Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 12:15 PM To: Maven Users List Subject: RE: Goal [java:compile] has no action definition Answer 1: java:compile works fine on its own. test:test works fine on its own Answer 2: I have tried with just *.cache removed. Then I tried with the entire plugins directory wiped out. Same failure in both cases. Sri -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 5:31 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition Just recapping my Q's to see what is happening here: 1) If you run just java:compile on its own does it work? 2) When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 12:27 AM To: Maven Users List Subject: RE: Goal [java:compile] has no action definition I am sorry... I meant to say attainGoal name=test:test/. So, to recap: Project structure Root | +-- sub-project-1 | +-- sub-project-2 Root's maven.xml: goal name=root_project:build-all maven:reactor .../ attainGoal name=test:test/ -- Causes the error /goal -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 23, 2004 9:35 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition IS this a real example? test:test/ doesn't exist. You must mean attainGoal name=test:test / If you run just java:compile on its own does it work? When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Wednesday, 24 March 2004 1:28 PM To: [EMAIL PROTECTED] Subject: Goal [java:compile] has no action definition Using : Maven 1.0 rc2 OS: Windows XP Professional At the end of a reactor build I invoke test:test to run integration tests on my entire project. The entire reactor build runs successfully. However, the call to test:test fails with the message Goal [java:compile] has no action definition I have scoured this list and tried some of the recommendations (such as wiping out the plugins cache) to no avail. Can you help? Sri Details: Project structure Root | +-- sub-project-1 | +-- sub-project-2 Root's maven.xml: goal name=root_project:build-all maven:reactor .../ test:test/ -- Causes the error /goal - 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: Goal [java:compile] has no action definition
Right you are! Things work just fine with the official rc-2 release. Sorry for having taken up the bandwidth. Thanks for all the help. I commend the work you do Brett; not just in developing the plug-ins but also in how you acquit yourself to addressing countless questions on this list everyday -- politely and patiently. Keep up the good work. Sri -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 10:26 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition Ok, now it makes more sense. This bug existed on HEAD for some time - the fix was only merged in Tuesday. You might like to refer to the wiki or my earlier email today that details the current CVS status. Cheers, Bret -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 2:24 PM To: Maven Users List Subject: RE: Goal [java:compile] has no action definition I've been using rc2 for a while now (built Maven from CVS HEAD) and so haven't tried it on rc1. I will a) try it on the official rc2 release b) if (a) is not successful create a small project and try and recreate the problem. Sri -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 8:20 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition Thanks. This is odd. Did this work on rc1 or is it a new installation? Do you have a small sample project that shows the problem? If so, post it to JIRA. Thanks, Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 12:15 PM To: Maven Users List Subject: RE: Goal [java:compile] has no action definition Answer 1: java:compile works fine on its own. test:test works fine on its own Answer 2: I have tried with just *.cache removed. Then I tried with the entire plugins directory wiped out. Same failure in both cases. Sri -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 5:31 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition Just recapping my Q's to see what is happening here: 1) If you run just java:compile on its own does it work? 2) When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 March 2004 12:27 AM To: Maven Users List Subject: RE: Goal [java:compile] has no action definition I am sorry... I meant to say attainGoal name=test:test/. So, to recap: Project structure Root | +-- sub-project-1 | +-- sub-project-2 Root's maven.xml: goal name=root_project:build-all maven:reactor .../ attainGoal name=test:test/ -- Causes the error /goal -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 23, 2004 9:35 PM To: 'Maven Users List' Subject: RE: Goal [java:compile] has no action definition IS this a real example? test:test/ doesn't exist. You must mean attainGoal name=test:test / If you run just java:compile on its own does it work? When you say that you deleted the plugin cache, did you remove the entire ~/.maven/plugins directory or just the .cache files? - Brett -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Wednesday, 24 March 2004 1:28 PM To: [EMAIL PROTECTED] Subject: Goal [java:compile] has no action definition Using : Maven 1.0 rc2 OS: Windows XP Professional At the end of a reactor build I invoke test:test to run integration tests on my entire project. The entire reactor build runs successfully. However, the call to test:test fails with the message Goal [java:compile] has no action definition I have scoured this list and tried some of the recommendations (such as wiping out the plugins cache) to no avail. Can you help? Sri Details: Project structure Root | +-- sub-project-1 | +-- sub-project-2 Root's maven.xml: goal name=root_project:build-all maven:reactor .../ test:test/ -- Causes the error /goal - 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]
