Folks,
I've spent a little time trying to get to the bottom of ISIS-82, where
the reporter is wondering if there's a local issue with his Eclipse
configuration.
I'm pretty sure that there isn't a problem in the Isis code, ie that it
is "environmental", so I thought I'd have a go at eliminating at least
one variable from the equation, namely his Eclipse IDE setup.
My idea is to allow the developer to be able to package the quickrun app
(for DnD viewer), and then run it entirely from the commandline. I've
therefore spent a bit of time playing around with the shade plugin (to
create an "uber jar") along with the antrun plugin (to allow said uber
jar to be run using java -jar xxx.jar).
This works fine, however the uber jar isn't quite "uber" enough because
it relies on the property files belonging in the config/ directory.
We do, though, offer the ability to pick up config files from the
classpath - this is something we use in the webapp WARs. My suggestion,
therefore, is that the Maven archetype places the isis.properties config
file in the src/main/resources, rather than config/ directory.
With this done, the developer can then package and run the app using:
mvn package ## creates the uber jar target/myapp-1.0-SNAPSHOT.jar
mvn antrun:run -D exec=dnd ## run the uber jar with --viewer dnd
mvn antrun:run -D exec=html ## run the uber jar with --viewer html
mvn antrun:run -D exec=restful ## run the uber jar with --viewer restful
Any objections to me changing the archetype to put config files in
src/main/resources?
Thx
Dan
