My thinking on this was to leave it as is for 2.1. We fix this right
for 2.2, when we split the trunk into different svn trees.
Moving the c-m-p configuration settings from configs parent pom to the
root pom is not a problem. It is the boatload of property settings
that will cause Jason good
On Jan 10, 2008, at 11:33 PM, Jacek Laskowski wrote:
On Jan 11, 2008 7:12 AM, David Jencks [EMAIL PROTECTED] wrote:
After the reorganization into plugins most everything still has its
old pom parent, either o.a.g.modules/modules or o.a.g.plugins/
plugins. This seems to me like a bad idea.
On Jan 11, 2008 9:27 AM, David Jencks [EMAIL PROTECTED] wrote:
I guess we'd have to ask a maven expert for a real answer, I just
have a feeling it will lead to trouble, but...
...
The relativePath is just wrong. If we were to make it accurate it
would be
parent
IIRC and [1], the relative path is used if the parent artifact is not
already in the local repository. So a build from the subproject
directory would complain. It is a good idea to fix the relative paths.
The relativePaths will break if someone insists on checking out part
of the server and
After the reorganization into plugins most everything still has its
old pom parent, either o.a.g.modules/modules or o.a.g.plugins/
plugins. This seems to me like a bad idea.
I don't see any problem fixing this for jars, but cars would need the
car plugin setup moved to perhaps the root
On Jan 11, 2008 7:12 AM, David Jencks [EMAIL PROTECTED] wrote:
After the reorganization into plugins most everything still has its
old pom parent, either o.a.g.modules/modules or o.a.g.plugins/
plugins. This seems to me like a bad idea.
Could you elaborate on why this is a bad idea?
Jacek
