| Re: [hudson-dev] Candidates for Hudson 2.2.1 |
On 17 Apr 2012, at 02:14, Winston Prakash wrote: > Stuart, > > Instead of relying on Eclipse branch of stapler, you could put the > related fixes in to > > https://github.com/hudson/maven-stapler-plugin > https://github.com/hudson/stapler > > release a version and then use it. Will that work? Yes that works, wasn't sure where the old stapler project lived... I'll create some pull-requests with the backported fixes > - WInston > > On 4/16/12 5:00 PM, Stuart McCulloch wrote: >> On 16 Apr 2012, at 22:54, Henrik Lynggaard Hansen wrote: >> >>> As mentioned in todays meeting I have a few candidates for a 2.2.1 release >>> >>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=376917 ( Maven 3.0.4 is >>> not supported) >>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=376785 (Maven3 build >>> dies with remoting exception when retrieving artifacts) >>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=373753 "Nothing to do - >>> FAILURE" if no change in Git repository >> I would like to include the various XSS 'escape-by-default' / markup fixes that I've been applying to trunk. >> >> I have a branch based on 2.2.0 where I've done a preliminary backport: >> >> https://github.com/mcculls/hudson/commits/hudson-2.2.0-escapebydefault/ >> --> https://github.com/mcculls/hudson/commit/1b7284c88d7c81e5b1100f0c08bb99ff4da9b043 >> >> These fixes currently rely on the Eclipse branch of stapler: >> >> https://github.com/mcculls/hudson/commit/a4bf322b658c4e9ee1d6ed91004adf39d530a430 >> >> But we could always backport the following fix to the old stapler project instead: >> >> http://git.eclipse.org/c/hudson/org.eclipse.hudson.stapler.git/commit/?id=5cca490c5b9fc44f60a877f767508bc81bff5945 >> >> Any thoughts? >> >>> Best regards >>> Henrik >>> _______________________________________________ >>> hudson-dev mailing list >>> hudson-dev@xxxxxxxxxxx >>> https://dev.eclipse.org/mailman/listinfo/hudson-dev