Bring build into the modern world

• Key: DIRTSEC-2
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Alex Karasulu
• Reporter: David Jencks
• Fix Version/s: 1.0.0

Description

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.

Comments

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!

[Alex Karasulu]

Ok this patch has some crazy rejects in it. Sorry for asking this but could you svn up and check that you don't have any conflicts? Thanks!

[David Jencks]

Attached patch resolves conflicts with Alex's attempt to do the same thing and also:

- moves all the rest of the dependency versions for external jars to dependencyManagement
- adds a pluginManagement section to specify the versions of all plugins used
- updates some dependency versions (jetty, tomcat at least)
- removes some unused dependencies from dependencyManagement
- uses the geronimo servlet 2.4 and jsp 2.0 spec jars everywhere instead of a mix of servlet 2.3 and 2.4 jars and not-sure-what jsp jars. I prefer to know what spec version I am using from the artifact name.

[David Jencks]

Applied in rev 490644.

There might still be some kind of version mismatch between apacheds components: while the build works fine most of the time I once got an IncompatibleClassChangeError in a webapp-admin test.

I don't seem to have jira privileges to close this yet.

[David Jencks]

Should I be able to close this? I applied my patch.