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

[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 performing the 
deploy.

Florin

-
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJBOSS-3


Here is an overview of the issue:
-
Key: MPJBOSS-3
Summary: jboss 3.2 JXM deploy/undeploy URL is slightly different from what's in 
jboss plugin project.properties
   Type: Bug

 Status: Closed
   Priority: Minor
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-jboss-plugin
   Fix Fors:
 1.4
   Versions:
 1.3

   Assignee: 
   Reporter: Dima Berastau

Created: Tue, 1 Jul 2003 3:53 AM
Updated: Fri, 28 Nov 2003 12:28 AM

Description:
default maven.jboss.jmx.url.deploy and maven.jboss.jmx.url.undeploy seem to be missing 
0 at the end (should read 'arg0=' rather than 'arg=', tested in jboss 3.2).


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[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 [id]-[version]-client
Changes:
 Attachment changed to ejb.patch
-
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPEJB-2&page=history

-
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPEJB-2


Here is an overview of the issue:
-
Key: MPEJB-2
Summary: ejb:install should also depend and install client
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: 1 day
 Time Spent: Unknown
  Remaining: 1 day

Project: maven-ejb-plugin
   Versions:
 1.2

   Assignee: 
   Reporter: Archimedes Trajano

Created: Thu, 27 Nov 2003 11:11 PM
Updated: Fri, 28 Nov 2003 12:23 AM

Description:
Need to add into plugin.jelly something like

   



 
  
  

  
  
  

Not sure how to build pom.client though.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[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


 
  
  
   
   
   


  
-
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPEJB-2


Here is an overview of the issue:
-
Key: MPEJB-2
Summary: ejb:install should also depend and install client
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: 1 day
 Time Spent: Unknown
  Remaining: 1 day

Project: maven-ejb-plugin
   Versions:
 1.2

   Assignee: 
   Reporter: Archimedes Trajano

Created: Thu, 27 Nov 2003 11:11 PM
Updated: Thu, 27 Nov 2003 11:58 PM

Description:
Need to add into plugin.jelly something like

   



 
  
  

  
  
  

Not sure how to build pom.client though.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[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 -client-1.2.jar.
-
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPARTIFACT-2


Here is an overview of the issue:
-
Key: MPARTIFACT-2
Summary: Add tag attribute to relax the restriction on artifact type and file 
extension association
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-artifact-plugin
   Fix Fors:
 1.1
   Versions:
 1.0

   Assignee: 
   Reporter: Willie Vu

Created: Sun, 28 Sep 2003 12:57 AM
Updated: Thu, 27 Nov 2003 11:44 PM

Description:
maven-dist needs to deploy .tar.gz and .zip files to distributions directory in repo.  
artifact can easily be modified to expand functionality to support other plugins like 
maven-dist.  The artifact tags can have an attribute that specifies a file extension, 
if that differs from the type.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[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:
-
Key: MPEJB-2
Summary: ejb:install should also depend and install client
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: 1 day
 Time Spent: Unknown
  Remaining: 1 day

Project: maven-ejb-plugin
   Versions:
 1.2

   Assignee: 
   Reporter: Archimedes Trajano

Created: Thu, 27 Nov 2003 11:11 PM
Updated: Thu, 27 Nov 2003 11:11 PM

Description:
Need to add into plugin.jelly something like

   



 
  
  

  
  
  

Not sure how to build pom.client though.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MPEJB-1) Documentation not updated to say anything about ejb:ejb-client

[jira]

Message:

  A new issue has been created in JIRA.

-
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPEJB-1


Here is an overview of the issue:
-
Key: MPEJB-1
Summary: Documentation not updated to say anything about ejb:ejb-client
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: 1 hour
 Time Spent: Unknown
  Remaining: 1 hour

Project: maven-ejb-plugin
   Versions:
 1.2

   Assignee: 
   Reporter: Archimedes Trajano

Created: Thu, 27 Nov 2003 11:02 PM
Updated: Thu, 27 Nov 2003 11:02 PM

Description:
Documentation not updated to say anything about ejb:ejb-client.  Update goals.xml


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

status of MAVEN_1-0_BRANCH?

[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 
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:609)
 [exec] at 
org.apache.maven.MavenSession.attainGoals(MavenSession.java:275)
 [exec] +

 [exec] at 
org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:312)
 [exec] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
 [exec] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
 [exec] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
 [exec] at 
com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:128)
 [exec] at com.werken.werkz.Goal.fire(Goal.java:639)
 [exec] at com.werken.werkz.Goal.attain(Goal.java:575)

Is this a known issue?
--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: jelly script woes

[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:
> > 
> > jdbc.database.${jdbc.os}
> >  > "${context.findVariable(variable)}" />
> > 
> > This sets dbdatabase to the value of the variable ('jdbc.database.' +
> > whatever was in the variable 'jdbc.os').
> 
> Does not work unfortunately. In your example I get an empty string as 
> content of "dbdatabase". Looking into Jelly examples I can use the 
> expression ${context.findVariable("variable")}, but this is equivalent 
to 
> ${variable} and delivers just the name of the created variable, but not 
its value ..

It works fine for me. Can you post your example that doesn't work?

--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven cli & build trouble

[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 
-
> Dmaven.genapp.template.name="Elsag-Solutions Application" 
-Dmaven.genapp.
> template.package=com.elsagsolutions.app -Dmaven.genapp.template.id=esapp 
genapp
>  __  __
> |  \/  |__ _Apache__ ___
> | |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
> |_|  |_\__,_|\_/\___|_||_|  v. 1.0-rc1-SNAPSHOT
> 
> BUILD FAILED
> Goal "Application" does not exist in this project.
> Total time: 2 seconds
> Finished at: Thu Nov 27 13:51:16 CET 2003
> === snap 
> 
> Does anybody have a clue (I tried any thinkable combination of setting 
the 
> quotation)? Originally I thought it is a bug in CLIManager.java (http:
> //jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1058), but if I run 
this
> comannd-line in the debugger with the sources from MAVEN-1_0-BRANCH and 
> commons-cli-1.0-beta-2 it works.
is this windows or linux.

If it's windows, it's easy. just put the quotes around the entire 
argument, including the -D= 
--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Plugin plugin] Changing plugin:deploy

[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 jar in the local
> plugin cache (if this feature is used by anyone, I can rename the goal
> to plugin:unpack)
> 
> Ok?
> 
> Thanks
> -Vincent
> 
> 
> -
> 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]

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

[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 overview of the issue:
-
Key: MAVEN-1058
Summary: [PATCH] CLI : multiple -Dprop=value not allowed
   Type: Bug

 Status: Closed
   Priority: Major
 Resolution: WON'T FIX

 Original Estimate: 5 minutes
 Time Spent: Unknown
  Remaining: 5 minutes

Project: maven
 Components: 
 core
   Fix Fors:
 1.0-rc2
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Jörg Schaible

Created: Thu, 27 Nov 2003 6:30 AM
Updated: Thu, 27 Nov 2003 5:20 PM

Description:
Reopened issue MAVEN-219.

Still not possible to define more than 1 property at command line.

See patch for wrong usage of OptionBuilder.

BTW: Maven's project.xml still references commons-cli-1.0-beta2 although this version 
has been released some time ago.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Question and Apology

[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 adding a switch to
the POM?

-- 
Alain Javier Guarnieri del Gesu - [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Javadoc Linking

[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 PROTECTED]

-
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

[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
   clover/src/plugin-test/src/test/org/apache/maven/clover/test
SimpleTest.java
  Log:
  Added plugin tests
  
  Revision  ChangesPath
  1.1  maven-plugins/clover/src/plugin-test/project.properties
  
  Index: project.properties
  ===
  maven.clover.report.xml = true
  
  
  
  1.1  maven-plugins/clover/src/plugin-test/project.xml
  
  Index: project.xml
  ===
  
  
3
test-maven-clover-plugin
Maven Clover plugin test
maven
1.0

  Apache Software Foundation
  http://jakarta.apache.org/

2003
org.apache.maven.clover.test
Test project for Maven Clover plugin
http://maven.apache.org/reference/plugins/clover/

  scm:cvs:pserver:[EMAIL 
PROTECTED]:/home/cvspublic:maven-plugins/clover/
  http://cvs.apache.org/viewcvs/maven-plugins/clover/





  src/main
  src/test
  

  **/Test*.java

  


  maven-clover-plugin

  
  
  
  1.1  maven-plugins/clover/src/plugin-test/maven.xml
  
  Index: maven.xml
  ===
  
  

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  

  
  
  
  
  1.1  
maven-plugins/clover/src/plugin-test/src/main/org/apache/maven/clover/test/Simple.java
  
  Index: Simple.java
  ===
  package org.apache.maven.clover.test;
  
  /* 
   * The Apache Software License, Version 1.1
   *
   * Copyright (c) 2001 The Apache Software Foundation.  All rights
   * reserved.
   *
   * Redistribution and use in source and binary forms, with or without
   * modification, are permitted provided that the following conditions
   * are met:
   *
   * 1. Redistributions of source code must retain the above copyright
   *notice, this list of conditions and the following disclaimer.
   *
   * 2. Redistributions in binary form must reproduce the above copyright
   *notice, this list of conditions and the following disclaimer in
   *the documentation and/or other materials provided with the
   *distribution.
   *
   * 3. The end-user documentation included with the redistribution,
   *if any, must include the following acknowledgment:
   *   "This product includes software developed by the
   *Apache Software Foundation (http://www.apache.org/)."
   *Alternately, this acknowledgment may appear in the software itself,
   *if and wherever such third-party acknowledgments normally appear.
   *
   * 4. The names "Apache" and "Apache Software Foundation" and
   *"Apache Maven" must not be used to endorse or promote products
   *derived from this software without prior written permission. For
   *written permission, please contact [EMAIL PROTECTED]
   *
   * 5. Products derived from this software may not be called "Apache",
   *"Apache Maven", nor may "Apache" appear in their name, without
   *prior written permission of the Apache Software Foundation.
   *
   * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
   * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
   * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
   * DISCLAIMED.  IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
   * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
   * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
   * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
   * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
   * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
   * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
   * SUCH DAMAGE.
   * 
   *
   * This software consists of voluntary contributions made by many
   * individuals on behalf of the Apache Software Foundation.  For more
   * information on the Apache Software Foundation, please see
   * .
   *
   * 
   */
  
  public class Simple
  {
  public void someMethod()
  {
  }
  } 
  
  
  1.1  
maven-plugins/clover/src/plugin-test/src/test/org/apache/maven/clover/test/SimpleTest.j

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

[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/main/org/apache/maven - New directory

[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/main/org/apache/maven/clover - New directory

[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/apache/maven/clover/test - New directory

[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/test/org/apache/maven/clover/test - New directory

[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 - New directory

[vmassol]

vmassol 2003/11/27 12:19:33

  maven-plugins/clover/src/plugin-test/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/test/org/apache/maven - New directory

[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

[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/main - New directory

[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

[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 - New directory

[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/test/org - New directory

[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/main/org/apache - New directory

[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 - New directory

[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

[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]

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

[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  task. See 
http://jakarta.apache.org/cactus/integration/ant/task_runservertests.html for details.
-
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJBOSS-3


Here is an overview of the issue:
-
Key: MPJBOSS-3
Summary: jboss 3.2 JXM deploy/undeploy URL is slightly different from what's in 
jboss plugin project.properties
   Type: Bug

 Status: Closed
   Priority: Minor
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-jboss-plugin
   Fix Fors:
 1.4
   Versions:
 1.3

   Assignee: 
   Reporter: Dima Berastau

Created: Tue, 1 Jul 2003 3:53 AM
Updated: Thu, 27 Nov 2003 1:59 PM

Description:
default maven.jboss.jmx.url.deploy and maven.jboss.jmx.url.undeploy seem to be missing 
0 at the end (should read 'arg0=' rather than 'arg=', tested in jboss 3.2).


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[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 how to do 
that.

Forking out with "start" though it may work will not solve the problem because we have 
to make it wait till the server finishes loading before we can deploy our code.

That way we can do

maven jboss:start jboss:deploy-ear test jboss:stop

-
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJBOSS-3


Here is an overview of the issue:
-
Key: MPJBOSS-3
Summary: jboss 3.2 JXM deploy/undeploy URL is slightly different from what's in 
jboss plugin project.properties
   Type: Bug

 Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-jboss-plugin
   Fix Fors:
 1.4
   Versions:
 1.3

   Assignee: 
   Reporter: Dima Berastau

Created: Tue, 1 Jul 2003 3:53 AM
Updated: Thu, 27 Nov 2003 1:48 PM

Description:
default maven.jboss.jmx.url.deploy and maven.jboss.jmx.url.undeploy seem to be missing 
0 at the end (should read 'arg0=' rather than 'arg=', tested in jboss 3.2).


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[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:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJBOSS-3


Here is an overview of the issue:
-
Key: MPJBOSS-3
Summary: jboss 3.2 JXM deploy/undeploy URL is slightly different from what's in 
jboss plugin project.properties
   Type: Bug

 Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-jboss-plugin
   Fix Fors:
 1.4
   Versions:
 1.3

   Assignee: 
   Reporter: Dima Berastau

Created: Tue, 1 Jul 2003 3:53 AM
Updated: Thu, 27 Nov 2003 1:46 PM

Description:
default maven.jboss.jmx.url.deploy and maven.jboss.jmx.url.undeploy seem to be missing 
0 at the end (should read 'arg0=' rather than 'arg=', tested in jboss 3.2).


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (MAVEN-936) Specification-Version and Implementation-Vendor-Id not being set

[jira]

The following comment has been added to this issue:

 Author: Lynn Richards
Created: Thu, 27 Nov 2003 1:35 PM
   Body:
I believe the EJB jar manifest should document the specification and implementation of 
the *application* not that of EJB/J2EE.  EJB information is available separately in 
EJB-specific files (via DTDs in XML).
-
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-936


Here is an overview of the issue:
-
Key: MAVEN-936
Summary: Specification-Version and Implementation-Vendor-Id not being set
   Type: Improvement

 Status: Unassigned
   Priority: Trivial

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-jar
   Fix Fors:
 1.0-rc2
   Versions:
 1.0-rc1

   Assignee: 
   Reporter: Lynn Richards

Created: Wed, 15 Oct 2003 2:29 PM
Updated: Thu, 27 Nov 2003 1:35 PM
Environment: XP

Description:
Please make the jar manifests consistent.

1. Specification-Version not being set.  pom.specifiationVersion not defined in 
project schema.

- maven.jar.plugin uses:



- maven.ejb.plugin uses:




2. Implementation-Vendor-Id not being set.  pom.organization.identifier not defined in 
project schema.

- maven.jar.plugin uses:



- maven.ejb.plugin uses (title rather than vendor-id):




Thanks,



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [Plugin plugin] Changing plugin:deploy

[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 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)
> 
> plugin:deploy sounds like it should deploy to the remote repo. Is
there
> no plugin:install for just doing things locally?

That's the point... plugin:deploy is not doing what you thought it would
be doing (hence my proposal to rename it)... There is a plugin:install
for doing things locally. plugin:deploy is currently unpacking the
plugin jar locally.

> 
> > Ok?
> 
> +1
> 
> > Thanks
> > -Vincent
> >
> >
> >
-
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> --
> jvz.
> 
> Jason van Zyl
> [EMAIL PROTECTED]
> http://tambora.zenplex.org
> 
> In short, man creates for himself a new religion of a rational
> and technical order to justify his work and to be justified in it.
> 
>   -- Jacques Ellul, The Technological Society
> 
> 
> -
> 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]

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

[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 
conventions used (less specific to more specific as you navigate from left to right).

- removed the X suffix 

I've also used a more compact notation for some tests (this was not in your patch). 

Thanks

-
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJBOSS-3


Here is an overview of the issue:
-
Key: MPJBOSS-3
Summary: jboss 3.2 JXM deploy/undeploy URL is slightly different from what's in 
jboss plugin project.properties
   Type: Bug

 Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-jboss-plugin
   Fix Fors:
 1.4
   Versions:
 1.3

   Assignee: 
   Reporter: Dima Berastau

Created: Tue, 1 Jul 2003 3:53 AM
Updated: Thu, 27 Nov 2003 11:12 AM

Description:
default maven.jboss.jmx.url.deploy and maven.jboss.jmx.url.undeploy seem to be missing 
0 at the end (should read 'arg0=' rather than 'arg=', tested in jboss 3.2).


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[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 plugin...
  
  Revision  ChangesPath
  1.5   +19 -5 maven-plugins/jboss/xdocs/properties.xml
  
  Index: properties.xml
  ===
  RCS file: /home/cvs/maven-plugins/jboss/xdocs/properties.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- properties.xml21 Jun 2003 14:02:28 -  1.4
  +++ properties.xml27 Nov 2003 17:05:21 -  1.5
  @@ -19,7 +19,7 @@
 
   
 Location of JBoss home (i.e. where JBoss is installed on your 
  -  local drive. Example: c:/jboss-3.0.4.
  +  local drive. Example: c:/jboss-3.2.2.
   
 
   
  @@ -86,22 +86,36 @@
 
   
   
  -  maven.jboss.jmx.url.deploy
  +  maven.jboss.${maven.jboss.version}.jmx.url.deploy
 Yes
 
   
  -  URL at which an http get will deploy a target. Default value is
  +  URL at which an http get will deploy a target.
  +
  +
  +  Default value for JBoss 3.0 is
 
http://${maven.jboss.hostname}:${maven.jboss.port}/jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.system:service%3DMainDeployer&methodName=deploy&argType=java.lang.String&arg=
   
  +
  +  Default value for JBoss 3.2 is
  +  
http://${maven.jboss.hostname}:${maven.jboss.port}/jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.system:service%3DMainDeployer&methodName=deploy&argType=java.net.URL&arg0=
  +
 
   
   
  -  maven.jboss.jmx.url.undeploy
  +  maven.jboss.${maven.jboss.version}.jmx.url.undeploy
 Yes
 
   
  -  URL at which an http get will undeploy a target. Default value is
  +  URL at which an http get will undeploy a target.
  +
  +
  +  Default value for JBoss 3.0 is
 
http://${maven.jboss.hostname}:${maven.jboss.port}/jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.system:service%3DMainDeployer&methodName=undeploy&argType=java.lang.String&arg=
  +
  +
  +  Default value for JBoss 3.2 is
  +  
http://${maven.jboss.hostname}:${maven.jboss.port}/jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.system:service%3DMainDeployer&methodName=undeploy&argType=java.net.URL&arg0=
   
 
 
  
  
  
  1.19  +5 -1  maven-plugins/jboss/xdocs/changes.xml
  
  Index: changes.xml
  ===
  RCS file: /home/cvs/maven-plugins/jboss/xdocs/changes.xml,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- changes.xml   25 Nov 2003 10:12:22 -  1.18
  +++ changes.xml   27 Nov 2003 17:05:21 -  1.19
  @@ -8,8 +8,12 @@
 
   
   
  +  
  +Fixed deploy/undeploy URLs for JBoss 3.2.
  +  
 
  -Fix jboss:shutdown and jboss:start hanging on pause.
  +Fix jboss:shutdown and jboss:start hanging on
  +pause.
 
   
   
  
  
  
  1.6   +4 -2  maven-plugins/jboss/plugin.properties
  
  Index: plugin.properties
  ===
  RCS file: /home/cvs/maven-plugins/jboss/plugin.properties,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- plugin.properties 21 Jun 2003 14:02:28 -  1.5
  +++ plugin.properties 27 Nov 2003 17:05:21 -  1.6
  @@ -71,8 +71,10 @@

   # URL which, when fed to , will cause a thing
   # to be deployed
  -maven.jboss.jmx.url.deploy = 
http://${maven.jboss.hostname}:${maven.jboss.port}/jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.system:service%3DMainDeployer&methodName=deploy&argType=java.lang.String&arg=
  +maven.jboss.jmx.url.deploy.3.0 = 
http://${maven.jboss.hostname}:${maven.jboss.port}/jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.system:service%3DMainDeployer&methodName=deploy&argType=java.lang.String&arg=
  +maven.jboss.jmx.url.deploy.3.2 = 
http://${maven.jboss.hostname}:${maven.jboss.port}/jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.system:service%3DMainDeployer&methodName=deploy&argType=java.net.URL&arg0=
 
   
   # URL which, when fed to , will cause a thing
   # to be undeployed
  -maven.jboss.jmx.url.undeploy = 
http://${maven.jboss.hostname}:${maven.jboss.port}/jmx-console/Ht

Re: [Plugin plugin] Changing plugin:deploy

[Jason van Zyl]

On Thu, 2003-11-27 at 03:30, Vincent Massol wrote:
> 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)

plugin:deploy sounds like it should deploy to the remote repo. Is there
no plugin:install for just doing things locally?

> Ok?

+1

> Thanks
> -Vincent
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [Plugin plugin] Changing plugin:deploy

[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.
> 
> 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, deploy, deploy-snapshot) working consistently with
> the plugins for other artifact types.
> 
> There is a problem though with the current plugin:install goal: there
> must be a goal for deploying the plugin into maven runtime, which is
> different that deploying into local/remote directory. How should this
> one be called? Ideas, anyone?

plugin:setup ?
plugin:install-maven ?

However, maybe we can simply keep plugin:install which will do 2 things:
- install the plugin as an artifact in the local repo
- install it in maven

-Vincent


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: jelly script woes

[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
>> prop.x=1
>> prop.y=2
>> prop.z=0
>> 
>> I would like to iterate over the properties "prop." defined in
>> "all": 
>> 
>> 
>> > xmlns:ant:"jelly:ant"> >delim=",">${all} > items="${all.split}"> prop.${i}:${prop[i]}
>>  
>> 
>> The script should have printed:
>> 
>> prop.x:1
>> prop.y:2
>> 
>> Unfortunately Jelly seems not to support the [] syntax and the
>> second expression evaluates to null. This approach is a syntax error:
>> 
>>prop.${i}:${prop.${i}}
>> 
>> This one will print also nothing useful:
>> 
>>prop.${i}:${}
>> 
>> So is there any solution to create such assembled variables?
> 
> 
> Use something like this:
> 
> jdbc.database.${jdbc.os}
>  "${context.findVariable(variable)}" />
> 
> This sets dbdatabase to the value of the variable ('jdbc.database.' +
> whatever was in the variable 'jdbc.os').

Does not work unfortunately. In your example I get an empty string as content of 
"dbdatabase". Looking into Jelly examples I can use the expression 
${context.findVariable("variable")}, but this is equivalent to ${variable} and 
delivers just the name of the created variable, but not its value ...

I also tried something like

$${all.${i}}


but this wont work either, since unlike the set tag the expr tag evaluates only the 
value attribute.

:(


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Plugin plugin] Changing plugin:deploy

[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, deploy, deploy-snapshot) working consistently with
the plugins for other artifact types.

There is a problem though with the current plugin:install goal: there
must be a goal for deploying the plugin into maven runtime, which is
different that deploying into local/remote directory. How should this
one be called? Ideas, anyone?

R.




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[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:
-
Key: MAVEN-1059
Summary: Upload phoenix 4.0.4 jars
   Type: Task

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 Repo Jar Requests

   Assignee: 
   Reporter: Mauro Talevi

Created: Thu, 27 Nov 2003 8:19 AM
Updated: Thu, 27 Nov 2003 8:19 AM

Description:
Please upload the phoenix 4.0.4 jars to ibiblio repo

http://www.apache.org/dist/avalon/phoenix/jars/

Thanks, Mauro



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

maven cli & build trouble

[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" 
-Dmaven.genapp.template.package=com.elsagsolutions.app 
-Dmaven.genapp.template.id=esapp genapp
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-rc1-SNAPSHOT

BUILD FAILED
Goal "Application" does not exist in this project.
Total time: 2 seconds
Finished at: Thu Nov 27 13:51:16 CET 2003
=== snap 

Does anybody have a clue (I tried any thinkable combination of setting the quotation)? 
Originally I thought it is a bug in CLIManager.java 
(http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1058), but if I run this 
comannd-line in the debugger with the sources from MAVEN-1_0-BRANCH and 
commons-cli-1.0-beta-2 it works.
 
Unfortunately I cannot create and work with a Maven snapshot (checked out 
MAVEN-1_0-BRANCH), since its build fails.

= snip ==
$ ant -f build-bootstrap.xml

Buildfile: build-bootstrap.xml

check-maven-home:

check-maven-home-local-1:

check-maven-home-local-2:

check-maven-repo-local:

check-properties:

check-env:
 [echo] maven.home = c:\Programme\Apache Software Foundation\Maven 1.0-SNAPSHOT

env:
 [echo] maven.home = c:\Programme\Apache Software Foundation\Maven 1.0-SNAPSHOT
 [echo] maven.home.local = C:\Dokumente und Einstellungen\jos\.maven
 [echo] maven.repo.local = C:\Dokumente und Einstellungen\jos\.maven\repository
 [echo] 
 [echo] +--
 [echo] | WARNING WARNING WARNING WARNING WARNING WARNING WARNING
 [echo] |
 [echo] |  Maven bootstrap now creates a repository in
 [echo] |  ${user.home}/.maven/repository
 [echo] |  if you do not have the maven.repo.local property set
 [echo] |  before bootstrapping.
 [echo] |
 [echo] |  Maven bootstrap also expands plugins to
 [echo] |  ${user.home}/.maven/plugins
 [echo] |  if you do not have the MAVEN_HOME_LOCAL environment
 [echo] |  variable or
 [echo] |  maven.home.local property set before bootstrapping.
 [echo] |
 [echo] |  This feature is to accomodate the new ability of Maven
 [echo] |  to work from a read only install to MAVEN_HOME.
 [echo] |
 [echo] | WARNING WARNING WARNING WARNING WARNING WARNING WARNING
 [echo] +--

bootstrap-compile:
   [delete] Deleting directory C:\Work\Apps\Maven\maven\bootstrap
[mkdir] Created dir: C:\Work\Apps\Maven\maven\bootstrap\bootstrap-classes
[javac] Compiling 4 source files to 
C:\Work\Apps\Maven\maven\bootstrap\bootstrap-classes

bootstrap:
 [echo] 
 [echo] +--+
 [echo] |  |
 [echo] | L O A D I N G  B O O T S T R A P  T A S K D E F  |
 [echo] |  |
 [echo] +--+
 [echo] 
 [echo] +--+
 [echo] |  |
 [echo] | R U N N I N G  B O O T S T R A P  T A S K|
 [echo] |  |
 [echo] +--+
[mkdir] Created dir: C:\Work\Apps\Maven\maven\bootstrap\bin
[bootstrap] Using the following for your maven.repo.local: C:\Dokumente und 
Einstellungen\jos\.maven\repository
[bootstrap] Destination file C:\Dokumente und 
Einstellungen\jos\.maven\repository\dom4j\jars\dom4j-1.4-dev-8.jar exists. Not 
dowloading.
[bootstrap] Destination file C:\Dokumente und 
Einstellungen\jos\.maven\repository\ant\jars\ant-1.5.3-1.jar exists. Not dowloading.
[bootstrap] Destination file C:\Dokumente und 
Einstellungen\jos\.maven\repository\ant\jars\ant-optional-1.5.3-1.jar exists. Not 
dowloading.
[bootstrap] Destination file C:\Dokumente und 
Einstellungen\jos\.maven\repository\commons-betwixt\jars\commons-betwixt-1.0-beta-1.20030111.103454.jar
 exists. Not dowloading.
[bootstrap] Destination file C:\Dokumente und 
Einstellungen\jos\.maven\repository\commons-digester\jars\commons-digester-1.4.1.jar 
exists. Not dowloading.
[bootstrap] Destination file C:\Dokumente und 
Einstellungen\jos\.maven\repository\commons-jelly\jars\commons-jelly-20030902.160215.jar
 exists. Not dowloading.
[bootstrap] Destination file C:\Dokumente und 
Einstellungen\jos\.maven\repository\commons-jelly\jars\commons-jelly-tags-ant-20030625.032346.jar
 exists. Not dowloading.
[bootstrap] Destination file

patch : choose jdk to run unit test

[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



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[jira]

The following comment has been added to this issue:

 Author: Jörg Schaible
Created: Thu, 27 Nov 2003 6:50 AM
   Body:
Uups. Please ignore this patch. Investigating further it shows, that the problem lies 
in the used commons-cli. Multiple definitions of properties at the command line work 
only with commons-cli-1.0-beta-2, but not with commons-cli-1.0. Sorry for the noise.
-
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1058


Here is an overview of the issue:
-
Key: MAVEN-1058
Summary: [PATCH] CLI : multiple -Dprop=value not allowed
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: 5 minutes
 Time Spent: Unknown
  Remaining: 5 minutes

Project: maven
 Components: 
 core
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Jörg Schaible

Created: Thu, 27 Nov 2003 6:30 AM
Updated: Thu, 27 Nov 2003 6:50 AM

Description:
Reopened issue MAVEN-219.

Still not possible to define more than 1 property at command line.

See patch for wrong usage of OptionBuilder.

BTW: Maven's project.xml still references commons-cli-1.0-beta2 although this version 
has been released some time ago.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MPASPECTJ-2) Add more parameter for AJC ant task

[jira]

Message:

  A new issue has been created in JIRA.

-
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPASPECTJ-2


Here is an overview of the issue:
-
Key: MPASPECTJ-2
Summary: Add more parameter for AJC ant task 
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-aspectj-plugin

   Assignee: 
   Reporter: Emmanuel Boudrant

Created: Thu, 27 Nov 2003 6:48 AM
Updated: Thu, 27 Nov 2003 6:48 AM

Description:
Add more parameter for AJD ant task like :

-help   emit this help message and quit
-versionemit compiler version number and quit
-classpathdirectories and zip files for the classpath
( uses platform-specific path delimiter)
-bootclasspath  override bootclasspath for finding compile types
( uses platform-specific path delimiter)
-extdirs  override extension dirs for finding compile types
( uses platform-specific path delimiter)
-d destination directory for output classes
-targetclassfile setting (1.1 or 1.2, default is 1.1)
-1.3set compliance level to 1.3 (default)
-1.4set compliance level to 1.4
-sourceassertions toggle (1.3 or 1.4, default is 1.3
in -1.3 mode and 1.4 in -1.4 mode)
-nowarn emit no warnings (same as '-warn:none')
-warn:emit warnings specified by comma-delimited list
(eg '-warn:unusedLocals,deprecation')
  constructorName   method with constructor name
  packageDefaultMethod  attempt to override package-default method
  deprecation   usage of deprecated type or member
  maskedCatchBlocks hidden catch block
  unusedLocals  unused local variable (never read)
  unusedArguments   unused method argument (never read)
  unusedImports unused imports
  syntheticAccess   performing synthetic access for inner classes
  assertIdentifier  'assert' used as identifier
-deprecationsame as '-warn:deprecation'
-noImportError  emit no errors for unresolved imports
-proceedOnError keep compiling after errors, dumping class files
with problem methods
-g[:]debug attributes level
-g  all debug info (same as '-g:lines,vars,source')
-g:none no debug info
-g:  debug info for any/all of [lines, vars, source]
-preserveAllLocals  code gen preserve all local variables (for debug)
-referenceInfo  compute reference info
-encoding specify default source encoding format
(Specify encoding for any source file/folder by
suffixing each input name with '[encoding]')
-verboseemit accessed/processed compilation units
-log  specify a log file for compile messages
-progress   show progress (requires -log mode)
-time   display speed information
-noExit do not call System.exit(n) at end of compilation
(n=0 if no error)
-repeat  repeat compilation process  times (perf analysis)


Thx,
-emmanuel


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[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
-
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1058&page=history

-
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1058


Here is an overview of the issue:
-
Key: MAVEN-1058
Summary: [PATCH] CLI : multiple -Dprop=value not allowed
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: 5 minutes
 Time Spent: Unknown
  Remaining: 5 minutes

Project: maven
 Components: 
 core
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Jörg Schaible

Created: Thu, 27 Nov 2003 6:30 AM
Updated: Thu, 27 Nov 2003 6:31 AM

Description:
Reopened issue MAVEN-219.

Still not possible to define more than 1 property at command line.

See patch for wrong usage of OptionBuilder.

BTW: Maven's project.xml still references commons-cli-1.0-beta2 although this version 
has been released some time ago.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[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:
-
Key: MAVEN-1058
Summary: [PATCH] CLI : multiple -Dprop=value not allowed
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: 5 minutes
 Time Spent: Unknown
  Remaining: 5 minutes

Project: maven
 Components: 
 core
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Jörg Schaible

Created: Thu, 27 Nov 2003 6:30 AM
Updated: Thu, 27 Nov 2003 6:30 AM

Description:
Reopened issue MAVEN-219.

Still not possible to define more than 1 property at command line.

See patch for wrong usage of OptionBuilder.

BTW: Maven's project.xml still references commons-cli-1.0-beta2 although this version 
has been released some time ago.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[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 
attribute (according to junit doc).

Changes:
 Attachment changed to maven-test-junit-patch.diff
-
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1057&page=history

-
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1057


Here is an overview of the issue:
-
Key: MAVEN-1057
Summary: Choose JDK used to run unit tests?
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-test
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Eric Berenguier

Created: Thu, 27 Nov 2003 4:50 AM
Updated: Thu, 27 Nov 2003 5:02 AM

Description:
Maven does not allow to choose which JVM to be used to run unit tests, even if the 
underlying junit ant task allows it (jvm attribute).

This is useful if you want to run your tests in a different JVM version than the one 
used to run maven.



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[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:
-
Key: MAVEN-1057
Summary: Choose JDK used to run unit tests?
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-test
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Eric Berenguier

Created: Thu, 27 Nov 2003 4:50 AM
Updated: Thu, 27 Nov 2003 4:50 AM

Description:
Maven does not allow to choose which JVM to be used to run unit tests, even if the 
underlying junit ant task allows it (jvm attribute).

This is useful if you want to run your tests in a different JVM version than the one 
used to run maven.



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Plugin plugin] Changing plugin:deploy

[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 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
> 
> 
> -
> 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]

[Plugin plugin] Changing plugin:deploy

[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


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [pom3/4] element.

[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 an example):


  1.0-rc1
  1.0-rc2
  1.0-rc3-SNAPSHOT


Proposal 2:

* Reuse the dependencies elements of project.xml (this is an example):

 
  maven
  maven
  1.0+
  maven 
 

My analysis:

* First question to answer: whether we wish to support complex
versioning right now. i.e. the use of "+". I am personally not in favor
of using that now for 2 reasons:
  * It is complex to implement and we could easily use a list of
versions as showin in proposal 1
  * It raises lots of ugly questions. Like: if I say "1.0-rc1+", how can
I know that my plugin will be compatible with 1.1 when it is not even
yet designed nor released? So in practice I cannot say 1.0-rc1+ but I'll
have to say something like "1.0-rc1"-"1.0"

* I like the dependency reuse but for the following points:
  * We will need to really tackle the  element properly and
provide Resolvers for each type. We'll also need to provide better APIs
for plugin developers as I believe some plugins are currently iterating
over any dependency. Something like project.getDependencies(type) maybe.
  * How do we specify multiple versions? Using a comma-separated list
seem to have been rejected by everyone (see previous posts on
compatibility in archives).

* Although we could reuse the dependency stuff, Maven core is something
special and unlike other dependencies. Why? Because other dependencies
can be downloaded whereas Maven core is installed and cannot be changed
automatically. Also Maven is not an artifact. It is not composed only of
a JAR. It is a complete system. That means there's no relationship
between the Maven system installed on your machine and the remote
repository. It happens there is a maven jar but this not the
compatibility we are stating. We are stating a compatibility with the
full installed Maven, not an API compatibility with the maven jar.

* Are we going to also specify what version of the POM a plugin
supports? Now that plugins are extracted from the core and could be
provided by third parties, it may become necessary. One solution would
be to link Maven versions with POM versions but I don't know if it
provides enough flexibility.

Thanks
-Vincent

-

Could you comment on the 2 proposals?

Thanks
-Vincent

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 27 November 2003 06:53
> To: [EMAIL PROTECTED]
> Subject: [pom3/4]  element.
> 
> Where did this discussion end up.
> 
> From what I can tell, I suggested we re-use the  element
with
> a new , and then discussion stalled.
> 
> Is that it?
> --
> dIon Gillard, Multitask Consulting
> Blog:  http://blogs.codehaus.org/people/dion/
> 
> 
> 
> -
> 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: cvs commit: maven-plugins/sea plugin.jelly

[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

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 27 November 2003 07:50
> To: [EMAIL PROTECTED]
> Subject: cvs commit: maven-plugins/sea plugin.jelly
> 
> dion2003/11/26 22:49:53
> 
>   Modified:sea  plugin.jelly
>   Log:
>   Removed unnecessary use of pom.getPluginContext
> 
>   Revision  ChangesPath
>   1.5   +3 -3  maven-plugins/sea/plugin.jelly
> 
>   Index: plugin.jelly
>   ===
>   RCS file: /home/cvs/maven-plugins/sea/plugin.jelly,v
>   retrieving revision 1.4
>   retrieving revision 1.5
>   diff -u -r1.4 -r1.5
>   --- plugin.jelly12 Mar 2003 03:50:43 -  1.4
>   +++ plugin.jelly27 Nov 2003 06:49:53 -  1.5
>   @@ -52,11 +52,11 @@
>   -->
> 
> -file="${pom.getPluginContext('maven-sea-
> plugin').getVariable('plugin.dir')}/sea-tar"
>   +file="${plugin.dir}/sea-tar"
>perm="+x"/>
> 
> -executable="${pom.getPluginContext('maven-sea-
> plugin').getVariable('plugin.dir')}/sea-tar">
>   +executable="${plugin.dir}/sea-tar">
>
>
>
>   @@ -66,7 +66,7 @@
>  
> 
> -file="${pom.getPluginContext('maven-sea-
> plugin').getVariable('plugin.resources')}/sea-header"
>   +file="${plugin.resources}/sea-header"
>tofile="${maven.build.dir}/project-sea-header"
>overwrite="true"
>filtering="true"
> 
> 
> 
> 
> -
> 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]