Hi,
We're still actively using Jelly and while the usefulness of some of the
extension modules may be debatable (and definitely without wishing to enter
into a debate of whether it is appropriate to have "executable" data), as a
core tool Jelly has allowed us to rapidly produce pluggable languages for
defining drawings, web services, schedules, JDBC configuration, and more
where the tag implementation configures POJOs.
Coincidentally, we've recently reached the point where we must make changes
to the code base (bug fixes and new features) and so a couple of weeks ago I
emailed James asking if he was still maintaining the project and if so what
is plans were and whether I'd be able to contribute. Perhaps not
surprisingly I didn't receive a reply, and now it seems I might have broken
protocol by asking him direct instead of asking here. My apologies if that
was inappropriate.
We have a number of changes to make to Jelly, and I am prepared to put
myself and my company forward as a maintainer. If that's acceptable to you
all, the first task would be to briefly update the website and make a
maintenance release (there are some essential bug fixes in SVN that are not
in the official release), followed by various other fixes and additions in a
beta release. Admittedly, my focus would be the core of Jelly and the core
tags - I do not use the additional tag libraries and would find it difficult
to provide a significant amount of regression testing and support for them
but I'll keep them going where possible and try to help out any users with
problems.
Is this something you would be interested in? If the conclusion by the list
is that Jelly should still be retired then as an alternative would it be
possible for me to fork the Jelly project out of commons and into (for
example) SourceForge?
In case it makes a difference, I am not currently an Apache committer.
Regards,
John
----- Original Message -----
From: "Henri Yandell" <[EMAIL PROTECTED]>
To: "Commons Developers List" <dev@commons.apache.org>; <[EMAIL PROTECTED]>
Sent: Friday, November 07, 2008 12:00 AM
Subject: Re: [jelly] Is jelly still in development
On Thu, Nov 6, 2008 at 3:11 PM, ralph.goers @dslextreme.com
<[EMAIL PROTECTED]> wrote:
On Thu, Nov 6, 2008 at 11:44 AM, Henri Yandell <[EMAIL PROTECTED]>
wrote:
I'm thinking we should:
a) remove from trunks-proper
b) Update the homepage to say "Not Actively Maintained"
c) Update the Commons homepage to put this into a release subcategory
of "Not Actively Maintained"
d) Put said N.A.M. note on the JIRA page.
Thoughts?
If it is removed from trunks-proper where does it go?
trunks-proper is a dir of svn:externals, so it's not lost just not in
our active development set.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
