RE: Maven Abbot plugin - feedback wanted
Hi Dion, In the case of webtesting you could have a look at the Canoo WebTest Plugin hosted on maven-plugins.sourceforge.net. Cheers, Siegfried Goeschl -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Samstag, 01. Mai 2004 15:08 To: Maven Users List Subject: Re: Maven Abbot plugin - feedback wanted Can abbot be used for web app testing? -- dIon Gillard, Multitask Consulting Vincent Massol [EMAIL PROTECTED] wrote on 01/05/2004 07:46:11 AM: Hi Abbot and Maven users, I've just committed today a Maven plugin for Abbot. See http://maven.apache.org/reference/plugins/abbot/ for more information. Note that this plugin supports testing webstart applications. The plugin is not released yet so you'll have to build it from source. To do this, install Maven, checkout the maven-plugins-sandbox module (http://cvs.apache.org/viewcvs.cgi/maven-plugins-sandbox/), cd to abbot/ and type maven plugin:install. Feedback is much welcome. Thanks -Vincent Wanna see JUnit in Action? (http://manning.com/massol) - 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]
How to set suppressions for checkstyle plugin
I'm using the checkstyle plugin and I'd like to suppress some of the things it checks. The docs for the plugin talk about a checkstyle properties but nothing about supressions. The checkstyle docs talk about a suppressions.xml but I'm not sure how to configure the maven plugin to use the suppressions.xml document. Any ideas? Regards, Michael Mattox -- 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]
Re: multiproject plugin
Have you run multiproject:install so all jars/wars/ears have been made for
the site goal to use to generate reports?
If appEJB's pom extends app's pom, it might be because of not using
${basedir} as a prefix. For example: .../src/java...
What's the output? Maybe the javadocs report failed because the command line
was to long (there is a fix for that by writing them to a file), maybe other
things failed.
--
With kind regards,
Geoffrey
Ricardo de Souza Moura [EMAIL PROTECTED] schreef in bericht
news:[EMAIL PROTECTED]
I am trying to use the multiproject plugin, but when I try to call
multiproject:site, it fail.
my structure:
app
appEJB
appWEB
appEAR
I call maven multiproject:site from app directory.
The error:
You must exclude app:app (the top level project) from the subproject set
All properties are with default value, so my maven.multiproject.includes
propertie is with value: */project.xml. So my top level project is
exclude.
But...
When I call:
maven -Dgoal=site multiproject:goal
almost everything works well.
I understood that would be generated a aggregate site in the
${basedir}/multiproject/ with a menu with links to all subprojects. It
didn't happen. Why not ?
Thanks
_
MSN Messenger: converse com os seus amigos online.
http://messenger.msn.com.br
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
maven, junit JAAS
Hi! Is someone made junit test case which try to login by using JAAS? I try to call maven with following: maven -Djava.security.manager -Djava.security.auth.login.config=/home/artsi/workspace/server/test.conf test But i still got: Testcase: test(fi.canter.ams.JAASLoginTest):Caused an ERROR Unable to locate a login configuration java.lang.SecurityException: Unable to locate a login configuration at com.sun.security.auth.login.ConfigFile.init(ConfigFile.java:97) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) Artsi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven2] Anything Groovy in Maven2?
Jason van Zyl [EMAIL PROTECTED] wrote on 03/05/2004 01:03:57 PM:
On Sun, 2004-05-02 at 21:10, [EMAIL PROTECTED] wrote:
Given the vast amount of ant build scripts out there, there must be a
few.
Yes, but that's a result of there never being a choice. If someone had
made a build tool using something like beanshell during the time ant was
becoming popular I do wonder what the population of XML build files
would be. Maybe a lot, maybe not. I'm used to them now as I've been
exposed to them for quite a while like most but it doesn't mean they are
optimal or ideal.
Another thing to consider is the IO model for Ant is a lot less verbose
than plain Java.
Groovy is a step ahead in this regard, but still standard Java is very
verbose and a large effort compared to a build snippet to do copies,
moves, xml transforms on multiple files.
Compare:
-ant approach
project
delete dir=${maven.build.dir}/
/project
ant
-ant approach
with
- java approach
public class Clean {
public static void main(String[] args)
{
new java.io.File(args[0]).delete();
}
}
javac Clean.java
java Clean target
-java approach
- windows shell approach
rmdir target /q /s
- windows shell approach
And the java approach doesn't handle simple stuff like deleting non-empty
directories.
The real issue is a lack of decent libraries for doing typical build
tasks. If java-based plugins are to be a success, we'll need to beef up
the existing libraries to handle common tasks.
--
dIon Gillard, Multitask Consulting
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
aopalliance
I opened MAVEN-1256 to upload aopalliance.jar on ibiblio (needed to use spring AOP) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to set suppressions for checkstyle plugin
Hi Michael, You have complete power over the checkstyle.xml file. So you can provide your own. I think that the suppressions/filter stuff are defined inside this file so you should be able to control them. Why don't you try it and tell us how it goes? If required, we can improve the plugin to support whatever's needed. Thanks -Vincent -Original Message- From: Michael Mattox [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 10:54 To: Maven Users List Subject: How to set suppressions for checkstyle plugin I'm using the checkstyle plugin and I'd like to suppress some of the things it checks. The docs for the plugin talk about a checkstyle properties but nothing about supressions. The checkstyle docs talk about a suppressions.xml but I'm not sure how to configure the maven plugin to use the suppressions.xml document. Any ideas? Regards, Michael Mattox -- 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven, junit and JAAS
Hi! Is someone made junit test case which try to login by using JAAS? I try to call maven with following: maven -Djava.security.manager -Djava.security.auth.login.config=/home/artsi/workspace/server/test.conf test But i still got: Testcase: test(fi.canter.ams.JAASLoginTest):Caused an ERROR Unable to locate a login configuration java.lang.SecurityException: Unable to locate a login configuration at com.sun.security.auth.login.ConfigFile.init(ConfigFile.java:97) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) Artsi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Mysterious no goal [xdoc]
Hello, I have a mysterious problem where maven doesn't want to use its xdoc-Plugin (v 1.6 on rc2). On one day invoking the site:deploy goal caused no problems while on the other day the build fails like this: BUILD FAILED File.. file:/opt/tomcat/.maven/plugins/maven-site-plugin-1.5/plugin.jelly Element... attainGoal Line.. 40 Column 42 No goal [xdoc:register-reports] Total time: 12 seconds Finished at: Mon May 03 12:00:55 CEST 2004 Trying any xdoc goal directly leads to a NoSuchGoalException. The same project's site-goal (and several xdoc goals) build perfectly on my local Win2000 machine, but on the server (Sun Solaris) they won't. The xdoc plugin is installed as far as I can tell (i.e. the maven-xdoc-plugin-1.6.jar is in the install dir's pluging directory and the extracted files are present in the user's maven/plugins directory), so I have not a clue right now of what is going wrong... Can anyone offer hints? Many thanks, Christian Nill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven, junit JAAS
Ok, if someone interested, i must add: maven.junit.jvmargs=-Djava.security.auth.login.config=test.conf to project.properties, instead definind that in command line. On Mon, 2004-05-03 at 13:14, Arto Pastinen wrote: Hi! Is someone made junit test case which try to login by using JAAS? I try to call maven with following: maven -Djava.security.manager -Djava.security.auth.login.config=/home/artsi/workspace/server/test.conf test But i still got: Testcase: test(fi.canter.ams.JAASLoginTest):Caused an ERROR Unable to locate a login configuration java.lang.SecurityException: Unable to locate a login configuration at com.sun.security.auth.login.ConfigFile.init(ConfigFile.java:97) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) Artsi - 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: [maven2] Anything Groovy in Maven2?
On Mon, 3 May 2004 14:06:27 +1000, [EMAIL PROTECTED] wrote:
Jason van Zyl [EMAIL PROTECTED] wrote on 03/05/2004 01:03:57 PM:
On Sun, 2004-05-02 at 21:10, [EMAIL PROTECTED] wrote:
Given the vast amount of ant build scripts out there, there must be a
few.
Yes, but that's a result of there never being a choice. If someone had
made a build tool using something like beanshell during the time ant was
becoming popular I do wonder what the population of XML build files
would be. Maybe a lot, maybe not. I'm used to them now as I've been
exposed to them for quite a while like most but it doesn't mean they are
optimal or ideal.
Another thing to consider is the IO model for Ant is a lot less verbose
than plain Java.
Groovy is a step ahead in this regard, but still standard Java is very
verbose and a large effort compared to a build snippet to do copies,
moves, xml transforms on multiple files.
Compare:
-ant approach
project
delete dir=${maven.build.dir}/
/project
ant
-ant approach
with
- java approach
public class Clean {
public static void main(String[] args)
{
new java.io.File(args[0]).delete();
}
}
javac Clean.java
java Clean target
-java approach
I relly don't thinkt this is so bad. Most of the plugins are much more than
one liners and as you can see the overhead for each file here is 4 lines.
On the upside the plugins will be much easier to test and will run fast as
hell.
- windows shell approach
rmdir target /q /s
- windows shell approach
And the java approach doesn't handle simple stuff like deleting non-empty
directories.
The real issue is a lack of decent libraries for doing typical build
tasks. If java-based plugins are to be a success, we'll need to beef up
the existing libraries to handle common tasks.
There are quite a bit of very good file handing methods in commons-io but
I totally agree with you. We might wan't to create a maven-plugin-utils
library for making plugin development easier.
--
dIon Gillard, Multitask Consulting
--
Trygve
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven, junit JAAS
Arto Pastinen wrote on Monday, May 03, 2004 12:42 PM: Ok, if someone interested, i must add: maven.junit.jvmargs=-Djava.security.auth.login.config=test.conf to project.properties, instead definind that in command line. You might also setup an system environment in the test case's setUp method. Just Retrieve the original environemnt with System.getProperties and restore them later in tearDown with system.setProperties. Regards, Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mysterious no goal [xdoc]
Hi, Christian Nill [EMAIL PROTECTED] writes: I have a mysterious problem where maven doesn't want to use its xdoc-Plugin (v 1.6 on rc2). On one day invoking the site:deploy goal caused no problems while on the other day the build fails like this: BUILD FAILED File.. file:/opt/tomcat/.maven/plugins/maven-site-plugin-1.5/plugin.jelly Element... attainGoal Line.. 40 Column 42 No goal [xdoc:register-reports] Total time: 12 seconds Finished at: Mon May 03 12:00:55 CEST 2004 I guess, this isn't the real cause of your problem. Is there any other additional error output ? Trying any xdoc goal directly leads to a NoSuchGoalException. The same project's site-goal (and several xdoc goals) build perfectly on my local Win2000 machine, but on the server (Sun Solaris) they won't. This smells like a display problem, which occurs if you are e.g. using fonts on Unix and you neither have a DISPLAY set nor using JDK 1.4 with the headless option. Does the problem occurs if you are running maven from the CLI and you are sure that you can start X programs (like xlock) from the command line (with a valid DISPLAY environment variable set) ? cu... -- ...roland huss consol.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [maven2] Anything Groovy in Maven2?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 06:06 To: Maven Users List Subject: Re: [maven2] Anything Groovy in Maven2? [snip] And the java approach doesn't handle simple stuff like deleting non-empty directories. The real issue is a lack of decent libraries for doing typical build tasks. If java-based plugins are to be a success, we'll need to beef up the existing libraries to handle common tasks. Yep, and that's what Ant is trying to remedy (IMO). Thus it makes sense to me to reuse Ant task from our java plugin. Yes, I know, I'm repeating myself... ;-) I've had Jason's opinion on this idea of reusing Ant tasks from our java plugin but not other's. What do you think guys? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Mysterious no goal [xdoc]
I have a mysterious problem where maven doesn't want to use its xdoc-Plugin (v 1.6 on rc2). On one day invoking the site:deploy goal caused no problems while on the other day the build fails like this: BUILD FAILED File.. file:/opt/tomcat/.maven/plugins/maven-site-plugin-1.5/plugin.jelly Element... attainGoal Line.. 40 Column 42 No goal [xdoc:register-reports] Total time: 12 seconds Finished at: Mon May 03 12:00:55 CEST 2004 I guess, this isn't the real cause of your problem. Is there any other additional error output ? No, this really is all the output I get Trying any xdoc goal directly leads to a NoSuchGoalException. The same project's site-goal (and several xdoc goals) build perfectly on my local Win2000 machine, but on the server (Sun Solaris) they won't. This smells like a display problem, which occurs if you are e.g. using fonts on Unix and you neither have a DISPLAY set nor using JDK 1.4 with the headless option. Does the problem occurs if you are running maven from the CLI and you are sure that you can start X programs (like xlock) from the command line (with a valid DISPLAY environment variable set) ? As this goal _used_ to succeed, I don't think this is the cause. On my Win2000 client calling maven -g lists among all the others the [xdoc] goals, while on that Sun machine maven -g will not mention [xdoc]. Is there any config file that informs maven about the plugins installed? I tried deleting the maven-plugin-xdoc directory in the user's maven/plugin directory and called maven site:deploy once again. While it fails the xdoc-plugin is reinstalled in the user's .maven path. Still clueless, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Mysterious no goal [xdoc]
Have you tried to clean your plugin cache? Michal -Original Message- From: Christian Nill [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 12:32 PM To: Maven Users List Subject: Mysterious no goal [xdoc] Hello, I have a mysterious problem where maven doesn't want to use its xdoc-Plugin (v 1.6 on rc2). On one day invoking the site:deploy goal caused no problems while on the other day the build fails like this: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to set suppressions for checkstyle plugin
I looked into this.. I found the xml file in checkstyle plugin directory in
.plugins. since this is created automatically, I am reluctant to modify
this file. Upgrading to a newer version of checkstyle plugin could
overwrite it. Or upgrading maven, I often delete my .plugins file. Now if
I can put the checkstyle.xml in another directory that would be nice but I
don't see a way to do that. I only see a thing about checkstyle properties
and I don't think that is referring to the XML files. I spent a bit of time
trying it out but couldn't get anywhere with it, so I assumed I was missing
something simple. Now I think everyone just uses the defaults. ;)
A few more plugin properties would be really cool, like:
checkstyle.suppressions.file=${basedir}/checkstyle_suppressions.xml
Michael
-Message d'origine-
De : Vincent Massol [mailto:[EMAIL PROTECTED]
Envoye : lundi 3 mai 2004 11:15
A : 'Maven Users List'
Objet : RE: How to set suppressions for checkstyle plugin
Hi Michael,
You have complete power over the checkstyle.xml file. So you can provide
your own. I think that the suppressions/filter stuff are defined inside
this file so you should be able to control them. Why don't you try it
and tell us how it goes? If required, we can improve the plugin to
support whatever's needed.
Thanks
-Vincent
-Original Message-
From: Michael Mattox [mailto:[EMAIL PROTECTED]
Sent: 03 May 2004 10:54
To: Maven Users List
Subject: How to set suppressions for checkstyle plugin
I'm using the checkstyle plugin and I'd like to suppress some of the
things
it checks. The docs for the plugin talk about a checkstyle properties
but
nothing about supressions. The checkstyle docs talk about a
suppressions.xml but I'm not sure how to configure the maven plugin to
use
the suppressions.xml document. Any ideas?
Regards,
Michael Mattox
--
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]
--
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]
AW: Mysterious no goal [xdoc]
How could it be so simple... I had not deleted the whole cache, just the portions I thought to be relevant... Cleaning the whole cache somehow solved the problem (for now). Thanks, Christian -Ursprüngliche Nachricht- Von: Maczka Michal [mailto:[EMAIL PROTECTED] Gesendet: Montag, 3. Mai 2004 13:21 An: 'Maven Users List' Betreff: RE: Mysterious no goal [xdoc] Have you tried to clean your plugin cache? Michal -Original Message- From: Christian Nill [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 12:32 PM To: Maven Users List Subject: Mysterious no goal [xdoc] Hello, I have a mysterious problem where maven doesn't want to use its xdoc-Plugin (v 1.6 on rc2). On one day invoking the site:deploy goal caused no problems while on the other day the build fails like this: - 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: [java] [ANN] Mevenide move
The following page contains a dead link to a page that should contain eclipse update manager information: http://mevenide.codehaus.org/download.html Not Found The requested URL /mevenide-ui-eclipse/updates/index.html was not found on this server. Andreas Gilles Dodinet wrote: The Mevenide team is proud to announce its move to The Codehaus. Website is now hosted at http://mevenide.codehaus.org/. The Mevenide project's focus is to create IDE tools for the Maven project management and project comprehension tool (http://maven.apache.org). The aim of the project is to make developer's life easier by providing tools for easy creation and maintainance of Maven based projects from the favourite IDE of choice. latest releases can be found at http://dist.codehaus.org/mevenide/release/ -- gd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [maven2] Anything Groovy in Maven2?
Vincent Massol [EMAIL PROTECTED] wrote on 03/05/2004 09:12:42 PM: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 06:06 To: Maven Users List Subject: Re: [maven2] Anything Groovy in Maven2? [snip] And the java approach doesn't handle simple stuff like deleting non-empty directories. The real issue is a lack of decent libraries for doing typical build tasks. If java-based plugins are to be a success, we'll need to beef up the existing libraries to handle common tasks. Yep, and that's what Ant is trying to remedy (IMO). Thus it makes sense to me to reuse Ant task from our java plugin. Yes, I know, I'm repeating myself... ;-) I've had Jason's opinion on this idea of reusing Ant tasks from our java plugin but not other's. What do you think guys? I think it's a viable alternative. I can't see how the current set of Maven2 plugins is an advantage, for all the speed and testability on offer you have to balance that against the effort required to make it user friendly. There are lots of issues Ant covers well I don't think we've even begun to look at. -- dIon Gillard, Multitask Consulting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to set suppressions for checkstyle plugin
See http://maven.apache.org/reference/plugins/checkstyle/properties.html
On that page, check out the entry for maven.checkstyle.properties.
Copy one of the ones found in the plugin and then set that property in
your project.properties,
e.g.
maven.checkstyle.properties=${basedir}/mycheckstyle.xml
HTH,
--
dIon Gillard, Multitask Consulting
Michael Mattox [EMAIL PROTECTED] wrote on 03/05/2004
09:32:18 PM:
I looked into this.. I found the xml file in checkstyle plugin directory
in
.plugins. since this is created automatically, I am reluctant to modify
this file. Upgrading to a newer version of checkstyle plugin could
overwrite it. Or upgrading maven, I often delete my .plugins file. Now
if
I can put the checkstyle.xml in another directory that would be nice but
I
don't see a way to do that. I only see a thing about checkstyle
properties
and I don't think that is referring to the XML files. I spent a bit of
time
trying it out but couldn't get anywhere with it, so I assumed I was
missing
something simple. Now I think everyone just uses the defaults. ;)
A few more plugin properties would be really cool, like:
checkstyle.suppressions.file=${basedir}/checkstyle_suppressions.xml
Michael
-Message d'origine-
De : Vincent Massol [mailto:[EMAIL PROTECTED]
Envoye : lundi 3 mai 2004 11:15
A : 'Maven Users List'
Objet : RE: How to set suppressions for checkstyle plugin
Hi Michael,
You have complete power over the checkstyle.xml file. So you can
provide
your own. I think that the suppressions/filter stuff are defined
inside
this file so you should be able to control them. Why don't you try it
and tell us how it goes? If required, we can improve the plugin to
support whatever's needed.
Thanks
-Vincent
-Original Message-
From: Michael Mattox [mailto:[EMAIL PROTECTED]
Sent: 03 May 2004 10:54
To: Maven Users List
Subject: How to set suppressions for checkstyle plugin
I'm using the checkstyle plugin and I'd like to suppress some of the
things
it checks. The docs for the plugin talk about a checkstyle
properties
but
nothing about supressions. The checkstyle docs talk about a
suppressions.xml but I'm not sure how to configure the maven plugin
to
use
the suppressions.xml document. Any ideas?
Regards,
Michael Mattox
--
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]
--
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven2] Anything Groovy in Maven2?
Trygve Laugstøl [EMAIL PROTECTED] wrote on 03/05/2004
08:43:15 PM:
[snip]
I relly don't thinkt this is so bad. Most of the plugins are much more
than
one liners and as you can see the overhead for each file here is 4
lines.
4 lines, and it's not as functional. The Maven2 clean plugin is over 100
lines of java. The jelly version is just over 10. We're talking orders of
magnitude more code, and the Ant codebase is well tested, as evidenced by
the copying of bizarre code from it into Maven2.
On the upside the plugins will be much easier to test and will run fast
as
hell.
Definitely, but this doesn't help people write them first time.
There are quite a bit of very good file handing methods in commons-io
but
I totally agree with you. We might wan't to create a maven-plugin-utils
library for making plugin development easier.
commons-io is painfully thin on the sort of code you could use in a build
tool. And plexus FileUtils is pretty much just a copy of Ant's code.
Take the jar plugin in Maven2. It's 164 lines of java code.
Compare it to the one in Maven1. It's 295 lines of Jelly.
The Maven2 plugin simply creates a jar file of the current directory
excluding package.html files. It is functionally equivalent to
jar destfile=${outputDirectory}/${jarName}.jar basedir=${basedir}
excludes=**/package.html/
For the extra 131 lines of code in the Maven1 plugin, you get an
incredible amount more including goals to deploy the artifact (deploy,
deploy-snapshot, install, install-snapshot) and a whole lot of
customisation. Let's compare apples to apples.
If someone gave me the choice between 1 line of Ant and 164 lines of
custom Java code with throws Exception throughout and a whole load of
empty catch blocks I know which I'd choose.
--
dIon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to set suppressions for checkstyle plugin
-Original Message-
From: Michael Mattox [mailto:[EMAIL PROTECTED]
Sent: 03 May 2004 13:32
To: Vincent Massol; 'Maven Users List'
Subject: RE: How to set suppressions for checkstyle plugin
I looked into this.. I found the xml file in checkstyle plugin
directory
in
.plugins. since this is created automatically, I am reluctant to
modify
this file. Upgrading to a newer version of checkstyle plugin could
overwrite it.
No, no. You don't get me. You must use the maven.checkstyle.properties
property and provide your own CS configuration. This is the way to use
CS.
Or upgrading maven, I often delete my .plugins file. Now
if
I can put the checkstyle.xml in another directory that would be nice
but I
don't see a way to do that. I only see a thing about checkstyle
properties
and I don't think that is referring to the XML files.
It is! It is badly named as it was named like this when CS was still
using properties file for its configuration... :-)
I spent a bit of
time
trying it out but couldn't get anywhere with it, so I assumed I was
missing
something simple. Now I think everyone just uses the defaults. ;)
Usually people always use the maven.checkstyle.properties property
because everyone wants to tune the checks to his/her own liking! :-)
A few more plugin properties would be really cool, like:
checkstyle.suppressions.file=${basedir}/checkstyle_suppressions.xml
That's possible too. Could you please open a JIRA issue and provide a
patch?
Thanks
-Vincent
Michael
-Message d'origine-
De : Vincent Massol [mailto:[EMAIL PROTECTED]
Envoye : lundi 3 mai 2004 11:15
A : 'Maven Users List'
Objet : RE: How to set suppressions for checkstyle plugin
Hi Michael,
You have complete power over the checkstyle.xml file. So you can
provide
your own. I think that the suppressions/filter stuff are defined
inside
this file so you should be able to control them. Why don't you try
it
and tell us how it goes? If required, we can improve the plugin to
support whatever's needed.
Thanks
-Vincent
-Original Message-
From: Michael Mattox [mailto:[EMAIL PROTECTED]
Sent: 03 May 2004 10:54
To: Maven Users List
Subject: How to set suppressions for checkstyle plugin
I'm using the checkstyle plugin and I'd like to suppress some of
the
things
it checks. The docs for the plugin talk about a checkstyle
properties
but
nothing about supressions. The checkstyle docs talk about a
suppressions.xml but I'm not sure how to configure the maven
plugin to
use
the suppressions.xml document. Any ideas?
Regards,
Michael Mattox
--
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]
--
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]
Re: [maven2] Anything Groovy in Maven2?
On Mon, 2004-05-03 at 07:36, [EMAIL PROTECTED] wrote: If someone gave me the choice between 1 line of Ant and 164 lines of custom Java code with throws Exception throughout and a whole load of empty catch blocks I know which I'd choose. For anyone who wants to try to embed Ant that's your perogative. When you try it, which I'm sure you and Vincent want to you be responsible for all that entails. Up to this point you and Vincent have never been responsible for any of the Ant voodoo required to make Ant work in Maven. I've taken code from the commons, ant and other places in order to provide a small set of plugins that are self-contained, easy to test, easy to embed. The bottom line is that you've never done of the Ant integration and it's not fun and it's not productive. That said I am working with James to extract the Ant embedding solution that is present in groovy so that it can also be used in Maven. But my priority for plugins is clarity, economy of size, speed, having as few dependencies as possible, the ability to work in long-lived process, the ability for plugins to communicate with each other during a long-lived process and code that reflects the simplicity provided by maven's directory structure. As far as the core goes, with it's plugins it will be entirely free from Ant and Jelly. Ant just wasn't design well for embedding and the Jelly/Ant tag library is clear evidence of that as is the groovy ant code. There is nothing that would stop you from from using Ant code but you get the fun of integrating it and then we'll see how much you like it. I personally don't although I am in the process of extracting the ant groovy stuff for use in maven generally that can be used in a layer outside the core. If groovy is integrated into maven2 then we'll get ant integration for free anyway. But a scripting option will be layered upon the core which will be as small, fast as possible with as few dependencies as humanly possible. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
artifact:install and custom jars/EAR type tag
Hey all,
I'm trying to setup WSR's as part of my process, and in trying to remain true to maven
NOT use the ant-copy task. So, I have this:
postGoal name=ejb:install
artifact:install
artifact=${basedir}/target/${pom.artifactId}-WSR-${pom.currentVersion}.wsr
type=wsr
project=${pom}/
/postGoal
The .wsr is a JAR file with a different extension. As found when using the EAR task,
I can not have an EJB/JAR/WSR with the same artifactId even if they have different
extensions, so I thought I could simply change the artifact filepath that it should
copy...but it didn't work.
The file called MYSESSION-WSR-1.0.wsr created (and verified) in the /target directory
is instead changed back to MYSESSION-1.0.wsr when installed into the Repository.
Since the task that creates the EJB and the WSR are the same sub-project (and in fact
the same Maven task), can not (should not?) change the artifactId itself.
In keeping true to maven (i.e. not working around with an ant-copy task), please
advise how to handle this little dilema.
-D
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven2] Anything Groovy in Maven2?
On Mon, 2004-05-03 at 09:00, Incze Lajos wrote: That's why I would consider groovy, as it has an ant builder (almost the same way as jelly has) Not quite but that is exactly piece I'm extract with some advice from Strachan. Once free from groovy dependencies it can be used in groovy obviously, but also in Maven. It could be given back to Ant to make embedding much more simple. Clear evidence of embedding problems is the fact that most IDEs that I have seen the Ant integration for resort to executing Ant from the command line because embedding Ant is like pulling out your own teeth with pliers. If anyone wants to witness the fun take a look at the AntBuilder in groovy: not many folks would have been able to write that beast. Hopefully we can benefit from what Strachan went through writing it and reuse it. , has decent xml processing and building tools (anyway, the same guy stands behind it as behind jelly, and many ideas were transferred) + it's a compilable, interpretable, embeddable terse language. The main drawback for me was that it is in a state of the continous flux. I'll take the AntBuilder for now! :-) incze - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [maven2] Anything Groovy in Maven2?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 1:36 PM To: Maven Users List Subject: Re: [maven2] Anything Groovy in Maven2? Trygve Laugstøl [EMAIL PROTECTED] wrote on 03/05/2004 08:43:15 PM: [snip] I relly don't thinkt this is so bad. Most of the plugins are much more than one liners and as you can see the overhead for each file here is 4 lines. 4 lines, and it's not as functional. The Maven2 clean plugin is over 100 lines of java. The jelly version is just over 10. We're talking orders of magnitude more code, and the Ant codebase is well tested, as evidenced by the copying of bizarre code from it into Maven2. I don't think it will be that bad. Now clean, jar, compile plugin and it's goal can be easly reused in other plugins (e.g you don't have to write the same code for test plugin). My main problem with jelly/current design is that it disallows to reuse the code easly. See how test plugin is similar to java plugin. Duplicated code = no consitency = bad design. More over nobody else was ever reusing our long jelly scripts. With simple Pojo stratgey we might even serve as source of ant tasks! Once we will cover basic functionality (it's not that far from now) we will have our own building blocks which will enable fast development. I believe actually that we will be much faster after passing some point then we are now. On the upside the plugins will be much easier to test and will run fast as hell. Definitely, but this doesn't help people write them first time. Sure. But I don't know a single person which tried to implement something with jelly which was really productive. I dare to say that it will be much faster to write plugins in Java then in jelly. I spent myself hours doing something horribly basic in jelly. And note that number of users of plugins in not comparable with the number of plugin devlopers. Most people just use the plugins and the way it is implemented is not importand for them regards Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [maven2] Anything Groovy in Maven2?
-Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 15:23 To: Maven Users List Subject: Re: [maven2] Anything Groovy in Maven2? On Mon, 2004-05-03 at 07:36, [EMAIL PROTECTED] wrote: If someone gave me the choice between 1 line of Ant and 164 lines of custom Java code with throws Exception throughout and a whole load of empty catch blocks I know which I'd choose. For anyone who wants to try to embed Ant that's your perogative. When you try it, which I'm sure you and Vincent want to you be responsible for all that entails. Up to this point you and Vincent have never been responsible for any of the Ant voodoo required to make Ant work in Maven. True. But that's my point: there's no voodoo if you reuse Ant tasks only (without reusing the Ant engine). I'm doing this in Cactus land and I can tell you I've never had to do any voodoo stuff. It's all plain, clean, easy. Now I admit that I may have been lucky and there may be cases more complex. But I'm positive we can solve them with the Ant team. I've always taken ownership of whatever I've coded so of course I'll take ownership of whatever I code in the future too. Anyway, I'm not talking about developing a framework layer for plugins. I'm simply talking about reusing some Ant tasks from java plugin code. I've taken code from the commons, ant and other places in order to provide a small set of plugins that are self-contained, easy to test, easy to embed. The bottom line is that you've never done of the Ant integration and it's not fun and it's not productive. That said I am working with James to extract the Ant embedding solution that is present in groovy so that it can also be used in Maven. But my priority for plugins is clarity, economy of size, speed, having as few dependencies as possible, the ability to work in long-lived process, the ability for plugins to communicate with each other during a long-lived process and code that reflects the simplicity provided by maven's directory structure. As far as the core goes, with it's plugins it will be entirely free from Ant and Jelly. Ant just wasn't design well for embedding and the Jelly/Ant tag library is clear evidence of that as is the groovy ant code. There is nothing that would stop you from from using Ant code but you get the fun of integrating it and then we'll see how much you like it. I'll take the challenge of writing m2 plugins in java and reusing some Ant tasks. It won't impact any other plugin nor any architectural code. Just a standalone plugin. I personally don't although I am in the process of extracting the ant groovy stuff for use in maven generally that can be used in a layer outside the core. If groovy is integrated into maven2 then we'll get ant integration for free anyway. But a scripting option will be layered upon the core which will be as small, fast as possible with as few dependencies as humanly possible. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [maven2] Anything Groovy in Maven2?
On Mon, 2004-05-03 at 10:00, Vincent Massol wrote: True. But that's my point: there's no voodoo if you reuse Ant tasks only (without reusing the Ant engine). Try the JUnit task or the style task and see if that holds true. It doesn't and I know because I've tried. The surefire plugin I've checked is was the only way I could get Junit tests to run in an embedded environment. I'm doing this in Cactus land and I can tell you I've never had to do any voodoo stuff. It's all plain, clean, easy. Now I admit that I may have been lucky and there may be cases more complex. But I'm positive we can solve them with the Ant team. It's easy to solve, don't code things as Ant tasks. If you're doing something new then there is absolutely no reason to bind your code to Ant. Make POJO and wrap it. I've always taken ownership of whatever I've coded so of course I'll take ownership of whatever I code in the future too. Anyway, I'm not talking about developing a framework layer for plugins. I'm simply talking about reusing some Ant tasks from java plugin code. I'm not going to stop you, but when you run into a classloading problem that is a result of using an Ant task when you could have easily avoided the whole problem by using a POJO and adapting it for different environments I'm going to say I told you so. I'll take the challenge of writing m2 plugins in java and reusing some Ant tasks. It won't impact any other plugin nor any architectural code. Just a standalone plugin. That's fine, you can do whatever you like outside the core. But no core plugins will depend on Ant. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Compile from CVS
Can anyne compile maven from CVS? I assume the answer is yes... But I cenrtainly cannot and I've tried a lot... what special enviroment is required? I try at home and at work (jdk 1.4.2 03) ant 1.61 and 1.60, debian unstable but I get always a failure when 'trying to build maven with itself' anyone had a similar problem or is just me being a total idiot? NOTE: last or is not exclusive, unfortunately for me -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional Solutions Miami +1 305 357 8109 Madrid +34 915 726 763 Buenos Aires: +54 11 43227100 [EMAIL PROTECTED] http://www.technisys.net - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Generate javadoc of multiple projects
Hi there, my project consists of multiple components. For each component I can run maven site:genreate and get a nice site with reports such as javadoc. For the project itself I also use maven to generate the site. Now my question is if there is an easy way to generate a javadoc (and xref) for the main project site containing the code of all components? If not I would also be pleased to hear how to do it complicated :) Thanks a lot, Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Réf. : Generate javadoc of multiple projects
Define the repports you want to include in each sub project and : maven multiproject:site Look at the multiproject plugin for more info Nicolas, Jörg Hohwiller [EMAIL PROTECTED] 03/05/2004 17:53 Veuillez répondre à Maven Users List Pour : Maven Users List [EMAIL PROTECTED] cc : Objet : Generate javadoc of multiple projects Hi there, my project consists of multiple components. For each component I can run maven site:genreate and get a nice site with reports such as javadoc. For the project itself I also use maven to generate the site. Now my question is if there is an easy way to generate a javadoc (and xref) for the main project site containing the code of all components? If not I would also be pleased to hear how to do it complicated :) Thanks a lot, Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven night-build integration
Hi all Just wondering... Is there such a thing as a night-built plugin for maven or any other code base that is ready to be used? I mean by that some scheduled mechanism that could execute a maven build but that will also trap all outputs and make a nice HTML report out of this? thx Eric. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [java] [ANN] Mevenide move
Andreas Guther wrote: The following page contains a dead link to a page that should contain eclipse update manager information: http://mevenide.codehaus.org/download.html thanks for reporting. website will be updated in the coming week(s) to reflect cvs head state. ill take care of that prob in the same time. -- gd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
java.lang.OutOfMemoryError during site:deploy, tar
Greetings -- I'm getting a 'java.lang.OutOfMemoryError' as follows: BUILD FAILED File.. file:/home/build/.maven/plugins/maven-site-plugin-1.5/plugin.jelly Element... tar Line.. 132 Column 91 java.lang.OutOfMemoryError Total time: 25 minutes 3 seconds The maximum Java heap size is set to 1900M via 'MAVEN_OPTS=-Xmx1900m'. It seems odd that I'd run out of memory while executing the tar task. Has anyone seen anything like this? -adrian- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Compile from CVS
Latest from CVS does not compile for me either. Same point of failure - building maven wth itself My traceback suggests plugin-parent-1.0/plugin.jelly has gone missing. Miguel Griffa wrote: Can anyne compile maven from CVS? I assume the answer is yes... But I cenrtainly cannot and I've tried a lot... what special enviroment is required? I try at home and at work (jdk 1.4.2 03) ant 1.61 and 1.60, debian unstable but I get always a failure when 'trying to build maven with itself' anyone had a similar problem or is just me being a total idiot? NOTE: last or is not exclusive, unfortunately for me - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Compile from CVS
Hello Miguel! Nothing special is required. But I think that ANT 1.5.4 is recommended. Can you give us more info about the failure?? Error, Exception, ... Did you checkout the 1.0 Branch or the HEAD one?? #Arnaud. -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 18:03 À : [EMAIL PROTECTED] Objet : Compile from CVS Can anyne compile maven from CVS? I assume the answer is yes... But I cenrtainly cannot and I've tried a lot... what special enviroment is required? I try at home and at work (jdk 1.4.2 03) ant 1.61 and 1.60, debian unstable but I get always a failure when 'trying to build maven with itself' anyone had a similar problem or is just me being a total idiot? NOTE: last or is not exclusive, unfortunately for me -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional Solutions Miami +1 305 357 8109 Madrid +34 915 726 763 Buenos Aires: +54 11 43227100 [EMAIL PROTECTED] http://www.technisys.net - 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: Compile from CVS
This problem was created and corrected yesterday. Did you update maven plugins with the option to create new directories?? Did you checkout/update the maven 1.0 branch? #Arnaud -Message d'origine- De : Gene Hovey [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 19:06 À : Maven Users List Objet : Re: Compile from CVS Latest from CVS does not compile for me either. Same point of failure - building maven wth itself My traceback suggests plugin-parent-1.0/plugin.jelly has gone missing. Miguel Griffa wrote: Can anyne compile maven from CVS? I assume the answer is yes... But I cenrtainly cannot and I've tried a lot... what special enviroment is required? I try at home and at work (jdk 1.4.2 03) ant 1.61 and 1.60, debian unstable but I get always a failure when 'trying to build maven with itself' anyone had a similar problem or is just me being a total idiot? NOTE: last or is not exclusive, unfortunately for me - 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: Compile from CVS
Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Arnaud Heritier wrote: Hello Miguel! Nothing special is required. But I think that ANT 1.5.4 is recommended. Can you give us more info about the failure?? Error, Exception, ... Did you checkout the 1.0 Branch or the HEAD one?? #Arnaud. -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 18:03 À : [EMAIL PROTECTED] Objet : Compile from CVS Can anyne compile maven from CVS? I assume the answer is yes... But I cenrtainly cannot and I've tried a lot... what special enviroment is required? I try at home and at work (jdk 1.4.2 03) ant 1.61 and 1.60, debian unstable but I get always a failure when 'trying to build maven with itself' anyone had a similar problem or is just me being a total idiot? NOTE: last or is not exclusive, unfortunately for me -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional Solutions Miami +1 305 357 8109 Madrid +34 915 726 763 Buenos Aires: +54 11 43227100 [EMAIL PROTECTED] http://www.technisys.net - 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] -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional Solutions Miami +1 305 357 8109 Madrid +34 915 726 763 Buenos Aires: +54 11 43227100 [EMAIL PROTECTED] http://www.technisys.net - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
POSSIBLE BUG: Can't run a SPECIFIC ant tag inside maven
Hi all, Maven can't run replacetoken tag... Maven, Jelly or Werkz seams to delete the content inside replacetoken tag before ant is executed by maven... replace file=teste.txt replacetoken123/replacetoken replacevalue12345/replacevalue /replace With this example String 123 is deleted and ant (executed by maven) can't run because The token attribute must not be an empty string. Is this a Maven problem, Jelly problem or Werkz problem? I need some guidings to continue searching the source of this problem... Thanks, Cassio M. Nosshe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Signing jars before deployment
Does anyone know of a good way to sign jars before deploying them? I've
tried writing the following goal:
goal name=jar:sign
attainGoal name=jar:jar/
signjar jar=${maven.build.dir}/${maven.final.name}.jar
alias=milkshake storepass=frylock/
attainGoal name=jar:deploy/
/goal
Unfortunately, after the jar is signed the deploy goal causes the jar to be
built again, without being signed. I couldn't seem to find any properties
in the jar plugin reference to help with this, so I was wondering if anyone
has any idea what the best approach to this would be. Thanks.
Yoway Buorn
Software Engineer
Imagery Systems Engineering
GENERAL DYNAMICS
Advanced Information Systems
I refuse to tiptoe through life only to arrive safely at death's door. --
???
RE: Compile from CVS
-Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile. I will try to find what the problem is with the HEAD. #Arnaud. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Compile from CVS
Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScriptHousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java:645) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile. I will try to find what the problem is with the HEAD. #Arnaud. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional Solutions Miami +1 305 357 8109 Madrid +34 915 726 763 Buenos Aires: +54 11 43227100 [EMAIL PROTECTED] http://www.technisys.net - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Compile from CVS
Amen. I think I was lulled into believing it's a more mature project than it is by all the Built With Maven graphics on so many Jakarta projects. -Original Message- From: Miguel Griffa [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 1:54 PM To: Maven Users List Subject: Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScriptH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java:64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile. I will try to find what the problem is with the HEAD. #Arnaud. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional Solutions Miami +1 305 357 8109 Madrid +34 915 726 763 Buenos Aires: +54 11 43227100 [EMAIL PROTECTED] http://www.technisys.net - 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: Signing jars before deployment
I just wrote a goal based on the code for jar:deploy. I copied the contents
of the goal and then inserted a signjar right before deploying. If anyone
is interested here is the code:
maven:user-check user=${maven.username}/
attainGoal name=jar:jar/
property name=maven.jar.to.deploy
value=${maven.final.name}.jar/
j:set var=sl value=//
util:replace var=jarToDeploy oldChar=\
newChar=/${maven.build.dir}/${maven.jar.to.deploy}/util:replace
util:replace var=forwardSlashBaseDir oldChar=\ newChar=/
value=${basedir}/
j:if test=${!forwardSlashBaseDir.endsWith('/')}
j:set var=base value=${forwardSlashBaseDir}/ /
/j:if
j:set
var=relativePath${jarToDeploy.substring(base.length())}/j:set
signjar jar=${maven.build.dir}/${maven.jar.to.deploy}
alias=milkshake storepass=frylock/
deploy:artifact
artifact=${relativePath}
type=jars
assureDirectoryCommand=mkdir -p
siteCommand=cd @deployDirectory@; chmod g+w
${maven.jar.to.deploy}; chgrp ${maven.remote.group} ${maven.jar.to.deploy}
/
Also, was wondering if it would make sense to have a property where you
could specify the alias and storepass and if these have been set, have all
the jar goals sign the jar right after generating it. I was thinking maybe
a maven.keystore.alias and maven.keystore.pass and then in the jar goals
just check if any of these are set.
-Original Message-
From: Buorn, Yoway
Sent: Monday, May 03, 2004 11:05 AM
To: [EMAIL PROTECTED]
Subject: Signing jars before deployment
Does anyone know of a good way to sign jars before deploying them? I've
tried writing the following goal:
goal name=jar:sign
attainGoal name=jar:jar/
signjar jar=${maven.build.dir}/${maven.final.name}.jar
alias=milkshake storepass=frylock/
attainGoal name=jar:deploy/
/goal
Unfortunately, after the jar is signed the deploy goal causes the jar to be
built again, without being signed. I couldn't seem to find any properties
in the jar plugin reference to help with this, so I was wondering if anyone
has any idea what the best approach to this would be. Thanks.
Yoway Buorn
Software Engineer
Imagery Systems Engineering
GENERAL DYNAMICS
Advanced Information Systems
I refuse to tiptoe through life only to arrive safely at death's door. --
???
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven and JWSDP-1.3 !!!
Eric,
I don't think this is exactly the answer to your question, but maybe it
could be useful. Below are some snippets from our maven.xml files for the
server and client pieces of a JWSDP JAX-RPC based application. We put all of
the JWSDP JAR files in our local Maven repository and then reference them as
normal dependencies. Our JWSDP JAXRPC-SI specific configuration files are
called config-[web service model name].xml and are referenced as part of our
source resources in project.xml.
Server side:
!--
This goal creates the JAX-RPC model and WSDL files and places them in
the expanded
build webapp directory. It runs after the war:webapp goal from the Maven
war plugin.
--
postGoal name=war:webapp
!-- define JAX-RPC ant task --
ant:taskdef name=wscompile
classname=com.sun.xml.rpc.tools.ant.Wscompile
ant:classpath
ant:path refid=maven.dependency.classpath/
/ant:classpath
/ant:taskdef
!-- loop through the resources in project.xml --
ant:echo message=resources=${pom.build.resources}/
j:forEach var=resource items=${pom.build.resources}
j:set var=directory value=${resource.directory}/
ant:echo message=directory=${directory}/
!-- put XML files from the resource in the 'files' variable --
ant:fileScanner var=files
ant:fileset dir=${directory}
ant:patternset
ant:include name=config-*.xml/
/ant:patternset
/ant:fileset
/ant:fileScanner
!-- loop the files from the resource --
j:forEach var=file items=${files.iterator()}
ant:echo message=file=${file}/
!-- parse out the model name from the config file name --
j:set var=model
value=${file.name.substring(7,file.name.indexOf('.xml'))}-model.gz/
ant:echo message=model=${model}/
ant:mkdir dir=${maven.build.dir}/gen-model/
!-- generate the model and wsdl files for this config file --
ant:wscompile base=${maven.war.webapp.dir}/WEB-INF define=true
verbose=true classpath=${maven.build.dest}
model=${maven.war.webapp.dir}/WEB-INF/${model} config=${file}
ant:classpath
ant:path refid=maven.dependency.classpath/
/ant:classpath
/ant:wscompile
/j:forEach
/j:forEach
!-- update any tokens in web.xml --
ant:replace file=${maven.war.webapp.dir}/WEB-INF/web.xml
ant:replacefilter token=@my.management.port@
value=${my.management.port}/
/ant:replace
/postGoal
!--
This goal creates the JAX-RPC implementation files.
It runs after the war:war goal from the Maven war plugin.
--
postGoal name=war:war
!-- define JAX-RPC ant task --
ant:taskdef name=wsdeploy
classname=com.sun.xml.rpc.tools.ant.Wsdeploy
ant:classpath
ant:path refid=maven.dependency.classpath/
/ant:classpath
/ant:taskdef
ant:mkdir dir=${maven.war.build.dir}/wsdeploy-generated/
ant:move file=${maven.war.build.dir}/${pom.artifactId}.war
tofile=${maven.war.build.dir}/${pom.artifactId}-portable.war/
ant:wsdeploy
inWarFile=${maven.war.build.dir}/${pom.artifactId}-portable.war
outWarFile=${maven.war.build.dir}/${pom.artifactId}.war
tmpDir=${maven.war.build.dir}/wsdeploy-generated keep=true
verbose=true
ant:classpath
ant:path refid=maven.dependency.classpath/
/ant:classpath
/ant:wsdeploy
/postGoal
Client side:
!--
This goal creates the JAX-RPC stubs.
It runs after the java:compile goal from the Maven java plugin.
--
postGoal name=java:compile
!-- define JAX-RPC ant task --
ant:taskdef name=wscompile
classname=com.sun.xml.rpc.tools.ant.Wscompile
ant:classpath
ant:path refid=maven.dependency.classpath/
/ant:classpath
/ant:taskdef
!-- extract the WSDL files from the server WAR file --
j:forEach var=dep items=${pom.dependencies}
j:if test=${dep.artifactId == 'my-server'}
j:set var=my.server.war
value=${maven.repo.local}/${dep.groupId}/${dep.type}s/${dep.artifactId}-${d
ep.version}.${dep.extension}/
ant:unwar src=${my.server.war}
dest=${maven.build.dir}/my-server
ant:patternset
ant:include name=**/*.wsdl/
/ant:patternset
/ant:unwar
/j:if
/j:forEach
!-- copy config files to filter values --
ant:filter token=my.server.war.webinf
value=${maven.build.dir}/my-server/WEB-INF/
ant:copy todir=${maven.build.dir}/conf filtering=true
ant:fileset dir=${maven.src.dir}/conf
ant:include name=config-*.xml/
/ant:fileset
/ant:copy
!-- put config XML files in the 'files' variable --
ant:fileScanner var=files
ant:fileset dir=${maven.build.dir}/conf
ant:patternset
ant:include name=config-*.xml/
/ant:patternset
/ant:fileset
/ant:fileScanner
!-- loop the files --
j:forEach var=file items=${files.iterator()}
ant:echo
RE: Compile from CVS = you must use MAVEN-1_0-BRANCH
Miguel : Did you try to delete your plugins cache directory before the build? Maury and others : Do not use the HEAD branch. I verified and the last modifications aren't applied to the HEAD branch. Sorry for this. It should be clarified. #Arnaud. -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:54 À : Maven Users List Objet : Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScriptH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java:64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile. I will try to find what the problem is with the HEAD. #Arnaud. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional Solutions Miami +1 305 357 8109 Madrid +34 915 726 763 Buenos Aires: +54 11 43227100 [EMAIL PROTECTED] http://www.technisys.net - 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: Compile from CVS
Hi Miguel, Can you try cleaning your maven cache? There might be some leftovers from some previous install there (just remove your .maven/plugins directory). The 1.0 branch is building fine here on my machine and I believe it's also working on Arnaud's machine. Thanks -Vincent -Original Message- From: Miguel Griffa [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 20:54 To: Maven Users List Subject: Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScrip tH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: 64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597 ) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Im pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile. I will try to find what the problem is with the HEAD. #Arnaud. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional Solutions Miami +1 305 357 8109 Madrid +34 915 726 763 Buenos Aires: +54 11 43227100 [EMAIL PROTECTED] http://www.technisys.net - 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: Compile from CVS
Building from HEAD or branch HEAD is reserved to power-users/developers. I'd suggest you use the latest released version (rc2). Otherwise, stop whining and start participating :-) Thanks -Vincent -Original Message- From: Jarrell, Maury [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 20:50 To: 'Maven Users List' Subject: RE: Compile from CVS Amen. I think I was lulled into believing it's a more mature project than it is by all the Built With Maven graphics on so many Jakarta projects. -Original Message- From: Miguel Griffa [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 1:54 PM To: Maven Users List Subject: Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScrip tH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: 64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597 ) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Im pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile. I will try to find what the problem is with the HEAD. #Arnaud. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional Solutions Miami +1 305 357 8109 Madrid +34 915 726 763 Buenos Aires: +54 11 43227100 [EMAIL PROTECTED] http://www.technisys.net - 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: Compile from CVS
Well said :) - Original Message - From: Vincent Massol [EMAIL PROTECTED] To: 'Maven Users List' [EMAIL PROTECTED] Sent: Monday, May 03, 2004 3:28 PM Subject: RE: Compile from CVS Building from HEAD or branch HEAD is reserved to power-users/developers. I'd suggest you use the latest released version (rc2). Otherwise, stop whining and start participating :-) Thanks -Vincent -Original Message- From: Jarrell, Maury [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 20:50 To: 'Maven Users List' Subject: RE: Compile from CVS Amen. I think I was lulled into believing it's a more mature project than it is by all the Built With Maven graphics on so many Jakarta projects. -Original Message- From: Miguel Griffa [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 1:54 PM To: Maven Users List Subject: Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScrip tH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: 64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597 ) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Im pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile. I will try to find what the problem is with the HEAD. #Arnaud. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional Solutions Miami +1 305 357 8109 Madrid +34 915 726 763 Buenos Aires: +54 11 43227100 [EMAIL PROTECTED] http://www.technisys.net - 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: Compile from CVS = you must use MAVEN-1_0-BRANCH
Arnaud, There are 2 CVS modules: - one for maven/ - one for maven-plugins/ For maven/ there are 2 branches: 1.0 one and HEAD For maven-plugins/ there is only HEAD All my changes of this week end were done in the maven-plugins/ and thus on HEAD for that module. That's unless you're talking about other modifications? Thanks -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 21:12 To: 'Maven Users List' Subject: RE: Compile from CVS = you must use MAVEN-1_0-BRANCH Miguel : Did you try to delete your plugins cache directory before the build? Maury and others : Do not use the HEAD branch. I verified and the last modifications aren't applied to the HEAD branch. Sorry for this. It should be clarified. #Arnaud. -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:54 À : Maven Users List Objet : Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScrip tH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: 64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597 ) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Im pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile. I will try to find what the problem is with the HEAD. #Arnaud. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional Solutions Miami +1 305 357 8109 Madrid +34 915 726 763 Buenos Aires: +54 11 43227100 [EMAIL PROTECTED] http://www.technisys.net - 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: Compile from CVS = you must use MAVEN-1_0-BRANCH
-Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 22:44 To: 'Maven Users List'; [EMAIL PROTECTED] Subject: RE: Compile from CVS = you must use MAVEN-1_0-BRANCH Arnaud, There are 2 CVS modules: - one for maven/ - one for maven-plugins/ For maven/ there are 2 branches: 1.0 one and HEAD For maven-plugins/ there is only HEAD All my changes of this week end were done in the maven-plugins/ and thus on HEAD for that module. Ah! That's except for the multiproject exclude... I had forgotten this one. I'll merge it to HEAD. Thanks! -Vincent That's unless you're talking about other modifications? Thanks -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 21:12 To: 'Maven Users List' Subject: RE: Compile from CVS = you must use MAVEN-1_0-BRANCH Miguel : Did you try to delete your plugins cache directory before the build? Maury and others : Do not use the HEAD branch. I verified and the last modifications aren't applied to the HEAD branch. Sorry for this. It should be clarified. #Arnaud. -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:54 À : Maven Users List Objet : Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScrip tH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: 64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597 ) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Im pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile. I will try to find what the problem is with the HEAD. #Arnaud. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional Solutions Miami +1 305 357 8109 Madrid +34 915 726 763 Buenos Aires: +54 11 43227100 [EMAIL PROTECTED] http://www.technisys.net - 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: Compile from CVS
I deserve that. I was venting some frustration is a not-so-helpful way. The truth is that I'd love to participate if I can ever get Maven to successfully do a site:generate. Unfortunately, I was told rc2 won't work because it there are some bugs with some goals that site:generate depends on. I'm not familiar with CVS so I'm on a learning curve there, too. Add to that the fact that I'm behind a firewall and the whole thing has been a succession of roadblocks for me. I'll stop whining and keep working... Thanks for your help, Maury -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 2:28 PM To: 'Maven Users List' Subject: RE: Compile from CVS Building from HEAD or branch HEAD is reserved to power-users/developers. I'd suggest you use the latest released version (rc2). Otherwise, stop whining and start participating :-) Thanks -Vincent -Original Message- From: Jarrell, Maury [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 20:50 To: 'Maven Users List' Subject: RE: Compile from CVS Amen. I think I was lulled into believing it's a more mature project than it is by all the Built With Maven graphics on so many Jakarta projects. -Original Message- From: Miguel Griffa [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 1:54 PM To: Maven Users List Subject: Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScrip tH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: 64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597 ) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Im pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile. I will try to find what the problem is with the HEAD. #Arnaud. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional Solutions Miami +1 305 357 8109 Madrid +34 915 726 763 Buenos Aires: +54 11 43227100 [EMAIL PROTECTED] http://www.technisys.net - 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
RE: Compile from CVS = you must use MAVEN-1_0-BRANCH
Ok. I've committed the change. However, maven HEAD does not build for me too. I get the following error: [...] [echo] | BUILDING MAVEN WITH ITSELF... [echo] | [echo] [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.1-SNAPSHOT [exec] java.io.FileNotFoundException: C:\Documents and Settings\Vincent Massol\.maven\plugins\c lean\project.xml (The system cannot find the path specified) [...] I don't think it's related to my changes of this week end. It must something from before. Brett, any idea? Anyway, as Arnaud said, just use the 1.0 branch for now. Thanks -Vincent -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 22:46 To: 'Maven Users List'; [EMAIL PROTECTED] Subject: RE: Compile from CVS = you must use MAVEN-1_0-BRANCH -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 22:44 To: 'Maven Users List'; [EMAIL PROTECTED] Subject: RE: Compile from CVS = you must use MAVEN-1_0-BRANCH Arnaud, There are 2 CVS modules: - one for maven/ - one for maven-plugins/ For maven/ there are 2 branches: 1.0 one and HEAD For maven-plugins/ there is only HEAD All my changes of this week end were done in the maven-plugins/ and thus on HEAD for that module. Ah! That's except for the multiproject exclude... I had forgotten this one. I'll merge it to HEAD. Thanks! -Vincent That's unless you're talking about other modifications? Thanks -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 21:12 To: 'Maven Users List' Subject: RE: Compile from CVS = you must use MAVEN-1_0-BRANCH Miguel : Did you try to delete your plugins cache directory before the build? Maury and others : Do not use the HEAD branch. I verified and the last modifications aren't applied to the HEAD branch. Sorry for this. It should be clarified. #Arnaud. -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:54 À : Maven Users List Objet : Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScrip tH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: 64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597 ) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Im pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile. I will try to find what the problem is
RE: Compile from CVS
Thanks! I'll try that. I really appreciate your efforts. Ditto to Arnaud who just offered the same to me offline. Now I have to go erase the mean things I wrote about you guys off the bathroom wall... ;-) Thanks again, Maury -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 4:21 PM To: 'Maven Users List' Subject: RE: Compile from CVS Ok, here's some help for you... :-) Follow these steps: 1/ remove your .maven/plugins directory 2/ grab http://cvs.apache.org/~vmassol/maven-rc3-20040503.zip and unzip it 3/ ensure your MAVEN_HOME variable points to the place you've unzipped it 4/ ensure MAVEN_HOME/bin is in your classpath 5/ try it Hope it helps, -Vincent -Original Message- From: Jarrell, Maury [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 23:01 To: 'Maven Users List' Subject: RE: Compile from CVS I deserve that. I was venting some frustration is a not-so-helpful way. The truth is that I'd love to participate if I can ever get Maven to successfully do a site:generate. Unfortunately, I was told rc2 won't work because it there are some bugs with some goals that site:generate depends on. I'm not familiar with CVS so I'm on a learning curve there, too. Add to that the fact that I'm behind a firewall and the whole thing has been a succession of roadblocks for me. I'll stop whining and keep working... Thanks for your help, Maury -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 2:28 PM To: 'Maven Users List' Subject: RE: Compile from CVS Building from HEAD or branch HEAD is reserved to power-users/developers. I'd suggest you use the latest released version (rc2). Otherwise, stop whining and start participating :-) Thanks -Vincent -Original Message- From: Jarrell, Maury [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 20:50 To: 'Maven Users List' Subject: RE: Compile from CVS Amen. I think I was lulled into believing it's a more mature project than it is by all the Built With Maven graphics on so many Jakarta projects. -Original Message- From: Miguel Griffa [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 1:54 PM To: Maven Users List Subject: Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScrip tH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: 64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597 ) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Im pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final
Re: Compile from CVS = you must use MAVEN-1_0-BRANCH
I'm sorry, I feel really stupid here I've done this in a brand new directory cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic/ co -r MAVEN-1_0-BRANCH maven cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic/ co maven-plugins (1.0 branch doesn't seem to be on maven-plugins ) cd maven rm -rf /usr/local/maven-cvs $HOME/.maven/plugins export MAVEN_HOME=/usr/local/maven-cvs ant -d -f build-bootstrap.xml | tee ant.log PS: Thank you guys for being so pacient... It seems to be building now, I got confused about the branches. What I was doing was using 1.0 branch for BOTH project (when it actually doesn't exists on plugins) so there were no plugins to install, stupid me, still, but some info regarding this may be usefull somewhere on the compilation instructions... I think I'll submit a path for the document Arnaud Heritier wrote: Miguel : Did you try to delete your plugins cache directory before the build? Maury and others : Do not use the HEAD branch. I verified and the last modifications aren't applied to the HEAD branch. Sorry for this. It should be clarified. #Arnaud. -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:54 À : Maven Users List Objet : Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScriptH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java:64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile. I will try to find what the problem is with the HEAD. #Arnaud. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven2] Anything Groovy in Maven2?
Jason van Zyl [EMAIL PROTECTED] wrote on 03/05/2004 11:27:06 PM: On Mon, 2004-05-03 at 09:00, Incze Lajos wrote: That's why I would consider groovy, as it has an ant builder (almost the same way as jelly has) Will Groovy end up as an unmaintained project like Jelly has? -- dIon Gillard, Multitask Consulting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven2] Anything Groovy in Maven2?
On Mon, 2004-05-03 at 17:39, [EMAIL PROTECTED] wrote: Jason van Zyl [EMAIL PROTECTED] wrote on 03/05/2004 11:27:06 PM: Will Groovy end up as an unmaintained project like Jelly has? Unlikely now that it has been accepted as a JSR. But if we're going to pick an Ant bridge to maintain the one in Groovy right now is in better shape. As it stands now Mauro Televi and myself are going to take the AntBuilder and extract it from groovy so hopefully in that form it can be used within Groovy and we can wrap it for use in maven1 which means we'll have updated Ant support. And we can also use it in maven2 which is also good. -- dIon Gillard, Multitask Consulting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Compile from CVS
Trying to be a good citizen http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1257 Thank you all Vincent Massol wrote: Hi Miguel, Can you try cleaning your maven cache? There might be some leftovers from some previous install there (just remove your .maven/plugins directory). The 1.0 branch is building fine here on my machine and I believe it's also working on Arnaud's machine. Thanks -Vincent -Original Message- From: Miguel Griffa [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 20:54 To: Maven Users List Subject: Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScrip tH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: 64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597 ) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Im pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile. I will try to find what the problem is with the HEAD. -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional Solutions Miami +1 305 357 8109 Madrid +34 915 726 763 Buenos Aires: +54 11 43227100 [EMAIL PROTECTED] http://www.technisys.net - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Mevenide move
The Mevenide team is proud to announce its move to The Codehaus. Website is now hosted at http://mevenide.codehaus.org/. Did you typo the project name this time too??? :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Compile from CVS
Thanks to you. #Arnaud -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : mardi 4 mai 2004 00:22 À : Maven Users List Objet : Re: Compile from CVS Trying to be a good citizen http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1257 Thank you all Vincent Massol wrote: Hi Miguel, Can you try cleaning your maven cache? There might be some leftovers from some previous install there (just remove your .maven/plugins directory). The 1.0 branch is building fine here on my machine and I believe it's also working on Arnaud's machine. Thanks -Vincent -Original Message- From: Miguel Griffa [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 20:54 To: Maven Users List Subject: Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScrip tH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: 64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597 ) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Im pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile. I will try to find what the problem is with the HEAD. -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional Solutions Miami +1 305 357 8109 Madrid +34 915 726 763 Buenos Aires: +54 11 43227100 [EMAIL PROTECTED] http://www.technisys.net - 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: Compile from CVS
I'm curious about these RC2 site:generate problems? I deserve that. I was venting some frustration is a not-so-helpful way. The truth is that I'd love to participate if I can ever get Maven to successfully do a site:generate. Unfortunately, I was told rc2 won't work because it there are some bugs with some goals that site:generate depends on. I'm not familiar with CVS so I'm on a learning curve there, too. Add to that the fact that I'm behind a firewall and the whole thing has been a succession of roadblocks for me. I'll stop whining and keep working... Thanks for your help, Maury
RE: plugins / root classloader
There are other ways to do this 99% of the time. Can you bundle up the whole plugin source and post it to JIRA? I'd like to fix this before RC3. - Brett -Original Message- From: Nathan Coast [mailto:[EMAIL PROTECTED] Sent: Tuesday, 4 May 2004 11:19 AM To: [EMAIL PROTECTED] Subject: plugins / root classloader Hi, I have a plugin that used to work with rc1 but now fails with a no class def error with rc2. The plugin has classes that extend junit classes. The plugin has a dependency like this: dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version properties classloaderroot/classloader /properties typejar/type /dependency without the classloader root element, the plugin fails with NoClassDef on the junit classes. The plugin has classes which are needed by junit at runtime. The classes are in plugins/maven-junitejb-plugin-1.0/com/foo/bar but maven is unable to locate them. What do I have to do in order to make the classes within the plugin available at plugin execution? thanks Nathan __ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
plugins / root classloader
Hi, I have a plugin that used to work with rc1 but now fails with a no class def error with rc2. The plugin has classes that extend junit classes. The plugin has a dependency like this: dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version properties classloaderroot/classloader /properties typejar/type /dependency without the classloader root element, the plugin fails with NoClassDef on the junit classes. The plugin has classes which are needed by junit at runtime. The classes are in plugins/maven-junitejb-plugin-1.0/com/foo/bar but maven is unable to locate them. What do I have to do in order to make the classes within the plugin available at plugin execution? thanks Nathan __ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE: POSSIBLE BUG: Can't run a SPECIFIC ant tag inside maven
replacetoken is a subtag of replace ant task. The tag replacetoken exists in ant 1.5.3... I've tested with this ant version in my build.xml and works: target name=teste4 replace file=teste.txt replacetoken123/replacetoken replacevalue12345/replacevalue /replace /target but with maven 1.0-rc2 (maven.xml), with the same code: goal name=teste4 replace file=teste.txt replacetoken123/replacetoken replacevalue12345/replacevalue /replace /goal ...does not work!!! Could you test that, please? It would take 5 min or less... :-) -Cassio Monday, May 3, 2004, 8:13:28 PM, you wrote: BP What version of Ant has this tag? We only use 1.5.3-1. BP - Brett -Original Message- From: Cassio [mailto:[EMAIL PROTECTED] Sent: Tuesday, 4 May 2004 3:50 AM To: [EMAIL PROTECTED] Subject: POSSIBLE BUG: Can't run a SPECIFIC ant tag inside maven Hi all, Maven can't run replacetoken tag... Maven, Jelly or Werkz seams to delete the content inside replacetoken tag before ant is executed by maven... replace file=teste.txt replacetoken123/replacetoken replacevalue12345/replacevalue /replace With this example String 123 is deleted and ant (executed by maven) can't run because The token attribute must not be an empty string. Is this a Maven problem, Jelly problem or Werkz problem? I need some guidings to continue searching the source of this problem... Thanks, Cassio M. Nosshe - 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: java.lang.OutOfMemoryError during site:deploy, tar
Interesting - how big is the final created tar? I have generated some huge sites without problems. Some more information on OS, etc. would be helpful. Thanks, - Brett -Original Message- From: Kalaveshi, Adrian [mailto:[EMAIL PROTECTED] Sent: Tuesday, 4 May 2004 3:04 AM To: '[EMAIL PROTECTED]' Subject: java.lang.OutOfMemoryError during site:deploy, tar Greetings -- I'm getting a 'java.lang.OutOfMemoryError' as follows: BUILD FAILED File.. file:/home/build/.maven/plugins/maven-site-plugin-1.5/plugin.j elly Element... tar Line.. 132 Column 91 java.lang.OutOfMemoryError Total time: 25 minutes 3 seconds The maximum Java heap size is set to 1900M via 'MAVEN_OPTS=-Xmx1900m'. It seems odd that I'd run out of memory while executing the tar task. Has anyone seen anything like this? -adrian- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: POSSIBLE BUG: Can't run a SPECIFIC ant tag inside maven
What version of Ant has this tag? We only use 1.5.3-1. - Brett -Original Message- From: Cassio [mailto:[EMAIL PROTECTED] Sent: Tuesday, 4 May 2004 3:50 AM To: [EMAIL PROTECTED] Subject: POSSIBLE BUG: Can't run a SPECIFIC ant tag inside maven Hi all, Maven can't run replacetoken tag... Maven, Jelly or Werkz seams to delete the content inside replacetoken tag before ant is executed by maven... replace file=teste.txt replacetoken123/replacetoken replacevalue12345/replacevalue /replace With this example String 123 is deleted and ant (executed by maven) can't run because The token attribute must not be an empty string. Is this a Maven problem, Jelly problem or Werkz problem? I need some guidings to continue searching the source of this problem... Thanks, Cassio M. Nosshe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Compile from CVS
-Original Message- From: Jarrell, Maury [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 23:31 To: 'Maven Users List' Subject: RE: Compile from CVS Thanks! I'll try that. I really appreciate your efforts. Ditto to Arnaud who just offered the same to me offline. Now I have to go erase the mean things I wrote about you guys off the bathroom wall... ;-) :-) -Vincent Thanks again, Maury -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 4:21 PM To: 'Maven Users List' Subject: RE: Compile from CVS Ok, here's some help for you... :-) Follow these steps: 1/ remove your .maven/plugins directory 2/ grab http://cvs.apache.org/~vmassol/maven-rc3-20040503.zip and unzip it 3/ ensure your MAVEN_HOME variable points to the place you've unzipped it 4/ ensure MAVEN_HOME/bin is in your classpath 5/ try it Hope it helps, -Vincent -Original Message- From: Jarrell, Maury [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 23:01 To: 'Maven Users List' Subject: RE: Compile from CVS I deserve that. I was venting some frustration is a not-so-helpful way. The truth is that I'd love to participate if I can ever get Maven to successfully do a site:generate. Unfortunately, I was told rc2 won't work because it there are some bugs with some goals that site:generate depends on. I'm not familiar with CVS so I'm on a learning curve there, too. Add to that the fact that I'm behind a firewall and the whole thing has been a succession of roadblocks for me. I'll stop whining and keep working... Thanks for your help, Maury -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 2:28 PM To: 'Maven Users List' Subject: RE: Compile from CVS Building from HEAD or branch HEAD is reserved to power-users/developers. I'd suggest you use the latest released version (rc2). Otherwise, stop whining and start participating :-) Thanks -Vincent -Original Message- From: Jarrell, Maury [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 20:50 To: 'Maven Users List' Subject: RE: Compile from CVS Amen. I think I was lulled into believing it's a more mature project than it is by all the Built With Maven graphics on so many Jakarta projects. -Original Message- From: Miguel Griffa [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 1:54 PM To: Maven Users List Subject: Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScrip tH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: 64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597 ) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Im pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d
RE: [maven2] Anything Groovy in Maven2?
Maczka Michal [EMAIL PROTECTED] wrote on 03/05/2004 11:31:21 PM: I don't think it will be that bad. Now clean, jar, compile plugin and it's goal can be easly reused in other plugins (e.g you don't have to write the same code for test plugin). The same can be said for the jelly code. My main problem with jelly/current design is that it disallows to reuse the code easly. See how test plugin is similar to java plugin. That can quite easily be fixed by creating a taglib as you know. Duplicated code = no consitency = bad design. More over nobody else was ever reusing our long jelly scripts. The whole point of maven is that you don't need to change the code, though. With simple Pojo stratgey we might even serve as source of ant tasks! That'd be a great strategy. Extract the ant tasks into POJOs. Sure. But I don't know a single person which tried to implement something with jelly which was really productive. I dare to say that it will be much faster to write plugins in Java then in jelly. I spent myself hours doing something horribly basic in jelly. And note that number of users of plugins in not comparable with the number of plugin devlopers. Most people just use the plugins and the way it is implemented is not importand for them It's long been possible to write beans in jelly and call them from plugins, as you know. why do so few people do it? -- dIon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Compile from CVS
Ok, here's some help for you... :-) Follow these steps: 1/ remove your .maven/plugins directory 2/ grab http://cvs.apache.org/~vmassol/maven-rc3-20040503.zip and unzip it 3/ ensure your MAVEN_HOME variable points to the place you've unzipped it 4/ ensure MAVEN_HOME/bin is in your classpath 5/ try it Hope it helps, -Vincent -Original Message- From: Jarrell, Maury [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 23:01 To: 'Maven Users List' Subject: RE: Compile from CVS I deserve that. I was venting some frustration is a not-so-helpful way. The truth is that I'd love to participate if I can ever get Maven to successfully do a site:generate. Unfortunately, I was told rc2 won't work because it there are some bugs with some goals that site:generate depends on. I'm not familiar with CVS so I'm on a learning curve there, too. Add to that the fact that I'm behind a firewall and the whole thing has been a succession of roadblocks for me. I'll stop whining and keep working... Thanks for your help, Maury -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 2:28 PM To: 'Maven Users List' Subject: RE: Compile from CVS Building from HEAD or branch HEAD is reserved to power-users/developers. I'd suggest you use the latest released version (rc2). Otherwise, stop whining and start participating :-) Thanks -Vincent -Original Message- From: Jarrell, Maury [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 20:50 To: 'Maven Users List' Subject: RE: Compile from CVS Amen. I think I was lulled into believing it's a more mature project than it is by all the Built With Maven graphics on so many Jakarta projects. -Original Message- From: Miguel Griffa [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 1:54 PM To: Maven Users List Subject: Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScrip tH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: 64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597 ) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Im pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile? Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile. I will try to find what the problem is with the HEAD. #Arnaud. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Miguel Griffa Software Architect Technisys.NET The First Digital e-nabler Transactional
native plugin
Does anyone know where to download the latest version of the native plugin, or a repository in whcih it may reside, its not on ibiblio as far as I can tell. If it were just for myself I would grab it from cvs and use that but I have a pretty decent sized team which is continually growing and do not want to get into the habit of supplying plugins that should be up on ibib. thanks R-- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Signing jars before deployment
On Monday 03 May 2004 20:55, [EMAIL PROTECTED] wrote: I just wrote a goal based on the code for jar:deploy. I copied the contents of the goal and then inserted a signjar right before deploying. If anyone is interested here is the code: Hi I don;t know what you are trying but have you looked at the jnlp (for java web start) plugin? http://maven.apache.org/reference/plugins/jnlp/ it creates a singed jar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [maven2] Anything Groovy in Maven2?
-Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 17:11 To: Maven Users List Subject: RE: [maven2] Anything Groovy in Maven2? On Mon, 2004-05-03 at 10:00, Vincent Massol wrote: True. But that's my point: there's no voodoo if you reuse Ant tasks only (without reusing the Ant engine). Try the JUnit task or the style task and see if that holds true. It doesn't and I know because I've tried. The surefire plugin I've checked is was the only way I could get Junit tests to run in an embedded environment. funnily, I'm running the JUnit task in embedded mode for the abbot plugin I've checked in a few days ago and believe it or not... it works :-) Here's the url: http://tinyurl.com/2uy9b (look at the executeAntJunitTestRunner method). [snip] Anyway, let's stop the words and let's wait for some action! I'll start working on some java plugin as a proof of concept when I get back from TSSS2004. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: plugins / root classloader
sure, which project in jira? core? plugin manager? fyi, my workaround is to bundle the plugin classes in a jar and refer to them as a dependency for the plugin with root classloader. cheers Nathan --- Brett Porter [EMAIL PROTECTED] wrote: There are other ways to do this 99% of the time. Can you bundle up the whole plugin source and post it to JIRA? I'd like to fix this before RC3. - Brett -Original Message- From: Nathan Coast [mailto:[EMAIL PROTECTED] Sent: Tuesday, 4 May 2004 11:19 AM To: [EMAIL PROTECTED] Subject: plugins / root classloader Hi, I have a plugin that used to work with rc1 but now fails with a no class def error with rc2. The plugin has classes that extend junit classes. The plugin has a dependency like this: dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version properties classloaderroot/classloader /properties typejar/type /dependency without the classloader root element, the plugin fails with NoClassDef on the junit classes. The plugin has classes which are needed by junit at runtime. The classes are in plugins/maven-junitejb-plugin-1.0/com/foo/bar but maven is unable to locate them. What do I have to do in order to make the classes within the plugin available at plugin execution? thanks Nathan __ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: plugins / root classloader
Right, that's a good workaround. Add to maven, component plugin manager. I'll see if there is an alternative. Thanks, Brett -Original Message- From: Nathan Coast [mailto:[EMAIL PROTECTED] Sent: Tuesday, 4 May 2004 1:46 PM To: Maven Users List Subject: RE: plugins / root classloader sure, which project in jira? core? plugin manager? fyi, my workaround is to bundle the plugin classes in a jar and refer to them as a dependency for the plugin with root classloader. cheers Nathan --- Brett Porter [EMAIL PROTECTED] wrote: There are other ways to do this 99% of the time. Can you bundle up the whole plugin source and post it to JIRA? I'd like to fix this before RC3. - Brett -Original Message- From: Nathan Coast [mailto:[EMAIL PROTECTED] Sent: Tuesday, 4 May 2004 11:19 AM To: [EMAIL PROTECTED] Subject: plugins / root classloader Hi, I have a plugin that used to work with rc1 but now fails with a no class def error with rc2. The plugin has classes that extend junit classes. The plugin has a dependency like this: dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version properties classloaderroot/classloader /properties typejar/type /dependency without the classloader root element, the plugin fails with NoClassDef on the junit classes. The plugin has classes which are needed by junit at runtime. The classes are in plugins/maven-junitejb-plugin-1.0/com/foo/bar but maven is unable to locate them. What do I have to do in order to make the classes within the plugin available at plugin execution? thanks Nathan __ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Compile from CVS = you must use MAVEN-1_0-BRANCH
Same error for me. Arnaud -Message d'origine- De : Vincent Massol [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 23:10 À : 'Maven Users List' Objet : RE: Compile from CVS = you must use MAVEN-1_0-BRANCH Ok. I've committed the change. However, maven HEAD does not build for me too. I get the following error: [...] [echo] | BUILDING MAVEN WITH ITSELF... [echo] | [echo] [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.1-SNAPSHOT [exec] java.io.FileNotFoundException: C:\Documents and Settings\Vincent Massol\.maven\plugins\c lean\project.xml (The system cannot find the path specified) [...] I don't think it's related to my changes of this week end. It must something from before. Brett, any idea? Anyway, as Arnaud said, just use the 1.0 branch for now. Thanks -Vincent -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 22:46 To: 'Maven Users List'; [EMAIL PROTECTED] Subject: RE: Compile from CVS = you must use MAVEN-1_0-BRANCH -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 22:44 To: 'Maven Users List'; [EMAIL PROTECTED] Subject: RE: Compile from CVS = you must use MAVEN-1_0-BRANCH Arnaud, There are 2 CVS modules: - one for maven/ - one for maven-plugins/ For maven/ there are 2 branches: 1.0 one and HEAD For maven-plugins/ there is only HEAD All my changes of this week end were done in the maven-plugins/ and thus on HEAD for that module. Ah! That's except for the multiproject exclude... I had forgotten this one. I'll merge it to HEAD. Thanks! -Vincent That's unless you're talking about other modifications? Thanks -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 21:12 To: 'Maven Users List' Subject: RE: Compile from CVS = you must use MAVEN-1_0-BRANCH Miguel : Did you try to delete your plugins cache directory before the build? Maury and others : Do not use the HEAD branch. I verified and the last modifications aren't applied to the HEAD branch. Sorry for this. It should be clarified. #Arnaud. -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:54 À : Maven Users List Objet : Re: Compile from CVS Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task.. [exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScrip tH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: 64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597 ) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Im pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) Arnaud Heritier wrote: -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : lundi 3 mai 2004 20:01 À : Maven Users List Objet : Re: Compile from CVS Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d ) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 Shouldn't the head version compile?
RE: JUnit and getResourceAsStream
The second possibility is configuration. I also had some problems locating files in Junit tests because of forking issues. If the above does not help, try creating a 'project.properties' file next to your 'project.xml' file and include this: # Forked JUnit because of some problems involving classloading of resources in test scenarios. maven.junit.fork=true Hope this helps. Well it just did! Thanks for your post. Best Regards, -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Mevenide move
Chad Woolley wrote: The Mevenide team is proud to announce its move to The Codehaus. Website is now hosted at http://mevenide.codehaus.org/. Did you typo the project name this time too??? :) hehe good one ;) you know how history bites us ;) -- gd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
