Le 05/06/15 17:18, Shawn McKinney a écrit : > 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.
+1 > 2. fortress-master contains installation and configuration documentation > covering the required fortress components (e.g. openldap, apache directory > server, studio, tomcat, etc) I'd rather create a sub-project for that. Maven does not like things that are at the top level. > 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. It would be a profile. +1 > 4. contains target to pull down tomcat and configure to use fortress realm Same : a profile. +1 > 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 Same : a profile. +1 > 8. runs the automated tests to verify the installation I would suggest a sub-project. >
