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 2012/11/06 15:51:48 UTC
[VOTE] Release Turbine 2.3.3 Maven Archetype, Version 1.0.0 based
on staged repository
Hi folks,
the Maven Archetypes have shown to be useful even in development stage.
This is a release candidate for the Maven Archetype to create a Turbine
2.3.3 web application.
Please verify this release candidate and vote...
Tag:
https://svn.apache.org/repos/asf/turbine/maven/archetypes/tags/turbine-webapp-2.3.3-1.0.0
Artifacts:
https://repository.apache.org/content/repositories/orgapacheturbine-025/
[ ] +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: where to start with new template component?
Posted by Thomas Vandahl <tv...@apache.org>.
Hi Georg,
On 25.03.2013 17:24, Georg Kallidis wrote:
> If I would like to integrate another templating mechanism (e.g. Jade)
> instead of or parallel to e.g. Velocity, where would I start? (not that
> I actually would do this right now, but just in case)..
That would be very welcome.
> So, my question is: Would I hook in the existing (Yaafi) component
> fulcrum-template (I do not use it at the moment) or just better look at
> the classes in package org.apache.turbine.services?
The general idea of the Fulcrum components was to make them available to
use-cases outside of Turbine. Right now, the template-service is rather
tightly coupled to the Turbine module concept. This is not to say that
such a templating service could not be useful outside of Turbine. It
would just need a lot of generalization of the interface to make that
happen. If you want to invest that effort, I'll be fine with it. If not,
I'm fine, too.
Bye, Thomas.
PS: Please be aware that the Fulcrum component has not been updated with
the patches that went into the TurbineTemplateService for a long time.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
where to start with new template component?
Posted by Georg Kallidis <ge...@cedis.fu-berlin.de>.
Hello,
I am a little bit at a loss concerning the following case and hopefully
not missed the whole point, but:
If I would like to integrate another templating mechanism (e.g. Jade)
instead of or parallel to e.g. Velocity, where would I start? (not that
I actually would do this right now, but just in case)..
There is an old Howto (Template Service) mentioned in the Fulcrum
project webpage*, and another template related link**; in the VCS/SVN I
find a copy of JSP and Velocity Service (fulcrum-template) - but these
classes (package org.apache.fulcrum.template) have sister classes e.g.
in package org/apache/turbine/services/velocity in the default turbine
module (AND the latter classes are more up-to-date, e.g.
TurbineTemplateService compared to the same class in the other package).
It seems to me, that integration of the templating mechanism as a Yaafi
component is not the way to go... Was it a design decision in the past,
NOT to integrate the templating services into Yaafi? Then may be IMO
fulcrum-template should be removed (may be I missed the right place).
So, my question is: Would I hook in the existing (Yaafi) component
fulcrum-template (I do not use it at the moment) or just better look at
the classes in package org.apache.turbine.services?
Thanks,
Georg
* http://turbine.apache.org/fulcrum/howto/template-service.html
** http://turbine.apache.org/fulcrum/fulcrum-template, which currently
points to the BSF component. BTW: The example shows, how it would be
used as a fulcrum-yaafi, but I cannot find the class TurbineBSFService
only DefaultBSFService.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: [VOTE] Release Turbine 2.3.3 Maven Archetype, Version 1.0.0 based
on staged repository
Posted by Siegfried Goeschl <sg...@gmx.at>.
Hi folks,
> [X] +1 release it
> [ ] +0 go ahead I don't care
> [ ] -1 no, do not release it because
Cheers,
Siegfried Goeschl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: [VOTE] Release Turbine 2.3.3 Maven Archetype, Version 1.0.0 based on staged repository
Posted by Jürgen Hoffmann <ho...@ellumination.de>.
Am 06.11.2012 um 15:51 schrieb Thomas Vandahl <tv...@apache.org>:
> [X] +1 release it
> [ ] +0 go ahead I don't care
> [ ] -1 no, do not release it because
Re: [VOTE] Release Turbine 2.3.3 Maven Archetype, Version 1.0.0 based
on staged repository
Posted by Thomas Vandahl <tv...@apache.org>.
On 06.11.12 15:51, 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
[RESULT] [VOTE] Release Turbine 2.3.3 Maven Archetype, Version 1.0.0
based on staged repository
Posted by Thomas Vandahl <tv...@apache.org>.
On 06.11.12 15:51, Thomas Vandahl wrote:
> the Maven Archetypes have shown to be useful even in development stage.
> This is a release candidate for the Maven Archetype to create a Turbine
> 2.3.3 web application.
> Please verify this release candidate and vote...
Hi folks,
we have three binding +1 votes for the release candidate (in order of
appearance)
- Thomas Vandahl
- Jürgen Hoffmann
- Siegfried Goeschl
and one non-binding +1 vote
- Georg Kallidis
No 0 and -1 votes were cast. The vote has passed. I will be publishing
the artifacts on Nexus shortly (keep your fingers crossed). 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