Re: Integrate Maven Site reporting with maven plugin that externally create report html page.

[Hervé BOUTEMY]

that's the purpose of isExternalReport() method of reporting-api: [1]

Just implement it as "return true;" and no content will be generated by m-
site-p/Doxia: it is expected that the tool will generated the page

you can have a look at m-javadoc-p, that's exactly what is done here

Regards,

Hervé

[1] 
http://maven.apache.org/shared/maven-reporting-api/apidocs/org/apache/maven/reporting/MavenReport.html

Le mercredi 26 novembre 2014 14:42:03 animator a écrit :
> I'm developing maven plugin
> (https://github.com/lgadawski/cloverage-maven-plugin). This plugin produces
> code coverage report for clojure sources from project. This report (html
> page) is generated by cloverage (clojure library as dependency in my maven
> plugin). The problem is that I would like to link this generated html file
> to maven site reporting section. Is that possible to achieve this
> automagically? Any suggestions?
> My Mojo extends AbstractMavenReport and after calling 'mvn site' I get link
> in "Project Reports" section. How to link there generated earlier html page?
> 
> Thanks for any ansewrs!
> 
> 
> 
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Integrate-Maven-Site-reporting-with-maven-> 
> plugin-that-externally-create-report-html-page-tp5817068.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

[Stephane Nicoll]

+1

On Tuesday, November 25, 2014, 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=imghp&tbm=isch&q=maven+logo&oq=maven+logo
>
>
> http://www.bing.com/images/search?q=maven+logo&go=Submit&qs=n&form=QBLH&scope=images&pq=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
>


-- 
Sent from my phone

Re: [VOTE] Change project logo and adopt owl as mascot

[Olivier Lamy]

+1

I reckon you have some designer skills!! :P

On 25 November 2014 at 21:57, Stephen Connolly
 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=imghp&tbm=isch&q=maven+logo&oq=maven+logo
>
> http://www.bing.com/images/search?q=maven+logo&go=Submit&qs=n&form=QBLH&scope=images&pq=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



-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Ticket Transition Workflow: Abandoned issues

[David Jencks]

In my work life use of RTC Backlog means "needs to be investigated by a 
developer".  I think Cancelled as Incomplete might be a closer RTC match to the 
meaning we are looking for here.

david jencks

On Nov 26, 2014, at 2:14 PM, Chris Graham  wrote:

> RTC uses Backlog. Does Jira have something similar?
> 
> Sent from my iPhone
> 
> On 27/11/2014, at 8:13 AM, David Jencks  
> wrote:
> 
>> Retired rather than Archived?
>> 
>> This cleanup seems like a really good idea :-)
>> 
>> david jencks
>> 
>> On Nov 26, 2014, at 12:41 PM, Paul Benedict  wrote:
>> 
>>> My 2-cents on the word "Archived" is that it's a synonym for
>>> Backup/Storage, which I don't think is what this process is about.
>>> 
>>> 
>>> Cheers,
>>> Paul
>>> 
>>> On Wed, Nov 26, 2014 at 1:57 PM, Michael Osipov  wrote:
>>> 
 Am 2014-11-26 um 16:16 schrieb Paul Benedict:
 
> This email is related to thread "Abandoned bug analysis" [1].
> 
> We have done the Great Ticket Cleanup of 2014 twice this year. It has
> really been productive for anyone who triages outstanding bugs and
> enhancements. We've been adding a note in the ticket, as a courtesy to the
> participants, and closing them as "Won't Fix".
> 
> This is certainly one valid way of accomplishing the goal. However, I do
> believe we should enhance our workflow by adding an "Abandoned" (my fav)
> or
> "Archived" resolution. Why? Because "Won't Fix" is typically is used to
> close out a bug that will never be fixed (i.e., too many people rely on
> the
> bad behavior) or the enhancement is deemed worthless or incorrect. But
> more
> importantly, it's not possible to do a JIRA search and distinguish between
> these two conditions unless a new resolution is introduced.
> 
 
 We need two new things:
 
 1. Status: Awaiting Feedback (not just labels).
 2. Resolution: Archived
 
 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: Ticket Transition Workflow: Abandoned issues

[Jörg Schaible]

Stephen Connolly wrote:

> I think we can add whatever states we want.
> 
> These are not Backlog though
> 
> They are perhaps "Stale" or "Inactive/Unconfirmed"
> 
> Just need a label that communicates the ticket as closed due to no
> response and no clear report"

Incomplete ;-)

> 
> On Wednesday, November 26, 2014, Chris Graham 
> wrote:
> 
>> RTC uses Backlog. Does Jira have something similar?
>>
>> Sent from my iPhone
>>
>> On 27/11/2014, at 8:13 AM, David Jencks 
>> wrote:
>>
>> > Retired rather than Archived?
>> >
>> > This cleanup seems like a really good idea :-)
>> >
>> > david jencks
>> >
>> > On Nov 26, 2014, at 12:41 PM, Paul Benedict > > wrote:
>> >
>> >> My 2-cents on the word "Archived" is that it's a synonym for
>> >> Backup/Storage, which I don't think is what this process is about.
>> >>
>> >>
>> >> Cheers,
>> >> Paul
>> >>
>> >> On Wed, Nov 26, 2014 at 1:57 PM, Michael Osipov > > wrote:
>> >>
>> >>> Am 2014-11-26 um 16:16 schrieb Paul Benedict:
>> >>>
>>  This email is related to thread "Abandoned bug analysis" [1].
>> 
>>  We have done the Great Ticket Cleanup of 2014 twice this year. It
>>  has really been productive for anyone who triages outstanding bugs
>>  and enhancements. We've been adding a note in the ticket, as a
>>  courtesy
>> to the
>>  participants, and closing them as "Won't Fix".
>> 
>>  This is certainly one valid way of accomplishing the goal. However,
>>  I
>> do
>>  believe we should enhance our workflow by adding an "Abandoned" (my
>> fav)
>>  or
>>  "Archived" resolution. Why? Because "Won't Fix" is typically is used
>> to
>>  close out a bug that will never be fixed (i.e., too many people rely
>> on
>>  the
>>  bad behavior) or the enhancement is deemed worthless or incorrect.
>>  But more
>>  importantly, it's not possible to do a JIRA search and distinguish
>> between
>>  these two conditions unless a new resolution is introduced.
>> 
>> >>>
>> >>> We need two new things:
>> >>>
>> >>> 1. Status: Awaiting Feedback (not just labels).
>> >>> 2. Resolution: Archived
>> >>>
>> >>> 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: Ticket Transition Workflow: Abandoned issues

[Stephen Connolly]

I think we can add whatever states we want.

These are not Backlog though

They are perhaps "Stale" or "Inactive/Unconfirmed"

Just need a label that communicates the ticket as closed due to no response
and no clear report"

On Wednesday, November 26, 2014, Chris Graham  wrote:

> RTC uses Backlog. Does Jira have something similar?
>
> Sent from my iPhone
>
> On 27/11/2014, at 8:13 AM, David Jencks 
> wrote:
>
> > Retired rather than Archived?
> >
> > This cleanup seems like a really good idea :-)
> >
> > david jencks
> >
> > On Nov 26, 2014, at 12:41 PM, Paul Benedict  > wrote:
> >
> >> My 2-cents on the word "Archived" is that it's a synonym for
> >> Backup/Storage, which I don't think is what this process is about.
> >>
> >>
> >> Cheers,
> >> Paul
> >>
> >> On Wed, Nov 26, 2014 at 1:57 PM, Michael Osipov  > wrote:
> >>
> >>> Am 2014-11-26 um 16:16 schrieb Paul Benedict:
> >>>
>  This email is related to thread "Abandoned bug analysis" [1].
> 
>  We have done the Great Ticket Cleanup of 2014 twice this year. It has
>  really been productive for anyone who triages outstanding bugs and
>  enhancements. We've been adding a note in the ticket, as a courtesy
> to the
>  participants, and closing them as "Won't Fix".
> 
>  This is certainly one valid way of accomplishing the goal. However, I
> do
>  believe we should enhance our workflow by adding an "Abandoned" (my
> fav)
>  or
>  "Archived" resolution. Why? Because "Won't Fix" is typically is used
> to
>  close out a bug that will never be fixed (i.e., too many people rely
> on
>  the
>  bad behavior) or the enhancement is deemed worthless or incorrect. But
>  more
>  importantly, it's not possible to do a JIRA search and distinguish
> between
>  these two conditions unless a new resolution is introduced.
> 
> >>>
> >>> We need two new things:
> >>>
> >>> 1. Status: Awaiting Feedback (not just labels).
> >>> 2. Resolution: Archived
> >>>
> >>> 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 
>
>

-- 
Sent from my phone

Re: Ticket Transition Workflow: Abandoned issues

[Chris Graham]

RTC uses Backlog. Does Jira have something similar?

Sent from my iPhone

On 27/11/2014, at 8:13 AM, David Jencks  wrote:

> Retired rather than Archived?
> 
> This cleanup seems like a really good idea :-)
> 
> david jencks
> 
> On Nov 26, 2014, at 12:41 PM, Paul Benedict  wrote:
> 
>> My 2-cents on the word "Archived" is that it's a synonym for
>> Backup/Storage, which I don't think is what this process is about.
>> 
>> 
>> Cheers,
>> Paul
>> 
>> On Wed, Nov 26, 2014 at 1:57 PM, Michael Osipov  wrote:
>> 
>>> Am 2014-11-26 um 16:16 schrieb Paul Benedict:
>>> 
 This email is related to thread "Abandoned bug analysis" [1].
 
 We have done the Great Ticket Cleanup of 2014 twice this year. It has
 really been productive for anyone who triages outstanding bugs and
 enhancements. We've been adding a note in the ticket, as a courtesy to the
 participants, and closing them as "Won't Fix".
 
 This is certainly one valid way of accomplishing the goal. However, I do
 believe we should enhance our workflow by adding an "Abandoned" (my fav)
 or
 "Archived" resolution. Why? Because "Won't Fix" is typically is used to
 close out a bug that will never be fixed (i.e., too many people rely on
 the
 bad behavior) or the enhancement is deemed worthless or incorrect. But
 more
 importantly, it's not possible to do a JIRA search and distinguish between
 these two conditions unless a new resolution is introduced.
 
>>> 
>>> We need two new things:
>>> 
>>> 1. Status: Awaiting Feedback (not just labels).
>>> 2. Resolution: Archived
>>> 
>>> 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: Ticket Transition Workflow: Abandoned issues

[Chris Graham]

Nicely worded!

+1

Sent from my iPhone

On 27/11/2014, at 2:16 AM, Paul Benedict  wrote:

> This email is related to thread "Abandoned bug analysis" [1].
> 
> We have done the Great Ticket Cleanup of 2014 twice this year. It has
> really been productive for anyone who triages outstanding bugs and
> enhancements. We've been adding a note in the ticket, as a courtesy to the
> participants, and closing them as "Won't Fix".
> 
> This is certainly one valid way of accomplishing the goal. However, I do
> believe we should enhance our workflow by adding an "Abandoned" (my fav) or
> "Archived" resolution. Why? Because "Won't Fix" is typically is used to
> close out a bug that will never be fixed (i.e., too many people rely on the
> bad behavior) or the enhancement is deemed worthless or incorrect. But more
> importantly, it's not possible to do a JIRA search and distinguish between
> these two conditions unless a new resolution is introduced.
> 
> So I'd like to officially propose a new resolution to address this concern.
> 
> [1]
> http://mail-archives.apache.org/mod_mbox/maven-dev/201411.mbox/%3c5473ab9b.4090...@apache.org%3E
> 
> Cheers,
> Paul

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Integrate Maven Site reporting with maven plugin that externally create report html page.

[animator]

I'm developing maven plugin
(https://github.com/lgadawski/cloverage-maven-plugin). This plugin produces
code coverage report for clojure sources from project. This report (html
page) is generated by cloverage (clojure library as dependency in my maven
plugin). The problem is that I would like to link this generated html file
to maven site reporting section. Is that possible to achieve this
automagically? Any suggestions? 
My Mojo extends AbstractMavenReport and after calling 'mvn site' I get link
in "Project Reports" section. How to link there generated earlier html page? 

Thanks for any ansewrs!



--
View this message in context: 
http://maven.40175.n5.nabble.com/Integrate-Maven-Site-reporting-with-maven-plugin-that-externally-create-report-html-page-tp5817068.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: [VOTE] Change project logo and adopt owl as mascot

[Mirko Friedenhagen]

+1
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/


On Wed, Nov 26, 2014 at 8:23 PM, Anders Hammar  wrote:
> +1
>
> /Anders
>
> On Tue, Nov 25, 2014 at 11:57 AM, 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=imghp&tbm=isch&q=maven+logo&oq=maven+logo
>>
>>
>> http://www.bing.com/images/search?q=maven+logo&go=Submit&qs=n&form=QBLH&scope=images&pq=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: Ticket Transition Workflow: Abandoned issues

[David Jencks]

Retired rather than Archived?

This cleanup seems like a really good idea :-)

david jencks

On Nov 26, 2014, at 12:41 PM, Paul Benedict  wrote:

> My 2-cents on the word "Archived" is that it's a synonym for
> Backup/Storage, which I don't think is what this process is about.
> 
> 
> Cheers,
> Paul
> 
> On Wed, Nov 26, 2014 at 1:57 PM, Michael Osipov  wrote:
> 
>> Am 2014-11-26 um 16:16 schrieb Paul Benedict:
>> 
>>> This email is related to thread "Abandoned bug analysis" [1].
>>> 
>>> We have done the Great Ticket Cleanup of 2014 twice this year. It has
>>> really been productive for anyone who triages outstanding bugs and
>>> enhancements. We've been adding a note in the ticket, as a courtesy to the
>>> participants, and closing them as "Won't Fix".
>>> 
>>> This is certainly one valid way of accomplishing the goal. However, I do
>>> believe we should enhance our workflow by adding an "Abandoned" (my fav)
>>> or
>>> "Archived" resolution. Why? Because "Won't Fix" is typically is used to
>>> close out a bug that will never be fixed (i.e., too many people rely on
>>> the
>>> bad behavior) or the enhancement is deemed worthless or incorrect. But
>>> more
>>> importantly, it's not possible to do a JIRA search and distinguish between
>>> these two conditions unless a new resolution is introduced.
>>> 
>> 
>> We need two new things:
>> 
>> 1. Status: Awaiting Feedback (not just labels).
>> 2. Resolution: Archived
>> 
>> 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: Ticket Transition Workflow: Abandoned issues

[Paul Benedict]

My 2-cents on the word "Archived" is that it's a synonym for
Backup/Storage, which I don't think is what this process is about.


Cheers,
Paul

On Wed, Nov 26, 2014 at 1:57 PM, Michael Osipov  wrote:

> Am 2014-11-26 um 16:16 schrieb Paul Benedict:
>
>> This email is related to thread "Abandoned bug analysis" [1].
>>
>> We have done the Great Ticket Cleanup of 2014 twice this year. It has
>> really been productive for anyone who triages outstanding bugs and
>> enhancements. We've been adding a note in the ticket, as a courtesy to the
>> participants, and closing them as "Won't Fix".
>>
>> This is certainly one valid way of accomplishing the goal. However, I do
>> believe we should enhance our workflow by adding an "Abandoned" (my fav)
>> or
>> "Archived" resolution. Why? Because "Won't Fix" is typically is used to
>> close out a bug that will never be fixed (i.e., too many people rely on
>> the
>> bad behavior) or the enhancement is deemed worthless or incorrect. But
>> more
>> importantly, it's not possible to do a JIRA search and distinguish between
>> these two conditions unless a new resolution is introduced.
>>
>
> We need two new things:
>
> 1. Status: Awaiting Feedback (not just labels).
> 2. Resolution: Archived
>
> Michael
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [DISCUSS] Design by committee

[Ralph Goers]

> On Nov 25, 2014, at 8:14 AM, Stephen Connolly 
>  wrote:
> 
> On 25 November 2014 at 14:31, Ralph Goers 
> 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
>  
> 

Nice photos!

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

This one actually looks like an owl to me.

> 
> Others go for a different colour with more explicit feather imagery
> 
> https://encrypted-tbn1.gstatic.com/images?q=tbn:ANd9GcSVOyxAkja3O_JbGfsKAhwAVFHS1fNUblq3NiT8IxAgE6waH-ARcA
>  
> 

Hmm. Looks like an owl wearing “old man” pants to me. ;-)

> 
> 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 
>> 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=imghp&tbm=isch&q=maven+logo&oq=maven+logo
 
 
 
>> http://www.bing.com/images/search?q=maven+logo&go=Submit&qs=n&form=QBLH&scope=images&pq=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
>> depend

Re: Ticket Transition Workflow: Abandoned issues

[Michael Osipov]

Am 2014-11-26 um 16:16 schrieb Paul Benedict:

This email is related to thread "Abandoned bug analysis" [1].

We have done the Great Ticket Cleanup of 2014 twice this year. It has
really been productive for anyone who triages outstanding bugs and
enhancements. We've been adding a note in the ticket, as a courtesy to the
participants, and closing them as "Won't Fix".

This is certainly one valid way of accomplishing the goal. However, I do
believe we should enhance our workflow by adding an "Abandoned" (my fav) or
"Archived" resolution. Why? Because "Won't Fix" is typically is used to
close out a bug that will never be fixed (i.e., too many people rely on the
bad behavior) or the enhancement is deemed worthless or incorrect. But more
importantly, it's not possible to do a JIRA search and distinguish between
these two conditions unless a new resolution is introduced.


We need two new things:

1. Status: Awaiting Feedback (not just labels).
2. Resolution: Archived

Michael

-
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

[Anders Hammar]

+1

/Anders

On Tue, Nov 25, 2014 at 11:57 AM, 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=imghp&tbm=isch&q=maven+logo&oq=maven+logo
>
>
> http://www.bing.com/images/search?q=maven+logo&go=Submit&qs=n&form=QBLH&scope=images&pq=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] Idle bug handling approach

[Michael Osipov]

Am 2014-11-26 um 18:05 schrieb tibor17:

Hi Michael,

I've seen that you are closing the issues in SUREFIRE according to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014

Do you want to make any new regulations in closing the bugs or you suppose
this mail discussion is closed by then?


Please rephrase your question. I do not understand what you have on your 
mind.


Michael


-
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

[Daniel Kulp]

+1

I like the owl.

Dan



> On Nov 25, 2014, at 5:57 AM, Stephen Connolly 
>  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=imghp&tbm=isch&q=maven+logo&oq=maven+logo
> 
> http://www.bing.com/images/search?q=maven+logo&go=Submit&qs=n&form=QBLH&scope=images&pq=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

-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven-wagon pull request: Prevent fingerprints loss in know_hosts

[marob]

GitHub user marob opened a pull request:

https://github.com/apache/maven-wagon/pull/16

Prevent fingerprints loss in know_hosts

Currently, when adding new fingerprints the whole know_hosts file is 
rewritten from the loaded fingerprints.
But only fingerprints with a compatible algorithm (from jsch point of view) 
are kept: for example, all "ecdsa-sha2-nistp256" are lost!

Hence this pull request that appends the new fingerprint in the known_hosts 
file (without modifying the rest of the file) and keeps unknown fingerprints 
with unknown algorithms.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/marob/maven-wagon master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-wagon/pull/16.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #16


commit f78c87d8916d1cea9572ae2921f9a588c9bfe0f1
Author: marob 
Date:   2014-11-26T17:46:32Z

Append in known_host instead of the current "clean and write" that
filters unknown formats (like ecdsa-sha2-nistp256)




---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
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

[Hilton Wichwski Silva]

+1

2014-11-26 10:48 GMT-02:00 Emilio Lopez :

> +1
>
> I love the new logo
>
> EmilioLLBB
>

Re: [DISCUSS] Idle bug handling approach

[tibor17]

Hi Michael,

I've seen that you are closing the issues in SUREFIRE according to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014

Do you want to make any new regulations in closing the bugs or you suppose
this mail discussion is closed by then?



-
BR, tibor17
--
View this message in context: 
http://maven.40175.n5.nabble.com/DISCUSS-Idle-bug-handling-approach-tp5815394p5817003.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: Abandoned bugs analysis

[Brian Fox]

+1 close em...

On Tue, Nov 25, 2014 at 4:22 PM, Jason van Zyl  wrote:
> 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  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" :
>>
>>> 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

Ticket Transition Workflow: Abandoned issues

[Paul Benedict]

This email is related to thread "Abandoned bug analysis" [1].

We have done the Great Ticket Cleanup of 2014 twice this year. It has
really been productive for anyone who triages outstanding bugs and
enhancements. We've been adding a note in the ticket, as a courtesy to the
participants, and closing them as "Won't Fix".

This is certainly one valid way of accomplishing the goal. However, I do
believe we should enhance our workflow by adding an "Abandoned" (my fav) or
"Archived" resolution. Why? Because "Won't Fix" is typically is used to
close out a bug that will never be fixed (i.e., too many people rely on the
bad behavior) or the enhancement is deemed worthless or incorrect. But more
importantly, it's not possible to do a JIRA search and distinguish between
these two conditions unless a new resolution is introduced.

So I'd like to officially propose a new resolution to address this concern.

[1]
http://mail-archives.apache.org/mod_mbox/maven-dev/201411.mbox/%3c5473ab9b.4090...@apache.org%3E

Cheers,
Paul

Re: [VOTE] Change project logo and adopt owl as mascot

[Emilio Lopez]

+1

I love the new logo

EmilioLLBB

[ANN] Apache Maven Assembly Plugin 2.5.2 Released

[Kristian Rosenvold]

The Apache Maven team is pleased to announce the release of the
Apache Maven Assembly Plugin, version 2.5.2.

The Assembly Plugin for Maven is primarily intended to allow users to aggregate
the project output along with its dependencies, modules, site documentation,
and other files into a single distributable archive.

Most notable for this release are:
Rewritten duplicate handling strategy, revised documentation. Please
note that previously documented strategy was mostly wishful thinking,
the currently documented strategy is hard reality :) See
http://maven.apache.org/plugins/maven-assembly-plugin/advanced-descriptor-topics.html

http://maven.apache.org/plugins/maven-assembly-plugin/


You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-assembly-plugin
  2.5.2



Release Notes - Maven Assembly Plugin - Version 2.5.2



** Bug
* [MASSEMBLY-478] - allow overwriting newer files with older files
contained within fileset
* [MASSEMBLY-558] - Assembly does not include runtime-dependency
if test-dependency with shorter path exists
* [MASSEMBLY-565] - jar-with-dependencies: class from the source
in project does NOT override the class in jar dependency
* [MASSEMBLY-569] - The numbering of the items in the FAQ on the
site is messed up
* [MASSEMBLY-580] - dependencySet ignores directoryMode descriptor
* [MASSEMBLY-583] - DependencySet elements appear not to be able
to target the same outputDirectory
* [MASSEMBLY-597] - Duplicate files added to archive when present
in both dependencyset and fileset of the same assembly
* [MASSEMBLY-601] -
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html
seems to have the components of a filter element in the wrong order
* [MASSEMBLY-609] - Misbehavior on multi-module projects,
outputDirectory not being interpolated properly
* [MASSEMBLY-655] - Archive file resolution does not work as documented
* [MASSEMBLY-671] - Cryptic debug warning message needs
improvement and/or documentation
* [MASSEMBLY-725] - Fix phase ordering
* [MASSEMBLY-726] - Fix artifact inclusion/exclusion filtering
* [MASSEMBLY-728] - Assembly plugin >= 2.5 thinks my group ID is too big
* [MASSEMBLY-729] - lineEnding ignored when file is not filtered
* [MASSEMBLY-730] - jar-with-dependencies : a file in a dependency
is overridden by the same file in JDK / JRE
* [MASSEMBLY-731] - Assembly plugin bundles symlinks as emtpy
folders when directoryMode is set on fileset
* [MASSEMBLY-732] - baseDirectory is ignored with files entries
* [MASSEMBLY-733] - Plugin no longer prepends final name when
packaging files specified using 'files/file' elements.



** Improvement
* [MASSEMBLY-702] - Add default values for directoryMode / fileMode
* [MASSEMBLY-708] - predefined descriptors lack of permission
definition for unix (directoryMode/fileMode)


Enjoy,

-The Apache Maven team

-
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

[Stephen Connolly]

If the vote is successful I'll commit the SVG originals, and we can slice
and dice, eg maybe keep the owl out of the top bar, add an owl favicon, and
rework the overly busy front page.

I also think we should remove the side-bars (and perhaps switch to a top
bar menu) as they hinder mobile accessibility. We can use hopscotch to let
people know where the stuff is, much like clicking the "Take a tour" button
on the junit.org site revamp I did.

On Wednesday, 26 November 2014, Hervé BOUTEMY  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: dev-unsubscr...@maven.apache.org 
> For additional commands, e-mail: dev-h...@maven.apache.org 
>
>

-- 
Sent from my phone