First technical thoughts

[Toni Menzel]

Just looked at MF from a sourcecode perspective and have some (first)
questions i want to share:

1. Build
I read that ant is priorised over maven, which is quite refreshing
(=good).
But as far as i know, the wikipage http://code.google.com/p/modulefusion/wiki/BuildModuleFusion
is out of date.
As a maven2 convict (a standard love/hate relationship) i had to solve
some problems in order to build from scratch.
Currently, my view is that "ant setup package" does the job for sub
projects, but not from project root.
(without module tests it works)

2. IDE setup
Found that MF is prepared for eclipse, so i am eager to prepare it for
IntelliJ (pax developers are used to it - except stuart; last man
standing :)

3. Continnuus Integration ?
I think gcode does not provide a CI Server, right ? Do you think that
a CI Build over at ops4j (see http://ci.ops4j.org) who uses Bamboo
would be suitable ?

4. Assemblies
One requested feature in enterprise environment is sometimes the self-
containment of deliveries.
-- provide a "Fat MF" delivery which contains all artefacts in order
to run. Probably then just ship with default platform (=felix)
-- provide way to create a fat assembly on demand (say, a modulefusion-
creator). Could be a simple build.xml at first.
-- all this is possible with standard paxrunner as of today (pre-run
on build in order to download required artefacts without running the
framework afterwards), but some more thoughts could lead to new
features on paxrunner.

Thats for now, will provide more later.

[Stuart McCulloch]

2009/2/3 Toni Menzel <to...@okidokiteam.com>

Just looked at MF from a sourcecode perspective and have some (first)
questions i want to share:

1. Build
I read that ant is priorised over maven, which is quite  refreshing
(=good).
But as far as i know, the wikipage http://code.google.com/p/modulefusion/wiki/BuildModuleFusion
is out of date.
As a maven2 convict (a standard love/hate relationship) i had to solve
some problems in order to build from scratch.
Currently, my view is that "ant setup package" does the job for sub
projects, but not from project root.
(without module tests it works)

2. IDE setup
Found that MF is prepared for eclipse, so i am eager to prepare it for
IntelliJ (pax developers are used to it - except stuart; last man
standing :)

hehe, you'll have to get me to switch from vi first ;)

3. Continnuus Integration ?
I think gcode does not provide a CI Server, right ? Do you think that
a CI Build over at ops4j (see http://ci.ops4j.org) who uses Bamboo
would be suitable ?

+1  afaik it shouldn't care which subversion repository the code comes from

4. Assemblies
One requested feature in enterprise environment is sometimes the self-
containment of deliveries.
-- provide a "Fat MF" delivery which contains all artefacts in order
to run. Probably then just ship with default platform (=felix)
-- provide way to create a fat assembly on demand (say, a modulefusion-
creator). Could be a simple build.xml at first.
-- all this is possible with standard paxrunner as of today (pre-run
on build in order to download required artefacts without running the
framework afterwards), but some more thoughts could lead to new
features on paxrunner.

yep, I believe this ties in well with Alin's plans for Pax-Runner
 

Thats for now, will provide more later.

--
Cheers, Stuart