[
https://issues.apache.org/jira/browse/TORQUE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923216#comment-17923216
]
Georg Kallidis commented on TORQUE-371:
---------------------------------------
yes, IMO Avalon is a very lightweighted xml based DI configuration framework.
I think initialization might be later than using Spring and Turbine has also
annotation aware configuration ..
As long as Torque and Turbine are quite tightly coupled, it makes sense to use
this as default configuration. Besides Torque Turbine has components (called
"Fulcrum") as well.
On the other side, if you want use only Torque it would make sense to allow
Torque to be initialized in a Spring context. May be to do it as an optional
plugin, because if you do not want to use Spring, you do not want all Spring
dependencies included or referenced.
Yes, concerning migrating from svn to git you may want to start to ask this
question on the dev mailing list (I did this a couple of years ago for
Turbine), and if no one complains we could do it. I think the process is
nowadays much easier than before, almost automatic (check if you could access
https://gitbox.apache.org/boxer/). You may want to think about, how Torque
should be set in git - as a single project or not.
> 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
