> It was already there, I assumed it was you when you were working on
> adding support for Portlet 2 spec

Right! This is the old one which was replaced with the new portlet2 spec
implementation.


#################################################
web: http://www.jgeppert.com
twitter: http://twitter.com/jogep


2015-05-22 15:46 GMT+02:00 Lukasz Lenart <lukaszlen...@apache.org>:

> 2015-05-22 13:40 GMT+02:00 Rene Gielen <gie...@it-neering.net>:
> > While it is OK for me to drop GitFlow, I'm -1 for moving core
> > development to GitHub. We should not rely on an external service for our
> > internal workflow. GitHub should remain the interface for external
> > contributors, but not the place where the committership driven
> > development should take place. I'm pretty sure we'll get in trouble
> > justifying such a move towards the board.
>
> I'm not saying that we must use GH for everything, but instead
> scattering people's repos I prefer working on my own clone or local
> branch. Each branch pushed into Apache Git will be replicated to
> GitHub and then to users' repos.
>
> > Basides that, what was the reasoning behind deprecating
> > struts2-portlet-plugin? Did I miss something?
>
> It was already there, I assumed it was you when you were working on
> adding support for Portlet 2 spec
>
>
> Regards
> --
> Ɓukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
>
>

Reply via email to