It builds now. But for some reason torque generates my base and peer-classes into subpackages. I have had this setting for another project but can't figure out why its done like this now. Haven't used maven 1 for a while though...
I found some things that I would like to help improve. From documentation to making the project maven 2 compatible. What would be the next step? Discussing things here? Using JIRA? Or just making the changes I see fit and submitting a patch? /Ludwig -----Original Message----- From: Thomas Vandahl [mailto:[email protected]] Sent: den 10 mars 2010 20:10 To: Turbine Developers List Subject: Re: Fulcrum - state, plan and activity? Ludwig Magnusson wrote: > Hi! > > Working with turbine I extended some of its core components for our project. > There among the torque security service which I thought had some flaws. I > thought I might check the current state of the fulcrum service and see if I > could contribute. However, the torque security service had very many errors, > I could not build it. I also saw that the last checkin was almost two years > ago. The Fulcrum security service contains implementations for Torque, Hibernate, NTLM and an attempt to port the old LDAP service over from Turbine 2.3. The Torque flavour builds fine here using Maven1 and all tests pass - just checked. You need to build and install the Security API first. What errors do you get? > Now I wonder what the plan for turbine and fulcrum is. What components are > prioritized and worked on? Which ones do you want help with and which ones > are dead? The only component left to be released for Turbine 4.0 (M1) as it is right now, is fulcrum-cache. All necessary others have been released during the last months. Besides this, fulcrum-quartz is on my agenda. Bye, Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
