Mailing-List: contact ctakes-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ctakes-dev@incubator.apache.org
Date: Tue, 2 Oct 2012 13:15:07 +1100 (NCT)
From: "Steven Bethard (JIRA)" <jira@apache.org>
To: ctakes-dev@incubator.apache.org
Message-ID: <1210208650.152673.1349144107473.JavaMail.jiratomcat@arcas>
In-Reply-To: <499880843.152578.1349143867913.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (CTAKES-65) JCasGen runs constantly in Eclise
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CTAKES-65?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Bethard updated CTAKES-65:
---------------------------------

    Attachment: ctakes-jcasgen-maven-plugin.diff

I think the solution is to create a real jcasgen-maven-plugin and a proper =
m2e connector that only runs JCasGen when the type system has changed (or o=
n project import, or if target/generated-sources/jcasgen is missing, etc.).=
 Here's the instructions to try this out:

(1) Apply the patch to cTAKES trunk, which uses the jcasgen-maven-plugin in=
 the pom.xml files instead of the exec-maven-plugin and build-helper-maven-=
plugin:
   $ svn patch ctakes-jcasgen-maven-plugin.diff

(2) Open Eclipse, and refresh your cTAKES checkout. You should see a bunch =
of errors in the Problems view that look like "Project configuration is not=
 up-to-date with pom.xml. Run Maven->Update Project or use Quick Fix."=20

(3) Update the Maven projects as suggested.

(4) You should now see some new errors that look like: "Plugin execution no=
t covered by lifecycle configuration: org.cleartk:jcasgen-maven-plugin:0.9.=
0:generate (execution: default, phase: generate-sources)"

(5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help -> I=
nstall New Software=E2=80=A6, add the update site http://cleartk.googlecode=
.com/git/jcasgen-m2e-connector/org.cleartk.plugin.jcasgen.m2e.repo/target/r=
epository/ and install the "m2e connector for JCasGen Maven plugin". Eclips=
e will restart.

(6) Update the Maven projects again, as in step (3). The errors should all =
be gone now.

Some things to try to make sure the fix worked:

(1) Check that  JCasGen is no longer be constantly running in the backgroun=
d. Go to the Progress view and make sure that eventually you see just "No o=
perations to display at this time."

(2) Modify a few non-type-system files and and make sure (in the Progress v=
iew again) that JCasGen does not run.

(3) Modify a type system, and make sure that JCasGen *does* run. An easy wa=
y to check this is to change an annotation or feature name and make sure yo=
u got some new compile errors.
               =20
> JCasGen runs constantly in Eclise
> ---------------------------------
>
>                 Key: CTAKES-65
>                 URL: https://issues.apache.org/jira/browse/CTAKES-65
>             Project: cTAKES
>          Issue Type: Bug
>            Reporter: Steven Bethard
>             Fix For: 3.0-incubating
>
>         Attachments: ctakes-jcasgen-maven-plugin.diff
>
>
> I have Eclipse set to "Build Automatically" and I'm constantly seeing tas=
ks running in the background in my Progress view that look like:
> Compiling ctakes-type-system/target/generated-sources/...
> Refreshing ctakes-type-system/target/generated-sources/...
> These tasks run, complete and then immediately start again, and as a resu=
lt, my Eclipse runs very slowly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira