[jira] Commented: (MPECLIPSE-13) Two hacks to the eclipse plug-in in .classpath generation (see comments for details)
The following comment has been added to this issue:
Author: Pål Brattberg
Created: Thu, 3 Jun 2004 2:21 AM
Body:
Jens, I too needed what you was asking for, and here is my attempt.
Notice that support for exclusion patterns in not on by default in Eclipse, at least
not in IBM WSAD (which in turn is derived from Eclipse). So, if you do not have
exclusion support on, and you have exclude patterns in your project.xml file, Eclipse
will complain about your new .classpath file. Either comment the piece in my addition
that adds exclusions, or tell Eclipse to support exclusion.
This code should go in
MAVEN_HOME/plugins/maven-eclipse-plugin-1.7/plugin-resources/templates/classpath.jelly.
I added it right after the first classpath entry.
j:if test=${!pom.build.resources.isEmpty()}
j:forEach var=res items=${pom.build.resources}
maven:makeRelativePath var=srcDir basedir=${basedir}
path=${res.directory}/
!-- Comment this if you do not wish to use exclusions for resources.
Note that _includes_ do not yet work in Eclipse (AFAIK), so beware of that
if things seem to crash. Also make sure your project is prepared for
exclusions,
this can be set as a property for the compiler. --
j:set var=excluding value=/
j:forEach var=exclude items=${res.excludes}
j:choose
j:when test=${excluding.length() == 0}
j:set var=excluding value=${exclude}/
/j:when
j:otherwise
j:set var=excluding value=${excluding},${exclude}/
/j:otherwise
/j:choose
/j:forEach
!-- End exclusion patterns --
classpathentry kind=src path=${srcDir} excluding=${excluding} /
/j:forEach
/j:if
-
View this comment:
http://jira.codehaus.org/browse/MPECLIPSE-13?page=comments#action_20300
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-13
Here is an overview of the issue:
-
Key: MPECLIPSE-13
Summary: Two hacks to the eclipse plug-in in .classpath generation (see comments
for details)
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-eclipse-plugin
Assignee:
Reporter: Diego Fernandez
Created: Wed, 16 Apr 2003 3:00 PM
Updated: Thu, 3 Jun 2004 2:21 AM
Description:
The attached file contains two hacks to the generation of the classpath in the
eclipse:generate-classpath plug-in:
1. Added the source directory for the integration unit tests.
(TODO: add cactus JARs to the classpath)
2. Add JARs only once (using a Set), this is useful when you have a junit in the
dependencies (or may be in the future when you have the cactus libs)
-
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: (MPECLIPSE-14) Add the ability to exclude source
The following comment has been added to this issue: Author: Pål Brattberg Created: Thu, 3 Jun 2004 2:39 AM Body: On a similar note, see my code at MPECLIPSE-13 for exclusions of resources defined in the project.xml file. Might be related for some users. - View this comment: http://jira.codehaus.org/browse/MPECLIPSE-14?page=comments#action_20302 - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-14 Here is an overview of the issue: - Key: MPECLIPSE-14 Summary: Add the ability to exclude source Type: Improvement Status: Unassigned Priority: Major Original Estimate: 1 week Time Spent: Unknown Remaining: 1 week Project: maven-eclipse-plugin Assignee: Reporter: dion gillard Created: Mon, 2 Jun 2003 7:49 PM Updated: Thu, 3 Jun 2004 2:39 AM Description: From Doug Patterson [EMAIL PROTECTED] The Eclipse plugin creates a .classpath file with tags like: classpathentry kind=src path=src/java Eclipse also supports an excluding attribute that filters out any files matching the supplied pattern. I tweaked plugin.jelly (patch below) to check for a maven.eclipse.exclude property in project.properties and modify kind=src entries accordingly. For example: maven.eclipse.exclude=**/.svn/*# Stop Eclipse complaining about Subversion files - 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: (MPJAR-27) Send e-mail after successfully deploying jars and jar snapshots
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPJAR-27 Here is an overview of the issue: - Key: MPJAR-27 Summary: Send e-mail after successfully deploying jars and jar snapshots Type: New Feature Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jar-plugin Assignee: Jason van Zyl Reporter: Boris Boehlen Created: Thu, 3 Jun 2004 5:37 AM Updated: Thu, 3 Jun 2004 5:37 AM Description: It would be great if an e-mail is send after successfully deploying jars and jar snapshots. This way developers would know that a new version has been uploaded to the repository. - 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: (MPASPECTJ-10) Warning when nothing to weave, maxmem fix, and doc
The following issue has been updated: Updater: Vincent Massol (mailto:[EMAIL PROTECTED]) Date: Thu, 3 Jun 2004 7:40 AM Changes: Fix Version changed to 3.1 - For a full history of the issue, see: http://jira.codehaus.org/browse/MPASPECTJ-10?page=history - View the issue: http://jira.codehaus.org/browse/MPASPECTJ-10 Here is an overview of the issue: - Key: MPASPECTJ-10 Summary: Warning when nothing to weave, maxmem fix, and doc Type: Improvement Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-aspectj-plugin Fix Fors: 3.1 Versions: 3.0 Assignee: Reporter: Carlos Sanchez Created: Sat, 15 May 2004 2:21 PM Updated: Thu, 3 Jun 2004 7:40 AM Description: Warning when nothing to weave Use maxmem only when fork=true to avoid aspectj warnings Added Compiling aspect sources section to xdoc - 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/aspectj project.xml plugin.jelly plugin.properties
vmassol 2004/06/03 04:49:46
Modified:aspectj/xdocs changes.xml properties.xml
aspectj project.xml plugin.jelly plugin.properties
Log:
Added new codemaven.aspectj.source/code and codemaven.aspectj.time/code
properties.
Revision ChangesPath
1.13 +6 -0 maven-plugins/aspectj/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/aspectj/xdocs/changes.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- changes.xml 16 May 2004 02:04:10 - 1.12
+++ changes.xml 3 Jun 2004 11:49:45 - 1.13
@@ -27,6 +27,12 @@
author email=[EMAIL PROTECTED]Carlos Sanchez/author
/properties
body
+release version=3.1-SNAPSHOT date=in CVS
+ action dev=vmassol type=add due-to=Jules Gosnell
+Added new codemaven.aspectj.source/code and
+codemaven.aspectj.time/code properties.
+ /action
+/release
release version=3.0 date=2004-05-15
action dev=vmassol type=add issue=MPASPECTJ-9 due-to=Carlos Sanchez
due-to-email=[EMAIL PROTECTED]Added new
codemaven.aspectj.fork/codeand
1.8 +18 -0 maven-plugins/aspectj/xdocs/properties.xml
Index: properties.xml
===
RCS file: /home/cvs/maven-plugins/aspectj/xdocs/properties.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- properties.xml10 May 2004 18:23:05 - 1.7
+++ properties.xml3 Jun 2004 11:49:45 - 1.8
@@ -107,6 +107,24 @@
/td
/tr
+tr
+ tdmaven.aspectj.source/td
+ tdYes/td
+ td
+The J2SE source compliance level. Valid values are [1.3 1.4].
+Defaults to code1.3/code.
+ /td
+/tr
+
+tr
+ tdmaven.aspectj.time/td
+ tdYes/td
+ td
+If true, display speed information during weaving.
+Defaults to codefalse/code.
+ /td
+/tr
+
/table
/section
1.35 +6 -1 maven-plugins/aspectj/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven-plugins/aspectj/project.xml,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- project.xml 16 May 2004 02:04:10 - 1.34
+++ project.xml 3 Jun 2004 11:49:45 - 1.35
@@ -23,7 +23,7 @@
pomVersion3/pomVersion
idmaven-aspectj-plugin/id
nameMaven AspectJ Plugin/name
- currentVersion3.0/currentVersion
+ currentVersion3.1-SNAPSHOT/currentVersion
description/
shortDescriptionAspectJ Plugin for Maven/shortDescription
urlhttp://maven.apache.org/reference/plugins/aspectj//url
@@ -49,6 +49,11 @@
id3.0/id
name3.0/name
tagMAVEN_ASPECTJ_3_0/tag
+/version
+version
+ id3.1/id
+ name3.1/name
+ tagHEAD/tag
/version
/versions
developers
1.12 +3 -1 maven-plugins/aspectj/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/aspectj/plugin.jelly,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- plugin.jelly 10 May 2004 18:23:05 - 1.11
+++ plugin.jelly 3 Jun 2004 11:49:45 - 1.12
@@ -103,7 +103,9 @@
sourceRootCopyFilter=${maven.aspectj.sourceRootCopyFilter}
debug=${maven.aspectj.debug}
emacssym=${maven.aspectj.emacssym}
- verbose=${maven.aspectj.verbose}
+ verbose=${maven.aspectj.verbose}
+ source=${maven.aspectj.source}
+ time=${maven.aspectj.time}
ant:sourceroots
ant:path refid=maven.compile.src.set/
1.6 +7 -0 maven-plugins/aspectj/plugin.properties
Index: plugin.properties
===
RCS file: /home/cvs/maven-plugins/aspectj/plugin.properties,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- plugin.properties 10 May 2004 18:23:05 - 1.5
+++ plugin.properties 3 Jun 2004 11:49:45 - 1.6
@@ -45,3 +45,10 @@
# The maximum memory to use for the new VM when fork is true. Values should
# have the same form as accepted by the VM, e.g., 128m.
maven.aspectj.maxmem = 128m
+
+# The J2SE source compliance level. Valid values are [1.3 1.4].
+# Defaults to 1.3.
+maven.aspectj.source = 1.3
+
+# If true, display speed information during weaving.
+maven.aspectj.time = false
cvs commit: maven-plugins/aspectj project.xml
vmassol 2004/06/03 04:53:16 Modified:aspectj/xdocs changes.xml aspectj project.xml Log: Now using AspectJ 1.2 release. Revision ChangesPath 1.14 +3 -0 maven-plugins/aspectj/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/aspectj/xdocs/changes.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- changes.xml 3 Jun 2004 11:49:45 - 1.13 +++ changes.xml 3 Jun 2004 11:53:16 - 1.14 @@ -28,6 +28,9 @@ /properties body release version=3.1-SNAPSHOT date=in CVS + action dev=vmassol type=update +Now using AspectJ 1.2 release. + /action action dev=vmassol type=add due-to=Jules Gosnell Added new codemaven.aspectj.source/code and codemaven.aspectj.time/code properties. 1.36 +2 -2 maven-plugins/aspectj/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/aspectj/project.xml,v retrieving revision 1.35 retrieving revision 1.36 diff -u -r1.35 -r1.36 --- project.xml 3 Jun 2004 11:49:45 - 1.35 +++ project.xml 3 Jun 2004 11:53:16 - 1.36 @@ -93,12 +93,12 @@ dependency groupIdaspectj/groupId artifactIdaspectjrt/artifactId - version1.2rc1/version + version1.2/version /dependency dependency groupIdaspectj/groupId artifactIdaspectjtools/artifactId - version1.2rc1/version + version1.2/version /dependency /dependencies /project - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Adding SVN support to SCM and CruiseControl plugins
Hi all, Anyone have a reason why I shouldn't tweak the SCM and CruiseControl plugins to support Subversion? I am using a custom .jsl file to compile my cruisecontrol configuration file, and the CruiseControl plugin calls the scm:validate method which dies right now. Eric Pugh Scanned for viruses by MessageLabs. The integrity and security of this message cannot be guaranteed. This email is intended for the named recipient only, and may contain confidential information and proprietary material. Any unauthorised use or disclosure is prohibited.
[jira] Created: (MPJAR-28) Broken Class-Path entry in manifest.mf
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPJAR-28 Here is an overview of the issue: - Key: MPJAR-28 Summary: Broken Class-Path entry in manifest.mf Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jar-plugin Assignee: Jason van Zyl Reporter: Janne Kario Created: Thu, 3 Jun 2004 9:47 AM Updated: Thu, 3 Jun 2004 9:47 AM Environment: Maven RC3, Java 1.4.2_03 Description: Class-Path manifest entry created by the jar plugin is wrapped at 70 chars resulting in a broken manifest entry. eg. Class-Path: ***-common-1.0.jar ***-jms-1.0.jar ***-ej b-1.0.jar mx4j-jmx-2.0.1.jar mx4j-2.0.1.jar mx4j-tools-2.0.1.jar mx4j -impl-2.0.1.jar log4j-1.2.8.jar Each manifest entry line ends at char number 70. The next line begins with a space. - 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: (MPJAR-28) Broken Class-Path entry in manifest.mf
The following comment has been added to this issue: Author: Janne Kario Created: Thu, 3 Jun 2004 9:51 AM Body: The same thing happens with the Class-Path entry in the ejb plugin which leads me to believe that this is not an issues with JAR plugin itself. - View this comment: http://jira.codehaus.org/browse/MPJAR-28?page=comments#action_20314 - View the issue: http://jira.codehaus.org/browse/MPJAR-28 Here is an overview of the issue: - Key: MPJAR-28 Summary: Broken Class-Path entry in manifest.mf Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jar-plugin Assignee: Jason van Zyl Reporter: Janne Kario Created: Thu, 3 Jun 2004 9:47 AM Updated: Thu, 3 Jun 2004 9:51 AM Environment: Maven RC3, Java 1.4.2_03 Description: Class-Path manifest entry created by the jar plugin is wrapped at 70 chars resulting in a broken manifest entry. eg. Class-Path: ***-common-1.0.jar ***-jms-1.0.jar ***-ej b-1.0.jar mx4j-jmx-2.0.1.jar mx4j-2.0.1.jar mx4j-tools-2.0.1.jar mx4j -impl-2.0.1.jar log4j-1.2.8.jar Each manifest entry line ends at char number 70. The next line begins with a space. - 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: (MPJCOVERAGE-9) Bad path to stylesheet generated
The following issue has been updated: Updater: Philippe Mouawad (mailto:[EMAIL PROTECTED]) Date: Thu, 3 Jun 2004 10:08 AM Comment: What is described in the mail Changes: Attachment changed to CoverageReport.java - For a full history of the issue, see: http://jira.codehaus.org/browse/MPJCOVERAGE-9?page=history - View the issue: http://jira.codehaus.org/browse/MPJCOVERAGE-9 Here is an overview of the issue: - Key: MPJCOVERAGE-9 Summary: Bad path to stylesheet generated Type: Bug Status: Open Priority: Major Original Estimate: 0 minutes Time Spent: Unknown Remaining: 0 minutes Project: maven-jcoverage-plugin Versions: 1.0.3 1.0.4 1.0.5 Assignee: Emmanuel Venisse Reporter: Philippe Mouawad Created: Thu, 3 Jun 2004 10:06 AM Updated: Thu, 3 Jun 2004 10:08 AM Environment: Windows NT Description: When I use jcoverage plugin, it generate HTML files with the following kind of path for stylesheet: link rel =stylesheet type=text/css href=\.\./\.\./\.\./style.css title=Style As you can see there is \. that should be . This results into the browser not finding the stylesheet. I opened the code and replaced return new Perl5Util().substitute(s/[^\\.]*(\\.|$)/\\.\\.\\//g, path); by return new Perl5Util().substitute(s/[^\\.]*(\\.|$)/..\\//g, path); In method org.apache.maven.jcoveragereport.CoverageReport = private String getRelativePath(String path) In fact if you look at ; http://jakarta.apache.org/oro/api/org/apache/oro/text/perl/Perl5Util.html In the following example: line = util.substitute(s/description1\\.html/about1.html/, line); They don't escape the . in the replacement string. and it know generates good pathes. Since I didn't find a bug for this I thought I may be doing something wrong, could you help me please. - 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: (MPJCOVERAGE-9) Bad path to stylesheet generated
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPJCOVERAGE-9 Here is an overview of the issue: - Key: MPJCOVERAGE-9 Summary: Bad path to stylesheet generated Type: Bug Status: Open Priority: Major Original Estimate: 0 minutes Time Spent: Unknown Remaining: 0 minutes Project: maven-jcoverage-plugin Versions: 1.0.3 1.0.4 1.0.5 Assignee: Emmanuel Venisse Reporter: Philippe Mouawad Created: Thu, 3 Jun 2004 10:06 AM Updated: Thu, 3 Jun 2004 10:06 AM Environment: Windows NT Description: When I use jcoverage plugin, it generate HTML files with the following kind of path for stylesheet: link rel =stylesheet type=text/css href=\.\./\.\./\.\./style.css title=Style As you can see there is \. that should be . This results into the browser not finding the stylesheet. I opened the code and replaced return new Perl5Util().substitute(s/[^\\.]*(\\.|$)/\\.\\.\\//g, path); by return new Perl5Util().substitute(s/[^\\.]*(\\.|$)/..\\//g, path); In method org.apache.maven.jcoveragereport.CoverageReport = private String getRelativePath(String path) In fact if you look at ; http://jakarta.apache.org/oro/api/org/apache/oro/text/perl/Perl5Util.html In the following example: line = util.substitute(s/description1\\.html/about1.html/, line); They don't escape the . in the replacement string. and it know generates good pathes. Since I didn't find a bug for this I thought I may be doing something wrong, could you help me please. - 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: (MPJAR-28) Broken Class-Path entry in manifest.mf
The following comment has been added to this issue: Author: Emmanuel Venisse Created: Thu, 3 Jun 2004 10:05 AM Body: It's the jar specification. http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html Line length: No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make the initial line longer than this, it should be continued on extra lines (each starting with a single SPACE). - View this comment: http://jira.codehaus.org/browse/MPJAR-28?page=comments#action_20315 - View the issue: http://jira.codehaus.org/browse/MPJAR-28 Here is an overview of the issue: - Key: MPJAR-28 Summary: Broken Class-Path entry in manifest.mf Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jar-plugin Assignee: Jason van Zyl Reporter: Janne Kario Created: Thu, 3 Jun 2004 9:47 AM Updated: Thu, 3 Jun 2004 10:05 AM Environment: Maven RC3, Java 1.4.2_03 Description: Class-Path manifest entry created by the jar plugin is wrapped at 70 chars resulting in a broken manifest entry. eg. Class-Path: ***-common-1.0.jar ***-jms-1.0.jar ***-ej b-1.0.jar mx4j-jmx-2.0.1.jar mx4j-2.0.1.jar mx4j-tools-2.0.1.jar mx4j -impl-2.0.1.jar log4j-1.2.8.jar Each manifest entry line ends at char number 70. The next line begins with a space. - 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: (MPJAR-28) Broken Class-Path entry in manifest.mf
The following comment has been added to this issue: Author: Dominique Jocal Created: Thu, 3 Jun 2004 10:24 AM Body: We could notice that the spec does not require to 'split' the words, it only requires lines to size 72 char max. A classical word-wrapping (words not splitted) should be ok with the spec. We observed in big projects that Manifests with cut dependencies are terrific : it's not possible any more to search for a dependency by its name, as it's potentially splitted. Unfortunately, a correction in Maven may be difficult to do as it seems here we use an Ant feature. - View this comment: http://jira.codehaus.org/browse/MPJAR-28?page=comments#action_20317 - View the issue: http://jira.codehaus.org/browse/MPJAR-28 Here is an overview of the issue: - Key: MPJAR-28 Summary: Broken Class-Path entry in manifest.mf Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jar-plugin Assignee: Jason van Zyl Reporter: Janne Kario Created: Thu, 3 Jun 2004 9:47 AM Updated: Thu, 3 Jun 2004 10:24 AM Environment: Maven RC3, Java 1.4.2_03 Description: Class-Path manifest entry created by the jar plugin is wrapped at 70 chars resulting in a broken manifest entry. eg. Class-Path: ***-common-1.0.jar ***-jms-1.0.jar ***-ej b-1.0.jar mx4j-jmx-2.0.1.jar mx4j-2.0.1.jar mx4j-tools-2.0.1.jar mx4j -impl-2.0.1.jar log4j-1.2.8.jar Each manifest entry line ends at char number 70. The next line begins with a space. - 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: (MPJCOVERAGE-9) Bad path to stylesheet generated
The following comment has been added to this issue: Author: Emmanuel Venisse Created: Thu, 3 Jun 2004 10:36 AM Body: Do you redefine the stylesheet property or you use the default value? - View this comment: http://jira.codehaus.org/browse/MPJCOVERAGE-9?page=comments#action_20318 - View the issue: http://jira.codehaus.org/browse/MPJCOVERAGE-9 Here is an overview of the issue: - Key: MPJCOVERAGE-9 Summary: Bad path to stylesheet generated Type: Bug Status: Open Priority: Major Original Estimate: 0 minutes Time Spent: Unknown Remaining: 0 minutes Project: maven-jcoverage-plugin Versions: 1.0.3 1.0.4 1.0.5 Assignee: Emmanuel Venisse Reporter: Philippe Mouawad Created: Thu, 3 Jun 2004 10:06 AM Updated: Thu, 3 Jun 2004 10:36 AM Environment: Windows NT Description: When I use jcoverage plugin, it generate HTML files with the following kind of path for stylesheet: link rel =stylesheet type=text/css href=\.\./\.\./\.\./style.css title=Style As you can see there is \. that should be . This results into the browser not finding the stylesheet. I opened the code and replaced return new Perl5Util().substitute(s/[^\\.]*(\\.|$)/\\.\\.\\//g, path); by return new Perl5Util().substitute(s/[^\\.]*(\\.|$)/..\\//g, path); In method org.apache.maven.jcoveragereport.CoverageReport = private String getRelativePath(String path) In fact if you look at ; http://jakarta.apache.org/oro/api/org/apache/oro/text/perl/Perl5Util.html In the following example: line = util.substitute(s/description1\\.html/about1.html/, line); They don't escape the . in the replacement string. and it know generates good pathes. Since I didn't find a bug for this I thought I may be doing something wrong, could you help me please. - 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: (MPASPECTJ-6) autoweave test code before running tests
The following issue has been updated: Updater: Carlos Sanchez (mailto:[EMAIL PROTECTED]) Date: Thu, 3 Jun 2004 12:19 PM Comment: Weave test classes - added goal aspectj:test-compile - created aspectj taglib to avoid duplication - documented, of course ;) Changes: Attachment changed to aspectj-test.txt - For a full history of the issue, see: http://jira.codehaus.org/browse/MPASPECTJ-6?page=history - View the issue: http://jira.codehaus.org/browse/MPASPECTJ-6 Here is an overview of the issue: - Key: MPASPECTJ-6 Summary: autoweave test code before running tests Type: Improvement Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-aspectj-plugin Fix Fors: 3.1 Assignee: Reporter: John Fallows Created: Wed, 25 Feb 2004 8:58 PM Updated: Thu, 3 Jun 2004 12:19 PM Environment: maven-1.0-rc1, WinXP, J2SE 1.4.2 Description: I have recently started to use virtual mock objects (http://www.virtualmock.org) that make heavy use of AspectJ in the test cases of a maven project. I noticed that the latest AspectJ plugin has support for autoweaving the project sources, but not the test sources. Once you have resolved how to weave the compiled classes instead of just the JAR, how difficult would it be to autoweave the test classes as well? - 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: (MPASPECTJ-6) autoweave test code before running tests
The following comment has been added to this issue: Author: Carlos Sanchez Created: Thu, 3 Jun 2004 12:20 PM Body: The patch is against latest CVS - View this comment: http://jira.codehaus.org/browse/MPASPECTJ-6?page=comments#action_20320 - View the issue: http://jira.codehaus.org/browse/MPASPECTJ-6 Here is an overview of the issue: - Key: MPASPECTJ-6 Summary: autoweave test code before running tests Type: Improvement Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-aspectj-plugin Fix Fors: 3.1 Assignee: Reporter: John Fallows Created: Wed, 25 Feb 2004 8:58 PM Updated: Thu, 3 Jun 2004 12:20 PM Environment: maven-1.0-rc1, WinXP, J2SE 1.4.2 Description: I have recently started to use virtual mock objects (http://www.virtualmock.org) that make heavy use of AspectJ in the test cases of a maven project. I noticed that the latest AspectJ plugin has support for autoweaving the project sources, but not the test sources. Once you have resolved how to weave the compiled classes instead of just the JAR, how difficult would it be to autoweave the test classes as well? - 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]
AspectJ 1.2 on ibilio
Hi, I've seen that anybody has uploaded AspectJ 1.2 to ibiblio before the AspectJ guys had submitted an upload request to JIRA. They have just mailed me the pom and license files, should they be also uploaded to ibiblio? Thanks 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: AspectJ 1.2 on ibilio
On Thu, 2004-06-03 at 11:57, Carlos Sanchez wrote: Hi, I've seen that anybody has uploaded AspectJ 1.2 to ibiblio before the AspectJ guys had submitted an upload request to JIRA. They have just mailed me the pom and license files, should they be also uploaded to ibiblio? Make a bundle, toss it into JIRA and it will be processed. So, yes, the POM and license are necessary. Thanks 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] -- 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]
[jira] Commented: (MPMULTIPROJECT-32) Multiproject and properties inheritance issue
The following comment has been added to this issue: Author: Winston Rast Created: Thu, 3 Jun 2004 1:01 PM Body: This sounds suspiciously similar to MAVEN-1296, where I have attached an example project that demonstrates the problem from my perspective. - View this comment: http://jira.codehaus.org/browse/MPMULTIPROJECT-32?page=comments#action_20322 - View the issue: http://jira.codehaus.org/browse/MPMULTIPROJECT-32 Here is an overview of the issue: - Key: MPMULTIPROJECT-32 Summary: Multiproject and properties inheritance issue Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-multiproject-plugin Versions: 1.3 Assignee: dion gillard Reporter: Carlos Sanchez Created: Wed, 2 Jun 2004 7:09 PM Updated: Thu, 3 Jun 2004 1:01 PM Environment: Maven 1.0-rc3 WinXP Description: I have some projects common/all common/model extends common/all common/webapp extends common/model party/model extends common/model party/webapp extends common/webapp doc extends common/all Some properties are set in a project.properties file in common/all (for example maven.test.skip=true). When calling multiproject from the doc subproject (which calls all projects), properties defined in common/all are not available to the party/model and party/webapp If I define the properties in the doc project.properties everything seems ok. If I run multiproject from common/all everything also seems ok. - 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-1304) SAR dependencies don't appear on classpath
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1304 Here is an overview of the issue: - Key: MAVEN-1304 Summary: SAR dependencies don't appear on classpath Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Versions: 1.0-rc3 1.0-rc2 Assignee: Reporter: Chris Bonham Created: Thu, 3 Jun 2004 1:27 PM Updated: Thu, 3 Jun 2004 1:27 PM Environment: JDK 1.4.2_03, RH ES 2.4.21-4.EL Description: When a dependency is created of type sar, it doesn't show up on the dependency classpath when needed by javac: dependencies dependency groupIdsc/groupId artifactIdsc-common/artifactId version1.0/version typesar/type properties /properties /dependency /dependencies [javac] [VERBOSE] Compilation arguments: '-d' 'C:\sc\src\ejb\target\classes' '-classpath' 'C:\sc\src\ejb\target\classes;C:\Documents and Settings\cbonham\.maven\repository\ejb\jars\ejb-2.0.jar;C:\Documents and Settings\cbonham\.maven\repository\jta\jars\jta-1.0.1.jar;C:\Documents and Settings\cbonham\.maven\repository\servletapi\jars\servletapi-2.3.jar;C:\Documents and Settings\cbonham\.maven\repository\jmx\jars\jmxri-1.0.jar;C:\Documents and Settings\cbonham\.maven\repository\activation\jars\activation-1.0.2.jar;C:\Documents and Settings\cbonham\.maven\repository\javamail\jars\mail-1.3.jar;C:\Documents and Settings\cbonham\.maven\repository\commons-collections\jars\commons-collections-2.1.jar;C:\Documents and Settings\cbonham\.maven\repository\commons-logging\jars\commons-logging-1.0.3.jar;C:\maven-1.0-rc3\lib\forehead-1.0-beta-5.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]
[maven2 build] Thu Jun 3 14:12:53 EDT 2004
Performing a clean check out of maven-components ... Updates occured, build required ... --- Building mboot ... --- --- Maven MBoot --- Installing mboot in /home/users/jvanzyl/mboot ... --- Installing MBoot dependencies ... --- --- Install the parent pom for all maven-component artifacts ... --- Installing POM in /home/users/jvanzyl/maven-repo-local/maven/poms/maven-component-2.0-SNAPSHOT.pom --- Building maven-model ... --- Generating java in target/generated-sources from maven.mdo Generating xpp3 unmarshaller in target/generated-sources from maven.mdo Generating xpp3 marshaller in target/generated-sources from maven.mdo Generating xml schema in . from maven.mdo Generating xdoc in target/generated-xdocs from maven.mdo Building project in /home/users/jvanzyl/m2/maven-components/maven-model Using the following for your maven.repo.local: /home/users/jvanzyl/maven-repo-local Building tests in /home/users/jvanzyl/m2/maven-components/maven-model Running tests in /home/users/jvanzyl/m2/maven-components/maven-model --- T E S T S --- [surefire] Running org.codehaus.surefire.battery.DirectoryBattery [surefire] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 0 sec Building jars (maven-model-2.0-SNAPSHOT.jar) in /home/users/jvanzyl/m2/maven-components/maven-model/target Installing maven-model-2.0-SNAPSHOT.jar in /home/users/jvanzyl/maven-repo-local/maven/jars Installing POM in /home/users/jvanzyl/maven-repo-local/maven/poms/maven-model-2.0-SNAPSHOT.pom --- Building maven-project ... --- Building project in /home/users/jvanzyl/m2/maven-components/maven-project Using the following for your maven.repo.local: /home/users/jvanzyl/maven-repo-local Downloading dependency: plexus/jars/plexus-0.14-SNAPSHOT.jar . . Downloading dependency: plexus/jars/plexus-i18n-1.0-beta-2-SNAPSHOT.jar .. . Downloading dependency: maven/jars/wagon-api-0.9-SNAPSHOT.jar ... . Downloading dependency: classworlds/jars/classworlds-1.1-SNAPSHOT.jar .. . src/main/java/org/apache/maven/artifact/downloader/DefaultArtifactDownloader.java:14: cannot resolve symbol symbol : class Md5SumObserver location: package observers import org.apache.maven.wagon.observers.Md5SumObserver; ^ src/main/java/org/apache/maven/artifact/downloader/DefaultArtifactDownloader.java:134: cannot resolve symbol symbol : class Md5SumObserver location: class org.apache.maven.artifact.downloader.DefaultArtifactDownloader Md5SumObserver md5SumObserver = new Md5SumObserver(); ^ src/main/java/org/apache/maven/artifact/downloader/DefaultArtifactDownloader.java:134: cannot resolve symbol symbol : class Md5SumObserver location: class org.apache.maven.artifact.downloader.DefaultArtifactDownloader Md5SumObserver md5SumObserver = new Md5SumObserver(); ^ 3 errors Failed compiling classes! --- Building maven-plugin ... --- Building project in /home/users/jvanzyl/m2/maven-components/maven-plugin Using the following for your maven.repo.local: /home/users/jvanzyl/maven-repo-local Building tests in /home/users/jvanzyl/m2/maven-components/maven-plugin Running tests in /home/users/jvanzyl/m2/maven-components/maven-plugin --- T E S T S --- [surefire] Running org.codehaus.surefire.battery.DirectoryBattery [surefire] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 0 sec [surefire] Running org.apache.maven.plugin.generator.jelly.JellyHarnessGeneratorTest [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.131 sec [surefire] Running org.apache.maven.plugin.generator.BeanGeneratorTest [surefire] Tests run: 1, Failures: 0, Errors: 0, Time
cvs commit: maven-components/maven-core m2-bootstrap-all.sh
jvanzyl 2004/06/03 11:20:52 Modified:maven-core m2-bootstrap-all.sh Log: o add check for MBOOT_HOME Revision ChangesPath 1.3 +2 -0 maven-components/maven-core/m2-bootstrap-all.sh Index: m2-bootstrap-all.sh === RCS file: /home/cvs/maven-components/maven-core/m2-bootstrap-all.sh,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- m2-bootstrap-all.sh 1 Jun 2004 21:33:16 - 1.2 +++ m2-bootstrap-all.sh 3 Jun 2004 18:20:52 - 1.3 @@ -1,5 +1,7 @@ #!/bin/sh +[ -z $MBOOT_HOME ] echo echo 'You must set $MBOOT_HOME to use mboot!' echo exit + # Build and install mboot ( echo --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-components/maven-core m2-bootstrap.sh
jvanzyl 2004/06/03 11:21:05 Modified:maven-core m2-bootstrap.sh Log: o add check for MBOOT_HOME Revision ChangesPath 1.2 +3 -0 maven-components/maven-core/m2-bootstrap.sh Index: m2-bootstrap.sh === RCS file: /home/cvs/maven-components/maven-core/m2-bootstrap.sh,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- m2-bootstrap.sh 1 Jun 2004 21:31:06 - 1.1 +++ m2-bootstrap.sh 3 Jun 2004 18:21:05 - 1.2 @@ -1,6 +1,9 @@ #!/bin/sh +[ -z $MBOOT_HOME ] echo echo 'You must set $MBOOT_HOME to use mboot!' echo exit + rm -rf target + mboot --leave-boot-files --install DIST=dist/m2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-components/maven-core m2-bootstrap-all.sh
jvanzyl 2004/06/03 11:30:13 Modified:maven-core m2-bootstrap-all.sh Log: o check to make sure mboot is in the path Revision ChangesPath 1.4 +6 -0 maven-components/maven-core/m2-bootstrap-all.sh Index: m2-bootstrap-all.sh === RCS file: /home/cvs/maven-components/maven-core/m2-bootstrap-all.sh,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- m2-bootstrap-all.sh 3 Jun 2004 18:20:52 - 1.3 +++ m2-bootstrap-all.sh 3 Jun 2004 18:30:13 - 1.4 @@ -1,6 +1,12 @@ #!/bin/sh +# Check to make sure MBOOT_HOME is set [ -z $MBOOT_HOME ] echo echo 'You must set $MBOOT_HOME to use mboot!' echo exit + +# Check to make sure mboot is in the path +which mboot /dev/null 21 + +[ $? = 1 ] echo echo You must mboot in your PATH! echo exit # Build and install mboot ( - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-components/maven-core m2-bootstrap.sh
jvanzyl 2004/06/03 11:30:23 Modified:maven-core m2-bootstrap.sh Log: o check to make sure mboot is in the path Revision ChangesPath 1.3 +6 -0 maven-components/maven-core/m2-bootstrap.sh Index: m2-bootstrap.sh === RCS file: /home/cvs/maven-components/maven-core/m2-bootstrap.sh,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- m2-bootstrap.sh 3 Jun 2004 18:21:05 - 1.2 +++ m2-bootstrap.sh 3 Jun 2004 18:30:23 - 1.3 @@ -1,6 +1,12 @@ #!/bin/sh +# Check to make sure MBOOT_HOME is set [ -z $MBOOT_HOME ] echo echo 'You must set $MBOOT_HOME to use mboot!' echo exit + +# Check to make sure mboot is in the path +which mboot /dev/null 21 + +[ $? = 1 ] echo echo You must mboot in your PATH! echo exit rm -rf target - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPTEST-34) Documentation for maven.test.failure.ignore not correct
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPTEST-34 Here is an overview of the issue: - Key: MPTEST-34 Summary: Documentation for maven.test.failure.ignore not correct Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-test-plugin Assignee: Jason van Zyl Reporter: Erik Husby Created: Thu, 3 Jun 2004 3:02 PM Updated: Thu, 3 Jun 2004 3:02 PM Environment: Any Description: It used to be that setting maven.test.failure.ignore to any value caused test failures to be ignored. That is what the current documentation says. However, the code was changed such that it is now required that maven.test.failure.ignore=true for test failures to be ignored. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-components ci.sh
jvanzyl 2004/06/03 12:04:44 Modified:.ci.sh Log: o directing to m2-dev now that the list is up Revision ChangesPath 1.21 +1 -1 maven-components/ci.sh Index: ci.sh === RCS file: /home/cvs/maven-components/ci.sh,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- ci.sh 1 Jun 2004 21:31:23 - 1.20 +++ ci.sh 3 Jun 2004 19:04:44 - 1.21 @@ -32,7 +32,7 @@ REPO=maven-repo-local [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] SCM_LOG=scm.log TIMESTAMP=`date +%Y%M%d.%H%M%S` DEPLOY_DIR=$HOME_DIR/public_html/m2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-components/maven-project/src/main/java/org/apache/maven/artifact/downloader DefaultArtifactDownloader.java
michal 2004/06/03 12:09:30 Modified:maven-project/src/main/java/org/apache/maven/artifact/downloader DefaultArtifactDownloader.java Log: Md5Observer renamed to ChecksumObserver Revision ChangesPath 1.6 +5 -5 maven-components/maven-project/src/main/java/org/apache/maven/artifact/downloader/DefaultArtifactDownloader.java Index: DefaultArtifactDownloader.java === RCS file: /home/cvs/maven-components/maven-project/src/main/java/org/apache/maven/artifact/downloader/DefaultArtifactDownloader.java,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- DefaultArtifactDownloader.java21 May 2004 16:54:13 - 1.5 +++ DefaultArtifactDownloader.java3 Jun 2004 19:09:30 - 1.6 @@ -11,7 +11,7 @@ import org.apache.maven.wagon.Wagon; import org.apache.maven.wagon.authorization.AuthorizationException; import org.apache.maven.wagon.manager.WagonManager; -import org.apache.maven.wagon.observers.Md5SumObserver; +import org.apache.maven.wagon.observers.ChecksumObserver; import org.apache.maven.wagon.repository.Repository; import org.codehaus.plexus.logging.AbstractLogEnabled; @@ -131,7 +131,7 @@ // So we can easly add SH1, SHA2, validatoion or whatevre else while the logic // of this operation will be hidden. // -Md5SumObserver md5SumObserver = new Md5SumObserver(); +ChecksumObserver md5SumObserver = new ChecksumObserver(); wagon.addTransferListener( md5SumObserver ); @@ -164,9 +164,9 @@ wagon.removeTransferListener( md5SumObserver ); } -getLogger().info( Actual md5 : + md5SumObserver.getActualMd5Sum() ); +getLogger().info( Actual md5 : + md5SumObserver.getActualChecksum() ); -getLogger().info( Expected md5: + md5SumObserver.getExpectedMd5Sum() ); +getLogger().info( Expected md5: + md5SumObserver.getExpectedChecksum() ); getLogger().info( md5 is valid: + md5SumObserver.cheksumIsValid() ); - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build] Thu Jun 3 15:02:37 EDT 2004
Performing a clean check out of maven-components ... Updates occured, build required ... --- Building mboot ... --- --- Maven MBoot --- Installing mboot in /home/users/jvanzyl/mboot ... --- Installing MBoot dependencies ... --- --- Install the parent pom for all maven-component artifacts ... --- Installing POM in /home/users/jvanzyl/maven-repo-local/maven/poms/maven-component-2.0-SNAPSHOT.pom --- Building maven-model ... --- Generating java in target/generated-sources from maven.mdo Generating xpp3 unmarshaller in target/generated-sources from maven.mdo Generating xpp3 marshaller in target/generated-sources from maven.mdo Generating xml schema in . from maven.mdo Generating xdoc in target/generated-xdocs from maven.mdo Building project in /home/users/jvanzyl/m2/maven-components/maven-model Using the following for your maven.repo.local: /home/users/jvanzyl/maven-repo-local Building tests in /home/users/jvanzyl/m2/maven-components/maven-model Running tests in /home/users/jvanzyl/m2/maven-components/maven-model --- T E S T S --- [surefire] Running org.codehaus.surefire.battery.DirectoryBattery [surefire] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 0 sec Building jars (maven-model-2.0-SNAPSHOT.jar) in /home/users/jvanzyl/m2/maven-components/maven-model/target Installing maven-model-2.0-SNAPSHOT.jar in /home/users/jvanzyl/maven-repo-local/maven/jars Installing POM in /home/users/jvanzyl/maven-repo-local/maven/poms/maven-model-2.0-SNAPSHOT.pom --- Building maven-project ... --- Building project in /home/users/jvanzyl/m2/maven-components/maven-project Using the following for your maven.repo.local: /home/users/jvanzyl/maven-repo-local Downloading dependency: plexus/jars/plexus-0.14-SNAPSHOT.jar . . Downloading dependency: plexus/jars/plexus-i18n-1.0-beta-2-SNAPSHOT.jar .. . Downloading dependency: maven/jars/wagon-api-0.9-SNAPSHOT.jar . . Downloading dependency: classworlds/jars/classworlds-1.1-SNAPSHOT.jar . . src/main/java/org/apache/maven/artifact/downloader/DefaultArtifactDownloader.java:14: cannot resolve symbol symbol : class Md5SumObserver location: package observers import org.apache.maven.wagon.observers.Md5SumObserver; ^ src/main/java/org/apache/maven/artifact/downloader/DefaultArtifactDownloader.java:134: cannot resolve symbol symbol : class Md5SumObserver location: class org.apache.maven.artifact.downloader.DefaultArtifactDownloader Md5SumObserver md5SumObserver = new Md5SumObserver(); ^ src/main/java/org/apache/maven/artifact/downloader/DefaultArtifactDownloader.java:134: cannot resolve symbol symbol : class Md5SumObserver location: class org.apache.maven.artifact.downloader.DefaultArtifactDownloader Md5SumObserver md5SumObserver = new Md5SumObserver(); ^ 3 errors Failed compiling classes! --- Building maven-plugin ... --- Building project in /home/users/jvanzyl/m2/maven-components/maven-plugin Using the following for your maven.repo.local: /home/users/jvanzyl/maven-repo-local Building tests in /home/users/jvanzyl/m2/maven-components/maven-plugin Running tests in /home/users/jvanzyl/m2/maven-components/maven-plugin --- T E S T S --- [surefire] Running org.codehaus.surefire.battery.DirectoryBattery [surefire] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 0 sec [surefire] Running org.apache.maven.plugin.generator.jelly.JellyHarnessGeneratorTest [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.134 sec [surefire] Running org.apache.maven.plugin.generator.BeanGeneratorTest [surefire] Tests run: 1, Failures: 0, Errors: 0,
cvs commit: maven-components/maven-project/src/main/java/org/apache/maven/artifact/downloader DefaultArtifactDownloader.java
michal 2004/06/03 13:07:44
Modified:maven-project/src/main/java/org/apache/maven/artifact/downloader
DefaultArtifactDownloader.java
Log:
removed debug info
Revision ChangesPath
1.7 +2 -2
maven-components/maven-project/src/main/java/org/apache/maven/artifact/downloader/DefaultArtifactDownloader.java
Index: DefaultArtifactDownloader.java
===
RCS file:
/home/cvs/maven-components/maven-project/src/main/java/org/apache/maven/artifact/downloader/DefaultArtifactDownloader.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- DefaultArtifactDownloader.java3 Jun 2004 19:09:30 - 1.6
+++ DefaultArtifactDownloader.java3 Jun 2004 20:07:44 - 1.7
@@ -85,7 +85,7 @@
{
//@todo improve error handling and reporting
-getLogger().info( Failed to download: + artifact.getUrlPath() +
from + repository.getUrl(), e );
+getLogger().info( Failed to download: + artifact.getUrlPath() +
from + repository.getUrl() );
return false;
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-723) Specifying multiple directories in project.xml
The following comment has been added to this issue: Author: analogue Created: Thu, 3 Jun 2004 5:03 PM Body: +1 on having maven support multiple source directories. Having just one src dir lacks much needed flexiblity and doesn't address instances where a project's directory structure has either already been decided, mandated by policy, or adheres to popular opinion (Eclipse support for multiple directories in 2.x was abysmal. Not only did they get it right in 3.0 because of user feedback, they outdid themselves. Its a joy to see so much inherent flexibility in the end result). Developers, users, managers, and decision makers can all generally agree...choice is a good thing. Nevertheless, as wonderful and powerful a product as Maven is, this issue in particular (in my experience) is going to end up being a big thumbs down for Maven as far as corporate adoption goes. - View this comment: http://jira.codehaus.org/browse/MAVEN-723?page=comments#action_20323 - View the issue: http://jira.codehaus.org/browse/MAVEN-723 Here is an overview of the issue: - Key: MAVEN-723 Summary: Specifying multiple directories in project.xml Type: Improvement Status: Closed Priority: Blocker Resolution: WON'T FIX Original Estimate: 0 minutes Time Spent: Unknown Remaining: 0 minutes Project: maven Fix Fors: 1.0-rc1 Assignee: james strachan Reporter: Created: Thu, 20 Feb 2003 4:08 PM Updated: Thu, 3 Jun 2004 5:03 PM Environment: n/a Description: Eclipse allows the user to specify multiple source directories while project.xml only supports one sourceDirectory. That's why synchronizing eclipse .classpath file and project.xml appears problematic. Allowing maven users to specify multiple src dirs will allow to solve that issue in a rather easy way. [EMAIL PROTECTED] - 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: Adding SVN support to SCM and CruiseControl plugins
Go for it. Quoting Pugh Eric, Slough [EMAIL PROTECTED]: Hi all, Anyone have a reason why I shouldn't tweak the SCM and CruiseControl plugins to support Subversion? I am using a custom .jsl file to compile my cruisecontrol configuration file, and the CruiseControl plugin calls the scm:validate method which dies right now. Eric Pugh Scanned for viruses by MessageLabs. The integrity and security of this message cannot be guaranteed. This email is intended for the named recipient only, and may contain confidential information and proprietary material. Any unauthorised use or disclosure is prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1305) dependency id is never set. Clean up getId() method
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1305 Here is an overview of the issue: - Key: MAVEN-1305 Summary: dependency id is never set. Clean up getId() method Type: Improvement Status: Unassigned Priority: Trivial Original Estimate: 5 minutes Time Spent: Unknown Remaining: 5 minutes Project: maven Components: core Versions: 1.0-rc3 Assignee: Reporter: Jerome Lacoste Created: Thu, 3 Jun 2004 11:06 PM Updated: Thu, 3 Jun 2004 11:06 PM Description: setId() in the BaseObject class is overriden by setId() in the Dependency class. So I don't see how id can be set to a non null value. Clean up o.a.m.project.Dependency#getId() can be made. - 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-1305) dependency id is never set. Clean up getId() method
The following issue has been updated: Updater: Jerome Lacoste (mailto:[EMAIL PROTECTED]) Date: Thu, 3 Jun 2004 11:07 PM Comment: patch for the 1.0 branch Changes: Attachment changed to maven.1.0.final.dependency.cleanup.txt - For a full history of the issue, see: http://jira.codehaus.org/browse/MAVEN-1305?page=history - View the issue: http://jira.codehaus.org/browse/MAVEN-1305 Here is an overview of the issue: - Key: MAVEN-1305 Summary: dependency id is never set. Clean up getId() method Type: Improvement Status: Unassigned Priority: Trivial Original Estimate: 5 minutes Time Spent: Unknown Remaining: 5 minutes Project: maven Components: core Versions: 1.0-rc3 Assignee: Reporter: Jerome Lacoste Created: Thu, 3 Jun 2004 11:06 PM Updated: Thu, 3 Jun 2004 11:07 PM Description: setId() in the BaseObject class is overriden by setId() in the Dependency class. So I don't see how id can be set to a non null value. Clean up o.a.m.project.Dependency#getId() can be made. - 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-26) needed check incorrect
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPJAVADOC-26
Here is an overview of the issue:
-
Key: MPJAVADOC-26
Summary: needed check incorrect
Type: Bug
Status: Open
Priority: Minor
Original Estimate: 10 minutes
Time Spent: Unknown
Remaining: 10 minutes
Project: maven-javadoc-plugin
Versions:
1.5.1
Assignee: Jason van Zyl
Reporter: Denis McLaughlin
Created: Thu, 3 Jun 2004 11:46 PM
Updated: Thu, 3 Jun 2004 11:46 PM
Description:
The javadoc plugin has undergone some changes adding support for iterating across
the directories in the maven.compile.src.set path ref. However, there is an error in
the check:needed logic.
Line numbers below are against this version of the plugin:
http://cvs.apache.org/viewcvs.cgi/maven-plugins/javadoc/plugin.jelly?rev=1.42view=markup
The foreach loop at line 99 iterates across the directories in the
maven.compile.src.set. The test at line 101 reads:
j:if test=${needed == null}
If there are two directories in maven.compile.src.set, and the first directory has
no source files in it, then the first iteration of this loop will leave needed equal
to false. The second time through the loop, since needed is no longer equal to null,
the loop is short circuited, and, because needed is false, no processing is done, even
though there may be valid source files in the second directory.
Changing the test on line 101 to:
j:if test=${needed != true}
will correct this problem, short circuiting the loop only after the first directory
with valid source files is found.
Denis
-
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]
