[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
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: (MAVENUPLOAD-158) xmlstubs 1.0.2 upload request
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-158 Here is an overview of the issue: - Key: MAVENUPLOAD-158 Summary: xmlstubs 1.0.2 upload request Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: nicolas de loof Created: Wed, 7 Jul 2004 3:05 AM Updated: Wed, 7 Jul 2004 3:05 AM Description: XmlStub is a simple tool to replace the model in an MVC webapp by an XML based model simulation. It is usefull to build a webapp when business layer is not ready for use or to test some special cases. It can also be used to make a demo of the web to the customer in a early development stage. - 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:setup/plugin:remove to replace plugin:install/plugin:u ninstall
-Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 06, 2004 2:33 PM To: Maven Developers List Subject: 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. +1 Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1260) please upload xmlstubs-1.0.1 on ibiblio
The following comment has been added to this issue: Author: nicolas de loof Created: Wed, 7 Jul 2004 3:17 AM Body: replaced by http://jira.codehaus.org/browse/MAVENUPLOAD-158 - View this comment: http://jira.codehaus.org/browse/MAVEN-1260?page=comments#action_21456 - 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: Wed, 7 Jul 2004 3:17 AM Description: please upload xmlstubs-1.0.1 on ibiblio groupIdazote/groupId artifactIdxmlstubs/artifactId version1.0.1/version 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]
[jira] Commented: (MAVENUPLOAD-158) xmlstubs 1.0.2 upload request
The following comment has been added to this issue: Author: nicolas de loof Created: Wed, 7 Jul 2004 3:20 AM Body: It seem's URL to bundle doesn't work. Please download 1.0.2-bundle on http://sourceforge.net/project/showfiles.php?group_id=95695package_id=116971release_id=251387 - View this comment: http://jira.codehaus.org/browse/MAVENUPLOAD-158?page=comments#action_21457 - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-158 Here is an overview of the issue: - Key: MAVENUPLOAD-158 Summary: xmlstubs 1.0.2 upload request Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: nicolas de loof Created: Wed, 7 Jul 2004 3:05 AM Updated: Wed, 7 Jul 2004 3:20 AM Description: XmlStub is a simple tool to replace the model in an MVC webapp by an XML based model simulation. It is usefull to build a webapp when business layer is not ready for use or to test some special cases. It can also be used to make a demo of the web to the customer in a early development stage. - 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: mercredi 7 juillet 2004 01:59 To: Maven Developers List Subject: 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. Sure! I will do this. Thanks again for your insight. -Vincent - 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 j:set working only before initialisation to push it 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] - 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: Wed, 7 Jul 2004 5:07 AM Body: Sure, but this already exists. It's called the changes report. IMO the goal of the announcement plugin is different. It is actually a RELEASE NOTE. And a release note is usually about the current version. Also, as it is generated for all versions you can always see the changes from your version and the previous version. I really think what you are talking about is a changes report and not a release note. The current release note is not too far from the changes report (with some additions like how to install a plugin, the description of the project, etc). However, in the future we plan to extend the information in there by adding for example the list of open bugs for that release, etc. - View this comment: http://jira.codehaus.org/browse/MPANNOUNCEMENT-4?page=comments#action_21463 - 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: Wed, 7 Jul 2004 5:07 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:
[jira] Created: (MAVEN-1361) Must remove the deploy plugin to use this version of the jar plugin
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1361 Here is an overview of the issue: - Key: MAVEN-1361 Summary: Must remove the deploy plugin to use this version of the jar plugin Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: jelly/ant integration Versions: 1.0-rc4 Assignee: Reporter: Andre Duursma Created: Wed, 7 Jul 2004 5:21 AM Updated: Wed, 7 Jul 2004 5:21 AM Environment: P:\solmaven --info __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc4 # BEGIN: Which report Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $) java.version=1.4.2 file.encoding=Cp1252 java.ext.dirs=C:\j2sdk1.4.2\jre\lib\ext java.class.path=C:\maven-1.0-rc4\lib\forehead-1.0-beta-5.jar os.name=Windows 2000 java.vendor=Sun Microsystems Inc. sun.boot.class.path=C:\maven-1.0-rc4\lib\endorsed\xerces-2.4.0.jar;C:\maven-1.0-rc4\lib\endorsed\xml-apis-1.0.b2.jar;C:\j2sdk1.4.2\jre\lib\rt.jar;C:\j2sdk1.4.2\jre\lib\i18n.jar;C:\j2sdk1.4.2\jre\lib\sunrsasign.jar;C:\j2sdk1.4.2\jre\lib\jsse.jar;C:\j2sdk1.4.2\jre\lib\jce.jar;C:\j2sdk1.4.2\jre\lib\cha rsets.jar;C:\j2sdk1.4.2\jre\classes java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition # END: Which report Installed plugins: maven-announcement-plugin-1.1 maven-ant-plugin-1.7 maven-antlr-plugin-1.2 maven-appserver-plugin-2.0 maven-artifact-plugin-1.3 maven-ashkelon-plugin-1.2 maven-aspectj-plugin-3.1 maven-aspectwerkz-plugin-1.2 maven-caller-plugin-1.1 maven-castor-plugin-1.2 maven-changelog-plugin-1.6 maven-changes-plugin-1.4 maven-checkstyle-plugin-2.4.1 maven-clean-plugin-1.3 maven-clover-plugin-1.5 maven-console-plugin-1.1 maven-cruisecontrol-plugin-1.3 maven-dashboard-plugin-1.3 maven-deploy-plugin-1.3 maven-developer-activity-plugin-1.5 maven-dist-plugin-1.6 maven-docbook-plugin-1.2 maven-ear-plugin-1.5 maven-eclipse-plugin-1.7 maven-ejb-plugin-1.4 maven-faq-plugin-1.4 maven-file-activity-plugin-1.5 maven-genapp-plugin-2.2 maven-gump-plugin-1.3 maven-hibernate-plugin-1.1 maven-html2xdoc-plugin-1.3 maven-idea-plugin-1.5 maven-j2ee-plugin-1.5 maven-jalopy-plugin-1.2 maven-jar-plugin-1.6 maven-java-plugin-1.4 maven-javacc-plugin-1.1 maven-javadoc-plugin-1.5 maven-javancss-plugin-1.2 maven-jboss-plugin-1.5 maven-jbuilder-plugin-1.5 maven-jcoverage-plugin-1.0.5 maven-jdee-plugin-1.1 maven-jdepend-plugin-1.5 maven-jdeveloper-plugin-1.4 maven-jdiff-plugin-1.4 maven-jellydoc-plugin-1.3 maven-jetty-plugin-1.1 maven-jira-plugin-1.1 maven-jnlp-plugin-1.3 maven-junit-doclet-plugin-1.2 maven-junit-report-plugin-1.5 maven-jxr-plugin-1.4 maven-latex-plugin-1.2 maven-latka-plugin-1.4 maven-license-plugin-1.2 maven-linkcheck-plugin-1.3.1 maven-multichanges-plugin-1.1 maven-multiproject-plugin-1.3.1 maven-native-plugin-1.1 maven-nsis-plugin-1.0 maven-pdf-plugin-2.1 maven-plugin-plugin-1.5 maven-pmd-plugin-1.5 maven-pom-plugin-1.4.1 maven-rar-plugin-1.0 maven-release-plugin-1.4 maven-repository-plugin-1.2 maven-scm-plugin-1.4 maven-shell-plugin-1.1 maven-simian-plugin-1.4 maven-site-plugin-1.5 maven-struts-plugin-1.3 maven-tasklist-plugin-2.3 maven-test-plugin-1.6.2 maven-tjdo-plugin-1.0.0 maven-uberjar-plugin-1.2 maven-vdoclet-plugin-1.2 maven-war-plugin-1.6 maven-webserver-plugin-2.0 maven-wizard-plugin-1.1 maven-xdoc-plugin-1.7.2 Description: P:\solmaven -e dist __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc4 File.. C:\WINNT\Profiles\Duursma1\.maven\cache\maven-jar-plugin-1.6\plugin.jelly Element... ant:fail Line.. 43 Column 17 Must remove the deploy plugin to use this version of the jar plugin. Please delete maven-deploy-plugin-1.3.jar from C:\maven-1.0-rc4/plugins and C:\WINNT\Profiles\Duursma1/.maven/plugins (if it exists) org.apache.commons.jelly.JellyTagException: C:\WINNT\Profiles\Duursma1\.maven\cache\maven-jar-plugin-1.6\plugin.jelly:43:17: ant:fail Must remove the deploy plugin to use this version of the jar plugin. Please delete maven-deploy-plugin-1.3.jar from C:\maven-1.0-rc4/plugins and C:\WINNT\Profiles\Duursma1/.maven/plugins (if it exists) at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:683) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:288) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at
cvs commit: maven-plugins/javadoc plugin.jelly
brett 2004/07/07 03:00:16
Modified:javadoc plugin.jelly
Log:
remove unneeded property declarations
Revision ChangesPath
1.46 +0 -27 maven-plugins/javadoc/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/javadoc/plugin.jelly,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- plugin.jelly 6 Jul 2004 12:37:18 - 1.45
+++ plugin.jelly 7 Jul 2004 10:00:15 - 1.46
@@ -33,33 +33,6 @@
!-- == --
goal name=javadoc:init prereqs=xdoc:init
-!-- FIXME: none of this is required --
-!-- javadoc plugin properties --
-maven:get var=maven.javadoc.additionalparam plugin=maven-javadoc-plugin
property=maven.javadoc.additionalparam/
-maven:get var=maven.javadoc.author plugin=maven-javadoc-plugin
property=maven.javadoc.author/
-maven:get var=maven.javadoc.customtags plugin=maven-javadoc-plugin
property=maven.javadoc.customtags/
-maven:get var=maven.javadoc.debugplugin=maven-javadoc-plugin
property=maven.javadoc.debug/
-maven:get var=maven.javadoc.destdir plugin=maven-javadoc-plugin
property=maven.javadoc.destdir/
-maven:get var=maven.javadoc.doclet plugin=maven-javadoc-plugin
property=maven.javadoc.doclet/
-maven:get var=maven.javadoc.docletpath plugin=maven-javadoc-plugin
property=maven.javadoc.docletpath/
-maven:get var=maven.javadoc.linksplugin=maven-javadoc-plugin
property=maven.javadoc.links/
-maven:get var=maven.javadoc.locale plugin=maven-javadoc-plugin
property=maven.javadoc.locale/
-maven:get var=maven.javadoc.maxmemoryplugin=maven-javadoc-plugin
property=maven.javadoc.maxmemory/
-maven:get var=maven.javadoc.mode.online plugin=maven-javadoc-plugin
property=maven.javadoc.mode.online/
-maven:get var=maven.javadoc.offlineLinks plugin=maven-javadoc-plugin
property=maven.javadoc.offlineLinks/
-maven:get var=maven.javadoc.overview plugin=maven-javadoc-plugin
property=maven.javadoc.overview/
-maven:get var=maven.javadoc.package plugin=maven-javadoc-plugin
property=maven.javadoc.package/
-maven:get var=maven.javadoc.private plugin=maven-javadoc-plugin
property=maven.javadoc.private/
-maven:get var=maven.javadoc.public plugin=maven-javadoc-plugin
property=maven.javadoc.public/
-maven:get var=maven.javadoc.source plugin=maven-javadoc-plugin
property=maven.javadoc.source/
-maven:get var=maven.javadoc.stylesheet plugin=maven-javadoc-plugin
property=maven.javadoc.stylesheet/
-maven:get var=maven.javadoc.tagletpath plugin=maven-javadoc-plugin
property=maven.javadoc.tagletpath/
-maven:get var=maven.javadoc.taglets plugin=maven-javadoc-plugin
property=maven.javadoc.taglets/
-maven:get var=maven.javadoc.use plugin=maven-javadoc-plugin
property=maven.javadoc.use/
-maven:get var=maven.javadoc.useexternalfile plugin=maven-javadoc-plugin
property=maven.javadoc.useexternalfile/
-maven:get var=maven.javadoc.version plugin=maven-javadoc-plugin
property=maven.javadoc.version/
-maven:get var=maven.javadoc.windowtitle plugin=maven-javadoc-plugin
property=maven.javadoc.windowtitle/
-
!-- internal variables --
j:set var=internal.javadoc.jar
value=${maven.build.dir}/${maven.final.name}_javadoc.jar/
j:set var=internal.javadoc.neededvalue=null/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/xdocs changes.xml
brett 2004/07/07 03:00:55 Modified:.Tag: MAVEN-1_0-BRANCH project.xml xdocsTag: MAVEN-1_0-BRANCH changes.xml Log: include XML tag library. Needed for new build function, but also because it is so often needed and forgotten in plugins. Revision ChangesPath No revision No revision 1.317.4.30 +6 -0 maven/project.xml Index: project.xml === RCS file: /home/cvs/maven/project.xml,v retrieving revision 1.317.4.29 retrieving revision 1.317.4.30 diff -u -r1.317.4.29 -r1.317.4.30 --- project.xml 28 Jun 2004 15:09:45 - 1.317.4.29 +++ project.xml 7 Jul 2004 10:00:55 - 1.317.4.30 @@ -632,6 +632,12 @@ urlhttp://jakarta.apache.org/commons/jelly/tags/util//url /dependency dependency + groupIdcommons-jelly/groupId + artifactIdcommons-jelly-tags-xml/artifactId + version20040613.030723/version + urlhttp://jakarta.apache.org/commons/jelly/tags/xml//url +/dependency +dependency idcommons-graph/id version0.8.1/version urlhttp://jakarta.apache.org/commons/sandbox/graph//url No revision No revision 1.14.4.31 +1 -0 maven/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven/xdocs/changes.xml,v retrieving revision 1.14.4.30 retrieving revision 1.14.4.31 diff -u -r1.14.4.30 -r1.14.4.31 --- changes.xml 6 Jul 2004 12:45:48 - 1.14.4.30 +++ changes.xml 7 Jul 2004 10:00:55 - 1.14.4.31 @@ -25,6 +25,7 @@ /properties body release version=1.0-final-SNAPSHOT date=in CVS + action dev=brett type=addBundle the Jelly XML tag library for build and for plugin's convenience/action action dev=brett type=fix issue=MAVEN-1296 due-to=Eric LapierreFix property inheritence under some circumstances/action action dev=brett type=addAdd different types of download progress meters./action action dev=brett type=fixlt;maven:get/gt; now initialises the plugin if it has not already been loaded, removing the need for dependency handles/action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/java/org/apache/maven/plugin PluginManager.java
brett 2004/07/07 03:09:08
Modified:src/java/org/apache/maven/plugin Tag: MAVEN-1_0-BRANCH
PluginManager.java
Log:
rename property to correct meaning, don't install to plugin directory
Revision ChangesPath
No revision
No revision
1.70.4.52 +4 -9 maven/src/java/org/apache/maven/plugin/PluginManager.java
Index: PluginManager.java
===
RCS file: /home/cvs/maven/src/java/org/apache/maven/plugin/PluginManager.java,v
retrieving revision 1.70.4.51
retrieving revision 1.70.4.52
diff -u -r1.70.4.51 -r1.70.4.52
--- PluginManager.java5 Jul 2004 21:01:48 - 1.70.4.51
+++ PluginManager.java7 Jul 2004 10:09:08 - 1.70.4.52
@@ -806,17 +806,12 @@
* @param parentProject the project to load the installed plugin into
* @todo remove any old one
*/
-public void installPlugin( File file, Project parentProject, boolean
installToUserPluginDirectory )
+public void installPlugin( File file, Project parentProject, boolean cache )
throws MavenException
{
-log.debug( Using plugin dependency: + file );
+log.debug( Using plugin file: + file );
try
{
-if ( installToUserPluginDirectory )
-{
-FileUtils.copyFileToDirectory( file, userPluginsDir );
-}
-
String pluginName = file.getCanonicalFile().getName();
pluginName = pluginName.substring( 0, pluginName.indexOf( .jar ) );
@@ -836,7 +831,7 @@
housing.parse( transientMapper );
// Should only be putting in the transientMapper - but it is
not consistent with isLoaded
housing.parse( mapper );
-if ( installToUserPluginDirectory )
+if ( cache )
{
cacheManager.registerPlugin( pluginName, housing );
housing.parse( cacheManager );
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/plugin-parent project.xml
brett 2004/07/07 03:24:18 Modified:plugin-parent project.xml Log: add nagEmailAddress Revision ChangesPath 1.6 +1 -0 maven-plugins/plugin-parent/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/plugin-parent/project.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- project.xml 25 Jun 2004 15:24:30 - 1.5 +++ project.xml 7 Jul 2004 10:24:18 - 1.6 @@ -134,6 +134,7 @@ build sourceDirectorysrc/main/sourceDirectory unitTestSourceDirectorysrc/test/unitTestSourceDirectory +nagEmailAddress[EMAIL PROTECTED]/nagEmailAddress unitTest includes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven plugin-profile.xml maven.xml project.properties
brett 2004/07/07 03:35:35
Modified:.Tag: MAVEN-1_0-BRANCH maven.xml project.properties
Added: .Tag: MAVEN-1_0-BRANCH plugin-profile.xml
Log:
use a plugin profile to build the release so that it can be reproduced later
Revision ChangesPath
No revision
No revision
1.97.2.31 +27 -38maven/maven.xml
Index: maven.xml
===
RCS file: /home/cvs/maven/maven.xml,v
retrieving revision 1.97.2.30
retrieving revision 1.97.2.31
diff -u -r1.97.2.30 -r1.97.2.31
--- maven.xml 5 Jul 2004 20:58:49 - 1.97.2.30
+++ maven.xml 7 Jul 2004 10:35:35 - 1.97.2.31
@@ -18,6 +18,7 @@
project default=jar:jar
xmlns:j=jelly:core
xmlns:u=jelly:util
+ xmlns:x=jelly:xml
xmlns:ant=jelly:ant
xmlns:maven=jelly:maven
@@ -177,35 +178,20 @@
ant:fixcrlf srcdir=${installerDir} eol=crlf includes=**/*.bat /
ant:fixcrlf srcdir=${installerDir} eol=lf includes=**/*.sh,**/maven /
-!-- TODO: check if this works when run by scm:perform-release --
+x:parse var=plugins xml=${maven.plugins.profile} /
+x:forEach var=plugin select=$plugins/plugins/plugin
+ j:set var=groupIdx:expr select=@groupId //j:set
+ j:set var=artifactIdx:expr select=@artifactId //j:set
+ j:set var=versionx:expr select=@version //j:set
+ ant:echoDownloading ${groupId}:${artifactId} version ${version}/ant:echo
+ attainGoal name=plugin:download-artifact /
+ ant:copy
+
file=${maven.repo.local}/${groupId}/plugins/${artifactId}-${version}.jar
+ todir=${installerDir}/plugins
+ /
+/x:forEach
-maven:reactor
- basedir=${maven.plugins.directory}
- includes=${maven.plugins.includes}
- excludes=${maven.plugins.excludes}
- postProcessing=true
- banner=Gathering
- ignoreFailures=false
-/
-j:forEach var=reactorProject items=${reactorProjects}
- j:set var=version
value=${reactorProject.versions[size(reactorProject.versions)-1]} /
- j:if test=${version.tag == 'HEAD'}
-j:set var=version
value=${reactorProject.versions[size(reactorProject.versions)-2]} /
- /j:if
- j:if test=${version == null}
-ant:failWARNING: no version for ${reactorProject})/ant:fail
- /j:if
- j:if test=${version != null}
-ant:echoDownloading ${reactorProject.artifactId} version
${version}/ant:echo
-j:set var=groupId value=maven /
-j:set var=artifactId value=${reactorProject.artifactId} /
-attainGoal name=plugin:download-artifact /
-ant:copy
-
file=${maven.repo.local}/${reactorProject.groupId}/plugins/${reactorProject.artifactId}-${version}.jar
-todir=${installerDir}/plugins
-/
- /j:if
-/j:forEach
+attainGoal name=maven:build-seed-repo /
/goal
goal name=maven:build-plugin-profile
@@ -217,7 +203,8 @@
banner=Gathering
ignoreFailures=false
/
-j:file name=${maven.build.dir}/plugin-profile.xml
+ant:copy tofile=${maven.plugins.profile}.bak file=${maven.plugins.profile}
/
+j:file name=${maven.plugins.profile}
omitXmlDeclaration=false
outputMode=xml
prettyPrint=true
@@ -228,7 +215,7 @@
j:set var=version
value=${reactorProject.versions[size(reactorProject.versions)-2]} /
/j:if
j:if test=${version == null}
-ant:echoWARNING: no version for ${reactorProject})/ant:echo
+ant:echoWARNING: no version for ${reactorProject}/ant:echo
/j:if
j:if test=${version != null}
plugin artifactId=${reactorProject.artifactId} groupId=maven
version=${version} /
@@ -336,7 +323,8 @@
j:when test=${systemScope['os.name'].startsWith('Windows')}
j:set var=maven.dist.bin.assembly.dir value=${installerDir} /
attainGoal name=nsis /
-ant:copy
tofile=${maven.build.dir}/installer/${pom.artifactId}-${pom.currentVersion}.exe
file=${maven.build.dir}/${pom.artifactId}.exe /
+maven:get var=distDir plugin=maven-dist-plugin
property=maven.dist.dir/
+ant:copy
tofile=${maven.build.dir}/installer/${pom.artifactId}-${pom.currentVersion}.exe
file=${distDir}/${pom.artifactId}.exe /
!--
j:set var=maven.dist.bin.assembly.dir value=${installerDirLite} /
attainGoal name=nsis /
@@ -414,14 +402,15 @@
j:set var=prevRepoLocal value=${maven.repo.local} /
j:set var=prevRepoRemote value=${maven.repo.remote} /
j:set var=repoLocal value=${basedir}/target/seed-repo /
-j:set var=maven.repo.local value=${repoLocal} /
-j:set var=maven.repo.remote value=file:${prevRepoLocal},${prevRepoRemote}
/
[jira] Created: (MAVEN-1363) Reactor goal attribute does not have whitespace trimmed from comma-delimited goal-names
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1363
Here is an overview of the issue:
-
Key: MAVEN-1363
Summary: Reactor goal attribute does not have whitespace trimmed from
comma-delimited goal-names
Type: Bug
Status: Unassigned
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Versions:
1.0
Assignee:
Reporter: Simon Turner
Created: Wed, 7 Jul 2004 7:09 AM
Updated: Wed, 7 Jul 2004 7:09 AM
Environment: Win XP Pro, Red Hat 8
Description:
It is possible to define a goal attribute in the reactor element of a goal which has a
number of goal-names, separated by commas:
m:reactor basedir=${basedir}/..
includes=*/project.xml
goals=clean, jar:install
banner=bla
ignoreFailures=false/
In the above example, the second goal-name will be interpreted by maven as
jar:install rather than jar:install (so the build fails). This was not the case
with 1.0 rc1, but is the case with 1.0 rc4.
-
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]
[vote] plugin releases
Doesn't seem so long since I was last doing this :) I would like to release the following plugins as they've had reasonable changes artifact gump javadoc jcoverage xdoc Also, I'd like to release the following quietly to update the commons-* dependencies and reduce the download size of maven site: antlr jira jxr latex latka linkcheck site I think the following should be polished and released by others before 1.0: abbot (Vincent) hibernate (Eric) jnlp (Emmanuel) nsis (Dion) The following have changed, and anyone interested in the fixes should put forward a release for them, however I'm not planning to wait on 1.0 for them: announcement, ant, appserver, aspectj, changes, checkstyle, dist, eclipse, ejb, jalopy, jboss, webserver How does this sound? I'll now turn my attention to documentation again, including some of my recent changes I've been a little slack with. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-160) tm4j-tmapi-0.9.5
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-160 Here is an overview of the issue: - Key: MAVENUPLOAD-160 Summary: tm4j-tmapi-0.9.5 Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Kal Ahmed Created: Wed, 7 Jul 2004 7:29 AM Updated: Wed, 7 Jul 2004 7:29 AM Description: Implementation of the standard TMAPI interfaces for the TM4J topic map engine. - 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: (MAVENUPLOAD-159) tm4j-0.9.5
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-159 Here is an overview of the issue: - Key: MAVENUPLOAD-159 Summary: tm4j-0.9.5 Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Kal Ahmed Created: Wed, 7 Jul 2004 7:28 AM Updated: Wed, 7 Jul 2004 7:28 AM Description: http://www.tm4j.org/maven-upload/tm4j-0.9.5-bundle.jar TM4J topic map engine for Java. - 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: (MAVENUPLOAD-162) tm4jadmintool-0.9.5
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-162 Here is an overview of the issue: - Key: MAVENUPLOAD-162 Summary: tm4jadmintool-0.9.5 Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Kal Ahmed Created: Wed, 7 Jul 2004 7:31 AM Updated: Wed, 7 Jul 2004 7:31 AM Description: http://www.tm4j.org/maven-upload/tm4jadmintool-0.9.5-bundle.jar GUI tool for managing topic map repositories that use TM4J. - 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: (MAVENUPLOAD-161) tm4j-tologx-0.9.5
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-161 Here is an overview of the issue: - Key: MAVENUPLOAD-161 Summary: tm4j-tologx-0.9.5 Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Kal Ahmed Created: Wed, 7 Jul 2004 7:30 AM Updated: Wed, 7 Jul 2004 7:30 AM Description: http://www.tm4j.org/maven-upload/tm4j-tologx-0.9.5-bundle.jar Implementation of the tolog topic map query language for the TM4J topic map engine. - 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: (MAVENUPLOAD-164) tm4ozone-0.9.5
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-164 Here is an overview of the issue: - Key: MAVENUPLOAD-164 Summary: tm4ozone-0.9.5 Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Kal Ahmed Created: Wed, 7 Jul 2004 7:33 AM Updated: Wed, 7 Jul 2004 7:33 AM Description: http://www.tm4j.org/maven-upload/tm4ozone-0.9.5-bundle.jar Object-oriented database persistence for the TM4J topic map engine. - 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: (MAVENUPLOAD-163) tm4jdbc-0.9.5
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-163 Here is an overview of the issue: - Key: MAVENUPLOAD-163 Summary: tm4jdbc-0.9.5 Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Kal Ahmed Created: Wed, 7 Jul 2004 7:32 AM Updated: Wed, 7 Jul 2004 7:32 AM Description: http://www.tm4j.org/maven-upload/tm4jadmintool-0.9.5-bundle.jar Relational database persistence for the TM4J topic map engine. - 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: (MPJALOPY-5) Jalopy destroys JUnitDoclet generated test classes
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPJALOPY-5 Here is an overview of the issue: - Key: MPJALOPY-5 Summary: Jalopy destroys JUnitDoclet generated test classes Type: Improvement Status: Open Priority: Critical Original Estimate: 20 minutes Time Spent: Unknown Remaining: 20 minutes Project: maven-jalopy-plugin Assignee: Emmanuel Venisse Reporter: Joachim Bader Created: Wed, 7 Jul 2004 9:10 AM Updated: Wed, 7 Jul 2004 9:10 AM Environment: JUnitDoclet Plugin 1.2, Jalopy Plugin 1.3-SNAPSHOT with my own code stylesheet Description: If test classes there, jalopy formats the test classes. If tests are generated with JUnitDoclet the junitdoclet plugin canont read/update the test classes anymore. Reason: unexpected code format solution: exclude the JUnitDoclet generated test classes from format. Attached is a patch which add separate include/exclude properties for src/java and src/test directory. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPJALOPY-5) Jalopy destroys JUnitDoclet generated test classes
The following issue has been updated: Updater: Joachim Bader (mailto:[EMAIL PROTECTED]) Date: Wed, 7 Jul 2004 9:11 AM Comment: add the following properites to the plugin: maven.jalopy.filesetExclude maven.jalopy.src.filesetInclude maven.jalopy.src.filesetExclude maven.jalopy.test.filesetInclude maven.jalopy.test.filesetExclude Changes: Attachment changed to patch.diff - For a full history of the issue, see: http://jira.codehaus.org/browse/MPJALOPY-5?page=history - View the issue: http://jira.codehaus.org/browse/MPJALOPY-5 Here is an overview of the issue: - Key: MPJALOPY-5 Summary: Jalopy destroys JUnitDoclet generated test classes Type: Improvement Status: Open Priority: Critical Original Estimate: 20 minutes Time Spent: Unknown Remaining: 20 minutes Project: maven-jalopy-plugin Assignee: Emmanuel Venisse Reporter: Joachim Bader Created: Wed, 7 Jul 2004 9:10 AM Updated: Wed, 7 Jul 2004 9:11 AM Environment: JUnitDoclet Plugin 1.2, Jalopy Plugin 1.3-SNAPSHOT with my own code stylesheet Description: If test classes there, jalopy formats the test classes. If tests are generated with JUnitDoclet the junitdoclet plugin canont read/update the test classes anymore. Reason: unexpected code format solution: exclude the JUnitDoclet generated test classes from format. Attached is a patch which add separate include/exclude properties for src/java and src/test directory. - 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: (MPJALOPY-2) maven jalopy doesn't format test source
The following comment has been added to this issue:
Author: Joachim Bader
Created: Wed, 7 Jul 2004 9:14 AM
Body:
fine, but this destorys junitdoclet generated test classes.
MPJALOPY-5 fix this issue
-
View this comment:
http://jira.codehaus.org/browse/MPJALOPY-2?page=comments#action_21474
-
View the issue:
http://jira.codehaus.org/browse/MPJALOPY-2
Here is an overview of the issue:
-
Key: MPJALOPY-2
Summary: maven jalopy doesn't format test source
Type: Bug
Status: Closed
Priority: Minor
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-jalopy-plugin
Assignee:
Reporter: Steve Vaughan
Created: Mon, 8 Sep 2003 7:09 AM
Updated: Wed, 7 Jul 2004 9:14 AM
Description:
Executing maven jalopy doesn't format test source code. By making a small change to
the jalopy plugin.jelly file, the goal can include test source code.
cvs diff src/plugins-build/jalopy/plugin.jelly
Index: src/plugins-build/jalopy/plugin.jelly
===
RCS file: /home/cvspublic/maven/src/plugins-build/jalopy/plugin.jelly,v
retrieving revision 1.3
diff -r1.3 plugin.jelly
4c4
xmlns:ant=jelly:ant
---
xmlns:ant=jelly:ant xmlns:j=jelly:core
50a51,55
j:if test=${unitTestSourcesPresent == 'true'}
ant:fileset dir=${pom.build.unitTestSourceDirectory}
ant:include name=${maven.jalopy.filesetInclude} /
/ant:fileset
/j:if
-
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]
Request for help unsubscribing
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 unsubscribe 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]
RE : maven 1.0 prep
Brett, There's a recent problem with the bootstrap on the 1.0 Can you try to fix it please ? http://jira.codehaus.org/browse/MAVEN-1362 Arnaud -Message d'origine- De : Brett Porter [mailto:[EMAIL PROTECTED] Envoyé : mardi 6 juillet 2004 16:47 À : Maven Developers List Objet : 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPSCM-15) Plucin to support StarTeam
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPSCM-15 Here is an overview of the issue: - Key: MPSCM-15 Summary: Plucin to support StarTeam Type: New Feature Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-scm-plugin Assignee: Brett Porter Reporter: Jan Najvarek Created: Wed, 7 Jul 2004 10:22 AM Updated: Wed, 7 Jul 2004 10:22 AM Environment: Windows Description: This plugin should support StarTeam source versioning system. Changelog, Developer activity plugins already support this. SCM is last piece in the puzzle to have full support for StarTeam. Thanks! - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [vote] plugin releases
Brett Porter wrote on Wednesday, July 07, 2004 1:10 PM: Doesn't seem so long since I was last doing this :) I would like to release the following plugins as they've had reasonable changes artifact gump javadoc jcoverage xdoc Please include MPXDOC-80. It is very small and allows a single css in a multiproject setup. [snip] How does this sound? Well :) -- Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [vote] plugin releases
-Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: mercredi 7 juillet 2004 13:10 To: Maven Developers List Subject: [vote] plugin releases Doesn't seem so long since I was last doing this :) I would like to release the following plugins as they've had reasonable changes artifact gump javadoc jcoverage xdoc +1 You'll also need to release the announcement plugin then as the download report now also generate release notes. That said, there's probably a better way of doing this (maybe by considering release notes as an artifact type). Still if you wish to release the very latest code of the xdoc plugin you also need to release the latest code of the announcement plugin. Also, I'd like to release the following quietly to update the commons-* dependencies and reduce the download size of maven site: antlr jira jxr latex latka linkcheck site +1 I think the following should be polished and released by others before 1.0: abbot (Vincent) It's actually ready to be released in a 1.0 version. I'll do this tomorrow. hibernate (Eric) jnlp (Emmanuel) nsis (Dion) The following have changed, and anyone interested in the fixes should put forward a release for them, however I'm not planning to wait on 1.0 for them: announcement, ant, appserver, aspectj, changes, checkstyle, dist, eclipse, ejb, jalopy, jboss, webserver I can do (tomorrow) the changes one + the jboss one. I'll let Carlos handle the aspectj one ;-) How does this sound? I'll now turn my attention to documentation again, including some of my recent changes I've been a little slack with. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Request for help unsubscribing
On Wed, 2004-07-07 at 09:53, Paterline, David L. wrote: 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 unsubscribe me manually from this list. Can anyone help? What address did you subscribe with? Problems generally only arise when you've subscribed with one address and then try and unsubscribe with another. Give me the address that you subscribed with and I'll get infrastructure to unsubscribe you. 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] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPJALOPY-5) Jalopy destroys JUnitDoclet generated test classes
Message: The following issue has been closed. Resolver: Emmanuel Venisse Date: Wed, 7 Jul 2004 11:59 AM Applied. Thanks. - View the issue: http://jira.codehaus.org/browse/MPJALOPY-5 Here is an overview of the issue: - Key: MPJALOPY-5 Summary: Jalopy destroys JUnitDoclet generated test classes Type: Improvement Status: Closed Priority: Critical Resolution: FIXED Original Estimate: 20 minutes Time Spent: Unknown Remaining: 20 minutes Project: maven-jalopy-plugin Fix Fors: 1.3 Assignee: Emmanuel Venisse Reporter: Joachim Bader Created: Wed, 7 Jul 2004 9:10 AM Updated: Wed, 7 Jul 2004 11:59 AM Environment: JUnitDoclet Plugin 1.2, Jalopy Plugin 1.3-SNAPSHOT with my own code stylesheet Description: If test classes there, jalopy formats the test classes. If tests are generated with JUnitDoclet the junitdoclet plugin canont read/update the test classes anymore. Reason: unexpected code format solution: exclude the JUnitDoclet generated test classes from format. Attached is a patch which add separate include/exclude properties for src/java and src/test directory. - 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/07 03:25:30
Modified:src/test/touchstone-build Tag: MAVEN-1_0-BRANCH maven.xml
Log:
remove dist goal attainment. weas just testing - not needed
Revision ChangesPath
No revision
No revision
1.43.4.20 +0 -1 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.19
retrieving revision 1.43.4.20
diff -u -r1.43.4.19 -r1.43.4.20
--- maven.xml 6 Jul 2004 12:27:20 - 1.43.4.19
+++ maven.xml 7 Jul 2004 10:25:30 - 1.43.4.20
@@ -863,7 +863,6 @@
j:if test=${d != 'foo'}
failmaven.javadoc.debug in javadoc plugin is not 'foo', is '${d}'/fail
/j:if
-attainGoal name=dist /
/goal
/project
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1362) Cannot build maven : test-plugin-loading fails in the bootstrap
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1362 Here is an overview of the issue: - Key: MAVEN-1362 Summary: Cannot build maven : test-plugin-loading fails in the bootstrap Type: Bug Status: Open Priority: Blocker Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Fix Fors: 1.0 Versions: 1.0 Assignee: Brett Porter Reporter: Arnaud HERITIER Created: Wed, 7 Jul 2004 5:43 AM Updated: Wed, 7 Jul 2004 5:43 AM Environment: Win XP, Maven 1.0 CVS Branch Description: Since several days I can't build maven with the bootstrap. The build fails on the test-plugin-loading at the end of the bootstrap. The error is the following : [exec] test-plugin-loading: [exec] [echo] DEPRECATED: the use of dependency-handle is deprecated. Please use maven:get/set to modify properties of the multiproject plugin [exec] Plugin 'maven-deploy-plugin' in project 'Touchstone' is not available [exec] BUILD FAILED [exec] File.. C:\Work\Opensources\maven-1.0\maven.xml [exec] Element... maven:maven [exec] Line.. 66 [exec] Column 7 [exec] Unable to obtain goal [touchstone-tests] -- C:\Work\Opensources\maven-1.0\src\test\touchstone-build\maven.xml:859:13: fail maven.dist.tar.executable in dist plugin is not 'tar', is 'gtar' [exec] Total time: 1 minutes 52 seconds [exec] Finished at: Wed Jul 07 11:12:05 CEST 2004 The problem seems to appear because at work I defined in my %HOME%/build.properties the following property : maven.dist.tar.executable = gtar I don't want to comment this property each time I build maven. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven 1.0 prep
Brett Porter wrote on Tuesday, July 06, 2004 4:47 PM: [snip] 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. Can you review again http://jira.codehaus.org/browse/MPXDOC-80 ? Thanks, Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jalopy/xdocs changes.xml properties.xml
evenisse2004/07/07 08:59:27
Modified:jalopy plugin.jelly plugin.properties
jalopy/xdocs changes.xml properties.xml
Log:
[MPJALOPY-5]. Add some exclude properties.
Revision ChangesPath
1.7 +4 -2 maven-plugins/jalopy/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/jalopy/plugin.jelly,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- plugin.jelly 10 May 2004 23:38:03 - 1.6
+++ plugin.jelly 7 Jul 2004 15:59:27 - 1.7
@@ -64,12 +64,14 @@
classpathref=project.classpath
j:if test=${sourcesPresent == 'true'}
ant:fileset dir=${pom.build.sourceDirectory}
- ant:include name=${maven.jalopy.filesetInclude} /
+ ant:include name=${maven.jalopy.src.filesetInclude} /
+ ant:exclude name=${maven.jalopy.src.filesetExclude} /
/ant:fileset
/j:if
j:if test=${unitTestSourcesPresent == 'true'}
ant:fileset dir=${pom.build.unitTestSourceDirectory}
- ant:include name=${maven.jalopy.filesetInclude} /
+ ant:include name=${maven.jalopy.test.filesetInclude} /
+ ant:exclude name=${maven.jalopy.test.filesetExclude} /
/ant:fileset
/j:if
/ant:jalopy
1.5 +8 -0 maven-plugins/jalopy/plugin.properties
Index: plugin.properties
===
RCS file: /home/cvs/maven-plugins/jalopy/plugin.properties,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- plugin.properties 4 Mar 2004 18:31:20 - 1.4
+++ plugin.properties 7 Jul 2004 15:59:27 - 1.5
@@ -25,3 +25,11 @@
maven.jalopy.nbThread=1
maven.jalopy.failOnError=true
maven.jalopy.filesetInclude=**/*.java
+maven.jalopy.filesetExclude=
+
+maven.jalopy.src.filesetInclude=${maven.jalopy.filesetInclude}
+maven.jalopy.src.filesetExclude=${maven.jalopy.filesetExclude}
+
+maven.jalopy.test.filesetInclude=${maven.jalopy.filesetInclude}
+maven.jalopy.test.filesetExclude=${maven.jalopy.filesetExclude}
+
1.12 +2 -1 maven-plugins/jalopy/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/jalopy/xdocs/changes.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- changes.xml 5 Jul 2004 08:05:28 - 1.11
+++ changes.xml 7 Jul 2004 15:59:27 - 1.12
@@ -25,7 +25,8 @@
/properties
body
release version=1.3 date=In CVS
- action dev=dion type=updateMove to jalopy 1.0b11/action
+ action dev=evenisse type=update issue=MPJALOPY-5Add some exclude
properties./action
+ action dev=evenisse type=updateMove to jalopy 1.0b11/action
/release
release version=1.2 date=2004-05-15/release
release version=1.1 date=2003-09-29
1.3 +42 -1 maven-plugins/jalopy/xdocs/properties.xml
Index: properties.xml
===
RCS file: /home/cvs/maven-plugins/jalopy/xdocs/properties.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- properties.xml4 Mar 2004 18:31:21 - 1.2
+++ properties.xml7 Jul 2004 15:59:27 - 1.3
@@ -27,6 +27,7 @@
body
section name=Jalopy Settings
table
+ trthProperty/ththOptional?/ththDescription/th/tr
tr
tdmaven.jalopy.fileFormat/td
tdYes/td
@@ -84,9 +85,49 @@
tdmaven.jalopy.filesetInclude/td
tdYes/td
td
-Specifies a fileset source file to format. Defaults to **/*.java.
+Specifies a fileset source file to format. Defaults to
code**/*.java/code.
/td
/tr
+tr
+ tdmaven.jalopy.filesetExclude/td
+ tdYes/td
+ td
+Source files excluded from format. Default: empty.
+ /td
+/tr
+tr
+ tdmaven.jalopy.src.filesetInclude/td
+ tdYes/td
+ td
+For codesrc/java/code directory. Specifies a fileset source file to
format.
+ Defaults to code${maven.jalopy.filesetInclude}/code.
+ /td
+/tr
+tr
+ tdmaven.jalopy.src.filesetExclude/td
+ tdYes/td
+ td
+For codesrc/java/code direcotry. Source files excluded from format.
+ Defaults to code${maven.jalopy.filesetExclude}/code.
+ /td
+/tr
+tr
+ tdmaven.jalopy.test.filesetInclude/td
+ tdYes/td
+ td
+
RE : plugin:setup/plugin:remove to replace plugin:install/plugin:uninstall
+1 Arnaud -Message d'origine- De : Brett Porter [mailto:[EMAIL PROTECTED] Envoyé : mardi 6 juillet 2004 14:33 À : Maven Developers List Objet : 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] plugin releases
- Original Message - From: Brett Porter [EMAIL PROTECTED] To: Maven Developers List [EMAIL PROTECTED] Sent: Wednesday, July 07, 2004 1:10 PM Subject: [vote] plugin releases Doesn't seem so long since I was last doing this :) I would like to release the following plugins as they've had reasonable changes artifact gump javadoc jcoverage xdoc +1 Also, I'd like to release the following quietly to update the commons-* dependencies and reduce the download size of maven site: antlr jira jxr latex latka linkcheck site +1 I think the following should be polished and released by others before 1.0: abbot (Vincent) hibernate (Eric) jnlp (Emmanuel) nsis (Dion) I'll release my plugin. The following have changed, and anyone interested in the fixes should put forward a release for them, however I'm not planning to wait on 1.0 for them: announcement, ant, appserver, aspectj, changes, checkstyle, dist, eclipse, ejb, jalopy, jboss, webserver I'll release jalopy plugion before 1.0 And I'm +1 for release the ejb plugin because windows user obtain ejb:*-client goals in RC4 and linux user not ;-) I'll can release it. How does this sound? I'll now turn my attention to documentation again, including some of my recent changes I've been a little slack with. Cheers, Brett - 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] Created: (MPNSIS-7) Use desktop shortcuts in default templates causes compilation error
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPNSIS-7 Here is an overview of the issue: - Key: MPNSIS-7 Summary: Use desktop shortcuts in default templates causes compilation error Type: Bug Status: Open Priority: Critical Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-nsis-plugin Versions: 1.0 Assignee: dion gillard Reporter: Geoffrey Created: Wed, 7 Jul 2004 4:00 PM Updated: Wed, 7 Jul 2004 4:00 PM Description: If you put in a desktop-shortcuts.nsh file, the script won't compile, because this will be generated: ; OPTIONAL Desktop Shortcut Section Create Desktop Shortcut !include desktop-shortcuts.nsh ;SectionEnd ; -- Section to Install the Uninstaller Section Install Uninstaller The extra ; in ;SectionEnd makes Section to Install the Uninstaller not compile If you don't have that file, it doesn't put in the desktop shorcut part - 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: (MPXDOC-114) cvs-usage presumes pserve protocol on connection
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPXDOC-114 Here is an overview of the issue: - Key: MPXDOC-114 Summary: cvs-usage presumes pserve protocol on connection Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-xdoc-plugin Assignee: Jason van Zyl Reporter: Erik Husby Created: Wed, 7 Jul 2004 4:10 PM Updated: Wed, 7 Jul 2004 4:10 PM Description: The Repository report makes some assumptions about ones use of cvs that are not necessarily true. 1. The pom.repository.connection is assumed to be the pserve protocol. Not true for our in-house projects. 2. The pom.repository.developerConnection is only displayed when there is a pom.repository.connection entry. The two fields are not connected. 3. The CVS Access behind firewall is always included if pom.repository.connection is specified. This is not true in our in-house environment. The changelog report works fine if only pom.repository.developerConnection is specified, I would like to not specify pom.repository.connnection Problem#1 can be addressed by examinging the cvs protocol and adjusting the comments. Problem#2 I experimented with modifing the cvs-usage.xml but not being knowledge in velocity, I could not see why problem #2 occurs. Problem#3 can be solved in a number of ways from an addition to the pom.repository or by an additional maven-xdoc-plugin property. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/src/plugin-resources/templates setup.jelly
dion2004/07/07 14:01:52 Modified:nsis/src/plugin-resources/templates setup.jelly Log: Remove accidental comment. Issue MPNSIS-7 Revision ChangesPath 1.15 +1 -1 maven-plugins/nsis/src/plugin-resources/templates/setup.jelly Index: setup.jelly === RCS file: /home/cvs/maven-plugins/nsis/src/plugin-resources/templates/setup.jelly,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- setup.jelly 5 Jul 2004 13:05:45 - 1.14 +++ setup.jelly 7 Jul 2004 21:01:52 - 1.15 @@ -117,7 +117,7 @@ ; OPTIONAL Desktop Shortcut Section Create Desktop Shortcut !include desktop-shortcuts.nsh -;SectionEnd +SectionEnd /util:available ; -- Section to Install the Uninstaller - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs changes.xml
dion2004/07/07 14:02:39 Modified:nsis/xdocs changes.xml Log: Remove accidental comment. Issue MPNSIS-7 Revision ChangesPath 1.8 +3 -0 maven-plugins/nsis/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/nsis/xdocs/changes.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- changes.xml 5 Jul 2004 13:20:37 - 1.7 +++ changes.xml 7 Jul 2004 21:02:39 - 1.8 @@ -25,6 +25,9 @@ /properties body release version=1.1-SNAPSHOT date=in CVS + action dev=dion type=fix issue=MPNSIS-7 due-to=Geoffrey +Desktop shortcuts cause a compile error + /action action dev=dion type=fixUse pom.organization.name instead of pom.organization./action action dev=dion type=update issue=MPNSIS-6 due-to=Geoffrey Add PROJECT_URL to constants. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPNSIS-7) Use desktop shortcuts in default templates causes compilation error
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MPNSIS-7 Here is an overview of the issue: - Key: MPNSIS-7 Summary: Use desktop shortcuts in default templates causes compilation error Type: Bug Status: Closed Priority: Critical Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-nsis-plugin Fix Fors: 1.1 Versions: 1.0 Assignee: dion gillard Reporter: Geoffrey Created: Wed, 7 Jul 2004 4:00 PM Updated: Wed, 7 Jul 2004 5:02 PM Description: If you put in a desktop-shortcuts.nsh file, the script won't compile, because this will be generated: ; OPTIONAL Desktop Shortcut Section Create Desktop Shortcut !include desktop-shortcuts.nsh ;SectionEnd ; -- Section to Install the Uninstaller Section Install Uninstaller The extra ; in ;SectionEnd makes Section to Install the Uninstaller not compile If you don't have that file, it doesn't put in the desktop shorcut part - 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/javadoc/xdocs changes.xml goals.xml index.xml navigation.xml properties.xml
aheritier2004/07/07 14:21:45
Modified:javadoc plugin.jelly
javadoc/src/plugin-test maven.xml project.xml
javadoc/src/plugin-test/src/main/org/apache/maven
package.html
javadoc/src/plugin-test/src/main/org/apache/maven2
package.html
javadoc/src/plugin-test/src/opt/org/apache/maven3
package.html
javadoc/xdocs changes.xml goals.xml index.xml navigation.xml
properties.xml
Log:
Remove sourceModifications management in the plugin.
It created a lot of problems (MPJAVADOC-28, MPJAVADOC-29).
Revision ChangesPath
1.47 +9 -81 maven-plugins/javadoc/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/javadoc/plugin.jelly,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- plugin.jelly 7 Jul 2004 10:00:15 - 1.46
+++ plugin.jelly 7 Jul 2004 21:21:45 - 1.47
@@ -36,7 +36,6 @@
!-- internal variables --
j:set var=internal.javadoc.jar
value=${maven.build.dir}/${maven.final.name}_javadoc.jar/
j:set var=internal.javadoc.neededvalue=null/
-j:set var=internal.javadoc.src.modifsvalue=false/
j:set var=internal.javadoc.src.set
value=${context.getAntProject().getReferences().get('maven.compile.src.set')}/
j:set var=internal.javadoc.working.dir
value=${maven.build.dir}/javadoc/
@@ -75,7 +74,6 @@
==
internal.javadoc.jar= [${internal.javadoc.jar}]
internal.javadoc.needed = [${internal.javadoc.needed}]
-internal.javadoc.src.modifs = [${internal.javadoc.src.modifs}]
internal.javadoc.src.set= [${internal.javadoc.src.set}]
internal.javadoc.working.dir= [${internal.javadoc.working.dir}]
/ant:echo
@@ -99,61 +97,29 @@
j:when test=${internal.javadoc.needed != null}
!-- We have already decided if javadoc is needed --
- j:if test=${maven.javadoc.debug}ant:echo${internal.javadoc.needed}
not null/ant:echo/j:if
+ j:if test=${maven.javadoc.debug}ant:echointernal.javadoc.needed not
null : ${internal.javadoc.needed}/ant:echo/j:if
/j:when
-j:otherwise
- !-- Create a patternset for source modifications --
- patternset id=source.modifications
-ant:include name=**/*.java/
-!-- handle source modifications --
-j:forEach var=sm items=${pom.build.sourceModifications}
- ant:available property=classPresent classname=${sm.className}/
- j:if test=${classPresent != 'true'}
-j:forEach var=exclude items=${sm.excludes}
- ant:exclude name=${exclude}/
-/j:forEach !-- end sourceModification exclude --
-j:forEach var=include items=${sm.includes}
- ant:include name=${include}/
-/j:forEach !-- end sourceModification include --
- /j:if
-/j:forEach !-- end sourceModification --
- /patternset
-
- !-- test if sourceModifications are defined --
- j:if test=${pom.build.sourceModifications != null amp;amp;
!pom.build.sourceModifications.isEmpty()}
-j:set var=internal.javadoc.src.modifs scope=parent value=true/
- /j:if
-
- j:if test=${maven.javadoc.debug}
-ant:echointernal.javadoc.src.modifs is
${internal.javadoc.src.modifs}/ant:echo
- /j:if
+j:otherwise
!-- Tokenize the set of directories --
util:tokenize var=sources.dirs
delim=${path.separator}${internal.javadoc.src.set}/util:tokenize
-
- !-- Counter used to name filesets --
- j:set var=src.set.counter value=0/
-
+
!-- For each directory --
j:forEach var=dir items=${sources.dirs}
!-- If we have not already find sources --
j:if test=${internal.javadoc.needed != true}
!-- We construct the fileset --
- ant:fileset id=${src.set.counter} dir=${dir}
-patternset refid=source.modifications/
- /ant:fileset
ant:fileScanner var=sources
-ant:fileset refid=${src.set.counter} /
+ant:fileset dir=${dir} include=**/*.java/
/ant:fileScanner
j:set var=internal.javadoc.needed scope=parent
value=${sources.iterator().hasNext()} /
- j:set var=src.set.counter
[jira] Closed: (MPJAVADOC-29) broken on jdk 1.3 for multiple packages
Message: The following issue has been closed. Resolver: Arnaud HERITIER Date: Wed, 7 Jul 2004 5:24 PM use of sourceModifications is removed. - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-29 Here is an overview of the issue: - Key: MPJAVADOC-29 Summary: broken on jdk 1.3 for multiple packages Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-javadoc-plugin Assignee: Arnaud HERITIER Reporter: Brett Porter Created: Mon, 28 Jun 2004 6:13 AM Updated: Wed, 7 Jul 2004 5:24 PM Description: works in 1.4, but under 1.3 the packages are all meshed into one. - 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-1364) remove the javadoc link to http://werkz.werken.com/apidocs/
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1364 Here is an overview of the issue: - Key: MAVEN-1364 Summary: remove the javadoc link to http://werkz.werken.com/apidocs/ Type: Bug Status: Unassigned Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Versions: 1.0 Assignee: Reporter: Arnaud HERITIER Created: Wed, 7 Jul 2004 5:52 PM Updated: Wed, 7 Jul 2004 5:52 PM Environment: Maven 1.0 BRANCH from CVS Description: The javadoc for werkz isn't available from http://werkz.werken.com/apidocs/ The javadoc task fails with the JDK 1.3 if a link is missing. We must remove http://werkz.werken.com/apidocs/ from the property maven.javadoc.links - 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/javadoc/xdocs changes.xml properties.xml
aheritier2004/07/07 14:55:27
Modified:javadoc plugin.jelly
javadoc/xdocs changes.xml properties.xml
Log:
PR: MPJAVADOC-31
Submitted by: Takayoshi Kimura
Reviewed by: Arnaud Heritier
Encoding used when reading sources
Revision ChangesPath
1.48 +10 -1 maven-plugins/javadoc/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/javadoc/plugin.jelly,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- plugin.jelly 7 Jul 2004 21:21:45 - 1.47
+++ plugin.jelly 7 Jul 2004 21:55:27 - 1.48
@@ -33,6 +33,7 @@
!-- == --
goal name=javadoc:init prereqs=xdoc:init
+
!-- internal variables --
j:set var=internal.javadoc.jar
value=${maven.build.dir}/${maven.final.name}_javadoc.jar/
j:set var=internal.javadoc.neededvalue=null/
@@ -43,6 +44,10 @@
ant:echo
### Debug mode is on ###
==
+=== java plugin properties ===
+==
+maven.compile.encoding = [${maven.compile.encoding}]
+==
=== javadoc plugin properties ===
==
maven.javadoc.additionalparam = [${maven.javadoc.additionalparam}]
@@ -245,7 +250,11 @@
j:if test=${context.getVariable('maven.javadoc.source') != null}
ant:setProperty name=source value=${maven.javadoc.source} /
/j:if
-
+
+j:if test=${context.getVariable('maven.compile.encoding') != null}
+ ant:setProperty name=encoding value=${maven.compile.encoding} /
+/j:if
+
!-- Process/Parse links --
!-- This code allows to specify a packagelistLoc even when in online mode
--
j:forEach var=link items=${links}
1.35 +1 -0 maven-plugins/javadoc/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/javadoc/xdocs/changes.xml,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- changes.xml 7 Jul 2004 21:21:45 - 1.34
+++ changes.xml 7 Jul 2004 21:55:27 - 1.35
@@ -24,6 +24,7 @@
/properties
body
release version=1.5.1-SNAPSHOT date=In CVS
+ action dev=aheritier type=fix issue=MPJAVADOC-31 due-to=Takayoshi
KimuraUse the property 'maven.compile.encoding' to set the encoding used when
reading sources in javadoc task./action
action dev=aheritier type=fix issue=MPJAVADOC-29Packages list broken
on jdk 1.3 for multiple packages./action
action dev=aheritier type=fix issue=MPJAVADOC-28@link tag not working
with package names./action
action dev=aheritier type=addAdd the property maven.javadoc.debug to
print informations to debug the plugin./action
1.17 +16 -0 maven-plugins/javadoc/xdocs/properties.xml
Index: properties.xml
===
RCS file: /home/cvs/maven-plugins/javadoc/xdocs/properties.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- properties.xml7 Jul 2004 21:21:45 - 1.16
+++ properties.xml7 Jul 2004 21:55:27 - 1.17
@@ -306,5 +306,21 @@
/tr
/table
/section
+section name=Other Settings
+ table
+tr
+ thProperty/th
+ thOptional?/th
+ thDescription/th
+/tr
+tr
+ tdmaven.compile.encoding/td
+ tdYes/td
+ td
+Sets the encoding of the .java files being documented (and compiled).
+ /td
+/tr
+ /table
+/section
/body
/document
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPJAVADOC-31) Default encoding used when reading sources
Message: The following issue has been closed. Resolver: Arnaud HERITIER Date: Wed, 7 Jul 2004 5:56 PM Applied. thanks. - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-31 Here is an overview of the issue: - Key: MPJAVADOC-31 Summary: Default encoding used when reading sources Type: Improvement Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-javadoc-plugin Versions: 1.5 Assignee: Arnaud HERITIER Reporter: Takayoshi Kimura Created: Thu, 1 Jul 2004 4:29 PM Updated: Wed, 7 Jul 2004 5:56 PM Description: Javadocs would be garbled if encoging differ between sources and default one because no encoding specified to ant:javadoc /. - 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-1365) Dependency Being Skipped
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1365 Here is an overview of the issue: - Key: MAVEN-1365 Summary: Dependency Being Skipped Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Versions: 1.0-rc3 Assignee: Reporter: David Erickson Created: Wed, 7 Jul 2004 6:03 PM Updated: Wed, 7 Jul 2004 6:03 PM Environment: WinXp Description: Example: dependency groupIddisplaytag/groupId artifactIddisplaytag/artifactId version1.0-rc1/version jardisplaytag-1.0-rc1.jar/jar urlhttp://displaytag.sourceforge.net//url properties war.bundletrue/war.bundle /properties /dependency dependency groupIddisplaytag/groupId artifactIddisplaytag/artifactId version12/version jardisplaytag-12.tld/jar typetld/type urlhttp://displaytag.sourceforge.net//url properties war.bundletrue/war.bundle /properties /dependency Maven will download and integrate the first dependency, however it skips the second one thinking it is the same, even tho its version, jar name, and type are entirely different. It displays the same behavior if I omit the jar tag as well. (And the jar tag should likely be renamed since it could be something different than a jar, especially in this case). - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/plugin-parent project.properties
aheritier2004/07/07 15:18:07
Modified:plugin-parent project.properties
Log:
Update URL template to Jira issues used in the changes plugin.
Revision ChangesPath
1.2 +3 -0 maven-plugins/plugin-parent/project.properties
Index: project.properties
===
RCS file: /home/cvs/maven-plugins/plugin-parent/project.properties,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- project.properties2 May 2004 12:31:35 - 1.1
+++ project.properties7 Jul 2004 22:18:07 - 1.2
@@ -29,3 +29,6 @@
# License plugin settings
maven.license.licenseFile=${basedir}/../LICENSE.txt
+
+# Changes issue template
+maven.changes.issue.template = %URL%/%ISSUE%
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/changes/src/plugin-resources/images rss.png
aheritier2004/07/07 15:41:10 Modified:changes/src/plugin-resources/images rss.png Log: ascii - binary Revision ChangesPath 1.3 +1 -1 maven-plugins/changes/src/plugin-resources/images/rss.png Binary file - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/javadoc/xdocs changes.xml properties.xml
aheritier2004/07/07 16:01:13
Modified:javadoc plugin.jelly plugin.properties
javadoc/xdocs changes.xml properties.xml
Log:
PR: MPJAVADOC-30
Submitted by: Maarten Coene
Reviewed by: Arnaud Heritier
Use the property 'maven.javadoc.excludepackagenames' to exclude packages from
javadoc generation.
Revision ChangesPath
1.49 +34 -29maven-plugins/javadoc/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/javadoc/plugin.jelly,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- plugin.jelly 7 Jul 2004 21:55:27 - 1.48
+++ plugin.jelly 7 Jul 2004 23:01:12 - 1.49
@@ -46,41 +46,42 @@
==
=== java plugin properties ===
==
-maven.compile.encoding = [${maven.compile.encoding}]
+maven.compile.encoding= [${maven.compile.encoding}]
==
=== javadoc plugin properties ===
==
-maven.javadoc.additionalparam = [${maven.javadoc.additionalparam}]
-maven.javadoc.author= [${maven.javadoc.author}]
-maven.javadoc.customtags= [${maven.javadoc.customtags}]
-maven.javadoc.debug = [${maven.javadoc.debug}]
-maven.javadoc.destdir = [${maven.javadoc.destdir}]
-maven.javadoc.doclet= [${maven.javadoc.doclet}]
-maven.javadoc.docletpath= [${maven.javadoc.docletpath}]
-maven.javadoc.links = [${maven.javadoc.links}]
-maven.javadoc.locale= [${maven.javadoc.locale}]
-maven.javadoc.maxmemory = [${maven.javadoc.maxmemory}]
-maven.javadoc.mode.online = [${maven.javadoc.mode.online}]
-maven.javadoc.offlineLinks = [${maven.javadoc.offlineLinks}]
-maven.javadoc.overview = [${maven.javadoc.overview}]
-maven.javadoc.package = [${maven.javadoc.package}]
-maven.javadoc.private = [${maven.javadoc.private}]
-maven.javadoc.public= [${maven.javadoc.public}]
-maven.javadoc.source= [${maven.javadoc.source}]
-maven.javadoc.stylesheet= [${maven.javadoc.stylesheet}]
-maven.javadoc.tagletpath= [${maven.javadoc.tagletpath}]
-maven.javadoc.taglets = [${maven.javadoc.taglets}]
-maven.javadoc.use = [${maven.javadoc.use}]
-maven.javadoc.useexternalfile = [${maven.javadoc.useexternalfile}]
-maven.javadoc.version = [${maven.javadoc.version}]
-maven.javadoc.windowtitle = [${maven.javadoc.windowtitle}]
+maven.javadoc.additionalparam = [${maven.javadoc.additionalparam}]
+maven.javadoc.author = [${maven.javadoc.author}]
+maven.javadoc.customtags = [${maven.javadoc.customtags}]
+maven.javadoc.debug = [${maven.javadoc.debug}]
+maven.javadoc.destdir = [${maven.javadoc.destdir}]
+maven.javadoc.doclet = [${maven.javadoc.doclet}]
+maven.javadoc.docletpath = [${maven.javadoc.docletpath}]
+maven.javadoc.excludepackagenames = [${maven.javadoc.excludepackagenames}]
+maven.javadoc.links = [${maven.javadoc.links}]
+maven.javadoc.locale = [${maven.javadoc.locale}]
+maven.javadoc.maxmemory = [${maven.javadoc.maxmemory}]
+maven.javadoc.mode.online = [${maven.javadoc.mode.online}]
+maven.javadoc.offlineLinks= [${maven.javadoc.offlineLinks}]
+maven.javadoc.overview= [${maven.javadoc.overview}]
+maven.javadoc.package = [${maven.javadoc.package}]
+maven.javadoc.private = [${maven.javadoc.private}]
+maven.javadoc.public = [${maven.javadoc.public}]
+maven.javadoc.source = [${maven.javadoc.source}]
+maven.javadoc.stylesheet = [${maven.javadoc.stylesheet}]
+maven.javadoc.tagletpath = [${maven.javadoc.tagletpath}]
+maven.javadoc.taglets = [${maven.javadoc.taglets}]
+maven.javadoc.use = [${maven.javadoc.use}]
+maven.javadoc.useexternalfile = [${maven.javadoc.useexternalfile}]
+maven.javadoc.version = [${maven.javadoc.version}]
+maven.javadoc.windowtitle = [${maven.javadoc.windowtitle}]
==
=== javadoc internal variables ===
==
-internal.javadoc.jar= [${internal.javadoc.jar}]
-internal.javadoc.needed = [${internal.javadoc.needed}]
-internal.javadoc.src.set= [${internal.javadoc.src.set}]
-internal.javadoc.working.dir= [${internal.javadoc.working.dir}]
+internal.javadoc.jar = [${internal.javadoc.jar}]
+internal.javadoc.needed = [${internal.javadoc.needed}]
+internal.javadoc.src.set =
[jira] Closed: (MPJAVADOC-30) exclude packages from javadoc generation
Message: The following issue has been closed. Resolver: Arnaud HERITIER Date: Wed, 7 Jul 2004 7:01 PM Applied. Thanks. - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-30 Here is an overview of the issue: - Key: MPJAVADOC-30 Summary: exclude packages from javadoc generation Type: New Feature Status: Closed Priority: Major Resolution: FIXED Original Estimate: 15 minutes Time Spent: Unknown Remaining: 15 minutes Project: maven-javadoc-plugin Fix Fors: 1.5.1 Assignee: Arnaud HERITIER Reporter: Maarten Coene Created: Tue, 29 Jun 2004 8:03 AM Updated: Wed, 7 Jul 2004 7:01 PM Description: Hi, I don't want to generate javadocs for all packages of my sources. I'll upload a patch that allows the user to specify a list of package names that are excluded from javadoc generation. For instance, to exclude javadocs for package com.foo and com.foo1, the user can specify this property in the project.properties file: maven.javadoc.excludepackagenames = com.foo,com.foo1 The generated javadocs won't contain these packages... 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]
[jira] Closed: (MPJAVADOC-16) Failure to generate relative cross-references to local classess.
Message: The following issue has been closed. Resolver: Arnaud HERITIER Date: Wed, 7 Jul 2004 7:06 PM The use of file set is removed. - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-16 Here is an overview of the issue: - Key: MPJAVADOC-16 Summary: Failure to generate relative cross-references to local classess. Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: 1 day Time Spent: Unknown Remaining: 1 day Project: maven-javadoc-plugin Fix Fors: 1.5.1 Assignee: Arnaud HERITIER Reporter: Alain Javier Guarnieri del Gesu Created: Thu, 4 Dec 2003 11:55 AM Updated: Wed, 7 Jul 2004 7:06 PM Environment: Macintosh OS X 10.2, JDK 1.41 Description: I just pulled and build maven from cvs. Unlike the Javadoc at http://maven.apache.org/apidocs/index.html, my local build of Maven DID NOT generate cross-reference links to classes within the same package under the package heirarchy of org.apache.maven.* I've fixed this locally, by copying the Javadoc source files to a temporary directory based on the includes and excludes. It seems that the Javadoc Ant task will not generate cross-references when source files are specified using a file set. Of course, I could specify a link to the project Javadoc, but that requires an absolute path and does not generate Javadoc suitable for redistribution. I've read the build.properties file that comes with Maven, I've built Maven locally, I can't see why the Maven site has cross-reference links and my checkout build doesn't. - 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: (MPJAVADOC-15) [Javadoc Plugin] Javadoc link should maintain the documentation header
Message: The following issue has been closed. Resolver: Arnaud HERITIER Date: Wed, 7 Jul 2004 7:11 PM Now the javadoc is opened in a new window. - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-15 Here is an overview of the issue: - Key: MPJAVADOC-15 Summary: [Javadoc Plugin] Javadoc link should maintain the documentation header Type: Improvement Status: Closed Priority: Minor Resolution: WON'T FIX Original Estimate: 1 hour Time Spent: Unknown Remaining: 1 hour Project: maven-javadoc-plugin Fix Fors: 1.5.1 Assignee: Peter Lynch Reporter: Peter Lynch Created: Fri, 14 Feb 2003 2:38 PM Updated: Wed, 7 Jul 2004 7:11 PM Description: When clicking the Javadoc link, we should integrate the javadoc into the documentation header forthe rest of the site. So the result would be the Javadoc on the bottom, the regular maven header on top. - 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: [vote] plugin releases
+1 I'll make the AspectJ 3.1.1 tomorrow. Thanks Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 07, 2004 5:03 PM To: 'Maven Developers List' Subject: RE: [vote] plugin releases -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: mercredi 7 juillet 2004 13:10 To: Maven Developers List Subject: [vote] plugin releases Doesn't seem so long since I was last doing this :) I would like to release the following plugins as they've had reasonable changes artifact gump javadoc jcoverage xdoc +1 You'll also need to release the announcement plugin then as the download report now also generate release notes. That said, there's probably a better way of doing this (maybe by considering release notes as an artifact type). Still if you wish to release the very latest code of the xdoc plugin you also need to release the latest code of the announcement plugin. Also, I'd like to release the following quietly to update the commons-* dependencies and reduce the download size of maven site: antlr jira jxr latex latka linkcheck site +1 I think the following should be polished and released by others before 1.0: abbot (Vincent) It's actually ready to be released in a 1.0 version. I'll do this tomorrow. hibernate (Eric) jnlp (Emmanuel) nsis (Dion) The following have changed, and anyone interested in the fixes should put forward a release for them, however I'm not planning to wait on 1.0 for them: announcement, ant, appserver, aspectj, changes, checkstyle, dist, eclipse, ejb, jalopy, jboss, webserver I can do (tomorrow) the changes one + the jboss one. I'll let Carlos handle the aspectj one ;-) How does this sound? I'll now turn my attention to documentation again, including some of my recent changes I've been a little slack with. 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: [vote] plugin releases
-Message d'origine- De : Brett Porter [mailto:[EMAIL PROTECTED] Envoyé : mercredi 7 juillet 2004 13:10 À : Maven Developers List Objet : [vote] plugin releases Doesn't seem so long since I was last doing this :) I would like to release the following plugins as they've had reasonable changes artifact gump javadoc jcoverage xdoc +1. I applied all changes in the javadoc plugin. If nobody finds a problem in the next days you can release it. Also, I'd like to release the following quietly to update the commons-* dependencies and reduce the download size of maven site: antlr jira jxr latex latka linkcheck site +1 I think the following should be polished and released by others before 1.0: abbot (Vincent) hibernate (Eric) jnlp (Emmanuel) nsis (Dion) The following have changed, and anyone interested in the fixes should put forward a release for them, however I'm not planning to wait on 1.0 for them: announcement, ant, appserver, aspectj, changes, checkstyle, dist, eclipse, ejb, jalopy, jboss, webserver How does this sound? I think that the new announcement plugin is great. If we can release it ? I'll now turn my attention to documentation again, including some of my recent changes I've been a little slack with. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven-plugins/javadoc/xdocs changes.xml goals.xml index.xml navigation.xml properties.xml
Was there any discussion of removing this functionality?
I know I would have preferred another way around this.
On 7 Jul 2004 21:21:45 -, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
aheritier2004/07/07 14:21:45
Modified:javadoc plugin.jelly
javadoc/src/plugin-test maven.xml project.xml
javadoc/src/plugin-test/src/main/org/apache/maven
package.html
javadoc/src/plugin-test/src/main/org/apache/maven2
package.html
javadoc/src/plugin-test/src/opt/org/apache/maven3
package.html
javadoc/xdocs changes.xml goals.xml index.xml navigation.xml
properties.xml
Log:
Remove sourceModifications management in the plugin.
It created a lot of problems (MPJAVADOC-28, MPJAVADOC-29).
Revision ChangesPath
1.47 +9 -81 maven-plugins/javadoc/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/javadoc/plugin.jelly,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- plugin.jelly 7 Jul 2004 10:00:15 - 1.46
+++ plugin.jelly 7 Jul 2004 21:21:45 - 1.47
@@ -36,7 +36,6 @@
!-- internal variables --
j:set var=internal.javadoc.jar
value=${maven.build.dir}/${maven.final.name}_javadoc.jar/
j:set var=internal.javadoc.neededvalue=null/
-j:set var=internal.javadoc.src.modifsvalue=false/
j:set var=internal.javadoc.src.set
value=${context.getAntProject().getReferences().get('maven.compile.src.set')}/
j:set var=internal.javadoc.working.dir
value=${maven.build.dir}/javadoc/
@@ -75,7 +74,6 @@
==
internal.javadoc.jar= [${internal.javadoc.jar}]
internal.javadoc.needed = [${internal.javadoc.needed}]
-internal.javadoc.src.modifs = [${internal.javadoc.src.modifs}]
internal.javadoc.src.set= [${internal.javadoc.src.set}]
internal.javadoc.working.dir= [${internal.javadoc.working.dir}]
/ant:echo
@@ -99,61 +97,29 @@
j:when test=${internal.javadoc.needed != null}
!-- We have already decided if javadoc is needed --
- j:if
test=${maven.javadoc.debug}ant:echo${internal.javadoc.needed} not
null/ant:echo/j:if
+ j:if test=${maven.javadoc.debug}ant:echointernal.javadoc.needed
not null : ${internal.javadoc.needed}/ant:echo/j:if
/j:when
-j:otherwise
- !-- Create a patternset for source modifications --
- patternset id=source.modifications
-ant:include name=**/*.java/
-!-- handle source modifications --
-j:forEach var=sm items=${pom.build.sourceModifications}
- ant:available property=classPresent classname=${sm.className}/
- j:if test=${classPresent != 'true'}
-j:forEach var=exclude items=${sm.excludes}
- ant:exclude name=${exclude}/
-/j:forEach !-- end sourceModification exclude --
-j:forEach var=include items=${sm.includes}
- ant:include name=${include}/
-/j:forEach !-- end sourceModification include --
- /j:if
-/j:forEach !-- end sourceModification --
- /patternset
-
- !-- test if sourceModifications are defined --
- j:if test=${pom.build.sourceModifications != null amp;amp;
!pom.build.sourceModifications.isEmpty()}
-j:set var=internal.javadoc.src.modifs scope=parent value=true/
- /j:if
-
- j:if test=${maven.javadoc.debug}
-ant:echointernal.javadoc.src.modifs is
${internal.javadoc.src.modifs}/ant:echo
- /j:if
+j:otherwise
!-- Tokenize the set of directories --
util:tokenize var=sources.dirs
delim=${path.separator}${internal.javadoc.src.set}/util:tokenize
-
- !-- Counter used to name filesets --
- j:set var=src.set.counter value=0/
-
+
!-- For each directory --
j:forEach var=dir items=${sources.dirs}
!-- If we have not already find sources --
j:if test=${internal.javadoc.needed != true}
!-- We construct the fileset --
- ant:fileset id=${src.set.counter} dir=${dir}
-patternset refid=source.modifications/
- /ant:fileset
ant:fileScanner var=sources
-ant:fileset refid=${src.set.counter} /
+ant:fileset dir=${dir} include=**/*.java/
/ant:fileScanner
cvs commit: maven-plugins/nsis/xdocs changes.xml
dion2004/07/07 18:00:00
Modified:nsis/xdocs changes.xml
Log:
[maven-scm-plugin] prepare release 1.1
Revision ChangesPath
1.9 +8 -13 maven-plugins/nsis/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/nsis/xdocs/changes.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- changes.xml 7 Jul 2004 21:02:39 - 1.8
+++ changes.xml 8 Jul 2004 01:00:00 - 1.9
@@ -24,22 +24,17 @@
author email=[EMAIL PROTECTED]Brett Porter/author
/properties
body
-release version=1.1-SNAPSHOT date=in CVS
- action dev=dion type=fix issue=MPNSIS-7 due-to=Geoffrey
-Desktop shortcuts cause a compile error
- /action
+release version=1.1 date=2004-07-08
+ action dev=dion type=fix issue=MPNSIS-7 due-to=GeoffreyDesktop
shortcuts cause a compile error/action
action dev=dion type=fixUse pom.organization.name instead of
pom.organization./action
- action dev=dion type=update issue=MPNSIS-6 due-to=Geoffrey
-Add PROJECT_URL to constants.
- /action
+ action dev=dion type=update issue=MPNSIS-6 due-to=GeoffreyAdd
PROJECT_URL to constants./action
action dev=dion type=fixFix typo in registry uninstall key./action
- action dev=dion type=fix issue=MPNSIS-2 due-to=Geoffrey
-Generate exe in distributions directory.
- /action
- action dev=dion type=update
-Rename codePROJECT_DIST_DIR/code constant to
+ action dev=dion type=fix issue=MPNSIS-2 due-to=GeoffreyGenerate exe
in distributions directory./action
+ action dev=dion type=updateRename
+codePROJECT_DIST_DIR/codeconstant to
codePROJECT_DIST_BIN_DIR/code, and define
-codePROJECT_DIST_DIR/code to be code${maven.dist.dir/code
+codePROJECT_DIST_DIR/codeto be
+code${maven.dist.dirgt;/code
/action
action dev=dion type=updateAdd docs on how the plugin process
works/action
action dev=dion type=updateAdd some basic documentation/action
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Releasing plugins
When I was doing the release for the NSIS plugin today, I got the following: BUILD FAILED File.. C:\Documents and Settings\Dion Gillard\.maven\cache\maven-scm-plugin-1.4.1-SNAPSHOT\plugin.jelly Element... maven:maven Line.. 158 Column 9 Unable to obtain goal [plugin:repository-deploy] -- C:\Documents and Settings\Dion Gillard\.maven\cache\maven-artifact-plugin-1.4-SN APSHOT\plugin.jelly:323:67: ant:exec null returned: 1 Total time: 28 seconds when running the plugin:repository-deploy step. Is this supposed to work or is our documentation wrong? -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis project.xml
dion2004/07/07 18:13:33 Modified:nsis project.xml Log: For some reason scm:prepare-release doesn't change to POM to remove the -SNAPSHOT Revision ChangesPath 1.10 +12 -20maven-plugins/nsis/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/nsis/project.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- project.xml 2 Jul 2004 08:13:50 - 1.9 +++ project.xml 8 Jul 2004 01:13:33 - 1.10 @@ -1,29 +1,13 @@ ?xml version=1.0 encoding=UTF-8? -!-- -/* - * 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. - */ - -- - project extend../plugin-parent/project.xml/extend pomVersion3/pomVersion - idmaven-nsis-plugin/id nameMaven NSIS Plug-in/name - currentVersion1.1-SNAPSHOT/currentVersion + groupIdmaven-nsis-plugin/groupId + artifactIdmaven-nsis-plugin/artifactId + currentVersion1.1/currentVersion + organization/ descriptionA plugin to generate Win32 installer programs using NSIS/description shortDescriptionNSIS Plugin for Maven/shortDescription urlhttp://maven.apache.org/reference/plugins/nsis//url @@ -40,7 +24,14 @@ name1.0/name tagMAVEN_NSIS_1_0/tag /version +version + id1.1/id + name1.1/name + tagMAVEN_NSIS_1_1/tag +/version /versions + branches/ + mailingLists/ developers developer namedIon Gillard/name @@ -52,4 +43,5 @@ /roles /developer /developers + properties/ /project - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven NSIS Plugin release
The maven-nsis-plugin team is pleased to announce the Maven NSIS Plug-in 1.1
release!
http://maven.apache.org/reference/plugins/nsis/
A plugin to generate Win32 installer programs using NSIS
Changes in this version include:
Fixed bugs:
o Desktop shortcuts cause a compile error Issue: MPNSIS-7. Thanks to
Geoffrey.
o Use pom.organization.name instead of pom.organization.
o Fix typo in registry uninstall key.
o Generate exe in distributions directory. Issue: MPNSIS-2. Thanks to
Geoffrey.
Changes:
o Add PROJECT_URL to constants. Issue: MPNSIS-6. Thanks to Geoffrey.
o Rename PROJECT_DIST_DIRconstant to PROJECT_DIST_BIN_DIR, and define
PROJECT_DIST_DIRto be ${maven.dist.dir};
o Add docs on how the plugin process works
o Add some basic documentation
To automatically install the plugin, type the following on a single line:
maven plugin:download
-DgroupId=maven
-DartifactId=maven-nsis-plugin
-Dversion=1.1
For a manual installation, you can download the plugin here:
http://www.ibiblio.org/maven/maven-nsis-plugin/plugins/maven-nsis-plugin-1.1.jar
--
http://www.multitask.com.au/people/dion/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPPLUGIN-23) plugin:repository-deploy doesn't create an md5 file
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPPLUGIN-23 Here is an overview of the issue: - Key: MPPLUGIN-23 Summary: plugin:repository-deploy doesn't create an md5 file Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-plugin-plugin Versions: 1.6 Assignee: dion gillard Reporter: dion gillard Created: Wed, 7 Jul 2004 9:39 PM Updated: Wed, 7 Jul 2004 9:39 PM Description: - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPPLUGIN-22) plugin:repository-deploy uses blank groupId
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPPLUGIN-22 Here is an overview of the issue: - Key: MPPLUGIN-22 Summary: plugin:repository-deploy uses blank groupId Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-plugin-plugin Versions: 1.6 Assignee: dion gillard Reporter: dion gillard Created: Wed, 7 Jul 2004 9:38 PM Updated: Wed, 7 Jul 2004 9:38 PM Description: run 'maven plugin:repository-deploy' from any maven-plugins plugin, e.g.nsis - 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/artifact/xdocs tags.xml
dion2004/07/07 18:47:52 Modified:artifact/xdocs tags.xml Log: Fix typo Revision ChangesPath 1.6 +2 -2 maven-plugins/artifact/xdocs/tags.xml Index: tags.xml === RCS file: /home/cvs/maven-plugins/artifact/xdocs/tags.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- tags.xml 8 Apr 2004 00:54:54 - 1.5 +++ tags.xml 8 Jul 2004 01:47:52 - 1.6 @@ -77,7 +77,7 @@ tdtype/td tdThe type of the artifact (like ijar/i or iwar/i or iplugin/i). Type is used for - computing a detination path in repository. + computing a destination path in repository. /td tdNo/td /tr @@ -181,7 +181,7 @@ tdtype/td tdThe type of the artifact (like ijar/i or iwar/i). Type is used for - computing a detination path in repository. + computing a destination path in repository. /td tdNo/td /tr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs changes.xml
dion2004/07/07 18:50:30 Modified:nsis project.xml nsis/xdocs changes.xml Log: Add back license to project.xml after the scm plugin removed it. Revision ChangesPath 1.11 +18 -2 maven-plugins/nsis/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/nsis/project.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- project.xml 8 Jul 2004 01:13:33 - 1.10 +++ project.xml 8 Jul 2004 01:50:30 - 1.11 @@ -1,12 +1,28 @@ ?xml version=1.0 encoding=UTF-8? - +!-- +/* + * 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. + */ + -- project extend../plugin-parent/project.xml/extend pomVersion3/pomVersion nameMaven NSIS Plug-in/name groupIdmaven-nsis-plugin/groupId artifactIdmaven-nsis-plugin/artifactId - currentVersion1.1/currentVersion + currentVersion1.2-SNAPSHOT/currentVersion organization/ descriptionA plugin to generate Win32 installer programs using NSIS/description shortDescriptionNSIS Plugin for Maven/shortDescription 1.10 +7 -0 maven-plugins/nsis/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/nsis/xdocs/changes.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- changes.xml 8 Jul 2004 01:00:00 - 1.9 +++ changes.xml 8 Jul 2004 01:50:30 - 1.10 @@ -24,6 +24,13 @@ author email=[EMAIL PROTECTED]Brett Porter/author /properties body + +release version=1.2-SNAPSHOT date=Unreleased + action dev=dion type=update +Add back license to project.xml after the scm plugin removed it. + /action +/release + release version=1.1 date=2004-07-08 action dev=dion type=fix issue=MPNSIS-7 due-to=GeoffreyDesktop shortcuts cause a compile error/action action dev=dion type=fixUse pom.organization.name instead of pom.organization./action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis project.xml
dion2004/07/07 18:51:12 Modified:nsis project.xml Log: Make groupId maven. Revision ChangesPath 1.12 +1 -1 maven-plugins/nsis/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/nsis/project.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- project.xml 8 Jul 2004 01:50:30 - 1.11 +++ project.xml 8 Jul 2004 01:51:12 - 1.12 @@ -20,7 +20,7 @@ extend../plugin-parent/project.xml/extend pomVersion3/pomVersion nameMaven NSIS Plug-in/name - groupIdmaven-nsis-plugin/groupId + groupIdmaven/groupId artifactIdmaven-nsis-plugin/artifactId currentVersion1.2-SNAPSHOT/currentVersion organization/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis project.xml
dion2004/07/07 18:51:40 Modified:nsis project.xml Log: groupId is in the parent project Revision ChangesPath 1.13 +0 -1 maven-plugins/nsis/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/nsis/project.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- project.xml 8 Jul 2004 01:51:12 - 1.12 +++ project.xml 8 Jul 2004 01:51:40 - 1.13 @@ -20,7 +20,6 @@ extend../plugin-parent/project.xml/extend pomVersion3/pomVersion nameMaven NSIS Plug-in/name - groupIdmaven/groupId artifactIdmaven-nsis-plugin/artifactId currentVersion1.2-SNAPSHOT/currentVersion organization/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Releasing plugins
Running which goal? What was the actual error? It has always worked for me, with the exception of the occasional cvs: protocol error data discarded, by which you just have to run it again (CVS server bug). - Brett Quoting Dion Gillard [EMAIL PROTECTED]: When I was doing the release for the NSIS plugin today, I got the following: BUILD FAILED File.. C:\Documents and Settings\Dion Gillard\.maven\cache\maven-scm-plugin-1.4.1-SNAPSHOT\plugin.jelly Element... maven:maven Line.. 158 Column 9 Unable to obtain goal [plugin:repository-deploy] -- C:\Documents and Settings\Dion Gillard\.maven\cache\maven-artifact-plugin-1.4-SN APSHOT\plugin.jelly:323:67: ant:exec null returned: 1 Total time: 28 seconds when running the plugin:repository-deploy step. Is this supposed to work or is our documentation wrong? -- 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]
Re: [vote] plugin releases
Quoting Dion Gillard [EMAIL PROTECTED]: I'm happy to do changes to the latka plugin if u like, and release it. That'd be great. I haven't had a chance to test all those yet (was going to), so I'd appreciate it if you could check the commons-* upgrade didn't break anything. I think the plugin plugin has changed too. Wasn't that just a test change? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE : [vote] plugin releases
Can you release it when ready? Thanks. - Brett Quoting Heritier Arnaud [EMAIL PROTECTED]: Hello Brett. Can you wait 2 or 3 days before to release the javadoc plugin. I would like to remove the usage of sourceModifications which creates a lot of problems. I think it is the better solution as we talked about it in the thread Javadoc Plugin Change - What is better ? After that I'll close the issues MPJAVADOC-28 and MPJAVADOC-29. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPPLUGIN-23) plugin:repository-deploy doesn't create an md5 file
Message: The following issue has been closed. Resolver: Brett Porter Date: Wed, 7 Jul 2004 11:41 PM it does if you don't use the legacy deploy mechanism from the artifact plugin. This is more a documentation issue than anything. - View the issue: http://jira.codehaus.org/browse/MPPLUGIN-23 Here is an overview of the issue: - Key: MPPLUGIN-23 Summary: plugin:repository-deploy doesn't create an md5 file Type: Bug Status: Closed Priority: Major Resolution: INCOMPLETE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-plugin-plugin Versions: 1.6 Assignee: dion gillard Reporter: dion gillard Created: Wed, 7 Jul 2004 9:39 PM Updated: Wed, 7 Jul 2004 11:41 PM Description: - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPPLUGIN-22) plugin:repository-deploy uses blank groupId
The following comment has been added to this issue: Author: Brett Porter Created: Wed, 7 Jul 2004 11:40 PM Body: are you sure? It should use pom.groupId. Was it because of your various groupId mishaps with nsis? - View this comment: http://jira.codehaus.org/browse/MPPLUGIN-22?page=comments#action_21496 - View the issue: http://jira.codehaus.org/browse/MPPLUGIN-22 Here is an overview of the issue: - Key: MPPLUGIN-22 Summary: plugin:repository-deploy uses blank groupId Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-plugin-plugin Versions: 1.6 Assignee: dion gillard Reporter: dion gillard Created: Wed, 7 Jul 2004 9:38 PM Updated: Wed, 7 Jul 2004 11:40 PM Description: run 'maven plugin:repository-deploy' from any maven-plugins plugin, e.g.nsis - 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-22) plugin:repository-deploy uses blank groupId
The following comment has been added to this issue: Author: dion gillard Created: Wed, 7 Jul 2004 11:49 PM Body: Will do it again, but at no time should the groupId been blank. id was set before... Using: project extend../plugin-parent/project.xml/extend pomVersion3/pomVersion nameMaven NSIS Plug-in/name artifactIdmaven-nsis-plugin/artifactId currentVersion1.2-SNAPSHOT/currentVersion organization/ produces: plugin:repository-deploy: [echo] maven.repo.list is not set - using legacy deploy mode [echo] DEPRECATED: use of deploy:artifact tag and the legacy deploy method are deprecated [echo] Copying project.xml to the /www/www.apache.org/dist/java-repository//maven/poms on www.apache.org Maybe I'm mistaking //maven for an empty group??? - View this comment: http://jira.codehaus.org/browse/MPPLUGIN-22?page=comments#action_21498 - View the issue: http://jira.codehaus.org/browse/MPPLUGIN-22 Here is an overview of the issue: - Key: MPPLUGIN-22 Summary: plugin:repository-deploy uses blank groupId Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-plugin-plugin Versions: 1.6 Assignee: dion gillard Reporter: dion gillard Created: Wed, 7 Jul 2004 9:38 PM Updated: Wed, 7 Jul 2004 11:49 PM Description: run 'maven plugin:repository-deploy' from any maven-plugins plugin, e.g.nsis - 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-23) plugin:repository-deploy doesn't create an md5 file
The following comment has been added to this issue: Author: dion gillard Created: Wed, 7 Jul 2004 11:50 PM Body: In that case, we have a bug in the plugin's project.properties, or the plugin-parent's project.properties, in that we're not specify a repo list, right? - View this comment: http://jira.codehaus.org/browse/MPPLUGIN-23?page=comments#action_21499 - View the issue: http://jira.codehaus.org/browse/MPPLUGIN-23 Here is an overview of the issue: - Key: MPPLUGIN-23 Summary: plugin:repository-deploy doesn't create an md5 file Type: Bug Status: Closed Priority: Major Resolution: INCOMPLETE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-plugin-plugin Versions: 1.6 Assignee: dion gillard Reporter: dion gillard Created: Wed, 7 Jul 2004 9:39 PM Updated: Wed, 7 Jul 2004 11:50 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]
Re: Releasing plugins
On Thu, 8 Jul 2004 13:16:38 +1000, Brett Porter [EMAIL PROTECTED] wrote: Running which goal? What was the actual error? scm:perform-release, during the plugin:repository-deploy step. It has always worked for me, with the exception of the occasional cvs: protocol error data discarded, by which you just have to run it again (CVS server bug). This happened, and the above was on the second and third runs. Quoting Dion Gillard [EMAIL PROTECTED]: When I was doing the release for the NSIS plugin today, I got the following: BUILD FAILED File.. C:\Documents and Settings\Dion Gillard\.maven\cache\maven-scm-plugin-1.4.1-SNAPSHOT\plugin.jelly Element... maven:maven Line.. 158 Column 9 Unable to obtain goal [plugin:repository-deploy] -- C:\Documents and Settings\Dion Gillard\.maven\cache\maven-artifact-plugin-1.4-SN APSHOT\plugin.jelly:323:67: ant:exec null returned: 1 Total time: 28 seconds when running the plugin:repository-deploy step. Is this supposed to work or is our documentation wrong? -- 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] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] plugin releases
On Thu, 8 Jul 2004 13:21:34 +1000, Brett Porter [EMAIL PROTECTED] wrote: Quoting Dion Gillard [EMAIL PROTECTED]: I think the plugin plugin has changed too. No. action dev=dion type=add issue=MPPLUGIN-20 Prompt for artifactId, groupId and version if missing. /action -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] plugin releases
This is on plugin:download? Right - I don't think I had that in CVS when I compiled the list. If you want to do a point release for it, that'd be fine. I'm really keen for the plugins to released on their own merits and Maven just bundle the latest. Now that the interactions and Maven API is stable enough, there's no reason they need to be mass updated again (except for dependency synchronisations, but I guess we'll just live with some getting behind and downloading more). - Brett Quoting Dion Gillard [EMAIL PROTECTED]: On Thu, 8 Jul 2004 13:21:34 +1000, Brett Porter [EMAIL PROTECTED] wrote: Quoting Dion Gillard [EMAIL PROTECTED]: I think the plugin plugin has changed too. No. action dev=dion type=add issue=MPPLUGIN-20 Prompt for artifactId, groupId and version if missing. /action -- 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]
Re: Releasing plugins
I can try it later... any more info you have above the FAILURE? -e output useful? - Brett Quoting Dion Gillard [EMAIL PROTECTED]: On Thu, 8 Jul 2004 13:16:38 +1000, Brett Porter [EMAIL PROTECTED] wrote: Running which goal? What was the actual error? scm:perform-release, during the plugin:repository-deploy step. It has always worked for me, with the exception of the occasional cvs: protocol error data discarded, by which you just have to run it again (CVS server bug). This happened, and the above was on the second and third runs. Quoting Dion Gillard [EMAIL PROTECTED]: When I was doing the release for the NSIS plugin today, I got the following: BUILD FAILED File.. C:\Documents and Settings\Dion Gillard\.maven\cache\maven-scm-plugin-1.4.1-SNAPSHOT\plugin.jelly Element... maven:maven Line.. 158 Column 9 Unable to obtain goal [plugin:repository-deploy] -- C:\Documents and Settings\Dion Gillard\.maven\cache\maven-artifact-plugin-1.4-SN APSHOT\plugin.jelly:323:67: ant:exec null returned: 1 Total time: 28 seconds when running the plugin:repository-deploy step. Is this supposed to work or is our documentation wrong? -- 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] -- 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] Closed: (MPPLUGIN-22) plugin:repository-deploy uses blank groupId
Message: The following issue has been closed. Resolver: Brett Porter Date: Thu, 8 Jul 2004 12:10 AM yep. maven is the group, poms is the type /java-repository/ is the base. Did it fail? - View the issue: http://jira.codehaus.org/browse/MPPLUGIN-22 Here is an overview of the issue: - Key: MPPLUGIN-22 Summary: plugin:repository-deploy uses blank groupId Type: Bug Status: Closed Priority: Major Resolution: INCOMPLETE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-plugin-plugin Versions: 1.6 Assignee: dion gillard Reporter: dion gillard Created: Wed, 7 Jul 2004 9:38 PM Updated: Thu, 8 Jul 2004 12:10 AM Description: run 'maven plugin:repository-deploy' from any maven-plugins plugin, e.g.nsis - 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/nsis/xdocs faq.fml
dion2004/07/07 21:19:05
Added: nsis/xdocs faq.fml
Log:
Add FAQ thanks to geoffrey
Revision ChangesPath
1.1 maven-plugins/nsis/xdocs/faq.fml
Index: faq.fml
===
?xml version=1.0 encoding=UTF-8?
faqs title=Frequently Asked Questions
part id=installing
titleInstalling/title
faq id=installing.files
question
Which files are installed into the installation directory?
/question
answer
p
With the default templates, all the files from the directory denoted by the
codemaven.dist.bin.assembly.dir/code property are installed,
together with an uninstaller if the end-user so desires.
/p
p
If you call the dist goal before calling the nsis goal,
it will set the property correctly and generate files into that directory.
/p
/answer
/faq
faq id=installing.includeJvm
question
Can I include a jvm in my installer?
/question
answer
p
The default templates currently doesn't support this.
It does however support a nsis script function called
codeAssertJavaHome/code,
which you can run before installing. See the documentation.
/p
p
There is nothing stopping you to write a template that includes a jvm.
And there is nothing stopping you to contribute it to the Maven community
either :)
/p
/answer
/faq
faq id=installing.dynamicShortcuts
question
Can I make my shortcuts dynamic based on my pom properties?
/question
answer
p
The default templates mirror a few pom properties into the NSIS script.
Using them you can set the start menu shortcuts like this:
/p
source
CreateShortCut ${PROJECT_STARTMENU_FOLDER}\${PROJECT_NAME} ${PROJECT_VERSION}.lnk
$INSTDIR\${PROJECT_FINAL_NAME}.jar
CreateShortCut ${PROJECT_STARTMENU_FOLDER}\Uninstall ${PROJECT_NAME}
${PROJECT_VERSION}.lnk $INSTDIR\Uninst.exe
CreateShortCut ${PROJECT_STARTMENU_FOLDER}\${PROJECT_NAME} site.lnk
${PROJECT_URL}
/source
/answer
/faq
/part
part id=troubleshooting
titleTroubleshooting/title
faq id=troubleshooting.execCommandSection
question
Why am I getting code[exec] Error: command Section not valid in
section/code
when I run the codensis/code goal?
/question
answer
p
For the nsis plugin to work, nsis must be installed on your system
and the codemaven.nsis.exe/code property must be set correctly.
You can download nsis from a href=http://nsis.sourceforge.net;
target=_new/.
If you installed nsis to the default directory, the
codemaven.nsis.exe/code property
will have the correct value by default, otherwise you must set it
accordingly,
for example:
/p
source
maven.nsis.exe=C:/develop/build/NSIS/makensis.exe
/source
p
As the NSIS installation directory is probably different between you and
other team
members, it is best to set this in codebuild.properties/code.
/p
/answer
/faq
faq id=troubleshooting.assemblyDir
question
Why am I getting codeorg.apache.commons.jelly.JellyTagException: ...
'maven.dist.bin.assembly.dir' must be specified .../code
when I run the codensis/code goal?
/question
answer
p
The nsis goal counts on the codemaven.dist.bin.assembly.dir/code
property being set.
Normally the dist goal does this. You could also pass it in when running
the goal, e.g.
/p
sourcemaven -Dmaven.dist.bin.assembly.dir=c:/develop/build/files
nsis/source
/answer
/faq
/part
/faqs
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs changes.xml
dion2004/07/07 21:19:44 Modified:nsis/xdocs changes.xml Log: Add FAQ thanks to geoffrey Revision ChangesPath 1.11 +1 -0 maven-plugins/nsis/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/nsis/xdocs/changes.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- changes.xml 8 Jul 2004 01:50:30 - 1.10 +++ changes.xml 8 Jul 2004 04:19:44 - 1.11 @@ -26,6 +26,7 @@ body release version=1.2-SNAPSHOT date=Unreleased + action dev=dion type=add due-to=GeoffreyAdd faq/action action dev=dion type=update Add back license to project.xml after the scm plugin removed it. /action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs changes.xml
dion2004/07/07 21:34:14
Modified:nsis plugin.jelly
nsis/xdocs changes.xml
Log:
Check maven.nsis.exe exists before using it.
Revision ChangesPath
1.8 +4 -1 maven-plugins/nsis/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/nsis/plugin.jelly,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- plugin.jelly 4 Jul 2004 14:27:30 - 1.7
+++ plugin.jelly 8 Jul 2004 04:34:14 - 1.8
@@ -21,7 +21,6 @@
project
xmlns:j=jelly:core
xmlns:ant=jelly:ant
- xmlns:dist=dist
xmlns:license=license
xmlns:maven=jelly:maven
xmlns:util=jelly:util
@@ -77,6 +76,10 @@
j:set var=script value=${maven.build.dir}/setup.nsi/
+util:file var=nsisExeFile name=${maven.nsis.exe} /
+j:if test=${!nsisExeFile.exists()}
+ failThe NSIS executable '${maven.nsis.exe}' could not be found/fail
+/j:if
maven:get var=maven.dist.dir plugin=maven-dist-plugin
property=maven.dist.dir/
mkdir dir=${maven.dist.dir}/
!-- call makensis.exe with the setup.nsi file --
1.12 +1 -0 maven-plugins/nsis/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/nsis/xdocs/changes.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- changes.xml 8 Jul 2004 04:19:44 - 1.11
+++ changes.xml 8 Jul 2004 04:34:14 - 1.12
@@ -26,6 +26,7 @@
body
release version=1.2-SNAPSHOT date=Unreleased
+ action dev=dion type=fix due-to=GeoffreyCheck maven.nsis.exe exists
before using it./action
action dev=dion type=add due-to=GeoffreyAdd faq/action
action dev=dion type=update
Add back license to project.xml after the scm plugin removed it.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] plugin releases
On Thu, 8 Jul 2004 14:07:20 +1000, Brett Porter [EMAIL PROTECTED] wrote: This is on plugin:download? Yep. Right - I don't think I had that in CVS when I compiled the list. If you want to do a point release for it, that'd be fine. I'm really keen for the plugins to released on their own merits and Maven just bundle the latest. By point release, you mean changing it from 1.6-SNAPSHOT to 1.5.1-SNAPSHOT? -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPPLUGIN-22) plugin:repository-deploy uses blank groupId
The following comment has been added to this issue: Author: dion gillard Created: Thu, 8 Jul 2004 1:09 AM Body: No. plugin:repository-deploy: [echo] maven.repo.list is not set - using legacy deploy mode [echo] DEPRECATED: use of deploy:artifact tag and the legacy deploy method are deprecated [echo] Copying project.xml to the /www/www.apache.org/dist/java-repository//maven/poms on www.apache.org [exec] scp: x/www/www.apache.org/dist/java-repository//maven/poms/maven-nsis-plugin-1.2-SNAPSHOT.pom: Permission denied Seems the directory isn't group writable: drwxr-xr-x 2 brett apcvs512 Jun 28 05:26 . And the group is wrong - View this comment: http://jira.codehaus.org/browse/MPPLUGIN-22?page=comments#action_21503 - View the issue: http://jira.codehaus.org/browse/MPPLUGIN-22 Here is an overview of the issue: - Key: MPPLUGIN-22 Summary: plugin:repository-deploy uses blank groupId Type: Bug Status: Closed Priority: Major Resolution: INCOMPLETE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-plugin-plugin Versions: 1.6 Assignee: dion gillard Reporter: dion gillard Created: Wed, 7 Jul 2004 9:38 PM Updated: Thu, 8 Jul 2004 1:09 AM Description: run 'maven plugin:repository-deploy' from any maven-plugins plugin, e.g.nsis - 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: Releasing plugins
I think the other issue is related. The poms directory isn't group writeable and the group is wrong On Thu, 8 Jul 2004 14:08:33 +1000, Brett Porter [EMAIL PROTECTED] wrote: I can try it later... any more info you have above the FAILURE? -e output useful? - Brett Quoting Dion Gillard [EMAIL PROTECTED]: On Thu, 8 Jul 2004 13:16:38 +1000, Brett Porter [EMAIL PROTECTED] wrote: Running which goal? What was the actual error? scm:perform-release, during the plugin:repository-deploy step. It has always worked for me, with the exception of the occasional cvs: protocol error data discarded, by which you just have to run it again (CVS server bug). This happened, and the above was on the second and third runs. Quoting Dion Gillard [EMAIL PROTECTED]: When I was doing the release for the NSIS plugin today, I got the following: BUILD FAILED File.. C:\Documents and Settings\Dion Gillard\.maven\cache\maven-scm-plugin-1.4.1-SNAPSHOT\plugin.jelly Element... maven:maven Line.. 158 Column 9 Unable to obtain goal [plugin:repository-deploy] -- C:\Documents and Settings\Dion Gillard\.maven\cache\maven-artifact-plugin-1.4-SN APSHOT\plugin.jelly:323:67: ant:exec null returned: 1 Total time: 28 seconds when running the plugin:repository-deploy step. Is this supposed to work or is our documentation wrong? -- 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] -- 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] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cvs commit: maven-plugins/javadoc/xdocs changes.xml goals.xml index.xml navigation.xml properties.xml
Hello Dion,
We discussed a little bit on the thread Javadoc Plugin Change - What is better ?
I know that it was better if we can keep it but actually I (we?) have no solution to
do something clean.
The use of a fileset creates a lot of problems (MJAVADOC16, MPJAVADOC-28,
MPJAVADOC-29) that we can fix even if we add a lot of
tests to use a fileset only when needed.
I think that it is better actually to not implement the functionality and to not
create a lot of problems for users.
If someone find a solution to use the javadoc with a fileset which doesn't break the
standard functionalities, he's the welcome.
Arnaud
-Message d'origine-
De : Dion Gillard [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 8 juillet 2004 02:32
À : Maven Developers List
Objet : Re: cvs commit: maven-plugins/javadoc/xdocs changes.xml goals.xml index.xml
navigation.xml
properties.xml
Was there any discussion of removing this functionality?
I know I would have preferred another way around this.
On 7 Jul 2004 21:21:45 -, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
aheritier2004/07/07 14:21:45
Modified:javadoc plugin.jelly
javadoc/src/plugin-test maven.xml project.xml
javadoc/src/plugin-test/src/main/org/apache/maven
package.html
javadoc/src/plugin-test/src/main/org/apache/maven2
package.html
javadoc/src/plugin-test/src/opt/org/apache/maven3
package.html
javadoc/xdocs changes.xml goals.xml index.xml navigation.xml
properties.xml
Log:
Remove sourceModifications management in the plugin.
It created a lot of problems (MPJAVADOC-28, MPJAVADOC-29).
Revision ChangesPath
1.47 +9 -81 maven-plugins/javadoc/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/javadoc/plugin.jelly,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- plugin.jelly 7 Jul 2004 10:00:15 - 1.46
+++ plugin.jelly 7 Jul 2004 21:21:45 - 1.47
@@ -36,7 +36,6 @@
!-- internal variables --
j:set var=internal.javadoc.jar
value=${maven.build.dir}/${maven.final.name}_javadoc.jar/
j:set var=internal.javadoc.neededvalue=null/
-j:set var=internal.javadoc.src.modifsvalue=false/
j:set var=internal.javadoc.src.set
value=${context.getAntProject().getReferences().get('maven.compile.src.set')}/
j:set var=internal.javadoc.working.dir
value=${maven.build.dir}/javadoc/
@@ -75,7 +74,6 @@
==
internal.javadoc.jar= [${internal.javadoc.jar}]
internal.javadoc.needed = [${internal.javadoc.needed}]
-internal.javadoc.src.modifs = [${internal.javadoc.src.modifs}]
internal.javadoc.src.set= [${internal.javadoc.src.set}]
internal.javadoc.working.dir= [${internal.javadoc.working.dir}]
/ant:echo
@@ -99,61 +97,29 @@
j:when test=${internal.javadoc.needed != null}
!-- We have already decided if javadoc is needed --
- j:if
test=${maven.javadoc.debug}ant:echo${internal.javadoc.needed} not
null/ant:echo/j:if
+ j:if test=${maven.javadoc.debug}ant:echointernal.javadoc.needed
not null :
${internal.javadoc.needed}/ant:echo/j:if
/j:when
-j:otherwise
- !-- Create a patternset for source modifications --
- patternset id=source.modifications
-ant:include name=**/*.java/
-!-- handle source modifications --
-j:forEach var=sm items=${pom.build.sourceModifications}
- ant:available property=classPresent
classname=${sm.className}/
- j:if test=${classPresent != 'true'}
-j:forEach var=exclude items=${sm.excludes}
- ant:exclude name=${exclude}/
-/j:forEach !-- end sourceModification exclude --
-j:forEach var=include items=${sm.includes}
- ant:include name=${include}/
-/j:forEach !-- end sourceModification include --
- /j:if
-/j:forEach !-- end sourceModification --
- /patternset
-
- !-- test if sourceModifications are defined --
- j:if test=${pom.build.sourceModifications != null amp;amp;
!pom.build.sourceModifications.isEmpty()}
-j:set var=internal.javadoc.src.modifs scope=parent
value=true/
- /j:if
-
- j:if test=${maven.javadoc.debug}
-ant:echointernal.javadoc.src.modifs is
${internal.javadoc.src.modifs}/ant:echo
-
RE: RE : [vote] plugin releases
Ok Brett, if everybody is agree with the remove of sourceModifications usage. Dion? If it's ok, I'll do it tomorrow. Arnaud. -Message d'origine- De : Brett Porter [mailto:[EMAIL PROTECTED] Envoyé : jeudi 8 juillet 2004 15:07 À : Maven Developers List Objet : Re: RE : [vote] plugin releases Can you release it when ready? Thanks. - Brett Quoting Heritier Arnaud [EMAIL PROTECTED]: Hello Brett. Can you wait 2 or 3 days before to release the javadoc plugin. I would like to remove the usage of sourceModifications which creates a lot of problems. I think it is the better solution as we talked about it in the thread Javadoc Plugin Change - What is better ? After that I'll close the issues MPJAVADOC-28 and MPJAVADOC-29. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven-plugins/javadoc/xdocs changes.xml goals.xml index.xml navigation.xml properties.xml
Must've missed it.
Oh well, time to postGoal javadoc and do some deleting
On Thu, 8 Jul 2004 07:50:22 +0200, Arnaud Heritier [EMAIL PROTECTED] wrote:
Hello Dion,
We discussed a little bit on the thread Javadoc Plugin Change - What is better ?
I know that it was better if we can keep it but actually I (we?) have no solution to
do something clean.
The use of a fileset creates a lot of problems (MJAVADOC16, MPJAVADOC-28,
MPJAVADOC-29) that we can fix even if we add a lot of
tests to use a fileset only when needed.
I think that it is better actually to not implement the functionality and to not
create a lot of problems for users.
If someone find a solution to use the javadoc with a fileset which doesn't break the
standard functionalities, he's the welcome.
Arnaud
-Message d'origine-
De : Dion Gillard [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 8 juillet 2004 02:32
À : Maven Developers List
Objet : Re: cvs commit: maven-plugins/javadoc/xdocs changes.xml goals.xml
index.xml navigation.xml
properties.xml
Was there any discussion of removing this functionality?
I know I would have preferred another way around this.
On 7 Jul 2004 21:21:45 -, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
aheritier2004/07/07 14:21:45
Modified:javadoc plugin.jelly
javadoc/src/plugin-test maven.xml project.xml
javadoc/src/plugin-test/src/main/org/apache/maven
package.html
javadoc/src/plugin-test/src/main/org/apache/maven2
package.html
javadoc/src/plugin-test/src/opt/org/apache/maven3
package.html
javadoc/xdocs changes.xml goals.xml index.xml navigation.xml
properties.xml
Log:
Remove sourceModifications management in the plugin.
It created a lot of problems (MPJAVADOC-28, MPJAVADOC-29).
Revision ChangesPath
1.47 +9 -81 maven-plugins/javadoc/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/javadoc/plugin.jelly,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- plugin.jelly 7 Jul 2004 10:00:15 - 1.46
+++ plugin.jelly 7 Jul 2004 21:21:45 - 1.47
@@ -36,7 +36,6 @@
!-- internal variables --
j:set var=internal.javadoc.jar
value=${maven.build.dir}/${maven.final.name}_javadoc.jar/
j:set var=internal.javadoc.neededvalue=null/
-j:set var=internal.javadoc.src.modifsvalue=false/
j:set var=internal.javadoc.src.set
value=${context.getAntProject().getReferences().get('maven.compile.src.set')}/
j:set var=internal.javadoc.working.dir
value=${maven.build.dir}/javadoc/
@@ -75,7 +74,6 @@
==
internal.javadoc.jar= [${internal.javadoc.jar}]
internal.javadoc.needed = [${internal.javadoc.needed}]
-internal.javadoc.src.modifs = [${internal.javadoc.src.modifs}]
internal.javadoc.src.set= [${internal.javadoc.src.set}]
internal.javadoc.working.dir= [${internal.javadoc.working.dir}]
/ant:echo
@@ -99,61 +97,29 @@
j:when test=${internal.javadoc.needed != null}
!-- We have already decided if javadoc is needed --
- j:if
test=${maven.javadoc.debug}ant:echo${internal.javadoc.needed} not
null/ant:echo/j:if
+ j:if
test=${maven.javadoc.debug}ant:echointernal.javadoc.needed not null :
${internal.javadoc.needed}/ant:echo/j:if
/j:when
-j:otherwise
- !-- Create a patternset for source modifications --
- patternset id=source.modifications
-ant:include name=**/*.java/
-!-- handle source modifications --
-j:forEach var=sm items=${pom.build.sourceModifications}
- ant:available property=classPresent
classname=${sm.className}/
- j:if test=${classPresent != 'true'}
-j:forEach var=exclude items=${sm.excludes}
- ant:exclude name=${exclude}/
-/j:forEach !-- end sourceModification exclude --
-j:forEach var=include items=${sm.includes}
- ant:include name=${include}/
-/j:forEach !-- end sourceModification include --
- /j:if
-/j:forEach !-- end sourceModification --
- /patternset
-
- !-- test if sourceModifications are defined --
- j:if test=${pom.build.sourceModifications != null amp;amp;
!pom.build.sourceModifications.isEmpty()}
-
