Hello, Contemplating concerns surrounding upcoming 1.0.0 release. There is consensus that installation and packaging are not yet mature.
I propose we add a new fortress project (fortress-master) to do the following: 1. fortress-master is parent to core, realm, web and rest and child of apache directory project pom. 2. fortress-master contains installation and configuration documentation covering the required fortress components (e.g. openldap, apache directory server, studio, tomcat, etc) 3. fortress-master contains a pom that has targets to pull down the sub-project binaries, source and javadoc by version and installs to local maven repo. 4. contains target to pull down tomcat and configure to use fortress realm 5. contains target to deploy fortress-rest into tomcat 6. contains target to deploy fortress-web into tomcat 7. contains target to perform base load and initialization of target ldap server 8. runs the automated tests to verify the installation What is missing (or wrong) about this list? We may need to do one more interim release, 1.0-RC41, to get these ducks in a row before finalizing with 1.0.0. I want to move fast on these activities, (days not weeks). Best, Shawn [email protected]
