commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruno P. Kinoshita" <brunodepau...@yahoo.com.br>
Subject Re: [jelly] Working on some old issues
Date Fri, 01 May 2015 10:10:07 GMT
Jenkins supports Groovy as an alternative to Jelly too, so both UI template engines of Jenkins
are powered by Apache software :-) There's a comment on a problem they had with Groovy in
this Wiki page, and I want to take a look at the Groovy version in the incubator to see if
that's easy to reproduce/fix too.

 What I would like to see in the future in Jelly are extensions and enhancements to the project
to facilitate writing and debugging Jenkins plug-ins in Jelly. 

Thanks Benedikt!Bruno
[1] https://wiki.jenkins-ci.org/display/JENKINS/Groovy+View
 
      From: Benedikt Ritter <britter@apache.org>
 To: Commons Developers List <dev@commons.apache.org>; Bruno P. Kinoshita <brunodepaulak@yahoo.com.br>

 Sent: Friday, May 1, 2015 10:00 PM
 Subject: Re: [jelly] Working on some old issues
   
2015-05-01 10:22 GMT+02:00 Bruno P. Kinoshita <brunodepaulak@yahoo.com.br>:

> Hi all,
> Since I joined Commons I've had a special interest in [jelly] due to its
> importance in the Jenkins project.
>
> Jenkins uses a patched version of [jelly]. Kohsuke, creator of Jenkins,
> is/was a Commons committer too, and submitted some issues. I intend to
> investigate if that'd be doable fix the issues to a point that Jenkins can
> drop the patched version, and [jelly] can be updated and released again.
>
> Any objections?
>

I would love to see this kind of inter-project collaboration happen. Please
go ahead!




> Bruno
>
>


-- 
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter


   
 
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message