cvs commit: maven-plugins/jcoverage/xdocs changes.xml
brett 2004/07/02 19:08:16 Modified:jcoverage plugin.jelly project.xml jcoverage/xdocs changes.xml Log: avoid needing dependencies for a simple maven clean should cvsignore the file, or set up a way to tell clean there is a new file to clean Revision ChangesPath 1.14 +0 -5 maven-plugins/jcoverage/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven-plugins/jcoverage/plugin.jelly,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- plugin.jelly 28 May 2004 10:27:27 - 1.13 +++ plugin.jelly 3 Jul 2004 02:08:16 - 1.14 @@ -240,9 +240,4 @@ - - - - - 1.26 +1 -1 maven-plugins/jcoverage/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/jcoverage/project.xml,v retrieving revision 1.25 retrieving revision 1.26 diff -u -r1.25 -r1.26 --- project.xml 28 Jun 2004 11:37:59 - 1.25 +++ project.xml 3 Jul 2004 02:08:16 - 1.26 @@ -23,7 +23,7 @@ 3 maven-jcoverage-plugin Maven JCoverage plugin - 1.0.5 + 1.0.6-SNAPSHOT org.apache.maven.jcoveragereport This plugin provides coverage analysis of your source-code based on the open-source jcoverage tool. This plugin provides coverage analysis of your source-code based on the open-source jcoverage tool. 1.18 +3 -0 maven-plugins/jcoverage/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/jcoverage/xdocs/changes.xml,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- changes.xml 28 Jun 2004 11:37:59 - 1.17 +++ changes.xml 3 Jul 2004 02:08:16 - 1.18 @@ -24,6 +24,9 @@ Emmanuel Venisse + + Remove postGoal on clean to avoid introducing all these dependencies on a simple clean. + Fixed report generation fails when no java source present. Handle multiple source directories correctly - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/cruisecontrol plugin.jelly plugin.properties project.properties
brett 2004/07/02 19:06:58
Modified:cruisecontrol plugin.jelly plugin.properties
Removed: cruisecontrol project.properties
Log:
link to the build results
Revision ChangesPath
1.7 +19 -1 maven-plugins/cruisecontrol/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/cruisecontrol/plugin.jelly,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- plugin.jelly 12 Jun 2004 00:08:24 - 1.6
+++ plugin.jelly 3 Jul 2004 02:06:58 - 1.7
@@ -22,7 +22,8 @@
xmlns:j="jelly:core"
xmlns:util="jelly:util"
xmlns:x="jelly:xml"
-xmlns:ant="jelly:ant">
+xmlns:ant="jelly:ant"
+xmlns:doc="doc">
@@ -84,5 +85,22 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
1.7 +1 -0 maven-plugins/cruisecontrol/plugin.properties
Index: plugin.properties
===
RCS file: /home/cvs/maven-plugins/cruisecontrol/plugin.properties,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- plugin.properties 31 May 2004 15:56:08 - 1.6
+++ plugin.properties 3 Jul 2004 02:06:58 - 1.7
@@ -23,3 +23,4 @@
maven.cruisecontrol.mail.defaultsuffix=DEFAULT_SUFFIX_NOT_SET
maven.cruisecontrol.mail.subjectprefix=[BUILD]
maven.cruisecontrol.template=${plugin.resources}/cruisecontrol.jsl
+maven.cruisecontrol.buildresults.url=http://localhost:8080/cruisecontrol
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/artifact/xdocs changes.xml
brett 2004/07/02 19:05:33 Modified:artifact project.xml artifact/xdocs changes.xml Log: dependency sync Revision ChangesPath 1.32 +3 -3 maven-plugins/artifact/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/artifact/project.xml,v retrieving revision 1.31 retrieving revision 1.32 diff -u -r1.31 -r1.32 --- project.xml 28 Jun 2004 09:40:14 - 1.31 +++ project.xml 3 Jul 2004 02:05:33 - 1.32 @@ -70,19 +70,19 @@ commons-net commons-net - 1.0.0 + 1.1.0 jar commons-httpclient commons-httpclient - 2.0-beta1 + 2.0 jar commons-lang commons-lang - 1.0.1 + 2.0 jar 1.25 +1 -0 maven-plugins/artifact/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/artifact/xdocs/changes.xml,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- changes.xml 30 Jun 2004 04:13:01 - 1.24 +++ changes.xml 3 Jul 2004 02:05:33 - 1.25 @@ -27,6 +27,7 @@ Allow use of distributionSite POM attribute in artifact method + Update dependencies on commons-* Allow non-passive FTP - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/antlr/xdocs changes.xml
brett 2004/07/02 19:04:27 Modified:antlr/xdocs changes.xml Log: dependency sync Revision ChangesPath 1.12 +3 -0 maven-plugins/antlr/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/antlr/xdocs/changes.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- changes.xml 16 May 2004 03:06:03 - 1.11 +++ changes.xml 3 Jul 2004 02:04:27 - 1.12 @@ -24,6 +24,9 @@ dIon Gillard + + Update to commons-lang 2.0 + update to commons-lang 1.0.1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/antlr project.xml
brett 2004/07/02 19:03:39 Modified:antlrproject.xml Log: dependency sync Revision ChangesPath 1.35 +2 -2 maven-plugins/antlr/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/antlr/project.xml,v retrieving revision 1.34 retrieving revision 1.35 diff -u -r1.34 -r1.35 --- project.xml 25 Jun 2004 15:24:27 - 1.34 +++ project.xml 3 Jul 2004 02:03:39 - 1.35 @@ -23,7 +23,7 @@ 3 maven-antlr-plugin Maven Antlr Plugin - 1.2 + 1.2.1-SNAPSHOT Process Antlr grammars http://maven.apache.org/reference/plugins/antlr/ @@ -85,7 +85,7 @@ commons-lang commons-lang - 1.0.1 + 2.0 antlr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/xdoc/xdocs changes.xml
brett 2004/07/02 19:02:30
Modified:xdoc plugin.jelly
xdoc/src/plugin-resources navigation.jelly
xdoc/src/plugin-resources/templates maven-reports.xml
xdoc/xdocs changes.xml
Log:
allow external link to be used for a report
Revision ChangesPath
1.61 +1 -0 maven-plugins/xdoc/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/xdoc/plugin.jelly,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -r1.60 -r1.61
--- plugin.jelly 10 May 2004 22:25:05 - 1.60
+++ plugin.jelly 3 Jul 2004 02:02:30 - 1.61
@@ -74,6 +74,7 @@
${report.put('pluginName', pluginName)}
${report.put('description', description)}
${report.put('link', link)}
+ ${report.put('externalLink', externalLink)}
${report.put('target', target)}
${reports.add(report)}
1.10 +5 -1 maven-plugins/xdoc/src/plugin-resources/navigation.jelly
Index: navigation.jelly
===
RCS file: /home/cvs/maven-plugins/xdoc/src/plugin-resources/navigation.jelly,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- navigation.jelly 10 May 2004 22:25:05 - 1.9
+++ navigation.jelly 3 Jul 2004 02:02:30 - 1.10
@@ -53,9 +53,13 @@
+
+
+
+
@@ -76,4 +80,4 @@
-
\ No newline at end of file
+
1.13 +10 -0
maven-plugins/xdoc/src/plugin-resources/templates/maven-reports.xml
Index: maven-reports.xml
===
RCS file:
/home/cvs/maven-plugins/xdoc/src/plugin-resources/templates/maven-reports.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- maven-reports.xml 18 May 2004 22:39:12 - 1.12
+++ maven-reports.xml 3 Jul 2004 02:02:30 - 1.13
@@ -47,6 +47,16 @@
$report.description
#end
+#if ($report.externalLink && $report.externalLink.length() != 0)
+
+ #if($report.target && $report.target.length() != 0)
+ $report.name
+ #else
+ $report.name
+ #end
+ $report.description
+
+#end
#end
1.59 +1 -0 maven-plugins/xdoc/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/xdoc/xdocs/changes.xml,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -r1.58 -r1.59
--- changes.xml 2 Jul 2004 21:27:56 - 1.58
+++ changes.xml 3 Jul 2004 02:02:30 - 1.59
@@ -26,6 +26,7 @@
+ Add an externalLink attribute to a report to
use if link is not present
Added a link to the release notes in the download report. Note that this
link is only created if the project has a xdocs/changes.xml
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven maven.xml
brett 2004/07/02 18:50:37 Modified:.Tag: MAVEN-1_0-BRANCH maven.xml Log: generate a seed repo. just encompasses site (and default reports), java:compile Revision ChangesPath No revision No revision 1.97.2.29 +22 -0 maven/maven.xml Index: maven.xml === RCS file: /home/cvs/maven/maven.xml,v retrieving revision 1.97.2.28 retrieving revision 1.97.2.29 diff -u -r1.97.2.28 -r1.97.2.29 --- maven.xml 12 Jun 2004 04:38:50 - 1.97.2.28 +++ maven.xml 3 Jul 2004 01:50:37 - 1.97.2.29 @@ -379,5 +379,27 @@ + + + + + + + + + + + + + + + + + + + + + + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-1357) make maven inherit properties from parent projects
Message: The following issue has been closed. Resolver: Brett Porter Date: Fri, 2 Jul 2004 9:38 PM RC3 inherits project.properties in the same way as project.xml. Also, you have ssh solutions for windows, and in RC4 the artifact plugin is used instead, so you can do file and ftp based deployment as well. - View the issue: http://jira.codehaus.org/browse/MAVEN-1357 Here is an overview of the issue: - Key: MAVEN-1357 Summary: make maven inherit properties from parent projects Type: Bug Status: Closed Priority: Major Resolution: WON'T FIX Original Estimate: 4 hours Time Spent: Unknown Remaining: 4 hours Project: maven Components: core Versions: 1.0-rc3 Assignee: Reporter: Eirik Maus Created: Fri, 2 Jul 2004 9:58 AM Updated: Fri, 2 Jul 2004 9:38 PM Description: The only reasonable way I have found to share repository for windows-based developers is to have all local projects extend a common parent project. Windows-based organisations have the following in common: - one maven installation per (client) computer, - no ssh Consequently, - the deploy plugin cannot be configured to deploy to local network directory (necessary for commercial closed-source projects), as it is based on ssh. - making local adjustments based on a custom plugin in no good, since everybody most manually install the plugin ang make sure they are up-to-date with it all the time. So, I made a common "site-defaults" project with some goals, and made all projects inherit from it. And everything is inherited EXCEPT the property values that specify locations of fiels, urls to repository etc. The property values work for the goals in the project at the same level that they are defined, but they are not available in the inheriting project, so they cannot be used to adjust plugin parameters in the "real" projects. I cannot see any reason for this behaviour, and find it contratictory to the behaviour of inheriting maven.xml and project.xml contents. I think "parent-project/project.properties" should be first for the properties evaluation, before project.properties, build.properties and ~/*.properties - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-1356) Windows start script fails
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MAVEN-1356 Here is an overview of the issue: - Key: MAVEN-1356 Summary: Windows start script fails Type: Bug Status: Closed Priority: Trivial Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: cli Versions: 1.0-rc4 Assignee: Reporter: Jan Matèrne Created: Fri, 2 Jul 2004 8:13 AM Updated: Fri, 2 Jul 2004 9:35 PM Environment: Windows 2000 German Description: I had installed Maven 1.0RC4 via Windows installer (maven-1.0-rc4.exe). After installing I had to add %MAVEN_HOME%\bin to the path. When invoking "maven" then I got an output abouts java invoke syntax. The result: I had to change %HOME% to %HOMEDRIVE% because trailing backslash lets java not launch. Error near line 126 in bin/maven.bat. Changing from %MAVEN_JAVA_EXE% -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl "-Duser.home.env=%HOME%" "-Dmaven.home=%MAVEN_HOME%" "-Dtools.jar=%JAVA_HOME%\lib\tools.jar" "-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf" -Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH% %MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS% to %MAVEN_JAVA_EXE% -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl "-Duser.home.env=%HOMEDRIVE%" "-Dmaven.home=%MAVEN_HOME%" "-Dtools.jar=%JAVA_HOME%\lib\tools.jar" "-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf" -Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH% %MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS% resolved the problem. But I think there are other invocation points ... - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-1356) Windows start script fails
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MAVEN-1356 Here is an overview of the issue: - Key: MAVEN-1356 Summary: Windows start script fails Type: Bug Status: Closed Priority: Trivial Resolution: DUPLICATE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: cli Versions: 1.0-rc4 Assignee: Reporter: Jan Matèrne Created: Fri, 2 Jul 2004 8:13 AM Updated: Fri, 2 Jul 2004 9:35 PM Environment: Windows 2000 German Description: I had installed Maven 1.0RC4 via Windows installer (maven-1.0-rc4.exe). After installing I had to add %MAVEN_HOME%\bin to the path. When invoking "maven" then I got an output abouts java invoke syntax. The result: I had to change %HOME% to %HOMEDRIVE% because trailing backslash lets java not launch. Error near line 126 in bin/maven.bat. Changing from %MAVEN_JAVA_EXE% -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl "-Duser.home.env=%HOME%" "-Dmaven.home=%MAVEN_HOME%" "-Dtools.jar=%JAVA_HOME%\lib\tools.jar" "-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf" -Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH% %MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS% to %MAVEN_JAVA_EXE% -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl "-Duser.home.env=%HOMEDRIVE%" "-Dmaven.home=%MAVEN_HOME%" "-Dtools.jar=%JAVA_HOME%\lib\tools.jar" "-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf" -Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH% %MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS% resolved the problem. But I think there are other invocation points ... - 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] Reopened: (MAVEN-1356) Windows start script fails
Message: The following issue has been reopened. - View the issue: http://jira.codehaus.org/browse/MAVEN-1356 Here is an overview of the issue: - Key: MAVEN-1356 Summary: Windows start script fails Type: Bug Status: Reopened Priority: Trivial Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: cli Versions: 1.0-rc4 Assignee: Reporter: Jan Matèrne Created: Fri, 2 Jul 2004 8:13 AM Updated: Fri, 2 Jul 2004 9:35 PM Environment: Windows 2000 German Description: I had installed Maven 1.0RC4 via Windows installer (maven-1.0-rc4.exe). After installing I had to add %MAVEN_HOME%\bin to the path. When invoking "maven" then I got an output abouts java invoke syntax. The result: I had to change %HOME% to %HOMEDRIVE% because trailing backslash lets java not launch. Error near line 126 in bin/maven.bat. Changing from %MAVEN_JAVA_EXE% -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl "-Duser.home.env=%HOME%" "-Dmaven.home=%MAVEN_HOME%" "-Dtools.jar=%JAVA_HOME%\lib\tools.jar" "-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf" -Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH% %MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS% to %MAVEN_JAVA_EXE% -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl "-Duser.home.env=%HOMEDRIVE%" "-Dmaven.home=%MAVEN_HOME%" "-Dtools.jar=%JAVA_HOME%\lib\tools.jar" "-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf" -Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH% %MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS% resolved the problem. But I think there are other invocation points ... - 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: (MPCRUISECONTROL-6) Request to make test results visable in the "Test Results" tab.
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPCRUISECONTROL-6 Here is an overview of the issue: - Key: MPCRUISECONTROL-6 Summary: Request to make test results visable in the "Test Results" tab. Type: Improvement Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-cruisecontrol-plugin Assignee: Brett Porter Reporter: Paul Spencer Created: Fri, 2 Jul 2004 6:26 PM Updated: Fri, 2 Jul 2004 6:26 PM Description: The test results can be merged into the CruiseControl log. This will make them visable in "Test Results" in the CruiseControl web aplication. This can be accomplished by replacing with in cruisecontrol.jsl - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPANNOUNCEMENT-4) Cannot use plugin in project.xml's report element.
The following comment has been added to this issue:
Author: Vincent Massol
Created: Fri, 2 Jul 2004 5:30 PM
Body:
Done. The download report now links to the release notes (announcements).
Let me know if I can close this issue.
-
View this comment:
http://jira.codehaus.org/browse/MPANNOUNCEMENT-4?page=comments#action_21325
-
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: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-announcement-plugin
Versions:
1.1
Assignee:
Reporter: Gary Gregory
Created: Tue, 22 Jun 2004 5:44 PM
Updated: Fri, 2 Jul 2004 5:30 PM
Environment: >maven -i
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc3
# BEGIN: Which report
Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)
java.version=1.4.2_04
file.encoding=Cp1252
java.ext.dirs=C:\java\sun\1.4.2_04\jre\lib\ext
java.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\forehead-1.0-beta-5.jar
os.name=Windows XP
java.vendor=Sun Microsystems Inc.
sun.boot.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\endorsed\xerces-2.4.0.jar;C:\Program Files\Apache Software
Foundation\Maven 1.
0-rc3\lib\endorsed\xml-apis-1.0.b2.jar;C:\java\sun\1.4.2_04\jre\lib\rt.jar;C:\java\sun\1.4.2_04\jre\lib\i18n.jar;C:\java\sun\1.4.2_04\jre\lib\sunrsasign.jar;C:\
java\sun\1.4.2_04\jre\lib\jsse.jar;C:\java\sun\1.4.2_04\jre\lib\jce.jar;C:\java\sun\1.4.2_04\jre\lib\charsets.jar;C:\java\sun\1.4.2_04\jre\classes
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
# END: Which report
Installed plugins:
maven-castor-plugin-1.2
maven-site-plugin-1.5
maven-multiproject-plugin-1.3
maven-jdepend-plugin-1.5
maven-clover-plugin-1.5
maven-genapp-plugin-2.2
maven-jbuilder-plugin-1.5
maven-jboss-plugin-1.5
maven-dashboard-plugin-1.3
maven-artifact-plugin-1.2
maven-developer-activity-plugin-1.5
maven-war-plugin-1.6
maven-native-plugin-1.1
maven-cruisecontrol-plugin-1.2
maven-webserver-plugin-2.0
maven-docbook-plugin-1.2
maven-deploy-plugin-1.3
maven-ear-plugin-1.5
maven-repository-plugin-1.2
maven-j2ee-plugin-1.5
maven-jnlp-plugin-1.3
maven-linkcheck-plugin-1.2
maven-javadoc-plugin-1.5
maven-vdoclet-plugin-1.2
maven-hibernate-plugin-1.1
maven-appserver-plugin-2.0
maven-antlr-plugin-1.2
maven-jira-plugin-1.1
maven-ant-plugin-1.7
maven-gump-plugin-1.3
maven-tasklist-plugin-2.3
maven-xdoc-plugin-1.7.1
maven-ashkelon-plugin-1.2
maven-tjdo-plugin-1.0.0
maven-html2xdoc-plugin-1.3
maven-announcement-plugin-1.1
maven-pmd-plugin-1.4
maven-jxr-plugin-1.4
maven-struts-plugin-1.3
maven-latka-plugin-1.4
maven-junit-doclet-plugin-1.2
maven-pom-plugin-1.4
maven-changelog-plugin-1.5
maven-clean-plugin-1.2
maven-license-plugin-1.2
maven-jetty-plugin-1.1
maven-jdee-plugin-1.1
maven-file-activity-plugin-1.5
maven-jcoverage-plugin-1.0.4
maven-jdiff-plugin-1.4
maven-jar-plugin-1.5
maven-scm-plugin-1.3
maven-aspectwerkz-plugin-1.2
maven-faq-plugin-1.3
maven-plugin-plugin-1.3
maven-dist-plugin-1.5
maven-jellydoc-plugin-1.3
maven-javacc-plugin-1.1
maven-shell-plugin-1.1
maven-simian-plugin-1.4
maven-ejb-plugin-1.4
maven-java-plugin-1.4
maven-console-plugin-1.1
maven-pdf-plugin-2.1
maven-release-plugin-1.3
maven-changes-plugin-1.4
maven-nsis-plugin-1.0
maven-checkstyle-plugin-2.4.1
maven-wizard-plugin-1.1
maven-uberjar-plugin-1.2
maven-caller-plugin-1.1
maven-junit-report-plugin-1.5
maven-eclipse-plugin-1.7
maven-latex-plugin-1.2
maven-jdeveloper-plugin-1.4
maven-aspectj-plugin-3.0
maven-idea-plugin-1.4
maven-jalopy-plugin-1.2
maven-test-plugin-1.6.1
maven-multichanges-plugin-1.1
Home Build properties: {jaxp.xslt.jar=C:/java/apache/xalan-2_5_D1//bin/xalan.jar,
servlet.jar=C:/java/sun/jwsdp-1.1/common/lib/servlet.jar, jaxp.jaxp.jar=C:/jav
a/apache/xalan-2_5_D1//bin/xml-apis.jar, junit.jar=C:/java/junit3.8.1/junit.jar}
Description:
Cannot use plugin in project.xml's report element.
I want to be able to say:
[snip]
maven-announcement-plugin
[snip]
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 o
cvs commit: maven-plugins/xdoc/src/plugin-resources/templates downloads.jelly
vmassol 2004/07/02 14:28:36
Modified:xdoc/src/plugin-resources/templates downloads.jelly
Log:
Binary --> Ascii
Revision ChangesPath
1.3 +104 -104
maven-plugins/xdoc/src/plugin-resources/templates/downloads.jelly
Index: downloads.jelly
===
RCS file:
/home/cvs/maven-plugins/xdoc/src/plugin-resources/templates/downloads.jelly,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- downloads.jelly 2 Jul 2004 21:27:56 - 1.2
+++ downloads.jelly 2 Jul 2004 21:28:36 - 1.3
@@ -1,104 +1,104 @@
-
-
-
-
-
-
-
-
-
- Downloads
-
-
-
-
-
-
-
-
-
-
- You must define the maven.xdoc.distributionUrl
- property if you wish to generate the download report.
-
-
-
-
-
-
-
-
- This project has not released any version yet.
-
-
-
-
-
- List of available downloads.
-
-
-
-
-
-
-
-Download links
-
- Release notes
-
-
-
-
-
-
-
- ${pom.name}
v${version}
-
-
-
-
-
-${version} release notes
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+ Downloads
+
+
+
+
+
+
+
+
+
+
+ You must define the maven.xdoc.distributionUrl
+ property if you wish to generate the download report.
+
+
+
+
+
+
+
+
+ This project has not released any version yet.
+
+
+
+
+
+ List of available downloads.
+
+
+
+
+
+
+
+Download links
+
+ Release notes
+
+
+
+
+
+
+
+ ${pom.name}
v${version}
+
+
+
+
+
+${version} release notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/xdoc project.xml
vmassol 2004/07/02 14:27:56
Modified:xdoc/xdocs changes.xml
xdoc/src/plugin-resources/templates downloads.jelly
xdoc project.xml
Log:
- Added a link to the release notes in the download report. Note that this link is
only created if the project has a xdocs/changes.xml file.
- Changed version to be 1.8-SNAPSHOT instead of 1.7.3-SNAPSHOT as there is now a
relatively important change that warrants a new minor
Revision ChangesPath
1.58 +6 -1 maven-plugins/xdoc/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/xdoc/xdocs/changes.xml,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -r1.57 -r1.58
--- changes.xml 30 Jun 2004 04:20:54 - 1.57
+++ changes.xml 2 Jul 2004 21:27:56 - 1.58
@@ -25,7 +25,12 @@
Vincent Massol
-
+
+
+Added a link to the release notes in the download report. Note that this
+link is only created if the project has a xdocs/changes.xml
+file.
+
Add instructions to
checkout with maven to cvs-usage page
1.2 +15 -0
maven-plugins/xdoc/src/plugin-resources/templates/downloads.jelly
Index: downloads.jelly
===
RCS file:
/home/cvs/maven-plugins/xdoc/src/plugin-resources/templates/downloads.jelly,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- downloads.jelly 2 May 2004 10:16:08 - 1.1
+++ downloads.jelly 2 Jul 2004 21:27:56 - 1.2
@@ -60,9 +60,17 @@
List of available downloads.
+
+
+
+
Download links
+
+ Release notes
+
+
+${version} release notes
+
+
1.57 +6 -1 maven-plugins/xdoc/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven-plugins/xdoc/project.xml,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -r1.56 -r1.57
--- project.xml 29 Jun 2004 08:48:35 - 1.56
+++ project.xml 2 Jul 2004 21:27:56 - 1.57
@@ -23,7 +23,7 @@
3
maven-xdoc-plugin
Maven XDoc Plug-in
- 1.7.3-SNAPSHOT
+ 1.8-SNAPSHOT
Convert xdocs into HTML. Requires Maven 1.0 RC2.
Convert xdocs into HTML
http://maven.apache.org/reference/plugins/xdoc/
@@ -59,6 +59,11 @@
1.7.2
1.7.2
MAVEN_XDOC_1_7_2
+
+
+ 1.8
+ 1.8
+ HEAD
-
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: Fri, 2 Jul 2004 5:07 PM
Body:
hmmm... I'm still unsure about step 2 as it would link the changes plugin to the
announcement plugin, which is not a best practice.
I still think I would prefer to dispay the release notes in the download report (my
first comment) as this is a typical use case:
- the user goes to the download section to download a file
- he wants to know what's in the version he downloads
-
View this comment:
http://jira.codehaus.org/browse/MPANNOUNCEMENT-4?page=comments#action_21323
-
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: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-announcement-plugin
Versions:
1.1
Assignee:
Reporter: Gary Gregory
Created: Tue, 22 Jun 2004 5:44 PM
Updated: Fri, 2 Jul 2004 5:07 PM
Environment: >maven -i
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc3
# BEGIN: Which report
Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)
java.version=1.4.2_04
file.encoding=Cp1252
java.ext.dirs=C:\java\sun\1.4.2_04\jre\lib\ext
java.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\forehead-1.0-beta-5.jar
os.name=Windows XP
java.vendor=Sun Microsystems Inc.
sun.boot.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\endorsed\xerces-2.4.0.jar;C:\Program Files\Apache Software
Foundation\Maven 1.
0-rc3\lib\endorsed\xml-apis-1.0.b2.jar;C:\java\sun\1.4.2_04\jre\lib\rt.jar;C:\java\sun\1.4.2_04\jre\lib\i18n.jar;C:\java\sun\1.4.2_04\jre\lib\sunrsasign.jar;C:\
java\sun\1.4.2_04\jre\lib\jsse.jar;C:\java\sun\1.4.2_04\jre\lib\jce.jar;C:\java\sun\1.4.2_04\jre\lib\charsets.jar;C:\java\sun\1.4.2_04\jre\classes
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
# END: Which report
Installed plugins:
maven-castor-plugin-1.2
maven-site-plugin-1.5
maven-multiproject-plugin-1.3
maven-jdepend-plugin-1.5
maven-clover-plugin-1.5
maven-genapp-plugin-2.2
maven-jbuilder-plugin-1.5
maven-jboss-plugin-1.5
maven-dashboard-plugin-1.3
maven-artifact-plugin-1.2
maven-developer-activity-plugin-1.5
maven-war-plugin-1.6
maven-native-plugin-1.1
maven-cruisecontrol-plugin-1.2
maven-webserver-plugin-2.0
maven-docbook-plugin-1.2
maven-deploy-plugin-1.3
maven-ear-plugin-1.5
maven-repository-plugin-1.2
maven-j2ee-plugin-1.5
maven-jnlp-plugin-1.3
maven-linkcheck-plugin-1.2
maven-javadoc-plugin-1.5
maven-vdoclet-plugin-1.2
maven-hibernate-plugin-1.1
maven-appserver-plugin-2.0
maven-antlr-plugin-1.2
maven-jira-plugin-1.1
maven-ant-plugin-1.7
maven-gump-plugin-1.3
maven-tasklist-plugin-2.3
maven-xdoc-plugin-1.7.1
maven-ashkelon-plugin-1.2
maven-tjdo-plugin-1.0.0
maven-html2xdoc-plugin-1.3
maven-announcement-plugin-1.1
maven-pmd-plugin-1.4
maven-jxr-plugin-1.4
maven-struts-plugin-1.3
maven-latka-plugin-1.4
maven-junit-doclet-plugin-1.2
maven-pom-plugin-1.4
maven-changelog-plugin-1.5
maven-clean-plugin-1.2
maven-license-plugin-1.2
maven-jetty-plugin-1.1
maven-jdee-plugin-1.1
maven-file-activity-plugin-1.5
maven-jcoverage-plugin-1.0.4
maven-jdiff-plugin-1.4
maven-jar-plugin-1.5
maven-scm-plugin-1.3
maven-aspectwerkz-plugin-1.2
maven-faq-plugin-1.3
maven-plugin-plugin-1.3
maven-dist-plugin-1.5
maven-jellydoc-plugin-1.3
maven-javacc-plugin-1.1
maven-shell-plugin-1.1
maven-simian-plugin-1.4
maven-ejb-plugin-1.4
maven-java-plugin-1.4
maven-console-plugin-1.1
maven-pdf-plugin-2.1
maven-release-plugin-1.3
maven-changes-plugin-1.4
maven-nsis-plugin-1.0
maven-checkstyle-plugin-2.4.1
maven-wizard-plugin-1.1
maven-uberjar-plugin-1.2
maven-caller-plugin-1.1
maven-junit-report-plugin-1.5
maven-eclipse-plugin-1.7
maven-latex-plugin-1.2
maven-jdeveloper-plugin-1.4
maven-aspectj-plugin-3.0
maven-idea-plugin-1.4
maven-jalopy-plugin-1.2
maven-test-plugin-1.6.1
maven-multichanges-plugin-1.1
Home Build properties: {jaxp.xslt.jar=C:/java/apache/xalan-2_5_D1//bin/xalan.jar,
servlet.jar=C:/java/sun/jwsdp-1.1/common/lib/servlet.jar, jaxp.jaxp.jar=C:/jav
a/apache/xalan-2_5_D1//bin/xml-apis.jar, junit.jar=C:/java/junit3.8.1/junit.jar}
Description:
Cannot use plugin in project.xml's report element.
I want to be able to say:
[snip]
maven-announcement-plugin
[snip]
Thanks.
[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: Fri, 2 Jul 2004 5:03 PM
Body:
I've thought a bit more about it and my view has changed since my last comment. Here's
how I view it now:
1- the announcement plugin generates announcement that go in target/docs (i.e. they go
on the web site when it's deployed)
2- the changes report contain links to the announcement file in its "Release History"
section
Thus there's no need for a "announcement" report as it's available through the changes
report.
I've already committed step 1 and I'm working on step 2.
I Hope you like it... :-)
Thanks
-Vincent
-
View this comment:
http://jira.codehaus.org/browse/MPANNOUNCEMENT-4?page=comments#action_21322
-
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: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-announcement-plugin
Versions:
1.1
Assignee:
Reporter: Gary Gregory
Created: Tue, 22 Jun 2004 5:44 PM
Updated: Fri, 2 Jul 2004 5:03 PM
Environment: >maven -i
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc3
# BEGIN: Which report
Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)
java.version=1.4.2_04
file.encoding=Cp1252
java.ext.dirs=C:\java\sun\1.4.2_04\jre\lib\ext
java.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\forehead-1.0-beta-5.jar
os.name=Windows XP
java.vendor=Sun Microsystems Inc.
sun.boot.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\endorsed\xerces-2.4.0.jar;C:\Program Files\Apache Software
Foundation\Maven 1.
0-rc3\lib\endorsed\xml-apis-1.0.b2.jar;C:\java\sun\1.4.2_04\jre\lib\rt.jar;C:\java\sun\1.4.2_04\jre\lib\i18n.jar;C:\java\sun\1.4.2_04\jre\lib\sunrsasign.jar;C:\
java\sun\1.4.2_04\jre\lib\jsse.jar;C:\java\sun\1.4.2_04\jre\lib\jce.jar;C:\java\sun\1.4.2_04\jre\lib\charsets.jar;C:\java\sun\1.4.2_04\jre\classes
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
# END: Which report
Installed plugins:
maven-castor-plugin-1.2
maven-site-plugin-1.5
maven-multiproject-plugin-1.3
maven-jdepend-plugin-1.5
maven-clover-plugin-1.5
maven-genapp-plugin-2.2
maven-jbuilder-plugin-1.5
maven-jboss-plugin-1.5
maven-dashboard-plugin-1.3
maven-artifact-plugin-1.2
maven-developer-activity-plugin-1.5
maven-war-plugin-1.6
maven-native-plugin-1.1
maven-cruisecontrol-plugin-1.2
maven-webserver-plugin-2.0
maven-docbook-plugin-1.2
maven-deploy-plugin-1.3
maven-ear-plugin-1.5
maven-repository-plugin-1.2
maven-j2ee-plugin-1.5
maven-jnlp-plugin-1.3
maven-linkcheck-plugin-1.2
maven-javadoc-plugin-1.5
maven-vdoclet-plugin-1.2
maven-hibernate-plugin-1.1
maven-appserver-plugin-2.0
maven-antlr-plugin-1.2
maven-jira-plugin-1.1
maven-ant-plugin-1.7
maven-gump-plugin-1.3
maven-tasklist-plugin-2.3
maven-xdoc-plugin-1.7.1
maven-ashkelon-plugin-1.2
maven-tjdo-plugin-1.0.0
maven-html2xdoc-plugin-1.3
maven-announcement-plugin-1.1
maven-pmd-plugin-1.4
maven-jxr-plugin-1.4
maven-struts-plugin-1.3
maven-latka-plugin-1.4
maven-junit-doclet-plugin-1.2
maven-pom-plugin-1.4
maven-changelog-plugin-1.5
maven-clean-plugin-1.2
maven-license-plugin-1.2
maven-jetty-plugin-1.1
maven-jdee-plugin-1.1
maven-file-activity-plugin-1.5
maven-jcoverage-plugin-1.0.4
maven-jdiff-plugin-1.4
maven-jar-plugin-1.5
maven-scm-plugin-1.3
maven-aspectwerkz-plugin-1.2
maven-faq-plugin-1.3
maven-plugin-plugin-1.3
maven-dist-plugin-1.5
maven-jellydoc-plugin-1.3
maven-javacc-plugin-1.1
maven-shell-plugin-1.1
maven-simian-plugin-1.4
maven-ejb-plugin-1.4
maven-java-plugin-1.4
maven-console-plugin-1.1
maven-pdf-plugin-2.1
maven-release-plugin-1.3
maven-changes-plugin-1.4
maven-nsis-plugin-1.0
maven-checkstyle-plugin-2.4.1
maven-wizard-plugin-1.1
maven-uberjar-plugin-1.2
maven-caller-plugin-1.1
maven-junit-report-plugin-1.5
maven-eclipse-plugin-1.7
maven-latex-plugin-1.2
maven-jdeveloper-plugin-1.4
maven-aspectj-plugin-3.0
maven-idea-plugin-1.4
maven-jalopy-plugin-1.2
maven-test-plugin-1.6.1
maven-multichanges-plugin-1.1
Home Build properties: {jaxp.xslt.jar=C:/java/apache/xalan-2_5_D1//bin/xalan.jar,
servlet.jar=C:/java/sun/jwsdp-1.1/common/lib/servlet.jar, jaxp.jaxp.jar=C:/jav
a/apache/xalan-2_5_D1//bin/xml-apis.jar, junit.jar=C:/java/junit3.8.1/junit.jar}
Description:
Cannot use plugin in project.xml
cvs commit: maven-plugins/announcement plugin.jelly plugin.properties
vmassol 2004/07/02 13:57:16
Modified:announcement/xdocs changes.xml goals.xml properties.xml
announcement/src/plugin-resources announcement.jsl
announcement plugin.jelly plugin.properties
Log:
- Added new announcement:generate-all to generate announcement files
for all releases.
- Generates the announcement file in ${maven.gen.docs}/announcements so
that it is copied to the web site when this later is deployed.
- Default announcement file name now contains the version in its name.
Revision ChangesPath
1.18 +11 -0 maven-plugins/announcement/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/announcement/xdocs/changes.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- changes.xml 24 Jun 2004 08:50:31 - 1.17
+++ changes.xml 2 Jul 2004 20:57:16 - 1.18
@@ -25,6 +25,17 @@
+
+Added new announcement:generate-all to generate
+announcement files for all releases.
+
+
+Generates the announcement file in
${maven.gen.docs}/announcements
+so that it is copied to the web site when this later is deployed.
+
+
+Default announcement file name now contains the version in its name.
+
Detect whether the project is a plugin or
not by the existence of plugin.jelly in the project directory, and change the wording
accordingly.
1.4 +9 -1 maven-plugins/announcement/xdocs/goals.xml
Index: goals.xml
===
RCS file: /home/cvs/maven-plugins/announcement/xdocs/goals.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- goals.xml 1 May 2004 17:53:24 - 1.3
+++ goals.xml 2 Jul 2004 20:57:16 - 1.4
@@ -1,4 +1,5 @@
+
-
1.9 +67 -18maven-plugins/announcement/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/announcement/plugin.jelly,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- plugin.jelly 2 May 2004 08:20:59 - 1.8
+++ plugin.jelly 2 Jul 2004 20:57:16 - 1.9
@@ -26,25 +26,35 @@
xmlns:util="jelly:util"
xmlns:doc="doc"
xmlns:maven="jelly:maven"
- xmlns:jsl="jelly:jsl">
+ xmlns:jsl="jelly:jsl"
+ xmlns:announcement="announcement">
-
-
-Generating announcement for release ${maven.announcement.version} in
${maven.announcement.file}...
+
-
-
-
+
+
+
+
+
+
+
+
-
+
+
+
+
+
+
+
@@ -52,22 +62,61 @@
+
+
The release '${maven.announcement.version}' could not be found in
change log
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Generating announcement for release ${versionVariable} in
${file}...
+
+
+
+
+
+
+
+
+
1.10 +0 -3 maven-plugins/announcement/plugin.properties
Index: plugin.properties
===
RCS file: /home/cvs/maven-plugins/announcement/plugin.properties,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- plugin.properties 11 May 2004 23:33:44 - 1.9
+++ plugin.properties 2 Jul 2004 20:57:16 - 1.10
@@ -23,9 +23,6 @@
# For example:
# maven.announcement.version = ${pom.currentVersion}
-# Name and location of generated announcement file
-maven.announcement.file=${maven.build.dir}/announcement.txt
-
# Distribution location. For now, this property does not exist in the
# POM (there's only a distributionSite and distributionDirectory which
# doesn't map to anything for the web). We'll need to remove this
-
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: Fri, 2 Jul 2004 2:11 PM
Body:
I guess what you'd really like is to see the announcement appear on the web site.
However this should only happen when there is a release. That's why it's manual ATM.
Thus I guess it should rather be linked to the scm plugin which is used during
releases. Maybe that plugin could bundle the announcement on the web site.
Another idea would be to link the announcement to the generation of the download page
so that people who want to download a given version of the project can instantly know
what it contains. Yeah I think I like this idea... :-)
What do you think?
-
View this comment:
http://jira.codehaus.org/browse/MPANNOUNCEMENT-4?page=comments#action_21313
-
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: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-announcement-plugin
Versions:
1.1
Assignee:
Reporter: Gary Gregory
Created: Tue, 22 Jun 2004 5:44 PM
Updated: Fri, 2 Jul 2004 2:11 PM
Environment: >maven -i
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc3
# BEGIN: Which report
Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)
java.version=1.4.2_04
file.encoding=Cp1252
java.ext.dirs=C:\java\sun\1.4.2_04\jre\lib\ext
java.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\forehead-1.0-beta-5.jar
os.name=Windows XP
java.vendor=Sun Microsystems Inc.
sun.boot.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\endorsed\xerces-2.4.0.jar;C:\Program Files\Apache Software
Foundation\Maven 1.
0-rc3\lib\endorsed\xml-apis-1.0.b2.jar;C:\java\sun\1.4.2_04\jre\lib\rt.jar;C:\java\sun\1.4.2_04\jre\lib\i18n.jar;C:\java\sun\1.4.2_04\jre\lib\sunrsasign.jar;C:\
java\sun\1.4.2_04\jre\lib\jsse.jar;C:\java\sun\1.4.2_04\jre\lib\jce.jar;C:\java\sun\1.4.2_04\jre\lib\charsets.jar;C:\java\sun\1.4.2_04\jre\classes
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
# END: Which report
Installed plugins:
maven-castor-plugin-1.2
maven-site-plugin-1.5
maven-multiproject-plugin-1.3
maven-jdepend-plugin-1.5
maven-clover-plugin-1.5
maven-genapp-plugin-2.2
maven-jbuilder-plugin-1.5
maven-jboss-plugin-1.5
maven-dashboard-plugin-1.3
maven-artifact-plugin-1.2
maven-developer-activity-plugin-1.5
maven-war-plugin-1.6
maven-native-plugin-1.1
maven-cruisecontrol-plugin-1.2
maven-webserver-plugin-2.0
maven-docbook-plugin-1.2
maven-deploy-plugin-1.3
maven-ear-plugin-1.5
maven-repository-plugin-1.2
maven-j2ee-plugin-1.5
maven-jnlp-plugin-1.3
maven-linkcheck-plugin-1.2
maven-javadoc-plugin-1.5
maven-vdoclet-plugin-1.2
maven-hibernate-plugin-1.1
maven-appserver-plugin-2.0
maven-antlr-plugin-1.2
maven-jira-plugin-1.1
maven-ant-plugin-1.7
maven-gump-plugin-1.3
maven-tasklist-plugin-2.3
maven-xdoc-plugin-1.7.1
maven-ashkelon-plugin-1.2
maven-tjdo-plugin-1.0.0
maven-html2xdoc-plugin-1.3
maven-announcement-plugin-1.1
maven-pmd-plugin-1.4
maven-jxr-plugin-1.4
maven-struts-plugin-1.3
maven-latka-plugin-1.4
maven-junit-doclet-plugin-1.2
maven-pom-plugin-1.4
maven-changelog-plugin-1.5
maven-clean-plugin-1.2
maven-license-plugin-1.2
maven-jetty-plugin-1.1
maven-jdee-plugin-1.1
maven-file-activity-plugin-1.5
maven-jcoverage-plugin-1.0.4
maven-jdiff-plugin-1.4
maven-jar-plugin-1.5
maven-scm-plugin-1.3
maven-aspectwerkz-plugin-1.2
maven-faq-plugin-1.3
maven-plugin-plugin-1.3
maven-dist-plugin-1.5
maven-jellydoc-plugin-1.3
maven-javacc-plugin-1.1
maven-shell-plugin-1.1
maven-simian-plugin-1.4
maven-ejb-plugin-1.4
maven-java-plugin-1.4
maven-console-plugin-1.1
maven-pdf-plugin-2.1
maven-release-plugin-1.3
maven-changes-plugin-1.4
maven-nsis-plugin-1.0
maven-checkstyle-plugin-2.4.1
maven-wizard-plugin-1.1
maven-uberjar-plugin-1.2
maven-caller-plugin-1.1
maven-junit-report-plugin-1.5
maven-eclipse-plugin-1.7
maven-latex-plugin-1.2
maven-jdeveloper-plugin-1.4
maven-aspectj-plugin-3.0
maven-idea-plugin-1.4
maven-jalopy-plugin-1.2
maven-test-plugin-1.6.1
maven-multichanges-plugin-1.1
Home Build properties: {jaxp.xslt.jar=C:/java/apache/xalan-2_5_D1//bin/xalan.jar,
servlet.jar=C:/java/sun/jwsdp-1.1/common/lib/servlet.jar, jaxp.jaxp.jar=C:/jav
a/apache/xalan-2_5_D1//bin/xml-apis.jar, junit.jar=C:/java/junit3.8.1/junit.ja
[jira] Updated: (MPCHANGES-16) Add multiple issue support to issues action attributes
The following issue has been updated:
Updater: Vincent Massol (mailto:[EMAIL PROTECTED])
Date: Fri, 2 Jul 2004 1:51 PM
Changes:
Fix Version changed to 1.5
-
For a full history of the issue, see:
http://jira.codehaus.org/browse/MPCHANGES-16?page=history
-
View the issue:
http://jira.codehaus.org/browse/MPCHANGES-16
Here is an overview of the issue:
-
Key: MPCHANGES-16
Summary: Add multiple issue support to issues action attributes
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-changes-plugin
Fix Fors:
1.5
Versions:
1.4
Assignee:
Reporter: Gary Gregory
Created: Tue, 22 Jun 2004 2:29 PM
Updated: Fri, 2 Jul 2004 1:51 PM
Environment: >maven -i
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc3
# BEGIN: Which report
Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)
java.version=1.4.2_04
file.encoding=Cp1252
java.ext.dirs=C:\java\sun\1.4.2_04\jre\lib\ext
java.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\forehead-1.0-beta-5.jar
os.name=Windows XP
java.vendor=Sun Microsystems Inc.
sun.boot.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\endorsed\xerces-2.4.0.jar;C:\Program Files\Apache Software
Foundation\Maven 1.
0-rc3\lib\endorsed\xml-apis-1.0.b2.jar;C:\java\sun\1.4.2_04\jre\lib\rt.jar;C:\java\sun\1.4.2_04\jre\lib\i18n.jar;C:\java\sun\1.4.2_04\jre\lib\sunrsasign.jar;C:\
java\sun\1.4.2_04\jre\lib\jsse.jar;C:\java\sun\1.4.2_04\jre\lib\jce.jar;C:\java\sun\1.4.2_04\jre\lib\charsets.jar;C:\java\sun\1.4.2_04\jre\classes
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
# END: Which report
Installed plugins:
maven-castor-plugin-1.2
maven-site-plugin-1.5
maven-multiproject-plugin-1.3
maven-jdepend-plugin-1.5
maven-clover-plugin-1.5
maven-genapp-plugin-2.2
maven-jbuilder-plugin-1.5
maven-jboss-plugin-1.5
maven-dashboard-plugin-1.3
maven-artifact-plugin-1.2
maven-developer-activity-plugin-1.5
maven-war-plugin-1.6
maven-native-plugin-1.1
maven-cruisecontrol-plugin-1.2
maven-webserver-plugin-2.0
maven-docbook-plugin-1.2
maven-deploy-plugin-1.3
maven-ear-plugin-1.5
maven-repository-plugin-1.2
maven-j2ee-plugin-1.5
maven-jnlp-plugin-1.3
maven-linkcheck-plugin-1.2
maven-javadoc-plugin-1.5
maven-vdoclet-plugin-1.2
maven-hibernate-plugin-1.1
maven-appserver-plugin-2.0
maven-antlr-plugin-1.2
maven-jira-plugin-1.1
maven-ant-plugin-1.7
maven-gump-plugin-1.3
maven-tasklist-plugin-2.3
maven-xdoc-plugin-1.7.1
maven-ashkelon-plugin-1.2
maven-tjdo-plugin-1.0.0
maven-html2xdoc-plugin-1.3
maven-announcement-plugin-1.1
maven-pmd-plugin-1.4
maven-jxr-plugin-1.4
maven-struts-plugin-1.3
maven-latka-plugin-1.4
maven-junit-doclet-plugin-1.2
maven-pom-plugin-1.4
maven-changelog-plugin-1.5
maven-clean-plugin-1.2
maven-license-plugin-1.2
maven-jetty-plugin-1.1
maven-jdee-plugin-1.1
maven-file-activity-plugin-1.5
maven-jcoverage-plugin-1.0.4
maven-jdiff-plugin-1.4
maven-jar-plugin-1.5
maven-scm-plugin-1.3
maven-aspectwerkz-plugin-1.2
maven-faq-plugin-1.3
maven-plugin-plugin-1.3
maven-dist-plugin-1.5
maven-jellydoc-plugin-1.3
maven-javacc-plugin-1.1
maven-shell-plugin-1.1
maven-simian-plugin-1.4
maven-ejb-plugin-1.4
maven-java-plugin-1.4
maven-console-plugin-1.1
maven-pdf-plugin-2.1
maven-release-plugin-1.3
maven-changes-plugin-1.4
maven-nsis-plugin-1.0
maven-checkstyle-plugin-2.4.1
maven-wizard-plugin-1.1
maven-uberjar-plugin-1.2
maven-caller-plugin-1.1
maven-junit-report-plugin-1.5
maven-eclipse-plugin-1.7
maven-latex-plugin-1.2
maven-jdeveloper-plugin-1.4
maven-aspectj-plugin-3.0
maven-idea-plugin-1.4
maven-jalopy-plugin-1.2
maven-test-plugin-1.6.1
maven-multichanges-plugin-1.1
Home Build properties: {jaxp.xslt.jar=C:/java/apache/xalan-2_5_D1//bin/xalan.jar,
servlet.jar=C:/java/sun/jwsdp-1.1/common/lib/servlet.jar, jaxp.jaxp.jar=C:/jav
a/apache/xalan-2_5_D1//bin/xml-apis.jar, junit.jar=C:/java/junit3.8.1/junit.jar}
Description:
Add multiple issue support to issues action attributes.
For example, I should be able to say:
issue="26617, 27789"
in:
QuotedPrintableCodec: Codec for RFC 1521 MIME (Multipurpose Internet
Mail Extensions) Part One. Rules #3, #4, and #5 of the quoted-printable
spec
are not implemented yet.
and have the issue generate 2 links.
Thanks.
-
[jira] Updated: (MPCHANGES-17) jira links don't work with /browse/ form
The following issue has been updated: Updater: Vincent Massol (mailto:[EMAIL PROTECTED]) Date: Fri, 2 Jul 2004 1:51 PM Changes: Fix Version changed to 1.5 - For a full history of the issue, see: http://jira.codehaus.org/browse/MPCHANGES-17?page=history - View the issue: http://jira.codehaus.org/browse/MPCHANGES-17 Here is an overview of the issue: - Key: MPCHANGES-17 Summary: jira links don't work with /browse/ form Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-changes-plugin Fix Fors: 1.5 Assignee: Reporter: Brett Porter Created: Mon, 28 Jun 2004 6:12 AM Updated: Fri, 2 Jul 2004 1:51 PM Description: they append the ViewIssue to /browse/ - 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: (MPCHANGES-14) Allow entries to be sorted by action type.
The following issue has been updated:
Updater: Vincent Massol (mailto:[EMAIL PROTECTED])
Date: Fri, 2 Jul 2004 1:51 PM
Changes:
Fix Version changed to 1.5
-
For a full history of the issue, see:
http://jira.codehaus.org/browse/MPCHANGES-14?page=history
-
View the issue:
http://jira.codehaus.org/browse/MPCHANGES-14
Here is an overview of the issue:
-
Key: MPCHANGES-14
Summary: Allow entries to be sorted by action type.
Type: New Feature
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-changes-plugin
Fix Fors:
1.5
Versions:
1.4
Assignee:
Reporter: Gary Gregory
Created: Tue, 22 Jun 2004 2:30 AM
Updated: Fri, 2 Jul 2004 1:51 PM
Environment: >maven -i
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc3
# BEGIN: Which report
Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)
java.version=1.4.2_04
file.encoding=Cp1252
java.ext.dirs=C:\java\sun\1.4.2_04\jre\lib\ext
java.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\forehead-1.0-beta-5.jar
os.name=Windows XP
java.vendor=Sun Microsystems Inc.
sun.boot.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\endorsed\xerces-2.4.0.jar;C:\Program Files\Apache Software
Foundation\Maven 1.
0-rc3\lib\endorsed\xml-apis-1.0.b2.jar;C:\java\sun\1.4.2_04\jre\lib\rt.jar;C:\java\sun\1.4.2_04\jre\lib\i18n.jar;C:\java\sun\1.4.2_04\jre\lib\sunrsasign.jar;C:\
java\sun\1.4.2_04\jre\lib\jsse.jar;C:\java\sun\1.4.2_04\jre\lib\jce.jar;C:\java\sun\1.4.2_04\jre\lib\charsets.jar;C:\java\sun\1.4.2_04\jre\classes
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
# END: Which report
Installed plugins:
maven-castor-plugin-1.2
maven-site-plugin-1.5
maven-multiproject-plugin-1.3
maven-jdepend-plugin-1.5
maven-clover-plugin-1.5
maven-genapp-plugin-2.2
maven-jbuilder-plugin-1.5
maven-jboss-plugin-1.5
maven-dashboard-plugin-1.3
maven-artifact-plugin-1.2
maven-developer-activity-plugin-1.5
maven-war-plugin-1.6
maven-native-plugin-1.1
maven-cruisecontrol-plugin-1.2
maven-webserver-plugin-2.0
maven-docbook-plugin-1.2
maven-deploy-plugin-1.3
maven-ear-plugin-1.5
maven-repository-plugin-1.2
maven-j2ee-plugin-1.5
maven-jnlp-plugin-1.3
maven-linkcheck-plugin-1.2
maven-javadoc-plugin-1.5
maven-vdoclet-plugin-1.2
maven-hibernate-plugin-1.1
maven-appserver-plugin-2.0
maven-antlr-plugin-1.2
maven-jira-plugin-1.1
maven-ant-plugin-1.7
maven-gump-plugin-1.3
maven-tasklist-plugin-2.3
maven-xdoc-plugin-1.7.1
maven-ashkelon-plugin-1.2
maven-tjdo-plugin-1.0.0
maven-html2xdoc-plugin-1.3
maven-announcement-plugin-1.1
maven-pmd-plugin-1.4
maven-jxr-plugin-1.4
maven-struts-plugin-1.3
maven-latka-plugin-1.4
maven-junit-doclet-plugin-1.2
maven-pom-plugin-1.4
maven-changelog-plugin-1.5
maven-clean-plugin-1.2
maven-license-plugin-1.2
maven-jetty-plugin-1.1
maven-jdee-plugin-1.1
maven-file-activity-plugin-1.5
maven-jcoverage-plugin-1.0.4
maven-jdiff-plugin-1.4
maven-jar-plugin-1.5
maven-scm-plugin-1.3
maven-aspectwerkz-plugin-1.2
maven-faq-plugin-1.3
maven-plugin-plugin-1.3
maven-dist-plugin-1.5
maven-jellydoc-plugin-1.3
maven-javacc-plugin-1.1
maven-shell-plugin-1.1
maven-simian-plugin-1.4
maven-ejb-plugin-1.4
maven-java-plugin-1.4
maven-console-plugin-1.1
maven-pdf-plugin-2.1
maven-release-plugin-1.3
maven-changes-plugin-1.4
maven-nsis-plugin-1.0
maven-checkstyle-plugin-2.4.1
maven-wizard-plugin-1.1
maven-uberjar-plugin-1.2
maven-caller-plugin-1.1
maven-junit-report-plugin-1.5
maven-eclipse-plugin-1.7
maven-latex-plugin-1.2
maven-jdeveloper-plugin-1.4
maven-aspectj-plugin-3.0
maven-idea-plugin-1.4
maven-jalopy-plugin-1.2
maven-test-plugin-1.6.1
maven-multichanges-plugin-1.1
Home Build properties: {jaxp.xslt.jar=C:/java/apache/xalan-2_5_D1//bin/xalan.jar,
servlet.jar=C:/java/sun/jwsdp-1.1/common/lib/servlet.jar, jaxp.jaxp.jar=C:/jav
a/apache/xalan-2_5_D1//bin/xml-apis.jar, junit.jar=C:/java/junit3.8.1/junit.jar}
Description:
Allow entries to be sorted by action type.
Today, I must sort (and keep sorted :-) the action entries in changes.xml. It would be
nice to be able to specify - perhaps in the properties file - that the generated XML
and text file be sorted by action. Maybe something like:
maven.changes.action.sort = add, fix, update, remove
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was s
[jira] Updated: (MPCHANGES-9) Sourceforge tracker support
The following issue has been updated: Updater: Vincent Massol (mailto:[EMAIL PROTECTED]) Date: Fri, 2 Jul 2004 1:51 PM Changes: Fix Version changed to 1.5 - For a full history of the issue, see: http://jira.codehaus.org/browse/MPCHANGES-9?page=history - View the issue: http://jira.codehaus.org/browse/MPCHANGES-9 Here is an overview of the issue: - Key: MPCHANGES-9 Summary: Sourceforge tracker support Type: Improvement Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-changes-plugin Fix Fors: 1.5 Assignee: Vincent Massol Reporter: Martijn Dashorst Created: Sun, 13 Jun 2004 11:25 AM Updated: Fri, 2 Jul 2004 1:51 PM Description: The URL as it is generated now doesn't support the sourceforge (SF) tracker format. The SF format consists of three pieces of information: - the project id (group_id) - the artifact id (aid) - the artifact type id (atid) Especially the atrifact type id is worisome, since it is needed to discriminate the different trackers. It is not possible to retrieve an artifact by group_id and aid alone. In order to facilitate this, some additional information is required, namely the tracker id. I am creating a patch for the changes plugin which integrates the support for sourceforge. - 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: (MPCHANGES-15) Add multiple author support to dev, due-to, and due-to-email action attributes
The following issue has been updated:
Updater: Vincent Massol (mailto:[EMAIL PROTECTED])
Date: Fri, 2 Jul 2004 1:51 PM
Changes:
Fix Version changed to 1.5
-
For a full history of the issue, see:
http://jira.codehaus.org/browse/MPCHANGES-15?page=history
-
View the issue:
http://jira.codehaus.org/browse/MPCHANGES-15
Here is an overview of the issue:
-
Key: MPCHANGES-15
Summary: Add multiple author support to dev, due-to, and due-to-email action
attributes
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-changes-plugin
Fix Fors:
1.5
Versions:
1.4
Assignee:
Reporter: Gary Gregory
Created: Tue, 22 Jun 2004 2:19 PM
Updated: Fri, 2 Jul 2004 1:51 PM
Environment: >maven -i
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc3
# BEGIN: Which report
Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)
java.version=1.4.2_04
file.encoding=Cp1252
java.ext.dirs=C:\java\sun\1.4.2_04\jre\lib\ext
java.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\forehead-1.0-beta-5.jar
os.name=Windows XP
java.vendor=Sun Microsystems Inc.
sun.boot.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\endorsed\xerces-2.4.0.jar;C:\Program Files\Apache Software
Foundation\Maven 1.
0-rc3\lib\endorsed\xml-apis-1.0.b2.jar;C:\java\sun\1.4.2_04\jre\lib\rt.jar;C:\java\sun\1.4.2_04\jre\lib\i18n.jar;C:\java\sun\1.4.2_04\jre\lib\sunrsasign.jar;C:\
java\sun\1.4.2_04\jre\lib\jsse.jar;C:\java\sun\1.4.2_04\jre\lib\jce.jar;C:\java\sun\1.4.2_04\jre\lib\charsets.jar;C:\java\sun\1.4.2_04\jre\classes
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
# END: Which report
Installed plugins:
maven-castor-plugin-1.2
maven-site-plugin-1.5
maven-multiproject-plugin-1.3
maven-jdepend-plugin-1.5
maven-clover-plugin-1.5
maven-genapp-plugin-2.2
maven-jbuilder-plugin-1.5
maven-jboss-plugin-1.5
maven-dashboard-plugin-1.3
maven-artifact-plugin-1.2
maven-developer-activity-plugin-1.5
maven-war-plugin-1.6
maven-native-plugin-1.1
maven-cruisecontrol-plugin-1.2
maven-webserver-plugin-2.0
maven-docbook-plugin-1.2
maven-deploy-plugin-1.3
maven-ear-plugin-1.5
maven-repository-plugin-1.2
maven-j2ee-plugin-1.5
maven-jnlp-plugin-1.3
maven-linkcheck-plugin-1.2
maven-javadoc-plugin-1.5
maven-vdoclet-plugin-1.2
maven-hibernate-plugin-1.1
maven-appserver-plugin-2.0
maven-antlr-plugin-1.2
maven-jira-plugin-1.1
maven-ant-plugin-1.7
maven-gump-plugin-1.3
maven-tasklist-plugin-2.3
maven-xdoc-plugin-1.7.1
maven-ashkelon-plugin-1.2
maven-tjdo-plugin-1.0.0
maven-html2xdoc-plugin-1.3
maven-announcement-plugin-1.1
maven-pmd-plugin-1.4
maven-jxr-plugin-1.4
maven-struts-plugin-1.3
maven-latka-plugin-1.4
maven-junit-doclet-plugin-1.2
maven-pom-plugin-1.4
maven-changelog-plugin-1.5
maven-clean-plugin-1.2
maven-license-plugin-1.2
maven-jetty-plugin-1.1
maven-jdee-plugin-1.1
maven-file-activity-plugin-1.5
maven-jcoverage-plugin-1.0.4
maven-jdiff-plugin-1.4
maven-jar-plugin-1.5
maven-scm-plugin-1.3
maven-aspectwerkz-plugin-1.2
maven-faq-plugin-1.3
maven-plugin-plugin-1.3
maven-dist-plugin-1.5
maven-jellydoc-plugin-1.3
maven-javacc-plugin-1.1
maven-shell-plugin-1.1
maven-simian-plugin-1.4
maven-ejb-plugin-1.4
maven-java-plugin-1.4
maven-console-plugin-1.1
maven-pdf-plugin-2.1
maven-release-plugin-1.3
maven-changes-plugin-1.4
maven-nsis-plugin-1.0
maven-checkstyle-plugin-2.4.1
maven-wizard-plugin-1.1
maven-uberjar-plugin-1.2
maven-caller-plugin-1.1
maven-junit-report-plugin-1.5
maven-eclipse-plugin-1.7
maven-latex-plugin-1.2
maven-jdeveloper-plugin-1.4
maven-aspectj-plugin-3.0
maven-idea-plugin-1.4
maven-jalopy-plugin-1.2
maven-test-plugin-1.6.1
maven-multichanges-plugin-1.1
Home Build properties: {jaxp.xslt.jar=C:/java/apache/xalan-2_5_D1//bin/xalan.jar,
servlet.jar=C:/java/sun/jwsdp-1.1/common/lib/servlet.jar, jaxp.jaxp.jar=C:/jav
a/apache/xalan-2_5_D1//bin/xml-apis.jar, junit.jar=C:/java/junit3.8.1/junit.jar}
Description:
Please add multiple author support to dev, due-to, and due-to-email action attributes.
Commas can be used to separate list items.
For a new feature I want to give credit to more than 1 author, for example:
Right now, I can only have one. The example above will generate one link. The goal is
to have 2 separate links. Thanks.
-
JIRA INFORMATION:
This message is automatically g
[jira] Commented: (MAVEN-1357) make maven inherit properties from parent projects
The following comment has been added to this issue: Author: Carlos Sanchez Created: Fri, 2 Jul 2004 10:50 AM Body: Maven does inherit properties. Check putty and cygwin ssh clients for windows - View this comment: http://jira.codehaus.org/browse/MAVEN-1357?page=comments#action_21305 - View the issue: http://jira.codehaus.org/browse/MAVEN-1357 Here is an overview of the issue: - Key: MAVEN-1357 Summary: make maven inherit properties from parent projects Type: Bug Status: Unassigned Priority: Major Original Estimate: 4 hours Time Spent: Unknown Remaining: 4 hours Project: maven Components: core Versions: 1.0-rc3 Assignee: Reporter: Eirik Maus Created: Fri, 2 Jul 2004 9:58 AM Updated: Fri, 2 Jul 2004 10:50 AM Description: The only reasonable way I have found to share repository for windows-based developers is to have all local projects extend a common parent project. Windows-based organisations have the following in common: - one maven installation per (client) computer, - no ssh Consequently, - the deploy plugin cannot be configured to deploy to local network directory (necessary for commercial closed-source projects), as it is based on ssh. - making local adjustments based on a custom plugin in no good, since everybody most manually install the plugin ang make sure they are up-to-date with it all the time. So, I made a common "site-defaults" project with some goals, and made all projects inherit from it. And everything is inherited EXCEPT the property values that specify locations of fiels, urls to repository etc. The property values work for the goals in the project at the same level that they are defined, but they are not available in the inheriting project, so they cannot be used to adjust plugin parameters in the "real" projects. I cannot see any reason for this behaviour, and find it contratictory to the behaviour of inheriting maven.xml and project.xml contents. I think "parent-project/project.properties" should be first for the properties evaluation, before project.properties, build.properties and ~/*.properties - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: when to touch changes.xml/project.xml version RE: cvs commit: maven-plugins/java project.xml
> -Original Message- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Friday, July 02, 2004 8:52 AM > To: 'Maven Developers List' > Subject: RE: when to touch changes.xml/project.xml version > RE: cvs commit: maven-plugins/java project.xml > > > > > -Original Message- > > From: Carlos Sanchez [mailto:[EMAIL PROTECTED] > > Sent: vendredi 2 juillet 2004 00:08 > > To: 'Maven Developers List' > > Subject: RE: when to touch changes.xml/project.xml version > RE: cvs commit: > > maven-plugins/java project.xml > > > > [snip] > > > > One question about SNAPSHOT, when you decide to increase version > > number should it be: > > new.version.number-SNAPSHOT > > > > This generates artifactId + version + snapshot info. > > Is this ok or should be artifactId + snapshot info? > > I personally much prefer -SNAPSHOT > > It indicates what version is being developed. Otherwise, it > cannot be guessed. Yes, I also prefer that, but I was a bit confused about SNAPSHOT (seen in docs and mails), so the recomended way is ... 1.0-SNAPSHOT ... And I'll suppose that this is supported and everything's gonna work as expected. Thanks > > Thanks > -Vincent > > > > > Thanks > > > > > > Carlos Sanchez > > A Coruña, Spain > > > > Oness Project > > http://oness.sourceforge.net > > > > > > > > > > -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] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1357) make maven inherit properties from parent projects
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1357 Here is an overview of the issue: - Key: MAVEN-1357 Summary: make maven inherit properties from parent projects Type: Bug Status: Unassigned Priority: Major Original Estimate: 4 hours Time Spent: Unknown Remaining: 4 hours Project: maven Components: core Versions: 1.0-rc3 Assignee: Reporter: Eirik Maus Created: Fri, 2 Jul 2004 9:58 AM Updated: Fri, 2 Jul 2004 9:58 AM Description: The only reasonable way I have found to share repository for windows-based developers is to have all local projects extend a common parent project. Windows-based organisations have the following in common: - one maven installation per (client) computer, - no ssh Consequently, - the deploy plugin cannot be configured to deploy to local network directory (necessary for commercial closed-source projects), as it is based on ssh. - making local adjustments based on a custom plugin in no good, since everybody most manually install the plugin ang make sure they are up-to-date with it all the time. So, I made a common "site-defaults" project with some goals, and made all projects inherit from it. And everything is inherited EXCEPT the property values that specify locations of fiels, urls to repository etc. The property values work for the goals in the project at the same level that they are defined, but they are not available in the inheriting project, so they cannot be used to adjust plugin parameters in the "real" projects. I cannot see any reason for this behaviour, and find it contratictory to the behaviour of inheriting maven.xml and project.xml contents. I think "parent-project/project.properties" should be first for the properties evaluation, before project.properties, build.properties and ~/*.properties - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1356) Windows start script fails
The following comment has been added to this issue: Author: Harald Ommang Created: Fri, 2 Jul 2004 8:15 AM Body: This is a duplicate of MAVEN-1354 - View this comment: http://jira.codehaus.org/browse/MAVEN-1356?page=comments#action_21301 - View the issue: http://jira.codehaus.org/browse/MAVEN-1356 Here is an overview of the issue: - Key: MAVEN-1356 Summary: Windows start script fails Type: Bug Status: Unassigned Priority: Trivial Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: cli Versions: 1.0-rc4 Assignee: Reporter: Jan Matèrne Created: Fri, 2 Jul 2004 8:13 AM Updated: Fri, 2 Jul 2004 8:15 AM Environment: Windows 2000 German Description: I had installed Maven 1.0RC4 via Windows installer (maven-1.0-rc4.exe). After installing I had to add %MAVEN_HOME%\bin to the path. When invoking "maven" then I got an output abouts java invoke syntax. The result: I had to change %HOME% to %HOMEDRIVE% because trailing backslash lets java not launch. Error near line 126 in bin/maven.bat. Changing from %MAVEN_JAVA_EXE% -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl "-Duser.home.env=%HOME%" "-Dmaven.home=%MAVEN_HOME%" "-Dtools.jar=%JAVA_HOME%\lib\tools.jar" "-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf" -Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH% %MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS% to %MAVEN_JAVA_EXE% -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl "-Duser.home.env=%HOMEDRIVE%" "-Dmaven.home=%MAVEN_HOME%" "-Dtools.jar=%JAVA_HOME%\lib\tools.jar" "-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf" -Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH% %MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS% resolved the problem. But I think there are other invocation points ... - 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-1356) Windows start script fails
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1356 Here is an overview of the issue: - Key: MAVEN-1356 Summary: Windows start script fails Type: Bug Status: Unassigned Priority: Trivial Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: cli Versions: 1.0-rc4 Assignee: Reporter: Jan Matèrne Created: Fri, 2 Jul 2004 8:13 AM Updated: Fri, 2 Jul 2004 8:13 AM Environment: Windows 2000 German Description: I had installed Maven 1.0RC4 via Windows installer (maven-1.0-rc4.exe). After installing I had to add %MAVEN_HOME%\bin to the path. When invoking "maven" then I got an output abouts java invoke syntax. The result: I had to change %HOME% to %HOMEDRIVE% because trailing backslash lets java not launch. Error near line 126 in bin/maven.bat. Changing from %MAVEN_JAVA_EXE% -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl "-Duser.home.env=%HOME%" "-Dmaven.home=%MAVEN_HOME%" "-Dtools.jar=%JAVA_HOME%\lib\tools.jar" "-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf" -Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH% %MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS% to %MAVEN_JAVA_EXE% -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl "-Duser.home.env=%HOMEDRIVE%" "-Dmaven.home=%MAVEN_HOME%" "-Dtools.jar=%JAVA_HOME%\lib\tools.jar" "-Dforehead.conf.file=%MAVEN_HOME%\bin\forehead.conf" -Djava.endorsed.dirs=%MAVEN_ENDORSED% %MAVEN_OPTS% -classpath %MAVEN_CLASSPATH% %MAVEN_MAIN_CLASS% %MAVEN_CMD_LINE_ARGS% resolved the problem. But I think there are other invocation points ... - 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: cvs commit: maven/src/java/org/apache/maven/plugin PluginManager.java
- Original Message -
From: "Brett Porter" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Friday, July 02, 2004 2:33 AM
Subject: Re: cvs commit: maven/src/java/org/apache/maven/plugin
PluginManager.java
> Emmanuel,
>
> This is checking the wrong directory - the user plugin directory is
usually
> empty (ie jars in $MAVEN_HOME_LOCAL/plugins). It should be checking the
first
> one: pluginFiles. (that is $MAVEN_HOME/plugins)
>
> Also, wouldn't userPluginFiles.isEmpty() be much easier? :)
Done.
>
> - Brett
>
> >Map pluginFiles = getPluginFiles( pluginsDir, true );
> > -pluginFiles.putAll( getPluginFiles( userPluginsDir,
false ) );
> > +Map userPluginFiles = getPluginFiles( userPluginsDir,
false );
> > +
> > +if ( !Collections.EMPTY_MAP.equals( userPluginFiles ) &&
> > +Collections.EMPTY_MAP.hashCode() ==
userPluginFiles.hashCode()
> > )
> > +{
> > +pluginFiles.putAll( userPluginFiles );
> > +}
> > +else
> > +{
> > +throw new MavenException( "Maven was badly installed.
Please
> > reinstall it." );
> > +}
> > +
>
> -
> 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]
cvs commit: maven/src/java/org/apache/maven/plugin PluginManager.java
evenisse2004/07/02 03:55:20
Modified:src/java/org/apache/maven/plugin Tag: MAVEN-1_0-BRANCH
PluginManager.java
Log:
Fix installation checker.
Revision ChangesPath
No revision
No revision
1.70.4.50 +9 -7 maven/src/java/org/apache/maven/plugin/PluginManager.java
Index: PluginManager.java
===
RCS file: /home/cvs/maven/src/java/org/apache/maven/plugin/PluginManager.java,v
retrieving revision 1.70.4.49
retrieving revision 1.70.4.50
diff -u -r1.70.4.49 -r1.70.4.50
--- PluginManager.java1 Jul 2004 20:20:36 - 1.70.4.49
+++ PluginManager.java2 Jul 2004 10:55:19 - 1.70.4.50
@@ -228,6 +228,13 @@
setPluginsDir( new File( mavenSession.getRootContext().getPluginsDir() ) );
setUnpackedPluginsDir( new File(
mavenSession.getRootContext().getUnpackedPluginsDir() ) );
setUserPluginsDir( new File(
mavenSession.getRootContext().getUserPluginsDir() ) );
+
+if ( !getPluginsDir().isDirectory() ||
+ ( getPluginsDir().listFiles() != null &&
+ getPluginsDir().listFiles().length == 0 ) )
+{
+throw new MavenException( "Maven was badly installed. Please reinstall
it." );
+}
if ( log.isDebugEnabled() )
{
@@ -243,14 +250,9 @@
Map pluginFiles = getPluginFiles( pluginsDir, true );
Map userPluginFiles = getPluginFiles( userPluginsDir, false );
-if ( !Collections.EMPTY_MAP.equals( userPluginFiles ) &&
-Collections.EMPTY_MAP.hashCode() == userPluginFiles.hashCode() )
+if ( !userPluginFiles.isEmpty() )
{
pluginFiles.putAll( userPluginFiles );
-}
-else
-{
-throw new MavenException( "Maven was badly installed. Please reinstall
it." );
}
Map pluginDirs = expandPluginFiles( pluginFiles );
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven build-bootstrap.xml
evenisse2004/07/02 02:52:48
Modified:.Tag: MAVEN-1_0-BRANCH build-bootstrap.xml
Log:
Fix properties declaration for necessary jars when maven.repo.local is define in
build.properties.
Revision ChangesPath
No revision
No revision
1.212.2.15 +8 -8 maven/build-bootstrap.xml
Index: build-bootstrap.xml
===
RCS file: /home/cvs/maven/build-bootstrap.xml,v
retrieving revision 1.212.2.14
retrieving revision 1.212.2.15
diff -u -r1.212.2.14 -r1.212.2.15
--- build-bootstrap.xml 1 Jul 2004 14:23:38 - 1.212.2.14
+++ build-bootstrap.xml 2 Jul 2004 09:52:48 - 1.212.2.15
@@ -34,6 +34,14 @@
maven.home = ${maven.home}
maven.home.local = ${maven.home.local}
maven.repo.local = ${maven.repo.local}
+
+
+
+
+
+
+
+
+--
| WARNING WARNING WARNING WARNING WARNING WARNING WARNING
@@ -399,14 +407,6 @@
-
-
-
-
-
-
-
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPXDOC-80) Support global theme
The following issue has been updated:
Updater: Joerg Schaible (mailto:[EMAIL PROTECTED])
Date: Fri, 2 Jul 2004 5:04 AM
Comment:
xdoc-theme.diff
Updated patch to support a global theme. Patch for plugin.jelly and
xdoc/properties.xml.
Changes:
Attachment changed to xdoc-theme.diff
-
For a full history of the issue, see:
http://jira.codehaus.org/browse/MPXDOC-80?page=history
-
View the issue:
http://jira.codehaus.org/browse/MPXDOC-80
Here is an overview of the issue:
-
Key: MPXDOC-80
Summary: Support global theme
Type: Improvement
Status: Open
Priority: Major
Original Estimate: 10 minutes
Time Spent: Unknown
Remaining: 10 minutes
Project: maven-xdoc-plugin
Assignee: Jason van Zyl
Reporter: Joerg Schaible
Created: Tue, 17 Feb 2004 8:18 AM
Updated: Fri, 2 Jul 2004 5:04 AM
Description:
While it is possible to set an URL for an own theme using the new property
maven.xdoc.theme.url, you cannot tell the xdoc plugin which local file you are using.
The current approach enforces every project to have its own copy of the theme. This is
extremly nasty in combination with multiproject.
Proposal: Support a new property maven.xdoc.theme.file, that defines the local
location of the theme file. This file is copied into the ${maven.docs.dest}/style
directory.
Please have a look at jakarta-commons, they suffer from this problem also:
http://www.mail-archive.com/commons-dev%40jakarta.apache.org/index.html#35557
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
maven.src.dir
Hi all, I was wondering if any of you could help me. I'm looking for at get method which returns a value when you provide a key like maven.xxx.xxx (e.g. maven.src.dir, maven.build.dir) but I can't find the class. Could some of you please help me? regards, J. Andersen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs changes.xml
dion2004/07/02 01:13:50 Modified:nsis project.xml nsis/xdocs changes.xml Log: Bump version Add changes entry Revision ChangesPath 1.9 +1 -1 maven-plugins/nsis/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/nsis/project.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- project.xml 25 Jun 2004 15:24:30 - 1.8 +++ project.xml 2 Jul 2004 08:13:50 - 1.9 @@ -23,7 +23,7 @@ 3 maven-nsis-plugin Maven NSIS Plug-in - 1.0 + 1.1-SNAPSHOT A plugin to generate Win32 installer programs using NSIS NSIS Plugin for Maven http://maven.apache.org/reference/plugins/nsis/ 1.2 +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.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- changes.xml 13 May 2004 11:07:57 - 1.1 +++ changes.xml 2 Jul 2004 08:13:50 - 1.2 @@ -25,6 +25,7 @@ + Add some basic documentation - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs index.xml
dion2004/07/02 01:13:07
Modified:nsis/xdocs index.xml
Log:
Format
Revision ChangesPath
1.3 +1 -1 maven-plugins/nsis/xdocs/index.xml
Index: index.xml
===
RCS file: /home/cvs/maven-plugins/nsis/xdocs/index.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- index.xml 2 Jul 2004 08:12:23 - 1.2
+++ index.xml 2 Jul 2004 08:13:07 - 1.3
@@ -54,7 +54,7 @@
Once you've run dist, run the nsis goal. This
-produces an executable in ${maven.build.dir}/${maven.final.name}.exe
+produces an executable in
${maven.build.dir}/${maven.final.name}.exe
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs index.xml
dion2004/07/02 01:12:23
Modified:nsis/xdocs index.xml
Log:
Basic using docs
Revision ChangesPath
1.2 +11 -1 maven-plugins/nsis/xdocs/index.xml
Index: index.xml
===
RCS file: /home/cvs/maven-plugins/nsis/xdocs/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 2 Jul 2004 07:47:17 - 1.1
+++ index.xml 2 Jul 2004 08:12:23 - 1.2
@@ -46,6 +46,16 @@
-
+
+
+The plugin creates an installation program from your
distribution,
+as created by maven dist. The dist goal must be
+run before using the plugin.
+
+
+Once you've run dist, run the nsis goal. This
+produces an executable in ${maven.build.dir}/${maven.final.name}.exe
+
+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Clearly separated RMI Client and Server JARs
Jason van Zyl wrote: On Thu, 2004-07-01 at 11:35, Laszlo Papp wrote: Is there a clear solution for this kind of problematic ? This is actually one of the nastiest use cases we are trying to sort out at the moment. All RMI-based solutions do this sort of thing and we're definitely working on a solution. This violates maven's notion of one artifact per project but all RMI-like compilers make the main JAR and client stubs so we'll find something that works. Thanx a lot. Chao: Laci Hi, Thanx for the answer... Let's hope for the best... :-) But it is obviously strange from the RMI framework that one needs the _implementation_ classes in order to compile an independent interface for that... I hope it'll once work. Good luck... :-) Chao: Laci -- Laszlo Papp Epigenomics AG www.epigenomics.com Kleine Präsidentenstr. 1. +49-30-24345-0 10178 Berlin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Clearly separated RMI Client and Server JARs
Mark Church wrote: What about a 3rd project that contains Impl.java? Both the client and server projects could then depend on this project. Mark Church Hi, It would look better but it would still violate the concept of the preferred DAG (Directed Acyclic Graph) dependency graphs... Between the server and the 3rd JAR there would be a cyclic dependency. Chao: Laci -- Laszlo Papp Epigenomics AG www.epigenomics.com Kleine Präsidentenstr. 1. +49-30-24345-0 10178 Berlin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPECLIPSE-5) Generated source support
The following issue has been updated: Updater: David Eric Pugh (mailto:[EMAIL PROTECTED]) Date: Fri, 2 Jul 2004 3:48 AM Comment: I got an email back from JvZ (extract below) that I am going to use as a my approach to get this done. This affects me as well when doing work with XDoclet generated mapping files for Hibernate as well. Extract from JvZ: In all of the m2 code I have been using: $pom.build.directory/generated-sources which defaults to $basedir/target/generated-sources Now, undoubtedly, some folks will want to perform some actions on generated sources. Something like generating javadoc from generated sources, or running xdoclet on generated sources. So this could be expanded on on a per-plugin basis but we might want to keep all the generated sources in the same directory to perform a common action, like a javadoc sweep or something like that. So maybe something like: $basedir/target/generated-sources/xdoclet might be prudent. This way each plugin that might produce generated sources can have a distinct sink but with a common root directory common operations like javadoc can be performed on the generated sources. Changes: assignee changed to David Eric Pugh environment changed to Fix Version changed to 1.8 - For a full history of the issue, see: http://jira.codehaus.org/browse/MPECLIPSE-5?page=history - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-5 Here is an overview of the issue: - Key: MPECLIPSE-5 Summary: Generated source support Type: Improvement Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-eclipse-plugin Fix Fors: 1.8 Assignee: David Eric Pugh Reporter: Archimedes Trajano Created: Fri, 31 Oct 2003 5:16 AM Updated: Fri, 2 Jul 2004 3:48 AM Description: Maven already provides the tag maven.build.src which contains the directory for generated sources Can you add the following snippet into the classpath.jelly file? 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]
cvs commit: maven-plugins/nsis/xdocs index.xml
dion2004/07/02 00:47:17 Added: nsis/xdocs index.xml Log: Add basic overview docs. No real meat yet. Revision ChangesPath 1.1 maven-plugins/nsis/xdocs/index.xml Index: index.xml === Maven NSIS Plug-in dIon Gillard This plugin is used to generate Win32 installer programs using NSIS DocumentDescription Properties The behavior of this plugin can be altered via several properties. This document describes each property available, and the default used. Goals This plugin provides goals to help in building the installer. This document describes each goal available. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPHIBERNATE-6) Aggregate mappings and schema-export from multiple base dirs
Message: The following issue has been closed. Resolver: David Eric Pugh Date: Fri, 2 Jul 2004 3:39 AM Alex, I have applied your changes. A couple of edits I had to make, so can you verify the changes: 1) I only applied the first patch.. As far as I could tell the second patch was a subset of the first? In the future, make sure your patches are all seperate, or clearly identify which ones are invalide. 2) Changed all the System.out's to use a LOG object. Check out the verboseness.. some of the LOG.info maybe be LOG.debug. 3) Typos.. Had a couple hiberante's and aggragants floating about! I type hiberante all the time as well! Thanks for the contribution! - View the issue: http://jira.codehaus.org/browse/MPHIBERNATE-6 Here is an overview of the issue: - Key: MPHIBERNATE-6 Summary: Aggregate mappings and schema-export from multiple base dirs Type: New Feature Status: Closed Priority: Trivial Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-hibernate-plugin Fix Fors: 1.2 Assignee: David Eric Pugh Reporter: Alex Shnyderman Created: Thu, 1 Jul 2004 2:02 PM Updated: Fri, 2 Jul 2004 3:39 AM Description: 1. Added aggregate-mappings goal. When executed the goal will aggregate mappings from separate mapping files into one single mapping file. 2. Modified schema-export goal, so that you can specify multiple base directories. Basically my generated classes sit in a separate tree from my hbm.xml mapping files. With unpatched version I was forced to put mapping files into the same dir as my generated classes. So I modified SchemaExportBean a bit to accommodate multiple base directories. - 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/hibernate project.xml
epugh 2004/07/02 00:38:56 Modified:hibernate project.xml Log: Add section for patch from Alex Revision ChangesPath 1.33 +6 -0 maven-plugins/hibernate/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/hibernate/project.xml,v retrieving revision 1.32 retrieving revision 1.33 diff -u -r1.32 -r1.33 --- project.xml 27 Jun 2004 08:05:07 - 1.32 +++ project.xml 2 Jul 2004 07:38:56 - 1.33 @@ -67,6 +67,12 @@ + + + Alex Shneyderman + [EMAIL PROTECTED] + + hibernate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/hibernate/src/plugin-test/src/etc Component.hbm.xml
epugh 2004/07/02 00:32:53
Modified:hibernate/xdocs changes.xml properties.xml goals.xml
hibernate/src/main/org/apache/maven/hibernate/jelly
HibernateTagLibrary.java SchemaExportTag.java
hibernate plugin.jelly plugin.properties
hibernate/src/plugin-test project.xml project.properties
maven.xml
hibernate/src/main/org/apache/maven/hibernate/beans
SchemaExportBean.java
Added: hibernate/src/main/org/apache/maven/hibernate/jelly
AggregateMappingsTag.java
hibernate/src/plugin-test/src/main/org/apache/maven/hibernate
Component.java
hibernate/src/main/org/apache/maven/hibernate/beans
CommonOperationsBean.java
MappingsAggregatorBean.java
hibernate/src/plugin-test/src/etc Component.hbm.xml
Log:
MPHIBERNATE-6, allow multiple base dirs and new aggregate-mappings goal.
Revision ChangesPath
1.16 +3 -1 maven-plugins/hibernate/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/hibernate/xdocs/changes.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- changes.xml 27 Jun 2004 08:05:07 - 1.15
+++ changes.xml 2 Jul 2004 07:32:52 - 1.16
@@ -24,7 +24,9 @@
Michal Maczka
-
+
+ New aggregate-mappings goal to aggregate multiple .hbm files into one
file.
+ Added multiple base directories for mapping files
Update to hibernate-2.1.3.
1.6 +10 -4 maven-plugins/hibernate/xdocs/properties.xml
Index: properties.xml
===
RCS file: /home/cvs/maven-plugins/hibernate/xdocs/properties.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- properties.xml21 Jun 2004 10:36:36 - 1.5
+++ properties.xml2 Jul 2004 07:32:52 - 1.6
@@ -96,8 +96,8 @@
maven.hibernate.input.dir
Yes
- Used to generate the url value for Gump
- Indicates base directory where mapping files. It defaults
+ Comma-seperated list of base directories indicating where
+ mapping files are located. It defaults
to ${maven.build.dest}.
@@ -105,7 +105,7 @@
maven.hibernate.input.includes
Yes
- Comma-separated list of patterns of Hiberante mapping files,
+ Comma-separated list of patterns of Hibernate mapping files,
which will be included during generation process.
Note: Files are relative to
@@ -119,7 +119,7 @@
maven.hibernate.input.excludes
Yes
- Comma-separated list of patterns of Hiberante mapping files,
+ Comma-separated list of patterns of Hibernate mapping files,
which will be excluded during generation process.
Note: Files are relative to
@@ -133,6 +133,12 @@
Yes
String used to separate commands in SQL output.
+
+ maven.hibernate.aggregate.output.file
+ Yes
+ When aggregate-mappings is run, this file will contain
the aggregated mappings
+
+
1.4 +7 -0 maven-plugins/hibernate/xdocs/goals.xml
Index: goals.xml
===
RCS file: /home/cvs/maven-plugins/hibernate/xdocs/goals.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- goals.xml 1 Jun 2004 15:31:04 - 1.3
+++ goals.xml 2 Jul 2004 07:32:52 - 1.4
@@ -35,6 +35,13 @@
Creates SQL DDL file from set of *.hbm.xml files
+
+
+
+ hibernate:aggregate-mappings
+
+ Aggregates multiple hibernate mappings into one
+
1.3 +3 -2
maven-plugins/hibernate/src/main/org/apache/maven/hibernate/jelly/HibernateTagLibrary.java
Index: HibernateTagLibrary.java
===
RCS file:
/home/cvs/maven-plugins/hibernate/src/main/org/apach
cvs commit: maven-plugins/hibernate/src/plugin-test/src/etc - New directory
epugh 2004/07/02 00:32:47 maven-plugins/hibernate/src/plugin-test/src/etc - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/hibernate/src/plugin-test .cvsignore
epugh 2004/07/02 00:32:05 Added: hibernate/src/plugin-test .cvsignore Log: Ignore Eclipse generated files Revision ChangesPath 1.1 maven-plugins/hibernate/src/plugin-test/.cvsignore Index: .cvsignore === target .classpath .project - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPHIBERNATE-6) Aggregate mappings and schema-export from multiple base dirs
The following issue has been updated: Updater: David Eric Pugh (mailto:[EMAIL PROTECTED]) Date: Fri, 2 Jul 2004 3:29 AM Comment: Move to be fixed in 1.2 Changes: timeoriginalestimate changed from 0 timeestimate changed from 0 minutes Fix Version changed to 1.2 - For a full history of the issue, see: http://jira.codehaus.org/browse/MPHIBERNATE-6?page=history - View the issue: http://jira.codehaus.org/browse/MPHIBERNATE-6 Here is an overview of the issue: - Key: MPHIBERNATE-6 Summary: Aggregate mappings and schema-export from multiple base dirs Type: New Feature Status: Open Priority: Trivial Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-hibernate-plugin Fix Fors: 1.2 Assignee: David Eric Pugh Reporter: Alex Shnyderman Created: Thu, 1 Jul 2004 2:02 PM Updated: Fri, 2 Jul 2004 3:29 AM Description: 1. Added aggregate-mappings goal. When executed the goal will aggregate mappings from separate mapping files into one single mapping file. 2. Modified schema-export goal, so that you can specify multiple base directories. Basically my generated classes sit in a separate tree from my hbm.xml mapping files. With unpatched version I was forced to put mapping files into the same dir as my generated classes. So I modified SchemaExportBean a bit to accommodate multiple base directories. - 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: Jira: setting up versions and roadmaps
> -Original Message- > From: Eric Pugh [mailto:[EMAIL PROTECTED] > Sent: vendredi 2 juillet 2004 08:49 > To: Maven-Dev > Subject: Jira: setting up versions and roadmaps > > Hi all, > > Maybe the answer is RTFM.. :-) However, I am hunting around trying to > setup versions for the MPHIBERNATE project in Jira, and I think I don't > have > the juice to do it.. Can someone setup a couple versions? Done > > And, just to reconfirm, since the Hibernate plugin is on 1.2-snapshot, > that > means the current public version would be 1.1, and we are developing 1.2 > right now, and when I'm ready to cut the plugin, we remove the -snapshot, > cut the plugin, and then bump it to 1.3-snapshot? Exactly -Vincent > > Eric > > > - > 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: (MPNSIS-4) shortcut to the executable jar not needed to be hard coded
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Fri, 2 Jul 2004 2:59 AM
User bad
-
View the issue:
http://jira.codehaus.org/browse/MPNSIS-4
Here is an overview of the issue:
-
Key: MPNSIS-4
Summary: shortcut to the executable jar not needed to be hard coded
Type: Wish
Status: Closed
Priority: Major
Resolution: WON'T FIX
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-nsis-plugin
Assignee: dion gillard
Reporter: Geoffrey
Created: Thu, 1 Jul 2004 2:58 PM
Updated: Fri, 2 Jul 2004 2:59 AM
Description:
Currently I am hardcoding a shortcut to the executable jar:
CreateShortCut "${PROJECT_STARTMENU_FOLDER}\NetworkTools.lnk"
"$INSTDIR\NetworkTools-1.2.1.jar" "" "$INSTDIR" 0
Problem here is the version number: "1.2.1", this is of course dynamic. Also the jar
name could depend on the pom :)
Maybe I am overlooking a way to do this dynamic?
Low documentation makes this wonderfull plugin underused.
-
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: (MPNSIS-4) shortcut to the executable jar not needed to be hard coded
The following comment has been added to this issue:
Author: dion gillard
Created: Fri, 2 Jul 2004 2:59 AM
Body:
Yes, please raise an issue for the docs
-
View this comment:
http://jira.codehaus.org/browse/MPNSIS-4?page=comments#action_21290
-
View the issue:
http://jira.codehaus.org/browse/MPNSIS-4
Here is an overview of the issue:
-
Key: MPNSIS-4
Summary: shortcut to the executable jar not needed to be hard coded
Type: Wish
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-nsis-plugin
Assignee: dion gillard
Reporter: Geoffrey
Created: Thu, 1 Jul 2004 2:58 PM
Updated: Fri, 2 Jul 2004 2:59 AM
Description:
Currently I am hardcoding a shortcut to the executable jar:
CreateShortCut "${PROJECT_STARTMENU_FOLDER}\NetworkTools.lnk"
"$INSTDIR\NetworkTools-1.2.1.jar" "" "$INSTDIR" 0
Problem here is the version number: "1.2.1", this is of course dynamic. Also the jar
name could depend on the pom :)
Maybe I am overlooking a way to do this dynamic?
Low documentation makes this wonderfull plugin underused.
-
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]
