Results of clean bootstrap at 20030624- 308
Last 500 lines of a clean bootstrap build of maven at 20030624- 308 == /home/bwalding/src/logs/maven-build-20030624- == [exec] + [exec] clean:clean: [exec] clean: [exec] plugin: [exec] java:prepare-filesystem: [exec] [mkdir] Created dir: /home/bwalding/src/maven/src/plugins-build/touchstone-partner/target/classes [exec] java:compile: [exec] [echo] Compiling to /home/bwalding/src/maven/src/plugins-build/touchstone-partner/target/classes [exec] [echo] No java source files to compile. [exec] java:jar-resources: [exec] [copy] Copying 3 files to /home/bwalding/src/maven/src/plugins-build/touchstone-partner/target/classes [exec] test:prepare-filesystem: [exec] [mkdir] Created dir: /home/bwalding/src/maven/src/plugins-build/touchstone-partner/target/test-classes [exec] [mkdir] Created dir: /home/bwalding/src/maven/src/plugins-build/touchstone-partner/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: /home/bwalding/src/maven/src/plugins-build/touchstone-partner/target/maven-touchstone-partner-plugin-1.0.jar [exec] [copy] Copying 1 file to /home/bwalding/.maven/repository/maven/jars [exec] + [exec] | Building Maven Uberjar Plugin [exec] | Memory: 134M/144M [exec] + [exec] clean:clean: [exec] clean: [exec] plugin: [exec] java:prepare-filesystem: [exec] [mkdir] Created dir: /home/bwalding/src/maven/src/plugins-build/uberjar/target/classes [exec] java:compile: [exec] [echo] Compiling to /home/bwalding/src/maven/src/plugins-build/uberjar/target/classes [exec] [echo] No java source files to compile. [exec] java:jar-resources: [exec] [copy] Copying 1 file to /home/bwalding/src/maven/src/plugins-build/uberjar/target/classes/plugin-resources [exec] [copy] Copying 2 files to /home/bwalding/src/maven/src/plugins-build/uberjar/target/classes [exec] test:prepare-filesystem: [exec] [mkdir] Created dir: /home/bwalding/src/maven/src/plugins-build/uberjar/target/test-classes [exec] [mkdir] Created dir: /home/bwalding/src/maven/src/plugins-build/uberjar/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: /home/bwalding/src/maven/src/plugins-build/uberjar/target/maven-uberjar-plugin-1.0.jar [exec] [copy] Copying 1 file to /home/bwalding/.maven/repository/maven/jars [exec] + [exec] | Building Maven VDoclet Plug-in [exec] | Memory: 136M/144M [exec] + [exec] clean:clean: [exec] clean: [exec] plugin: [exec] java:prepare-filesystem: [exec] [mkdir] Created dir: /home/bwalding/src/maven/src/plugins-build/vdoclet/target/classes [exec] java:compile: [exec] [echo] Compiling to /home/bwalding/src/maven/src/plugins-build/vdoclet/target/classes [exec] [javac] Compiling 1 source file to /home/bwalding/src/maven/src/plugins-build/vdoclet/target/classes [exec] java:jar-resources: [exec] [copy] Copying 4 files to /home/bwalding/src/maven/src/plugins-build/vdoclet/target/classes [exec] test:prepare-filesystem: [exec] [mkdir] Created dir: /home/bwalding/src/maven/src/plugins-build/vdoclet/target/test-classes [exec] [mkdir] Created dir: /home/bwalding/src/maven/src/plugins-build/vdoclet/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: /home/bwalding/src/maven/src/plugins-build/vdoclet/target/maven-vdoclet-plugin-1.0.jar [exec] [copy] Copying 1 file to /home/bwalding/.maven/repository/maven/jars [exec] + [exec] | Building Maven WAR Plugin [exec] | Memory: 139M/144M [exec] + [exec] clean:clean: [exec] clean: [exec] plugin: [exec] java:prepare-filesystem: [exec] [mkdir] Created dir: /home/bwalding/src/maven/src/plugins-build/war/target/classes [exec] java:compile: [exec] [echo] Compiling to /home/bwalding/src/maven/src/plugins-build/war/target/classes [exec] [echo] No java source files to compile
Re: Torque build failure
Daniel Rall wrote: Janne [EMAIL PROTECTED] writes: * /home/*/tmp/db-torque maven dist:lite __ __ | \/ |__ Jakarta _ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9-SNAPSHOT Attempting to download commons-configuration-1.0-dev-3.20030607.194155.jar. Error retrieving artifact from [http://www.ibiblio.org/maven/commons-configuration/jars/commons-configuration-1.0-dev-3.20030607.194155.jar]: java.lang.Exception: Can't get commons-configuration-1.0-dev-3.20030607.194155.jar.incomplete to /tmp/maven-1.0-beta-9/repository/commons-configuration/jars/commons-configuration-1.0-dev-3.20030607.194155.jar.incomplete WARNING: Failed to download commons-configuration-1.0-dev-3.20030607.194155.jar.Attempting to download commons-dbcp-SNAPSHOT.jar. .. Attempting to download jdbc-2.0.jar. Error retrieving artifact from [http://www.ibiblio.org/maven/jdbc/jars/jdbc-2.0.jar]: java.lang.Exception: Can't get jdbc-2.0.jar.incomplete to /tmp/maven-1.0-beta-9/repository/jdbc/jars/jdbc-2.0.jar.incomplete WARNING: Failed to download jdbc-2.0.jar. Attempting to download jndi-1.2.1.jar. Error retrieving artifact from [http://www.ibiblio.org/maven/jndi/jars/jndi-1.2.1.jar]: java.lang.Exception: Can't get jndi-1.2.1.jar.incomplete to /tmp/maven-1.0-beta-9/repository/jndi/jars/jndi-1.2.1.jar.incomplete WARNING: Failed to download jndi-1.2.1.jar. The build cannot continue because of the following unsatisfied dependencies: commons-configuration-1.0-dev-3.20030607.194155.jar jdbc-2.0.jar jndi-1.2.1.jar Total time: 14 seconds I checked http://www.ibiblio.org/maven repository and the above files do not exists there. I had the same problem last week for (only) commons-configuration-1.0-dev-3.20030607.194155.jar. I worked around it by adding the following to my project.properties: maven.jar.override=on maven.jar.commons-configuration=1.0-dev This solved problem with commons-configuration. jndi and jdbc to go. I guess this has gone unnoticed because developers seldom start with a clean maven repository just as I did. Who should I contact at ibiblio to get the missing libraries in place? - Janne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-516) Simian Plugin (fully documented and ready to use)
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-516 Here is an overview of the issue: - Key: MAVEN-516 Summary: Simian Plugin (fully documented and ready to use) Type: New Feature Status: Unassigned Priority: Major Time Spent: Unknown Estimate: 0 minutes Project: maven Components: plugin-other Versions: 1.0-beta-10 Assignee: Reporter: Aslak Hellesy Created: Tue, 24 Jun 2003 6:54 AM Updated: Tue, 24 Jun 2003 6:54 AM Description: Simian (http://www.redhillconsulting.com.au/products/simian/index.html ) is a great little tool that detects duplicate source code. Very much like PMD's CPD (http://pmd.sourceforge.net/cpd.html), but a _lot_ faster. I have written a Maven report plugin for Simian that I'd like to contribute to Maven. Have a look at some sample reports: http://www.picocontainer.org/simian-report.html http://www.nanocontainer.org/simian-report.html It would be really nice to have the Simian Report included in the standard reports, as it reveals refactoring candidates and is something every sound project should have! - 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/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-516) Simian Plugin (fully documented and ready to use)
The following issue has been updated: Updater: Aslak Hellesy (mailto:[EMAIL PROTECTED]) Date: Tue, 24 Jun 2003 6:55 AM Comment: Here is the entire plugin Changes: Attachment changed from to maven-simian-plugin-1.0-src.zip - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-516page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-516 Here is an overview of the issue: - Key: MAVEN-516 Summary: Simian Plugin (fully documented and ready to use) Type: New Feature Status: Unassigned Priority: Major Time Spent: Unknown Estimate: 0 minutes Project: maven Components: plugin-other Versions: 1.0-beta-10 Assignee: Reporter: Aslak Hellesy Created: Tue, 24 Jun 2003 6:54 AM Updated: Tue, 24 Jun 2003 6:55 AM Description: Simian (http://www.redhillconsulting.com.au/products/simian/index.html ) is a great little tool that detects duplicate source code. Very much like PMD's CPD (http://pmd.sourceforge.net/cpd.html), but a _lot_ faster. I have written a Maven report plugin for Simian that I'd like to contribute to Maven. Have a look at some sample reports: http://www.picocontainer.org/simian-report.html http://www.nanocontainer.org/simian-report.html It would be really nice to have the Simian Report included in the standard reports, as it reveals refactoring candidates and is something every sound project should have! - 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/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-516) Simian Plugin (fully documented and ready to use)
The following comment has been added to this issue: Author: Aslak Hellesy Created: Tue, 24 Jun 2003 7:15 AM Body: please ignore the build.xml in the zip. It's crap. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-516 Here is an overview of the issue: - Key: MAVEN-516 Summary: Simian Plugin (fully documented and ready to use) Type: New Feature Status: Unassigned Priority: Major Time Spent: Unknown Estimate: 0 minutes Project: maven Components: plugin-other Versions: 1.0-beta-10 Assignee: Reporter: Aslak Hellesy Created: Tue, 24 Jun 2003 6:54 AM Updated: Tue, 24 Jun 2003 6:55 AM Description: Simian (http://www.redhillconsulting.com.au/products/simian/index.html ) is a great little tool that detects duplicate source code. Very much like PMD's CPD (http://pmd.sourceforge.net/cpd.html), but a _lot_ faster. I have written a Maven report plugin for Simian that I'd like to contribute to Maven. Have a look at some sample reports: http://www.picocontainer.org/simian-report.html http://www.nanocontainer.org/simian-report.html It would be really nice to have the Simian Report included in the standard reports, as it reveals refactoring candidates and is something every sound project should have! - 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/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]
Simian Plugin (fully documented and ready to use)
It seems Maven's JIRA still doesn't notify this list, so here I go... Simian (http://www.redhillconsulting.com.au/products/simian/index.html ) is a great little tool that detects duplicate source code. Very much like PMD's CPD (http://pmd.sourceforge.net/cpd.html), but a _lot_ faster. I have written a Maven report plugin for Simian that I'd like to contribute to Maven. Have a look at some sample reports: http://www.picocontainer.org/simian-report.html http://www.nanocontainer.org/simian-report.html It would be really nice to have the Simian Report included in the standard reports, as it reveals refactoring candidates and is something every sound project should have! It's all in JIRA: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-516 Cheers, Aslak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-517) PDF Plug-In 2.0
The following issue has been updated: Updater: Andrew Jaquith (mailto:[EMAIL PROTECTED]) Date: Tue, 24 Jun 2003 9:13 AM Comment: Here is the tarball for the plug-in... Changes: Attachment changed from to maven-pdf-plugin-2.0.tar.gz - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-517page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-517 Here is an overview of the issue: - Key: MAVEN-517 Summary: PDF Plug-In 2.0 Type: Improvement Status: Unassigned Priority: Major Time Spent: Unknown Estimate: 20 minutes Project: maven Components: plugin-other Assignee: Reporter: Andrew Jaquith Created: Tue, 24 Jun 2003 9:12 AM Updated: Tue, 24 Jun 2003 9:13 AM Environment: All Description: I have completely re-written the PDF plug-in. It solves most of the thorniest issues, such as table formatting, more levels in the table of contents, and image sizing. The graphic design is also dramatically improved. - 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/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-517) PDF Plug-In 2.0
The following comment has been added to this issue: Author: bob mcwhirter Created: Tue, 24 Jun 2003 9:21 AM Body: I'm not very familiar at all with the pdf plugin, but I'd like to suggest renaming it to address the source file format, not the target output format. The 'latex' plugin, for example, can produce PDFs also, but from LaTeX sources. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-517 Here is an overview of the issue: - Key: MAVEN-517 Summary: PDF Plug-In 2.0 Type: Improvement Status: Unassigned Priority: Major Time Spent: Unknown Estimate: 20 minutes Project: maven Components: plugin-other Assignee: Reporter: Andrew Jaquith Created: Tue, 24 Jun 2003 9:12 AM Updated: Tue, 24 Jun 2003 9:13 AM Environment: All Description: I have completely re-written the PDF plug-in. It solves most of the thorniest issues, such as table formatting, more levels in the table of contents, and image sizing. The graphic design is also dramatically improved. - 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/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-518) plugins guess filename from 'dependency', should use 'artifact'
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-518
Here is an overview of the issue:
-
Key: MAVEN-518
Summary: plugins guess filename from 'dependency', should use 'artifact'
Type: Bug
Status: Unassigned
Priority: Major
Time Spent: Unknown
Estimate: 0 minutes
Project: maven
Assignee:
Reporter: Brian Ewins
Created: Tue, 24 Jun 2003 9:49 AM
Updated: Tue, 24 Jun 2003 9:49 AM
Description:
Quite a few plugins are mistakenly referring to and looping over dependencies when
they mean to use artifacts. For example this code in the war plugin:
j:forEach var=dep items=${pom.dependencies}
j:if test=${dep.getProperty('war.bundle.jar')=='true'}
lib dir=${maven.repo.local}/${dep.artifactDirectory}/jars/
include name=${dep.artifact}/
/lib
/j:if
/j:forEach
Will not work if the 'jar' element has been used to override the filename of a
dependency. In maven Artifacts know their filename, Dependencies don't. You can
navigate from an Artifact to a Dependency if required, so that one fix might look like:
j:forEach var=lib items=${pom.artifacts}
j:set var=dep value=${lib.dependency}/
j:if test=${dep.getProperty('war.bundle.jar')=='true'}
lib dir=${maven.repo.local}
include name=${lib.path}/
/lib
/j:if
/j:forEach
While this removes all knowledge of the internal structure of the local repo from the
plugin, it is still not ideal. If a project is allowed to depend on jars that are
outside the local repository via the jar override mechanism then plugins should not
use 'maven.repo.local' either.
To find these issues in the plugins, go to the plugins-build directory and do:
$ find . -name '*.jelly' | xargs grep pom.dependencies
(NB the gump and release plugins are listed by this but are not affected)
also do:
$ find . -name '*.jelly' | xargs grep maven.repo.local
the second set will pick out most of the first set of problems, but will also find the
occasional case where an individual dependency is misused.
The following files are known to be affected by this bug:
./ant/plugin.jelly
./deploy/plugin.jelly
./ear/plugin.jelly
./ejb/plugin.jelly
./idea/plugin.jelly
./jboss/plugin.jelly
./jdeveloper/plugin.jelly
./jnlp/plugin.jelly
./uberjar/plugin.jelly
./war/plugin.jelly
(Patch to follow)
-
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/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]
missing jar at ibiblio for bootstrap build
I tried a clean ($HOME/.maven/repository removed/empty!) bootstrap build and got [exec] The build cannot continue because of the following unsatisfied dependency: [exec] commons-jelly-tags-xml-20030211.142705.jar During the B U I L D I N G T H E P L U G I N S pahse Searched for that jar at ibiblio but didn't found it... Any ideas? -- Martin Skopp Riege Software International GmbH Support: mailto:[EMAIL PROTECTED], Information: http://www.riege.com This email is intended to be viewed with a nonproportional font. Public Key on http://www.keyserver.net, Key-ID: 3D4027B5 Fingerprint: 1970 C78D 9A1D 99FA 5CE4 5C0D 29E6 6A95 3D40 27B5 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-461) Patches for JBuilder plugin
The following issue has been updated: Updater: David Zeleznik (mailto:[EMAIL PROTECTED]) Date: Tue, 24 Jun 2003 1:48 PM Comment: - Added support for JBuilder 9 - Added maven.jbuilder.verbose property - Library files that are automatically generated from versioned (not snapshot) artifact dependencies are now versioned themselves. This is also true for snapshot dependencies where an unversioned library file has not been created yet from the corresponding artifact. As before, if an unversioned library file has already been created for a snapshot dependency, the unversioned library will be referenced. Changes: Attachment changed from to plugin.properties - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-461page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-461 Here is an overview of the issue: - Key: MAVEN-461 Summary: Patches for JBuilder plugin Type: Improvement Status: Unassigned Priority: Major Time Spent: Unknown Estimate: 1 day Project: maven Components: plugin-other Versions: 1.0-beta-9 Assignee: Reporter: David Zeleznik Created: Tue, 3 Jun 2003 5:08 PM Updated: Tue, 24 Jun 2003 1:48 PM Description: - The plugin attempts to find JBuilder's HOME directory where it will read the user's default project properties file. - The JBuilder HOME directory is also where library files are generated. This is a major rewrite of the JBuilder plugin that keeps backwards compatibility, while adding much more complete generation of project and library files. Some of the ideas have been borrowed from the latest versions of the IDEA and Eclipse plugins. Here is a short summary that covers some of the highlights: - The plugin attempts to find JBuilder's HOME directory where it will read the user's default project properties file. The JBuilder HOME directory is also where library files are generated. - When you generate a JBuilder project file, the plugin iterates through its dependencies. For each dependency, a library definition file is generated for the dependency jar in the local repo. This dependent library file is generated if, and only if, the library file does not already exist or the library file was previously generated the same way (as a dependency on a jar in the local repo). - The previous point means that when you generate a jbuilder library definition file directly from a Maven project (using the jbuilder:generate-library goal) you will replace any previous definition of the library that was generated as a jar-only dependency with a library definition that references both the source and class files. - For library definitions that remain jar-only references to the local repo, you can specify a path to the corresponding source code via properties. - Support has been added for generating JBuilder application and applet runtime configurations from properties. - Any resources are added to the JBuilder project source path. - Using an optional property, you can specify a list of explicit files that will be included in the JBuilder project if they exist. The default list are project.xml, project.properties, and maven.xml. - 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/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: Simian Plugin (fully documented and ready to use)
Hi Aslak, I love the idea of CPD/Simian. However, before we can commit anything here we would need agreement from redhillconsulting.com that we can put the simian jar in the Maven remote repository on ibiblio. If we dont get this agreement, we could still store this plugin in the SF mavne-plugins project and users would need to download the simian jar and put it manually in their local repository. Thanks -Vincent -Original Message- From: Aslak Hellesøy [mailto:[EMAIL PROTECTED] Sent: 24 June 2003 13:58 To: Maven Developers List Cc: [EMAIL PROTECTED] Subject: Simian Plugin (fully documented and ready to use) It seems Maven's JIRA still doesn't notify this list, so here I go... Simian (http://www.redhillconsulting.com.au/products/simian/index.html ) is a great little tool that detects duplicate source code. Very much like PMD's CPD (http://pmd.sourceforge.net/cpd.html), but a _lot_ faster. I have written a Maven report plugin for Simian that I'd like to contribute to Maven. Have a look at some sample reports: http://www.picocontainer.org/simian-report.html http://www.nanocontainer.org/simian-report.html It would be really nice to have the Simian Report included in the standard reports, as it reveals refactoring candidates and is something every sound project should have! It's all in JIRA: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-516 Cheers, Aslak - 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: Simian Plugin (fully documented and ready to use)
You have my permission to do so. The license agreement allows for this. Cheers, Simon -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Wednesday, 25 June 2003 4:54 AM To: 'Maven Developers List' Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Simian Plugin (fully documented and ready to use) Hi Aslak, I love the idea of CPD/Simian. However, before we can commit anything here we would need agreement from redhillconsulting.com that we can put the simian jar in the Maven remote repository on ibiblio. If we dont get this agreement, we could still store this plugin in the SF mavne-plugins project and users would need to download the simian jar and put it manually in their local repository. Thanks -Vincent -Original Message- From: Aslak Hellesøy [mailto:[EMAIL PROTECTED] Sent: 24 June 2003 13:58 To: Maven Developers List Cc: [EMAIL PROTECTED] Subject: Simian Plugin (fully documented and ready to use) It seems Maven's JIRA still doesn't notify this list, so here I go... Simian (http://www.redhillconsulting.com.au/products/simian/index.htm l ) is a great little tool that detects duplicate source code. Very much like PMD's CPD (http://pmd.sourceforge.net/cpd.html), but a _lot_ faster. I have written a Maven report plugin for Simian that I'd like to contribute to Maven. Have a look at some sample reports: http://www.picocontainer.org/simian-report.html http://www.nanocontainer.org/simian-report.html It would be really nice to have the Simian Report included in the standard reports, as it reveals refactoring candidates and is something every sound project should have! It's all in JIRA: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-516 Cheers, Aslak - 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]
clean build fails
On a fresh CVS clean bootstrap build I get (building maven with itself phase): ... [exec] [junit] dir attribute ignored if running in the same VM [exec] [junit] Running org.apache.maven.project.ProjectInheritanceTest [exec] [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 6.397 sec [exec] [junit] [ERROR] TEST org.apache.maven.project.ProjectInheritanceTest FAILED ... [exec] BUILD FAILED [exec] There were test failures. BUILD FAILED file:/home/s/tmp/maven/build-bootstrap.xml:313: exec returned: 70 RedHat 8.0 (all recent patches), J2SDK 1.4.1_03. incze - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Responsibility - was [RE: Simian Plugin (fully documented and ready to use)\
# antlr M (bob) # ashkelonM (ben) # jalopy M (jcej, I think) # latex M (bob) # perforceM (jcej) # uberjar M (bob, pete) -bob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Simian Plugin (fully documented and ready to use)
Here is a copy of the license agreement that you may distribute with simian for maven Cheers, Simon -Original Message- From: Simon Harris [mailto:[EMAIL PROTECTED] Sent: Wednesday, 25 June 2003 6:06 AM To: 'Vincent Massol'; 'Maven Developers List' Cc: '[EMAIL PROTECTED]' Subject: RE: Simian Plugin (fully documented and ready to use) You have my permission to do so. The license agreement allows for this. Cheers, Simon -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Wednesday, 25 June 2003 4:54 AM To: 'Maven Developers List' Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Simian Plugin (fully documented and ready to use) Hi Aslak, I love the idea of CPD/Simian. However, before we can commit anything here we would need agreement from redhillconsulting.com that we can put the simian jar in the Maven remote repository on ibiblio. If we dont get this agreement, we could still store this plugin in the SF mavne-plugins project and users would need to download the simian jar and put it manually in their local repository. Thanks -Vincent -Original Message- From: Aslak Hellesøy [mailto:[EMAIL PROTECTED] Sent: 24 June 2003 13:58 To: Maven Developers List Cc: [EMAIL PROTECTED] Subject: Simian Plugin (fully documented and ready to use) It seems Maven's JIRA still doesn't notify this list, so here I go... Simian (http://www.redhillconsulting.com.au/products/simian/index.htm l ) is a great little tool that detects duplicate source code. Very much like PMD's CPD (http://pmd.sourceforge.net/cpd.html), but a _lot_ faster. I have written a Maven report plugin for Simian that I'd like to contribute to Maven. Have a look at some sample reports: http://www.picocontainer.org/simian-report.html http://www.nanocontainer.org/simian-report.html It would be really nice to have the Simian Report included in the standard reports, as it reveals refactoring candidates and is something every sound project should have! It's all in JIRA: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-516 Cheers, Aslak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] SIMIAN VERSION 1 (ONE) SOFTWARE LICENSE AGREEMENT 1. Licenses and Software RedHill Consulting, Pty. Ltd., an Australian Proprietary Limited Company (REDHILL) hereby grants to the purchaser (the LICENSEE) a limited, revocable, worldwide, non-exclusive, nontransferable, non-sublicensable license to use the Simian version 1 (one) software (the Software), including any minor upgrades thereof during the Term (hereinafter defined) up to, but not including the next major version of the Software. The licensee shall not, or knowingly allow others to, reverse engineer, decompile, disassemble, modify, adapt, create derivative works from or otherwise attempt to derive source code from the Software provided. And, in accordance with the terms and conditions of this Software License Agreement (the Agreement), the Software shall be used solely by the licensed users in accordance with the following edition specific conditions: a) A license entitles the licensee to use Simian solely for a single licensed project. 2. License Fee In exchange for the License(s), the Licensee shall pay to RedHill a one-time, up front, non-refundable license fee. At the sole discretion of RedHill, this fee will be waived for non-commercial projects and for a period of 15 days for evaluation purposes only. Notwithstanding the Licensee's payment of the License Fee, RedHill reserves the right to terminate the License if RedHill discovers that the Licensee and/or the Licensee's use of the Software is in breach of this Agreement. 3. Proprietary Rights RedHill will retain all right, title and interest in and to the Software, all copies thereof, and RedHill website(s), software, and other intellectual property, including, but not limited to, ownership of all copyrights, look and feel, trademark rights, design rights, trade secret rights and any and all other intellectual property and other proprietary rights therein. The Licensee will not directly or indirectly obtain or attempt to obtain at any time, any right, title or interest by registration or otherwise in or to the trademarks, service marks, copyrights, trade names, symbols, logos or designations or other intellectual property rights owned or used by RedHill. All technical manuals or other information provided by RedHill to the Licensee shall be the sole property of RedHill. 4. Term and Termination Subject to the other provisions hereof, this Agreement shall commence upon the Licensee's opting into this Agreement and continue until the Licensee discontinues use of the Software or the Agreement
Re: Responsibility - was [RE: Simian Plugin (fully documented andready to use)\
On Tue, 2003-06-24 at 17:19, Rafal Krzewski wrote: Michal Maczka wrote: C - core - needed to perform basic tasks M - actively maintained O - obsoleted by other plugins B - broken # aspectj M (vmassol, jvanzyl 1.1) # codeswitcher M # genapp M C (used for generating sample projects) # idea M (jvanzyl # plexus M (jvanzyl # plugin C (use for bootstrap) # runner M (jvanzyl) # sea M (jvanzyl # vdoclet M (jvanzyl) All the Ms can definitely be moved elsewhere at some point. - 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]
Re: clean build fails
On Tue, Jun 24, 2003 at 11:24:00PM +0200, Rafal Krzewski wrote:
Incze Lajos wrote:
On a fresh CVS clean bootstrap build I get (building maven with itself phase):
...
[exec] [junit] dir attribute ignored if running in the same VM
[exec] [junit] Running org.apache.maven.project.ProjectInheritanceTest
[exec] [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 6.397
sec
[exec] [junit] [ERROR] TEST
org.apache.maven.project.ProjectInheritanceTest FAILED
...
[exec] BUILD FAILED
[exec] There were test failures.
BUILD FAILED
file:/home/s/tmp/maven/build-bootstrap.xml:313: exec returned: 70
I've seen that yesterday too, I even tried to post a message on that but
it got munched by my email client (bad network day, or rather week to
be more specific...)
Could you please locate the associated failure report in
target/test-reports (it'll be something-ProjectInheritanceTest.txt) and
post it? I don't have mine handy ATM.
Yes, that's it:
line 122 (from src/test/java/test/org/apache/maven/project/ProjectInheritenceTest.java)
// Test Source Directories
assertEquals( src/java, p.getBuild().getSourceDirectory() );
and the fail:
FAILED
expected:... but was:/home/s/tmp/maven/src/test/extend/...
junit.framework.ComparisonFailure: expected:... but
was:/home/s/tmp/maven/src/test/extend/...
-
So, it expects relative path and gets an absolute.
iSeems to me, that time to stick with on econvention (basedir relative,
or ${basedir}/... in POM) and gow through all the plugins and tests
to behave accordingly.
incze
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/artifact project.xml
michal 2003/06/24 15:22:55
Modified:src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers
FtpDeployer.java FileDeployer.java
HttpDeployer.java
src/plugins-build/artifact/src/main/org/apache/maven/artifact/deployer
DefaultArtifactDeployer.java
MavenDeployRequest.java
src/plugins-build/artifact/src/main/org/apache/maven/deploy
DeployRequest.java DeployTool.java
src/plugins-build/artifact project.xml
Added: src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers
SFtpDeployer.java
Removed: src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers
SshDeployer.java
Log:
Changed SCP Deployer to SFTP deployer. I am done with functionality
(except of Http Deployer)
Now I will test it deeper and assure that everything works.
Revision ChangesPath
1.3 +11 -7
maven/src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers/FtpDeployer.java
Index: FtpDeployer.java
===
RCS file:
/home/cvs/maven/src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers/FtpDeployer.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- FtpDeployer.java 19 Jun 2003 22:02:36 - 1.2
+++ FtpDeployer.java 24 Jun 2003 22:22:54 - 1.3
@@ -75,15 +75,20 @@
/**
* An FTP deployer based on the FTPClient in the Commons Net package.
*
+ * Proxy server for FTPClient is not supported:
+ * [EMAIL PROTECTED] http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18039}
+ *
* @author a href=mailto:[EMAIL PROTECTED]Jason van Zyl/a
- *
+ * @author a href=[EMAIL PROTECTED]Michal Maczka/a
* @version $Id$
- *
- * @todo account for username and password.
+ *
+ *
*/
public class FtpDeployer extends AbstractDeployer
{
-
+
+public final static String PROTOCOL = ftp://;;
+
/**
* Description of the Method
*/
@@ -140,8 +145,7 @@
}
__main : try
-{
-System.out.println(username: ' + username +' password: '+
password+');
+{
if (ftp.login(username.trim(), password.trim()) == false)
{
ftp.logout();
1.4 +3 -1
maven/src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers/FileDeployer.java
Index: FileDeployer.java
===
RCS file:
/home/cvs/maven/src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers/FileDeployer.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- FileDeployer.java 20 Jun 2003 15:24:52 - 1.3
+++ FileDeployer.java 24 Jun 2003 22:22:54 - 1.4
@@ -71,6 +71,8 @@
public class FileDeployer implements Deployer
{
+public final static String PROTOCOL = file://;
+
/**
* @see org.apache.maven.fetch.fetchers.Fetcher#fetchUrl(java.lang.String,
java.io.OutputStream)
*/
1.2 +2 -1
maven/src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers/HttpDeployer.java
Index: HttpDeployer.java
===
RCS file:
/home/cvs/maven/src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers/HttpDeployer.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- HttpDeployer.java 17 Jun 2003 22:05:59 - 1.1
+++ HttpDeployer.java 24 Jun 2003 22:22:54 - 1.2
@@ -87,6 +87,7 @@
public class HttpDeployer extends AbstractDeployer
{
+public final static String PROTOCOL = http://;;
/**
* Description of the Method
*/
1.1
maven/src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers/SFtpDeployer.java
Index: SFtpDeployer.java
===
package org.apache.maven.deploy.deployers;
/*
* The Apache Software License, Version 1.1
*
* Copyright (c) 2001 The Apache Software Foundation. All rights
* reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
*notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
*notice, this list of
Re: cvs commit: maven/src/test/java/org/apache/maven/project ProjectInheritanceTest.java
On Tue, Jun 24, 2003 at 10:14:05PM +, [EMAIL PROTECTED] wrote:
jvanzyl 2003/06/24 15:14:05
Modified:src/test/java/org/apache/maven/project
ProjectInheritanceTest.java
Log:
o Need to use basedir.
That's ok for this test case. But there are other points
where (as we don't have a strict convention) the
programmer works according to the one (src/java) or the
other (${basedir}/src/java) convention in her/his mind.
E.g. if you use this style, the checkstyle report will go
wrong, as it's stylesheet allways preprends with ${basedir}
what it finds in the sourceDirectory tag.
incze
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven/src/plugins-build/artifact project.xml
[EMAIL PROTECTED] wrote: Added: src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers SFtpDeployer.java Removed: src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers SshDeployer.java Log: Changed SCP Deployer to SFTP deployer. I am done with functionality (except of Http Deployer) Excuse me is SCP deployment no longer supported? I believe that this is what most people use for their deployments! Correct me if I'm wrong but SFTP is plain old FTP running over TLS - a standard that never really catched on, and it's servers are really hard to come by now. Why on earth would support that instead of de-facto standard that scp is? R. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: clean build (next round)
On Wed, Jun 25, 2003 at 12:53:39AM +0200, Incze Lajos wrote: Now, the problem is that we have a jsch-0.1.5 dependency, but no artifact at ibiblio to download. incze Artifact plugin has compile error with jsch-0.1.5.jar, so no build yet. incze - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ProjectInheritenceTest doesn't compile
There is a basedir/baseDir mismatch in the recent patch. incze - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Responsibility - was [RE: Simian Plugin (fully documented andready to use)\
Michal Maczka wrote: Just wanted to express my opinion about new plugins. I don't think that we should add more plugins to maven, unless they are really core plugins. I think we have quite a lot of dead plugins and many broken plugins, I like more the idea of having this plugin elsewhere, so original plugin authors can take responsibility. Knowing Aslak's skills I have no doubt that Maven team can give him access right to CVS repository to let him maintain this plugin but I want to discuss general policy regarding this subject. I think Aslak has a lot of experience with such problems from XDoclet project. Simply any plugin which is based on external libraries is very sensitive to any changes in those libraries. For example Hibernate, Torque, JBoss plugins will be broken once there is minor change in those project. Keeping all plugin up to date in enormous work. From the other hand I feel that Maven should have a catalog of known foreign plugins ( in form both of web site, and machine readable file format (XML ?), so any plugin can be downloaded automatically) This will not only improve quality of code which is kept in our CVS repository, but also will increase the number of people which can actively work on plugins and having cvs access rights, so also plugin will be better. What you think? Good call! XDoclet2's strategy is to delegate plugin development, maintenance and distribution to 3rd party vendors/projects. This increases the probability of plugins keeping up to date with the product they relate to, and lets the core team focus on the core. XDoclet2 will only maintain a very very sparse set of plugins. I think Maven could benefit from a similar strategy, as could many other projects/products. However, there is a crucial thing that needs to be in place before this can be truly effective: Transparency for the users. They shouldn't have to trawl the web for plugins and documentation in a gazillion different places. It should be centralised. That means some service where plugins (and documentation) can be registered, and some mechanism that can actually retrieve them from wherever they live (not only at ibiblio, but anywhere!) This is a concept that applies to a lot of different platforms: Maven, XDoclet, Ant, IDEs, you name it. Put in other words, the aforementioned containers should be able to locate and access components. And there should be a nice way for plugin developers for various platforms to register their plugin. What I'm thinking about here is a lookup-service that runs as a server, and can be used by various platforms. Some kind of web service thingy, but not quite. I'd like to hear people's thought about this and whether you think a new project should be sparked off somewhere to implement (and possibly host) such services. Michal -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 8:54 PM To: 'Maven Developers List' Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Simian Plugin (fully documented and ready to use) Hi Aslak, I love the idea of CPD/Simian. However, before we can commit anything here we would need agreement from redhillconsulting.com that we can put the simian jar in the Maven remote repository on ibiblio. If we dont get this agreement, we could still store this plugin in the SF mavne-plugins project and users would need to download the simian jar and put it manually in their local repository. Thanks -Vincent -Original Message- From: Aslak Hellesy [mailto:[EMAIL PROTECTED] Sent: 24 June 2003 13:58 To: Maven Developers List Cc: [EMAIL PROTECTED] Subject: Simian Plugin (fully documented and ready to use) It seems Maven's JIRA still doesn't notify this list, so here I go... Simian (http://www.redhillconsulting.com.au/products/simian/index.html ) is a great little tool that detects duplicate source code. Very much like PMD's CPD (http://pmd.sourceforge.net/cpd.html), but a _lot_ faster. I have written a Maven report plugin for Simian that I'd like to contribute to Maven. Have a look at some sample reports: http://www.picocontainer.org/simian-report.html http://www.nanocontainer.org/simian-report.html It would be really nice to have the Simian Report included in the standard reports, as it reveals refactoring candidates and is something every sound project should have! It's all in JIRA: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-516 Cheers, Aslak - 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] -- Klikaj!!! I skorzystaj!!! http://link.interia.pl/f1739
Re: ProjectInheritenceTest doesn't compile
On Wed, Jun 25, 2003 at 01:31:39AM +0200, Incze Lajos wrote: There is a basedir/baseDir mismatch in the recent patch. incze Other problem: private String PS = System.getProperty( path.separator ); Should be: private String FS = System.getProperty( file.separator ); incze - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-496) Missing information for resolving problems when using Maven
Message: The following issue has been closed. Resolver: dion gillard Date: Tue, 24 Jun 2003 7:11 PM Fixed plugin manager cache class to write better error messages - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-496 Here is an overview of the issue: - Key: MAVEN-496 Summary: Missing information for resolving problems when using Maven Type: Bug Status: Closed Priority: Major Resolution: FIXED Time Spent: Unknown Estimate: 0 minutes Project: maven Fix Fors: 1.0-beta-10 Assignee: dion gillard Reporter: Vincent Massol Created: Wed, 18 Jun 2003 10:56 AM Updated: Tue, 24 Jun 2003 7:11 PM Description: I type maven and I got: __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-beta-10-SNAPSHOT Fatal Error [line 142, row 19]: The prefix ant for element ant:echo is not bound. org.xml.sax.SAXParseException: The prefix ant for element ant:echo is not bound. at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.apache.maven.plugin.PluginCacheManager.parse(PluginCacheManager.java:357) at org.apache.maven.plugin.PluginManager.cachePlugin(PluginManager.java:795) at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:335) at org.apache.maven.MavenSession.initializePluginManager(MavenSession.java:293) at org.apache.maven.MavenSession.initialize(MavenSession.java:233) at org.apache.maven.cli.App.doMain(App.java:514) at org.apache.maven.cli.App.main(App.java:1088) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:543) at com.werken.forehead.Forehead.main(Forehead.java:573) Starting the reactor... [...] How do I know in which file the ant:echo problem is? The maven.log doesn't help. Shouldn't we print the file name in addition to the line and row? Thanks -Vincent - 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/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-517) PDF Plug-In 2.0
The following comment has been added to this issue: Author: dion gillard Created: Tue, 24 Jun 2003 7:15 PM Body: this is an existing plugin, and i'm not too keen on renaming it It converts xdocs - pdf. Same way the site plugin produces html from the xdocs. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-517 Here is an overview of the issue: - Key: MAVEN-517 Summary: PDF Plug-In 2.0 Type: Improvement Status: Unassigned Priority: Major Time Spent: Unknown Estimate: 20 minutes Project: maven Components: plugin-other Assignee: Reporter: Andrew Jaquith Created: Tue, 24 Jun 2003 9:12 AM Updated: Tue, 24 Jun 2003 9:13 AM Environment: All Description: I have completely re-written the PDF plug-in. It solves most of the thorniest issues, such as table formatting, more levels in the table of contents, and image sizing. The graphic design is also dramatically improved. - 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/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/test/java/org/apache/maven/project ProjectInheritanceTest.java
jvanzyl 2003/06/24 16:58:25
Modified:src/test/java/org/apache/maven/project
ProjectInheritanceTest.java
Log:
o Sorry 'bout that. Head down in refactoring.
Revision ChangesPath
1.31 +4 -4
maven/src/test/java/org/apache/maven/project/ProjectInheritanceTest.java
Index: ProjectInheritanceTest.java
===
RCS file:
/home/cvs/maven/src/test/java/org/apache/maven/project/ProjectInheritanceTest.java,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- ProjectInheritanceTest.java 24 Jun 2003 22:14:05 - 1.30
+++ ProjectInheritanceTest.java 24 Jun 2003 23:58:25 - 1.31
@@ -69,7 +69,7 @@
private String TEST_DOCUMENT = null;
private String TEST_DOCUMENT2 = null;
private String basedir;
-private String PS = System.getProperty( path.separator );
+private String FS = System.getProperty( file.separator );
public ProjectInheritanceTest( String testName )
{
@@ -121,15 +121,15 @@
( (Dependency) p.getDependencies().get( 1 ) ).getVersion() );
// Test Source Directories
-assertEquals( basedir + PS + src/java, p.getBuild().getSourceDirectory()
);
+assertEquals( basedir + FS + src/java, p.getBuild().getSourceDirectory()
);
// Unit Test Source Directories
-assertEquals( basedir + PS + src/test/java,
p.getBuild().getUnitTestSourceDirectory() );
+assertEquals( basedir + FS + src/test/java,
p.getBuild().getUnitTestSourceDirectory() );
// Test Aspect Source Directories
//assertEquals(src/aspect, p.getBuild().getAspectSourceDirectory());
// Test Test Source Directories ;-)
-assertEquals( basedir + PS + src/test/java,
p.getBuild().getUnitTestSourceDirectory() );
+assertEquals( basedir + FS + src/test/java,
p.getBuild().getUnitTestSourceDirectory() );
String iuSrc = p.getBuild().getIntegrationUnitTestSourceDirectory();
assertTrue( Should be empty in maven's project descriptor: [ + iuSrc +
],
StringUtils.isEmpty( iuSrc ) );
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven/src/plugins-build/artifact project.xml
Jason van Zyl wrote: On Tue, 2003-06-24 at 18:39, Rafal Krzewski wrote: [EMAIL PROTECTED] wrote: Added: src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers SFtpDeployer.java Removed: src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers SshDeployer.java Log: Changed SCP Deployer to SFTP deployer. I am done with functionality (except of Http Deployer) Excuse me is SCP deployment no longer supported? I believe that this is what most people use for their deployments! Correct me if I'm wrong but SFTP is plain old FTP running over TLS - a standard that never really catched on, and it's servers are really hard to come by now. Why on earth would support that instead of de-facto standard that scp is? That SShDeployer uses an SCP session just implemented in Java instead of using the scp executable. I really don't appreciate this kind of name reuse - sftp is a protocol registered by the IETF (tcp/115). It was rather silly of JCraft to use that name for their scp implementation. Let's do better than them and have JavaScpDeployer (and possibly ExternalScpDeployer, if we want to keep it for whatever reasons). R. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven/src/plugins-build/artifact project.xml
Excuse me is SCP deployment no longer supported? I believe that this is what most people use for their deployments! Correct me if I'm wrong but SFTP is plain old FTP running over TLS - a standard that never really catched on, and it's servers are really hard to come by now. Why on earth would support that instead of de-facto standard that scp is? fwiw, ibiblio.org and codehaus.org both run sftp daemons. -bob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven/src/plugins-build/artifact project.xml
On Tue, 2003-06-24 at 19:59, Rafal Krzewski wrote: That SShDeployer uses an SCP session just implemented in Java instead of using the scp executable. I really don't appreciate this kind of name reuse - sftp is a protocol registered by the IETF (tcp/115). It was rather silly of JCraft to use that name for their scp implementation. Let's do better than them and have JavaScpDeployer (and possibly ExternalScpDeployer, if we want to keep it for whatever reasons). I'm agreeing with you. I think Michal removed the SshDeployer and I'm not sure why. That's where the original SCP stuff was and it could have been more aptly named. When it comes back we'll do that. R. - 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/test/java/org/apache/maven/project ProjectInheritanceTest.java
dion2003/06/24 17:10:23
Modified:src/test/java/org/apache/maven/project
ProjectInheritanceTest.java
Log:
Someone should compile stuff first
Revision ChangesPath
1.32 +4 -4
maven/src/test/java/org/apache/maven/project/ProjectInheritanceTest.java
Index: ProjectInheritanceTest.java
===
RCS file:
/home/cvs/maven/src/test/java/org/apache/maven/project/ProjectInheritanceTest.java,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- ProjectInheritanceTest.java 24 Jun 2003 23:58:25 - 1.31
+++ ProjectInheritanceTest.java 25 Jun 2003 00:10:23 - 1.32
@@ -68,7 +68,7 @@
{
private String TEST_DOCUMENT = null;
private String TEST_DOCUMENT2 = null;
-private String basedir;
+private String baseDir;
private String FS = System.getProperty( file.separator );
public ProjectInheritanceTest( String testName )
@@ -121,15 +121,15 @@
( (Dependency) p.getDependencies().get( 1 ) ).getVersion() );
// Test Source Directories
-assertEquals( basedir + FS + src/java, p.getBuild().getSourceDirectory()
);
+assertEquals( baseDir + FS + src/java, p.getBuild().getSourceDirectory()
);
// Unit Test Source Directories
-assertEquals( basedir + FS + src/test/java,
p.getBuild().getUnitTestSourceDirectory() );
+assertEquals( baseDir + FS + src/test/java,
p.getBuild().getUnitTestSourceDirectory() );
// Test Aspect Source Directories
//assertEquals(src/aspect, p.getBuild().getAspectSourceDirectory());
// Test Test Source Directories ;-)
-assertEquals( basedir + FS + src/test/java,
p.getBuild().getUnitTestSourceDirectory() );
+assertEquals( baseDir + FS + src/test/java,
p.getBuild().getUnitTestSourceDirectory() );
String iuSrc = p.getBuild().getIntegrationUnitTestSourceDirectory();
assertTrue( Should be empty in maven's project descriptor: [ + iuSrc +
],
StringUtils.isEmpty( iuSrc ) );
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-516) Simian Plugin (fully documented and ready to use)
The following comment has been added to this issue: Author: Aslak Hellesy Created: Tue, 24 Jun 2003 7:30 PM Body: I assume you refer to Simian's built-in integration with Checkstyle. I haven't tried that part, but I'm sure Simon can shed some light here. I am biased, since I don't always use the checkstyle plugin, simply because it's not in sync with the jalopy plugin, and because the report get so darn long. And it's broken too. (bad links - check out http://www.picocontainer.org/checkstyle-report.html). So if Checkstyle and Jalopy are synced, and a Simian/Checkstyle integrated report reveals at least as much information as the one attached here, I'm all for it. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-516 Here is an overview of the issue: - Key: MAVEN-516 Summary: Simian Plugin (fully documented and ready to use) Type: New Feature Status: Unassigned Priority: Major Time Spent: Unknown Estimate: 0 minutes Project: maven Components: plugin-other Versions: 1.0-beta-10 Assignee: Reporter: Aslak Hellesy Created: Tue, 24 Jun 2003 6:54 AM Updated: Tue, 24 Jun 2003 6:55 AM Description: Simian (http://www.redhillconsulting.com.au/products/simian/index.html ) is a great little tool that detects duplicate source code. Very much like PMD's CPD (http://pmd.sourceforge.net/cpd.html), but a _lot_ faster. I have written a Maven report plugin for Simian that I'd like to contribute to Maven. Have a look at some sample reports: http://www.picocontainer.org/simian-report.html http://www.nanocontainer.org/simian-report.html It would be really nice to have the Simian Report included in the standard reports, as it reveals refactoring candidates and is something every sound project should have! - 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/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: Responsibility - was [RE: Simian Plugin (fully documented and ready touse)\
Rafal Krzewski [EMAIL PROTECTED] wrote on 25/06/2003 07:19:26 AM: I daresay that 2/3 of exising maven plugins is broken and/or orphaned. This is obviously an unacceptable situation. I daresay you're wrong, and would love to see a change :-) Below there's a list of plugins taken from current website. I've put marks next to them representing *my personal* opinion on the pluin's condition. C - core - needed to perform basic tasks M - actively maintained O - obsoleted by other plugins B - broken # ant AFAIK, this is 'M' - stable but actively maintained. # antlr # appserver # artifact M C # ashkelon # aspectj I would put this at M # cactus M # castor # changelog C M # changesC M # checkstyle M C # clean C M - I changed it not long back. # clover M # codeswitcher # consoleC # deploy O? # developer-activity C M # dist C # docbook M # earC M # eclipse M # ejb M # examples M # faq # file-activity C M # genapp M # gump M # hibernate # html2xdoc # idea # j2ee O # jalopy # jarC M # java C M # javadocC M # jbossM # jbuilder M # jdee # jdepend # jdeveloper # jdiff # jellydoc M # jnlp M # junit-report M # junitdoclet M # jxrC # latex # latka M # licenseC M # linkcheckM C # native # pdf M # perforce # plexus # plugin M # pmd # pomC M # releaseC # repository M C # runner # sea # shell # site # statcvsC # struts # summit # tasklist C M # test C M # torque # touchstone M C # touchstone-partner M C # uberjar M # vdoclet # war M # was40M # webserverO? M - peter lynch has updated this recently. # wizard # word2html M # xdoc M C There is a few plugins there that I don't know/understand so my marks may be off base here and there. It would be nice if one of the commiters checked in a plugin-map.xml xdoc that would contain a list of plugins similar to that one above, and then all commiters would add their name next to the plugins they are willing to work on, and their name in ( ) next to the plugins they know good enough to fix if they happen to break. That's what project.xml is for - if they're willing to work on it, add themselves as a developer/contributor As for the core/obsolete status of each plugin an IRC discussion with a sigle person writing down resolutions would probably be best. I second Michal's opinion that we should not put any more plugins into maven repository, and that some of the existing one should move away onto another CVS repo on maven.apache.org or even to the repos of their associated software projects. I thought maven-plugin was to be the new apache cvs repo for plugins once we worked out how to declare plugin usage. The notation for those dependencies is basicly in place, we might need to introduce addtional artifact types for that. Here's a snippet from a hypotetical plugin's project.xml: dependencies dependency dependencyTyperuntime/dependencyType groupIdmaven.apache.org/groupId artifactIdmaven-core-plugin/artifactId I believe it was agreed to use typemaven-plugin/type -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Work: http://www.multitask.com.au
cvs commit: maven/src/test/java/org/apache/maven/project ProjectInheritanceTest.java
dion2003/06/24 17:37:30
Modified:src/test/java/org/apache/maven/project
ProjectInheritanceTest.java
Log:
Fix so that this works on windows and other operating systems.
- the project.xml file has ${basedir}/src/java note the '/' used, it's not operating
system dependent
- the basedir being passed in is not the same as the one for the newly created
project, as all projects have basedir set to the project.xml location by default.
Revision ChangesPath
1.33 +2 -1
maven/src/test/java/org/apache/maven/project/ProjectInheritanceTest.java
Index: ProjectInheritanceTest.java
===
RCS file:
/home/cvs/maven/src/test/java/org/apache/maven/project/ProjectInheritanceTest.java,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- ProjectInheritanceTest.java 25 Jun 2003 00:10:23 - 1.32
+++ ProjectInheritanceTest.java 25 Jun 2003 00:37:30 - 1.33
@@ -69,7 +69,7 @@
private String TEST_DOCUMENT = null;
private String TEST_DOCUMENT2 = null;
private String baseDir;
-private String FS = System.getProperty( file.separator );
+private String FS = /; // note: same on windows and others
public ProjectInheritanceTest( String testName )
{
@@ -120,6 +120,7 @@
assertEquals( 1.4-dev-8,
( (Dependency) p.getDependencies().get( 1 ) ).getVersion() );
+baseDir = p.getContext().findVariable(basedir).toString();
// Test Source Directories
assertEquals( baseDir + FS + src/java, p.getBuild().getSourceDirectory()
);
// Unit Test Source Directories
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-516) Simian Plugin (fully documented and ready to use)
The following comment has been added to this issue: Author: Simon Harris Created: Tue, 24 Jun 2003 7:59 PM Body: Hey guys, I run checkstyle myself but I use the Ant plugin. If I were running maven I think I'd run the Maven plugin. Why? Well the fact is that on my source base checkstyle breaks the build and so does simian so really reporting is not much of an issue for me. I guess the other reason would be, as Aslak suggested, that it means I'm not tied to checkstyle (even though I love it!). Technically, there is no real reason. I imagine performance is pretty much the same in either case. The only major difference is that the Maven plugin has the cool links to the source code. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-516 Here is an overview of the issue: - Key: MAVEN-516 Summary: Simian Plugin (fully documented and ready to use) Type: New Feature Status: Unassigned Priority: Major Time Spent: Unknown Estimate: 0 minutes Project: maven Components: plugin-other Versions: 1.0-beta-10 Assignee: Reporter: Aslak Hellesy Created: Tue, 24 Jun 2003 6:54 AM Updated: Tue, 24 Jun 2003 6:55 AM Description: Simian (http://www.redhillconsulting.com.au/products/simian/index.html ) is a great little tool that detects duplicate source code. Very much like PMD's CPD (http://pmd.sourceforge.net/cpd.html), but a _lot_ faster. I have written a Maven report plugin for Simian that I'd like to contribute to Maven. Have a look at some sample reports: http://www.picocontainer.org/simian-report.html http://www.nanocontainer.org/simian-report.html It would be really nice to have the Simian Report included in the standard reports, as it reveals refactoring candidates and is something every sound project should have! - 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/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: Responsibility - was [RE: Simian Plugin (fully documented andready to use)\
[EMAIL PROTECTED] wrote: It would be nice if one of the commiters checked in a plugin-map.xml xdoc that would contain a list of plugins similar to that one above, and then all commiters would add their name next to the plugins they are willing to work on, and their name in ( ) next to the plugins they know good enough to fix if they happen to break. That's what project.xml is for - if they're willing to work on it, add themselves as a developer/contributor You are right, it's even better - provided that the information in the POMs is accurate - it would be gread if the commiters checked their entries. I second Michal's opinion that we should not put any more plugins into maven repository, and that some of the existing one should move away onto another CVS repo on maven.apache.org or even to the repos of their associated software projects. I thought maven-plugin was to be the new apache cvs repo for plugins once we worked out how to declare plugin usage. Yup, that repo is up already. Non core plugins could move there when the discovery/dependency stuff works. I believe it was agreed to use typemaven-plugin/type It's OK with me if it is an established policy. I would personaly opt for shorter 'plugin' name, because there is no ambiguity here - what other type of plugins artifact could we have? R. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven/src/test/java/org/apache/maven/projectProjectInheritanceTest.java
I believe this is now fixed, and if someone can tell me how to stop JUnit truncating messages like that.. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Work: http://www.multitask.com.au Incze Lajos [EMAIL PROTECTED] wrote on 25/06/2003 10:26:50 AM: On Wed, Jun 25, 2003 at 12:10:23AM +, [EMAIL PROTECTED] wrote: dion2003/06/24 17:10:23 Modified:src/test/java/org/apache/maven/project ProjectInheritanceTest.java Log: Someone should compile stuff first Not enough:) Should run, as well. The test fails with the message: === [exec] [junit] dir attribute ignored if running in the same VM [exec] [junit] Running org.apache.maven.project. ProjectInheritanceTest [exec] [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 6.826 sec [exec] [junit] [ERROR] TEST org.apache.maven.project. ProjectInheritanceTest FAILED === Testcase: testProjectMapping took 6.802 sec FAILED expected:.. but was:...test/extend/src/... junit.framework.ComparisonFailure: expected:.. but was:... test/extend/src/... at org.apache.maven.project.ProjectInheritanceTest. testProjectMapping(ProjectInheritanceTest.java:124) incze - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-516) Simian Plugin (fully documented and ready to use)
The following comment has been added to this issue: Author: Tom Copeland Created: Tue, 24 Jun 2003 9:25 PM Body: Note to self - twiddle CPD to make it faster :-) tom - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-516 Here is an overview of the issue: - Key: MAVEN-516 Summary: Simian Plugin (fully documented and ready to use) Type: New Feature Status: Unassigned Priority: Major Time Spent: Unknown Estimate: 0 minutes Project: maven Components: plugin-other Versions: 1.0-beta-10 Assignee: Reporter: Aslak Hellesy Created: Tue, 24 Jun 2003 6:54 AM Updated: Tue, 24 Jun 2003 6:55 AM Description: Simian (http://www.redhillconsulting.com.au/products/simian/index.html ) is a great little tool that detects duplicate source code. Very much like PMD's CPD (http://pmd.sourceforge.net/cpd.html), but a _lot_ faster. I have written a Maven report plugin for Simian that I'd like to contribute to Maven. Have a look at some sample reports: http://www.picocontainer.org/simian-report.html http://www.nanocontainer.org/simian-report.html It would be really nice to have the Simian Report included in the standard reports, as it reveals refactoring candidates and is something every sound project should have! - 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/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 project.xml
dion2003/06/24 20:35:40 Modified:.project.xml Log: Upgrade to less noisy version of ant tag lib Revision ChangesPath 1.280 +1 -1 maven/project.xml Index: project.xml === RCS file: /home/cvs/maven/project.xml,v retrieving revision 1.279 retrieving revision 1.280 diff -u -r1.279 -r1.280 --- project.xml 19 Jun 2003 23:25:42 - 1.279 +++ project.xml 25 Jun 2003 03:35:40 - 1.280 @@ -401,7 +401,7 @@ dependency groupIdcommons-jelly/groupId artifactIdcommons-jelly-tags-ant/artifactId - version20030211.142045/version + version20030625.032346/version urlhttp://jakarta.apache.org/commons/jelly/tags/ant//url /dependency dependency - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
