[
https://issues.apache.org/jira/browse/TORQUE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922610#comment-17922610
]
Georg Kallidis commented on TORQUE-371:
---------------------------------------
I don't know, if it is only about support for Avalon framework Apache Turbine
web framework, which is still alive does require Avalon, which is, of course
one reason, we should not just drop this. Or probably it's more about support
for more/other frameworks/integrations?
Certainly, if there a needs to do so, or we find another better lightweight
component framework?
My experience is that Avalon until now (this might change in the future) does
just work without apparent workarounds or similar hardships.
What do you suggest? Does it make sense to add another integration? As a very
first step, org.apache.runtime.Torque class could be renamed to TorqueAvalon .
:)
If I 've not missed something ..
> Remove Avalon
> -------------
>
> Key: TORQUE-371
> URL: https://issues.apache.org/jira/browse/TORQUE-371
> Project: Torque
> Issue Type: Task
> Components: Runtime
> Reporter: Max Philipp Wriedt
> Priority: Minor
>
> As Avalon and its successor seem to be gone. We might also remove Avalon?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org
For additional commands, e-mail: torque-dev-h...@db.apache.org
