[jira] Created: (MPJALOPY-6) Patch of MPJALOPY-5 allows only a single exclude pattern
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPJALOPY-6 Here is an overview of the issue: - Key: MPJALOPY-6 Summary: Patch of MPJALOPY-5 allows only a single exclude pattern Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jalopy-plugin Versions: 1.0 Assignee: Emmanuel Venisse Reporter: Joachim Bader Created: Tue, 24 Aug 2004 3:02 AM Updated: Tue, 24 Aug 2004 3:02 AM Description: The patch provided by MPJALOPY-5 allows only one single exclude pattern. It uses ant:include/exclude ... better is ant:fileset includes=... excludes=... More then one file pattern can excluded from jalopy - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPJALOPY-6) Patch of MPJALOPY-5 allows only a single exclude pattern
The following issue has been updated: Updater: Joachim Bader (mailto:[EMAIL PROTECTED]) Date: Tue, 24 Aug 2004 3:03 AM Comment: allows multiple include/exclude patterns Changes: Attachment changed to patch.diff - For a full history of the issue, see: http://jira.codehaus.org/browse/MPJALOPY-6?page=history - View the issue: http://jira.codehaus.org/browse/MPJALOPY-6 Here is an overview of the issue: - Key: MPJALOPY-6 Summary: Patch of MPJALOPY-5 allows only a single exclude pattern Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jalopy-plugin Versions: 1.0 Assignee: Emmanuel Venisse Reporter: Joachim Bader Created: Tue, 24 Aug 2004 3:02 AM Updated: Tue, 24 Aug 2004 3:03 AM Description: The patch provided by MPJALOPY-5 allows only one single exclude pattern. It uses ant:include/exclude ... better is ant:fileset includes=... excludes=... More then one file pattern can excluded from jalopy - 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: (MPJAVADOC-40) javadoc:jar fails if project doesn't have source files
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-40 Here is an overview of the issue: - Key: MPJAVADOC-40 Summary: javadoc:jar fails if project doesn't have source files Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-javadoc-plugin Versions: 1.6 1.6.1 Assignee: Arnaud HERITIER Reporter: Arnaud HERITIER Created: Tue, 24 Aug 2004 5:17 AM Updated: Tue, 24 Aug 2004 5:17 AM Description: If your project doesn't have source files, javadoc:jar (and goals that depends on it, like javadoc:deploy) fails, even though javadoc itself suceeds. You can reproduce this bug on the maven-plugins root: $ maven javadoc __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-cpqd-1.0.0 BUILD SUCCESSFUL Total time: 26 seconds Finished at: Mon Aug 23 14:53:19 BRT 2004 $ maven javadoc:jar __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-cpqd-1.0.0 build:start: xdoc:init: [mkdir] Created dir: D:\cvs\maven-plugins\target\generated-xdocs [mkdir] Created dir: D:\cvs\maven-plugins\target\docs maven-javadoc-plugin:report: [mkdir] Created dir: D:\cvs\maven-plugins\target\javadoc [mkdir] Created dir: D:\cvs\maven-plugins\target\javadoc\src BUILD FAILED File.. C:\Documents and Settings\t_fl01\.maven\cache\maven-javadoc-plugin-1.7-snapshot-cpqd\plugin.jelly Element... ant:jar Line.. 464 Column 24 D:\cvs\maven-plugins\target\docs\apidocs not found. Total time: 38 seconds Finished at: Mon Aug 23 14:51:35 BRT 2004 It shouldn't be hard to fix this one - I will try a patch once I'm back from my 'break' :-) -- Felipe - 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: [BUG] javadoc:jar fails if project doesn't have source files
Hi Felipe, I succeeded to open an issue: MPJAVADOC-40 Arnaud -Message d'origine- De : Felipe Leme [mailto:[EMAIL PROTECTED] Envoyé : lundi 23 août 2004 20:06 À : Maven Developers List Objet : [BUG] javadoc:jar fails if project doesn't have source files Here is another bug I was going to report (before Jira boicotted me :-): If your project doesn't have source files, javadoc:jar (and goals that depends on it, like javadoc:deploy) fails, even though javadoc itself suceeds. You can reproduce this bug on the maven-plugins root: $ maven javadoc __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-cpqd-1.0.0 BUILD SUCCESSFUL Total time: 26 seconds Finished at: Mon Aug 23 14:53:19 BRT 2004 $ maven javadoc:jar __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-cpqd-1.0.0 build:start: xdoc:init: [mkdir] Created dir: D:\cvs\maven-plugins\target\generated-xdocs [mkdir] Created dir: D:\cvs\maven-plugins\target\docs maven-javadoc-plugin:report: [mkdir] Created dir: D:\cvs\maven-plugins\target\javadoc [mkdir] Created dir: D:\cvs\maven-plugins\target\javadoc\src BUILD FAILED File.. C:\Documents and Settings\t_fl01\.maven\cache\maven-javadoc-plugin-1.7-snapshot-cpqd\plugin.jelly Element... ant:jar Line.. 464 Column 24 D:\cvs\maven-plugins\target\docs\apidocs not found. Total time: 38 seconds Finished at: Mon Aug 23 14:51:35 BRT 2004 It shouldn't be hard to fix this one - I will try a patch once I'm back from my 'break' :-) -- Felipe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] #== gPopper Menu ===# Delete from Gmail inbox: mailto:del|[EMAIL PROTECTED] Mark message as unread:mailto:unr|[EMAIL PROTECTED] Mark message as read: mailto:rea|[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPJALOPY-6) Patch of MPJALOPY-5 allows only a single exclude pattern
Message: The following issue has been closed. Resolver: Emmanuel Venisse Date: Tue, 24 Aug 2004 7:29 AM Applied. Thanks. - View the issue: http://jira.codehaus.org/browse/MPJALOPY-6 Here is an overview of the issue: - Key: MPJALOPY-6 Summary: Patch of MPJALOPY-5 allows only a single exclude pattern Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jalopy-plugin Fix Fors: 1.4 Versions: 1.0 Assignee: Emmanuel Venisse Reporter: Joachim Bader Created: Tue, 24 Aug 2004 3:02 AM Updated: Tue, 24 Aug 2004 7:29 AM Description: The patch provided by MPJALOPY-5 allows only one single exclude pattern. It uses ant:include/exclude ... better is ant:fileset includes=... excludes=... More then one file pattern can excluded from jalopy - 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: (MPJALOPY-1) prereq for java:compile throws off line numbers.
Message: The following issue has been closed. Resolver: Emmanuel Venisse Date: Tue, 24 Aug 2004 7:33 AM Jalopy requires that files compile before format code. - View the issue: http://jira.codehaus.org/browse/MPJALOPY-1 Here is an overview of the issue: - Key: MPJALOPY-1 Summary: prereq for java:compile throws off line numbers. Type: Bug Status: Closed Priority: Major Resolution: WON'T FIX Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jalopy-plugin Assignee: Reporter: Joakim Erdfelt Created: Mon, 10 Nov 2003 7:56 AM Updated: Tue, 24 Aug 2004 7:33 AM Environment: solaris 2.8 / j2sdk 1.4.2_01 / maven 1.0rc1 Description: Why is there a preReq for the maven-jalopy-plugin to perform a 'java:compile' before running jalopy on the source files? I find this annoying when attempting to debug stuff. As the line numbers are all off in this situation. The project I'm working on has many generated source files. The process (in straight ant) that works for us is ... 1) get latest xml definition of old legacy socket protocol. 2) perform xslt transform against legacy.xml to generate optimum java source to read/write against protocol. 3) perform xslt transform against legacy.xml to generate some integration tests for the protocol to ensure that the spec and reality mesh. 3) jalopy the source to make source readable. 4) compile sources. 5) test. Now, if we use the maven with the maven-jalopy-plugin step #4 moves up to between #1 and #2. If we have to debug the code, then the line numbers in the compiled classes do not match the line numbers in the source files. Which is annoying to say the least. Can we either make the java:compile prereq optional or remove it entirely? - 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: (MPJAVADOC-40) javadoc:jar fails if project doesn't have source files
The following comment has been added to this issue:
Author: Felipe Leme
Created: Tue, 24 Aug 2004 7:47 AM
Body:
Hi Arnaud,
Thanks for opening this issue (I couldn't, as Jira was bug).
Anyway, the fix is pretty simple: it's just a matter of callign mkdir before the
j:if statement:
Before it was:
goal name=maven-javadoc-plugin:report
description=Generate API documentation prereqs=xdoc:init
javadoc:init/
j:if test=${internal.javadoc.needed}
ant:mkdir dir=${maven.javadoc.destdir}/
Now it should be:
ant:mkdir dir=${maven.javadoc.destdir}/
j:if test=${internal.javadoc.needed}
I'll provide a patch...
Felipe
-
View this comment:
http://jira.codehaus.org/browse/MPJAVADOC-40?page=comments#action_23377
-
View the issue:
http://jira.codehaus.org/browse/MPJAVADOC-40
Here is an overview of the issue:
-
Key: MPJAVADOC-40
Summary: javadoc:jar fails if project doesn't have source files
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-javadoc-plugin
Versions:
1.6
1.6.1
Assignee: Arnaud HERITIER
Reporter: Arnaud HERITIER
Created: Tue, 24 Aug 2004 5:17 AM
Updated: Tue, 24 Aug 2004 7:47 AM
Description:
If your project doesn't have source files, javadoc:jar (and goals that depends on it,
like javadoc:deploy) fails, even though javadoc itself suceeds.
You can reproduce this bug on the maven-plugins root:
$ maven javadoc
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-cpqd-1.0.0
BUILD SUCCESSFUL
Total time: 26 seconds
Finished at: Mon Aug 23 14:53:19 BRT 2004
$ maven javadoc:jar
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-cpqd-1.0.0
build:start:
xdoc:init:
[mkdir] Created dir: D:\cvs\maven-plugins\target\generated-xdocs
[mkdir] Created dir: D:\cvs\maven-plugins\target\docs
maven-javadoc-plugin:report:
[mkdir] Created dir: D:\cvs\maven-plugins\target\javadoc
[mkdir] Created dir: D:\cvs\maven-plugins\target\javadoc\src
BUILD FAILED
File.. C:\Documents and
Settings\t_fl01\.maven\cache\maven-javadoc-plugin-1.7-snapshot-cpqd\plugin.jelly
Element... ant:jar
Line.. 464
Column 24
D:\cvs\maven-plugins\target\docs\apidocs not found.
Total time: 38 seconds
Finished at: Mon Aug 23 14:51:35 BRT 2004
It shouldn't be hard to fix this one - I will try a patch once I'm back
from my 'break' :-)
-- Felipe
-
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
evenisse2004/08/24 05:02:10 Modified:jira project.xml jira/src/main/org/apache/maven/jira JiraDownloader.java jira/xdocs changes.xml Log: MPJIRA-3. Fix jira downloading url for some jira instance like Apache. Revision ChangesPath 1.12 +1 -1 maven-plugins/jira/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/jira/project.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- project.xml 11 Jul 2004 03:00:12 - 1.11 +++ project.xml 24 Aug 2004 12:02:10 - 1.12 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-jira-plugin/id nameMaven JIRA Plug-in/name - currentVersion1.1.1/currentVersion + currentVersion1.1.2-SNAPSHOT/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 1.3 +1 -1 maven-plugins/jira/src/main/org/apache/maven/jira/JiraDownloader.java Index: JiraDownloader.java === RCS file: /home/cvs/maven-plugins/jira/src/main/org/apache/maven/jira/JiraDownloader.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- JiraDownloader.java 2 Mar 2004 15:07:07 - 1.2 +++ JiraDownloader.java 24 Aug 2004 12:02:10 - 1.3 @@ -112,7 +112,7 @@ int pos = url.indexOf(?); String id = url.substring(pos+4); url = url.substring(0, url.lastIndexOf(/)); -link = url + /secure/IssueNavigator.jspa?view=rsspid= + id + sorter/field=issuekeysorter/order=DESCsorter/field=statussorter/order=DESCtempMax= + String.valueOf(nbEntriesMax) + reset=true; +link = url + /secure/IssueNavigator.jspa?view=rsspid= + id + sorter/field=issuekeysorter/order=DESCsorter/field=statussorter/order=DESCtempMax= + String.valueOf(nbEntriesMax) + reset=truedecorator=none; } } 1.5 +3 -0 maven-plugins/jira/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/jira/xdocs/changes.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- changes.xml 11 Jul 2004 03:00:12 - 1.4 +++ changes.xml 24 Aug 2004 12:02:10 - 1.5 @@ -24,6 +24,9 @@ author email=[EMAIL PROTECTED]Brett Porter/author /properties body +release version=1.1.2 date=In CVS + action dev=evenisse type=fix issue=MPJIRA-3Fix jira downloading url for some jira instance like Apache./action +/release release version=1.1.1 date=2004-07-10 action dev=brett type=updateUpdate commons-httpclient dependency/action /release - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPJIRA-3) The element type link must be terminated by the matching end-tag
Message: The following issue has been closed. Resolver: Emmanuel Venisse Date: Tue, 24 Aug 2004 8:07 AM Applied. Thanks. - 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: Closed Priority: Major Resolution: FIXED 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: Tue, 24 Aug 2004 8:07 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] Closed: (MPJNLP-14) Filenames of dependencies are getting chopped off
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Tue, 24 Aug 2004 8:13 AM
Already fixed.
-
View the issue:
http://jira.codehaus.org/browse/MPJNLP-14
Here is an overview of the issue:
-
Key: MPJNLP-14
Summary: Filenames of dependencies are getting chopped off
Type: Bug
Status: Closed
Priority: Blocker
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-jnlp-plugin
Versions:
1.4
Assignee: Emmanuel Venisse
Reporter: Jeff Campbell
Created: Wed, 14 Jul 2004 3:49 AM
Updated: Tue, 24 Aug 2004 8:13 AM
Environment: WindowsXP
j2sdk 1.4.2_05
Description:
plugin.jelly has a bug where the name of dependencies are getting chopped off
Line 350:
Bug: j:set var=lib.file.signedname value=${lib.final.name}.jar/
Fix: j:set var=lib.file.signedname value=${lib.file.name}.jar/
Reason: ${lib.final.name} is never defined... so the name of the jar is left blank and
you get a file called .jar
-
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: (MPJIRA-4) issueTrackingUrl must contain an id attribute
The following comment has been added to this issue: Author: Emmanuel Venisse Created: Tue, 24 Aug 2004 8:19 AM Body: I don't know how to obtain the xml result with the id (like JS2). And you? - View this comment: http://jira.codehaus.org/browse/MPJIRA-4?page=comments#action_23381 - 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: Tue, 24 Aug 2004 8:19 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] Closed: (MCOMPONENTS-9) Mboot and test failures
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MCOMPONENTS-9 Here is an overview of the issue: - Key: MCOMPONENTS-9 Summary: Mboot and test failures Type: Task Status: Closed Priority: Major Resolution: FIXED Original Estimate: 10 minutes Time Spent: Unknown Remaining: 10 minutes Project: maven-components Components: maven-mboot Assignee: Emmanuel Venisse Reporter: Emmanuel Venisse Created: Wed, 14 Jan 2004 8:31 AM Updated: Tue, 24 Aug 2004 8:20 AM Description: When some tests failed, mboot must stop process. - 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: (MPJAVADOC-40) javadoc:jar fails if project doesn't have source files
The following comment has been added to this issue: Author: Felipe Leme Created: Tue, 24 Aug 2004 8:45 AM Body: Yes, it will. But I think it's better then getting an exception. Anyway, the current behavior is not consistent, as javadoc:generate works. So we either change javadoc:jar to work too or change javadoc:generate to fail as well. Another option would be enclosing the javadoc:install (and others) tags into a util:available tag. That way the jar won't be created and the goal won't fail. Anyway, it's just a matter of style (I, for instance, prefer a empty jar than nothing at all). So, whatever we decide, I can create a patch. Felipe - View this comment: http://jira.codehaus.org/browse/MPJAVADOC-40?page=comments#action_23383 - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-40 Here is an overview of the issue: - Key: MPJAVADOC-40 Summary: javadoc:jar fails if project doesn't have source files Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-javadoc-plugin Versions: 1.6 1.6.1 Assignee: Arnaud HERITIER Reporter: Arnaud HERITIER Created: Tue, 24 Aug 2004 5:17 AM Updated: Tue, 24 Aug 2004 8:45 AM Description: If your project doesn't have source files, javadoc:jar (and goals that depends on it, like javadoc:deploy) fails, even though javadoc itself suceeds. You can reproduce this bug on the maven-plugins root: $ maven javadoc __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-cpqd-1.0.0 BUILD SUCCESSFUL Total time: 26 seconds Finished at: Mon Aug 23 14:53:19 BRT 2004 $ maven javadoc:jar __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-cpqd-1.0.0 build:start: xdoc:init: [mkdir] Created dir: D:\cvs\maven-plugins\target\generated-xdocs [mkdir] Created dir: D:\cvs\maven-plugins\target\docs maven-javadoc-plugin:report: [mkdir] Created dir: D:\cvs\maven-plugins\target\javadoc [mkdir] Created dir: D:\cvs\maven-plugins\target\javadoc\src BUILD FAILED File.. C:\Documents and Settings\t_fl01\.maven\cache\maven-javadoc-plugin-1.7-snapshot-cpqd\plugin.jelly Element... ant:jar Line.. 464 Column 24 D:\cvs\maven-plugins\target\docs\apidocs not found. Total time: 38 seconds Finished at: Mon Aug 23 14:51:35 BRT 2004 It shouldn't be hard to fix this one - I will try a patch once I'm back from my 'break' :-) -- Felipe - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/javadoc plugin.jelly
aheritier2004/08/24 05:57:16
Modified:javadoc plugin.jelly
Log:
temporary fix for MPJAVADOC-40
Revision ChangesPath
1.59 +2 -2 maven-plugins/javadoc/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/javadoc/plugin.jelly,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -r1.58 -r1.59
--- plugin.jelly 21 Aug 2004 23:25:37 - 1.58
+++ plugin.jelly 24 Aug 2004 12:57:16 - 1.59
@@ -245,9 +245,9 @@
javadoc:init/
+ant:mkdir dir=${maven.javadoc.destdir}/
+
j:if test=${internal.javadoc.needed}
-
- ant:mkdir dir=${maven.javadoc.destdir}/
!-- Get the year to display in the Javadocs --
ant:tstamp
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/javadoc/src/plugin-test/test07 - New directory
aheritier2004/08/24 06:02:43 maven-plugins/javadoc/src/plugin-test/test07 - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPJAVADOC-40) javadoc:jar fails if project doesn't have source files
The following comment has been added to this issue: Author: Arnaud HERITIER Created: Tue, 24 Aug 2004 9:05 AM Body: Temporarly I commited the fix with the mkdir before the test. I'll do somethink better with util:available to definitively close this issue. - View this comment: http://jira.codehaus.org/browse/MPJAVADOC-40?page=comments#action_23384 - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-40 Here is an overview of the issue: - Key: MPJAVADOC-40 Summary: javadoc:jar fails if project doesn't have source files Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-javadoc-plugin Versions: 1.6 1.6.1 Assignee: Arnaud HERITIER Reporter: Arnaud HERITIER Created: Tue, 24 Aug 2004 5:17 AM Updated: Tue, 24 Aug 2004 9:05 AM Description: If your project doesn't have source files, javadoc:jar (and goals that depends on it, like javadoc:deploy) fails, even though javadoc itself suceeds. You can reproduce this bug on the maven-plugins root: $ maven javadoc __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-cpqd-1.0.0 BUILD SUCCESSFUL Total time: 26 seconds Finished at: Mon Aug 23 14:53:19 BRT 2004 $ maven javadoc:jar __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-cpqd-1.0.0 build:start: xdoc:init: [mkdir] Created dir: D:\cvs\maven-plugins\target\generated-xdocs [mkdir] Created dir: D:\cvs\maven-plugins\target\docs maven-javadoc-plugin:report: [mkdir] Created dir: D:\cvs\maven-plugins\target\javadoc [mkdir] Created dir: D:\cvs\maven-plugins\target\javadoc\src BUILD FAILED File.. C:\Documents and Settings\t_fl01\.maven\cache\maven-javadoc-plugin-1.7-snapshot-cpqd\plugin.jelly Element... ant:jar Line.. 464 Column 24 D:\cvs\maven-plugins\target\docs\apidocs not found. Total time: 38 seconds Finished at: Mon Aug 23 14:51:35 BRT 2004 It shouldn't be hard to fix this one - I will try a patch once I'm back from my 'break' :-) -- Felipe - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/javadoc/src/plugin-test/test07 .cvsignore maven.xml project.xml
aheritier2004/08/24 06:04:31
Added: javadoc/src/plugin-test/test07 .cvsignore maven.xml
project.xml
Log:
test case for MPJAVADOC-40
Revision ChangesPath
1.1 maven-plugins/javadoc/src/plugin-test/test07/.cvsignore
Index: .cvsignore
===
target
1.1 maven-plugins/javadoc/src/plugin-test/test07/maven.xml
Index: maven.xml
===
!--
/*
* Copyright 2001-2004 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the License);
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an AS IS BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
--
project xmlns:util=jelly:util
xmlns:maven=jelly:maven
xmlns:j=jelly:core
xmlns:assert=assert
xmlns:ant=jelly:ant
goal name=testPlugin
delete dir=${maven.build.dir} failonerror=false/
attainGoal name=javadoc:jar/
/goal
/project
1.1 maven-plugins/javadoc/src/plugin-test/test07/project.xml
Index: project.xml
===
?xml version=1.0 encoding=UTF-8?
!--
/*
* Copyright 2001-2004 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the License);
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an AS IS BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
--
project
pomVersion3/pomVersion
idtest-maven-javadoc-plugin-07/id
nameMPJAVADOC-40/name
groupIdmaven/groupId
currentVersion1.0/currentVersion
organization
nameApache Software Foundation/name
urlhttp://www.apache.org//url
logohttp://maven.apache.org/images/apache-maven-project.png/logo
/organization
inceptionYear2001/inceptionYear
logohttp://maven.apache.org/images/maven.jpg/logo
descriptionMPJAVADOC-40/description
shortDescriptionMPJAVADOC-40/shortDescription
urlhttp://maven.apache.org/reference/plugins/javadoc/index.html/url
siteDirectory/www/maven.apache.org/reference/plugins/javadoc//siteDirectory
repository
connectionscm:cvs:pserver:[EMAIL
PROTECTED]:/home/cvspublic:maven-plugins/javadoc//connection
urlhttp://cvs.apache.org/viewcvs/maven-plugins/javadoc//url
/repository
/project
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPMULTIPROJECT-44) multiproject:site fail if sub-projects has a amp; on POM
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPMULTIPROJECT-44 Here is an overview of the issue: - Key: MPMULTIPROJECT-44 Summary: multiproject:site fail if sub-projects has a amp; on POM Type: Bug Status: Open Priority: Major Original Estimate: 3 hours Time Spent: Unknown Remaining: 3 hours Project: maven-multiproject-plugin Versions: 1.4 Assignee: dion gillard Reporter: Felipe Leme Created: Tue, 24 Aug 2004 9:13 AM Updated: Tue, 24 Aug 2004 9:13 AM Description: If a sub-project has a amp; in its description, multiproject:site fails, even though site:generate works fine on the sub-project: xdoc:jelly-transform: [echo] Generating D:/cvs/maven-plugins/test-multiproject/target/docs/projects-overview.html from D:\cvs\maven-plugins\test-multiproject\target\generated-xdocs\projects-overview.xml BUILD FAILED File.. C:\Documents and Settings\t_fl01\.maven\cache\maven-xdoc-plugin-1.9-snapshot-cpqd\plugin.jelly Element... x:parse Line.. 719 Column 42 Error on line 31 of document file:/D:/cvs/maven-plugins/test-multiproject/target/generated-xdocs/projects-overview.xml: The reference to entity : must end with the ';' delimiter. Nested exception: The reference to entity : must end with the ';' delimiter. Total time: 39 seconds Finished at: Mon Aug 23 10:05:13 BRT 2004 I haven't checked how projects-overview.xml is generated yet, but it is probably applying a XSL on the sub-project POM, and that transformation is replacing amp; for . - 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: (MPMULTIPROJECT-44) multiproject:site fail if sub-projects has a amp; on POM
The following issue has been updated: Updater: Felipe Leme (mailto:[EMAIL PROTECTED]) Date: Tue, 24 Aug 2004 9:16 AM Comment: Simple testcase that shows the issue. Changes: Attachment changed to testcase-MPMULTIPROJECT44.zip - For a full history of the issue, see: http://jira.codehaus.org/browse/MPMULTIPROJECT-44?page=history - View the issue: http://jira.codehaus.org/browse/MPMULTIPROJECT-44 Here is an overview of the issue: - Key: MPMULTIPROJECT-44 Summary: multiproject:site fail if sub-projects has a amp; on POM Type: Bug Status: Open Priority: Major Original Estimate: 3 hours Time Spent: Unknown Remaining: 3 hours Project: maven-multiproject-plugin Versions: 1.4 Assignee: dion gillard Reporter: Felipe Leme Created: Tue, 24 Aug 2004 9:13 AM Updated: Tue, 24 Aug 2004 9:16 AM Description: If a sub-project has a amp; in its description, multiproject:site fails, even though site:generate works fine on the sub-project: xdoc:jelly-transform: [echo] Generating D:/cvs/maven-plugins/test-multiproject/target/docs/projects-overview.html from D:\cvs\maven-plugins\test-multiproject\target\generated-xdocs\projects-overview.xml BUILD FAILED File.. C:\Documents and Settings\t_fl01\.maven\cache\maven-xdoc-plugin-1.9-snapshot-cpqd\plugin.jelly Element... x:parse Line.. 719 Column 42 Error on line 31 of document file:/D:/cvs/maven-plugins/test-multiproject/target/generated-xdocs/projects-overview.xml: The reference to entity : must end with the ';' delimiter. Nested exception: The reference to entity : must end with the ';' delimiter. Total time: 39 seconds Finished at: Mon Aug 23 10:05:13 BRT 2004 I haven't checked how projects-overview.xml is generated yet, but it is probably applying a XSL on the sub-project POM, and that transformation is replacing amp; for . - 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] Felipe Leme as maven plugins committer
Hi committers, I'd like to propose Felipe Leme as a committer on maven-plugins. Felipe has provided patches and test-cases for many Maven plugins (announcement, eclipse, xdoc) as well as maven-related projects (cactus, jelly-tags) and even Maven itself (his first contribution was issue MAVEN-564). He is already a committer for Jakarta Taglibs (as some might have realized in the taglibs repository thread a couple of weeks ago) and contributor to many other Apache projects (Ant, Tomcat, Commons, etc..). Here's my +1 Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Felipe Leme as maven plugins committer
+1 Emmanuel - Original Message - From: Vincent Massol [EMAIL PROTECTED] To: 'Maven Developers List' [EMAIL PROTECTED] Sent: Tuesday, August 24, 2004 3:27 PM Subject: [VOTE] Felipe Leme as maven plugins committer Hi committers, I'd like to propose Felipe Leme as a committer on maven-plugins. Felipe has provided patches and test-cases for many Maven plugins (announcement, eclipse, xdoc) as well as maven-related projects (cactus, jelly-tags) and even Maven itself (his first contribution was issue MAVEN-564). He is already a committer for Jakarta Taglibs (as some might have realized in the taglibs repository thread a couple of weeks ago) and contributor to many other Apache projects (Ant, Tomcat, Commons, etc..). Here's my +1 Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Felipe Leme as maven plugins committer
+1 for me. Arnaud -Message d'origine- De : Vincent Massol [mailto:[EMAIL PROTECTED] Envoyé : mardi 24 août 2004 15:27 À : 'Maven Developers List' Objet : [VOTE] Felipe Leme as maven plugins committer Hi committers, I'd like to propose Felipe Leme as a committer on maven-plugins. Felipe has provided patches and test-cases for many Maven plugins (announcement, eclipse, xdoc) as well as maven-related projects (cactus, jelly-tags) and even Maven itself (his first contribution was issue MAVEN-564). He is already a committer for Jakarta Taglibs (as some might have realized in the taglibs repository thread a couple of weeks ago) and contributor to many other Apache projects (Ant, Tomcat, Commons, etc..). Here's my +1 Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] #== gPopper Menu ===# Delete from Gmail inbox: mailto:del|[EMAIL PROTECTED] Mark message as unread:mailto:unr|[EMAIL PROTECTED] Mark message as read: mailto:rea|[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Felipe Leme as maven plugins committer
+1 On Tue, 24 Aug 2004 15:27:09 +0200, Vincent Massol [EMAIL PROTECTED] wrote: Hi committers, I'd like to propose Felipe Leme as a committer on maven-plugins. Felipe has provided patches and test-cases for many Maven plugins (announcement, eclipse, xdoc) as well as maven-related projects (cactus, jelly-tags) and even Maven itself (his first contribution was issue MAVEN-564). He is already a committer for Jakarta Taglibs (as some might have realized in the taglibs repository thread a couple of weeks ago) and contributor to many other Apache projects (Ant, Tomcat, Commons, etc..). Here's my +1 Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPJIRA-4) issueTrackingUrl must contain an id attribute
The following comment has been added to this issue: Author: Paul Spencer Created: Tue, 24 Aug 2004 12:05 PM Body: I do not know how to know the answer either. The folks at Jira should know the answer. - View this comment: http://jira.codehaus.org/browse/MPJIRA-4?page=comments#action_23391 - 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: Tue, 24 Aug 2004 12:05 PM 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] Created: (MAVENUPLOAD-191) Please upload jasperreports-0.6.0 to ibiblio
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-191 Here is an overview of the issue: - Key: MAVENUPLOAD-191 Summary: Please upload jasperreports-0.6.0 to ibiblio Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Felipe Leme Created: Tue, 24 Aug 2004 1:54 PM Updated: Tue, 24 Aug 2004 1:54 PM Description: I will be attaching a new POM... - 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: (MAVENUPLOAD-191) Please upload jasperreports-0.6.0 to ibiblio
The following issue has been updated: Updater: Felipe Leme (mailto:[EMAIL PROTECTED]) Date: Tue, 24 Aug 2004 1:56 PM Comment: POM Changes: Attachment changed to POM.xml.txt - For a full history of the issue, see: http://jira.codehaus.org/browse/MAVENUPLOAD-191?page=history - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-191 Here is an overview of the issue: - Key: MAVENUPLOAD-191 Summary: Please upload jasperreports-0.6.0 to ibiblio Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Felipe Leme Created: Tue, 24 Aug 2004 1:54 PM Updated: Tue, 24 Aug 2004 1:56 PM Description: I will be attaching a new POM... - 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: (MAVENUPLOAD-191) Please upload jasperreports-0.6.0 to ibiblio
The following issue has been updated: Updater: Felipe Leme (mailto:[EMAIL PROTECTED]) Date: Tue, 24 Aug 2004 2:05 PM Comment: License - JasperReportsLicense Changes: Attachment changed to license.txt - For a full history of the issue, see: http://jira.codehaus.org/browse/MAVENUPLOAD-191?page=history - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-191 Here is an overview of the issue: - Key: MAVENUPLOAD-191 Summary: Please upload jasperreports-0.6.0 to ibiblio Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Felipe Leme Created: Tue, 24 Aug 2004 1:54 PM Updated: Tue, 24 Aug 2004 2:05 PM Description: I will be attaching a new POM... - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-191) Please upload jasperreports-0.6.0 to ibiblio
The following comment has been added to this issue: Author: Carlos Sanchez Created: Tue, 24 Aug 2004 2:12 PM Body: Felipe, you should bundle them all in a jar and put it directly available in a web server - View this comment: http://jira.codehaus.org/browse/MAVENUPLOAD-191?page=comments#action_23396 - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-191 Here is an overview of the issue: - Key: MAVENUPLOAD-191 Summary: Please upload jasperreports-0.6.0 to ibiblio Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Felipe Leme Created: Tue, 24 Aug 2004 1:54 PM Updated: Tue, 24 Aug 2004 2:12 PM Description: I will be attaching a new POM... - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-192) CAS 2.0.12 Upload Request
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-192 Here is an overview of the issue: - Key: MAVENUPLOAD-192 Summary: CAS 2.0.12 Upload Request Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Luke Taylor Created: Tue, 24 Aug 2004 2:19 PM Updated: Tue, 24 Aug 2004 2:19 PM Description: CAS is Yale University ITS's Central Authentication Service: http://www.yale.edu/tp/cas/ It is used by the Acegi Security project for the Spring Framework and we are hoping to move towards using Maven for the main project build. We've been in touch with the project maintainer, Drew Mazurek, to OK the upload with them. Thanks, Luke. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-193) CAS Client Upload Request
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-193 Here is an overview of the issue: - Key: MAVENUPLOAD-193 Summary: CAS Client Upload Request Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Luke Taylor Created: Tue, 24 Aug 2004 2:23 PM Updated: Tue, 24 Aug 2004 2:23 PM Description: This is the client jar for the CAS server (For details, see the upload request http://jira.codehaus.org/browse/MAVENUPLOAD-192). Thanks, Luke. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-191) Please upload jasperreports-0.6.0 to ibiblio
The following comment has been added to this issue: Author: Felipe Leme Created: Tue, 24 Aug 2004 2:27 PM Body: Yes, but I don't have access to any site I could upload the bundle right now :-( Besides, version 0.5.0 was uploaded this way (except that it didn't have a license): http://jira.codehaus.org/browse/MAVENUPLOAD-41 - View this comment: http://jira.codehaus.org/browse/MAVENUPLOAD-191?page=comments#action_23398 - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-191 Here is an overview of the issue: - Key: MAVENUPLOAD-191 Summary: Please upload jasperreports-0.6.0 to ibiblio Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Felipe Leme Created: Tue, 24 Aug 2004 1:54 PM Updated: Tue, 24 Aug 2004 2:27 PM Description: I will be attaching a new POM... - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-191) Please upload jasperreports-0.6.0 to ibiblio
The following comment has been added to this issue: Author: Carlos Sanchez Created: Tue, 24 Aug 2004 2:49 PM Body: you really don't have any? what about your apache account? I'm afraid Jason is very busy (there are lots of pending upload requests) and won't upload it if it's not correct. Last version was uploaded long ago. - View this comment: http://jira.codehaus.org/browse/MAVENUPLOAD-191?page=comments#action_23399 - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-191 Here is an overview of the issue: - Key: MAVENUPLOAD-191 Summary: Please upload jasperreports-0.6.0 to ibiblio Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Felipe Leme Created: Tue, 24 Aug 2004 1:54 PM Updated: Tue, 24 Aug 2004 2:49 PM Description: I will be attaching a new POM... - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-191) Please upload jasperreports-0.6.0 to ibiblio
The following comment has been added to this issue: Author: Felipe Leme Created: Tue, 24 Aug 2004 3:03 PM Body: Ok, I wil provide a bundle later then... - View this comment: http://jira.codehaus.org/browse/MAVENUPLOAD-191?page=comments#action_23402 - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-191 Here is an overview of the issue: - Key: MAVENUPLOAD-191 Summary: Please upload jasperreports-0.6.0 to ibiblio Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Felipe Leme Created: Tue, 24 Aug 2004 1:54 PM Updated: Tue, 24 Aug 2004 3:03 PM Description: I will be attaching a new POM... - 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-1429) Add Joda-Time jar to repo
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1429 Here is an overview of the issue: - Key: MAVEN-1429 Summary: Add Joda-Time jar to repo Type: Task Status: Unassigned Priority: Major Original Estimate: 10 minutes Time Spent: Unknown Remaining: 10 minutes Project: maven Assignee: Reporter: Dan Diephouse Created: Tue, 24 Aug 2004 3:45 PM Updated: Tue, 24 Aug 2004 3:45 PM Description: Can someone add the joda-time jar to the repo? http://sourceforge.net/project/showfiles.php?group_id=97367package_id=104212 Thanks! - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: touchstone tests failing in maven HEAD?
It worked when I last tested it, but it certainly seems to be a bug since I upgraded to jelly HEAD. I'll take a look. If you downgrade your jelly and jexl dependencies to those used on the 1.0 branch it should be ok, but please leave CVS HEAD as is. - Brett Quoting Fabrizio Giustina [EMAIL PROTECTED]: When trying to build maven from HEAD I always end up with the touchstone tests failing... I already tried deleting everything and do a fresh check-out from CVS but the problem is still there. Does anybody else experience the same problem? fabrizio --- maven log --- [exec] touchstone-partner-goal-B: [exec] [echo] checkValue = true [exec] Sto tentando il download di touchstone-SNAPSHOT.jar. [exec] Sto tentando il download di test-SNAPSHOT.war. [exec] Sto tentando il download di touchstone-SNAPSHOT.jar. [exec] Sto tentando il download di test-SNAPSHOT.war. [exec] Starting the reactor... [exec] Our processing order: [exec] Starting the reactor... [exec] Our processing order: [exec] BUILD FAILED [exec] File.. D:\apps\maven\maven\maven.xml [exec] Element... maven:maven [exec] Line.. 67 [exec] Column 7 [exec] Unable to obtain goal [touchstone-tests] -- D:\apps\maven\maven\src\test\touchstone-build\maven.xml:272:13: fail maven.build.failure not set [exec] Total time: 2 minutes 35 seconds - 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] Felipe Leme as maven plugins committer
+1 Quoting Carlos Sanchez [EMAIL PROTECTED]: +1 Carlos -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 24, 2004 3:27 PM To: 'Maven Developers List' Subject: [VOTE] Felipe Leme as maven plugins committer Hi committers, I'd like to propose Felipe Leme as a committer on maven-plugins. Felipe has provided patches and test-cases for many Maven plugins (announcement, eclipse, xdoc) as well as maven-related projects (cactus, jelly-tags) and even Maven itself (his first contribution was issue MAVEN-564). He is already a committer for Jakarta Taglibs (as some might have realized in the taglibs repository thread a couple of weeks ago) and contributor to many other Apache projects (Ant, Tomcat, Commons, etc..). Here's my +1 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]
Repository upload instructions
Hi, Could anyone put in a place where any user can see it a link to http://maven.apache.org/repository-upload.html, there are many incorrect upload requests. I would do it but I have no permissions. 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]
Re: Repository upload instructions
On Tue, 2004-08-24 at 19:27, Carlos Sanchez wrote: Could anyone put in a place where any user can see it a link to http://maven.apache.org/repository-upload.html, there are many incorrect upload requests. Just as a personal note, I knew about that site before asking for before creating MAVENUPLOAD-191 (although I must admit I didn't fully read it :-) I would do it but I have no permissions. That's weird, you should: -bash-2.05b$ ls -l /www/maven.apache.org/repository-upload.html -rw-rw-r-- 1 dion maven 6647 Jul 20 02:08 /www/maven.apache.org/repository-upload.html -bash-2.05b$ id carlos uid=1874(carlos) gid=1874(carlos) groups=1874(carlos), 5000(apcvs), 5027(maven) Regarding your comment that Jason is very busy (which I agree) and there are lots of pending upload requests, I have a suggestion to distribute the burden among the other committers: instead of Jason being responsible for upload each of the requests, we could set a common directory where the committers would copy the files that need to be uploaded (already in the ibiblio's format) then Jason would rsync/scp that directory at once, from time to time. In other worlds, the workflow would be: 1.User opens a jira request (preferably providing a bundle) 2.Random committer assigns the issue to himself and copy the bundle to common place on ASF's NFS 3.Committer updates issue stating it is ready to sync 4.Steps 1-3 repeats at will 5.Jason syncs the bundles and notify the list 6.Each committer close his Jira requests What do you think? Felipe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Felipe Leme as maven plugins committer
+1 -- Trygve On Tue, Aug 24, 2004 at 03:27:09PM +0200, Vincent Massol wrote: Hi committers, I'd like to propose Felipe Leme as a committer on maven-plugins. Felipe has provided patches and test-cases for many Maven plugins (announcement, eclipse, xdoc) as well as maven-related projects (cactus, jelly-tags) and even Maven itself (his first contribution was issue MAVEN-564). He is already a committer for Jakarta Taglibs (as some might have realized in the taglibs repository thread a couple of weeks ago) and contributor to many other Apache projects (Ant, Tomcat, Commons, etc..). Here's my +1 Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] signature.asc Description: Digital signature
[jira] Commented: (MAVENUPLOAD-191) Please upload jasperreports-0.6.0 to ibiblio
The following comment has been added to this issue: Author: Felipe Leme Created: Tue, 24 Aug 2004 9:24 PM Body: Ok, here is the bundle: http://apache.org/~felipeal/jasperreports-0.6.0.zip - View this comment: http://jira.codehaus.org/browse/MAVENUPLOAD-191?page=comments#action_23439 - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-191 Here is an overview of the issue: - Key: MAVENUPLOAD-191 Summary: Please upload jasperreports-0.6.0 to ibiblio Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Felipe Leme Created: Tue, 24 Aug 2004 1:54 PM Updated: Tue, 24 Aug 2004 9:24 PM Description: I will be attaching a new POM... - 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: Repository upload instructions
On Tue, 2004-08-24 at 19:25, Felipe Leme wrote: On Tue, 2004-08-24 at 19:27, Carlos Sanchez wrote: Could anyone put in a place where any user can see it a link to http://maven.apache.org/repository-upload.html, there are many incorrect upload requests. Just as a personal note, I knew about that site before asking for before creating MAVENUPLOAD-191 (although I must admit I didn't fully read it :-) Regarding your comment that Jason is very busy (which I agree) and there are lots of pending upload requests, I have a suggestion to distribute the burden among the other committers: instead of Jason being responsible for upload each of the requests, we could set a common directory where the committers would copy the files that need to be uploaded (already in the ibiblio's format) then Jason would rsync/scp that directory at once, from time to time. In other worlds, the workflow would be: 1.User opens a jira request (preferably providing a bundle) 2.Random committer assigns the issue to himself and copy the bundle to common place on ASF's NFS 3.Committer updates issue stating it is ready to sync 4.Steps 1-3 repeats at will 5.Jason syncs the bundles and notify the list 6.Each committer close his Jira requests What do you think? Sounds good to me! The only change I would see is that the staging area would be on beaver.codehaus.org. I can make accounts for anyone who needs access. I would like it here because this is going to be where the staging area will be when the repo app is up and running. The machine is close to where I live, it is backed up regularly and there are no licensing issues. We can't put (L)GPL stuff in Apache hardware period. Most maven committers have a codehaus account, those that want to do some repo management, just ping me and I'll set you up. Trygve, Brett and I will figure something out on beaver.codehaus.org ASAP and then everyone can pitch in. More help would be wonderful. Felipe - 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]
Re: touchstone tests failing in maven HEAD?
I just ran it again and it worked. Please make sure you do a clean bootstrap. Let me know if you have any more problems. - Brett Quoting Brett Porter [EMAIL PROTECTED]: It worked when I last tested it, but it certainly seems to be a bug since I upgraded to jelly HEAD. I'll take a look. If you downgrade your jelly and jexl dependencies to those used on the 1.0 branch it should be ok, but please leave CVS HEAD as is. - Brett Quoting Fabrizio Giustina [EMAIL PROTECTED]: When trying to build maven from HEAD I always end up with the touchstone tests failing... I already tried deleting everything and do a fresh check-out from CVS but the problem is still there. Does anybody else experience the same problem? fabrizio --- maven log --- [exec] touchstone-partner-goal-B: [exec] [echo] checkValue = true [exec] Sto tentando il download di touchstone-SNAPSHOT.jar. [exec] Sto tentando il download di test-SNAPSHOT.war. [exec] Sto tentando il download di touchstone-SNAPSHOT.jar. [exec] Sto tentando il download di test-SNAPSHOT.war. [exec] Starting the reactor... [exec] Our processing order: [exec] Starting the reactor... [exec] Our processing order: [exec] BUILD FAILED [exec] File.. D:\apps\maven\maven\maven.xml [exec] Element... maven:maven [exec] Line.. 67 [exec] Column 7 [exec] Unable to obtain goal [touchstone-tests] -- D:\apps\maven\maven\src\test\touchstone-build\maven.xml:272:13: fail maven.build.failure not set [exec] Total time: 2 minutes 35 seconds - 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: Repository upload instructions
On Tue, 2004-08-24 at 22:47, Jason van Zyl wrote: issues. We can't put (L)GPL stuff in Apache hardware period. Better remove my bundle then :-( Trygve, Brett and I will figure something out on beaver.codehaus.org ASAP and then everyone can pitch in. More help would be wonderful. Ok, I think the important thing is the new process - where this temporary repo is is irrelevant for now (as the number of committers is small; otherwise, you would have a problem to scale the accounts creation :-) -- Felipe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-191) Please upload jasperreports-0.6.0 to ibiblio
The following comment has been added to this issue: Author: Felipe Leme Created: Tue, 24 Aug 2004 10:09 PM Body: New bundle (as we should not keep GPL software on Apache's sites): http://felipeal.net/tmp/jasperreports-0.6.0.zip - View this comment: http://jira.codehaus.org/browse/MAVENUPLOAD-191?page=comments#action_23443 - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-191 Here is an overview of the issue: - Key: MAVENUPLOAD-191 Summary: Please upload jasperreports-0.6.0 to ibiblio Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Felipe Leme Created: Tue, 24 Aug 2004 1:54 PM Updated: Tue, 24 Aug 2004 10:09 PM Description: I will be attaching a new POM... - 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]
