Re: JDK 17 related plugin releases

Acknowlegded, but ASM 9.1 already supports Java 17, which is our main target. Robert -- Origineel bericht -- Van: "Gary Gregory" Aan: "Maven Developers List" ; mthmuld...@apache.org Verzonden: 18-8-2021 13:34:05 Onderwerp: Re: JDK 17 related plugin releases N

Re: JDK 17 related plugin releases

Note that the current version of ASM is 9.2. Gary On Wed, Aug 18, 2021, 03:49 Maarten Mulders wrote: > Well, that was a short ride - the latest release of the > maven-plugin-tools is already up-to-date, as it uses ASM 9.1. > > Same goes for the maven-dependency-plugin; latest release is also on

Re: JDK 17 related plugin releases

Well, that was a short ride - the latest release of the maven-plugin-tools is already up-to-date, as it uses ASM 9.1. Same goes for the maven-dependency-plugin; latest release is also on ASM 9.1 From the "Required" list on the aforementioned Wiki page, that leaves us with the maven-shade-plugi

Re: JDK 17 related plugin releases

I'll take the maven-plugin-plugin for a ride. Maarten On 17/08/2021 19:28, Robert Scholte wrote: With JDK 17 appearing soon we should at least release those plugins that depend on ASM.[1] Even though optional, I'll release both the maven-compiler-plugin and maven-javadoc-plugin too. I could

JDK 17 related plugin releases

With JDK 17 appearing soon we should at least release those plugins that depend on ASM.[1]  Even though optional, I'll release both the maven-compiler-plugin and maven-javadoc-plugin too. I could use some help with the other plugins too, including verifying if there are PRs worth adding and the

Re: Roadmap Proposal Plugin Releases

On Mon, Feb 2, 2015 at 12:42 PM, Karl Heinz Marbaise wrote: > Hi, > > after some discussions at FOSDEM with Hervé, Kristian and Robert in Brussels > i will summarize some ideas we would like to share here: > > Make a final release of all plugins with minium Maven 2.2.1 (prerequisites) > and Java 1

Re: Roadmap Proposal Plugin Releases

I'll poke around. On Wed, Feb 4, 2015 at 4:46 PM, Anders Hammar wrote: > ARCHETYPE-431 fixed. > However, when building I see a bunch of Maven "Build Failure" in the output > from tests. Don't know if that's expected, but it looks weird. The tests > pass though, but that could be wrong. Didn't hav

Re: Roadmap Proposal Plugin Releases

ARCHETYPE-431 fixed. However, when building I see a bunch of Maven "Build Failure" in the output from tests. Don't know if that's expected, but it looks weird. The tests pass though, but that could be wrong. Didn't have time to look into that. Also, there are some warnings in the build that could b

Re: Roadmap Proposal Plugin Releases

I'll have a look. /Anders (mobile) Den 4 feb 2015 14:03 skrev "Benson Margulies" : > Gents, are you willing to do it and I'll just be RM? > > > On Wed, Feb 4, 2015 at 6:33 AM, Arnaud Héritier > wrote: > > +1 > > > > On Wed, Feb 4, 2015 at 10:18 AM, Anders Hammar > wrote: > > > >> > Ouch that's

Re: Roadmap Proposal Plugin Releases

Gents, are you willing to do it and I'll just be RM? On Wed, Feb 4, 2015 at 6:33 AM, Arnaud Héritier wrote: > +1 > > On Wed, Feb 4, 2015 at 10:18 AM, Anders Hammar wrote: > >> > Ouch that's an old one :-) >> > >> > Yes I was interested to have a 2.3 release but we failed to find the >> > motiva

Re: Roadmap Proposal Plugin Releases

+1 On Wed, Feb 4, 2015 at 10:18 AM, Anders Hammar wrote: > > Ouch that's an old one :-) > > > > Yes I was interested to have a 2.3 release but we failed to find the > > motivation/time to close 431 > > > Yes, I hardly even remember this one. The code seems to be fixed except the > unit test. I'd

Re: Roadmap Proposal Plugin Releases

> Ouch that's an old one :-) > > Yes I was interested to have a 2.3 release but we failed to find the > motivation/time to close 431 Yes, I hardly even remember this one. The code seems to be fixed except the unit test. I'd say we should go for the easiest way so that we could close this ticket.

Re: Roadmap Proposal Plugin Releases

Ouch that's an old one :-) Yes I was interested to have a 2.3 release but we failed to find the motivation/time to close 431 On Wed, Feb 4, 2015 at 4:12 AM, Hervé BOUTEMY wrote: > I didn't work on this one for a long time > > Anders and Arnaud seem to have problems to decide how to fix and clos

Re: Roadmap Proposal Plugin Releases

I didn't work on this one for a long time Anders and Arnaud seem to have problems to decide how to fix and close http://jira.codehaus.org/browse/ARCHETYPE-431 Regards, Hervé Le mardi 3 février 2015 21:50:00 Benson Margulies a écrit : > So, I've committed changes to the archetype system that I

Re: Roadmap Proposal Plugin Releases

So, I've committed changes to the archetype system that I believe correspond to the 2.2.1 level. What else wants to happen before a release? On Tue, Feb 3, 2015 at 9:13 PM, Hervé BOUTEMY wrote: > Le lundi 2 février 2015 12:42:02 Karl Heinz Marbaise a écrit : >> Hi, >> >> after some discussions at

Re: Roadmap Proposal Plugin Releases

Le lundi 2 février 2015 12:42:02 Karl Heinz Marbaise a écrit : > Hi, > > after some discussions at FOSDEM with Hervé, Kristian and Robert in > Brussels i will summarize some ideas we would like to share here: > > Make a final release of all plugins with minium Maven 2.2.1 > (prerequisites) and Ja

Re: Roadmap Proposal Plugin Releases

Sounds good to me. I especially like the Maven 3.0 (not 3.0.5) requirement. /Anders On Mon, Feb 2, 2015 at 12:42 PM, Karl Heinz Marbaise wrote: > Hi, > > after some discussions at FOSDEM with Hervé, Kristian and Robert in > Brussels i will summarize some ideas we would like to share here: > > M

Roadmap Proposal Plugin Releases

Hi, after some discussions at FOSDEM with Hervé, Kristian and Robert in Brussels i will summarize some ideas we would like to share here: Make a final release of all plugins with minium Maven 2.2.1 (prerequisites) and Java 1.5 The current state of this approach can be watched on the dist-to

Re: next plugin releases toward Maven 3.1-A1

ok, maven-site-plugin 3.3 vote just started tomorrow, I will start maven-project-info-reports-plugin and maven-dependency- plugin given the 72h vote duration, monday or tuesday should be ok to include the plugin releases into the next core release. Regards, Hervé Le jeudi 9 mai 2013 10:07:56

Re: next plugin releases toward Maven 3.1-A1

I'm planning to cut a release on Monday. I have a a refactoring of the CLI that I will finish over the weekend, primary to help exposing JSR330 bindings from startup so that the core can start down the path of switching the Plexus components to proper JSR330 components. If no one gets around to

Re: next plugin releases toward Maven 3.1-A1

great thank you Hervé Le lundi 6 mai 2013 17:52:00 Kristian Rosenvold a écrit : > I can do the shade release, I'll skim through the issues and push it in a > few days. > > Kristian > > > 2013/5/6 Hervé BOUTEMY > > > To have Maven 3.1-A1 compatible plugins, we now need to release: > > - maven

Re: next plugin releases toward Maven 3.1-A1

I can do the shade release, I'll skim through the issues and push it in a few days. Kristian 2013/5/6 Hervé BOUTEMY > To have Maven 3.1-A1 compatible plugins, we now need to release: > - maven-site-plugin 3.3 > - maven dependency-plugin 2.8 > - maven-shade-plugin 2.1 > - maven-project-info-rep

next plugin releases toward Maven 3.1-A1

To have Maven 3.1-A1 compatible plugins, we now need to release: - maven-site-plugin 3.3 - maven dependency-plugin 2.8 - maven-shade-plugin 2.1 - maven-project-info-reports-plugin 2.7 Other projects may have plugins to release too, like Tycho. I still have some work to do on maven-site-plugin bef

Re: Getting Maven component and plugin releases to /dist -- space

On Sun, 23 Dec 2012, Benson Margulies wrote: Date: Sun, 23 Dec 2012 14:46:57 +0100 From: Benson Margulies To: "infrastruct...@apache.org" , Maven Developers List Subject: Re: Getting Maven component and plugin releases to /dist -- space As far as I can determine, there shoul

Re: Getting Maven component and plugin releases to /dist -- space

On Sun, 23 Dec 2012, Benson Margulies wrote: Date: Sun, 23 Dec 2012 15:26:18 +0100 From: Benson Margulies To: Henk P. Penning Cc: Maven Developers List , "infrastruct...@apache.org" Subject: Re: Getting Maven component and plugin releases to /dist -- space Hi Benson,

Re: Getting Maven component and plugin releases to /dist -- space

pache.org" >> >> Subject: Re: Getting Maven component and plugin releases to /dist -- space >> > > Hi Benson, > > excellent. > > As far as I can see, everything can go directly into > "archive.a.o/dist/maven/". > > The only point of

Re: Getting Maven component and plugin releases to /dist -- space

Henk, I'm sorry that I'm effectively top-posting; for some reason gmail doesn't want to set up interlinear commentary on your message. If I miss something, please let me know. If you look in https://svn.apache.org/repos/asf/maven/project/tools/scrape-nexus-releases, you will find two files, inve

Re: Getting Maven component and plugin releases to /dist -- space

ssage- >>>> From: Benson Margulies [mailto:bimargul...@gmail.com] >>>> Sent: Sunday, 23 December 2012 8:31 AM >>>> To: Maven Developers List >>>> Cc: infrastruct...@apache.org >>>> Subject: Getting Maven component and plugin releases to /

Re: Getting Maven component and plugin releases to /dist -- space

ald > wrote: >> >> >>> -Original Message- >>> From: Benson Margulies [mailto:bimargul...@gmail.com] >>> Sent: Sunday, 23 December 2012 8:31 AM >>> To: Maven Developers List >>> Cc: infrastruct...@apache.org >>> Subject: Get

Re: Getting Maven component and plugin releases to /dist -- space

On Sat, Dec 22, 2012 at 5:11 PM, Gavin McDonald wrote: > > >> -Original Message- >> From: Benson Margulies [mailto:bimargul...@gmail.com] >> Sent: Sunday, 23 December 2012 8:31 AM >> To: Maven Developers List >> Cc: infrastruct...@apache.org >> S

Re: Getting Maven component and plugin releases to /dist -- space

pache.org > > Subject: Getting Maven component and plugin releases to /dist -- space > > > > https://svn.apache.org/repos/asf/maven/project/tools/scrape-nexus- > > releases/inventory.sizes > > > > contains my attempt to inventory all the Maven releases that are on

RE: Getting Maven component and plugin releases to /dist -- space

> -Original Message- > From: Benson Margulies [mailto:bimargul...@gmail.com] > Sent: Sunday, 23 December 2012 8:31 AM > To: Maven Developers List > Cc: infrastruct...@apache.org > Subject: Getting Maven component and plugin releases to /dist -- space > > https://

Re: Getting Maven component and plugin releases to /dist -- space

On 22/12/2012 22:00, Benson Margulies wrote: > https://svn.apache.org/repos/asf/maven/project/tools/scrape-nexus-releases/inventory.sizes > > contains my attempt to inventory all the Maven releases that are on > repository.apache.org but are not on /dist. > > The bottom line, literally, is 862217

Getting Maven component and plugin releases to /dist -- space

https://svn.apache.org/repos/asf/maven/project/tools/scrape-nexus-releases/inventory.sizes contains my attempt to inventory all the Maven releases that are on repository.apache.org but are not on /dist. The bottom line, literally, is 86221717 bytes -- not counting the detached signature files. I

Re: Pending plugin releases

I meant the Y in x.y.z, not the x;) Den 10. mai 2010 kl. 10.32 skrev Stephane Nicoll : > Hi, > > What does full point upgrade means exactly? > > S. > > --- > [image: Linkedin] [image: > Twitter] > > > On Mon, May 10, 2010 at 9:01 AM,

Re: Pending plugin releases

Hi, What does full point upgrade means exactly? S. --- [image: Linkedin] [image: Twitter] On Mon, May 10, 2010 at 9:01 AM, Kristian Rosenvold < kristian.rosenv...@gmail.com> wrote: > I'm going to be releasing .1 upgrades to add @

Pending plugin releases

I'm going to be releasing .1 upgrades to add @threadSafe to the following mojos this week/next week: maven-compiler-plugin maven-install-plugin maven-source-plugin maven-resources-plugin maven-surefire-plugin maven-jar-plugin maven-war-plugin maven-ear-plugin (will be full point upgrade) maven-a

Re: Using a downloader to test plugin releases

The only benefit of the profile is that the plugin is downloaded and installed as Maven does normally. Updating metadata accordingly and all that jazz. On 27-Aug-08, at 1:14 PM, Dan Fabulich wrote: Jason van Zyl wrote: The method that we've pushed in a couple releases is a simple profile

Re: Using a downloader to test plugin releases

On Wed, Aug 27, 2008 at 12:02 PM, Dan Fabulich <[EMAIL PROTECTED]> wrote: > I thought it would be cool to have a downloader plugin that let you do this: > > mvn downloader:get >-Dartifact=org.apache.maven.plugins:maven-scm-plugin:1.1 >-DrepoUrl=http://people.apache.org/~olamy/staging-repo

Re: Using a downloader to test plugin releases

Jason van Zyl wrote: The method that we've pushed in a couple releases is a simple profile which lists the staging repository where a test plugin has been deployed. The profile can be generated with the release and it's a separate file, so you just erase it when you're done with it. Think the

Re: Using a downloader to test plugin releases

The method that we've pushed in a couple releases is a simple profile which lists the staging repository where a test plugin has been deployed. The profile can be generated with the release and it's a separate file, so you just erase it when you're done with it. Think the profile might be a

Using a downloader to test plugin releases

I've always found it to be a hassle to test plugins that don't need to be wired up in POM files, e.g. the archetype, dependency, scm plugins. I find that to test them I have to create a dummy POM file with a section, as described in our guide to testing staged releases. http://maven.apach

Re: A report on the status of our plugin releases

Jason van Zyl wrote: On 24 Jul 07, at 10:26 AM 24 Jul 07, Dennis Lundberg wrote: Now it is (finally) checked in: http://svn.apache.org/repos/asf/maven/sandbox/trunk/shared/reports/all-plugin-versions.vm Coolio, you mind if I wire that up on the central machine to a cron job and publish

Re: A report on the status of our plugin releases

On 24 Jul 07, at 10:26 AM 24 Jul 07, Dennis Lundberg wrote: Now it is (finally) checked in: http://svn.apache.org/repos/asf/maven/sandbox/trunk/shared/reports/ all-plugin-versions.vm Coolio, you mind if I wire that up on the central machine to a cron job and publish it? Henri Yandell

Re: A report on the status of our plugin releases

Now it is (finally) checked in: http://svn.apache.org/repos/asf/maven/sandbox/trunk/shared/reports/all-plugin-versions.vm Henri Yandell wrote: They look good :) I hope you were able to copy from the commons one[1] rather than having to go from scratch. Are your swizzle scripts checked in yet? F

Re: A report on the status of our plugin releases

On 6 Jun 07, at 4:25 PM 6 Jun 07, Dennis Lundberg wrote: Hi I've spent the day learning the ins and outs of swizzle. It's really an awesome tool for aggregating data from JIRA. There are some hoops you need to jump through to get what you want, but the results are exciting. David Ble

Re: A report on the status of our plugin releases

For the Hibernate 2.X report, that project was initially built for the hibernate 2 plugin, which at this moment I don't know if it's still a live project. The hibernate 3 plugin still part of MOJO so all bug tracking and release it's done inside MOJO Regards Johann Reyes On 6/6/07, Dennis Lundb

Re: A report on the status of our plugin releases

They look good :) I hope you were able to copy from the commons one[1] rather than having to go from scratch. Are your swizzle scripts checked in yet? Fun things to look at. Hen [1]http://svn.apache.org/repos/asf/jakarta/commons/proper/commons-nightly/trunk/jira-email.vm and http://people.apach

A report on the status of our plugin releases

Hi I've spent the day learning the ins and outs of swizzle. It's really an awesome tool for aggregating data from JIRA. There are some hoops you need to jump through to get what you want, but the results are exciting. My incentive to do this has been trying to get a grip on the status of our

[Result] [vote] [m1] plugin releases

This vote passed with 3 binding (Arnaud, Jason, Lukas) and one non-binding (Jeff) +1s. Thanks to those who voted, I'll do the releases soon. -Lukas Lukas Theussl wrote: Hi, These are the plugins that do not need the updated maven-model, so I'd like to release them already: maven-clover-p

Re: [vote] [m1] plugin releases

+1 across the board On 22 Mar 07, at 8:37 AM 22 Mar 07, Lukas Theussl wrote: Hi, These are the plugins that do not need the updated maven-model, so I'd like to release them already: maven-clover-plugin-1.11.2 maven-jdiff-plugin-1.5.1 maven-pdf-plugin-2.5.1 maven-pmd-plugin-1.10 maven-scm-p

Re: [vote] [m1] plugin releases

+1 for all Arnaud On 22/03/07, Lukas Theussl <[EMAIL PROTECTED]> wrote: The clover plugin had no changes at all (version 1.11.1 was only released last November) apart from the clover license being updated, which had expired a few weeks ago. -Lukas Jeff Jensen wrote: > +1 for all but clover

Re: [vote] [m1] plugin releases

The clover plugin had no changes at all (version 1.11.1 was only released last November) apart from the clover license being updated, which had expired a few weeks ago. -Lukas Jeff Jensen wrote: +1 for all but clover (never used it!). -

RE: [vote] [m1] plugin releases

+1 for all but clover (never used it!). -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Thursday, March 22, 2007 7:38 AM To: Maven Developers List Subject: [vote] [m1] plugin releases Hi, These are the plugins that do not need the updated maven-model, so I&#

[vote] [m1] plugin releases

Hi, These are the plugins that do not need the updated maven-model, so I'd like to release them already: maven-clover-plugin-1.11.2 maven-jdiff-plugin-1.5.1 maven-pdf-plugin-2.5.1 maven-pmd-plugin-1.10 maven-scm-plugin-1.6.1 maven-site-plugin-1.7.1 Changes are mostly minor, have a look at th

Re: Plugin Releases

There's one fix I need to get into the Perforce provider before it goes into a new release plugin. I'll commit to getting it done this weekend if you'll hold off on building the beta-4 snapshot. http://jira.codehaus.org/browse/SCM-229 mike On 11/30/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrot

Re: Plugin Releases

On 30 Nov 06, at 11:39 AM 30 Nov 06, Dan Tran wrote: I would like the test replease plugin against maven-scm-1.0-beta-4-SNAPSHOTfirst. I haven't sent out the vote for the release plugin because I haven't actually started working on it, so plenty of time. Test away against trunk. Jason.

Re: Plugin Releases

I would like the test replease plugin against maven-scm-1.0-beta-4-SNAPSHOTfirst. To help with the testing, we need to: - release maven-plugins's pom.xml version 4 - deploy maven-scm-beta-4-SNAPSHOT - deploy maven-release-plugin-beta-5-SNASHOT which will be built with the new maven-scm

Re: Plugin Releases

We need to release maven-scm beta-4 before to release release plugin Emmanuel Jason van Zyl a écrit : Now that thing are working I suggest we start new threads for all the votes. Jason. On 29 Nov 06, at 7:29 PM 29 Nov 06, Jason van Zyl wrote: Hi, The license insertion in to JAR, Source, a

Re: Plugin Releases

Now that thing are working I suggest we start new threads for all the votes. Jason. On 29 Nov 06, at 7:29 PM 29 Nov 06, Jason van Zyl wrote: Hi, The license insertion in to JAR, Source, and JavaDoc bundles is working fine now and I have updated the headers to their correct form for all

Plugin Releases

Hi, The license insertion in to JAR, Source, and JavaDoc bundles is working fine now and I have updated the headers to their correct form for all resoures for the following Plugins: Dependency Checkstyle JavaDoc PMD RAR RAR Release Remote Resources Source Surefire WAR Anyone who has been w

Re: plugin releases

I thought so too, and tried turning off the cache in {jiraissue...}. But the results were the same. -- Dennis Lundberg Brett Porter wrote: I'm working with Jeff from Atlassian to figure it out. Possibly some bad caching. On 07/09/2006, at 8:25 AM, Dennis Lundberg wrote: Thanks for the link

Re: plugin releases

I'm working with Jeff from Atlassian to figure it out. Possibly some bad caching. On 07/09/2006, at 8:25 AM, Dennis Lundberg wrote: Thanks for the link. I've put together a first draft here: http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Status Unfortunately it seems that the numbers r

Re: plugin releases

Thanks for the link. I've put together a first draft here: http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Status Unfortunately it seems that the numbers returned by the macros are not correct. Try the example links that I have put in the page for the changelog and changes plugins. Compare

Re: plugin releases

On 1 Sep 06, at 11:48 AM 1 Sep 06, Joakim Erdfelt wrote: Jason van Zyl wrote: On 1 Sep 06, at 4:10 AM 1 Sep 06, Stephane Nicoll wrote: Hi, For the record here's the doc of the Jira issues macro: http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro I'm not sure there is enough in

Re: plugin releases

On 1 Sep 06, at 11:33 AM 1 Sep 06, Joakim Erdfelt wrote: Jason van Zyl wrote: On 1 Sep 06, at 4:10 AM 1 Sep 06, Stephane Nicoll wrote: Hi, For the record here's the doc of the Jira issues macro: http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro I'm not sure there is enough in

Re: plugin releases

Jason van Zyl wrote: I'm not sure there is enough in the macros to do what we need. I asked David Blevins to help me use Swizzle to create a list of all the outstanding issues for plugins that have votes. I would like to sum the votes in each plugin project and then sort them in ranked order.

Re: plugin releases

Jason van Zyl wrote: > On 1 Sep 06, at 4:10 AM 1 Sep 06, Stephane Nicoll wrote: > >> Hi, >> >> For the record here's the doc of the Jira issues macro: >> http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro >> > > I'm not sure there is enough in the macros to do what we need. I asked > Dav

Re: plugin releases

Jason van Zyl wrote: > On 1 Sep 06, at 4:10 AM 1 Sep 06, Stephane Nicoll wrote: > >> Hi, >> >> For the record here's the doc of the Jira issues macro: >> http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro >> > > I'm not sure there is enough in the macros to do what we need. I asked > Dav

Re: plugin releases

On 1 Sep 06, at 4:10 AM 1 Sep 06, Stephane Nicoll wrote: Hi, For the record here's the doc of the Jira issues macro: http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro I'm not sure there is enough in the macros to do what we need. I asked David Blevins to help me use Swizzle to

Re: plugin releases

Hi, For the record here's the doc of the Jira issues macro: http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro Cheers, Stéphane On 9/1/06, Brett Porter <[EMAIL PROTECTED]> wrote: On 01/09/2006, at 6:55 AM, Dennis Lundberg wrote: > > I'll have some time this weekend, so unless you b

Re: plugin releases

On 01/09/2006, at 6:55 AM, Dennis Lundberg wrote: I'll have some time this weekend, so unless you beat me to it I'll do it then. Assuming that the "JIRA queries in Confluence" feature has some documentation I should be fine. Yep, if you edit a confluence page and go to the full notation g

Re: plugin releases

Brett Porter wrote: On 31/08/2006, at 8:52 AM, Dennis Lundberg wrote: Count me in. I was about to start something similar, albeit on a smaller scale. How about we start out with a wiki page in Confluence and look at automation later, once we get the feel for what data we need? We coul

Re: plugin releases

On 31/08/2006, at 8:52 AM, Dennis Lundberg wrote: Yep, the glue between maven core and the plugins should be the plugins-api. That probably won't happen, but more decoupling is definitely good. Well, you'll always need project objects and artifacts though their use should be minimised.

Re: plugin releases

On 8/30/06, Brett Porter <[EMAIL PROTECTED]> wrote: Good morning, ... More importantly, is anyone willing to help? Particularly if we could grab this data from JIRA and automate it, it would be a lot easier. This is something I could help do. I have written plugins for jira, but not Co

Re: plugin releases

On 30 Aug 06, at 6:36 PM 30 Aug 06, Alan D. Cabrera wrote: Brett Porter wrote: Good morning, So, reading through the discussions on users@ and the one here yesterday, we're getting kicked for not releasing plugins often enough again. Back at the start of the year I started sending out th

Re: plugin releases

> More importantly, is anyone willing to help? Particularly if we could > grab this data from JIRA and automate it, it would be a lot easier. Count me in. I was about to start something similar, albeit on a smaller scale. How about we start out with a wiki page in Confluence and look at automatio

Re: plugin releases

Brett Porter wrote: Good morning, So, reading through the discussions on users@ and the one here yesterday, we're getting kicked for not releasing plugins often enough again. And rightly so :( Back at the start of the year I started sending out the list of plugins to get a report on what's

Re: plugin releases

Brett Porter wrote: Good morning, So, reading through the discussions on users@ and the one here yesterday, we're getting kicked for not releasing plugins often enough again. Back at the start of the year I started sending out the list of plugins to get a report on what's happening with the

plugin releases

Good morning, So, reading through the discussions on users@ and the one here yesterday, we're getting kicked for not releasing plugins often enough again. Back at the start of the year I started sending out the list of plugins to get a report on what's happening with them. That wasn't v

Re: [vote] [m1] plugin releases: eclipse, war

Vote results: +1 for both: Arnaud, Lukas, Stéphane The voting thread is here: http://www.nabble.com/-vote---m1--plugin-releases%3A-eclipse%2C-war-t1782296.html#a4853463 The releases are being performed Cheers, Stéphane On 6/14/06, Lukas Theussl <[EMAIL PROTECTED]> wrote: +1 x2 I s

Re: [vote] [m1] plugin releases: eclipse, war

+1 x2 I suppose that MPWAR-40 and MPWAR-44 can be closed as won't fix now? -Lukas Stephane Nicoll wrote: Hi, I'd like to call a vote to release the maven eclipse plugin 1.11 [1] and the war plugin 1.6.2 [2] (second try!): The staging sites are available at: * eclipse: http://people.apache

Re: [vote] [m1] plugin releases : ant & pdf

The vote passed. I'll release them ASAP. Arnaud On 6/6/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote: +1 s/ On 6/6/06, Lukas Theussl <[EMAIL PROTECTED]> wrote: > Another ping to our fellow pmc's. > > Please! > > -Lukas > > > Arnaud HERITIER wrote: > > I need another vote to release these plu

Re: [vote] [m1] plugin releases: eclipse, war

+1 for both Arnaud On 6/13/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote: Hi, I'd like to call a vote to release the maven eclipse plugin 1.11 [1] and the war plugin 1.6.2 [2] (second try!): The staging sites are available at: * eclipse: http://people.apache.org/~snicoll/maven-stage-site/ma

[vote] [m1] plugin releases: eclipse, war

Hi, I'd like to call a vote to release the maven eclipse plugin 1.11 [1] and the war plugin 1.6.2 [2] (second try!): The staging sites are available at: * eclipse: http://people.apache.org/~snicoll/maven-stage-site/maven-1.x/plugins/eclipse/ * war: http://people.apache.org/~snicoll/maven-stage

Re: [vote] [m1] plugin releases : ant & pdf

+1 s/ On 6/6/06, Lukas Theussl <[EMAIL PROTECTED]> wrote: Another ping to our fellow pmc's. Please! -Lukas Arnaud HERITIER wrote: > I need another vote to release these plugins. > > cheers > > arnaud > > On 5/11/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > >> >> >> >> On 5/9/06, Lukas T

Re: [vote] [m1] plugin releases : ant & pdf

Another ping to our fellow pmc's. Please! -Lukas Arnaud HERITIER wrote: I need another vote to release these plugins. cheers arnaud On 5/11/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: On 5/9/06, Lukas Theussl <[EMAIL PROTECTED] > wrote: > > +1 x2 > > Just some comments on the ant p

Re: [vote] [m1] plugin releases : ant & pdf

I need another vote to release these plugins. cheers arnaud On 5/11/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: On 5/9/06, Lukas Theussl <[EMAIL PROTECTED] > wrote: > > +1 x2 > > Just some comments on the ant plugin: > > * there is a layout problem in the table of the properties page > (

Re: [vote] [m1] plugin releases : ant & pdf

On 5/9/06, Lukas Theussl <[EMAIL PROTECTED] > wrote: +1 x2 Just some comments on the ant plugin: * there is a layout problem in the table of the properties page (maven.ant.excludeTests) Fixed, Thx. * there is an issue with m1.0 compatibility: running maven genapp - ant - ant:execute fails

Re: [vote] [m1] plugin releases : ant & pdf

+1 x2 Just some comments on the ant plugin: * there is a layout problem in the table of the properties page (maven.ant.excludeTests) * there is an issue with m1.0 compatibility: running maven genapp - ant - ant:execute fails on m1.0.2 because junit classes cannot be found. I suppose it's be

[vote] [m1] plugin releases : ant & pdf

Hi, I think the following m1 plugins are ready for a release: [] maven-ant-plugin-1.10 [] maven-pdf-plugin-2.5 For changes in each version, check the jira and changes reports on the stage sites given below. +1, 72h... Cheers, Arnaud http://people.apache.org/~aheritier/maven-stage-site/maven-

[result] [vote] [m1] plugin releases

This vote has passed with 4 binding +1s: Jason, Stephane, Arnaud and myself. Voting thread: http://www.nabble.com/-vote-m1-plugin-releases-t1553467.html#a4220358 Thanks evryone! -Lukas Lukas Theussl wrote: Hi, I think the following m1 plugins are ready for a release: [] maven-jalopy

Re: [vote] [m1] plugin releases

You are right, this is by design. I prefer to have a build fail by default, even if the error is minor, because otherwise I tend to overlook things. The problem with sourceforge is that remote users don't have the right to change the permission for the root site directory (htdocs), so the

Re: [vote] [m1] plugin releases

There is a bug in the plugin caching mechanism in m1.0. Sometimes just running the same goal a second time resolves the problem (or running a fake goal, as Stephane suggests), but the best thing to do is just clearing your cache. However, I don't know exactly under which circumstances this hap

Re: [vote] [m1] plugin releases

Fixed. Thanks for spotting this! -Lukas Dennis Lundberg wrote: Hi Lukas First off, thanks for pushing out new versions of all the Maven 1 plugins! Reading through the changes report for the site plugin I couldn't quite understand one thing. There seems to be an error in the changes report

Re: [vote] [m1] plugin releases

It's me again... After getting the project site built correctly, I then tried to sshdeploy it to SourceForge using the new site-plugin. It didn't go all that well. Having switched back and forth between 1.6.1 and 1.7-SNAPSHOT I have found one thing that's different in 1.7. This might be by desig

Re: [vote] [m1] plugin releases

When you have changed a plugin it's always better to call a fake goal (such as cleanr or something) to make sure the cache is up-to-date. Some plugins have a weird behavior in this case (such as the site/xdoc plugins) Cheers, Stéphane On 5/4/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote: Hello

Re: [vote] [m1] plugin releases

Hello It seems that there was a glitch during the upgrade. I tried a couple of other projects and they all ran fine. So I went back and tried my project again, and it worked. Then I looked back to the beginning of the session and found this snippet right at the start: plugin maven-site-plugin-

Re: [vote] [m1] plugin releases

Hi Dennis, Can you try to clean your plugins cache ? The new site plugin doesn't need a newer release of the xdoc plugin. It seems that maven lost your xdoc plugin 1.9.2. Arnaud On 5/4/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote: Lukas, I tried the site plugin on a SourceForge project I

Re: [vote] [m1] plugin releases

Lukas, I tried the site plugin on a SourceForge project I work on, but the site generation fails. Here's what I did: - maven clean - maven site (all is well) - maven clean - upgrade from maven-site-plugin-1.6.1 to maven-site-plugin-1.7-SNAPSHOT - maven site (ERROR see below) ... xdoc:generate

  1   2   3   >