Re: maven 1.0 prep
Brett, On Tuesday 06 July 2004 16:46, Brett Porter wrote: > I'd like to start preparing a release for Maven 1.0, so all the plugin > maintainers out there - please vote and pump out a release asap if you want > a new one bundled. after commiting of http://jira.codehaus.org/browse/MPNATIVE-6 the maven-native-plugin is ready for cross compile and ready for a release. thanks regards, Joachim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPJAVA-24) Target java:compile fails on Java 1.5.0 beta 2
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPJAVA-24 Here is an overview of the issue: - Key: MPJAVA-24 Summary: Target java:compile fails on Java 1.5.0 beta 2 Type: Bug Status: Open Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-java-plugin Assignee: Jason van Zyl Reporter: Christian Stein Created: Wed, 7 Jul 2004 2:00 AM Updated: Wed, 7 Jul 2004 2:00 AM Environment: W2k, J2SDK 1.5.0_beta2 Description: java:compile: [...] BUILD FAILED File... %HOME%\.maven\cache\maven-java-plugin-1.4\plugin.jelly Element ant:javac Line... 52 Column. 48 com/sun/tools/javac/Main (Unsupported major.minor version 49.0) Time to start maven-java-plugin-1.5 ?! :-) - 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: maven 1.0 prep
Tuesday would be great if you have a chance to take it for a spin. Quoting Dion Gillard <[EMAIL PROTECTED]>: > To do any real testing, I wont be able to do it over the weekend. > > I held off upgrading one set of projects to RC4 due to the HTTP > problems, and the earliest I'll get to that would be next Tuesday. > > On Wed, 7 Jul 2004 00:46:50 +1000, Brett Porter <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > I'd like to start preparing a release for Maven 1.0, so all the plugin > > maintainers out there - please vote and pump out a release asap if you want > a > > new one bundled. > > > > I'll do so tomorrow for the stuff I've touched recently where it is needed, > but > > with the mailing lists all dead at the moment, there's no need to hurry :) > > > > I'd like to have a final preview release ready for the weekend so people > here > > can take it for a spin and sanity check it. Then set it wild next week and > I'll > > go away on holidays and let someone else clean up the mess ;) > > > > As far as I'm concerned, there are no outstanding issues other than > > documentation that I intend to target for 1.0. Please let me know if you > disagree. > > > > Cheers, > > Brett > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > http://www.multitask.com.au/people/dion/ > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPANNOUNCEMENT-4) Cannot use plugin in project.xml's report element.
The following comment has been added to this issue: Author: Gary Gregory Created: Tue, 6 Jul 2004 9:27 PM Body: Here is an alternate POV. The changes plugin takes changes.xml as input and produces an HTML page out of it. I think the announcement plugin should be behave the same by default in the sense that the text file should contain a section for each release. This is commonly done in many products. This allows the user to see *in one place* what has changed between the version *he has* and the *new version*. This is important because the new version N, is not going to always be (by a longshot in my experience) the version the user has + 1. For example, I use version 2.1 and the new version is 3.5, with 2.2, 3.0, 3.1, etc in between. Of course a property should let the plugin generate just text for just one version but I really like it when release notes contain the history of previous releases. My 2c. - View this comment: http://jira.codehaus.org/browse/MPANNOUNCEMENT-4?page=comments#action_21449 - View the issue: http://jira.codehaus.org/browse/MPANNOUNCEMENT-4 Here is an overview of the issue: - Key: MPANNOUNCEMENT-4 Summary: Cannot use plugin in project.xml's report element. Type: New Feature Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-announcement-plugin Fix Fors: 1.2 Versions: 1.1 Assignee: Vincent Massol Reporter: Gary Gregory Created: Tue, 22 Jun 2004 5:44 PM Updated: Tue, 6 Jul 2004 9:27 PM Environment: >maven -i __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3 # BEGIN: Which report Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $) java.version=1.4.2_04 file.encoding=Cp1252 java.ext.dirs=C:\java\sun\1.4.2_04\jre\lib\ext java.class.path=C:\Program Files\Apache Software Foundation\Maven 1.0-rc3\lib\forehead-1.0-beta-5.jar os.name=Windows XP java.vendor=Sun Microsystems Inc. sun.boot.class.path=C:\Program Files\Apache Software Foundation\Maven 1.0-rc3\lib\endorsed\xerces-2.4.0.jar;C:\Program Files\Apache Software Foundation\Maven 1. 0-rc3\lib\endorsed\xml-apis-1.0.b2.jar;C:\java\sun\1.4.2_04\jre\lib\rt.jar;C:\java\sun\1.4.2_04\jre\lib\i18n.jar;C:\java\sun\1.4.2_04\jre\lib\sunrsasign.jar;C:\ java\sun\1.4.2_04\jre\lib\jsse.jar;C:\java\sun\1.4.2_04\jre\lib\jce.jar;C:\java\sun\1.4.2_04\jre\lib\charsets.jar;C:\java\sun\1.4.2_04\jre\classes java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition # END: Which report Installed plugins: maven-castor-plugin-1.2 maven-site-plugin-1.5 maven-multiproject-plugin-1.3 maven-jdepend-plugin-1.5 maven-clover-plugin-1.5 maven-genapp-plugin-2.2 maven-jbuilder-plugin-1.5 maven-jboss-plugin-1.5 maven-dashboard-plugin-1.3 maven-artifact-plugin-1.2 maven-developer-activity-plugin-1.5 maven-war-plugin-1.6 maven-native-plugin-1.1 maven-cruisecontrol-plugin-1.2 maven-webserver-plugin-2.0 maven-docbook-plugin-1.2 maven-deploy-plugin-1.3 maven-ear-plugin-1.5 maven-repository-plugin-1.2 maven-j2ee-plugin-1.5 maven-jnlp-plugin-1.3 maven-linkcheck-plugin-1.2 maven-javadoc-plugin-1.5 maven-vdoclet-plugin-1.2 maven-hibernate-plugin-1.1 maven-appserver-plugin-2.0 maven-antlr-plugin-1.2 maven-jira-plugin-1.1 maven-ant-plugin-1.7 maven-gump-plugin-1.3 maven-tasklist-plugin-2.3 maven-xdoc-plugin-1.7.1 maven-ashkelon-plugin-1.2 maven-tjdo-plugin-1.0.0 maven-html2xdoc-plugin-1.3 maven-announcement-plugin-1.1 maven-pmd-plugin-1.4 maven-jxr-plugin-1.4 maven-struts-plugin-1.3 maven-latka-plugin-1.4 maven-junit-doclet-plugin-1.2 maven-pom-plugin-1.4 maven-changelog-plugin-1.5 maven-clean-plugin-1.2 maven-license-plugin-1.2 maven-jetty-plugin-1.1 maven-jdee-plugin-1.1 maven-file-activity-plugin-1.5 maven-jcoverage-plugin-1.0.4 maven-jdiff-plugin-1.4 maven-jar-plugin-1.5 maven-scm-plugin-1.3 maven-aspectwerkz-plugin-1.2 maven-faq-plugin-1.3 maven-plugin-plugin-1.3 maven-dist-plugin-1.5 maven-jellydoc-plugin-1.3 maven-javacc-plugin-1.1 maven-shell-plugin-1.1 maven-simian-plugin-1.4 maven-ejb-plugin-1.4 maven-java-plugin-1.4 maven-console-plugin-1.1 maven-pdf-plugin-2.1 maven-release-plugin-1.3 maven-changes-plugin-1.4 maven-nsis-plugin-1.0 maven-checkstyle-plugin-2.4.1 maven-wizard-plugin-1.1 maven-uberjar-plugin-1.2 maven-caller-plugin-1.1 maven-junit-report-plugin-1.5 maven-eclipse-plugin-1.7 maven-latex-plugin-1.2 maven-jdeveloper-plugin-1.4 maven-aspectj-plugin-3.0 maven-idea-plugin-1.4 maven-jalopy-plugin-1
Re: maven 1.0 prep
To do any real testing, I wont be able to do it over the weekend. I held off upgrading one set of projects to RC4 due to the HTTP problems, and the earliest I'll get to that would be next Tuesday. On Wed, 7 Jul 2004 00:46:50 +1000, Brett Porter <[EMAIL PROTECTED]> wrote: > Hi all, > > I'd like to start preparing a release for Maven 1.0, so all the plugin > maintainers out there - please vote and pump out a release asap if you want a > new one bundled. > > I'll do so tomorrow for the stuff I've touched recently where it is needed, but > with the mailing lists all dead at the moment, there's no need to hurry :) > > I'd like to have a final preview release ready for the weekend so people here > can take it for a spin and sanity check it. Then set it wild next week and I'll > go away on holidays and let someone else clean up the mess ;) > > As far as I'm concerned, there are no outstanding issues other than > documentation that I intend to target for 1.0. Please let me know if you disagree. > > Cheers, > Brett > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPARTIFACT-25) some of the other plugins still refer maven-deploy-plugin
The following comment has been added to this issue: Author: Brett Porter Created: Tue, 6 Jul 2004 8:00 PM Body: They only refer to it to check it is not installed :) The warning is unfortunate... I may push that back to "debug" level I think. - View this comment: http://jira.codehaus.org/browse/MPARTIFACT-25?page=comments#action_21447 - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-25 Here is an overview of the issue: - Key: MPARTIFACT-25 Summary: some of the other plugins still refer maven-deploy-plugin Type: Bug Status: Unassigned Priority: Critical Original Estimate: 1 hour Time Spent: Unknown Remaining: 1 hour Project: maven-artifact-plugin Assignee: Reporter: Henning Schmiedehausen Created: Tue, 6 Jul 2004 7:05 AM Updated: Tue, 6 Jul 2004 8:00 PM Environment: java version "1.4.2_04" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05) Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode) Fedora Core 1 Linux Maven 1.0-RC4 built from CVS Maven Plugins HEAD built from CVS Description: maven-dist-plugin-1.7 maven-jar-plugin-1.6 maven-plugin-plugin-1.6 still refer to the maven-deploy-plugin which (according to the CVS) has been folded into maven-artifact-plugin. So e.g. building a plugin reports __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc4 Plugin 'maven-deploy-plugin' in project 'Maven Environment for Turbine Applications Plugin' is not available Plugin 'maven-deploy-plugin' in project 'Maven Environment for Turbine Applications Plugin' is not available build:start: plugin:plugin: java:prepare-filesystem: [...] - 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: (MPARTIFACT-25) some of the other plugins still refer maven-deploy-plugin
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-25 Here is an overview of the issue: - Key: MPARTIFACT-25 Summary: some of the other plugins still refer maven-deploy-plugin Type: Bug Status: Closed Priority: Critical Resolution: INCOMPLETE Original Estimate: 1 hour Time Spent: Unknown Remaining: 1 hour Project: maven-artifact-plugin Assignee: Reporter: Henning Schmiedehausen Created: Tue, 6 Jul 2004 7:05 AM Updated: Tue, 6 Jul 2004 8:00 PM Environment: java version "1.4.2_04" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05) Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode) Fedora Core 1 Linux Maven 1.0-RC4 built from CVS Maven Plugins HEAD built from CVS Description: maven-dist-plugin-1.7 maven-jar-plugin-1.6 maven-plugin-plugin-1.6 still refer to the maven-deploy-plugin which (according to the CVS) has been folded into maven-artifact-plugin. So e.g. building a plugin reports __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc4 Plugin 'maven-deploy-plugin' in project 'Maven Environment for Turbine Applications Plugin' is not available Plugin 'maven-deploy-plugin' in project 'Maven Environment for Turbine Applications Plugin' is not available build:start: plugin:plugin: java:prepare-filesystem: [...] - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: plugin dependencies
Thanks Vincent, I was more referring to adding a DEPRECATION message inside the cactus:dependency-handle tag, for example, so no new code uses it. - Brett Quoting Vincent Massol <[EMAIL PROTECTED]>: > > > > -Original Message- > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent: mardi 6 juillet 2004 14:30 > > To: Maven Developers List > > Subject: plugin dependencies > > > > Hi, > > > > After dIon prompted me to take a look yesterday afternoon I figured a way > > to > > load the plugin contexts on the fly without messing up the order of > > things, so > > maven:get/maven:set (and their legacy versions pluginVar > > and getPluginContext) now initialise a plugin if it is not already > > initialised. > > > > This means that all of the following are valid ways of introducing a > > plugin, and > > work together: > > - using a dynamic tag library from it > > - using a goal from it > > - using maven:get/maven:set > > > > The odd behaviour of > into > > the plugin context will continue to work, but is not something we want to > > encourage, so the documented way of manipulating plugin properties needs > > to be > > maven:get/maven:set. I won't document the dependency-handle stuff in this > > case > > as that really has nothing to do with the use of plugin properties. That > > was > > only the chosen preferred fashion last year because it was (marginally) > > better > > than a goal prereq. > > > > I've added deprecation warnings to all the :load goals and :dependecy- > > handle > > tags I could find. Vincent, you might like to do this for cactus too. > > Thanks for this change. Much needed and much appreciated. It was really a > pain in the past... > > I'll definitely modify the plugins I "manage". However, I'd prefer not to > modify them for some time as I would like them to stay compatible with older > versions of Maven (otherwise, it requires people to update their maven jelly > tags jar). I think a few weeks after 1.0 is released should be ok though. > > Thanks > -Vincent > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: plugin:setup/plugin:remove to replace plugin:install/plugin:uninstall
+1. On Tue, 6 Jul 2004 22:33:26 +1000, Brett Porter <[EMAIL PROTECTED]> wrote: > I propose that we rename (And deprecate the old) plugin:install/uninstall to > plugin:setup and plugin:remove > respectively. > This would pave the way to later rename plugin:repository-* to just plugin:* and > bring it in line with other artifact based plugins, and m2. > > plugin:install-now and plugin:uninstall-now should be removed and become > implicit in the installation process (these goals install into the executing Maven) > > Additionally, a mode parameter should be introduced that installs to either > "global", or "user". Global is maven.plugin.dir - ie the maven installation, use > is maven.plugin.user.dir - ie ~/.maven/plugins > > Cheers, > Brett > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/plugin/src/plugin-test maven.xml
dion2004/07/06 15:22:36
Modified:plugin/src/plugin-test maven.xml
Log:
- Use assert taglib in tests. The plugin must be installed to test anyway.
- Fix test loop bugs
Revision ChangesPath
1.3 +7 -10 maven-plugins/plugin/src/plugin-test/maven.xml
Index: maven.xml
===
RCS file: /home/cvs/maven-plugins/plugin/src/plugin-test/maven.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- maven.xml 4 Mar 2004 18:37:56 - 1.2
+++ maven.xml 6 Jul 2004 22:22:36 - 1.3
@@ -15,7 +15,10 @@
* limitations under the License.
*/
-->
-
+
+
@@ -23,18 +26,12 @@
-
-
- no xdocs directory created
-
+
navigation.xml,goals.xml
-
-
-
-no ${file} created
-
+
+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPPLUGIN-20) If artifactId, groupId or version are not present for plugin:download, prompt for them
Message: The following issue has been closed. Resolver: dion gillard Date: Tue, 6 Jul 2004 6:21 PM in 1.6 - View the issue: http://jira.codehaus.org/browse/MPPLUGIN-20 Here is an overview of the issue: - Key: MPPLUGIN-20 Summary: If artifactId, groupId or version are not present for plugin:download, prompt for them Type: Improvement Status: Closed Priority: Trivial Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-plugin-plugin Assignee: dion gillard Reporter: dion gillard Created: Tue, 29 Jun 2004 6:47 AM Updated: Tue, 6 Jul 2004 6:21 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]
cvs commit: maven-plugins/plugin project.xml plugin.jelly
dion2004/07/06 15:21:07 Modified:plugin/xdocs changes.xml plugin project.xml plugin.jelly Log: Prompt for artifactId, groupId and version if missing. PR: MPPLUGIN-20 Revision ChangesPath 1.26 +3 -0 maven-plugins/plugin/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/plugin/xdocs/changes.xml,v retrieving revision 1.25 retrieving revision 1.26 diff -u -r1.25 -r1.26 --- changes.xml 29 Jun 2004 11:41:05 - 1.25 +++ changes.xml 6 Jul 2004 22:21:06 - 1.26 @@ -25,6 +25,9 @@ + +Prompt for artifactId, groupId and version if missing. + Add assertFileNotFound tag 1.41 +5 -0 maven-plugins/plugin/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/plugin/project.xml,v retrieving revision 1.40 retrieving revision 1.41 diff -u -r1.40 -r1.41 --- project.xml 29 Jun 2004 11:41:05 - 1.40 +++ project.xml 6 Jul 2004 22:21:07 - 1.41 @@ -92,5 +92,10 @@ 20030211.142705 http://jakarta.apache.org/commons/jelly/libs/xml/ + + commons-jelly + commons-jelly-tags-interaction + 20030211.143817 + 1.41 +19 -4 maven-plugins/plugin/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven-plugins/plugin/plugin.jelly,v retrieving revision 1.40 retrieving revision 1.41 diff -u -r1.40 -r1.41 --- plugin.jelly 29 Jun 2004 11:41:05 - 1.40 +++ plugin.jelly 6 Jul 2004 22:21:07 - 1.41 @@ -19,14 +19,14 @@ @@ -206,8 +206,23 @@ + + + + + + + + + + +
[jira] Commented: (MPJAR-30) Manifest creation for dependency jars deployed in a sub-directory
The following comment has been added to this issue:
Author: Eric Giguere
Created: Tue, 6 Jul 2004 2:30 PM
Body:
Hello.
Finally, here is the CVS diff run against jar plugin v1.6
A note.. I've submitted another change (the includes) for the plugin. The change was
integrated a while ago but was removed from version 1.6. Is there a reason??
Anyway, I'll submit here both diffs:
Index: plugin.jelly
===
RCS file: /home/cvs/cvsroot/nhc-maven/maven-plugins/jar/plugin.jelly,v
retrieving revision 1.3
diff -w -b -i -r1.3 plugin.jelly
83c83,84
< excludes="${maven.jar.excludes}">
---
> excludes="${maven.jar.excludes}"
> includes="${maven.jar.includes}">
And here is the new addition to allow sub-dir deployment of dependency jars with Jar
manifest classpath updated accordingly.
105a107,111
>
>
> value="${pom.getProperty('jar.dependency.dist.dir')}${'/'}"/>
>
>
108c114,120
<
---
>
>
>
>
> value="${dep.getProperty('jar.dependency.dist.dir')}${'/'}"/>
>
>
* CVS exited normally with code 1 *
-
View this comment:
http://jira.codehaus.org/browse/MPJAR-30?page=comments#action_21442
-
View the issue:
http://jira.codehaus.org/browse/MPJAR-30
Here is an overview of the issue:
-
Key: MPJAR-30
Summary: Manifest creation for dependency jars deployed in a sub-directory
Type: Improvement
Status: Open
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-jar-plugin
Assignee: Jason van Zyl
Reporter: Eric Giguere
Created: Fri, 18 Jun 2004 10:40 AM
Updated: Tue, 6 Jul 2004 2:30 PM
Environment: All OS, no special specs for this feature.
Description:
Library jars are not usually deployed in the same directory than the executable
application file. Usually, libraries are deployed in subdirectories of the project
root, even sometimes general library paths accessible by many applications.
The change I submit here uses a property you define at the project and that can be
overriden for a sinble dependency.
The project property looks like this:
lib
The same entry is used in a dependency entry in project.xml.
The code change required in the plugin is this (CVS diff):
* CVS exited normally with code 0 *
cvs diff -r 1.1 -r 1.2 -wb -i plugin.jelly plugin.jelly (in directory
C:\Work\cvs-nhc-maven\nhc-maven\maven-plugins\jar\)
Index: plugin.jelly
===
RCS file: /home/cvs/cvsroot/nhc-maven/maven-plugins/jar/plugin.jelly,v
retrieving revision 1.1
retrieving revision 1.2
diff -w -b -i -r1.1 -r1.2
55a56,60
>
>
> value="${pom.getProperty('jar.dependency.dist.dir')}${'/'}"/>
>
>
58c63,69
<
---
>
>
>
>
> value="${dep.getProperty('jar.dependency.dist.dir')}${'/'}"/>
>
>
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1360) Broken archive breaks the build
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1360 Here is an overview of the issue: - Key: MAVEN-1360 Summary: Broken archive breaks the build Type: Improvement Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Versions: 1.0 Assignee: Reporter: Ludovic Claude Created: Tue, 6 Jul 2004 2:26 PM Updated: Tue, 6 Jul 2004 2:26 PM Description: Somewhere in my repository there is a broken archive, and it breaks my build badly. Unfortunately, maven doesn't help me very much to locate the guilty archive. Here is the error as reported by maven: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.(ZipFile.java:112) at java.util.zip.ZipFile.(ZipFile.java:128) at org.apache.tools.ant.AntClassLoader.getResourceURL(AntClassLoader.java:870) at org.apache.tools.ant.AntClassLoader.getResource(AntClassLoader.java:799) at java.lang.Class.getResource(Class.java:1352) at xdoclet.tagshandler.MergeTagsHandler.getMergeFileContents(MergeTagsHandler.java:207) at xdoclet.tagshandler.MergeTagsHandler.merge(MergeTagsHandler.java:67) at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at xdoclet.template.TemplateEngine.invoke(TemplateEngine.java:603) at xdoclet.template.TemplateEngine.invokeMethod(TemplateEngine.java:502) at xdoclet.template.TemplateEngine.invokeBlockMethod(TemplateEngine.java:927) at xdoclet.template.TemplateEngine.handleBlockTag(TemplateEngine.java:894) at xdoclet.template.TemplateEngine.handleTag(TemplateEngine.java:434) at xdoclet.template.TemplateEngine.generate(TemplateEngine.java:333) at xdoclet.XDocletTagSupport.generate(XDocletTagSupport.java:738) at xdoclet.tagshandler.MergeTagsHandler.generateUsingMergedFile(MergeTagsHandler.java:256) at xdoclet.tagshandler.MergeTagsHandler.merge(MergeTagsHandler.java:79) at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at xdoclet.template.TemplateEngine.invoke(TemplateEngine.java:603) at xdoclet.template.TemplateEngine.invokeMethod(TemplateEngine.java:502) at xdoclet.template.TemplateEngine.invokeBlockMethod(TemplateEngine.java:927) at xdoclet.template.TemplateEngine.handleBlockTag(TemplateEngine.java:894) at xdoclet.template.TemplateEngine.handleTag(TemplateEngine.java:434) at xdoclet.template.TemplateEngine.generate(TemplateEngine.java:333) at xdoclet.XDocletTagSupport.generate(XDocletTagSupport.java:738) at xdoclet.modules.ejb.EjbTagsHandler.ifIsAConcreteEJBean(EjbTagsHandler.java:544) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at xdoclet.template.TemplateEngine.invoke(TemplateEngine.java:603) at xdoclet.template.TemplateEngine.invokeMethod(TemplateEngine.java:529) at xdoclet.template.TemplateEngine.invokeBlockMethod(TemplateEngine.java:927) at xdoclet.template.TemplateEngine.handleBlockTag(TemplateEngine.java:894) at xdoclet.template.TemplateEngine.handleTag(TemplateEngine.java:434) at xdoclet.template.TemplateEngine.generate(TemplateEngine.java:333) at xdoclet.XDocletTagSupport.generate(XDocletTagSupport.java:738) at xdoclet.modules.ejb.session.SessionTagsHandler.forAllSessionBeans(SessionTagsHandler.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at xdoclet.template.TemplateEngine.invoke(TemplateEngine.java:603) at xdoclet.template.TemplateEngine.invokeMethod(TemplateEngine.java:502) at xdoclet.template.TemplateEngine.invokeBlockMethod(TemplateEngine.java:927) at xdoclet.template.TemplateEngine.handleBlockTag(TemplateEngine.java:894)
[jira] Commented: (MPDIST-11) Parent project is not included in distributions
The following comment has been added to this issue: Author: Carlos Sanchez Created: Tue, 6 Jul 2004 12:10 PM Body: This will be fixed if parent project could be in a dependency jar. See MAVEN-699 - View this comment: http://jira.codehaus.org/browse/MPDIST-11?page=comments#action_21438 - View the issue: http://jira.codehaus.org/browse/MPDIST-11 Here is an overview of the issue: - Key: MPDIST-11 Summary: Parent project is not included in distributions Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-dist-plugin Assignee: Jason van Zyl Reporter: Carlos Sanchez Created: Sat, 3 Jul 2004 2:16 PM Updated: Tue, 6 Jul 2004 12:10 PM Description: I think that parent project.xml and project.properties should be merged with those from current project to be included in distribution It's easier to distribute only one project.xml and project.properties - 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: (MPJCOVERAGE-9) Bad path to stylesheet generated
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Tue, 6 Jul 2004 12:07 PM
Applied. Thanks.
-
View the issue:
http://jira.codehaus.org/browse/MPJCOVERAGE-9
Here is an overview of the issue:
-
Key: MPJCOVERAGE-9
Summary: Bad path to stylesheet generated
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Original Estimate: 0 minutes
Time Spent: Unknown
Remaining: 0 minutes
Project: maven-jcoverage-plugin
Fix Fors:
1.0.6
Versions:
1.0.3
1.0.4
1.0.5
Assignee: Emmanuel Venisse
Reporter: Philippe Mouawad
Created: Thu, 3 Jun 2004 10:06 AM
Updated: Tue, 6 Jul 2004 12:07 PM
Environment: Windows NT
Description:
When I use jcoverage plugin, it generate HTML files with the following kind of path
for stylesheet:
As you can see there is \. that should be .
This results into the browser not finding the stylesheet.
I opened the code and replaced
return new Perl5Util().substitute("s/[^\\.]*(\\.|$)/\\.\\.\\//g", path);
by
return new Perl5Util().substitute("s/[^\\.]*(\\.|$)/..\\//g", path);
In method org.apache.maven.jcoveragereport.CoverageReport => private String
getRelativePath(String path)
In fact if you look at ;
http://jakarta.apache.org/oro/api/org/apache/oro/text/perl/Perl5Util.html
In the following example:
line = util.substitute("s/description1\\.html/about1.html/", line);
They don't escape the . in the replacement string.
and it know generates good pathes.
Since I didn't find a bug for this I thought I may be doing something wrong,
could you help me please.
-
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-1260) please upload xmlstubs-1.0.1 on ibiblio
Message: The following issue has been closed. Resolver: Carlos Sanchez Date: Tue, 6 Jul 2004 11:56 AM Check http://maven.apache.org/repository-upload.html - View the issue: http://jira.codehaus.org/browse/MAVEN-1260 Here is an overview of the issue: - Key: MAVEN-1260 Summary: please upload xmlstubs-1.0.1 on ibiblio Type: Wish Status: Closed Priority: Major Resolution: INCOMPLETE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Assignee: Reporter: nicolas de loof Created: Tue, 4 May 2004 5:39 AM Updated: Tue, 6 Jul 2004 11:56 AM Description: please upload xmlstubs-1.0.1 on ibiblio azote xmlstubs 1.0.1 licensed under apache http://www.apache.org/licenses/LICENSE-2.0 - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: plugin dependencies
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: mardi 6 juillet 2004 14:30 > To: Maven Developers List > Subject: plugin dependencies > > Hi, > > After dIon prompted me to take a look yesterday afternoon I figured a way > to > load the plugin contexts on the fly without messing up the order of > things, so > maven:get/maven:set (and their legacy versions pluginVar > and getPluginContext) now initialise a plugin if it is not already > initialised. > > This means that all of the following are valid ways of introducing a > plugin, and > work together: > - using a dynamic tag library from it > - using a goal from it > - using maven:get/maven:set > > The odd behaviour of into > the plugin context will continue to work, but is not something we want to > encourage, so the documented way of manipulating plugin properties needs > to be > maven:get/maven:set. I won't document the dependency-handle stuff in this > case > as that really has nothing to do with the use of plugin properties. That > was > only the chosen preferred fashion last year because it was (marginally) > better > than a goal prereq. > > I've added deprecation warnings to all the :load goals and :dependecy- > handle > tags I could find. Vincent, you might like to do this for cactus too. Thanks for this change. Much needed and much appreciated. It was really a pain in the past... I'll definitely modify the plugins I "manage". However, I'd prefer not to modify them for some time as I would like them to stay compatible with older versions of Maven (otherwise, it requires people to update their maven jelly tags jar). I think a few weeks after 1.0 is released should be ok though. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPXDOC-80) Support global theme
The following comment has been added to this issue:
Author: Joerg Schaible
Created: Tue, 6 Jul 2004 11:41 AM
Body:
No, not at all. This patch has nothing to do with a jsl file. It's just the location,
where your theme (css file) is physically located, that you want to use in all your
subprojects. Currently you have to have such a css in every "xdocs/stylesheets"
folder. With the patch, the defined file is copied into each projects'
${maven.docs.dest}/style folder.
Working example:
maven.xdoc.theme=my-theme
maven.xdoc.theme.file=${maven.multiproject.basedir}/root/xdocs/stylesheets/maven-my-theme.css
-
View this comment:
http://jira.codehaus.org/browse/MPXDOC-80?page=comments#action_21433
-
View the issue:
http://jira.codehaus.org/browse/MPXDOC-80
Here is an overview of the issue:
-
Key: MPXDOC-80
Summary: Support global theme
Type: Improvement
Status: Open
Priority: Major
Original Estimate: 10 minutes
Time Spent: Unknown
Remaining: 10 minutes
Project: maven-xdoc-plugin
Assignee: Brett Porter
Reporter: Joerg Schaible
Created: Tue, 17 Feb 2004 8:18 AM
Updated: Tue, 6 Jul 2004 11:41 AM
Description:
While it is possible to set an URL for an own theme using the new property
maven.xdoc.theme.url, you cannot tell the xdoc plugin which local file you are using.
The current approach enforces every project to have its own copy of the theme. This is
extremly nasty in combination with multiproject.
Proposal: Support a new property maven.xdoc.theme.file, that defines the local
location of the theme file. This file is copied into the ${maven.docs.dest}/style
directory.
Please have a look at jakarta-commons, they suffer from this problem also:
http://www.mail-archive.com/commons-dev%40jakarta.apache.org/index.html#35557
-
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-1359) maven.bat fails when %HOME% contains a back slash at the end
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MAVEN-1359 Here is an overview of the issue: - Key: MAVEN-1359 Summary: maven.bat fails when %HOME% contains a back slash at the end Type: Bug Status: Closed Priority: Major Resolution: DUPLICATE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: cli Versions: 1.0-rc4 Assignee: Reporter: Kenichi Masuko Created: Tue, 6 Jul 2004 9:45 AM Updated: Tue, 6 Jul 2004 11:37 AM Environment: Windows XP, Windows 2000 Description: In maven.bat, java is launched with the following command: %MAVEN_JAVA_EXE% ... "-Duser.home.env=%HOME%" ... When the last character of the content of HOME is a back slash, maven failed to start. For example, when HOME is set to be d:\ "-Duser.home.env=%HOME%" becomes "-Duser.home.env=d:\" and Windows sees the character sequence \" at the end as a single character (an escape character + a special character) rather than a character followed by a quotation which ends a parameter. This breaks matching of quotation character pairs making the last pair consume all the characters after it. As a result, main java class name near the end of the line is concatenated to the content of the last pair, and java doesn't see the main class to run and exits. I first tried to change HOME to be d: rather than d:\ but Windows 2000/XP doesn't accept d: saying it is not a valid absolute path. So, if the last character of HOME is a back slash, I think we need to replace it with double back slashes like below. set HOME_ENV_PARAM_LEFT=%HOME:~0,-1% set HOME_ENV_PARAM_RIGHT=%HOME:~-1% set HOME_ENV_PARAM=%HOME_ENV_PARAM_LEFT%%HOME_ENV_PARAM_RIGHT:\=\\% %MAVEN_JAVA_EXE% ... "-Duser.home.env=%HOME_ENV_PARAM%" ... - 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: (MAVENUPLOAD-140) JPOX Enhancer
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Tue, 6 Jul 2004 9:11 AM Uploaded - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-140 Here is an overview of the issue: - Key: MAVENUPLOAD-140 Summary: JPOX Enhancer Type: Bug Status: Closed Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Andy Jefferson Created: Tue, 15 Jun 2004 12:04 PM Updated: Tue, 6 Jul 2004 9:11 AM Description: http://www.jpox.org/jpox-enhancer-1.0.0-beta-4-bundle.jar Please upload! DO IT NOW! This should be put under groupId of "jpox" and NOT "jpox-enhancer". - 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: (MAVENUPLOAD-145) Spring 1.0.2
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Tue, 6 Jul 2004 9:09 AM I moved this ZIP up manually this time, but I won't do it again. So either give me bundles to upload or let's create a repo on your end that can be sync'd to ibiblio. Moving ZIP files around is error prone and a PITA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-145 Here is an overview of the issue: - Key: MAVENUPLOAD-145 Summary: Spring 1.0.2 Type: Wish Status: Closed Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Alef Arendsen Created: Tue, 22 Jun 2004 5:38 PM Updated: Tue, 6 Jul 2004 9:09 AM Description: Hi guys, There's another Spring release people want to have uploaded in ibiblio. I've put a file online at www.springframework.org/downloads/ibiblio-spring-1.0.2.zip. Thanks a bunch! p.s. I prepared the file just as before, if you need changes to the format or something, just let me know. Alef Arendsen - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jcoverage/xdocs changes.xml
evenisse2004/07/06 09:06:46
Modified:jcoverage/src/main/org/apache/maven/jcoveragereport
CoverageReport.java
jcoverage/xdocs changes.xml
Log:
[MPJCOVERAGE-9]. Fixed path to stylesheet.
Revision ChangesPath
1.10 +2 -2
maven-plugins/jcoverage/src/main/org/apache/maven/jcoveragereport/CoverageReport.java
Index: CoverageReport.java
===
RCS file:
/home/cvs/maven-plugins/jcoverage/src/main/org/apache/maven/jcoveragereport/CoverageReport.java,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- CoverageReport.java 31 Mar 2004 22:55:19 - 1.9
+++ CoverageReport.java 6 Jul 2004 16:06:46 - 1.10
@@ -489,7 +489,7 @@
{
if (path != null && !path.equals(""))
{
-return new Perl5Util().substitute("s/[^\\.]*(\\.|$)/\\.\\.\\//g", path);
+return new Perl5Util().substitute("s/[^\\.]*(\\.|$)/..\\//g", path);
}
else
{
1.19 +1 -0 maven-plugins/jcoverage/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/jcoverage/xdocs/changes.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- changes.xml 3 Jul 2004 02:08:16 - 1.18
+++ changes.xml 6 Jul 2004 16:06:46 - 1.19
@@ -25,6 +25,7 @@
+ Fixed path to
stylesheet.
Remove postGoal on clean to avoid introducing
all these dependencies on a simple clean.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-144) Please upload sslext.jar
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Tue, 6 Jul 2004 9:04 AM Uploaded - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-144 Here is an overview of the issue: - Key: MAVENUPLOAD-144 Summary: Please upload sslext.jar Type: Bug Status: Closed Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Tim Shadel Created: Fri, 18 Jun 2004 1:41 PM Updated: Tue, 6 Jul 2004 9:04 AM Description: http://www.timshadel.com/sslext-1.10-4-bundle.jar SSLExt is an extension for Struts. It is maintained by Steve Ditlinger on SourceForge (http://sslext.sf.net). Please upload it to make it available to Maven. Thanks! - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-146) Event-1.0
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Tue, 6 Jul 2004 9:03 AM Uploaded - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-146 Here is an overview of the issue: - Key: MAVENUPLOAD-146 Summary: Event-1.0 Type: New Feature Status: Closed Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Berin Loritsch Created: Thu, 24 Jun 2004 9:52 AM Updated: Tue, 6 Jul 2004 9:03 AM Description: http://dist.d-haven.org/even-1.0-bundle.jar D-Haven Event is a library designed to make it easier to develop event based processing systems. It also includes a CommandManager to handle certain activities behind the scenes in a controlled number of background threads. The library has been fully tested, and all dependencies have been brought to a minimum. - 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: (MAVENUPLOAD-147) Managed Pool 1.0
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Tue, 6 Jul 2004 9:00 AM Uploaded - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-147 Here is an overview of the issue: - Key: MAVENUPLOAD-147 Summary: Managed Pool 1.0 Type: New Feature Status: Closed Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Berin Loritsch Created: Thu, 24 Jun 2004 10:22 AM Updated: Tue, 6 Jul 2004 9:00 AM Description: D-Haven Managed Pool is a library designed to provide pools that are asynchronously managed in a background thread. The pool system is very flexible and can accomodate just about every need. It boasts the ability to add pool listeners so that you can instrument and intercept the pooled objects when they are created, destroyed, acquired, and released. - 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: (MAVENUPLOAD-148) DBUnit 2.1
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Tue, 6 Jul 2004 8:55 AM Link to bundle yields a 404. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-148 Here is an overview of the issue: - Key: MAVENUPLOAD-148 Summary: DBUnit 2.1 Type: Task Status: Closed Resolution: INCOMPLETE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Carlos Sanchez Created: Fri, 25 Jun 2004 9:13 AM Updated: Tue, 6 Jul 2004 8:55 AM Description: http://oness.sourceforge.net/maven/upload-bundles/dbunit-2.1-bundle.jar DbUnit is a JUnit extension targeted for database-driven projects - 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: Maven 1.0-rc4 Released
Hi - I have tried unsuccessfully several times to unsubscribe from the maven developers list (both via email to [EMAIL PROTECTED] and through the web site). None of my attempts to unsubscribe have worked. I am still receiving mail from the list. I need a human being to unsubscrib me manually from this list. Can anyone help? Thank you. - David L. Paterline Principal Engineer Westinghouse Electric Company Nuclear Fuel Engineering Engineering Computing [EMAIL PROTECTED] PH: 412-374-2286 FX: 412-374-2284 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-149) Jgoodies uploads of latest libraries
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Tue, 6 Jul 2004 8:53 AM Uploaded - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-149 Here is an overview of the issue: - Key: MAVENUPLOAD-149 Summary: Jgoodies uploads of latest libraries Type: Improvement Status: Closed Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Colin Saxton Created: Sun, 27 Jun 2004 9:07 AM Updated: Tue, 6 Jul 2004 8:53 AM Description: I have been given permission to request upload of the latest jgoodies jars by [EMAIL PROTECTED] - The original email is as follows... ** Hi Colin,The JGoodies JARs at ibiblio.org are outdated.The most recent versions are forms-1.0.4.jar andlooks-1.2.2.jar, as well as animation-1.0.3.jar.I should appreciate if you could tell the Maven peopleto update the JARs at ibiblio.org to provide the latest versions.You can find all my library releases at http://www.jgoodies.com/downloads/libraries.htmlBest regards,Karsten ** Please contact him if you require confirmation 3 bundles follow... http://homepage.ntlworld.com/colin.saxton/looks-1.2.2-bundle.jar Free high-fidelity Windows and multi-platform appearance. The JGoodies Looks make your Swing applications and applets look better. The package consists of a Windows look&feel and the Plastic look&feel family. These have been optimized for readability, precise micro-design and usability. http://homepage.ntlworld.com/colin.saxton/animation-1.1.3-bundle.jar Time-based real-time animations. The JGoodies Animation framework enables you to produce sophisticated time-based real-time animations in Java. It has been designed for a seemless, flexible and powerful integration with Java, ease-of-use and a small library size. The Animation framework requires Java 1.4 or later. http://homepage.ntlworld.com/colin.saxton/forms-1.0.4-bundle.jar Build better screens faster. The Forms framework helps you lay out and implement elegant Swing panels quickly and consistently. It makes simple things easy and the hard stuff possible, the good design easy and the bad difficult. Forms requires Java 1.4 or later. - 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: (MAVENUPLOAD-151) Upload Ubique's IniEditor
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Tue, 6 Jul 2004 8:46 AM Uploaded - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-151 Here is an overview of the issue: - Key: MAVENUPLOAD-151 Summary: Upload Ubique's IniEditor Type: Task Status: Closed Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Joerg Schaible Created: Tue, 29 Jun 2004 10:03 AM Updated: Tue, 6 Jul 2004 8:46 AM Description: Small utility class supporting config files in ini style. License in BSD style. - 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-1093) clarify xmlns dependency notation for plugin
Message: The following issue has been closed. Resolver: Brett Porter Date: Tue, 6 Jul 2004 8:40 AM that method is no longer used. - View the issue: http://jira.codehaus.org/browse/MAVEN-1093 Here is an overview of the issue: - Key: MAVEN-1093 Summary: clarify xmlns dependency notation for plugin Type: Task Status: Closed Priority: Major Resolution: WON'T FIX Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin manager Fix Fors: 1.0 Versions: 1.0-rc2 Assignee: Brett Porter Reporter: Brett Porter Created: Tue, 30 Dec 2003 10:39 PM Updated: Tue, 6 Jul 2004 8:40 AM Description: several plugins reference dynataglibs that are not present. IT can be used as a way to specify a dependency on that plugin and load it's namespace. It would be better to use plugin dependency elements to do this - decide and implement if that is the case. Additionally, suppress the current warning messages that occur when this is used. Check it still works as is for now. Also, cleanup any unused ones in plugins (eg license in nsis, I think is unused) - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPARTIFACT-25) some of the other plugins still refer maven-deploy-plugin
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-25 Here is an overview of the issue: - Key: MPARTIFACT-25 Summary: some of the other plugins still refer maven-deploy-plugin Type: Bug Status: Unassigned Priority: Critical Original Estimate: 1 hour Time Spent: Unknown Remaining: 1 hour Project: maven-artifact-plugin Assignee: Reporter: Henning Schmiedehausen Created: Tue, 6 Jul 2004 7:05 AM Updated: Tue, 6 Jul 2004 7:05 AM Environment: java version "1.4.2_04" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05) Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode) Fedora Core 1 Linux Maven 1.0-RC4 built from CVS Maven Plugins HEAD built from CVS Description: maven-dist-plugin-1.7 maven-jar-plugin-1.6 maven-plugin-plugin-1.6 still refer to the maven-deploy-plugin which (according to the CVS) has been folded into maven-artifact-plugin. So e.g. building a plugin reports __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc4 Plugin 'maven-deploy-plugin' in project 'Maven Environment for Turbine Applications Plugin' is not available Plugin 'maven-deploy-plugin' in project 'Maven Environment for Turbine Applications Plugin' is not available build:start: plugin:plugin: java:prepare-filesystem: [...] - 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: (MAVENUPLOAD-152) Java 3D core library
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Tue, 6 Jul 2004 8:39 AM Uploaded - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-152 Here is an overview of the issue: - Key: MAVENUPLOAD-152 Summary: Java 3D core library Type: Wish Status: Closed Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Omair-Inam Abdul-Matin Created: Wed, 30 Jun 2004 4:51 PM Updated: Tue, 6 Jul 2004 8:39 AM 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] Closed: (MAVENUPLOAD-150) EventBus 1.0
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Tue, 6 Jul 2004 8:51 AM Uploaded - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-150 Here is an overview of the issue: - Key: MAVENUPLOAD-150 Summary: EventBus 1.0 Type: Task Status: Closed Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Berin Loritsch Created: Mon, 28 Jun 2004 3:42 PM Updated: Tue, 6 Jul 2004 8:51 AM Description: http://dist.d-haven.org/eventbus-1.0-bundle.jar Provide a well tested Event Bus for use in any Swing based application. Licensed under the Apache Software License 2.0. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/war/xdocs changes.xml
brett 2004/07/06 05:37:18 Modified:abbotplugin.jelly artifact plugin.jelly artifact/xdocs changes.xml aspectj plugin.jelly clover plugin.jelly ear plugin.jelly project.xml ear/xdocs changes.xml eclipse plugin.jelly idea plugin.jelly java plugin.jelly java/xdocs changes.xml javadoc plugin.jelly multiproject plugin.jelly project.xml multiproject/xdocs changes.xml rar plugin.jelly rar/xdocs changes.xml test plugin.jelly project.xml test/xdocs changes.xml war plugin.jelly war/xdocs changes.xml Log: update a bunch of plugin dependency usages Revision ChangesPath 1.3 +1 -0 maven-plugins/abbot/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven-plugins/abbot/plugin.jelly,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- plugin.jelly 12 Jun 2004 14:15:14 - 1.2 +++ plugin.jelly 6 Jul 2004 12:37:16 - 1.3 @@ -359,6 +359,7 @@ + DEPRECATED: the use of dependency-handle is deprecated. Please use maven:get/set to modify properties of the abbot plugin 1.10 +1 -2 maven-plugins/artifact/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven-plugins/artifact/plugin.jelly,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- plugin.jelly 25 Jun 2004 18:37:27 - 1.9 +++ plugin.jelly 6 Jul 2004 12:37:17 - 1.10 @@ -214,8 +214,7 @@ - DEPRECATED: you do not need to use artifact:load for plugin dependencies. Instead, use the - xmlns:artifact="artifact" notation + DEPRECATED: you do not need to use artifact:load for plugin dependencies. 1.26 +1 -0 maven-plugins/artifact/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/artifact/xdocs/changes.xml,v retrieving revision 1.25 retrieving revision 1.26 diff -u -r1.25 -r1.26 --- changes.xml 3 Jul 2004 02:05:33 - 1.25 +++ changes.xml 6 Jul 2004 12:37:17 - 1.26 @@ -26,6 +26,7 @@ + Deprecated the artifact:load hook goal Allow use of distributionSite POM attribute in artifact method Update dependencies on commons-* 1.18 +1 -0 maven-plugins/aspectj/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven-plugins/aspectj/plugin.jelly,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- plugin.jelly 30 Jun 2004 20:45:19 - 1.17 +++ plugin.jelly 6 Jul 2004 12:37:17 - 1.18 @@ -211,6 +211,7 @@ + 1.25 +1 -0 maven-plugins/clover/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven-plugins/clover/plugin.jelly,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- plugin.jelly 12 Jun 2004 05:20:57 - 1.24 +++ plugin.jelly 6 Jul 2004 12:37:17 - 1.25 @@ -34,6 +34,7 @@ --> + 1.19 +3 -1 maven-plugins/ear/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven-plugins/ear/plugin.jelly,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- plugin.jelly 15 Mar 2004 10:54:10 - 1.18 +++ plugin.jelly 6 Jul 2004 12:37:17 - 1.19 @@ -257,7 +257,9 @@ - + +DEPRECATED: do not use ear:load, there is no need + 1.33 +1 -1 maven-plugins/ear/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/ear/project.xml,v retrieving revision 1.32 retrieving revision 1.33 diff -u -r1.32 -r1.33 --- project.xml 25 Jun 2004 15:24:28 - 1.32 +++ project.xml 6 Jul 2004 12:37:17 - 1.33 @@ -23,7 +23,7 @@ 3 maven-ear-plugin Maven EAR Plugin - 1.5 + 1.6-SNAPSHOT Ear Plugin for Maven Ear Plugin for Maven http://maven.apache.org/reference/plugins/ear/
[jira] Reopened: (MAVENUPLOAD-148) DBUnit 2.1
Message: The following issue has been reopened. Reopener: Carlos Sanchez Date: Tue, 6 Jul 2004 10:31 AM Fixed 404 - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-148 Here is an overview of the issue: - Key: MAVENUPLOAD-148 Summary: DBUnit 2.1 Type: Task Status: Reopened Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Carlos Sanchez Created: Fri, 25 Jun 2004 9:13 AM Updated: Tue, 6 Jul 2004 10:31 AM Description: http://oness.sourceforge.net/maven/upload-bundles/dbunit-2.1-bundle.jar DbUnit is a JUnit extension targeted for database-driven projects - 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: (MPARTIFACT-23) scp dos not work at all
Message: The following issue has been closed. Resolver: Brett Porter Date: Tue, 6 Jul 2004 10:30 AM added -o - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-23 Here is an overview of the issue: - Key: MPARTIFACT-23 Summary: scp dos not work at all Type: Bug Status: Closed Priority: Critical Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-artifact-plugin Versions: 1.1 Assignee: Brett Porter Reporter: Joerg Schaible Created: Mon, 5 Jul 2004 10:49 AM Updated: Tue, 6 Jul 2004 10:30 AM Environment: Source: WIN XP, Cygwin; Target: SuSE Linux 7.1; Maven 1.0 RC4 Description: I cannot get the scp protocol to work at all. Obviously support for ssh-agent is missing (MPARTIFACT-22) and I can only connect at all if I set the username, password, passphrase and privatekey of the repo. Unfortunately the deployment still fails with: == %< == jar:deploy: [echo] maven.repo.list is set - using artifact deploy mode Will deploy to 1 repository(ies): elsag Deploying to repository: elsag host: 'es3.elsag.de' Using private key: C:\Dokumente und Einstellungen\jos\.ssh\id_dsa Deploying: C:\Work\Projects\commons\test\project.xml-->elsag-commons/poms/elsag-test-0.2-SNAPSHOT.pom deployNotCompressed=false Executing command: scp -t /devel/maven/home/public_html/repo/maven-deployer-62294.zip Executing command: unzip -u /devel/maven/home/public_html/repo/maven-deployer-62294.zip -d /devel/maven/home/public_html/repo Failed to deploy to: elsag Reason: Cannot execute remote command: unzip -u /devel/maven/home/public_html/repo/maven-deployer-62294.zip -d /devel/maven/home/public_html/repo org.apache.maven.deploy.exceptions.TransferFailedException: Cannot execute remote command: unzip -u /devel/maven/home/public_html/repo/maven-deployer-62294.zip -d /devel/maven/home/public_html/repo == %< == Executing the commend directly, it is obvious: == %< == $ ssh es3 unzip -u /devel/maven/home/public_html/repo/maven-deployer-62294.zip -d /devel/maven/home/public_html/repo Archive: /devel/maven/home/public_html/repo/maven-deployer-62294.zip replace /devel/maven/home/public_html/repo/elsag-commons/poms/elsag-test-0.2-SNAPSHOT.pom? [y]es, [n]o, [A]ll, [N]one, [r]ename: Killed by signal 2. == %< == Please use -uo as option for unzip! Overwriting is quite common for SNAPSHOT :) -- Jörg - 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-1354) maven.bat does not handle user home at root of drive (Windows)
Message: The following issue has been closed. Resolver: Brett Porter Date: Tue, 6 Jul 2004 10:30 AM just removed it. - View the issue: http://jira.codehaus.org/browse/MAVEN-1354 Here is an overview of the issue: - Key: MAVEN-1354 Summary: maven.bat does not handle user home at root of drive (Windows) Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: 30 minutes Time Spent: Unknown Remaining: 30 minutes Project: maven Fix Fors: 1.0 Versions: 1.0-rc4 Assignee: Brett Porter Reporter: Harald Ommang Created: Thu, 1 Jul 2004 2:40 AM Updated: Tue, 6 Jul 2004 10:30 AM Environment: Windows Description: In maven.bat for rc4, a new property is added to the command line for running maven: "-Duser.home.env=%HOME%". When the user has %HOME% set to the root of a drive, so that the result is e.g. "-Duser.home.env=Q:\" , this command fails. The backslash escapes the following quoute, and java.exe complains that the usage pattern is not followed. - 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/test/touchstone-build maven.xml
brett 2004/07/06 05:27:20
Modified:src/test/touchstone-build Tag: MAVEN-1_0-BRANCH maven.xml
Log:
add test for maven:set
Revision ChangesPath
No revision
No revision
1.43.4.19 +6 -0 maven/src/test/touchstone-build/maven.xml
Index: maven.xml
===
RCS file: /home/cvs/maven/src/test/touchstone-build/maven.xml,v
retrieving revision 1.43.4.18
retrieving revision 1.43.4.19
diff -u -r1.43.4.18 -r1.43.4.19
--- maven.xml 5 Jul 2004 21:01:49 - 1.43.4.18
+++ maven.xml 6 Jul 2004 12:27:20 - 1.43.4.19
@@ -858,6 +858,12 @@
maven.dist.tar.executable in dist plugin is not 'tar', is '${d}'
+
+
+
+ maven.javadoc.debug in javadoc plugin is not 'foo', is '${d}'
+
+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPCRUISECONTROL-7) Add support for
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPCRUISECONTROL-7 Here is an overview of the issue: - Key: MPCRUISECONTROL-7 Summary: Add support for Type: Improvement Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-cruisecontrol-plugin Assignee: Brett Porter Reporter: Paul Spencer Created: Tue, 6 Jul 2004 10:23 AM Updated: Tue, 6 Jul 2004 10:23 AM Environment: maven 1.0-rc4, maven-cruisecontrol-plugin-1.3, CruiseControl 2.1.6 Description: CruiseControl will build a project if another project successfully builds. This is controlled by the tag in cruisecontrol.xml. This functionality allows a project to be build when one of it's depend jars is built, even though the project has not changed. Suggested implementation: 1) Add the property "maven.cruisecontrol.triggerProjects". This property contains a list of cruisecontrol projects that will trigger the current project to build. 2) In cruisecontrol.jsl, generate a tag for each item in the property list. Example: maven.cruisecontrol.triggerProjects=proj_a, proj_b output file cruisecontrol.xml: ... ... .. .. .. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-156) add simple-jndi-0.9 to ibiblio
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Tue, 6 Jul 2004 8:31 AM OSJava already has a sync set up with ibiblio. Ask someone to put this version of simple-jndi in the OSJava repository if it already isn't there. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-156 Here is an overview of the issue: - Key: MAVENUPLOAD-156 Summary: add simple-jndi-0.9 to ibiblio Type: Task Status: Closed Resolution: WON'T FIX Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Mark Proctor Created: Sun, 4 Jul 2004 4:46 PM Updated: Tue, 6 Jul 2004 8:31 AM Description: simple-jndi-0.9 - 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: (MAVENUPLOAD-155) upload dom4j 1.5 RC1 to ibiblio
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Tue, 6 Jul 2004 8:35 AM Uploaded - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-155 Here is an overview of the issue: - Key: MAVENUPLOAD-155 Summary: upload dom4j 1.5 RC1 to ibiblio Type: Task Status: Closed Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Maarten Coene Created: Sun, 4 Jul 2004 4:19 PM Updated: Tue, 6 Jul 2004 8:35 AM Description: thanks Maarten - 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 MavenUtils.java
brett 2004/07/06 05:23:41 Modified:src/java/org/apache/maven Tag: MAVEN-1_0-BRANCH MavenUtils.java Log: PR: MAVEN-1296 Submitted by: Eric Lapierre Reviewed by: Brett Porter fix for property inheritence in some circumstances Revision ChangesPath No revision No revision 1.107.4.22 +3 -5 maven/src/java/org/apache/maven/MavenUtils.java Index: MavenUtils.java === RCS file: /home/cvs/maven/src/java/org/apache/maven/MavenUtils.java,v retrieving revision 1.107.4.21 retrieving revision 1.107.4.22 diff -u -r1.107.4.21 -r1.107.4.22 --- MavenUtils.java 26 Jun 2004 14:52:05 - 1.107.4.21 +++ MavenUtils.java 6 Jul 2004 12:23:41 - 1.107.4.22 @@ -236,10 +236,8 @@ context.setParent( parent.getContext() ); } -Properties properties = loadProjectBuildProperties( parentPom.getParentFile() ); -integrateMapInContext( properties, context ); -properties = loadProjectProperties( parentPom.getParentFile() ); -integrateMapInContext( properties, context ); +// Map in the parent context which already has the properties loaded +integrateMapInContext( parent.getContext().getVariables(), context ); project.mergeParent( parent ); } - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-157) add commons-convert-0.1-bundle.jar to ibiblio
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Tue, 6 Jul 2004 8:29 AM Ask a commons person to sync this via the apache repository. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-157 Here is an overview of the issue: - Key: MAVENUPLOAD-157 Summary: add commons-convert-0.1-bundle.jar to ibiblio Type: Task Status: Closed Resolution: WON'T FIX Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Mark Proctor Created: Sun, 4 Jul 2004 4:48 PM Updated: Tue, 6 Jul 2004 8:29 AM Description: http://www.markproctor.com/commons-convert-0.1-bundle.jar Needed for simple-jndi - 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-1312) downloading artifacts doesn't provide feedback
Message: The following issue has been closed. Resolver: Brett Porter Date: Tue, 6 Jul 2004 8:35 AM I had planned this anyway since I added content-length handling and changed the type last time and it broke the bootstrap mechnism as it didn't like \r. I had a look at this patch and its basically the same idea, although the patch contains a lot of unrelated fixes, commented out additional debug statements, and so on. I've just stuck with what I was working on. - View the issue: http://jira.codehaus.org/browse/MAVEN-1312 Here is an overview of the issue: - Key: MAVEN-1312 Summary: downloading artifacts doesn't provide feedback Type: Improvement Status: Closed Priority: Minor Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Fix Fors: 1.0 Versions: 1.0-rc3 Assignee: Brett Porter Reporter: Jerome Lacoste Created: Sun, 6 Jun 2004 3:04 PM Updated: Tue, 6 Jul 2004 8:35 AM Description: I am using a modem these days, and it is particularly frustrating to see maven downloading files without knowing more about the time it will take. We should then provide a way for HttpUtils to give more feedback. In the future, maven might get integrated into IDEs. The design of the feature should also allow for easy integration with nice graphical frontends. - 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: (MAVENUPLOAD-154) Java 3D core utils library
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Tue, 6 Jul 2004 8:36 AM Uploaded - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-154 Here is an overview of the issue: - Key: MAVENUPLOAD-154 Summary: Java 3D core utils library Type: Wish Status: Closed Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Omair-Inam Abdul-Matin Created: Wed, 30 Jun 2004 4:52 PM Updated: Tue, 6 Jul 2004 8:36 AM 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] Closed: (MAVENUPLOAD-153) Java 3D vector math library
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Tue, 6 Jul 2004 8:38 AM Uploaded - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-153 Here is an overview of the issue: - Key: MAVENUPLOAD-153 Summary: Java 3D vector math library Type: Wish Status: Closed Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Omair-Inam Abdul-Matin Created: Wed, 30 Jun 2004 4:52 PM Updated: Tue, 6 Jul 2004 8:38 AM 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] Closed: (MAVEN-1296) Multiproject property inheritance
Message: The following issue has been closed. Resolver: Brett Porter Date: Tue, 6 Jul 2004 8:23 AM applied - thanks. No idea why I didn't do it that way in the first place :) - View the issue: http://jira.codehaus.org/browse/MAVEN-1296 Here is an overview of the issue: - Key: MAVEN-1296 Summary: Multiproject property inheritance Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Fix Fors: 1.0 Versions: 1.0-rc3 Assignee: Brett Porter Reporter: Winston Rast Created: Thu, 27 May 2004 11:10 AM Updated: Tue, 6 Jul 2004 8:23 AM Description: I'm trying to generate "1.4 friendly" compiled classes. I'm getting failures on the assert keyword. Here's a rundown of my multiproject structure: root/ project.xml (extends root/service/project.xml) project.ent common/ maven/ project.properties project.xml (Parent) entities/ versions.ent dependencies.ent developers.ent service/ maven.xml project.properties project.xml (extends root/common/maven/project.xml) ejb/ project.ent project.properties project.xml (extends root/project.xml) I have the maven.compile.source and maven.compile.target properties set in root/service/project.properties. Yet when I run "maven multiproject:install" from my root directory I get a warning and error regarding the assert keyword. If I put these properties in a root/project.properties file it works fine. Can anyone tell me if this is a bug or if I'm doing something wrong? -- Just to follow up with some more info that I discovered... I created a root/maven.xml to echo the maven.compile.* properties during the build. Somewhere along the way my property values are being lost: build: [echo] maven.compile.source=1.4 [echo] maven.compile.target=1.4 multiproject:install: multiproject:projects-init: [echo] Gathering project list Starting the reactor... xdoclet:ejbdoclet: java:prepare-filesystem: java:compile: [echo] maven.compile.source=1.3 [echo] maven.compile.target=1.1 So is the problem in the property inheritance, the java plugin, or the multiproject plugin? Your help is greatly appreciated. --- I've been doing a lot of trial and error with this problem and I've narrowed it down to what I think is a problem in multiproject environments with inherited properties. It is *not* an issue strictly with the maven.compile.* properties as I've previously mentioned. I'm attaching a jar file of my stripped down example to demonstrate. In my example, I'm demonstrating the problem with the maven.repo.remote property. To replicate the problem, do the following: * Edit project.properties under test/ and change maven.repo.remote to something other than ibiblio. * Edit test/service/myservice/ejb/project.xml with a dependency (something NOT on ibiblio, but on the remote repo specified previously) * Remove this dependent jar from your local repository so it's forced to download it again * From test/service/myservice, execute a maven goal (I generally do clean) This should fail to download. Strangely, if I run the same maven goal from test/service/myservice/ejb, it DOES download! Anyone have a clue what's happening 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] Closed: (MPMULTIPROJECT-32) Multiproject and properties inheritance issue
Message: The following issue has been closed. Resolver: Brett Porter Date: Tue, 6 Jul 2004 8:25 AM test case succeeds with fix for MAVEN-1296 - View the issue: http://jira.codehaus.org/browse/MPMULTIPROJECT-32 Here is an overview of the issue: - Key: MPMULTIPROJECT-32 Summary: Multiproject and properties inheritance issue Type: Bug Status: Closed Priority: Major Resolution: DUPLICATE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-multiproject-plugin Versions: 1.3 Assignee: Brett Porter Reporter: Carlos Sanchez Created: Wed, 2 Jun 2004 7:09 PM Updated: Tue, 6 Jul 2004 8:25 AM Environment: Maven 1.0-rc3 WinXP Description: I have some projects common/all common/model extends common/all common/webapp extends common/model party/model extends common/model party/webapp extends common/webapp doc extends common/all Some properties are set in a project.properties file in common/all (for example maven.test.skip=true). When calling multiproject from the "doc" subproject (which calls all projects), properties defined in "common/all" are not available to the party/model and party/webapp If I define the properties in the "doc" project.properties everything seems ok. If I run multiproject from common/all everything also seems ok. - 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: (MPPLUGIN-20) If artifactId, groupId or version are not present for plugin:download, prompt for them
The following comment has been added to this issue: Author: dion gillard Created: Tue, 6 Jul 2004 10:17 AM Body: Have started work on this - View this comment: http://jira.codehaus.org/browse/MPPLUGIN-20?page=comments#action_21428 - View the issue: http://jira.codehaus.org/browse/MPPLUGIN-20 Here is an overview of the issue: - Key: MPPLUGIN-20 Summary: If artifactId, groupId or version are not present for plugin:download, prompt for them Type: Improvement Status: Open Priority: Trivial Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-plugin-plugin Assignee: dion gillard Reporter: dion gillard Created: Tue, 29 Jun 2004 6:47 AM Updated: Tue, 6 Jul 2004 10:17 AM 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] Commented: (MPXDOC-80) Support global theme
The following comment has been added to this issue:
Author: Brett Porter
Created: Tue, 6 Jul 2004 10:03 AM
Body:
does this assume that you are using a custom site.jsl? There isn't any hook into the
default site.jsl.
-
View this comment:
http://jira.codehaus.org/browse/MPXDOC-80?page=comments#action_21427
-
View the issue:
http://jira.codehaus.org/browse/MPXDOC-80
Here is an overview of the issue:
-
Key: MPXDOC-80
Summary: Support global theme
Type: Improvement
Status: Open
Priority: Major
Original Estimate: 10 minutes
Time Spent: Unknown
Remaining: 10 minutes
Project: maven-xdoc-plugin
Assignee: Brett Porter
Reporter: Joerg Schaible
Created: Tue, 17 Feb 2004 8:18 AM
Updated: Tue, 6 Jul 2004 10:03 AM
Description:
While it is possible to set an URL for an own theme using the new property
maven.xdoc.theme.url, you cannot tell the xdoc plugin which local file you are using.
The current approach enforces every project to have its own copy of the theme. This is
extremly nasty in combination with multiproject.
Proposal: Support a new property maven.xdoc.theme.file, that defines the local
location of the theme file. This file is copied into the ${maven.docs.dest}/style
directory.
Please have a look at jakarta-commons, they suffer from this problem also:
http://www.mail-archive.com/commons-dev%40jakarta.apache.org/index.html#35557
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/abbot project.xml
vmassol 2004/07/06 06:53:07 Modified:abbotproject.xml Log: - extend parent-plugin's project.xml - removed the report section as we wish to use the default reports - changed Christian's email address as he's now an Octo employee :-) Revision ChangesPath 1.6 +3 -12 maven-plugins/abbot/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/abbot/project.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- project.xml 25 Jun 2004 15:24:27 - 1.5 +++ project.xml 6 Jul 2004 13:53:07 - 1.6 @@ -19,7 +19,7 @@ --> - ../project.xml + ../plugin-parent/project.xml 3 maven-abbot-plugin Maven Abbot plugin @@ -44,8 +44,8 @@ Christian Blavier cblavier - [EMAIL PROTECTED] - BNP Paribas + [EMAIL PROTECTED] + Octo Technology Creator Java Developer @@ -161,13 +161,4 @@ - -maven-changes-plugin -maven-changelog-plugin -maven-file-activity-plugin -maven-developer-activity-plugin -maven-file-activity-plugin -maven-license-plugin -maven-linkcheck-plugin - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
plugin:setup/plugin:remove to replace plugin:install/plugin:uninstall
I propose that we rename (And deprecate the old) plugin:install/uninstall to plugin:setup and plugin:remove respectively. This would pave the way to later rename plugin:repository-* to just plugin:* and bring it in line with other artifact based plugins, and m2. plugin:install-now and plugin:uninstall-now should be removed and become implicit in the installation process (these goals install into the executing Maven) Additionally, a mode parameter should be introduced that installs to either "global", or "user". Global is maven.plugin.dir - ie the maven installation, use is maven.plugin.user.dir - ie ~/.maven/plugins Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven 1.0 prep
Hi all, I'd like to start preparing a release for Maven 1.0, so all the plugin maintainers out there - please vote and pump out a release asap if you want a new one bundled. I'll do so tomorrow for the stuff I've touched recently where it is needed, but with the mailing lists all dead at the moment, there's no need to hurry :) I'd like to have a final preview release ready for the weekend so people here can take it for a spin and sanity check it. Then set it wild next week and I'll go away on holidays and let someone else clean up the mess ;) As far as I'm concerned, there are no outstanding issues other than documentation that I intend to target for 1.0. Please let me know if you disagree. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/artifact/xdocs changes.xml properties.xml protocols.xml
brett 2004/07/06 06:42:25
Modified:artifact/src/main/org/apache/maven/artifact/deployer
RepositoryInfoBuilder.java
artifact/src/main/org/apache/maven/deploy DeployTool.java
RepositoryInfo.java
artifact/xdocs changes.xml properties.xml protocols.xml
Log:
PR: MPARTIFACT-22
add scpexe protocol - uses external scp executable
Revision ChangesPath
1.7 +22 -1
maven-plugins/artifact/src/main/org/apache/maven/artifact/deployer/RepositoryInfoBuilder.java
Index: RepositoryInfoBuilder.java
===
RCS file:
/home/cvs/maven-plugins/artifact/src/main/org/apache/maven/artifact/deployer/RepositoryInfoBuilder.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- RepositoryInfoBuilder.java25 Jun 2004 18:50:38 - 1.6
+++ RepositoryInfoBuilder.java6 Jul 2004 13:42:25 - 1.7
@@ -94,6 +94,23 @@
String proxyPort = (String) project.getContext().getProxyPort();
+String scpExe = (String) project.getContext().getVariable("maven.repo." +
repository + ".scp.executable");
+if (scpExe == null) {
+scpExe = (String)
project.getContext().getVariable("maven.scp.executable");
+}
+String scpArgs = (String) project.getContext().getVariable("maven.repo." +
repository + ".scp.args");
+if (scpArgs == null) {
+ scpArgs = (String) project.getContext().getVariable("maven.scp.args");
+}
+String sshExe = (String) project.getContext().getVariable("maven.repo." +
repository + ".ssh.executable");
+if (sshExe == null) {
+ sshExe = (String)
project.getContext().getVariable("maven.ssh.executable");
+}
+String sshArgs = (String) project.getContext().getVariable("maven.repo." +
repository + ".ssh.args");
+if (sshArgs == null) {
+ sshArgs = (String) project.getContext().getVariable("maven.ssh.args");
+}
+
if (username == null) {
username = (String) project.getContext().getVariable("maven.username");
}
@@ -107,6 +124,10 @@
repoInfo.setProxyHost(proxyHost);
repoInfo.setProxyUserName(proxyUser);
repoInfo.setProxyPassword(proxyPassword);
+repoInfo.setScpExe(scpExe);
+repoInfo.setScpArgs(scpArgs);
+repoInfo.setSshExe(sshExe);
+repoInfo.setSshArgs(sshArgs);
if (passiveModeOn != null)
{
if ("false".equalsIgnoreCase(passiveModeOn))
1.13 +6 -1
maven-plugins/artifact/src/main/org/apache/maven/deploy/DeployTool.java
Index: DeployTool.java
===
RCS file:
/home/cvs/maven-plugins/artifact/src/main/org/apache/maven/deploy/DeployTool.java,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- DeployTool.java 25 Jun 2004 13:50:05 - 1.12
+++ DeployTool.java 6 Jul 2004 13:42:25 - 1.13
@@ -29,6 +29,7 @@
import org.apache.maven.deploy.deployers.HttpDeployer;
import org.apache.maven.deploy.deployers.SFtpDeployer;
import org.apache.maven.deploy.deployers.ScpDeployer;
+import org.apache.maven.deploy.deployers.ScpExeDeployer;
import org.apache.maven.deploy.exceptions.AuthenticationException;
import org.apache.maven.deploy.exceptions.TransferFailedException;
import org.apache.maven.deploy.exceptions.UnsupportedProtocolException;
@@ -87,6 +88,10 @@
if (url.startsWith(ExternalDeployer.PROTOCOL))
{
deployer = new ExternalDeployer();
+}
+if (url.startsWith(ScpExeDeployer.PROTOCOL))
+{
+ deployer = new ScpExeDeployer();
}
if (deployer == null)
{
1.6 +31 -1
maven-plugins/artifact/src/main/org/apache/maven/deploy/RepositoryInfo.java
Index: RepositoryInfo.java
===
RCS file:
/home/cvs/maven-plugins/artifact/src/main/org/apache/maven/deploy/RepositoryInfo.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- RepositoryInfo.java 25 Jun 2004 18:50:38 - 1.5
+++ RepositoryInfo.java 6 Jul 2004 13:42:25 - 1.6
@@ -82,6 +82,12 @@
/** compress */
private boolean compress;
+/** parms for ScpExeDeployer */
+private String sshExe;
+private String sshArgs;
+private String scpExe;
+private String scpArgs;
+
/**
* @param compress
*/
@@ -383,4 +389,28 @@
this.passiveModeOn = passiveModeOn;
}
+ public String getScpArgs() {
+ return scpAr
cvs commit: maven-plugins/artifact/src/main/org/apache/maven/deploy/deployers ScpExeDeployer.java
brett 2004/07/06 07:42:49
Added: artifact/src/main/org/apache/maven/deploy/deployers
ScpExeDeployer.java
Log:
PR: MPARTIFACT-22
Revision ChangesPath
1.1
maven-plugins/artifact/src/main/org/apache/maven/deploy/deployers/ScpExeDeployer.java
Index: ScpExeDeployer.java
===
package org.apache.maven.deploy.deployers;
/*
* Copyright 2001-2004 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*
*/
import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStream;
import java.io.InputStreamReader;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import org.apache.maven.deploy.DeployRequest;
import org.apache.maven.deploy.RepositoryInfo;
import org.apache.maven.deploy.exceptions.AuthenticationException;
import org.apache.maven.deploy.exceptions.TransferFailedException;
/**
* SCP deployer using "external" scp program. To allow for
* ssh-agent type behavior. Also provides backwards compatible
* support for those using the
* maven.scp.executable/maven.scp.args
* and maven.ssh.executable/maven.ssh.args
*
*
*/
public class ScpExeDeployer extends AbstractDeployer
{
public final static String PROTOCOL = "scpexe://";
private RepositoryInfo repositoryInfo = null;
private String cmd = null;
private static final Log LOG = LogFactory.getLog(ScpExeDeployer.class);
/* (non-Javadoc)
* @see
org.apache.maven.deploy.deployers.Deployer#init(org.apache.maven.deploy.HostInfo)
*/
public void init(RepositoryInfo repoInfo) throws AuthenticationException
{
repositoryInfo = repoInfo;
}
private RepositoryInfo getRepositoryInfo() {
return repositoryInfo;
}
/**
* @see org.apache.maven.deploy.deployers.Deployer#release()
*/
public void release()
{
}
/**
* @see
org.apache.maven.deploy.deployers.Deployer#deploy(org.apache.maven.deploy.DeployRequest)
*/
public void deploy(DeployRequest request) throws TransferFailedException
{
String mkdirCmd =
"mkdir -p "
+ getRepositoryInfo().getBasedir()
+ "/"
+ request.dirname()
+ "\n";
executeSimpleCommand(mkdirCmd);
doCopy(request);
if (getRepositoryInfo().getGroup() != null)
{
String chgrpCmd =
"chgrp "
+ getRepositoryInfo().getGroup()
+ " "
+ getRepositoryInfo().getBasedir()
+ "/"
+ request.getDestFile()
+ "\n";
executeSimpleCommand(chgrpCmd);
}
}
private String arrayToString(String[] array) {
StringBuffer sb = new StringBuffer();
for (int i=0; i 0) {
// If an old SNAPSHOT exists, remove it
executeSimpleCommand("rm -r " + destFile);
}
String[] scpCmd = { getRepositoryInfo().getScpExe(),
args,
srcFile,
dest };
try {
if (LOG.isDebugEnabled()) {
LOG.debug("Executing command: " +
arrayToString(scpCmd));
}
Process p = Runtime.getRuntime().exec(scpCmd);
// any error message?
StreamGobbler errorGobbler = new StreamGobbler(p.getErrorStream(),
"ERROR");
// any output?
StreamGobbler outputGobbler = new
StreamGobbler(p.getInputStream(), "OUTPUT");
// kick them off
errorGobbler.start();
outputGobbler.start();
p.waitFor();
} catch (IOException e) {
LOG.error("Error executing command: " + cmd);
t
plugin dependencies
Hi, After dIon prompted me to take a look yesterday afternoon I figured a way to load the plugin contexts on the fly without messing up the order of things, so maven:get/maven:set (and their legacy versions pluginVar and getPluginContext) now initialise a plugin if it is not already initialised. This means that all of the following are valid ways of introducing a plugin, and work together: - using a dynamic tag library from it - using a goal from it - using maven:get/maven:set The odd behaviour of
cvs commit: maven/src/bin maven maven.bat
brett 2004/07/06 07:29:46
Modified:src/bin Tag: MAVEN-1_0-BRANCH maven maven.bat
Log:
PR: MAVEN-1354
remove the user.home.env property from startup
Revision ChangesPath
No revision
No revision
1.31.4.7 +0 -1 maven/src/bin/maven
Index: maven
===
RCS file: /home/cvs/maven/src/bin/maven,v
retrieving revision 1.31.4.6
retrieving revision 1.31.4.7
diff -u -r1.31.4.6 -r1.31.4.7
--- maven 14 Jun 2004 12:36:48 - 1.31.4.6
+++ maven 6 Jul 2004 14:29:46 - 1.31.4.7
@@ -155,6 +155,5 @@
"-Dforehead.conf.file=${MAVEN_HOME}/bin/forehead.conf" \
"-Dtools.jar=$TOOLS_JAR" \
"-Dmaven.home=${MAVEN_HOME}" \
- "-Duser.home.env=${HOME}" \
$MAIN_CLASS "$@"
1.38.4.6 +4 -4 maven/src/bin/maven.bat
Index: maven.bat
===
RCS file: /home/cvs/maven/src/bin/maven.bat,v
retrieving revision 1.38.4.5
retrieving revision 1.38.4.6
diff -u -r1.38.4.5 -r1.38.4.6
--- maven.bat 14 Jun 2004 12:36:48 - 1.38.4.5
+++ maven.bat 6 Jul 2004 14:29:46 - 1.38.4.6
@@ -123,14 +123,14 @@
if not "%MAVEN_HOME_LOCAL%" == "" goto StartMHL
@REM Start MAVEN without MAVEN_HOME_LOCAL override
-%MAVEN_JAVA_EXE%
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
"-Duser.home.env=%HOME%" "-Dmaven.home=%MAVEN_HOME%"
"-Dtools.jar=%JAVA_HOME%\lib\tools.jar"
"-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf"
-Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH%
%MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS%
[EMAIL PROTECTED] %MAVEN_JAVA_EXE%
-Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
"-Duser.home.env=%HOME%" "-Dmaven.home=%MAVEN_HOME%"
"-Dtools.jar=%JAVA_HOME%\lib\tools.jar"
"-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf"
-Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH%
%MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS%
+%MAVEN_JAVA_EXE%
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
"-Dmaven.home=%MAVEN_HOME%" "-Dtools.jar=%JAVA_HOME%\lib\tools.jar"
"-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf"
-Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH%
%MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS%
[EMAIL PROTECTED] %MAVEN_JAVA_EXE%
-Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
"-Dmaven.home=%MAVEN_HOME%" "-Dtools.jar=%JAVA_HOME%\lib\tools.jar"
"-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf"
-Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH%
%MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS%
goto :end
@REM Start MAVEN with MAVEN_HOME_LOCAL override
:StartMHL
-%MAVEN_JAVA_EXE%
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
"-Duser.home.env=%HOME%" "-Dmaven.home=%MAVEN_HOME%"
"-Dmaven.home.local=%MAVEN_HOME_LOCAL%" "-Dtools.jar=%JAVA_HOME%\lib\tools.jar"
"-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf"
-Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH%
%MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS%
[EMAIL PROTECTED] %MAVEN_JAVA_EXE%
-Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
"-Duser.home.env=%HOME%" "-Dmaven.home=%MAVEN_HOME%"
"-Dmaven.home.local=%MAVEN_HOME_LOCAL%" "-Dtools.jar=%JAVA_HOME%\lib\tools.jar"
"-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf"
-Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH%
%MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS%
+%MAVEN_JAVA_EXE%
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
"-Dmaven.home=%MAVEN_HOME%" "-Dmaven.home.local=%MAVEN_HOME_LOCAL%"
"-Dtools.jar=%JAVA_HOME%\lib\tools.jar"
"-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf"
-Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH%
%MAVEN_MAIN_C
cvs commit: maven-plugins/artifact/xdocs changes.xml
brett 2004/07/06 07:29:30 Modified:artifact/src/main/org/apache/maven/deploy/deployers ScpDeployer.java artifact/xdocs changes.xml Log: PR: MPARTIFACT-23 add -o option to unzip Revision ChangesPath 1.12 +2 -2 maven-plugins/artifact/src/main/org/apache/maven/deploy/deployers/ScpDeployer.java Index: ScpDeployer.java === RCS file: /home/cvs/maven-plugins/artifact/src/main/org/apache/maven/deploy/deployers/ScpDeployer.java,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- ScpDeployer.java 25 Jun 2004 13:50:05 - 1.11 +++ ScpDeployer.java 6 Jul 2004 14:29:30 - 1.12 @@ -196,7 +196,7 @@ doCopy(session, request); String unzipCmd = -"unzip -u " +"unzip -uo " + getRepositoryInfo().getBasedir() + "/" + request.getDestFile() 1.28 +1 -0 maven-plugins/artifact/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/artifact/xdocs/changes.xml,v retrieving revision 1.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- changes.xml 6 Jul 2004 13:42:25 - 1.27 +++ changes.xml 6 Jul 2004 14:29:30 - 1.28 @@ -26,6 +26,7 @@ + Add overwrite option to unzip - necessary to run in batch mode Add an scp executable deployer Deprecated the artifact:load hook goal Allow use of distributionSite POM attribute in artifact method - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/xdocs changes.xml
brett 2004/07/06 05:45:48 Modified:.Tag: MAVEN-1_0-BRANCH build-bootstrap.xml src/bootstrap/org/apache/maven Tag: MAVEN-1_0-BRANCH BootstrapTask.java src/java/org/apache/maven Tag: MAVEN-1_0-BRANCH MavenConstants.java src/java/org/apache/maven/util Tag: MAVEN-1_0-BRANCH HttpUtils.java src/java/org/apache/maven/verifier Tag: MAVEN-1_0-BRANCH DependencyVerifier.java xdocsTag: MAVEN-1_0-BRANCH changes.xml Added: src/java/org/apache/maven/util Tag: MAVEN-1_0-BRANCH BootstrapDownloadMeter.java ConsoleDownloadMeter.java DownloadMeter.java SilentDownloadMeter.java Log: different download progress monitors (particularly for bootstrap compatibility) Revision ChangesPath No revision No revision 1.212.2.16 +6 -2 maven/build-bootstrap.xml Index: build-bootstrap.xml === RCS file: /home/cvs/maven/build-bootstrap.xml,v retrieving revision 1.212.2.15 retrieving revision 1.212.2.16 diff -u -r1.212.2.15 -r1.212.2.16 --- build-bootstrap.xml 2 Jul 2004 09:52:48 - 1.212.2.15 +++ build-bootstrap.xml 6 Jul 2004 12:45:47 - 1.212.2.16 @@ -69,7 +69,7 @@ - + | @@ -260,6 +260,7 @@ failonerror="true"> + @@ -285,6 +286,7 @@ failonerror="true"> + @@ -300,6 +302,7 @@ + @@ -346,7 +349,7 @@ - + @@ -365,6 +368,7 @@ optimize="off" classpathref="bootstrap.libs"> + No revision No revision 1.20.2.6 +2 -1 maven/src/bootstrap/org/apache/maven/BootstrapTask.java Index: BootstrapTask.java === RCS file: /home/cvs/maven/src/bootstrap/org/apache/maven/BootstrapTask.java,v retrieving revision 1.20.2.5 retrieving revision 1.20.2.6 diff -u -r1.20.2.5 -r1.20.2.6 --- BootstrapTask.java27 Jun 2004 07:57:48 - 1.20.2.5 +++ BootstrapTask.java6 Jul 2004 12:45:48 - 1.20.2.6 @@ -26,6 +26,7 @@ import java.util.List; import org.apache.maven.util.HttpUtils; +import org.apache.maven.util.BootstrapDownloadMeter; import org.apache.tools.ant.BuildException; import org.apache.tools.ant.Project; import org.apache.tools.ant.Task; @@ -378,7 +379,7 @@ proxyHost, proxyPort, proxyUserName, - proxyPassword, loginHost, loginDomain ); + proxyPassword, loginHost, loginDomain, new BootstrapDownloadMeter() ); break; } catch ( Exception e ) No revision No revision 1.30.4.9 +4 -1 maven/src/java/org/apache/maven/MavenConstants.java Index: MavenConstants.java === RCS file: /home/cvs/maven/src/java/org/apache/maven/MavenConstants.java,v retrieving revision 1.30.4.8 retrieving revision 1.30.4.9 diff -u -r1.30.4.8 -r1.30.4.9 --- MavenConstants.java 28 Jun 2004 09:39:09 - 1.30.4.8 +++ MavenConstants.java 6 Jul 2004 12:45:48 - 1.30.4.9 @@ -76,6 +76,9 @@ /** Proxy loginDomain tag. */ public static final String PROXY_LOGINDOMAIN = "maven.proxy.ntlm.domain"; +/** Download meter type variable. */ +public static final String DOWNLOAD_METER = "maven.download.meter"; + /** Snapshot JAR signifier tag. */ public static final String SNAPSHOT_SIGNIFIER = "SNAPSHOT"; No revision No revision 1.28.4.14 +44 -21maven/src/java/org/apache/maven/util/HttpUtils.java Index: HttpUtils.java === RCS file: /home/cvs/maven/src/java/org/apache/maven/util/HttpUtils.java,v retrieving revision 1.28.4.13 retrieving revision 1.28.4.14 diff -u -r1.28.4.13 -r1.28.4.14 --- HttpUtils.java1 Jul 2004 14:22:52 - 1.28.4.13 +++ HttpUtils.java6 Jul 2004 12:45:48 - 1.28.4.14 @@ -68,6 +68,10 @@ /** @todo make it a property. */ private static final int RE
[jira] Created: (MAVEN-1359) maven.bat fails when %HOME% contains a back slash at the end
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1359 Here is an overview of the issue: - Key: MAVEN-1359 Summary: maven.bat fails when %HOME% contains a back slash at the end Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: cli Versions: 1.0-rc4 Assignee: Reporter: Kenichi Masuko Created: Tue, 6 Jul 2004 9:45 AM Updated: Tue, 6 Jul 2004 9:45 AM Environment: Windows XP, Windows 2000 Description: In maven.bat, java is launched with the following command: %MAVEN_JAVA_EXE% ... "-Duser.home.env=%HOME%" ... When the last character of the content of HOME is a back slash, maven failed to start. For example, when HOME is set to be d:\ "-Duser.home.env=%HOME%" becomes "-Duser.home.env=d:\" and Windows sees the character sequence \" at the end as a single character (an escape character + a special character) rather than a character followed by a quotation which ends a parameter. This breaks matching of quotation character pairs making the last pair consume all the characters after it. As a result, main java class name near the end of the line is concatenated to the content of the last pair, and java doesn't see the main class to run and exits. I first tried to change HOME to be d: rather than d:\ but Windows 2000/XP doesn't accept d: saying it is not a valid absolute path. So, if the last character of HOME is a back slash, I think we need to replace it with double back slashes like below. set HOME_ENV_PARAM_LEFT=%HOME:~0,-1% set HOME_ENV_PARAM_RIGHT=%HOME:~-1% set HOME_ENV_PARAM=%HOME_ENV_PARAM_LEFT%%HOME_ENV_PARAM_RIGHT:\=\\% %MAVEN_JAVA_EXE% ... "-Duser.home.env=%HOME_ENV_PARAM%" ... - 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: (MPARTIFACT-22) New ScpExeDeployer
Message: The following issue has been closed. Resolver: Brett Porter Date: Tue, 6 Jul 2004 9:42 AM applied - thanks. Please also attach docs to diff in future. - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-22 Here is an overview of the issue: - Key: MPARTIFACT-22 Summary: New ScpExeDeployer Type: Improvement Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-artifact-plugin Assignee: Brett Porter Reporter: Leif Nelson Created: Mon, 28 Jun 2004 4:54 PM Updated: Tue, 6 Jul 2004 9:42 AM Description: I have implemented an ScpExeDeployer plugin (like I said I would back in November!). When I upgraded to RC4, I saw that you were "serious" about getting rid of the old scp/ssh type of deployment. :-) Anyways, I really need to have the ssh-agent type of support in the deployment artifacts, so I implemented this plugin. It's backwards compatible with folks that supply the old maven.ssh.executable, maven.ssh.args, maven.scp.executable, maven.scp.args. I also made it look for these params in "server-specific" props like you do with the new stuff.. maven.repo.x.ssh.executable, maven.repo.x.ssh.args, maven.repo.x.scp.executable, maven.repo.x.scp.args. So, if someone wanted to deploy with different args, or different commands to different servers, the plugin would support that. This work was done in regards to this email thread.. http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=8065 Thanks much for consideration. :-) --Leif - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPARTIFACT-24) file permissions of artifacts after deployment with ftp
The following comment has been added to this issue: Author: Joerg Schaible Created: Tue, 6 Jul 2004 4:36 AM Body: SITE CHMOD 664 Supported by most ftp servers (at least Unix based). - View this comment: http://jira.codehaus.org/browse/MPARTIFACT-24?page=comments#action_21401 - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-24 Here is an overview of the issue: - Key: MPARTIFACT-24 Summary: file permissions of artifacts after deployment with ftp Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-artifact-plugin Versions: 1.1 Assignee: Brett Porter Reporter: Joerg Schaible Created: Mon, 5 Jul 2004 11:04 AM Updated: Tue, 6 Jul 2004 4:36 AM Description: After deploying artifacts with ftp, only the owner has by default write permissions. This is a major problem for snapshots, since they may be published from any team member. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPDIST-12) build-src goal use predefined src field, not sourceDirectory
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPDIST-12 Here is an overview of the issue: - Key: MPDIST-12 Summary: build-src goal use predefined src field, not sourceDirectory Type: Bug Status: Open Priority: Major Original Estimate: 3 hours Time Spent: Unknown Remaining: 3 hours Project: maven-dist-plugin Assignee: Jason van Zyl Reporter: Marcin S. Created: Tue, 6 Jul 2004 4:04 AM Updated: Tue, 6 Jul 2004 4:04 AM Environment: win2k SP4, java 1.4.2_04, maven 1.0-rc4 Description: When I run maven dist:build-src I get product-src.zip containing only build.xml, LICENSE.txt, project.properties and project.xml. No files from sourceDirectory is taken. If I move all contents of my sourceDirectory (Source/java) to src in project root directory everything is OK. I suppose that maven is always taking default location (src) and do not change it with value from /project/build/sourceDirectory. PS. Other actions like compiling, jar, javadoc are working perfect, so it should not be a problem with my project.xml and mavem.xml. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPANNOUNCEMENT-4) Cannot use plugin in project.xml's report element.
The following comment has been added to this issue:
Author: Vincent Massol
Created: Tue, 6 Jul 2004 3:19 AM
Body:
Yes, you're right. I'll need to introduce the concept of a template then because the
announcement plugin can now generate announcement files for all the releases of a
given project.
So we'll need something like:
maven.announcement.template =
${maven.gen.docs}/announcements/announcement-%VERSION%.txt
ok, I'll work on this when I have some time. In the meantime, don't worry I won't
remove the maven.announcement.file property :-)
Thanks
-
View this comment:
http://jira.codehaus.org/browse/MPANNOUNCEMENT-4?page=comments#action_21397
-
View the issue:
http://jira.codehaus.org/browse/MPANNOUNCEMENT-4
Here is an overview of the issue:
-
Key: MPANNOUNCEMENT-4
Summary: Cannot use plugin in project.xml's report element.
Type: New Feature
Status: Closed
Priority: Major
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-announcement-plugin
Fix Fors:
1.2
Versions:
1.1
Assignee: Vincent Massol
Reporter: Gary Gregory
Created: Tue, 22 Jun 2004 5:44 PM
Updated: Tue, 6 Jul 2004 3:19 AM
Environment: >maven -i
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc3
# BEGIN: Which report
Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)
java.version=1.4.2_04
file.encoding=Cp1252
java.ext.dirs=C:\java\sun\1.4.2_04\jre\lib\ext
java.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\forehead-1.0-beta-5.jar
os.name=Windows XP
java.vendor=Sun Microsystems Inc.
sun.boot.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\endorsed\xerces-2.4.0.jar;C:\Program Files\Apache Software
Foundation\Maven 1.
0-rc3\lib\endorsed\xml-apis-1.0.b2.jar;C:\java\sun\1.4.2_04\jre\lib\rt.jar;C:\java\sun\1.4.2_04\jre\lib\i18n.jar;C:\java\sun\1.4.2_04\jre\lib\sunrsasign.jar;C:\
java\sun\1.4.2_04\jre\lib\jsse.jar;C:\java\sun\1.4.2_04\jre\lib\jce.jar;C:\java\sun\1.4.2_04\jre\lib\charsets.jar;C:\java\sun\1.4.2_04\jre\classes
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
# END: Which report
Installed plugins:
maven-castor-plugin-1.2
maven-site-plugin-1.5
maven-multiproject-plugin-1.3
maven-jdepend-plugin-1.5
maven-clover-plugin-1.5
maven-genapp-plugin-2.2
maven-jbuilder-plugin-1.5
maven-jboss-plugin-1.5
maven-dashboard-plugin-1.3
maven-artifact-plugin-1.2
maven-developer-activity-plugin-1.5
maven-war-plugin-1.6
maven-native-plugin-1.1
maven-cruisecontrol-plugin-1.2
maven-webserver-plugin-2.0
maven-docbook-plugin-1.2
maven-deploy-plugin-1.3
maven-ear-plugin-1.5
maven-repository-plugin-1.2
maven-j2ee-plugin-1.5
maven-jnlp-plugin-1.3
maven-linkcheck-plugin-1.2
maven-javadoc-plugin-1.5
maven-vdoclet-plugin-1.2
maven-hibernate-plugin-1.1
maven-appserver-plugin-2.0
maven-antlr-plugin-1.2
maven-jira-plugin-1.1
maven-ant-plugin-1.7
maven-gump-plugin-1.3
maven-tasklist-plugin-2.3
maven-xdoc-plugin-1.7.1
maven-ashkelon-plugin-1.2
maven-tjdo-plugin-1.0.0
maven-html2xdoc-plugin-1.3
maven-announcement-plugin-1.1
maven-pmd-plugin-1.4
maven-jxr-plugin-1.4
maven-struts-plugin-1.3
maven-latka-plugin-1.4
maven-junit-doclet-plugin-1.2
maven-pom-plugin-1.4
maven-changelog-plugin-1.5
maven-clean-plugin-1.2
maven-license-plugin-1.2
maven-jetty-plugin-1.1
maven-jdee-plugin-1.1
maven-file-activity-plugin-1.5
maven-jcoverage-plugin-1.0.4
maven-jdiff-plugin-1.4
maven-jar-plugin-1.5
maven-scm-plugin-1.3
maven-aspectwerkz-plugin-1.2
maven-faq-plugin-1.3
maven-plugin-plugin-1.3
maven-dist-plugin-1.5
maven-jellydoc-plugin-1.3
maven-javacc-plugin-1.1
maven-shell-plugin-1.1
maven-simian-plugin-1.4
maven-ejb-plugin-1.4
maven-java-plugin-1.4
maven-console-plugin-1.1
maven-pdf-plugin-2.1
maven-release-plugin-1.3
maven-changes-plugin-1.4
maven-nsis-plugin-1.0
maven-checkstyle-plugin-2.4.1
maven-wizard-plugin-1.1
maven-uberjar-plugin-1.2
maven-caller-plugin-1.1
maven-junit-report-plugin-1.5
maven-eclipse-plugin-1.7
maven-latex-plugin-1.2
maven-jdeveloper-plugin-1.4
maven-aspectj-plugin-3.0
maven-idea-plugin-1.4
maven-jalopy-plugin-1.2
maven-test-plugin-1.6.1
maven-multichanges-plugin-1.1
Home Build properties: {jaxp.xslt.jar=C:/java/apache/xalan-2_5_D1//bin/xalan.jar,
servlet.jar=C:/java/sun/jwsdp-1.1/common/lib/servlet.jar, jaxp.jaxp.jar=C:/jav
a/apache/xalan-2_5_D1//bin/xml-apis.jar, junit.jar=C:/java/junit3.8.1/junit.jar}
Description:
Cannot use plugin in project.xml's report element.
I
[jira] Closed: (MPNSIS-3) Depend on dist goal
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MPNSIS-3 Here is an overview of the issue: - Key: MPNSIS-3 Summary: Depend on dist goal Type: Bug Status: Closed Priority: Minor Resolution: WON'T FIX Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-nsis-plugin Fix Fors: 1.1 Assignee: dion gillard Reporter: Geoffrey Created: Thu, 1 Jul 2004 2:51 PM Updated: Tue, 6 Jul 2004 2:59 AM Description: Run the goal clean, then the goal nsis: it won't work because you first need to run dist. Maybe nsis could depend on the dist 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]
