27 Oct
2008
27 Oct
'08
6:44 p.m.
Vincent Massol wrote:
On Oct 27, 2008, at 5:51 PM, Sergiu Dumitriu wrote:
Can you remind me what was the problem? I knew we had problems before,
when we decided to split the distribution according to the database, but
I don't remember what was the problem we were facing.
Thomas Mortagne wrote:
And
the amount of duplication is...
I'd rather have just one module, /distribution/. The differences
between
all the poms are minor. I know, the problem is that the released
artifact will need to have a different name. Can't we just use a pom
setting for this? I'm sure we can.
No we cannot.
I went that route initially but it's not possible. The Maven mantra is
one module one artifact and this shouldn't be changed with the current
maven version. It only leads to issues. Also I
think we need to work more on the profiles so that we don't
need to specify both "derby" and "glassfish-derby". Ideally we would
only need to run:
mvn clean install -Pglassfish,derby
Not sure if it's doable or not but I think it might be possible
Well I think
we could do that with something like
/distribution/glassfish/derby with a <profiles> filter at each level. Duplications could be removed by using maven plugins +
shared POM
configurations.
We already do this to a certain limit; we could improve more.
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Sergiu Dumitriu
http://purl.org/net/sergiu/