[
https://issues.apache.org/jira/browse/VELOCITY-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478377
]
Henning Schmiedehausen commented on VELOCITY-522:
-------------------------------------------------
You might want to reconsider this, given the fact that e.g. Torque is a heavy
Texen user (actually I think that Texen was specifically invented to be the
base of the O/R layer in Turbine that later became Torque). Torque has a big
user base and screwing them over would be a Bad Thing (TM).
I thought about this for a while and I would suggest the following:
- Deprecate all the Texen and Anakia related classes from the main velocity
tree.
- Factor this code out into org.apache.texen and org.apache.anakia (the package
change is intentional to allow them to be used in parallel with all Velocity
Releases)
- Release these tools immediately (without any further code changes) as
anakia-1.0 and texen-1.0. Make it clear to all depending sub-projects that they
*must* move to these releases ASAP.
- Keep the deprecated classes around for any 1.5.x relase and 1.6
- Remove them in 1.7 and 2.0
- Keep developing Texen and Anakia on their own trees and release early,
release often.
> Remove Anakia and Texen from Engine distribution
> ------------------------------------------------
>
> Key: VELOCITY-522
> URL: https://issues.apache.org/jira/browse/VELOCITY-522
> Project: Velocity
> Issue Type: New Feature
> Components: Anakia, Build, Texen
> Reporter: Will Glass-Husain
> Priority: Minor
> Fix For: 1.6
>
>
> I'd like to see us create separate builds and release cycles for Texen and
> Anakia now that we are TLP.
> ((I thought an issue already existed for this, but couldn't find it)
> In particular, Texen seems to have a minimal user base at this point. Be
> nice to have a separate release that is stable and mature, take it out of the
> Velocity upgrade cycle. If the user community gets excited about it again in
> the future, it'll be easy to add features and issue a new release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
