Mailing-List: contact ctakes-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ctakes-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of steven.bethard@colorado.edu
 designates 128.138.128.235 as permitted sender)
From: Steven Bethard <steven.bethard@Colorado.EDU>
To: "ctakes-dev@incubator.apache.org" <ctakes-dev@incubator.apache.org>
Date: Fri, 5 Oct 2012 15:27:58 -0600
Subject: Re: Eclipse, Maven and JCasGen
Thread-Topic: Eclipse, Maven and JCasGen
Thread-Index: Ac2jQEslUazm8+e8S+uJFnQXA1VBTg==
Message-ID: <6E568A85-6AD4-4A76-9091-38706AECE2E1@colorado.edu>
References: <705776C9-325E-49FC-A5DF-ACE3434A6AFC@colorado.edu>
In-Reply-To: <705776C9-325E-49FC-A5DF-ACE3434A6AFC@colorado.edu>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On Sep 28, 2012, at 9:58 AM, Steven Bethard <Steven.Bethard@Colorado.EDU> w=
rote:
> 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:
>=20
> Compiling ctakes-type-system/target/generated-sources/...
> Refreshing ctakes-type-system/target/generated-sources/...
>=20
> These tasks run, complete and then immediately start again, and as a resu=
lt, my Eclipse runs very slowly.

So this is still pretty crippling for me. The only way I have found to work=
 on cTAKES right now is to apply the patch I proposed. But every time someo=
ne updates a pom.xml, I get merge conflicts and have to spend a bunch of ti=
me updating the patch.

Any suggestions of what I can do in the meantime?

Or any progress on reviewing the patch in https://issues.apache.org/jira/br=
owse/CTAKES-65?

Steve

> I think the solution is to create a real jcasgen-maven-plugin and a prope=
r m2e connector that only runs JCasGen when the type system has changed (or=
 on project import, or if target/generated-sources/jcasgen is missing, etc.=
).
>=20
> What do you all think? Does this approach sound okay? I have a working pl=
ugin and m2e connector, but I didn't want to just commit the change because=
 if I do, everyone will have to install the m2e connector in their Eclipse =
environment. So I figured we should discuss it first.
>=20
> Steve
>=20
> P.S. For anyone was experiencing the same problem, could you try out the =
following fix?
>=20
> (1) Apply the attached patch to cTAKES trunk, which uses the jcasgen-mave=
n-plugin in the pom.xml files instead of the exec-maven-plugin and build-he=
lper-maven-plugin:
>    $ svn patch ctakes-jcasgen-maven-plugin.diff
>=20
> (2) Open Eclipse, and refresh your cTAKES checkout. You should see a bunc=
h of errors in the Problems view that look like "Project configuration is n=
ot up-to-date with pom.xml. Run Maven->Update Project or use Quick Fix."=20
>=20
> (3) Update the Maven projects as suggested.
>=20
> (4) You should now see some new errors that look like: "Plugin execution =
not covered by lifecycle configuration: org.cleartk:jcasgen-maven-plugin:0.=
9.0:generate (execution: default, phase: generate-sources)"
>=20
> (5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help ->=
 Install New Software=85, add the update site http://cleartk.googlecode.com=
/git/jcasgen-m2e-connector/org.cleartk.plugin.jcasgen.m2e.repo/target/repos=
itory/ and install the "m2e connector for JCasGen Maven plugin". Eclipse wi=
ll restart.
>=20
> (6) Update the Maven projects again, as in step (3). The errors should al=
l be gone now.
>=20
> Some things to try to make sure the fix worked:
>=20
> (1) Check that  JCasGen is no longer be constantly running in the backgro=
und. Go to the Progress view and make sure that eventually you see just "No=
 operations to display at this time."
>=20
> (2) Modify a few non-type-system files and and make sure (in the Progress=
 view again) that JCasGen does not run.
>=20
> (3) Modify a type system, and make sure that JCasGen *does* run. An easy =
way to check this is to change an annotation or feature name and make sure =
you got some new compile errors.
>=20
>=20
> <ctakes-jcasgen-maven-plugin.diff>