use maven best practices in build
---------------------------------
Key: SCOUT-82
URL: https://issues.apache.org/jira/browse/SCOUT-82
Project: Scout
Issue Type: Improvement
Components: Scout Implementation
Affects Versions: 1.1
Reporter: David Jencks
Assignee: Kurt T Stam
Fix For: 1.1
I think your build would be a lot easier to deal with if it followed current
maven best pracices.
Since the api jar should not be released in tandem with the scout impl they
should not be part of the same multi-module project. With only one module
scout doesn't need a scout-parent.
Using the apache 6 pom provides most of the infrastructure for a good
policy-compliant build and release to the apache nexus instance using the
maven-release-plugin.
Attached patch is a first step towards this.
It also cleans up and minimizes the dependencies considerably and builds an
osgi bundle rather than plain jar (this just means it has osgi metadata in the
manifest)
I changed to use all geronimo specs. These are validated against the tck so
they may be a better choice than the scout jaxr api which currently won't pass
(see SCOUT-81)
If everyone likes this then the site should probably be moved into the scout
module.
Using the apache 6 pom requires a project to agree to use the apache nexus
instance and add a task to https://issues.apache.org/jira/browse/INFRA-1896.
Basically someone needs to post to the dev list saying "lets use nexus" and
people agree (or at least not -1 the idea).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
