[jelly] Working on some old issues

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

[jelly] Working on some old issues

Bruno P. Kinoshita
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?
Bruno

Reply | Threaded
Open this post in threaded view
|

Re: [jelly] Working on some old issues

Benedikt Ritter-4
2015-05-01 10:22 GMT+02:00 Bruno P. Kinoshita <[hidden email]>:

> 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
Reply | Threaded
Open this post in threaded view
|

Re: [jelly] Working on some old issues

Siegfried Goeschl-4
Go for it :-)

Siegfried Goeschl

> On 01 May 2015, at 12:00, Benedikt Ritter <[hidden email]> wrote:
>
> 2015-05-01 10:22 GMT+02:00 Bruno P. Kinoshita <[hidden email]>:
>
>> 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


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [jelly] Working on some old issues

Bruno P. Kinoshita
In reply to this post by Benedikt Ritter-4
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 <[hidden email]>
 To: Commons Developers List <[hidden email]>; Bruno P. Kinoshita <[hidden email]>
 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 <[hidden email]>:

> 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


   
 
Reply | Threaded
Open this post in threaded view
|

Re: [jelly] Working on some old issues

Paul Libbrecht-4
In reply to this post by Bruno P. Kinoshita

On 1/05/15 10:22, Bruno P. Kinoshita wrote:
> 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.

Hello Bruno,

if I remember well how the patches of Kohsuke landed, I remember I was
unable to apply them because they seemed to be breaking some of the
"standard command-line jelly". I think I remember that a pluggeable
context was discussed but, maybe, was not developed.

Thus, I can only encourage you to go ahead. I think it would be nice to
have both worlds working well with a single code base.

I have not been able to save cycles to address more issues of Jelly and
I know of some other folks, fellows in research in learning technology,
that were, looking forward to getting more releases of jelly at the time
I met them.

Hope it helps.
I am happy to help you if I can towards making it better.

paul



signature.asc (548 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [jelly] Working on some old issues

Bruno P. Kinoshita
Hi Paul
> if I remember well how the patches of Kohsuke landed, I remember I was
unable to apply them because they seemed to be breaking some of the
"standard command-line jelly". I think I remember that a pluggeable
context was discussed but, maybe, was not developed.
Any kind of background on old issues is welcome! Before I start to work on any issue,
I'll triage old issues, try to find some low hanging fruits, and then will start a one or two dayresearch on the mailing list to see if I can learn as much as possible before coding.
>I have not been able to save cycles to address more issues of Jelly and
I know of some other folks, fellows in research in learning technology,
that were, looking forward to getting more releases of jelly at the time
I met them.

I will work a little bit every weekend on triage issues, but will have a one or two week cyclein the middle of June and in July (lovely weather for coding; cold, cloudy, and raining a lot :)

>Hope it helps.
>I am happy to help you if I can towards making it better.

It definitely helps. Very happy for having someone I can ask questions about some old issuesin [jelly] :)
ThanksBruno

 
      From: Paul Libbrecht <[hidden email]>
 To: Commons Developers List <[hidden email]>
 Sent: Sunday, May 3, 2015 8:33 AM
 Subject: Re: [jelly] Working on some old issues
   



On 1/05/15 10:22, Bruno P. Kinoshita wrote:
> 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.

Hello Bruno,

if I remember well how the patches of Kohsuke landed, I remember I was
unable to apply them because they seemed to be breaking some of the
"standard command-line jelly". I think I remember that a pluggeable
context was discussed but, maybe, was not developed.

Thus, I can only encourage you to go ahead. I think it would be nice to
have both worlds working well with a single code base.

I have not been able to save cycles to address more issues of Jelly and
I know of some other folks, fellows in research in learning technology,
that were, looking forward to getting more releases of jelly at the time
I met them.

Hope it helps.
I am happy to help you if I can towards making it better.

paul



   
 
Reply | Threaded
Open this post in threaded view
|

Re: [jelly] Working on some old issues

sebb-2-2
I think the first job is to ensure that the build works with Maven2/3,
having tidied up the layout to conform with Maven2/3 conventions
(src/test/java and src/main/java etc).

I see that a start has been made, but it looks like there is some way to go yet.

On 10 May 2015 at 10:48, Bruno P. Kinoshita <[hidden email]> wrote:

> Hi Paul
>> if I remember well how the patches of Kohsuke landed, I remember I was
> unable to apply them because they seemed to be breaking some of the
> "standard command-line jelly". I think I remember that a pluggeable
> context was discussed but, maybe, was not developed.
> Any kind of background on old issues is welcome! Before I start to work on any issue,
> I'll triage old issues, try to find some low hanging fruits, and then will start a one or two dayresearch on the mailing list to see if I can learn as much as possible before coding.
>>I have not been able to save cycles to address more issues of Jelly and
> I know of some other folks, fellows in research in learning technology,
> that were, looking forward to getting more releases of jelly at the time
> I met them.
>
> I will work a little bit every weekend on triage issues, but will have a one or two week cyclein the middle of June and in July (lovely weather for coding; cold, cloudy, and raining a lot :)
>
>>Hope it helps.
>>I am happy to help you if I can towards making it better.
>
> It definitely helps. Very happy for having someone I can ask questions about some old issuesin [jelly] :)
> ThanksBruno
>
>
>       From: Paul Libbrecht <[hidden email]>
>  To: Commons Developers List <[hidden email]>
>  Sent: Sunday, May 3, 2015 8:33 AM
>  Subject: Re: [jelly] Working on some old issues
>
>
>
>
> On 1/05/15 10:22, Bruno P. Kinoshita wrote:
>> 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.
>
> Hello Bruno,
>
> if I remember well how the patches of Kohsuke landed, I remember I was
> unable to apply them because they seemed to be breaking some of the
> "standard command-line jelly". I think I remember that a pluggeable
> context was discussed but, maybe, was not developed.
>
> Thus, I can only encourage you to go ahead. I think it would be nice to
> have both worlds working well with a single code base.
>
> I have not been able to save cycles to address more issues of Jelly and
> I know of some other folks, fellows in research in learning technology,
> that were, looking forward to getting more releases of jelly at the time
> I met them.
>
> Hope it helps.
> I am happy to help you if I can towards making it better.
>
> paul
>
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [jelly] Working on some old issues

Niall Pemberton
On Sun, May 10, 2015 at 3:19 PM, sebb <[hidden email]> wrote:

> I think the first job is to ensure that the build works with Maven2/3,
> having tidied up the layout to conform with Maven2/3 conventions
> (src/test/java and src/main/java etc).
>

I worked on a maven branch back in 2010 here:

https://svn.apache.org/repos/asf/commons/proper/jelly/branches/MAVEN-2-BRANCH

Niall



> I see that a start has been made, but it looks like there is some way to
> go yet.
>
> On 10 May 2015 at 10:48, Bruno P. Kinoshita <[hidden email]>
> wrote:
> > Hi Paul
> >> if I remember well how the patches of Kohsuke landed, I remember I was
> > unable to apply them because they seemed to be breaking some of the
> > "standard command-line jelly". I think I remember that a pluggeable
> > context was discussed but, maybe, was not developed.
> > Any kind of background on old issues is welcome! Before I start to work
> on any issue,
> > I'll triage old issues, try to find some low hanging fruits, and then
> will start a one or two dayresearch on the mailing list to see if I can
> learn as much as possible before coding.
> >>I have not been able to save cycles to address more issues of Jelly and
> > I know of some other folks, fellows in research in learning technology,
> > that were, looking forward to getting more releases of jelly at the time
> > I met them.
> >
> > I will work a little bit every weekend on triage issues, but will have a
> one or two week cyclein the middle of June and in July (lovely weather for
> coding; cold, cloudy, and raining a lot :)
> >
> >>Hope it helps.
> >>I am happy to help you if I can towards making it better.
> >
> > It definitely helps. Very happy for having someone I can ask questions
> about some old issuesin [jelly] :)
> > ThanksBruno
> >
> >
> >       From: Paul Libbrecht <[hidden email]>
> >  To: Commons Developers List <[hidden email]>
> >  Sent: Sunday, May 3, 2015 8:33 AM
> >  Subject: Re: [jelly] Working on some old issues
> >
> >
> >
> >
> > On 1/05/15 10:22, Bruno P. Kinoshita wrote:
> >> 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.
> >
> > Hello Bruno,
> >
> > if I remember well how the patches of Kohsuke landed, I remember I was
> > unable to apply them because they seemed to be breaking some of the
> > "standard command-line jelly". I think I remember that a pluggeable
> > context was discussed but, maybe, was not developed.
> >
> > Thus, I can only encourage you to go ahead. I think it would be nice to
> > have both worlds working well with a single code base.
> >
> > I have not been able to save cycles to address more issues of Jelly and
> > I know of some other folks, fellows in research in learning technology,
> > that were, looking forward to getting more releases of jelly at the time
> > I met them.
> >
> > Hope it helps.
> > I am happy to help you if I can towards making it better.
> >
> > paul
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [jelly] Working on some old issues

Bruno P. Kinoshita
Hi Nial
Do you know why your branch wasn't merged? I've checked it out and a few tests are failing with Maven 3.2.5 and Java 7 & 8. But I'd like to use your branch, try to fix any failing tests and merge back onto trunk.
Created https://issues.apache.org/jira/browse/JELLY-291 to track this issue.
Thanks!Bruno

 
      From: Niall Pemberton <[hidden email]>
 To: Commons Developers List <[hidden email]>
Cc: Bruno P. Kinoshita <[hidden email]>
 Sent: Monday, May 11, 2015 3:36 AM
 Subject: Re: [jelly] Working on some old issues
   
On Sun, May 10, 2015 at 3:19 PM, sebb <[hidden email]> wrote:

> I think the first job is to ensure that the build works with Maven2/3,
> having tidied up the layout to conform with Maven2/3 conventions
> (src/test/java and src/main/java etc).
>

I worked on a maven branch back in 2010 here:

https://svn.apache.org/repos/asf/commons/proper/jelly/branches/MAVEN-2-BRANCH

Niall





> I see that a start has been made, but it looks like there is some way to
> go yet.
>
> On 10 May 2015 at 10:48, Bruno P. Kinoshita <[hidden email]>
> wrote:
> > Hi Paul
> >> if I remember well how the patches of Kohsuke landed, I remember I was
> > unable to apply them because they seemed to be breaking some of the
> > "standard command-line jelly". I think I remember that a pluggeable
> > context was discussed but, maybe, was not developed.
> > Any kind of background on old issues is welcome! Before I start to work
> on any issue,
> > I'll triage old issues, try to find some low hanging fruits, and then
> will start a one or two dayresearch on the mailing list to see if I can
> learn as much as possible before coding.
> >>I have not been able to save cycles to address more issues of Jelly and
> > I know of some other folks, fellows in research in learning technology,
> > that were, looking forward to getting more releases of jelly at the time
> > I met them.
> >
> > I will work a little bit every weekend on triage issues, but will have a
> one or two week cyclein the middle of June and in July (lovely weather for
> coding; cold, cloudy, and raining a lot :)
> >
> >>Hope it helps.
> >>I am happy to help you if I can towards making it better.
> >
> > It definitely helps. Very happy for having someone I can ask questions
> about some old issuesin [jelly] :)
> > ThanksBruno
> >
> >
> >      From: Paul Libbrecht <[hidden email]>
> >  To: Commons Developers List <[hidden email]>
> >  Sent: Sunday, May 3, 2015 8:33 AM
> >  Subject: Re: [jelly] Working on some old issues
> >
> >
> >
> >
> > On 1/05/15 10:22, Bruno P. Kinoshita wrote:
> >> 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.
> >
> > Hello Bruno,
> >
> > if I remember well how the patches of Kohsuke landed, I remember I was
> > unable to apply them because they seemed to be breaking some of the
> > "standard command-line jelly". I think I remember that a pluggeable
> > context was discussed but, maybe, was not developed.
> >
> > Thus, I can only encourage you to go ahead. I think it would be nice to
> > have both worlds working well with a single code base.
> >
> > I have not been able to save cycles to address more issues of Jelly and
> > I know of some other folks, fellows in research in learning technology,
> > that were, looking forward to getting more releases of jelly at the time
> > I met them.
> >
> > Hope it helps.
> > I am happy to help you if I can towards making it better.
> >
> > paul
> >
>


   
Reply | Threaded
Open this post in threaded view
|

Re: [jelly] Working on some old issues

Niall Pemberton
On Sun, May 24, 2015 at 7:52 AM, Bruno P. Kinoshita <
[hidden email]> wrote:

> Hi Nial
> Do you know why your branch wasn't merged?


I dont really remember. I'm not sure whether all issues were resolved
(perhaps around tags doc generation). I sent the following email at the
start of 2010 - but I did some more work after that email:
    * http://markmail.org/message/yveew57uparj3aab

I think the main reason though was that jelly was petty dormant and there
was no real interest.

Niall


> I've checked it out and a few tests are failing with Maven 3.2.5 and Java
> 7 & 8. But I'd like to use your branch, try to fix any failing tests and
> merge back onto trunk.
> Created https://issues.apache.org/jira/browse/JELLY-291 to track this
> issue.
> Thanks!Bruno
>
>
>       From: Niall Pemberton <[hidden email]>
>  To: Commons Developers List <[hidden email]>
> Cc: Bruno P. Kinoshita <[hidden email]>
>  Sent: Monday, May 11, 2015 3:36 AM
>  Subject: Re: [jelly] Working on some old issues
>
> On Sun, May 10, 2015 at 3:19 PM, sebb <[hidden email]> wrote:
>
> > I think the first job is to ensure that the build works with Maven2/3,
> > having tidied up the layout to conform with Maven2/3 conventions
> > (src/test/java and src/main/java etc).
> >
>
> I worked on a maven branch back in 2010 here:
>
>
> https://svn.apache.org/repos/asf/commons/proper/jelly/branches/MAVEN-2-BRANCH
>
> Niall
>
>
>
>
>
> > I see that a start has been made, but it looks like there is some way to
> > go yet.
> >
> > On 10 May 2015 at 10:48, Bruno P. Kinoshita <[hidden email]>
> > wrote:
> > > Hi Paul
> > >> if I remember well how the patches of Kohsuke landed, I remember I was
> > > unable to apply them because they seemed to be breaking some of the
> > > "standard command-line jelly". I think I remember that a pluggeable
> > > context was discussed but, maybe, was not developed.
> > > Any kind of background on old issues is welcome! Before I start to work
> > on any issue,
> > > I'll triage old issues, try to find some low hanging fruits, and then
> > will start a one or two dayresearch on the mailing list to see if I can
> > learn as much as possible before coding.
> > >>I have not been able to save cycles to address more issues of Jelly and
> > > I know of some other folks, fellows in research in learning technology,
> > > that were, looking forward to getting more releases of jelly at the
> time
> > > I met them.
> > >
> > > I will work a little bit every weekend on triage issues, but will have
> a
> > one or two week cyclein the middle of June and in July (lovely weather
> for
> > coding; cold, cloudy, and raining a lot :)
> > >
> > >>Hope it helps.
> > >>I am happy to help you if I can towards making it better.
> > >
> > > It definitely helps. Very happy for having someone I can ask questions
> > about some old issuesin [jelly] :)
> > > ThanksBruno
> > >
> > >
> > >      From: Paul Libbrecht <[hidden email]>
> > >  To: Commons Developers List <[hidden email]>
> > >  Sent: Sunday, May 3, 2015 8:33 AM
> > >  Subject: Re: [jelly] Working on some old issues
> > >
> > >
> > >
> > >
> > > On 1/05/15 10:22, Bruno P. Kinoshita wrote:
> > >> 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.
> > >
> > > Hello Bruno,
> > >
> > > if I remember well how the patches of Kohsuke landed, I remember I was
> > > unable to apply them because they seemed to be breaking some of the
> > > "standard command-line jelly". I think I remember that a pluggeable
> > > context was discussed but, maybe, was not developed.
> > >
> > > Thus, I can only encourage you to go ahead. I think it would be nice to
> > > have both worlds working well with a single code base.
> > >
> > > I have not been able to save cycles to address more issues of Jelly and
> > > I know of some other folks, fellows in research in learning technology,
> > > that were, looking forward to getting more releases of jelly at the
> time
> > > I met them.
> > >
> > > Hope it helps.
> > > I am happy to help you if I can towards making it better.
> > >
> > > paul
> > >
> >
>
>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [jelly] Working on some old issues

Bruno P. Kinoshita
Thanks for clarifying Niall.

I'll try to fix the tests, and will try to generate the Maven site and the tags documentation.
Probably I'll update the commons-parent version in the pom.xml, and will use the new bootstrap style too - which is already used by other commons components.

Once that's done I'll post to the mailing list proposing to merge the branch into trunk.
What do you think?
Bruno

 
      From: Niall Pemberton <[hidden email]>
 To: Commons Developers List <[hidden email]>; Bruno P. Kinoshita <[hidden email]>
 Sent: Monday, May 25, 2015 7:41 AM
 Subject: Re: [jelly] Working on some old issues
   
On Sun, May 24, 2015 at 7:52 AM, Bruno P. Kinoshita <
[hidden email]> wrote:

> Hi Nial
> Do you know why your branch wasn't merged?


I dont really remember. I'm not sure whether all issues were resolved
(perhaps around tags doc generation). I sent the following email at the
start of 2010 - but I did some more work after that email:
    * http://markmail.org/message/yveew57uparj3aab

I think the main reason though was that jelly was petty dormant and there
was no real interest.

Niall




> I've checked it out and a few tests are failing with Maven 3.2.5 and Java
> 7 & 8. But I'd like to use your branch, try to fix any failing tests and
> merge back onto trunk.
> Created https://issues.apache.org/jira/browse/JELLY-291 to track this
> issue.
> Thanks!Bruno
>
>
>      From: Niall Pemberton <[hidden email]>
>  To: Commons Developers List <[hidden email]>
> Cc: Bruno P. Kinoshita <[hidden email]>
>  Sent: Monday, May 11, 2015 3:36 AM
>  Subject: Re: [jelly] Working on some old issues
>
> On Sun, May 10, 2015 at 3:19 PM, sebb <[hidden email]> wrote:
>
> > I think the first job is to ensure that the build works with Maven2/3,
> > having tidied up the layout to conform with Maven2/3 conventions
> > (src/test/java and src/main/java etc).
> >
>
> I worked on a maven branch back in 2010 here:
>
>
> https://svn.apache.org/repos/asf/commons/proper/jelly/branches/MAVEN-2-BRANCH
>
> Niall
>
>
>
>
>
> > I see that a start has been made, but it looks like there is some way to
> > go yet.
> >
> > On 10 May 2015 at 10:48, Bruno P. Kinoshita <[hidden email]>
> > wrote:
> > > Hi Paul
> > >> if I remember well how the patches of Kohsuke landed, I remember I was
> > > unable to apply them because they seemed to be breaking some of the
> > > "standard command-line jelly". I think I remember that a pluggeable
> > > context was discussed but, maybe, was not developed.
> > > Any kind of background on old issues is welcome! Before I start to work
> > on any issue,
> > > I'll triage old issues, try to find some low hanging fruits, and then
> > will start a one or two dayresearch on the mailing list to see if I can
> > learn as much as possible before coding.
> > >>I have not been able to save cycles to address more issues of Jelly and
> > > I know of some other folks, fellows in research in learning technology,
> > > that were, looking forward to getting more releases of jelly at the
> time
> > > I met them.
> > >
> > > I will work a little bit every weekend on triage issues, but will have
> a
> > one or two week cyclein the middle of June and in July (lovely weather
> for
> > coding; cold, cloudy, and raining a lot :)
> > >
> > >>Hope it helps.
> > >>I am happy to help you if I can towards making it better.
> > >
> > > It definitely helps. Very happy for having someone I can ask questions
> > about some old issuesin [jelly] :)
> > > ThanksBruno
> > >
> > >
> > >      From: Paul Libbrecht <[hidden email]>
> > >  To: Commons Developers List <[hidden email]>
> > >  Sent: Sunday, May 3, 2015 8:33 AM
> > >  Subject: Re: [jelly] Working on some old issues
> > >
> > >
> > >
> > >
> > > On 1/05/15 10:22, Bruno P. Kinoshita wrote:
> > >> 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.
> > >
> > > Hello Bruno,
> > >
> > > if I remember well how the patches of Kohsuke landed, I remember I was
> > > unable to apply them because they seemed to be breaking some of the
> > > "standard command-line jelly". I think I remember that a pluggeable
> > > context was discussed but, maybe, was not developed.
> > >
> > > Thus, I can only encourage you to go ahead. I think it would be nice to
> > > have both worlds working well with a single code base.
> > >
> > > I have not been able to save cycles to address more issues of Jelly and
> > > I know of some other folks, fellows in research in learning technology,
> > > that were, looking forward to getting more releases of jelly at the
> time
> > > I met them.
> > >
> > > Hope it helps.
> > > I am happy to help you if I can towards making it better.
> > >
> > > paul
> > >
> >
>
>
>
>


   
Reply | Threaded
Open this post in threaded view
|

Re: [jelly] Working on some old issues

Benedikt Ritter-4
2015-05-25 8:07 GMT+02:00 Bruno P. Kinoshita <[hidden email]>:

> Thanks for clarifying Niall.
>
> I'll try to fix the tests, and will try to generate the Maven site and the
> tags documentation.
> Probably I'll update the commons-parent version in the pom.xml, and will
> use the new bootstrap style too - which is already used by other commons
> components.
>
> Once that's done I'll post to the mailing list proposing to merge the
> branch into trunk.
> What do you think?
>

Go for it! Great to see some action in jelly!


> Bruno
>
>
>       From: Niall Pemberton <[hidden email]>
>  To: Commons Developers List <[hidden email]>; Bruno P. Kinoshita
> <[hidden email]>
>  Sent: Monday, May 25, 2015 7:41 AM
>  Subject: Re: [jelly] Working on some old issues
>
> On Sun, May 24, 2015 at 7:52 AM, Bruno P. Kinoshita <
> [hidden email]> wrote:
>
> > Hi Nial
> > Do you know why your branch wasn't merged?
>
>
> I dont really remember. I'm not sure whether all issues were resolved
> (perhaps around tags doc generation). I sent the following email at the
> start of 2010 - but I did some more work after that email:
>     * http://markmail.org/message/yveew57uparj3aab
>
> I think the main reason though was that jelly was petty dormant and there
> was no real interest.
>
> Niall
>
>
>
>
> > I've checked it out and a few tests are failing with Maven 3.2.5 and Java
> > 7 & 8. But I'd like to use your branch, try to fix any failing tests and
> > merge back onto trunk.
> > Created https://issues.apache.org/jira/browse/JELLY-291 to track this
> > issue.
> > Thanks!Bruno
> >
> >
> >      From: Niall Pemberton <[hidden email]>
> >  To: Commons Developers List <[hidden email]>
> > Cc: Bruno P. Kinoshita <[hidden email]>
> >  Sent: Monday, May 11, 2015 3:36 AM
> >  Subject: Re: [jelly] Working on some old issues
> >
> > On Sun, May 10, 2015 at 3:19 PM, sebb <[hidden email]> wrote:
> >
> > > I think the first job is to ensure that the build works with Maven2/3,
> > > having tidied up the layout to conform with Maven2/3 conventions
> > > (src/test/java and src/main/java etc).
> > >
> >
> > I worked on a maven branch back in 2010 here:
> >
> >
> >
> https://svn.apache.org/repos/asf/commons/proper/jelly/branches/MAVEN-2-BRANCH
> >
> > Niall
> >
> >
> >
> >
> >
> > > I see that a start has been made, but it looks like there is some way
> to
> > > go yet.
> > >
> > > On 10 May 2015 at 10:48, Bruno P. Kinoshita <
> [hidden email]>
> > > wrote:
> > > > Hi Paul
> > > >> if I remember well how the patches of Kohsuke landed, I remember I
> was
> > > > unable to apply them because they seemed to be breaking some of the
> > > > "standard command-line jelly". I think I remember that a pluggeable
> > > > context was discussed but, maybe, was not developed.
> > > > Any kind of background on old issues is welcome! Before I start to
> work
> > > on any issue,
> > > > I'll triage old issues, try to find some low hanging fruits, and then
> > > will start a one or two dayresearch on the mailing list to see if I can
> > > learn as much as possible before coding.
> > > >>I have not been able to save cycles to address more issues of Jelly
> and
> > > > I know of some other folks, fellows in research in learning
> technology,
> > > > that were, looking forward to getting more releases of jelly at the
> > time
> > > > I met them.
> > > >
> > > > I will work a little bit every weekend on triage issues, but will
> have
> > a
> > > one or two week cyclein the middle of June and in July (lovely weather
> > for
> > > coding; cold, cloudy, and raining a lot :)
> > > >
> > > >>Hope it helps.
> > > >>I am happy to help you if I can towards making it better.
> > > >
> > > > It definitely helps. Very happy for having someone I can ask
> questions
> > > about some old issuesin [jelly] :)
> > > > ThanksBruno
> > > >
> > > >
> > > >      From: Paul Libbrecht <[hidden email]>
> > > >  To: Commons Developers List <[hidden email]>
> > > >  Sent: Sunday, May 3, 2015 8:33 AM
> > > >  Subject: Re: [jelly] Working on some old issues
> > > >
> > > >
> > > >
> > > >
> > > > On 1/05/15 10:22, Bruno P. Kinoshita wrote:
> > > >> 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.
> > > >
> > > > Hello Bruno,
> > > >
> > > > if I remember well how the patches of Kohsuke landed, I remember I
> was
> > > > unable to apply them because they seemed to be breaking some of the
> > > > "standard command-line jelly". I think I remember that a pluggeable
> > > > context was discussed but, maybe, was not developed.
> > > >
> > > > Thus, I can only encourage you to go ahead. I think it would be nice
> to
> > > > have both worlds working well with a single code base.
> > > >
> > > > I have not been able to save cycles to address more issues of Jelly
> and
> > > > I know of some other folks, fellows in research in learning
> technology,
> > > > that were, looking forward to getting more releases of jelly at the
> > time
> > > > I met them.
> > > >
> > > > Hope it helps.
> > > > I am happy to help you if I can towards making it better.
> > > >
> > > > paul
> > > >
> > >
> >
> >
> >
> >
>
>
>
>


--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Reply | Threaded
Open this post in threaded view
|

Re: [jelly] Working on some old issues

Niall Pemberton
On Tue, May 26, 2015 at 7:39 AM, Benedikt Ritter <[hidden email]> wrote:

> 2015-05-25 8:07 GMT+02:00 Bruno P. Kinoshita <[hidden email]>:
>
> > Thanks for clarifying Niall.
> >
> > I'll try to fix the tests, and will try to generate the Maven site and
> the
> > tags documentation.
> > Probably I'll update the commons-parent version in the pom.xml, and will
> > use the new bootstrap style too - which is already used by other commons
> > components.
> >
> > Once that's done I'll post to the mailing list proposing to merge the
> > branch into trunk.
> > What do you think?
> >
>
> Go for it! Great to see some action in jelly!
>

+1

Niall


>
>
> > Bruno
> >
> >
> >       From: Niall Pemberton <[hidden email]>
> >  To: Commons Developers List <[hidden email]>; Bruno P.
> Kinoshita
> > <[hidden email]>
> >  Sent: Monday, May 25, 2015 7:41 AM
> >  Subject: Re: [jelly] Working on some old issues
> >
> > On Sun, May 24, 2015 at 7:52 AM, Bruno P. Kinoshita <
> > [hidden email]> wrote:
> >
> > > Hi Nial
> > > Do you know why your branch wasn't merged?
> >
> >
> > I dont really remember. I'm not sure whether all issues were resolved
> > (perhaps around tags doc generation). I sent the following email at the
> > start of 2010 - but I did some more work after that email:
> >     * http://markmail.org/message/yveew57uparj3aab
> >
> > I think the main reason though was that jelly was petty dormant and there
> > was no real interest.
> >
> > Niall
> >
> >
> >
> >
> > > I've checked it out and a few tests are failing with Maven 3.2.5 and
> Java
> > > 7 & 8. But I'd like to use your branch, try to fix any failing tests
> and
> > > merge back onto trunk.
> > > Created https://issues.apache.org/jira/browse/JELLY-291 to track this
> > > issue.
> > > Thanks!Bruno
> > >
> > >
> > >      From: Niall Pemberton <[hidden email]>
> > >  To: Commons Developers List <[hidden email]>
> > > Cc: Bruno P. Kinoshita <[hidden email]>
> > >  Sent: Monday, May 11, 2015 3:36 AM
> > >  Subject: Re: [jelly] Working on some old issues
> > >
> > > On Sun, May 10, 2015 at 3:19 PM, sebb <[hidden email]> wrote:
> > >
> > > > I think the first job is to ensure that the build works with
> Maven2/3,
> > > > having tidied up the layout to conform with Maven2/3 conventions
> > > > (src/test/java and src/main/java etc).
> > > >
> > >
> > > I worked on a maven branch back in 2010 here:
> > >
> > >
> > >
> >
> https://svn.apache.org/repos/asf/commons/proper/jelly/branches/MAVEN-2-BRANCH
> > >
> > > Niall
> > >
> > >
> > >
> > >
> > >
> > > > I see that a start has been made, but it looks like there is some way
> > to
> > > > go yet.
> > > >
> > > > On 10 May 2015 at 10:48, Bruno P. Kinoshita <
> > [hidden email]>
> > > > wrote:
> > > > > Hi Paul
> > > > >> if I remember well how the patches of Kohsuke landed, I remember I
> > was
> > > > > unable to apply them because they seemed to be breaking some of the
> > > > > "standard command-line jelly". I think I remember that a pluggeable
> > > > > context was discussed but, maybe, was not developed.
> > > > > Any kind of background on old issues is welcome! Before I start to
> > work
> > > > on any issue,
> > > > > I'll triage old issues, try to find some low hanging fruits, and
> then
> > > > will start a one or two dayresearch on the mailing list to see if I
> can
> > > > learn as much as possible before coding.
> > > > >>I have not been able to save cycles to address more issues of Jelly
> > and
> > > > > I know of some other folks, fellows in research in learning
> > technology,
> > > > > that were, looking forward to getting more releases of jelly at the
> > > time
> > > > > I met them.
> > > > >
> > > > > I will work a little bit every weekend on triage issues, but will
> > have
> > > a
> > > > one or two week cyclein the middle of June and in July (lovely
> weather
> > > for
> > > > coding; cold, cloudy, and raining a lot :)
> > > > >
> > > > >>Hope it helps.
> > > > >>I am happy to help you if I can towards making it better.
> > > > >
> > > > > It definitely helps. Very happy for having someone I can ask
> > questions
> > > > about some old issuesin [jelly] :)
> > > > > ThanksBruno
> > > > >
> > > > >
> > > > >      From: Paul Libbrecht <[hidden email]>
> > > > >  To: Commons Developers List <[hidden email]>
> > > > >  Sent: Sunday, May 3, 2015 8:33 AM
> > > > >  Subject: Re: [jelly] Working on some old issues
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 1/05/15 10:22, Bruno P. Kinoshita wrote:
> > > > >> 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.
> > > > >
> > > > > Hello Bruno,
> > > > >
> > > > > if I remember well how the patches of Kohsuke landed, I remember I
> > was
> > > > > unable to apply them because they seemed to be breaking some of the
> > > > > "standard command-line jelly". I think I remember that a pluggeable
> > > > > context was discussed but, maybe, was not developed.
> > > > >
> > > > > Thus, I can only encourage you to go ahead. I think it would be
> nice
> > to
> > > > > have both worlds working well with a single code base.
> > > > >
> > > > > I have not been able to save cycles to address more issues of Jelly
> > and
> > > > > I know of some other folks, fellows in research in learning
> > technology,
> > > > > that were, looking forward to getting more releases of jelly at the
> > > time
> > > > > I met them.
> > > > >
> > > > > Hope it helps.
> > > > > I am happy to help you if I can towards making it better.
> > > > >
> > > > > paul
> > > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter
>