[jira] Commented: (MPECLIPSE-17) maven.eclipse.classpath.include does not appear to work

2004-03-03 Thread jira
The following comment has been added to this issue: Author: John Cavacas Created: Thu, 4 Mar 2004 12:38 AM Body: I've also found this to be the case (using the latest eclipse 1.5 plugin) Having taking a look at the plugin template which generates the .classpath, it's obvious that

cvs commit: maven-plugins/xdoc/src/plugin-resources/templates mail-lists.xml

2004-03-03 Thread evenisse
evenisse2004/03/03 21:19:32 Modified:xdoc/src/plugin-resources/templates mail-lists.xml Log: A little fix for links with spaces. Revision ChangesPath 1.4 +1 -1 maven-plugins/xdoc/src/plugin-resources/templates/mail-lists.xml Index: mail-lists.xml ===

[jira] Commented: (MPXDOC-79) Unevaluated maven:property tags left in output

2004-03-03 Thread jira
The following comment has been added to this issue: Author: dion gillard Created: Wed, 3 Mar 2004 11:12 PM Body: This is on the maven.apache.org website, built using RC2-SNAPSHOT - View this comment: http://jira

[jira] Commented: (MPXDOC-79) Unevaluated maven:property tags left in output

2004-03-03 Thread jira
The following comment has been added to this issue: Author: Brett Porter Created: Wed, 3 Mar 2004 10:51 PM Body: is this using 1.0-rc1? I don't think maven:property was in that release. Any unrecognised tags are just output verbatim. The other thing to check is that the maven nam

[jira] Commented: (MPXDOC-79) Unevaluated maven:property tags left in output

2004-03-03 Thread jira
The following comment has been added to this issue: Author: dion gillard Created: Wed, 3 Mar 2004 10:22 PM Body: nope, evaluating the tags is not the issue - View this comment: http://jira.codehaus.org/secure/Vi

[jira] Commented: (MPXDOC-79) Unevaluated maven:property tags left in output

2004-03-03 Thread jira
The following comment has been added to this issue: Author: Edward Kaganovich Created: Wed, 3 Mar 2004 10:16 PM Body: If I understand the title correcty, xdoc plugin does not resolve variables specified in input files (navigation.xml, etc...). It would be great if plugin could pe

RE: Projects with Native Code...

2004-03-03 Thread Klaasmeyer, Corey M
No. The "so" comes from reading the native plugin's jelly script's native:install goal: ... ... It puts the shared library in the ${artifactId}/so directory which lead me to believe that Maven do something clever like put the library "so" directory on the java.library.path. I

Re: Projects with Native Code...

2004-03-03 Thread matthew.hawthorne
Klaasmeyer, Corey M wrote: I'm using Maven for a couple projects with native components. Does the maven local repository handle native shared libraries? For example, if I download a project with a shared library in the "//so" directory, does maven add the library to the path, so that the JVM can lo

[jira] Commented: (MAVEN-1173) Move to ASL v2.

2004-03-03 Thread jira
The following comment has been added to this issue: Author: dion gillard Created: Wed, 3 Mar 2004 7:02 PM Body: There are scripts that do a whole load of them for you. For Jelly, I used the perl script with a few mods. Look in committer/relicense if you haven't already. -

[jira] Created: (MPTEST-26) Add jvm attribute to junit tasks.

2004-03-03 Thread jira
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPTEST-26 Here is an overview of the issue:

[jira] Reopened: (MAVEN-1173) Move to ASL v2.

2004-03-03 Thread jira
Message: The following issue has been reopened. Reopener: Brett Porter Date: Wed, 3 Mar 2004 6:29 PM this could take a while... - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1173 Here

[jira] Commented: (MAVEN-1173) Move to ASL v2.

2004-03-03 Thread jira
The following comment has been added to this issue: Author: dion gillard Created: Wed, 3 Mar 2004 6:24 PM Body: Yep, it is documented. See http://www.apache.org/dev/apply-license.html "Yes. All source files should include the copyright notice boilerplate that indicates it is ow

[jira] Commented: (MAVEN-1173) Move to ASL v2.

2004-03-03 Thread jira
The following comment has been added to this issue: Author: Brett Porter Created: Wed, 3 Mar 2004 5:52 PM Body: is it documented on which file types it must be included? Is it anything that eventually gets executed? In that case, all the plugin.jelly's etc need it too. ---

Projects with Native Code...

2004-03-03 Thread Klaasmeyer, Corey M
I'm using Maven for a couple projects with native components. Does the maven local repository handle native shared libraries? For example, if I download a project with a shared library in the "//so" directory, does maven add the library to the path, so that the JVM can load it? Later, Corey

[jira] Commented: (MAVEN-1173) Move to ASL v2.

2004-03-03 Thread jira
The following comment has been added to this issue: Author: dion gillard Created: Wed, 3 Mar 2004 4:35 PM Body: Looks incomplete AFAICT. >From the top level directory several files were missing license info: build-bootstrap.xml checkstyle.xml gump.xml maven.xml plugins-site.xml p

[jira] Updated: (MPDIST-7) Use shorter path for assembling distributions and clean up afterwards.

2004-03-03 Thread jira
The following issue has been updated: Updater: Bruce Chenoweth (mailto:[EMAIL PROTECTED]) Date: Wed, 3 Mar 2004 1:28 PM Comment: corresponding properties.xml documentation Changes: Attachment changed to properties.xml

[jira] Updated: (MPDIST-7) Use shorter path for assembling distributions and clean up afterwards.

2004-03-03 Thread jira
The following issue has been updated: Updater: Bruce Chenoweth (mailto:[EMAIL PROTECTED]) Date: Wed, 3 Mar 2004 1:26 PM Changes: Attachment changed to plugin.properties - For a full history of the i

[jira] Updated: (MPDIST-7) Use shorter path for assembling distributions and clean up afterwards.

2004-03-03 Thread jira
The following issue has been updated: Updater: Bruce Chenoweth (mailto:[EMAIL PROTECTED]) Date: Wed, 3 Mar 2004 1:26 PM Comment: Here is an implementation of my suggestions Changes: Attachment changed to plugin.jelly -

[jira] Created: (MPDIST-7) Use shorter path for assembling distributions and clean up afterwards.

2004-03-03 Thread jira
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPDIST-7 Here is an overview of the issue: -

[jira] Created: (MPJAVA-16) Incorrect defaults cause problems with javac changes

2004-03-03 Thread jira
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJAVA-16 Here is an overview of the issue:

[jira] Updated: (MAVEN-1179) Cannot build when JAVA_HOME has spaces

2004-03-03 Thread jira
The following issue has been updated: Updater: Berin Loritsch (mailto:[EMAIL PROTECTED]) Date: Wed, 3 Mar 2004 10:25 AM Comment: This fixes it for Cygwin/Windows environments--as well as Unix environments with spaces Changes: Attachment changed to maven

[jira] Updated: (MAVEN-1185) The Maven CLI breaks with JDK 1.5 and Cygwyn

2004-03-03 Thread jira
The following issue has been updated: Updater: Berin Loritsch (mailto:[EMAIL PROTECTED]) Date: Wed, 3 Mar 2004 10:21 AM Comment: Updated run script that works with JDK 1.5 on Cygwin Changes: Attachment changed to maven ---

[jira] Created: (MAVEN-1185) The Maven CLI breaks with JDK 1.5 and Cygwyn

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

cvs commit: maven-plugins/cruisecontrol/xdocs changes.xml

2004-03-03 Thread brett
brett 2004/03/03 03:44:40 Modified:cruisecontrol project.xml Added: cruisecontrol/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.1 Revision ChangesPath 1.12 +10 -4 maven-plugins/cruisecontrol/project.xml Index: project.xml ==

cvs commit: maven-plugins/tjdo project.xml

2004-03-03 Thread brett
brett 2004/03/03 03:34:02 Modified:tjdo project.xml Log: developer connection Revision ChangesPath 1.8 +1 -0 maven-plugins/tjdo/project.xml Index: project.xml === RCS file: /home/cvs

cvs commit: maven-plugins/wizard project.xml

2004-03-03 Thread brett
brett 2004/03/03 03:29:37 Modified:wizard project.xml Log: developer connection Revision ChangesPath 1.17 +1 -0 maven-plugins/wizard/project.xml Index: project.xml === RCS file: /home/c

cvs commit: maven maven.xml

2004-03-03 Thread brett
brett 2004/03/03 02:54:57 Modified:.Tag: MAVEN-1_0-BRANCH maven.xml Log: aspectwerkz is fixed Revision ChangesPath No revision No revision 1.97.2.14 +1 -2 maven/maven.xml Index: maven.xml ==

cvs commit: maven maven.xml

2004-03-03 Thread brett
brett 2004/03/03 02:47:43 Modified:.Tag: MAVEN-1_0-BRANCH maven.xml Log: new release technique Revision ChangesPath No revision No revision 1.97.2.13 +63 -1 maven/maven.xml Index: maven.xml =

[jira] Closed: (MAVEN-1153) update commons-lang dependency

2004-03-03 Thread jira
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1153 Here is an overview of the issue: ---

cvs commit: maven project.xml

2004-03-03 Thread brett
brett 2004/03/03 02:38:20 Modified:.Tag: MAVEN-1_0-BRANCH project.xml Log: PR: MAVEN-1153 update commons-lang dependency Revision ChangesPath No revision No revision 1.317.4.12 +7 -2 maven/project.xml Index: pr

cvs commit: maven-plugins/aspectwerkz/src/plugin-test maven.xml

2004-03-03 Thread evenisse
evenisse2004/03/03 02:37:04 Modified:aspectwerkz/src/plugin-test maven.xml Log: Fix aspectwerkz tests. Revision ChangesPath 1.5 +1 -5 maven-plugins/aspectwerkz/src/plugin-test/maven.xml Index: maven.xml ===

[jira] Reopened: (MPCHECKSTYLE-18) I can't build checkstyle plugin

2004-03-03 Thread jira
Message: The following issue has been reopened. Reopener: Brett Porter Date: Wed, 3 Mar 2004 5:44 AM still occurring when root entries reinstated. Removing root entries causes checkstyle to fail after java:compile

cvs commit: maven-plugins/checkstyle project.xml

2004-03-03 Thread brett
brett 2004/03/03 02:36:39 Modified:checkstyle project.xml Log: remove log4j again - back to original POM. Checkstyle should not care about log4j, it never uses it directly. Revision ChangesPath 1.37 +0 -8 maven-plugins/checkstyle/project.xml Index: proj

cvs commit: maven-plugins/checkstyle plugin.jelly

2004-03-03 Thread brett
brett 2004/03/03 02:34:09 Modified:checkstyle plugin.jelly Log: write a dummy license to avoid failure Revision ChangesPath 1.22 +2 -0 maven-plugins/checkstyle/plugin.jelly Index: plugin.jelly

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

2004-03-03 Thread brett
brett 2004/03/03 02:34:02 Modified:src/test/java/org/apache/maven/project Tag: MAVEN-1_0-BRANCH LegacyIdTest.java src/java/org/apache/maven/project Tag: MAVEN-1_0-BRANCH Project.java Added: src/test/test-data/pom/ex

cvs commit: maven/src/test/test-data/pom/extend - New directory

2004-03-03 Thread brett
brett 2004/03/03 02:30:45 maven/src/test/test-data/pom/extend - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (MAVEN-1105) resolve plugin release technique when bundling with maven core

2004-03-03 Thread jira
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1105 Here is an overview of the issue: ---

[jira] Updated: (MAVEN-1175) Add the concept of scope to prevent variable clashes between plugins and multiple targets

2004-03-03 Thread jira
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Wed, 3 Mar 2004 5:01 AM Changes: Fix Version changed to 1.1 - For a full history of the issue, see: ht

[jira] Updated: (MAVEN-1172) additional comment for dependencies in POM

2004-03-03 Thread jira
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Wed, 3 Mar 2004 5:01 AM Changes: Fix Version changed to 1.1 - For a full history of the issue, see: ht

[jira] Updated: (MAVEN-1184) Broken support of whitespaces in parameters

2004-03-03 Thread jira
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Wed, 3 Mar 2004 4:59 AM Changes: priority changed from Critical - For a full history of the issue, see:

[jira] Updated: (MAVEN-1179) Cannot build when JAVA_HOME has spaces

2004-03-03 Thread jira
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Wed, 3 Mar 2004 4:59 AM Changes: priority changed from Major - For a full history of the issue, see: h

[jira] Updated: (MAVEN-1184) Broken support of whitespaces in parameters

2004-03-03 Thread jira
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Wed, 3 Mar 2004 4:59 AM Changes: Fix Version changed to 1.0-final - For a full history of the issue, see:

[jira] Updated: (MAVEN-1179) Cannot build when JAVA_HOME has spaces

2004-03-03 Thread jira
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Wed, 3 Mar 2004 4:59 AM Changes: Fix Version changed to 1.0-final - For a full history of the issue, see:

[jira] Closed: (MAVEN-464) Reactor cannot find goals in plugin

2004-03-03 Thread jira
Message: The following issue has been closed. Resolver: Brett Porter Date: Wed, 3 Mar 2004 4:52 AM having looked at the test case, I can see that the plugin construction project is not valid. The resulting plugin has no contents. The plugin project.xml needs to include what the ba

[jira] Closed: (MAVEN-1173) Move to ASL v2.

2004-03-03 Thread jira
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1173 Here is an overview of the issue: ---

[jira] Resolved: (MAVEN-1173) Move to ASL v2.

2004-03-03 Thread jira
Message: The following issue has been resolved as FIXED. Resolver: Emmanuel Venisse Date: Wed, 3 Mar 2004 3:39 AM Done on core and plugins - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN

[jira] Created: (MAVEN-1184) Broken support of whitespaces in parameters

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