I think this should be resolved - the Maven pom.xml has never been used to build JSecurity - it has only ever existed for others to use for dependency management (auto downloading) in the Maven repository.
It will be quite an exercise to make the build maven compatible, and even then, I'm not sure that most members on the team want to go down that road, as we've debated internally (to some length) before. Of course, with the new team coming in to place, we can have that discussion again at some point, but I'd like to reserve that until after 0.9 final if possible. So, because Maven has never built the product before I don't believe it should be a precondition to resolving a 0.9 issue. Are there still any outstanding objections to me closing the issue? Thanks, Les On Thu, Nov 13, 2008 at 12:30 PM, Alan Cabrera (JIRA) <[EMAIL PROTECTED]> wrote: > > [ > https://issues.apache.org/jira/browse/JSEC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Alan Cabrera reopened JSEC-24: > ------------------------------ > > > Maven build is still broken. Also, when you check in code, please make sure > that the issue numbers are in the checkin comment. > >> Missing org.jsecurity.cache.ehcache.EhCacheManager >> -------------------------------------------------- >> >> Key: JSEC-24 >> URL: https://issues.apache.org/jira/browse/JSEC-24 >> Project: JSecurity >> Issue Type: Bug >> Affects Versions: 0.9-RC1 >> Reporter: Alan Cabrera >> Assignee: Les Hazlewood >> Fix For: 0.9 >> >> >> We seem to be missing org.jsecurity.cache.ehcache.EhCacheManager. The >> CachingSecurityManager seems to need it. For time time being I have >> commented out the code in anticipation to you fixing the problem. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
