RE: [vote] release Maven 1.0
+1 Arnaud > -Message d'origine- > De : Brett Porter [mailto:[EMAIL PROTECTED] > Envoyé : mardi 13 juillet 2004 03:15 > À : [EMAIL PROTECTED] > Cc : [EMAIL PROTECTED] > Objet : [vote] release Maven 1.0 > > Dear PMC, > > I propose we release Maven 1.0. The contents are identical to the test release > built the other day, with the addition of the following: > maven-javadoc-plugin-1.6.1 (pending vote) > maven-changelog-plugin-1.7.1 > maven-jnlp-plugin-1.4 > maven-jcoverage-plugin-1.0.7 > and the version will be changed from "1.0-final-SNAPSHOT" to just "1.0". > > I will continue working on documentation this week, but now believe that this > need not be a dependency for the Maven release. > > From me, it's obviously +1. > > Cheers, > Brett > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [vote] release javadoc 1.6.1
+1, Sorry I didn't see this bug :-( Arnaud > -Message d'origine- > De : Brett Porter [mailto:[EMAIL PROTECTED] > Envoyé : mardi 13 juillet 2004 03:09 > À : [EMAIL PROTECTED] > Objet : [vote] release javadoc 1.6.1 > > There was a regression in 1.6 that caused the javadoc to fail hard when no > sources were found (check-needed had a bug). > > The patch I will apply is attached when I have CVS access tonight, and then will > release Javadoc 1.6.1. > > Is everyone in agreeance? +1 from me. > > Cheers, > Brett > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release Maven 1.0
+1 Alex > > On Jul 12, 2004, at 9:15 PM, Brett Porter wrote: > > > > > Dear PMC, > > > > > > I propose we release Maven 1.0. The contents are identical to the test > > > release > > > built the other day, with the addition of the following: > > > maven-javadoc-plugin-1.6.1 (pending vote) > > > maven-changelog-plugin-1.7.1 > > > maven-jnlp-plugin-1.4 > > > maven-jcoverage-plugin-1.0.7 > > > and the version will be changed from "1.0-final-SNAPSHOT" to just > > > "1.0". > > > > > > I will continue working on documentation this week, but now believe > > > that this > > > need not be a dependency for the Maven release. > > > > > > From me, it's obviously +1. > > > > > > Cheers, > > > Brett > > > > -- > Bob McWhirter[EMAIL PROTECTED] > The Werken Company http://werken.com/ > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release Maven 1.0
+1 rock'n'roll. -bob On Mon, 12 Jul 2004, Peter Kazmier wrote: > +1 > > > On Jul 12, 2004, at 9:15 PM, Brett Porter wrote: > > > Dear PMC, > > > > I propose we release Maven 1.0. The contents are identical to the test > > release > > built the other day, with the addition of the following: > > maven-javadoc-plugin-1.6.1 (pending vote) > > maven-changelog-plugin-1.7.1 > > maven-jnlp-plugin-1.4 > > maven-jcoverage-plugin-1.0.7 > > and the version will be changed from "1.0-final-SNAPSHOT" to just > > "1.0". > > > > I will continue working on documentation this week, but now believe > > that this > > need not be a dependency for the Maven release. > > > > From me, it's obviously +1. > > > > Cheers, > > Brett > -- Bob McWhirter[EMAIL PROTECTED] The Werken Company http://werken.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release Maven 1.0
+1 On Jul 12, 2004, at 9:15 PM, Brett Porter wrote: Dear PMC, I propose we release Maven 1.0. The contents are identical to the test release built the other day, with the addition of the following: maven-javadoc-plugin-1.6.1 (pending vote) maven-changelog-plugin-1.7.1 maven-jnlp-plugin-1.4 maven-jcoverage-plugin-1.0.7 and the version will be changed from "1.0-final-SNAPSHOT" to just "1.0". I will continue working on documentation this week, but now believe that this need not be a dependency for the Maven release. From me, it's obviously +1. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release javadoc 1.6.1
On Mon, 2004-07-12 at 21:08, Brett Porter wrote: > There was a regression in 1.6 that caused the javadoc to fail hard when no > sources were found (check-needed had a bug). > > The patch I will apply is attached when I have CVS access tonight, and then will > release Javadoc 1.6.1. > > Is everyone in agreeance? +1 from me. +1 > Cheers, > Brett > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[vote] release Maven 1.0
Dear PMC, I propose we release Maven 1.0. The contents are identical to the test release built the other day, with the addition of the following: maven-javadoc-plugin-1.6.1 (pending vote) maven-changelog-plugin-1.7.1 maven-jnlp-plugin-1.4 maven-jcoverage-plugin-1.0.7 and the version will be changed from "1.0-final-SNAPSHOT" to just "1.0". I will continue working on documentation this week, but now believe that this need not be a dependency for the Maven release. >From me, it's obviously +1. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPJIRA-3) The element type "link" must be terminated by the matching end-tag
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Mon, 12 Jul 2004 9:10 PM Changes: Fix Version changed to 1.2 - For a full history of the issue, see: http://jira.codehaus.org/browse/MPJIRA-3?page=history - 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 Fix Fors: 1.2 Versions: 1.1 Assignee: Emmanuel Venisse Reporter: Paul Spencer Created: Sat, 10 Jul 2004 5:26 AM Updated: Mon, 12 Jul 2004 9:10 PM 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=rss&pid=10492&sorter/field=issuekey&sorter/order=DESC&sorter/field=status&sorter/order=DESC&tempMax=1000&reset=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 "". Nested exception: The element type "link" must be terminated by the matching end-tag "". 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]
[vote] release javadoc 1.6.1
There was a regression in 1.6 that caused the javadoc to fail hard when no sources were found (check-needed had a bug). The patch I will apply is attached when I have CVS access tonight, and then will release Javadoc 1.6.1. Is everyone in agreeance? +1 from me. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jar/src/plugin-test/src/main/org/apache/maven Dummy.java
dion2004/07/12 16:35:06
Modified:jar project.xml plugin.jelly plugin.properties
Removed: jar/src/plugin-test project.xml .cvsignore maven.xml
jar/src/plugin-test/src/main/org/apache/maven Dummy.java
Log:
Rollback MPJAR-32.
Revision ChangesPath
1.31 +1 -1 maven-plugins/jar/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven-plugins/jar/project.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- project.xml 12 Jul 2004 06:58:00 - 1.30
+++ project.xml 12 Jul 2004 23:35:06 - 1.31
@@ -23,7 +23,7 @@
3
maven-jar-plugin
Maven Jar Plug-in
- 1.6.1-SNAPSHOT
+ 1.6
Plugin for creating JAR files. Requires Maven 1.0 RC2.
Create jar files
http://maven.apache.org/reference/plugins/jar/
1.42 +1 -18 maven-plugins/jar/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/jar/plugin.jelly,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- plugin.jelly 12 Jul 2004 06:58:00 - 1.41
+++ plugin.jelly 12 Jul 2004 23:35:06 - 1.42
@@ -63,11 +63,7 @@
You must define currentVersion in your POM.
-
-
-
-
-
+
@@ -273,17 +269,4 @@
project="${pom}"
/>
-
-
-
-
-
-
-
-
-
-
-
-
-
1.12 +0 -2 maven-plugins/jar/plugin.properties
Index: plugin.properties
===
RCS file: /home/cvs/maven-plugins/jar/plugin.properties,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- plugin.properties 12 Jul 2004 06:58:01 - 1.11
+++ plugin.properties 12 Jul 2004 23:35:06 - 1.12
@@ -24,5 +24,3 @@
maven.jar.excludes = **/package.html
maven.jar.index=false
maven.jar.compress=true
-maven.jar.include.source=false
-maven.jar.source.path=src
\ No newline at end of file
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vote for release plugins
Holy crap! Where did this mammoth list come from? I audited all the plugins that had significant changes and all the releases are done. jnlp was the only one that didn't get done, and it now has. I was going to vote on a Maven 1.0 release today, except that I found that javadoc fails fairly regularly at work. Please, let's keep this sane. I see no reason to do any more plugin releases for 1.0 except for javadoc to fix this bug which I'll do tonight. If we do all these, all the testing needs to be done all over again. I'm +0 to releasing any of these plugins, but -1 to including those releases in Maven 1.0. Happy to hear convincing arguments on a plugin-by-plugin basis though. - Brett Quoting Emmanuel Venisse <[EMAIL PROTECTED]>: > Hi, > > I would like to release some plugins before the 1.0 release. All this > plugins fix some little bug, so with a release, we'll limit bug registration > on jira or on mailling list. > > ant : +1 > appserver : +0 > changes : +0 > changelog : +1 > checkstyle : +1 > clover : +0 > dist : +1 > ear : +1 > eclipse : +1 > faq : +1 > hibernate : +1 > j2ee : +0 > jar : +0 > java : +0 > jboss : +0 > jdiff : +0 > jetty : +0 > junit-report : +1 > multiproject : +0 > nsis : +1 > pdf : +1 > rar : +0 > scm : +1 > struts : +1 > tasklist : +0 > war : +1 > webserver : +1 > > Emmanuel > > > - > 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: (MAVEN-1371) maven.repo.remote w/ multiple repos specified redownloads jar from each repo in the list
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MAVEN-1371 Here is an overview of the issue: - Key: MAVEN-1371 Summary: maven.repo.remote w/ multiple repos specified redownloads jar from each repo in the list Type: Bug Status: Closed Priority: Minor Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Fix Fors: 1.0 Versions: 1.0-rc4 Assignee: Reporter: Ian P. Springer Created: Mon, 12 Jul 2004 3:35 PM Updated: Mon, 12 Jul 2004 7:17 PM Environment: n/a Description: In my project.xml, I have: maven.repo.remote=http://www.ibiblio.org/maven/,http://mip.esr.hp.com/wsdm/repository/ I would expect this to mean: Attempt to download each dep jar from www.ibiblio.org first. If that fails, then try to download the jar from mip.esr.hp.com. However, the way it's working, even if it successfully downloads a jar from ibiblio, it still proceeds to redownload the jar from the second repository and overwrite the first one it just downloaded. - 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?
Eric Pugh wrote:
Can we add maven.gen.src=${maven.build.dest}/generated-sources?
This sounds alot like what http://jira.codehaus.org/browse/MAVEN-723
talks about (albeit in a different context).
If what you are talking about can/should be done, wouldn't this be just
another way of using multiple source directories?
What I'm getting at is this; if we can do this, can't we also support
multiple source directories as well? Would make the solution more
complete IMHO.
/ pål
--
Pål Brattberg
Eminds AB
S:t Eriksgatan 37a
112 34 Stockholm
http://www.eminds.se
Direct: +46 8 545 639 80
Mobile: +46 7 077 000 81
Fax:+46 8 545 639 81
E-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven plugin-profile.xml
evenisse2004/07/12 14:30:35 Modified:.Tag: MAVEN-1_0-BRANCH plugin-profile.xml Log: Update changelog plugin. Revision ChangesPath No revision No revision 1.1.2.6 +1 -1 maven/Attic/plugin-profile.xml Index: plugin-profile.xml === RCS file: /home/cvs/maven/Attic/plugin-profile.xml,v retrieving revision 1.1.2.5 retrieving revision 1.1.2.6 diff -u -r1.1.2.5 -r1.1.2.6 --- plugin-profile.xml12 Jul 2004 13:22:10 - 1.1.2.5 +++ plugin-profile.xml12 Jul 2004 21:30:35 - 1.1.2.6 @@ -23,7 +23,7 @@ - + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/changelog/xdocs changes.xml
evenisse2004/07/12 14:17:33 Modified:changelog project.xml changelog/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.7.1 Revision ChangesPath 1.48 +6 -1 maven-plugins/changelog/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/changelog/project.xml,v retrieving revision 1.47 retrieving revision 1.48 diff -u -r1.47 -r1.48 --- project.xml 9 Jul 2004 11:53:46 - 1.47 +++ project.xml 12 Jul 2004 21:17:33 - 1.48 @@ -23,7 +23,7 @@ 3 maven-changelog-plugin Maven Changelog Plugin - 1.7.1-SNAPSHOT + 1.7.1 Produce SCM changelog reports http://maven.apache.org/reference/plugins/changelog/ @@ -54,6 +54,11 @@ 1.7 1.7 MAVEN_CHANGELOG_1_7 + + + 1.7.1 + 1.7.1 + MAVEN_CHANGELOG_1_7_1 1.40 +1 -1 maven-plugins/changelog/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/changelog/xdocs/changes.xml,v retrieving revision 1.39 retrieving revision 1.40 diff -u -r1.39 -r1.40 --- changes.xml 9 Jul 2004 12:37:36 - 1.39 +++ changes.xml 12 Jul 2004 21:17:33 - 1.40 @@ -25,7 +25,7 @@ Emmanuel Venisse - + changelog.xml author tag in Clearcase contains developer.id. Plugin does not find the password for the CVSROOT in .cvspass if the CVSROOT in .cvspass is preceded by a "/1". - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1371) maven.repo.remote w/ multiple repos specified redownloads jar from each repo in the list
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1371 Here is an overview of the issue: - Key: MAVEN-1371 Summary: maven.repo.remote w/ multiple repos specified redownloads jar from each repo in the list Type: Bug Status: Unassigned Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Versions: 1.0-rc4 Assignee: Reporter: Ian P. Springer Created: Mon, 12 Jul 2004 3:35 PM Updated: Mon, 12 Jul 2004 3:35 PM Environment: n/a Description: In my project.xml, I have: maven.repo.remote=http://www.ibiblio.org/maven/,http://mip.esr.hp.com/wsdm/repository/ I would expect this to mean: Attempt to download each dep jar from www.ibiblio.org first. If that fails, then try to download the jar from mip.esr.hp.com. However, the way it's working, even if it successfully downloads a jar from ibiblio, it still proceeds to redownload the jar from the second repository and overwrite the first one it just downloaded. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-1370) "-Duser.home.env=%HOME%" option causes java.exe failure.
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MAVEN-1370 Here is an overview of the issue: - Key: MAVEN-1370 Summary: "-Duser.home.env=%HOME%" option causes java.exe failure. Type: Bug Status: Closed Priority: Minor Resolution: DUPLICATE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: cli Assignee: Reporter: Brent Worden Created: Mon, 12 Jul 2004 12:16 PM Updated: Mon, 12 Jul 2004 1:45 PM Environment: WinXP JDK 1.3.1_06-b01 Maven 1.0-rc4 Description: After a new install of Maven 1.0-rc4. I added a MAVEN_HOME environment variable and added %MAVEN_HOME%\bin to PATH. When I ran maven with no command-line options, I received the java.exe usage message indicating an illegal command line argument. By process of elimination, I tracked it down to the user.home.env properties setting. By removing the quotes around the option, java.exe executed and the Maven ran and completed. I tried the same thing with a new install of Maven 1.0-rc3 and JDK 1.3.1_06-b01 and I did not receive the java.exe usage message. - 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-1370) "-Duser.home.env=%HOME%" option causes java.exe failure.
The following comment has been added to this issue: Author: Brent Worden Created: Mon, 12 Jul 2004 12:19 PM Body: BTW, the HOME environment variable is H:\ which is a mapped network drive. - View this comment: http://jira.codehaus.org/browse/MAVEN-1370?page=comments#action_21689 - View the issue: http://jira.codehaus.org/browse/MAVEN-1370 Here is an overview of the issue: - Key: MAVEN-1370 Summary: "-Duser.home.env=%HOME%" option causes java.exe failure. Type: Bug Status: Unassigned Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: cli Assignee: Reporter: Brent Worden Created: Mon, 12 Jul 2004 12:16 PM Updated: Mon, 12 Jul 2004 12:19 PM Environment: WinXP JDK 1.3.1_06-b01 Maven 1.0-rc4 Description: After a new install of Maven 1.0-rc4. I added a MAVEN_HOME environment variable and added %MAVEN_HOME%\bin to PATH. When I ran maven with no command-line options, I received the java.exe usage message indicating an illegal command line argument. By process of elimination, I tracked it down to the user.home.env properties setting. By removing the quotes around the option, java.exe executed and the Maven ran and completed. I tried the same thing with a new install of Maven 1.0-rc3 and JDK 1.3.1_06-b01 and I did not receive the java.exe usage message. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1370) "-Duser.home.env=%HOME%" option causes java.exe failure.
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1370 Here is an overview of the issue: - Key: MAVEN-1370 Summary: "-Duser.home.env=%HOME%" option causes java.exe failure. Type: Bug Status: Unassigned Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: cli Assignee: Reporter: Brent Worden Created: Mon, 12 Jul 2004 12:16 PM Updated: Mon, 12 Jul 2004 12:16 PM Environment: WinXP JDK 1.3.1_06-b01 Maven 1.0-rc4 Description: After a new install of Maven 1.0-rc4. I added a MAVEN_HOME environment variable and added %MAVEN_HOME%\bin to PATH. When I ran maven with no command-line options, I received the java.exe usage message indicating an illegal command line argument. By process of elimination, I tracked it down to the user.home.env properties setting. By removing the quotes around the option, java.exe executed and the Maven ran and completed. I tried the same thing with a new install of Maven 1.0-rc3 and JDK 1.3.1_06-b01 and I did not receive the java.exe usage message. - 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: jar install plugin (maven)
Yes, you're right, the jar is only generated whe any file changes. I don't see much sense to do what you say in an install goal, as it's used when making releases, neither in an install-snapshot as usually you will clean first to ensure everything is correctly built, do you ;)? If you don't think so please raise an isue in JIRA (artifact plugin) and try to convince. Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net > -Original Message- > From: colin saxton [mailto:[EMAIL PROTECTED] > Sent: Monday, July 12, 2004 4:13 PM > To: [EMAIL PROTECTED] > Subject: RE: jar install plugin (maven) > > Not when I tested it...the jar is only generated if you have > updated any of the files that make up the jar...If you don't > change the files then the jar doesn't change...so if > overwrite is set to false then it would not copy the latest > jar to the repository since it will not have changed. > On Mon, 2004-07-12 at 13:41, Carlos Sanchez wrote: > > Hi, > > > > jar:install attains jar:jar so the jar created will have > the current > > date, it will always override the one in the repository. > > > > Regards > > > > Carlos Sanchez > > A Coruña, Spain > > > > Oness Project > > http://oness.sourceforge.net > > > > > > > -Original Message- > > > From: colin saxton [mailto:[EMAIL PROTECTED] > > > Sent: Monday, July 12, 2004 1:35 PM > > > To: [EMAIL PROTECTED] > > > Subject: jar install plugin (maven) > > > > > > Just wondering! The jar:install goal copies the jar to the local > > > repository even if there are no changes since overwrite is set to > > > true...This can be a problem when using the reactor since all of > > > your subcomponents will now have new dates set against > jars in the > > > repository...it just causes unnecessary builds...can we just set > > > this to false or would it cause problems? > > > > > > > > > > > > > - 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 test release
Hi, IMHO a sources are needed but I agree with jvz and see it more clear in a separate artifact type. Think that javadoc may be also needed and end up with all these in a binary jar is not a good idea. The folks at mevenide only have to add a check so if the source file is present in the repository add it as source artifact. The same for a javadoc artifact. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net > -Original Message- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: Monday, July 12, 2004 5:37 PM > To: Maven Users List > Subject: Re: maven test release > > On Mon, 2004-07-12 at 11:10, Dion Gillard wrote: > > > I'm not sure I see the issue. If you are suggesting it should be > > another 'artifact JAR', I can see how that would be good, with a > > standard naming convention. But I'm not sure why having a > 'mix bag' is > > an issue. > > Joe user downloads one JAR and finds it works somehow for > stepping through the source and then Joe user downloads > another JAR and find this doesn't work which will illicit all > sorts of questions about why this works in some cases and > doesn't in others. Multiplicity with respect to this, as it > is with all things attempted in Maven, is not a good thing. > > > > For releases, I think it would be cool to have the source > jar made > > > as well as part of the standard process. For snapshots I > don't know > > > if this is really worth it. > > > > Do you meant the one produced by the dist plugin? > > > > > How to make this easy for users? I think this falls in > the domain of > > > the IDE. For example, I don't think it would take much for the > > > Mevenide folks to add a snippet of code to look for a > source archive > > > artifact and pull it down if the user wishes. We should make the > > > source drops available but mixing sources with binaries I > think is a big no no. > > > > I can easily roll it back out of the jar plugin if you > like, but since > > Brett said 'commit away', I'm reluctant to do so. > > If putting the sources in the JAR is an option and that's > there now then I'm -1 on that becoming any sort of standard > of distributing sources. > > > For each L/GPL jar that gets distributed, the license says > the source > > must accompany the binaries. > > They don't have to be in the JAR, they have to be available. > > > I get the feeling ibiblio is illegally distributing jars like > > checkstyle because there is no source provided with the > binaries, and > > Maven simply downloads the jar. > > The sources have to be available and we do not repackage > anything and make a new distribution for which we would have > to provide the source. > But for most things like checkstyle the source is freely available: > > http://sourceforge.net/project/showfiles.php?group_id=29721 > > > Having source in the jar alleviates the need to do this for > those with > > that sort of license, similar to ensuring the license is in > META-INF. > > The source is available, this is not a problem and if any > project sees it as a problem, as I noted when Dalibor Topic > complained the last time, we can remove their artifacts from > ibiblio but I doubt any project would want that. > > Or you could just change the deploy plugin to push the source > archive up there too and then IDEs or users can pull down > what they like. > > > If the Maven team doesn't want this feature, I could simply > release it > > elsewhere if there's a need. > > Source archive available for every artifact: > > +1 > > Mixing in the sources with the standard JAR: > > -1 > > > -- > 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] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven test release
It's currently in v1.6.1-SNAPSHOT of the jar plugin. Which could be built from CVS. On Mon, 12 Jul 2004 16:22:03 +0200, Jerome Lacoste <[EMAIL PROTECTED]> wrote: > > > The reasons I think for including source jars in Maven 1.0 > [...] > > That's my 2c. Does anyone else feel that it's a must have feature for 1.0? > > As a user, I would also like to have the code. > > If it isn't possible to do that for 1.0, maybe there is a way to > automatically download/install them using a specific goal? > > Jerome > > - > 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 test release
> The reasons I think for including source jars in Maven 1.0 [...] > That's my 2c. Does anyone else feel that it's a must have feature for 1.0? As a user, I would also like to have the code. If it isn't possible to do that for 1.0, maybe there is a way to automatically download/install them using a specific goal? Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPJAVA-25) Bug in documentation: maven.compile.target property is missed
The following comment has been added to this issue: Author: dion gillard Created: Mon, 12 Jul 2004 9:59 AM Body: Where are you looking? On http://maven.apache.org/reference/plugins/java/properties.html the maven.compile.target property is defined. Yes, .source is defined twice...but target is still defined. - View this comment: http://jira.codehaus.org/browse/MPJAVA-25?page=comments#action_21687 - View the issue: http://jira.codehaus.org/browse/MPJAVA-25 Here is an overview of the issue: - Key: MPJAVA-25 Summary: Bug in documentation: maven.compile.target property is missed Type: Bug Status: Open Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-java-plugin Assignee: Jason van Zyl Reporter: Alexey Kakunin Created: Mon, 12 Jul 2004 7:25 AM Updated: Mon, 12 Jul 2004 9:59 AM Environment: Maven 1.0 rc4 Description: I found this bug in Java-Plugin web-site. In properties documentation mave.compile.target property is missed. But maven.compile.source property exist twice :) Seems one of them should be renamed to target. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vote for release plugins
I'd prefer to wait to make sure they'll be in the release, otherwise it can wait On Mon, 12 Jul 2004 15:50:58 +0200, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > Can you release some of them? > > Emmanuel > > > > - Original Message - > From: "Dion Gillard" <[EMAIL PROTECTED]> > To: "Maven Developers List" <[EMAIL PROTECTED]> > Sent: Monday, July 12, 2004 3:28 PM > Subject: Re: Vote for release plugins > > > On Mon, 12 Jul 2004 15:29:23 +0200, Emmanuel Venisse > > <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > I would like to release some plugins before the 1.0 release. All this > > > plugins fix some little bug, so with a release, we'll limit bug > registration > > > on jira or on mailling list. > > > > > > ant : +1 > > > appserver : +0 > > > changes : +0 > > > changelog : +1 > > > checkstyle : +1 > > > clover : +0 > > > dist : +1 > > > ear : +1 > > > eclipse : +1 > > > faq : +1 > > > hibernate : +1 > > > j2ee : +0 > > > jar : +0 > > > java : +0 > > > jboss : +0 > > > jdiff : +0 > > > jetty : +0 > > > junit-report : +1 > > > multiproject : +0 > > > nsis : +1 > > > pdf : +1 > > > rar : +0 > > > scm : +1 > > > struts : +1 > > > tasklist : +0 > > > war : +1 > > > webserver : +1 > > > > I'm happy to do some of the ones I've changed, nsis, struts,j2ee,rar, > > faq again, and help with others. > > > > -- > > http://www.multitask.com.au/people/dion/ > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vote for release plugins
Can you release some of them? Emmanuel - Original Message - From: "Dion Gillard" <[EMAIL PROTECTED]> To: "Maven Developers List" <[EMAIL PROTECTED]> Sent: Monday, July 12, 2004 3:28 PM Subject: Re: Vote for release plugins > On Mon, 12 Jul 2004 15:29:23 +0200, Emmanuel Venisse > <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I would like to release some plugins before the 1.0 release. All this > > plugins fix some little bug, so with a release, we'll limit bug registration > > on jira or on mailling list. > > > > ant : +1 > > appserver : +0 > > changes : +0 > > changelog : +1 > > checkstyle : +1 > > clover : +0 > > dist : +1 > > ear : +1 > > eclipse : +1 > > faq : +1 > > hibernate : +1 > > j2ee : +0 > > jar : +0 > > java : +0 > > jboss : +0 > > jdiff : +0 > > jetty : +0 > > junit-report : +1 > > multiproject : +0 > > nsis : +1 > > pdf : +1 > > rar : +0 > > scm : +1 > > struts : +1 > > tasklist : +0 > > war : +1 > > webserver : +1 > > I'm happy to do some of the ones I've changed, nsis, struts,j2ee,rar, > faq again, and help with others. > > -- > http://www.multitask.com.au/people/dion/ > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vote for release plugins
On Mon, 12 Jul 2004 15:29:23 +0200, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > Hi, > > I would like to release some plugins before the 1.0 release. All this > plugins fix some little bug, so with a release, we'll limit bug registration > on jira or on mailling list. > > ant : +1 > appserver : +0 > changes : +0 > changelog : +1 > checkstyle : +1 > clover : +0 > dist : +1 > ear : +1 > eclipse : +1 > faq : +1 > hibernate : +1 > j2ee : +0 > jar : +0 > java : +0 > jboss : +0 > jdiff : +0 > jetty : +0 > junit-report : +1 > multiproject : +0 > nsis : +1 > pdf : +1 > rar : +0 > scm : +1 > struts : +1 > tasklist : +0 > war : +1 > webserver : +1 I'm happy to do some of the ones I've changed, nsis, struts,j2ee,rar, faq again, and help with others. -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Vote for release plugins
Hi, I would like to release some plugins before the 1.0 release. All this plugins fix some little bug, so with a release, we'll limit bug registration on jira or on mailling list. ant : +1 appserver : +0 changes : +0 changelog : +1 checkstyle : +1 clover : +0 dist : +1 ear : +1 eclipse : +1 faq : +1 hibernate : +1 j2ee : +0 jar : +0 java : +0 jboss : +0 jdiff : +0 jetty : +0 junit-report : +1 multiproject : +0 nsis : +1 pdf : +1 rar : +0 scm : +1 struts : +1 tasklist : +0 war : +1 webserver : +1 Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven test release
On Mon, 12 Jul 2004 13:13:30 +1000, Brett Porter <[EMAIL PROTECTED]> wrote: > Absolutely. You're welcome to try and convince me/the list otherwise on it... I > just feel that its not a must-have feature for 1.0. We're getting patches almost > daily now, and we'd never cut a release if all of them were applied first. Just > drawing a line in the sand :) > > > > Sound reasonable? Let me know how testing goes. The reasons I think for including source jars in Maven 1.0 1) Projects whose license require distribution of the source can do so via the same means as the binary. 2) Jars created by Maven can be 'IDE Debug Friendly'. This allows users to step through code in the jars during debugging sessions with no extra download and little extra configuration. 3) Its a simple change, with test cases and 4) It's been requested before, e.g. a) http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=808912 b) http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=809540 That's my 2c. Does anyone else feel that it's a must have feature for 1.0? -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven plugin-profile.xml
evenisse2004/07/12 06:22:10 Modified:.Tag: MAVEN-1_0-BRANCH plugin-profile.xml Log: Update jnlp plugin Revision ChangesPath No revision No revision 1.1.2.5 +1 -1 maven/Attic/plugin-profile.xml Index: plugin-profile.xml === RCS file: /home/cvs/maven/Attic/plugin-profile.xml,v retrieving revision 1.1.2.4 retrieving revision 1.1.2.5 diff -u -r1.1.2.4 -r1.1.2.5 --- plugin-profile.xml12 Jul 2004 07:51:23 - 1.1.2.4 +++ plugin-profile.xml12 Jul 2004 13:22:10 - 1.1.2.5 @@ -97,7 +97,7 @@ - + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jnlp/xdocs changes.xml
evenisse2004/07/12 06:02:51
Modified:jnlp project.xml
jnlp/xdocs changes.xml
Log:
[maven-scm-plugin] prepare release 1.4
Revision ChangesPath
1.23 +6 -1 maven-plugins/jnlp/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven-plugins/jnlp/project.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- project.xml 25 Jun 2004 15:24:29 - 1.22
+++ project.xml 12 Jul 2004 13:02:50 - 1.23
@@ -23,7 +23,7 @@
3
maven-jnlp-plugin
Maven JNLP Plug-in
- 1.4-SNAPSHOT
+ 1.4
JNLP Plugin for Maven
http://maven.apache.org/reference/plugins/jnlp/
http://jira.codehaus.org/browse/MPJNLP
@@ -59,6 +59,11 @@
1.3
1.3
MAVEN_JNLP_1_3
+
+
+ 1.4
+ 1.4
+ MAVEN_JNLP_1_4
1.20 +2 -2 maven-plugins/jnlp/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/jnlp/xdocs/changes.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- changes.xml 19 Jun 2004 12:42:25 - 1.19
+++ changes.xml 12 Jul 2004 13:02:50 - 1.20
@@ -25,7 +25,7 @@
Emmanuel Venisse
-
+
Add initial attempt at test project
Initialize correctly
jnlp:generate-keystore goal.
Added Support for JarDiff.
@@ -36,7 +36,7 @@
Added extra property
maven.jnlp.cert.version to support certificate renewals.
Updated jarversions
support to take SNAPSHOT jars into account.
-
+
Add support for jar
versions.
Remove the need for ${pom} interpolation
in properties. The use of the maven:property tag is now used to glean a default
property.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: jar install plugin (maven)
Hi, jar:install attains jar:jar so the jar created will have the current date, it will always override the one in the repository. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net > -Original Message- > From: colin saxton [mailto:[EMAIL PROTECTED] > Sent: Monday, July 12, 2004 1:35 PM > To: [EMAIL PROTECTED] > Subject: jar install plugin (maven) > > Just wondering! The jar:install goal copies the jar to the > local repository even if there are no changes since overwrite > is set to true...This can be a problem when using the reactor > since all of your subcomponents will now have new dates set > against jars in the repository...it just causes unnecessary > builds...can we just set this to false or would it cause problems? > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1369) Multiple dependencies with same artifactId but different types
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1369 Here is an overview of the issue: - Key: MAVEN-1369 Summary: Multiple dependencies with same artifactId but different types Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Assignee: Reporter: Guillaume Nodet Created: Mon, 12 Jul 2004 8:10 AM Updated: Mon, 12 Jul 2004 8:10 AM Description: I've got a maven project that generates a jar and a tld with the same name. When using it as a dependency in another project, only the first dependency is taken into account and the other one (same artifactId but different type is ignored) ... - 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]
jar install plugin (maven)
Just wondering! The jar:install goal copies the jar to the local repository even if there are no changes since overwrite is set to true...This can be a problem when using the reactor since all of your subcomponents will now have new dates set against jars in the repository...it just causes unnecessary builds...can we just set this to false or would it cause problems? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPJAVA-25) Bug in documentation: maven.compile.target property is missed
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPJAVA-25 Here is an overview of the issue: - Key: MPJAVA-25 Summary: Bug in documentation: maven.compile.target property is missed Type: Bug Status: Open Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-java-plugin Assignee: Jason van Zyl Reporter: Alexey Kakunin Created: Mon, 12 Jul 2004 7:25 AM Updated: Mon, 12 Jul 2004 7:25 AM Environment: Maven 1.0 rc4 Description: I found this bug in Java-Plugin web-site. In properties documentation mave.compile.target property is missed. But maven.compile.source property exist twice :) Seems one of them should be renamed to target. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/plugin-parent project.properties
carlos 2004/07/12 02:17:34
Modified:plugin-parent project.properties
Log:
Added repository
Revision ChangesPath
1.7 +10 -0 maven-plugins/plugin-parent/project.properties
Index: project.properties
===
RCS file: /home/cvs/maven-plugins/plugin-parent/project.properties,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- project.properties11 Jul 2004 03:09:50 - 1.6
+++ project.properties12 Jul 2004 09:17:33 - 1.7
@@ -38,3 +38,13 @@
# Changes issue template
maven.changes.issue.template = %URL%/%ISSUE%
+
+# Repository to deploy to
+maven.repo.list=apache
+
+maven.repo.apache=scp://${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=
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (CONTINUUM-5) Add jabber (or IM in general) notifier
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/CONTINUUM-5 Here is an overview of the issue: - Key: CONTINUUM-5 Summary: Add jabber (or IM in general) notifier Type: New Feature Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: continuum Components: continuum-core Assignee: Trygve Laugstol Reporter: Emmanuel Venisse Created: Mon, 12 Jul 2004 4:24 AM Updated: Mon, 12 Jul 2004 4:24 AM Description: For the server, we can use OpenIM. - 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 plugin-profile.xml
evenisse2004/07/12 00:51:23 Modified:.Tag: MAVEN-1_0-BRANCH plugin-profile.xml Log: Update jcoverage plugin version. Revision ChangesPath No revision No revision 1.1.2.4 +1 -1 maven/Attic/plugin-profile.xml Index: plugin-profile.xml === RCS file: /home/cvs/maven/Attic/plugin-profile.xml,v retrieving revision 1.1.2.3 retrieving revision 1.1.2.4 diff -u -r1.1.2.3 -r1.1.2.4 --- plugin-profile.xml11 Jul 2004 03:12:49 - 1.1.2.3 +++ plugin-profile.xml12 Jul 2004 07:51:23 - 1.1.2.4 @@ -81,7 +81,7 @@ - + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jdiff plugin.jelly
dion2004/07/12 00:40:28 Modified:jdiffplugin.jelly Log: Use maven:get rather than pom.getPluginContext Revision ChangesPath 1.13 +1 -2 maven-plugins/jdiff/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven-plugins/jdiff/plugin.jelly,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- plugin.jelly 12 Jul 2004 07:33:07 - 1.12 +++ plugin.jelly 12 Jul 2004 07:40:28 - 1.13 @@ -58,8 +58,7 @@ - + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jdiff/xdocs changes.xml
dion2004/07/12 00:39:16 Modified:jdiff/xdocs changes.xml Log: Add version Revision ChangesPath 1.13 +4 -1 maven-plugins/jdiff/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/jdiff/xdocs/changes.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- changes.xml 18 Jun 2004 11:01:53 - 1.12 +++ changes.xml 12 Jul 2004 07:39:16 - 1.13 @@ -21,10 +21,13 @@ Changes -dIon Gillard +dIon Gillard Emmanuel Venisse + + Add basic homepage. + Add maven-jdiff-plugin:report, maven-jdiff-plugin:register and maven-jdiff-plugin:deregister goals for add jdiff report in site generation. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jdiff project.xml
dion2004/07/12 00:35:33 Modified:jdiffproject.xml Log: Bump version. Remove bad package name Revision ChangesPath 1.33 +1 -2 maven-plugins/jdiff/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/jdiff/project.xml,v retrieving revision 1.32 retrieving revision 1.33 diff -u -r1.32 -r1.33 --- project.xml 25 Jun 2004 15:24:29 - 1.32 +++ project.xml 12 Jul 2004 07:35:33 - 1.33 @@ -20,11 +20,10 @@ ../plugin-parent/project.xml - blah 3 maven-jdiff-plugin Maven JDiff Plugin - 1.4 + 1.4.1-SNAPSHOT Diff between CVS releases http://maven.apache.org/reference/plugins/jdiff/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jdiff plugin.jelly
dion2004/07/12 00:33:07 Modified:jdiffplugin.jelly Log: Little formatting Revision ChangesPath 1.12 +4 -4 maven-plugins/jdiff/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven-plugins/jdiff/plugin.jelly,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- plugin.jelly 16 Jun 2004 08:39:41 - 1.11 +++ plugin.jelly 12 Jul 2004 07:33:07 - 1.12 @@ -159,10 +159,10 @@ - - - - + + + + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jdiff/xdocs index.xml
dion2004/07/12 00:32:31 Added: jdiff/xdocs index.xml Log: Add basic doc index Revision ChangesPath 1.1 maven-plugins/jdiff/xdocs/index.xml Index: index.xml === Maven NSIS Plug-in dIon Gillard This plugin is used to generate an API difference report between two versions of code. DocumentDescription Properties The behavior of this plugin can be altered via several properties. This document describes each property available, and the default used. Goals This plugin provides goals to help in building the installer. This document describes each goal available. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
