Mailing-List: contact dev-help@ctakes.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ctakes.apache.org
Received-SPF: pass (athena.apache.org: domain of
 Timothy.Miller@childrens.harvard.edu designates 134.174.13.92 as permitted
 sender)
From: "Miller, Timothy" <Timothy.Miller@childrens.harvard.edu>
To: "dev@ctakes.apache.org" <dev@ctakes.apache.org>
Subject: export runnable jar issue
Thread-Topic: export runnable jar issue
Thread-Index: Ac4+iwaGqLCFiR8bS/OaQpU+0pRbIw==
Date: Sun, 21 Apr 2013 12:23:27 +0000
Message-ID: <E084D8EFE2B03A408B324458C5212E9421133F39@CHEXMBX3A.CHBOSTON.ORG>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I've found it useful to "export runnable jar" to create a single file=0A=
that can be run with 'java -jar' on a server/cluster for a given run=0A=
configuration. There is an issue that may be an eclipse bug but also may=0A=
be a ctakes issue.=0A=
=0A=
The issue is that files under src/main/java source folders export=0A=
exactly as expected, while files under src/main/resources folders export=0A=
with the "resources" folder prepended. So you will get the following=0A=
classpaths in the jar:=0A=
=0A=
org/apache/ctakes/someproject/SomeCode.class=0A=
resources/org/apache/ctakes/someproject/some_model.bin=0A=
=0A=
This obviously screws up important classpaths at runtime. I can=0A=
workaround it, but does anyone have a sense of whether this issue is:=0A=
1) Clearly an eclipse issue with nothing we can do except try to notify=0A=
someone=0A=
2) An eclipse issue but there is something we're doing wrong (like a=0A=
convention for resources we're not following that would fix this)=0A=
3) Clearly a ctakes issue=0A=
=0A=
Tim=0A=