date:20030803

[jira] Updated: (MAVEN-400) new plugin that generates forehead/classworlds config files to run application

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 2:04 AM
Changes:
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-400
Summary: new plugin that generates forehead/classworlds config files to run 
application
   Type: New Feature

 Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: 1 hour

Project: maven
   Fix Fors:
 1.1

   Assignee: 
   Reporter: Alexey Demakov

Created: Thu, 17 Apr 2003 3:48 AM
Updated: Mon, 4 Aug 2003 2:04 AM

Description:
plugin parameters:

maven.forehead.class - main class name. if not set, don't generate config

maven.forehead.file - optional config file name. default to "${pom.artifactId}.fh"

Not implemented: generation of script to run forehead with this config.

For example, windows bat-file:

@echo off

java -classpath %MAVEN_HOME%/lib/forehead-1.0-beta-4.jar 
-Dmaven.repo.local=%MAVEN_HOME%/repository 
-Dforehead.conf.file=${maven.build.dir}/${pom.artifactId}.fh
com.werken.forehead.Forehead %*

bash script is very similar

Possible improvements:

May be there are right way of file creation from jelly script.
I implemented my own tag library for adding line to file.


-
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-104) maven.repo.remote.enabled=false prevents dep checking

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 2:04 AM
Changes:
 environment changed to 
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-104
Summary: maven.repo.remote.enabled=false prevents dep checking
   Type: Bug

 Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.1
   Versions:
 1.0-beta-7

   Assignee: 
   Reporter: Vincent Massol

Created: Fri, 13 Sep 2002 8:01 AM
Updated: Mon, 4 Aug 2003 2:04 AM

Description:
if maven.repo.remote.enabled = false then Maven does not check dependencies any more.

Thanks
-Vincent



-
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: junit-report.html

2003-08-03 Thread Rafal Krzewski

John Farrell wrote:
> Hi all. I am a new Maven user. I believe I have tidied up and improved the 
> junit report page. To whom do I send my changes? Thanks,

You should create an 'Improvement' issue in Maven's Jira, describe what
you did, and attach a patch (in unidiff format) to the issue. If your
issue doesn't get sheduled (get the 'fix version' set) in a few days,
you should email dIon Gillard and ask to shedule it.

Thanks,
R.

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

[jira] Closed: (MAVEN-216) The axis plugin doesn't allow a custom wsdl location

2003-08-03 Thread jira

Message:

   The following issue has been closed.

   Resolver: dion gillard
   Date: Mon, 4 Aug 2003 2:02 AM

The axis plugin was removed
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-216
Summary: The axis plugin doesn't allow a custom wsdl location
   Type: New Feature

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

 Time Spent: Unknown
  Remaining: 0 minutes

Project: maven
 Components: 
 core
   Fix Fors:
 1.0-rc1
   Versions:
 1.0-beta-8

   Assignee: 
   Reporter: Dan Diephouse

Created: Sat, 25 Jan 2003 1:40 PM
Updated: Mon, 4 Aug 2003 2:02 AM
Environment: All

Description:
The axis plugin assumes a location for wsdl files which is not always the case.  


-
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-113) Add download links to all plugin versions on the download page

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 2:01 AM
Changes:
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-113
Summary: Add download links to all plugin versions on the download page
   Type: Improvement

 Status: Assigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: 4 hours

Project: maven
   Fix Fors:
 1.1

   Assignee: dion gillard
   Reporter: dion gillard

Created: Thu, 19 Sep 2002 5:27 AM
Updated: Mon, 4 Aug 2003 2:01 AM
Environment: N/A

Description:
There is currently no easy way to know which versions of plugins are available @ 
ibiblio. It'd be nice if the download page listed the plugins (all versions) available 
for download.

This could be a generated page using the plugin's  tag


-
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-567) ClassNotFoundException: velocity after clearing local repo

2003-08-03 Thread jira

The following comment has been added to this issue:

 Author: dion gillard
Created: Mon, 4 Aug 2003 2:00 AM
   Body:
Am trying this myself.

If I can't reproduce, I'll close the issue
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-567
Summary: ClassNotFoundException: velocity after clearing local repo
   Type: Bug

 Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: Brett Porter

Created: Tue, 15 Jul 2003 1:11 AM
Updated: Tue, 15 Jul 2003 1:11 AM

Description:
situation: clearing out the local repository (rm -rf ~/.maven/repository, and also if 
you delete all the plugins by rm -rf ~/.maven).

Obviously, this is also the case for a new install.

First run of maven on maven itself (and presumably other projects), causes:

ClassNotFoundException: velocity
...

Second run works, as velocity was downloaded in the first run.

I'm imagining this will be fixed in the great pluginmanager refactoring, but filing 
issue to verify. This issue has also been raised on the -user list.


-
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: junit-report.html

2003-08-03 Thread Ben Walding

http://wiki.codehaus.org/maven/SubmittingPatches

John Farrell wrote:

Hi all. I am a new Maven user. I believe I have tidied up and improved the 
junit report page. To whom do I send my changes? Thanks,

John

-
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: junit-report.html

2003-08-03 Thread dion

You post them in our issue tracking system, Jira.

See http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030

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


John Farrell <[EMAIL PROTECTED]> wrote on 04/08/2003 04:38:11 PM:

> Hi all. I am a new Maven user. I believe I have tidied up and improved 
the 
> junit report page. To whom do I send my changes? Thanks,
> 
> John
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

Re: junit-report.html

2003-08-03 Thread Martin Skopp

Hi John,

On Mon, 2003-08-04 at 08:38, John Farrell wrote:
> Hi all. I am a new Maven user. I believe I have tidied up and improved the 
> junit report page. To whom do I send my changes? Thanks,

Please create a issue on http://jira.codehaus.org
-- 
Martin Skopp
Riege Software International GmbH
Support: mailto:[EMAIL PROTECTED], Information: http://www.riege.com
 
This email is intended to be viewed with a nonproportional font.
Public Key on http://www.keyserver.net, Key-ID: 3D4027B5
Fingerprint: 1970 C78D 9A1D 99FA 5CE4  5C0D 29E6 6A95 3D40 27B5



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

[jira] Closed: (MAVEN-408) [j2ee] fixes to plugin.jelly

2003-08-03 Thread jira

Message:

   The following issue has been closed.

   Resolver: dion gillard
   Date: Mon, 4 Aug 2003 1:49 AM

Applied
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-408
Summary: [j2ee] fixes to plugin.jelly
   Type: Bug

 Status: Closed
   Priority: Minor
 Resolution: FIXED

 Time Spent: Unknown
  Remaining: 0 minutes

Project: maven
 Components: 
 plugin-war
   Fix Fors:
 1.0-rc1
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: Joe Germuska

Created: Sat, 19 Apr 2003 9:26 PM
Updated: Mon, 4 Aug 2003 1:49 AM

Description:
When attempting to attain the j2ee:validate-war goal, I got the following error:

[warvalidator] [ERROR] Error in class org.apache.maven.j2ee.WarValidator

BUILD FAILED
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory

Looking at plugin.jelly for the j2ee plugin, I saw that the ant:taskdef for the 
"warvalidator" task did not include commons-logging.  Adding it solved the problem.

Also, I suspect that in common use, the war plugin gets initialized before 
j2ee:validate-war gets called, but in my case I was attempting  to achieve the goal 
directly.  The problem was that maven.war.build.dir was undefined, making the 
following set variable have an unexpected result:



By adding "war:init" as a prereq to the j2ee:validate-war goal, this problem was 
solved.  It makes me wonder whether the validate-war goal shouldn't just be rolled 
into the "war" plugin instead, but maybe there's some history I don't know yet.  

The attached patch deals with both of these issues.


-
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/src/plugins-build/j2ee plugin.jelly

2003-08-03 Thread dion

dion2003/08/03 23:43:51

  Modified:src/plugins-build/j2ee plugin.jelly
  Log:
  Apply patches from MAVEN-408 
  Thanks Joe
  
  Revision  ChangesPath
  1.10  +2 -1  maven/src/plugins-build/j2ee/plugin.jelly
  
  Index: plugin.jelly
  ===
  RCS file: /home/cvs/maven/src/plugins-build/j2ee/plugin.jelly,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- plugin.jelly  1 Apr 2003 06:28:54 -   1.9
  +++ plugin.jelly  4 Aug 2003 06:43:51 -   1.10
  @@ -17,7 +17,7 @@
 
 
 
  -  
   
   
  @@ -27,6 +27,7 @@
   
   
   
  +
 
   
   
  
  
  

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

cvs commit: maven/xdocs/start integrate.xml

2003-08-03 Thread dion

dion2003/08/03 23:42:16

  Modified:xdocs/start integrate.xml
  Log:
  Apply patches for MAVEN-610
  
  Revision  ChangesPath
  1.21  +6 -0  maven/xdocs/start/integrate.xml
  
  Index: integrate.xml
  ===
  RCS file: /home/cvs/maven/xdocs/start/integrate.xml,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- integrate.xml 27 Jul 2003 14:31:41 -  1.20
  +++ integrate.xml 4 Aug 2003 06:42:16 -   1.21
  @@ -219,8 +219,14 @@
   
   
 
  +${basedir}/src/resources/misc
   
 *.xsd
  +
  +  
  +  
  +${basedir}/src/resources/logging
  +
 log4j.properties
   
 
  
  
  

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

[jira] Closed: (MAVEN-619) Documentation jar resources

2003-08-03 Thread jira

Message:

   The following issue has been closed.

   Resolver: dion gillard
   Date: Mon, 4 Aug 2003 1:42 AM

Patches applied
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-619
Summary: Documentation jar resources
   Type: Improvement

 Status: Closed
   Priority: Minor
 Resolution: FIXED

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 documentation
   Fix Fors:
 1.0-rc1
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: Moritz Petersen

Created: Sun, 27 Jul 2003 7:01 AM
Updated: Mon, 4 Aug 2003 1:42 AM
Environment: Mac OS X 10.2.6, Java 1.4.1

Description:
Documentation update regarding the  element in POM. The current 
documentation does not reflect the needed elements.


-
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/xdocs/reference project-descriptor.xml

2003-08-03 Thread dion

dion2003/08/03 23:38:05

  Modified:xdocs/reference project-descriptor.xml
  Log:
  Apply patches for MAVEN-610
  
  Revision  ChangesPath
  1.19  +7 -0  maven/xdocs/reference/project-descriptor.xml
  
  Index: project-descriptor.xml
  ===
  RCS file: /home/cvs/maven/xdocs/reference/project-descriptor.xml,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- project-descriptor.xml21 Jul 2003 05:50:51 -  1.18
  +++ project-descriptor.xml4 Aug 2003 06:38:05 -   1.19
  @@ -713,6 +713,13 @@
 elements (described below). These resources are 
used to
 complete the jar file or to run unit test.
   
  +
  +  ElementDescription
  +  
  +resource
  +Each resource must be defined in a resource element.
  +  
  +
 
 
   
  
  
  

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

junit-report.html

2003-08-03 Thread John Farrell

Hi all. I am a new Maven user. I believe I have tidied up and improved the 
junit report page. To whom do I send my changes? Thanks,

John


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

[jira] Updated: (MAVEN-455) Patch for Changelog-Plugin

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 1:37 AM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-455
Summary: Patch for Changelog-Plugin
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Fix Fors:
 1.1
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: Tammo van Lessen

Created: Sun, 1 Jun 2003 10:22 AM
Updated: Mon, 4 Aug 2003 1:37 AM

Description:
Hi,

i've made a patch for the changelog-plugin. it makes it more customizeable, thereby 
you can get the changelog of another module and/or from another repository by setting 
the new propierties

maven.changelog.repository.connection and
maven.changelog.basedir

Cheers,
  Tammo



-
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-258) Decouple Project reading from the File object

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 1:33 AM
Changes:
 environment changed to 
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-258
Summary: Decouple Project reading from the File object
   Type: Improvement

 Status: Unassigned
   Priority: Trivial

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.1

   Assignee: 
   Reporter: Ben Walding

Created: Fri, 7 Feb 2003 5:54 PM
Updated: Mon, 4 Aug 2003 1:33 AM

Description:
At the moment MavenUtils has a couple getProject(File, *) methods.

Unfortunately, things like Overlord / anything that is downloading the POM via a URL 
don't have File references to work with. And as such, deserializing the POM fails.

I propose we either
1) Start using URLs
2) Add a resolver to resolve lookups.

I prefer 2 as it means that I can download a project, save it to disk, have the 
getProject(File) work, and if it needs a parent POM, the resolver is called.  At which 
point I can download that POM and return a ref to it.

Some classes that I use are visible at
http://projects.walding.com:8000/viewcvs/DataForge/dataforge-engine/src/java/com/walding/dataforge/resolvers/

I will relicense these (and any deps) under ASL if they are used in Maven in any form.

(That whole library will be come ASL compatible shortly in any event).



-
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-556) Roadmap doc plugin

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 1:35 AM
Comment:
Does the patch apply? And has it been tested?
Changes:
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-556
Summary: Roadmap doc plugin
   Type: New Feature

 Status: Unassigned
   Priority: Trivial

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 documentation
   Fix Fors:
 1.1

   Assignee: 
   Reporter: dion gillard

Created: Wed, 9 Jul 2003 12:10 AM
Updated: Mon, 4 Aug 2003 1:35 AM

Description:
Hi,
   would anyone be interested in a plugin which 
generates a project roadmap?

This would be a simple report, linked from the 
Project Documentation nav menu, and have sections
including:
. release version
. estimated release date
. line items including:
  . functionality type (addition, change etc)
  . description
  . assigned developer

I would expect it to be very similar to the changes
plugin, and be generated by the inclusion of a roadmap.xml
file in the xdocs directory, e.g:


  

  
Refactor administration UI.
  
  ...







  
Add clustering support, based on javagroups.
  

  



Thoughts?

-Tim



-
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] Closed: (MAVEN-617) multiproject and including resources in ejb needs clearification in docs

2003-08-03 Thread jira

Message:

   The following issue has been closed.

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-617
Summary: multiproject and including resources in ejb needs clearification in docs
   Type: Improvement

 Status: Closed
   Priority: Trivial
 Resolution: FIXED

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 documentation
   Fix Fors:
 1.0-rc1
   Versions:
 1.0-rc1

   Assignee: 
   Reporter: Thomas Christensen

Created: Sun, 27 Jul 2003 3:58 AM
Updated: Mon, 4 Aug 2003 1:33 AM
Environment: Windows XP, Java 1.4

Description:
A tip when using the multiproject plugin: Use ${basedir} in your POM's resource 
section:


${basedir}/src/java

**/*.properties



The resources won't be included if you just specify "src/java" as directory unless you 
are located in the subproject directory.

It took me a while since many examples uses "src/java" and because the java:compile 
goal works fine in multiproject without ${basedir}.

I suggest the docs on multiproject is updated with this tip.


-
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/src/plugins-build/multiproject project.xml

2003-08-03 Thread dion

dion2003/08/03 23:29:10

  Modified:src/plugins-build/multiproject/xdocs navigation.xml
   src/plugins-build/multiproject project.xml
  Added:   src/plugins-build/multiproject/xdocs faq.fml
  Log:
  Apply patch for MAVEN-617 and fix reports in project.xml
  
  Revision  ChangesPath
  1.2   +1 -0  maven/src/plugins-build/multiproject/xdocs/navigation.xml
  
  Index: navigation.xml
  ===
  RCS file: /home/cvs/maven/src/plugins-build/multiproject/xdocs/navigation.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- navigation.xml30 Jun 2003 03:18:49 -  1.1
  +++ navigation.xml4 Aug 2003 06:29:10 -   1.2
  @@ -10,6 +10,7 @@
   
 
 
  +  
   
 
   
  
  
  
  1.1  maven/src/plugins-build/multiproject/xdocs/faq.fml
  
  Index: faq.fml
  ===
  
  
  
  Using Multiproject
  
  When using multiproject to build subprojects, resources are 
not included in my artifacts. Why?
  
  Use ${basedir} in your subproject's POM resource section:
  
  
  
  
  
  
  The resources won't be included if you just specify "src/java" 
as directory unless maven is started from within the subproject directory.
  
  
  
  
  
  
  
  
  1.7   +17 -0 maven/src/plugins-build/multiproject/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven/src/plugins-build/multiproject/project.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- project.xml   25 Jul 2003 12:31:32 -  1.6
  +++ project.xml   4 Aug 2003 06:29:10 -   1.7
  @@ -57,4 +57,21 @@
   
   
 
  +  
  +  
  +maven-changelog-plugin
  +maven-changes-plugin
  +maven-checkstyle-plugin
  +maven-developer-activity-plugin
  +maven-faq-plugin
  +maven-file-activity-plugin
  +maven-javadoc-plugin
  +maven-jdepend-plugin
  +maven-junit-report-plugin
  +maven-jxr-plugin
  +maven-license-plugin
  +maven-linkcheck-plugin
  +maven-pmd-plugin
  +maven-tasklist-plugin
  +  
   
  
  
  

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

cvs commit: maven/src/java/org/apache/maven/project Project.java

2003-08-03 Thread dion

dion2003/08/03 23:27:56

  Modified:src/java/org/apache/maven/plugin PluginManager.java
   src/java/org/apache/maven/project Project.java
  Log:
  Move maven.xml definition off to project
  
  Revision  ChangesPath
  1.62  +8 -14 maven/src/java/org/apache/maven/plugin/PluginManager.java
  
  Index: PluginManager.java
  ===
  RCS file: /home/cvs/maven/src/java/org/apache/maven/plugin/PluginManager.java,v
  retrieving revision 1.61
  retrieving revision 1.62
  diff -u -r1.61 -r1.62
  --- PluginManager.java4 Aug 2003 04:30:39 -   1.61
  +++ PluginManager.java4 Aug 2003 06:27:56 -   1.62
  @@ -402,26 +402,20 @@
   // FIXME: Part of this belongs as a method on Project, e.g. the name and
   //construction of maven.xml
   // Project's Jelly script
  -if ( project.getFile() != null )
  +if ( project.hasMavenXml() )
   {
  -// maven.xml
  -File f = new File( project.getFile().getParentFile(), 
MavenConstants.BUILD_FILE_NAME );
  -
  -if ( f.exists() )
  -{
  -//!!! This is the cause of the classloader problems!!
  -JellyScriptHousing jellyScriptHousing = createJellyScriptHousing( 
project, null, f );
  -mapper.parse( new FileReader( f ), jellyScriptHousing );
  -runJellyScriptHousing( jellyScriptHousing, baseContext );
  -}
  +File mavenXml = project.getMavenXml();
  +//!!! This is the cause of the classloader problems!!
  +JellyScriptHousing jellyScriptHousing = createJellyScriptHousing( 
project, null, mavenXml );
  +mapper.parse( new FileReader( mavenXml ), jellyScriptHousing );
  +runJellyScriptHousing( jellyScriptHousing, baseContext );
   }
   
   // Parent's Jelly script
   // FIXME: What about further up the chain?
  -if ( project.hasParent() )
  +if ( project.hasParent() && project.getParent().hasMavenXml() )
   {
   // FIXME: this is a badly named method
  -
   File f = project.parentMavenXml();
   
   if ( f.exists() )
  
  
  
  1.87  +24 -1 maven/src/java/org/apache/maven/project/Project.java
  
  Index: Project.java
  ===
  RCS file: /home/cvs/maven/src/java/org/apache/maven/project/Project.java,v
  retrieving revision 1.86
  retrieving revision 1.87
  diff -u -r1.86 -r1.87
  --- Project.java  4 Aug 2003 01:11:13 -   1.86
  +++ Project.java  4 Aug 2003 06:27:56 -   1.87
  @@ -227,6 +227,9 @@
   
   /** The maven session this project is running in. */
   private Maven maven;
  +
  +/** the maven.xml file for this project */
  +private File mavenXml;
   
   public Project getParent()
   {
  @@ -466,6 +469,26 @@
   public File parentMavenXml()
   {
   return new File( parentBasedir(), MavenConstants.BUILD_FILE_NAME );
  +}
  +
  +/**
  + * @return the maven.xml file
  + */
  +public File getMavenXml()
  +{
  +if (mavenXml == null)
  +{
  +mavenXml = new File( getFile().getParentFile(), 
MavenConstants.BUILD_FILE_NAME );
  +}
  +return mavenXml;
  +}
  +
  +/**
  + * @return true if the maven.xml file for the project exists
  + */
  +public boolean hasMavenXml()
  +{
  +return getMavenXml().exists();
   }
   
   /**
  
  
  

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

[jira] Updated: (MAVEN-255) maven.username does NOT necessarily need to be set

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 1:25 AM
Changes:
 Version changed from 1.1
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-255
Summary: maven.username does NOT necessarily need to be set
   Type: Improvement

 Status: Assigned
   Priority: Trivial

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Fix Fors:
 1.1

   Assignee: Ben Walding
   Reporter: Ben Walding

Created: Wed, 5 Feb 2003 6:09 AM
Updated: Mon, 4 Aug 2003 1:25 AM

Description:
There is no real reason that maven.username needs to be set for ssh deployments.

The file ~/.ssh/config is often used to store all the pertinent information for the 
connection. Including ports, user ids, keys, compression etc.


-
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-540) Property: maven.plugin.dir doesn't work

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 1:25 AM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-540
Summary: Property: maven.plugin.dir doesn't work
   Type: Bug

 Status: Unassigned
   Priority: Trivial

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 release
   Fix Fors:
 1.1
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: Olaf Kaus

Created: Wed, 2 Jul 2003 10:37 AM
Updated: Mon, 4 Aug 2003 1:25 AM
Environment: Windows NT, JDK1.3.1_04

Description:
I put the following lines in the build.properties-File in $user.home\build.properties 
(c:\Winnt\profiles\account\build.properties)

maven.repo.local = ${maven.home}/../maven_repository
maven.plugin.dir = ${maven.home}/../maven_plugins

The entry for the repository works fine, but for the maven.plugin.dir doesn't work.
The NT file-structure looks like this:
d:\maven-1.0-beta-9\bin\..
d:\maven-1.0-beta-9\lib\..
d:\maven_repository
d:\maven_plugins

The MAVEN_HOME-Env maps to: d:\maven-1.0-beta-9\

so, whats wrong?



-
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-255) maven.username does NOT necessarily need to be set

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 1:22 AM
Comment:
A patch would help
Changes:
 environment changed to 
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-255
Summary: maven.username does NOT necessarily need to be set
   Type: Improvement

 Status: Assigned
   Priority: Trivial

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Versions:
 1.1

   Assignee: Ben Walding
   Reporter: Ben Walding

Created: Wed, 5 Feb 2003 6:09 AM
Updated: Mon, 4 Aug 2003 1:22 AM

Description:
There is no real reason that maven.username needs to be set for ssh deployments.

The file ~/.ssh/config is often used to store all the pertinent information for the 
connection. Including ports, user ids, keys, compression etc.


-
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] Closed: (MAVEN-254) maven.bat has incorrect syntax on WinXP's cmd.exe

2003-08-03 Thread jira

Message:

   The following issue has been closed.

   Resolver: dion gillard
   Date: Mon, 4 Aug 2003 1:20 AM

Me either
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-254
Summary: maven.bat has incorrect syntax on WinXP's cmd.exe
   Type: Bug

 Status: Closed
   Priority: Trivial
 Resolution: CANNOT REPRODUCE

 Time Spent: Unknown
  Remaining: 10 minutes

Project: maven
 Components: 
 core
   Fix Fors:
 1.0-rc1
   Versions:
 1.0-beta-7

   Assignee: 
   Reporter: Carlos Villela

Created: Tue, 4 Feb 2003 3:41 PM
Updated: Mon, 4 Aug 2003 1:20 AM
Environment: Microsoft Windows XP [version 5.1.2600], using cmd.exe, JDK 1.4.0

Description:
The provided maven.bat double-quotes -D runtime definitions, and the VM interprets 
this incorrectly, giving the user a command-line options help page.

I fixed it re-quoting the following lines:

SET MAVEN_OPTS=-Xmx128m
REM -- The following values are quoted as MAVEN_HOME might contain spaces
SET JAVA="%JAVA_HOME%\bin\java"
SET MAVEN_OPTS=%MAVEN_OPTS% -Dmaven.home="%MAVEN_HOME%"
SET MAVEN_OPTS=%MAVEN_OPTS% -Dtools.jar="%JAVA_HOME%\lib\tools.jar"
SET MAVEN_OPTS=%MAVEN_OPTS% -Dforehead.conf.file="%MAVEN_HOME%\bin\forehead.conf"
SET MAVEN_CLASSPATH="%MAVEN_HOME%\lib\forehead-1.0-beta-4.jar"
SET MAVEN_MAIN=com.werken.forehead.Forehead



-
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-607) Updated IDEA plugin for Aurora (plugin attached)

2003-08-03 Thread jira

The following comment has been added to this issue:

 Author: Brett Porter
Created: Mon, 4 Aug 2003 12:58 AM
   Body:
I altogether missed this, and was about to start on this myself separately.

I'll take this away and use it as a base for what I was doing; as well as fixing the 
issues listed here.
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-607
Summary: Updated IDEA plugin for Aurora (plugin attached)
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-other
   Fix Fors:
 1.1
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: Mike Cannon-Brookes

Created: Thu, 24 Jul 2003 4:22 AM
Updated: Mon, 4 Aug 2003 12:54 AM

Description:
We've created a plugin which generates IDEA's .ipr, .iml and .iws files. It works with 
IDEA Aurura EAP 856 build. Not sure it will work with other builds yet, but we will 
endeavour to update it going forward.

I've attached a ZIP of the plugin here.


-
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-607) Updated IDEA plugin for Aurora (plugin attached)

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:54 AM
Comment:
The issues discussed here haven't been resolved
Changes:
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-607
Summary: Updated IDEA plugin for Aurora (plugin attached)
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-other
   Fix Fors:
 1.1
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: Mike Cannon-Brookes

Created: Thu, 24 Jul 2003 4:22 AM
Updated: Mon, 4 Aug 2003 12:54 AM

Description:
We've created a plugin which generates IDEA's .ipr, .iml and .iws files. It works with 
IDEA Aurura EAP 856 build. Not sure it will work with other builds yet, but we will 
endeavour to update it going forward.

I've attached a ZIP of the plugin here.


-
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-604) [multiproject] maven.multiproject.excludes should include default excludes values.

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:54 AM
Comment:
A patch would help
Changes:
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-604
Summary: [multiproject] maven.multiproject.excludes should include default 
excludes values.
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-other
   Fix Fors:
 1.1
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: matthew hawthorne

Created: Wed, 23 Jul 2003 6:26 PM
Updated: Mon, 4 Aug 2003 12:54 AM
Environment: windows 2k // CYGWIN_NT-5.0

Description:
When the multiproject plugin searches for project.xml files, it finds them even if 
they are in directories that are typically excluded, such as a "CVS" directory.

For example, it found a project.xml file that was not only in , but also 
in /CVS/Base, which caused it to build the project twice.

I think that the default excludes values from ant should be good enough.


-
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-593) Jbuilder plugin - can't find home directory

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:52 AM
Changes:
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-593
Summary: Jbuilder plugin - can't find home directory
   Type: Bug

 Status: Unassigned
   Priority: Blocker

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-other
   Fix Fors:
 1.1
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: Aleksander Blomsk?ld

Created: Mon, 21 Jul 2003 5:51 AM
Updated: Mon, 4 Aug 2003 12:52 AM

Description:
The following errormessage comes up evry time I try to use the jbuilder plugin:

BUILD FAILED
File.. file:/C:/Documents and Settings/Aleksander 
Blomskold/.maven/plugins/maven-jbuilder-plugin-1.3-SNAPSHOT/
Element... fail
Line.. 464
Column 25
+--
| ERROR!
|
| A JBuilder installation could not be found.
+--
Total time:  3 seconds

I've tried to set the maven.jbuilder.userHome attribute, but it still doesn't work.


-
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-594) NullPointerException in jbuilder-plugin

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:53 AM
Changes:
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-594
Summary: NullPointerException in jbuilder-plugin
   Type: Bug

 Status: Unassigned
   Priority: Blocker

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-other
   Fix Fors:
 1.1
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: Aleksander Blomsk?ld

Created: Mon, 21 Jul 2003 6:16 AM
Updated: Mon, 4 Aug 2003 12:53 AM

Description:
I get the following error while trying to use the jbuilder plugin.

BUILD FAILED
File.. file:/C:/Documents and Settings/Aleksander 
Blomskold/.maven/plugins/maven-jbuilder-plugin-1.3-SNAPSHOT/
Element... jbuilder:generateDependencyLibrary
Line.. 482
Column 47
java.lang.NullPointerException
Total time:  3 seconds



-
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] Closed: (MAVEN-530) element distribution is undefined in maven-project.xsd

2003-08-03 Thread jira

Message:

   The following issue has been closed.

   Resolver: dion gillard
   Date: Mon, 4 Aug 2003 12:51 AM

Fixed a while back
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-530
Summary: element distribution is undefined in maven-project.xsd
   Type: Bug

 Status: Closed
   Priority: Major
 Resolution: FIXED

 Time Spent: Unknown
  Remaining: 1 hour

Project: maven
   Fix Fors:
 1.0-rc1
   Versions:
 1.0-beta-9

   Assignee: 
   Reporter: Abdelkrim BOUJRAF

Created: Mon, 30 Jun 2003 11:16 AM
Updated: Mon, 4 Aug 2003 12:51 AM
Environment: Windows 2000 Server, XML Spy 5 release 4

Description:
I try to create a maven.xml file with XML Spy.
Unfortunately when I try to save my maven.xml file I get an error from the schema 
validator saying that "element 'distribution' is undefined".

Effectively the maven-project.xsd provided in the maven-1.0-beta-9.zip distribution, 
you can find the following schema code:


  
  
  






  



But the 'distribution' element is unfortunately undefined in the whole file.

Same problem occurs in maven-1.0-beta-8.zip version.

Either the 'distribution' element is defined in another schema file or the 
'distribution' name is incorrect.




-
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-528) I would like more control over the packages that javadoc uses to generate online documentation

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:50 AM
Comment:
Patches would help
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-528
Summary: I would like more control over the packages that javadoc uses to generate 
online documentation
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-other
   Fix Fors:
 1.1
   Versions:
 1.0-beta-8
 1.0-beta-9
 1.0-beta-10

   Assignee: 
   Reporter: Julian Payne

Created: Mon, 30 Jun 2003 7:58 AM
Updated: Mon, 4 Aug 2003 12:50 AM

Description:
Today the javadoc plugin takes the list of packages to be what is in the POM and it 
then appends ".*" on the end of pom.package.

In our case we will put "a.b.c" as the package but there are some sub-packages that 
should not be documented via javadoc. In this case I would like to be able to specify 
"a.b.c.d,a.b.c.e.f" as the list of packages to document.

I can suggest 2 possible ways to implement this:

1) If pom.package has a comma in it then don't add the ".*"

2) Add a new property for the plugin that overrides the pom.package if, and only if, 
it exists

Thanks,

Julian Payne


-
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-525) maven-eclipse-plugin does not generate all artifacts one could expect

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:22 AM
Changes:
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-525
Summary: maven-eclipse-plugin does not generate all artifacts one could expect
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-other
   Fix Fors:
 1.1
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: gilles dodinet

Created: Mon, 30 Jun 2003 1:43 AM
Updated: Mon, 4 Aug 2003 12:22 AM

Description:
eclipse plugin doesnot generate all expected artifacts. for instance :
* if build/aspectSourceDirectory is present in the pom, a source folder 
corresponding to this source directory should be added to the project AND aspectj 
nature should be attached to the eclipse project (assuming aspectj plugin has been 
installed)
* if build/resource(s) are declared in the pom, a source folder should be created 
in the eclipse project for every unique resource folder. same goes for 
unitTest/resources (and perhaps integrationUnitTest ? never used it so im not sure of 
whats declared in the pom)


-
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-527) I would like to control the output of the unit tests

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:23 AM
Comment:
A patch would help
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-527
Summary: I would like to control the output of the unit tests
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-test
   Fix Fors:
 1.1
   Versions:
 1.0-beta-8
 1.0-beta-9
 1.0-beta-10

   Assignee: 
   Reporter: Julian Payne

Created: Mon, 30 Jun 2003 7:52 AM
Updated: Mon, 4 Aug 2003 12:23 AM

Description:
I would like to be able to control the printing of exceptions when running the unit 
tests. Today the output is hardcoded as:




Ideally what I would like is to have a property to control the printSummary:

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-526) Add timeouts to the test plugin

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:22 AM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-526
Summary: Add timeouts to the test plugin
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-test
   Fix Fors:
 1.1
   Versions:
 1.0-beta-8
 1.0-beta-9
 1.0-beta-10

   Assignee: 
   Reporter: Julian Payne

Created: Mon, 30 Jun 2003 7:43 AM
Updated: Mon, 4 Aug 2003 12:22 AM

Description:
I need to be able to set a timeout in the unit tests because we have graphical tests 
that block from time to time.

Here is what I would like to be added in the plugin.jelly as part of the junit element:

 


  





-
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-515) unit test levels

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:21 AM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-515
Summary: unit test levels
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Fix Fors:
 1.1

   Assignee: 
   Reporter: Brett Porter

Created: Mon, 23 Jun 2003 9:53 AM
Updated: Mon, 4 Aug 2003 12:21 AM

Description:
This is to track the progress of what is decided about this feature. Once again, happy 
to implement when I get time as I need it for work :)

here is the proposal sent to the list:
proposal: allow multiple unit test sets in the POM
justification: some take a long time to run or require resources not always present, 
and should be omitted in regular development, but run in nightly builds for example.

implementation:


  default (same as if type ommitted)
 ... as before ...



  performance
...



  integration
...



  touchstone
...


By default, just the first is run, but by setting 
-Dmaven.test.sets=performance,integration
Then those will be run (and default which is always run)

There will also be the special case of -Dmaven.test.sets=all, which will run 
everything. Or perhaps test:test-all?

They could all use the same unitTestSourceDirectory, or move those into each unitTest 
set (with code to keep it backwards compatible).

Each set would have its own junit report I imagine.


-
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-463) Project properties overwrite all other properties when Reactor is used.

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:21 AM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-463
Summary: Project properties overwrite all other properties when Reactor is used.
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 maven-reactor-plugin
   Fix Fors:
 1.0-final
   Versions:
 maven-new-unreleased

   Assignee: 
   Reporter: Charles Chan

Created: Wed, 4 Jun 2003 12:43 PM
Updated: Mon, 4 Aug 2003 12:21 AM

Description:
If you execute the reactor Goal in Project A, Project A's
properties overwrites all other definitions. If you
execute in Project B where 'conf.dir' is not defined,
you will get the right behavior. I am going to report
this as a bug in JIRA.

=

Apparently, Maven allows only one definition of a
property in reactor.

Consider the following scenario:

Project A
project.properties
==
conf.dir=/A/conf

Project B
project.properties
==
No definition of conf.dir

My Plugin
plugin.jelly


  conf.dir=${conf.dir}


plugin.properties
=
(default conf.dir)
conf.dir=${maven.src.dir}/conf

If you have a reactor that executes both A and B's
testProperty goal, A's conf.dir property will be used
when running B's goal.

This is unexpected because when we execute B by
itself, it uses the default conf.dir property defined
in the Plugin.




-
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-460) Overhaul of docbook plugin

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:20 AM
Comment:
Still waiting for Gabriel
Changes:
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-460
Summary: Overhaul of docbook plugin
   Type: New Feature

 Status: Assigned
   Priority: Major

 Time Spent: Unknown
  Remaining: 1 week

Project: maven
 Components: 
 documentation
   Fix Fors:
 1.1

   Assignee: dion gillard
   Reporter: Gabriel Sjoberg

Created: Tue, 3 Jun 2003 11:38 AM
Updated: Mon, 4 Aug 2003 12:20 AM
Environment: java

Description:
I've pretty much completely redone the docbook plugin.  I merged the current plugin 
with the one at sourceforge.  It now supports full, chunked, and simple docbook.  It 
can translate into pdf, html, and fo.  Soon I'll add a few more output formats.  
Because of the differences, a diff isn't really helpful, so I'm attaching a zip of the 
plugin as it stands now.  It still needs a bit of work, but I want to hear from others 
before I do too much more with this.


-
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-413) Allow support in pdf plugin for alternative navigation.xml

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:19 AM
Comment:
Got a patch?
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-413
Summary: Allow support in pdf plugin for alternative navigation.xml
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Fix Fors:
 1.1
   Versions:
 1.0-beta-9

   Assignee: 
   Reporter: Yannick Menager

Created: Tue, 22 Apr 2003 6:11 AM
Updated: Mon, 4 Aug 2003 12:19 AM

Description:
I've been playing with the pdf plugin to generate documentations as well as the 
project website. However the standard navigation.xml isn't very appropriate for that ( 
generates empty pages for external links, or deeply nested pages don't show up ). So 
I've come to use an alternative navigation.xml to generate the pdf file. It would be 
nice if the plugin supported a property allowing to set an alternative navigation.xml 
( as a hack I'm currently using preGoal and postGoal to move the 2 navigation.xml 
around ).


-
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-441) a property to exclude sites from proxy is needed

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:20 AM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-441
Summary: a property to exclude sites from proxy is needed
   Type: Improvement

 Status: Assigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Fix Fors:
 1.1
   Versions:
 1.0-beta-9

   Assignee: Ben Walding
   Reporter: Mattias Neuling

Created: Fri, 23 May 2003 3:54 AM
Updated: Mon, 4 Aug 2003 12:20 AM
Environment: Two repositorys: one reachable via internet, the other one via local 
network.

Description:
If you have proxy settings in the build.properties Maven can only access the internet 
repository. On the other hand if there are no proxy settings Maven can only access the 
local network repository.

So a new property is needed to make Maven accessible to the internet and the lan 
repository. The property could be "maven.proxy.exclude" where you can set the hosts 
are not reachable via proxy.

e.g.
maven.proxy.host = yourproxy
maven.proxy.port = 4711
maven.proxy.exclude = 192.168.0.123, 10.7.2.123, *.yourdomain.com



-
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-391) FAQ Plugin - CDATA section is not processed correctly in tag.

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:17 AM
Changes:
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-391
Summary: FAQ Plugin - CDATA section is not processed correctly in  tag.
   Type: Bug

 Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: 1 week

Project: maven
   Fix Fors:
 1.1
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: dion gillard

Created: Sun, 13 Apr 2003 7:55 PM
Updated: Mon, 4 Aug 2003 12:17 AM
Environment: N/A

Description:
"Willie Vu" 14/04/2003 02:34 AM


CDATA section is not processed correctly in  tag.

For instance, I have the following:




It results






-
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-405) maven.test.skip should also skip test compiles

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:17 AM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-405
Summary: maven.test.skip should also skip test compiles
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-test
   Fix Fors:
 1.1
   Versions:
 1.0-beta-9

   Assignee: 
   Reporter: David Zeleznik

Created: Fri, 18 Apr 2003 8:16 AM
Updated: Mon, 4 Aug 2003 12:17 AM

Description:
In beta9, the maven.test.skip property was added which allows you
to skip running all of the unit tests. However, this is not as useful as it may seem 
because when set true, all of the tests are still compiled. This flag should also 
no-op the test:compile goal, just as it does the test:test goal. Currently it is not 
possible to use this flag to build a jar when the tests have not been updated and are 
not fully compilable.


-
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] Closed: (MAVEN-409) Add new goal to plugin plugin to download and manipulate installed plugins

2003-08-03 Thread jira

Message:

   The following issue has been closed.

   Resolver: dion gillard
   Date: Mon, 4 Aug 2003 12:16 AM

Dupe of maven-536
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-409
Summary: Add new goal to plugin plugin to download and manipulate installed plugins
   Type: Improvement

 Status: Closed
   Priority: Minor
 Resolution: DUPLICATE

 Time Spent: Unknown
  Remaining: 2 hours

Project: maven
   Versions:
 1.0-beta-10

   Assignee: Ben Walding
   Reporter: Ben Walding

Created: Sun, 20 Apr 2003 5:57 PM
Updated: Mon, 4 Aug 2003 12:16 AM

Description:
Create some new goals to manipulate the installed plugins

eg.

maven plugin:remove maven-jar-plugin

maven plugin:get http://maven-plugins.sf.net/maven-jar-plugin-v1.0.jar




(This will get us away from forcing new releases down on users to get plugin fixes).  
More thought will be need in so far that the pom will need to specify minimum core 
versions, but that is on it's way anyway.


-
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-351) ant-plugin not obeying jar override

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:15 AM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-351
Summary: ant-plugin not obeying jar override
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.1
   Versions:
 1.0-beta-9

   Assignee: 
   Reporter: Mike Bowler

Created: Tue, 25 Mar 2003 12:16 PM
Updated: Mon, 4 Aug 2003 12:15 AM
Environment: Sun JDK1.3.1 on windows.  Maven from cvs on March 24, 2003

Description:
When using the ant-plugin to generate an ant build file, the generated  tags do 
not obey the jar overrides specified in project.properties.  All  tags attempt to 
load the jars from ibiblio even though an override was specified that points to the 
local harddrive.  Overrides are being used because the jar files in question are 
proprietary and cannot be uploaded to ibiblio.


-
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] Closed: (MAVEN-386) Ampersands in navigation.xml being escaped twice during xml parsing

2003-08-03 Thread jira

Message:

   The following issue has been closed.

   Resolver: dion gillard
   Date: Mon, 4 Aug 2003 12:14 AM

Noone's come back on trying to reproduce this.
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-386
Summary: Ampersands in navigation.xml being escaped twice during xml parsing
   Type: Bug

 Status: Closed
   Priority: Minor
 Resolution: CANNOT REPRODUCE

 Time Spent: Unknown
  Remaining: 0 minutes

Project: maven
 Components: 
 plugin-xdoc
   Fix Fors:
 1.0-rc1
   Versions:
 1.0-beta-8

   Assignee: 
   Reporter: Andrew Mace

Created: Fri, 11 Apr 2003 6:21 AM
Updated: Mon, 4 Aug 2003 12:14 AM

Description:
Within my Maven navigation.xml i would like to include a URL that includes parameter 
(&s).  So if I place & or & after the xml is parsed the URL that is generated 
in the html files have '&' instead of an '&'
I have the xml encoding ISO-8859-1




-
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-389) Create a plugin downloader goal

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:13 AM
Changes:
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-389
Summary: Create a plugin downloader goal
   Type: New Feature

 Status: Assigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: 2 hours

Project: maven
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-10

   Assignee: dion gillard
   Reporter: Ben Walding

Created: Sat, 12 Apr 2003 9:58 AM
Updated: Mon, 4 Aug 2003 12:13 AM

Description:
Create a plugin capable of downloading and installing 3rd party plugins.

Ideally it would work like this:

maven plugin:download http://crazybob.com/plugin-aptdoc-1.0.jar

Which would download and unpack the plugin

Things to be done
1) Make maven take command line arguments properly (could be stuffed into a list in 
the context / arg.0 arg.1 etc
2) Create the new goals (make sure they are proxy aware - HttpUtils
3) Profit!


Ultimately for known plugins we should be able to do
maven plugin:download maven-aptdoc-plugin

But that is a fair way away at the moment




-
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-352) Generation of application.xml and inclusion of project's war/ejb in ear

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:11 AM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-352
Summary: Generation of application.xml and inclusion of project's war/ejb in ear
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Fix Fors:
 1.1
   Versions:
 1.0-beta-9

   Assignee: 
   Reporter: Christian Amor Kvalheim

Created: Wed, 26 Mar 2003 9:09 AM
Updated: Mon, 4 Aug 2003 12:11 AM

Description:
This patch adds two new features in the ear plugin:

1) Automatic generation of application.xml
2) Possibility to automatically include ejb and war files from the same project.

Documentation and changelog has been updated.


-
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-384) War and Ear Plugin Don't Handle Jar Overrides For Bundling

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:11 AM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-384
Summary: War and Ear Plugin Don't Handle Jar Overrides For Bundling
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-war
   Fix Fors:
 1.1

   Assignee: 
   Reporter: Anthony Vito

Created: Thu, 10 Apr 2003 5:51 PM
Updated: Mon, 4 Aug 2003 12:11 AM
Environment: NA

Description:
The war and ear plugin both suffer from the same flaw of hard coding the local 
repository jar path for the means of bundling dependencies. This obviously doesn't 
work when jar overriding has occured. The solution is probably not to have all plugins 
handle overrides, but a more global approach. The Project Objects 
"getDependencyPath(String id)" Method might be of interest here, I'm hoping they're 
miss documented.


-
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-384) War and Ear Plugin Don't Handle Jar Overrides For Bundling

2003-08-03 Thread jira

The following comment has been added to this issue:

 Author: dion gillard
Created: Mon, 4 Aug 2003 12:10 AM
   Body:
Is this still an issue?
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-384
Summary: War and Ear Plugin Don't Handle Jar Overrides For Bundling
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: 0 minutes

Project: maven
 Components: 
 plugin-war
   Fix Fors:
 1.1

   Assignee: 
   Reporter: Anthony Vito

Created: Thu, 10 Apr 2003 5:51 PM
Updated: Tue, 29 Apr 2003 9:03 AM
Environment: NA

Description:
The war and ear plugin both suffer from the same flaw of hard coding the local 
repository jar path for the means of bundling dependencies. This obviously doesn't 
work when jar overriding has occured. The solution is probably not to have all plugins 
handle overrides, but a more global approach. The Project Objects 
"getDependencyPath(String id)" Method might be of interest here, I'm hoping they're 
miss documented.


-
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-375) App server plugin docs are out of date

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:10 AM
Changes:
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-375
Summary: App server plugin docs are out of date
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: 1 hour

Project: maven
   Fix Fors:
 1.1
   Versions:
 1.0-beta-9

   Assignee: 
   Reporter: Ben Walding

Created: Sat, 5 Apr 2003 7:19 PM
Updated: Mon, 4 Aug 2003 12:10 AM

Description:
The app server docs should be updated to match the plugin. They are a mess of J2EE 
plugin references


-
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-352) Generation of application.xml and inclusion of project's war/ejb in ear

2003-08-03 Thread jira

The following comment has been added to this issue:

 Author: dion gillard
Created: Mon, 4 Aug 2003 12:09 AM
   Body:
I'm not sure if we want to have EJB, WAR and EAR all in one project.
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-352
Summary: Generation of application.xml and inclusion of project's war/ejb in ear
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: 0 minutes

Project: maven
   Versions:
 1.0-beta-9

   Assignee: 
   Reporter: Christian Amor Kvalheim

Created: Wed, 26 Mar 2003 9:09 AM
Updated: Wed, 26 Mar 2003 9:11 AM

Description:
This patch adds two new features in the ear plugin:

1) Automatic generation of application.xml
2) Possibility to automatically include ejb and war files from the same project.

Documentation and changelog has been updated.


-
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] Closed: (MAVEN-347) Torque plugin goals can't access JDBC driver

2003-08-03 Thread jira

Message:

   The following issue has been closed.

   Resolver: dion gillard
   Date: Mon, 4 Aug 2003 12:07 AM

Applied patch
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-347
Summary: Torque plugin goals can't access JDBC driver
   Type: Bug

 Status: Closed
   Priority: Major
 Resolution: FIXED

 Time Spent: Unknown
  Remaining: 0 minutes

Project: maven
 Components: 
 core
   Fix Fors:
 1.0-rc1
   Versions:
 1.0-beta-9

   Assignee: 
   Reporter: Jim Crossley

Created: Mon, 24 Mar 2003 6:08 PM
Updated: Mon, 4 Aug 2003 12:07 AM

Description:
Since torque's behavior is encapsulated in Ant tasks, and Ant requires its libs to be 
in the root classloader, it seems the only way to make the driver available is to put 
something like this in the plugin's pom:


  mysql
  2.0.14
  mysql-connector-java-2.0.14-bin.jar
  http://www.mysql.com/
  
root
  


But it's gross to do that for all the possible jdbc drivers.  It's less gross to put 
the above in the project's pom, but that doesn't work.  :-(

Even less gross might be to reimplement the torque behavior without Ant.


-
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/src/plugins-build/torque plugin.jelly

2003-08-03 Thread dion

dion2003/08/03 22:03:02

  Modified:src/plugins-build/torque plugin.jelly
  Log:
  Applied patch for MAVEN-347
  
  Revision  ChangesPath
  1.8   +1 -0  maven/src/plugins-build/torque/plugin.jelly
  
  Index: plugin.jelly
  ===
  RCS file: /home/cvs/maven/src/plugins-build/torque/plugin.jelly,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- plugin.jelly  9 Jul 2003 12:58:50 -   1.7
  +++ plugin.jelly  4 Aug 2003 05:03:01 -   1.8
  @@ -34,6 +34,7 @@
 
 
 
  +

[jira] Updated: (MAVEN-344) provide build:start goal to attach other goals to

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:05 AM
Changes:
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-344
Summary: provide build:start goal to attach other goals to
   Type: Improvement

 Status: Assigned
   Priority: Major

 Time Spent: Unknown
  Remaining: 1 hour

Project: maven
 Components: 
 core
   Fix Fors:
 1.1
   Versions:
 1.0-beta-9

   Assignee: Jason van Zyl
   Reporter: Ben Walding

Created: Sun, 23 Mar 2003 6:02 AM
Updated: Mon, 4 Aug 2003 12:05 AM

Description:
We need a goal that occurs before dependency resolution so that tasks that help fix 
dep resolution can occur.

eg.

I would like to create the concept of project repository files that get pushed to the 
local repository - eg. activation / mail and all that other stuff we can't have on 
ibiblio.


  

  

  



-
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-332) INTERNAL ERROR: Trying to override java:jar

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:05 AM
Comment:
Has this been fixed Jason?
Changes:
 environment changed to 
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-332
Summary: INTERNAL ERROR: Trying to override java:jar
   Type: Bug

 Status: Assigned
   Priority: Critical

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-9

   Assignee: Jason van Zyl
   Reporter: Charles Chan

Created: Wed, 12 Mar 2003 4:32 PM
Updated: Mon, 4 Aug 2003 12:05 AM

Description:
On Thu, 2003-01-09 at 10:20, Chan, Charles wrote:
> (I am using Maven-CVS Head)
> 
> Hi, I am trying to replace java:jar target but when I invoke jar:install, I
> get the following error:
> 
> INTERNAL ERROR
> Reference made to goal 'test:test' which has no definition.
> 
> 
> Here's my maven.xml:
> 
> 
> 
>   
> TEST
>   
> 
> 
> 
> project.xml
> 
> 
> 
>   3
>   test
>   Test
> 
> 
> I invoke "maven jar:install"
> 
> However, if I duplicate jar:install (copy and paste from plugin.jelly) in my
> maven.xml, everything works (I have to change prereqs to attainGoal,
> however)
> 
> Any idea?

Yup, it's a little prereq bug in the plugin dependency processing. Will
try to clear this up today. It's biting me too :-) And I'll add
something to the touchstone too.

> Charles
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 
-- 
jvz.


-
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-324) wrong parameter order in deploy plugin

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:03 AM
Comment:
Is this still an issue?
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-324
Summary: wrong parameter order in deploy plugin
   Type: Bug

 Status: In Progress
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-dist
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-9

   Assignee: Ben Walding
   Reporter: Fabian Ritzmann

Created: Tue, 11 Mar 2003 4:10 AM
Updated: Mon, 4 Aug 2003 12:03 AM
Environment: Windows 2000
Putty (ssh implementation)

Description:
The plugin.jelly in the deploy plugin contains the following lines:


  


This doesn't work with my ssh client (Putty). The parameters (-l ${username}) need to 
be before the siteAddress.




-
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-321) Make clover run over unit tests as well

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:03 AM
Changes:
 environment changed to 
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-321
Summary: Make clover run over unit tests as well
   Type: Improvement

 Status: Assigned
   Priority: Major

 Time Spent: Unknown
  Remaining: 1 hour

Project: maven
   Fix Fors:
 1.0-final

   Assignee: Ben Walding
   Reporter: Ben Walding

Created: Mon, 10 Mar 2003 5:05 AM
Updated: Mon, 4 Aug 2003 12:03 AM

Description:
A slightly more radical approach to code coverage is to get the coverage program to 
instrument the test cases to make sure they are all running properly also.

Add this as an optional capability for clover and make it off by default.


eg.

maven.clover.instrument.tests = true | false






-
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-318) OutOfMemoryError during site:generate

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Mon, 4 Aug 2003 12:03 AM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-318
Summary: OutOfMemoryError during site:generate
   Type: Bug

 Status: Assigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-9

   Assignee: Ben Walding
   Reporter: Quinton McCombs

Created: Thu, 6 Mar 2003 1:35 PM
Updated: Mon, 4 Aug 2003 12:03 AM
Environment: SuSE Linux 8.0, Java 1.4.1-b21

Description:
I have started getting OutOfMemoryErrors being thrown during the execution of the 
linkcheck plugin.


-
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-317) Ability to have one snapshot per development branch of a project

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:59 PM
Comment:
Should this be marked as WONTFIX?
Changes:
 environment changed to 
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-317
Summary: Ability to have one snapshot per development branch of a project
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.1

   Assignee: 
   Reporter: Quinton McCombs

Created: Thu, 6 Mar 2003 10:50 AM
Updated: Sun, 3 Aug 2003 11:59 PM

Description:
Currently, a SNAPSHOT and a timestamp jar relate to CVS HEAD of a particular project.  
For projects which have multiple development branches, this causes a problem.

I would propose that the version number of the project be added to the filename of the 
snapshot and the timestamp jar.  It should be documented in the manual that the 
version should always be the unreleased version.  

Perhaps the version number is not the right identifier to add.  I would just like to 
see something that would allow one snapshot per development branch.


-
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-295) New junit test runner

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:56 PM
Changes:
 environment changed to 
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-295
Summary: New junit test runner
   Type: Wish

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: 4 hours

Project: maven
   Fix Fors:
 1.1

   Assignee: 
   Reporter: Ben Walding

Created: Wed, 26 Feb 2003 4:27 AM
Updated: Sun, 3 Aug 2003 11:56 PM

Description:
The existing junit runner only has an all or nothing approach to forking for tests.

It would be advantageous (speedwise) if the jvm could be forked once for the entire 
set of tests.

(JVM forks are SLOOWW)


-
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-316) Ability to disable a single report via POM

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:57 PM
Changes:
 environment changed to 
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-316
Summary: Ability to disable a single report via POM
   Type: New Feature

 Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 Requested POM Additions
   Fix Fors:
 1.1

   Assignee: 
   Reporter: Quinton McCombs

Created: Thu, 6 Mar 2003 10:40 AM
Updated: Sun, 3 Aug 2003 11:57 PM

Description:
I would like to be able to disable one or more reports in the POM without having to 
list all of the reports that I do want.  For example:




  maven-linkcheck-plugin





-
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-256) does not use the global session

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:55 PM
Comment:
Is this still the case post beta 10?
Changes:
 environment changed to 
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-256
Summary:  does not use the global session
   Type: Bug

 Status: Assigned
   Priority: Critical

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-8

   Assignee: bob mcwhirter
   Reporter: Peter Lynch

Created: Thu, 6 Feb 2003 4:00 AM
Updated: Sun, 3 Aug 2003 11:55 PM

Description:
The problem:

Basically there needs to be a way to call a goal from inside another goal and
have the called goal use the current session.

The result being no new session created and all already attained goals would not
be called again by the called goal's prereqs attribute or nested  tags.

The only way to create a new session would be to use the  tags or set 
 if an attribute is decided to be the 
way to flag session creation.

Alternatively it was suggested a new tag be added called  which would always 
create a new session, and  would be reverted to use the current session.

Here is the thread from the mailing lists describing the problems and soltuions.

- Original Message - 
From: "Colin Sampaleanu" <[EMAIL PROTECTED]>
To: "Turbine Maven Users List" <[EMAIL PROTECTED]>
Cc: "Turbine Maven Developers List" <[EMAIL PROTECTED]>
Sent: Thursday, January 30, 2003 7:27 AM
Subject: Re: goals are broken, let's fix it


> bob mcwhirter wrote:
> 
> >On Thu, 30 Jan 2003, Colin Sampaleanu wrote:
> >
> >>I think that there is currently a serious problem in maven and a number 
> >>of plugins, in that 'attainGoal' is being used in various places (goals, 
> >>preGoals, and postGoals) with the expectation that the goal being named 
> >>to be attained will be part of the dependency graph of the main build 
> >>itself, and will be attained only once. However, due to the way the 
> >>werkz 'attainGoal' tag is implemented, there is no integration into the 
> >>main maven dependency session, and each invocation of attainGoal with a 
> >>specific goal will call that goal again including all its dependencies, 
> >>becoming more of a subroutine call. At best, I would say it's confusing 
> >>as hell, since the name 'attainGoal' implies something; certainly there 
> >>is some code which is using the tag with the expectation that it is 
> >>integrating into the dependency graph, and there is other code which is 
> >>using it like a subroutine call. I would also suggest there need to be 
> >>clearly named, different mechanisms, to handle both usage semantics.
> >>
> >>
> >Yah, this is a well-understood problem (at least by me, having written
> >werkz).
> >
> >Though, my non-scientific polling has resulted in me thinking that
> >most folks are now taking advantage of the fact that 
> >doesn't participate in the global session.
> >
> >ie:
> >
> > 
> > 
> > 
> > 
> >
> >Where 'clean' wouldn't fire the 2nd time if we shared in the global
> >session.
> >
> >We noodled around with keeping the current syntax and semantics the
> >same but adding a session="true" attribute for folks needing new
> >semantics.
> >
> >Or, since so many other things have changed lately, retaining backwards
> >compatibility is less important, and we could certain make 
> >behave has expected, and rename the current functionality to 
> >or  or somesuch.
> >
> >The biggest use-case we must accomodate is folks wanting to 'clean'
> >multple times and not have werkz think everything is still attained.
> >
> >Though, that could maybe be rememdied with something like:
> >
> > 
> >
> >
> > 
> >
> >That'd allow us to invalidate the werkz session and allow for rebuilds
> >without confusing werkz.
> >
> >IRC would probably be a glad place to hammer out the details.
> >
> (still cross-posting, as I think this has big implications for users as 
> well as developers...)
> 
> How are the IRC sessions typically arranged? i.e. when are you guys 
> normally on?. My main issue with IRC is that unfortunately it is blocked 
> for me during the day due to the firewall at work, although in the worst 
> case I could probably ssh to my home machine and do a text mode client 
> from there. Evenings wouldn't be a problem.
> 
> My

1.0 release

2003-08-03 Thread dion

There are a whole load of things piled up as tasks for a 1.0 release.

I've been gradually going through Jira and moving things to 1.1 or 1.0 
depending on whether I thought it was new functionality or a bug.

It'd be great if people could start working on those issues, and we could 
come to a consensus about what will be in 1.0, 1.1, 2.0 etc.
--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/

[jira] Updated: (MAVEN-271) maven -g does not list goals defined in maven.xml

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:51 PM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-271
Summary: maven -g does not list goals defined in maven.xml
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-9

   Assignee: 
   Reporter: Peter Lynch

Created: Fri, 14 Feb 2003 12:18 PM
Updated: Sun, 3 Aug 2003 11:51 PM
Environment: JDK 1.4.1_01 Windows 2000

Description:
I added the following goal to my project's maven.xml


   


I type maven -g or maven.bat -g and the goals listed do not mention this  goal 
anywhere.

Also I cleared all my cache files and still it does not list that goal.


-
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-228) Importing a jelly script used to expose goals definied in it.

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:45 PM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-228
Summary: Importing a jelly script used to expose goals definied in it.
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 jelly-integ
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-8

   Assignee: 
   Reporter: David Eric Pugh

Created: Wed, 29 Jan 2003 5:43 PM
Updated: Sun, 3 Aug 2003 11:45 PM
Environment: W2k with CVS Head

Description:
Previously, you could import a jelly script and expose the goals.  This was crucially 
import in the cactus plugin for dynamically importing the scripts for various app 
servers.  At this point, this functionality doesn't work.  Should I edit the 
touchstone code to demonstrate this?  

Here is what used to work:
  
  

  

  

  


if you do a maven -g you will see all the included file's goals are not available.


-
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-225) Missing xdoclet module results in silent failure in maven, but not in pure ant build

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:43 PM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-225
Summary: Missing xdoclet module results in silent failure in maven, but not in 
pure ant build
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-8

   Assignee: 
   Reporter: Colin Sampaleanu

Created: Tue, 28 Jan 2003 5:34 PM
Updated: Sun, 3 Aug 2003 11:43 PM
Environment: maven CVS HEAD 2003-1-28

Description:
There appears to be a silent failure and continue (instead of the appropriate 
build-breakage) happening when xdoclet is run and a needed module is not found on the 
classpath, and this would appear to be a maven problem.

Consider the following code in a pure ant based build, which uses xdoclet:
   
 ...
 
 ...
   

Now the JBossSubtask class which is a subtask of EjbDocletTask, also uses the 
JMXDocletTask, which is found in another xdoclet module entirely. When the ant based 
build is run, if the xdoclet jmx module is not found on the classpath, the build fails 
as follows:
 excerpt
xdoclet:

BUILD FAILED
file:./proj/buildTargets.xml:153: Couldn't find the class xdoclet.modules.jmx.JM
XDocletTask on the classpath: D:\src\tira\cvs\core\data-access\lib\core\log4j.ja
r;D:\src\tira\cvs\core\data-access\lib\forbuild\ejb.jar;D:\src\tira\cvs\shared\l
ib\xdoclet\xdoclet-1.2\commons-collections.jar;D:\src\tira\cvs\shared\lib\xdocle
t\xdoclet-1.2\commons-logging.jar;D:\src\tira\cvs\shared\lib\xdoclet\xdoclet-1.2
\xdoclet-bea-module.jar;D:\src\tira\cvs\shared\lib\xdoclet\xdoclet-1.2\xdoclet-e
jb-module.jar;D:\src\tira\cvs\shared\lib\xdoclet\xdoclet-1.2\xdoclet-jboss-modul
e.jar;D:\src\tira\cvs\shared\lib\xdoclet\xdoclet-1.2\xdoclet-mvcsoft-module.jar;
D:\src\tira\cvs\shared\lib\xdoclet\xdoclet-1.2\xdoclet-web-module.jar;D:\src\tir
a\cvs\shared\lib\xdoclet\xdoclet-1.2\xdoclet-xjavadoc.jar;D:\src\tira\cvs\shared
\lib\xdoclet\xdoclet-1.2\xdoclet.jar


but when maven is run, with a goal using the exact same ejbdoclet task definition, 
there is no error printed, the build is not stopped, and there is no indication that 
there is a problem, except that xdoclet does not run at all. I do not believe that 
this is an xdoclet problem. As indicated in the pure ant case, xdoclet is trying to 
stop the build when it can't find a needed module, but in the maven environment, that 
is not happening.




-
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-225) Missing xdoclet module results in silent failure in maven, but not in pure ant build

2003-08-03 Thread jira

The following comment has been added to this issue:

 Author: dion gillard
Created: Sun, 3 Aug 2003 11:39 PM
   Body:
Does this still happen on 1.0-beta-10?
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-225
Summary: Missing xdoclet module results in silent failure in maven, but not in 
pure ant build
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: 0 minutes

Project: maven
 Components: 
 core
   Versions:
 1.0-beta-8

   Assignee: 
   Reporter: Colin Sampaleanu

Created: Tue, 28 Jan 2003 5:34 PM
Updated: Fri, 11 Apr 2003 2:22 PM
Environment: maven CVS HEAD 2003-1-28

Description:
There appears to be a silent failure and continue (instead of the appropriate 
build-breakage) happening when xdoclet is run and a needed module is not found on the 
classpath, and this would appear to be a maven problem.

Consider the following code in a pure ant based build, which uses xdoclet:
   
 ...
 
 ...
   

Now the JBossSubtask class which is a subtask of EjbDocletTask, also uses the 
JMXDocletTask, which is found in another xdoclet module entirely. When the ant based 
build is run, if the xdoclet jmx module is not found on the classpath, the build fails 
as follows:
 excerpt
xdoclet:

BUILD FAILED
file:./proj/buildTargets.xml:153: Couldn't find the class xdoclet.modules.jmx.JM
XDocletTask on the classpath: D:\src\tira\cvs\core\data-access\lib\core\log4j.ja
r;D:\src\tira\cvs\core\data-access\lib\forbuild\ejb.jar;D:\src\tira\cvs\shared\l
ib\xdoclet\xdoclet-1.2\commons-collections.jar;D:\src\tira\cvs\shared\lib\xdocle
t\xdoclet-1.2\commons-logging.jar;D:\src\tira\cvs\shared\lib\xdoclet\xdoclet-1.2
\xdoclet-bea-module.jar;D:\src\tira\cvs\shared\lib\xdoclet\xdoclet-1.2\xdoclet-e
jb-module.jar;D:\src\tira\cvs\shared\lib\xdoclet\xdoclet-1.2\xdoclet-jboss-modul
e.jar;D:\src\tira\cvs\shared\lib\xdoclet\xdoclet-1.2\xdoclet-mvcsoft-module.jar;
D:\src\tira\cvs\shared\lib\xdoclet\xdoclet-1.2\xdoclet-web-module.jar;D:\src\tir
a\cvs\shared\lib\xdoclet\xdoclet-1.2\xdoclet-xjavadoc.jar;D:\src\tira\cvs\shared
\lib\xdoclet\xdoclet-1.2\xdoclet.jar


but when maven is run, with a goal using the exact same ejbdoclet task definition, 
there is no error printed, the build is not stopped, and there is no indication that 
there is a problem, except that xdoclet does not run at all. I do not believe that 
this is an xdoclet problem. As indicated in the pure ant case, xdoclet is trying to 
stop the build when it can't find a needed module, but in the maven environment, that 
is not happening.




-
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-202) unable to override java:jar

2003-08-03 Thread jira

The following comment has been added to this issue:

 Author: dion gillard
Created: Sun, 3 Aug 2003 11:39 PM
   Body:
Is this still an issue?
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-202
Summary: unable to override java:jar
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: 0 minutes

Project: maven
 Components: 
 core
   Fix Fors:
 1.1
   Versions:
 1.0-beta-8

   Assignee: 
   Reporter: Charles Chan

Created: Tue, 14 Jan 2003 10:09 AM
Updated: Fri, 11 Apr 2003 2:22 PM

Description:
(I am using Maven-CVS Head)

Hi, I am trying to replace java:jar target but when I invoke jar:install, I
get the following error:

INTERNAL ERROR
Reference made to goal 'test:test' which has no definition.


Here's my maven.xml:



  
TEST
  



project.xml



  3
  test
  Test


I invoke "maven jar:install"

However, if I duplicate jar:install (copy and paste from plugin.jelly) in my
maven.xml, everything works (I have to change prereqs to attainGoal,
however)

Any idea?
Charles


-
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-202) unable to override java:jar

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:39 PM
Changes:
 environment changed to 
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-202
Summary: unable to override java:jar
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.1
   Versions:
 1.0-beta-8

   Assignee: 
   Reporter: Charles Chan

Created: Tue, 14 Jan 2003 10:09 AM
Updated: Sun, 3 Aug 2003 11:39 PM

Description:
(I am using Maven-CVS Head)

Hi, I am trying to replace java:jar target but when I invoke jar:install, I
get the following error:

INTERNAL ERROR
Reference made to goal 'test:test' which has no definition.


Here's my maven.xml:



  
TEST
  



project.xml



  3
  test
  Test


I invoke "maven jar:install"

However, if I duplicate jar:install (copy and paste from plugin.jelly) in my
maven.xml, everything works (I have to change prereqs to attainGoal,
however)

Any idea?
Charles


-
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-197) Artifact type handling - there is no way no add artifact of other type than jar to build classpath

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:37 PM
Changes:
 environment changed to 
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-197
Summary: Artifact type handling - there is no way no add artifact of other type 
than jar to build classpath
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-8

   Assignee: 
   Reporter: Michal Maczka

Created: Sun, 12 Jan 2003 12:06 PM
Updated: Sun, 3 Aug 2003 11:37 PM

Description:
Currently Maven adds to build class path only dependencies which
type is "jar".

There are dependencies of other type than jar (e.g. ejb modules)
which also contain java class files. 


Solution:



A Simple solution yet compatible with current code and additionally supporting adding 
to build class path dependencies of type "ejb" can look like follows:

1. add to artifact information if artifact should be added to build class path (e.g. 
new property addToClasspath). 
This information will be set by ArtifactFactory. More advanced implementation 
ArtifactFactory 
(e.g. configurable through config file) should be smart enough to set this property 
correctly basing on dependency type


public boolean addToClasspath() 
{
   return (getType().equals("jar") || getType().equals("ejb")); 
 
}



2. In class org.apache.maven.DependencyClasspathBuilder

This property of artifact can be than used in following way.


/**
 * Create the dependency classpath.
 *
 * @throws Exception If an error occurs while creating the classpath.
 */
public static String build( Project project )
throws Exception
{
//Path classpath = new Path( getProject().getRootContext().getAntProject() );
StringBuffer classpath = new StringBuffer();

for ( Iterator i = project.getArtifacts().iterator(); i.hasNext(); )
{
Artifact artifact = (Artifact) i.next();
Dependency d = artifact.getDependency();

if ()

// Only add jar dependencies to the classpath
if ( artifact.addToClasspath()==false)
{
continue;
}

classpath.append( artifact.getPath() ).append( cps );
project.setDependencyPath( d.getId(), artifact.getPath() );
}


This is still dirty, but marks the path for future refactoring and centralized the 
source
of problem (only addToClasspath property in Artifact will/should contain appropriate 
information)






-
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-156) classpath or jelly:xml issue with XSLT transformations

2003-08-03 Thread jira

The following comment has been added to this issue:

 Author: dion gillard
Created: Sun, 3 Aug 2003 11:36 PM
   Body:
see how this is done in the latka plugin
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-156
Summary: classpath or jelly:xml issue with XSLT transformations
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: 0 minutes

Project: maven
 Components: 
 jelly-integ
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-7

   Assignee: 
   Reporter: tim stephenson

Created: Thu, 21 Nov 2002 5:28 PM
Updated: Fri, 11 Apr 2003 2:28 PM
Environment: win2k, 1.4.1-b21, maven b7 and also winxp, jdk 1.3.1-01, maven b6

Description:
see also my mail to the user list titled 'Style task / x:transform problem'

It seems there is a general problem with XSLT launched from maven. My own transforms 
in the maven.xml and that in the docbook plugin behave the same. Behaviour is that 
instead of transforming as expected the transform command is printed to console. Some 
processing has occurred (eg var substitution). For example the following:

  

prints this to the console: 



but no transform.

The same thing results when using x:transform. Other jelly:xml commands such as 
x:parse and so on work  fine 

Using a  command to fork a VM and launch a Xalan Process command, taking control 
of the classpath works ok so I am using this a workaround.

Hopefully it will be obvious to someone that better understands the way maven loads 
its classes!


-
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-156) classpath or jelly:xml issue with XSLT transformations

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:36 PM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-156
Summary: classpath or jelly:xml issue with XSLT transformations
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 jelly-integ
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-7

   Assignee: 
   Reporter: tim stephenson

Created: Thu, 21 Nov 2002 5:28 PM
Updated: Sun, 3 Aug 2003 11:36 PM
Environment: win2k, 1.4.1-b21, maven b7 and also winxp, jdk 1.3.1-01, maven b6

Description:
see also my mail to the user list titled 'Style task / x:transform problem'

It seems there is a general problem with XSLT launched from maven. My own transforms 
in the maven.xml and that in the docbook plugin behave the same. Behaviour is that 
instead of transforming as expected the transform command is printed to console. Some 
processing has occurred (eg var substitution). For example the following:

  

prints this to the console: 



but no transform.

The same thing results when using x:transform. Other jelly:xml commands such as 
x:parse and so on work  fine 

Using a  command to fork a VM and launch a Xalan Process command, taking control 
of the classpath works ok so I am using this a workaround.

Hopefully it will be obvious to someone that better understands the way maven loads 
its classes!


-
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-125) Documentation enhancements

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:33 PM
Changes:
 environment changed to 
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-125
Summary: Documentation enhancements
   Type: Improvement

 Status: Assigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: 1 week

Project: maven
   Fix Fors:
 1.1

   Assignee: dion gillard
   Reporter: dion gillard

Created: Tue, 1 Oct 2002 10:44 PM
Updated: Sun, 3 Aug 2003 11:33 PM

Description:
Ok,
Here are some changes I would recommend (as dIon asked for it ;-):
1) Change the welcome page to have direct links to gettting started. This is
what I want to see when I visit the front page
2) The user guide should have information from the download and install
sections to make it a more complete user's guide
3) getting started and user's guide should possibly be rethought into user's
guide and developer's guide.
4) The plug-ins should be split into core and additional (or optional)
5) Someone who has written a plug-in should write a plug-in development
howto and integrate that with the developer's guide.
6) Plug-ins should be described on the listing page
7) In the user's guide it would be nice to have a link to an example
maven.xml file

Let me know what you guys think, when I get a chance to look at it further I
may have some further suggestions (and maybe patches ;-).

-warner

+warner onstine+



-
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/src/java/org/apache/maven/plugin PluginManager.java

2003-08-03 Thread dion

dion2003/08/03 21:30:39

  Modified:src/java/org/apache/maven/plugin PluginManager.java
  Log:
  Refactor werkz project creation into helper method
  
  Revision  ChangesPath
  1.61  +25 -11maven/src/java/org/apache/maven/plugin/PluginManager.java
  
  Index: PluginManager.java
  ===
  RCS file: /home/cvs/maven/src/java/org/apache/maven/plugin/PluginManager.java,v
  retrieving revision 1.60
  retrieving revision 1.61
  diff -u -r1.60 -r1.61
  --- PluginManager.java4 Aug 2003 02:41:10 -   1.60
  +++ PluginManager.java4 Aug 2003 04:30:39 -   1.61
  @@ -369,18 +369,10 @@
   buildAntProject( project, baseContext );
   
   Session session = getJellySession(baseContext);
  -
   // add the global session to the pluginContext so that it can be used by 
tags
   baseContext.setVariable( GLOBAL_SESSION_KEY, session );
   
  -// We put in our listener to frob the session.
  -MavenAttainGoalListener listener = new MavenAttainGoalListener();
  -listener.setBaseContext( baseContext );
  -listener.setPluginManager( this );
  -
  -WerkzProject werkzProject = new WerkzProject();
  -werkzProject.addAttainGoalListener( listener );
  -baseContext.setWerkzProject( werkzProject );
  +WerkzProject werkzProject = buildWerkzProject( baseContext );
   
   // 
-
   // Execution of the Jelly scripts:
  @@ -407,6 +399,8 @@
   //mapper.parse( new InputStreamReader( driver ), driverHousing );
   //runJellyScriptHousing( driverHousing, baseContext );
   
  +// FIXME: Part of this belongs as a method on Project, e.g. the name and
  +//construction of maven.xml
   // Project's Jelly script
   if ( project.getFile() != null )
   {
  @@ -423,8 +417,11 @@
   }
   
   // Parent's Jelly script
  +// FIXME: What about further up the chain?
   if ( project.hasParent() )
   {
  +// FIXME: this is a badly named method
  +
   File f = project.parentMavenXml();
   
   if ( f.exists() )
  @@ -478,6 +475,23 @@
   }
   
   /**
  + * 
  + * @param context the base context for the werkz project
  + * @return a configured werkz project
  + */
  +private WerkzProject buildWerkzProject(MavenJellyContext context)
  +{
  +// We put in our listener to frob the session.
  +MavenAttainGoalListener listener = new MavenAttainGoalListener();
  +listener.setBaseContext( context );
  +listener.setPluginManager( this );
  +WerkzProject werkzProject = new WerkzProject();
  +werkzProject.addAttainGoalListener( listener );
  +context.setWerkzProject( werkzProject );
  +return werkzProject;
  +}
  +
  +/**
* Get the Werkz Session
* FIXME: Describe what it's for?
* @param baseContext the maven context the session should use
  @@ -606,7 +620,7 @@
* @return an Ant project
* @throws Exception When any error occurs. FIXME this is bad.
*/
  -public GrantProject buildAntProject( Project project, MavenJellyContext context 
)
  +private GrantProject buildAntProject( Project project, MavenJellyContext 
context )
   throws Exception
   {
   // Create the build listener.
  
  
  

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

[jira] Updated: (MAVEN-121) Checking of downloaded jars and other artifacts

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:32 PM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-121
Summary: Checking of downloaded jars and other artifacts
   Type: New Feature

 Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.1

   Assignee: 
   Reporter: peter neubauer

Created: Tue, 1 Oct 2002 7:25 AM
Updated: Sun, 3 Aug 2003 11:32 PM
Environment: all

Description:
Maven should check downloaded artifacts for integrety, especially .jar files, since 
they can get corrupted by e.g. bad cvswrappers (no -kb) and other things. Right now 
there is no way to now if a .jar is containing all information once the filename 
exists in the local repository

/peter


-
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-109) Maven does not return exit codes

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:30 PM
Changes:
 Version changed from 1.1
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-109
Summary: Maven does not return exit codes
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.1
   Versions:
 1.0-beta-7

   Assignee: 
   Reporter: Vincent Massol

Created: Wed, 18 Sep 2002 3:53 AM
Updated: Sun, 3 Aug 2003 11:30 PM

Description:
I have some other scripts starting Maven and they need to know if the build was 
successful or not. But it seems Maven does not return any error code.

Thanks
-Vincent


-
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-109) Maven does not return exit codes

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:30 PM
Changes:
 environment changed to 
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-109
Summary: Maven does not return exit codes
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.1
   Versions:
 1.0-beta-7

   Assignee: 
   Reporter: Vincent Massol

Created: Wed, 18 Sep 2002 3:53 AM
Updated: Sun, 3 Aug 2003 11:30 PM

Description:
I have some other scripts starting Maven and they need to know if the build was 
successful or not. But it seems Maven does not return any error code.

Thanks
-Vincent


-
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-37) Not honoring parents project.properties when inheriting projects.

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:28 PM
Changes:
 description changed from When a project is inheiriting from a parent 
project, the parent's project project.properties file is not being read.  Example:

Parent project.properties defines maven.repo.remote.  When the child is built it will 
default to maven's default remote repo at jakarta.
 environment changed from java version "1.4.0_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

Redhat 7.3 + errata
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-37
Summary: Not honoring parents project.properties when inheriting projects.
   Type: Bug

 Status: Assigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.1
   Versions:
 1.0-beta-7

   Assignee: Jason van Zyl
   Reporter: Jeff Brekke

Created: Sun, 4 Aug 2002 9:15 PM
Updated: Sun, 3 Aug 2003 11:28 PM
Environment: java version "1.4.0_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

Redhat 7.3 + errata

Description:
When a project is inheiriting from a parent project, the parent's project 
project.properties file is not being read.  Example:

Parent project.properties defines maven.repo.remote.  When the child is built it will 
default to maven's default remote repo at jakarta.


-
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-25) No way to list plugins available in a remote repository

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:25 PM
Comment:
New functionality
Changes:
 description changed to 
 environment changed to 
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-25
Summary: No way to list plugins available in a remote repository
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.1
   Versions:
 1.0-beta-7

   Assignee: 
   Reporter: dion gillard

Created: Sun, 4 Aug 2002 3:31 AM
Updated: Sun, 3 Aug 2003 11:25 PM

Description:



-
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-542) SnapshotResolver hardcodes the ibibio repo instead of using the custom repos

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:24 PM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-542
Summary: SnapshotResolver hardcodes the ibibio repo instead of using the custom 
repos
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 release
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: Wandy Wang

Created: Wed, 2 Jul 2003 6:35 PM
Updated: Sun, 3 Aug 2003 11:24 PM

Description:
SnapshotResolver hardcodes the ibibio repo instead of using the custom repos set up in 
the project.properties.

String url = "http://www.ibiblio.org/maven/"; + groupId + "/jars/" + artifactId + 
"-snapshot-version";


-
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-541) test-compile doesn't allow for same options as java-compile

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:21 PM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-541
Summary: test-compile doesn't allow for same options as java-compile
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-test
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: Wandy Wang

Created: Wed, 2 Jul 2003 6:34 PM
Updated: Sun, 3 Aug 2003 11:21 PM

Description:
test-compile doesn't use the same compile options that are allowd by java-compile.  
Most noteably, the ability to fork.  This caused my test classes to not compile.


-
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-464) Reactor cannot find goals in plugin

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:16 PM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-464
Summary: Reactor cannot find goals in plugin
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.0-final
   Versions:
 maven-new-unreleased

   Assignee: 
   Reporter: Charles Chan

Created: Wed, 4 Jun 2003 12:44 PM
Updated: Sun, 3 Aug 2003 11:16 PM

Description:
Hi, I am trying to setup a very simple plugin with a
reactor inside. (See Attached Zip file).

When I invoke 

maven reactor-test-maven

I got the following output. I have no idea why this is
happening. I am testing against Maven from CVS.

Any help is appreciated.
Charles


Our processing order:
Project A
Project B
Project C
Project Master Template
Test Plugin
+
| Building Project A
| Memory: 2M/3M
+
[DEBUG] Adding reference: maven.dependency.classpath
-> 
[DEBUG] Adding reference: maven-classpath -> 
test-maven:
test-plugin-default-variable:
[echo] Variable: test.conf.dir is
/this/is/A/conf.dir
+
| Building Project B
| Memory: 2M/3M
+

BUILD FAILED
Unknown goal "test-maven"
com.werken.werkz.UnattainableGoalException: Unable to
obtain goal [reactor-test-maven] -- null:17:43:
 Unknown goal "test-maven"
at com.werken.werkz.Goal.fire(Goal.java:646)
at com.werken.werkz.Goal.attain(Goal.java:575)
at
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:403)
at
org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
at
org.apache.maven.cli.App.doMain(App.java:525)
at
org.apache.maven.cli.App.main(App.java:1088)
at java.lang.reflect.Method.invoke(Native
Method)
at
com.werken.forehead.Forehead.run(Forehead.java:543)
at
com.werken.forehead.Forehead.main(Forehead.java:573)
org.apache.commons.jelly.JellyTagException:
null:17:43:  Unknown goal "test-maven"
at
org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:383)




-
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-426) Allow genapp to support multiple templates

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:09 PM
Changes:
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-426
Summary: Allow genapp to support multiple templates
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Fix Fors:
 1.1
   Versions:
 1.0-beta-9
 1.1

   Assignee: 
   Reporter: Brian Ewins

Created: Wed, 14 May 2003 10:27 AM
Updated: Sun, 3 Aug 2003 11:09 PM
Environment: all

Description:
At the moment the genapp plugin is pretty rudimentary, you only get the 'standard' 
maven template project. I'd like maven to support multiple project templates, to make 
it easier to (for example) set up a beginner's webapp, ejb, maven-plugin project; a 
project with a standard setup for a company (logos, developers, scm); etc etc.

Attached is some code to support this proposal. It changes the structure of the genapp 
'plugin.resources' directory so that it more closely matches a normal project:

plugin-resources/:
project.properties  project.xml  src

plugin-resources/src:
conf  java  test

plugin-resources/src/conf:
app.properties

plugin-resources/src/java:
App.java

plugin-resources/src/test:
AbstractTestCase.java  AppTest.java  NaughtyTest.java

Next we identify the three kinds of resource which need copied - those which need 
'repackaged' like java, test; those which need filtered (project.xml), and those which 
just need copied (everything else). I do this by adding a plugin.properties with the 
lines:

maven.genapp.repackage=java,test
maven.genapp.filter=project.xml

Finally I updated the plugin.jelly (attached). The plugin.jelly was written for b8, 
(hence the missing 'ant:' stuff) and takes an extra parameter:
maven -Dpackage=blah -Dtemplate=example genapp
this will try to copy the 'example' project from the user's home dir. This code isn't 
really sophisticated enough, it should try the user's home dir first then fall back on 
the plugin.resources dir, with the 'default' output of genapp moved to a project 
called 'default'; this would let maven ship with more examples (including a reactor 
example!) while giving the user a way to override them.

If the comments on this idea involve more changes to the plugin I'd be happy to oblige.


-
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-423) Project Descriptor documentation out of date

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:05 PM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-423
Summary: Project Descriptor documentation out of date
   Type: Bug

 Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 documentation
   Fix Fors:
 1.0-final

   Assignee: 
   Reporter: Ryan Hoegg

Created: Sun, 27 Apr 2003 1:45 PM
Updated: Sun, 3 Aug 2003 11:05 PM

Description:
The project descriptor documentation in xdocs/reference/project-descriptor.xml is out 
of date.  People visiting the site at http://maven.apache.org to figure out how to use 
maven are unnecessarily confused by this.


unitTest element is out of date.  The deprecated unitTestPatterns is 
documented
integrationUnitTest element is out of date.  The deprecated 
integrationUnitTestPatterns is documented
resources element is out of date.  The deprecated jarResources is documented



-
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/src/conf driver.jelly

2003-08-03 Thread dion

dion2003/08/03 19:53:06

  Modified:src/conf driver.jelly
  Log:
  Add warning
  
  Revision  ChangesPath
  1.26  +5 -0  maven/src/conf/driver.jelly
  
  Index: driver.jelly
  ===
  RCS file: /home/cvs/maven/src/conf/driver.jelly,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- driver.jelly  31 Jul 2003 06:52:10 -  1.25
  +++ driver.jelly  4 Aug 2003 02:53:06 -   1.26
  @@ -6,5 +6,10 @@
 xmlns:define="jelly:define"
 xmlns:util="jelly:util">
   
  +  
  +
   
   
  
  
  

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

[jira] Updated: (MAVEN-349) Consistent properties for jar, war, ejb and ear

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 9:47 PM
Changes:
 Version changed from 1.0-final
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-349
Summary: Consistent properties for jar, war, ejb and ear
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-java
 plugin-war
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-9

   Assignee: 
   Reporter: Aslak Hellesoy

Created: Tue, 25 Mar 2003 5:11 AM
Updated: Sun, 3 Aug 2003 9:47 PM

Description:
The current naming conventions for properties defining the names of jar, ejb, war and 
ear are somewhat inconsistent.

This patch introduces 4 new properties:

# defined in the java plugin's plugin.properties
maven.jar.final.name = ${maven.final.name}.jar

# defined in the war plugin's plugin.properties
maven.war.final.name = ${maven.final.name}.war

# defined in the ejb plugin's plugin.properties
maven.ejb.final.name = ${maven.final.name}.jar

# defined in the ear plugin's plugin.properties
maven.ear.final.name = ${maven.final.name}.ear

This patch solves the following problems:

1) It removes the risk of name clashes for projects that produce both plain
jar files and ejb jar files, since the maven.ejb.final.name property can be overridden.

2) When packaging wars and ejbs inside ears, it is sometimes desirable to have 
different names for ejbs and wars, like foo-ejb-1.0.jar and foo-war-1.0.war. This is 
necessary when the contents of an ear file is to be deployed on different weblogic 
servers with weblogic.deploy. This can now be achieved by overriding 
maven.ejb.final.name and/or maven.war.final.name.

This patch should not change any of the current functionality, and the documentation 
has been updated too.



-
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-349) Consistent properties for jar, war, ejb and ear

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 9:44 PM
Changes:
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-349
Summary: Consistent properties for jar, war, ejb and ear
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-java
 plugin-war
   Versions:
 1.0-beta-9
 1.0-final

   Assignee: 
   Reporter: Aslak Hellesoy

Created: Tue, 25 Mar 2003 5:11 AM
Updated: Sun, 3 Aug 2003 9:44 PM

Description:
The current naming conventions for properties defining the names of jar, ejb, war and 
ear are somewhat inconsistent.

This patch introduces 4 new properties:

# defined in the java plugin's plugin.properties
maven.jar.final.name = ${maven.final.name}.jar

# defined in the war plugin's plugin.properties
maven.war.final.name = ${maven.final.name}.war

# defined in the ejb plugin's plugin.properties
maven.ejb.final.name = ${maven.final.name}.jar

# defined in the ear plugin's plugin.properties
maven.ear.final.name = ${maven.final.name}.ear

This patch solves the following problems:

1) It removes the risk of name clashes for projects that produce both plain
jar files and ejb jar files, since the maven.ejb.final.name property can be overridden.

2) When packaging wars and ejbs inside ears, it is sometimes desirable to have 
different names for ejbs and wars, like foo-ejb-1.0.jar and foo-war-1.0.war. This is 
necessary when the contents of an ear file is to be deployed on different weblogic 
servers with weblogic.deploy. This can now be achieved by overriding 
maven.ejb.final.name and/or maven.war.final.name.

This patch should not change any of the current functionality, and the documentation 
has been updated too.



-
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/src/java/org/apache/maven/plugin PluginManager.java

2003-08-03 Thread dion

dion2003/08/03 19:41:10

  Modified:src/java/org/apache/maven/plugin PluginManager.java
  Log:
  Move ant stuff into a single method
  
  Revision  ChangesPath
  1.60  +7 -7  maven/src/java/org/apache/maven/plugin/PluginManager.java
  
  Index: PluginManager.java
  ===
  RCS file: /home/cvs/maven/src/java/org/apache/maven/plugin/PluginManager.java,v
  retrieving revision 1.59
  retrieving revision 1.60
  diff -u -r1.59 -r1.60
  --- PluginManager.java4 Aug 2003 01:11:13 -   1.59
  +++ PluginManager.java4 Aug 2003 02:41:10 -   1.60
  @@ -87,7 +87,6 @@
   import java.io.File;
   import java.io.FileInputStream;
   import java.io.FileReader;
  -import java.io.IOException;
   import java.io.InputStream;
   import java.io.OutputStreamWriter;
   import java.io.PrintStream;
  @@ -363,14 +362,11 @@
   // Before attempting to attain the goals verify the project
   // if desired.
   // FIXME: From attainGoals angle, how does it know the project needs to
  -//to be verified, or that the project object has
  +//to be verified, or that the project object hasn't been used before
   project.verifyDependencies();
   
   // Set up the ant project.
  -GrantProject antProject = buildAntProject( project, baseContext );
  -Path p = new Path( antProject );
  -p.setPath( project.getDependencyClasspath() );
  -antProject.addReference( MavenConstants.DEPENDENCY_CLASSPATH, p );
  +buildAntProject( project, baseContext );
   
   Session session = getJellySession(baseContext);
   
  @@ -635,6 +631,10 @@
   
   context.setAntProject( antProject );
   AntTagLibrary.setProject( context, antProject );
  +
  +Path p = new Path( antProject );
  +p.setPath( project.getDependencyClasspath() );
  +antProject.addReference( MavenConstants.DEPENDENCY_CLASSPATH, p );
   
   return antProject;
   }
  
  
  

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

[jira] Commented: (MAVEN-349) Consistent properties for jar, war, ejb and ear

2003-08-03 Thread jira

The following comment has been added to this issue:

 Author: dion gillard
Created: Sun, 3 Aug 2003 9:42 PM
   Body:
Is this still an issue?
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-349
Summary: Consistent properties for jar, war, ejb and ear
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: 0 minutes

Project: maven
 Components: 
 plugin-java
 plugin-war
   Versions:
 1.0-beta-9

   Assignee: 
   Reporter: Aslak Hellesoy

Created: Tue, 25 Mar 2003 5:11 AM
Updated: Tue, 25 Mar 2003 5:11 AM

Description:
The current naming conventions for properties defining the names of jar, ejb, war and 
ear are somewhat inconsistent.

This patch introduces 4 new properties:

# defined in the java plugin's plugin.properties
maven.jar.final.name = ${maven.final.name}.jar

# defined in the war plugin's plugin.properties
maven.war.final.name = ${maven.final.name}.war

# defined in the ejb plugin's plugin.properties
maven.ejb.final.name = ${maven.final.name}.jar

# defined in the ear plugin's plugin.properties
maven.ear.final.name = ${maven.final.name}.ear

This patch solves the following problems:

1) It removes the risk of name clashes for projects that produce both plain
jar files and ejb jar files, since the maven.ejb.final.name property can be overridden.

2) When packaging wars and ejbs inside ears, it is sometimes desirable to have 
different names for ejbs and wars, like foo-ejb-1.0.jar and foo-war-1.0.war. This is 
necessary when the contents of an ear file is to be deployed on different weblogic 
servers with weblogic.deploy. This can now be achieved by overriding 
maven.ejb.final.name and/or maven.war.final.name.

This patch should not change any of the current functionality, and the documentation 
has been updated too.



-
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/src/plugins-build/plugin plugin.jelly project.xml

2003-08-03 Thread dion

dion2003/08/03 19:32:35

  Modified:src/plugins-build/plugin plugin.jelly project.xml
  Log:
  Start of work on a maven plugin:download.
  See MAVEN-536
  
  Revision  ChangesPath
  1.10  +22 -0 maven/src/plugins-build/plugin/plugin.jelly
  
  Index: plugin.jelly
  ===
  RCS file: /home/cvs/maven/src/plugins-build/plugin/plugin.jelly,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- plugin.jelly  28 Jul 2003 06:30:17 -  1.9
  +++ plugin.jelly  4 Aug 2003 02:32:35 -   1.10
  @@ -1,7 +1,9 @@
   
   
   
   
  @@ -158,5 +160,25 @@
 
   
   
  +  
  +  
  +  
  +  
  +
  +
  +
  +${maven.repo.remote}
  +${repoList.trim()}
  +
  +  repo is '${repo}'
  +  
  +  
  +
  +trying to download ${remoteFile}
  +
  +  
  +
 
   
  
  
  
  1.15  +12 -0 maven/src/plugins-build/plugin/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven/src/plugins-build/plugin/project.xml,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- project.xml   29 Jul 2003 04:49:40 -  1.14
  +++ project.xml   4 Aug 2003 02:32:35 -   1.15
  @@ -41,5 +41,17 @@
 20030211.142705
 http://jakarta.apache.org/commons/jelly/libs/xml/
   
  +
  +  commons-jelly
  +  commons-jelly-tags-http
  +  20030211.143043
  +  http://jakarta.apache.org/commons/jelly/libs/http/
  +
  +
  +  commons-httpclient
  +  commons-httpclient
  +  2.0-rc1
  +  http://jakarta.apache.org/commons/httpclient/
  +
 
   
  
  
  

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

[jira] Updated: (MAVEN-309) Order of classpath entries should be changed

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 9:35 PM
Changes:
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-309
Summary: Order of classpath entries should be changed
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-test
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-9

   Assignee: 
   Reporter: Michal Maczka

Created: Mon, 3 Mar 2003 5:07 AM
Updated: Sun, 3 Aug 2003 9:35 PM

Description:
Behavior of my application is controlled through set of configuration files(like 
log4j.propertrties).

I want to control behavior of my application differently for the test
environment and differently for the production environment.

The problem is that currently in maven the "production" resources are preceding the 
test resources in the classpath
and [test] plugin is always taking  them in first order.

I am including short example showing where is the problem.
Basically in  it I have two log4j.properties files: one in
'test-resources', second in 'resources' directory.
This example shows that the the one kept in test-resources is never used and it is not 
possible  to easily control
the "test environment" when it is overlapping with "production'
environment".

As a result of this program the output of log statements is always written to 
production.log. Test resources are containing log4j.properties file which configures 
the log system for tests and directs log statements to a file test.log. This example 
shows that 
this file is never created.

Other problem here is: if any of the dependencies in the classpath contains 
log4j.properties  this file will even preceeds the log4j.properties in the classpath.
So the best solution in my opinion will be to have followiing order of entries in the 
class path:


   
   
   
   



The problem is generic and not only typical to log4j. The same applies for example to 
jndi.properties.


Michal Maczka









-
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-253) allows to specify cvs tag when using dist plugin

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 9:32 PM
Changes:
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-253
Summary: allows to specify cvs tag when using dist plugin
   Type: New Feature

 Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-dist
   Fix Fors:
 1.1
   Versions:
 1.0-beta-8
 1.1

   Assignee: 
   Reporter: Alexey Styrov

Created: Tue, 4 Feb 2003 11:33 AM
Updated: Sun, 3 Aug 2003 9:32 PM

Description:
It would be really cool if I could tell maven to checkout and build some version 
specified in  part of POM

Pete Kazmier told me that this feature has been dropped while migrating  maven to 
jelly from ant. He also told me that it should be  a part of dist plugin.


-
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-253) allows to specify cvs tag when using dist plugin

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 9:30 PM
Changes:
 environment changed to 
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-253
Summary: allows to specify cvs tag when using dist plugin
   Type: New Feature

 Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-dist
   Versions:
 1.0-beta-8
 1.1

   Assignee: 
   Reporter: Alexey Styrov

Created: Tue, 4 Feb 2003 11:33 AM
Updated: Sun, 3 Aug 2003 9:30 PM

Description:
It would be really cool if I could tell maven to checkout and build some version 
specified in  part of POM

Pete Kazmier told me that this feature has been dropped while migrating  maven to 
jelly from ant. He also told me that it should be  a part of dist plugin.


-
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] Closed: (MAVEN-227) Still can't get Touchstone goal - C interplugin to work

2003-08-03 Thread jira

Message:

   The following issue has been closed.

   Resolver: dion gillard
   Date: Sun, 3 Aug 2003 9:29 PM

I believe this has been fixed a while back
-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-227
Summary: Still can't get Touchstone goal - C interplugin to work
   Type: Bug

 Status: Closed
   Priority: Major
 Resolution: FIXED

 Time Spent: Unknown
  Remaining: 0 minutes

Project: maven
 Components: 
 core
   Versions:
 1.0-beta-8

   Assignee: 
   Reporter: David Eric Pugh

Created: Wed, 29 Jan 2003 5:06 PM
Updated: Sun, 3 Aug 2003 9:29 PM
Environment: Win2K with CVS Head as of 1/29 5:00 PM EST.  Ant 1.5

Description:
I am still recieving errors on the touchstone build.  I believe I saw on an email that 
this was a possibly environmental thing, that some get the error, and others don't.  
Is this still true?  I am trying to push forward on the cactus plugin, but I need the 
interplugin ability to retrieve properties.

Stack Trace:
 [exec] java:jar:
 [exec] [jar] Building jar: 
C:\java\jakarta-turbine-maven\src\test\touchstone-build\target\touchstone-1.0.jar

 [exec] touchstone-tests:
 [exec] touchstone-goal-A:
 [exec] [echo] Overriding touchstone-goal-A

 [exec] touchstone-goal-B:
 [exec] [echo] touchstone-goal-B defined in plugin.

 [exec] test-addPath:

 [exec] test-plugin-property-override:
 [exec] com.werken.werkz.UnattainableGoalException: Unable to obtain goal 
[touchstone-tests] -- Inter-plugin preGoal
s are not being dealt with correctly. File: null At tag : line: 150 column: 24
 [exec] [echo] maven.touchstone.A = override.maven.touchstone.A

 [exec] touchstone-goal-C:
 [exec] at com.werken.werkz.Goal.fire(Goal.java:639)
 [exec] [echo] touchstone-goal-C defined in plugin.

 [exec] at com.werken.werkz.Goal.attain(Goal.java:568)
 [exec] [echo] checkValue =
 [exec] at 
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:383)
 [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:372)
 [exec] at org.apache.maven.jelly.tags.maven.MavenTag.doTag(MavenTag.java:116)
 [exec] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:278)
 [exec] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:133)
 [exec] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:232)
 [exec] at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:87)
 [exec] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:278)
 [exec] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:133)
 [exec] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:232)
 [exec] at 
com.werken.werkz.jelly.PostGoalTag$1.firePostGoal(PostGoalTag.java:86)
 [exec] at com.werken.werkz.Goal.firePostGoalCallbacks(Goal.java:703)
 [exec] at com.werken.werkz.Goal.fire(Goal.java:647)
 [exec] at com.werken.werkz.Goal.attain(Goal.java:568)
 [exec] at com.werken.werkz.Goal.attainPrecursors(Goal.java:481)
 [exec] at com.werken.werkz.Goal.attain(Goal.java:566)
 [exec] at 
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:383)
 [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:360)
 [exec] at org.apache.maven.cli.App.doMain(App.java:523)
 [exec] at org.apache.maven.cli.App.main(App.java:1079)
 [exec] at java.lang.reflect.Method.invoke(Native Method)
 [exec] at com.werken.forehead.Forehead.run(Forehead.java:543)
 [exec] at com.werken.forehead.Forehead.main(Forehead.java:573)
 [exec] org.apache.commons.jelly.JellyException: Inter-plugin preGoals are not 
being dealt with correctly. File: nul
l At tag : line: 150 column: 24
 [exec] at 
org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:659)
 [exec] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:284)
 [exec] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:133)
 [exec] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:232)
 [exec] at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:87)
 [exec] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:278)
 [exec] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:133)
 [exec] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:232)
 [exec] at com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:108)
 [exec] at com.werken.werkz.Goal.fire(Goal.java:632)
 [exec] at com.we

[jira] Updated: (MAVEN-309) Order of classpath entries should be changed

2003-08-03 Thread jira

The following issue has been updated:

Updater: Ben Walding (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 9:10 PM
Changes:
 description changed from Behavior of my application is controlled through 
set of configuration files(like log4j.propertrties).

I want to control behavior of my application differently for the test
environment and differently for the production environment.

The problem is that currently in maven the "production" resources are preceding the 
test resources in the classpath
and [test] plugin is always taking  them in first order.

I am including short example showing where is the problem.
Basically in  it I have two log4j.properties files: one in
'test-resources', second in 'resources' directory.
This example shows that the the one kept in test-resources is never used and it is not 
possible  to easily control
the "test environment" when it is overlapping with "production'
environment".

As a result of this program the output of log statements is always written to 
production.log. Test resources are containing log4j.properties file which configures 
the log system for tests and directs log statements to a file test.log. This example 
shows that 
this file is never created.

Other problem here is: if any of the dependencies in the classpath contains 
log4j.properties  this file will even preceeds the log4j.properties in the classpath.
So the best solution in my opinion will be to have followiing order of entries in the 
class path:


   
   
   
   



The problem is generic and not only typical to log4j. The same applies for example to 
jndi.properties.


Michal Maczka







-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-309
Summary: Order of classpath entries should be changed
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-test
   Versions:
 1.0-beta-9

   Assignee: 
   Reporter: Michal Maczka

Created: Mon, 3 Mar 2003 5:07 AM
Updated: Sun, 3 Aug 2003 9:10 PM

Description:
Behavior of my application is controlled through set of configuration files(like 
log4j.propertrties).

I want to control behavior of my application differently for the test
environment and differently for the production environment.

The problem is that currently in maven the "production" resources are preceding the 
test resources in the classpath
and [test] plugin is always taking  them in first order.

I am including short example showing where is the problem.
Basically in  it I have two log4j.properties files: one in
'test-resources', second in 'resources' directory.
This example shows that the the one kept in test-resources is never used and it is not 
possible  to easily control
the "test environment" when it is overlapping with "production'
environment".

As a result of this program the output of log statements is always written to 
production.log. Test resources are containing log4j.properties file which configures 
the log system for tests and directs log statements to a file test.log. This example 
shows that 
this file is never created.

Other problem here is: if any of the dependencies in the classpath contains 
log4j.properties  this file will even preceeds the log4j.properties in the classpath.
So the best solution in my opinion will be to have followiing order of entries in the 
class path:


   
   
   
   



The problem is generic and not only typical to log4j. The same applies for example to 
jndi.properties.


Michal Maczka









-
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-123) creating Class-Path in manifest file

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 9:10 PM
Changes:
 environment changed to 
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-123
Summary: creating Class-Path in manifest file
   Type: New Feature

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Fix Fors:
 1.1

   Assignee: 
   Reporter: Xuhua Lin

Created: Tue, 1 Oct 2002 10:26 AM
Updated: Sun, 3 Aug 2003 9:10 PM

Description:
It would be nice for Maven to create Class-Path attribute in the manifest.mf file, the 
value of which containing a list of dependency jar file separated by space. Can be 
controlled by maven.jar.manifest.class-path property. 


-
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-309) Order of classpath entries should be changed

2003-08-03 Thread jira

The following issue has been updated:

Updater: Ben Walding (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 9:09 PM
Comment:
Removed xml breaking characters.
Changes:
 description changed from Behavior of my application is controlled through 
set of configuration files(like log4j.propertrties).

I want to control behavior of my application differently for the test
environment and differently for the production environment.

The problem is that currently in maven the "production" resources are preceding the 
test resources in the classpath
and [test] plugin is always taking  them in first order.

I am including short example showing where is the problem.
Basically in  it I have two log4j.properties files: one in
'test-resources', second in 'resources' directory.
This example shows that the the one kept in test-resources is never used and it is not 
possible  to easily control
the "test environment" when it is overlapping with "production'
environment".

As a result of this program the output of log statements is always written to 
production.log. Test resources are containing log4j.properties file which configures 
the log system for tests and directs log statements to a file test.log. This example 
shows that 
this file is never created.

Other problem here is: if any of the dependencies in the classpath contains 
log4j.properties  this file will even preceeds the lo4j.properties in the classpath.
So the best solution in my opinion will be to have followiing order of entries in the 
class path:


   
   
   
   



The problem is generic and not only typical to log4j. The same applies for example to 
jndi.properties.


Michal Maczka







 environment changed to 
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-309
Summary: Order of classpath entries should be changed
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-test
   Versions:
 1.0-beta-9

   Assignee: 
   Reporter: Michal Maczka

Created: Mon, 3 Mar 2003 5:07 AM
Updated: Sun, 3 Aug 2003 9:09 PM

Description:
Behavior of my application is controlled through set of configuration files(like 
log4j.propertrties).

I want to control behavior of my application differently for the test
environment and differently for the production environment.

The problem is that currently in maven the "production" resources are preceding the 
test resources in the classpath
and [test] plugin is always taking  them in first order.

I am including short example showing where is the problem.
Basically in  it I have two log4j.properties files: one in
'test-resources', second in 'resources' directory.
This example shows that the the one kept in test-resources is never used and it is not 
possible  to easily control
the "test environment" when it is overlapping with "production'
environment".

As a result of this program the output of log statements is always written to 
production.log. Test resources are containing log4j.properties file which configures 
the log system for tests and directs log statements to a file test.log. This example 
shows that 
this file is never created.

Other problem here is: if any of the dependencies in the classpath contains 
log4j.properties  this file will even preceeds the log4j.properties in the classpath.
So the best solution in my opinion will be to have followiing order of entries in the 
class path:


   
   
   
   



The problem is generic and not only typical to log4j. The same applies for example to 
jndi.properties.


Michal Maczka









-
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-639) Add maven.javadoc.overview property to the javadoc plugin

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 9:02 PM
Comment:
New functionality in 1.1 unless a developer can squeeze it in 1.0
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-639
Summary: Add maven.javadoc.overview property to the javadoc plugin
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 plugin-other
   Fix Fors:
 1.1
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: Kai Runte

Created: Thu, 31 Jul 2003 4:33 PM
Updated: Sun, 3 Aug 2003 9:02 PM
Environment: system independent

Description:
It would be nice to have an additional property in the javadoc plugin for setting an 
overview.html file (option -overview in javadoc). A possible patch for the 
maven-javadoc-plugin-1.3-SNAPSHOT would be:


Index: plugin.jelly
===
RCS file: /home/cvspublic/maven/src/plugins-build/javadoc/plugin.jelly,v
retrieving revision 1.17
diff -r1.17 plugin.jelly
98a99
> overview="${maven.javadoc.overview}"
Index: plugin.properties
===
RCS file: /home/cvspublic/maven/src/plugins-build/javadoc/plugin.properties,v
retrieving revision 1.4
diff -r1.4 plugin.properties
14a15
> maven.javadoc.overview = 



-
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-122) FTP repository support

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 9:01 PM
Comment:
Need to release at some point
Changes:
 environment changed to 
 timeoriginalestimate changed from 0
 timeestimate changed from 0 minutes
 Fix Version changed to 1.1
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-122
Summary: FTP repository support
   Type: New Feature

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Fix Fors:
 1.1

   Assignee: 
   Reporter: Carlo Conserva

Created: Tue, 1 Oct 2002 9:45 AM
Updated: Sun, 3 Aug 2003 9:01 PM

Description:
I've done some work to implement an FTP repository support in maven,
for dependency downloading and artifact deploying, 
and I'd like my work to be included in the project if maven developers consider it 
well made and useful.

In attachment I put all the necessary files to include my FTP patch in maven, together 
with installation instructions and a description of the modifications.
The code is tested with maven 1.0 beta 7.






-
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-224) remote and local repo overrides in project.properties does not work for plugins

2003-08-03 Thread jira

The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 8:59 PM
Changes:
 Fix Version changed to 1.0-final
-
For a full history of the issue, see:

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

-
View the issue:

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


Here is an overview of the issue:
-
Key: MAVEN-224
Summary: remote and local repo overrides in project.properties does not work for 
plugins
   Type: Bug

 Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.0-final
   Versions:
 1.0-beta-8
 1.0-final

   Assignee: 
   Reporter: Colin Sampaleanu

Created: Tue, 28 Jan 2003 2:41 PM
Updated: Sun, 3 Aug 2003 8:59 PM
Environment: cvs HEAD from 2003-1-28, win2k

Description:
It is possible to override both the local and remote repos by using entris such as the 
following in a project's project.properties file:
--- from project.properties
# override remote repo since we want to also point to a cvs based remote repo
# to get some jars not found at ibiblio
maven.repo.remote=http://www.ibiblio.com/maven/,http://some.where/else/,file:../../shared/repository
# overrid local repo since we want to allow this set of related source projects
# to be built from multiple locations without conflicting
maven.repo.local=../mavenrepo


However, while this works for satisfying dependencies declared in the project's 
project.xml file, when building that project, if using any plugins, it does not 
override the repos that a plugin itself will use when trying to satisfy it's own 
dependencies specified in its own project.xml file. The only solution would seem to be 
to modify each plugin in the maven plugins dir to point to the correct repo, 
relatively impractical since there are a lot of plugins, and they get blown away on 
rebuilding 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]

1 2 >

1 - 100 of 123 matches

Mail list logo