[jira] Commented: (MAVEN-942) running maven on windows 98
The following comment has been added to this issue: Author: anita kulshreshtha Created: Sun, 22 Feb 2004 12:33 AM Body: EXTERNAL MESSAGE: SUBJECT: Re: [jira] Commented: (MAVEN-942) running maven on windows 98 Hi Brett I did cvs update. I am getting the following error. I have used ant -q . . . [echo] [echo] +--+ [echo] | | [echo] | I N S T A L L I N G T H E P L U G I N S| [echo] | | [echo] +--+ [echo] [exec] com.werken.werkz.NoSuchGoalException: No goal [C:\WINDOWS\.maven] [exec] at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:19 0) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManag er.java:565) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:3 04) [exec] at org.apache.maven.cli.App.doMain(App.java:490) [exec] at org.apache.maven.cli.App.main(App.java:1141) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces sorImpl.java:39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet hodAccessorImpl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) [echo] [echo] +--+ [echo] | | [echo] | T E S T I N G T H E P L U G I N S | [echo] | | .ctrl-c Thanks >> Anita << --- [EMAIL PROTECTED] wrote: - http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-942&page=comments#action_16992 - http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-942 - MAVEN_ENDORSED="-Djava.endorsed.dirs=%JAVA_HOME%\lib\endorsed;%MAVEN_HOME%\lib\endorsed" MAVEN_ENDORSED="%JAVA_HOME%\lib\endorsed;%MAVEN_HOME%\lib\endorsed" - __ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools - View this comment: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-942&page=comments#action_17022 - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-942 Here is an overview of the issue: - Key: MAVEN-942 Summary: running maven on windows 98 Type: Bug Status: Closed Priority: Minor Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Fix Fors: 1.0-rc2 Versions: 1.0-rc1 Assignee: Brett Porter Reporter: anita kulshreshtha Created: Thu, 16 Oct 2003 9:14 PM Updated: Sun, 22 Feb 2004 12:33 AM Environment: windows 98 second edition Description: It appears from maven.bat file that maven intends to support windows 98 based systems. The following changes are needed to make it run on windows 98 second edition -- file maven.bat --- L57 : %MAVEN_COMMAND_COM% /C DIR "%JAVA_HOME%" 2>&1 | %MAVEN_FIND_EXE% /I /C "%JAVA_HOME%" >nul L79 : %MAVEN_COMMAND_COM% /C DIR "%MAVEN_HOME%" 2>&1 | %MAVEN_FIND_EXE% /I /C "%MAVEN_HOME%" >nul L57 and L79 give "Too many parameters -2" error on windows 98. These will have to be rewritten. L125 : SET MAVEN_ENDORSED="-Djava.endorsed.dirs=%JAVA_HOME%\lib\endorsed;%MAVEN_HOME%\lib\endorsed" On windows 98 SET ... = "...=..." gives Syntax error. The following changes work - 1. change L125 to -- SET MAVEN_ENDORSED="%JAVA_HOME%\lib\endorsed;%MAVEN_HOME%\lib\endorsed" 2. Replace %MAVEN_ENDORSED% by -Djava.endorsed.dirs=%MAVEN_ENDORSED% in lines L129, L130, L135 and L136. 3. SystemRoot is not defined. It should be mentioned along with MAVEN_HOME and JAVA_HOME. - JIRA INFORMATION: This message is automatically generated by JIRA. If you thin
[jira] Closed: (MAVEN-1128) Jelly tag "maven" in taglib "jelly:maven" fails on second invocation.
Message: The following issue has been closed. Resolver: Brett Porter Date: Sat, 21 Feb 2004 8:05 PM fixed in RC2 - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1128 Here is an overview of the issue: - Key: MAVEN-1128 Summary: Jelly tag "maven" in taglib "jelly:maven" fails on second invocation. Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: jelly/ant integration Fix Fors: 1.0-rc2 Versions: 1.0-rc1 Assignee: Reporter: Jan-Helge Bergesen Created: Fri, 23 Jan 2004 6:42 AM Updated: Sat, 21 Feb 2004 8:05 PM Environment: Windows 2000, Java 1.4.2_01-b06 Description: The second call to a "" Jelly tag results in the following failure. Workaround is to use Ant tag . - com.werken.werkz.UnattainableGoalException: Unable to obtain goal [dev_jar] -- file:/D:/jhb_sn_main_view/sw/java/common/:119:37: Go al [java:compile] has no action definition. at com.werken.werkz.Goal.fire(Goal.java:646) at com.werken.werkz.Goal.attain(Goal.java:575) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:448) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:360) at org.apache.maven.jelly.tags.maven.MavenTag.doTag(MavenTag.java:120) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:128) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:448) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:348) at org.apache.maven.cli.App.doMain(App.java:543) at org.apache.maven.cli.App.main(App.java:1109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) org.apache.commons.jelly.JellyTagException: file:/D:/jhb_sn_main_view/sw/java/common/:119:37: Goal [java:compile] has no action def inition. at com.werken.werkz.jelly.AttainGoalTag.doTag(AttainGoalTag.java:159) at org.apache.maven.jelly.tags.werkz.LazyAttainGoalTag.doTag(LazyAttainGoalTag.java:107) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:128) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:448) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:360) at org.apache.maven.jelly.tags.maven.MavenTag.doTag(MavenTag.java:120) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:128) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:448) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:348) at org.apache.maven.cli.App.doMain(App.java:543) at org.apache.maven.cli.App.main(App.java:1109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: com.werken.werkz.NoActionDefinitionException: Goal [java:compile] has no action definition. at com.werken.werkz.Goal.fire(Goal.ja
cvs commit: maven-plugins/jdee project.xml
brett 2004/02/21 16:58:14 Modified:appserver project.xml docbook project.xml docbook/xdocs changes.xml jdee project.xml Log: consistency Revision ChangesPath 1.21 +1 -1 maven-plugins/appserver/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/appserver/project.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- project.xml 10 Feb 2004 12:49:42 - 1.20 +++ project.xml 22 Feb 2004 00:58:14 - 1.21 @@ -5,7 +5,7 @@ 3 maven-appserver-plugin Maven Appserver Plugin - 2.0-dev + 2.0-SNAPSHOT A Maven plugin that can be used to install and control a J2EE application server instance. http://maven.apache.org/reference/plugins/appserver/ 1.24 +1 -1 maven-plugins/docbook/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/docbook/project.xml,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- project.xml 10 Feb 2004 12:49:43 - 1.23 +++ project.xml 22 Feb 2004 00:58:14 - 1.24 @@ -5,7 +5,7 @@ 3 maven-docbook-plugin Maven DocBook Plug-in - 1.1 + 1.2-SNAPSHOT Convert docbook to xdoc http://maven.apache.org/reference/plugins/docbook/ /www/maven.apache.org/reference/plugins/docbook/ 1.10 +1 -1 maven-plugins/docbook/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/docbook/xdocs/changes.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- changes.xml 15 Jan 2004 14:25:44 - 1.9 +++ changes.xml 22 Feb 2004 00:58:14 - 1.10 @@ -6,7 +6,7 @@ - + added functionality to generate pdfs from docbook (ala hibernate documentation) 1.7 +1 -1 maven-plugins/jdee/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/jdee/project.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- project.xml 10 Oct 2003 19:21:01 - 1.6 +++ project.xml 22 Feb 2004 00:58:14 - 1.7 @@ -5,7 +5,7 @@ 3 maven-jdee-plugin Maven JDEE Plug-in - 1.0-beta-1 + 1.0-SNAPSHOT A plugin to create a project file to be used within the
cvs commit: maven-plugins/tjdo/xdocs changes.xml
brett 2004/02/21 16:55:02 Modified:tjdo/xdocs changes.xml Log: consistency Revision ChangesPath 1.6 +1 -1 maven-plugins/tjdo/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/tjdo/xdocs/changes.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- changes.xml 10 Nov 2003 19:29:40 - 1.5 +++ changes.xml 22 Feb 2004 00:55:02 - 1.6 @@ -7,7 +7,7 @@ - + Addition of "drop-tables", and revision of jelly code. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-1131) JAR - Test dependency change
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 8:00 PM Changes: Version changed to 1.0-rc2 Version changed from 1.1 Fix Version changed to 1.1 - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1131&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1131 Here is an overview of the issue: - Key: MAVEN-1131 Summary: JAR - Test dependency change Type: Improvement Status: Reopened Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Fix Fors: 1.1 Versions: 1.0-rc2 Assignee: Reporter: Andy Jefferson Created: Sat, 24 Jan 2004 3:18 AM Updated: Sat, 21 Feb 2004 8:00 PM Description: The current "jar" plugin has a prerequisite "test". In certain circumstances this is undesirable. For example if the system wants to use the JAR that they will release in testing. At the moment it insists on running tests even though the JAR is not built. It is necessary desirable to have this configurable. - 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/struts project.xml
brett 2004/02/21 16:51:11 Modified:struts project.xml Log: WIP version Revision ChangesPath 1.32 +1 -1 maven-plugins/struts/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/struts/project.xml,v retrieving revision 1.31 retrieving revision 1.32 diff -u -r1.31 -r1.32 --- project.xml 5 Jan 2004 09:57:30 - 1.31 +++ project.xml 22 Feb 2004 00:51:11 - 1.32 @@ -5,7 +5,7 @@ 3 maven-struts-plugin Maven Struts Plugin - 1.2 + 1.3-SNAPSHOT Work with struts jars http://maven.apache.org/reference/plugins/struts/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-1135) maven site fails due to problems with maven-license-plugin
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 7:55 PM Changes: Fix Version changed to 1.0-rc2 - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1135&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1135 Here is an overview of the issue: - Key: MAVEN-1135 Summary: maven site fails due to problems with maven-license-plugin Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Fix Fors: 1.0-rc2 Versions: 1.0-rc1 Assignee: Reporter: Marco Tedone Created: Mon, 26 Jan 2004 6:18 PM Updated: Sat, 21 Feb 2004 7:55 PM Environment: Windows XP SP1 Description: Hi, if I run the "site" goal with no reports description or with the maven-license-plugin report, I obtain an error due to the maven-license-plugin:register goal that is not found by the maven-xdoc-plugin. Here follows the debugged version of my build process: PI Specification, java.class.version=48.0, java.util.prefs.PreferencesFactory=java.util.prefs.WindowsPreferencesFac tory, os.version=5.1, user.home=C:\Documents and Settings\mtedone, user.timezone=Europe/London, java.awt.printerjob =sun.awt.windows.WPrinterJob, file.encoding=Cp1252, java.specification.version=1.4, user.name=mtedone, java.class.p ath=d:\Program Files\Apache Software Foundation\Maven 1.0-rc1\lib\forehead-1.0-beta-5.jar, java.vm.specification.ve rsion=1.0, sun.arch.data.model=32, java.home=D:\J2SE\jre, java.specification.vendor=Sun Microsystems Inc., user.lan guage=en, awt.toolkit=sun.awt.windows.WToolkit, java.vm.info=mixed mode, java.version=1.4.2, java.ext.dirs=D:\J2SE\ jre\lib\ext, sun.boot.class.path=d:\Program Files\Apache Software Foundation\Maven 1.0-rc1\lib\endorsed\xerces-2.4. 0.jar;d:\Program Files\Apache Software Foundation\Maven 1.0-rc1\lib\endorsed\xml-apis-1.0.b2.jar;D:\J2SE\jre\lib\rt .jar;D:\J2SE\jre\lib\i18n.jar;D:\J2SE\jre\lib\sunrsasign.jar;D:\J2SE\jre\lib\jsse.jar;D:\J2SE\jre\lib\jce.jar;D:\J2 SE\jre\lib\charsets.jar;D:\J2SE\jre\classes, java.vendor=Sun Microsystems Inc., javax.xml.parsers.DocumentBuilderFa ctory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl, maven.home=d:\Program Files\Apache Software Foundation\Mav en 1.0-rc1, file.separator=\, java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi, sun.cpu.endian=little, sun.io.unicode.encoding=UnicodeLittle, sun.cpu.isalist=pentium i486 i386} [junit] [VERBOSE] Implicitly adding C:\Documents and Settings\mtedone\.maven\repository\junit\jars\junit-3.8.1. jar;d:\Program Files\Apache Software Foundation\Maven 1.0-rc1\lib\ant-1.5.3-1.jar;d:\Program Files\Apache Software Foundation\Maven 1.0-rc1\lib\ant-optional-1.5.3-1.jar to CLASSPATH [junit] [VERBOSE] Using CLASSPATH D:\Projects\jemos-logging\src\target\test-classes;D:\Projects\jemos-logging\s rc\target\classes;C:\Documents and Settings\mtedone\.maven\repository\junit\jars\junit-3.8.1.jar;D:\Program Files\A pache Software Foundation\Maven 1.0-rc1\lib\ant-1.5.3-1.jar;D:\Program Files\Apache Software Foundation\Maven 1.0-r c1\lib\ant-optional-1.5.3-1.jar [junit] [DEBUG] Finding class org.jemos.logging.test.JemosLoggerTestCase [junit] [DEBUG] Finding class org.jemos.logging.test.JemosAbstractTest [junit] [DEBUG] Class junit.framework.TestCase loaded from parent loader [junit] [DEBUG] Finding class org.jemos.logging.LoggerConfig [junit] [DEBUG] Class java.lang.Object loaded from parent loader [junit] [DEBUG] Class org.jemos.logging.LoggerConfig loaded from ant loader [junit] [DEBUG] Class org.jemos.logging.test.JemosAbstractTest loaded from ant loader [junit] [DEBUG] Class org.jemos.logging.test.JemosLoggerTestCase loaded from ant loader [junit] [DEBUG] Class java.io.InputStream loaded from parent loader [junit] [DEBUG] Class java.io.FileInputStream loaded from parent loader [junit] [DEBUG] Finding class org.jemos.logging.AbstractFactory [junit] [DEBUG] Class org.jemos.logging.AbstractFactory loaded from ant loader [junit] [DEBUG] Finding class org.jemos.logging.JemosLoggerFactory [junit] [DEBUG] Class org.jemos.logging.JemosLoggerFactory loaded from ant loader [junit] [DEBUG] Class java.lang.SecurityException loaded from parent loader [junit] [DEBUG] Class java.io.IOException loaded from parent loader [junit] [DEBUG] Class java.io.FileNotFoundException loaded from parent loader [junit] [DEBUG] Class java.lang.String loaded from parent loader [junit] [DEBUG] Class java.util.logging.Lo
[jira] Updated: (MAVEN-1125) ant:java fork issues
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 7:52 PM Changes: Version changed to 1.0-rc2 Version changed from 1.0-final Fix Version changed to 1.1 - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1125&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1125 Here is an overview of the issue: - Key: MAVEN-1125 Summary: ant:java fork issues Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Fix Fors: 1.1 Versions: 1.0-rc2 Assignee: Reporter: Andy Jefferson Created: Thu, 22 Jan 2004 10:33 AM Updated: Sat, 21 Feb 2004 7:52 PM Environment: Linux, JDK1.4.2 Description: I have a Java app that I want to invoke via Maven. The Java app uses stdin and stdout. If I invoke using ant:java using "fork=true" then stdin doesn not respond correctly. That is, the app prompts, but the user can type to their hearts content and nothing reaches the app. If I invoke using ant:java using "fork=false" then I get strange XML related errors about unresolved references org/w3c/dom/Node, org/w3c/dom/Document - 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: (MAVEN-1155) plugin 'lists" link for dev list is bad
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 7:46 PM Changes: Fix Version changed to 1.0-final - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1155&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1155 Here is an overview of the issue: - Key: MAVEN-1155 Summary: plugin 'lists" link for dev list is bad Type: Bug Status: Unassigned Priority: Trivial Original Estimate: 3 minutes Time Spent: Unknown Remaining: 3 minutes Project: maven Fix Fors: 1.0-final Assignee: Reporter: Chad McHenry Created: Sun, 8 Feb 2004 12:31 PM Updated: Sat, 21 Feb 2004 7:46 PM Description: The link to [EMAIL PROTECTED] has a spurious trailing '/' - 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: (MAVEN-1124) Add exit to maven.bat
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 7:45 PM Changes: Fix Version changed to 1.0-final - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1124&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1124 Here is an overview of the issue: - Key: MAVEN-1124 Summary: Add exit to maven.bat Type: Improvement Status: Unassigned Priority: Trivial Original Estimate: 1 minute Time Spent: Unknown Remaining: 1 minute Project: maven Components: core Fix Fors: 1.0-final Assignee: Reporter: Ronald Blaschke Created: Thu, 22 Jan 2004 5:59 AM Updated: Sat, 21 Feb 2004 7:45 PM Environment: Windows (XP) Description: Windows (XP) seems to not propagate the last ERRORLEVEL in batch files. Thus, when calling maven.bat from an ant build file, ant reports success, even when maven fails. ... 1 error 2 warnings BUILD FAILED Total time: 6 seconds Finished at: Thu Jan 22 11:49:10 CET 2004 File.. file:/C:/Documents and Settings/user/.maven/plugins/maven-test-plugin-1 .4/ Element... javac Line.. 34 Column 46 Compile failed; see the compiler error output for details. BUILD SUCCESSFUL Total time: 8 seconds - 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: (MAVEN-1129) Maven uses sun.* classes directly to access Base64 codec
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Sat, 21 Feb 2004 7:45 PM
Changes:
Fix Version changed to 1.0-final
-
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1129&page=history
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1129
Here is an overview of the issue:
-
Key: MAVEN-1129
Summary: Maven uses sun.* classes directly to access Base64 codec
Type: Bug
Status: Unassigned
Priority: Blocker
Original Estimate: 1 hour
Time Spent: Unknown
Remaining: 1 hour
Project: maven
Fix Fors:
1.0-final
Assignee:
Reporter: Dalibor Topic
Created: Fri, 23 Jan 2004 10:36 AM
Updated: Sat, 21 Feb 2004 7:45 PM
Environment: Building Maven CVS HEAD, on a free runtime (Kaffe, CVS HEAD) with Maven
1.0-rc1.
Description:
Code in src/java/org/apache/maven/util/HttpUtils.java uses a 'forbidden' class in
sun.* package hierarchy directly to access a Base64 encoder. Instead, it should use
Jakarta's own commons-codec package.
The patch below adds a dependency to commons-codec (1.1, because 1.2 is not on
ibiblio.org/maven yet), and fixes the code to use jakarta's own portable implementaion.
With this patch, using kaffe from CVS [1] and a slighlty patched maven 1.0-rc1 [2], I
can build maven's CVS HEAD using
MAVEN_OPTS=-Dbuild.compiler=kjc maven jars
and run maven's tests just fine (except for the online tests, but that seems to be an
unrelated issue).
This bug is filed as blocker, because it blocks development of maven on free runtimes
using free tools.
Given that free runtimes are starting to become suitable for a lot of tasks, it would
be nice to make developers of free java software take a notice and work with us to
make the free runtimes an equivalently suitable (or preferably better ;) choice for
development of free java software as non-free runtimes.
Index: project.xml
===
RCS file: /home/cvspublic/maven/project.xml,v
retrieving revision 1.327
diff -u -r1.327 project.xml
--- project.xml 28 Dec 2003 23:04:13 - 1.327
+++ project.xml 22 Jan 2004 17:48:12 -
@@ -431,6 +431,11 @@
1.4.1
http://jakarta.apache.org/commons/digester.html
+
+ commons-codec
+ 1.1
+ http://jakarta.apache.org/commons/codec/
+
commons-jelly
Index: src/java/org/apache/maven/util/HttpUtils.java
===
RCS file: /home/cvspublic/maven/src/java/org/apache/maven/util/HttpUtils.java,v
retrieving revision 1.28
diff -u -r1.28 HttpUtils.java
--- src/java/org/apache/maven/util/HttpUtils.java 27 Oct 2003 16:33:11 -
1.28
+++ src/java/org/apache/maven/util/HttpUtils.java 22 Jan 2004 17:48:12 -
@@ -67,6 +67,9 @@
import java.net.URL;
import java.net.URLConnection;
+import org.apache.commons.codec.BinaryEncoder;
+import org.apache.commons.codec.binary.Base64;
+
/**
* Http utils for retrieving files.
*
@@ -238,14 +241,9 @@
{
String up = username + ":" + password;
String encoding = null;
-// check to see if sun's Base64 encoder is available.
-try
-{
-sun.misc.BASE64Encoder encoder =
-(sun.misc.BASE64Encoder) Class.forName(
-"sun.misc.BASE64Encoder" ).newInstance();
-
-encoding = encoder.encode( up.getBytes() );
+ try {
+BinaryEncoder encoder = new Base64();
+encoding = new String( encoder.encode( up.getBytes() ) );
}
catch ( Exception ex )
{
@@ -405,4 +403,4 @@
file.setLastModified( modifiedTime );
return true;
}
-}
\ No newline at end of file
+}
thanks a lot for taking your time to encourage me to post this fix.
cheers,
dalibor topic
[1] http://www.kaffe.org/anoncvs.shtml
[2] You need to remove tools.jar entries from forehead.conf. Free runtimes are not
allowed to ship Sun's java compiler, so a direct dependency on tools.jar is pointless
in their case, and the lack of a tools.jar in kaffe needlessly causes forehead to
abort. Instead, you should let ant sort out the compiler. Ant works fine with jikes,
and kaffe's java compiler, with an appropriate build.compiler option.
Of course, you also need to set JAVA_HOME to where you installed kaffe from CVS HEAD ;)
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the a
[jira] Updated: (MAVEN-1127) decouple artifact type implementations from maven core
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 7:37 PM Changes: Fix Version changed to 1.1 - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1127&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1127 Here is an overview of the issue: - Key: MAVEN-1127 Summary: decouple artifact type implementations from maven core Type: New Feature Status: Unassigned Priority: Major Original Estimate: 6 hours Time Spent: Unknown Remaining: 6 hours Project: maven Components: core Fix Fors: 1.1 Versions: 1.1 Assignee: Reporter: John Casey Created: Thu, 22 Jan 2004 2:22 PM Updated: Sat, 21 Feb 2004 7:37 PM Environment: all Description: This is a copy of the proposal email I send to the dev list (http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=13740): While I find the plugin architecture of maven to be fantastic, I have run into a somewhat serious barrier to my own plugin development efforts: adding support for new artifacts requires some pretty significant changes to the maven core, and results in a requirement that I maintain a patch for each artifact type. The Problem The concept of artifact types is intimately coupled with the rest of the maven core implementation. There seems to be no real compelling reason for this; each artifact type has a base set of operations which can be performed against it (with high overlap between types: install, install-snapshot, deploy, deploy-snapshot), and one or more plugins which are the primary producers/consumers of it. While I would agree that certain artifact types are fundamental to maven operation, it can also be stated that certain plugins are similarly fundamental. Therefore, for these plugins, the concept of decoupling via plugin architecture is flawed. In order to change the plugin in any significant way, a change to the maven core may be required to support changes to the artifact type. In addition, this inherently limits plugin development by giving a hard-and-fast set of artifact types which can be manipulated by maven. The Solution --- Simply put, decouple artifact type implementations from the maven core. Instead of having a concrete implementation specifying attributes about a .jar, EJB, or .pom, factor out the common behavior (aforementioned permutations of install and deploy) into an interface, called ArtifactTypeHandler. Then, create concrete implementations of this interface for each type. Finally, add a new dynamic type handler loader (factory class) which will do the following: 1. Pull the typename attribute from a dependency, or otherwise arrive at the artifact type desired. 2. Read the classpath resource META-INF/artifactTypes/typename; line 1 of this file specifies the fully-qualified class name for the type handler. 3. Instantiate this handler class, and return it as the implementation to use in manipulating this artifact. This is a variation on the JAR service discovery method specified in the JDK1.3, and allows each _plugin_ to add an artifact type handler for its own use. Unrecognized artifact types (i.e. the handler jar is not in the classpath, and therefore the META-INF/artifactTypes/typename resource is not present) can be ignored or throw an exception. Justification Under this new architecture, the only artifact-related code in maven-core is the ArtifactTypeHandlerFactory and the abstract [interface] ArtifactTypeHandler. This frees maven up to be a general build tool, agnostic of what type of artifacts it is handling. DLL's, C headers, configuration files, etc. are all perfectly usable within the maven repository scheme. Maven is only limited by the plugins available for it at this point, and plugin development is not limited by the release cycle for maven-core. I can produce a patch against maven to accomplish this, if there is adequate interest... - 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: (MAVEN-1163) mark remote repo with failed (not 404) download as unavailable
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 7:37 PM Changes: Fix Version changed to 1.1 - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1163&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1163 Here is an overview of the issue: - Key: MAVEN-1163 Summary: mark remote repo with failed (not 404) download as unavailable Type: Improvement Status: Unassigned Priority: Minor Original Estimate: 2 hours Time Spent: Unknown Remaining: 2 hours Project: maven Components: core Fix Fors: 1.1 Versions: 1.0-rc2 Assignee: Reporter: John Casey Created: Mon, 16 Feb 2004 10:20 PM Updated: Sat, 21 Feb 2004 7:37 PM Environment: all Description: Currently, when you have multiple repo's, maven will always try each repo in order for each dependency it attempts to download. This is not optimal behavior, and can easily be improved by marking sites as unavailable upon the first failed dependency download. This "marking" would only persist for the duration of the build, and would save the [useless] retry of that site for successive dependencies. Obviously, we wouldn't want to trigger the unavailable flag for 404's and the like... - 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: (MAVEN-1133) Add an instant messaging adress tag for developpers
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 7:37 PM Changes: Fix Version changed to 1.1 - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1133&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1133 Here is an overview of the issue: - Key: MAVEN-1133 Summary: Add an instant messaging adress tag for developpers Type: New Feature Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: model additions Fix Fors: 1.1 Versions: 1.0-final Assignee: Reporter: Emmanuel Venisse Created: Mon, 26 Jan 2004 4:54 AM Updated: Sat, 21 Feb 2004 7:37 PM Description: For continuum, and project team page, I think it's a good idea to have an IM tag for send automatically message when continuum run build. It's a necessary feature for project create in a business entity. - 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: (MAVEN-1169) Maven isn't able to dowload an artifact of type distribution
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 7:37 PM Changes: Fix Version changed to 1.1 - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1169&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1169 Here is an overview of the issue: - Key: MAVEN-1169 Summary: Maven isn't able to dowload an artifact of type distribution Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Fix Fors: 1.1 Versions: 1.0-rc1 1.0-rc2 Assignee: Reporter: Jason Chaffee Created: Fri, 20 Feb 2004 4:05 PM Updated: Sat, 21 Feb 2004 7:37 PM Description: Currently, the maven dist plugin creates files with extensions .zip and .tar.gz and places them in the repository as type distribution. Also, you may have the extension .bin under the type distribution. Maven sets up special cases for plugin, ejb, and aspect types in the ArtifactType class and maps the type to an extension different then from the type. This won't work for distributions because there are at least 3 different extensions for the distribution type. Maven needs to either needs to have a way to handle this special case and be able to download all the possible extensions. - 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: (MAVEN-1160) Need a place for user only plugins outside of maven home
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Sat, 21 Feb 2004 7:37 PM
Changes:
Fix Version changed to 1.1
-
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1160&page=history
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1160
Here is an overview of the issue:
-
Key: MAVEN-1160
Summary: Need a place for user only plugins outside of maven home
Type: New Feature
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Fix Fors:
1.1
Assignee: Brett Porter
Reporter: dion gillard
Created: Wed, 11 Feb 2004 8:25 PM
Updated: Sat, 21 Feb 2004 7:37 PM
Environment: Any
Description:
Currently all plugins are installed in ${maven.home}/plugins.
This doesn't scale for:
- installations which use plugins other than those provided by Maven.
At each install of maven, plugins must be copied over manually to
maven home. Bootstrapping makes this worse as it arbitrarily removes
the maven home directory.
Currently RC2 expands plugins found in ${user.home}/.maven/plugins though this may not
be intentional and is not documented.
-
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: (MAVEN-1145) Per-plugin adjustable log4j settings
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 7:37 PM Changes: Fix Version changed to 1.1 - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1145&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1145 Here is an overview of the issue: - Key: MAVEN-1145 Summary: Per-plugin adjustable log4j settings Type: Improvement Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin manager Fix Fors: 1.1 Assignee: Reporter: Brian Topping Created: Mon, 2 Feb 2004 11:46 PM Updated: Sat, 21 Feb 2004 7:37 PM Description: It should be up to the plugin what log4j settings are used when the plugin is executed. In this manner, a plugin could bundle two different log4j configurations -- one for when the plugin was being operated normally, and the other for debug (-X) mode. If there is no bundled configuration, the current settings would be used. This would be useful with the XDoclet plugin, because either it uses nonstandard settings, or the settings that Maven chooses for it are insufficient for error messages (which may be posted as warnings) to reach the console. When this happens, generation problems are silently lost and the root cause can be very difficult to track down. - 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: (MAVEN-1139) global configuration file for maven
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 7:37 PM Changes: Fix Version changed to 1.1 - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1139&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1139 Here is an overview of the issue: - Key: MAVEN-1139 Summary: global configuration file for maven Type: Improvement Status: Reopened Priority: Trivial Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Fix Fors: 1.1 Versions: 1.0-rc1 Assignee: Reporter: Jean-Frederic Clere Created: Wed, 28 Jan 2004 6:26 AM Updated: Sat, 21 Feb 2004 7:37 PM Environment: UNIX Description: It will be nice to have the following in bin/maven: +++ # load system-wide maven configuration if [ -f "/etc/maven.conf" ] ; then . /etc/maven.conf fi +++ Like it is in ant. - 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: (MAVEN-1152) Unable to authenticate against proxy server
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Sat, 21 Feb 2004 7:37 PM
Changes:
Fix Version changed to 1.1
-
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1152&page=history
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1152
Here is an overview of the issue:
-
Key: MAVEN-1152
Summary: Unable to authenticate against proxy server
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Fix Fors:
1.1
Versions:
1.0-rc1
Assignee:
Reporter: Kristopher Brown
Created: Fri, 6 Feb 2004 4:54 AM
Updated: Sat, 21 Feb 2004 7:37 PM
Environment: WinXP dev machine, MS ISA Server (Proxy Server) requiring domain
authentication.
Tested under java 1.3.1_07 and 1.4.1_02
Description:
Supplying the proxy host, port, username and password in the build.properties file as
specified in the documentation still failed to get through the proxy server where I
work.
HttpUtils sets the default Authenticator as I'd expect to handle such authentication
challenges, however, I added a line of logging to the getPasswordAuthentication()
method and noticed that is was not being called under our environment. Why this is
the case, I cannot honestly say - however, I have noticed that a few articles on the
web mention how people could not get Authenticator to work.
Reading further, a few sites recommended that the "Proxy-Authentication" header is
used, and I noticed that the "Authentication" header is already being used in
HttpUtils (presumably for pre java 1.2 support). Adding similar handling for
"Proxy-Authentication" header allowed maven to successfully connect through our proxy
server.
I've provided a patch below for this, should it be decided its a reasonable addition.
PATCH START
Index: HttpUtils.java
===
RCS file: /home/cvspublic/maven/src/java/org/apache/maven/util/HttpUtils.java,v
retrieving revision 1.28
diff -c -r1.28 HttpUtils.java
*** HttpUtils.java 27 Oct 2003 16:33:11 - 1.28
--- HttpUtils.java 6 Feb 2004 09:48:46 -
***
*** 284,289
--- 284,312
throw new Exception( "Not authorized." );
}
}
+ // add proxy authentication header if required
+ if ( proxyUserName != null || proxyPassword != null )
+ {
+ String up = proxyUserName + ":"
+ + (proxyPassword == null ? "" : proxyPassword);
+ String encoding = null;
+ // check to see if sun's Base64 encoder is available.
+ try
+ {
+ sun.misc.BASE64Encoder encoder =
+ (sun.misc.BASE64Encoder) Class.forName(
+ "sun.misc.BASE64Encoder" ).newInstance();
+
+ encoding = encoder.encode( up.getBytes() );
+ }
+ catch ( Exception ex )
+ {
+ // Do nothing, as for MavenSession we will never use
+ // auth and we will eventually move over httpclient
+ // in the commons.
+ }
+ connection.setRequestProperty( "Proxy-Authorization", "Basic " +
encoding );
+ }
// REVISIT: at this point even non HTTP connections may support the
// if-modified-since behaviour - we just check the date of the
- PATCH END -
-
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: (MAVEN-1147) tag should be able to inherit at least a subset of variables.
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 7:08 PM Changes: Fix Version changed to 1.1 - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1147&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1147 Here is an overview of the issue: - Key: MAVEN-1147 Summary: tag should be able to inherit at least a subset of variables. Type: Improvement Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: jelly/ant integration Fix Fors: 1.1 Versions: 1.0-rc1 Assignee: Reporter: Jan-Helge Bergesen Created: Tue, 3 Feb 2004 4:43 AM Updated: Sat, 21 Feb 2004 7:08 PM Environment: Windows 2000, J2SDK 1.4.2 Description: The maven:maven jelly tag should be able to inherit at least a subset of the invoker's environment in order to do controlled override of properties set in build/project properties. Either by using something like or by context or hierarchial naming convention of properties, ie: my.prop1=a my.prop2=b your.prop1=c ... - 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: (MAVEN-1150) maven.xml inheritance strangeness
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 7:05 PM Changes: assignee changed to Brett Porter Fix Version changed to 1.0-rc2 - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1150&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1150 Here is an overview of the issue: - Key: MAVEN-1150 Summary: maven.xml inheritance strangeness Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: inheritance Fix Fors: 1.0-rc2 Versions: 1.0-rc2 Assignee: Brett Porter Reporter: Sean Timm Created: Wed, 4 Feb 2004 4:52 PM Updated: Sat, 21 Feb 2004 7:05 PM Description: The attachment contains child/project.xml that extends project-base.xml. There is a maven.xml file in the folder with project-base.xml as well as a maven.xml in the child folder. If you go to the child folder and type "maven different", it will successfully output "ECHO". If you type "maven" or "maven footest", you'll get a TargetInvocationException due to the echo call in the parent's maven.xml. Note that other jelly tags work successfully in the parent...it appears to be an issue just with Ant tags. Additionally, if you remove the maven.xml from the child folder, and then type "maven footest" in the child folder, you get a "no such goal" error rather than executing the inherited maven.xml goal. - 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: (MAVEN-1161) goal mapper does not follow j:import tags
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 6:59 PM Comment: this is only because it is using j:import - if it is in a plugin or in maven.xml itself it works fine. There's another bug around like this. Changes: assignee changed to Brett Porter summary changed from Error message displayed for imported taglibraries priority changed from Major Component changed to jelly/ant integration Component changed to plugin manager Component changed from core Fix Version changed to 1.0-final - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1161&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1161 Here is an overview of the issue: - Key: MAVEN-1161 Summary: goal mapper does not follow j:import tags Type: Bug Status: Open Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: jelly/ant integration plugin manager Fix Fors: 1.0-final Versions: 1.0-rc2 Assignee: Brett Porter Reporter: dion gillard Created: Wed, 11 Feb 2004 11:54 PM Updated: Sat, 21 Feb 2004 6:59 PM Description: RC2 displays an error message for tag libraries that are imported and declared in maven.xml. RC1 does not. See zip file attachment for sample to reproduce the bug. Here is the output from running the sample with RC2 and then RC1. C:\Temp\mavenBug>maven showBug __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc2-SNAPSHOT Tag library requested that is not present: 'bug' in plugin: 'maven:maven' showBug: [echo] Hello World BUILD SUCCESSFUL Total time: 7 seconds Finished at: Thu Feb 12 15:45:47 EST 2004 C:\Temp\mavenBug>mavenrc1 showBug __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc1-SNAPSHOT showBug: [echo] Hello World BUILD SUCCESSFUL Total time: 18 seconds Finished at: Thu Feb 12 15:46:17 EST 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] Updated: (MAVEN-1153) update commons-lang dependency
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 6:48 PM Comment: I think we can actually remove the dependency, which should free it up some. The only problem is that some people who rely on it being there may need to add a dependency to their project... I'll take a look Changes: assignee changed to Brett Porter Version changed from 1.1 Fix Version changed to 1.0-rc2 - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1153&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1153 Here is an overview of the issue: - Key: MAVEN-1153 Summary: update commons-lang dependency Type: Improvement Status: Open Priority: Trivial Original Estimate: 5 minutes Time Spent: Unknown Remaining: 5 minutes Project: maven Fix Fors: 1.0-rc2 Versions: 1.0-rc2 Assignee: Brett Porter Reporter: fabrizio giustina Created: Sat, 7 Feb 2004 10:54 AM Updated: Sat, 21 Feb 2004 6:48 PM Description: actually maven dependencies include commons-lang 1.0-b1.1. It would be better to update it to commons-lang 2.0: the new release is totally compatible with the old (no methods have been removed) and this will allows to use new useful string utils method in plugin (replace, trim, ...). Actually also if you include a commons-lang 2.0 dependency in a plugin it seems you are not able to call commons-lang 2.0 methods from jelly, since it always find the old commons-lang 1.0 classes in maven classloader first (unless specifing a root classloader in dependency). Change: modify in project.xml commons-lang 1.0-b1.1 http://jakarta.apache.org/commons/ with: commons-lang commons-lang 2.0 http://jakarta.apache.org/commons/ - 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: (MAVEN-126) Add a -logfile option
The following issue has been updated: Updater: Eric Hauser (mailto:[EMAIL PROTECTED]) Date: Sat, 21 Feb 2004 5:21 PM Comment: I cleaned up the earlier patches I submitted. It made more sense to me for these properties to be called maven.ant.listener and maven.ant.logger.level as not to confuse users that they were setting listeners for maven itself. I also updated the documentation for the new attributes. Changes: Attachment changed to MAVEN126.patch - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-126&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-126 Here is an overview of the issue: - Key: MAVEN-126 Summary: Add a -logfile option Type: New Feature Status: Unassigned Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: cli Fix Fors: 1.1 Assignee: Reporter: Andrew Stevens Created: Wed, 2 Oct 2002 10:50 AM Updated: Sat, 21 Feb 2004 5:21 PM Environment: Windows 98 Description: One of the options I find useful in Ant is '-logfile ', which redirects the build's output to a given file. It would be nice if I could do the same with Maven; I've not had much success trying to use Win98's command line redirection or paging on Maven's output. - 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/aspectwerkz/src/plugin-test project.xml
vmassol 2004/02/21 07:00:46 Modified:aspectwerkz/src/plugin-test project.xml Log: use AspectWerkz 0.9 Revision ChangesPath 1.4 +1 -1 maven-plugins/aspectwerkz/src/plugin-test/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/aspectwerkz/src/plugin-test/project.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- project.xml 28 Jan 2004 16:07:07 - 1.3 +++ project.xml 21 Feb 2004 15:00:46 - 1.4 @@ -37,7 +37,7 @@ aspectwerkz aspectwerkz - 0.9.RC2.dev.20040125 + 0.9 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1166) plugin issues to fix by RC2
The following comment has been added to this issue: Author: fabrizio giustina Created: Sat, 21 Feb 2004 4:39 AM Body: please also take a look at MPCHANGELOG-30 and MAVEN-1153 (this one is related to a maven dependency, not a plugin) - View this comment: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1166&page=comments#action_16997 - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1166 Here is an overview of the issue: - Key: MAVEN-1166 Summary: plugin issues to fix by RC2 Type: Task Status: Open Priority: Blocker Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: planning Fix Fors: 1.0-rc2 Versions: 1.0-rc1 Assignee: Brett Porter Reporter: Brett Porter Created: Wed, 18 Feb 2004 6:31 PM Updated: Sat, 21 Feb 2004 4:39 AM Description: please link any plugin issues from the plugin projects that need to be fixed before RC2 is released. If you don't have permissions to link, add a comment, and a Maven developer will decide whether it should be linked or not. - 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]
