Re: Publishing plugin sites

2006-12-08 Thread Stephane Nicoll
On 12/8/06, Wendy Smoak [EMAIL PROTECTED] wrote: Just a reminder and in case it needs more discussion: we are now publishing the latest plugin docs from svn, and not waiting for a release to do it. Can't we add the version of the plugin matching the status of the documentation? Even if we

Re: [vote] release maven-dependency-tree

2006-12-08 Thread Stephane Nicoll
+1 Stéphane On 12/7/06, Joakim Erdfelt [EMAIL PROTECTED] wrote: This has been corrected in subversion. [maven-dependency-tree]$ mvn -PsharedResources clean package ...(snip) ... [maven-dependency-tree]$ jar -tvf target/maven-dependency-tree-1.0-SNAPSHOT.jar 0 Thu Dec 07 17:38:32 EST

Re: [vote] release maven-dependency-tree

2006-12-08 Thread Fabrizio Giustina
+1 fabrizio On 12/7/06, Joakim Erdfelt [EMAIL PROTECTED] wrote: I would like to get maven-dependency-tree out of SNAPSHOT mode. I'm proposing making it 1.0-alpha-1. Found at https://svn.apache.org/repos/asf/maven/shared/trunk/maven-dependency-tree It is used by

Re: [vote] release maven-dependency-tree

2006-12-08 Thread Mark Hobson
+1 :) Mark On 08/12/06, Fabrizio Giustina [EMAIL PROTECTED] wrote: +1 fabrizio On 12/7/06, Joakim Erdfelt [EMAIL PROTECTED] wrote: I would like to get maven-dependency-tree out of SNAPSHOT mode. I'm proposing making it 1.0-alpha-1. Found at

Maven 1.x Release Requirements

2006-12-08 Thread Jason van Zyl
Hi, Some please get the Maven 1.x that they know of up so we can try to work together to get the release out. The only things I see are: - compatibility - that wagon is used for transport as we have to get rid of commons- httpclient, or at least the version that is currently killing us I

Re: Maven 1.x Release Requirements

2006-12-08 Thread Martin van den Bemt
(don't use maven 1 anymore) Do you mean the problem that httpclient by default doesn't follow redirects ? If it is an option to have a quicker release by just fixing the httpclient wagon provider, I can have a go at fixing that (I prefer httpclient over the lightweight one, since that one

Re: Maven 1.x Release Requirements

2006-12-08 Thread Lukas Theussl
AFAICT neither maven-core nor the artifact plugin are actually using httpclient anymore, only the jira and linkcheck plugins still use it. For compat, the blocker is MAVEN-1755, that's the only issue IMO that needs to be resolved for 1.1. Arnaud was working on it, I let him sum up the status.

Re: Maven 1.x Release Requirements

2006-12-08 Thread Jason van Zyl
On 8 Dec 06, at 8:38 AM 8 Dec 06, Martin van den Bemt wrote: (don't use maven 1 anymore) Do you mean the problem that httpclient by default doesn't follow redirects ? Right. If it is an option to have a quicker release by just fixing the httpclient wagon provider, I can have a go at

Re: Maven 1.x Release Requirements

2006-12-08 Thread Jason van Zyl
On 8 Dec 06, at 9:06 AM 8 Dec 06, Lukas Theussl wrote: AFAICT neither maven-core nor the artifact plugin are actually using httpclient anymore, only the jira and linkcheck plugins still use it. For compat, the blocker is MAVEN-1755, that's the only issue IMO that needs to be resolved

Re: Maven 1.x Release Requirements

2006-12-08 Thread Martin van den Bemt
Is an hotfix not the easiest way to get this solved ? Mvgr, Martin Jason van Zyl wrote: On 8 Dec 06, at 8:38 AM 8 Dec 06, Martin van den Bemt wrote: (don't use maven 1 anymore) Do you mean the problem that httpclient by default doesn't follow redirects ? Right. If it is an option

Re: Maven 1.x Release Requirements

2006-12-08 Thread Jason van Zyl
On 8 Dec 06, at 9:16 AM 8 Dec 06, Martin van den Bemt wrote: Is an hotfix not the easiest way to get this solved ? Not really. In order for things to work m1 users just need to change a configuration. Easier then upgrading a JAR. But for a real fix we need to get m1 users over to the m2

Re: [VOTE] Release Maven-SCM 1.0-beta-4

2006-12-08 Thread Emmanuel Venisse
5 PMC - 2 commiter - 1 user with +1 I start the release now Emmanuel Emmanuel Venisse a écrit : Hi I'd like to release 1.0-beta-4. We have 41 issues fixed in it since April 2006, and lot of them fix some pb in plugins that use Maven-SCM (release, changelog plugins and continuum) +1 from

Re: [m2] New pre-package phase?

2006-12-08 Thread Aaron . Digulla
Kenney Westerhof [EMAIL PROTECTED] schrieb am 07.12.2006 15:54:46: Hi, What I'm reading below looks exactly like Maven, except for the scope of the dependencies. Just for fun, I'll try to make the differences in your system and maven more concrete. Correct me if I get anything

maven-ear-plugin: is har supported or not?

2006-12-08 Thread Graham Leggett
Hi all, According to the docs at http://maven.apache.org/plugins/maven-ear-plugin/modules.html#harModule, it is now at long last possible to build ear files containing har files with maven. Unfortunately, any attempt at adding the config in the docs results in this exception:

Re: maven-ear-plugin: is har supported or not?

2006-12-08 Thread Stephane Nicoll
Hi, On 12/8/06, Graham Leggett [EMAIL PROTECTED] wrote: Hi all, According to the docs at http://maven.apache.org/plugins/maven-ear-plugin/modules.html#harModule, it is now at long last possible to build ear files containing har files with maven. Has the version of the maven-ear-plugin

Re: maven-ear-plugin: is har supported or not?

2006-12-08 Thread Graham Leggett
Stephane Nicoll wrote: No, it's implemented as from 2.3 which is not yet released. You can retrieve it on the snapshot repository [1] or you can build the plugin from source yourself. Are there any showstoppers preventing its release? I was very confusing to see the docs for the new plugin

Re: maven-ear-plugin: is har supported or not?

2006-12-08 Thread Stephane Nicoll
On 12/8/06, Graham Leggett [EMAIL PROTECTED] wrote: Stephane Nicoll wrote: No, it's implemented as from 2.3 which is not yet released. You can retrieve it on the snapshot repository [1] or you can build the plugin from source yourself. Are there any showstoppers preventing its release?

Re: maven-ear-plugin: is har supported or not?

2006-12-08 Thread Graham Leggett
Stephane Nicoll wrote: Are there any showstoppers preventing its release? No. I just need to cast a vote and we'll release it. Here is a non binding +1 for release: +1 :) I was very confusing to see the docs for the new plugin released and live before the plugin itself. Yes, the sites

maven-eclipse-plugin and eclipse:make-artifacts

2006-12-08 Thread Graham Leggett
Hi all, According to the docs at http://maven.apache.org/plugins/maven-eclipse-plugin/make-artifacts-mojo.html, the eclipse plugin can import artifacts from an eclipse installation. The most recent released plugin disagrees: [INFO]

[Ann] Maven-SCM 1.0-beta-4 is released

2006-12-08 Thread Emmanuel Venisse
Hi, I'm happy to announce the release of Maven-SCM 1.0-beta-4. This version includes lot of fixes for CVS, Subversion, Perforce, Clearcase, Starteam, Visual Source Safe and the support of CM Synergy. Release Notes :

Re: svn commit: r484646 - in /maven/plugins/trunk/maven-gpg-plugin: ./ src/main/java/org/apache/maven/plugin/gpg/GpgSignAttachedMojo.java

2006-12-08 Thread Wendy Smoak
On 12/8/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Author: evenisse Date: Fri Dec 8 07:53:20 2006 New Revision: 484646 URL: http://svn.apache.org/viewvc?view=revrev=484646 Log: Don't generate signature on artifact when the project is a pom I think poms also need to be signed, see:

Re: Ibiblio repository broken for Maven 1.0.2

2006-12-08 Thread Carlos Sanchez
The workaround is to use the mirror configuration. maven.repo.remote=http://mirrors.ibiblio.org/pub/mirrors/maven We are waiting for the ibiblio guys to fix it On 12/7/06, Jeff Turner [EMAIL PROTECTED] wrote: On Thu, Nov 30, 2006 at 04:26:04PM +0200, Jukka Zitting wrote: Hi, On 11/30/06,

Re: [result] Archiva Logo

2006-12-08 Thread Henri Yandell
On 12/7/06, Brett Porter [EMAIL PROTECTED] wrote: I have decided to call this in favour of UR. http://people.apache.org/ ~brett/archiva-logos/ur.html Good call, +1 to your decision. Hen

normalize usage in RepositoryAccess

2006-12-08 Thread Henri Yandell
In looking at moving from Plexus FileUtils.normalize to IO FilenameUtils.normalize, there's on feature difference in that the latter does not convert '//etc/passwd' to '/etc/passwd'. Kenney suggests on #plexus that that is probably to support Windows SMB names. RepositoryAccessTest contains a

Re: svn commit: r481446 - in /maven/archiva/trunk: ./ archiva-cli/ archiva-cli/src/main/java/org/apache/maven/archiva/cli/ archiva-configuration/ archiva-configuration/src/main/java/org/apache/maven/a

2006-12-08 Thread Henri Yandell
On 12/3/06, Trygve Laugstøl [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: Author: bayard Date: Fri Dec 1 15:44:12 2006 New Revision: 481446 URL: http://svn.apache.org/viewvc?view=revrev=481446 Log: Moved from Plexus-Util StringUtils to Lang StringUtils. replace, split and join

Re: svn commit: r484649 - /maven/scm/trunk/pom.xml

2006-12-08 Thread Brett Porter
Shouldn't these be in the release profile so they are activated automatically? On 09/12/2006, at 3:20 AM, [EMAIL PROTECTED] wrote: Author: evenisse Date: Fri Dec 8 08:20:43 2006 New Revision: 484649 URL: http://svn.apache.org/viewvc?view=revrev=484649 Log: add two profiles for the release

Re: svn commit: r484646 - in /maven/plugins/trunk/maven-gpg-plugin: ./ src/main/java/org/apache/maven/plugin/gpg/GpgSignAttachedMojo.java

2006-12-08 Thread Brett Porter
Why not? I think signing the metadata is just as important. - Brett On 09/12/2006, at 2:53 AM, [EMAIL PROTECTED] wrote: Author: evenisse Date: Fri Dec 8 07:53:20 2006 New Revision: 484646 URL: http://svn.apache.org/viewvc?view=revrev=484646 Log: Don't generate signature on artifact when the

Re: svn commit: r484633 - in /maven/sandbox/plugins/maven-license-plugin: ./ src/main/java/org/apache/maven/plugins/license/ src/main/java/org/apache/maven/plugins/license/filetype/ src/main/java/org/

2006-12-08 Thread Brett Porter
What is the license on the .jj file? On 09/12/2006, at 2:15 AM, [EMAIL PROTECTED] wrote: Author: joakime Date: Fri Dec 8 07:15:03 2006 New Revision: 484633 URL: http://svn.apache.org/viewvc?view=revrev=484633 Log: Some uncommmited work against a java parser.

Re: [Ann] Maven-SCM 1.0-beta-4 is released

2006-12-08 Thread Brett Porter
Did you send this to [EMAIL PROTECTED] On 09/12/2006, at 4:55 AM, Emmanuel Venisse wrote: Hi, I'm happy to announce the release of Maven-SCM 1.0-beta-4. This version includes lot of fixes for CVS, Subversion, Perforce, Clearcase, Starteam, Visual Source Safe and the support of CM Synergy.

Re: svn commit: r484646 - in /maven/plugins/trunk/maven-gpg-plugin: ./ src/main/java/org/apache/maven/plugin/gpg/GpgSignAttachedMojo.java

2006-12-08 Thread Wendy Smoak
On 12/8/06, Brett Porter [EMAIL PROTECTED] wrote: Why not? I think signing the metadata is just as important. The maven-metadata.xml files? 1. It's not required by the readme file and 2. They change on every deployment, so you'd be overwriting the signature, which could well belong to

Re: svn commit: r484646 - in /maven/plugins/trunk/maven-gpg-plugin: ./ src/main/java/org/apache/maven/plugin/gpg/GpgSignAttachedMojo.java

2006-12-08 Thread Brett Porter
Sorry, responded having read the commits list, not the dev list :) I agreed with your mail - when I said metadata I meant POMs. Definitely don't need to sign maven-metadata.xml. - Brett On 09/12/2006, at 12:19 PM, Wendy Smoak wrote: On 12/8/06, Brett Porter [EMAIL PROTECTED] wrote: Why

Maven 1.1 development status - For a release, help required ....

2006-12-08 Thread Arnaud Héritier
Hi guys, I'm back. Sorry for the delay to reply to this emergency. As you certainly know we released the beta 3 at the beginning of august. The next step for us it to release a first release candidate to quickly have a final release. We are focusing on keeping the compatibility

Re: Maven 1.1 development status - For a release, help required ....

2006-12-08 Thread Brett Porter
On 09/12/2006, at 12:46 PM, Arnaud Héritier wrote: MAVEN-1755 Backward Incompability : Usage of xml entities in the POM doesn't work in maven 1.1 beta 1 2 I began to fix this one. I modified the maven-model to use a new one which uses dom4j and not xpp3 (and it works). For that

Re: normalize usage in RepositoryAccess

2006-12-08 Thread Brett Porter
Wouldn't the windows SMB name be //central/etc/password? ie, normalize should remove duplicate path separators unless they are leading? - Brett On 09/12/2006, at 8:17 AM, Henri Yandell wrote: In looking at moving from Plexus FileUtils.normalize to IO FilenameUtils.normalize, there's on

Re: normalize usage in RepositoryAccess

2006-12-08 Thread Joakim Erdfelt
The Request Path is what is being tested here. Proper pattern is /${repoId}/${pathToResource} The idea with the normalize found in RepositoryAccess is to prevent a user from requesting resources outside of the repository tree, such as /etc/passwd or /etc/groups or the configuration files for the

Re: svn commit: r484649 - /maven/scm/trunk/pom.xml

2006-12-08 Thread Jason van Zyl
On 8 Dec 06, at 7:25 PM 8 Dec 06, Brett Porter wrote: Shouldn't these be in the release profile so they are activated automatically? Not until they are tested a few times. I will do a series of releases with them and Emm is doing the same. Jason. On 09/12/2006, at 3:20 AM, [EMAIL

Re: Maven 1.1 development status - For a release, help required ....

2006-12-08 Thread Lukas Theussl
Arnaud Héritier wrote: Those plugins use maven-model, thus it could be interesting to wait for the release of maven-model 3.0.2 before to release them : artifact, eclipse, ejb, multiproject and xdoc are ready, they should be released for RC1 even without upgraded model dependency.