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
I've updated the log to: MWAR-45: add config prop to specify webapp classes should be zipped and placed into WEB-INF/lib/xxx.jar instead of placed in WEB-INF/classes/ Submitted by: Prasad Kashyap - Brett On 12/06/2006 2:06 PM, Brett Porter wrote: [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] -- 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]
Questions on XML plugin
Hi, I have written a plugin, which I currently call maven-xml-plugin. This first version is able to validate XML documents (test phase) or to transform XML documents by applying an XSLT stylesheet (generate-resources). So far development is finished (including a test suite), the exception being docs, which I intend to create in the next days. Now I have two questions: - A question of style: Does it make sense to have these functions in one and the same plugin or do people feel, it would be better to have two plugins (xml-transform and xml-validate)? - What is the suggested target for the plugin? Being an Apache committer, I'd strongly prefer to put it into the Maven Plugins Sandbox, or at a similar location. But I understand, that this is a question of policy, which is not upon me to choose. Thanks, Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r415834 - /maven/plugins/trunk/maven-checkstyle-plugin/src/main/resources/config/maven_checks.xml
Are you changing these because you think these are the best final value, or because the current code isn't close to complying? If it's the former, that's cool; if it's the latter I'd suggest we should keep the checkstyle plugin in the "ideal" configuration, and override it in Maven itself. - Brett On 21/06/2006 8:55 AM, [EMAIL PROTECTED] wrote: Author: carlos Date: Tue Jun 20 15:55:05 2006 New Revision: 415834 URL: http://svn.apache.org/viewvc?rev=415834&view=rev Log: Use more realistic maven rules Modified: maven/plugins/trunk/maven-checkstyle-plugin/src/main/resources/config/maven_checks.xml Modified: maven/plugins/trunk/maven-checkstyle-plugin/src/main/resources/config/maven_checks.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-checkstyle-plugin/src/main/resources/config/maven_checks.xml?rev=415834&r1=415833&r2=415834&view=diff == --- maven/plugins/trunk/maven-checkstyle-plugin/src/main/resources/config/maven_checks.xml (original) +++ maven/plugins/trunk/maven-checkstyle-plugin/src/main/resources/config/maven_checks.xml Tue Jun 20 15:55:05 2006 @@ -62,9 +62,13 @@ - + + + - + + + @@ -134,7 +138,9 @@ - + + + -- 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: svn commit: r415835 - /maven/site/trunk/src/site/resources/checkstyle.xml
Are these linked or configured from anywhere? Any reason not to point directly at the SVN version which will always be up to date? - Brett On 21/06/2006 8:57 AM, [EMAIL PROTECTED] wrote: Author: carlos Date: Tue Jun 20 15:57:13 2006 New Revision: 415835 URL: http://svn.apache.org/viewvc?rev=415835&view=rev Log: Use a better name Added: maven/site/trunk/src/site/resources/checkstyle.xml - copied unchanged from r415833, maven/site/trunk/src/site/resources/maven_checks.xml -- 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: svn commit: r415697 - /maven/archetype/branches/archetype-1.0.x/pom.xml
Jesse, Please revert these commits. Apache snapshots go to the Apache repo, which this pom was already inheriting (if it wasn't working we can figure it out from there). BTW, do you think we should terminate this branch and instead use trunk from now on? I only created this to roll the alpha release while Jason was going to make other changes (so the branch name is misleading). I think we can just delete it now... I haven't done anything new on the branch, have you? - Brett On 21/06/2006 1:12 AM, [EMAIL PROTECTED] wrote: Author: jmcconnell Date: Tue Jun 20 08:12:46 2006 New Revision: 415697 URL: http://svn.apache.org/viewvc?rev=415697&view=rev Log: added updated dav based snapshot distribution management section so I can get an updated archetype out to snapshot Modified: maven/archetype/branches/archetype-1.0.x/pom.xml Modified: maven/archetype/branches/archetype-1.0.x/pom.xml URL: http://svn.apache.org/viewvc/maven/archetype/branches/archetype-1.0.x/pom.xml?rev=415697&r1=415696&r2=415697&view=diff == --- maven/archetype/branches/archetype-1.0.x/pom.xml (original) +++ maven/archetype/branches/archetype-1.0.x/pom.xml Tue Jun 20 08:12:46 2006 @@ -42,6 +42,13 @@ maven-archetypes + + +org.apache.maven.wagon +wagon-webdav +1.0-beta-1 + + @@ -58,4 +65,14 @@ scm:svn:https://svn.apache.org/repos/asf/maven/archetype/branches http://svn.apache.org/viewcvs.cgi/maven/archetype/branches + + + maven-snapshots + Maven Central Development Repository + dav:https://dav.codehaus.org/snapshots.repository/mojo/ + +false + + + -- 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: [vote] Second attempt: Release maven-deploy-plugin 2.2.1
plus one On 21/06/2006 1:06 AM, John Casey wrote: Hi everyone. I just wanted to reopen this vote to see if we can release a bugfix version of the deploy plugin. This version doesn't have any new features, but does fix two critical ones found when using the deploy:deploy-file mojo: * POM and artifact build numbers are out of sync when using -DpomFile=... * Repository layout is not configurable For a full changelog of this release, see: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11131&fixfor=12257 I've taken a cursory look at the plugin documentation, and it looks pretty good. There is an open issue to review this documentation, so any gaps should be addressed in the next day or two. The latest snapshot in the ASF snapshot repository should still be valid for this vote; I'll paste the timestamp/buildnumber for that snapshot as a follow-up email to this one. Let's give it another 72h. Please test the plugin before voting, if you can. +1/+0/-1 Here's my +1. Thanks, John -- 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: apply MNG-2293 to maven-2.0.x?
On 20/06/2006 10:27 PM, jerome lacoste wrote: On 6/10/06, Brett Porter <[EMAIL PROTECTED]> wrote: +1, but considering it an exception to the rule, not a change to the rule. I'd rather we were doing .x releases every 6 months instead. +1: 2 -1: 0 Is that sufficient? Kenney makes 3, but that's irrelevant. One +1 is enough to do it, one -1 is enough to pull it back out (though in both cases it is healthy to discuss it first if you are unsure :) If so, who's responsible to apply this change onto the branch ? I'll leave that to Kenney as the original committer. Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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: [vote] Second attempt: Release maven-deploy-plugin 2.2.1
I've set the Fix For version for MDEPLOY-23. -john On 6/20/06, jerome lacoste <[EMAIL PROTECTED]> wrote: On 6/20/06, John Casey <[EMAIL PROTECTED]> wrote: > Hi everyone. > > I just wanted to reopen this vote to see if we can release a bugfix version > of the deploy plugin. This version doesn't have any new features, but does > fix two critical ones found when using the deploy:deploy-file mojo: > > * POM and artifact build numbers are out of sync when using -DpomFile=... > * Repository layout is not configurable > > For a full changelog of this release, see: > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11131&fixfor=12257 I wonder if http://jira.codehaus.org/browse/MDEPLOY-23 is not missing from the list of fixes. It was reported against 2.2 and seems to have been fixed in the same period. (Note that's the only issue marked Fixed, reported against 2.2 and not marked as fixed in 2.3 or 2.2.1). > I've taken a cursory look at the plugin documentation, and it looks pretty > good. There is an open issue to review this documentation, so any gaps > should be addressed in the next day or two. > > The latest snapshot in the ASF snapshot repository should still be valid for > this vote; I'll paste the timestamp/buildnumber for that snapshot as a > follow-up email to this one. > > Let's give it another 72h. Please test the plugin before voting, if you can. > > +1/+0/-1 > > Here's my +1. Haven't tested the latest snapshot, but I did test some of the earlier ones in the serie. :) Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Second attempt: Release maven-deploy-plugin 2.2.1
+1 Fabrice On 6/20/06, John Casey <[EMAIL PROTECTED]> wrote: Hi everyone. I just wanted to reopen this vote to see if we can release a bugfix version of the deploy plugin. This version doesn't have any new features, but does fix two critical ones found when using the deploy:deploy-file mojo: * POM and artifact build numbers are out of sync when using -DpomFile=... * Repository layout is not configurable For a full changelog of this release, see: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11131&fixfor=12257 I've taken a cursory look at the plugin documentation, and it looks pretty good. There is an open issue to review this documentation, so any gaps should be addressed in the next day or two. The latest snapshot in the ASF snapshot repository should still be valid for this vote; I'll paste the timestamp/buildnumber for that snapshot as a follow-up email to this one. Let's give it another 72h. Please test the plugin before voting, if you can. +1/+0/-1 Here's my +1. Thanks, John
Re: [vote] Second attempt: Release maven-deploy-plugin 2.2.1
On 6/20/06, John Casey <[EMAIL PROTECTED]> wrote: Hi everyone. I just wanted to reopen this vote to see if we can release a bugfix version of the deploy plugin. This version doesn't have any new features, but does fix two critical ones found when using the deploy:deploy-file mojo: * POM and artifact build numbers are out of sync when using -DpomFile=... * Repository layout is not configurable For a full changelog of this release, see: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11131&fixfor=12257 I wonder if http://jira.codehaus.org/browse/MDEPLOY-23 is not missing from the list of fixes. It was reported against 2.2 and seems to have been fixed in the same period. (Note that's the only issue marked Fixed, reported against 2.2 and not marked as fixed in 2.3 or 2.2.1). I've taken a cursory look at the plugin documentation, and it looks pretty good. There is an open issue to review this documentation, so any gaps should be addressed in the next day or two. The latest snapshot in the ASF snapshot repository should still be valid for this vote; I'll paste the timestamp/buildnumber for that snapshot as a follow-up email to this one. Let's give it another 72h. Please test the plugin before voting, if you can. +1/+0/-1 Here's my +1. Haven't tested the latest snapshot, but I did test some of the earlier ones in the serie. :) Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Second attempt: Release maven-deploy-plugin 2.2.1
John Casey wrote: Hi everyone. I just wanted to reopen this vote to see if we can release a bugfix version of the deploy plugin. This version doesn't have any new features, but does fix two critical ones found when using the deploy:deploy-file mojo: * POM and artifact build numbers are out of sync when using -DpomFile=... * Repository layout is not configurable For a full changelog of this release, see: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11131&fixfor=12257 I've taken a cursory look at the plugin documentation, and it looks pretty good. There is an open issue to review this documentation, so any gaps should be addressed in the next day or two. The latest snapshot in the ASF snapshot repository should still be valid for this vote; I'll paste the timestamp/buildnumber for that snapshot as a follow-up email to this one. Let's give it another 72h. Please test the plugin before voting, if you can. +1, no time to test :( -- Trygve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Second attempt: Release maven-deploy-plugin 2.2.1
+1 Emmanuel John Casey a écrit : Hi everyone. I just wanted to reopen this vote to see if we can release a bugfix version of the deploy plugin. This version doesn't have any new features, but does fix two critical ones found when using the deploy:deploy-file mojo: * POM and artifact build numbers are out of sync when using -DpomFile=... * Repository layout is not configurable For a full changelog of this release, see: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11131&fixfor=12257 I've taken a cursory look at the plugin documentation, and it looks pretty good. There is an open issue to review this documentation, so any gaps should be addressed in the next day or two. The latest snapshot in the ASF snapshot repository should still be valid for this vote; I'll paste the timestamp/buildnumber for that snapshot as a follow-up email to this one. Let's give it another 72h. Please test the plugin before voting, if you can. +1/+0/-1 Here's my +1. Thanks, John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[vote] Second attempt: Release maven-deploy-plugin 2.2.1
Hi everyone. I just wanted to reopen this vote to see if we can release a bugfix version of the deploy plugin. This version doesn't have any new features, but does fix two critical ones found when using the deploy:deploy-file mojo: * POM and artifact build numbers are out of sync when using -DpomFile=... * Repository layout is not configurable For a full changelog of this release, see: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11131&fixfor=12257 I've taken a cursory look at the plugin documentation, and it looks pretty good. There is an open issue to review this documentation, so any gaps should be addressed in the next day or two. The latest snapshot in the ASF snapshot repository should still be valid for this vote; I'll paste the timestamp/buildnumber for that snapshot as a follow-up email to this one. Let's give it another 72h. Please test the plugin before voting, if you can. +1/+0/-1 Here's my +1. Thanks, John
Re: Docs: remaining questions
I'm not sure if we're talking about the same reports section. IMO, the project-info links on the landing page (see http://maven.apache.org/jxr.htmlfor example) don't help anything. If we want to have a list of contributors or information about the mailing lists, then maybe we should: 1. clean up those reports, and pare down the ones (like JXR) that have no content on the main page...then, maybe make them more visible in the navigation, rather than burying them two clicks down. Also, pages like http://maven.apache.org/integration.html seem a little sparse somehow...I'm not sure if we have enough to say about Maven's CI testbed to warrant a whole page. IMO, it could be easier for new users to digest this information... 2. (my preference) Digest the information contained under the Project Documentation nav header into a couple of easy-to-read pages that have a good balance of information vs. white space, and display these pages more prominently in the navigation. Also, I want to point out that these reports don't address all of Maven; they only address the site project, IIUC. This is misleading, particularly if we're publishing it on the site's main page. As far as rendering wiki content: I see what you mean now, and I agree. -j On 6/19/06, Brett Porter <[EMAIL PROTECTED]> wrote: On 20/06/2006 7:19 AM, John Casey wrote: >> 1) should we drop the standard reports from the maven site? > > > I never was really pushing to drop reports altogether; it just didn't > really > make sense to me to have them on the main site, in addition to the > individual reference pages. IMO, until we can aggregate all of those > reports > for the entirety of Maven, it's confusing what they represent. Also, it > clutters up the main site for users who might not have any use for that > information. When I say standard information, I mean standard - just project-info-reports (mailing list, etc). Is that what you mean? There aren't others on the site. > The only drawbacks I > can > see here are in keeping the wiki information up to date with new releases, > and navigational consistency between wiki and the main site. > > I really don't see much value in rendering the wiki content to static > pages, > particularly when we'll have to implement in Doxia the confluence macro-set > we'll need to represent a technical discussion...things like the code > macro. The reason to render it into the site is for consistency (navigation and appearance), and speed. There shouldn't be any bottleneck as we can run this automatically every hour or something. Other sites are already doing this: http://incubator.apache.org/activemq/ - 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: apply MNG-2293 to maven-2.0.x?
On 6/10/06, Brett Porter <[EMAIL PROTECTED]> wrote: +1, but considering it an exception to the rule, not a change to the rule. I'd rather we were doing .x releases every 6 months instead. +1: 2 -1: 0 Is that sufficient? If so, who's responsible to apply this change onto the branch ? Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fw: [plexus-dev] Plexus Website (update)
Hi again, A quick update to let everyone know that we have posted some updates to Plexus website and would like to get some feedback on them. Please note that a few pages are still in the process of being updated. The website is accessible at: http://plexus.codehaus.org/index.html We appreciate all the feedback we can get to help us align the site content best to user expectations. Cheers, Rahul - Original Message - From: "Rinku" <[EMAIL PROTECTED]> To: "Maven Developers List" Sent: Thursday, June 15, 2006 7:29 PM Subject: Re: Fw: [plexus-dev] Plexus Website Yep, I am on that task to get them organized and published. Cheers, Rahul - Original Message - From: "Brett Porter" <[EMAIL PROTECTED]> To: "Maven Developers List" Sent: Thursday, June 15, 2006 6:09 PM Subject: Re: Fw: [plexus-dev] Plexus Website That's a good idea too :) I was actually thinking of taking the ideas from John's thread on the Maven documentation and applying the same principles, but it'd be good to hear what Maven plugin people think of the plexus docs. Perhaps best to get through the current round of polishing them up and actually publishing them along with the existing todo list before getting too much feedback that says "there's nothing there" :) - Brett Rinku wrote: Greetings everyone, We are keen to gather inputs for Plexus documentation/website from users on this list. Please see the attached emails below for a heads up. Ideas and suggestions are welcome; contributions are even better :-) Look forward to hear... cheers, Rahul - Original Message - From: "Brett Porter" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 15, 2006 5:22 PM Subject: Re: [plexus-dev] Plexus Website Rinku wrote: Greetings, There's been a growing interest on IRC lately in Plexus and I quickly wanted to touch base on Plexus website and documentation: 1) Is anyone working on the website content to move from current Confluence base to APT based? If not, I am happy to pick this activity up. you are :) Everything in Confluence is in APT (most of it needs editing). I deleted all the Confluence content as it was outdated and/or needed significant editing. 2) Does any one have any thoughts, ideas that they would like to share or like to see included in the website? I like the trails approach. Let's just feed off the discussion on [EMAIL PROTECTED] for further ideas. There's a doc in SVN about "things that need to be documented too". - Brett -- Brett Porter <[EMAIL PROTECTED]> Apache Maven - http://maven.apache.org/ Better Builds with Maven - http://library.mergere.com/ - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
