On Mon, Oct 27, 2008 at 9:15 AM, Vincent Massol <[email protected]> wrote:
On Oct 27, 2008, at 4:59 PM, Thomas Mortagne wrote:
Hi devs,
I finished a maven build for XWiki+GlassFish+derby distribution.
I think Thomas forgot to mention the reason he did this :) The idea is that the Glassfish project planning a big launch of GF v3 and if we provide this distribution then XWiki will be a partner of the launch thus making advertising for XWiki. This is good for us.
In addition this ties nicely to the mail I sent about a default distribution that could also run in production (see http://tinyurl.com/599sl5) . I suggested using Jetty (I still think we should do this for the default one).
Last Thomas noticed a speed increase with GF+Derby. We need to conduct more tests. At the very minimum the first page loads immediatly I believe which is good. Dunno if it's thanks to GF or Derby though.
I think guess it's more an improvement from derby compared to hsqldb as XWiki do lot's of db access the first time.
So this means a distribution not based on jetty and we can't use database profile to decide what distribution to build anymore.
So I propose:
1) havnig distributions like jetty-hsqldb, glassfish-derby, etc. and to remove distribution we are not releasing/using right now on XE/XEM like hsqldb-pgsql, hsqldb-derby etc.
On maven build this means that to build XE glassfish-derby you will need to execute: - on XE parent : mvn install -Pci,derby,glassfish-derby - on the distribution : mvn install
Why do you need to mvn install the distribution if you specify the profiles in XE top level dir?
This is the two possibilities to build the distributions, not the two things to do :) I forgot the "or"
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.
This will change all distributions ids but I don't think it's a problem.
(since there would now be the container name in the artifact)
2) jetty-hsqldb remain the default distribution for now
Here is my +1 for both
+1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne