Okay, fair enough... by why are you calling it "samples-parent"?
Usually -parent modules are themselves top-level projects with no
children, which are used to hold common pom configuration.
I'd recommend simply calling the module "samples" instead.
And we may even want to just make a samples module in the server
tree, since it looks like you are branching this project when the
server is branched. It may be better to add this module to the
server project and simply make it build optionally.
--jason
On Jan 31, 2007, at 1:56 PM, Prasad Kashyap wrote:
The samples-parent was added to have a separate tree for the
individual samples and differentiate them from the
geronimo-samples-archetype child project.
A lot of parent level configuration is applicable only to the samples
tree but not to the archetype. For eg. resources filtering can be
configured at the top for the samples sub-tree but this should not
happen for the archetype.
Cheers
Prasad
On 1/31/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
why is there a 'samples-parent' underweight the top-level 'samples'
project? ie...
<snip>
samples/
pom.xml
samples-parent/
pom.xml
</snip>
This seems very, very odd to me. Why was this done?
--jason
