On 3/7/12 13:26 , Benedikt Ritter wrote:
Am 7. März 2012 16:13 schrieb Richard S. Hall<[email protected]>:
Yeah, I don't know. The current approach was just intended to be
simple/simplistic.
You'd likely have to create a new project that built all of the existing
projects and then copied the JARs or something...similar to what we do for
the framework in the main/main.distribution projects. Not sure what is best
here, since I'm not an expert maven user either.
What if we pass the locations of all bundles that should be started as
cmd line params?
If users want to try the project from within their IDE, they can
configure a Run configuration that passes, for example
"file:../extenderbased.circle/target/extenderbased.circle-1.0.0.jar"
to static void main
If the application is deployed as a jar outside the workspace, one can
simply pass "extenderbased.circle-1.0.0.jar" (if that jar is in the
same directory) in the command line.
That makes starting it from the command line somewhat of a pain, but in
the end I'm fine with it, since you could also say it is more flexible.
[CUT]
As you can see, javax.swing can not be resolved. ATM I don't know how to
fix that. Any idea how to fix that?
Odd. It work for me:
Then it has to be some maven/eclipse problem. I'll try to solve that
and let you know.
I build and run from the command line.
What's your JIRA user name?
My JIRA user name is britter.
My Confluence user name is benediktritter.
Sorry, I meant your Confluence user name... :-o
I'm sure Marcel can figure it out... :-)
-> richard
Marcel, can you give Benedikt wiki karma?
Thanks.
-> richard
