jerome lacoste wrote:
> Note I am not trying to be a pain in the butt here.
:) I meant I know the fact that the issue could have been moved up to
2.0.1 was the pain, not you.
> I am just saying
> that there was something that could have been done better and that I
> hope won't happen again.
I'
On 2/1/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> jerome lacoste wrote:
> > Sorry but it's not marked as such in Jira
> >
> > http://jira.codehaus.org/browse/MASSEMBLY-19
> >
> > Component/s: None
> > Affects Version/s:None
> > Fix Version/s:None
> >
>
> I know its a pain i
jerome lacoste wrote:
> Sorry but it's not marked as such in Jira
>
> http://jira.codehaus.org/browse/MASSEMBLY-19
>
> Component/s: None
> Affects Version/s:None
> Fix Version/s:None
>
I know its a pain in the butt, but I will reiterate. We created the JIRA
projects *after
On 1/30/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> As I explained in response to your previous message, we already do that.
> You fixes were scheduled for, and always have been scheduled for 2.1.
Sorry but it's not marked as such in Jira
http://jira.codehaus.org/browse/MASSEMBLY-19
Component/
As I explained in response to your previous message, we already do that.
You fixes were scheduled for, and always have been scheduled for 2.1.
2.1 has not been delayed in any way. 2.0.1 was pushed up with some bug
fixes that were represented as more critical.
As soon as the outstanding 2.1 bugs/f
"When a milestone is about to be released, there should probably be a
way for us bug reporters to know. That's why I proposed to use Jira:
targeting an issue to a future release will notify me and I can react."
+1
-
To unsubsc
Hi,
I've had a little issue with regard to the latest release of maven
assembly plugin. Mostly because some issues I had reported and fixed
almost 3 months ago didn't make it into the release.
So I am being told that 1- there was a description of the issues to be
fixed, and 2- there was a 72h vot
