Hi all, I have been watching the large numbers of posts about not being able to build Turbine due to the Torque plugin problems. And while granted, it is an issue with Maven, I also want to remove the torque jars from my project.xml since I don't use Turbine's security or the scheduler service. However, this causes problems because Turbine needs Torque, even when you don't use it.
What is stopping us from removing the security code and scheduler service from Turbine, and putting them in Fulcrum's core? Is it because we are trying to get to 2.3? Or because no one has tackled the effort? it seems that now that Torque has been Avalonized (thanks henning) that we should do the same with the components that use Torque. I am willing to signup my name next to this, but I need some confirmation that this is the path we want, and that we will remove the code from Turbine that is in Fulcrum. As an aside, the duplicated code in Turbine and Fulcrum means that in Eclipse, when I popup my imports, I am constantly guessing which jar to import my classes from, Turbine or Fulcrum! On a related note, when can we remove the Criteria object from the interfaces for security like UserManager? I would be willing to live with Criteria just being an Object, not a criteria, and casting it one way in DBUserManager, and another way in PassiveUserManager. Heck, then if we had HibernateUserManager then the criteria object could be a Hibernate HQL query! Frustrated with polluted interfaces, Eric Pugh --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
