[path][rfe] maven2 definition for 0.9.5-SNAPSHOT

[GoogleCodeExporter]

* set version to 0.9.5-SNAPSHOT
* clean up : to have simple pom.xml (readable and maintenable)
  * remove duplication between children's pom.xml and parent's pom.xml
(groupId, version, developers, scm, ...)
  * comments scm information, must not be used by maven's plugin (normal
scm point to the root project = directory with the pom.xml for svn)
* define dependencyManagement into the parent's pom.xml to manage version
number in a central point
* change the groupId of higgins to org.eclipse.higgins (follow the convention)
* use ${groupId} and {$version} for dependency to other openid4java
children projects
* upgrade version of jetty to 6.1.6rc0 (and fix the groupId)
* remove optional dependencies of commons-logging (not mark as optional :
every logging system that could be wrapped)
* deploy higgins on a repository http://alchim.sf.net/download/snapshots/
(create pom.xml and a deploy.sh)
* deploy openid4java-0.9.4.339.jar on a repository
http://alchim.sf.net/download/releases/
* remove the build/reporting section from the children project, because
there is to many compilation error due to lake of class.

Because :
* the original project isn't split into several projects, to maintain the
include/exclude of the build will be a hard task
* the full jar isn't currently heavy 600K
* the main goal of the maven sub project is to provide a clear definition
of dependencies
Then 
* I define every dependencies of openid4java to scope provided or test,
remove compile and runtime
* other subproject are converted into "meta-project" (like meta package in
linux distro), provide an empty jar and define the required
(compile/runtime) dependencies.
* I remove the build, reporting section from "meta-project"

So maven user define a dependency of its project with the meta-project (and
not directly with openid4java (may be rename it to
openid4java-core/nodep/... to avoid bug when user will upgrade from 0.9.3
or 0.9.4)

Obviously, when the original project will be split or converted to maven,
the jar generated will be lighter and the pom will be correct and uptodate.

Todo :
* optimise dependencies (eg: does openid4java-infocard depends of
openid4java or openid4java-server ?)
* check the new pom.xml (dependencies) by a core developper
* more end user tests/feedback
* submit fix to maven central repo about 
  * openxri depencencies
  * for a pom for xmlsec-1.3.0

(the changeset is attached to issue (see tracker), it's not a patch but a
directory to install at the save level as maven2 dir, to allow install it
and test it in a parallele directory, if you prefer i could submit a patch
for maven2 directory)

Original issue reported on code.google.com by david.bernard.31 on 7 Oct 2007 at 10:18

Attachments:

• maven2-0.9.5-SNAPSHOT.tar.gz

[GoogleCodeExporter]

Original comment by zhoushu...@gmail.com on 8 Oct 2007 at 3:58

• Changed state: Started

[GoogleCodeExporter]

the svn patch

Original comment by david.bernard.31 on 8 Oct 2007 at 7:06

Attachments:

• maven2.patch

[GoogleCodeExporter]

Fixed.

Original comment by zhoushu...@gmail.com on 10 Oct 2007 at 7:09

• Changed state: Fixed