> Am 19.05.2017 um 15:50 schrieb Oliver Heger <oliver.he...@oliver-heger.de>: > > Hi, > > thank you for looking into this. > > Am 18.05.2017 um 16:46 schrieb Benedikt Ritter: >> Hi, >> >>> Am 17.05.2017 um 19:38 schrieb Gary Gregory <garydgreg...@gmail.com >>> <mailto:garydgreg...@gmail.com>>: >>> >>> I think that we could, as a community test of interest, say something like, >>> if Oliver wants to push out what is in trunk in the next 30 days or so (or >>> 60 or 90), we will help. I would help with odds and ends. Aside from that, >>> if no one cares enough to "do", then let's hibernate it. >> >> I’m currently having a look at the code base. There is a lot of work to do. >> I’m currently trying to fix the build to republish the website. Here are the >> things I discovered: >> >> - dependencies are out dated >> - mixture of build files: build.xml, project.xml, maven.xml, pom.xml (can we >> drop all but pom.xml?) > Yes, IMHO keeping only pom.xml should be fine. > >> - missing maven plugin „maven-jellydoc-plugin“. It seems to be part of the >> code base, but the build is not configured to generate it >> - strange structure of the project with several source folders (src and >> jelly-tags) > Somehow the tag libs were treated as separate modules, but probably in a > layout compliant to Maven 1.x. > >> >> But these are all things that can be fixed, given people find the time to >> work on this :-) >> > We might also think about the minimum Java version we want to support. > As the project has been unmaintained for such a long time, I assume we > are pretty free to switch to a modern version as nobody expects an update. > > It might even be beneficial to switch to Java 8. I can imagine that > lambda syntax could be used in an elegant way to create simple tags.
I think Bruno needs Jelly for Jenkins. So we need to make sure it can be used within Jenkins. Benedikt > > Oliver > >> Regards, >> Benedikt >> >>> >>> Gary >>> >>> On Wed, May 17, 2017 at 1:37 PM, Benedikt Ritter <brit...@apache.org> wrote: >>> >>>> Hey guys, >>>> >>>> this is just the reaction I’m looking for. I think it is important to poke >>>> in the hole every once in a while and see if anybody is still interested in >>>> a component. If you have intends to work on Jelly, there is no reason to >>>> move it to dormant. >>>> >>>> I’ll wait for the 72 hours to pass anyway to see whether there are even >>>> more people who still need jelly. >>>> >>>> Cheers, >>>> Benedikt >>>> >>>>> Am 17.05.2017 um 15:46 schrieb Bruno P. Kinoshita <ki...@apache.org>: >>>>> >>>>> Ditto for my -1. I've always wanted to move Jenkins fork patches back to >>>> Jelly, but last time I worked on it Mavenizing the project and its >>>> components took too much time. >>>>> Bruno >>>>> >>>>> Sent from Yahoo Mail on Android >>>>> >>>>> On Thu, May 18, 2017 at 7:34, Oliver Heger<oliver.he...@oliver-heger.de> >>>> wrote: Hm, >>>>> >>>>> being a user of Jelly, I have the long-term goal to contribute to the >>>>> project because I have indeed some itch to scratch, but unfortunately >>>>> never got to it. >>>>> >>>>> So I am -1, but I cannot promise that I can work on Jelly in the near >>>>> future. >>>>> >>>>> Oliver >>>>> >>>>> Am 17.05.2017 um 20:26 schrieb Benedikt Ritter: >>>>>> Hi, >>>>>> >>>>>> I think we should move Apache Commons Jelly to dormant for the >>>> following reasons: >>>>>> >>>>>> - Jelly hasn’t seen any activity in a while. There haven’t been any >>>> relevant commits since 2010 (I didn’t search the history further than >>>> that…) >>>>>> - The last release dates back to 2005. >>>>>> - There is no activity in Jira or on our mailing lists. >>>>>> >>>>>> For this reason I’m calling a vote by lazy consensus for moving Apache >>>> Commons Jelly to dormant. This vote will pass if nobody objects within the >>>> next 72 hours, e.g. after 20-May 2017 14:30 EDT (UTC-4). >>>>>> >>>>>> Regards, >>>>>> Benedikt >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>>> >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>> >>>> >>> >>> >>> -- >>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >>> Java Persistence with Hibernate, Second Edition >>> <https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8> >>> >>> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459> >>> JUnit in Action, Second Edition >>> <https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22> >>> >>> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021> >>> Spring Batch in Action >>> <https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action> >>> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951> >>> Blog: http://garygregory.wordpress.com >>> Home: http://garygregory.com/ >>> Tweet! http://twitter.com/GaryGregory >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > <mailto:dev-unsubscr...@commons.apache.org> > For additional commands, e-mail: dev-h...@commons.apache.org > <mailto:dev-h...@commons.apache.org>
