Simon Kitching wrote:
On Tue, 2005-06-14 at 13:12 +1200, Simon Kitching wrote:
And
the lack of bugzilla entries and user/development questions also implies
that Jelly is fine as-is.
umm .. the lack of Bugzilla entries is probably because Jelly uses
Jira :-(.
Jira has quite a few bug entries (73).
It looks like there are quite a few bugs that really should be addressed
before a 1.0 release because it looks to me like they have the potential
to change Jelly behaviour - after a 1.0 release, that would mean going
to 2.0 I believe.
Well, this was dicussed last Oct when it came time to prepare the first
release candidate, and that they would be targetted at a 1.1 or 2.0
depending on whether they would break things. I think those that are
using Jelly now deserve a release that is stable.
On the other hand, we need to consider that Jelly have any regular
maintainers. And if Maven2 moves to Marmalade (marmalade.codehaus.org)
instead of Jelly the developer pool will drop even further.
I'm the only Maven developer here, and my involvement in Jelly has
really been ensuring it did maintain compat with Maven 1.
To clear up a common misconception - Maven 2 is not "moving to"
Marmalade over Jelly. Maven 1 is based on Jelly and Ant. None of that is
bound to the core of Maven 2 - you can use Marmalade just like you can
use Beanshell and plain Java components. You could also plug Jelly in,
or Groovy, or others, if there was demand. Existing Jelly scripts
wouldn't work with Maven 2 anyway (different goal architecture), but if
someone had a reason to want to integrate Jelly there is no reason they
couldn't - and all the code could just as easily live in the Jelly
libraries.
My point - I would look to the people using Jelly for other purposes to
decide it's future beyond 1.0. There are certainly a few of them here
already, and they are already the most active.
So saying no
to a 1.0 release now may mean saying no to a 1.0 release forever -
despite the fact that Jelly is clearly useable for many purposes right
now. I don't know which is the best choice...
I think it is best to stick with 1.0 for now. From a purely Maven
perspective, it's unlikely to survive any Jelly API changes, and it
would be a shame to have to finish on a snapshot build, where it started :)
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
