RE: cvs commit: maven-plugins/sea plugin.jelly

2003-11-27 Thread Vincent Massol
dIon, Are you sure it is unnecessary? This is inside a tag and thus the tag will be executed in *another* context. Thus if it needs to find resources from the plugin dir, it will need to use the getPluginContext I think... I had the same issue with some of my plugins in the past. Thanks -Vincent

RE: [pom3/4] compatibilities element.

2003-11-27 Thread Vincent Massol
Here is what I said in an email: --- As requested by dIon here's a summary of the 2 proposals we have for introducing compatibility definition in the POM for plugins (i.e. what version of Maven a given plugin is compatible with). Proposal 1: * Add the following to project.xml (this is

[Plugin plugin] Changing plugin:deploy

2003-11-27 Thread Vincent Massol
Hi, I'd like to change the plugin:deploy goal so that it deploys the plugin on the remote repo instead of simply unpacking a plugin jar in the local plugin cache (if this feature is used by anyone, I can rename the goal to plugin:unpack) Ok? Thanks -Vincent

Re: [Plugin plugin] Changing plugin:deploy

2003-11-27 Thread Emmanuel Venisse
+1 for rename actual deploy to unpack +1 for deploy on remote repo Emmanuel - Original Message - From: Vincent Massol [EMAIL PROTECTED] To: 'Maven Developers List' [EMAIL PROTECTED] Sent: Thursday, November 27, 2003 9:30 AM Subject: [Plugin plugin] Changing plugin:deploy Hi, I'd

[jira] Created: (MAVEN-1057) Choose JDK used to run unit tests?

2003-11-27 Thread jira
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1057 Here is an overview of the issue:

[jira] Updated: (MAVEN-1057) Choose JDK used to run unit tests?

2003-11-27 Thread jira
The following issue has been updated: Updater: Eric Berenguier (mailto:[EMAIL PROTECTED]) Date: Thu, 27 Nov 2003 5:02 AM Comment: This patch solves this issue. it adds a maven.junit.jvm properties. This properties defaults to java which is the default value for the junit jvm

[jira] Created: (MAVEN-1058) [PATCH] CLI : multiple -Dprop=value not allowed

2003-11-27 Thread jira
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1058 Here is an overview of the issue:

[jira] Updated: (MAVEN-1058) [PATCH] CLI : multiple -Dprop=value not allowed

2003-11-27 Thread jira
The following issue has been updated: Updater: Jörg Schaible (mailto:[EMAIL PROTECTED]) Date: Thu, 27 Nov 2003 6:31 AM Comment: fix OptionBuilder usage in CLIManager.java Changes: Attachment changed to CLIManager.java.diff

patch : choose jdk to run unit test

2003-11-27 Thread Eric Berenguier
Hello, I've just submitted a small patch to jira that allows to choose which JVM is used to run unit tests : http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1057 I hope it doesn't have any side effect because it feeds a default value for the jvm attribute in junit ant task. Eric

maven cli build trouble

2003-11-27 Thread Jörg Schaible
Hello Maven developers, I have currently trouble with the cli of Maven and the Maven build itself: === snip $ maven -Dmaven.genapp.template.repository=C:/Work/buildsystem/templates -Dmaven.genapp.template.name=Elsag-Solutions Application

[jira] Created: (MAVEN-1059) Upload phoenix 4.0.4 jars

2003-11-27 Thread jira
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1059 Here is an overview of the issue:

Re: [Plugin plugin] Changing plugin:deploy

2003-11-27 Thread Rafal Krzewski
Emmanuel Venisse wrote: +1 for rename actual deploy to unpack +1 for deploy on remote repo ditto. Did you notice that the plugin:install goal also does something different than (jar|war|ear):install goals? What I'd like best would be full suite of deployment goals (install, install-snapshot,

RE: jelly script woes

2003-11-27 Thread Jörg Schaible
[EMAIL PROTECTED] wrote on Thursday, November 27, 2003 7:58 AM: Jörg Schaible [EMAIL PROTECTED] wrote on 26/11/2003 11:49:11 PM: Hello, currently I fight with the Jelly script for a plugin extension and I got stuck. See the following example: Having following properties: all=y,x

RE: [Plugin plugin] Changing plugin:deploy

2003-11-27 Thread Vincent Massol
-Original Message- From: Rafal Krzewski [mailto:[EMAIL PROTECTED] Sent: 27 November 2003 15:32 To: Maven Developers List Subject: Re: [Plugin plugin] Changing plugin:deploy Emmanuel Venisse wrote: +1 for rename actual deploy to unpack +1 for deploy on remote repo ditto.

cvs commit: maven-plugins/jboss plugin.properties project.xml plugin.jelly

2003-11-27 Thread vmassol
vmassol 2003/11/27 09:05:21 Modified:jboss/xdocs properties.xml changes.xml jbossplugin.properties project.xml plugin.jelly Log: Fixed deploy/undeploy URLs for JBoss 3.2. Applied patch from Archimedes. Not tested. We really ought to create some tests for this

[jira] Commented: (MPJBOSS-3) jboss 3.2 JXM deploy/undeploy URL is slightly different from what's in jboss plugin project.properties

2003-11-27 Thread jira
The following comment has been added to this issue: Author: Vincent Massol Created: Thu, 27 Nov 2003 11:12 AM Body: Applied. Could you please test it? I've modified a few things from your patch: - put the version at the end of the properties to be more in line with the naming

RE: [Plugin plugin] Changing plugin:deploy

2003-11-27 Thread Vincent Massol
-Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: 27 November 2003 17:09 To: Maven Developers List Subject: Re: [Plugin plugin] Changing plugin:deploy On Thu, 2003-11-27 at 03:30, Vincent Massol wrote: Hi, I'd like to change the plugin:deploy goal so

[jira] Commented: (MPJBOSS-3) jboss 3.2 JXM deploy/undeploy URL is slightly different from what's in jboss plugin project.properties

2003-11-27 Thread jira
The following comment has been added to this issue: Author: Archimedes Trajano Created: Thu, 27 Nov 2003 1:46 PM Body: Tested. You may close it now. - View the issue:

[jira] Commented: (MPJBOSS-3) jboss 3.2 JXM deploy/undeploy URL is slightly different from what's in jboss plugin project.properties

2003-11-27 Thread jira
The following comment has been added to this issue: Author: Archimedes Trajano Created: Thu, 27 Nov 2003 1:48 PM Body: Actually one thing we should do, but need to create another defect for this is to make jboss:start terminate but leave the app server running. Not really sure

[jira] Closed: (MPJBOSS-3) jboss 3.2 JXM deploy/undeploy URL is slightly different from what's in jboss plugin project.properties

2003-11-27 Thread jira
Message: The following issue has been closed. Resolver: Vincent Massol Date: Thu, 27 Nov 2003 1:59 PM cool. BTW, what you describe is exactly what cactus does. It's possible to reuse Cactus's runservertests task. See

cvs commit: maven-plugins/clover/src/plugin-test - New directory

2003-11-27 Thread vmassol
vmassol 2003/11/27 12:19:33 maven-plugins/clover/src/plugin-test - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/clover/src - New directory

2003-11-27 Thread vmassol
vmassol 2003/11/27 12:19:33 maven-plugins/clover/src - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/clover/src/plugin-test/src/main/org/apache - New directory

2003-11-27 Thread vmassol
vmassol 2003/11/27 12:19:33 maven-plugins/clover/src/plugin-test/src/main/org/apache - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/clover/src/plugin-test/src/test/org/apache/maven - New directory

2003-11-27 Thread vmassol
vmassol 2003/11/27 12:19:33 maven-plugins/clover/src/plugin-test/src/test/org/apache/maven - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/clover/src/plugin-test/src/test/org/apache - New directory

2003-11-27 Thread vmassol
vmassol 2003/11/27 12:19:33 maven-plugins/clover/src/plugin-test/src/test/org/apache - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/clover/src/plugin-test/src/test/org/apache/maven/clover/test - New directory

2003-11-27 Thread vmassol
vmassol 2003/11/27 12:19:33 maven-plugins/clover/src/plugin-test/src/test/org/apache/maven/clover/test - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/clover/src/plugin-test/src/main/org/apache/maven/clover/test - New directory

2003-11-27 Thread vmassol
vmassol 2003/11/27 12:19:33 maven-plugins/clover/src/plugin-test/src/main/org/apache/maven/clover/test - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/clover/src/plugin-test/src/main - New directory

2003-11-27 Thread vmassol
vmassol 2003/11/27 12:19:33 maven-plugins/clover/src/plugin-test/src/main - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/clover/src/plugin-test/src/test - New directory

2003-11-27 Thread vmassol
vmassol 2003/11/27 12:19:33 maven-plugins/clover/src/plugin-test/src/test - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/clover/src/plugin-test/src/main/org/apache/maven/clover - New directory

2003-11-27 Thread vmassol
vmassol 2003/11/27 12:19:33 maven-plugins/clover/src/plugin-test/src/main/org/apache/maven/clover - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/clover/src/plugin-test/src/main/org - New directory

2003-11-27 Thread vmassol
vmassol 2003/11/27 12:19:33 maven-plugins/clover/src/plugin-test/src/main/org - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/clover/src/plugin-test/src/main/org/apache/maven - New directory

2003-11-27 Thread vmassol
vmassol 2003/11/27 12:19:33 maven-plugins/clover/src/plugin-test/src/main/org/apache/maven - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/clover/src/plugin-test/src/test/org/apache/maven/clover - New directory

2003-11-27 Thread vmassol
vmassol 2003/11/27 12:19:33 maven-plugins/clover/src/plugin-test/src/test/org/apache/maven/clover - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/clover/src/plugin-test/src/test/org - New directory

2003-11-27 Thread vmassol
vmassol 2003/11/27 12:19:33 maven-plugins/clover/src/plugin-test/src/test/org - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/clover/src/plugin-test/src/test/org/apache/maven/clover/test SimpleTest.java

2003-11-27 Thread vmassol
vmassol 2003/11/27 12:19:46 Added: clover/src/plugin-test project.properties project.xml maven.xml clover/src/plugin-test/src/main/org/apache/maven/clover/test Simple.java

Javadoc Linking

2003-11-27 Thread Alain Javier Guarnieri del Gesu
Dion? I've fixed the problem I was having with Javadoc linking. I create a temporary directory and copy the source fields specified by the includes and excludes. I then run Javadoc on that directory. It works well. Interested? I can JIRA and patch. -- Alain Javier Guarnieri del Gesu - [EMAIL

[jira] Closed: (MAVEN-1058) [PATCH] CLI : multiple -Dprop=value not allowed

2003-11-27 Thread jira
Message: The following issue has been closed. Resolver: dion gillard Date: Thu, 27 Nov 2003 5:20 PM Bad report - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1058 Here is an

Re: [Plugin plugin] Changing plugin:deploy

2003-11-27 Thread dion
+1. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Vincent Massol [EMAIL PROTECTED] wrote on 27/11/2003 07:30:23 PM: Hi, I'd like to change the plugin:deploy goal so that it deploys the plugin on the remote repo instead of simply unpacking a plugin

Re: maven cli build trouble

2003-11-27 Thread dion
Jörg Schaible [EMAIL PROTECTED] wrote on 28/11/2003 12:39:13 AM: Hello Maven developers, I have currently trouble with the cli of Maven and the Maven build itself: === snip $ maven -Dmaven.genapp.template.repository=C:/Work/buildsystem/templates -

RE: jelly script woes

2003-11-27 Thread dion
Jörg Schaible [EMAIL PROTECTED] wrote on 28/11/2003 02:17:16 AM: [snip] So is there any solution to create such assembled variables? Use something like this: j:set var=variablejdbc.database.${jdbc.os}/j:set j:set var=dbdatabase value=

status of MAVEN_1-0_BRANCH?

2003-11-27 Thread dion
I've tried to bootstrap 1.0 and it fails while building the plugins, with: [exec] + [exec] BUILD FAILED [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] | Building Maven Announcement plugin [exec] | Memory: 6M/8M [exec] at

[jira] Created: (MPEJB-2) ejb:install should also depend and install client

2003-11-27 Thread jira
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPEJB-2 Here is an overview of the issue:

[jira] Commented: (MPARTIFACT-2) Add tag attribute to relax the restriction on artifact type and file extension association

2003-11-27 Thread jira
The following comment has been added to this issue: Author: Archimedes Trajano Created: Thu, 27 Nov 2003 11:44 PM Body: This would be useful for the ejb plugin so it can create a client artifact with the name ejb-client-1.2.jar.

[jira] Commented: (MPEJB-2) ejb:install should also depend and install client

2003-11-27 Thread jira
The following comment has been added to this issue: Author: Archimedes Trajano Created: Thu, 27 Nov 2003 11:58 PM Body: Okay I think I figured it out goal name=ejb:install prereqs=ejb:ejb,ejb:ejb-client description=Install the ejb in the local repository

[jira] Updated: (MPEJB-2) ejb:install should also depend and install client

2003-11-27 Thread jira
The following issue has been updated: Updater: Archimedes Trajano (mailto:[EMAIL PROTECTED]) Date: Fri, 28 Nov 2003 12:23 AM Comment: Patch to the files Includes patches to deploy and snapshots as well. Changed the path to say [id]-client-[version] instead of

[jira] Commented: (MPJBOSS-3) jboss 3.2 JXM deploy/undeploy URL is slightly different from what's in jboss plugin project.properties

2003-11-27 Thread jira
The following comment has been added to this issue: Author: Florin Vancea Created: Fri, 28 Nov 2003 12:28 AM Body: Just a thought on Archimedes's last comment: Forking on start is OK, provided that you wait on %JBOSS_HOME%/server/%JBOOS_CONF_NAME%/conf/jboss-service.xml before

Question and Apology

2003-11-27 Thread Alain Javier Guarnieri del Gesu
First, sorry for posting on the Logo issue when it had already been resolved. I was weeding through 600+ messages. Second, how does one specify the bootclasspath? It isn't possible in RC2. I had to hard code my bootclasspath into the java plugin. Is there a solution? It seems like it would mean