Re: [maven-compiler-plugin] 02/02: [MCOMPILER-506] Upgrade parent pom to 37 and cleanup pom

slachiewicz pushed a commit to branch MCOMPILER-506 > > > in repository > > > https://gitbox.apache.org/repos/asf/maven-compiler-plugin.git > > > > > > commit ff45fef673b01ff000299f83dec0737c2251bd0c > > > Author: Sylwester Lachiewicz >

Re: [maven-compiler-plugin] 02/02: [MCOMPILER-506] Upgrade parent pom to 37 and cleanup pom

d0c > > Author: Sylwester Lachiewicz > > AuthorDate: Fri Sep 9 00:47:09 2022 +0200 > > > > [MCOMPILER-506] Upgrade parent pom to 37 and cleanup pom > > --- > > pom.xml | 95 > > +++-- > >

Re: [maven-compiler-plugin] 02/02: [MCOMPILER-506] Upgrade parent pom to 37 and cleanup pom

e.org/repos/asf/maven-compiler-plugin.git > > commit ff45fef673b01ff000299f83dec0737c2251bd0c > Author: Sylwester Lachiewicz > AuthorDate: Fri Sep 9 00:47:09 2022 +0200 > > [MCOMPILER-506] Upgrade parent pom to 37 and

[GitHub] [maven-shared-incremental] olamy merged pull request #9: cleanup pom, upgrade some code to modern sugar syntax

olamy merged PR #9: URL: https://github.com/apache/maven-shared-incremental/pull/9 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[GitHub] [maven-shared-incremental] olamy opened a new pull request, #9: cleanup pom, upgrade some code to modern sugar syntax

olamy opened a new pull request, #9: URL: https://github.com/apache/maven-shared-incremental/pull/9 Signed-off-by: Olivier Lamy -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

[GitHub] [maven-gh-actions-shared] slachiewicz merged pull request #20: Cleanup main branch

slachiewicz merged pull request #20: URL: https://github.com/apache/maven-gh-actions-shared/pull/20 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

[GitHub] [maven-gh-actions-shared] slawekjaranowski opened a new pull request #20: Cleanup main branch

slawekjaranowski opened a new pull request #20: URL: https://github.com/apache/maven-gh-actions-shared/pull/20 - shared workflows should be only in v* branches All projects use `v1` https://github.com/search?l=YAML=1=%22apache%2Fmaven-gh-actions-shared%22=Code -- This is an

[GitHub] [maven-site] elharo merged pull request #242: docs: minor cleanup

elharo merged pull request #242: URL: https://github.com/apache/maven-site/pull/242 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[GitHub] [maven-site] elharo opened a new pull request #242: docs: minor cleanup

elharo opened a new pull request #242: URL: https://github.com/apache/maven-site/pull/242 @michael-o omit needless words -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment.

[GitHub] [maven-shared-jar] elharo closed pull request #4: [MSHARED-887] set Maven 3.1.0 as minimum and cleanup dependencies

elharo closed pull request #4: URL: https://github.com/apache/maven-shared-jar/pull/4 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go

[GitHub] [maven-shared-jar] slachiewicz commented on pull request #4: [MSHARED-887] set Maven 3.1.0 as minimum and cleanup dependencies

slachiewicz commented on pull request #4: URL: https://github.com/apache/maven-shared-jar/pull/4#issuecomment-636504356 I use the plexus version that was imported by the Maven 3.1 dependencies (3.1.1 already has a different version). It seems to me that if we use a newer version of Plexus

[GitHub] [maven-shared-jar] elharo commented on pull request #4: [MSHARED-887] set Maven 3.1.0 as minimum and cleanup dependencies

elharo commented on pull request #4: URL: https://github.com/apache/maven-shared-jar/pull/4#issuecomment-636486988 @slachiewicz After looking at that commit, the difference seems to be that this PR imports plexus-containers-default and that one imports org.eclipse.sisu.plexus. I'm

[GitHub] [maven-shared-jar] elharo commented on pull request #4: [MSHARED-905] set Maven 3.1.0 as minimum and cleanup dependencies

elharo commented on pull request #4: URL: https://github.com/apache/maven-shared-jar/pull/4#issuecomment-636474949 That code doesn't seem to be in HEAD? This is an automated message from the Apache Git Service. To respond

[GitHub] [maven-shared-jar] slachiewicz commented on pull request #4: [MSHARED-905] set Maven 3.1.0 as minimum and cleanup dependencies

slachiewicz commented on pull request #4: URL: https://github.com/apache/maven-shared-jar/pull/4#issuecomment-636472449 https://github.com/apache/maven-shared-jar/commit/580f53c1b63a7630cb3a70822035f4531bfadf2b This is an

[GitHub] [maven-shared-jar] slachiewicz edited a comment on pull request #4: [MSHARED-905] set Maven 3.1.0 as minimum and cleanup dependencies

slachiewicz edited a comment on pull request #4: URL: https://github.com/apache/maven-shared-jar/pull/4#issuecomment-636472449 See other jira and commit https://github.com/apache/maven-shared-jar/commit/580f53c1b63a7630cb3a70822035f4531bfadf2b

[GitHub] [maven-shared-jar] elharo opened a new pull request #4: [MSHARED-905] set Maven 3.1.0 as minimum and cleanup dependencies

elharo opened a new pull request #4: URL: https://github.com/apache/maven-shared-jar/pull/4 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above

[GitHub] [maven-site-plugin] elharo commented on pull request #27: [MSITE-757] More cleanup after upgrade to Maven 3.0.5

elharo commented on pull request #27: URL: https://github.com/apache/maven-site-plugin/pull/27#issuecomment-634132747 seems to have broken Jenkins: https://builds.apache.org/job/maven-box/job/maven-site-plugin/job/master/99/

[GitHub] [maven-site-plugin] slachiewicz opened a new pull request #27: [MSITE-757] More cleanup after upgrade to Maven 3.0.5

slachiewicz opened a new pull request #27: URL: https://github.com/apache/maven-site-plugin/pull/27 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[GitHub] [maven-site-plugin] slachiewicz commented on pull request #27: [MSITE-757] More cleanup after upgrade to Maven 3.0.5

slachiewicz commented on pull request #27: URL: https://github.com/apache/maven-site-plugin/pull/27#issuecomment-633969397 This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [maven-site-plugin] slachiewicz closed pull request #27: [MSITE-757] More cleanup after upgrade to Maven 3.0.5

slachiewicz closed pull request #27: URL: https://github.com/apache/maven-site-plugin/pull/27 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

Re: Yearly JIRA cleanup

t 6:29 AM Elliotte Rusty Harold > >> wrote: > >> > > >> > While working through the bugs I found this interesting bit of history: > >> > > >> > > >> https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 >

Re: Yearly JIRA cleanup

ther than simply ignoring the issue and not responding. >> >> On Fri, Dec 20, 2019 at 6:29 AM Elliotte Rusty Harold >> wrote: >> > >> > While working through the bugs I found this interesting bit of history: >> > >> > >> https://cwiki.apac

Re: Yearly JIRA cleanup

onest with them about our true objections, > rather than simply ignoring the issue and not responding. > > On Fri, Dec 20, 2019 at 6:29 AM Elliotte Rusty Harold > wrote: > > > > While working through the bugs I found this interesting bit of history: > > > > > htt

Re: Yearly JIRA cleanup

h the bugs I found this interesting bit of history: > > > > https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 > > > > It seems like we've been here before. Some of the bugs that were > > autoclosed then were reopened and are now scheduled for autoclose &

Re: Yearly JIRA cleanup

AM Elliotte Rusty Harold wrote: > > While working through the bugs I found this interesting bit of history: > > https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 > > It seems like we've been here before. Some of the bugs that were > autoclos

Re: Yearly JIRA cleanup

I will exlude those. It does not makes sense to close/reopen again. Am 2019-12-20 um 12:29 schrieb Elliotte Rusty Harold: While working through the bugs I found this interesting bit of history: https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 It seems like

Re: Yearly JIRA cleanup

While working through the bugs I found this interesting bit of history: https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 It seems like we've been here before. Some of the bugs that were autoclosed then were reopened and are now scheduled for autoclose again. Any

Re: Yearly JIRA cleanup

Am 2019-12-13 um 16:08 schrieb Elliotte Rusty Harold: NVM, I seem to have access now. I think I just needed to logout with my old credentials and back in with the new ones. Elliotte, please go through the list and update those tickets you seen to be addressible within a decent timeframe.

Re: Yearly JIRA cleanup

NVM, I seem to have access now. I think I just needed to logout with my old credentials and back in with the new ones. On Fri, Dec 13, 2019 at 9:56 AM Elliotte Rusty Harold wrote: > > On Thu, Dec 12, 2019 at 6:56 PM Stephen Connolly > wrote: > > I think we have some crazy permissions that Brian

Re: Yearly JIRA cleanup

On Thu, Dec 12, 2019 at 6:56 PM Stephen Connolly wrote: > I think we have some crazy permissions that Brian manages. Ldap just fixes > the account name to match across systems AIUI > That's probably true. As of an hour ago, I did not seem able to close issues. -- Elliotte Rusty Harold

Re: Yearly JIRA cleanup

On Thu 12 Dec 2019 at 17:31, Robert Scholte wrote: > IIUC since Jira uses the ASF LDAP, there's no extra need for Brian to do > this anymore. All should be in place by now. > I think we have some crazy permissions that Brian manages. Ldap just fixes the account name to match across systems AIUI

Re: Yearly JIRA cleanup

IIUC since Jira uses the ASF LDAP, there's no extra need for Brian to do this anymore. All should be in place by now. thanks, Robert On 12-12-2019 15:20:24, Stephen Connolly wrote: On Mon 9 Dec 2019 at 20:53, Elliotte Rusty Harold wrote: > On Mon, Dec 9, 2019 at 3:18 PM Michael Osipov wrote:

Re: Yearly JIRA cleanup

On Mon 9 Dec 2019 at 20:53, Elliotte Rusty Harold wrote: > On Mon, Dec 9, 2019 at 3:18 PM Michael Osipov wrote: > > > > Am 2019-12-08 um 18:08 schrieb Elliotte Rusty Harold: > > > Please don't. There are certainly some real and important issues in > > > there. More importantly, users spent a

Re: Yearly JIRA cleanup

On Mon, Dec 9, 2019 at 3:18 PM Michael Osipov wrote: > > Am 2019-12-08 um 18:08 schrieb Elliotte Rusty Harold: > > Please don't. There are certainly some real and important issues in > > there. More importantly, users spent a great deal of effort and time > > to file those. Bulk closing them

Re: Yearly JIRA cleanup

at least one year of silence, I'd like to perform another JIRA issue cleanup for issues which have been not touched for more than three years. Query: https://issues.apache.org/jira/issues/?filter=12333204=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20AND%20resolution%20%3D%20Unresolved

Re: Yearly JIRA cleanup

: Hi folks, after at least one year of silence, I'd like to perform another JIRA issue cleanup for issues which have been not touched for more than three years. Query: https://issues.apache.org/jira/issues/?filter=12333204=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20AND%20resolution

Re: Yearly JIRA cleanup

one year of silence, I'd like to perform another JIRA > > issue cleanup for issues which have been not touched for more than three > > years. > > > > Query: > > > https://issues.apache.org/jira/issues/?filter=12333204=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-

Re: Yearly JIRA cleanup

at least one year of silence, I'd like to perform another JIRA > issue cleanup for issues which have been not touched for more than three > years. > > Query: > https://issues.apache.org/jira/issues/?filter=12333204=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20AND%20re

Re: Yearly JIRA cleanup

ved search. Michael On December 8, 2019 at 13:50, Michael Osipov wrote: Hi folks, after at least one year of silence, I'd like to perform another JIRA issue cleanup for issues which have been not touched for more than three years. Query: https://issues.apache.org/jira/issues/?filter=1233320

Re: Yearly JIRA cleanup

, Maarten On December 8, 2019 at 13:50, Michael Osipov wrote: Hi folks, after at least one year of silence, I'd like to perform another JIRA issue cleanup for issues which have been not touched for more than three years. Query: https://issues.apache.org/jira/issues/?filter=12333204=cate

Yearly JIRA cleanup

Hi folks, after at least one year of silence, I'd like to perform another JIRA issue cleanup for issues which have been not touched for more than three years. Query: https://issues.apache.org/jira/issues/?filter=12333204=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20AND

Re: Cleanup Jenkins Jobs - Part II

Hi, I have removed all the jobs in that view including the view itself... Kind regards Karl Heinz Marbaise On 07/08/18 21:31, Karl Heinz Marbaise wrote: Hi, we have a number of Maven Jobs: https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/ which are superflous in the meantime cause

Cleanup Jenkins Jobs - Part II

Hi, we have a number of Maven Jobs: https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/ which are superflous in the meantime cause they are handled by the pipelines. I would go to delete them on 17.08.2018 except somebody will object? Kind regards Karl Heinz Marbaise

Re: Spring cleanup JIRA

Am 2018-03-07 um 23:31 schrieb Michael Osipov: Folks, I did yet another analysis on open issues. We have currently more than 400 open issues which haven't been touched for more than three (3) years. The last two times I autoclosed them with a message. People could request a reopen, very

Re: Spring cleanup JIRA

100 for the whole Maven project? Luckily we have ~85 projects, so the damage looks manageable. However, with a total of 2000+ open issues and with the current active resources it is impossible to fix them all. So yes, close them as Auto-Close with a clear message. I sometimes look at

Re: Spring cleanup JIRA

Non binding but agreed - once an issue list gets beyond 50 it's hard to see the forest, once it's beyond 100 you can pretty much guarantee that everyone is lost. Cheers, Martijn On 8 March 2018 at 07:45, Anders Hammar wrote: > +1 for the same process as last time. > >

Re: Spring cleanup JIRA

+1 for the same process as last time. /Anders On Wed, Mar 7, 2018 at 11:31 PM, Michael Osipov wrote: > Folks, > > I did yet another analysis on open issues. We have currently more than 400 > open issues which haven't been touched for more than three (3) years. > > The last

Spring cleanup JIRA

Folks, I did yet another analysis on open issues. We have currently more than 400 open issues which haven't been touched for more than three (3) years. The last two times I autoclosed them with a message. People could request a reopen, very little did. Should we do this again? The list

[GitHub] maven-indexer issue #23: Full codebase reformat, minor cleanup, no code/logi...

Github user hboutemy commented on the issue: https://github.com/apache/maven-indexer/pull/23 sorry, I did not notice you were working on it, I did some checkstyle fixes that messed your work :( --- - To

[GitHub] maven-indexer issue #23: Full codebase reformat, minor cleanup, no code/logi...

Github user cstamas commented on the issue: https://github.com/apache/maven-indexer/pull/23 Not merged, gave up. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail:

[GitHub] maven-indexer pull request #23: Full codebase reformat, minor cleanup, no co...

Github user cstamas closed the pull request at: https://github.com/apache/maven-indexer/pull/23 --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven-indexer pull request #23: Full codebase reformat, minor cleanup, no co...

GitHub user cstamas opened a pull request: https://github.com/apache/maven-indexer/pull/23 Full codebase reformat, minor cleanup, no code/logic change Reformatted full codebase, as there was mixed formatting, and checkstyle did report a huge amount of errors. Now, mostly

[GitHub] maven pull request #111: [MNG-6203] Minor cleanup in MavenCli.java

Github user stefaneicher closed the pull request at: https://github.com/apache/maven/pull/111 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] maven issue #111: [MNG-6203] Minor cleanup in MavenCli.java

Github user khmarbaise commented on the issue: https://github.com/apache/maven/pull/111 This pull request has been integrated into maven core. Thanks for your support. Please close this pull request. --- If your project is set up for it, you can reply to this email and have your

[GitHub] maven issue #111: [MNG-6203] Minor cleanup in MavenCli.java

Github user khmarbaise commented on the issue: https://github.com/apache/maven/pull/111 If you add the JIRA ticket this PR is automatically added to the JIRA ticket...Thanks for this.. --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] maven pull request #111: [MNG-6203] Minor cleanup in MavenCli.java

GitHub user stefaneicher opened a pull request: https://github.com/apache/maven/pull/111 [MNG-6203] Minor cleanup in MavenCli.java There is some unnecessary code in the MavenCli.java from line #1465 to #1474. The functionality has been moved to line #1215. Signed-off

Re: Another yearly issue cleanup in JIRA

cleanup in JIRA like a did last year. We currently have 127 unresolved issues which haven't been updated for more than three years. They drill down as follows: Wish: 3 Task: 4 New Feature: 14 Improvement: 34 Bug: 72 Here is the query for: category = Maven AND updated <= -156w AND resolut

Re: Another yearly issue cleanup in JIRA

to remember that no issue has been updated since my last mail. You still have a couple of days to take a look. Monday is deadline. Am 2015-12-25 um 19:00 schrieb Michael Osipov: Hi folks, the previous had a bad wording, so I decided to rerun that. I'd like to do another issue cleanup in JIRA like

Re: Another yearly issue cleanup in JIRA

Am 2015-12-25 um 19:00 schrieb Michael Osipov: Hi folks, the previous had a bad wording, so I decided to rerun that. I'd like to do another issue cleanup in JIRA like a did last year. We currently have 127 unresolved issues which haven't been updated for more than three years. They drill down

Another yearly issue cleanup in JIRA

Hi folks, the previous had a bad wording, so I decided to rerun that. I'd like to do another issue cleanup in JIRA like a did last year. We currently have 127 unresolved issues which haven't been updated for more than three years. They drill down as follows: Wish: 3 Task: 4 New Feature: 14

Maven Core Branch Cleanup

Hi, i have taken a look onto the list of branches on maven core which is a list of 17 beanches but where many of them haven't been touched for years (yes i'm using plural)... MNG-3004 Updated 6 years ago by Daniel Fabulich MNG-4388 Updated 6 years ago by bentmann MNG-1803 Updated 5 years ago

Re: Maven Core Branch Cleanup

Hi, cleaning up done... heads 23 hours agomaster shortlog | log | tree 8 days ago slf4j-log4j2.4 shortlog | log | tree 6 weeks ago MNG-5878 shortlog | log | tree 9 months agoconfigurator shortlog | log | tree 19 months ago maven-3.1.x shortlog |

Re: Maven Core Branch Cleanup

You can nuke all my branches. They are either integrated, irrelevant, or easy to recreate. > On Oct 12, 2015, at 2:11 PM, Karl Heinz Marbaise wrote: > > Hi, > > i have taken a look onto the list of branches on maven core which is a list > of 17 beanches but where many of

Re: Maven Core Branch Cleanup

Anyone wishing to retain these branches can just go ahead and fork the girhub repo, they' 2015-10-12 20:20 GMT+02:00 Jason van Zyl : > You can nuke all my branches. They are either integrated, irrelevant, or easy > to recreate. > >> On Oct 12, 2015, at 2:11 PM, Karl Heinz

Re: Another JIRA cleanup

(thousands) haven't been touched for years. I hardly believe that someone will pick them up after two or three years. To get us focused on new issues and ongoing improvements, I'd like to perform another cleanup in JIRA. Currectly we have: * 729 issues older than three (3) years [2] * 1496 issues

Re: Another JIRA cleanup

believe that someone will pick them up after two or three years. To get us focused on new issues and ongoing improvements, I'd like to perform another cleanup in JIRA. Currectly we have: * 729 issues older than three (3) years [2] * 1496 issues older than two (2) years [3] (Numbers accumulate

Re: Another JIRA cleanup

ments, I'd like to > perform another cleanup in JIRA. > > Currectly we have: > > * 729 issues older than three (3) years [2] > * 1496 issues older than two (2) years [3] > > (Numbers accumulate) > > I'd like to set the three-year-old issues to ASF JIRA "Auto Closed&quo

Re: Re: Another JIRA cleanup

> Gesendet: Mittwoch, 02. September 2015 um 10:31 Uhr > Von: "Tibor Digana" <tibor.dig...@googlemail.com> > An: "Maven Developers List" <dev@maven.apache.org> > Betreff: Re: Another JIRA cleanup > > The link is not reachable. Can you fix it?

Re: Another JIRA cleanup

o reperform that task because we have more than 3100 open > > issues at the moment [1]. > > > > Many issues (thousands) haven't been touched for years. I hardly believe > > that someone will pick them up after two or three years. > > > > To get us focused o

Re: Another JIRA cleanup

used on new issues and ongoing improvements, I'd like to > perform another cleanup in JIRA. > > Currectly we have: > > * 729 issues older than three (3) years [2] > * 1496 issues older than two (2) years [3] > > (Numbers accumulate) > > I'd like to set the three-year-ol

Re: Another JIRA cleanup

+1 I think the constant looking at ways to cleanup the issues is necessary. So I appreciate going through and culling the issues that have not been looked at in quite a while. > On Aug 30, 2015, at 3:31 PM, Michael Osipov <micha...@apache.org> wrote: > > Hi folks, > &

Another JIRA cleanup

after two or three years. To get us focused on new issues and ongoing improvements, I'd like to perform another cleanup in JIRA. Currectly we have: * 729 issues older than three (3) years [2] * 1496 issues older than two (2) years [3] (Numbers accumulate) I'd like to set the three-year-old

Re: Maven site cleanup

Jason when we talked about this in the past. At this stage I will move forward with this suspecting that your silence is a sign of agreement. manfred Manfred Moser wrote on 2015-06-25 13:07: Hi! I would like to do some cleanup of download page and related things. It is the most used page

Re: Maven site cleanup

this in the past. At this stage I will move forward with this suspecting that your silence is a sign of agreement. manfred Manfred Moser wrote on 2015-06-25 13:07: Hi! I would like to do some cleanup of download page and related things. It is the most used page on the site and I think we could

Re: Maven site cleanup

with this suspecting that your silence is a sign of agreement. manfred Manfred Moser wrote on 2015-06-25 13:07: Hi! I would like to do some cleanup of download page and related things. It is the most used page on the site and I think we could have some signficant improvements around

Re: Maven site cleanup

that your silence is a sign of agreement. manfred Manfred Moser wrote on 2015-06-25 13:07: Hi! I would like to do some cleanup of download page and related things. It is the most used page on the site and I think we could have some signficant improvements around the downloa

Re: Maven site cleanup

some cleanup of download page and related things. It is the most used page on the site and I think we could have some signficant improvements around the downloa and installation experience. Please check out details at https://issues.apache.org/jira/browse/MNGSITE-245 and comment here

Re: Maven site cleanup

with this suspecting that your silence is a sign of agreement. manfred Manfred Moser wrote on 2015-06-25 13:07: Hi! I would like to do some cleanup of download page and related things. It is the most used page on the site and I think we could have some signficant improvements around

Re: Two cleanup patches for maven-eclipse-plugin (MECLIPSE-697, MECLIPSE-758)

Great, Thanks! I'll do the 2.10 release in a not too distant future. Am Donnerstag, 9. April 2015 schrieb Joseph Walton : I've taken a look at two cleanup tasks for maven-eclipse-plugin. One is a clearout of long-deprecated classes: https://issues.apache.org/jira/browse/MECLIPSE-697

Two cleanup patches for maven-eclipse-plugin (MECLIPSE-697, MECLIPSE-758)

I've taken a look at two cleanup tasks for maven-eclipse-plugin. One is a clearout of long-deprecated classes: https://issues.apache.org/jira/browse/MECLIPSE-697 and the other is updating the mojos to use annotations: https://issues.apache.org/jira/browse/MECLIPSE-758 Both have

Maven 1.x cleanup

Hi, About a year ago, the EOL banner was added for Maven 1.x. Today I saw there was a still a maven-1.x link in the navigation from the parent POM, which I removed, and added a single section to the bottom of the front page for archived documentation. Looking at

Re: Maven 1.x cleanup

Leave SVN alone, it's only a matter of time before it's permanently retired in it's entirety, right? On Tue, Jul 29, 2014 at 12:58 PM, Brett Porter br...@apache.org wrote: Hi, About a year ago, the EOL banner was added for Maven 1.x. Today I saw there was a still a maven-1.x link in the

Further cleanup of Builders (extension of MNG-5575)

Hi, I made a first pass at coalescing the logic for a specific way to build (single threaded, multi threaded, weave) into its own implementation but there is still much cleanup to be done. This was pure refactoring and there isn't much functional change aside from adding a command line

Re: Further cleanup of Builders (extension of MNG-5575)

but there is still much cleanup to be done. This was pure refactoring and there isn't much functional change aside from adding a command line parameter to specify the id of a specific builder if you have your own implementation. I'm using this capability for an aggressive mode of parallelization and while

Re: Further cleanup of Builders (extension of MNG-5575)

for a specific way to build (single threaded, multi threaded, weave) into its own implementation but there is still much cleanup to be done. This was pure refactoring and there isn't much functional change aside from adding a command line parameter to specify the id of a specific builder if you have your

Re: Further cleanup of Builders (extension of MNG-5575)

) into its own implementation but there is still much cleanup to be done. This was pure refactoring and there isn't much functional change aside from adding a command line parameter to specify the id of a specific builder if you have your own implementation. I'm using this capability

Re: Further cleanup of Builders (extension of MNG-5575)

ja...@takari.io følgende: Hi, I made a first pass at coalescing the logic for a specific way to build (single threaded, multi threaded, weave) into its own implementation but there is still much cleanup to be done. This was pure refactoring and there isn't much functional change aside from

RE: JIRA Cleanup

List Subject: Re: JIRA Cleanup I changed the strategy slightly as I thought it might be crappy if the issue was created 5 years ago, but the person updated it 2 months ago. So I took all the issues that have not been updated in the last year and unassigned and closed those out. Got to about

Re: JIRA Cleanup

updated in the last year and unassigned and closed those out. Got to about the same number and thought this more fair. I referred anyone looking at the comment to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 I'll start sifting through what remains tomorrow

Re: JIRA Cleanup

at the comment to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 I'll start sifting through what remains tomorrow. On Jan 22, 2014, at 1:02 PM, Jason van Zyl ja...@takari.io wrote: Yup, it's very straight forward to add a comment to each of the issues

Re: JIRA Cleanup

of providing a working stand-alone example of the problem. This will at least start the cleanup process. How's that sound? On Jan 20, 2014, at 4:53 PM, Jason van Zyl ja...@takari.io wrote: Ok, I'll write something up and send it to the user and dev list. On Jan 20, 2014, at 2:17 PM, Benson

Re: JIRA Cleanup

trying to get the JIRA issue under control. We're closing all unassigned issues older than 2 years but people are free to reopen issues for bugs if they follow a process of providing a working stand-alone example of the problem. This will at least start the cleanup process. How's that sound

Re: JIRA Cleanup

are free to reopen issues for bugs if they follow a process of providing a working stand-alone example of the problem. This will at least start the cleanup process. How's that sound? On Jan 20, 2014, at 4:53 PM, Jason van Zyl ja...@takari.io wrote: Ok, I'll write something up and send

Re: JIRA Cleanup

for bugs if they follow a process of providing a working stand-alone example of the problem. This will at least start the cleanup process. How's that sound? On Jan 20, 2014, at 4:53 PM, Jason van Zyl ja...@takari.io wrote: Ok, I'll write something up and send it to the user and dev list

Re: JIRA Cleanup

this more fair. I referred anyone looking at the comment to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 I'll start sifting through what remains tomorrow. On Jan 22, 2014, at 1:02 PM, Jason van Zyl ja...@takari.io wrote: Yup, it's very straight forward to add

Re: JIRA Cleanup

issue under control. We're closing all unassigned issues older than 2 years but people are free to reopen issues for bugs if they follow a process of providing a working stand-alone example of the problem. This will at least start the cleanup process. How's that sound? On Jan 20, 2014, at 4:53

JIRA Cleanup

Really, it's more about dropping a nuclear bomb on JIRA. While trying to sift through it this weekend it's clear to me it's less than ideal in there. There are issues that are 12 years old and while there might be some useful information in there that we hand select, I think anything that is

Re: JIRA Cleanup

If we are going wholesale dumping issues (and I am not against that), I have a more radical suggestion... let's just move core to the ASF JIRA... with next to no issues needing migration it would be easy ;-) On 20 January 2014 17:23, Jason van Zyl ja...@takari.io wrote: Really, it's more about

Re: JIRA Cleanup

Am 2014-01-20 18:32, schrieb Stephen Connolly: If we are going wholesale dumping issues (and I am not against that), I have a more radical suggestion... let's just move core to the ASF JIRA... with next to no issues needing migration it would be easy ;-) +1 I head this idea in mind for

Re: JIRA Cleanup

Am 2014-01-20 18:32, schrieb Stephen Connolly: If we are going wholesale dumping issues (and I am not against that), I have a more radical suggestion... let's just move core to the ASF JIRA... with next to no issues needing migration it would be easy ;-) +1 I head this idea in mind for

  1   2   >