Re: [vote] [m1] release xdoc-plugin-1.10

2006-06-11 Thread Lukas Theussl

Thanks Dennis! See my comments in-line.


- There is no longer a pdf.gif file under /images/. 


This was deleted by Arnaud in rev 386905 
(http://svn.apache.org/viewvc?view=rev&revision=386905), and moved to 
the pdf plugin. Is there an issue with that?



- The "Downloads" link always shows up in the left hand navbar.


I built the beanutils page myself and I do not see the Download link. 
This link is only generated when the property 
'maven.xdoc.distributionUrl' is defined, however, I don't think this 
behavior has changed since xdoc-1.9.2.



- On some components [beanutils] the title is missing "Downloads" after 
the project name, on the downloads page.


- On some components [beanutils] the title is missing "Source 
repository" after the project name, on the scm-usage page.


Do you have a component where there is a title? - I don't see one 
anywhere, but you have that problem already on your current site (eg 
http://jakarta.apache.org/commons/beanutils/dependencies.html) which was 
built with xdoc-plugin-1.9.2 (I presume). It's due to an issue with your 
custom site.jsl (commons-site.jsl) file, it doesn't take into account 
that the standart Maven-generated pages are fully internationalized. I'd 
have to take a closer look to see how to fix it, but anyway, this is not 
an issue caused by xdoc-plugin-1.10.


- The "Development process" link in the navbar now goes to a generated 
page, which contains a link, instead of going to the url directly.


See http://jira.codehaus.org/browse/MPXDOC-170, apparently I forgot to 
add it to the changes.xml file. Will do.


- The file rename from cvs-usage to scm-usage will mean some work for 
us, but the change is well documented and it is "the right thing" to do.



:)

You didn't cast a vote but IMO these are all non-blocking issues (if 
issues at all), so I take it that we can go ahead with the release?


Thanks again for the testing and the feedback,

-Lukas

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: svn commit: r413502 - in /maven/plugins/trunk/maven-war-plugin/src/main/java/org/apache/maven/plugin/war: AbstractWarMojo.java WarManifestMojo.java WarMojo.java

2006-06-11 Thread Brett Porter

[EMAIL PROTECTED] wrote:

Author: jvanzyl
Date: Sun Jun 11 11:33:41 2006
New Revision: 413502

URL: http://svn.apache.org/viewvc?rev=413502&view=rev
Log:
MWAR-45: patch applied and snapshot deployed


Could we get this log updated to reflect what the change was?

Thanks,
Brett

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: svn commit: r413502 - in /maven/plugins/trunk/maven-war-plugin/src/main/java/org/apache/maven/plugin/war: AbstractWarMojo.java WarManifestMojo.java WarMojo.java

2006-06-11 Thread Brett Porter

[EMAIL PROTECTED] wrote:

Author: jvanzyl
Date: Sun Jun 11 11:33:41 2006
New Revision: 413502

URL: http://svn.apache.org/viewvc?rev=413502&view=rev
Log:
MWAR-45: patch applied and snapshot deployed


Could we get this log updated to reflect what the change was?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: svn commit: r413456 - /maven/plugins/trunk/maven-release-plugin/pom.xml

2006-06-11 Thread Brett Porter

You used an old version of the release plugin.

You should revert the change entirely as it did more to the pom (like 
removing things and reordering it), as well as delete the bogus tag.


- Brett

[EMAIL PROTECTED] wrote:

Author: jvanzyl
Date: Sun Jun 11 07:35:18 2006
New Revision: 413456

URL: http://svn.apache.org/viewvc?rev=413456&view=rev
Log:
o putting the POM back, i used the dryRun option to see what would happen and 
it changed the POM ... looking to see what happened.

Modified:
maven/plugins/trunk/maven-release-plugin/pom.xml

Modified: maven/plugins/trunk/maven-release-plugin/pom.xml
URL: 
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-release-plugin/pom.xml?rev=413456&r1=413455&r2=413456&view=diff
==
--- maven/plugins/trunk/maven-release-plugin/pom.xml (original)
+++ maven/plugins/trunk/maven-release-plugin/pom.xml Sun Jun 11 07:35:18 2006
@@ -8,7 +8,7 @@
   maven-release-plugin
   maven-plugin
   Maven Release plugin
-  2.0-beta-6-SNAPSHOT
+  2.0-beta-5-SNAPSHOT
   
 
   
@@ -157,4 +157,4 @@
   1.0-beta-3
 
   
-
\ No newline at end of file
+





--
Brett Porter <[EMAIL PROTECTED]>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Please sync Lucene to ibiblio

2006-06-11 Thread Martin Cooper

I've just deployed Lucene Core 1.9.1 and 2.0.0 to the ASF M2 repo:

http://www.apache.org/dist/maven-repository/org/apache/lucene/lucene-core/

Please sync to ibiblio. TIA.

--
Martin Cooper


RE: [vote] move maven-archiver from components to shared

2006-06-11 Thread Mike Perham
+1 

> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED] 
> Sent: Sunday, June 11, 2006 7:07 PM
> To: Maven Developers List
> Subject: [vote] move maven-archiver from components to shared
> 
> I propose that we move v2.1 of maven-archiver to the /shared/ 
> area of SVN. I think we should leave it on the branch for now, though.
> 
> This will allow it it's own release cycle, so that plugins 
> can depend on it sooner than Maven releases. Nothing in Maven 
> itself depends on it.
> 
> Cheers,
> Brett
> 
> --
> Brett Porter <[EMAIL PROTECTED]>
> Apache Maven - http://maven.apache.org/
> Better Builds with Maven - http://library.mergere.com/
> 
> -
> 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: [vote] move maven-archiver from components to shared

2006-06-11 Thread Jesse McConnell

+1 nice idea

On 6/11/06, Brett Porter <[EMAIL PROTECTED]> wrote:

I propose that we move v2.1 of maven-archiver to the /shared/ area of
SVN. I think we should leave it on the branch for now, though.

This will allow it it's own release cycle, so that plugins can depend on
it sooner than Maven releases. Nothing in Maven itself depends on it.

Cheers,
Brett

--
Brett Porter <[EMAIL PROTECTED]>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
jesse mcconnell
jesseDOTmcconnellATgmailDOTcom

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: ApacheCON europe, anybody there?

2006-06-11 Thread Alan D. Cabrera

Fabrizio Giustina wrote:

Hi,
will anybody from the maven team be at ApacheCon in Dublin? I see that
at least Jason will be there (great!), but nobody signed up for the
Hackathon yet...

just courius, I will be there at least for the first 2 days, and hope
to meet you there... (and just a few days before there is also the
Server Side Symposium in Barcelona, hope to meet people there too)

When is the Hackathon?


Regards,
Alan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[vote] move maven-archiver from components to shared

2006-06-11 Thread Brett Porter
I propose that we move v2.1 of maven-archiver to the /shared/ area of 
SVN. I think we should leave it on the branch for now, though.


This will allow it it's own release cycle, so that plugins can depend on 
it sooner than Maven releases. Nothing in Maven itself depends on it.


Cheers,
Brett

--
Brett Porter <[EMAIL PROTECTED]>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Merge it0105 and it0107 to 2.0.x branch

2006-06-11 Thread Brett Porter

jerome lacoste wrote:

Someone might want to create a test case for a branch issue without
looking at the trunk. And it's better to keep itest ids synchronized.


That would be against our development practices we agreed on a while 
back (everything goes through trunk).


The only scenario would be something that only ever works on the branch, 
not the trunk, I'd question the value of such a thing.


- Brett

--
Brett Porter <[EMAIL PROTECTED]>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



ApacheCON europe, anybody there?

2006-06-11 Thread Fabrizio Giustina

Hi,
will anybody from the maven team be at ApacheCon in Dublin? I see that
at least Jason will be there (great!), but nobody signed up for the
Hackathon yet...

just courius, I will be there at least for the first 2 days, and hope
to meet you there... (and just a few days before there is also the
Server Side Symposium in Barcelona, hope to meet people there too)

fabrizio

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [vote] [m1] release xdoc-plugin-1.10

2006-06-11 Thread Dennis Lundberg
Here's some feedback on the new xdoc plugin. I've ran it on a couple of 
Jakarta Commons components, which have various degrees of 
xdoc-complexity. This is what has caught my eye:


- There is no longer a pdf.gif file under /images/. None of the tested 
products has PDF docs generated, so this might be by design. Couldn't 
find anything in the changelog that seemed to fit though.


- The "Downloads" link always shows up in the left hand navbar.

Sometimes it points to an "empty" page saying that the "project has not 
released any version yet". See [beanutils] for an empty example.


Other times there is a non-empty page though, see [fileupload], but on 
that page the download links does not work.


I don't know what triggers this. It seems that [fileupload] has 
versions/version entries in project.xml whereas [beanutils] does not. 
Anyway, I don't think the link should show up in the navbar if there is 
nothing useful for the end-user on the page that it links to.


- On some components [beanutils] the title is missing "Downloads" after 
the project name, on the downloads page.


- On some components [beanutils] the title is missing "Source 
repository" after the project name, on the scm-usage page.


- The "Development process" link in the navbar now goes to a generated 
page, which contains a link, instead of going to the url directly.


- The file rename from cvs-usage to scm-usage will mean some work for 
us, but the change is well documented and it is "the right thing" to do.



--
Dennis Lundberg


Lukas Theussl wrote:

No problem Dennis, I guess I can wait those few more days, too. ;)
I'd certainly appreciate the feedback though.

Cheers,
-Lukas


Dennis Lundberg wrote:

Lukas,

I would really like to try this version out on Jakarta Commons 
components, but I won't have enough time to do it until Sunday.




-
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]



Please update the assembly descriptor docs

2006-06-11 Thread Wendy Smoak

The assembly plugin was released in mid-May, and most of the website
is updated, but not the descriptor:
  http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html

That page is still dated last October, and doesn't show the new
 element.

Thanks,
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Merge it0105 and it0107 to 2.0.x branch

2006-06-11 Thread jerome lacoste

On 6/9/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:

On Fri, 9 Jun 2006, Carlos Sanchez wrote:

Carlos,

> Kenney, could you check it0105 and it0107 and merge its revisions them
> to the 2.0.x branch, or does it not apply?

it0107 is related to MNG-2293 which is only applied to trunk, so that one
doesn't make any sense to commit to the 2.0.x branch.

it0105.. that's a long time ago. Looking at the issue (MRESOURCES-18),
it's intended for 2.2 (although it's fixed in trunk so it'll be in 2.1
too).


BTW, is there some policy to add them to the README.txt and
integrationtests.txt files anyway, to make sure the 'ids' are
allocated?

Something like:

it0107: trunk only

Someone might want to create a test case for a branch issue without
looking at the trunk. And it's better to keep itest ids synchronized.

Jerome

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]