[ http://issues.apache.org/jira/browse/DIRTSEC-2?page=comments#action_12460305 ] Alex Karasulu commented on DIRTSEC-2: -------------------------------------
That's funny David this is exactly what I did myself on Dec 19th. I put a bunch of deps into dependencyManagement and updated most of the dependencies to the latest versions. I got the build working too. I don't know what this will do now wrt to your patch so I'll just try to apply it and see what happens. BTW the one thing that I did not do yet was change the groupId. Let me attempt to apply your patch then give more feed back. Thanks! > Bring build into the modern world > --------------------------------- > > Key: DIRTSEC-2 > URL: http://issues.apache.org/jira/browse/DIRTSEC-2 > Project: Triplesec > Issue Type: Bug > Reporter: David Jencks > Assigned To: Alex Karasulu > Attachments: DIR-198.patch > > > I updated the triplesec build to: > - uses groupId org.apache.directory.triplesec > - include all dependency versions in root pom dependencyManagement > - include all plugin versions in root pom pluginManagement > - use latest apacheDS and wicket and a few other projects > - actually build > The attached patch has minimal format changes. It really needs pom cleanup, > but I am reluctant to supply a patch that changes almost every line of every > file involved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
