September 2012


Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Chris Hollander <[log in to unmask]>
Reply To:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Sat, 8 Sep 2012 22:52:00 +0200
text/plain (59 lines)
We've been using Maven to compile MASON for a while now. It's really
nice because of how all the dependencies are handled. We had to do a
work around for the way resources (images) are included by making a
new resource folder and dumping them all there, then using a build
variable to include that file for the JARs. If anyone's really
interested, I can send you our POM file for it.

Chris Hollander
University of Central Florida

On Sat, Sep 8, 2012 at 10:38 PM, John Nelson <[log in to unmask]> wrote:
> As per the manual, I know "MASON does not use Ant: Iím an old Unix hacker."
> My guess is, the main reason is also related to priorities, given the
> response Sean gave me regarding git. I also noticed that someone once asked
> the same question without a reply and even ported and pushed MASON 14 to a
> maven repository.
> Has anything changed -- that is, would there now be an interest in using
> Maven? Personally, I really like being able to quickly start a project by
> including a repository and it's dependencies automatically. To be honest,
> there have been times that I used NetLogo over MASON simply because I don't
> feel like going through the initiation motions. (I even made a skeleton
> generator to that end.)
> Ignoring the automatic management benefits, I also think some of Maven's
> features from a library development standpoint are really useful (e.g. mvn
> compile; mvn test; mvn install; mvn publish; etc)
> If you are interested (mostly Sean), I took the liberty of sketching the
> port: You can play with
> it by downloading, unzipping, cding and running:
>> mvn compile
>> mvn exec:java -Dexec.mainClass=sim.display.Console
> Maven's resource inclusion convention differs from the one used by MASON, so
> I had to modify a lot of functions that called X.class.getResource(). In the
> apps package, I only did it for the Ants model, since it would take an hour
> and I don't know how this will be received.
> Also, do a:
>> mvn site
>> mvn javadoc:javadoc
> and take a look at /target/site/index.html
> Let me know what you think. I can finish off the current port if your
> interested.
> // Johnny