You are here: Wiki>Security Web>RecentIssues>MavenMigration (23 May 2007, JanDrewnak)Edit Attach

Maven migration

  • Question: How to restructure the security system's code base for new maven based build process?
  • Problem: Maven projects are designed to produce exactly one "artifact" (a jar, a webapp, ...).
  • Proposal:

Module name
(prefix: 52n-security-) 		Contents Dependencies Status Comments
core
everything you need to build your own implementations of service and client (former common)
none
ready, 1.2-alpha-5
Who will ever need this solely
client
basic service client implementations without GU interfaces (former client)
core
ready, 1.2-alpha-5
~client API
service
basic service implementations without web interfaces (former service)
client, core
ready, 1.2-alpha-5
~service API
wss-webapp
 
service, core
ready, 1.2-SNAPSHOT
was-webapp
 
service, core
ready, 1.2-SNAPSHOT
facade
former extensions.securitysystem
client
ready, 1.2-alpha-5
facade-webapp
 
facade, client
ready, 1.2-rc1
licman-webapp
OWS-4 LicMan Implementation
service, core
ready, 1.2-SNAPSHOT
pap.binding.licensemanager
ows4-gatekeeper
ows4-gatekeeper-webapp
ows4-authz
ows4-authz-webapp
ows4-authn
ows4-authn-webapp

-- JanDrewnak - 23 May 2007
Tags:
create new tag
, view all tags
Edit  | Attach | Print version | History: r2 < r1 | Backlinks | View wiki text | Edit wiki text | More topic actions
Topic revision: r1 - 23 May 2007, JanDrewnak
Legal Notice | Privacy Statement

This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Wiki? Send feedback