Fix URL, TLP pom version numbering doesn't seems to have minor versions. Just sequent numbering
The top level Maven Project Object Model (POM) for Directory is used to centralize information about the Directory Project which is common to all projects at the TLP. It can be used in the POM inheritance tree to make sure subprojects use the appropriate repositories and contain the same information that can be managed centrally rather than duplicated in every subproject's master POM file.
The top level POM was used initially to build all the projects at Directory which is a bit out of line with what it should really have been used for as stated above. Hence it has directives now to build all the subprojects like shared and daemon as well as apacheds. This causes it's misuse to facilitate building ApacheDS and all it's dependencies in one big build. This must stop because this usage makes it inconvenient to use for building other projects like Triplesec and Apache Directory Studio once it moves to Maven.
Futhermore because of the limitations of subversion externals directives this file is being copied into a directory that contains all the ApacheDS external dependencies. SVN does not allow an externals link on a file. Externals can only be used with directories. So the file is being copied to build ADS in different branches and we're failing to properly version this file.
Another issue regarding the TLP POM file for Directory exists due to a Maven bug. Maven cannot resolve and download SNAPSHOT parent POMs it seems. So if projects refer to this TLP POM as their parent they must refer to a non-SNAPSHOT version of it. Otherwise when attempting to build the subproject the build will fail. For example if the daemon subproject refers to 1.0.5-SNAPSHOT of the TLP POM as it's parent the build for the daemon project will fail unless this 1.0.5-SNAPSHOT pom.xml file is in the directory above the daemon sources and the build is issued one level above the daemon folder. If of course the 1.0.5-SNAPSHOT is already in the local repository then there is no problem. This situation prevents successful builds on fresh checkouts of subprojects like daemon or apacheds when the parent TLP POM is a SNAPSHOT.
Once a new version of the TLP POM is created it is to be tagged here:
The POM itself resides in the trunk of the tlp-common project today. Once tagged the request can be made to the dev list to publish (release) this POM. After a 4 hr grace period the POM can be deployed to the ibiblio sync repos
Only PMC members are allowed to release this POM since it requires special handling and information associated with the TLP. Normal committers must request that a PMC member handle the publishing of this file.
Releases of this POM need not branch the POM file since it's essentially for on branch of progress reflecting the entire TLP. The revision can simply be incremented up to the next number.