I'd much rather focus my efforts on the 1.0 branch.
Yes, it's taking time, but it has the least chance of suprising us with
unexpected issues.
I've seen radical implementation switches cost us lots of time before too,
and I don't believe we have anywhere near enough tests to cover the
current
e to have 1.0 out is that I am writing an article on
"How to
> Write a Maven Plugin" and it would be nice to have the 1.0 release be
out
> when the article is published ;-)
>
> Eric
>
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTE
t; To: Maven Developers List
> Subject: RE: Mini roadmap
>
>
> On Thu, 2003-12-04 at 18:18, Brett Porter wrote:
> > > This is not directed at you exclusively. It is directed at my
> > > first attempt, Dion's subsequent attempt and your attempt.
> > >
On Thu, 2003-12-04 at 18:18, Brett Porter wrote:
> > This is not directed at you exclusively. It is directed at my
> > first attempt, Dion's subsequent attempt and your attempt.
> > The problem with the attempts is that the core is so gory
> > that collaboration is difficult at best.
>
> I unde
> This is not directed at you exclusively. It is directed at my
> first attempt, Dion's subsequent attempt and your attempt.
> The problem with the attempts is that the core is so gory
> that collaboration is difficult at best.
I understand - I really meant to explain why it is currently stalle
On Thu, 2003-12-04 at 17:23, Brett Porter wrote:
> We need to stop changing the roadmap and decide now. I thought we'd already
> done that, but here goes again...
>
> The 3 options:
> 1) release MAVEN 1.0 RC1 as Maven 1.0 final with any non-plugin-context
> related bugs backported off the branch.
We need to stop changing the roadmap and decide now. I thought we'd already
done that, but here goes again...
The 3 options:
1) release MAVEN 1.0 RC1 as Maven 1.0 final with any non-plugin-context
related bugs backported off the branch. Kill the branch and start 1.1 with
the new model.
2) start in
On Thu, 2003-12-04 at 13:06, Vincent Massol wrote:
> Why not simply release Maven 1.0 now (from the 1.0 branch)? There are
> some limitations sure but they will be addressed in Maven 1.1.
That's what I recommended about a month ago and you were one of the
people who advised against that :-) I'm fi
Why not simply release Maven 1.0 now (from the 1.0 branch)? There are
some limitations sure but they will be addressed in Maven 1.1.
I think it's much less work (and less risky) than trying to create
something new altogether. I'm really worried by introducing completely
new code when we should act
