RE: [vote] AspectJ Plugin Release
+1 -Original Message- From: Carlos Sanchez [mailto:[EMAIL PROTECTED] Sent: vendredi 9 juillet 2004 16:56 To: 'Maven Developers List' Subject: [vote] AspectJ Plugin Release Hi, I would like to release the AspectJ Plugin 3.1.1 o Output info messages to log using jelly:log o Use maven:get instead of pom.getPluginContext Fixed bugs: o Check that unitTestSourceDirectory is defined in pom Issue: MPASPECTJ- 11. o Check that aspectSourceDirectory is defined in pom Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net - 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-plugins/nsis/src/plugin-resources/templates project.jelly setup.jelly
dion2004/07/10 01:57:27
Modified:nsis/xdocs customizing.xml changes.xml
nsis/src/plugin-resources/templates project.jelly
setup.jelly
Log:
Rename ORGANIZATION constant to PROJECT_ORGANIZATION.
Revision ChangesPath
1.7 +2 -2 maven-plugins/nsis/xdocs/customizing.xml
Index: customizing.xml
===
RCS file: /home/cvs/maven-plugins/nsis/xdocs/customizing.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- customizing.xml 5 Jul 2004 12:39:38 - 1.6
+++ customizing.xml 10 Jul 2004 08:57:27 - 1.7
@@ -82,7 +82,6 @@
/p
table
trthConstant/th thValue/th/tr
- trtdORGANIZATION/td td${pom.organization}/td/tr
trtdPROJECT_BUILD_DIR/td td${maven.build.dir}/td/tr
trtdPROJECT_DIST_BIN_DIR/td
td${maven.dist.bin.assembly.dir}/td/tr
trtdPROJECT_DIST_DIR/td td${maven.dist.dir}/td/tr
@@ -91,7 +90,8 @@
trtdPROJECT_LICENSE_TEXT/td
td${maven.nsis.license.text}/td/tr
trtdPROJECT_LOGO/td td${maven.nsis.logo}/td/tr
trtdPROJECT_NAME/td td${pom.name}/td/tr
- trtdPROJECT_REG_KEY/td
tdSOFTWARE\${pom.organization}\${pom.name}\${pom.currentVersion}/td/tr
+ trtdPROJECT_ORGANIZATION/td
td${pom.organization.name}/td/tr
+ trtdPROJECT_REG_KEY/td
tdSOFTWARE\${pom.organization.name}\${pom.name}\${pom.currentVersion}/td/tr
trtdPROJECT_REG_UNINSTALL_KEY/td
tdSoftware\Microsoft\Windows\CurrentVersion\Uninstall\${pom.name}
${pom.currentVersion}/td/tr
trtdPROJECT_STARTMENU_FOLDER/td
td$$SMPROGRAMS\${pom.organization}\${pom.name} ${pom.currentVersion}/td/tr
trtdPROJECT_URL/td td${pom.url}/td/tr
1.15 +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.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- changes.xml 9 Jul 2004 13:59:34 - 1.14
+++ changes.xml 10 Jul 2004 08:57:27 - 1.15
@@ -26,6 +26,7 @@
body
release version=1.2-SNAPSHOT date=Unreleased
+ action dev=dion type=updateRename codeORGANIZATION/code constant to
codePROJECT_ORGANIZATION./code/action
action dev=dion type=fix due-to=GeoffreyCheck maven.nsis.exe exists
before using it./action
action dev=dion type=add due-to=GeoffreyAdd faq/action
action dev=dion type=updateAdd back license to project.xml after the
scm plugin removed it./action
1.11 +1 -1 maven-plugins/nsis/src/plugin-resources/templates/project.jelly
Index: project.jelly
===
RCS file: /home/cvs/maven-plugins/nsis/src/plugin-resources/templates/project.jelly,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- project.jelly 9 Jul 2004 12:52:34 - 1.10
+++ project.jelly 10 Jul 2004 08:57:27 - 1.11
@@ -31,7 +31,6 @@
; generated by ${user.name} from project.xml version ${pom.currentVersion}
; on date ${TODAY}, time ${TSTAMP}
-!define ORGANIZATION ${pom.organization.name}
!define PROJECT_BUILD_DIR ${build}
!define PROJECT_DIST_BIN_DIR ${maven.dist.bin.assembly.dir}
!define PROJECT_DIST_DIR ${maven.dist.dir}
@@ -41,6 +40,7 @@
!define PROJECT_LICENSE_TEXT ${maven.nsis.license.text}
/util:available
!define PROJECT_NAME ${pom.name}
+!define PROJECT_ORGANIZATION ${pom.organization.name}
!define PROJECT_REG_KEY
SOFTWARE\${pom.organization.name}\${pom.name}\${pom.currentVersion}
!define PROJECT_REG_UNINSTALL_KEY
Software\Microsoft\Windows\CurrentVersion\Uninstall\${pom.name} ${pom.currentVersion}
!define PROJECT_STARTMENU_FOLDER $$SMPROGRAMS\${pom.organization.name}\${pom.name}
${pom.currentVersion}
1.16 +1 -1 maven-plugins/nsis/src/plugin-resources/templates/setup.jelly
Index: setup.jelly
===
RCS file: /home/cvs/maven-plugins/nsis/src/plugin-resources/templates/setup.jelly,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- setup.jelly 7 Jul 2004 21:01:52 - 1.15
+++ setup.jelly 10 Jul 2004 08:57:27 - 1.16
@@ -74,7 +74,7 @@
!endif
; The default installation directory
-InstallDir $$PROGRAMFILES\$${ORGANIZATION}\$${PROJECT_NAME} $${PROJECT_VERSION}
+InstallDir $$PROGRAMFILES\$${PROJECT_ORGANIZATION}\$${PROJECT_NAME}
$${PROJECT_VERSION}
; Registry key to check
cvs commit: maven-plugins/nsis/xdocs changes.xml
dion2004/07/10 01:58:27 Modified:nsis/xdocs changes.xml Log: doc update Revision ChangesPath 1.16 +1 -1 maven-plugins/nsis/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/nsis/xdocs/changes.xml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- changes.xml 10 Jul 2004 08:57:27 - 1.15 +++ changes.xml 10 Jul 2004 08:58:27 - 1.16 @@ -26,7 +26,7 @@ body release version=1.2-SNAPSHOT date=Unreleased - action dev=dion type=updateRename codeORGANIZATION/code constant to codePROJECT_ORGANIZATION./code/action + action dev=dion type=updateRename codeORGANIZATION/code constant to codePROJECT_ORGANIZATION/code./action action dev=dion type=fix due-to=GeoffreyCheck maven.nsis.exe exists before using it./action action dev=dion type=add due-to=GeoffreyAdd faq/action action dev=dion type=updateAdd back license to project.xml after the scm plugin removed it./action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs changes.xml
dion2004/07/10 01:58:46 Modified:nsis/xdocs changes.xml Log: doc update Revision ChangesPath 1.17 +1 -1 maven-plugins/nsis/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/nsis/xdocs/changes.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- changes.xml 10 Jul 2004 08:58:27 - 1.16 +++ changes.xml 10 Jul 2004 08:58:46 - 1.17 @@ -25,7 +25,7 @@ /properties body -release version=1.2-SNAPSHOT date=Unreleased +release version=1.2-SNAPSHOT date=In CVS action dev=dion type=updateRename codeORGANIZATION/code constant to codePROJECT_ORGANIZATION/code./action action dev=dion type=fix due-to=GeoffreyCheck maven.nsis.exe exists before using it./action action dev=dion type=add due-to=GeoffreyAdd faq/action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPJIRA-3) The element type link must be terminated by the matching end-tag
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPJIRA-3 Here is an overview of the issue: - Key: MPJIRA-3 Summary: The element type link must be terminated by the matching end-tag Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jira-plugin Versions: 1.1 Assignee: Emmanuel Venisse Reporter: Paul Spencer Created: Sat, 10 Jul 2004 5:26 AM Updated: Sat, 10 Jul 2004 5:26 AM Description: I am getting the following error when generating a JIRA report for an Apache project. Root Cause: The generated link is missing decorator=none maven-jira-plugin:report: [mkdir] Created dir: C:\cvs_apache\jakarta-jetspeed-2\target\jira Downloading http://nagoya.apache.org/jira/secure/secure/IssueNavigator.jspa?view=rsspid=10492sorter/field=issuekeysorter/order=DESCsorter/field=statussorter/order=DESCtempMax=1000reset=true BUILD FAILED File.. c:\maven_repo\1.0-rc4\cache\maven-xdoc-plugin-1.7.2\plugin.jelly Element... x:parse Line.. 119 Column 48 Error on line 27 of document file:/C:/cvs_apache/jakarta-jetspeed-2/target/jira/jira-results.xml : The element type link must be terminated by the matching end-tag /link. Nested exception: The element type link must be terminated by the matching end-tag /link. Total time: 11 seconds Finished at: Sat Jul 10 04:58:27 EDT 2004 - - 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: (MPJIRA-4) issueTrackingUrl must contain an id attribute
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPJIRA-4 Here is an overview of the issue: - Key: MPJIRA-4 Summary: issueTrackingUrl must contain an id attribute Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jira-plugin Versions: 1.1 Assignee: Emmanuel Venisse Reporter: Paul Spencer Created: Sat, 10 Jul 2004 5:35 AM Updated: Sat, 10 Jul 2004 5:35 AM Description: Although the following URLs are equivelement, only the one containing the id attribute will work with the JIRA plugin. http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10492 http://nagoya.apache.org/jira/browse/JS2 When using http://nagoya.apache.org/jira/browse/JS2; for the issueTrackerUrl the following error is received. Notice the pid attribute on the url. Downloading http://nagoya.apache.org/jira/browse/secure/IssueNavigator.jspa?view=rsspid=p://nagoya.apache.org/jira/browse/JS2sorter/field=issuekeysorter/order=DESCsorter/field=statussorter/order=DESCtempMax=1000reset=true Received: [404] for http://nagoya.apache.org/jira/browse/secure/IssueNavigator.jspa?view=rsspid=p://nagoya.apache.org/jira/browse/JS2sorter/field=issuekeysorter/order=DESCsorter/field=statussorter/order=DESCtempMax=1000reset=true Received: [404] for http://nagoya.apache.org/jira/browse/secure/IssueNavigator.jspa?view=rsspid=p://nagoya.apache.org/jira/browse/JS2sorter/field=issuekeysorter/order=DESCsorter/field=statussorter/order=DESCtempMax=1000reset=true BUILD FAILED File.. c:\maven_repo\1.0-rc4\cache\maven-xdoc-plugin-1.7.2\plugin.jelly Element... x:parse Line.. 119 Column 48 Error on line 27 of document file:/C:/cvs_apache/jakarta-jetspeed-2/target/jira/jira-results.xml : The element type link must be terminated by the matching end-tag /link. Nested exception: The element type link must be terminated by the matching end-tag /link. Total time: 4 seconds Finished at: Sat Jul 10 05:31:54 EDT 2004 C:\cvs_apache\jakarta-jetspeed-2 - 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-275) ability to mark goals as private ( not allowed to be the first goal called )
The following comment has been added to this issue: Author: Juha Komulainen Created: Sat, 10 Jul 2004 5:38 AM Body: If I recall correctly, in Ant tasks starting with '-' will be considered private. While they can be called from command-line, they won't be listed on ant -projecthelp. Perhaps something like this would work? - View this comment: http://jira.codehaus.org/browse/MAVEN-275?page=comments#action_21585 - View the issue: http://jira.codehaus.org/browse/MAVEN-275 Here is an overview of the issue: - Key: MAVEN-275 Summary: ability to mark goals as private ( not allowed to be the first goal called ) Type: Improvement Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: jelly/ant integration Fix Fors: 1.1 Assignee: Reporter: Peter Lynch Created: Fri, 14 Feb 2003 3:51 PM Updated: Sat, 10 Jul 2004 5:38 AM Description: Frequently goals are written to perform some arbitrary task that would not be useful if performed in isolation. Other goals are meant to be called directly by the user. There should be a way to mark a goal as 'private', and not allow that goal to start an execution chain. This would also allow us to be more choosy as to which goals gets displayed when using 'maven -g' - 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-plugins/javadoc plugin.jelly
Thanks, I didn't find this syntax!!
I'll correct it.
Where are documented the keywords in Jelly??
Arnaud
-Message d'origine-
De : Dion Gillard [mailto:[EMAIL PROTECTED]
Envoyé : samedi 10 juillet 2004 01:53
À : Maven Developers List
Objet : Re: cvs commit: maven-plugins/javadoc plugin.jelly
On 9 Jul 2004 18:50:48 -, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
aheritier2004/07/09 11:50:48
Modified:javadoc plugin.jelly
Log:
To generate javadoc when sourceModifications are used, we copy in a temporary
directory all the
needed source files.
Fix MPJAVADOC-32
+ j:if test=${pom.build.sourceModifications!=null amp;amp;
!pom.build.sourceModifications.isEmpty()}
I always find 'and' easier to read than amp;amp;
--
http://www.multitask.com.au/people/dion/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven-plugins/javadoc plugin.jelly
It's actually part of jexland neither of them are well documented.
On Sat, 10 Jul 2004 11:45:19 +0200, Arnaud Heritier
[EMAIL PROTECTED] wrote:
Thanks, I didn't find this syntax!!
I'll correct it.
Where are documented the keywords in Jelly??
Arnaud
-Message d'origine-
De : Dion Gillard [mailto:[EMAIL PROTECTED]
Envoyé : samedi 10 juillet 2004 01:53
À : Maven Developers List
Objet : Re: cvs commit: maven-plugins/javadoc plugin.jelly
On 9 Jul 2004 18:50:48 -, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
aheritier2004/07/09 11:50:48
Modified:javadoc plugin.jelly
Log:
To generate javadoc when sourceModifications are used, we copy in a temporary
directory all the
needed source files.
Fix MPJAVADOC-32
+ j:if test=${pom.build.sourceModifications!=null amp;amp;
!pom.build.sourceModifications.isEmpty()}
I always find 'and' easier to read than amp;amp;
--
http://www.multitask.com.au/people/dion/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://www.multitask.com.au/people/dion/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins .cvsignore
vmassol 2004/07/10 02:56:30 Modified:..cvsignore Log: Added eclipse dir .settings to ignore file Revision ChangesPath 1.4 +1 -0 maven-plugins/.cvsignore Index: .cvsignore === RCS file: /home/cvs/maven-plugins/.cvsignore,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- .cvsignore21 Sep 2003 13:37:07 - 1.3 +++ .cvsignore10 Jul 2004 09:56:30 - 1.4 @@ -4,3 +4,4 @@ .classpath .project build.properties +.settings - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPJAR-32) Add the ability to include the source code in the jar
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPJAR-32 Here is an overview of the issue: - Key: MPJAR-32 Summary: Add the ability to include the source code in the jar Type: New Feature Status: Open Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jar-plugin Assignee: Jason van Zyl Reporter: dion gillard Created: Sat, 10 Jul 2004 5:57 AM Updated: Sat, 10 Jul 2004 5:57 AM Description: Often projects ship jars that include the source code, for convenience, or use in an IDE. This patch adds: - a plugin property, maven.jar.include.source, defaulted to false, that is used to decide whether source is included in the jar - a plugin property, maven.jar.source.path, defaulted to 'src', which is the location of the source in the jar - a goal to copy source into the maven.build.dest directory before jar'ing. - 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: (MPJAR-32) Add the ability to include the source code in the jar
The following issue has been updated: Updater: dion gillard (mailto:[EMAIL PROTECTED]) Date: Sat, 10 Jul 2004 5:58 AM Comment: Patch to allow creation of source jars Changes: Attachment changed to jar-source.txt - For a full history of the issue, see: http://jira.codehaus.org/browse/MPJAR-32?page=history - View the issue: http://jira.codehaus.org/browse/MPJAR-32 Here is an overview of the issue: - Key: MPJAR-32 Summary: Add the ability to include the source code in the jar Type: New Feature Status: Open Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jar-plugin Assignee: Jason van Zyl Reporter: dion gillard Created: Sat, 10 Jul 2004 5:57 AM Updated: Sat, 10 Jul 2004 5:58 AM Description: Often projects ship jars that include the source code, for convenience, or use in an IDE. This patch adds: - a plugin property, maven.jar.include.source, defaulted to false, that is used to decide whether source is included in the jar - a plugin property, maven.jar.source.path, defaulted to 'src', which is the location of the source in the jar - a goal to copy source into the maven.build.dest directory before jar'ing. - 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 and CruiseControl Plugin
Could someone create a couple versions for the CruiseControl plugin in JIRA? Everything is under Unscheduled. Thanks! Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA and CruiseControl Plugin
Shouldn't the currentVersion for the plugin be 1.4-SNAPSHOT? On Sat, 10 Jul 2004 12:20:08 +0100, Eric Pugh [EMAIL PROTECTED] wrote: Could someone create a couple versions for the CruiseControl plugin in JIRA? Everything is under Unscheduled. Thanks! Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA and CruiseControl Plugin
Doing it now... On Sat, 10 Jul 2004 12:20:08 +0100, Eric Pugh [EMAIL PROTECTED] wrote: Could someone create a couple versions for the CruiseControl plugin in JIRA? Everything is under Unscheduled. Thanks! Eric -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Carlos Sanchez as maven-plugins developers
+1 -Original Message- From: Heritier Arnaud [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 12, 2004 6:46 PM To: Maven Developers List Subject: RE: [VOTE] Carlos Sanchez as maven-plugins developers +1 from me. I already voted yesterday but I don't see my mail :-( #Arnaud -Message d'origine- De : Vincent Massol [mailto:[EMAIL PROTECTED] Envoyé : mardi 11 mai 2004 19:33 À : 'Maven Developers List' Objet : [VOTE] Carlos Sanchez as maven-plugins developers Hi, Following my post on the subject of Is it possible to accept a new committer for a specific plugin?, I'd like to propose Carlos as a maven-plugins committer. Carlos has provided an excellent patch (it's actually a full rewrite) for the AspectJ plugin. I suggest that we let him improve and maintain the AspectJ plugin himself! :-) +1 from me Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven.gen.src added to maven?
Hi all,
Can we add maven.gen.src=${maven.build.dest}/generated-sources?
I've been doing a bunch of work with the Hibernate, Xdoclet, and Eclipse
plugins for a client. One of the challenges we had was getting source code
generated via the Xdoclet and Hibernate plugins to play nice w/ a normal
Maven build as well as using it within Eclipse. Eclipse is their primary
environment for their developers, so Maven had to play nice with Eclipse.
The biggest challenge was getting various generated code bits into the
/target directory. When we put files in /target/classes and then ran builds
in Eclipse the /target/classes directory would be completely cleaned, and
wiped out the generated code that was needed.
After chatting with JvZ, I added to the Eclipse plugin the ability to add as
seperate source directories anything in ${maven.gen.src}. So, after
generating hibernate mapping files and a ddl I would have:
/target/generated-sources/xdoclet
/target/generated-sources/schema
and they would each be a source folder in Eclipse. Works great. However,
because maven.gen.src is defined in the Eclipse plugin only, you have to
specify for the hibernate and xdoclet plugins the full path to generate
source into. It would be much simpler if maven.gen.src worked the same way
that maven.build.dest and other properties like that work.
Eric
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: JIRA and CruiseControl Plugin
Yes, it should be.. I actually noticed it yesterday while fixing up the xdcos/changes.xml doc. Thanks for adding the versions for CC. While you are at it, could you do the same for the Hibernate plugin? Eric -Original Message- From: Dion Gillard [mailto:[EMAIL PROTECTED] Sent: Saturday, July 10, 2004 12:44 PM To: Maven Developers List; [EMAIL PROTECTED] Subject: Re: JIRA and CruiseControl Plugin Shouldn't the currentVersion for the plugin be 1.4-SNAPSHOT? On Sat, 10 Jul 2004 12:20:08 +0100, Eric Pugh [EMAIL PROTECTED] wrote: Could someone create a couple versions for the CruiseControl plugin in JIRA? Everything is under Unscheduled. Thanks! Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven.gen.src added to maven?
Do we want to do this so close to 1.0?
On Sat, 10 Jul 2004 13:33:30 +0100, Eric Pugh [EMAIL PROTECTED] wrote:
Hi all,
Can we add maven.gen.src=${maven.build.dest}/generated-sources?
I've been doing a bunch of work with the Hibernate, Xdoclet, and Eclipse
plugins for a client. One of the challenges we had was getting source code
generated via the Xdoclet and Hibernate plugins to play nice w/ a normal
Maven build as well as using it within Eclipse. Eclipse is their primary
environment for their developers, so Maven had to play nice with Eclipse.
The biggest challenge was getting various generated code bits into the
/target directory. When we put files in /target/classes and then ran builds
in Eclipse the /target/classes directory would be completely cleaned, and
wiped out the generated code that was needed.
After chatting with JvZ, I added to the Eclipse plugin the ability to add as
seperate source directories anything in ${maven.gen.src}. So, after
generating hibernate mapping files and a ddl I would have:
/target/generated-sources/xdoclet
/target/generated-sources/schema
and they would each be a source folder in Eclipse. Works great. However,
because maven.gen.src is defined in the Eclipse plugin only, you have to
specify for the hibernate and xdoclet plugins the full path to generate
source into. It would be much simpler if maven.gen.src worked the same way
that maven.build.dest and other properties like that work.
Eric
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://www.multitask.com.au/people/dion/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/clover/xdocs changes.xml
vmassol 2004/07/10 06:04:46
Modified:clover plugin.jelly project.xml
clover/xdocs changes.xml
Log:
Updated to Clover Ant 1.3_01.
Revision ChangesPath
1.26 +9 -3 maven-plugins/clover/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/clover/plugin.jelly,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- plugin.jelly 6 Jul 2004 12:37:17 - 1.25
+++ plugin.jelly 10 Jul 2004 13:04:46 - 1.26
@@ -55,12 +55,12 @@
ant:pathelement path=${maven.clover.jar}/
/j:when
j:otherwise
- ant:pathelement path=${plugin.getDependencyPath('clover')}/
+ ant:pathelement path=${plugin.getDependencyPath('clover:clover-ant')}/
/j:otherwise
/j:choose
/ant:path
- ant:taskdef resource=clovertasks/
+ant:taskdef resource=clovertasks/
ant:typedef resource=clovertypes/
j:set var=cloverDatabase
@@ -74,7 +74,13 @@
ant:mkdir dir=${maven.clover.build.classes}/
ant:mkdir dir=${maven.clover.database.dir}/
ant:mkdir dir=${cloverReportDirectory}/
-
+
+!-- Add the Clover license to the classpath. --
+j:invokeStatic className=java.lang.System method=setProperty
+ j:arg type=java.lang.String value=clover.license.path/
+ j:arg type=java.lang.String
value=${plugin.getDependencyPath('clover:clover-30day-eval')}/
+/j:invokeStatic
+
/goal
!--
1.43 +9 -3 maven-plugins/clover/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven-plugins/clover/project.xml,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- project.xml 25 Jun 2004 15:24:27 - 1.42
+++ project.xml 10 Jul 2004 13:04:46 - 1.43
@@ -23,7 +23,7 @@
pomVersion3/pomVersion
idmaven-clover-plugin/id
nameMaven Clover Plugin/name
- currentVersion1.5/currentVersion
+ currentVersion1.6-SNAPSHOT/currentVersion
description/
shortDescriptionProduce Clover reports/shortDescription
urlhttp://maven.apache.org/reference/plugins/clover//url
@@ -102,11 +102,17 @@
dependencies
dependency
groupIdclover/groupId
- artifactIdclover/artifactId
- version1.2.3/version
+ artifactIdclover-ant/artifactId
+ version1.3_01/version
properties
classloaderroot/classloader
/properties
+/dependency
+dependency
+ groupIdclover/groupId
+ artifactIdclover-30day-eval/artifactId
+ version1.0/version
+ typelicense/type
/dependency
/dependencies
/project
1.31 +5 -0 maven-plugins/clover/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/clover/xdocs/changes.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- changes.xml 12 Jun 2004 05:20:57 - 1.30
+++ changes.xml 10 Jul 2004 13:04:46 - 1.31
@@ -25,6 +25,11 @@
author email=[EMAIL PROTECTED]Emmanuel Venisse/author
/properties
body
+release version=1.6-SNAPSHOT date=in CVS
+ action dev=vmassol type=update
+Updated to Clover Ant 1.3_01.
+ /action
+/release
release version=1.5 date=2004-05-15
action dev=vmassol type=fixDo not execute Clover if there are no tests
to run Clover on. This prevents an error happening in the
codeclover:on/codegoal.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven.gen.src added to maven?
On Sat, Jul 10, 2004 at 01:33:30PM +0100, Eric Pugh wrote:
Hi all,
Can we add maven.gen.src=${maven.build.dest}/generated-sources?
Where would you like to add this?
Which plugins would be affected/need up be updated.
I've been doing a bunch of work with the Hibernate, Xdoclet, and Eclipse
plugins for a client. One of the challenges we had was getting source code
generated via the Xdoclet and Hibernate plugins to play nice w/ a normal
Maven build as well as using it within Eclipse. Eclipse is their primary
environment for their developers, so Maven had to play nice with Eclipse.
The biggest challenge was getting various generated code bits into the
/target directory. When we put files in /target/classes and then ran builds
in Eclipse the /target/classes directory would be completely cleaned, and
wiped out the generated code that was needed.
After chatting with JvZ, I added to the Eclipse plugin the ability to add as
seperate source directories anything in ${maven.gen.src}. So, after
generating hibernate mapping files and a ddl I would have:
/target/generated-sources/xdoclet
/target/generated-sources/schema
and they would each be a source folder in Eclipse. Works great. However,
because maven.gen.src is defined in the Eclipse plugin only, you have to
specify for the hibernate and xdoclet plugins the full path to generate
source into. It would be much simpler if maven.gen.src worked the same way
that maven.build.dest and other properties like that work.
Eric
As dIon said I don't think we should make changes like this before 1.0 but
I'm +1 for this after a Maven 1.0 release.
--
Trygve
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENPROXY-12) content-length response header is not set
Message: The following issue has been closed. Resolver: Ben Walding Date: Sat, 10 Jul 2004 9:29 AM Done. Will be part of the 0.2 release. - View the issue: http://jira.codehaus.org/browse/MAVENPROXY-12 Here is an overview of the issue: - Key: MAVENPROXY-12 Summary: content-length response header is not set Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-component-proxy Assignee: Ben Walding Reporter: Ben Walding Created: Wed, 30 Jun 2004 7:49 AM Updated: Sat, 10 Jul 2004 9:29 AM Description: Set it... makes for more informative download messages from maven - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENPROXY-6) Bypass HTTP proxy for local addresses
The following comment has been added to this issue: Author: Ben Walding Created: Sat, 10 Jul 2004 9:27 AM Body: This is not a problem with the maven-proxy. Needs to be reassigned to the correct component. Will do this later - View this comment: http://jira.codehaus.org/browse/MAVENPROXY-6?page=comments#action_21590 - View the issue: http://jira.codehaus.org/browse/MAVENPROXY-6 Here is an overview of the issue: - Key: MAVENPROXY-6 Summary: Bypass HTTP proxy for local addresses Type: Improvement Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-component-proxy Assignee: Reporter: Created: Fri, 22 Aug 2003 11:34 AM Updated: Sat, 10 Jul 2004 9:27 AM Description: The configuration settings for using an HTTP proxy need to include a facility to bypass the proxy when going to local addresses, much like IE has. Without this feature I can connect to ibiblio but not our in-house repository... or I can connect to the in-house repo but not ibiblio. So I have to keep switching the build.properties file. I guess a simple comma-separated list of known local addresses would suffice. - 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: (MAVENPROXY-7) java.lang.IllegalStateException: Can't set fields in SENDING for HTTP/1.1
Message: The following issue has been closed. Resolver: Ben Walding Date: Sat, 10 Jul 2004 9:28 AM This no longer occurs - View the issue: http://jira.codehaus.org/browse/MAVENPROXY-7 Here is an overview of the issue: - Key: MAVENPROXY-7 Summary: java.lang.IllegalStateException: Can't set fields in SENDING for HTTP/1.1 Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: 30 minutes Time Spent: Unknown Remaining: 30 minutes Project: maven-component-proxy Assignee: Reporter: Ben Walding Created: Fri, 22 Aug 2003 7:52 PM Updated: Sat, 10 Jul 2004 9:28 AM Description: java.lang.IllegalStateException: Can't set fields in SENDING for HTTP/1.1 Probably caused by closing the servletoutputstream. Downloads still seem to work however. - 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]
Set repository in plugin-parent/project.properties
Hi,
Is there any reason why the repository is not set in
plugin-parent/project.properties?
If not, I'll add it.
# Repository to deploy to
maven.repo.list=apache
maven.repo.apache=sftp://${pom.distributionSite}
maven.repo.apache.directory=${pom.distributionDirectory}
# These must be set elsewhere
#maven.repo.apache.username=
#maven.repo.apache.privatekey=
#maven.repo.apache.passphrase=
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven AspectJ Plugin 3.1.1 released
The maven team is pleased to announce the Maven AspectJ Plugin 3.1.1 release! http://maven.apache.org/reference/plugins/aspectj/ Changes in this version include: New Features: o Output messages to log Fixed bugs: o Check that unitTestSourceDirectory is defined in pom Issue: MPASPECTJ-11. o Check that aspectSourceDirectory is defined in pom To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-aspectj-plugin -Dversion=3.1.1 For a manual installation, you can download the plugin here: http://www.apache.org/dist/java-repository/maven/plugins/maven-aspectj-plugi n-3.1.1.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPARTIFACT-27) Stack trace when auth fails
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-27 Here is an overview of the issue: - Key: MPARTIFACT-27 Summary: Stack trace when auth fails Type: Bug Status: Unassigned Priority: Trivial Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-artifact-plugin Assignee: Reporter: Carlos Sanchez Created: Sat, 10 Jul 2004 11:05 AM Updated: Sat, 10 Jul 2004 11:05 AM Description: Also some info could be printed to the user (host, username) Will deploy to 1 repository(ies): default Deploying to repository: default com.jcraft.jsch.JSchException: Auth fail at com.jcraft.jsch.Session.connect(Unknown Source) at org.apache.maven.deploy.deployers.GenericSshDeployer.init(GenericSshDeployer.java:166) at org.apache.maven.deploy.deployers.ScpDeployer.init(ScpDeployer.java:103) at org.apache.maven.deploy.DeployTool.deploy(DeployTool.java:129) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(DefaultArtifactDeployer.java:385) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:123) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:121) at org.apache.maven.artifact.deployer.DeployBean.deploy(DeployBean.java:144) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:230) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:145) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:87) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:84) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:125) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:616) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) at org.apache.maven.jelly.tags.maven.MavenTag.doTag(MavenTag.java:82) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:616) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266)
Re: maven.gen.src added to maven?
On Sat, 2004-07-10 at 08:47, Dion Gillard wrote: Do we want to do this so close to 1.0? I don't think it would be wise to make this addition this close to 1.0, but it can definitely be added post 1.0. How it will be added by making an addition to this: http://cvs.apache.org/viewcvs.cgi/maven-components/maven-model/maven.mdo?rev=1.48view=auto The goal of using the model will include zero impact on current usage of the model in 1.x and all releases post 1.0 will use the model so if you want to make an addition lets pick the element to add now in preparation. Brett is coming to Guelph in about 10 days and while he's here one of things we're going to do is formulate a plan of attack for moving the 1.x code over to using the model in a first phase and then the project builder from the component-based code. I'm basically lying in wait for 1.0 release at this point. The code for 1.0 is not going change unless there is a serious show stopper and subsequent to the 1.0 release I am going to start merging the component-based code with 1.x as fast as humanly possible. The goal is zero impact on usage which will restrict the use of some of the more advanced features found in the components but compatibility is more important. So as far as the generation concerns go, I am totally willing to help you make changes to the model and flesh out any ideas required to make code generation scalable. So you certainly need to be able to compile generated sources, but you may also want to generate resources from generated sources or process the generated sources in any arbitrary fashion and we want to do this in a way that avoids coupling between plugins because that's just a disaster waiting to happen. So it's easy enough to have something like maven.compile.src.set (compileSourceRoots in m2) and allow plugins to make additions to this set for compilation but we have to take this another step and make any additions that allow any arbitrary processing on the generated sources. So you might generate some sources with xdoclet tags in them that you want to generate mappings from. Maybe that's a contrived example but that's the type of thing we should account for. I assume you need this asap for your client so we can start doing this work on HEAD if you're in a serious rush. I'll give you any help you need. I was going to wait until Brett got here but we can experiment getting the model working in HEAD as that won't affect anything insofar as 1.0 is concerned. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven javadoc plugin 1.6 ready
Hi Arnaud, I've created a 1.7 version. However I'm not sure what I should do the for 1.5.1 or 1.6 one. There's already a 1.6 one. Do you want me to remove the 1.5.1 version and possibly reassign the issues assigned to it to 1.6? Thanks -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 17:59 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready Hello guys. Can you give me the administrators rights for Jira or help me to move the release 1.5.1 in 1.6 for the javadoc plugin please ? I need also to create a 1.7 release. Arnaud -Message d'origine- De : Arnaud Heritier [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 00:17 À : 'Maven Developers List' Objet : RE: Maven javadoc plugin 1.6 ready Hi guys, I sent the 1.6 release and site on apache. I will wait that Jira is updated to make the announcement. I will need to re-send the site because the 1.6 plugin is not yet found on ibiblio in the download page. I'll do it tomorrow when the rsync between ibilio and minotaur will be done. Arnaud. -Message d'origine- De : Arnaud HERITIER [mailto:[EMAIL PROTECTED] Envoyé : vendredi 9 juillet 2004 23:25 À : 'Maven Developers List' Objet : Maven javadoc plugin 1.6 ready Hello guys, I'm ready to release the new javadoc plugin but I'm not administrator for this project on Jira. I want to create a release 1.6 instead of 1.5.1 because there are not only bug fixes but also improvements. Is there someone who can help me? Thanks Arnaud - 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]
RE: Maven javadoc plugin 1.6 ready
Hello Vincent, Yes I want to reassign all issues fixed in the 1.5.1 to 1.6 I think I can do it if the 1.6 exists. But I'll need your help to remove the 1.5.1 which won't exist. Arnaud -Message d'origine- De : Vincent Massol [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 18:01 À : 'Maven Developers List' Objet : RE: Maven javadoc plugin 1.6 ready Hi Arnaud, I've created a 1.7 version. However I'm not sure what I should do the for 1.5.1 or 1.6 one. There's already a 1.6 one. Do you want me to remove the 1.5.1 version and possibly reassign the issues assigned to it to 1.6? Thanks -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 17:59 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready Hello guys. Can you give me the administrators rights for Jira or help me to move the release 1.5.1 in 1.6 for the javadoc plugin please ? I need also to create a 1.7 release. Arnaud -Message d'origine- De : Arnaud Heritier [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 00:17 À : 'Maven Developers List' Objet : RE: Maven javadoc plugin 1.6 ready Hi guys, I sent the 1.6 release and site on apache. I will wait that Jira is updated to make the announcement. I will need to re-send the site because the 1.6 plugin is not yet found on ibiblio in the download page. I'll do it tomorrow when the rsync between ibilio and minotaur will be done. Arnaud. -Message d'origine- De : Arnaud HERITIER [mailto:[EMAIL PROTECTED] Envoyé : vendredi 9 juillet 2004 23:25 À : 'Maven Developers List' Objet : Maven javadoc plugin 1.6 ready Hello guys, I'm ready to release the new javadoc plugin but I'm not administrator for this project on Jira. I want to create a release 1.6 instead of 1.5.1 because there are not only bug fixes but also improvements. Is there someone who can help me? Thanks Arnaud - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven javadoc plugin 1.6 ready
Done. -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 18:06 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready Hello Vincent, Yes I want to reassign all issues fixed in the 1.5.1 to 1.6 I think I can do it if the 1.6 exists. But I'll need your help to remove the 1.5.1 which won't exist. Arnaud -Message d'origine- De : Vincent Massol [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 18:01 À : 'Maven Developers List' Objet : RE: Maven javadoc plugin 1.6 ready Hi Arnaud, I've created a 1.7 version. However I'm not sure what I should do the for 1.5.1 or 1.6 one. There's already a 1.6 one. Do you want me to remove the 1.5.1 version and possibly reassign the issues assigned to it to 1.6? Thanks -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 17:59 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready Hello guys. Can you give me the administrators rights for Jira or help me to move the release 1.5.1 in 1.6 for the javadoc plugin please ? I need also to create a 1.7 release. Arnaud -Message d'origine- De : Arnaud Heritier [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 00:17 À : 'Maven Developers List' Objet : RE: Maven javadoc plugin 1.6 ready Hi guys, I sent the 1.6 release and site on apache. I will wait that Jira is updated to make the announcement. I will need to re-send the site because the 1.6 plugin is not yet found on ibiblio in the download page. I'll do it tomorrow when the rsync between ibilio and minotaur will be done. Arnaud. -Message d'origine- De : Arnaud HERITIER [mailto:[EMAIL PROTECTED] Envoyé : vendredi 9 juillet 2004 23:25 À : 'Maven Developers List' Objet : Maven javadoc plugin 1.6 ready Hello guys, I'm ready to release the new javadoc plugin but I'm not administrator for this project on Jira. I want to create a release 1.6 instead of 1.5.1 because there are not only bug fixes but also improvements. Is there someone who can help me? Thanks Arnaud -- --- 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] - 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] Reopened: (MPJAVADOC-24) doc-files directory is not copied
Message: The following issue has been reopened. Reopener: Arnaud HERITIER Date: Sat, 10 Jul 2004 12:07 PM reopen issue to move the fix version to 1.6 - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-24 Here is an overview of the issue: - Key: MPJAVADOC-24 Summary: doc-files directory is not copied Type: Bug Status: Reopened Priority: Critical Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-javadoc-plugin Fix Fors: 1.6 Versions: 1.4 Assignee: Arnaud HERITIER Reporter: Boris Boehlen Created: Mon, 17 May 2004 9:39 AM Updated: Sat, 10 Jul 2004 12:07 PM Description: The javadoc plugin does not copy the contents of the doc-files directories to the target directory. Thus, javadoc documentation relying on files in the doc-files directories are incomplete, making this bug critical for me. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPJAVADOC-24) doc-files directory is not copied
Message: The following issue has been closed. Resolver: Arnaud HERITIER Date: Sat, 10 Jul 2004 12:08 PM New javadoc plugin release is 1.6 - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-24 Here is an overview of the issue: - Key: MPJAVADOC-24 Summary: doc-files directory is not copied Type: Bug Status: Closed Priority: Critical Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-javadoc-plugin Fix Fors: 1.6 Versions: 1.4 Assignee: Arnaud HERITIER Reporter: Boris Boehlen Created: Mon, 17 May 2004 9:39 AM Updated: Sat, 10 Jul 2004 12:08 PM Description: The javadoc plugin does not copy the contents of the doc-files directories to the target directory. Thus, javadoc documentation relying on files in the doc-files directories are incomplete, making this bug critical for me. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven javadoc plugin 1.6 ready
BTW, there is one issue remaining in 1.6 (which is already released)! Shall I move it to the 1.7 version? -Vincent -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 18:08 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready Done. -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 18:06 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready Hello Vincent, Yes I want to reassign all issues fixed in the 1.5.1 to 1.6 I think I can do it if the 1.6 exists. But I'll need your help to remove the 1.5.1 which won't exist. Arnaud -Message d'origine- De : Vincent Massol [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 18:01 À : 'Maven Developers List' Objet : RE: Maven javadoc plugin 1.6 ready Hi Arnaud, I've created a 1.7 version. However I'm not sure what I should do the for 1.5.1 or 1.6 one. There's already a 1.6 one. Do you want me to remove the 1.5.1 version and possibly reassign the issues assigned to it to 1.6? Thanks -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 17:59 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready Hello guys. Can you give me the administrators rights for Jira or help me to move the release 1.5.1 in 1.6 for the javadoc plugin please ? I need also to create a 1.7 release. Arnaud -Message d'origine- De : Arnaud Heritier [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 00:17 À : 'Maven Developers List' Objet : RE: Maven javadoc plugin 1.6 ready Hi guys, I sent the 1.6 release and site on apache. I will wait that Jira is updated to make the announcement. I will need to re-send the site because the 1.6 plugin is not yet found on ibiblio in the download page. I'll do it tomorrow when the rsync between ibilio and minotaur will be done. Arnaud. -Message d'origine- De : Arnaud HERITIER [mailto:[EMAIL PROTECTED] Envoyé : vendredi 9 juillet 2004 23:25 À : 'Maven Developers List' Objet : Maven javadoc plugin 1.6 ready Hello guys, I'm ready to release the new javadoc plugin but I'm not administrator for this project on Jira. I want to create a release 1.6 instead of 1.5.1 because there are not only bug fixes but also improvements. Is there someone who can help me? Thanks Arnaud -- --- 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] - 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]
RE: Maven javadoc plugin 1.6 ready
Oooopss... I've just realized it was a temporary edit you've just done... :-) -Vincent -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 18:09 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready BTW, there is one issue remaining in 1.6 (which is already released)! Shall I move it to the 1.7 version? -Vincent -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 18:08 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready Done. -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 18:06 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready Hello Vincent, Yes I want to reassign all issues fixed in the 1.5.1 to 1.6 I think I can do it if the 1.6 exists. But I'll need your help to remove the 1.5.1 which won't exist. Arnaud -Message d'origine- De : Vincent Massol [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 18:01 À : 'Maven Developers List' Objet : RE: Maven javadoc plugin 1.6 ready Hi Arnaud, I've created a 1.7 version. However I'm not sure what I should do the for 1.5.1 or 1.6 one. There's already a 1.6 one. Do you want me to remove the 1.5.1 version and possibly reassign the issues assigned to it to 1.6? Thanks -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 17:59 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready Hello guys. Can you give me the administrators rights for Jira or help me to move the release 1.5.1 in 1.6 for the javadoc plugin please ? I need also to create a 1.7 release. Arnaud -Message d'origine- De : Arnaud Heritier [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 00:17 À : 'Maven Developers List' Objet : RE: Maven javadoc plugin 1.6 ready Hi guys, I sent the 1.6 release and site on apache. I will wait that Jira is updated to make the announcement. I will need to re-send the site because the 1.6 plugin is not yet found on ibiblio in the download page. I'll do it tomorrow when the rsync between ibilio and minotaur will be done. Arnaud. -Message d'origine- De : Arnaud HERITIER [mailto:[EMAIL PROTECTED] Envoyé : vendredi 9 juillet 2004 23:25 À : 'Maven Developers List' Objet : Maven javadoc plugin 1.6 ready Hello guys, I'm ready to release the new javadoc plugin but I'm not administrator for this project on Jira. I want to create a release 1.6 instead of 1.5.1 because there are not only bug fixes but also improvements. Is there someone who can help me? Thanks Arnaud -- -- -- --- 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] - 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]
RE: Maven javadoc plugin 1.6 ready
Thanks Vincent. I saw that you did it. I will announce the new release. Arnaud -Message d'origine- De : Arnaud Heritier [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 18:06 À : 'Maven Developers List' Objet : RE: Maven javadoc plugin 1.6 ready Hello Vincent, Yes I want to reassign all issues fixed in the 1.5.1 to 1.6 I think I can do it if the 1.6 exists. But I'll need your help to remove the 1.5.1 which won't exist. Arnaud -Message d'origine- De : Vincent Massol [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 18:01 À : 'Maven Developers List' Objet : RE: Maven javadoc plugin 1.6 ready Hi Arnaud, I've created a 1.7 version. However I'm not sure what I should do the for 1.5.1 or 1.6 one. There's already a 1.6 one. Do you want me to remove the 1.5.1 version and possibly reassign the issues assigned to it to 1.6? Thanks -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 17:59 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready Hello guys. Can you give me the administrators rights for Jira or help me to move the release 1.5.1 in 1.6 for the javadoc plugin please ? I need also to create a 1.7 release. Arnaud -Message d'origine- De : Arnaud Heritier [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 00:17 À : 'Maven Developers List' Objet : RE: Maven javadoc plugin 1.6 ready Hi guys, I sent the 1.6 release and site on apache. I will wait that Jira is updated to make the announcement. I will need to re-send the site because the 1.6 plugin is not yet found on ibiblio in the download page. I'll do it tomorrow when the rsync between ibilio and minotaur will be done. Arnaud. -Message d'origine- De : Arnaud HERITIER [mailto:[EMAIL PROTECTED] Envoyé : vendredi 9 juillet 2004 23:25 À : 'Maven Developers List' Objet : Maven javadoc plugin 1.6 ready Hello guys, I'm ready to release the new javadoc plugin but I'm not administrator for this project on Jira. I want to create a release 1.6 instead of 1.5.1 because there are not only bug fixes but also improvements. Is there someone who can help me? Thanks Arnaud - 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] - 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]
[ANN] Maven Javadoc Plug-in 1.6
The maven team is pleased to announce the Maven Javadoc Plug-in 1.6 release! http://maven.apache.org/reference/plugins/javadoc/ Changes in this version include: New Features: o Use the property 'maven.javadoc.excludepackagenames' to exclude packages from javadoc generation. Issue: MPJAVADOC-30. Thanks to Maarten Coene. o Add the property maven.javadoc.debug to print informations to debug the plugin. Fixed bugs: o Javadoc plugin ignores the package specified in the pom. Issue: MPJAVADOC-33. o The maven-javadoc-plugin:register failed in javadoc plugin 1.5.1-SNAPSHOT. Issue: MPJAVADOC-32. Thanks to Guillaume Nodet. o Use the property 'maven.compile.encoding' to set the encoding used when reading sources in javadoc task. Issue: MPJAVADOC-31. Thanks to Takayoshi Kimura. o Packages list broken on jdk 1.3 for multiple packages. Issue: MPJAVADOC-29. o @link tag not working with package names. Issue: MPJAVADOC-28. o Fix the needed flag when there's an empty sources directory. Issue: MPJAVADOC-26. Thanks to Denis McLaughlin. o doc-files directories contents are correctly copied. Issue: MPJAVADOC-24. o Failure to generate relative cross-references to local classes. Issue: MPJAVADOC-16. o Add support for multiple source directories. Issue: MPJAVADOC-5. To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-javadoc-plugin -Dversion=1.6 For a manual installation, you can download the plugin here: http://www.apache.org/dist/java-repository/maven/plugins/maven-javadoc-plugin-1.6.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven javadoc plugin 1.6 ready
Yes. You were faster than me ;-) Thanks a lot Arnaud -Message d'origine- De : Vincent Massol [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 18:10 À : 'Maven Developers List' Objet : RE: Maven javadoc plugin 1.6 ready Oooopss... I've just realized it was a temporary edit you've just done... :-) -Vincent -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 18:09 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready BTW, there is one issue remaining in 1.6 (which is already released)! Shall I move it to the 1.7 version? -Vincent -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 18:08 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready Done. -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 18:06 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready Hello Vincent, Yes I want to reassign all issues fixed in the 1.5.1 to 1.6 I think I can do it if the 1.6 exists. But I'll need your help to remove the 1.5.1 which won't exist. Arnaud -Message d'origine- De : Vincent Massol [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 18:01 À : 'Maven Developers List' Objet : RE: Maven javadoc plugin 1.6 ready Hi Arnaud, I've created a 1.7 version. However I'm not sure what I should do the for 1.5.1 or 1.6 one. There's already a 1.6 one. Do you want me to remove the 1.5.1 version and possibly reassign the issues assigned to it to 1.6? Thanks -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 17:59 To: 'Maven Developers List' Subject: RE: Maven javadoc plugin 1.6 ready Hello guys. Can you give me the administrators rights for Jira or help me to move the release 1.5.1 in 1.6 for the javadoc plugin please ? I need also to create a 1.7 release. Arnaud -Message d'origine- De : Arnaud Heritier [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 00:17 À : 'Maven Developers List' Objet : RE: Maven javadoc plugin 1.6 ready Hi guys, I sent the 1.6 release and site on apache. I will wait that Jira is updated to make the announcement. I will need to re-send the site because the 1.6 plugin is not yet found on ibiblio in the download page. I'll do it tomorrow when the rsync between ibilio and minotaur will be done. Arnaud. -Message d'origine- De : Arnaud HERITIER [mailto:[EMAIL PROTECTED] Envoyé : vendredi 9 juillet 2004 23:25 À : 'Maven Developers List' Objet : Maven javadoc plugin 1.6 ready Hello guys, I'm ready to release the new javadoc plugin but I'm not administrator for this project on Jira. I want to create a release 1.6 instead of 1.5.1 because there are not only bug fixes but also improvements. Is there someone who can help me? Thanks Arnaud -- -- -- --- 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] - 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] Closed: (MPCHANGES-9) Sourceforge tracker support
Message: The following issue has been closed. Resolver: Vincent Massol Date: Sat, 10 Jul 2004 12:20 PM I'm closing this issue as we have a solution for SF. When/if we find a bug tracker that needs more information than an issue #, then we'll open a new issue. - 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: Closed Priority: Major Resolution: WON'T FIX Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-changes-plugin Fix Fors: 1.6 Assignee: Vincent Massol Reporter: Martijn Dashorst Created: Sun, 13 Jun 2004 11:25 AM Updated: Sat, 10 Jul 2004 12:20 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] Commented: (MPCHANGES-14) Allow entries to be sorted by action type.
The following comment has been added to this issue:
Author: Vincent Massol
Created: Sat, 10 Jul 2004 12:23 PM
Body:
Hi Gary,
Could you please provide more information as to why this is required?
Also, you mention some generated XML/text but AFAIK there's no generation of any file
(apart from the HTML one) in the changes plugin. Could you please explain more?
Thanks
-
View this comment:
http://jira.codehaus.org/browse/MPCHANGES-14?page=comments#action_21597
-
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.6
Versions:
1.4
Assignee:
Reporter: Gary Gregory
Created: Tue, 22 Jun 2004 2:30 AM
Updated: Sat, 10 Jul 2004 12:23 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:
rss.png file
Hi, I can't recall but someone has changes the rss.png file from Binary to an Ascii format a few days back. The PNG file is now unreadable for me. Could the change be reverted as it breaks the changes plugin? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/changes/xdocs changes.xml
vmassol 2004/07/10 09:32:50 Modified:changes project.xml plugin.properties changes/xdocs changes.xml Log: Use the short notation for JIRA links (code%URL%/%ISSUE%/code). Fixes MPCHANGES-17 Revision ChangesPath 1.34 +1 -1 maven-plugins/changes/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/changes/project.xml,v retrieving revision 1.33 retrieving revision 1.34 diff -u -r1.33 -r1.34 --- project.xml 8 Jul 2004 15:50:06 - 1.33 +++ project.xml 10 Jul 2004 16:32:50 - 1.34 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-changes-plugin/id nameMaven Changes Plugin/name - currentVersion1.5/currentVersion + currentVersion1.6-SNAPSHOT/currentVersion shortDescriptionProduce changes report/shortDescription urlhttp://maven.apache.org/reference/plugins/changes//url issueTrackingUrlhttp://jira.codehaus.org/browse/MPCHANGES/issueTrackingUrl 1.7 +1 -1 maven-plugins/changes/plugin.properties Index: plugin.properties === RCS file: /home/cvs/maven-plugins/changes/plugin.properties,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- plugin.properties 13 Jun 2004 16:13:21 - 1.6 +++ plugin.properties 10 Jul 2004 16:32:50 - 1.7 @@ -27,7 +27,7 @@ # %ISSUE% : this is the issue number. # The default template below is the one for the JIRA bug tracker. -maven.changes.issue.template = %URL%/ViewIssue.jspa?key=%ISSUE% +maven.changes.issue.template = %URL%/%ISSUE% # For Bugzilla, assuming the issueTrackingUrl points to something like # http://nagoya.apache.org/bugzilla/ 1.28 +5 -0 maven-plugins/changes/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/changes/xdocs/changes.xml,v retrieving revision 1.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- changes.xml 8 Jul 2004 15:49:03 - 1.27 +++ changes.xml 10 Jul 2004 16:32:50 - 1.28 @@ -24,6 +24,11 @@ author email=[EMAIL PROTECTED]Vincent Massol/author /properties body +release version=1.6-SNAPSHOT date=in CVS + action dev=vmassol type=fix issue=MPCHANGES-17 +Use the short notation for JIRA links (code%URL%/%ISSUE%/code). + /action +/release release version=1.5 date=2004-07-08 action dev=vmassol type=addAdd generation of RSS feed for current version changes/action /release - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPCHANGES-17) jira links don't work with /browse/ form
Message: The following issue has been closed. Resolver: Vincent Massol Date: Sat, 10 Jul 2004 12:33 PM Done. Thanks. - 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: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-changes-plugin Fix Fors: 1.6 Assignee: Vincent Massol Reporter: Brett Porter Created: Mon, 28 Jun 2004 6:12 AM Updated: Sat, 10 Jul 2004 12:33 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]
Re: maven.gen.src added to maven?
On Saturday, July 10, 2004, at 05:33 AM, Eric Pugh wrote:
Hi all,
Can we add maven.gen.src=${maven.build.dest}/generated-sources?
I've been doing a bunch of work with the Hibernate, Xdoclet, and
Eclipse
plugins for a client. One of the challenges we had was getting source
code
generated via the Xdoclet and Hibernate plugins to play nice w/ a
normal
Maven build as well as using it within Eclipse. Eclipse is their
primary
environment for their developers, so Maven had to play nice with
Eclipse.
The biggest challenge was getting various generated code bits into the
/target directory. When we put files in /target/classes and then ran
builds
in Eclipse the /target/classes directory would be completely cleaned,
and
wiped out the generated code that was needed.
After chatting with JvZ, I added to the Eclipse plugin the ability to
add as
seperate source directories anything in ${maven.gen.src}. So, after
generating hibernate mapping files and a ddl I would have:
/target/generated-sources/xdoclet
/target/generated-sources/schema
Shouldn't this be
/target/generated-sources/hibernate? I don't know if hibernate is
generating something or only xdoclet, nor the content of schema.
I think total confusion will result unless the directory is clearly
labeled with the name of the tool that generated the source.
Since tools such as xdoclet may generate several kinds of source
artifacts, perhaps having another level of directories would be wise:
/target/generated-sources/xdoclet/java
/target/generated-sources/xdoclet/ejb
thanks
david jencks
and they would each be a source folder in Eclipse. Works great.
However,
because maven.gen.src is defined in the Eclipse plugin only, you have
to
specify for the hibernate and xdoclet plugins the full path to generate
source into. It would be much simpler if maven.gen.src worked the
same way
that maven.build.dest and other properties like that work.
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]
RE: rss.png file
Hello Vincent. It was me. I changed the type (ascii - binary) but I also replaced the image which was corrupted :-( The new one seems to work for me : http://maven.apache.org/reference/plugins/javadoc/changes-report.html Arnaud -Message d'origine- De : Vincent Massol [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 18:32 À : 'Maven Developers List' Objet : rss.png file Hi, I can't recall but someone has changes the rss.png file from Binary to an Ascii format a few days back. The PNG file is now unreadable for me. Could the change be reverted as it breaks the changes plugin? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: rss.png file
Strange. I've just removed the image from my local filesystem and then I've done a cvs update and the image is still invalid. -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 18:38 To: 'Maven Developers List' Subject: RE: rss.png file Hello Vincent. It was me. I changed the type (ascii - binary) but I also replaced the image which was corrupted :-( The new one seems to work for me : http://maven.apache.org/reference/plugins/javadoc/changes-report.html Arnaud -Message d'origine- De : Vincent Massol [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 18:32 À : 'Maven Developers List' Objet : rss.png file Hi, I can't recall but someone has changes the rss.png file from Binary to an Ascii format a few days back. The PNG file is now unreadable for me. Could the change be reverted as it breaks the changes plugin? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPCHANGES-14) Allow entries to be sorted by action type.
The following comment has been added to this issue: Author: Gary Gregory Created: Sat, 10 Jul 2004 1:29 PM Body: Correct, changes.xml produces HTML. I was also thinking of the annoucement plugin. Here is what I have in mind: when I read the (very nice BTW) HTML history report, I'd like to read things in groups. Here are all of the new features for this release first (the most important IMO). Then maybe I want to know what all of the bug fixes are, then all of the updated pieces and last all of the pieces that have been deprecated. Today I have to do all of this by hand in changes.xml, which is a pain. It is also possible that someday, we'll have a clever plugin that can create a changes.xml from Bugzilla or Jira, and who knows what the order of things in the file will be. It would be nice to be able to specify some UI view parameters separately from what I think of as the data model in changes.xml. Which is why I proposed to parameterize this in the proerties file. Now that I think of it, another tweak would be the option to have a header that says New Features and Bug Fixes just like there is a header today for the Release number and date. - View this comment: http://jira.codehaus.org/browse/MPCHANGES-14?page=comments#action_21599 - 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.6 Versions: 1.4 Assignee: Reporter: Gary Gregory Created: Tue, 22 Jun 2004 2:30 AM Updated: Sat, 10 Jul 2004 1:29 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
[jira] Commented: (MPJAVADOC-34) Javadoc links don't work behind a proxy
The following comment has been added to this issue: Author: Carlos Sanchez Created: Sat, 10 Jul 2004 2:49 PM Body: There's an issue open in the ant bug database http://issues.apache.org/bugzilla/show_bug.cgi?id=29870 Anyone interested please vote in the above link to get it solved - View this comment: http://jira.codehaus.org/browse/MPJAVADOC-34?page=comments#action_21603 - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-34 Here is an overview of the issue: - Key: MPJAVADOC-34 Summary: Javadoc links don't work behind a proxy Type: Improvement Status: Open Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-javadoc-plugin Versions: 1.1 1.2 1.3 1.4 1.5 Assignee: Arnaud HERITIER Reporter: Carlos Sanchez Created: Fri, 9 Jul 2004 12:38 PM Updated: Sat, 10 Jul 2004 2:49 PM Description: Links doesn't work behind a proxy javadoc: Error fetching URL: http://java.sun.com/j2se/1.4.2/docs/api/package-list I've found some information in the net: It is possible to pass proxy information to javadoc. Try: javadoc -J-DproxyHost=myproxyhost.com -J-DproxyPort=8080 -link http://java.sun.com/products/jdk/1.3/docs/api *.java You have to pass http.proxyhost and http.proxyport properties to the JVM. -Dhttp.proxyhost=proxy -Dhttp.proxyport=3128 The problem is that javadoc ant task starts in another jvm (as stated in ant docs) Also I've tried the setProxy ant task and it doesn't work either. ant:setproxy proxyhost=proxy proxyport=3128/ - 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: rss.png file
It's right I have the same problem. I'll commit the correct image. Arnaud -Message d'origine- De : Vincent Massol [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 19:28 À : 'Maven Developers List' Objet : RE: rss.png file Strange. I've just removed the image from my local filesystem and then I've done a cvs update and the image is still invalid. -Vincent -Original Message- From: Arnaud Heritier [mailto:[EMAIL PROTECTED] Sent: samedi 10 juillet 2004 18:38 To: 'Maven Developers List' Subject: RE: rss.png file Hello Vincent. It was me. I changed the type (ascii - binary) but I also replaced the image which was corrupted :-( The new one seems to work for me : http://maven.apache.org/reference/plugins/javadoc/changes-report.html Arnaud -Message d'origine- De : Vincent Massol [mailto:[EMAIL PROTECTED] Envoyé : samedi 10 juillet 2004 18:32 À : 'Maven Developers List' Objet : rss.png file Hi, I can't recall but someone has changes the rss.png file from Binary to an Ascii format a few days back. The PNG file is now unreadable for me. Could the change be reverted as it breaks the changes plugin? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/changes/src/plugin-resources/images rss.png
aheritier2004/07/10 12:04:56 Modified:changes/src/plugin-resources/images rss.png Log: replace corrupted image Revision ChangesPath 1.4 +1 -1 maven-plugins/changes/src/plugin-resources/images/rss.png Binary file - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Set repository in plugin-parent/project.properties
I use
maven.repo.list=apache
maven.repo.apache=scp://www.apache.org
maven.repo.apache.username=
maven.repo.apache.password=
maven.repo.apache.directory=/www/www.apache.org/dist/java-repository/
as I really don't like specifying the passphrase and private key combo.
On Sat, 10 Jul 2004 17:00:44 +0200, Carlos Sanchez
[EMAIL PROTECTED] wrote:
Hi,
Is there any reason why the repository is not set in
plugin-parent/project.properties?
If not, I'll add it.
# Repository to deploy to
maven.repo.list=apache
maven.repo.apache=sftp://${pom.distributionSite}
maven.repo.apache.directory=${pom.distributionDirectory}
# These must be set elsewhere
#maven.repo.apache.username=
#maven.repo.apache.privatekey=
#maven.repo.apache.passphrase=
Regards
--
http://www.multitask.com.au/people/dion/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven plugin-profile.xml
No, its used to build the release. I guess it could be added to the release notes? I'm auto-generating it at the moment, but committing it so that it can be tagged along with a release. - Brett Quoting Dion Gillard [EMAIL PROTECTED]: Is this deployed to the web site anywhere? On 10 Jul 2004 02:21:52 -, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: brett 2004/07/09 19:21:52 Modified:.Tag: MAVEN-1_0-BRANCH plugin-profile.xml Log: update plugin releases Revision ChangesPath No revision No revision 1.1.2.2 +12 -10maven/Attic/plugin-profile.xml Index: plugin-profile.xml === RCS file: /home/cvs/maven/Attic/plugin-profile.xml,v retrieving revision 1.1.2.1 retrieving revision 1.1.2.2 diff -u -r1.1.2.1 -r1.1.2.2 --- plugin-profile.xml7 Jul 2004 10:35:35 - 1.1.2.1 +++ plugin-profile.xml10 Jul 2004 02:21:52 - 1.1.2.2 @@ -1,7 +1,9 @@ ?xml version=1.0 encoding=UTF-8? plugins - plugin groupId=maven artifactId=maven-announcement-plugin version=1.1 + plugin groupId=maven artifactId=maven-abbot-plugin version=1.0 + /plugin + plugin groupId=maven artifactId=maven-announcement-plugin version=1.2 /plugin plugin groupId=maven artifactId=maven-ant-plugin version=1.7 /plugin @@ -13,7 +15,7 @@ /plugin plugin groupId=maven artifactId=maven-ashkelon-plugin version=1.2 /plugin - plugin groupId=maven artifactId=maven-aspectj-plugin version=3.1 + plugin groupId=maven artifactId=maven-aspectj-plugin version=3.1.1 /plugin plugin groupId=maven artifactId=maven-aspectwerkz-plugin version=1.2 /plugin @@ -21,9 +23,9 @@ /plugin plugin groupId=maven artifactId=maven-castor-plugin version=1.2 /plugin - plugin groupId=maven artifactId=maven-changelog-plugin version=1.6 + plugin groupId=maven artifactId=maven-changelog-plugin version=1.7 /plugin - plugin groupId=maven artifactId=maven-changes-plugin version=1.4 + plugin groupId=maven artifactId=maven-changes-plugin version=1.5 /plugin plugin groupId=maven artifactId=maven-checkstyle-plugin version=2.4.1 /plugin @@ -47,7 +49,7 @@ /plugin plugin groupId=maven artifactId=maven-eclipse-plugin version=1.7 /plugin - plugin groupId=maven artifactId=maven-ejb-plugin version=1.4 + plugin groupId=maven artifactId=maven-ejb-plugin version=1.5 /plugin plugin groupId=maven artifactId=maven-faq-plugin version=1.4 /plugin @@ -65,7 +67,7 @@ /plugin plugin groupId=maven artifactId=maven-j2ee-plugin version=1.5 /plugin - plugin groupId=maven artifactId=maven-jalopy-plugin version=1.2 + plugin groupId=maven artifactId=maven-jalopy-plugin version=1.3 /plugin plugin groupId=maven artifactId=maven-jar-plugin version=1.6 /plugin @@ -73,13 +75,13 @@ /plugin plugin groupId=maven artifactId=maven-javacc-plugin version=1.1 /plugin - plugin groupId=maven artifactId=maven-javadoc-plugin version=1.5 + plugin groupId=maven artifactId=maven-javadoc-plugin version=1.6 /plugin plugin groupId=maven artifactId=maven-jboss-plugin version=1.5 /plugin plugin groupId=maven artifactId=maven-jbuilder-plugin version=1.5 /plugin - plugin groupId=maven artifactId=maven-jcoverage-plugin version=1.0.5 + plugin groupId=maven artifactId=maven-jcoverage-plugin version=1.0.6 /plugin plugin groupId=maven artifactId=maven-jdee-plugin version=1.1 /plugin @@ -117,11 +119,11 @@ /plugin plugin groupId=maven artifactId=maven-native-plugin version=1.1 /plugin - plugin groupId=maven artifactId=maven-nsis-plugin version=1.0 + plugin groupId=maven artifactId=maven-nsis-plugin version=1.1 /plugin plugin groupId=maven artifactId=maven-pdf-plugin version=2.1 /plugin - plugin groupId=maven artifactId=maven-plugin-plugin version=1.5 + plugin groupId=maven artifactId=maven-plugin-plugin version=1.5.1 /plugin plugin groupId=maven artifactId=maven-pmd-plugin version=1.5 /plugin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL
cvs commit: maven-plugins/xdoc/xdocs properties.xml
brett 2004/07/10 17:57:59
Modified:plugin plugin.jelly
plugin/xdocs goals.xml
xdoc/xdocs properties.xml
Log:
doco for goals and properties
Revision ChangesPath
1.42 +11 -6 maven-plugins/plugin/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/plugin/plugin.jelly,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- plugin.jelly 6 Jul 2004 22:21:07 - 1.41
+++ plugin.jelly 11 Jul 2004 00:57:59 - 1.42
@@ -56,7 +56,7 @@
/goal
goal name=plugin:install prereqs=plugin:plugin
-description=Install the plugin jar, prepare Maven to expand it locally and
clear caches
+description=Install the plugin jar, prepare Maven to expand it locally next
run
plugin:uninstall name=${pom.artifactId} /
!-- Don't clear the cache. Maven will do this if we happened to clean up an
additional version --
@@ -268,7 +268,7 @@
--
!-- test a plugin --
- goal name=plugin:test
+ goal name=plugin:test description=Run a plugin's test project
u:available file=${basedir}/src/plugin-test/project.xml
maven:maven
descriptor=${basedir}/src/plugin-test/project.xml
@@ -277,7 +277,8 @@
/u:available
/goal
- goal name=plugin:repository-install prereqs=plugin:plugin
+ goal name=plugin:repository-install prereqs=plugin:plugin
+description=install a plugin into the local repository
artifact:install
artifact=${maven.build.dir}/${maven.final.name}.jar
type=plugin
@@ -285,7 +286,8 @@
/
/goal
- goal name=plugin:repository-install-snapshot prereqs=plugin:plugin
+ goal name=plugin:repository-install-snapshot prereqs=plugin:plugin
+description=install a plugin snapshot into the local repository
artifact:install-snapshot
artifact=${maven.build.dir}/${maven.final.name}.jar
type=plugin
@@ -293,7 +295,8 @@
/
/goal
- goal name=plugin:repository-deploy prereqs=plugin:plugin
+ goal name=plugin:repository-deploy prereqs=plugin:plugin
+description=deploy a plugin into the local repository
artifact:deploy
artifact=${maven.build.dir}/${maven.final.name}.jar
type=plugin
@@ -301,7 +304,8 @@
/
/goal
- goal name=plugin:repository-deploy-snapshot prereqs=plugin:plugin
+ goal name=plugin:repository-deploy-snapshot prereqs=plugin:plugin
+description=deploy a plugin snapshot into the local repository
artifact:deploy-snapshot
artifact=${maven.build.dir}/${maven.final.name}.jar
type=plugin
@@ -365,3 +369,4 @@
/define:taglib
/project
+
1.7 +33 -4 maven-plugins/plugin/xdocs/goals.xml
Index: goals.xml
===
RCS file: /home/cvs/maven-plugins/plugin/xdocs/goals.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- goals.xml 28 Apr 2004 03:33:50 - 1.6
+++ goals.xml 11 Jul 2004 00:57:59 - 1.7
@@ -30,14 +30,19 @@
descriptionBuild and install a plugin/description
/goal
goal
-nameplugin:deploy/name
-descriptionInstall an unpacked version of the plugin/description
- /goal
- goal
nameplugin:download/name
description
Download and install plugin from the remote repos.
Must provide groupId, artifactId and version variables.
+ You will be prompted for any that are omitted.
+/description
+ /goal
+ goal
+nameplugin:download-artifact/name
+description
+ Download plugin from the remote repos.
+ Must provide groupId, artifactId and version variables.
+ You will be prompted for any that are omitted.
/description
/goal
goal
@@ -82,6 +87,30 @@
goal
nameplugin:test/name
descriptionRun a plugin's test project/description
+ /goal
+ goal
+nameplugin:repository-install/name
+description
+ Install the current plugin version to the local repository.
+/description
+ /goal
+ goal
+nameplugin:repository-install-snapshot/name
+description
+ Install a snapshot build of the plugin to the local repository.
+/description
+ /goal
+ goal
+nameplugin:repository-deploy/name
+description
+ Deploy the current plugin version to the remote repository.
+/description
+ /goal
+ goal
+nameplugin:repository-deploy-snapshot/name
+description
+ Deploy a snapshot build of the
Re: Set repository in plugin-parent/project.properties
Leaving out username, password, etc is acceptable as th euser can
specify them and will get reasonable errors if they aren't specified I
think.
The defaults may work if you use ~/.ssh/id_dsa with no passphrase and
user.name matches.
- Brett
Dion Gillard wrote:
I use
maven.repo.list=apache
maven.repo.apache=scp://www.apache.org
maven.repo.apache.username=
maven.repo.apache.password=
maven.repo.apache.directory=/www/www.apache.org/dist/java-repository/
as I really don't like specifying the passphrase and private key combo.
On Sat, 10 Jul 2004 17:00:44 +0200, Carlos Sanchez
[EMAIL PROTECTED] wrote:
Hi,
Is there any reason why the repository is not set in
plugin-parent/project.properties?
If not, I'll add it.
# Repository to deploy to
maven.repo.list=apache
maven.repo.apache=sftp://${pom.distributionSite}
maven.repo.apache.directory=${pom.distributionDirectory}
# These must be set elsewhere
#maven.repo.apache.username=
#maven.repo.apache.privatekey=
#maven.repo.apache.passphrase=
Regards
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPCRUISECONTROL-7) Add support for buildstatus
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Sat, 10 Jul 2004 9:44 PM
Changes:
assignee changed from Brett Porter
Version changed to 1.4
Fix Version changed to 1.5
-
For a full history of the issue, see:
http://jira.codehaus.org/browse/MPCRUISECONTROL-7?page=history
-
View the issue:
http://jira.codehaus.org/browse/MPCRUISECONTROL-7
Here is an overview of the issue:
-
Key: MPCRUISECONTROL-7
Summary: Add support for buildstatus
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-cruisecontrol-plugin
Fix Fors:
1.5
Versions:
1.4
Assignee:
Reporter: Paul Spencer
Created: Tue, 6 Jul 2004 10:23 AM
Updated: Sat, 10 Jul 2004 9:44 PM
Environment: maven 1.0-rc4, maven-cruisecontrol-plugin-1.3, CruiseControl 2.1.6
Description:
CruiseControl will build a project if another project successfully builds. This is
controlled by the buildstatus tag in cruisecontrol.xml. This functionality allows a
project to be build when one of it's depend jars is built, even though the project has
not changed.
Suggested implementation:
1) Add the property maven.cruisecontrol.triggerProjects. This property contains a
list of cruisecontrol projects that will trigger the current project to build.
2) In cruisecontrol.jsl, generate a buildstatus tag for each item in the property
list.
buildstatus logdir=${maven.cruisecontrol.logs.dir}/${item}
Example:
maven.cruisecontrol.triggerProjects=proj_a, proj_b
output file cruisecontrol.xml:
cruisecontrol
...
project name=proj_c
...
modificationset
buildstatus logdir=c:\cc\cc-logs\proj_a
buildstatus logdir=c:\cc\cc-logs\proj_b
..
/modificationset
..
log dir=c:\cc\cc-logs\proj_c
..
/project
cruisecontrol
-
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]
[ANN] Maven Cruisecontrol Plugin 1.4 Released
The maven team is pleased to announce the Maven Cruise Control Plugin 1.4 release! http://maven.apache.org/reference/plugins/cruisecontrol/ A plugin to handle the generating and maintaining of Cruise Control configuration. Requires Maven 1.0 RC2. Changes in this version include: New Features: o Show unit test results in Test Results tab. Issue: MPCRUISECONTROL-6. Thanks to Paul Spencer. o Svnroot attribute incorrect in cruisecontrol config.xml. Issue: MPCRUISECONTROL-5. Thanks to Alwyn Schoeman. To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-cruisecontrol-plugin -Dversion=1.4 For a manual installation, you can download the plugin here: http://www.apache.org/dist/java-repository/maven/plugins/maven-cruisecontrol-plugin-1.4.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/artifact/xdocs changes.xml
brett 2004/07/10 18:57:32 Modified:artifact project.xml artifact/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.4 Revision ChangesPath 1.33 +6 -1 maven-plugins/artifact/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/artifact/project.xml,v retrieving revision 1.32 retrieving revision 1.33 diff -u -r1.32 -r1.33 --- project.xml 3 Jul 2004 02:05:33 - 1.32 +++ project.xml 11 Jul 2004 01:57:32 - 1.33 @@ -25,7 +25,7 @@ nameMaven Artifact Plugin/name !-- WARNING: some dependency checks will break if we get to 1.10, need to go to 2.0 from there -- - currentVersion1.4-SNAPSHOT/currentVersion + currentVersion1.4/currentVersion descriptionTools to manage artifacts and deployment. Requires Maven 1.0 RC4/description shortDescriptionTools to manage artifacts and deployment/shortDescription urlhttp://maven.apache.org/reference/plugins/artifact//url @@ -51,6 +51,11 @@ id1.3/id name1.3/name tagMAVEN_ARTIFACT_1_3/tag +/version +version + id1.4/id + name1.4/name + tagMAVEN_ARTIFACT_1_4/tag /version /versions developers/ 1.29 +1 -1 maven-plugins/artifact/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/artifact/xdocs/changes.xml,v retrieving revision 1.28 retrieving revision 1.29 diff -u -r1.28 -r1.29 --- changes.xml 6 Jul 2004 14:29:30 - 1.28 +++ changes.xml 11 Jul 2004 01:57:32 - 1.29 @@ -25,7 +25,7 @@ author email=[EMAIL PROTECTED]Vincent Massol/author /properties body -release version=1.4-SNAPSHOT date=in CVS +release version=1.4 date=2004-07-10 action dev=brett type=fix issue=MPARTIFACT-23Add overwrite option to unzip - necessary to run in batch mode/action action dev=brett type=add issue=MPARTIFACT-22 due-to=Leif NelsonAdd an scp executable deployer/action action dev=brett type=updateDeprecated the artifact:load hook goal/action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Artifact Plugin 1.4 Released
The maven team is pleased to announce the Maven Artifact Plugin 1.4 release! http://maven.apache.org/reference/plugins/artifact/ Tools to manage artifacts and deployment. Requires Maven 1.0 RC4 Changes in this version include: New Features: o Add an scp executable deployer Issue: MPARTIFACT-22. Thanks to Leif Nelson. o Allow use of distributionSite POM attribute in artifact method Fixed bugs: o Add overwrite option to unzip - necessary to run in batch mode Issue: MPARTIFACT-23. Changes: o Deprecated the artifact:load hook goal o Update dependencies on commons-* To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-artifact-plugin -Dversion=1.4 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-artifact-plugin-1.4.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/gump/xdocs changes.xml
brett 2004/07/10 19:07:29 Modified:gump project.xml gump/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.4 Revision ChangesPath 1.25 +6 -1 maven-plugins/gump/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/gump/project.xml,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- project.xml 25 Jun 2004 15:24:28 - 1.24 +++ project.xml 11 Jul 2004 02:07:29 - 1.25 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-gump-plugin/id nameMaven Gump Plug-in/name - currentVersion1.4-SNAPSHOT/currentVersion + currentVersion1.4/currentVersion description/ shortDescriptionproduce Gump descriptor/shortDescription urlhttp://maven.apache.org/reference/plugins/gump//url @@ -44,6 +44,11 @@ id1.3/id name1.3/name tagMAVEN_GUMP_1_3/tag +/version +version + id1.4/id + name1.4/name + tagMAVEN_GUMP_1_4/tag /version /versions developers 1.10 +2 -2 maven-plugins/gump/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/gump/xdocs/changes.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- changes.xml 30 Jun 2004 04:18:36 - 1.9 +++ changes.xml 11 Jul 2004 02:07:29 - 1.10 @@ -24,11 +24,11 @@ author email=[EMAIL PROTECTED]dIon Gillard/author /properties body -release version=1.4-SNAPSHOT date=in CVS +release version=1.4 date=2004-07-10 action dev=brett type=add issue=MPGUMP-1Allow creation of lt;maven descriptor element, and default to it/action action dev=brett type=addAdd maven.gump.ant.target and maven.gump.maven.goal properties/action /release -release version=1.3 date=2004-05-15/release +release version=1.3 date=2004-05-15/ release version=1.2 date=2003-09-29 action dev=dion type=fixgump.xml generated into basedir/action action dev=dion type=updateAdded test project/action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Gump Plugin 1.4 Released
The maven team is pleased to announce the Maven Gump Plug-in 1.4 release! http://maven.apache.org/reference/plugins/gump/ Changes in this version include: New Features: o Allow creation of maven descriptor element, and default to it Issue: MPGUMP-1. o Add maven.gump.ant.target and maven.gump.maven.goal properties To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-gump-plugin -Dversion=1.4 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-gump-plugin-1.4.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/xdoc/xdocs changes.xml
brett 2004/07/10 19:20:19 Modified:xdoc project.xml xdoc/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.8 Revision ChangesPath 1.59 +6 -1 maven-plugins/xdoc/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/xdoc/project.xml,v retrieving revision 1.58 retrieving revision 1.59 diff -u -r1.58 -r1.59 --- project.xml 9 Jul 2004 10:29:23 - 1.58 +++ project.xml 11 Jul 2004 02:20:19 - 1.59 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-xdoc-plugin/id nameMaven XDoc Plug-in/name - currentVersion1.8-SNAPSHOT/currentVersion + currentVersion1.8/currentVersion descriptionConvert xdocs into HTML. Requires Maven 1.0 RC2./description shortDescriptionConvert xdocs into HTML/shortDescription urlhttp://maven.apache.org/reference/plugins/xdoc//url @@ -59,6 +59,11 @@ id1.7.2/id name1.7.2/name tagMAVEN_XDOC_1_7_2/tag +/version +version + id1.8/id + name1.8/name + tagMAVEN_XDOC_1_8/tag /version /versions developers 1.60 +3 -5 maven-plugins/xdoc/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/xdoc/xdocs/changes.xml,v retrieving revision 1.59 retrieving revision 1.60 diff -u -r1.59 -r1.60 --- changes.xml 3 Jul 2004 02:02:30 - 1.59 +++ changes.xml 11 Jul 2004 02:20:19 - 1.60 @@ -25,12 +25,10 @@ author email=[EMAIL PROTECTED]Vincent Massol/author /properties body -release version=1.8-SNAPSHOT date=in CVS +release version=1.8 date=2004-07-10 action dev=brett type=addAdd an externalLink attribute to a report to use if link is not present/action - action dev=vmassol type=add -Added a link to the release notes in the download report. Note that this -link is only created if the project has a codexdocs/changes.xml/code -file. + action dev=vmassol type=addAdded a link to the release notes in the download report. Note that this link is only created if the project has a +codexdocs/changes.xml/codefile. /action action dev=carlos type=add issue=MPXDOC-112Add instructions to checkout with maven to cvs-usage page/action /release - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven XDoc Plugin 1.8 Released
The maven team is pleased to announce the Maven XDoc Plug-in 1.8 release! http://maven.apache.org/reference/plugins/xdoc/ Convert xdocs into HTML. Requires Maven 1.0 RC2. Changes in this version include: New Features: o Add an externalLink attribute to a report to use if link is not present o 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.xmlfile. o Add instructions to checkout with maven to cvs-usage page Issue: MPXDOC-112. To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-xdoc-plugin -Dversion=1.8 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-xdoc-plugin-1.8.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/linkcheck/xdocs changes.xml
brett 2004/07/10 19:25:14 Modified:linkcheck project.xml linkcheck/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.3.2 Revision ChangesPath 1.53 +6 -1 maven-plugins/linkcheck/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/linkcheck/project.xml,v retrieving revision 1.52 retrieving revision 1.53 diff -u -r1.52 -r1.53 --- project.xml 5 Jul 2004 21:07:19 - 1.52 +++ project.xml 11 Jul 2004 02:25:14 - 1.53 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-linkcheck-plugin/id nameMaven LinkCheck Plug-in/name - currentVersion1.3.2-SNAPSHOT/currentVersion + currentVersion1.3.2/currentVersion descriptionCheck xdoc links. Requires Maven 1.0 RC2./description shortDescriptionCheck xdoc links/shortDescription urlhttp://maven.apache.org/reference/plugins/linkcheck//url @@ -49,6 +49,11 @@ id1.3.1/id name1.3.1/name tagMAVEN_LINKCHECK_1_3_1/tag +/version +version + id1.3.2/id + name1.3.2/name + tagMAVEN_LINKCHECK_1_3_2/tag /version /versions developers 1.20 +1 -1 maven-plugins/linkcheck/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/linkcheck/xdocs/changes.xml,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- changes.xml 5 Jul 2004 21:07:19 - 1.19 +++ changes.xml 11 Jul 2004 02:25:14 - 1.20 @@ -25,7 +25,7 @@ author email=[EMAIL PROTECTED]Vincent Massol/author /properties body -release version=1.3.2-SNAPSHOT date=in CVS +release version=1.3.2 date=2004-07-10 action dev=brett type=update issue=MPLINKCHECK-14Only log exception in debug mode on connection refused/action action dev=brett type=updateUpdate commons-*/action /release - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/site project.xml
brett 2004/07/10 19:28:50 Modified:site project.xml Log: [maven-scm-plugin] prepare release 1.5.1 Revision ChangesPath 1.36 +6 -1 maven-plugins/site/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/site/project.xml,v retrieving revision 1.35 retrieving revision 1.36 diff -u -r1.35 -r1.36 --- project.xml 5 Jul 2004 21:07:19 - 1.35 +++ project.xml 11 Jul 2004 02:28:50 - 1.36 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-site-plugin/id nameMaven Site Plugin/name - currentVersion1.5.1-SNAPSHOT/currentVersion + currentVersion1.5.1/currentVersion descriptionGenerate web site. Requires Maven 1.0 RC2./description shortDescriptionGenerate web site/shortDescription urlhttp://maven.apache.org/reference/plugins/site//url @@ -81,6 +81,11 @@ id1.5/id name1.5/name tagMAVEN_SITE_1_5/tag +/version +version + id1.5.1/id + name1.5.1/name + tagMAVEN_SITE_1_5_1/tag /version /versions /project - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPANNOUNCEMENT-10) xml entities transformed in wrong direction
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPANNOUNCEMENT-10 Here is an overview of the issue: - Key: MPANNOUNCEMENT-10 Summary: xml entities transformed in wrong direction Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-announcement-plugin Versions: 1.3 Assignee: Reporter: Brett Porter Created: Sat, 10 Jul 2004 10:27 PM Updated: Sat, 10 Jul 2004 10:27 PM Description: If changes.xml contains amp; for example, in the announcement it should be but is amp;amp; IE, the entity should be evaluated, not escaped. - 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/site/xdocs changes.xml
brett 2004/07/10 19:29:54 Modified:site/xdocs changes.xml Log: fix xml Revision ChangesPath 1.19 +2 -1 maven-plugins/site/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/site/xdocs/changes.xml,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- changes.xml 5 Jul 2004 21:07:19 - 1.18 +++ changes.xml 11 Jul 2004 02:29:54 - 1.19 @@ -24,8 +24,9 @@ author email=[EMAIL PROTECTED]dIon Gillard/author /properties body -release version=1.6-SNAPSHOT date=in CVS +release version=1.5.1 date=2004-07-10 action dev=brett type=updateUpdate commons-httpclient and commons-net/action +/release release version=1.5 date=2004-03-10 action dev=evenisse type=add issue=MPDEPLOY-5Support for Putty in site:sshdeploy and add optional maven.ssh.args and maven.scp.args./action action dev=dion type=fixRemove telnet server for ftp deployment/action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jxr/xdocs changes.xml
brett 2004/07/10 19:33:11 Modified:jxr project.xml jxr/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.4.1 Revision ChangesPath 1.44 +6 -1 maven-plugins/jxr/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/jxr/project.xml,v retrieving revision 1.43 retrieving revision 1.44 diff -u -r1.43 -r1.44 --- project.xml 5 Jul 2004 21:07:19 - 1.43 +++ project.xml 11 Jul 2004 02:33:11 - 1.44 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-jxr-plugin/id nameMaven JXR Plug-in/name - currentVersion1.5-SNAPSHOT/currentVersion + currentVersion1.4.1/currentVersion descriptionCreate cross reference. Requires Maven 1.0 RC2./description shortDescriptionCreate cross reference/shortDescription urlhttp://maven.apache.org/reference/plugins/jxr//url @@ -124,6 +124,11 @@ id1.4/id name1.4/name tagMAVEN_JXR_1_4/tag +/version +version + id1.4.1/id + name1.4.1/name + tagMAVEN_JXR_1_4_1/tag /version /versions /project 1.21 +1 -1 maven-plugins/jxr/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/jxr/xdocs/changes.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- changes.xml 5 Jul 2004 21:07:19 - 1.20 +++ changes.xml 11 Jul 2004 02:33:11 - 1.21 @@ -25,7 +25,7 @@ author email=[EMAIL PROTECTED]Emmanuel Venisse/author /properties body -release version=1.5-SNAPSHOT date=in CVS +release version=1.4.1 date=2004-07-10 action dev=brett type=updateUpdate commons-* dependencies/action action dev=brett type=fix issue=MPJXR-9Remove xmlns on html elements as JSL messes it up/action /release - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/latex project.xml
brett 2004/07/10 19:37:09 Modified:latexproject.xml Log: [maven-scm-plugin] prepare release 1.4.1 Revision ChangesPath 1.32 +6 -1 maven-plugins/latex/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/latex/project.xml,v retrieving revision 1.31 retrieving revision 1.32 diff -u -r1.31 -r1.32 --- project.xml 5 Jul 2004 21:07:19 - 1.31 +++ project.xml 11 Jul 2004 02:37:09 - 1.32 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-latex-plugin/id nameMaven Latex Plug-in/name - currentVersion1.2.1-SNAPSHOT/currentVersion + currentVersion1.4.1/currentVersion description/ shortDescriptionProduce HTML from latex/shortDescription urlhttp://maven.apache.org/reference/plugins/latex//url @@ -44,6 +44,11 @@ id1.2/id name1.2/name tagMAVEN_LATEX_1_2/tag +/version +version + id1.4.1/id + name1.4.1/name + tagMAVEN_LATEX_1_4_1/tag /version /versions developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPSITE-5) SAXParserFactoryImpl not found from maven/lib/endorsed
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 10 Jul 2004 10:37 PM Changes: Fix Version changed to 1.6 Fix Version changed from 1.5 - For a full history of the issue, see: http://jira.codehaus.org/browse/MPSITE-5?page=history - View the issue: http://jira.codehaus.org/browse/MPSITE-5 Here is an overview of the issue: - Key: MPSITE-5 Summary: SAXParserFactoryImpl not found from maven/lib/endorsed Type: Bug Status: Unassigned Priority: Blocker Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-site-plugin Fix Fors: 1.6 Versions: 1.3 Assignee: Reporter: bmak Created: Wed, 10 Sep 2003 3:23 PM Updated: Sat, 10 Jul 2004 10:37 PM Environment: cygwin over win2k professional SP2 Description: BUILD FAILED File.. file:/d:/data/bmak/.maven/plugins/maven-site-plugin-1.2/ Element... attainGoal Line.. 24 Column 42 Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found I am able to run genapp and eclipse plugins just fine. but not site:generate I see that maven, per se, has maven/lib/endorsed/xerces-2.2.1.jar holding org.apache.xerces.jaxp.SAXParserFactoryImpl within it. And I see that the site plugin does NOT call out any xerces dependency - 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: (MPSITE-4) (Converted)? html files should be integrated into site layout
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 10 Jul 2004 10:37 PM Changes: Fix Version changed to 1.6 Fix Version changed from 1.5 - For a full history of the issue, see: http://jira.codehaus.org/browse/MPSITE-4?page=history - View the issue: http://jira.codehaus.org/browse/MPSITE-4 Here is an overview of the issue: - Key: MPSITE-4 Summary: (Converted)? html files should be integrated into site layout Type: Improvement Status: Unassigned Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-site-plugin Fix Fors: 1.6 Versions: 1.3 Assignee: Reporter: Ronald Blaschke Created: Fri, 5 Sep 2003 7:38 AM Updated: Sat, 10 Jul 2004 10:37 PM Description: Conversion of word documents to html is great. Integrating the html page(s) into the site layout would be perfect. :-) This may need the help of another plugin. Maybe some sort of layout plugin, which both xdoc and word2html (and other html-generating converters) could use. - 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: (MPSITE-7) Display status of inclusion in remote Maven repository on generated dependency page
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 10 Jul 2004 10:37 PM Changes: Fix Version changed to 1.6 Fix Version changed from 1.5 - For a full history of the issue, see: http://jira.codehaus.org/browse/MPSITE-7?page=history - View the issue: http://jira.codehaus.org/browse/MPSITE-7 Here is an overview of the issue: - Key: MPSITE-7 Summary: Display status of inclusion in remote Maven repository on generated dependency page Type: Improvement Status: Unassigned Priority: Trivial Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-site-plugin Fix Fors: 1.6 Versions: 1.3 Assignee: Reporter: Charlie Dobbie Created: Fri, 17 Oct 2003 9:29 AM Updated: Sat, 10 Jul 2004 10:37 PM Description: My project contains several dependencies that are not yet (or never will be) available from ibiblio. It would be useful to have an indication on the dependency page to distinguish these entries. As each environment has its own opinion of where dependencies come from, and thus what is and isn't custom, this would require a property named something like maven.repo.remote.official to store the project's opinion of standard repository locations. I can see this being implemented in one of two different ways: 1) At time of page generation, check whether each dependency exists in one of the official/standard repository locations. If in off-line mode, don't check and don't render any indication. 2) At time of dependency download, store extra information in the local repository detailing where the file came from. At page generation time, check these values instead. The first option is quick and easy, but requires network access which will slow a build down. The second option is more correct, but requires a (minor) change to a core Maven process. The second option may become out-of-sync with reality if a custom library is added - the local repository wouldn't be aware of this. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jira/xdocs changes.xml
brett 2004/07/10 20:00:12 Modified:jira project.xml jira/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.1.1 Revision ChangesPath 1.11 +6 -1 maven-plugins/jira/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/jira/project.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- project.xml 5 Jul 2004 21:07:19 - 1.10 +++ project.xml 11 Jul 2004 03:00:12 - 1.11 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-jira-plugin/id nameMaven JIRA Plug-in/name - currentVersion1.1.1-SNAPSHOT/currentVersion + currentVersion1.1.1/currentVersion descriptionThis plugin download issues from Jira and create a report./description shortDescriptionDownload issue from Jira/shortDescription urlhttp://maven.apache.org/reference/plugins/jira//url @@ -74,6 +74,11 @@ id1.1/id name1.1/name tagMAVEN_JIRA_1_1/tag +/version +version + id1.1.1/id + name1.1.1/name + tagMAVEN_JIRA_1_1_1/tag /version /versions /project 1.4 +2 -2 maven-plugins/jira/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/jira/xdocs/changes.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- changes.xml 5 Jul 2004 21:07:19 - 1.3 +++ changes.xml 11 Jul 2004 03:00:12 - 1.4 @@ -24,9 +24,9 @@ author email=[EMAIL PROTECTED]Brett Porter/author /properties body -release version=1.1.1-SNAPSHOT date=in CVS +release version=1.1.1 date=2004-07-10 action dev=brett type=updateUpdate commons-httpclient dependency/action /release -release version=1.1 date=2004-05-15/release +release version=1.1 date=2004-05-15/ /body /document - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/antlr/xdocs changes.xml
brett 2004/07/10 20:02:36 Modified:antlrproject.xml antlr/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.2.1 Revision ChangesPath 1.36 +6 -1 maven-plugins/antlr/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/antlr/project.xml,v retrieving revision 1.35 retrieving revision 1.36 diff -u -r1.35 -r1.36 --- project.xml 3 Jul 2004 02:03:39 - 1.35 +++ project.xml 11 Jul 2004 03:02:35 - 1.36 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-antlr-plugin/id nameMaven Antlr Plugin/name - currentVersion1.2.1-SNAPSHOT/currentVersion + currentVersion1.2.1/currentVersion description/ shortDescriptionProcess Antlr grammars/shortDescription urlhttp://maven.apache.org/reference/plugins/antlr//url @@ -44,6 +44,11 @@ id1.2/id name1.2/name tagMAVEN_ANTLR_1_2/tag +/version +version + id1.2.1/id + name1.2.1/name + tagMAVEN_ANTLR_1_2_1/tag /version /versions developers 1.13 +2 -2 maven-plugins/antlr/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/antlr/xdocs/changes.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- changes.xml 3 Jul 2004 02:04:27 - 1.12 +++ changes.xml 11 Jul 2004 03:02:35 - 1.13 @@ -24,10 +24,10 @@ author email=[EMAIL PROTECTED]dIon Gillard/author /properties body -release version=1.2.1-SNAPSHOT date=in CVS +release version=1.2.1 date=2004-07-10 action dev=brett type=updateUpdate to commons-lang 2.0/action /release -release version=1.2 date=2004-05-15/release +release version=1.2 date=2004-05-15/ release version=1.1 date=2003-09-29 action dev=dion type=updateupdate to commons-lang 1.0.1/action action dev=vmassol type=fix issue=MPANTLR-1Upgraded version of Antlr used to 2.7.2, so that this plugin plays well with the Checkstyle plugin (which requires Antlr 2.7.2)./action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/latka/xdocs changes.xml
brett 2004/07/10 20:05:04 Modified:latkaproject.xml latka/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.4.1 Revision ChangesPath 1.36 +7 -2 maven-plugins/latka/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/latka/project.xml,v retrieving revision 1.35 retrieving revision 1.36 diff -u -r1.35 -r1.36 --- project.xml 5 Jul 2004 21:07:19 - 1.35 +++ project.xml 11 Jul 2004 03:05:04 - 1.36 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-latka-plugin/id nameMaven Latka Plug-in/name - currentVersion1.5-SNAPSHOT/currentVersion + currentVersion1.4.1/currentVersion description/ shortDescriptionRun Latka scripts/shortDescription urlhttp://maven.apache.org/reference/plugins/latka//url @@ -45,8 +45,13 @@ name1.4/name tagMAVEN_LATKA_1_4/tag /version +version + id1.4.1/id + name1.4.1/name + tagMAVEN_LATKA_1_4_1/tag +/version /versions - developers/developers + developers/ dependencies dependency groupIdcommons-jelly/groupId 1.12 +3 -7 maven-plugins/latka/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/latka/xdocs/changes.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- changes.xml 5 Jul 2004 21:07:19 - 1.11 +++ changes.xml 11 Jul 2004 03:05:04 - 1.12 @@ -24,13 +24,9 @@ author email=[EMAIL PROTECTED]dIon Gillard/author /properties body -release version=1.5-SNAPSHOT date=in CVS - action dev=brett type=update -Update commons-httpclient to 2.0 - /action - action dev=dion type=update -Update docs to reflect the version of JMeter required. - /action +release version=1.4.1 date=2004-07-10 + action dev=brett type=updateUpdate commons-httpclient to 2.0/action + action dev=dion type=updateUpdate docs to reflect the version of JMeter required./action /release release version=1.4 date=2004-05-15 action dev=dion type=fix issue=MAVEN-993Fix MAVEN-993. Complain if file to be converted doesn't exist/action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/plugin-parent project.properties
brett 2004/07/10 20:09:50
Modified:plugin-parent project.properties
Log:
point links to mirrors
Revision ChangesPath
1.6 +2 -2 maven-plugins/plugin-parent/project.properties
Index: project.properties
===
RCS file: /home/cvs/maven-plugins/plugin-parent/project.properties,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- project.properties9 Jul 2004 08:13:39 - 1.5
+++ project.properties11 Jul 2004 03:09:50 - 1.6
@@ -21,7 +21,7 @@
# Display the date on the Maven web site
maven.xdoc.date = left
maven.xdoc.date.format = dd HH:mm z
-maven.xdoc.distributionUrl=http://www.ibiblio.org/maven/maven/plugins
+maven.xdoc.distributionUrl=http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins
# Checkstyle plugin settings
maven.checkstyle.header.file = ${basedir}/../checkstyle-license.txt
@@ -34,7 +34,7 @@
maven.artifact.legacy=false
# Announcement plugin properties
-maven.announcement.distributionUrl=http://www.apache.org/dist/java-repository/maven/plugins
+maven.announcement.distributionUrl=http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins
# Changes issue template
maven.changes.issue.template = %URL%/%ISSUE%
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven plugin-profile.xml
brett 2004/07/10 20:12:49 Modified:.Tag: MAVEN-1_0-BRANCH plugin-profile.xml Log: update plugin releases Revision ChangesPath No revision No revision 1.1.2.3 +15 -15maven/Attic/plugin-profile.xml Index: plugin-profile.xml === RCS file: /home/cvs/maven/Attic/plugin-profile.xml,v retrieving revision 1.1.2.2 retrieving revision 1.1.2.3 diff -u -r1.1.2.2 -r1.1.2.3 --- plugin-profile.xml10 Jul 2004 02:21:52 - 1.1.2.2 +++ plugin-profile.xml11 Jul 2004 03:12:49 - 1.1.2.3 @@ -1,17 +1,15 @@ ?xml version=1.0 encoding=UTF-8? plugins - plugin groupId=maven artifactId=maven-abbot-plugin version=1.0 - /plugin plugin groupId=maven artifactId=maven-announcement-plugin version=1.2 /plugin plugin groupId=maven artifactId=maven-ant-plugin version=1.7 /plugin - plugin groupId=maven artifactId=maven-antlr-plugin version=1.2 + plugin groupId=maven artifactId=maven-antlr-plugin version=1.2.1 /plugin plugin groupId=maven artifactId=maven-appserver-plugin version=2.0 /plugin - plugin groupId=maven artifactId=maven-artifact-plugin version=1.3 + plugin groupId=maven artifactId=maven-artifact-plugin version=1.4 /plugin plugin groupId=maven artifactId=maven-ashkelon-plugin version=1.2 /plugin @@ -19,6 +17,8 @@ /plugin plugin groupId=maven artifactId=maven-aspectwerkz-plugin version=1.2 /plugin + plugin groupId=maven artifactId=maven-abbot-plugin version=1.0 + /plugin plugin groupId=maven artifactId=maven-caller-plugin version=1.1 /plugin plugin groupId=maven artifactId=maven-castor-plugin version=1.2 @@ -35,7 +35,7 @@ /plugin plugin groupId=maven artifactId=maven-console-plugin version=1.1 /plugin - plugin groupId=maven artifactId=maven-cruisecontrol-plugin version=1.3 + plugin groupId=maven artifactId=maven-cruisecontrol-plugin version=1.4 /plugin plugin groupId=maven artifactId=maven-dashboard-plugin version=1.3 /plugin @@ -57,7 +57,7 @@ /plugin plugin groupId=maven artifactId=maven-genapp-plugin version=2.2 /plugin - plugin groupId=maven artifactId=maven-gump-plugin version=1.3 + plugin groupId=maven artifactId=maven-gump-plugin version=1.4 /plugin plugin groupId=maven artifactId=maven-hibernate-plugin version=1.1 /plugin @@ -95,7 +95,7 @@ /plugin plugin groupId=maven artifactId=maven-jetty-plugin version=1.1 /plugin - plugin groupId=maven artifactId=maven-jira-plugin version=1.1 + plugin groupId=maven artifactId=maven-jira-plugin version=1.1.1 /plugin plugin groupId=maven artifactId=maven-jnlp-plugin version=1.3 /plugin @@ -103,15 +103,15 @@ /plugin plugin groupId=maven artifactId=maven-junit-doclet-plugin version=1.2 /plugin - plugin groupId=maven artifactId=maven-jxr-plugin version=1.4 + plugin groupId=maven artifactId=maven-jxr-plugin version=1.4.1 /plugin - plugin groupId=maven artifactId=maven-latex-plugin version=1.2 + plugin groupId=maven artifactId=maven-latex-plugin version=1.4.1 /plugin - plugin groupId=maven artifactId=maven-latka-plugin version=1.4 + plugin groupId=maven artifactId=maven-latka-plugin version=1.4.1 /plugin plugin groupId=maven artifactId=maven-license-plugin version=1.2 /plugin - plugin groupId=maven artifactId=maven-linkcheck-plugin version=1.3.1 + plugin groupId=maven artifactId=maven-linkcheck-plugin version=1.3.2 /plugin plugin groupId=maven artifactId=maven-multichanges-plugin version=1.1 /plugin @@ -129,19 +129,19 @@ /plugin plugin groupId=maven artifactId=maven-pom-plugin version=1.4.1 /plugin - plugin groupId=maven artifactId=maven-rar-plugin version=1.0 - /plugin plugin groupId=maven artifactId=maven-release-plugin version=1.4 /plugin plugin groupId=maven artifactId=maven-repository-plugin version=1.2 /plugin + plugin groupId=maven artifactId=maven-rar-plugin version=1.0 + /plugin plugin groupId=maven artifactId=maven-scm-plugin version=1.4 /plugin plugin groupId=maven artifactId=maven-shell-plugin version=1.1 /plugin plugin groupId=maven artifactId=maven-simian-plugin version=1.4 /plugin - plugin groupId=maven artifactId=maven-site-plugin version=1.5 + plugin groupId=maven artifactId=maven-site-plugin version=1.5.1 /plugin plugin groupId=maven artifactId=maven-struts-plugin version=1.3 /plugin @@ -161,6 +161,6 @@ /plugin plugin groupId=maven artifactId=maven-wizard-plugin version=1.1 /plugin - plugin groupId=maven artifactId=maven-xdoc-plugin version=1.7.2 + plugin groupId=maven artifactId=maven-xdoc-plugin version=1.8 /plugin /plugins
Re: cvs commit: maven plugin-profile.xml
On Sun, 11 Jul 2004 10:31:39 +1000, Brett Porter [EMAIL PROTECTED] wrote: No, its used to build the release. I guess it could be added to the release notes? That and to allow a plugin to fetch it from a well known application and check against the installed ones. -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
