Re: [DISCUSS] Idle bug handling approach
Michaelo, Due to we have a lot of open issues in SUREFIRE I have decided to ask the Reporter for closing in JIRA. So I have created a list of closable JIRA bugs and opened a discussion in Maven mailing list last week. This way the list was visible to all developers and everybody could argue to not close them. After one week we got a consensus, there wasn't any objection from committers and PMC to not close ALL of them, and thus I closed them. Except for one bug where I made an exception which will be categorized as an improvement possibly in a new JIRA ticket. - BR, tibor17 -- View this message in context: http://maven.40175.n5.nabble.com/DISCUSS-Idle-bug-handling-approach-tp5815394p5815645.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] Idle bug handling approach
I thinks this is great. Add item 5: 5. Some judgement should be used when applying this procedure to issues that have significant user involvement. We should probably make 2 tags in jira for issues that are in state 2 and 4; feedbackRequired and Closeable ? :) Kristian 2014-11-24 22:58 GMT+01:00 Michael Osipov micha...@apache.org: Folks, here is a little wrap up after the ideas and votes posted so far: 1. Ask for additional information if you think you can fix that bug or want to help someone else to drag some attention 2. Give the reporter 30 days 3. Add a reminder after 30 days for a grace period of 10 days 4. 10 days have passed and no change has happened, close as Incomplete Did I miss something? I would this to the Development Center page in time. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] Idle bug handling approach
I also did this several times in surefire. I think this strategy is better because it can be used to avoid the accumulation of issues in the first place. It also allows us to be a little stricter on demanding test projects or similar, which is a great thing. As for the maven 1.x issues that's a completely different story, bulk closing sounds good to me ! Kristian 2014-11-25 9:33 GMT+01:00 tibor17 tibo...@lycos.com: Michaelo, Due to we have a lot of open issues in SUREFIRE I have decided to ask the Reporter for closing in JIRA. So I have created a list of closable JIRA bugs and opened a discussion in Maven mailing list last week. This way the list was visible to all developers and everybody could argue to not close them. After one week we got a consensus, there wasn't any objection from committers and PMC to not close ALL of them, and thus I closed them. Except for one bug where I made an exception which will be categorized as an improvement possibly in a new JIRA ticket. - BR, tibor17 -- View this message in context: http://maven.40175.n5.nabble.com/DISCUSS-Idle-bug-handling-approach-tp5815394p5815645.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Change project logo and adopt owl as mascot
+1 On 25 November 2014 at 10:57, Stephen Connolly stephen.alan.conno...@gmail.com wrote: For anyone who has been living under a rock, here is the background Background = I think everyone can agree that the site needs a reorganisation and a rewrite. Users cannot find what they need, and the end result is that people keep on abusing maven rather than having maven help them. Try as I might, I have been unable to motivate myself to do the reorganisation with the current dated look and feel of the site... I am not saying that picking a new logo and selecting a mascot will result in making progress, but it can't hurt and I believe it will help Proposed changes === 1. Change the logo font to Alte Haas Grotesk Bold with italics applied by Inkscape 2. Change the highlighted letter from 'a' to 'v' and replace the v with two Apache Feathers 3. Adopt the (currently unnamed) owl as our mascot Here is a link to the font: http://www.dafont.com/alte-haas-grotesk.font Here is a large version of the owl and the logo: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png A regular version of the own and the logo, e.g. a size suitable for use in the top of the standard maven sites: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final.png (Note that in all likelihood, the mascot would probably end up on the other side of the title bar from the logo... and that is IF the mascot ends up on the title bar) Here is both of those rendered in a site (as it can be helpful to see the graphics adjacent to text) http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-context.png Logo Rational === If we do some searches for the Maven logo: https://www.google.com/search?site=imghptbm=ischq=maven+logooq=maven+logo http://www.bing.com/images/search?q=maven+logogo=Submitqs=nform=QBLHscope=imagespq=maven+logo Our current logo, with a single highlighted letter stands out quite well from the other maven logos, so keeping a highlighted letter and an italic rendered font maintains continuity with our current logo. By changing the highlighted letter to the `v` and by using two Apache feathers to create the `v`, we connect our logo back to Apache... we are Apache Maven after all. The `v` is also the common short term for version (e.g.v3 is short for version 3). Apache Maven puts a lot of emphasis on versions of dependencies and plugins... you could say that versions are very important to Maven. The colours of the feather were changed to solid colours to match the owl mascot's scarf, beak and eyebrows Voting rules = Anyone who is subscribed to the dev or users list is eligible to vote. If you vote multiple times, only your final vote will be counted. The vote will be open until 1:00pm GMT on Wed 3rd Dec 2014 The vote is for all three changes as one single change. Partial votes (e.g. for the logo but not the mascot, or vice-versa) will not be counted. I, as the caller of the vote, reserve the right to cancel the vote if this vote is putting the harmony of the community at risk. If a majority of the PMC believe that this vote is putting the harmony of the community at risk, then the PMC may cancel this vote (though if even a small minority of the PMC were of that belief, I will more than likely have cancelled the vote before the PMC would need to decide... I'm just stating this FTR) The decision will be a simple majority, there will be no special veto powers. +1: [ ] Change the logo to the proposed logo and adopt the owl as project mascot 0: [ ] No opinion -1: [ ] No change Please only respond with +1, 0 or -1. If you want to discuss the proposed changes please use a different thread. This thread is for voting only. -Stephen
[VOTE] Change project logo and adopt owl as mascot
For anyone who has been living under a rock, here is the background Background = I think everyone can agree that the site needs a reorganisation and a rewrite. Users cannot find what they need, and the end result is that people keep on abusing maven rather than having maven help them. Try as I might, I have been unable to motivate myself to do the reorganisation with the current dated look and feel of the site... I am not saying that picking a new logo and selecting a mascot will result in making progress, but it can't hurt and I believe it will help Proposed changes === 1. Change the logo font to Alte Haas Grotesk Bold with italics applied by Inkscape 2. Change the highlighted letter from 'a' to 'v' and replace the v with two Apache Feathers 3. Adopt the (currently unnamed) owl as our mascot Here is a link to the font: http://www.dafont.com/alte-haas-grotesk.font Here is a large version of the owl and the logo: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png A regular version of the own and the logo, e.g. a size suitable for use in the top of the standard maven sites: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final.png (Note that in all likelihood, the mascot would probably end up on the other side of the title bar from the logo... and that is IF the mascot ends up on the title bar) Here is both of those rendered in a site (as it can be helpful to see the graphics adjacent to text) http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-context.png Logo Rational === If we do some searches for the Maven logo: https://www.google.com/search?site=imghptbm=ischq=maven+logooq=maven+logo http://www.bing.com/images/search?q=maven+logogo=Submitqs=nform=QBLHscope=imagespq=maven+logo Our current logo, with a single highlighted letter stands out quite well from the other maven logos, so keeping a highlighted letter and an italic rendered font maintains continuity with our current logo. By changing the highlighted letter to the `v` and by using two Apache feathers to create the `v`, we connect our logo back to Apache... we are Apache Maven after all. The `v` is also the common short term for version (e.g.v3 is short for version 3). Apache Maven puts a lot of emphasis on versions of dependencies and plugins... you could say that versions are very important to Maven. The colours of the feather were changed to solid colours to match the owl mascot's scarf, beak and eyebrows Voting rules = Anyone who is subscribed to the dev or users list is eligible to vote. If you vote multiple times, only your final vote will be counted. The vote will be open until 1:00pm GMT on Wed 3rd Dec 2014 The vote is for all three changes as one single change. Partial votes (e.g. for the logo but not the mascot, or vice-versa) will not be counted. I, as the caller of the vote, reserve the right to cancel the vote if this vote is putting the harmony of the community at risk. If a majority of the PMC believe that this vote is putting the harmony of the community at risk, then the PMC may cancel this vote (though if even a small minority of the PMC were of that belief, I will more than likely have cancelled the vote before the PMC would need to decide... I'm just stating this FTR) The decision will be a simple majority, there will be no special veto powers. +1: [ ] Change the logo to the proposed logo and adopt the owl as project mascot 0: [ ] No opinion -1: [ ] No change Please only respond with +1, 0 or -1. If you want to discuss the proposed changes please use a different thread. This thread is for voting only. -Stephen
Re: [VOTE] Change project logo and adopt owl as mascot
+1 thx On Tue, Nov 25, 2014 at 11:57 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1 On 25 November 2014 at 10:57, Stephen Connolly stephen.alan.conno...@gmail.com wrote: For anyone who has been living under a rock, here is the background Background = I think everyone can agree that the site needs a reorganisation and a rewrite. Users cannot find what they need, and the end result is that people keep on abusing maven rather than having maven help them. Try as I might, I have been unable to motivate myself to do the reorganisation with the current dated look and feel of the site... I am not saying that picking a new logo and selecting a mascot will result in making progress, but it can't hurt and I believe it will help Proposed changes === 1. Change the logo font to Alte Haas Grotesk Bold with italics applied by Inkscape 2. Change the highlighted letter from 'a' to 'v' and replace the v with two Apache Feathers 3. Adopt the (currently unnamed) owl as our mascot Here is a link to the font: http://www.dafont.com/alte-haas-grotesk.font Here is a large version of the owl and the logo: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png A regular version of the own and the logo, e.g. a size suitable for use in the top of the standard maven sites: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final.png (Note that in all likelihood, the mascot would probably end up on the other side of the title bar from the logo... and that is IF the mascot ends up on the title bar) Here is both of those rendered in a site (as it can be helpful to see the graphics adjacent to text) http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-context.png Logo Rational === If we do some searches for the Maven logo: https://www.google.com/search?site=imghptbm=ischq=maven+logooq=maven+logo http://www.bing.com/images/search?q=maven+logogo=Submitqs=nform=QBLHscope=imagespq=maven+logo Our current logo, with a single highlighted letter stands out quite well from the other maven logos, so keeping a highlighted letter and an italic rendered font maintains continuity with our current logo. By changing the highlighted letter to the `v` and by using two Apache feathers to create the `v`, we connect our logo back to Apache... we are Apache Maven after all. The `v` is also the common short term for version (e.g.v3 is short for version 3). Apache Maven puts a lot of emphasis on versions of dependencies and plugins... you could say that versions are very important to Maven. The colours of the feather were changed to solid colours to match the owl mascot's scarf, beak and eyebrows Voting rules = Anyone who is subscribed to the dev or users list is eligible to vote. If you vote multiple times, only your final vote will be counted. The vote will be open until 1:00pm GMT on Wed 3rd Dec 2014 The vote is for all three changes as one single change. Partial votes (e.g. for the logo but not the mascot, or vice-versa) will not be counted. I, as the caller of the vote, reserve the right to cancel the vote if this vote is putting the harmony of the community at risk. If a majority of the PMC believe that this vote is putting the harmony of the community at risk, then the PMC may cancel this vote (though if even a small minority of the PMC were of that belief, I will more than likely have cancelled the vote before the PMC would need to decide... I'm just stating this FTR) The decision will be a simple majority, there will be no special veto powers. +1: [ ] Change the logo to the proposed logo and adopt the owl as project mascot 0: [ ] No opinion -1: [ ] No change Please only respond with +1, 0 or -1. If you want to discuss the proposed changes please use a different thread. This thread is for voting only. -Stephen -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
[DISCUSS] In the event of adopting the owl as project mascot, what will we call it?
http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png When I created this owl, I gave it the name Couché Tard which is a french nickname for an owl (literal translation: Sleeps Late) Early versions of this owl have ended up with the nickname Shotgun Owl due to the belly feathers being white in the initial versions, which some people thought made it look like it had been shot. Some people feel that we shouldn't name a mascot... As creator of the graphic, I could force the issue... but I would much rather if the community has a name that the community wants. Please provide your suggestions in this thread. If the owl is adopted as a mascot, we will have a second vote thread to confirm its name. I personally recommend a gender neutral name.
Re: [VOTE] Change project logo and adopt owl as mascot
-1 -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Dienstag, 25. November 2014 11:57 An: Maven Developers List; Maven Users List Betreff: [VOTE] Change project logo and adopt owl as mascot For anyone who has been living under a rock, here is the background Background = I think everyone can agree that the site needs a reorganisation and a rewrite. Users cannot find what they need, and the end result is that people keep on abusing maven rather than having maven help them. Try as I might, I have been unable to motivate myself to do the reorganisation with the current dated look and feel of the site... I am not saying that picking a new logo and selecting a mascot will result in making progress, but it can't hurt and I believe it will help Proposed changes === 1. Change the logo font to Alte Haas Grotesk Bold with italics applied by Inkscape 2. Change the highlighted letter from 'a' to 'v' and replace the v with two Apache Feathers 3. Adopt the (currently unnamed) owl as our mascot Here is a link to the font: http://www.dafont.com/alte-haas-grotesk.font Here is a large version of the owl and the logo: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png A regular version of the own and the logo, e.g. a size suitable for use in the top of the standard maven sites: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final.png (Note that in all likelihood, the mascot would probably end up on the other side of the title bar from the logo... and that is IF the mascot ends up on the title bar) Here is both of those rendered in a site (as it can be helpful to see the graphics adjacent to text) http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-context.png Logo Rational === If we do some searches for the Maven logo: https://www.google.com/search?site=imghptbm=ischq=maven+logooq=maven+logo http://www.bing.com/images/search?q=maven+logogo=Submitqs=nform=QBLHscope=imagespq=maven+logo Our current logo, with a single highlighted letter stands out quite well from the other maven logos, so keeping a highlighted letter and an italic rendered font maintains continuity with our current logo. By changing the highlighted letter to the `v` and by using two Apache feathers to create the `v`, we connect our logo back to Apache... we are Apache Maven after all. The `v` is also the common short term for version (e.g.v3 is short for version 3). Apache Maven puts a lot of emphasis on versions of dependencies and plugins... you could say that versions are very important to Maven. The colours of the feather were changed to solid colours to match the owl mascot's scarf, beak and eyebrows Voting rules = Anyone who is subscribed to the dev or users list is eligible to vote. If you vote multiple times, only your final vote will be counted. The vote will be open until 1:00pm GMT on Wed 3rd Dec 2014 The vote is for all three changes as one single change. Partial votes (e.g. for the logo but not the mascot, or vice-versa) will not be counted. I, as the caller of the vote, reserve the right to cancel the vote if this vote is putting the harmony of the community at risk. If a majority of the PMC believe that this vote is putting the harmony of the community at risk, then the PMC may cancel this vote (though if even a small minority of the PMC were of that belief, I will more than likely have cancelled the vote before the PMC would need to decide... I'm just stating this FTR) The decision will be a simple majority, there will be no special veto powers. +1: [ ] Change the logo to the proposed logo and adopt the owl as +project mascot 0: [ ] No opinion -1: [ ] No change Please only respond with +1, 0 or -1. If you want to discuss the proposed changes please use a different thread. This thread is for voting only. -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Change project logo and adopt owl as mascot
+1 On Tue Nov 25 2014 at 11:57:49 AM Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1 On 25 November 2014 at 10:57, Stephen Connolly stephen.alan.conno...@gmail.com wrote: For anyone who has been living under a rock, here is the background Background = I think everyone can agree that the site needs a reorganisation and a rewrite. Users cannot find what they need, and the end result is that people keep on abusing maven rather than having maven help them. Try as I might, I have been unable to motivate myself to do the reorganisation with the current dated look and feel of the site... I am not saying that picking a new logo and selecting a mascot will result in making progress, but it can't hurt and I believe it will help Proposed changes === 1. Change the logo font to Alte Haas Grotesk Bold with italics applied by Inkscape 2. Change the highlighted letter from 'a' to 'v' and replace the v with two Apache Feathers 3. Adopt the (currently unnamed) owl as our mascot Here is a link to the font: http://www.dafont.com/alte-haas-grotesk.font Here is a large version of the owl and the logo: http://people.apache.org/~stephenc/maven-logo-contest/ maven-owl-final-large.png A regular version of the own and the logo, e.g. a size suitable for use in the top of the standard maven sites: http://people.apache.org/~stephenc/maven-logo-contest/ maven-owl-final.png (Note that in all likelihood, the mascot would probably end up on the other side of the title bar from the logo... and that is IF the mascot ends up on the title bar) Here is both of those rendered in a site (as it can be helpful to see the graphics adjacent to text) http://people.apache.org/~stephenc/maven-logo-contest/ maven-owl-final-context.png Logo Rational === If we do some searches for the Maven logo: https://www.google.com/search?site=imghptbm=ischq=maven+ logooq=maven+logo http://www.bing.com/images/search?q=maven+logogo=Submit; qs=nform=QBLHscope=imagespq=maven+logo Our current logo, with a single highlighted letter stands out quite well from the other maven logos, so keeping a highlighted letter and an italic rendered font maintains continuity with our current logo. By changing the highlighted letter to the `v` and by using two Apache feathers to create the `v`, we connect our logo back to Apache... we are Apache Maven after all. The `v` is also the common short term for version (e.g.v3 is short for version 3). Apache Maven puts a lot of emphasis on versions of dependencies and plugins... you could say that versions are very important to Maven. The colours of the feather were changed to solid colours to match the owl mascot's scarf, beak and eyebrows Voting rules = Anyone who is subscribed to the dev or users list is eligible to vote. If you vote multiple times, only your final vote will be counted. The vote will be open until 1:00pm GMT on Wed 3rd Dec 2014 The vote is for all three changes as one single change. Partial votes (e.g. for the logo but not the mascot, or vice-versa) will not be counted. I, as the caller of the vote, reserve the right to cancel the vote if this vote is putting the harmony of the community at risk. If a majority of the PMC believe that this vote is putting the harmony of the community at risk, then the PMC may cancel this vote (though if even a small minority of the PMC were of that belief, I will more than likely have cancelled the vote before the PMC would need to decide... I'm just stating this FTR) The decision will be a simple majority, there will be no special veto powers. +1: [ ] Change the logo to the proposed logo and adopt the owl as project mascot 0: [ ] No opinion -1: [ ] No change Please only respond with +1, 0 or -1. If you want to discuss the proposed changes please use a different thread. This thread is for voting only. -Stephen
Re: [VOTE] Change project logo and adopt owl as mascot
+1 On 25.11.2014, at 11:57, Stephen Connolly stephen.alan.conno...@gmail.com wrote: - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Change project logo and adopt owl as mascot
+1 WBR, Maxim (from mobile, sorry for the typos) On Nov 25, 2014 5:31 PM, domi d...@fortysix.ch wrote: +1 On 25.11.2014, at 11:57, Stephen Connolly stephen.alan.conno...@gmail.com wrote: - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [VOTE] Change project logo and adopt owl as mascot
+1 Am Dienstag, 25. November 2014 schrieb Stephen Connolly : For anyone who has been living under a rock, here is the background Background = I think everyone can agree that the site needs a reorganisation and a rewrite. Users cannot find what they need, and the end result is that people keep on abusing maven rather than having maven help them. Try as I might, I have been unable to motivate myself to do the reorganisation with the current dated look and feel of the site... I am not saying that picking a new logo and selecting a mascot will result in making progress, but it can't hurt and I believe it will help Proposed changes === 1. Change the logo font to Alte Haas Grotesk Bold with italics applied by Inkscape 2. Change the highlighted letter from 'a' to 'v' and replace the v with two Apache Feathers 3. Adopt the (currently unnamed) owl as our mascot Here is a link to the font: http://www.dafont.com/alte-haas-grotesk.font Here is a large version of the owl and the logo: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png A regular version of the own and the logo, e.g. a size suitable for use in the top of the standard maven sites: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final.png (Note that in all likelihood, the mascot would probably end up on the other side of the title bar from the logo... and that is IF the mascot ends up on the title bar) Here is both of those rendered in a site (as it can be helpful to see the graphics adjacent to text) http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-context.png Logo Rational === If we do some searches for the Maven logo: https://www.google.com/search?site=imghptbm=ischq=maven+logooq=maven+logo http://www.bing.com/images/search?q=maven+logogo=Submitqs=nform=QBLHscope=imagespq=maven+logo Our current logo, with a single highlighted letter stands out quite well from the other maven logos, so keeping a highlighted letter and an italic rendered font maintains continuity with our current logo. By changing the highlighted letter to the `v` and by using two Apache feathers to create the `v`, we connect our logo back to Apache... we are Apache Maven after all. The `v` is also the common short term for version (e.g.v3 is short for version 3). Apache Maven puts a lot of emphasis on versions of dependencies and plugins... you could say that versions are very important to Maven. The colours of the feather were changed to solid colours to match the owl mascot's scarf, beak and eyebrows Voting rules = Anyone who is subscribed to the dev or users list is eligible to vote. If you vote multiple times, only your final vote will be counted. The vote will be open until 1:00pm GMT on Wed 3rd Dec 2014 The vote is for all three changes as one single change. Partial votes (e.g. for the logo but not the mascot, or vice-versa) will not be counted. I, as the caller of the vote, reserve the right to cancel the vote if this vote is putting the harmony of the community at risk. If a majority of the PMC believe that this vote is putting the harmony of the community at risk, then the PMC may cancel this vote (though if even a small minority of the PMC were of that belief, I will more than likely have cancelled the vote before the PMC would need to decide... I'm just stating this FTR) The decision will be a simple majority, there will be no special veto powers. +1: [ ] Change the logo to the proposed logo and adopt the owl as project mascot 0: [ ] No opinion -1: [ ] No change Please only respond with +1, 0 or -1. If you want to discuss the proposed changes please use a different thread. This thread is for voting only. -Stephen
Re: [DISCUSS] In the event of adopting the owl as project mascot, what will we call it?
I suggest Darth Mowl. But not seriously ;-). Am Dienstag, 25. November 2014 schrieb Stephen Connolly : http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png When I created this owl, I gave it the name Couché Tard which is a french nickname for an owl (literal translation: Sleeps Late) Early versions of this owl have ended up with the nickname Shotgun Owl due to the belly feathers being white in the initial versions, which some people thought made it look like it had been shot. Some people feel that we shouldn't name a mascot... As creator of the graphic, I could force the issue... but I would much rather if the community has a name that the community wants. Please provide your suggestions in this thread. If the owl is adopted as a mascot, we will have a second vote thread to confirm its name. I personally recommend a gender neutral name.
Re: [VOTE] Change project logo and adopt owl as mascot
-1 - only because a) I don’t understand the purpose of what is going on on the bird’s chest and b) I love the idea of putting the bird in a sweater with the letter “M” on it. Ralph On Nov 25, 2014, at 5:05 AM, Andreas Gudian andreas.gud...@gmail.com wrote: +1 Am Dienstag, 25. November 2014 schrieb Stephen Connolly : For anyone who has been living under a rock, here is the background Background = I think everyone can agree that the site needs a reorganisation and a rewrite. Users cannot find what they need, and the end result is that people keep on abusing maven rather than having maven help them. Try as I might, I have been unable to motivate myself to do the reorganisation with the current dated look and feel of the site... I am not saying that picking a new logo and selecting a mascot will result in making progress, but it can't hurt and I believe it will help Proposed changes === 1. Change the logo font to Alte Haas Grotesk Bold with italics applied by Inkscape 2. Change the highlighted letter from 'a' to 'v' and replace the v with two Apache Feathers 3. Adopt the (currently unnamed) owl as our mascot Here is a link to the font: http://www.dafont.com/alte-haas-grotesk.font Here is a large version of the owl and the logo: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png A regular version of the own and the logo, e.g. a size suitable for use in the top of the standard maven sites: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final.png (Note that in all likelihood, the mascot would probably end up on the other side of the title bar from the logo... and that is IF the mascot ends up on the title bar) Here is both of those rendered in a site (as it can be helpful to see the graphics adjacent to text) http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-context.png Logo Rational === If we do some searches for the Maven logo: https://www.google.com/search?site=imghptbm=ischq=maven+logooq=maven+logo http://www.bing.com/images/search?q=maven+logogo=Submitqs=nform=QBLHscope=imagespq=maven+logo Our current logo, with a single highlighted letter stands out quite well from the other maven logos, so keeping a highlighted letter and an italic rendered font maintains continuity with our current logo. By changing the highlighted letter to the `v` and by using two Apache feathers to create the `v`, we connect our logo back to Apache... we are Apache Maven after all. The `v` is also the common short term for version (e.g.v3 is short for version 3). Apache Maven puts a lot of emphasis on versions of dependencies and plugins... you could say that versions are very important to Maven. The colours of the feather were changed to solid colours to match the owl mascot's scarf, beak and eyebrows Voting rules = Anyone who is subscribed to the dev or users list is eligible to vote. If you vote multiple times, only your final vote will be counted. The vote will be open until 1:00pm GMT on Wed 3rd Dec 2014 The vote is for all three changes as one single change. Partial votes (e.g. for the logo but not the mascot, or vice-versa) will not be counted. I, as the caller of the vote, reserve the right to cancel the vote if this vote is putting the harmony of the community at risk. If a majority of the PMC believe that this vote is putting the harmony of the community at risk, then the PMC may cancel this vote (though if even a small minority of the PMC were of that belief, I will more than likely have cancelled the vote before the PMC would need to decide... I'm just stating this FTR) The decision will be a simple majority, there will be no special veto powers. +1: [ ] Change the logo to the proposed logo and adopt the owl as project mascot 0: [ ] No opinion -1: [ ] No change Please only respond with +1, 0 or -1. If you want to discuss the proposed changes please use a different thread. This thread is for voting only. -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Change project logo and adopt owl as mascot
+1 non-binding Cheers, Paul On Tue, Nov 25, 2014 at 8:31 AM, Ralph Goers ralph.go...@dslextreme.com wrote: -1 - only because a) I don’t understand the purpose of what is going on on the bird’s chest and b) I love the idea of putting the bird in a sweater with the letter “M” on it. Ralph On Nov 25, 2014, at 5:05 AM, Andreas Gudian andreas.gud...@gmail.com wrote: +1 Am Dienstag, 25. November 2014 schrieb Stephen Connolly : For anyone who has been living under a rock, here is the background Background = I think everyone can agree that the site needs a reorganisation and a rewrite. Users cannot find what they need, and the end result is that people keep on abusing maven rather than having maven help them. Try as I might, I have been unable to motivate myself to do the reorganisation with the current dated look and feel of the site... I am not saying that picking a new logo and selecting a mascot will result in making progress, but it can't hurt and I believe it will help Proposed changes === 1. Change the logo font to Alte Haas Grotesk Bold with italics applied by Inkscape 2. Change the highlighted letter from 'a' to 'v' and replace the v with two Apache Feathers 3. Adopt the (currently unnamed) owl as our mascot Here is a link to the font: http://www.dafont.com/alte-haas-grotesk.font Here is a large version of the owl and the logo: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png A regular version of the own and the logo, e.g. a size suitable for use in the top of the standard maven sites: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final.png (Note that in all likelihood, the mascot would probably end up on the other side of the title bar from the logo... and that is IF the mascot ends up on the title bar) Here is both of those rendered in a site (as it can be helpful to see the graphics adjacent to text) http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-context.png Logo Rational === If we do some searches for the Maven logo: https://www.google.com/search?site=imghptbm=ischq=maven+logooq=maven+logo http://www.bing.com/images/search?q=maven+logogo=Submitqs=nform=QBLHscope=imagespq=maven+logo Our current logo, with a single highlighted letter stands out quite well from the other maven logos, so keeping a highlighted letter and an italic rendered font maintains continuity with our current logo. By changing the highlighted letter to the `v` and by using two Apache feathers to create the `v`, we connect our logo back to Apache... we are Apache Maven after all. The `v` is also the common short term for version (e.g.v3 is short for version 3). Apache Maven puts a lot of emphasis on versions of dependencies and plugins... you could say that versions are very important to Maven. The colours of the feather were changed to solid colours to match the owl mascot's scarf, beak and eyebrows Voting rules = Anyone who is subscribed to the dev or users list is eligible to vote. If you vote multiple times, only your final vote will be counted. The vote will be open until 1:00pm GMT on Wed 3rd Dec 2014 The vote is for all three changes as one single change. Partial votes (e.g. for the logo but not the mascot, or vice-versa) will not be counted. I, as the caller of the vote, reserve the right to cancel the vote if this vote is putting the harmony of the community at risk. If a majority of the PMC believe that this vote is putting the harmony of the community at risk, then the PMC may cancel this vote (though if even a small minority of the PMC were of that belief, I will more than likely have cancelled the vote before the PMC would need to decide... I'm just stating this FTR) The decision will be a simple majority, there will be no special veto powers. +1: [ ] Change the logo to the proposed logo and adopt the owl as project mascot 0: [ ] No opinion -1: [ ] No change Please only respond with +1, 0 or -1. If you want to discuss the proposed changes please use a different thread. This thread is for voting only. -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[DISCUSS] Design by committee
On 25 November 2014 at 14:31, Ralph Goers ralph.go...@dslextreme.com wrote: -1 - only because a) I don’t understand the purpose of what is going on on the bird’s chest and https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcSmbWMy3KPTNcnuorFhjAJABm6Al8mGBu8pMsxf8mmljydrIR4O https://encrypted-tbn1.gstatic.com/images?q=tbn:ANd9GcT24xwn6POkIGDYTCiTQV-Mplu-S7Cd1tRtgiraaZb9VutICnW1 just two photos of owls that a quick GIS revealed where the feathers on the owls belly are typically a lighter colour or a different pattern from the rest of the owl. Originally this was a white patch... people objected... The scalloping is to give the feather effect... and there are two sets of scalloping because any single sold colour results in the shotgun effect Some people go extra cute and make the center section a heart https://encrypted-tbn1.gstatic.com/images?q=tbn:ANd9GcQlwk2CQuHz9q9alG8iY5BDiC0mqWOpJBdIMmxXO7nZpN7xhWP1LA Others go for a different colour with more explicit feather imagery https://encrypted-tbn1.gstatic.com/images?q=tbn:ANd9GcSVOyxAkja3O_JbGfsKAhwAVFHS1fNUblq3NiT8IxAgE6waH-ARcA We want something different from others... and I like this end result... b) I love the idea of putting the bird in a sweater with the letter “M” on it. My skills of an artist did not give a good rendition... I did try though. If my skills were better perhaps I could have delivered such an owl... maybe somebody will contribute a version where CK removes his glasses and turns into super-owl Ralph On Nov 25, 2014, at 5:05 AM, Andreas Gudian andreas.gud...@gmail.com wrote: +1 Am Dienstag, 25. November 2014 schrieb Stephen Connolly : For anyone who has been living under a rock, here is the background Background = I think everyone can agree that the site needs a reorganisation and a rewrite. Users cannot find what they need, and the end result is that people keep on abusing maven rather than having maven help them. Try as I might, I have been unable to motivate myself to do the reorganisation with the current dated look and feel of the site... I am not saying that picking a new logo and selecting a mascot will result in making progress, but it can't hurt and I believe it will help Proposed changes === 1. Change the logo font to Alte Haas Grotesk Bold with italics applied by Inkscape 2. Change the highlighted letter from 'a' to 'v' and replace the v with two Apache Feathers 3. Adopt the (currently unnamed) owl as our mascot Here is a link to the font: http://www.dafont.com/alte-haas-grotesk.font Here is a large version of the owl and the logo: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png A regular version of the own and the logo, e.g. a size suitable for use in the top of the standard maven sites: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final.png (Note that in all likelihood, the mascot would probably end up on the other side of the title bar from the logo... and that is IF the mascot ends up on the title bar) Here is both of those rendered in a site (as it can be helpful to see the graphics adjacent to text) http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-context.png Logo Rational === If we do some searches for the Maven logo: https://www.google.com/search?site=imghptbm=ischq=maven+logooq=maven+logo http://www.bing.com/images/search?q=maven+logogo=Submitqs=nform=QBLHscope=imagespq=maven+logo Our current logo, with a single highlighted letter stands out quite well from the other maven logos, so keeping a highlighted letter and an italic rendered font maintains continuity with our current logo. By changing the highlighted letter to the `v` and by using two Apache feathers to create the `v`, we connect our logo back to Apache... we are Apache Maven after all. The `v` is also the common short term for version (e.g.v3 is short for version 3). Apache Maven puts a lot of emphasis on versions of dependencies and plugins... you could say that versions are very important to Maven. The colours of the feather were changed to solid colours to match the owl mascot's scarf, beak and eyebrows Voting rules = Anyone who is subscribed to the dev or users list is eligible to vote. If you vote multiple times, only your final vote will be counted. The vote will be open until 1:00pm GMT on Wed 3rd Dec 2014 The vote is for all three changes as one single change. Partial votes (e.g. for the logo but not the mascot, or vice-versa) will not be counted. I, as the caller of the vote, reserve the right to cancel the vote if this vote is putting the harmony of the community at risk. If a majority of the PMC believe that this vote is putting the harmony of the community at risk, then the PMC may cancel this vote
Re: [VOTE] Change project logo and adopt owl as mascot
+1 really like the new logo (or better any of those owls). LieGrue, strub On Tuesday, 25 November 2014, 12:02, Arnaud Héritier aherit...@gmail.com wrote: +1 thx On Tue, Nov 25, 2014 at 11:57 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1 On 25 November 2014 at 10:57, Stephen Connolly stephen.alan.conno...@gmail.com wrote: For anyone who has been living under a rock, here is the background Background = I think everyone can agree that the site needs a reorganisation and a rewrite. Users cannot find what they need, and the end result is that people keep on abusing maven rather than having maven help them. Try as I might, I have been unable to motivate myself to do the reorganisation with the current dated look and feel of the site... I am not saying that picking a new logo and selecting a mascot will result in making progress, but it can't hurt and I believe it will help Proposed changes === 1. Change the logo font to Alte Haas Grotesk Bold with italics applied by Inkscape 2. Change the highlighted letter from 'a' to 'v' and replace the v with two Apache Feathers 3. Adopt the (currently unnamed) owl as our mascot Here is a link to the font: http://www.dafont.com/alte-haas-grotesk.font Here is a large version of the owl and the logo: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png A regular version of the own and the logo, e.g. a size suitable for use in the top of the standard maven sites: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final.png (Note that in all likelihood, the mascot would probably end up on the other side of the title bar from the logo... and that is IF the mascot ends up on the title bar) Here is both of those rendered in a site (as it can be helpful to see the graphics adjacent to text) http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-context.png Logo Rational === If we do some searches for the Maven logo: https://www.google.com/search?site=imghptbm=ischq=maven+logooq=maven+logo http://www.bing.com/images/search?q=maven+logogo=Submitqs=nform=QBLHscope=imagespq=maven+logo Our current logo, with a single highlighted letter stands out quite well from the other maven logos, so keeping a highlighted letter and an italic rendered font maintains continuity with our current logo. By changing the highlighted letter to the `v` and by using two Apache feathers to create the `v`, we connect our logo back to Apache... we are Apache Maven after all. The `v` is also the common short term for version (e.g.v3 is short for version 3). Apache Maven puts a lot of emphasis on versions of dependencies and plugins... you could say that versions are very important to Maven. The colours of the feather were changed to solid colours to match the owl mascot's scarf, beak and eyebrows Voting rules = Anyone who is subscribed to the dev or users list is eligible to vote. If you vote multiple times, only your final vote will be counted. The vote will be open until 1:00pm GMT on Wed 3rd Dec 2014 The vote is for all three changes as one single change. Partial votes (e.g. for the logo but not the mascot, or vice-versa) will not be counted. I, as the caller of the vote, reserve the right to cancel the vote if this vote is putting the harmony of the community at risk. If a majority of the PMC believe that this vote is putting the harmony of the community at risk, then the PMC may cancel this vote (though if even a small minority of the PMC were of that belief, I will more than likely have cancelled the vote before the PMC would need to decide... I'm just stating this FTR) The decision will be a simple majority, there will be no special veto powers. +1: [ ] Change the logo to the proposed logo and adopt the owl as project mascot 0: [ ] No opinion -1: [ ] No change Please only respond with +1, 0 or -1. If you want to discuss the proposed changes please use a different thread. This thread is for voting only. -Stephen -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Change project logo and adopt owl as mascot
+1 non-binding Dan From: Paul Benedict pbened...@apache.org Subject: Re: [VOTE] Change project logo and adopt owl as mascot Date: November 25, 2014 at 9:43:41 AM EST To: Maven Developers List dev@maven.apache.org +1 non-binding Cheers, Paul - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Adapting checkstyle rules ?
Can one of you checkstyle gurus tell me how to disable the checkstyle rules that enforce bad practice ? I'm referring to the checkstyle meaningless javadoc required rule, how do I disable it permanently ? Preferably in the parent pom :) Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] In the event of adopting the owl as project mascot, what will we call it?
On Tuesday, November 25, 2014, Jeroen Hoek jer...@lable.org wrote: I would recommend leaving it without a name. I think that the name Pandora's box is already open, I suspect in the absence of a concrete alternative, shotgun will be the name The mascot can help in providing Maven with a stronger visual identity, but I'm not convinced naming it is helpful. On the contrary, it might come across as 'silly' or 'unprofessional', which for me goes against the nature of Maven: a mature tool many use as one of the steps towards stabilizing and professionalizing their code base. Why not call it simply 'The Maven Owl'? Ok, we'll add that suggestion into the pot. Kind regards, Jeroen Hoek Lable 2014-11-25 12:05 GMT+01:00 Stephen Connolly stephen.alan.conno...@gmail.com javascript:;: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png When I created this owl, I gave it the name Couché Tard which is a french nickname for an owl (literal translation: Sleeps Late) Early versions of this owl have ended up with the nickname Shotgun Owl due to the belly feathers being white in the initial versions, which some people thought made it look like it had been shot. Some people feel that we shouldn't name a mascot... As creator of the graphic, I could force the issue... but I would much rather if the community has a name that the community wants. Please provide your suggestions in this thread. If the owl is adopted as a mascot, we will have a second vote thread to confirm its name. I personally recommend a gender neutral name. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: users-h...@maven.apache.org javascript:; -- Sent from my phone
Re: [DISCUSS] In the event of adopting the owl as project mascot, what will we call it?
I really don't think we need to name the owl, do we? Are we just naming it for fun or is there a reason we want to? Cheers, Paul On Tue, Nov 25, 2014 at 1:23 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On Tuesday, November 25, 2014, Jeroen Hoek jer...@lable.org wrote: I would recommend leaving it without a name. I think that the name Pandora's box is already open, I suspect in the absence of a concrete alternative, shotgun will be the name The mascot can help in providing Maven with a stronger visual identity, but I'm not convinced naming it is helpful. On the contrary, it might come across as 'silly' or 'unprofessional', which for me goes against the nature of Maven: a mature tool many use as one of the steps towards stabilizing and professionalizing their code base. Why not call it simply 'The Maven Owl'? Ok, we'll add that suggestion into the pot. Kind regards, Jeroen Hoek Lable 2014-11-25 12:05 GMT+01:00 Stephen Connolly stephen.alan.conno...@gmail.com javascript:;: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png When I created this owl, I gave it the name Couché Tard which is a french nickname for an owl (literal translation: Sleeps Late) Early versions of this owl have ended up with the nickname Shotgun Owl due to the belly feathers being white in the initial versions, which some people thought made it look like it had been shot. Some people feel that we shouldn't name a mascot... As creator of the graphic, I could force the issue... but I would much rather if the community has a name that the community wants. Please provide your suggestions in this thread. If the owl is adopted as a mascot, we will have a second vote thread to confirm its name. I personally recommend a gender neutral name. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: users-h...@maven.apache.org javascript:; -- Sent from my phone
Re: [VOTE] Change project logo and adopt owl as mascot
-1 Am 2014-11-25 um 11:57 schrieb Stephen Connolly: For anyone who has been living under a rock, here is the background Background = I think everyone can agree that the site needs a reorganisation and a rewrite. Users cannot find what they need, and the end result is that people keep on abusing maven rather than having maven help them. Try as I might, I have been unable to motivate myself to do the reorganisation with the current dated look and feel of the site... I am not saying that picking a new logo and selecting a mascot will result in making progress, but it can't hurt and I believe it will help Proposed changes === 1. Change the logo font to Alte Haas Grotesk Bold with italics applied by Inkscape 2. Change the highlighted letter from 'a' to 'v' and replace the v with two Apache Feathers 3. Adopt the (currently unnamed) owl as our mascot Here is a link to the font: http://www.dafont.com/alte-haas-grotesk.font Here is a large version of the owl and the logo: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png A regular version of the own and the logo, e.g. a size suitable for use in the top of the standard maven sites: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final.png (Note that in all likelihood, the mascot would probably end up on the other side of the title bar from the logo... and that is IF the mascot ends up on the title bar) Here is both of those rendered in a site (as it can be helpful to see the graphics adjacent to text) http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-context.png Logo Rational === If we do some searches for the Maven logo: https://www.google.com/search?site=imghptbm=ischq=maven+logooq=maven+logo http://www.bing.com/images/search?q=maven+logogo=Submitqs=nform=QBLHscope=imagespq=maven+logo Our current logo, with a single highlighted letter stands out quite well from the other maven logos, so keeping a highlighted letter and an italic rendered font maintains continuity with our current logo. By changing the highlighted letter to the `v` and by using two Apache feathers to create the `v`, we connect our logo back to Apache... we are Apache Maven after all. The `v` is also the common short term for version (e.g.v3 is short for version 3). Apache Maven puts a lot of emphasis on versions of dependencies and plugins... you could say that versions are very important to Maven. The colours of the feather were changed to solid colours to match the owl mascot's scarf, beak and eyebrows Voting rules = Anyone who is subscribed to the dev or users list is eligible to vote. If you vote multiple times, only your final vote will be counted. The vote will be open until 1:00pm GMT on Wed 3rd Dec 2014 The vote is for all three changes as one single change. Partial votes (e.g. for the logo but not the mascot, or vice-versa) will not be counted. I, as the caller of the vote, reserve the right to cancel the vote if this vote is putting the harmony of the community at risk. If a majority of the PMC believe that this vote is putting the harmony of the community at risk, then the PMC may cancel this vote (though if even a small minority of the PMC were of that belief, I will more than likely have cancelled the vote before the PMC would need to decide... I'm just stating this FTR) The decision will be a simple majority, there will be no special veto powers. +1: [ ] Change the logo to the proposed logo and adopt the owl as project mascot 0: [ ] No opinion -1: [ ] No change - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] In the event of adopting the owl as project mascot, what will we call it?
From the peanut gallery: someone had complained that the owl as a mascot disregarded the Yiddish origin of the term Maven. How about naming the owl something like Abraham, Jacob, or Moses? :D Matt On Tue, Nov 25, 2014 at 5:05 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png When I created this owl, I gave it the name Couché Tard which is a french nickname for an owl (literal translation: Sleeps Late) Early versions of this owl have ended up with the nickname Shotgun Owl due to the belly feathers being white in the initial versions, which some people thought made it look like it had been shot. Some people feel that we shouldn't name a mascot... As creator of the graphic, I could force the issue... but I would much rather if the community has a name that the community wants. Please provide your suggestions in this thread. If the owl is adopted as a mascot, we will have a second vote thread to confirm its name. I personally recommend a gender neutral name. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] In the event of adopting the owl as project mascot, what will we call it?
Am 2014-11-25 um 20:56 schrieb Matt Benson: From the peanut gallery: someone had complained that the owl as a mascot disregarded the Yiddish origin of the term Maven. How about naming the owl something like Abraham, Jacob, or Moses? :D That was me and I still highly dislike the connection between the owl (Greek wisdom) and Yiddish background. This always leads me the same question: Why the owl? Having sad that, I would love to see a stylized version of a Woody Allen type: http://popchassid.wpengine.netdna-cdn.com/wp-content/uploads/2013/07/maxresdefault.jpg Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] In the event of adopting the owl as project mascot, what will we call it?
How about a rabbinical owl? Matt On Tue, Nov 25, 2014 at 2:07 PM, Michael Osipov micha...@apache.org wrote: Am 2014-11-25 um 20:56 schrieb Matt Benson: From the peanut gallery: someone had complained that the owl as a mascot disregarded the Yiddish origin of the term Maven. How about naming the owl something like Abraham, Jacob, or Moses? :D That was me and I still highly dislike the connection between the owl (Greek wisdom) and Yiddish background. This always leads me the same question: Why the owl? Having sad that, I would love to see a stylized version of a Woody Allen type: http://popchassid.wpengine.netdna-cdn.com/wp-content/uploads/2013/07/maxresdefault.jpg Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Abandoned bugs analysis
Hi Michael Unfortunatelly, I think that 2 years of inactivity is way to short time. I wish it wasn't so, but the reality is that the age of an issue is not a good indicator of whether the issue is valid or not. I think a better approach is to have joint bug scrub sessions, where we join forces to manually check the validity of the issues. -- Dennis Lundberg Den 24 nov 2014 23:05 skrev Michael Osipov micha...@apache.org: Hi folks, I ran this query in JIRA: project in projectsWhereUserHasPermission(Administer Projects) AND updated = 2012-12-31 and resolution = Unresolved and type = Bug ORDER BY created desc Bugs which haven't been touched for almost two years. Total amount: *1139*. A lot of them are still Maven 1.x related 8-). Is there someone with bulk change abilities able to close those as Won't Fix with a note like: Big clean up end of 2014, you think that this issue still persists, reopen it? What do you think? Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Abandoned bugs analysis
Am 2014-11-24 um 23:05 schrieb Michael Osipov: Hi folks, I ran this query in JIRA: project in projectsWhereUserHasPermission(Administer Projects) AND updated = 2012-12-31 and resolution = Unresolved and type = Bug ORDER BY created desc Bugs which haven't been touched for almost two years. Total amount: *1139*. A lot of them are still Maven 1.x related 8-). Is there someone with bulk change abilities able to close those as Won't Fix with a note like: Big clean up end of 2014, you think that this issue still persists, reopen it? I have now updated/closed hundreds of bugs which have not been touched for more than two years. A lot of them were Maven 1.x related. I have closed any bug some one of you have been assigned and you still think you can resolve it, reopen! Thanks, Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Abandoned bugs analysis
Am 2014-11-25 um 22:03 schrieb Dennis Lundberg: Hi Michael Unfortunatelly, I think that 2 years of inactivity is way to short time. I wish it wasn't so, but the reality is that the age of an issue is not a good indicator of whether the issue is valid or not. I think a better approach is to have joint bug scrub sessions, where we join forces to manually check the validity of the issues. Hi Dennis, you might be absolutely right but which timeframe is the right one? Three years? Four years? You cannot determine for a bulk update. A joint bug scrub is a better way -- yes but discussing 1500 bugs takes weeks. I already got the first reopen requests. As long as you you can always reopen an issue and someone reacts on the closure, aren't we good then? The point is to drag attention from the reporter. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] In the event of adopting the owl as project mascot, what will we call it?
:-D that would either look funny or ridiculous but worth evaluating. Are you or is someone else able provide a rendering which a Jewish-looking owl? Woody Allen style, for example. Michael Am 2014-11-25 um 21:51 schrieb Matt Benson: How about a rabbinical owl? Matt On Tue, Nov 25, 2014 at 2:07 PM, Michael Osipov micha...@apache.org wrote: Am 2014-11-25 um 20:56 schrieb Matt Benson: From the peanut gallery: someone had complained that the owl as a mascot disregarded the Yiddish origin of the term Maven. How about naming the owl something like Abraham, Jacob, or Moses? :D That was me and I still highly dislike the connection between the owl (Greek wisdom) and Yiddish background. This always leads me the same question: Why the owl? Having sad that, I would love to see a stylized version of a Woody Allen type: http://popchassid.wpengine.netdna-cdn.com/wp-content/uploads/2013/07/maxresdefault.jpg Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Abandoned bugs analysis
I don't agree. This is a project, not a product and if no one looks at something for 2 years then no one cares. We are not erasing the issues and if someone does care enough to ask to reopen an issue then that's great. But I've tried to purge down the list to something manageable twice now and it keeps growing so I highly appreciate what Michael is doing because it's unmanageable right now. And now that he's done that I have some motivation again to look through the issues so kudos to Michael. Nothing stops anyone from going through and reopening something, I don't think we need group scrubbing sessions. I think core committers need to go through and help curate the issues on a more regular basis. On Nov 25, 2014, at 4:03 PM, Dennis Lundberg denn...@apache.org wrote: Hi Michael Unfortunatelly, I think that 2 years of inactivity is way to short time. I wish it wasn't so, but the reality is that the age of an issue is not a good indicator of whether the issue is valid or not. I think a better approach is to have joint bug scrub sessions, where we join forces to manually check the validity of the issues. -- Dennis Lundberg Den 24 nov 2014 23:05 skrev Michael Osipov micha...@apache.org: Hi folks, I ran this query in JIRA: project in projectsWhereUserHasPermission(Administer Projects) AND updated = 2012-12-31 and resolution = Unresolved and type = Bug ORDER BY created desc Bugs which haven't been touched for almost two years. Total amount: *1139*. A lot of them are still Maven 1.x related 8-). Is there someone with bulk change abilities able to close those as Won't Fix with a note like: Big clean up end of 2014, you think that this issue still persists, reopen it? What do you think? Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - the course of true love never did run smooth ... -- Shakespeare
Re: Abandoned bugs analysis
Thanks for the praise Jason. Highly appreciated. Am 2014-11-25 um 22:22 schrieb Jason van Zyl: I don't agree. This is a project, not a product and if no one looks at something for 2 years then no one cares. We are not erasing the issues and if someone does care enough to ask to reopen an issue then that's great. But I've tried to purge down the list to something manageable twice now and it keeps growing so I highly appreciate what Michael is doing because it's unmanageable right now. And now that he's done that I have some motivation again to look through the issues so kudos to Michael. Nothing stops anyone from going through and reopening something, I don't think we need group scrubbing sessions. I think core committers need to go through and help curate the issues on a more regular basis. On Nov 25, 2014, at 4:03 PM, Dennis Lundberg denn...@apache.org wrote: Hi Michael Unfortunatelly, I think that 2 years of inactivity is way to short time. I wish it wasn't so, but the reality is that the age of an issue is not a good indicator of whether the issue is valid or not. I think a better approach is to have joint bug scrub sessions, where we join forces to manually check the validity of the issues. -- Dennis Lundberg Den 24 nov 2014 23:05 skrev Michael Osipov micha...@apache.org: Hi folks, I ran this query in JIRA: project in projectsWhereUserHasPermission(Administer Projects) AND updated = 2012-12-31 and resolution = Unresolved and type = Bug ORDER BY created desc Bugs which haven't been touched for almost two years. Total amount: *1139*. A lot of them are still Maven 1.x related 8-). Is there someone with bulk change abilities able to close those as Won't Fix with a note like: Big clean up end of 2014, you think that this issue still persists, reopen it? What do you think? Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - the course of true love never did run smooth ... -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Abandoned bugs analysis
One postive response from MECLIPSE-196: Perfectly happy this was closed, happy we're not using EARs any more. Can't wait to see new things coming from takari. Am 2014-11-25 um 22:22 schrieb Jason van Zyl: I don't agree. This is a project, not a product and if no one looks at something for 2 years then no one cares. We are not erasing the issues and if someone does care enough to ask to reopen an issue then that's great. But I've tried to purge down the list to something manageable twice now and it keeps growing so I highly appreciate what Michael is doing because it's unmanageable right now. And now that he's done that I have some motivation again to look through the issues so kudos to Michael. Nothing stops anyone from going through and reopening something, I don't think we need group scrubbing sessions. I think core committers need to go through and help curate the issues on a more regular basis. On Nov 25, 2014, at 4:03 PM, Dennis Lundberg denn...@apache.org wrote: Hi Michael Unfortunatelly, I think that 2 years of inactivity is way to short time. I wish it wasn't so, but the reality is that the age of an issue is not a good indicator of whether the issue is valid or not. I think a better approach is to have joint bug scrub sessions, where we join forces to manually check the validity of the issues. -- Dennis Lundberg Den 24 nov 2014 23:05 skrev Michael Osipov micha...@apache.org: Hi folks, I ran this query in JIRA: project in projectsWhereUserHasPermission(Administer Projects) AND updated = 2012-12-31 and resolution = Unresolved and type = Bug ORDER BY created desc Bugs which haven't been touched for almost two years. Total amount: *1139*. A lot of them are still Maven 1.x related 8-). Is there someone with bulk change abilities able to close those as Won't Fix with a note like: Big clean up end of 2014, you think that this issue still persists, reopen it? What do you think? Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - the course of true love never did run smooth ... -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Abandoned bugs analysis
We did this bug clean up before so this isn't new to me. However, I do wonder if the resolution Won't Fix rubs people the wrong way? Maybe if we had an Abandoned resolution that would sit better. Aside from reading the comments in the ticket, it's not possible to know what was closed truly because something is intended never to be fixed and what was closed due to age. Cheers, Paul On Tue, Nov 25, 2014 at 3:58 PM, Michael Osipov micha...@apache.org wrote: One postive response from MECLIPSE-196: Perfectly happy this was closed, happy we're not using EARs any more. Can't wait to see new things coming from takari. Am 2014-11-25 um 22:22 schrieb Jason van Zyl: I don't agree. This is a project, not a product and if no one looks at something for 2 years then no one cares. We are not erasing the issues and if someone does care enough to ask to reopen an issue then that's great. But I've tried to purge down the list to something manageable twice now and it keeps growing so I highly appreciate what Michael is doing because it's unmanageable right now. And now that he's done that I have some motivation again to look through the issues so kudos to Michael. Nothing stops anyone from going through and reopening something, I don't think we need group scrubbing sessions. I think core committers need to go through and help curate the issues on a more regular basis. On Nov 25, 2014, at 4:03 PM, Dennis Lundberg denn...@apache.org wrote: Hi Michael Unfortunatelly, I think that 2 years of inactivity is way to short time. I wish it wasn't so, but the reality is that the age of an issue is not a good indicator of whether the issue is valid or not. I think a better approach is to have joint bug scrub sessions, where we join forces to manually check the validity of the issues. -- Dennis Lundberg Den 24 nov 2014 23:05 skrev Michael Osipov micha...@apache.org: Hi folks, I ran this query in JIRA: project in projectsWhereUserHasPermission (Administer Projects) AND updated = 2012-12-31 and resolution = Unresolved and type = Bug ORDER BY created desc Bugs which haven't been touched for almost two years. Total amount: *1139*. A lot of them are still Maven 1.x related 8-). Is there someone with bulk change abilities able to close those as Won't Fix with a note like: Big clean up end of 2014, you think that this issue still persists, reopen it? What do you think? Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - the course of true love never did run smooth ... -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Abandoned bugs analysis
Am 2014-11-25 um 23:05 schrieb Paul Benedict: We did this bug clean up before so this isn't new to me. However, I do wonder if the resolution Won't Fix rubs people the wrong way? Maybe if we had an Abandoned resolution that would sit better. Aside from reading the comments in the ticket, it's not possible to know what was closed truly because something is intended never to be fixed and what was closed due to You mean: Status 'closed' and resolution 'abandoned'? Feel free to open up a thread about the ticket transition workflow (resolution field) we currently have. This is worth discussing. On Tue, Nov 25, 2014 at 3:58 PM, Michael Osipov micha...@apache.org wrote: One postive response from MECLIPSE-196: Perfectly happy this was closed, happy we're not using EARs any more. Can't wait to see new things coming from takari. Am 2014-11-25 um 22:22 schrieb Jason van Zyl: I don't agree. This is a project, not a product and if no one looks at something for 2 years then no one cares. We are not erasing the issues and if someone does care enough to ask to reopen an issue then that's great. But I've tried to purge down the list to something manageable twice now and it keeps growing so I highly appreciate what Michael is doing because it's unmanageable right now. And now that he's done that I have some motivation again to look through the issues so kudos to Michael. Nothing stops anyone from going through and reopening something, I don't think we need group scrubbing sessions. I think core committers need to go through and help curate the issues on a more regular basis. On Nov 25, 2014, at 4:03 PM, Dennis Lundberg denn...@apache.org wrote: Hi Michael Unfortunatelly, I think that 2 years of inactivity is way to short time. I wish it wasn't so, but the reality is that the age of an issue is not a good indicator of whether the issue is valid or not. I think a better approach is to have joint bug scrub sessions, where we join forces to manually check the validity of the issues. -- Dennis Lundberg Den 24 nov 2014 23:05 skrev Michael Osipov micha...@apache.org: Hi folks, I ran this query in JIRA: project in projectsWhereUserHasPermission (Administer Projects) AND updated = 2012-12-31 and resolution = Unresolved and type = Bug ORDER BY created desc Bugs which haven't been touched for almost two years. Total amount: *1139*. A lot of them are still Maven 1.x related 8-). Is there someone with bulk change abilities able to close those as Won't Fix with a note like: Big clean up end of 2014, you think that this issue still persists, reopen it? What do you think? Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - the course of true love never did run smooth ... -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] In the event of adopting the owl as project mascot, what will we call it?
Heh, I don't draw anymore but it wouldn't seem that hard for a good cartoonist. Matt On Tue, Nov 25, 2014 at 3:20 PM, Michael Osipov micha...@apache.org wrote: :-D that would either look funny or ridiculous but worth evaluating. Are you or is someone else able provide a rendering which a Jewish-looking owl? Woody Allen style, for example. Michael Am 2014-11-25 um 21:51 schrieb Matt Benson: How about a rabbinical owl? Matt On Tue, Nov 25, 2014 at 2:07 PM, Michael Osipov micha...@apache.org wrote: Am 2014-11-25 um 20:56 schrieb Matt Benson: From the peanut gallery: someone had complained that the owl as a mascot disregarded the Yiddish origin of the term Maven. How about naming the owl something like Abraham, Jacob, or Moses? :D That was me and I still highly dislike the connection between the owl (Greek wisdom) and Yiddish background. This always leads me the same question: Why the owl? Having sad that, I would love to see a stylized version of a Woody Allen type: http://popchassid.wpengine.netdna-cdn.com/wp-content/uploads/2013/07/maxresdefault.jpg Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Abandoned bugs analysis
+1 for Abandoned or Archived. Won't Fix implies that some one has actually looked at it. -Chris Sent from my iPhone On 26/11/2014, at 9:05 AM, Paul Benedict pbened...@apache.org wrote: We did this bug clean up before so this isn't new to me. However, I do wonder if the resolution Won't Fix rubs people the wrong way? Maybe if we had an Abandoned resolution that would sit better. Aside from reading the comments in the ticket, it's not possible to know what was closed truly because something is intended never to be fixed and what was closed due to age. Cheers, Paul On Tue, Nov 25, 2014 at 3:58 PM, Michael Osipov micha...@apache.org wrote: One postive response from MECLIPSE-196: Perfectly happy this was closed, happy we're not using EARs any more. Can't wait to see new things coming from takari. Am 2014-11-25 um 22:22 schrieb Jason van Zyl: I don't agree. This is a project, not a product and if no one looks at something for 2 years then no one cares. We are not erasing the issues and if someone does care enough to ask to reopen an issue then that's great. But I've tried to purge down the list to something manageable twice now and it keeps growing so I highly appreciate what Michael is doing because it's unmanageable right now. And now that he's done that I have some motivation again to look through the issues so kudos to Michael. Nothing stops anyone from going through and reopening something, I don't think we need group scrubbing sessions. I think core committers need to go through and help curate the issues on a more regular basis. On Nov 25, 2014, at 4:03 PM, Dennis Lundberg denn...@apache.org wrote: Hi Michael Unfortunatelly, I think that 2 years of inactivity is way to short time. I wish it wasn't so, but the reality is that the age of an issue is not a good indicator of whether the issue is valid or not. I think a better approach is to have joint bug scrub sessions, where we join forces to manually check the validity of the issues. -- Dennis Lundberg Den 24 nov 2014 23:05 skrev Michael Osipov micha...@apache.org: Hi folks, I ran this query in JIRA: project in projectsWhereUserHasPermission (Administer Projects) AND updated = 2012-12-31 and resolution = Unresolved and type = Bug ORDER BY created desc Bugs which haven't been touched for almost two years. Total amount: *1139*. A lot of them are still Maven 1.x related 8-). Is there someone with bulk change abilities able to close those as Won't Fix with a note like: Big clean up end of 2014, you think that this issue still persists, reopen it? What do you think? Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - the course of true love never did run smooth ... -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[LOGO] site with Fluido skin and owl logo
I created a branch in svn to test in my own browser https://svn.apache.org/repos/asf/maven/site/branches/fluido/ and here is the mvn site result: http://people.apache.org/~hboutemy/site-fluido-owl/ HTH Regards, Hervé - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Adapting checkstyle rules ?
the Maven Checkstyle coding style is written inside maven-checkstyle-plugin see svn [1] And when working on version 2.13, I created a dedicated component in Jira to track updates [2] Notice MCHECKSTYLE-257 to better document this for the next plugin version... Regards, Hervé [1] http://svn.apache.org/viewvc/maven/plugins/trunk/maven-checkstyle-plugin/src/main/resources/config/maven_checks.xml [2] http://jira.codehaus.org/browse/MCHECKSTYLE/component/16600 Le mardi 25 novembre 2014 19:33:11 Kristian Rosenvold a écrit : Can one of you checkstyle gurus tell me how to disable the checkstyle rules that enforce bad practice ? I'm referring to the checkstyle meaningless javadoc required rule, how do I disable it permanently ? Preferably in the parent pom :) Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [LOGO] site with Fluido skin and owl logo
Look great! Gary On Tue, Nov 25, 2014 at 11:22 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: I created a branch in svn to test in my own browser https://svn.apache.org/repos/asf/maven/site/branches/fluido/ and here is the mvn site result: http://people.apache.org/~hboutemy/site-fluido-owl/ HTH Regards, Hervé - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition http://www.manning.com/bauer3/ JUnit in Action, Second Edition http://www.manning.com/tahchiev/ Spring Batch in Action http://www.manning.com/templier/ Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
Re: Adapting checkstyle rules ?
Kristian,
For simplicity, and the ability to re-use the checkstyle configuration in a
multi-module reactor, I usually do this in two steps:
1. Create a codestyle project in the root level of your project. This
codestyle project contains the configuration files for checkstyle where the
codestyle within the project is defined (i.e.
src/main/resources/codestyle/checkstyle-suppressions.xml and
src/main/resources/codestyle/checkstyle.xml).
2. In your root pom, simply configure the checkstyle plugin to use your
custom checkstyle.xml. Example snippet below.
You can see an example of this in the nazgul-codestyle project and
nazgul-tools-parent pom respectively. Published on repo central.
!-- Checkstyle configuration parameters. --
checkstyle.plugin.version2.12/checkstyle.plugin.version
*checkstyle.config.locationcodestyle/checkstyle.xml/checkstyle.config.location
checkstyle.suppressions.locationcodestyle/checkstyle-suppressions.xml/checkstyle.suppressions.location*
checkstyle.violationSeverityerror/checkstyle.violationSeverity
and ...
!--Enforces the defined code
style, as provided within the codestyle project.
Why: Validates the codestyle.Used: Standard
lifecycle, mvn package.--plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-checkstyle-plugin/artifactId
version${checkstyle.plugin.version}/version
configuration
skip${skip.verify.code}/skip
configLocation${checkstyle.config.location}/configLocation
suppressionsFile${checkstyle.suppressions.location}/suppressionsFile
failOnViolation${breakOnFailure.checkstyle}/failOnViolation
violationSeverity${checkstyle.violationSeverity}/violationSeverity
/configurationexecutions
execution
idverify/id
phase${check.plugins.phase}/phase
goalsgoalcheck/goal
/goals/execution
executionidreport/id
goals
goalcheckstyle/goal/goals
/execution/executions
dependencies*dependency
groupIdse.jguru.nazgul.tools.codestyle/groupId
artifactIdnazgul-codestyle/artifactId
version4.0.1/version
/dependency*
/dependencies/plugin
2014-11-25 19:33 GMT+01:00 Kristian Rosenvold kristian.rosenv...@gmail.com
:
Can one of you checkstyle gurus tell me how to disable the checkstyle
rules that enforce bad practice ?
I'm referring to the checkstyle meaningless javadoc required rule,
how do I disable it permanently ?
Preferably in the parent pom :)
Kristian
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
--
+==+
| Bästa hälsningar,
| [sw. Best regards]
|
| Lennart Jörelid
| EAI Architect Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: l...@jguru.se
| URL: www.jguru.se
| Phone
| (skype):jgurueurope
| (intl): +46 708 507 603
| (domestic): 0708 - 507 603
+==+
