I'll be against the fact to loose our convention of having one Jira
project per component/plugin. It is a nightmare to manage everything
in a unique project ( have a look at Jenkins plugins)
I'll have a look at the HAUS issue tonight if possible. If it didn't
change I can administrate this jira.
C
On Sat, Sep 29, 2012 at 12:58 PM, Robert Scholte wrote:
> That would be the first Maven-project at issues.apache.org, right?
> Don't think that's very clear for users, assuming most of them already know
> their path to jira.codehaus.org.
As per Olamy's email, it's worse than that. The ASF JIRA In
That would be the first Maven-project at issues.apache.org, right?
Don't think that's very clear for users, assuming most of them already
know their path to jira.codehaus.org.
Op Sat, 29 Sep 2012 18:00:47 +0200 schreef Olivier Lamy :
I did https://jira.codehaus.org/browse/HAUS-2254
So as t
I did https://jira.codehaus.org/browse/HAUS-2254
So as the suggestion I did https://issues.apache.org/jira/browse/INFRA-5316
but INFRA folks @asf prefer not have a jira project per maven plugin.
So I'm lost :-)
I think I will reopen the HAUS one.
2012/9/29 Robert Scholte :
> Hi,
>
> could someone
Hi,
could someone create MSCMPUBLISH in Jira?
It seems like the first beta-users have some issues which they want to
register.
thanks,
Robert
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional command
+1 I see no reason to fumble with that stuff on foreign realms.
LieGrue,
strub
- Original Message -
> From: Olivier Lamy
> To: Maven Developers List
> Cc:
> Sent: Saturday, September 29, 2012 3:53 PM
> Subject: Re: PLXCOMP-1 and improving compiler-message parsing
>
> And that could
And that could be nice to such new components hosted @asf (maybe in
maven-shared)
2012/9/29 Olivier Lamy :
> Hi,
> Perso, I like the idea about using such pattern.
> That sounds a reasonable way to move forward.
>
> 2012/9/29 Kristian Rosenvold :
>> If I try to take a few steps back from this issu
Hi,
Perso, I like the idea about using such pattern.
That sounds a reasonable way to move forward.
2012/9/29 Kristian Rosenvold :
> If I try to take a few steps back from this issue; I wish there was
> some way we could just leave the old parsing logic as-is for 1.5 and
> make a cleaner fork that'
If I try to take a few steps back from this issue; I wish there was
some way we could just leave the old parsing logic as-is for 1.5 and
make a cleaner fork that'd be used for 1.6, maybe even some system
that could be extended to apply for 1.7 & 1.8 too ? I'm thinking along
the lines of what I did
+1 (non-binding).
Thanks
Le 29 sept. 2012 10:43, "Stephane Nicoll" a
écrit :
> +1
>
> Thanks,
> S.
>
> On Fri, Sep 28, 2012 at 8:08 AM, Dennis Lundberg
> wrote:
> > Hi,
> >
> > We solved 7 issues:
> >
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11150&styleName=Html&version=1829
+1
Thanks,
S.
On Fri, Sep 28, 2012 at 8:08 AM, Dennis Lundberg wrote:
> Hi,
>
> We solved 7 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11150&styleName=Html&version=18298
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigato
+1
Regards,
Hervé
Le vendredi 28 septembre 2012 08:08:20 Dennis Lundberg a écrit :
> Hi,
>
> We solved 7 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11150&styleName=H
> tml&version=18298
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/se
12 matches
Mail list logo
