Maven POM for Swarm uploaded

[Patrick Wright]

Hi all

I just uploaded a Maven 2 POM (pom.xml) for Swarm. Instructions for
use are in the wiki, at
http://code.google.com/p/swarm-dpl/wiki/GettingStartedUsingMaven2.

The Maven-Scala plugin in particular seems a little finicky because we
are using a non-standard source location (./src instead of
./src/main/scala); it should support this (so say the docs), but I
found myself running into problems where it wouldn't recognize the
files had changed. In a clean checkout of Swarm this isn't an issue,
but let me know if there are problems. In any case, if there are
problems, you can continue to use the build.sh and run.sh scripts in
the project.

Regards
Patrick

[Ian Clarke]

Great!

Is there any reason not to move /src to /src/main/scala ?

I'm all for sticking with the standard unless there is a good reason not to.

Ian. 

--
Ian Clarke
CEO, Uprizer Labs
Email: i...@uprizer.com
Ph: +1 512 422 3588
Fax: +1 512 276 6674

[Patrick Wright]

I was going to propose that, but wanted to let you lead on that front.

Standard for Maven would be
src/main/scala - root of Scala sources
src/main/java - any Java (I needed this for JavaSpace entry classes)
src/main/resources - config files
target - build output

If you want to make the move, I can update the POM accordingly.

In the future, if there are multiple backends for pushing the
continuations, we can break the code out to multiple subdirectories,
each with that same basic structure, each with a POM, with the
top-level POM referencing the sub-poms.

Patrick

[Ian Clarke]

Ok, I've made the change and pushed it.  I also updated the build.sh and run.sh scripts accordingly.

Please check that it works for you, and that everything is as it should be.

Ian.

[Patrick Wright]

Committed. Thanks for moving the files around. All of this makes it
somewhat easier to work with the project from the Big 3 Java editors,
which can all set themselves up based on a POM file.

I added a step in the POM which will extract the Scala library and CPS
JARs to target/dependency. Using this means the user has done the
Maven setup described in the wiki; the advantage is that shell scripts
can then reference those JARs (which are a copy of those used for the
builds) instead of references to paths elsewhere on the their system.

We don't need to update the shell script to use those, tho. I added it
in case you or someone else needed an easy way to access the same
versions of the JARs used for the Maven build.

Patrick