Re: [vote] release Maven 1.0.1

2004-11-11 Thread Brett Porter
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

cvs commit: maven/xdocs/start release-notes-1.0.1.xml download.xml

2004-11-11 Thread brett
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

Re: [vote] release Maven 1.0.1

2004-11-11 Thread Martin van den Bemt
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

Re: [vote] release Maven 1.0.1

2004-11-11 Thread Brett Porter
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

[ANN] Maven 1.0.1 Released

2004-11-11 Thread Brett Porter
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

[jira] Commented: (MPEAR-20) Deploy error because of display name

2004-11-11 Thread jira
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.

RE: [ANN] Maven 1.0.1 Released

2004-11-11 Thread Jörg Schaible
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,

Ant plugin and maven.jar.override

2004-11-11 Thread Eric Pugh
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

Re: Ant plugin and maven.jar.override

2004-11-11 Thread Brett Porter
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

RE: Ant plugin and maven.jar.override

2004-11-11 Thread Arnaud HERITIER
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

cvs commit: maven build-bootstrap.xml maven.xml plugin-profile.xml project.properties project.xml

2004-11-11 Thread brett
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

RE: Ant plugin and maven.jar.override

2004-11-11 Thread Eric Pugh
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

cvs commit: maven-plugins/changes/xdocs changes.xml

2004-11-11 Thread vmassol
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

cvs commit: maven-plugins/ear/xdocs changes.xml properties.xml

2004-11-11 Thread felipeal
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

[jira] Closed: (MPEAR-20) Deploy error because of display name

2004-11-11 Thread jira
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

[jira] Commented: (MPECLIPSE-56) Only create .classpath and javabuilder if sources are present

2004-11-11 Thread jira
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

[jira] Commented: (MPECLIPSE-56) Only create .classpath and javabuilder if sources are present

2004-11-11 Thread jira
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

[jira] Created: (MPJDEE-1) support jde-maven-command in prj.el

2004-11-11 Thread jira
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:

[jira] Updated: (MPJDEE-1) support jde-maven-command in prj.el

2004-11-11 Thread jira
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

cvs commit: maven-plugins/changes/src/plugin-resources changes.jsl

2004-11-11 Thread vmassol
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

[jira] Closed: (MPCHANGES-14) Allow entries to be sorted by action type.

2004-11-11 Thread jira
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:

[jira] Commented: (MPECLIPSE-56) Only create .classpath and javabuilder if sources are present

2004-11-11 Thread jira
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.

[jira] Commented: (MAVEN-1495) Test dependencies are NOT build / use dependencies

2004-11-11 Thread jira
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

RE: Ant plugin and maven.jar.override

2004-11-11 Thread Arnaud HERITIER
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

[jira] Commented: (MPECLIPSE-56) Only create .classpath and javabuilder if sources are present

2004-11-11 Thread jira
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

Strange exceptions during struts-config generation with xdoclet

2004-11-11 Thread Corey Scott
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

Re: Strange exceptions during struts-config generation with xdoclet

2004-11-11 Thread Konstantin Priblouda
--- 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

[jira] Closed: (MAVENUPLOAD-254) Clover 1.3.2 jar

2004-11-11 Thread jira
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-254 Here is an overview of the issue: -

[jira] Closed: (MAVENUPLOAD-247) Upload javassist-3.0-rc-1.jar

2004-11-11 Thread jira
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-247 Here is an overview of the issue: -

[jira] Closed: (MPJAVA-25) Bug in documentation: maven.compile.target property is missed

2004-11-11 Thread jira
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:

cvs commit: maven-plugins/ear/src/plugin-test/test02 maven.xml project.xml

2004-11-11 Thread felipeal
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

[jira] Closed: (MPEAR-12) incorrect property name for context root in ear plugin

2004-11-11 Thread jira
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). -

Writing plugin testcases (WAS Re: [jira] Commented: (MPECLIPSE-56) Only create .classpath and javabuilder if sources are present)

2004-11-11 Thread Felipe Leme
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,

[jira] Created: (MPCRUISECONTROL-15) Lost script extension when use maven cruisecontrol:configure command

2004-11-11 Thread jira
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: -

[jira] Commented: (MPECLIPSE-56) Only create .classpath and javabuilder if sources are present

2004-11-11 Thread jira
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