[jsr362-observers:] [jsr362-experts:] Re: The JSR 362 TCK on Pluto is open for business ...
- From: Werner Keil <
- Subject: [jsr362-observers:] [jsr362-experts:] Re: The JSR 362 TCK on Pluto is open for business ...
- Date: Mon, 28 Jul 2014 18:19:29 +0200
- List-id: <jsr362-experts.portletspec3.java.net>
Thanks, I could not see anything in
but the GitHub mirror
shows this module, thus I assume, Pluto switched over to Git now? We have a
dual mode at DeviceMap where some of the SVN repo gets mirrored
automatically to git.apache and then further to GitHub. I have not tried
whether committer role applies to the Git repo, but at least cloning and
pull requests should work in any case.
On Mon, Jul 28, 2014 at 6:01 PM, Martin Scott Nicklous <
> Hi Werner,
> Carsten is not currently working on the RI.
> Pluto is the RI for Portlet Specification 2.0, and we intend to evolve it
> to become the RI for Portlet Specification 3.0. I presented the idea on the
> Pluto development mailing list, and believe that this would be acceptable
> to those involved. The idea is to develop the TCK in parallel with the RI,
> which is the reason for putting the Portlet Specification 3.0 TCK up on
> Pluto. The short-term roadmap looks something like this:
> * Complete the v2.0 compatibility portion of the TCK so that we can make
> sure compatibility does not break as we move forward
> * Move the new portlet API code from the github portletspec3 project into
> the Pluto project
> * Switch the Pluto code over to use the new API code as dependency. Create
> scaffolding code for new methods as required.
> * Implement new methods
> * create TCK tests for new methods
> * Integrate the PortletHub for Ajax support into the Pluto theme
> * Implement the Ajax action and partial action processing sequences
> required for the PortletHub support
> PortletHub works as expected
> At this point, we will have implemented the level that will be defined in
> the Portlet Specification 3.0 EDR document, which I will be producing in
> parallel with this effort.
> After that, we will need to do another round of specification work to take
> care of the items we haven't yet closed on - alignment with JavaEE 7
> functionality, CDI support, improved resource sharing between portlets,
> improved mobile support, WebSocket support ... etc.
> Then (or in parallel) we can do another round of implementation. :-)
> Mit freundlichen Grüßen, / Kind regards,
> Scott Nicklous
> WebSphere Portal Standardization Lead & Technology Consultant
> Specification Lead, JSR 362 Portlet Specification 3.0
> IBM Software Group, IBM Collaboration Solutions
> IBM Deutschland Research & Development GmbH / Vorsitzender des
> Aufsichtsrats: Martina Koederitz / Geschäftsführung: Dirk Wittkopp
> Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart,
> HRB 243294
> Werner Keil
> wrote on 28.07.2014 16:59:11:
> > From: Werner Keil
> > <
> > To:
> > Cc:
> > Date: 28.07.2014 17:00
> > Subject: [jsr362-experts:] Re: The JSR 362 TCK on Pluto is open for
> > business ...
> > Scott/Carsten/all,
> > I hope, Carsten, you're still around and with the Pluto project? I
> > see, Pluto 2 is already out, and 2.1 in the pipeline, but assuming
> > it'll evolve with the Portlet Spec, is there a roadmap for its RI,
> > i.E. if Pluto 2.1 or a not yet defined version would play that role?
> > Thanks and Regards,
> > Werner
> > On Mon, Jul 28, 2014 at 4:49 PM, Martin Scott Nicklous <
> > wrote:
> > That would be really super, thanks!
> > Werner Keil
> > <
> > wrote on 27.07.2014 16:51:37:
> > > From: Werner Keil
> > > <
> > > To:
> > >
> > > Date: 27.07.2014 16:52
> > > Subject: [jsr362-experts:] Re: The JSR 362 TCK on Pluto is open for
> > > business ...
> > >
> > > Scott,
> > >
> > > Thanks, AFAIK I am committer in the Apache Portlet umbrella which
> > > Pluto must be under, so I should be able to check out this
> > > repository and be able to contribute there.
> > >
> > > Kind Regards,
> > > Werner
> > >