cvs commit: maven/src/plugins-build/findbugs plugin.jelly
bwalding2003/08/29 16:15:15
Modified:src/plugins-build/findbugs plugin.jelly
Log:
Was using incorrect sourcepath variable
Revision ChangesPath
1.2 +4 -4 maven/src/plugins-build/findbugs/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven/src/plugins-build/findbugs/plugin.jelly,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- plugin.jelly 29 Aug 2003 01:55:48 - 1.1
+++ plugin.jelly 29 Aug 2003 23:15:15 - 1.2
@@ -21,10 +21,10 @@
-
-
+ debug="false"
+ outputFile="${maven.build.dir}/findbugs.xml">
+
+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/findbugs .cvsignore
bwalding2003/08/29 15:12:56 Added: src/plugins-build/findbugs/xdocs index.xml goals.xml changes.xml properties.xml navigation.xml src/plugins-build/findbugs .cvsignore Log: Documentation for the plugin Revision ChangesPath 1.1 maven/src/plugins-build/findbugs/xdocs/index.xml Index: index.xml === Maven FindBugs Plug-in Ben Walding FindBugs is a program to find bugs in Java programs. It looks for instances of "bug patterns" --- code instances that are likely to be errors. The plugin executes the FindBugs program against your code and generates a report similar to CheckStyle. Currently this report is display in the console window, but will ultimately be integrated into the site. 1.1 maven/src/plugins-build/findbugs/xdocs/goals.xml Index: goals.xml === FindBugs Plugin Goals James Strachan GoalDescription maven-findbugs-plugin:report This scans your compiled code, applies a set of bug pattern detection rules, then produces a report in xdoc format (only generates to console at present). 1.1 maven/src/plugins-build/findbugs/xdocs/changes.xml Index: changes.xml === Changes Ben Walding 1.1 maven/src/plugins-build/findbugs/xdocs/properties.xml Index: properties.xml === FindBugs Properties Ben Walding PropertyOptional?Description 1.1 maven/src/plugins-build/findbugs/xdocs/navigation.xml Index: navigation.xml === Maven FAQ Plugin http://maven.apache.org/"/> http://www.cs.umd.edu/~pugh/java/bugs/"/> 1.1 maven/src/plugins-build/findbugs/.cvsignore Index: .cvsignore === target - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/findbugs/xdocs - New directory
bwalding2003/08/29 15:12:54 maven/src/plugins-build/findbugs/xdocs - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dotuml][contribute] how to submit patch (legals)
[EMAIL PROTECTED] wrote, On 29/08/2003 2.11: Ok, we'll check those out too. Excellent. Then I can really start closing Alexandria, knowing that if there is someone interested in the codebase, it has already been contacted. I think we have already incorporated JavaSrc into one of our plugins (jxr). Not really, AFAIK jxr uses the old version, while javasrc is a new donation to the ASF. The other sounds useful too. It still needs work, I left it off at an early stage, but it still may interest you guys. Have fun! :-) -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-757) wrong paths for file:// deployment
The following issue has been updated:
Updater: Frank Wagner (mailto:[EMAIL PROTECTED])
Date: Fri, 29 Aug 2003 9:02 AM
Changes:
Attachment changed to patch.txt
-
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-757&page=history
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-757
Here is an overview of the issue:
-
Key: MAVEN-757
Summary: wrong paths for file:// deployment
Type: Bug
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
plugin-artifact
Versions:
1.0-rc1
Assignee:
Reporter: Frank Wagner
Created: Fri, 29 Aug 2003 8:54 AM
Updated: Fri, 29 Aug 2003 9:02 AM
Description:
I am looking at Maven HEAD.
The org.apache.maven.deploy.deployers.FileDeployer is a little confused about the
destination file path.
It generates the offset directory twice:
Instead of copying a file to
///
it uses
//s//s
The current code in deploy(DeployRequest) is
...
destFile = new File(destFile, request.dirname());
if (!destFile.exists())
{
destFile.mkdirs();
}
destFile = new File(destFile, request.getDestFile());
...
That should be replaced by something like:
...
if (destFile.getParentFile()!=null &&
!destFile.getParentFile().exists())
{
destFile.getParentFile().mkdirs();
}
destFile = new File(destFile, request.getDestFile());
...
Which fixed the problem for me.
Tschau,
Frank
-
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-757) wrong paths for file:// deployment
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-757
Here is an overview of the issue:
-
Key: MAVEN-757
Summary: wrong paths for file:// deployment
Type: Bug
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
plugin-artifact
Versions:
1.0-rc1
Assignee:
Reporter: Frank Wagner
Created: Fri, 29 Aug 2003 8:54 AM
Updated: Fri, 29 Aug 2003 8:54 AM
Description:
I am looking at Maven HEAD.
The org.apache.maven.deploy.deployers.FileDeployer is a little confused about the
destination file path.
It generates the offset directory twice:
Instead of copying a file to
///
it uses
//s//s
The current code in deploy(DeployRequest) is
...
destFile = new File(destFile, request.dirname());
if (!destFile.exists())
{
destFile.mkdirs();
}
destFile = new File(destFile, request.getDestFile());
...
That should be replaced by something like:
...
if (destFile.getParentFile()!=null &&
!destFile.getParentFile().exists())
{
destFile.getParentFile().mkdirs();
}
destFile = new File(destFile, request.getDestFile());
...
Which fixed the problem for me.
Tschau,
Frank
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-750) SnapshotSignature does not include currentVersion
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Fri, 29 Aug 2003 6:39 AM
Applied
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-750
Here is an overview of the issue:
-
Key: MAVEN-750
Summary: SnapshotSignature does not include currentVersion
Type: Bug
Status: Closed
Priority: Minor
Resolution: FIXED
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
plugin-jar
Fix Fors:
1.0-rc1
Versions:
1.0-beta-10
Assignee:
Reporter:
Created: Wed, 27 Aug 2003 1:41 PM
Updated: Fri, 29 Aug 2003 6:39 AM
Environment: WinXP, J2SE 1.3.1
Description:
class org.apache.maven.jelly.tags.maven.SnapshotSignature
method doTag
/**
* Process the tag. Create a variable in the current context of the format
* ${pom.id}-${pom.currentVersion}.MMdd.HHmmss
*
* @param output used to send XML output to Jelly
* @throws MissingAttributeException if the project property is not set
*/
public void doTag( XMLOutput output ) throws MissingAttributeException
{
...
String snapshotSignature = getProject().getArtifactId() + "-" + snapshotVersion;
...
}
This method does not appear to generate a snapshot JAR name that includes the current
version (as spec'd in the Javadoc).
Thanks for your help :)
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-745) plugin-war does not copy artifact properly when instructed under dependency, war.bundle.
The following comment has been added to this issue: Author: Emmanuel Venisse Created: Fri, 29 Aug 2003 6:29 AM Body: In beta10, you must you war.bundle.jar instead of war.bundle For your log4j dependency, you should declare it like this: log4j log4j 1.2.8 http://jakarta.apache.org/log4j/ true or log4j 1.2.8 http://jakarta.apache.org/log4j/ true - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-745 Here is an overview of the issue: - Key: MAVEN-745 Summary: plugin-war does not copy artifact properly when instructed under dependency, war.bundle. Type: Bug Status: Unassigned Priority: Major Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-war Versions: 1.0-beta-10 Assignee: Reporter: Created: Tue, 26 Aug 2003 1:25 PM Updated: Tue, 26 Aug 2003 1:25 PM Environment: Red Hat 9.0 Linux Description: I create the maven -D... appgen sample application. I update the POM project.xml with my specific information along with adding a src/webapp/WEB-INF/ directory to the project home. Then I add these two dependencies in the POM: servletapi 2.3 log4j log4j log4j 1.2.8 log4j-1.2.8.jar jar http://jakarta.apache.org/log4j/ true When I run "maven war" or "maven war:webapp" I do NOT get the log4j-1.2.8.jar in my WEB-INF/lib directory. I actually don't get anthing in that directory. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-752) Added a feature to ant's junit task to fork only once
The following comment has been added to this issue: Author: Emmanuel Venisse Created: Fri, 29 Aug 2003 6:19 AM Body: This patch must be post to the ant list. We don't modify the ant source for support the future versions. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-752 Here is an overview of the issue: - Key: MAVEN-752 Summary: Added a feature to ant's junit task to fork only once Type: Improvement Status: Unassigned Priority: Minor Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-ant Versions: 1.0-beta-10 Assignee: Reporter: Created: Wed, 27 Aug 2003 9:20 PM Updated: Wed, 27 Aug 2003 9:26 PM Description: If the ant-optional.jar in maven's lib directory is replaced with the attached jar and "maven.junit.fork" is set to "once", the junit task will only fork once and run all the tests in one new JVM. The files out of ant's junit task that were modified are also attached. Please integrate this into maven, this saves a lot of time when running lots of tests. - 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/src/java/org/apache/maven/jelly/tags/maven SnapshotSignature.java
evenisse2003/08/29 04:27:50 Modified:src/java/org/apache/maven/jelly/tags/maven SnapshotSignature.java Log: MAVEN-750. Add current version to snapshotSignature Revision ChangesPath 1.10 +4 -2 maven/src/java/org/apache/maven/jelly/tags/maven/SnapshotSignature.java Index: SnapshotSignature.java === RCS file: /home/cvs/maven/src/java/org/apache/maven/jelly/tags/maven/SnapshotSignature.java,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- SnapshotSignature.java19 Aug 2003 04:25:39 - 1.9 +++ SnapshotSignature.java29 Aug 2003 11:27:50 - 1.10 @@ -111,7 +111,9 @@ SimpleDateFormat formatter = new SimpleDateFormat( "MMdd.HHmmss" ); formatter.setTimeZone( TimeZone.getTimeZone( "GMT" ) ); String snapshotVersion = formatter.format( now ); -String snapshotSignature = getProject().getArtifactId() + "-" + snapshotVersion; +String snapshotSignature = getProject().getArtifactId() + "-" + + getProject().getCurrentVersion() + "-" + + snapshotVersion; context.setVariable( "snapshotSignature", snapshotSignature ); - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-756) cvs-usage.xml breaks on non-cvs scm URL
The following issue has been updated: Updater: Patrick Woodworth (mailto:[EMAIL PROTECTED]) Date: Fri, 29 Aug 2003 6:34 AM Comment: I'm attaching a patch which allows the cvs-usage.xml file to check whether the connection string is actually a CVS connection string before requesting that it be parsed. This fixed the issue for me. Changes: Attachment changed to svnrepo.patch - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-756&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-756 Here is an overview of the issue: - Key: MAVEN-756 Summary: cvs-usage.xml breaks on non-cvs scm URL Type: Bug Status: Unassigned Priority: Major Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-xdoc Assignee: Reporter: Patrick Woodworth Created: Fri, 29 Aug 2003 6:31 AM Updated: Fri, 29 Aug 2003 6:34 AM Description: When using a subversion URL for the repository connection element such as scm:svn:http://svn.foo.com/repos/foo, the cvs-usage.xml file in the xdoc plugin breaks because it assumes that if there is a repository, then it must be a CVS 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] Created: (MAVEN-756) cvs-usage.xml breaks on non-cvs scm URL
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-756 Here is an overview of the issue: - Key: MAVEN-756 Summary: cvs-usage.xml breaks on non-cvs scm URL Type: Bug Status: Unassigned Priority: Major Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-xdoc Assignee: Reporter: Patrick Woodworth Created: Fri, 29 Aug 2003 6:31 AM Updated: Fri, 29 Aug 2003 6:31 AM Description: When using a subversion URL for the repository connection element such as scm:svn:http://svn.foo.com/repos/foo, the cvs-usage.xml file in the xdoc plugin breaks because it assumes that if there is a repository, then it must be a CVS 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] Closed: (MAVEN-755) add maven.jar.compress
Message: The following issue has been closed. Resolver: Emmanuel Venisse Date: Fri, 29 Aug 2003 6:10 AM Applied. Thanks. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-755 Here is an overview of the issue: - Key: MAVEN-755 Summary: add maven.jar.compress Type: Wish Status: Closed Priority: Trivial Resolution: FIXED Time Spent: Unknown Remaining: 5 minutes Project: maven Components: plugin-jar Fix Fors: 1.0-rc1 Versions: 1.0-rc1 Assignee: Reporter: Joachim Bader Created: Fri, 29 Aug 2003 4:44 AM Updated: Fri, 29 Aug 2003 6:10 AM Environment: embedded Device (Debian Linux, Wonka Java VM, XScale) Description: The J2ME Java VM that I use on my embedded device can't handle compressed jar/zip files. The VM has no problems with uncompressed jar/zip 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]
cvs commit: maven/src/plugins-build/jar/xdocs changes.xml properties.xml
evenisse2003/08/29 03:58:45
Modified:src/plugins-build/jar plugin.jelly plugin.properties
src/plugins-build/jar/xdocs changes.xml properties.xml
Log:
Maven-755. Add maven.jar.compress
Revision ChangesPath
1.18 +1 -0 maven/src/plugins-build/jar/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven/src/plugins-build/jar/plugin.jelly,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- plugin.jelly 5 Aug 2003 08:11:47 - 1.17
+++ plugin.jelly 29 Aug 2003 10:58:45 - 1.18
@@ -28,6 +28,7 @@
jarfile="${maven.build.dir}/${maven.final.name}.jar"
basedir="${maven.build.dest}"
index="${maven.jar.index}"
+ compress="${maven.jar.compress}"
excludes="${maven.jar.excludes}">
1.6 +1 -0 maven/src/plugins-build/jar/plugin.properties
Index: plugin.properties
===
RCS file: /home/cvs/maven/src/plugins-build/jar/plugin.properties,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- plugin.properties 5 Aug 2003 08:11:47 - 1.5
+++ plugin.properties 29 Aug 2003 10:58:45 - 1.6
@@ -4,4 +4,5 @@
maven.jar.manifest.extensions.add=false
maven.jar.excludes = **/package.html
maven.jar.index=false
+maven.jar.compress=true
maven.remote.group=maven
1.5 +5 -0 maven/src/plugins-build/jar/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven/src/plugins-build/jar/xdocs/changes.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- changes.xml 29 Aug 2003 01:55:46 - 1.4
+++ changes.xml 29 Aug 2003 10:58:45 - 1.5
@@ -8,6 +8,11 @@
+
+
+Maven-755. Add maven.jar.compress.
+
+
Added maven.jar.index property
1.6 +5 -0 maven/src/plugins-build/jar/xdocs/properties.xml
Index: properties.xml
===
RCS file: /home/cvs/maven/src/plugins-build/jar/xdocs/properties.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- properties.xml5 Aug 2003 08:11:47 - 1.5
+++ properties.xml29 Aug 2003 10:58:45 - 1.6
@@ -96,6 +96,11 @@
project descriptor
+
+ maven.jar.compress
+ Yes
+ Not only store data but also compress them, defaults to true.
+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-755) add maven.jar.compress
The following issue has been updated: Updater: Joachim Bader (mailto:[EMAIL PROTECTED]) Date: Fri, 29 Aug 2003 4:46 AM Changes: Attachment changed to patch.diff - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-755&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-755 Here is an overview of the issue: - Key: MAVEN-755 Summary: add maven.jar.compress Type: Wish Status: Unassigned Priority: Trivial Time Spent: Unknown Remaining: 5 minutes Project: maven Components: plugin-jar Versions: 1.0-rc1 Assignee: Reporter: Joachim Bader Created: Fri, 29 Aug 2003 4:44 AM Updated: Fri, 29 Aug 2003 4:46 AM Environment: embedded Device (Debian Linux, Wonka Java VM, XScale) Description: The J2ME Java VM that I use on my embedded device can't handle compressed jar/zip files. The VM has no problems with uncompressed jar/zip 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]
Re: [dotuml][contribute] how to submit patch (legals)
[EMAIL PROTECTED] wrote, On 29/08/2003 2.11: Ok, we'll check those out too. Excellent. Then I can really start closing Alexandria, knowing that if there is someone interested in the codebase, it has already been contacted. I think we have already incorporated JavaSrc into one of our plugins (jxr). Not really, AFAIK jxr uses the old version, while javasrc is a new donation to the ASF. The other sounds useful too. It still needs work, I left it off at an early stage, but it still may interest you guys. Have fun! :-) -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-755) add maven.jar.compress
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-755 Here is an overview of the issue: - Key: MAVEN-755 Summary: add maven.jar.compress Type: Wish Status: Unassigned Priority: Trivial Time Spent: Unknown Remaining: 5 minutes Project: maven Components: plugin-jar Versions: 1.0-rc1 Assignee: Reporter: Joachim Bader Created: Fri, 29 Aug 2003 4:44 AM Updated: Fri, 29 Aug 2003 4:44 AM Environment: embedded Device (Debian Linux, Wonka Java VM, XScale) Description: The J2ME Java VM that I use on my embedded device can't handle compressed jar/zip files. The VM has no problems with uncompressed jar/zip 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]
cvs commit: maven/xdocs/reference project-descriptor.xml
vmassol 2003/08/29 00:28:33 Modified:xdocs/reference project-descriptor.xml Log: Mark integrationUnitTestSourceDirectory as deprecated. Revision ChangesPath 1.27 +6 -6 maven/xdocs/reference/project-descriptor.xml Index: project-descriptor.xml === RCS file: /home/cvs/maven/xdocs/reference/project-descriptor.xml,v retrieving revision 1.26 retrieving revision 1.27 diff -u -r1.26 -r1.27 --- project-descriptor.xml28 Aug 2003 23:37:39 - 1.26 +++ project-descriptor.xml29 Aug 2003 07:28:33 - 1.27 @@ -788,12 +788,12 @@ integrationUnitTestSourceDirectory -This element specifies a directory containing the -integration unit test source of the project. The generated -build system will compile these directories when the project -is being tested. The integration unit tests must use the -Cactus test framework. -The path given is relative to the project descriptor. +This element is deprecated and should no longer be used. +Initially it was used by the first Cactus plugin. Now +the location of the Cactus test sources is defined +through a plugin property. See the +http://maven.apache.org/reference/plugins/cactus/properties.html";>Cactus +plugin properties page. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-548) Clarify usage of documentation/reporting properties
Message: The following issue has been closed. Resolver: dion gillard Date: Fri, 29 Aug 2003 1:57 AM Commited to CVS today - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-548 Here is an overview of the issue: - Key: MAVEN-548 Summary: Clarify usage of documentation/reporting properties Type: Improvement Status: Closed Priority: Major Resolution: FIXED Time Spent: Unknown Remaining: Unknown Project: maven Fix Fors: 1.0-rc1 Assignee: Reporter: Jason van Zyl Created: Fri, 4 Jul 2003 10:30 AM Updated: Fri, 29 Aug 2003 1:57 AM Description: As time has passed I think it has become apparent that reporting is key feature of Maven and as such I think it's time to push all of the properties for reporting and documentation to a place where they can be easily accessed. Currently we have a lot of the properties baked into the xdoc plugin which no long makes sense. We need a clean set of properties for docs and reports and make them generally accessible. Properties that would be in the same class as maven.repo.local. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-754) Pluggable search form in the nav bar
The following comment has been added to this issue: Author: Martin Skopp Created: Fri, 29 Aug 2003 1:43 AM Body: I like the idea! +1 Please consider to make it so flexible that the search engine ht://Dig ( http://www.htdig.org/ ) could be used as well - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-754 Here is an overview of the issue: - Key: MAVEN-754 Summary: Pluggable search form in the nav bar Type: Wish Status: Unassigned Priority: Minor Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-xdoc Fix Fors: 1.1 Versions: 1.0-rc1 Assignee: Reporter: Created: Thu, 28 Aug 2003 5:39 PM Updated: Thu, 28 Aug 2003 8:32 PM Environment: win xp, jdk 1.4.2 Description: It would be great to be able to plug in different search engines into the nav bar (as opposed to just google.com). For example, my maven sites will be deployed internally and we have an Ultraseek server that I'm using to index the sites. Right now I can doctor up my version of the site plugin, but it would be nice to be able to vary this on a per-project basis. If someone will point me in the right direction, I'll be happy to give it a try... Thanks! - Paul - 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/src/plugins-build/jdiff/xdocs changes.xml
dion2003/08/28 23:27:54 Modified:src/plugins-build/javadoc plugin.jelly plugin.properties src/plugins-build/clover/xdocs changes.xml src/plugins-build/word2html/xdocs/current changes.xml src/plugins-build/pdf/xdocs changes.xml src/plugins-build/xdoc plugin.jelly plugin.properties src/plugins-build/linkcheck/xdocs changes.xml src/plugins-build/pdf project.xml plugin.jelly src/plugins-build/docbook plugin.jelly src/plugins-build/jxr plugin.properties src/plugins-build/docbook/xdocs changes.xml src/plugins-build/multiproject/xdocs/current changes.xml src/plugins-build/checkstyle plugin.jelly src/plugins-build/jdiff project.xml plugin.jelly src/plugins-build/xdoc/xdocs changes.xml src/plugins-build/linkcheck plugin.jelly src/plugins-build/clover plugin.jelly src/plugins-build/ashkelon plugin.jelly project.xml src/plugins-build/statcvs plugin.jelly src/plugins-build/dist/xdocs changes.xml src/plugins-build/word2html plugin.jelly src/plugins-build/jellydoc/xdocs changes.xml src/plugins-build/multiproject plugin.jelly src/plugins-build/jxr/xdocs changes.xml src/plugins-build/license/xdocs changes.xml src/plugins-build/tasklist plugin.jelly src/plugins-build/tasklist/xdocs changes.xml src/plugins-build/javadoc/xdocs changes.xml src/plugins-build/site/xdocs changes.xml src/plugins-build/dist plugin.jelly src/plugins-build/statcvs/xdocs changes.xml src/plugins-build/jellydoc plugin.jelly src/plugins-build/license plugin.jelly src/plugins-build/site plugin.jelly src/plugins-build/changes/xdocs changes.xml src/plugins-build/changes plugin.jelly src/plugins-build/faq plugin.jelly project.xml src/plugins-build/checkstyle/xdocs changes.xml Added: src/plugins-build/ashkelon/xdocs changes.xml src/plugins-build/faq/xdocs changes.xml src/plugins-build/jdiff/xdocs changes.xml Log: MAVEN-548. Move common reporting properties to defaults Revision ChangesPath 1.20 +1 -1 maven/src/plugins-build/javadoc/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven/src/plugins-build/javadoc/plugin.jelly,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- plugin.jelly 22 Aug 2003 08:43:57 - 1.19 +++ plugin.jelly 29 Aug 2003 06:27:51 - 1.20 @@ -193,7 +193,7 @@ - + + +update to use maven.docs.*/maven.gen.docs + Fixed MAVEN-493. I register reports only if source, test,... exists. So, corresponding entrys in menu will appear only if reports are registered. 1.2 +4 -0 maven/src/plugins-build/word2html/xdocs/current/changes.xml Index: changes.xml === RCS file: /home/cvs/maven/src/plugins-build/word2html/xdocs/current/changes.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- changes.xml 28 Aug 2003 07:03:02 - 1.1 +++ changes.xml 29 Aug 2003 06:27:51 - 1.2 @@ -7,6 +7,10 @@ + + update to use maven.docs.*/maven.gen.docs + + Correctly handle files with .. in the names 1.4 +5 -1 maven/src/plugins-build/pdf/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven/src/plugins-build/pdf/xdocs/changes.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- changes.xml 12 Mar 2003 16:03:06 - 1.3 +++ changes.xml 29 Aug 2003 06:27:51 - 1.4 @@ -6,7 +6,11 @@ - + + update to use maven.docs.*/maven.gen.docs + + + Upgraded to xerces 2.3.0, xalan 2.4.1 and fop 0.20.5rc2 1.43 +3 -9 maven/src/plugins-build/xdoc/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven/src/plugins-build/xdoc/plugin.jelly,v retrieving revision 1.42 retrieving revision 1.43 diff -u -r1.42 -r1.43 --- plugin.jelly 21 Aug 2003 09:01:08 - 1.42 +++ plugin.jelly 29 Aug 2003 06:27:51 - 1.43 @@ -139,23 +139,17 @@
Results of clean bootstrap at 20030829-0121
Last 500 lines of a clean bootstrap build of maven at 20030829-0121 [exec] java:jar-resources: [exec] Copying 1 file to /usr/local/builds/maven/src/maven/src/plugins-build/webserver/target/classes/plugin-resources [exec] Copying 4 files to /usr/local/builds/maven/src/maven/src/plugins-build/webserver/target/classes [exec] test:prepare-filesystem: [exec] [mkdir] Created dir: /usr/local/builds/maven/src/maven/src/plugins-build/webserver/target/test-classes [exec] [mkdir] Created dir: /usr/local/builds/maven/src/maven/src/plugins-build/webserver/target/test-reports [exec] test:test-resources: [exec] test:compile: [exec] [echo] No test source files to compile. [exec] test:test: [exec] [echo] No tests to run. [exec] jar:jar: [exec] [jar] Building jar: /usr/local/builds/maven/src/maven/src/plugins-build/webserver/target/maven-webserver-plugin-2.0-dev.jar [exec] [copy] Copying 1 file to /home/tirsen/.maven/repository/maven/jars [exec] + [exec] | Building Maven Wizard Plug-in [exec] | Memory: 139M/149M [exec] + [exec] clean:clean: [exec] clean: [exec] plugin: [exec] java:prepare-filesystem: [exec] [mkdir] Created dir: /usr/local/builds/maven/src/maven/src/plugins-build/wizard/target/classes [exec] java:compile: [exec] [echo] Compiling to /usr/local/builds/maven/src/maven/src/plugins-build/wizard/target/classes [exec] [echo] No java source files to compile. [exec] java:jar-resources: [exec] Copying 2 files to /usr/local/builds/maven/src/maven/src/plugins-build/wizard/target/classes [exec] test:prepare-filesystem: [exec] [mkdir] Created dir: /usr/local/builds/maven/src/maven/src/plugins-build/wizard/target/test-classes [exec] [mkdir] Created dir: /usr/local/builds/maven/src/maven/src/plugins-build/wizard/target/test-reports [exec] test:test-resources: [exec] test:compile: [exec] [echo] No test source files to compile. [exec] test:test: [exec] [echo] No tests to run. [exec] jar:jar: [exec] [jar] Building jar: /usr/local/builds/maven/src/maven/src/plugins-build/wizard/target/maven-wizard-plugin-1.0.jar [exec] [copy] Copying 1 file to /home/tirsen/.maven/repository/maven/jars [exec] + [exec] | Building Maven Word to HTML Plug-in [exec] | Memory: 137M/149M [exec] + [exec] clean:clean: [exec] clean: [exec] plugin: [exec] java:prepare-filesystem: [exec] [mkdir] Created dir: /usr/local/builds/maven/src/maven/src/plugins-build/word2html/target/classes [exec] java:compile: [exec] [echo] Compiling to /usr/local/builds/maven/src/maven/src/plugins-build/word2html/target/classes [exec] [echo] No java source files to compile. [exec] java:jar-resources: [exec] Copying 1 file to /usr/local/builds/maven/src/maven/src/plugins-build/word2html/target/classes/plugin-resources [exec] Copying 4 files to /usr/local/builds/maven/src/maven/src/plugins-build/word2html/target/classes [exec] test:prepare-filesystem: [exec] [mkdir] Created dir: /usr/local/builds/maven/src/maven/src/plugins-build/word2html/target/test-classes [exec] [mkdir] Created dir: /usr/local/builds/maven/src/maven/src/plugins-build/word2html/target/test-reports [exec] test:test-resources: [exec] test:compile: [exec] [echo] No test source files to compile. [exec] test:test: [exec] [echo] No tests to run. [exec] jar:jar: [exec] [jar] Building jar: /usr/local/builds/maven/src/maven/src/plugins-build/word2html/target/maven-word2html-plugin-1.4-SNAPSHOT.jar [exec] [copy] Copying 1 file to /home/tirsen/.maven/repository/maven/jars [exec] + [exec] | Building Maven XDoc Plug-in [exec] | Memory: 144M/149M [exec] + [exec] clean:clean: [exec] clean: [exec] plugin: [exec] java:prepare-filesystem: [exec] [mkdir] Created dir: /usr/local/builds/maven/src/maven/src/plugins-build/xdoc/target/classes [exec] java:compile: [exec] [echo] Compiling to /usr/local/builds/maven/src/maven/src/plugins-build/xdoc/target/classes [exec] [javac] Compiling 3 source files to /usr/local/builds/maven/src/maven/src/plugins-build/xdoc/target/classes [exec] java:jar-resources: [exec] Copying 105 files to /usr/local/builds/maven/src/maven/src/plugins-build/xdoc/target/classes/plugin-resources [exec] Copied 1 empty directory to /usr/local/builds/maven/src/maven/src/plugins-build/xdoc/target/classes/plugin-resources
cvs commit: maven/xdocs/reference user-guide.xml
dion2003/08/28 23:26:23
Modified:xdocschanges.xml
xdocs/reference user-guide.xml
Log:
MAVEN-548. Move common reporting properties to defaults
Revision ChangesPath
1.14 +5 -0 maven/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven/xdocs/changes.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- changes.xml 20 Jun 2003 12:54:05 - 1.13
+++ changes.xml 29 Aug 2003 06:26:23 - 1.14
@@ -8,6 +8,11 @@
+
+
+Move maven.docs.* and maven.gen.docs to defaults.properties instead of xdoc
plugin
+
+
Added the new POM marshaller and unmarshaller based on the xpp3
xmlpull parser. This eliminates betwixt and friends from the POM
1.61 +42 -0 maven/xdocs/reference/user-guide.xml
Index: user-guide.xml
===
RCS file: /home/cvs/maven/xdocs/reference/user-guide.xml,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -r1.60 -r1.61
--- user-guide.xml19 Aug 2003 05:49:14 - 1.60
+++ user-guide.xml29 Aug 2003 06:26:23 - 1.61
@@ -628,6 +628,48 @@
+ maven.docs.dest
+
+The output directory for the generated html from reports.
+
+ ${maven.build.dir}/docs
+
+
+
+ maven.docs.omitXmlDeclaration
+
+Whether generated documentation should have an xml declaration, e.g.
+
+
+ false
+
+
+
+ maven.docs.outputencoding
+
+The character encoding for generated documentation
+
+ ISO-8859-1
+
+
+
+ maven.docs.src
+
+The directory for user supplied documentation.
+
+ ${basedir}/xdocs
+
+
+
+ maven.gen.docs
+
+The directory where generated xdocs that need to be transformed to
html
+are placed.
+
+ ${maven.build.dir}/generated-xdocs
+
+
+
maven.home.local
The directory on the local machine maven uses to write user
specific details
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/conf defaults.properties
dion2003/08/28 23:26:06
Modified:src/conf defaults.properties
Log:
MAVEN-548. Move common reporting properties to defaults
Revision ChangesPath
1.8 +10 -0 maven/src/conf/defaults.properties
Index: defaults.properties
===
RCS file: /home/cvs/maven/src/conf/defaults.properties,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- defaults.properties 19 Aug 2003 05:48:47 - 1.7
+++ defaults.properties 29 Aug 2003 06:26:06 - 1.8
@@ -15,6 +15,16 @@
maven.compile.optimize = off
maven.compile.deprecation = off
+# --
+# R E P O R T I N G P R O P E R T I E S
+# --
+maven.docs.src = ${basedir}/xdocs
+maven.docs.dest = ${maven.build.dir}/docs
+maven.docs.outputencoding = ISO-8859-1
+maven.docs.omitXmlDeclaration=false
+maven.gen.docs = ${maven.build.dir}/generated-xdocs
+
+
# ---
# M A V E N L O C A L R E P O
# ---
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-548) Clarify usage of documentation/reporting properties
The following comment has been added to this issue: Author: dion gillard Created: Fri, 29 Aug 2003 12:26 AM Body: Ok from this list, the suggestion is: Move to defaults: maven.docs.src maven.docs.dest maven.docs.outputencoding maven.gen.docs The rest of the properties stay in the plugin as noone else is using them. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-548 Here is an overview of the issue: - Key: MAVEN-548 Summary: Clarify usage of documentation/reporting properties Type: Improvement Status: Unassigned Priority: Major Time Spent: Unknown Remaining: Unknown Project: maven Fix Fors: 1.0-rc1 Assignee: Reporter: Jason van Zyl Created: Fri, 4 Jul 2003 10:30 AM Updated: Thu, 24 Jul 2003 1:49 PM Description: As time has passed I think it has become apparent that reporting is key feature of Maven and as such I think it's time to push all of the properties for reporting and documentation to a place where they can be easily accessed. Currently we have a lot of the properties baked into the xdoc plugin which no long makes sense. We need a clean set of properties for docs and reports and make them generally accessible. Properties that would be in the same class as maven.repo.local. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-548) Clarify usage of documentation/reporting properties
The following comment has been added to this issue: Author: dion gillard Created: Fri, 29 Aug 2003 12:22 AM Body: Some more missing on maven.gen.docs - html2xdoc - linkcheck - docbook - javadoc - jellydoc - license - asheklon - tasklist - changelog - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-548 Here is an overview of the issue: - Key: MAVEN-548 Summary: Clarify usage of documentation/reporting properties Type: Improvement Status: Unassigned Priority: Major Time Spent: Unknown Remaining: Unknown Project: maven Fix Fors: 1.0-rc1 Assignee: Reporter: Jason van Zyl Created: Fri, 4 Jul 2003 10:30 AM Updated: Thu, 24 Jul 2003 1:49 PM Description: As time has passed I think it has become apparent that reporting is key feature of Maven and as such I think it's time to push all of the properties for reporting and documentation to a place where they can be easily accessed. Currently we have a lot of the properties baked into the xdoc plugin which no long makes sense. We need a clean set of properties for docs and reports and make them generally accessible. Properties that would be in the same class as maven.repo.local. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-548) Clarify usage of documentation/reporting properties
The following comment has been added to this issue: Author: dion gillard Created: Fri, 29 Aug 2003 12:18 AM Body: Usage by other plugins: properties -- maven.docs.outputencoding - faq - file-activity - developer-activity - html2xdoc - linkcheck - changelog - changes - multiproject - tasklist - jellydoc - checkstyle - javadoc - hibernate maven.docs.src - plugin - pdf - changes - multiproject maven.docs.dest - linkcheck - pdf - site - pmd - dist - word2html - statcvs - multiproject - jdiff - clover - jxr - javadoc maven.xdoc.src - linkcheck maven.gen.docs - multiproject goals/tags - xdoc:performJSL - linkcheck xdoc:init - word2html - html2xdoc - jdiff - docbook - pdf - javadoc - site - dist - license - tasklist xdoc:jellyTransform - linkcheck xdoc:register-reports - site - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-548 Here is an overview of the issue: - Key: MAVEN-548 Summary: Clarify usage of documentation/reporting properties Type: Improvement Status: Unassigned Priority: Major Time Spent: Unknown Remaining: Unknown Project: maven Fix Fors: 1.0-rc1 Assignee: Reporter: Jason van Zyl Created: Fri, 4 Jul 2003 10:30 AM Updated: Thu, 24 Jul 2003 1:49 PM Description: As time has passed I think it has become apparent that reporting is key feature of Maven and as such I think it's time to push all of the properties for reporting and documentation to a place where they can be easily accessed. Currently we have a lot of the properties baked into the xdoc plugin which no long makes sense. We need a clean set of properties for docs and reports and make them generally accessible. Properties that would be in the same class as maven.repo.local. - 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-697) linkcheck plugin fails (in HEAD)
The following issue has been updated: Updater: dion gillard (mailto:[EMAIL PROTECTED]) Date: Thu, 28 Aug 2003 11:51 PM Comment: Looks like classloader isolation again Changes: Fix Version changed to 1.1 Fix Version changed from 1.0-rc1 - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-697&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-697 Here is an overview of the issue: - Key: MAVEN-697 Summary: linkcheck plugin fails (in HEAD) Type: Bug Status: Unassigned Priority: Major Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-linkcheck Fix Fors: 1.1 Versions: maven-new-unreleased Assignee: Reporter: Norbert Pabis Created: Wed, 20 Aug 2003 4:37 AM Updated: Thu, 28 Aug 2003 11:51 PM Environment: Java 1.4.2, Linux Description: I have neither custom xdocs nor maven goals, just plain projext.xml. While 'maven site' linkcheck fails with this: BUILD FAILED java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:230) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:145) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at 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 com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at com.werken.werkz.jelly.AttainGoalTag.doTag(AttainGoalTag.java:134) 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 org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:88) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:145) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:88) 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.PostGoalTag$1.firePostGoal(PostGoalTag.java:87) at com.werken.werkz.Goal.firePostGoalCallbacks(Goal.java:710) at com.werken.werkz.Goal.fire(Goal.java:654) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at com.werken.werkz.jelly.AttainGoalTag.doTag(AttainGoalTag.java:134) 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 com.werken.werkz.Goal.attainPrecursors(Goal.java:488) at com.werken.werkz.Goal.attain(Goal.java:573) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at com.werken.werkz.jelly.AttainGoalTag.doTag(AttainGoalTag.java:134) at org.apache.maven.jelly.tags.werkz.LazyAttainGoalTag.doTag(LazyAttainGoalTag.java:107) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:2
Re: Questions about the maven-new core
On Thu, 2003-08-28 at 20:26, [EMAIL PROTECTED] wrote: > So Jason, > > does this mean that maven-new is effectively over? If you mean is the plexus version of maven dead then the answer is most certainly not. But what's in that repository isn't of much use. I've been running Continuum for a week now using come refactored/rewritten components that started in maven-new. When Continuum is healthy I will release those components. I'm also convinced that what's there is effectively useless without plexus documentation. What I've got here shouldn't be considered any sort of replacement for 1.0. As we've seen before putting my experiments into CVS before maturity isn't of much use to anyone so I'm removing maven-new to keep anyone from going down the wrong path. > -- > dIon Gillard, Multitask Consulting > Blog: http://blogs.codehaus.org/people/dion/ > > > Alex Karasulu <[EMAIL PROTECTED]> wrote on 29/08/2003 05:00:54 AM: > > > At 02:06 PM 8/28/2003 -0400, you wrote: > > >On Thu, 2003-08-28 at 12:32, Alex Karasulu wrote: > > > > Hello, > > > > > > > > > > > > > > > > I'm very interested in helping with the new maven server project to > > > > basically Avalonize ;-) maven. Dion had pointed it out to me after > I > > > > approached him with a similar idea. I would like to get to the > point of > > > > submitting patches very soon. > > > > > >I will actually be moving that whole repository out soon. I have > > >refactored most of the pieces into Plexus components which I am using > > >for Continuum (continuous integration tool). What's in maven-new will > be > > >removed. I'm making plexus components and Ben is moving fetch over to > > >codehaus. > > > > fetch? What is that? Also where can I get at Continuum? > > > > >You'll just have to be patient because 1.0 is more important right now > > >the component'ized verson will be 2.0 and based on Plexus. I will post > > >messages when the maven-new repo is removed and the components surface > > >again. > > > > I was about to start a new sourceforge project just for building out > these > > components. Rather than do it on my own I thought I would contact you > and > > join the effort. How long do you think I'll have to wait before these > > components surface again? Is there any direction you can give in the > > interim - perhaps I can study some existing code base somewhere to > prepare > > to help when you are free? > > > > Alex > > > > >-- > > >jvz. > > > > > >Jason van Zyl > > >[EMAIL PROTECTED] > > >http://tambora.zenplex.org > > > > > >In short, man creates for himself a new religion of a rational > > >and technical order to justify his work and to be justified in it. > > > > > > -- Jacques Ellul, The Technological Society > > > > > > > > >- > > >To unsubscribe, e-mail: [EMAIL PROTECTED] > > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/jar/xdocs/current changes.xml
dion2003/08/28 19:10:06 Modified:src/plugins-build/jar project.xml src/plugins-build/jar/xdocs/current changes.xml Log: Ready for continuing work Revision ChangesPath 1.10 +1 -1 maven/src/plugins-build/jar/project.xml Index: project.xml === RCS file: /home/cvs/maven/src/plugins-build/jar/project.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- project.xml 29 Aug 2003 01:55:45 - 1.9 +++ project.xml 29 Aug 2003 02:10:06 - 1.10 @@ -5,7 +5,7 @@ 3 maven-jar-plugin Maven Jar Plug-in - 1.1 + 1.2-SNAPSHOT Java Project Management Tools http://maven.apache.org/reference/plugins/jar/ 1.2 +4 -0 maven/src/plugins-build/jar/xdocs/current/changes.xml Index: changes.xml === RCS file: /home/cvs/maven/src/plugins-build/jar/xdocs/current/changes.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- changes.xml 29 Aug 2003 01:55:46 - 1.1 +++ changes.xml 29 Aug 2003 02:10:06 - 1.2 @@ -8,6 +8,10 @@ + + + + Added maven.jar.index property - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/jar/xdocs navigation.xml
dion2003/08/28 19:06:07 Modified:src/plugins-build/jar/xdocs navigation.xml Log: Open by default Revision ChangesPath 1.4 +1 -1 maven/src/plugins-build/jar/xdocs/navigation.xml Index: navigation.xml === RCS file: /home/cvs/maven/src/plugins-build/jar/xdocs/navigation.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- navigation.xml29 Aug 2003 01:55:46 - 1.3 +++ navigation.xml29 Aug 2003 02:06:06 - 1.4 @@ -13,7 +13,7 @@ - + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/jar/xdocs/releases/v1.1 navigation.xml
dion2003/08/28 18:56:00 Removed: src/plugins-build/jar/xdocs/releases/v1.1 navigation.xml Log: Prep for bug fix release - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/findbugs - New directory
bwalding2003/08/28 18:55:45 maven/src/plugins-build/findbugs - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/jar/xdocs changes.xml navigation.xml
dion2003/08/28 18:55:46
Modified:src/plugins-build/jar project.xml
src/plugins-build/jar/xdocs changes.xml navigation.xml
Added: src/plugins-build/jar/announcements 1.1.ann
src/plugins-build/jar/xdocs/releases/v1.1 changes.xml
navigation.xml index.xml .cvsignore goals.xml
properties.xml
src/plugins-build/jar/xdocs/current properties.xml
changes.xml goals.xml index.xml
Log:
Prep for bug fix release
Revision ChangesPath
1.1 maven/src/plugins-build/jar/announcements/1.1.ann
Index: 1.1.ann
===
The Maven team is pleased to announce the Jar plugin 1.1 release!
http://maven.apache.org/reference/plugins/jar/index.html
The Maven Jar plugin is a core plugin of Maven that assists in creating jar files.
This release is a bug fix release to allow users of Maven 1.0-beta10 to update their
local
installation. The default for creating a jar index is now false.
Changes in this version:
o Added maven.jar.index property
o Upgrade to velocity 1.4-dev
You can download the Jar plugin here:
http://www.ibiblio.org/maven/maven/plugins/maven-jar-plugin-1.1.jar
Have fun!
-dIon
1.1 maven/src/plugins-build/jar/xdocs/releases/v1.1/changes.xml
Index: changes.xml
===
Changes
Emmanuel Venisse
dIon Gillard
Added maven.jar.index property
Upgrade to velocity 1.4-dev
Initial plugin created. Goals are move from java plugin.
1.1 maven/src/plugins-build/jar/xdocs/releases/v1.1/navigation.xml
Index: navigation.xml
===
Maven Jar Plugin
http://maven.apache.org/"/>
http://java.sun.com/"/>
1.1 maven/src/plugins-build/jar/xdocs/releases/v1.1/index.xml
Index: index.xml
===
Maven Jar Plug-in
Jason van Zyl
Emmanuel Venisse
This plug-in provides your basic Jar facilities.
For more information on the functionality provided by this plugin,
please see the Goals document.
For more information on how to customise the functionality provided
by this plugin, please see the properties
document.
1.1 maven/src/plugins-build/jar/xdocs/releases/v1.1/.cvsignore
Index: .cvsignore
===
stylesheets
1.1 maven/src/plugins-build/jar/xdocs/releases/v1.1/goals.xml
Index: goals.xml
===
Maven Java Plug-in Goals
dIon Gillard
Kurt Schrader
Emmanuel Venisse
GoalDescription
jar:jar
Launch jar:jar goal.
jar:jar
Creates a jar file in the Maven build directory with the
form ${project.id}-${project.currentVersion}.jar where
the id and currentVersion are taken from the project.xml
of the project being built.
jar:snapshot
Creates a jar file in the Maven build directory with the
form ${project.id}-MMDD.hhmmss.jar where
id - taken from the project.xml
of the project being built
MMDD - The current year in 8 digit format
hhmmss - the current time in 6 digit format
jar:deploy-snapshot
Deploy a snapshot jar to the remote repository
jar:deploy
Deploy a jar to the remote repository. The jar is built using
the java:jar goal
jar:install
Install a jar into the local repository. The jar is built using
the java:jar goal
jar:install-snapshot
Install a jar into the local repository. The jar is built using
the jar:snapshot goal a
cvs commit: maven/src/plugins-build/findbugs plugin.jelly maven.xml project.properties project.xml plugin.properties
bwalding2003/08/28 18:55:48
Added: src/plugins-build/findbugs plugin.jelly maven.xml
project.properties project.xml plugin.properties
Log:
First cut of a findbugs plugin. For the time being
* Won't create a report
* Will generate text output in your maven run
* Will require a monolithic (automatic) download of findbugs distribution
* We need to look at licensing (it's LGPL, but I repackaged the findbugs dist
will only be a minor issue at most). I have posted to findbugs list to
try and find out what versions of bcel / dom4j they use - then we can start to
disassemble the big dist into dependencies.
Revision ChangesPath
1.1 maven/src/plugins-build/findbugs/plugin.jelly
Index: plugin.jelly
===
1.1 maven/src/plugins-build/findbugs/maven.xml
Index: maven.xml
===
1.1 maven/src/plugins-build/findbugs/project.properties
Index: project.properties
===
# ---
# P R O J E C T P R O P E R T I E S
# ---
maven.xdoc.date=left
maven.xdoc.version=${pom.currentVersion}
1.1 maven/src/plugins-build/findbugs/project.xml
Index: project.xml
===
${basedir}/../project.xml
3
maven-findbugs-plugin
Maven FindBugs Plug-in
1.0-SNAPSHOT
FindBugs report plugin
http://maven.apache.org/reference/plugins/findbugs/
/www/maven.apache.org/reference/plugins/findbugs/
scm:cvs:pserver:[EMAIL
PROTECTED]:/home/cvspublic:maven/src/plugins-build/findbugs/
http://cvs.apache.org/viewcvs/maven/src/plugins-build/findbugs/
findbugs:findbugs-plugin
0.6.5
zip
findbugs:findbugs-ant
0.6.5
root
1.1 maven/src/plugins-build/findbugs/plugin.properties
Index: plugin.properties
===
# ---
# P L U G I N P R O P E R I E S
# ---
# LinkCheck report plugin.
# ---
maven.build.dir = ${basedir}/target
maven.docs.dest = ${maven.build.dir}/docs
maven.docs.outputencoding = ISO-8859-1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/jar/xdocs/releases - New directory
dion2003/08/28 18:55:14 maven/src/plugins-build/jar/xdocs/releases - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/jar/xdocs/releases/v1.1 - New directory
dion2003/08/28 18:55:14 maven/src/plugins-build/jar/xdocs/releases/v1.1 - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/jar/xdocs/current - New directory
dion2003/08/28 18:54:36 maven/src/plugins-build/jar/xdocs/current - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/jar/announcements - New directory
dion2003/08/28 18:54:12 maven/src/plugins-build/jar/announcements - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Questions about the maven-new core
So Jason, does this mean that maven-new is effectively over? -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Alex Karasulu <[EMAIL PROTECTED]> wrote on 29/08/2003 05:00:54 AM: > At 02:06 PM 8/28/2003 -0400, you wrote: > >On Thu, 2003-08-28 at 12:32, Alex Karasulu wrote: > > > Hello, > > > > > > > > > > > > I'm very interested in helping with the new maven server project to > > > basically Avalonize ;-) maven. Dion had pointed it out to me after I > > > approached him with a similar idea. I would like to get to the point of > > > submitting patches very soon. > > > >I will actually be moving that whole repository out soon. I have > >refactored most of the pieces into Plexus components which I am using > >for Continuum (continuous integration tool). What's in maven-new will be > >removed. I'm making plexus components and Ben is moving fetch over to > >codehaus. > > fetch? What is that? Also where can I get at Continuum? > > >You'll just have to be patient because 1.0 is more important right now > >the component'ized verson will be 2.0 and based on Plexus. I will post > >messages when the maven-new repo is removed and the components surface > >again. > > I was about to start a new sourceforge project just for building out these > components. Rather than do it on my own I thought I would contact you and > join the effort. How long do you think I'll have to wait before these > components surface again? Is there any direction you can give in the > interim - perhaps I can study some existing code base somewhere to prepare > to help when you are free? > > Alex > > >-- > >jvz. > > > >Jason van Zyl > >[EMAIL PROTECTED] > >http://tambora.zenplex.org > > > >In short, man creates for himself a new religion of a rational > >and technical order to justify his work and to be justified in it. > > > > -- Jacques Ellul, The Technological Society > > > > > >- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: [dotuml][contribute] how to submit patch (legals)
Ok, we'll check those out too. I think we have already incorporated JavaSrc into one of our plugins (jxr). The other sounds useful too. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote on 28/08/2003 06:45:28 PM: > > [EMAIL PROTECTED] wrote, On 28/08/2003 9.12: > > > > It looks to me like the umlgraph license is compatible with ASF guidelines. > > > > Can someone on licensing@ give me a definite answer? > > There is already a system that does this at Apache, under > jakarta-alexandria. > In fact, I'm in the process of closing down the project in accord with > the Jakarta PMC. > > In that project, there are two things that may interest Maven: > > - JavaSrc -> generates colored html from java files with a low memory > two pass system and full cross-indexing > - XmlDoclet > and stylesheets -> generate xml version of javadocs and have >stylesheets (comprising a xml2dot one) that >transform in various formats > > > -- > Nicola Ken Barozzi [EMAIL PROTECTED] > - verba volant, scripta manent - > (discussions get forgotten, just code remains) > - > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
[jira] Updated: (MAVEN-754) Pluggable search form in the nav bar
The following issue has been updated: Updater: dion gillard (mailto:[EMAIL PROTECTED]) Date: Thu, 28 Aug 2003 8:32 PM Comment: You'd need to add a property to the site plugin, used by site.jsl and plugin.jelly Changes: Fix Version changed to 1.1 - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-754&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-754 Here is an overview of the issue: - Key: MAVEN-754 Summary: Pluggable search form in the nav bar Type: Wish Status: Unassigned Priority: Minor Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-xdoc Fix Fors: 1.1 Versions: 1.0-rc1 Assignee: Reporter: Created: Thu, 28 Aug 2003 5:39 PM Updated: Thu, 28 Aug 2003 8:32 PM Environment: win xp, jdk 1.4.2 Description: It would be great to be able to plug in different search engines into the nav bar (as opposed to just google.com). For example, my maven sites will be deployed internally and we have an Ultraseek server that I'm using to index the sites. Right now I can doctor up my version of the site plugin, but it would be nice to be able to vary this on a per-project basis. If someone will point me in the right direction, I'll be happy to give it a try... Thanks! - Paul - 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]
