It may actually be a maven issue:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=284928
I'm a little swamped right now, but I'd like to try setting up a
non-maven project with two source folders:
src/main/java
src/main/resources
like ours, and see if this issue persists.
Tim
On 04/23/2013 11:21 AM, Masanz, James J. wrote:
I'm having the same issue.
I tried just creating a jar instead of a runnable jar and get the same.
Tim, I don't know if it's 1, 2 or 3.
-- James
-----Original Message-----
From: [email protected] [mailto:dev-
[email protected]] On Behalf Of Miller,
Timothy
Sent: Sunday, April 21, 2013 7:23 AM
To: [email protected]
Subject: export runnable jar issue
I've found it useful to "export runnable jar" to create a single file that
can be run with 'java -jar' on a server/cluster for a given run
configuration. There is an issue that may be an eclipse bug but also may
be a ctakes issue.
The issue is that files under src/main/java source folders export exactly
as expected, while files under src/main/resources folders export with the
"resources" folder prepended. So you will get the following classpaths in
the jar:
org/apache/ctakes/someproject/SomeCode.class
resources/org/apache/ctakes/someproject/some_model.bin
This obviously screws up important classpaths at runtime. I can workaround
it, but does anyone have a sense of whether this issue is:
1) Clearly an eclipse issue with nothing we can do except try to notify
someone
2) An eclipse issue but there is something we're doing wrong (like a
convention for resources we're not following that would fix this)
3) Clearly a ctakes issue
Tim
