Bernd Fondermann wrote:
On 11/8/06, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
I see that you marked JAMES-665 as Fixed.
https://issues.apache.org/jira/browse/JAMES-665
Shouldn't we include something in our distribution to declare it fixed?
I don't get your question, sorry. What do you mean with "distribution"?
I mean adding it in trunk and make sure that an "ant dist" create also
the spring stuff and maybe a spring-ready package.
The spring wired application could probably be used to debug the
application without using remote debugging (running phoenix inside the
IDE is much more complex than running spring).
Anyway I think we should mark the issue as open (in-progress), because
"fixed in 2.3.0" is misleading. Our 2.3.0 does not work with spring,
even if your prototype could be adapted to work with 2.3.0.
Have you already plan for this or should we consider this branch
"closed", as is, until someone will revamp the issue?
I am still working on it, especially an ant script would be important.
But also integration with other applications.
Ok, you're active on it! Then most thing I wrote does not apply ;-)
So we should updated the "Status:" line in the STATUS file to "active,
completed prototype, in-progress integration" or something similar.
What do you think? Is it feasible to add something to our ant build that
automatically create the spring-ready distribution?
As you can imagine I am not opposing this. But let us wait some weeks
until I (or others) have done more work on it. Especially more
extensive testing. Then we will for sure have some discussion around
this.
OK!
We should avoid to mantain 2 "assembly" files (phoenix + spring) and
maybe we should better create one from the other, or create a common
source for both.
There was some trial and error and trick to make the spring-config
fit. But yes, it would be cool to have something like that. I will
have a check.
Bernd
Yes, I remember you told this, and I had a look at the beans
configuration but I have not spotted the "tricks".
So we'll wait for further news from you in the next weeks. Thank you for
the update.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
