You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Thomas Vandahl <tv...@apache.org> on 2015/12/21 21:55:46 UTC
[VOTE] Release turbine-4.0-M2 based on RC1
Hi folks,
I thought is was about time to prepare a release candidate for the M2
milestone of Turbine 4.0. This milestone release is made for
verification of the modified security components and the API cleanup.
Please verify this release candidate, especially the completeness of the
source and binary distribution packages and vote...
Tag:
https://svn.apache.org/repos/asf/turbine/core/tags/turbine-4.0-M2/
Site:
http://turbine.apache.org/turbine/turbine-4.0-M2/
Staging repository:
https://repository.apache.org/content/repositories/orgapacheturbine-1010/
[ ] +1 release it
[ ] +0 go ahead I don't care
[ ] -1 no, do not release it because
Bye, Thomas.
Changes in this version include:
New features:
o Add QuartzSchedulerService
o Add Annotation @TurbineActionEvent to annotate action methods
with arbitrary event names.
o Add Annotation @TurbineLoader to inject a loader
instance into objects.
o Add Annotation @TurbineConfiguration to inject a configuration
instance into objects.
o Add Annotation @TurbineService to inject Turbine service instance
into assemblers such as screens, actions, navigations etc. and
pipeline valves.
See VelocityActionWithServiceInjection for an example.
o Add class cache for TurbineRunDataService
Fixed Bugs:
o Fix Velocity logging.
o Fix possible NPE in TurbinePullService.
o Use lastIndexOf() to get the template extension in
TurbineTemplateService. Issue: TRB-82.
o Fix TurbineYaafiComponentService to set its applicationRoot properly.
o Fix TurbineMacros to comply with the implementation of
HtmlPageattributes
o Port the handling of template encoding from Turbine 2.3.3
Changes:
o Update dependencies
- commons-codec to 1.10
- commons-collections to 3.2.2
- commons-logging to 1.2
- commons-beanutils to 1.9.2
- jython to 2.7.0
- log4j to 1.2.17
o Update dependencies
- fulcrum-security to 1.1.0
- fulcrum-intake to 1.2.0
o Update to Torque 4.0.0
o Update dependencies
- servlet-api to 2.5 (Tomcat 6.0)
- commons-codec to 1.8
- commons-configuration to 1.9
- commons-email to 1.3
- fulcrum-parser to 1.0.3
o Update Turbine Parent POM to version 3
o Switch to Fulcrum Security API
o Refactor handling of annotated fields into AnnotationProcessor.
o Reintroduce VelocityCachedLayout/Screen classes
o Adjust site for Apache Turbine Parent POM version 2
o Use Apache Turbine Parent POM version 2
o Remove duplicate data storage in DefaultTurbineRunData and
DefaultPipelineData
o Services that implement TurbineServiceProvider are inited early by
default Issue: TRB-72.
o Switch from String keys to Class keys for AssemblerBrokerService
o Refine interface of PipelineData and add user and acl objects
to pipelineData.
o Continue generification
Removed:
o Remove all deprecated methods using RunData as a parameter to clean
up the API Further cleanup is needed.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: PING Re: [VOTE] Release turbine-4.0-M2 based on RC1
Posted by Georg Kallidis <gk...@cedis.fu-berlin.de>.
Hi Thomas,
I´ll review it of course, ...
. Georg
Von: Thomas Vandahl <tv...@apache.org>
An: Turbine Developers List <de...@turbine.apache.org>,
private@turbine.apache.org
Datum: 02.01.2016 19:45
Betreff: PING Re: [VOTE] Release turbine-4.0-M2 based on RC1
On 21.12.15 21:55, Thomas Vandahl wrote:
> Hi folks,
>
> I thought is was about time to prepare a release candidate for the M2
> milestone of Turbine 4.0. This milestone release is made for
> verification of the modified security components and the API cleanup.
>
> Please verify this release candidate, especially the completeness of the
> source and binary distribution packages and vote...
Anyone else?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: PING Re: [VOTE] Release turbine-4.0-M2 based on RC1
Posted by Siegfried Göschl <si...@it20one.com>.
Hi Thomas,
[X] +1 release it
Cheers,
Siegfried Goeschl
----- Ursprüngliche Mail -----
Von: "Siegfried Göschl" <si...@it20one.com>
An: "Turbine Developers List" <de...@turbine.apache.org>, private@turbine.apache.org
Gesendet: Samstag, 2. Januar 2016 20:40:58
Betreff: Re: PING Re: [VOTE] Release turbine-4.0-M2 based on RC1
HI Thomas,
I'm having a look at it tonight :-)
Cheers,
Siegfried Goeschl
----- Ursprüngliche Mail -----
Von: "Thomas Vandahl" <tv...@apache.org>
An: "Turbine Developers List" <de...@turbine.apache.org>, private@turbine.apache.org
Gesendet: Samstag, 2. Januar 2016 19:45:02
Betreff: PING Re: [VOTE] Release turbine-4.0-M2 based on RC1
On 21.12.15 21:55, Thomas Vandahl wrote:
> Hi folks,
>
> I thought is was about time to prepare a release candidate for the M2
> milestone of Turbine 4.0. This milestone release is made for
> verification of the modified security components and the API cleanup.
>
> Please verify this release candidate, especially the completeness of the
> source and binary distribution packages and vote...
Anyone else?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: PING Re: [VOTE] Release turbine-4.0-M2 based on RC1
Posted by Siegfried Göschl <si...@it20one.com>.
HI Thomas,
I'm having a look at it tonight :-)
Cheers,
Siegfried Goeschl
----- Ursprüngliche Mail -----
Von: "Thomas Vandahl" <tv...@apache.org>
An: "Turbine Developers List" <de...@turbine.apache.org>, private@turbine.apache.org
Gesendet: Samstag, 2. Januar 2016 19:45:02
Betreff: PING Re: [VOTE] Release turbine-4.0-M2 based on RC1
On 21.12.15 21:55, Thomas Vandahl wrote:
> Hi folks,
>
> I thought is was about time to prepare a release candidate for the M2
> milestone of Turbine 4.0. This milestone release is made for
> verification of the modified security components and the API cleanup.
>
> Please verify this release candidate, especially the completeness of the
> source and binary distribution packages and vote...
Anyone else?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
PING Re: [VOTE] Release turbine-4.0-M2 based on RC1
Posted by Thomas Vandahl <tv...@apache.org>.
On 21.12.15 21:55, Thomas Vandahl wrote:
> Hi folks,
>
> I thought is was about time to prepare a release candidate for the M2
> milestone of Turbine 4.0. This milestone release is made for
> verification of the modified security components and the API cleanup.
>
> Please verify this release candidate, especially the completeness of the
> source and binary distribution packages and vote...
Anyone else?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: [VOTE] Release turbine-4.0-M2 based on RC1
Posted by Thomas Vandahl <tv...@apache.org>.
On 21.12.15 21:55, Thomas Vandahl wrote:
> [X] +1 release it
> [ ] +0 go ahead I don't care
> [ ] -1 no, do not release it because
>
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: JSONRPC /Jackson: Jabsorb Integration to Fulcrum?
Posted by Georg Kallidis <gk...@cedis.fu-berlin.de>.
the question could be postponed, as the actual reason, why I asked it -
the orgjson serialization- is resolved. Jabsorb 1.3.2 does this job
already very well ("direct match" sync), which I missed at the beginning.
Unfortunately I could not find any tag 1.3.2 in the Git version control,
just 1.3, which seems not exactly right (original vc was hg).
As a result this means that actually there is no need to upgrade or
release version 1.4. Nonetheless the question might arise later as
considerable code changes are not yet released and further fixes might be
necessary.
Best regards, Georg
Von: "Georg Kallidis" <gk...@cedis.fu-berlin.de>
An: dev@turbine.apache.org
Datum: 05.04.2016 09:48
Betreff: JSONRPC /Jackson: Jabsorb Integration to Fulcrum?
Hi,
Jackson is a very popular JSON mapping library (cft.
https://github.com/FasterXML/jackson). Turbine currently has the Jabsorb
library (cft. https://code.google.com/archive/p/jabsorb/) integrated in
the JSON-RPC module, which has its own ser/deser mechanism.
To take advantage of Jackson mappings in Jabsorb/JSON-RPC, some things
have to be checked, but technically I think this could be done with very
little effort.
Jabsorb uses Core JSON API from json.org. On the other hand Jackson
serialization could easily be mapped to this by using the
Jackson-OrgJson-Module (library already provided, thanks to
https://github.com/FasterXML/jackson-datatype-json-org). Jabsorb
serialization could then just be skipped. I would expect that performance
is at least the same.
To get to this point seems to be just a few lines of code, but the last
Jabsorb release number was 1.3.2 and the code is not maintained/actively
developed. Arthur Blake, last maintainer, told me (E-Mail Feb/15/2015),
that he doesn't expect any new releases.
The question is, how to release Jabsorb (currently 1.4-SNAPSHOT, Apache
2.0 license)?
Could/should we integrate jabsorb into Fulcrum giving it a new groupid? I
could release it otherwise with my own credentials.
There exist of course as an alternative more actively developed
Jsonrpc-projects, e.g. https://github.com/briandilley/jsonrpc4j.
Best regards, Georg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
JSONRPC /Jackson: Jabsorb Integration to Fulcrum?
Posted by Georg Kallidis <gk...@cedis.fu-berlin.de>.
Hi,
Jackson is a very popular JSON mapping library (cft.
https://github.com/FasterXML/jackson). Turbine currently has the Jabsorb
library (cft. https://code.google.com/archive/p/jabsorb/) integrated in
the JSON-RPC module, which has its own ser/deser mechanism.
To take advantage of Jackson mappings in Jabsorb/JSON-RPC, some things
have to be checked, but technically I think this could be done with very
little effort.
Jabsorb uses Core JSON API from json.org. On the other hand Jackson
serialization could easily be mapped to this by using the
Jackson-OrgJson-Module (library already provided, thanks to
https://github.com/FasterXML/jackson-datatype-json-org). Jabsorb
serialization could then just be skipped. I would expect that performance
is at least the same.
To get to this point seems to be just a few lines of code, but the last
Jabsorb release number was 1.3.2 and the code is not maintained/actively
developed. Arthur Blake, last maintainer, told me (E-Mail Feb/15/2015),
that he doesn't expect any new releases.
The question is, how to release Jabsorb (currently 1.4-SNAPSHOT, Apache
2.0 license)?
Could/should we integrate jabsorb into Fulcrum giving it a new groupid? I
could release it otherwise with my own credentials.
There exist of course as an alternative more actively developed
Jsonrpc-projects, e.g. https://github.com/briandilley/jsonrpc4j.
Best regards, Georg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: [VOTE] Release turbine-4.0-M2 based on RC1
Posted by Georg Kallidis <gk...@cedis.fu-berlin.de>.
> [X] +1 release it
> [ ] +0 go ahead I don't care
> [ ] -1 no, do not release it because
.Georg
Von: Thomas Vandahl <tv...@apache.org>
An: Turbine Developers List <de...@turbine.apache.org>,
private@turbine.apache.org
Datum: 21.12.2015 21:55
Betreff: [VOTE] Release turbine-4.0-M2 based on RC1
Hi folks,
I thought is was about time to prepare a release candidate for the M2
milestone of Turbine 4.0. This milestone release is made for
verification of the modified security components and the API cleanup.
Please verify this release candidate, especially the completeness of the
source and binary distribution packages and vote...
Tag:
https://svn.apache.org/repos/asf/turbine/core/tags/turbine-4.0-M2/
Site:
http://turbine.apache.org/turbine/turbine-4.0-M2/
Staging repository:
https://repository.apache.org/content/repositories/orgapacheturbine-1010/
[ ] +1 release it
[ ] +0 go ahead I don't care
[ ] -1 no, do not release it because
Bye, Thomas.
Changes in this version include:
New features:
o Add QuartzSchedulerService
o Add Annotation @TurbineActionEvent to annotate action methods
with arbitrary event names.
o Add Annotation @TurbineLoader to inject a loader
instance into objects.
o Add Annotation @TurbineConfiguration to inject a configuration
instance into objects.
o Add Annotation @TurbineService to inject Turbine service instance
into assemblers such as screens, actions, navigations
etc. and
pipeline valves.
See VelocityActionWithServiceInjection for an example.
o Add class cache for TurbineRunDataService
Fixed Bugs:
o Fix Velocity logging.
o Fix possible NPE in TurbinePullService.
o Use lastIndexOf() to get the template extension in
TurbineTemplateService. Issue: TRB-82.
o Fix TurbineYaafiComponentService to set its applicationRoot properly.
o Fix TurbineMacros to comply with the implementation of
HtmlPageattributes
o Port the handling of template encoding from Turbine 2.3.3
Changes:
o Update dependencies
- commons-codec to 1.10
- commons-collections to 3.2.2
- commons-logging to 1.2
- commons-beanutils to 1.9.2
- jython to 2.7.0
- log4j to 1.2.17
o Update dependencies
- fulcrum-security to 1.1.0
- fulcrum-intake to 1.2.0
o Update to Torque 4.0.0
o Update dependencies
- servlet-api to 2.5 (Tomcat 6.0)
- commons-codec to 1.8
- commons-configuration to 1.9
- commons-email to 1.3
- fulcrum-parser to 1.0.3
o Update Turbine Parent POM to version 3
o Switch to Fulcrum Security API
o Refactor handling of annotated fields into AnnotationProcessor.
o Reintroduce VelocityCachedLayout/Screen classes
o Adjust site for Apache Turbine Parent POM version 2
o Use Apache Turbine Parent POM version 2
o Remove duplicate data storage in DefaultTurbineRunData and
DefaultPipelineData
o Services that implement TurbineServiceProvider are inited early by
default Issue: TRB-72.
o Switch from String keys to Class keys for AssemblerBrokerService
o Refine interface of PipelineData and add user and acl objects
to pipelineData.
o Continue generification
Removed:
o Remove all deprecated methods using RunData as a parameter to clean
up the API Further cleanup is needed.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Antwort: Re: Turbine 4.0 Archetype + Fulcrum in Turbine / Security Services
/ Torque Persistence
Posted by Georg Kallidis <gk...@cedis.fu-berlin.de>.
Hi Thomas,
yes, I am too starting to build/migrate a Turbine 4.0-M2 project with
Fulcrum Security Torque.
As the database backend is similar, but different, I would like to have
org.apache.fulcrum.security.torque.turbine.TorqueTurbine*Manager classes
to be reusable. I think it could be done with a little effort.
Unfortunately all the implementations of
org.apache.fulcrum.security.model.turbine.entity.TurbineUser are not
reusable (for me).
To improve pipeline handling would be indeed worth another effort...
More upcoming steps follow ..
Best regards, Georg
Von: Thomas Vandahl <tv...@apache.org>
An: Turbine Developers List <de...@turbine.apache.org>
Datum: 11.05.2016 20:08
Betreff: Re: Turbine 4.0 Archetype + Fulcrum in Turbine / Security
Services / Torque Persistence
Hi Georg,
On 11.05.16 09:30, Georg Kallidis wrote:
> (2) When looking a little deeper into how actually things are to be
> implemented, some questions arise, e.g. how are the security services
> considered to be used? For example there exists a class in Turbine
called
> org.apache.turbine.services.security.DefaultSecurityService
> and another class in Fulcrum Security
> org.apache.fulcrum.security.BaseSecurityService
> and furthermore a (deprecated?) Turbine Adapters in Fulcrum Security
> org.apache.fulcrum.security.adapter.turbine.SecurityServiceAdapter
>
>
> Which of them is needed in which case (or could be substituted), which
are
> deprecated?
I'm currently trying to port an old web application of mine to Turbine 4
and Torque 4(.1-SNAPSHOT). I want to find out by myself how the handling
of the new features actually works. When I'm done, I think we'll have a
working blueprint for the archetype because the application will be
using fulcrum-security-torque as a security service.
> May be the easiest to answer is, when starting a brand-new Turbine
project
> using Torque what is the way to go. The new Fulcrum Security Torque
> persistence managers seem to be the candidate in the first place or not?
Yes, obviously. However a lot has changed and we need to make sure that
the Lego bricks of Turbine and Torque fit together as they used to. I
stumbled across several Torque issues, for example.
If you have a similar application at hand, I'd suggest to try it
yourself and see if you run against any obstacles and then discuss your
findings here.
I, for one, still find the handling of PipelineData cumbersome. I don't
want to leave it at this when going to 4.0 final. However, I don't have
any good idea how to resolve this right now.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: Turbine 4.0 Archetype + Fulcrum in Turbine / Security Services
/ Torque Persistence
Posted by Thomas Vandahl <tv...@apache.org>.
Hi Georg,
On 11.05.16 09:30, Georg Kallidis wrote:
> (2) When looking a little deeper into how actually things are to be
> implemented, some questions arise, e.g. how are the security services
> considered to be used? For example there exists a class in Turbine called
> org.apache.turbine.services.security.DefaultSecurityService
> and another class in Fulcrum Security
> org.apache.fulcrum.security.BaseSecurityService
> and furthermore a (deprecated?) Turbine Adapters in Fulcrum Security
> org.apache.fulcrum.security.adapter.turbine.SecurityServiceAdapter
>
>
> Which of them is needed in which case (or could be substituted), which are
> deprecated?
I'm currently trying to port an old web application of mine to Turbine 4
and Torque 4(.1-SNAPSHOT). I want to find out by myself how the handling
of the new features actually works. When I'm done, I think we'll have a
working blueprint for the archetype because the application will be
using fulcrum-security-torque as a security service.
> May be the easiest to answer is, when starting a brand-new Turbine project
> using Torque what is the way to go. The new Fulcrum Security Torque
> persistence managers seem to be the candidate in the first place or not?
Yes, obviously. However a lot has changed and we need to make sure that
the Lego bricks of Turbine and Torque fit together as they used to. I
stumbled across several Torque issues, for example.
If you have a similar application at hand, I'd suggest to try it
yourself and see if you run against any obstacles and then discuss your
findings here.
I, for one, still find the handling of PipelineData cumbersome. I don't
want to leave it at this when going to 4.0 final. However, I don't have
any good idea how to resolve this right now.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Turbine 4.0 Archetype + Fulcrum in Turbine / Security Services / Torque
Persistence
Posted by Georg Kallidis <gk...@cedis.fu-berlin.de>.
Hi,
(1) as far as I can see, the archetype trunk (turbine-webapp-4.0) points
to Version 4.0-M2.
Should we release it now or wait for Turbine 4.0 Final Release? It seems
quite ready to be used. Nonetheless some testing and validating should be
done.
If we proceed to 4.0-SNAPSHOT changing e.g. of turbine-pipeline.xml would
be required, which is not (yet) backward-compatible.
(2) When looking a little deeper into how actually things are to be
implemented, some questions arise, e.g. how are the security services
considered to be used? For example there exists a class in Turbine called
org.apache.turbine.services.security.DefaultSecurityService
and another class in Fulcrum Security
org.apache.fulcrum.security.BaseSecurityService
and furthermore a (deprecated?) Turbine Adapters in Fulcrum Security
org.apache.fulcrum.security.adapter.turbine.SecurityServiceAdapter
Which of them is needed in which case (or could be substituted), which are
deprecated?
Migrating to Turbine M2 (with Torque OM), probably many things just
continue to work, but what exactly should be dome could be made more
apparent. Especially getting an instance of and saving a user I see more
than one way to do it (I will document this somewhere).
May be the easiest to answer is, when starting a brand-new Turbine project
using Torque what is the way to go. The new Fulcrum Security Torque
persistence managers seem to be the candidate in the first place or not?
So, I think some more explanation is needed at some place ..
Best regards, Georg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: [VOTE] Release turbine-4.0-M2 based on RC1
Posted by Jürgen Hoffmann <ho...@ellumination.de>.
> [X] +1 release it
> [ ] +0 go ahead I don't care
> [ ] -1 no, do not release it because
Buddy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
[RESULT][VOTE] Release turbine-4.0-M2 based on RC1
Posted by Thomas Vandahl <tv...@apache.org>.
On 21.12.15 21:55, Thomas Vandahl wrote:
> Hi folks,
>
> I thought is was about time to prepare a release candidate for the M2
> milestone of Turbine 4.0. This milestone release is made for
> verification of the modified security components and the API cleanup.
>
> Please verify this release candidate, especially the completeness of the
> source and binary distribution packages and vote...
Hi folks,
we have four binding +1 votes for the release candidate (in order of
appearance)
- Thomas Vandahl
- Jürgen Hoffmann
- Siegfried Goeschl
- Georg Kallidis
No 0 and -1 votes were cast. The vote has passed. I will be publishing
the artifacts on Nexus shortly. Thanks to all the voters.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org