David Jencks wrote:
On May 20, 2008, at 11:27 AM, Daniel Kulp wrote:
The issue is how does it resolve:
<parent>
<groupId>org.apache.geronimo.samples</groupId>
<artifactId>samples</artifactId>
<version>2.2-SNAPSHOT</version>
</parent>
It needs to resolve that first to resolve the apache:apache:4
Without the snapshot repo defined, it won't resolve that.
Dan
Good point. So, it seems to me we have a 2-faced approach to the
samples.... do we want them to be individual projects or one big
project? I _think_ the main value of the parent pom is to define
dependency management. I suggest that we either:
- figure it's one big project, and snapshot versions can only be built
all together (first time): we leave out the apache-snapshots and rely on
the on in apache v4 pom
I think we have to treat this like one big project and require an
initial build. There isn't much more involved than building an
individual sample.
<soapbox>
Actually ... I think samples ought to be integrated into the server svn
again. I think the fact that we have never released samples
independently and the fact that we are now 3 months past our Server 2.1
release and we still don't have samples testify to why it isn't a good
idea to have them split. Also, I can think of no good reason to release
samples independently of a server release (and again - we have never doe
this anyway).
</soapbox>
- figure they are individual projects, have the parent for each sample
be genesis project-config, and use the new import feature in maven 2.0.9
to get the universal dependency management section from what is now the
parent. I think this will involve releasing each sample individually.
If we have to release samples individually it will never happen.
Right now I lean slightly towards the first approach. I ___really___
think we should not be duplicating information already present in parent
poms because we can't decide what the boundaries of an independently
buildable project are.
I definitely think we should be taking the 1st approach. BTW, if we
treat them as one big project we can begin to use dependency management
in the parent pom. At the moment we have version dependencies spread
across numerous samples which is really a maintenance problem (in that
nobody is maintaining it ... another issue that could be easily solved
if we moved the samples back into the server svn).
Joe
