Re: [vote] release Maven 1.0.1
Given that it was unanimous, this is now underway. The releases are there, and I am about to publish the site and mail the announcement I have also removed the RC releases from the distribution directory (they are still available at archive.apache.org). Hopefully this will strongly encourage upgrades. Thanks to everyone who's put in to submit and commit patches, fix bugs and test the release. Nice job! Cheers, Brett Brett Porter wrote: As I speak, I am building and uploading Maven 1.0.1 to http://www.apache.org/~brett/release-1.0.1 Please vote whether you think this should be an official release. If the vote is carried, I will move the release to the distribution area, update the website and post the announcement in 24 hours. +1 from me. Cheers, Brett - 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]
cvs commit: maven/xdocs/start release-notes-1.0.1.xml download.xml
brett 2004/11/11 00:28:54 Modified:xdocsTag: MAVEN-1_0-BRANCH index.xml status.xml xdocs/misc Tag: MAVEN-1_0-BRANCH index.xml powered.xml xdocs/start Tag: MAVEN-1_0-BRANCH download.xml Added: xdocs/start Tag: MAVEN-1_0-BRANCH release-notes-1.0.1.xml Log: updated documentation for the release Revision ChangesPath No revision No revision 1.11.10.5 +9 -7 maven/xdocs/index.xml Index: index.xml === RCS file: /home/cvs/maven/xdocs/index.xml,v retrieving revision 1.11.10.4 retrieving revision 1.11.10.5 diff -u -r1.11.10.4 -r1.11.10.5 --- index.xml 30 Oct 2004 04:27:49 - 1.11.10.4 +++ index.xml 11 Nov 2004 08:28:53 - 1.11.10.5 @@ -27,14 +27,15 @@ body - section name=Maven 1.0 Released - 13 July 2004 -pMaven 1.0 has been released.br/ a href=start/download.htmlDownload/a | -a href=start/install.htmlInstallation Instructions/a | -a href=start/release-notes-1.0.htmlRelease Notes/a -/p - /section - section name=Maven +subsection name=Get Maven + pMaven 1.0.1: a href=start/download.htmlDownload/a | +a href=start/install.htmlInstallation Instructions/a | +a href=start/release-notes-1.0.1.htmlRelease Notes/a + /p +/subsection + +subsection name=About Maven p Maven is a Java project management and project comprehension tool. Maven is based on the concept of a project object model (POM) in that all the @@ -61,6 +62,7 @@ and propagating the critical information about your project which is necessary in order to attract potential new developers and clients. /p + /subsection /section section name=The Big Picture 1.16.4.7 +11 -175 maven/xdocs/Attic/status.xml Index: status.xml === RCS file: /home/cvs/maven/xdocs/Attic/status.xml,v retrieving revision 1.16.4.6 retrieving revision 1.16.4.7 diff -u -r1.16.4.6 -r1.16.4.7 --- status.xml13 Jul 2004 14:21:03 - 1.16.4.6 +++ status.xml11 Nov 2004 08:28:53 - 1.16.4.7 @@ -21,205 +21,41 @@ document properties -titleNews and Status/title +titleStatus/title author email=[EMAIL PROTECTED]Pete Kazmier/author /properties body -section name=News and Status - p -This document contains the latest news and status regarding the -Maven project. It is here you'll find announcements related to -Maven. - /p - +section name=Status subsection name=Current Status p - We are currently catching developing a roadmap for future Maven development + We are currently developing a roadmap for future Maven development in the 1.x and 2.x series. /p - /subsection - - subsection name=13 July 2004 - Maven 1.0 released! p - See the a href=start/release-notes-1.0.htmlRelease Notes/a for more - information. + Check out a href=http://jira.codehaus.org/browse/MAVEN;JIRA/a for the + current road map to the 1.1 release. /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. + For the latest news and information on Maven, check out a href=http://www.mavenblogs.com;Maven Blogs/a. /p /subsection - subsection name=21 May 2004 - Maven 1.0 RC3 released! + subsection name=11 November 2004 - Maven 1.0.1 released! p - See the a href=start/release-notes-rc3.htmlRelease Notes/a for more + See the a href=start/release-notes-1.0.1.htmlRelease Notes/a for more information. /p /subsection - - subsection name=24 March 2004 - Maven 1.0 RC2 released! + subsection name=13 July 2004 - Maven 1.0 released! p - See the a href=start/release-notes-rc2.htmlRelease Notes/a for more + See the a href=start/release-notes-1.0.htmlRelease Notes/a for more information. /p /subsection - - subsection name=30 September 2003 - Maven 1.0 RC1 released! -p - Another quiet release mostly - a href=http://jira.codehaus.org/secure/IssueNavigator.jspa?view=amp;tempMax=1000amp;decorator=printableamp;start=0amp;fixfor=10181amp;mode=hideamp;reset=trueamp;pid=10030;fixing - problems/a with plugins and leaving some core refactoring problems - for the next leg of development. -
Re: [vote] release Maven 1.0.1
Is it possible to have a source release (at least for the maven-core)? Mvgr, Martin On Thu, 2004-11-11 at 09:15, Brett Porter wrote: Given that it was unanimous, this is now underway. The releases are there, and I am about to publish the site and mail the announcement I have also removed the RC releases from the distribution directory (they are still available at archive.apache.org). Hopefully this will strongly encourage upgrades. Thanks to everyone who's put in to submit and commit patches, fix bugs and test the release. Nice job! Cheers, Brett Brett Porter wrote: As I speak, I am building and uploading Maven 1.0.1 to http://www.apache.org/~brett/release-1.0.1 Please vote whether you think this should be an official release. If the vote is carried, I will move the release to the distribution area, update the website and post the announcement in 24 hours. +1 from me. Cheers, Brett - 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] -- Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release Maven 1.0.1
I would like to, but I've always stumbled on what to do with the plugins. Out of the box, a source release would require a prior installation of Maven and internet access to build, which doesn't sit well with me. I think it'd be a good idea to discuss this here, sort it out, and do it. I'd also like to do a documentation release. Cheers, Brett Martin van den Bemt wrote: Is it possible to have a source release (at least for the maven-core)? Mvgr, Martin On Thu, 2004-11-11 at 09:15, Brett Porter wrote: Given that it was unanimous, this is now underway. The releases are there, and I am about to publish the site and mail the announcement I have also removed the RC releases from the distribution directory (they are still available at archive.apache.org). Hopefully this will strongly encourage upgrades. Thanks to everyone who's put in to submit and commit patches, fix bugs and test the release. Nice job! Cheers, Brett Brett Porter wrote: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven 1.0.1 Released
The maven team is pleased to announce the Maven 1.0.1 release! http://maven.apache.org/start/download.html This release contains bugfixes since the Maven 1.0 release. In addition, all of the latest stable plugin releases are included, which include both bugfixes and some new features. We recommend that all users upgrade to this release, in particular those using pre-1.0 betas or release candidates. 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. Changes in this version can be found here: http://maven.apache.org/changes-report.html#1_0_1 Please note that each plugin has its own changes report - please refer to the plugins site to see the plugin you are interested in. For news and information, see: - Maven Blogs: http://www.mavenblogs.com/ Have fun! -The Apache Maven Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPEAR-20) Deploy error because of display name
The following comment has been added to this issue:
Author: Joerg Schaible
Created: Thu, 11 Nov 2004 4:42 AM
Body:
Personally I don't care. The artifactId only should rarely conflict with other
apps as long as the default for the display name not just breaks the deployment.
-
View this comment:
http://jira.codehaus.org/browse/MPEAR-20?page=comments#action_26322
-
View the issue:
http://jira.codehaus.org/browse/MPEAR-20
Here is an overview of the issue:
-
Key: MPEAR-20
Summary: Deploy error because of display name
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-ear-plugin
Versions:
1.5
Assignee: Felipe Leme
Reporter: Joerg Schaible
Created: Wed, 15 Sep 2004 6:32 AM
Updated: Thu, 11 Nov 2004 4:42 AM
Environment: IONA Orbix Application Server Platform, Windows
Description:
The IONA Orbix J2EE server uses the display name as root directory for the
exploaded EAR. Unfortunately this contains by default a colon
(${pom.groupId}:${pom.artifactId}) for a generated application.xml which is
obviously not an allowed character for files in Windows. This default value
should be set to something, that does not break any app server. Proposal: dot
-
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: [ANN] Maven 1.0.1 Released
Brett Porter wrote on Thursday, November 11, 2004 10:04 AM: The maven team is pleased to announce the Maven 1.0.1 release! Applause! Clap! Clap! Clap! Long awaited. Thanks for all your effort. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Ant plugin and maven.jar.override
Hi all,
I am working on generating an Ant file for a project that is using the
maven.jar.override option. We have a /lib/ directory where we have placed
some javamail.jar and activation.jar so that users dont' have to manually
install them.
However, when I run 'maven ant', the generated build.xml still tries to
download these dependencies from the remote repo. I am thinking about
modifying the Ant plugin so that if a dependency is located within the
project (relative to basedir) then we don't try and download it, but just
add it to the classpath from wherever it is.
However, if a dependency was specified as being in the local repo under a
different version or a completely different location, then the ant script
would work the same.
Is this a good idea? I think that the contained somewhere below the
${basedir} check on a jar implies that whoever is using the Ant build would
have checked out the project and have the jar on their local filesystem,
correct?
Eric Pugh
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ant plugin and maven.jar.override
I would think the correct behaviour is to simply honour the jar override
whenever it is set, regardless of where it points (remember that they
can be versions though, not necessarily a file!)
so add ${maven.jar.foo} to the classpath instead of getting it for
dependency foo if jar.override is on and jar.foo is not numerical.
Cheers,
Brett
Eric Pugh wrote:
Hi all,
I am working on generating an Ant file for a project that is using the
maven.jar.override option. We have a /lib/ directory where we have placed
some javamail.jar and activation.jar so that users dont' have to manually
install them.
However, when I run 'maven ant', the generated build.xml still tries to
download these dependencies from the remote repo. I am thinking about
modifying the Ant plugin so that if a dependency is located within the
project (relative to basedir) then we don't try and download it, but just
add it to the classpath from wherever it is.
However, if a dependency was specified as being in the local repo under a
different version or a completely different location, then the ant script
would work the same.
Is this a good idea? I think that the contained somewhere below the
${basedir} check on a jar implies that whoever is using the Ant build would
have checked out the project and have the jar on their local filesystem,
correct?
Eric Pugh
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Ant plugin and maven.jar.override
I think that this problem is already opened here:
http://jira.codehaus.org/browse/MPANT-7
I didn't yet investigate it.
Vote for it if you think that the proposed solution resolve your problem
Arnaud
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 11 novembre 2004 11:24
À : Maven Developers List
Objet : Re: Ant plugin and maven.jar.override
I would think the correct behaviour is to simply honour the jar override
whenever it is set, regardless of where it points (remember that they
can be versions though, not necessarily a file!)
so add ${maven.jar.foo} to the classpath instead of getting it for
dependency foo if jar.override is on and jar.foo is not numerical.
Cheers,
Brett
Eric Pugh wrote:
Hi all,
I am working on generating an Ant file for a project that is using the
maven.jar.override option. We have a /lib/ directory where we have placed
some javamail.jar and activation.jar so that users dont' have to manually
install them.
However, when I run 'maven ant', the generated build.xml still tries to
download these dependencies from the remote repo. I am thinking about
modifying the Ant plugin so that if a dependency is located within the
project (relative to basedir) then we don't try and download it, but just
add it to the classpath from wherever it is.
However, if a dependency was specified as being in the local repo under a
different version or a completely different location, then the ant script
would work the same.
Is this a good idea? I think that the contained somewhere below the
${basedir} check on a jar implies that whoever is using the Ant build would
have checked out the project and have the jar on their local filesystem,
correct?
Eric Pugh
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven build-bootstrap.xml maven.xml plugin-profile.xml project.properties project.xml
brett 2004/11/11 02:56:10 Modified:src/bin maven maven.bat src/conf defaults.properties driver.properties src/java/org/apache/maven/cli App.java src/java/org/apache/maven/jelly/tags/werkz MavenAttainGoalTag.java src/java/org/apache/maven/plugin PluginCacheManager.java PluginManager.java src/java/org/apache/maven/project Project.java src/java/org/apache/maven/repository AbstractArtifact.java Artifact.java src/java/org/apache/maven/util HttpUtils.java src/java/org/apache/maven/verifier DependencyVerifier.java src/java/org/apache/maven ArtifactListBuilder.java MavenSession.java MavenUtils.java src/test/java/org/apache/maven MavenUtilsTest.java src/test/touchstone-build/src/reactor-build/default/subproject maven.xml src/test/touchstone-build/src/reactor-build/default maven.xml src/test/touchstone-build maven.xml project.properties project.xml xdocs/misc index.xml powered.xml xdocs/reference/developers releasing-plugins.xml xdocs/reference project-descriptor.xml user-guide.xml xdocs/start bootstrap.xml download.xml index.xml install.xml integrate.xml xdocschanges.xml faq.fml features.xml getting-started.xml index.xml navigation-pdf.xml navigation.xml repository-upload.xml .build-bootstrap.xml maven.xml plugin-profile.xml project.properties project.xml Added: xdocs/start release-notes-1.0.1.xml xdocsobjectives.xml Removed: xdocs/start release-notes-rc2.xml release-notes-rc3.xml release-notes-rc4.xml xdocsgoals.xml Log: Merge MAVEN_1_0 to MAVEN_1_0_1 Revision ChangesPath 1.37 +10 -6 maven/src/bin/maven http://cvs.apache.org/viewcvs/maven/src/bin/maven.diff?r1=1.36r2=1.37 1.44 +1 -1 maven/src/bin/maven.bat http://cvs.apache.org/viewcvs/maven/src/bin/maven.bat.diff?r1=1.43r2=1.44 1.13 +4 -2 maven/src/conf/defaults.properties http://cvs.apache.org/viewcvs/maven/src/conf/defaults.properties.diff?r1=1.12r2=1.13 1.9 +1 -0 maven/src/conf/driver.properties http://cvs.apache.org/viewcvs/maven/src/conf/driver.properties.diff?r1=1.8r2=1.9 1.42 +38 -35maven/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.41r2=1.42 1.7 +2 -7 maven/src/java/org/apache/maven/jelly/tags/werkz/MavenAttainGoalTag.java http://cvs.apache.org/viewcvs/maven/src/java/org/apache/maven/jelly/tags/werkz/MavenAttainGoalTag.java.diff?r1=1.6r2=1.7 1.24 +8 -14 maven/src/java/org/apache/maven/plugin/PluginCacheManager.java http://cvs.apache.org/viewcvs/maven/src/java/org/apache/maven/plugin/PluginCacheManager.java.diff?r1=1.23r2=1.24 1.80 +259 -122 maven/src/java/org/apache/maven/plugin/PluginManager.java http://cvs.apache.org/viewcvs/maven/src/java/org/apache/maven/plugin/PluginManager.java.diff?r1=1.79r2=1.80 1.101 +5 -14 maven/src/java/org/apache/maven/project/Project.java http://cvs.apache.org/viewcvs/maven/src/java/org/apache/maven/project/Project.java.diff?r1=1.100r2=1.101 1.26 +16 -2 maven/src/java/org/apache/maven/repository/AbstractArtifact.java http://cvs.apache.org/viewcvs/maven/src/java/org/apache/maven/repository/AbstractArtifact.java.diff?r1=1.25r2=1.26 1.21 +10 -2 maven/src/java/org/apache/maven/repository/Artifact.java http://cvs.apache.org/viewcvs/maven/src/java/org/apache/maven/repository/Artifact.java.diff?r1=1.20r2=1.21 1.35 +23 -32maven/src/java/org/apache/maven/util/HttpUtils.java http://cvs.apache.org/viewcvs/maven/src/java/org/apache/maven/util/HttpUtils.java.diff?r1=1.34r2=1.35 1.40 +22 -2 maven/src/java/org/apache/maven/verifier/DependencyVerifier.java http://cvs.apache.org/viewcvs/maven/src/java/org/apache/maven/verifier/DependencyVerifier.java.diff?r1=1.39r2=1.40 1.17 +3 -1 maven/src/java/org/apache/maven/ArtifactListBuilder.java http://cvs.apache.org/viewcvs/maven/src/java/org/apache/maven/ArtifactListBuilder.java.diff?r1=1.16r2=1.17 1.25 +1 -4 maven/src/java/org/apache/maven/MavenSession.java http://cvs.apache.org/viewcvs/maven/src/java/org/apache/maven/MavenSession.java.diff?r1=1.24r2=1.25 1.115 +35 -34
RE: Ant plugin and maven.jar.override
I think it would solve my issue. Do you mind if I take a stab at
implementing it?
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 11, 2004 10:30 AM
To: 'Maven Developers List'
Subject: RE: Ant plugin and maven.jar.override
I think that this problem is already opened here:
http://jira.codehaus.org/browse/MPANT-7
I didn't yet investigate it.
Vote for it if you think that the proposed solution resolve your problem
Arnaud
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 11 novembre 2004 11:24
À : Maven Developers List
Objet : Re: Ant plugin and maven.jar.override
I would think the correct behaviour is to simply honour the jar override
whenever it is set, regardless of where it points (remember that they
can be versions though, not necessarily a file!)
so add ${maven.jar.foo} to the classpath instead of getting it for
dependency foo if jar.override is on and jar.foo is not numerical.
Cheers,
Brett
Eric Pugh wrote:
Hi all,
I am working on generating an Ant file for a project that is using the
maven.jar.override option. We have a /lib/ directory where we
have placed
some javamail.jar and activation.jar so that users dont' have
to manually
install them.
However, when I run 'maven ant', the generated build.xml still tries to
download these dependencies from the remote repo. I am thinking about
modifying the Ant plugin so that if a dependency is located within the
project (relative to basedir) then we don't try and download
it, but just
add it to the classpath from wherever it is.
However, if a dependency was specified as being in the local
repo under a
different version or a completely different location, then the
ant script
would work the same.
Is this a good idea? I think that the contained somewhere below the
${basedir} check on a jar implies that whoever is using the
Ant build would
have checked out the project and have the jar on their local
filesystem,
correct?
Eric Pugh
-
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]
-
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]
cvs commit: maven-plugins/changes/xdocs changes.xml
vmassol 2004/11/11 03:53:54 Modified:changes project.xml changes/xdocs changes.xml Log: Prepare for 1.6 development Revision ChangesPath 1.36 +1 -1 maven-plugins/changes/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/changes/project.xml,v retrieving revision 1.35 retrieving revision 1.36 diff -u -r1.35 -r1.36 --- project.xml 23 Oct 2004 11:08:54 - 1.35 +++ project.xml 11 Nov 2004 11:53:54 - 1.36 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-changes-plugin/id nameMaven Changes Plugin/name - currentVersion1.5.1/currentVersion + currentVersion1.6-SNAPSHOT/currentVersion shortDescriptionProduce changes report/shortDescription urlhttp://maven.apache.org/reference/plugins/changes//url issueTrackingUrlhttp://jira.codehaus.org/browse/MPCHANGES/issueTrackingUrl 1.32 +2 -0 maven-plugins/changes/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/changes/xdocs/changes.xml,v retrieving revision 1.31 retrieving revision 1.32 diff -u -r1.31 -r1.32 --- changes.xml 23 Oct 2004 11:08:54 - 1.31 +++ changes.xml 11 Nov 2004 11:53:54 - 1.32 @@ -24,6 +24,8 @@ author email=[EMAIL PROTECTED]Vincent Massol/author /properties body +release version=1.6-SNAPSHOT date=in CVS +/release release version=1.5.1 date=2004-10-23 action dev=vmassol type=fix issue=MPCHANGES-20Fixed typo in changes.xml example on plugin web site./action action dev=carlos type=fix issue=MPCHANGES-19Close output file in ReleaseVersion.releaseVersion()/action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/ear/xdocs changes.xml properties.xml
felipeal2004/11/11 03:55:45
Modified:ear plugin.properties
ear/xdocs changes.xml properties.xml
Log:
fix for MPEAR-20: changed the default value of the maven.ear.displayname
Revision ChangesPath
1.8 +2 -2 maven-plugins/ear/plugin.properties
Index: plugin.properties
===
RCS file: /home/cvs/maven-plugins/ear/plugin.properties,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- plugin.properties 15 Oct 2004 05:07:35 - 1.7
+++ plugin.properties 11 Nov 2004 11:55:45 - 1.8
@@ -28,7 +28,7 @@
maven.ear.appxml=${maven.ear.descriptordir}/application.xml
maven.ear.manifest=${maven.ear.descriptordir}/MANIFEST.MF
maven.ear.appxml.generate=false
-maven.ear.displayname=${pom.id}
+maven.ear.displayname=${pom.artifactId}
maven.ear.appxml.version=1.3
maven.ear.resources=${maven.build.dir}/ear
-maven.ear.appxml.encoding=UTF-8
\ No newline at end of file
+maven.ear.appxml.encoding=UTF-8
1.25 +2 -1 maven-plugins/ear/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/ear/xdocs/changes.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- changes.xml 11 Nov 2004 03:28:41 - 1.24
+++ changes.xml 11 Nov 2004 11:55:45 - 1.25
@@ -25,7 +25,8 @@
/properties
body
release version=1.6-SNAPSHOT date=in CVS
- action dev=felipeal type=felipeal issue=MPEAR-23 due-to=Wiley
FullerAdd new property dependency(codeear.target.path/code) to define
where a dependency should be added in the EAR./action
+ action dev=felipeal type=fix issue=MPEAR-20Changed the default
value of codemaven.ear.displayname/code./action
+ action dev=felipeal type=add issue=MPEAR-23 due-to=Wiley
FullerAdd new property dependency(codeear.target.path/code) to define
where a dependency should be added in the EAR./action
action dev=felipeal type=fix issue=MPEAR-9 due-to=Sean
TimmBuild now fails in some cases were the dependencies are copied with wrong
case./action
action dev=felipeal type=add issue=MPEAR-21Added property
codemaven.ear.appxml.encoding/code./action
action dev=vmassol type=update issue=MPEAR-19
1.16 +1 -1 maven-plugins/ear/xdocs/properties.xml
Index: properties.xml
===
RCS file: /home/cvs/maven-plugins/ear/xdocs/properties.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- properties.xml11 Nov 2004 03:28:41 - 1.15
+++ properties.xml11 Nov 2004 11:55:45 - 1.16
@@ -78,7 +78,7 @@
when codeapplication.xml/code file is autogenerated
/td
td
-${pom.id}
+${pom.artifactId}
/td
/tr
tr
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPEAR-20) Deploy error because of display name
Message:
The following issue has been closed.
Resolver: Felipe Leme
Date: Thu, 11 Nov 2004 7:00 AM
Fixed - the default value is now ${pom.artifactId}
-
View the issue:
http://jira.codehaus.org/browse/MPEAR-20
Here is an overview of the issue:
-
Key: MPEAR-20
Summary: Deploy error because of display name
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-ear-plugin
Fix Fors:
1.6
Versions:
1.5
Assignee: Felipe Leme
Reporter: Joerg Schaible
Created: Wed, 15 Sep 2004 6:32 AM
Updated: Thu, 11 Nov 2004 7:00 AM
Environment: IONA Orbix Application Server Platform, Windows
Description:
The IONA Orbix J2EE server uses the display name as root directory for the
exploaded EAR. Unfortunately this contains by default a colon
(${pom.groupId}:${pom.artifactId}) for a generated application.xml which is
obviously not an allowed character for files in Windows. This default value
should be set to something, that does not break any app server. Proposal: dot
-
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-56) Only create .classpath and javabuilder if sources are present
The following comment has been added to this issue: Author: Felipe Leme Created: Thu, 11 Nov 2004 8:23 AM Body: Archimedes/Eric, I'd like to add a test case for this fix. The test case per se wouldn't be hard, but it would require a new project.xml (without a source), which would in turn require that we break the test cases structure into multi-project. So, any better idea on how to test it? -- Felipe - View this comment: http://jira.codehaus.org/browse/MPECLIPSE-56?page=comments#action_26326 - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-56 Here is an overview of the issue: - Key: MPECLIPSE-56 Summary: Only create .classpath and javabuilder if sources are present Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-eclipse-plugin Versions: 1.9 Assignee: Reporter: Archimedes Trajano Created: Wed, 10 Nov 2004 2:13 AM Updated: Thu, 11 Nov 2004 8:23 AM Description: Only create .classpath and javabuilder if sources are present - 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-56) Only create .classpath and javabuilder if sources are present
The following comment has been added to this issue: Author: David Eric Pugh Created: Thu, 11 Nov 2004 8:31 AM Body: to be honest, we need to make it a multiproject setup anyway for the tests.. there are too many different project.xml structures, our tests are becoming more and more intertwined.. For instance, if you have cactus plugin or not.. Feel free to break them up (see hibernate plugin for an example). Eric - View this comment: http://jira.codehaus.org/browse/MPECLIPSE-56?page=comments#action_26327 - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-56 Here is an overview of the issue: - Key: MPECLIPSE-56 Summary: Only create .classpath and javabuilder if sources are present Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-eclipse-plugin Versions: 1.9 Assignee: Reporter: Archimedes Trajano Created: Wed, 10 Nov 2004 2:13 AM Updated: Thu, 11 Nov 2004 8:31 AM Description: Only create .classpath and javabuilder if sources are present - 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: (MPJDEE-1) support jde-maven-command in prj.el
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPJDEE-1 Here is an overview of the issue: - Key: MPJDEE-1 Summary: support jde-maven-command in prj.el Type: New Feature Status: Unassigned Priority: Minor Original Estimate: 30 minutes Time Spent: Unknown Remaining: 30 minutes Project: maven-jdee-plugin Components: default Assignee: Reporter: Dominik Dahlem Created: Thu, 11 Nov 2004 8:35 AM Updated: Thu, 11 Nov 2004 8:35 AM Description: Add support for generating a jde-maven-command entry in the prj.el file. - 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: (MPJDEE-1) support jde-maven-command in prj.el
The following issue has been updated: Updater: Dominik Dahlem (mailto:[EMAIL PROTECTED]) Date: Thu, 11 Nov 2004 8:37 AM Comment: patch to support jde-maven-command in prj.el. Changes: Attachment changed to patch.diff - For a full history of the issue, see: http://jira.codehaus.org/browse/MPJDEE-1?page=history - View the issue: http://jira.codehaus.org/browse/MPJDEE-1 Here is an overview of the issue: - Key: MPJDEE-1 Summary: support jde-maven-command in prj.el Type: New Feature Status: Unassigned Priority: Minor Original Estimate: 30 minutes Time Spent: Unknown Remaining: 30 minutes Project: maven-jdee-plugin Components: default Assignee: Reporter: Dominik Dahlem Created: Thu, 11 Nov 2004 8:35 AM Updated: Thu, 11 Nov 2004 8:37 AM Description: Add support for generating a jde-maven-command entry in the prj.el file. - 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/changes/src/plugin-resources changes.jsl
vmassol 2004/11/11 05:46:58
Modified:changes plugin.properties
changes/xdocs properties.xml changes.xml
changes/src/plugin-resources changes.jsl
Log:
MPCHANGES-14: Added sorting of codelt;actiongt;/code elements. It is
controlled by 2 properties. The codemaven.changes.sort/code property
decides whether sorting is enabled or not and the
codemaven.changes.sort.order/code one decides the sort order. Defaults to
codeadd,fix,update,remove/code.
Revision ChangesPath
1.8 +6 -0 maven-plugins/changes/plugin.properties
Index: plugin.properties
===
RCS file: /home/cvs/maven-plugins/changes/plugin.properties,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- plugin.properties 10 Jul 2004 16:32:50 - 1.7
+++ plugin.properties 11 Nov 2004 13:46:58 - 1.8
@@ -35,3 +35,9 @@
# For Sourceforge, use the aid parameter. For example:
# maven.changes.issue.template =
http://sourceforge.net/support/tracker.php?aid=%ISSUE%
+
+# Decide whether to sort the change actions by type or not
+maven.changes.sort = false
+
+# Decide the sort order for action types
+maven.changes.sort.order = add,fix,update,remove
1.6 +22 -0 maven-plugins/changes/xdocs/properties.xml
Index: properties.xml
===
RCS file: /home/cvs/maven-plugins/changes/xdocs/properties.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- properties.xml13 Jun 2004 16:16:48 - 1.5
+++ properties.xml11 Nov 2004 13:46:58 - 1.6
@@ -45,6 +45,28 @@
BugZilla: code%URL%/show_bug.cgi?id=%ISSUE%/code
/td
/tr
+tr
+ tdmaven.changes.sort/td
+ tdYes/td
+ td
+Decides whether to enable sorting the codelt;actiongt;/code
+elements or not.
+ /td
+ td
+false
+ /td
+/tr
+tr
+ tdmaven.changes.sort.order/td
+ tdYes/td
+ td
+Decides sort ordering of codelt;actiongt;/code elements.
+It is only used if sorting is enabled.
+ /td
+ td
+add,fix,update,remove
+ /td
+/tr
/table
/section
/body
1.33 +7 -0 maven-plugins/changes/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/changes/xdocs/changes.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- changes.xml 11 Nov 2004 11:53:54 - 1.32
+++ changes.xml 11 Nov 2004 13:46:58 - 1.33
@@ -25,6 +25,13 @@
/properties
body
release version=1.6-SNAPSHOT date=in CVS
+ action dev=vmassol type=fix issue=MPCHANGES-14
+Added sorting of codelt;actiongt;/code elements. It is
controlled
+by 2 properties. The codemaven.changes.sort/code property decides
+whether sorting is enabled or not and the
+codemaven.changes.sort.order/code one decides the sort order.
+Defaults to codeadd,fix,update,remove/code.
+ /action
/release
release version=1.5.1 date=2004-10-23
action dev=vmassol type=fix issue=MPCHANGES-20Fixed typo in
changes.xml example on plugin web site./action
1.14 +39 -2 maven-plugins/changes/src/plugin-resources/changes.jsl
Index: changes.jsl
===
RCS file: /home/cvs/maven-plugins/changes/src/plugin-resources/changes.jsl,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- changes.jsl 29 Jun 2004 20:39:56 - 1.13
+++ changes.jsl 11 Nov 2004 13:46:58 - 1.14
@@ -26,6 +26,8 @@
xmlns:jsl=jelly:jsl
xmlns:x=jelly:xml
xmlns:doc=doc
+xmlns:u=jelly:util
+xmlns:ant=jelly:ant
xmlns=dummy trim=false
jsl:template match=document
@@ -66,8 +68,43 @@
j:set var=anchorNamedoc:escapeNameToken
value=${version}//j:set
a name=${anchorName}/
table
- trth style='width:50px'Type/ththChanges/thth
style='width:70px'By/th/tr
- jsl:applyTemplates select=*/
+ trth style='width:50px'Type/ththChanges/thth
style='width:70px'By/th/tr
+ j:choose
+j:when test=${maven.changes.sort}
+ u:tokenize var=actionTypes delim=,
${maven.changes.sort.order}/u:tokenize
+
+ !-- FIXME: Big hack here. Jelly looses the reference to the
+ current node so we have to explicitely remember
[jira] Closed: (MPCHANGES-14) Allow entries to be sorted by action type.
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Thu, 11 Nov 2004 8:51 AM
ok, I understand now. I have implemented a first version of it.
-
View the issue:
http://jira.codehaus.org/browse/MPCHANGES-14
Here is an overview of the issue:
-
Key: MPCHANGES-14
Summary: Allow entries to be sorted by action type.
Type: New Feature
Status: Closed
Priority: Major
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-changes-plugin
Fix Fors:
1.6
Versions:
1.4
Assignee: Vincent Massol
Reporter: Gary Gregory
Created: Tue, 22 Jun 2004 2:30 AM
Updated: Thu, 11 Nov 2004 8:51 AM
Environment: maven -i
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc3
# BEGIN: Which report
Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)
java.version=1.4.2_04
file.encoding=Cp1252
java.ext.dirs=C:\java\sun\1.4.2_04\jre\lib\ext
java.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\forehead-1.0-beta-5.jar
os.name=Windows XP
java.vendor=Sun Microsystems Inc.
sun.boot.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\endorsed\xerces-2.4.0.jar;C:\Program Files\Apache Software
Foundation\Maven 1.
0-rc3\lib\endorsed\xml-apis-1.0.b2.jar;C:\java\sun\1.4.2_04\jre\lib\rt.jar;C:\java\sun\1.4.2_04\jre\lib\i18n.jar;C:\java\sun\1.4.2_04\jre\lib\sunrsasign.jar;C:\
java\sun\1.4.2_04\jre\lib\jsse.jar;C:\java\sun\1.4.2_04\jre\lib\jce.jar;C:\java\sun\1.4.2_04\jre\lib\charsets.jar;C:\java\sun\1.4.2_04\jre\classes
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
# END: Which report
Installed plugins:
maven-castor-plugin-1.2
maven-site-plugin-1.5
maven-multiproject-plugin-1.3
maven-jdepend-plugin-1.5
maven-clover-plugin-1.5
maven-genapp-plugin-2.2
maven-jbuilder-plugin-1.5
maven-jboss-plugin-1.5
maven-dashboard-plugin-1.3
maven-artifact-plugin-1.2
maven-developer-activity-plugin-1.5
maven-war-plugin-1.6
maven-native-plugin-1.1
maven-cruisecontrol-plugin-1.2
maven-webserver-plugin-2.0
maven-docbook-plugin-1.2
maven-deploy-plugin-1.3
maven-ear-plugin-1.5
maven-repository-plugin-1.2
maven-j2ee-plugin-1.5
maven-jnlp-plugin-1.3
maven-linkcheck-plugin-1.2
maven-javadoc-plugin-1.5
maven-vdoclet-plugin-1.2
maven-hibernate-plugin-1.1
maven-appserver-plugin-2.0
maven-antlr-plugin-1.2
maven-jira-plugin-1.1
maven-ant-plugin-1.7
maven-gump-plugin-1.3
maven-tasklist-plugin-2.3
maven-xdoc-plugin-1.7.1
maven-ashkelon-plugin-1.2
maven-tjdo-plugin-1.0.0
maven-html2xdoc-plugin-1.3
maven-announcement-plugin-1.1
maven-pmd-plugin-1.4
maven-jxr-plugin-1.4
maven-struts-plugin-1.3
maven-latka-plugin-1.4
maven-junit-doclet-plugin-1.2
maven-pom-plugin-1.4
maven-changelog-plugin-1.5
maven-clean-plugin-1.2
maven-license-plugin-1.2
maven-jetty-plugin-1.1
maven-jdee-plugin-1.1
maven-file-activity-plugin-1.5
maven-jcoverage-plugin-1.0.4
maven-jdiff-plugin-1.4
maven-jar-plugin-1.5
maven-scm-plugin-1.3
maven-aspectwerkz-plugin-1.2
maven-faq-plugin-1.3
maven-plugin-plugin-1.3
maven-dist-plugin-1.5
maven-jellydoc-plugin-1.3
maven-javacc-plugin-1.1
maven-shell-plugin-1.1
maven-simian-plugin-1.4
maven-ejb-plugin-1.4
maven-java-plugin-1.4
maven-console-plugin-1.1
maven-pdf-plugin-2.1
maven-release-plugin-1.3
maven-changes-plugin-1.4
maven-nsis-plugin-1.0
maven-checkstyle-plugin-2.4.1
maven-wizard-plugin-1.1
maven-uberjar-plugin-1.2
maven-caller-plugin-1.1
maven-junit-report-plugin-1.5
maven-eclipse-plugin-1.7
maven-latex-plugin-1.2
maven-jdeveloper-plugin-1.4
maven-aspectj-plugin-3.0
maven-idea-plugin-1.4
maven-jalopy-plugin-1.2
maven-test-plugin-1.6.1
maven-multichanges-plugin-1.1
Home Build properties:
{jaxp.xslt.jar=C:/java/apache/xalan-2_5_D1//bin/xalan.jar,
servlet.jar=C:/java/sun/jwsdp-1.1/common/lib/servlet.jar, jaxp.jaxp.jar=C:/jav
a/apache/xalan-2_5_D1//bin/xml-apis.jar, junit.jar=C:/java/junit3.8.1/junit.jar}
Description:
Allow entries to be sorted by action type.
Today, I must sort (and keep sorted :-) the action entries in changes.xml. It
would be nice to be able to specify - perhaps in the properties file - that the
generated XML and text file be sorted by action. Maybe something like:
maven.changes.action.sort = add, fix, update, remove
-
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,
[jira] Commented: (MPECLIPSE-56) Only create .classpath and javabuilder if sources are present
The following comment has been added to this issue: Author: Archimedes Trajano Created: Thu, 11 Nov 2004 9:55 AM Body: Is there any documentation on how to create non-java plugin test cases? I am still confused on how to write them. - View this comment: http://jira.codehaus.org/browse/MPECLIPSE-56?page=comments#action_26330 - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-56 Here is an overview of the issue: - Key: MPECLIPSE-56 Summary: Only create .classpath and javabuilder if sources are present Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-eclipse-plugin Versions: 1.9 Assignee: Reporter: Archimedes Trajano Created: Wed, 10 Nov 2004 2:13 AM Updated: Thu, 11 Nov 2004 9:55 AM Description: Only create .classpath and javabuilder if sources are present - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1495) Test dependencies are NOT build / use dependencies
The following comment has been added to this issue: Author: Corey Scott Created: Thu, 11 Nov 2004 10:32 AM Body: I have to say, I agree with Bryan and there seems to be similar requests/musings in some of the mailings list (maven-users / commons-dev (i think)) regarding this. I am happy to look into this if others agree that this is a useful feature? Thanks, -Corey - View this comment: http://jira.codehaus.org/browse/MAVEN-1495?page=comments#action_26331 - View the issue: http://jira.codehaus.org/browse/MAVEN-1495 Here is an overview of the issue: - Key: MAVEN-1495 Summary: Test dependencies are NOT build / use dependencies Type: Improvement Status: Unassigned Priority: Minor Original Estimate: 2 days Time Spent: Unknown Remaining: 2 days Project: maven Components: core Assignee: Reporter: bryan thompson Created: Fri, 5 Nov 2004 7:54 AM Updated: Thu, 11 Nov 2004 10:32 AM Environment: all Description: Feature: The POM dependency/ element should be modified to have an well-known attribute that identifies whether a dependency applies to the build, runtime, or tests. The site generation plugin should be modified to reflect this distinction in the generated documentation. Rationale: I find that I need to include various jars for testing purposes that are not a dependency for building or otherwise using the artifact generated by my maven project. At present, there is no way to mark a dependency as test-only such that it does not show up on the Dependencies report in the generated site documentation. This results in misleading documentation (in the generated site) and confounds the notion of a project test dependency with a project build or runtime dependency. Thanks, -bryan - 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: Ant plugin and maven.jar.override
You can submit a patch and if possible a test case.
I'll commit them as soon as possible.
Arnaud
-Message d'origine-
De : Eric Pugh [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 11 novembre 2004 12:20
À : Maven Developers List
Objet : RE: Ant plugin and maven.jar.override
I think it would solve my issue. Do you mind if I take a stab at
implementing it?
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 11, 2004 10:30 AM
To: 'Maven Developers List'
Subject: RE: Ant plugin and maven.jar.override
I think that this problem is already opened here:
http://jira.codehaus.org/browse/MPANT-7
I didn't yet investigate it.
Vote for it if you think that the proposed solution resolve your problem
Arnaud
-Message d'origine-
De: Brett Porter [mailto:[EMAIL PROTECTED]
Envoy: jeudi 11 novembre 2004 11:24
: Maven Developers List
Objet: Re: Ant plugin and maven.jar.override
I would think the correct behaviour is to simply honour the jar override
whenever it is set, regardless of where it points (remember that they
can be versions though, not necessarily a file!)
so add ${maven.jar.foo} to the classpath instead of getting it for
dependency foo if jar.override is on and jar.foo is not numerical.
Cheers,
Brett
Eric Pugh wrote:
Hi all,
I am working on generating an Ant file for a project that is using the
maven.jar.override option. We have a /lib/ directory where we
have placed
some javamail.jar and activation.jar so that users dont' have
to manually
install them.
However, when I run 'maven ant', the generated build.xml still tries to
download these dependencies from the remote repo. I am thinking about
modifying the Ant plugin so that if a dependency is located within the
project (relative to basedir) then we don't try and download
it, but just
add it to the classpath from wherever it is.
However, if a dependency was specified as being in the local
repo under a
different version or a completely different location, then the
ant script
would work the same.
Is this a good idea? I think that the contained somewhere below the
${basedir} check on a jar implies that whoever is using the
Ant build would
have checked out the project and have the jar on their local
filesystem,
correct?
Eric Pugh
-
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]
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPECLIPSE-56) Only create .classpath and javabuilder if sources are present
The following comment has been added to this issue: Author: David Eric Pugh Created: Thu, 11 Nov 2004 10:54 AM Body: It's mostly a matter of learning by example. If you look at maven-plugins/hibernate/src/test-plugin/ there is a good example of using multiproject to test a collection of seperate projects and testcases. Most of the plugins have testcases to look at in maven-plugins/[PLUGIN]/src/test-plugin. Eric - View this comment: http://jira.codehaus.org/browse/MPECLIPSE-56?page=comments#action_26333 - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-56 Here is an overview of the issue: - Key: MPECLIPSE-56 Summary: Only create .classpath and javabuilder if sources are present Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-eclipse-plugin Versions: 1.9 Assignee: Reporter: Archimedes Trajano Created: Wed, 10 Nov 2004 2:13 AM Updated: Thu, 11 Nov 2004 10:54 AM Description: Only create .classpath and javabuilder if sources are present - 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]
Strange exceptions during struts-config generation with xdoclet
This may be [OT] if it is please forgive me, and please tell me where I should be posting this, but... I am getting strange exception thrown when generating my struts config (web.xml/struts-config.xml/validation.xml) on something that previously worked, albeit on a different computer. Below is the stack trace, does anyone know what I can do to fix this? Thanks, Corey java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:112) at java.util.zip.ZipFile.init(ZipFile.java:128) at org.apache.tools.ant.AntClassLoader.getResourceURL(AntClassLoader.java:870) at org.apache.tools.ant.AntClassLoader.getResource(AntClassLoader.java:799) at java.lang.Class.getResource(Class.java:1352) at xdoclet.tagshandler.MergeTagsHandler.getMergeFileContents(MergeTagsHandler.java:207) at xdoclet.tagshandler.MergeTagsHandler.merge(MergeTagsHandler.java:67) at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at xdoclet.template.TemplateEngine.invoke(TemplateEngine.java:635) at xdoclet.template.TemplateEngine.invokeMethod(TemplateEngine.java:534) at xdoclet.template.TemplateEngine.invokeBlockMethod(TemplateEngine.java:959) at xdoclet.template.TemplateEngine.handleBlockTag(TemplateEngine.java:926) at xdoclet.template.TemplateEngine.handleTag(TemplateEngine.java:466) at xdoclet.template.TemplateEngine.generate(TemplateEngine.java:347) at xdoclet.XDocletTagSupport.generate(XDocletTagSupport.java:738) at xdoclet.tagshandler.ClassTagsHandler.forAllClasses(ClassTagsHandler.java:331) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at xdoclet.template.TemplateEngine.invoke(TemplateEngine.java:635) at xdoclet.template.TemplateEngine.invokeMethod(TemplateEngine.java:561) at xdoclet.template.TemplateEngine.invokeBlockMethod(TemplateEngine.java:959) at xdoclet.template.TemplateEngine.handleBlockTag(TemplateEngine.java:926) at xdoclet.template.TemplateEngine.handleTag(TemplateEngine.java:466) at xdoclet.template.TemplateEngine.generate(TemplateEngine.java:347) at xdoclet.template.TemplateEngine.start(TemplateEngine.java:414) at xdoclet.TemplateSubTask.startEngine(TemplateSubTask.java:560) at xdoclet.TemplateSubTask.startProcessForAll(TemplateSubTask.java:616) at xdoclet.TemplateSubTask.startProcess(TemplateSubTask.java:597) at xdoclet.XmlSubTask.startProcess(XmlSubTask.java:198) at xdoclet.modules.web.WebXmlSubTask.execute(WebXmlSubTask.java:366) at xdoclet.XDocletMain.start(XDocletMain.java:48) at xdoclet.DocletTask.start(DocletTask.java:464) at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:110) at org.apache.tools.ant.Task.perform(Task.java:341) at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:232) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at com.werken.werkz.jelly.PreGoalTag$1.firePreGoal(PreGoalTag.java:87) at com.werken.werkz.Goal.firePreGoalCallbacks(Goal.java:691) at com.werken.werkz.Goal.fire(Goal.java:616) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.Goal.attainPrecursors(Goal.java:488) at com.werken.werkz.Goal.attain(Goal.java:573) at com.werken.werkz.Goal.attainPrecursors(Goal.java:488) at com.werken.werkz.Goal.attain(Goal.java:573) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:634) at
Re: Strange exceptions during struts-config generation with xdoclet
--- Corey Scott [EMAIL PROTECTED] wrote: This may be [OT] if it is please forgive me, and please tell me where I should be posting this, but... I am getting strange exception thrown when generating my struts config (web.xml/struts-config.xml/validation.xml) on something that previously worked, albeit on a different computer. Below is the stack trace, does anyone know what I can do to fix this? I would say that you got corrupted jar file somewhere... regards, = [ Konstantin Pribluda ( ko5tik ) ] Plugins for xdoclet-2 are releassed. check it out http://www.sourceforge.net/projects/xdoclet-plugins/ [ http://www.pribluda.de ] __ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-254) Clover 1.3.2 jar
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-254 Here is an overview of the issue: - Key: MAVENUPLOAD-254 Summary: Clover 1.3.2 jar Type: Task Status: Closed Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Carlos Sanchez Reporter: Henri Yandell Created: Mon, 8 Nov 2004 4:22 PM Updated: Thu, 11 Nov 2004 4:47 PM Description: Bundle of the latest version of Clover. Cenqua have given permission for this. Note that I have not called it clover-ant, as that stops people being able to override the clover jar and allowing their clover-plugin to use it. The LICENSE.txt file is just a copy of the 30-day license and should not go out onto the site. The bundle feature refused to work without a license. - 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: (MAVENUPLOAD-247) Upload javassist-3.0-rc-1.jar
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-247 Here is an overview of the issue: - Key: MAVENUPLOAD-247 Summary: Upload javassist-3.0-rc-1.jar Type: Task Status: Closed Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Carlos Sanchez Reporter: Howard M. Lewis Ship Created: Tue, 2 Nov 2004 5:28 PM Updated: Thu, 11 Nov 2004 4:49 PM Description: This is the latest version of Javassist. It's part of the JBoss project. Home page: http://www.jboss.org/products/javassist - 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: (MPJAVA-25) Bug in documentation: maven.compile.target property is missed
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MPJAVA-25 Here is an overview of the issue: - Key: MPJAVA-25 Summary: Bug in documentation: maven.compile.target property is missed Type: Bug Status: Closed Priority: Minor Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-java-plugin Fix Fors: 1.5 Assignee: Jason van Zyl Reporter: Alexey Kakunin Created: Mon, 12 Jul 2004 7:25 AM Updated: Thu, 11 Nov 2004 5:24 PM Environment: Maven 1.0 rc4 Description: I found this bug in Java-Plugin web-site. In properties documentation mave.compile.target property is missed. But maven.compile.source property exist twice :) Seems one of them should be renamed to target. - 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/ear/src/plugin-test/test02 maven.xml project.xml
felipeal2004/11/11 18:10:32
Modified:ear/src/plugin-test/test02 maven.xml project.xml
Log:
MPEAR-20: add test that checks if a dependency without the new property is
set correctly
Revision ChangesPath
1.2 +2 -2 maven-plugins/ear/src/plugin-test/test02/maven.xml
Index: maven.xml
===
RCS file: /home/cvs/maven-plugins/ear/src/plugin-test/test02/maven.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- maven.xml 11 Nov 2004 03:28:41 - 1.1
+++ maven.xml 12 Nov 2004 02:10:32 - 1.2
@@ -40,8 +40,8 @@
assert:assertFileExists
file=${unzipDir}/APP-INF/lib/commons-logging-1.0.3.jar
msg=commons logging was not bundled/
-!-- check that commons-collections has not been packaged --
-assert:assertFileNotFound
file=${unzipDir}/APP-INF/lib/commons-collections-2.1.jar
+!-- check that commons-collections has been packaged in the right
place--
+assert:assertFileExists file=${unzipDir}/commons-collections-2.1.jar
msg=commons collections was bundled incorrectly/
1.2 +9 -2 maven-plugins/ear/src/plugin-test/test02/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven-plugins/ear/src/plugin-test/test02/project.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- project.xml 11 Nov 2004 03:28:41 - 1.1
+++ project.xml 12 Nov 2004 02:10:32 - 1.2
@@ -45,10 +45,17 @@
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
version1.0.3/version
- urlhttp://jakarta.apache.org/commons/logging.html/url
properties
-ear.bundletrue/ear.bundle
ear.target.pathAPP-INF/lib/ear.target.path
+ear.moduletrue/ear.module
+ /properties
+/dependency
+dependency
+ groupIdcommons-collections/groupId
+ artifactIdcommons-collections/artifactId
+ version2.1/version
+ properties
+ear.bundletrue/ear.bundle
/properties
/dependency
/dependencies
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPEAR-12) incorrect property name for context root in ear plugin
Message: The following issue has been closed. Resolver: Felipe Leme Date: Thu, 11 Nov 2004 9:18 PM I've checked the code and the documentation is already using the right property (ear.appxml.war.context-root). - View the issue: http://jira.codehaus.org/browse/MPEAR-12 Here is an overview of the issue: - Key: MPEAR-12 Summary: incorrect property name for context root in ear plugin Type: Bug Status: Closed Priority: Minor Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-ear-plugin Fix Fors: 1.5 Assignee: Reporter: Ryan Sonnek Created: Tue, 15 Jul 2003 12:51 PM Updated: Thu, 11 Nov 2004 9:18 PM Environment: maven-1.0-beta-10 ant-1.5.3 winXP Description: documentation states that the property to set the context-root for a war file is 'ear.appxml.war.context-root', but the plugin uses 'ear.appxml.ear.context-root' as the property. - 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]
Writing plugin testcases (WAS Re: [jira] Commented: (MPECLIPSE-56) Only create .classpath and javabuilder if sources are present)
Archimedes, Unfortunately, Eric is right - you gotta 'learn by examples', at least for now. I will comment how to do it in that Jira issue - let's use this thread for generic testcase layout issue. BTW, I think it's time to write a documentation about it, including how to write the test cases, what to test and Jelly tips. I could write such doc, but first we need to define some stuff: - what layout should we use by default? should we use the 'single project with one goal per testcase' or the 'multi-project with one project per testcase'? Let me explain better: usually, the single-project is more elegant and simpler. But in cases where we need diferent POMs for each tests, we need the multi-project setup. So the question really is: should we start with a single-project and migrate to multi-project only when we need to or should we start with a multi-project? - should we keep the test0? on the multi-project testcases or should we use a meaningful name for the directories? - once we migrate a single-project to the multi-project, should we use a standard name for the project with most of the testcases (i.e., with the maven.xml that was originally in the plugin)? These questions are not hard to answer, but we need to reach a consensus (and refactor the current testcases) before we write such documentation. -- Felipe On Thu, 2004-11-11 at 13:55, [EMAIL PROTECTED] wrote: The following comment has been added to this issue: Author: David Eric Pugh Created: Thu, 11 Nov 2004 10:54 AM Body: It's mostly a matter of learning by example. If you look at maven-plugins/hibernate/src/test-plugin/ there is a good example of using multiproject to test a collection of seperate projects and testcases. Most of the plugins have testcases to look at in maven-plugins/[PLUGIN]/src/test-plugin. Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPCRUISECONTROL-15) Lost script extension when use maven cruisecontrol:configure command
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPCRUISECONTROL-15 Here is an overview of the issue: - Key: MPCRUISECONTROL-15 Summary: Lost script extension when use maven cruisecontrol:configure command Type: Bug Status: Unassigned Priority: Major Original Estimate: 4 hours Time Spent: Unknown Remaining: 4 hours Project: maven-cruisecontrol-plugin Fix Fors: 1.4 Versions: 1.4 Assignee: Reporter: Qing Han Created: Thu, 11 Nov 2004 11:10 PM Updated: Thu, 11 Nov 2004 11:10 PM Environment: Windown 2000 pro JDK1.4.1 Maven1.0 maven-cc-plugin 1.4 Description: When I defined maven's config files(project.xml,project.properties,build.properties), maven's all tasks run ok then I use: maven cruisecontrol:configure to generate maven-cruisecontrol-plugin's config file(cruisecontrol.xml). then I run it: maven cruisecontrol:run BUT an error occured: === Project - exception attempting build in project XXX net.sourceforge.cruisecontrol.CruiseControlException: Encountered an IO exception while attempting to execute Maven. CruiseControl cannot continue. : CreateProcess: D:\Maven\bin\maven -Dcclastbuildtimestamp=2004111200 -Dlabel=build.1 -Dcclastgoodbuildtimestamp=2004111200 -Dlastbuildsuccessful=true -Dcvstimestamp=2004-11-12 02:01:23 GMT -Dcctimestamp=20041112100123 -X -b -p project.xml scm:update-project error=193 at net.sourceforge.cruisecontrol.builders.MavenBuilder.build(MavenBuilder.java:120) at net.sourceforge.cruisecontrol.Schedule.build(Schedule.java:144) at net.sourceforge.cruisecontrol.Project.build(Project.java:195) at net.sourceforge.cruisecontrol.Project.execute(Project.java:153) at net.sourceforge.cruisecontrol.ProjectWrapper.run(ProjectWrapper.java:66) at java.lang.Thread.run(Thread.java:536) === After I wast many time to fix this problem,I found the script extension lost in the cruisecontrol.xml: Default generated: schedule interval=300 maven goal=scm:update-project|clean test|site:deploy projectfile=project.xml mavenscript=D:/Maven/bin/maven /maven /schedule = when I add .bat to the mavenscript,it's OK now current: = schedule interval=300 maven goal=scm:update-project|clean test|site:deploy projectfile=project.xml mavenscript=D:/Maven/bin/maven.bat /maven /schedule = - 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-56) Only create .classpath and javabuilder if sources are present
The following comment has been added to this issue: Author: Felipe Leme Created: Thu, 11 Nov 2004 11:24 PM Body: Archimedes, Basically, what you have to do in this case is setup a project that doesn't have the source defined, run the eclipse goal and then parse the generated .classpath/.project to see if it was generated correctly (and failing if it doesn't). As Eric mentioned, the best way to understand how to achieve that is looking through other testcases. Also, you would need to create a new directory for this testcase, as it would require changing the current testcases POM. -- Felipe - View this comment: http://jira.codehaus.org/browse/MPECLIPSE-56?page=comments#action_26345 - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-56 Here is an overview of the issue: - Key: MPECLIPSE-56 Summary: Only create .classpath and javabuilder if sources are present Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-eclipse-plugin Versions: 1.9 Assignee: Reporter: Archimedes Trajano Created: Wed, 10 Nov 2004 2:13 AM Updated: Thu, 11 Nov 2004 11:24 PM Description: Only create .classpath and javabuilder if sources are present - 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]
