Jurgen, I am pretty sure that I have seen the same set of errors when I started building 2.3. I think it is related to the version of maven and the version of the torque plugin. From memory, which can be dangerous =:-) I think I compiled the torque-maven plugin from maven b9 and dropped it into the plugins repo in my maven b8 installation, then compiled turbine using maven b8.
Hope this helps, but I don't guarantee it! Regards, Peter On Fri, 2003-06-27 at 10:18, J�rgen Hoffmann wrote: > Hi, > > Ok i see =). We have implemented a quartz scheduler service, that i > would like to share with the community. It is written for turbine 2.2 > and i want to write it for t2.3. This is why I checked out current HEAD. > And did a maven eclipse. After setting the source path correctly i still > get 94 errors in: > > JobEntry.java > TurbineNonPersistentSchedulerService.java > TurbineSchedulerService.java > WorkerThread.java > GroupPeerManagerConstants.java > PermissionPeerManager.java > PermissionPeerManagerConstants.java > RolePeerManager.java > RolePeerManagerConstans.java > UserPeerManager.java > TorqueSecurityService.java > > Did i miss to checkout something? What would be a good way to implement > a quartz scheduler service in t2.3 as an AvalonComponent (I don't know > if that is possible (should be though)), or by extending Service? > > Is the community interested in such a scheduler solution or will the > scheduler code be abandoned? > > Kind regards > > J�rgen Hoffmann > ByteACTION GmbH > > > -----Urspr�ngliche Nachricht----- > Von: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED] > Gesendet: Freitag, 27. Juni 2003 10:36 > An: [EMAIL PROTECTED] > Betreff: Re: O.a.t.ObjectUtils.addOnce > > > =?iso-8859-1?Q?J=FCrgen_Hoffmann?= <[EMAIL PROTECTED]> writes: > > Ugh, right on the spot. :-) > > That's the one where we have no real replacement. Replacement is to use > a data structure which adds a member only once but keeps its sequence. > > I once had such a bugger, called an OrderedSet, and this went into > commons collections as SequencedSet decorator. However, it will be only > available with the next commons collections release (the CVS speaks of > "3.0"). However, I deprecated this so I can remove it in the 2.4-dev > cycle in favour of the SequencedSet. As far as I know, Martin has a > similar construct in the Torque code which could be replaced with > SequencedSet. > > If you want to get rid of the deprecation warning, remove the > @deprecated =;-) Or get a commons-collections snapshot, replace the > underlying Sets with SequencedSet and replace all "addOnce" with "add". > > Regards > Henning -- Peter Courcoux <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
