Am 2014-11-23 um 03:42 schrieb Hervé BOUTEMY:
IMHO, just open another Jira issue and make the proper fix (with existing ITs)
I head this in my too, the question is. How do we want to unify that.
Do we want everywhere:
g:a:v or Unnamed -- g:a:v?
That would count for the module report as well
Am 2014-11-22 um 20:58 schrieb Karl Heinz Marbaise:
Hi,
i'm trying to upgrade maven-ejb-plugin from maven-archiver 2.5 to
maven-archiver-2.6and i'm currently faced with a puzzling situation...
If i update to 2.6 several tests will fail...
For the tests there were stubs generated which
Hi folks,
while merging my local Git clone of maven.git I have noticed that some
trailing whitespace has been added to the repo. I performed some shell
magic:
find . -type f -name '*.extensions' -exec grep -E -l +$ {} \; |
xargs -I{} sed -i -e 's/ \+$//' {}
I have pushed the branch
Le dimanche 23 novembre 2014 15:58:56 Michael Osipov a écrit :
Hi folks,
while merging my local Git clone of maven.git I have noticed that some
trailing whitespace has been added to the repo. I performed some shell
magic:
find . -type f -name '*.extensions' -exec grep -E -l +$ {} \; |
Le dimanche 23 novembre 2014 10:27:12 Michael Osipov a écrit :
Am 2014-11-23 um 03:42 schrieb Hervé BOUTEMY:
IMHO, just open another Jira issue and make the proper fix (with existing
ITs)
I head this in my too, the question is. How do we want to unify that.
Do we want everywhere:
g:a:v
Am 2014-11-23 um 16:56 schrieb Hervé BOUTEMY:
Le dimanche 23 novembre 2014 15:58:56 Michael Osipov a écrit :
Hi folks,
while merging my local Git clone of maven.git I have noticed that some
trailing whitespace has been added to the repo. I performed some shell
magic:
find . -type f -name
Hi,
I stumbled upon MPMD-193 and rejected to apply the provided patch.
Version 5.1.1 introduced in CPD a postConstruct method which
intentionally modifies system variables just because someone was too
lazy to pass encoding to file readers:
Hi folks,
this has been itching me for quite some time now. Once in a while, I
check our JIRA projects for open issues and try to evaluate them for
fixability, etc. While some reporters respond after a question, some
never do.
I'd like to propose to close a ticket as *Incomplete* when the
+1
On Sunday, November 23, 2014, Michael Osipov micha...@apache.org wrote:
Hi folks,
this has been itching me for quite some time now. Once in a while, I check
our JIRA projects for open issues and try to evaluate them for fixability,
etc. While some reporters respond after a question, some
+1
Good idea. I err on the side of expunging to reduce the foot print. If the
person cares enough they will come back. There's a lot of gorp in JIRA.
On Nov 23, 2014, at 2:05 PM, Michael Osipov micha...@apache.org wrote:
Hi folks,
this has been itching me for quite some time now. Once in a
I think this is a very good idea. But I have seen this mis-used a few
times in other projects, and I think we want to avoid this scenario:
There are some bugs that have very well written bug reports with
detailed descriptions on reproduction and/or quite a few watchers too.
I've seen this rule
Hi,
+1 from me to...
On 11/23/14 8:48 PM, Kristian Rosenvold wrote:
I think this is a very good idea. But I have seen this mis-used a few
times in other projects, and I think we want to avoid this scenario:
There are some bugs that have very well written bug reports with
detailed descriptions
Hi,
On 11/23/14 10:27 AM, Michael Osipov wrote:
Am 2014-11-22 um 20:58 schrieb Karl Heinz Marbaise:
Hi,
i'm trying to upgrade maven-ejb-plugin from maven-archiver 2.5 to
maven-archiver-2.6and i'm currently faced with a puzzling
situation...
If i update to 2.6 several tests will fail...
+1
Le dimanche 23 novembre 2014 21:34:31 Karl Heinz Marbaise a écrit :
Hi,
+1 from me to...
On 11/23/14 8:48 PM, Kristian Rosenvold wrote:
I think this is a very good idea. But I have seen this mis-used a few
times in other projects, and I think we want to avoid this scenario:
On 23 November 2014 at 19:48, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
I think this is a very good idea. But I have seen this mis-used a few
times in other projects, and I think we want to avoid this scenario:
There are some bugs that have very well written bug reports with
I am also slightly sceptical of carpet-bombing jira with this stuff;
once we request more test data we're also giving the expectation that
someone /will/ be looking at the additional data that the user has
supplied. So I would be expecting whoever triages with this method to
also
Am 2014-11-23 um 22:32 schrieb Stephen Connolly:
On 23 November 2014 at 19:48, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
I think this is a very good idea. But I have seen this mis-used a few
times in other projects, and I think we want to avoid this scenario:
There are some bugs
Am 2014-11-23 um 22:33 schrieb Benson Margulies:
I am also slightly sceptical of carpet-bombing jira with this stuff;
once we request more test data we're also giving the expectation that
someone /will/ be looking at the additional data that the user has
supplied. So I would be expecting
On 23 November 2014 at 02:53, Hervé BOUTEMY herve.bout...@free.fr wrote:
Le samedi 22 novembre 2014 19:22:29 Benson Margulies a écrit :
I suggest that we ask Sally is there is any donated graphic design
assistance available. I suspect that there is.
+1
If somebody else wants to take a
Am 2014-11-23 um 20:48 schrieb Kristian Rosenvold:
I think this is a very good idea. But I have seen this mis-used a few
times in other projects, and I think we want to avoid this scenario:
There are some bugs that have very well written bug reports with
detailed descriptions on reproduction
Am 2014-11-23 um 22:59 schrieb Stephen Connolly:
On 23 November 2014 at 02:53, Hervé BOUTEMY herve.bout...@free.fr wrote:
Le samedi 22 novembre 2014 19:22:29 Benson Margulies a écrit :
I suggest that we ask Sally is there is any donated graphic design
assistance available. I suspect that
On 23 November 2014 at 21:33, Benson Margulies bimargul...@gmail.com
wrote:
I am also slightly sceptical of carpet-bombing jira with this stuff;
once we request more test data we're also giving the expectation that
someone /will/ be looking at the additional data that the user has
My suggestion at this point is:
1. Ask Sally if we can get professional help.
2. If there is none, or it endorses the Owl, or produces something we hate,
go with the owl.
3. as per Michael, don't name the Owl at all. Don't name the awl at owl?
On Sun, Nov 23, 2014 at 5:04 PM, Michael Osipov
Le dimanche 23 novembre 2014 19:53:10 Michael Osipov a écrit :
Hi,
I stumbled upon MPMD-193 and rejected to apply the provided patch.
Version 5.1.1 introduced in CPD a postConstruct method which
intentionally modifies system variables just because someone was too
lazy to pass encoding to
At m2e, we automatically close bugs that have not seen a meaningful
movement for 12+ months. This helps keep our bug backlog manageable and
m2e users seems to be content with this policy for the most part.
We don't have development resources to fix every single problem in our
projects, so we
On Sunday, November 23, 2014, Benson Margulies bimargul...@gmail.com
wrote:
My suggestion at this point is:
1. Ask Sally if we can get professional help.
I take it you're stepping up to do that ;-)
2. If there is none, or it endorses the Owl, or produces something we hate,
go with the
Sally,
The Maven community would like to update and improve its graphic design. I
wondered, based on the work on the overall Foundation site, where there was
any donated professional assistance of this kind available to individual
communities. We have some volunteer efforts in the direction of a
I like the owl, but why not just make the body a solid color? To me it now
looks like one of those fancy “haircuts’ people get where they have something
shaved into their head.
Ralph
On Nov 20, 2014, at 2:43 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
Stop calling
Why does the owl need chest hair? (or whatever the oval patch is supposed to
represent).
Ralph
On Nov 23, 2014, at 2:59 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 23 November 2014 at 02:53, Hervé BOUTEMY herve.bout...@free.fr
mailto:herve.bout...@free.fr wrote:
Le
Will the graphic be in PNG format so the shotgun stomach can be
transparent.?
Cheers,
Paul
On Sun, Nov 23, 2014 at 9:11 PM, Ralph Goers ralph.go...@dslextreme.com
wrote:
I like the owl, but why not just make the body a solid color? To me it
now looks like one of those fancy “haircuts’
Hey Benson --thanks so much for your note.
Unfortunately, our donated resources are extremely limited; I'm not sure how
we'll be proceeding with the proposed Foundation work given the level of
feedback to incorporate.
Having said that, several Apache projects, such as Logging, were seeking a
On 24 Nov 2014, at 16:20, Ralph Goers wrote:
Why does the owl need chest hair? (or whatever the oval patch is supposed to
represent).
You've heard of Yak Shaving right? Well this is so we maven guys have something
to shave when we're fighting dependency hell :)
--
Mark Derricutt
Github user mizdebsk closed the pull request at:
https://github.com/apache/maven-scm/pull/25
---
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
On Monday, November 24, 2014, Ralph Goers ralph.go...@dslextreme.com
wrote:
Why does the owl need chest hair? (or whatever the oval patch is supposed
to represent).
An owl does not *need* the patch of lighter coloured feathers that most
owls seem to have on their belly...
However, if you
34 matches
Mail list logo
