[jira] Closed: (MAVEN-1332) proxy firewall by NTLM authentication is not supported
Message: The following issue has been closed. Resolver: Emmanuel Venisse Date: Mon, 28 Jun 2004 3:44 AM Applied by Brett. We use commons-httpclient-2.0. - View the issue: http://jira.codehaus.org/browse/MAVEN-1332 Here is an overview of the issue: - Key: MAVEN-1332 Summary: proxy firewall by NTLM authentication is not supported Type: New Feature Status: Closed Priority: Major Resolution: FIXED Original Estimate: 3 hours Time Spent: Unknown Remaining: 3 hours Project: maven Components: core Fix Fors: 1.0-rc4 Versions: 1.0-rc3 Assignee: Brett Porter Reporter: george wang Created: Mon, 21 Jun 2004 5:16 PM Updated: Mon, 28 Jun 2004 3:44 AM Description: Some users reside inside a proxy firewall where NTLM authentication is used. Current implementation of maven does not support this authentication mechanisms. - 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]
repository src / javadocs for jars
I have been looking literally into the Maven Repository, is there any plans for the following to be added: 1) Source Code where available to correspond with the library jars ? 2) JavaDocs / API where available to correspond with the library jars ? Kind Regards Mark Ayad ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE : [Maven 1.0 branch] Problem with the bootstrap
Ok,
Thanks Brett.
I didn't found when you committed this change.
Why need we to produce a RC4 ?
Don't you think that the RC3 is more or less stable ??
Arnaud
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : lundi 28 juin 2004 01:08
À : Maven Developers List
Objet : Re: [Maven 1.0 branch] Problem with the bootstrap
That was awful dumb of me :)
I'll fix this up tonight when I cut the release for RC4.
Cheers,
Brett
Quoting Arnaud HERITIER [EMAIL PROTECTED]:
Hello guys,
I'm coming back after two weeks of inactivity and I
can't build maven
with the bootstrap.
The problem comes from the build-bootstrap ant file.
The get commands used to retrieve commons-logging and
http-client
jars use ${maven.get.jars.baseUrl} as source.
I replaced these lines
get ignoreerrors=true usetimestamp=true
dest=${maven.repo.local}/${cl-jar}
src=${maven.get.jars.baseUrl} /
get ignoreerrors=true usetimestamp=true
dest=${maven.repo.local}/${ch-jar}
src=${maven.get.jars.baseUrl}
/
with
get ignoreerrors=true usetimestamp=true
dest=${maven.repo.local}/${cl-jar}
src=${maven.get.jars.baseUrl}/${cl-jar} /
get ignoreerrors=true usetimestamp=true
dest=${maven.repo.local}/${ch-jar}
src=${maven.get.jars.baseUrl}/${ch-jar} /
And it works.
I attach the diff if a maven-core committer can apply it.
Thanks
Arnaud
-
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]
[jira] Closed: (MPMULTIPROJECT-36) Customized navigation no longer aggregated
Message: The following issue has been closed. Resolver: Brett Porter Date: Mon, 28 Jun 2004 5:34 AM add FAQ - View the issue: http://jira.codehaus.org/browse/MPMULTIPROJECT-36 Here is an overview of the issue: - Key: MPMULTIPROJECT-36 Summary: Customized navigation no longer aggregated Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-multiproject-plugin Versions: 1.3 Assignee: Brett Porter Reporter: Joerg Schaible Created: Tue, 15 Jun 2004 10:57 AM Updated: Mon, 28 Jun 2004 5:34 AM Description: Customized navigations no longer work with 1.3, since the variable used for the collection has been renamed from reactorProjects to multiprojects User's Guide: http://maven.apache.org/reference/user-guide.html#Multi_Project_Builds_and_the_Reactor Maven Wiki FAQ 4.20 - 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: (MPARTIFACT-21) distributionSite and distributionAddress
Message: The following issue has been closed. Resolver: Brett Porter Date: Mon, 28 Jun 2004 5:33 AM done - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-21 Here is an overview of the issue: - Key: MPARTIFACT-21 Summary: distributionSite and distributionAddress Type: Test Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-artifact-plugin Assignee: Brett Porter Reporter: Brett Porter Created: Sun, 27 Jun 2004 7:34 PM Updated: Mon, 28 Jun 2004 5:33 AM Description: check that distributionSite and distributionAddress from the POM still get honoured. Also, setup the appropriate properties in maven-plugins for this. - 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: (MPPMD-11) PMD report plugin fails if there is no src/java directory
Message: The following issue has been closed. Resolver: Brett Porter Date: Mon, 28 Jun 2004 5:36 AM if you can post some more information or a sample project, I'll reopen. However, on running pmd on a project with the source directory set to an invalid location, the pmd plugin succeeds. - View the issue: http://jira.codehaus.org/browse/MPPMD-11 Here is an overview of the issue: - Key: MPPMD-11 Summary: PMD report plugin fails if there is no src/java directory Type: Bug Status: Closed Priority: Major Resolution: CANNOT REPRODUCE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-pmd-plugin Assignee: Brett Porter Reporter: Michael Mattox Created: Thu, 17 Jun 2004 8:33 AM Updated: Mon, 28 Jun 2004 5:36 AM Environment: Maven 1.0rc3, win2k, jdk1.4.2 Description: The PMD report plugin fails if there is no src/java directory. This is a problem when using multiproject, because not all projects contain java src code. Specifically for me, my master project is just a base project which all my projects extend. Having PMD in the reports causes the plugin to run the report on my base project which contains no source. I think if there is no src/java it should not break a multiproject build. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jcoverage/announcements 1.0.2.ann 1.0.ann
brett 2004/06/28 02:39:03 Removed: jcoverage/announcements 1.0.2.ann 1.0.ann Log: remove announcements - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/xdocs/start install.xml
brett 2004/06/28 02:39:11
Modified:.Tag: MAVEN-1_0-BRANCH build-bootstrap.xml
src/conf Tag: MAVEN-1_0-BRANCH defaults.properties
src/java/org/apache/maven Tag: MAVEN-1_0-BRANCH
MavenConstants.java MavenSession.java
src/java/org/apache/maven/jelly Tag: MAVEN-1_0-BRANCH
MavenJellyContext.java
src/java/org/apache/maven/plugin Tag: MAVEN-1_0-BRANCH
PluginManager.java
xdocsTag: MAVEN-1_0-BRANCH changes.xml
xdocs/reference Tag: MAVEN-1_0-BRANCH user-guide.xml
xdocs/start Tag: MAVEN-1_0-BRANCH install.xml
Log:
split plugin cache (now in ~/.maven/cache) from local plugin installations
(~/.maven/plugins)
Revision ChangesPath
No revision
No revision
1.212.2.11 +2 -2 maven/build-bootstrap.xml
Index: build-bootstrap.xml
===
RCS file: /home/cvs/maven/build-bootstrap.xml,v
retrieving revision 1.212.2.10
retrieving revision 1.212.2.11
diff -u -r1.212.2.10 -r1.212.2.11
--- build-bootstrap.xml 27 Jun 2004 23:24:46 - 1.212.2.10
+++ build-bootstrap.xml 28 Jun 2004 09:39:09 - 1.212.2.11
@@ -44,7 +44,7 @@
| before bootstrapping.
|
| Maven bootstrap also expands plugins to
-| $${user.home}/.maven/plugins
+| $${user.home}/.maven/cache
| if you do not have the MAVEN_HOME_LOCAL environment
| variable or
| maven.home.local property set before bootstrapping.
@@ -438,7 +438,7 @@
mkdir dir=${maven.home}/plugins/
!-- cleanup the local plugins dir --
-delete dir=${maven.home.local}/plugins/
+delete dir=${maven.home.local}/cache/
/target
/project
No revision
No revision
1.8.4.5 +2 -1 maven/src/conf/defaults.properties
Index: defaults.properties
===
RCS file: /home/cvs/maven/src/conf/defaults.properties,v
retrieving revision 1.8.4.4
retrieving revision 1.8.4.5
diff -u -r1.8.4.4 -r1.8.4.5
--- defaults.properties 13 May 2004 10:15:54 - 1.8.4.4
+++ defaults.properties 28 Jun 2004 09:39:09 - 1.8.4.5
@@ -51,7 +51,8 @@
# M A V E N P L U G - I N D I R E C T O R Y
# ---
maven.plugin.dir = ${maven.home}/plugins
-maven.plugin.unpacked.dir = ${maven.home.local}/plugins
+maven.plugin.user.dir = ${maven.home.local}/plugins
+maven.plugin.unpacked.dir = ${maven.home.local}/cache
# ---
# M A V E N R E M O T E R E P O S
No revision
No revision
1.30.4.8 +4 -1 maven/src/java/org/apache/maven/MavenConstants.java
Index: MavenConstants.java
===
RCS file: /home/cvs/maven/src/java/org/apache/maven/MavenConstants.java,v
retrieving revision 1.30.4.7
retrieving revision 1.30.4.8
diff -u -r1.30.4.7 -r1.30.4.8
--- MavenConstants.java 27 Jun 2004 07:57:48 - 1.30.4.7
+++ MavenConstants.java 28 Jun 2004 09:39:09 - 1.30.4.8
@@ -105,6 +105,9 @@
/** MavenSession unpacked plugins context tag **/
public static final String MAVEN_UNPACKED_PLUGINS_DIR =
maven.plugin.unpacked.dir;
+/** MavenSession local plugins context tag **/
+public static final String MAVEN_USER_PLUGINS_DIR = maven.plugin.user.dir;
+
/** MavenSession build file url context tag **/
public static final String MAVEN_BUILD_FILE_URL = maven.project.buildFile.url;
1.18.4.13 +2 -2 maven/src/java/org/apache/maven/MavenSession.java
Index: MavenSession.java
===
RCS file: /home/cvs/maven/src/java/org/apache/maven/MavenSession.java,v
retrieving revision 1.18.4.12
retrieving revision 1.18.4.13
diff -u -r1.18.4.12 -r1.18.4.13
--- MavenSession.java 20 May 2004 15:34:53 - 1.18.4.12
+++ MavenSession.java 28 Jun 2004 09:39:09 - 1.18.4.13
@@ -62,7 +62,7 @@
public static final String DRIVER_SCRIPT_NAME = driver.jelly;
/** The current MavenSession version id */
-public static final String APP_VERSION = 1.0-final-SNAPSHOT;
+public static final String APP_VERSION = 1.0-rc4;
//
// C L A S S M E M B E R S
No revision
No revision
1.35.4.9 +12 -1 maven/src/java/org/apache/maven/jelly/MavenJellyContext.java
Index: MavenJellyContext.java
cvs commit: maven-plugins/artifact/xdocs changes.xml
brett 2004/06/28 02:40:14
Modified:artifact project.xml
artifact/src/main/org/apache/maven/artifact/deployer
DefaultArtifactDeployer.java
artifact/xdocs changes.xml
Log:
PR: MPARTIFACT-21
honour distributionSite
Revision ChangesPath
1.31 +2 -2 maven-plugins/artifact/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven-plugins/artifact/project.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- project.xml 25 Jun 2004 18:54:25 - 1.30
+++ project.xml 28 Jun 2004 09:40:14 - 1.31
@@ -25,8 +25,8 @@
nameMaven Artifact Plugin/name
!-- WARNING: some dependency checks will break if we get to 1.10, need to go to
2.0 from there --
- currentVersion1.3/currentVersion
- description/
+ currentVersion1.4-SNAPSHOT/currentVersion
+ descriptionTools to manage artifacts and deployment. Requires Maven 1.0
RC4/description
shortDescriptionTools to manage artifacts and deployment/shortDescription
urlhttp://maven.apache.org/reference/plugins/artifact//url
issueTrackingUrlhttp://jira.codehaus.org/browse/MPARTIFACT/issueTrackingUrl
1.22 +8 -3
maven-plugins/artifact/src/main/org/apache/maven/artifact/deployer/DefaultArtifactDeployer.java
Index: DefaultArtifactDeployer.java
===
RCS file:
/home/cvs/maven-plugins/artifact/src/main/org/apache/maven/artifact/deployer/DefaultArtifactDeployer.java,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- DefaultArtifactDeployer.java 25 Jun 2004 13:50:05 - 1.21
+++ DefaultArtifactDeployer.java 28 Jun 2004 09:40:14 - 1.22
@@ -350,7 +350,12 @@
if (repoStr == null || repoStr.trim().length() == 0)
{
-String central = (String)
project.getContext().getVariable(maven.repo.central);
+String central = project.getDistributionSite();
+String centralDirectory = project.getDistributionDirectory();
+if (central == null || central.trim().length() == 0) {
+central = (String)
project.getContext().getVariable(maven.repo.central);
+centralDirectory = (String)
project.getContext().getVariable(maven.repo.central.directory);
+}
if (central != null central.trim().length() 0) {
repoStr = default;
project.getContext().setVariable(maven.repo.default, scp:// +
central);
@@ -361,7 +366,7 @@
LOG.warn( WARNING: assuming empty passphrase. Specify
maven.repo.default.passphrase if needed );
project.getContext().setVariable(maven.repo.default.passphrase, );
}
-project.getContext().setVariable(maven.repo.default.directory,
project.getContext().getVariable(maven.repo.central.directory));
+project.getContext().setVariable(maven.repo.default.directory,
centralDirectory);
project.getContext().setVariable(maven.repo.default.username,
project.getContext().getVariable(maven.username));
project.getContext().setVariable(maven.repo.default.group,
project.getContext().getVariable(maven.remote.group));
}
1.22 +3 -0 maven-plugins/artifact/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/artifact/xdocs/changes.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- changes.xml 25 Jun 2004 18:54:25 - 1.21
+++ changes.xml 28 Jun 2004 09:40:14 - 1.22
@@ -25,6 +25,9 @@
author email=[EMAIL PROTECTED]Vincent Massol/author
/properties
body
+release version=1.4-SNAPSHOT date=in CVS
+ action dev=brett type=addAllow use of distributionSite POM attribute in
artifact method/action
+/release
release version=1.3 date=2004-06-25
action dev=brett type=add issue=MPARTIFACT-8 due-to=Matt SmithAllow
non-passive FTP/action
action dev=brett type=add issue=MPARTIFACT-20Fix copy-deps when list
is empty/action
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/plugin/xdocs changes.xml
brett 2004/06/28 02:42:48
Modified:plugin plugin.jelly project.xml
plugin/xdocs changes.xml
Log:
separate cache from plusing directory
Revision ChangesPath
1.39 +18 -36maven-plugins/plugin/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/plugin/plugin.jelly,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- plugin.jelly 25 Jun 2004 16:52:18 - 1.38
+++ plugin.jelly 28 Jun 2004 09:42:48 - 1.39
@@ -44,33 +44,28 @@
ant:fail
Must remove the deploy plugin to use this version of the plugin plugin.
Please delete ${deployPlugin.artifactId}-${deployPlugin.currentVersion}.jar
from
-${maven.plugin.dir} and ${maven.plugin.unpacked.dir} (if it exists)
+${maven.plugin.dir} and ${maven.plugin.user.dir} (if it exists)
/ant:fail
/j:if
/j:if
- goal name=plugin
-description=Build a plugin jar and install to the maven.repo.local
-
-!-- Plugins are just a jar. --
-attainGoal name=jar:jar/
-
-copy file=${maven.build.dir}/${maven.final.name}.jar
- todir=${maven.repo.local}/${pom.groupId}/plugins /
-
+ goal name=plugin prereqs=plugin:plugin description=Build a plugin jar /
+ goal name=plugin:plugin description=Build a plugin jar
+!-- For some reason a prereq on this causes an internal error... --
+attainGoal name=jar:jar /
/goal
- goal name=plugin:install prereqs=plugin
+ goal name=plugin:install prereqs=plugin:plugin
description=Install the plugin jar, prepare Maven to expand it locally and
clear caches
plugin:uninstall name=${pom.artifactId} /
-!-- Don't clear the cache. RC3 will do this if we happened to clean up an
additional version --
+!-- Don't clear the cache. Maven will do this if we happened to clean up an
additional version --
copy file=${maven.build.dir}/${maven.final.name}.jar
- todir=${maven.home}/plugins/
+ todir=${maven.plugin.dir} /
/goal
- goal name=plugin:install-now prereqs=plugin
+ goal name=plugin:install-now prereqs=plugin:plugin
description=Build a plugin and load it into the currently running instance of
Maven.
!-- The cache should remain intact through these operations --
plugin:uninstall name=${pom.artifactId} /
@@ -90,21 +85,6 @@
maven:uninstallPlugin artifactId=${pom.artifactId} /
/goal
- goal name=plugin:deploy prereqs=plugin
-description=Install a specific unpacked plugin but no new jar
-
-mkdir dir=${maven.plugin.unpacked.dir}/${maven.final.name}/
-unzip src=${maven.build.dir}/${maven.final.name}.jar
- dest=${maven.plugin.unpacked.dir}/${maven.final.name}/
-
-echo message=
- Warning: Contents of ${maven.home}/plugins/${maven.final.name}.jar does not match
- the unpacked contents of ${maven.plugin.unpacked.dir}/${maven.final.name}
directory.
-/echo
-
- /goal
-
-
!-- generate documentation --
!-- generate docs that are usually missing --
@@ -220,7 +200,7 @@
goal name=plugin:download description=download and install a plugin from a
remote repo prereqs=plugin:download-artifact
plugin:uninstall name=${artifactId} /
-u:file var=localPlugin
name=${maven.home}/plugins/${artifactId}-${version}.jar /
+u:file var=localPlugin
name=${maven.plugin.dir}/${artifactId}-${version}.jar /
ant:copy file=${localPluginFile} tofile=${localPlugin} /
/goal
@@ -282,7 +262,7 @@
/u:available
/goal
- goal name=plugin:repository-install prereqs=plugin
+ goal name=plugin:repository-install prereqs=plugin:plugin
artifact:install
artifact=${maven.build.dir}/${maven.final.name}.jar
type=plugin
@@ -290,7 +270,7 @@
/
/goal
- goal name=plugin:repository-install-snapshot prereqs=plugin
+ goal name=plugin:repository-install-snapshot prereqs=plugin:plugin
artifact:install-snapshot
artifact=${maven.build.dir}/${maven.final.name}.jar
type=plugin
@@ -298,7 +278,7 @@
/
/goal
- goal name=plugin:repository-deploy prereqs=plugin
+ goal name=plugin:repository-deploy prereqs=plugin:plugin
artifact:deploy
artifact=${maven.build.dir}/${maven.final.name}.jar
type=plugin
@@ -306,7 +286,7 @@
/
/goal
- goal name=plugin:repository-deploy-snapshot prereqs=plugin
+ goal name=plugin:repository-deploy-snapshot prereqs=plugin:plugin
artifact:deploy-snapshot
artifact=${maven.build.dir}/${maven.final.name}.jar
type=plugin
@@ -317,7 +297,10 @@
define:taglib uri=plugin
define:tag name=uninstall
ant:delete verbose=false failonerror=false
-
[jira] Commented: (MPJAR-20) Wrong permissions on JAR and repository directories.
The following comment has been added to this issue: Author: Brett Porter Created: Mon, 28 Jun 2004 5:44 AM Body: the patches do not address the original bug (and no longer apply) - View this comment: http://jira.codehaus.org/browse/MPJAR-20?page=comments#action_21102 - View the issue: http://jira.codehaus.org/browse/MPJAR-20 Here is an overview of the issue: - Key: MPJAR-20 Summary: Wrong permissions on JAR and repository directories. Type: Bug Status: Open Priority: Major Original Estimate: 10 minutes Time Spent: Unknown Remaining: 10 minutes Project: maven-jar-plugin Assignee: Brett Porter Reporter: Yoway Buorn Created: Tue, 16 Dec 2003 12:33 PM Updated: Mon, 28 Jun 2004 5:44 AM Environment: Unix. Description: jar:deploy-snapshot should chmod -R a+rx the repository directory. For example, say you've got this on your repository: /maven /some-plugin /jars /some-plugin-1.0.jar It should do a chmod -R a+rx inside /maven. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/pmd/xdocs faq.fml
brett 2004/06/28 02:46:48
Modified:cruisecontrol/xdocs faq.fml
pmd/xdocs faq.fml
Log:
update source elements to format better
Revision ChangesPath
1.3 +3 -9 maven-plugins/cruisecontrol/xdocs/faq.fml
Index: faq.fml
===
RCS file: /home/cvs/maven-plugins/cruisecontrol/xdocs/faq.fml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- faq.fml 26 Jun 2004 02:30:14 - 1.2
+++ faq.fml 28 Jun 2004 09:46:48 - 1.3
@@ -27,17 +27,11 @@
faq id=change-template
questionHow do I change the template used to generate
codecruisecontrol.xml/code configuration file?/question
answer
-If you specify your own maven.cruisecontrol.template, then that will be used
+If you specify your own codemaven.cruisecontrol.template/code, then
that will be used
instead. If you want to wrap all of your logic up in your own plugin so
that
you don't have to set each project individually, then specify it like this:
-
codemaven.cruisecontrol.template=${maven.home}/plugins/my-company-plugin-0.1/plugin-resources/cruisecontrol.jsl/code
-and add to your plugin.xml this:
-source![CDATA[
-preGoal name=build:start
- ant:property name=maven.cruisecontrol.template
value=${anite.cruisecontrol.template}/
- maven:pluginVar plugin=maven-cruisecontrol-plugin
property=maven.cruisecontrol.template var=loc/
-/preGoal]]/source
-Note, this is a very brittle solution and suggestions on how to not
hardcode the path would be appreciated!
+source![CDATA[
+maven.cruisecontrol.template=${plugin.resources}/my-cc-template.jsl]]/source
/answer
/faq
1.2 +24 -40maven-plugins/pmd/xdocs/faq.fml
Index: faq.fml
===
RCS file: /home/cvs/maven-plugins/pmd/xdocs/faq.fml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- faq.fml 12 Jun 2004 03:19:36 - 1.1
+++ faq.fml 28 Jun 2004 09:46:48 - 1.2
@@ -62,11 +62,8 @@
maven 1.0-rc1), you issue the following command to maven to
download the version of your choice.
/p
- source
-![CDATA[
- $ maven -DgroupId=maven -DartifactId=maven-pmd-plugin -Dtype=plugin -Dversion=1.3
plugin:download
-]]
- /source
+ source![CDATA[
+$ maven -DgroupId=maven -DartifactId=maven-pmd-plugin -Dtype=plugin -Dversion=1.3
plugin:download]]/source
p
This command will download the plugin, remove the other versions of
the maven-pmd-plugin and make this recently downloaded version
@@ -94,15 +91,12 @@
project descriptor/a.
/p
-source
-![CDATA[
- reports
-...
-reportmaven-pmd-plugin/report
-...
- /reports
-]]
-/source
+source![CDATA[
+reports
+ ...
+ reportmaven-pmd-plugin/report
+ ...
+/reports]]/source
/answer
/faq
@@ -117,29 +111,23 @@
maven.xml:
/p
-source
-![CDATA[
+source![CDATA[
?xml version=1.0?
preGoal name=site:generate
attainGoal name=pmd/
- /preGoal
-]]
-/source
+ /preGoal]]/source
p
The generated report has to be added manually to the
website which is usually done with navigation.xml.
/p
-source
-![CDATA[
+source![CDATA[
?xml version=1.0?
menu name=Custom Reports
item name=PMD Report href=/pmd-report.html/
!-- Add more custom reports here --
- /menu
-]]
-/source
+ /menu]]/source
/answer
/faq
@@ -210,11 +198,8 @@
p
The default setting for the codemaven.pmd.rulesetfiles/code
property is:
- source
-![CDATA[
- maven.pmd.rulesetfiles =
rulesets/basic.xml,rulesets/unusedcode.xml,rulesets/imports.xml
-]]
- /source
+ source![CDATA[
+maven.pmd.rulesetfiles =
rulesets/basic.xml,rulesets/unusedcode.xml,rulesets/imports.xml]]/source
/p
p
The following list of default pmd rulesets was obtained from
@@ -245,8 +230,7 @@
p
Example of a custom ruleset, saved as file called
codefavorite-pmd.xml/code in your project root.
- source
-![CDATA[
+ source![CDATA[
?xml version=1.0?
ruleset name=Favorites
@@ -267,18 +251,13 @@
cvs commit: maven-plugins/jar plugin.jelly
brett 2004/06/28 02:51:29
Modified:jar plugin.jelly
Log:
update comment for directory changes
Revision ChangesPath
1.40 +1 -1 maven-plugins/jar/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/jar/plugin.jelly,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- plugin.jelly 25 Jun 2004 16:52:18 - 1.39
+++ plugin.jelly 28 Jun 2004 09:51:29 - 1.40
@@ -43,7 +43,7 @@
ant:fail
Must remove the deploy plugin to use this version of the jar plugin.
Please delete ${deployPlugin.artifactId}-${deployPlugin.currentVersion}.jar
from
-${maven.plugin.dir} and ${maven.plugin.unpacked.dir} (if it exists)
+${maven.plugin.dir} and ${maven.plugin.user.dir} (if it exists)
/ant:fail
/j:if
/j:if
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPARTIFACT-13) plugin doesn't handle SNAPSHOT versions correctly
The following comment has been added to this issue: Author: Michal Maczka Created: Mon, 28 Jun 2004 5:50 AM Body: If it helps you can use currrentVersion1.0-SNAPHOT/currentVersion and jar:deploy goal. Only drawback at the moment is that snapshot-version files won't be deployed to remote repository. If you can live without them this might be a solution until this problem is fixed. - View this comment: http://jira.codehaus.org/browse/MPARTIFACT-13?page=comments#action_21103 - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-13 Here is an overview of the issue: - Key: MPARTIFACT-13 Summary: plugin doesn't handle SNAPSHOT versions correctly Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-artifact-plugin Versions: 1.0 1.1 Assignee: Reporter: Matthias Kerkhoff Created: Wed, 28 Apr 2004 3:44 PM Updated: Mon, 28 Jun 2004 5:50 AM Description: If the current version is something different than SNAPSHOT, the artifact plugin will fail to correctly deploy or install snapshot artifacts. Let's assume a currentVersion1.2-SNAPSHOT/currentVersion. Try it for yourself -- the artifact plugin will replace the 1.2-SNAPSHOT with SNAPSHOT. This is quite ugly in projects which may have multiple SNAPSHOTs. (Typically this happens in projects with concurrently developed branches. In such projects, SNAPSHOT versions have to be further qualified, usually with their version number as in my example.) We have a working solution, which we may attach to this issue, if you like. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/multiproject/xdocs faq.fml
brett 2004/06/28 02:53:07
Modified:multiproject/xdocs faq.fml
Log:
PR: MPMULTIPROJECT-36
address issue
Revision ChangesPath
1.4 +31 -26maven-plugins/multiproject/xdocs/faq.fml
Index: faq.fml
===
RCS file: /home/cvs/maven-plugins/multiproject/xdocs/faq.fml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- faq.fml 4 Mar 2004 18:36:33 - 1.3
+++ faq.fml 28 Jun 2004 09:53:07 - 1.4
@@ -18,30 +18,35 @@
--
faqs title=Frequently Asked Questions
-part id=using
-titleUsing Multiproject/title
-faq id=resources-not-included-in-artifacts
-questionWhen using multiproject to build subprojects, resources are
not included in my artifacts. Why?/question
-answer
-Use ${basedir} in your subproject's POM resource section:
-p
-source
-![CDATA[
- resources
- resource
-
directory${basedir}/src/java/directory
- includes
-
include**/*.properties/include
- /includes
- /resource
- /resources
- ]]
-/source
-/p
-p
-The resources won't be included if you just specify src/java
as directory unless maven is started from within the subproject directory.
-/p
-/answer
-/faq
-/part
+ part id=using
+titleUsing Multiproject/title
+faq id=collect-var-change
+ questionMy custom navigation uses codereactorProjects/code, and when I
upgraded it broke. Why?/question
+ answer
+codereactorProjects/code is reused by anything using the reactor. Since
there is no concept of scope or
+nesting, the variable codemultiprojects/code is now used instead. If
you change your variable references,
+this should start working again.
+ /answer
+/faq
+faq id=resources-not-included-in-artifacts
+ questionWhen using multiproject to build subprojects, resources are not
included in my artifacts. Why?/question
+ answer
+Use ${basedir} in your subproject's POM resource section:
+p
+ source![CDATA[
+resources
+ resource
+directory${basedir}/src/java/directory
+includes
+ include**/*.properties/include
+ /includes
+ /resource
+/resources]]/source
+/p
+p
+ The resources won't be included if you just specify src/java as
directory unless maven is started from within the subproject directory.
+/p
+ /answer
+/faq
+ /part
/faqs
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Self-dependent plugin
-Original Message- From: Julian Scheid [mailto:[EMAIL PROTECTED] Sent: Monday, June 28, 2004 5:45 AM To: [EMAIL PROTECTED] Subject: Self-dependent plugin Hello Maven friends, In general, what do Maven experts think: is the Maven architecture prepared for self-dependent projects like this, or should I better stick to the lower-level approach, Ant, for this particular kind of project? I don't think that Maven is prepared for such uses case. Generally it is not good idea to introduce such self dependency early in life cycle of the project. In the best case incremental development should work. Eg. you have fully functional version 0.1 of your tool and you are working on version 0.2 but internally you should be using version 0.1 for building version 0.2 Bootstrap system for maven1 is written using ant, for maven2 using unix scripts. IMO such solution is needed in initial phases of development. When project matures things might look differently. For example CVS sources are kept in CVS, SVN sources are kept in SVN repository, Javacc uses javacc for parsing its grammar files, AFAIK Ant can be also build with ant. This is just a sign of maturity of given project and requires that at least one fully reliable version exits and futures which are used internally don't go beyond this version. Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: repository src / javadocs for jars
-Original Message- From: Mark Ayad [mailto:[EMAIL PROTECTED] Sent: Monday, June 28, 2004 11:05 AM To: '[EMAIL PROTECTED]' Subject: repository src / javadocs for jars I have been looking literally into the Maven Repository, is there any plans for the following to be added: 1) Source Code where available to correspond with the library jars ? 2) JavaDocs / API where available to correspond with the library jars ? Kind Regards Mark Ayad We are working on that. Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: repository src / javadocs for jars
All Compressed in .jar format I hope. -Original Message- From: Maczka Michal [mailto:[EMAIL PROTECTED] Sent: 28 June 2004 10:02 To: 'Maven Developers List' Subject: RE: repository src / javadocs for jars -Original Message- From: Mark Ayad [mailto:[EMAIL PROTECTED] Sent: Monday, June 28, 2004 11:05 AM To: '[EMAIL PROTECTED]' Subject: repository src / javadocs for jars I have been looking literally into the Maven Repository, is there any plans for the following to be added: 1) Source Code where available to correspond with the library jars ? 2) JavaDocs / API where available to correspond with the library jars ? Kind Regards Mark Ayad We are working on that. Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPCHANGES-17) jira links don't work with /browse/ form
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPCHANGES-17 Here is an overview of the issue: - Key: MPCHANGES-17 Summary: jira links don't work with /browse/ form Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-changes-plugin Assignee: Reporter: Brett Porter Created: Mon, 28 Jun 2004 6:12 AM Updated: Mon, 28 Jun 2004 6:12 AM Description: they append the ViewIssue to /browse/ - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPJAVADOC-29) broken on jdk 1.3 for multiple packages
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-29 Here is an overview of the issue: - Key: MPJAVADOC-29 Summary: broken on jdk 1.3 for multiple packages Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-javadoc-plugin Assignee: Jason van Zyl Reporter: Brett Porter Created: Mon, 28 Jun 2004 6:13 AM Updated: Mon, 28 Jun 2004 6:13 AM Description: works in 1.4, but under 1.3 the packages are all meshed into one. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPJAVADOC-29) broken on jdk 1.3 for multiple packages
The following comment has been added to this issue: Author: Arnaud HERITIER Created: Mon, 28 Jun 2004 6:32 AM Body: I'll try to reproduce it tonight. - View this comment: http://jira.codehaus.org/browse/MPJAVADOC-29?page=comments#action_21104 - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-29 Here is an overview of the issue: - Key: MPJAVADOC-29 Summary: broken on jdk 1.3 for multiple packages Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-javadoc-plugin Assignee: Jason van Zyl Reporter: Brett Porter Created: Mon, 28 Jun 2004 6:13 AM Updated: Mon, 28 Jun 2004 6:32 AM Description: works in 1.4, but under 1.3 the packages are all meshed into one. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPJAVADOC-28) @link tag not working with package names
The following comment has been added to this issue: Author: Arnaud HERITIER Created: Mon, 28 Jun 2004 6:37 AM Body: Brett, will you try to resolve this bug ? - View this comment: http://jira.codehaus.org/browse/MPJAVADOC-28?page=comments#action_21105 - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-28 Here is an overview of the issue: - Key: MPJAVADOC-28 Summary: @link tag not working with package names Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-javadoc-plugin Assignee: Brett Porter Reporter: Maarten Coene Created: Fri, 25 Jun 2004 7:54 AM Updated: Mon, 28 Jun 2004 6:37 AM Description: I have a coulple of [EMAIL PROTECTED] package-name} tags in my javadocs, however, the javadoc plugin can resolve them to an URL. For instance: http://www.dom4j.org/xref/org/dom4j/DocumentType.html has links to the org.dom4j.dtd package. But if I generate the javadoc with maven, I receive this warning: src\java\org\dom4j\DocumentType.java:52: warning - Tag @link: reference not found: org.dom4j.dtd. But if I generate the javadocs with the Ant javadoc task myself, these links are resolved correctly!! For instance: http://www.dom4j.org/dom4j-1.4/apidocs/org/dom4j/DocumentType.html is the javadoc generated by the build.xml of dom4j which does only call the javadoc task provided by Ant. Maarten - 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/maven-jelly-tags .cvsignore
brett 2004/06/28 04:06:35 Removed: maven-jelly-tags Tag: MAVEN-1_0-BRANCH .cvsignore Log: delete from head - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPJAVADOC-28) @link tag not working with package names
The following comment has been added to this issue: Author: Brett Porter Created: Mon, 28 Jun 2004 7:09 AM Body: not for a little bit... if you have an idea of how to fix it, feel free to reassign to yourself. - View this comment: http://jira.codehaus.org/browse/MPJAVADOC-28?page=comments#action_21107 - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-28 Here is an overview of the issue: - Key: MPJAVADOC-28 Summary: @link tag not working with package names Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-javadoc-plugin Assignee: Brett Porter Reporter: Maarten Coene Created: Fri, 25 Jun 2004 7:54 AM Updated: Mon, 28 Jun 2004 7:09 AM Description: I have a coulple of [EMAIL PROTECTED] package-name} tags in my javadocs, however, the javadoc plugin can resolve them to an URL. For instance: http://www.dom4j.org/xref/org/dom4j/DocumentType.html has links to the org.dom4j.dtd package. But if I generate the javadoc with maven, I receive this warning: src\java\org\dom4j\DocumentType.java:52: warning - Tag @link: reference not found: org.dom4j.dtd. But if I generate the javadocs with the Ant javadoc task myself, these links are resolved correctly!! For instance: http://www.dom4j.org/dom4j-1.4/apidocs/org/dom4j/DocumentType.html is the javadoc generated by the build.xml of dom4j which does only call the javadoc task provided by Ant. Maarten - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/plugin/xdocs changes.xml
brett 2004/06/28 04:13:18 Modified:plugin project.xml plugin/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.5 Revision ChangesPath 1.39 +6 -1 maven-plugins/plugin/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/plugin/project.xml,v retrieving revision 1.38 retrieving revision 1.39 diff -u -r1.38 -r1.39 --- project.xml 28 Jun 2004 09:42:48 - 1.38 +++ project.xml 28 Jun 2004 11:13:17 - 1.39 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-plugin-plugin/id nameMaven Plugin Plugin/name - currentVersion1.5-SNAPSHOT/currentVersion + currentVersion1.5/currentVersion descriptionMaven Plugin management plugin. Requires Maven 1.0 RC4./description shortDescriptionMaven Plugin plugin/shortDescription urlhttp://maven.apache.org/reference/plugins/plugin//url @@ -49,6 +49,11 @@ id1.4/id name1.4/name tagMAVEN_PLUGIN_1_4/tag +/version +version + id1.5/id + name1.5/name + tagMAVEN_PLUGIN_1_5/tag /version /versions developers 1.24 +1 -1 maven-plugins/plugin/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/plugin/xdocs/changes.xml,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- changes.xml 28 Jun 2004 09:42:48 - 1.23 +++ changes.xml 28 Jun 2004 11:13:18 - 1.24 @@ -24,7 +24,7 @@ author email=[EMAIL PROTECTED]Emmanuel Venisse/author /properties body -release version=1.5-SNAPSHOT date=in CVS +release version=1.5 date=2004-06-28 action dev=brett type=fix issue=MPPLUGIN-16Install to maven.plugin.dir instead of maven.home/plugins/action action dev=brett type=updateMore consistency in default goal naming (plugin:plugin)/action action dev=brett type=updateplugin goal no longer installs to local repository: use plugin:repository-install/action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE : [jira] Commented: (MPJAVADOC-28) @link tag not working with package names
Ok, I will try to look at MPJAVADOC-28 and MPJAVADOC-29 tonight. Arnaud -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Envoyé : lundi 28 juin 2004 13:11 À : [EMAIL PROTECTED] Objet : [jira] Commented: (MPJAVADOC-28) @link tag not working with package names The following comment has been added to this issue: Author: Brett Porter Created: Mon, 28 Jun 2004 7:09 AM Body: not for a little bit... if you have an idea of how to fix it, feel free to reassign to yourself. - View this comment: http://jira.codehaus.org/browse/MPJAVADOC-28?page=comments#act ion_21107 - View the issue: http://jira.codehaus.org/browse/MPJAVADOC-28 Here is an overview of the issue: - Key: MPJAVADOC-28 Summary: @link tag not working with package names Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-javadoc-plugin Assignee: Brett Porter Reporter: Maarten Coene Created: Fri, 25 Jun 2004 7:54 AM Updated: Mon, 28 Jun 2004 7:09 AM Description: I have a coulple of [EMAIL PROTECTED] package-name} tags in my javadocs, however, the javadoc plugin can resolve them to an URL. For instance: http://www.dom4j.org/xref/org/dom4j/DocumentType.html has links to the org.dom4j.dtd package. But if I generate the javadoc with maven, I receive this warning: src\java\org\dom4j\DocumentType.java:52: warning - Tag @link: reference not found: org.dom4j.dtd. But if I generate the javadocs with the Ant javadoc task myself, these links are resolved correctly!! For instance: http://www.dom4j.org/dom4j-1.4/apidocs/org/dom4j/DocumentType. html is the javadoc generated by the build.xml of dom4j which does only call the javadoc task provided by Ant. Maarten - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPJCOVERAGE-9) Bad path to stylesheet generated
The following comment has been added to this issue: Author: Trond Arve Wasskog Created: Mon, 28 Jun 2004 7:23 AM Body: We see the same behaviour, using the default value for the stylesheet property (on Win2K and Linux, maven-jcoverage-plugin v1.0.4). - View this comment: http://jira.codehaus.org/browse/MPJCOVERAGE-9?page=comments#action_21108 - View the issue: http://jira.codehaus.org/browse/MPJCOVERAGE-9 Here is an overview of the issue: - Key: MPJCOVERAGE-9 Summary: Bad path to stylesheet generated Type: Bug Status: Open Priority: Major Original Estimate: 0 minutes Time Spent: Unknown Remaining: 0 minutes Project: maven-jcoverage-plugin Versions: 1.0.3 1.0.4 1.0.5 Assignee: Emmanuel Venisse Reporter: Philippe Mouawad Created: Thu, 3 Jun 2004 10:06 AM Updated: Mon, 28 Jun 2004 7:23 AM Environment: Windows NT Description: When I use jcoverage plugin, it generate HTML files with the following kind of path for stylesheet: link rel =stylesheet type=text/css href=\.\./\.\./\.\./style.css title=Style As you can see there is \. that should be . This results into the browser not finding the stylesheet. I opened the code and replaced return new Perl5Util().substitute(s/[^\\.]*(\\.|$)/\\.\\.\\//g, path); by return new Perl5Util().substitute(s/[^\\.]*(\\.|$)/..\\//g, path); In method org.apache.maven.jcoveragereport.CoverageReport = private String getRelativePath(String path) In fact if you look at ; http://jakarta.apache.org/oro/api/org/apache/oro/text/perl/Perl5Util.html In the following example: line = util.substitute(s/description1\\.html/about1.html/, line); They don't escape the . in the replacement string. and it know generates good pathes. Since I didn't find a bug for this I thought I may be doing something wrong, could you help me please. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jar/xdocs changes.xml
brett 2004/06/28 04:26:31 Modified:jar project.xml jar/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.6 Revision ChangesPath 1.29 +6 -1 maven-plugins/jar/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/jar/project.xml,v retrieving revision 1.28 retrieving revision 1.29 diff -u -r1.28 -r1.29 --- project.xml 25 Jun 2004 15:24:28 - 1.28 +++ project.xml 28 Jun 2004 11:26:31 - 1.29 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-jar-plugin/id nameMaven Jar Plug-in/name - currentVersion1.6-SNAPSHOT/currentVersion + currentVersion1.6/currentVersion descriptionPlugin for creating JAR files. Requires Maven 1.0 RC2./description shortDescriptionCreate jar files/shortDescription urlhttp://maven.apache.org/reference/plugins/jar//url @@ -44,6 +44,11 @@ id1.5/id name1.5/name tagMAVEN_JAR_1_5/tag +/version +version + id1.6/id + name1.6/name + tagMAVEN_JAR_1_6/tag /version /versions developers/ 1.21 +1 -1 maven-plugins/jar/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/jar/xdocs/changes.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- changes.xml 25 Jun 2004 13:52:23 - 1.20 +++ changes.xml 28 Jun 2004 11:26:31 - 1.21 @@ -25,7 +25,7 @@ author email=[EMAIL PROTECTED]dIon Gillard/author /properties body -release version=1.6 date=In CVS +release version=1.6 date=2004-06-28 action dev=brett type=updateUse the artifact plugin for installation/action action dev=evenisse type=fix due-to=Martin van den Bemt issue=MPJAR-29Replace Apache Jakarta Maven by Apache Maven in Manifest/action /release - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/pmd/xdocs changes.xml
brett 2004/06/28 04:31:23 Modified:pmd project.xml pmd/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.5 Revision ChangesPath 1.28 +6 -1 maven-plugins/pmd/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/pmd/project.xml,v retrieving revision 1.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- project.xml 25 Jun 2004 15:24:30 - 1.27 +++ project.xml 28 Jun 2004 11:31:23 - 1.28 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-pmd-plugin/id nameMaven PMD Plug-in/name - currentVersion1.5-SNAPSHOT/currentVersion + currentVersion1.5/currentVersion descriptionThe Maven PMD plugin is a plugin that wraps the PMD framework (http://pmd.sourceforge.net). PMD is a source checking framework that works by scanning Java source code and looks for potential problems like: unused local variables, empty catch blocks, unused parameters, empty 'if' statements, etc./description shortDescriptionMaven Plugin for PMD/shortDescription urlhttp://maven.apache.org/reference/plugins/pmd//url @@ -59,6 +59,11 @@ id1.4/id name1.4/name tagMAVEN_PMD_1_4/tag +/version +version + id1.5/id + name1.5/name + tagMAVEN_PMD_1_5/tag /version /versions developers 1.23 +2 -4 maven-plugins/pmd/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/pmd/xdocs/changes.xml,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- changes.xml 12 Jun 2004 03:19:36 - 1.22 +++ changes.xml 28 Jun 2004 11:31:23 - 1.23 @@ -25,10 +25,8 @@ author email=[EMAIL PROTECTED]Vincent Massol/author /properties body -release version=1.5-SNAPSHOT date=in CVS - action dev=brett due-to=Joakim Erdfelt issue=MPPMD-2 type=update -Upgrade to PMD 1.3, clean up and improve documentation. - /action +release version=1.5 date=2004-06-28 + action dev=brett due-to=Joakim Erdfelt issue=MPPMD-2 type=updateUpgrade to PMD 1.3, clean up and improve documentation./action /release release version=1.4 date=2004-05-15 action dev=brett type=fix issue=MPPMD-7Create directories that exist under maven.build.dir before using them so it works after clean./action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven PMD Plugin 1.5 Released
The maven team is pleased to announce the Maven PMD Plug-in 1.5 release! http://maven.apache.org/reference/plugins/pmd/ The Maven PMD plugin is a plugin that wraps the PMD framework (http://pmd.sourceforge.net). PMD is a source checking framework that works by scanning Java source code and looks for potential problems like: unused local variables, empty catch blocks, unused parameters, empty 'if' statements, etc. Changes in this version include: Changes: o Upgrade to PMD 1.3, clean up and improve documentation. Issue: MPPMD-2. Thanks to Joakim Erdfelt. To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-pmd-plugin -Dversion=1.5 For a manual installation, you can download the plugin here: http://www.ibiblio.org/maven/maven/plugins/maven-pmd-plugin-1.5.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jcoverage/xdocs changes.xml
brett 2004/06/28 04:37:59 Modified:jcoverage project.xml jcoverage/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.0.5 Revision ChangesPath 1.25 +6 -1 maven-plugins/jcoverage/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/jcoverage/project.xml,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- project.xml 25 Jun 2004 15:24:29 - 1.24 +++ project.xml 28 Jun 2004 11:37:59 - 1.25 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-jcoverage-plugin/id nameMaven JCoverage plugin/name - currentVersion1.0.5-SNAPSHOT/currentVersion + currentVersion1.0.5/currentVersion packageorg.apache.maven.jcoveragereport/package descriptionThis plugin provides coverage analysis of your source-code based on the open-source jcoverage tool./description shortDescriptionThis plugin provides coverage analysis of your source-code based on the open-source jcoverage tool./shortDescription @@ -50,6 +50,11 @@ id1.0.4/id name1.0.4/name tagMAVEN_JCOVERAGE_1_0_4/tag +/version +version + id1.0.5/id + name1.0.5/name + tagMAVEN_JCOVERAGE_1_0_5/tag /version /versions developers 1.17 +1 -1 maven-plugins/jcoverage/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/jcoverage/xdocs/changes.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- changes.xml 28 May 2004 10:27:27 - 1.16 +++ changes.xml 28 Jun 2004 11:37:59 - 1.17 @@ -24,7 +24,7 @@ author email=[EMAIL PROTECTED]Emmanuel Venisse/author /properties body -release version=1.0.5-SNAPSHOT date=in CVS +release version=1.0.5 date=2004-06-28 action dev=evenisse type=fix issue=MPJCOVERAGE-8Fixed report generation fails when no java source present./action action dev=brett type=fix issue=MPJCOVERAGE-1Handle multiple source directories correctly/action action dev=brett type=fixCopy all of maven.build.dest, excluding the class files, into the instrumentation directory, as some people hook into the resources copying themselves without adding them to the POM/action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven Jcoverage Plugin 1.0.5 Released
The maven team is pleased to announce the Maven JCoverage plugin 1.0.5 release! http://maven.apache.org/reference/plugins/jcoverage/ This plugin provides coverage analysis of your source-code based on the open-source jcoverage tool. Changes in this version include: Fixed bugs: o Fixed report generation fails when no java source present. Issue: MPJCOVERAGE-8. o Handle multiple source directories correctly Issue: MPJCOVERAGE-1. o Copy all of maven.build.dest, excluding the class files, into the instrumentation directory, as some people hook into the resources copying themselves without adding them to the POM To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-jcoverage-plugin -Dversion=1.0.5 For a manual installation, you can download the plugin here: http://www.ibiblio.org/maven/maven/plugins/maven-jcoverage-plugin-1.0.5.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/multiproject/xdocs changes.xml
brett 2004/06/28 04:43:36 Modified:multiproject project.xml multiproject/xdocs changes.xml Log: [maven-scm-plugin] prepare release 1.3.1 Revision ChangesPath 1.30 +6 -1 maven-plugins/multiproject/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/multiproject/project.xml,v retrieving revision 1.29 retrieving revision 1.30 diff -u -r1.29 -r1.30 --- project.xml 25 Jun 2004 15:24:30 - 1.29 +++ project.xml 28 Jun 2004 11:43:36 - 1.30 @@ -22,7 +22,7 @@ extend../plugin-parent/project.xml/extend idmaven-multiproject-plugin/id nameMaven Multi-Project Plug-in/name - currentVersion1.4-SNAPSHOT/currentVersion + currentVersion1.3.1/currentVersion descriptionA plugin to handle the building of multiple projects within maven. Requires Maven 1.0 RC3/description shortDescriptionMulti-Project Plugin for Maven/shortDescription urlhttp://maven.apache.org/reference/plugins/multiproject//url @@ -53,6 +53,11 @@ id1.3/id name1.3/name tagMAVEN_MULTIPROJECT_1_3/tag +/version +version + id1.3.1/id + name1.3.1/name + tagMAVEN_MULTIPROJECT_1_3_1/tag /version /versions developers 1.25 +1 -1 maven-plugins/multiproject/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/multiproject/xdocs/changes.xml,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- changes.xml 13 Jun 2004 05:26:16 - 1.24 +++ changes.xml 28 Jun 2004 11:43:36 - 1.25 @@ -25,7 +25,7 @@ author email=[EMAIL PROTECTED]Vincent Massol/author /properties body -release version=1.4-SNAPSHOT date=in CVS +release version=1.3.1 date=2004-06-28 action dev=brett type=fixBuild and run plugin against the installed version of Maven/action action dev=brett type=fix issue=MPMULTIPROJECT-31Make sure source directory exists as some circumstances cause it not to/action /release - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPPMD-11) PMD report plugin fails if there is no src/java directory
The following comment has been added to this issue: Author: Michael Mattox Created: Mon, 28 Jun 2004 8:00 AM Body: Did you try it with multiproject? The problem is the PMD report is run on my master project.xml (despite the fact that it's excluded in the project.properties) and it fails because my master project.xml doesn't have a src/java dir. Our solution was to create an empty src/java directory in our master project.xml directory and it works. - View this comment: http://jira.codehaus.org/browse/MPPMD-11?page=comments#action_21109 - View the issue: http://jira.codehaus.org/browse/MPPMD-11 Here is an overview of the issue: - Key: MPPMD-11 Summary: PMD report plugin fails if there is no src/java directory Type: Bug Status: Closed Priority: Major Resolution: CANNOT REPRODUCE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-pmd-plugin Assignee: Brett Porter Reporter: Michael Mattox Created: Thu, 17 Jun 2004 8:33 AM Updated: Mon, 28 Jun 2004 8:00 AM Environment: Maven 1.0rc3, win2k, jdk1.4.2 Description: The PMD report plugin fails if there is no src/java directory. This is a problem when using multiproject, because not all projects contain java src code. Specifically for me, my master project is just a base project which all my projects extend. Having PMD in the reports causes the plugin to run the report on my base project which contains no source. I think if there is no src/java it should not break a multiproject build. - 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 changes.xml
brett 2004/06/28 05:22:07
Modified:.Tag: MAVEN-1_0-BRANCH project.xml
xdocsTag: MAVEN-1_0-BRANCH changes.xml
Log:
[maven-scm-plugin] prepare release 1.0-rc4
Revision ChangesPath
No revision
No revision
1.317.4.28 +8 -6 maven/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven/project.xml,v
retrieving revision 1.317.4.27
retrieving revision 1.317.4.28
diff -u -r1.317.4.27 -r1.317.4.28
--- project.xml 27 Jun 2004 07:57:48 - 1.317.4.27
+++ project.xml 28 Jun 2004 12:22:06 - 1.317.4.28
@@ -22,7 +22,7 @@
pomVersion3/pomVersion
idmaven/id
nameMaven/name
- currentVersion1.0-final-SNAPSHOT/currentVersion
+ currentVersion1.0-rc4/currentVersion
organization
nameApache Software Foundation/name
urlhttp://www.apache.org//url
@@ -34,11 +34,7 @@
!-- Gump integration --
gumpRepositoryIdmaven/gumpRepositoryId
- description
-Maven is a project management and project comprehension tool. Maven is based on
the concept of a project object model: builds, documentation creation, site
publication, and distribution publication are all controlled from the project object
model. Maven also provides tools to create source metrics, change logs based directly
on source repository, and source cross-references.
-You can build a Maven installation from this source tree by running
- ant -f build-bootstrap.xml
- /description
+ descriptionMaven is a project management and project comprehension tool. Maven
is based on the concept of a project object model: builds, documentation creation,
site publication, and distribution publication are all controlled from the project
object model. Maven also provides tools to create source metrics, change logs based
directly on source repository, and source cross-references. You can build a Maven
installation from this source tree by running ant -f build-bootstrap.xml/description
shortDescriptionJava Project Management Tools/shortDescription
urlhttp://maven.apache.org//url
issueTrackingUrlhttp://jira.codehaus.org/BrowseProject.jspa?id=10030/issueTrackingUrl
@@ -117,6 +113,11 @@
name1.0-rc3/name
tagMAVEN_1_0_RC3/tag
/version
+version
+ id1.0-rc4/id
+ name1.0-rc4/name
+ tagMAVEN_1_0_RC4/tag
+/version
/versions
branches/
mailingLists
@@ -742,6 +743,7 @@
include**/*Test.java/include
/includes
!-- TODO - fix or remove --
+
excludes
exclude**/JAXPTest.java/exclude
/excludes
No revision
No revision
1.14.4.26 +11 -24maven/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven/xdocs/changes.xml,v
retrieving revision 1.14.4.25
retrieving revision 1.14.4.26
diff -u -r1.14.4.25 -r1.14.4.26
--- changes.xml 28 Jun 2004 09:39:10 - 1.14.4.25
+++ changes.xml 28 Jun 2004 12:22:07 - 1.14.4.26
@@ -24,32 +24,19 @@
author email=[EMAIL PROTECTED]Vincent Massol/author
/properties
body
-release version=1.0-final-SNAPSHOT date=in CVS
- action dev=brett type=update
-Set maven.plugin.user.dir to ${maven.home.local}/plugins by default, move
maven.plugin.unpacked.dir to
-${maven.home.local}/cache.
- /action
- action dev=brett type=update
-Read local plugin jars from maven.plugin.user.dir instead of
maven.plugin.unpacked.dir.
- /action
- action dev=brett type=update
-Use commons-httpclient for http downloads from the repository.
- /action
- action dev=brett type=add issue=MAVEN-1332 due-to=george wang
-Support NTLM authentication on a remote repository.
- /action
- action dev=evenisse type=fix issue=MAVEN-1320 due-to=Miguel Griffa
-Sort all installed plugins.
- /action
- action dev=brett type=fix issue=MAVEN-1273 due-to=Andreas Peschka
-Fix HTTP BASIC authentication for remote repos.
- /action
- action dev=dion type=fix issue=MAVEN-1298
-Repository element was broken for non-cvs connections
- /action
+release version=1.0-rc4 date=2004-06-28
+ action dev=brett type=updateSet maven.plugin.user.dir to
${maven.home.local}/plugins by default, move maven.plugin.unpacked.dir to
${maven.home.local}/cache./action
+ action dev=brett type=updateRead local plugin jars from
maven.plugin.user.dir instead of maven.plugin.unpacked.dir./action
+ action dev=brett type=updateUse commons-httpclient for http downloads
from the repository./action
+ action dev=brett type=add issue=MAVEN-1332
Re: RE : [Maven 1.0 branch] Problem with the bootstrap
I didn't found when you committed this change. dIon beat me to it - I only just got home. Why need we to produce a RC4 ? Because the artifact and httputils code changed significantly - there's a risk of problems. There are also still bugs in javadoc, and multiproject. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven/xdocs changes.xml
Brett,
you forget to change org.apache.maven.MavenSession.APP_VERSION
Emmanuel
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, June 28, 2004 2:22 PM
Subject: cvs commit: maven/xdocs changes.xml
brett 2004/06/28 05:22:07
Modified:.Tag: MAVEN-1_0-BRANCH project.xml
xdocsTag: MAVEN-1_0-BRANCH changes.xml
Log:
[maven-scm-plugin] prepare release 1.0-rc4
Revision ChangesPath
No revision
No revision
1.317.4.28 +8 -6 maven/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven/project.xml,v
retrieving revision 1.317.4.27
retrieving revision 1.317.4.28
diff -u -r1.317.4.27 -r1.317.4.28
--- project.xml 27 Jun 2004 07:57:48 - 1.317.4.27
+++ project.xml 28 Jun 2004 12:22:06 - 1.317.4.28
@@ -22,7 +22,7 @@
pomVersion3/pomVersion
idmaven/id
nameMaven/name
- currentVersion1.0-final-SNAPSHOT/currentVersion
+ currentVersion1.0-rc4/currentVersion
organization
nameApache Software Foundation/name
urlhttp://www.apache.org//url
@@ -34,11 +34,7 @@
!-- Gump integration --
gumpRepositoryIdmaven/gumpRepositoryId
- description
-Maven is a project management and project comprehension tool. Maven
is based on the concept of a project object model: builds, documentation
creation, site publication, and distribution publication are all controlled
from the project object model. Maven also provides tools to create source
metrics, change logs based directly on source repository, and source
cross-references.
-You can build a Maven installation from this source tree by running
- ant -f build-bootstrap.xml
- /description
+ descriptionMaven is a project management and project comprehension
tool. Maven is based on the concept of a project object model: builds,
documentation creation, site publication, and distribution publication are
all controlled from the project object model. Maven also provides tools to
create source metrics, change logs based directly on source repository, and
source cross-references. You can build a Maven installation from this source
tree by running ant -f build-bootstrap.xml/description
shortDescriptionJava Project Management Tools/shortDescription
urlhttp://maven.apache.org//url
issueTrackingUrlhttp://jira.codehaus.org/BrowseProject.jspa?id=10030/issu
eTrackingUrl
@@ -117,6 +113,11 @@
name1.0-rc3/name
tagMAVEN_1_0_RC3/tag
/version
+version
+ id1.0-rc4/id
+ name1.0-rc4/name
+ tagMAVEN_1_0_RC4/tag
+/version
/versions
branches/
mailingLists
@@ -742,6 +743,7 @@
include**/*Test.java/include
/includes
!-- TODO - fix or remove --
+
excludes
exclude**/JAXPTest.java/exclude
/excludes
No revision
No revision
1.14.4.26 +11 -24maven/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven/xdocs/changes.xml,v
retrieving revision 1.14.4.25
retrieving revision 1.14.4.26
diff -u -r1.14.4.25 -r1.14.4.26
--- changes.xml 28 Jun 2004 09:39:10 - 1.14.4.25
+++ changes.xml 28 Jun 2004 12:22:07 - 1.14.4.26
@@ -24,32 +24,19 @@
author email=[EMAIL PROTECTED]Vincent Massol/author
/properties
body
-release version=1.0-final-SNAPSHOT date=in CVS
- action dev=brett type=update
-Set maven.plugin.user.dir to ${maven.home.local}/plugins by
default, move maven.plugin.unpacked.dir to
-${maven.home.local}/cache.
- /action
- action dev=brett type=update
-Read local plugin jars from maven.plugin.user.dir instead of
maven.plugin.unpacked.dir.
- /action
- action dev=brett type=update
-Use commons-httpclient for http downloads from the repository.
- /action
- action dev=brett type=add issue=MAVEN-1332 due-to=george
wang
-Support NTLM authentication on a remote repository.
- /action
- action dev=evenisse type=fix issue=MAVEN-1320
due-to=Miguel Griffa
-Sort all installed plugins.
- /action
- action dev=brett type=fix issue=MAVEN-1273 due-to=Andreas
Peschka
-Fix HTTP BASIC authentication for remote repos.
- /action
- action dev=dion type=fix issue=MAVEN-1298
-Repository element was broken for non-cvs connections
- /action
+release version=1.0-rc4 date=2004-06-28
+ action dev=brett type=updateSet maven.plugin.user.dir to
${maven.home.local}/plugins by default, move maven.plugin.unpacked.dir to
${maven.home.local}/cache./action
+ action dev=brett
[jira] Commented: (MPPMD-11) PMD report plugin fails if there is no src/java directory
The following comment has been added to this issue: Author: Brett Porter Created: Mon, 28 Jun 2004 8:32 AM Body: no, but I tried it on a project that had no src/java and one that did, but had a different pom.build.sourceDirectory that didn't exist. If you are experiencing aproblem in multiproject, it is probably a flow on of MPMULTIPROJECT-32. - View this comment: http://jira.codehaus.org/browse/MPPMD-11?page=comments#action_21110 - View the issue: http://jira.codehaus.org/browse/MPPMD-11 Here is an overview of the issue: - Key: MPPMD-11 Summary: PMD report plugin fails if there is no src/java directory Type: Bug Status: Closed Priority: Major Resolution: CANNOT REPRODUCE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-pmd-plugin Assignee: Brett Porter Reporter: Michael Mattox Created: Thu, 17 Jun 2004 8:33 AM Updated: Mon, 28 Jun 2004 8:32 AM Environment: Maven 1.0rc3, win2k, jdk1.4.2 Description: The PMD report plugin fails if there is no src/java directory. This is a problem when using multiproject, because not all projects contain java src code. Specifically for me, my master project is just a base project which all my projects extend. Having PMD in the reports causes the plugin to run the report on my base project which contains no source. I think if there is no src/java it should not break a multiproject build. - 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 : RE : [Maven 1.0 branch] Problem with the bootstrap
I didn't found when you committed this change. dIon beat me to it - I only just got home. Sorry, I talked about the first time when you committed the bug. ;-) I try to follow the CVS mails ;-) Why need we to produce a RC4 ? Because the artifact and httputils code changed significantly - there's a risk of problems. There are also still bugs in javadoc, and multiproject. Ok. I'll try to fix the javadoc bugs in the next days. All these new bugs comes from the fact that the javadoc tool doesn't work similarly when you give it a set of files or a directory. I'll try to re-use the default behaviour with a directory when sourceModifications aren't setted. Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven/xdocs changes.xml
Nope, just accidentally committed that one earlier :)
Thanks for the eyes though!
- Brett
Quoting Emmanuel Venisse [EMAIL PROTECTED]:
Brett,
you forget to change org.apache.maven.MavenSession.APP_VERSION
Emmanuel
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, June 28, 2004 2:22 PM
Subject: cvs commit: maven/xdocs changes.xml
brett 2004/06/28 05:22:07
Modified:.Tag: MAVEN-1_0-BRANCH project.xml
xdocsTag: MAVEN-1_0-BRANCH changes.xml
Log:
[maven-scm-plugin] prepare release 1.0-rc4
Revision ChangesPath
No revision
No revision
1.317.4.28 +8 -6 maven/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven/project.xml,v
retrieving revision 1.317.4.27
retrieving revision 1.317.4.28
diff -u -r1.317.4.27 -r1.317.4.28
--- project.xml 27 Jun 2004 07:57:48 - 1.317.4.27
+++ project.xml 28 Jun 2004 12:22:06 - 1.317.4.28
@@ -22,7 +22,7 @@
pomVersion3/pomVersion
idmaven/id
nameMaven/name
- currentVersion1.0-final-SNAPSHOT/currentVersion
+ currentVersion1.0-rc4/currentVersion
organization
nameApache Software Foundation/name
urlhttp://www.apache.org//url
@@ -34,11 +34,7 @@
!-- Gump integration --
gumpRepositoryIdmaven/gumpRepositoryId
- description
-Maven is a project management and project comprehension tool. Maven
is based on the concept of a project object model: builds, documentation
creation, site publication, and distribution publication are all controlled
from the project object model. Maven also provides tools to create source
metrics, change logs based directly on source repository, and source
cross-references.
-You can build a Maven installation from this source tree by running
- ant -f build-bootstrap.xml
- /description
+ descriptionMaven is a project management and project comprehension
tool. Maven is based on the concept of a project object model: builds,
documentation creation, site publication, and distribution publication are
all controlled from the project object model. Maven also provides tools to
create source metrics, change logs based directly on source repository, and
source cross-references. You can build a Maven installation from this source
tree by running ant -f build-bootstrap.xml/description
shortDescriptionJava Project Management Tools/shortDescription
urlhttp://maven.apache.org//url
issueTrackingUrlhttp://jira.codehaus.org/BrowseProject.jspa?id=10030/issu
eTrackingUrl
@@ -117,6 +113,11 @@
name1.0-rc3/name
tagMAVEN_1_0_RC3/tag
/version
+version
+ id1.0-rc4/id
+ name1.0-rc4/name
+ tagMAVEN_1_0_RC4/tag
+/version
/versions
branches/
mailingLists
@@ -742,6 +743,7 @@
include**/*Test.java/include
/includes
!-- TODO - fix or remove --
+
excludes
exclude**/JAXPTest.java/exclude
/excludes
No revision
No revision
1.14.4.26 +11 -24maven/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven/xdocs/changes.xml,v
retrieving revision 1.14.4.25
retrieving revision 1.14.4.26
diff -u -r1.14.4.25 -r1.14.4.26
--- changes.xml 28 Jun 2004 09:39:10 - 1.14.4.25
+++ changes.xml 28 Jun 2004 12:22:07 - 1.14.4.26
@@ -24,32 +24,19 @@
author email=[EMAIL PROTECTED]Vincent Massol/author
/properties
body
-release version=1.0-final-SNAPSHOT date=in CVS
- action dev=brett type=update
-Set maven.plugin.user.dir to ${maven.home.local}/plugins by
default, move maven.plugin.unpacked.dir to
-${maven.home.local}/cache.
- /action
- action dev=brett type=update
-Read local plugin jars from maven.plugin.user.dir instead of
maven.plugin.unpacked.dir.
- /action
- action dev=brett type=update
-Use commons-httpclient for http downloads from the repository.
- /action
- action dev=brett type=add issue=MAVEN-1332 due-to=george
wang
-Support NTLM authentication on a remote repository.
- /action
- action dev=evenisse type=fix issue=MAVEN-1320
due-to=Miguel Griffa
-Sort all installed plugins.
- /action
- action dev=brett type=fix issue=MAVEN-1273 due-to=Andreas
Peschka
-Fix HTTP BASIC authentication for remote repos.
- /action
- action dev=dion type=fix issue=MAVEN-1298
-Repository element was broken for non-cvs connections
cvs commit: maven/xdocs/start release-notes-rc4.xml download.xml
brett 2004/06/28 06:33:07 Modified:xdocsTag: MAVEN-1_0-BRANCH status.xml xdocs/start Tag: MAVEN-1_0-BRANCH download.xml Added: xdocs/start Tag: MAVEN-1_0-BRANCH release-notes-rc4.xml Removed: announcements Tag: MAVEN-1_0-BRANCH 1.0-rc2.ann Log: RC4 documentation Revision ChangesPath No revision No revision 1.16.4.5 +8 -1 maven/xdocs/status.xml Index: status.xml === RCS file: /home/cvs/maven/xdocs/status.xml,v retrieving revision 1.16.4.4 retrieving revision 1.16.4.5 diff -u -r1.16.4.4 -r1.16.4.5 --- status.xml23 Jun 2004 12:56:19 - 1.16.4.4 +++ status.xml28 Jun 2004 13:33:07 - 1.16.4.5 @@ -37,7 +37,14 @@ subsection name=Current Status p We are currently working on the documentation and waiting for feedback on - Maven 1.0 RC3, before releasing Maven 1.0 final. + Maven 1.0 RC4, before releasing Maven 1.0 final. +/p + /subsection + + subsection name=29 June 2004 - Maven 1.0 RC4 released! +p + See the a href=start/release-notes-rc4.htmlRelease Notes/a for more + information. /p /subsection No revision No revision 1.20.2.4 +6 -6 maven/xdocs/start/download.xml Index: download.xml === RCS file: /home/cvs/maven/xdocs/start/download.xml,v retrieving revision 1.20.2.3 retrieving revision 1.20.2.4 diff -u -r1.20.2.3 -r1.20.2.4 --- download.xml 20 May 2004 15:20:37 - 1.20.2.3 +++ download.xml 28 Jun 2004 13:33:07 - 1.20.2.4 @@ -34,15 +34,15 @@ /p p -The current release is 1.0-rc3. Below are the links to the latest release in various formats +The current release is 1.0-rc4. Below are the links to the latest release in various formats /p ul -lia href=release-notes-rc3.htmlRelease Notes/a/li -lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc3.exe;Windows .exe/a/li -lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc3.tar.bz2;.tar.bz2 file/a/li -lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc3.tar.gz;.tar.gz file/a/li -lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc3.zip;.zip file/a/li +lia href=release-notes-rc4.htmlRelease Notes/a/li +lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc4.exe;Windows .exe/a/li +lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc4.tar.bz2;.tar.bz2 file/a/li +lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc4.tar.gz;.tar.gz file/a/li +lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc4.zip;.zip file/a/li /ul /section No revision Index: download.xml === RCS file: /home/cvs/maven/xdocs/start/download.xml,v retrieving revision 1.20.2.3 retrieving revision 1.20.2.4 diff -u -r1.20.2.3 -r1.20.2.4 --- download.xml 20 May 2004 15:20:37 - 1.20.2.3 +++ download.xml 28 Jun 2004 13:33:07 - 1.20.2.4 @@ -34,15 +34,15 @@ /p p -The current release is 1.0-rc3. Below are the links to the latest release in various formats +The current release is 1.0-rc4. Below are the links to the latest release in various formats /p ul -lia href=release-notes-rc3.htmlRelease Notes/a/li -lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc3.exe;Windows .exe/a/li -lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc3.tar.bz2;.tar.bz2 file/a/li -lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc3.tar.gz;.tar.gz file/a/li -lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc3.zip;.zip file/a/li +lia href=release-notes-rc4.htmlRelease Notes/a/li +lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc4.exe;Windows .exe/a/li +lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc4.tar.bz2;.tar.bz2 file/a/li +lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc4.tar.gz;.tar.gz file/a/li +lia href=http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc4.zip;.zip file/a/li /ul /section No
Maven 1.0-rc4 Released
The maven team is pleased to announce the Maven 1.0-rc4 release!
http://maven.apache.org/start/download.html
Maven is a project management and project comprehension tool. Maven is based
on the concept of a project object model: builds, documentation creation, site
publication, and distribution publication are all controlled from the project
object model. Maven also provides tools to create source metrics, change logs
based directly on source repository, and source cross-references.
Maven 1.0 RC4 is the final release candidate for Maven 1.0 (and this time we
mean it!)
Changes in this version include:
New Features:
o Support NTLM authentication on a remote repository. Issue: MAVEN-1332.
Thanks to george wang.
Fixed bugs:
o Sort all installed plugins. Issue: MAVEN-1320. Thanks to Miguel Griffa.
o Fix HTTP BASIC authentication for remote repos. Issue: MAVEN-1273. Thanks
to Andreas Peschka.
o Repository element was broken for non-cvs connections Issue: MAVEN-1298.
Changes:
o Set maven.plugin.user.dir to ${maven.home.local}/plugins by default, move
maven.plugin.unpacked.dir to ${maven.home.local}/cache.
o Read local plugin jars from maven.plugin.user.dir instead of
maven.plugin.unpacked.dir.
o Use commons-httpclient for http downloads from the repository.
Plugin changes:
o The deploy plugin has been merged into the artifact plugin. The artifact plugin
is used for all artifact deployments now, and supports the old-style deployment
transparently.
o Plenty of bugfix releases of other plugins - refer to the individial plugin
websites or release announcements.
o Addition of the new RAR plugin.
We hope you enjoy using Maven! If you have any questions, please consult:
o the FAQ: http://maven.apache.org/faq.html
o the Wiki: http://wiki.codehaus.org/maven
o the maven-user mailing list: http://maven.apache.org/mail-lists.html
For news and information, see:
o Maven Blogs: http://www.mavenblogs.com
- The Apache Maven Team
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/xdocs/start release-notes-rc2.xml release-notes-rc3.xml release-notes-rc4.xml anakia.xml bootstrap.xml download.xml install.xml use.xml release-notes.xml
brett 2004/06/28 08:09:19 Modified:.KEYS build-bootstrap.xml maven.xml project.xml src/bin maven maven.bat src/bootstrap/org/apache/maven BootstrapTask.java src/conf defaults.properties src/java/org/apache/maven MavenConstants.java MavenUtils.java src/java/org/apache/maven/ant MavenTask.java src/java/org/apache/maven/cli App.java src/java/org/apache/maven/jelly JellyUtils.java MavenJellyContext.java src/java/org/apache/maven/jelly/tags/jeez JeezTagLibrary.java src/java/org/apache/maven/jelly/tags/werkz MavenAttainGoalTag.java MavenGoalTag.java src/java/org/apache/maven/plugin GoalToJellyScriptHousingMapper.java JellyScriptHousing.java PluginCacheManager.java PluginManager.java PluginScriptParser.java src/java/org/apache/maven/project Organization.java Project.java Repository.java src/java/org/apache/maven/repository AbstractArtifact.java src/java/org/apache/maven/util HttpUtils.java src/java/org/apache/maven/verifier DependencyVerifier.java src/test/java/org/apache/maven JAXPTest.java MavenUtilsTest.java src/test/java/org/apache/maven/plugin PluginCacheManagerTest.java PluginManagerTest.java src/test/java/org/apache/maven/project BasedirTest.java LegacyIdTest.java OrganizationTest.java ProjectInheritanceTest.java RepositoryTest.java src/test/java/org/apache/maven/util HttpUtilsTest.java xdocschanges.xml faq.fml musings.xml navigation-pdf.xml navigation.xml repository-upload.xml status.xml xdocs/ant-guide terminology.xml xdocs/misc tasks.xml xdocs/reference user-guide.xml xdocs/reference/developers developer-guide.xml releasing-plugins.xml xdocs/start anakia.xml bootstrap.xml download.xml install.xml use.xml Added: .README.txt src/java/org/apache/maven/repository ArtifactTypeHandler.java DefaultArtifactTypeHandler.java xdocs/reference/developers sharing-plugins.xml xdocs/start release-notes-rc2.xml release-notes-rc3.xml release-notes-rc4.xml Removed: xdocs/start release-notes.xml Log: merge up to MAVEN_1_0_RC4 Revision ChangesPath 1.2 +31 -0 maven/KEYS http://cvs.apache.org/viewcvs/maven/KEYS.diff?r1=1.1r2=1.2 1.216 +12 -2 maven/build-bootstrap.xml http://cvs.apache.org/viewcvs/maven/build-bootstrap.xml.diff?r1=1.215r2=1.216 1.104 +15 -5 maven/maven.xml http://cvs.apache.org/viewcvs/maven/maven.xml.diff?r1=1.103r2=1.104 1.333 +12 -6 maven/project.xml http://cvs.apache.org/viewcvs/maven/project.xml.diff?r1=1.332r2=1.333 1.2 +2 -0 maven/README.txt http://cvs.apache.org/viewcvs/maven/README.txt.diff?r1=1.1r2=1.2 1.35 +6 -3 maven/src/bin/maven http://cvs.apache.org/viewcvs/maven/src/bin/maven.diff?r1=1.34r2=1.35 1.42 +4 -4 maven/src/bin/maven.bat http://cvs.apache.org/viewcvs/maven/src/bin/maven.bat.diff?r1=1.41r2=1.42 1.23 +31 -1 maven/src/bootstrap/org/apache/maven/BootstrapTask.java http://cvs.apache.org/viewcvs/maven/src/bootstrap/org/apache/maven/BootstrapTask.java.diff?r1=1.22r2=1.23 1.12 +2 -1 maven/src/conf/defaults.properties http://cvs.apache.org/viewcvs/maven/src/conf/defaults.properties.diff?r1=1.11r2=1.12 1.34 +8 -1 maven/src/java/org/apache/maven/MavenConstants.java http://cvs.apache.org/viewcvs/maven/src/java/org/apache/maven/MavenConstants.java.diff?r1=1.33r2=1.34 1.111 +2 -1 maven/src/java/org/apache/maven/MavenUtils.java http://cvs.apache.org/viewcvs/maven/src/java/org/apache/maven/MavenUtils.java.diff?r1=1.110r2=1.111 1.15 +1 -0 maven/src/java/org/apache/maven/ant/MavenTask.java http://cvs.apache.org/viewcvs/maven/src/java/org/apache/maven/ant/MavenTask.java.diff?r1=1.14r2=1.15 1.41 +2 -1 maven/src/java/org/apache/maven/cli/App.java http://cvs.apache.org/viewcvs/maven/src/java/org/apache/maven/cli/App.java.diff?r1=1.40r2=1.41 1.21 +3 -3 maven/src/java/org/apache/maven/jelly/JellyUtils.java http://cvs.apache.org/viewcvs/maven/src/java/org/apache/maven/jelly/JellyUtils.java.diff?r1=1.20r2=1.21
cvs commit: maven project.xml
brett 2004/06/28 08:09:45 Modified:src/java/org/apache/maven Tag: MAVEN-1_0-BRANCH MavenSession.java .Tag: MAVEN-1_0-BRANCH project.xml Log: bump version for development Revision ChangesPath No revision No revision 1.18.4.14 +2 -2 maven/src/java/org/apache/maven/MavenSession.java Index: MavenSession.java === RCS file: /home/cvs/maven/src/java/org/apache/maven/MavenSession.java,v retrieving revision 1.18.4.13 retrieving revision 1.18.4.14 diff -u -r1.18.4.13 -r1.18.4.14 --- MavenSession.java 28 Jun 2004 09:39:09 - 1.18.4.13 +++ MavenSession.java 28 Jun 2004 15:09:45 - 1.18.4.14 @@ -62,7 +62,7 @@ public static final String DRIVER_SCRIPT_NAME = driver.jelly; /** The current MavenSession version id */ -public static final String APP_VERSION = 1.0-rc4; +public static final String APP_VERSION = 1.0-final-SNAPSHOT; // // C L A S S M E M B E R S No revision No revision 1.317.4.29 +1 -1 maven/project.xml Index: project.xml === RCS file: /home/cvs/maven/project.xml,v retrieving revision 1.317.4.28 retrieving revision 1.317.4.29 diff -u -r1.317.4.28 -r1.317.4.29 --- project.xml 28 Jun 2004 12:22:06 - 1.317.4.28 +++ project.xml 28 Jun 2004 15:09:45 - 1.317.4.29 @@ -22,7 +22,7 @@ pomVersion3/pomVersion idmaven/id nameMaven/name - currentVersion1.0-rc4/currentVersion + currentVersion1.0-final-SNAPSHOT/currentVersion organization nameApache Software Foundation/name urlhttp://www.apache.org//url - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPPLUGIN-16) Plugin plugin copies to ${maven.home}/plugins instead of ${maven.plugin.dir}
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MPPLUGIN-16
Here is an overview of the issue:
-
Key: MPPLUGIN-16
Summary: Plugin plugin copies to ${maven.home}/plugins instead of
${maven.plugin.dir}
Type: Bug
Status: Closed
Priority: Minor
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-plugin-plugin
Assignee: Brett Porter
Reporter: Scott Moyer
Created: Mon, 21 Jun 2004 11:15 AM
Updated: Mon, 28 Jun 2004 11:52 AM
Description:
We're using ${maven.plugin.dir} to specify an alternate location for the internal
plugin directory so we can lock down the maven home directory.
Goal plugin:install has ${maven.home}/plugins hardcoded as the target for the internal
plugin directory.
Can the target be changed to ${maven.plugin.dir} so plugins will be installed into
whichever plugin directory you are currently working from?
49c49
todir=${maven.home}/plugins/
---
todir=${maven.plugin.dir}/
-
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: (MPJDEPEND-1) JDepend cannot find target\classes on Linux
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPJDEPEND-1 Here is an overview of the issue: - Key: MPJDEPEND-1 Summary: JDepend cannot find target\classes on Linux Type: Bug Status: Unassigned Priority: Critical Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jdepend-plugin Components: default Assignee: Reporter: Lars Trieloff Created: Mon, 28 Jun 2004 2:48 PM Updated: Mon, 28 Jun 2004 2:48 PM Environment: Gentoo Linux, Maven RC4, Java 1.5b2 Description: I run maven site with the maven-jdepend-plugin in my report list. Maven fails with following output: __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc4 build:start: site: xdoc:register-reports: maven-changes-plugin:register: maven-checkstyle-plugin:register: faq:init: maven-faq-plugin:register: maven-jcoverage-plugin:register: maven-jdepend-plugin:register: maven-jxr-plugin:register: maven-junit-report-plugin:register: maven-license-plugin:register: maven-pmd-plugin:register: maven-simian-plugin:register: maven-tasklist-plugin:register: site:run-reports: [echo] Generating the Checkstyle... checkstyle:init: checkstyle:report: checkstyle:run: [echo] Using file:/home/lars/.maven/cache/maven-checkstyle-plugin-2.4.1/plugin-resources/sun_checks.xml for checkstyle ... [echo] Generating the JCoverage... maven-jcoverage-plugin:report: java:prepare-filesystem: java:compile: [echo] Compiling to target\classes instrumenting the class-files... jcoverage:on: java:jar-resources: test:prepare-filesystem: test:test-resources: test:compile: [echo] No test source files to compile. test:test: [echo] No tests to run. jcoverage:html-report: [echo] No tests to run JCoverage on. [echo] Generating the Metrics... maven-jdepend-plugin:report: java:prepare-filesystem: java:compile: [echo] Compiling to target\classes [java] [java] Directory does not exist: target\classes [java] [java] usage: [java] [java] JDepend [-file output file] directory [directory2 [directory 3] ...] BUILD FAILED File.. /home/lars/.maven/cache/maven-jdepend-plugin-1.5/plugin.jelly Element... ant:java Line.. 57 Column 26 Java returned: 1 Total time: 9 seconds Finished at: Mon Jun 28 20:46:35 CEST 2004 The directory target/classes exists on my computer, the directory target\classes not. I think it is just a wrong slash. - 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]
test message
Test message to see if any of my mail to apache.org gets through. - David L. Paterline Principal Engineer Westinghouse Electric Company Nuclear Fuel Engineering Engineering Computing [EMAIL PROTECTED] PH: 412-374-2286 FX: 412-374-2284 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-150) EventBus 1.0
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-150 Here is an overview of the issue: - Key: MAVENUPLOAD-150 Summary: EventBus 1.0 Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Berin Loritsch Created: Mon, 28 Jun 2004 3:42 PM Updated: Mon, 28 Jun 2004 3:42 PM Description: http://dist.d-haven.org/eventbus-1.0-bundle.jar Provide a well tested Event Bus for use in any Swing based application. Licensed under the Apache Software License 2.0. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-146) Event-1.0
The following comment has been added to this issue: Author: Berin Loritsch Created: Mon, 28 Jun 2004 3:48 PM Body: I updated the project.xml for the requested URL so that I could add a group Id. - View this comment: http://jira.codehaus.org/browse/MAVENUPLOAD-146?page=comments#action_21120 - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-146 Here is an overview of the issue: - Key: MAVENUPLOAD-146 Summary: Event-1.0 Type: New Feature Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Berin Loritsch Created: Thu, 24 Jun 2004 9:52 AM Updated: Mon, 28 Jun 2004 3:48 PM Description: http://dist.d-haven.org/even-1.0-bundle.jar D-Haven Event is a library designed to make it easier to develop event based processing systems. It also includes a CommandManager to handle certain activities behind the scenes in a controlled number of background threads. The library has been fully tested, and all dependencies have been brought to a minimum. - 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: [jira] Created: (MAVENUPLOAD-150) EventBus 1.0
reply to message - David L. Paterline Principal Engineer Westinghouse Electric Company Nuclear Fuel Engineering Engineering Computing [EMAIL PROTECTED] PH: 412-374-2286 FX: 412-374-2284 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, June 28, 2004 3:43 PM To: [EMAIL PROTECTED] Subject: [jira] Created: (MAVENUPLOAD-150) EventBus 1.0 Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-150 Here is an overview of the issue: - Key: MAVENUPLOAD-150 Summary: EventBus 1.0 Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Berin Loritsch Created: Mon, 28 Jun 2004 3:42 PM Updated: Mon, 28 Jun 2004 3:42 PM Description: http://dist.d-haven.org/eventbus-1.0-bundle.jar Provide a well tested Event Bus for use in any Swing based application. Licensed under the Apache Software License 2.0. - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-147) Managed Pool 1.0
The following comment has been added to this issue: Author: Berin Loritsch Created: Mon, 28 Jun 2004 3:51 PM Body: I updated the project.xml to add a groupId to integrate things better overall. - View this comment: http://jira.codehaus.org/browse/MAVENUPLOAD-147?page=comments#action_21121 - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-147 Here is an overview of the issue: - Key: MAVENUPLOAD-147 Summary: Managed Pool 1.0 Type: New Feature Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Berin Loritsch Created: Thu, 24 Jun 2004 10:22 AM Updated: Mon, 28 Jun 2004 3:51 PM Description: D-Haven Managed Pool is a library designed to provide pools that are asynchronously managed in a background thread. The pool system is very flexible and can accomodate just about every need. It boasts the ability to add pool listeners so that you can instrument and intercept the pooled objects when they are created, destroyed, acquired, and released. - 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: (MPARTIFACT-22) New ScpExeDeployer
The following issue has been updated: Updater: Leif Nelson (mailto:[EMAIL PROTECTED]) Date: Mon, 28 Jun 2004 4:55 PM Comment: Here's the patch. Changes: Attachment changed to Artifact-ScpExeDeployer.patch - For a full history of the issue, see: http://jira.codehaus.org/browse/MPARTIFACT-22?page=history - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-22 Here is an overview of the issue: - Key: MPARTIFACT-22 Summary: New ScpExeDeployer Type: Improvement Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-artifact-plugin Assignee: Reporter: Leif Nelson Created: Mon, 28 Jun 2004 4:54 PM Updated: Mon, 28 Jun 2004 4:55 PM Description: I have implemented an ScpExeDeployer plugin (like I said I would back in November!). When I upgraded to RC4, I saw that you were serious about getting rid of the old scp/ssh type of deployment. :-) Anyways, I really need to have the ssh-agent type of support in the deployment artifacts, so I implemented this plugin. It's backwards compatible with folks that supply the old maven.ssh.executable, maven.ssh.args, maven.scp.executable, maven.scp.args. I also made it look for these params in server-specific props like you do with the new stuff.. maven.repo.x.ssh.executable, maven.repo.x.ssh.args, maven.repo.x.scp.executable, maven.repo.x.scp.args. So, if someone wanted to deploy with different args, or different commands to different servers, the plugin would support that. This work was done in regards to this email thread.. http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=8065 Thanks much for consideration. :-) --Leif - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/checkstyle/src/plugin-resources/images - New directory
vmassol 2004/06/28 14:03:55 maven-plugins/checkstyle/src/plugin-resources/images - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/checkstyle project.xml plugin.jelly
vmassol 2004/06/28 14:04:04
Modified:checkstyle/xdocs changes.xml
checkstyle/src/plugin-resources checkstyle.jsl
checkstyle project.xml plugin.jelly
Added: checkstyle/src/plugin-resources/images rss.png
checkstyle/src/plugin-resources checkstyle2rss.jsl
Log:
Added first cut of a checkstyle RSS feed. There's lot to improve but I'd like to
gather some feedback before working more on this feature. It relies on the fact that
RSS readers cache feed data previously read thus keeping an history of the feed
content over time.
Revision ChangesPath
1.1 maven-plugins/checkstyle/src/plugin-resources/images/rss.png
Binary file
1.33 +4 -1 maven-plugins/checkstyle/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/checkstyle/xdocs/changes.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- changes.xml 18 May 2004 21:50:24 - 1.32
+++ changes.xml 28 Jun 2004 21:04:04 - 1.33
@@ -25,7 +25,10 @@
author email=[EMAIL PROTECTED]Emmanuel Venisse/author
/properties
body
-release version=2.4.2-SNAPSHOT date=In CVS
+release version=2.5-SNAPSHOT date=In CVS
+ action dev=vmassol type=add
+Added generation of a Checkstyle RSS feed.
+ /action
action dev=aheritier type=fix issue=MPCHECKSTYLE-21Fix : Build failed
if target directory and License file didn't exist./action
/release
release version=2.4.1 date=2004-05-18
1.14 +2 -1 maven-plugins/checkstyle/src/plugin-resources/checkstyle.jsl
Index: checkstyle.jsl
===
RCS file: /home/cvs/maven-plugins/checkstyle/src/plugin-resources/checkstyle.jsl,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- checkstyle.jsl21 Apr 2004 00:55:43 - 1.13
+++ checkstyle.jsl28 Jun 2004 21:04:04 - 1.14
@@ -46,7 +46,8 @@
section name=Checkstyle Results
p
The following document contains the results of
-a href=http://checkstyle.sourceforge.net/;Checkstyle/a.
+a href=http://checkstyle.sourceforge.net/;Checkstyle/a
+a href=checkstyle.rssimg src=images/rss.png//a.
/p
/section
1.1 maven-plugins/checkstyle/src/plugin-resources/checkstyle2rss.jsl
Index: checkstyle2rss.jsl
===
?xml version=1.0 encoding=ISO-8859-1?
!--
*
*
* Copyright 2004 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the License);
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an AS IS BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*
*
--
jsl:stylesheet
select=$doc
xmlns:j=jelly:core
xmlns:jsl=jelly:jsl
xmlns:util=jelly:util
xmlns:x=jelly:xml
xmlns:doc=doc
xmlns=dummy trim=true
!-- This needs to be instantiated here to be available in the template matches --
j:useBean var=mavenTool class=org.apache.maven.util.MavenTool/
j:useBean var=htmlescape class=org.apache.velocity.anakia.Escape/
j:useBean var=fileutil class=org.apache.velocity.texen.util.FileUtil/
j:useBean var=pathtool class=org.apache.maven.util.DVSLPathTool/
jsl:template match=checkstyle
rss version=0.91
channel
titleCheckstyle report/title
link${pom.url}/link
descriptionCheckstyle report/description
languageen-us/language
copyrightCopyright 2004 The Apache Software Foundation/copyright
item
j:set var=fileCountx:expr select=count(file)//j:set
j:set var=infoCountx:expr select=count(file/[EMAIL
PROTECTED]'info'])//j:set
j:set var=warningCountx:expr select=count(file/[EMAIL
PROTECTED]'warning'])//j:set
j:set var=errorCountx:expr select=count(file/[EMAIL
PROTECTED]'error'])//j:set
titleFile: ${fileCount}, Errors: ${errorCount}, Warnings:
${warningCount}, Infos: ${infoCount}/title
cvs commit: maven-plugins/checkstyle/src/plugin-resources checkstyle2rss.jsl checkstyle2ref.jsl
vmassol 2004/06/28 14:04:35
Modified:checkstyle/src/plugin-resources checkstyle2rss.jsl
checkstyle2ref.jsl
Log:
Binary -- Ascii
Revision ChangesPath
1.2 +110 -110 maven-plugins/checkstyle/src/plugin-resources/checkstyle2rss.jsl
Index: checkstyle2rss.jsl
===
RCS file:
/home/cvs/maven-plugins/checkstyle/src/plugin-resources/checkstyle2rss.jsl,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- checkstyle2rss.jsl28 Jun 2004 21:04:04 - 1.1
+++ checkstyle2rss.jsl28 Jun 2004 21:04:35 - 1.2
@@ -1,110 +1,110 @@
-?xml version=1.0 encoding=ISO-8859-1?
-
-!--
- *
- *
- * Copyright 2004 The Apache Software Foundation.
- *
- * Licensed under the Apache License, Version 2.0 (the License);
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an AS IS BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- *
- *
---
-
-jsl:stylesheet
- select=$doc
- xmlns:j=jelly:core
- xmlns:jsl=jelly:jsl
- xmlns:util=jelly:util
- xmlns:x=jelly:xml
- xmlns:doc=doc
- xmlns=dummy trim=true
-
- !-- This needs to be instantiated here to be available in the template matches
--
- j:useBean var=mavenTool class=org.apache.maven.util.MavenTool/
- j:useBean var=htmlescape class=org.apache.velocity.anakia.Escape/
- j:useBean var=fileutil class=org.apache.velocity.texen.util.FileUtil/
- j:useBean var=pathtool class=org.apache.maven.util.DVSLPathTool/
-
- jsl:template match=checkstyle
-
-rss version=0.91
- channel
-titleCheckstyle report/title
-link${pom.url}/link
-descriptionCheckstyle report/description
-languageen-us/language
-copyrightCopyright 2004 The Apache Software Foundation/copyright
-item
-
- j:set var=fileCountx:expr select=count(file)//j:set
- j:set var=infoCountx:expr select=count(file/[EMAIL
PROTECTED]'info'])//j:set
- j:set var=warningCountx:expr select=count(file/[EMAIL
PROTECTED]'warning'])//j:set
- j:set var=errorCountx:expr select=count(file/[EMAIL
PROTECTED]'error'])//j:set
-
- titleFile: ${fileCount}, Errors: ${errorCount}, Warnings:
${warningCount}, Infos: ${infoCount}/title
-
- !-- If we don't go through a tmp variable Jelly inserts a space between
${pom.url}
- and '/checkstyle-report.html'. Go figure... --
- j:set var=link value=${pom.url}/checkstyle-report.html/
-
- link${link}/link
- description
-pClick a href=${pom.url}/checkstyle-report.htmlhere/a for the
full Checkstyle report./p
-
- table summary=Files border=1
-thead
- tr
-thFiles/th
-th style=width:30pxI/th
-th style=width:30pxW/th
-th style=width:30pxE/th
- /tr
-/thead
-tbody
- j:set var=fullSrcDir value=${pom.build.sourceDirectory}/
- j:set var=srcDir
value=${fileutil.file(fullSrcDir).getCanonicalPath()}/
- j:set var=srcDirLength value=${srcDir.length() + 1}/
- x:set var=files select=file sort=@name/
- !-- x:forEach is busted --
- j:forEach var=file items=${files}
-!-- Type coercion doesn't work worth a fuck in jexl. --
-j:set var=name value=${file.attribute('name').getValue()}/
-j:set var=name
value=${name.substring(mavenTool.toInteger(srcDirLength.toString()))}/
-util:replace var=name value=${name} oldChar=\\ newChar=//
-!--- +1 is for the trailing slash above --
-j:set var=infoCountx:expr select=count($file/[EMAIL
PROTECTED]'info'])//j:set
-j:set var=warningCountx:expr select=count($file/[EMAIL
PROTECTED]'warning'])//j:set
-j:set var=errorCountx:expr select=count($file/[EMAIL
PROTECTED]'error'])//j:set
-
-j:if test=${errorCount + warningCount + infoCount != 0}
- tr
-
[jira] Closed: (MPECLIPSE-6) junit dependency should be added to classpath even when tests do not exist
Message:
The following issue has been closed.
Resolver: David Eric Pugh
Date: Mon, 28 Jun 2004 5:49 PM
I am marking this as won't fix because I can't think of a good reason to include JUnit
if there are no unit test. The one example, writing a JUnit extension is so
specific.. and, it will work once you write your first unit test for the extension..
After lal, you are doing TDD ;-).. I looked at putting the logic in, but Jelly is
kinda icky and right now it is very clean and legible..
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-6
Here is an overview of the issue:
-
Key: MPECLIPSE-6
Summary: junit dependency should be added to classpath even when tests do not exist
Type: Bug
Status: Closed
Priority: Trivial
Resolution: WON'T FIX
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-eclipse-plugin
Assignee:
Reporter: Karl Kyck
Created: Wed, 22 Oct 2003 5:19 AM
Updated: Mon, 28 Jun 2004 5:49 PM
Environment: Windows XP SP1, P4 2.6GHz, 512Mb DDR 400
Description:
Created a fresh project.xml with a junit dependency so tests could be written
immediately after the .project and .classpath entries were generated, however the
junit dependency had not been added to the classpath.
As a test/fix this code
j:if test=${pom.getDependency('junit') != null}
j:set var=depVersion value=${pom.getDependency('junit').getVersion()}/
/j:if
was moved outside of the
j:if test=${unitTestSourcesPresent}
if block, and it worked fine.
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPECLIPSE-18) Patch to add support for custom project names in dependencies
The following comment has been added to this issue: Author: David Eric Pugh Created: Mon, 28 Jun 2004 5:52 PM Body: Why would you want to change the name of the dependency? Should you be using the version that you are referencing in Maven, versus a different kind? Otherwise what Maven builds against will be different list of dependencis from what Eclipse builds again, correct? - View this comment: http://jira.codehaus.org/browse/MPECLIPSE-18?page=comments#action_21124 - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-18 Here is an overview of the issue: - Key: MPECLIPSE-18 Summary: Patch to add support for custom project names in dependencies Type: Improvement Status: Unassigned Priority: Minor Original Estimate: 10 minutes Time Spent: Unknown Remaining: 10 minutes Project: maven-eclipse-plugin Versions: 1.6 Assignee: Reporter: Rob Dupuis Created: Tue, 10 Feb 2004 11:30 AM Updated: Mon, 28 Jun 2004 5:52 PM Description: I'm working on a project in which the aritfact name does not match the eclipse project name. I've created patches to support a new project.xml dependency property called eclipse.dependency.name, which allows you to specify a custom project name for a dependency. eg Before: dependency groupIdkizoom/groupId artifactIdcommon/artifactId version1/version properties eclipse.dependencytrue/eclipse.dependency /properties /dependency After: dependency groupIdkizoom/groupId artifactIdcommon/artifactId version1/version properties eclipse.dependencytrue/eclipse.dependency eclipse.dependency.nameKizoomCommon/eclipse.dependency.name /properties /dependency Not sure about the name eclipse.dependency.name, should this be eclipse.dependency.project.name or maybe eclipse.dependency.project? - 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: (MPECLIPSE-9) Eclipse plugin includes non-classpath dependencies in generated files
Message: The following issue has been closed. Resolver: David Eric Pugh Date: Mon, 28 Jun 2004 5:58 PM This issue is a duplicate of MPECLIPSE-10 and will be fixed by resolving MPECLIPSE-10 - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-9 Here is an overview of the issue: - Key: MPECLIPSE-9 Summary: Eclipse plugin includes non-classpath dependencies in generated files Type: Bug Status: Closed Priority: Minor Resolution: DUPLICATE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-eclipse-plugin Assignee: Reporter: dion gillard Created: Thu, 2 Oct 2003 7:57 PM Updated: Mon, 28 Jun 2004 5:58 PM Description: I am using the eclipse plugin for a project in which project.xml lists a dependency on a typetld/type artifact. maven eclipse then generates a dependency on MAVEN_REPO/path/file.tld Arguable this has no value, but Eclipse also does not like it, producing Unbound classpath variable messages. Manually removing these guys in Eclipse solves the problem, but of course each execute of maven eclipse reintroduces the problem. It seems that one can add a eclipse.depency property to each dependency to cause special behavior. I think a solution would be to either: - Introduce a new property eclipse.exclude, or - Make the eclipse plug-in aware of the supported artifact types and only include artifacts of type: jar, war, sar etc. but not tld - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/eclipse/src/plugin-resources/templates classpath.jelly
epugh 2004/06/28 15:07:32
Modified:eclipse/xdocs changes.xml properties.xml
eclipse/src/plugin-resources/templates classpath.jelly
Log:
MPECLIPSE-10 Fix for ignoring dependencies via
eclipse.dependencyfalse/eclipse.dependency
Revision ChangesPath
1.22 +1 -0 maven-plugins/eclipse/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/eclipse/xdocs/changes.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- changes.xml 13 Jun 2004 03:51:17 - 1.21
+++ changes.xml 28 Jun 2004 22:07:31 - 1.22
@@ -25,6 +25,7 @@
/properties
body
release version=1.8 date=In CVS
+ action dev=epugh type=add issue=MPECLIPSE-10 due-to=Thierry LackSet
eclipse.dependency=false to explicity ignore dependencies in classpath
generation/action
action dev=evenisse type=fix issue=MPECLIPSE-29 due-to=Marc-Antoine
GarrigueFix classpath generation when tests are not present/action
action dev=evenisse type=fix issue=MPECLIPSE-32classpath includes
must be relative directories/action
/release
1.10 +4 -0 maven-plugins/eclipse/xdocs/properties.xml
Index: properties.xml
===
RCS file: /home/cvs/maven-plugins/eclipse/xdocs/properties.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- properties.xml7 May 2004 09:14:37 - 1.9
+++ properties.xml28 Jun 2004 22:07:31 - 1.10
@@ -127,6 +127,10 @@
This indicates that the dependency is another project in the workspace.
Note that the name of the referenced project is the artifactId.
/p
+ p
+ The inverse also works. If you have included extra jars that shouldn't be
+ in the eclipse classpath then you can set
codeeclipse.dependency=false/code
+ /p
/section
/body
/document
1.16 +3 -0
maven-plugins/eclipse/src/plugin-resources/templates/classpath.jelly
Index: classpath.jelly
===
RCS file:
/home/cvs/maven-plugins/eclipse/src/plugin-resources/templates/classpath.jelly,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- classpath.jelly 13 Jun 2004 03:51:17 - 1.15
+++ classpath.jelly 28 Jun 2004 22:07:32 - 1.16
@@ -124,6 +124,9 @@
j:when test=${eclipseDependency == 'true'}
classpathentry kind=src path=/${lib.dependency.artifactId}/
/j:when
+ j:when test=${eclipseDependency == 'false'}
+!-- ignore specific dependencies --
+ /j:when
j:when test=${lib.dependency.groupId == 'junit'}
!-- ignoring junit dependency as we've already created it --
/j:when
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPECLIPSE-10) added eclipseDependency='false' behavior
Message: The following issue has been closed. Resolver: David Eric Pugh Date: Mon, 28 Jun 2004 6:07 PM Applied the eclipse.dependencyfalse/eclipse.dependency fix. - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-10 Here is an overview of the issue: - Key: MPECLIPSE-10 Summary: added eclipseDependency='false' behavior Type: Improvement Status: Closed Priority: Minor Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-eclipse-plugin Fix Fors: 1.8 Assignee: David Eric Pugh Reporter: Piotr Maj Created: Fri, 22 Aug 2003 6:43 AM Updated: Mon, 28 Jun 2004 6:07 PM Environment: any Description: While generating .classpath file maven-eclipse-plugin includes all artifacts defined in project.xml regardless of it's type. As a side effect it may be observed that even JSP's *.tld files are included as Eclipse variables.It leads to project compile problems. Actually such project won't compile at all. To avoid such behavior I propose a silly patch attached, which takes care of eclipseDependency property of artifacts. If it is set to 'false' the artifact will not be listed in .classpath. - 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: (MPECLIPSE-7) Source classpath entry was generated as full path.
Message:
The following issue has been closed.
Resolver: David Eric Pugh
Date: Mon, 28 Jun 2004 6:11 PM
I can't reproduce this with Maven RC3 and maven-eclipse-plugin 1.8
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-7
Here is an overview of the issue:
-
Key: MPECLIPSE-7
Summary: Source classpath entry was generated as full path.
Type: Bug
Status: Closed
Priority: Major
Resolution: CANNOT REPRODUCE
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-eclipse-plugin
Assignee:
Reporter: Makoto Shimomura
Created: Mon, 6 Oct 2003 11:39 PM
Updated: Mon, 28 Jun 2004 6:11 PM
Environment: Windows 2000, cygwin 1.5.5-1, J2SDK 1.4.2
Description:
Source classpathentry of generated .classpath was full path.
In beta-10, it was relative path correctly.
Project directory is /cygdrive/d/eclipse/workspace/myproj
classpathentry generated by 1.0-rc1:
classpathentry kind=src path=D:\eclipse\workspace\myproj\src\java
/classpathentry
classpathentry kind=src path=D:\eclipse\workspace\myproj\src\test
/classpathentry
classpathentry generated by 1.0-beta-10:
classpathentry kind=src path=src\java
/classpathentry
classpathentry kind=src path=src\test
/classpathentry
build.properties and ~/build.properties are not exists.
--- project.properties ---
maven.xdoc.date=left
maven.xdoc.version=${pom.currentVersion}
--
--- project.xml
project
:
:
build
sourceDirectorysrc/java/sourceDirectory
unitTestSourceDirectorysrc/test/unitTestSourceDirectory
unitTest
includes
include**/*Test.java/include
/includes
excludes
exclude**/NaughtyTest.java/exclude
/excludes
/unitTest
resources
resource
directorysrc/conf/directory
includes
include*.properties/include
/includes
/resource
/resources
/build
/project
--
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/javadoc/src/plugin-test/src/main/org/apache/maven2 Dummy3.java
aheritier2004/06/28 15:57:25
Modified:javadoc/src/plugin-test/src/main/org/apache/maven2
Dummy3.java
Log:
Add a test for MPJAVADOC-28
Revision ChangesPath
1.2 +4 -0
maven-plugins/javadoc/src/plugin-test/src/main/org/apache/maven2/Dummy3.java
Index: Dummy3.java
===
RCS file:
/home/cvs/maven-plugins/javadoc/src/plugin-test/src/main/org/apache/maven2/Dummy3.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Dummy3.java 19 May 2004 23:20:34 - 1.1
+++ Dummy3.java 28 Jun 2004 22:57:25 - 1.2
@@ -1,5 +1,9 @@
package org.apache.maven2;
+/**
+ * Test MPJAVADOC-28 : [EMAIL PROTECTED] org.apache.maven}
+ *
+ */
public class Dummy3
{
public String badChecky = error;
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/javadoc plugin.properties
aheritier2004/06/28 15:58:28
Modified:javadoc plugin.properties
Log:
Add the property maven.javadoc.debug
Revision ChangesPath
1.13 +14 -13maven-plugins/javadoc/plugin.properties
Index: plugin.properties
===
RCS file: /home/cvs/maven-plugins/javadoc/plugin.properties,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- plugin.properties 9 Jun 2004 22:28:03 - 1.12
+++ plugin.properties 28 Jun 2004 22:58:28 - 1.13
@@ -21,31 +21,32 @@
# ---
#maven.javadoc.additionalparam
-maven.javadoc.author = true
+maven.javadoc.author = true
#maven.javadoc.customtags
-maven.javadoc.destdir = ${maven.docs.dest}/apidocs
+maven.javadoc.debug = false
+maven.javadoc.destdir = ${maven.docs.dest}/apidocs
# optional properties for specifying a custom doclet
-#maven.javadoc.doclet=
-#maven.javadoc.docletpath=
+#maven.javadoc.doclet =
+#maven.javadoc.docletpath =
-maven.javadoc.links =
+maven.javadoc.links =
#specify an alternate locale
-#maven.javadoc.locale=en_US
+#maven.javadoc.locale = en_US
#maven.javadoc.maxmemory
#maven.javadoc.mode.online
#maven.javadoc.offlineLinks
#maven.javadoc.overview
-maven.javadoc.package = true
-maven.javadoc.private = false
-maven.javadoc.public = false
+maven.javadoc.package = true
+maven.javadoc.private = false
+maven.javadoc.public = false
#maven.javadoc.source
-maven.javadoc.stylesheet = ${plugin.resources}/stylesheet.css
+maven.javadoc.stylesheet = ${plugin.resources}/stylesheet.css
#maven.javadoc.tagletpath
#maven.javadoc.taglets
-maven.javadoc.use = true
+maven.javadoc.use = true
maven.javadoc.useexternalfile = yes
-maven.javadoc.version = true
-maven.javadoc.windowtitle = ${pom.name} ${pom.currentVersion} API
\ No newline at end of file
+maven.javadoc.version = true
+maven.javadoc.windowtitle = ${pom.name} ${pom.currentVersion} API
\ No newline at end of file
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPJAVADOC-28) @link tag not working with package names
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Mon, 28 Jun 2004 7:06 PM
Body:
I partially fixed this bug.
I re-introduce the use of a sourcepath instead of a fileset when
${pom.build.sourceModifications} aren't defined.
The bug will persist if you use sourceModifications AND link to package names at the
same time.
-
View this comment:
http://jira.codehaus.org/browse/MPJAVADOC-28?page=comments#action_21129
-
View the issue:
http://jira.codehaus.org/browse/MPJAVADOC-28
Here is an overview of the issue:
-
Key: MPJAVADOC-28
Summary: @link tag not working with package names
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-javadoc-plugin
Assignee: Arnaud HERITIER
Reporter: Maarten Coene
Created: Fri, 25 Jun 2004 7:54 AM
Updated: Mon, 28 Jun 2004 7:06 PM
Description:
I have a coulple of [EMAIL PROTECTED] package-name} tags in my javadocs, however, the
javadoc plugin can resolve them to an URL.
For instance: http://www.dom4j.org/xref/org/dom4j/DocumentType.html has links to the
org.dom4j.dtd package. But if I generate the javadoc with maven, I receive this
warning: src\java\org\dom4j\DocumentType.java:52: warning - Tag @link: reference not
found: org.dom4j.dtd.
But if I generate the javadocs with the Ant javadoc task myself, these links are
resolved correctly!!
For instance: http://www.dom4j.org/dom4j-1.4/apidocs/org/dom4j/DocumentType.html is
the javadoc generated by the build.xml of dom4j which does only call the javadoc task
provided by Ant.
Maarten
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPJAVADOC-29) broken on jdk 1.3 for multiple packages
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Mon, 28 Jun 2004 7:10 PM
Body:
I partially fixed this bug.
I re-introduce the use of a sourcepath instead of a fileset when
${pom.build.sourceModifications} aren't defined.
The bug will persist if you use sourceModifications AND jdk 1.3 at the same time.
We need to add a test to remove the use of the fileset if we don't use a jsdk 1.4.
-
View this comment:
http://jira.codehaus.org/browse/MPJAVADOC-29?page=comments#action_21130
-
View the issue:
http://jira.codehaus.org/browse/MPJAVADOC-29
Here is an overview of the issue:
-
Key: MPJAVADOC-29
Summary: broken on jdk 1.3 for multiple packages
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-javadoc-plugin
Assignee: Arnaud HERITIER
Reporter: Brett Porter
Created: Mon, 28 Jun 2004 6:13 AM
Updated: Mon, 28 Jun 2004 7:10 PM
Description:
works in 1.4, but under 1.3 the packages are all meshed into one.
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/javadoc/xdocs changes.xml properties.xml
aheritier2004/06/28 16:14:24
Modified:javadoc plugin.jelly
javadoc/xdocs changes.xml properties.xml
Log:
- Add the property maven.javadoc.debug
- MPJAVADOC-28 partially fixed : @link tag not working with package names.
- MPJAVADOC-29 partially fixed : Packages list broken on jdk 1.3 for multiple
packages.
Revision ChangesPath
1.44 +198 -71 maven-plugins/javadoc/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/javadoc/plugin.jelly,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- plugin.jelly 9 Jun 2004 21:54:38 - 1.43
+++ plugin.jelly 28 Jun 2004 23:14:24 - 1.44
@@ -28,30 +28,90 @@
xmlns:maven=jelly:maven
- goal name=maven-javadoc-plugin:register
-
-javadoc:check-needed/
-
-j:if test=${needed}
- doc:registerReport
-name=JavaDocs
-pluginName=maven-javadoc-plugin
-link=apidocs/index
-target=_blank
-description=JavaDoc API documentation.
-/
- doc:registerReport
-name=JavaDoc Report
-pluginName=
-link=javadoc
-description=Report on the generation of JavaDoc.
-/
-/j:if
- /goal
+ !-- == --
+ !-- Initialize plugin --
+ !-- == --
- goal name=maven-javadoc-plugin:deregister
-doc:deregisterReport name=JavaDocs/
-doc:deregisterReport name=JavaDoc Report/
+ goal name=javadoc:init prereqs=xdoc:init
+!-- javadoc plugin properties --
+maven:get var=maven.javadoc.additionalparam plugin=maven-javadoc-plugin
property=maven.javadoc.additionalparam/
+maven:get var=maven.javadoc.author plugin=maven-javadoc-plugin
property=maven.javadoc.author/
+maven:get var=maven.javadoc.customtags plugin=maven-javadoc-plugin
property=maven.javadoc.customtags/
+maven:get var=maven.javadoc.debugplugin=maven-javadoc-plugin
property=maven.javadoc.debug/
+maven:get var=maven.javadoc.destdir plugin=maven-javadoc-plugin
property=maven.javadoc.destdir/
+maven:get var=maven.javadoc.doclet plugin=maven-javadoc-plugin
property=maven.javadoc.doclet/
+maven:get var=maven.javadoc.docletpath plugin=maven-javadoc-plugin
property=maven.javadoc.docletpath/
+maven:get var=maven.javadoc.linksplugin=maven-javadoc-plugin
property=maven.javadoc.links/
+maven:get var=maven.javadoc.locale plugin=maven-javadoc-plugin
property=maven.javadoc.locale/
+maven:get var=maven.javadoc.maxmemoryplugin=maven-javadoc-plugin
property=maven.javadoc.maxmemory/
+maven:get var=maven.javadoc.mode.online plugin=maven-javadoc-plugin
property=maven.javadoc.mode.online/
+maven:get var=maven.javadoc.offlineLinks plugin=maven-javadoc-plugin
property=maven.javadoc.offlineLinks/
+maven:get var=maven.javadoc.overview plugin=maven-javadoc-plugin
property=maven.javadoc.overview/
+maven:get var=maven.javadoc.package plugin=maven-javadoc-plugin
property=maven.javadoc.package/
+maven:get var=maven.javadoc.private plugin=maven-javadoc-plugin
property=maven.javadoc.private/
+maven:get var=maven.javadoc.public plugin=maven-javadoc-plugin
property=maven.javadoc.public/
+maven:get var=maven.javadoc.source plugin=maven-javadoc-plugin
property=maven.javadoc.source/
+maven:get var=maven.javadoc.stylesheet plugin=maven-javadoc-plugin
property=maven.javadoc.stylesheet/
+maven:get var=maven.javadoc.tagletpath plugin=maven-javadoc-plugin
property=maven.javadoc.tagletpath/
+maven:get var=maven.javadoc.taglets plugin=maven-javadoc-plugin
property=maven.javadoc.taglets/
+maven:get var=maven.javadoc.use plugin=maven-javadoc-plugin
property=maven.javadoc.use/
+maven:get var=maven.javadoc.useexternalfile plugin=maven-javadoc-plugin
property=maven.javadoc.useexternalfile/
+maven:get var=maven.javadoc.version plugin=maven-javadoc-plugin
property=maven.javadoc.version/
+maven:get var=maven.javadoc.windowtitle plugin=maven-javadoc-plugin
property=maven.javadoc.windowtitle/
+
+!-- internal variables --
+j:set var=internal.javadoc.jar
value=${maven.build.dir}/${maven.final.name}_javadoc.jar/
+j:set var=internal.javadoc.neededvalue=null/
+j:set var=internal.javadoc.src.modifsvalue=false/
+j:set var=internal.javadoc.src.set
[jira] Created: (MAVEN-1341) build-bootstrap.xml target bootstrap-compile
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1341
Here is an overview of the issue:
-
Key: MAVEN-1341
Summary: build-bootstrap.xml target bootstrap-compile
Type: Bug
Status: Unassigned
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Versions:
1.0-rc4
Assignee:
Reporter: W. Sean Hennessy
Created: Mon, 28 Jun 2004 8:37 PM
Updated: Mon, 28 Jun 2004 8:37 PM
Environment: ant.version - Apache Ant version 1.6.1 compiled on February 12 2004
Detected Java version: 1.4
Detected OS: Windows XP
ant.file - C:\Wrk\CVSROOT\maven\build-bootstrap.xml
check-properties:
Condition true; setting online to true
Setting project property: online - true
Property ${maven.proxy.host} has not been set
Condition false; not setting proxied-online
check-env:
[echo] maven.home = C:\Tools\maven-1.0-RC4
env:
[echo] maven.home = C:\Tools\maven-1.0-RC4
[echo] maven.home.local = C:\Tools\maven_local
[echo] maven.repo.local = C:\Tools\maven_local\repository
[echo]
Description:
need
mkdir ${maven.repo.local}\repository\commons-logging\jars
mkdir ${maven.repo.local}\repository\commons-httpclient\jars
else
[get] Error getting
http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.0.3.jar to
C:\Tools\maven_local\repository\commons-logging\jars\commons-logging-1.0.3.jar
[get] Error getting
http://www.ibiblio.org/maven/commons-httpclient/jars/commons-httpclient-2.0.jar to
C:\Tools\maven_local\repository\commons-httpclient\jars\commons-httpclient-2.0.jar
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-1169) Maven isn't able to dowload an artifact of type distribution
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MAVEN-1169 Here is an overview of the issue: - Key: MAVEN-1169 Summary: Maven isn't able to dowload an artifact of type distribution Type: Bug Status: Closed Priority: Major Resolution: DUPLICATE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Fix Fors: 1.1 Versions: 1.0-rc1 1.0-rc2 Assignee: Reporter: Jason Chaffee Created: Fri, 20 Feb 2004 4:05 PM Updated: Mon, 28 Jun 2004 9:22 PM Description: Currently, the maven dist plugin creates files with extensions .zip and .tar.gz and places them in the repository as type distribution. Also, you may have the extension .bin under the type distribution. Maven sets up special cases for plugin, ejb, and aspect types in the ArtifactType class and maps the type to an extension different then from the type. This won't work for distributions because there are at least 3 different extensions for the distribution type. Maven needs to either needs to have a way to handle this special case and be able to download all the possible extensions. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-113) Add download links to all plugin versions on the download page
Message: The following issue has been closed. Resolver: Brett Porter Date: Mon, 28 Jun 2004 9:22 PM done - View the issue: http://jira.codehaus.org/browse/MAVEN-113 Here is an overview of the issue: - Key: MAVEN-113 Summary: Add download links to all plugin versions on the download page Type: Improvement Status: Closed Priority: Minor Resolution: FIXED Original Estimate: 4 hours Time Spent: Unknown Remaining: 4 hours Project: maven Assignee: Reporter: dion gillard Created: Thu, 19 Sep 2002 5:27 AM Updated: Mon, 28 Jun 2004 9:22 PM Environment: N/A Description: There is currently no easy way to know which versions of plugins are available @ ibiblio. It'd be nice if the download page listed the plugins (all versions) available for download. This could be a generated page using the plugin's versions tag - 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-1342) rc4 downloads snapshots even if a newer one exists
Message: The following issue has been closed. Resolver: Brett Porter Date: Mon, 28 Jun 2004 9:33 PM double clicked submit. dupes maven-1343 - View the issue: http://jira.codehaus.org/browse/MAVEN-1342 Here is an overview of the issue: - Key: MAVEN-1342 Summary: rc4 downloads snapshots even if a newer one exists Type: Bug Status: Closed Priority: Major Resolution: DUPLICATE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Assignee: Brett Porter Reporter: Brett Porter Created: Mon, 28 Jun 2004 9:33 PM Updated: Mon, 28 Jun 2004 9:33 PM Description: looks like something went awry in the code change and snapshots are now always downloaded. - 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-1343) rc4 downloads snapshots even if a newer one exists
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1343 Here is an overview of the issue: - Key: MAVEN-1343 Summary: rc4 downloads snapshots even if a newer one exists Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Fix Fors: 1.0 Assignee: Brett Porter Reporter: Brett Porter Created: Mon, 28 Jun 2004 9:33 PM Updated: Mon, 28 Jun 2004 9:33 PM Description: looks like something went awry in the code change and snapshots are now always downloaded. - 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-1342) rc4 downloads snapshots even if a newer one exists
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1342 Here is an overview of the issue: - Key: MAVEN-1342 Summary: rc4 downloads snapshots even if a newer one exists Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Assignee: Brett Porter Reporter: Brett Porter Created: Mon, 28 Jun 2004 9:33 PM Updated: Mon, 28 Jun 2004 9:33 PM Description: looks like something went awry in the code change and snapshots are now always downloaded. - 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-1344) downloads from all repos even if first was successful
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1344 Here is an overview of the issue: - Key: MAVEN-1344 Summary: downloads from all repos even if first was successful Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Fix Fors: 1.0 Versions: 1.0-rc4 Assignee: Brett Porter Reporter: Brett Porter Created: Mon, 28 Jun 2004 9:34 PM Updated: Mon, 28 Jun 2004 9:34 PM Description: when more than one remote repo is defined, maven downloads from all of them if the artifact didn't exist, even if the first download is successful. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/checkstyle plugin.jelly
vmassol 2004/06/28 22:42:45
Modified:checkstyle plugin.jelly
Log:
ensure that the full dir exists
Revision ChangesPath
1.28 +1 -1 maven-plugins/checkstyle/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/checkstyle/plugin.jelly,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- plugin.jelly 28 Jun 2004 21:04:04 - 1.27
+++ plugin.jelly 29 Jun 2004 05:42:45 - 1.28
@@ -205,7 +205,7 @@
prettyPrint=true/
!-- Copy the RSS XML logo --
-mkdir dir=${maven.docs.dest}/
+mkdir dir=${maven.docs.dest}/images/
copy todir=${maven.docs.dest}/images
file=${plugin.resources}/images/rss.png/
/goal
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[checkstyle] First try at generating a RSS feed - Feedback wanted
Hi guys, Yesterday, I've committed my first at generating a RSS feed of checkstyle errors. The idea is that whenever the project site is redeployed the feed will get updated. Feedback is much welcome. Thanks -Vincent
Re: [checkstyle] First try at generating a RSS feed - Feedback wanted
I'll take a look. Is this generic enough to be used in other reports and the dashboard? I find checkstyle useless personally, but an RSS of changes.xml, junit, cactus and others would be really nice... Cheers, Brett Quoting Vincent Massol [EMAIL PROTECTED]: Hi guys, Yesterday, I've committed my first at generating a RSS feed of checkstyle errors. The idea is that whenever the project site is redeployed the feed will get updated. Feedback is much welcome. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
