You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ctakes.apache.org by Steven Bethard <st...@Colorado.EDU> on 2012/09/28 17:58:36 UTC
Eclipse, Maven and JCasGen
Have any of you working on the new cTAKES trunk noticed JCasGen constantly running? I have Eclipse set to "Build Automatically" and I'm constantly seeing tasks 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 result, my Eclipse runs very slowly. Are other people experiencing this too?
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 on project import, or if target/generated-sources/jcasgen is missing, etc.).
What do you all think? Does this approach sound okay? I have a working plugin 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.
Steve
P.S. For anyone was experiencing the same problem, could you try out the following fix?
(1) Apply the attached 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."
(3) Update the Maven projects as suggested.
(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)"
(5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help -> Install New Software…, add the update site http://cleartk.googlecode.com/git/jcasgen-m2e-connector/org.cleartk.plugin.jcasgen.m2e.repo/target/repository/ and install the "m2e connector for JCasGen Maven plugin". Eclipse 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 background. Go to the Progress view and make sure that eventually you see just "No operations to display at this time."
(2) Modify a few non-type-system files and and make sure (in the Progress view again) that JCasGen does not run.
(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.
Re: Eclipse, Maven and JCasGen
Posted by Steven Bethard <st...@Colorado.EDU>.
On Oct 12, 2012, at 12:42 PM, Tim Miller <ti...@childrens.harvard.edu> wrote:
> I'm starting to experience this problem now so I can try this fix --
> Steve, was there supposed to be an attachment for step 1 in your email?
You should use the updated one from the issue:
https://issues.apache.org/jira/browse/CTAKES-65
That's also the best place to comment if things did or did not work.
Steve
Re: Eclipse, Maven and JCasGen
Posted by Tim Miller <ti...@childrens.harvard.edu>.
I'm starting to experience this problem now so I can try this fix --
Steve, was there supposed to be an attachment for step 1 in your email?
On 09/28/2012 11:58 AM, Steven Bethard wrote:
> Have any of you working on the new cTAKES trunk noticed JCasGen constantly running? I have Eclipse set to "Build Automatically" and I'm constantly seeing tasks 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 result, my Eclipse runs very slowly. Are other people experiencing this too?
>
> 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 on project import, or if target/generated-sources/jcasgen is missing, etc.).
>
> What do you all think? Does this approach sound okay? I have a working plugin 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.
>
> Steve
>
> P.S. For anyone was experiencing the same problem, could you try out the following fix?
>
> (1) Apply the attached 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."
>
> (3) Update the Maven projects as suggested.
>
> (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)"
>
> (5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help -> Install New Software…, add the update site http://cleartk.googlecode.com/git/jcasgen-m2e-connector/org.cleartk.plugin.jcasgen.m2e.repo/target/repository/ and install the "m2e connector for JCasGen Maven plugin". Eclipse 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 background. Go to the Progress view and make sure that eventually you see just "No operations to display at this time."
>
> (2) Modify a few non-type-system files and and make sure (in the Progress view again) that JCasGen does not run.
>
> (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.
>
>
Re: Eclipse, Maven and JCasGen
Posted by Steven Bethard <st...@Colorado.EDU>.
On Sep 28, 2012, at 11:06 AM, "Chen, Pei" <Pe...@childrens.harvard.edu> wrote:
> Would one still be able to build from the command line via mvn install in the suggestion?
Yep, from the command line, it would just invoke the jcasgen-maven-plugin directly, essentially in the same way we invoke exec-maven-plugin + build-helper-maven-plugin now. So command line people wouldn't have to do anything extra at all.
> [Not sure if everyone prefers Eclipse as their editor of choice]
For command line people, as I explained above, everything will still work smoothly.
I don't know much about other IDEs, e.g. IntelliJ. If they work now, they probably already run JCasGen on every single file change, like Eclipse does, and the m2e connector won't help them. But it also won't make it any worse - the m2e connector is *only* used in Eclipse, the pom.xml files have no notion of it at all - they just see the regular <plugin> definitions.
Steve
>
>> -----Original Message-----
>> From: Steven Bethard [mailto:steven.bethard@Colorado.EDU]
>> Sent: Friday, September 28, 2012 11:59 AM
>> To: ctakes-dev@incubator.apache.org
>> Subject: Eclipse, Maven and JCasGen
>>
>> Have any of you working on the new cTAKES trunk noticed JCasGen
>> constantly running? I have Eclipse set to "Build Automatically" and I'm
>> constantly seeing tasks 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 result,
>> my Eclipse runs very slowly. Are other people experiencing this too?
>>
>> 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 on
>> project import, or if target/generated-sources/jcasgen is missing, etc.).
>>
>> What do you all think? Does this approach sound okay? I have a working
>> plugin 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.
>>
>> Steve
>>
>> P.S. For anyone was experiencing the same problem, could you try out the
>> following fix?
>>
>> (1) Apply the attached 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."
>>
>> (3) Update the Maven projects as suggested.
>>
>> (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)"
>>
>> (5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help ->
>> Install New Software..., add the update site
>> http://cleartk.googlecode.com/git/jcasgen-m2e-
>> connector/org.cleartk.plugin.jcasgen.m2e.repo/target/repository/ and install
>> the "m2e connector for JCasGen Maven plugin". Eclipse 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 background.
>> Go to the Progress view and make sure that eventually you see just "No
>> operations to display at this time."
>>
>> (2) Modify a few non-type-system files and and make sure (in the Progress
>> view again) that JCasGen does not run.
>>
>> (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.
>>
>
RE: Eclipse, Maven and JCasGen
Posted by "Chen, Pei" <Pe...@childrens.harvard.edu>.
Would one still be able to build from the command line via mvn install in the suggestion?
Alternatively, we could take the jcasgen goal out of the default and have users explicitly call it? Probably not the most ideal, but was just thinking of some simple alternatives.
[Not sure if everyone prefers Eclipse as their editor of choice]
> -----Original Message-----
> From: Steven Bethard [mailto:steven.bethard@Colorado.EDU]
> Sent: Friday, September 28, 2012 11:59 AM
> To: ctakes-dev@incubator.apache.org
> Subject: Eclipse, Maven and JCasGen
>
> Have any of you working on the new cTAKES trunk noticed JCasGen
> constantly running? I have Eclipse set to "Build Automatically" and I'm
> constantly seeing tasks 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 result,
> my Eclipse runs very slowly. Are other people experiencing this too?
>
> 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 on
> project import, or if target/generated-sources/jcasgen is missing, etc.).
>
> What do you all think? Does this approach sound okay? I have a working
> plugin 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.
>
> Steve
>
> P.S. For anyone was experiencing the same problem, could you try out the
> following fix?
>
> (1) Apply the attached 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."
>
> (3) Update the Maven projects as suggested.
>
> (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)"
>
> (5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help ->
> Install New Software..., add the update site
> http://cleartk.googlecode.com/git/jcasgen-m2e-
> connector/org.cleartk.plugin.jcasgen.m2e.repo/target/repository/ and install
> the "m2e connector for JCasGen Maven plugin". Eclipse 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 background.
> Go to the Progress view and make sure that eventually you see just "No
> operations to display at this time."
>
> (2) Modify a few non-type-system files and and make sure (in the Progress
> view again) that JCasGen does not run.
>
> (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.
>
Re: Eclipse, Maven and JCasGen
Posted by Britt Fitch <br...@gmail.com>.
I am in the process of getting my cTAKES environment up and running
and I am experiencing the same build automatically issue *sometimes*.
Initially I created a new workspace using Eclipse Helios and it was
causing the constant build unless I shut off Build Automatically.
I downloaded Eclipse Juno and experienced the same issue, however, if
I shut off Build Automatically and then turn it back on without making
any other changes it appears to prevent the issue. It may happen that
this would start up again if I made any code changes though. I am
still trying to reliably reproduce it or complete my environment
setup, whichever comes first. I will update with more details as I get
them.
Thanks
Britt
On Mon, Oct 8, 2012 at 7:21 PM, Chen, Pei
<Pe...@childrens.harvard.edu> wrote:
> Cool. But, could I suggest we leave the Jira open for at least a few releases? Would like to try out a few more things, see if other developers are experiencing the same, as I think it was a nice feature to have jcasgen done automatically within eclipse IDE.
>
> Sent from my iPad
>
> On Oct 8, 2012, at 6:55 PM, "Masanz, James J." <Ma...@mayo.edu> wrote:
>
>> I like the switch to <ignore/> as a temporary work around at least. I'm not opposed to a maven plugin myself, but I don't know enough about maven yet to have a well informed opinion.
>>
>> I do my cTAKES development in a separate workspace; I see what a pain it would be to turn off Build Automatically in a shared workspace.
>>
>> -- James
>>
>>
>>> -----Original Message-----
>>> From: ctakes-dev-return-530-Masanz.James=mayo.edu@incubator.apache.org
>>> [mailto:ctakes-dev-return-530-Masanz.James=mayo.edu@incubator.apache.org]
>>> On Behalf Of Steven Bethard
>>> Sent: Monday, October 08, 2012 3:10 PM
>>> To: ctakes-dev@incubator.apache.org
>>> Subject: Re: Eclipse, Maven and JCasGen
>>>
>>> On Oct 6, 2012, at 8:53 PM, Steven Bethard <St...@Colorado.EDU>
>>> wrote:
>>>> If people are opposed to doing it the way m2e suggests (writing a
>>> jcasgen-maven-plugin and a connector, as is done in my patch), then I
>>> think the only alternative would be to use <ignore/> instead of <execute/>
>>> so that JCasGen never runs in Eclipse.
>>>
>>> I've just confirmed that switching <execute/> to <ignore/> stops the
>>> constant re-building. Of course, it also disables JCasGen generation of
>>> Java sources, which you have to do manually (e.g. by running `mvn compile`
>>> from the command line).
>>>
>>> Steve
>>>
>>> P.S. I also did a completely fresh install of Eclipse and the plugins, and
>>> I still get the same non-stop "Compiling .../target/generated-sources/..."
>>> messages.
Re: Eclipse, Maven and JCasGen
Posted by "Chen, Pei" <Pe...@childrens.harvard.edu>.
Cool. But, could I suggest we leave the Jira open for at least a few releases? Would like to try out a few more things, see if other developers are experiencing the same, as I think it was a nice feature to have jcasgen done automatically within eclipse IDE.
Sent from my iPad
On Oct 8, 2012, at 6:55 PM, "Masanz, James J." <Ma...@mayo.edu> wrote:
> I like the switch to <ignore/> as a temporary work around at least. I'm not opposed to a maven plugin myself, but I don't know enough about maven yet to have a well informed opinion.
>
> I do my cTAKES development in a separate workspace; I see what a pain it would be to turn off Build Automatically in a shared workspace.
>
> -- James
>
>
>> -----Original Message-----
>> From: ctakes-dev-return-530-Masanz.James=mayo.edu@incubator.apache.org
>> [mailto:ctakes-dev-return-530-Masanz.James=mayo.edu@incubator.apache.org]
>> On Behalf Of Steven Bethard
>> Sent: Monday, October 08, 2012 3:10 PM
>> To: ctakes-dev@incubator.apache.org
>> Subject: Re: Eclipse, Maven and JCasGen
>>
>> On Oct 6, 2012, at 8:53 PM, Steven Bethard <St...@Colorado.EDU>
>> wrote:
>>> If people are opposed to doing it the way m2e suggests (writing a
>> jcasgen-maven-plugin and a connector, as is done in my patch), then I
>> think the only alternative would be to use <ignore/> instead of <execute/>
>> so that JCasGen never runs in Eclipse.
>>
>> I've just confirmed that switching <execute/> to <ignore/> stops the
>> constant re-building. Of course, it also disables JCasGen generation of
>> Java sources, which you have to do manually (e.g. by running `mvn compile`
>> from the command line).
>>
>> Steve
>>
>> P.S. I also did a completely fresh install of Eclipse and the plugins, and
>> I still get the same non-stop "Compiling .../target/generated-sources/..."
>> messages.
RE: Eclipse, Maven and JCasGen
Posted by "Masanz, James J." <Ma...@mayo.edu>.
I like the switch to <ignore/> as a temporary work around at least. I'm not opposed to a maven plugin myself, but I don't know enough about maven yet to have a well informed opinion.
I do my cTAKES development in a separate workspace; I see what a pain it would be to turn off Build Automatically in a shared workspace.
-- James
> -----Original Message-----
> From: ctakes-dev-return-530-Masanz.James=mayo.edu@incubator.apache.org
> [mailto:ctakes-dev-return-530-Masanz.James=mayo.edu@incubator.apache.org]
> On Behalf Of Steven Bethard
> Sent: Monday, October 08, 2012 3:10 PM
> To: ctakes-dev@incubator.apache.org
> Subject: Re: Eclipse, Maven and JCasGen
>
> On Oct 6, 2012, at 8:53 PM, Steven Bethard <St...@Colorado.EDU>
> wrote:
> > If people are opposed to doing it the way m2e suggests (writing a
> jcasgen-maven-plugin and a connector, as is done in my patch), then I
> think the only alternative would be to use <ignore/> instead of <execute/>
> so that JCasGen never runs in Eclipse.
>
> I've just confirmed that switching <execute/> to <ignore/> stops the
> constant re-building. Of course, it also disables JCasGen generation of
> Java sources, which you have to do manually (e.g. by running `mvn compile`
> from the command line).
>
> Steve
>
> P.S. I also did a completely fresh install of Eclipse and the plugins, and
> I still get the same non-stop "Compiling .../target/generated-sources/..."
> messages.
Re: Eclipse, Maven and JCasGen
Posted by Steven Bethard <st...@Colorado.EDU>.
On Oct 6, 2012, at 8:53 PM, Steven Bethard <St...@Colorado.EDU> wrote:
> If people are opposed to doing it the way m2e suggests (writing a jcasgen-maven-plugin and a connector, as is done in my patch), then I think the only alternative would be to use <ignore/> instead of <execute/> so that JCasGen never runs in Eclipse.
I've just confirmed that switching <execute/> to <ignore/> stops the constant re-building. Of course, it also disables JCasGen generation of Java sources, which you have to do manually (e.g. by running `mvn compile` from the command line).
Steve
P.S. I also did a completely fresh install of Eclipse and the plugins, and I still get the same non-stop "Compiling .../target/generated-sources/..." messages.
Re: Eclipse, Maven and JCasGen
Posted by "Wu, Stephen T., Ph.D." <Wu...@mayo.edu>.
> I just tried a fresh download and install and wasn't able to recreate the odd
> behavior:
> I think Steven Wu and Dima was in the process of trying it out as well;
> perhaps we could see what their experience has been as well.
Yeah I can't recreate it either. See below for my setup.
It¹s much more minor but I did find that I had type system errors when I
checked out fresh from
https://svn.apache.org/repos/asf/incubator/ctakes/trunk
I was able to get rid of those type system compile errors by alternating
between two steps (for all projects and also for the individual ones with
leftover errors):
Maven > Update Project Configuration (or Update Dependencies)
point to pom.xml and Run As maven install
I do have Build Automatically set, so I'm not sure why I got what seems like
the opposite behavior that Steve got.
stephen
Mac OSX 10.6.8
Eclipse Java EE IDE for Web Developers Helios Release Build id:
20100617-1415
m2e - Maven Integration for Eclipse 1.0.100.20110804-1717
org.eclipse.m2e.feature.feature.group
m2e - slf4j over logback logging (Optional) 1.0.100.20110804-1717
org.eclipse.m2e.logback.feature.feature.group
m2e connector for build-helper-maven-plugin 0.14.0.201109282148
org.sonatype.m2e.buildhelper.feature.feature.group
m2e connector for mavenarchiver pom properties 0.14.0.201109282148
org.sonatype.m2e.mavenarchiver.feature.feature.group
Maven SCM handler for Subclipse 0.13.0.201107071330
org.sonatype.m2e.subclipse.feature.feature.group
Subclipse (Required) 1.6.18
org.tigris.subversion.subclipse.feature.group
Subclipse Integration for Mylyn 3.x (Optional) 3.0.0
org.tigris.subversion.subclipse.mylyn.feature.group
Subversion Client Adapter (Required) 1.6.12
org.tigris.subversion.clientadapter.feature.feature.group
Subversion JavaHL Native Library Adapter (Required) 1.6.13
org.tigris.subversion.clientadapter.javahl.feature.feature.group
Subversion Revision Graph 1.0.9
org.tigris.subversion.subclipse.graph.feature.feature.group
> My Alt setup:
> Mac OSX 10.7.4
> Eclipse SDK 4.2.1.M20120914-1800 org.eclipse.sdk.ide null
> m2e - Maven Integration for
> Eclipse 1.2.0.20120903-1050 org.eclipse.m2e.feature.feature.group Eclipse.org
> - m2e
> m2e connector for
> build-helper-maven-plugin 0.15.0.201207090124 org.sonatype.m2e.buildhelper.fea
> ture.feature.group Sonatype, Inc.
> m2e connector for mavenarchiver pom
> properties 0.15.0.201207090125 org.sonatype.m2e.mavenarchiver.feature.feature.
> group Sonatype, Inc.
> Maven SCM Handler for
> Subversive 0.13.0.201208191312 org.sonatype.m2e.subversive.feature.feature.gro
> up Sonatype, Inc.
> Subversive SVN
> Connectors 3.0.0.I20120818-1700 org.polarion.eclipse.team.svn.connector.featur
> e.group Polarion Software
> Subversive SVN Team
> Provider 1.0.0.I20120818-1700 org.eclipse.team.svn.feature.group Eclipse.org
> SVNKit 1.7.5.v1 Implementation
> (Optional) 3.0.0.I20120818-1700 org.polarion.eclipse.team.svn.connector.svnkit
> 17.feature.group Polarion Software
> UIMA Runtime 2.4.0 org.apache.uima.runtime.feature.group Apache Software
> Foundation
> UIMA tools (includes
> Runtime) 2.4.0 org.apache.uima.tools.feature.group Apache Software Foundation
>
> ________________________________________
> From: Steven Bethard [steven.bethard@Colorado.EDU]
> Sent: Saturday, October 06, 2012 10:54 PM
> To: ctakes-dev@incubator.apache.org
> Subject: Re: Eclipse, Maven and JCasGen
>
> On Oct 6, 2012, at 8:15 PM, "Masanz, James J." <Ma...@mayo.edu> wrote:
>> Does it behave that way if you turn "Build Automatically" off? Would that be
>> an OK work around for now?
>
> Yes, that works, but it's a pretty inconvenient workaround. Also, Eclipse will
> turn it off for all projects, so I'd have to turn it on and off all the time
> (because I don't only work on cTAKES, obviously).
>
>> Otherwise perhaps a post to UIMA's Users forum?
>
> I'm not sure what I'd ask.
>
> What we're doing right now (using <execute/> in the lifecycle mapping for
> exec-maven-plugin) is strongly discouraged by m2e:
>
> http://wiki.eclipse.org/M2E_plugin_execution_not_covered#execute_plugin_goal
>
> And it's guaranteed to run JCasGen on all java executions:
>
> http://stackoverflow.com/questions/6691723/m2e-generated-code-with-exec-maven-
> plugin
>
> So we know we're doing it wrong, and I'm getting exactly the behavior m2e
> promises when we do that. ;-)
>
> If people are opposed to doing it the way m2e suggests (writing a
> jcasgen-maven-plugin and a connector, as is done in my patch), then I think
> the only alternative would be to use <ignore/> instead of <execute/> so that
> JCasGen never runs in Eclipse.
>
> Steve
>
>
>>
>> ________________________________________
>> From: ctakes-dev-return-520-Masanz.James=mayo.edu@incubator.apache.org
>> [ctakes-dev-return-520-Masanz.James=mayo.edu@incubator.apache.org] on behalf
>> of Steven Bethard [steven.bethard@Colorado.EDU]
>> Sent: Friday, October 05, 2012 4:27 PM
>> To: ctakes-dev@incubator.apache.org
>> Subject: Re: Eclipse, Maven and JCasGen
>>
>> On Sep 28, 2012, at 9:58 AM, Steven Bethard <St...@Colorado.EDU>
>> wrote:
>>> I have Eclipse set to "Build Automatically" and I'm constantly seeing tasks
>>> 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 result,
>>> 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 someone
>> updates a pom.xml, I get merge conflicts and have to spend a bunch of time
>> 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/browse/CTAKES-65?
>>
>> Steve
>>
>>> 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 on
>>> project import, or if target/generated-sources/jcasgen is missing, etc.).
>>>
>>> What do you all think? Does this approach sound okay? I have a working
>>> plugin 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.
>>>
>>> Steve
>>>
>>> P.S. For anyone was experiencing the same problem, could you try out the
>>> following fix?
>>>
>>> (1) Apply the attached 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."
>>>
>>> (3) Update the Maven projects as suggested.
>>>
>>> (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)"
>>>
>>> (5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help ->
>>> Install New SoftwareŠ, add the update site
>>> http://cleartk.googlecode.com/git/jcasgen-m2e-connector/org.cleartk.plugin.j
>>> casgen.m2e.repo/target/repository/ and install the "m2e connector for
>>> JCasGen Maven plugin". Eclipse 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
>>> background. Go to the Progress view and make sure that eventually you see
>>> just "No operations to display at this time."
>>>
>>> (2) Modify a few non-type-system files and and make sure (in the Progress
>>> view again) that JCasGen does not run.
>>>
>>> (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.
>>>
>>>
>>> <ctakes-jcasgen-maven-plugin.diff>
>>
>
RE: Eclipse, Maven and JCasGen
Posted by "Chen, Pei" <Pe...@childrens.harvard.edu>.
I just tried a fresh download and install and wasn't able to recreate the odd behavior:
I think Steven Wu and Dima was in the process of trying it out as well; perhaps we could see what their experience has been as well.
My Alt setup:
Mac OSX 10.7.4
Eclipse SDK 4.2.1.M20120914-1800 org.eclipse.sdk.ide null
m2e - Maven Integration for Eclipse 1.2.0.20120903-1050 org.eclipse.m2e.feature.feature.group Eclipse.org - m2e
m2e connector for build-helper-maven-plugin 0.15.0.201207090124 org.sonatype.m2e.buildhelper.feature.feature.group Sonatype, Inc.
m2e connector for mavenarchiver pom properties 0.15.0.201207090125 org.sonatype.m2e.mavenarchiver.feature.feature.group Sonatype, Inc.
Maven SCM Handler for Subversive 0.13.0.201208191312 org.sonatype.m2e.subversive.feature.feature.group Sonatype, Inc.
Subversive SVN Connectors 3.0.0.I20120818-1700 org.polarion.eclipse.team.svn.connector.feature.group Polarion Software
Subversive SVN Team Provider 1.0.0.I20120818-1700 org.eclipse.team.svn.feature.group Eclipse.org
SVNKit 1.7.5.v1 Implementation (Optional) 3.0.0.I20120818-1700 org.polarion.eclipse.team.svn.connector.svnkit17.feature.group Polarion Software
UIMA Runtime 2.4.0 org.apache.uima.runtime.feature.group Apache Software Foundation
UIMA tools (includes Runtime) 2.4.0 org.apache.uima.tools.feature.group Apache Software Foundation
________________________________________
From: Steven Bethard [steven.bethard@Colorado.EDU]
Sent: Saturday, October 06, 2012 10:54 PM
To: ctakes-dev@incubator.apache.org
Subject: Re: Eclipse, Maven and JCasGen
On Oct 6, 2012, at 8:15 PM, "Masanz, James J." <Ma...@mayo.edu> wrote:
> Does it behave that way if you turn "Build Automatically" off? Would that be an OK work around for now?
Yes, that works, but it's a pretty inconvenient workaround. Also, Eclipse will turn it off for all projects, so I'd have to turn it on and off all the time (because I don't only work on cTAKES, obviously).
> Otherwise perhaps a post to UIMA's Users forum?
I'm not sure what I'd ask.
What we're doing right now (using <execute/> in the lifecycle mapping for exec-maven-plugin) is strongly discouraged by m2e:
http://wiki.eclipse.org/M2E_plugin_execution_not_covered#execute_plugin_goal
And it's guaranteed to run JCasGen on all java executions:
http://stackoverflow.com/questions/6691723/m2e-generated-code-with-exec-maven-plugin
So we know we're doing it wrong, and I'm getting exactly the behavior m2e promises when we do that. ;-)
If people are opposed to doing it the way m2e suggests (writing a jcasgen-maven-plugin and a connector, as is done in my patch), then I think the only alternative would be to use <ignore/> instead of <execute/> so that JCasGen never runs in Eclipse.
Steve
>
> ________________________________________
> From: ctakes-dev-return-520-Masanz.James=mayo.edu@incubator.apache.org [ctakes-dev-return-520-Masanz.James=mayo.edu@incubator.apache.org] on behalf of Steven Bethard [steven.bethard@Colorado.EDU]
> Sent: Friday, October 05, 2012 4:27 PM
> To: ctakes-dev@incubator.apache.org
> Subject: Re: Eclipse, Maven and JCasGen
>
> On Sep 28, 2012, at 9:58 AM, Steven Bethard <St...@Colorado.EDU> wrote:
>> I have Eclipse set to "Build Automatically" and I'm constantly seeing tasks 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 result, 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 someone updates a pom.xml, I get merge conflicts and have to spend a bunch of time 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/browse/CTAKES-65?
>
> Steve
>
>> 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 on project import, or if target/generated-sources/jcasgen is missing, etc.).
>>
>> What do you all think? Does this approach sound okay? I have a working plugin 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.
>>
>> Steve
>>
>> P.S. For anyone was experiencing the same problem, could you try out the following fix?
>>
>> (1) Apply the attached 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."
>>
>> (3) Update the Maven projects as suggested.
>>
>> (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)"
>>
>> (5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help -> Install New Software…, add the update site http://cleartk.googlecode.com/git/jcasgen-m2e-connector/org.cleartk.plugin.jcasgen.m2e.repo/target/repository/ and install the "m2e connector for JCasGen Maven plugin". Eclipse 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 background. Go to the Progress view and make sure that eventually you see just "No operations to display at this time."
>>
>> (2) Modify a few non-type-system files and and make sure (in the Progress view again) that JCasGen does not run.
>>
>> (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.
>>
>>
>> <ctakes-jcasgen-maven-plugin.diff>
>
Re: Eclipse, Maven and JCasGen
Posted by Steven Bethard <st...@Colorado.EDU>.
On Oct 6, 2012, at 8:15 PM, "Masanz, James J." <Ma...@mayo.edu> wrote:
> Does it behave that way if you turn "Build Automatically" off? Would that be an OK work around for now?
Yes, that works, but it's a pretty inconvenient workaround. Also, Eclipse will turn it off for all projects, so I'd have to turn it on and off all the time (because I don't only work on cTAKES, obviously).
> Otherwise perhaps a post to UIMA's Users forum?
I'm not sure what I'd ask.
What we're doing right now (using <execute/> in the lifecycle mapping for exec-maven-plugin) is strongly discouraged by m2e:
http://wiki.eclipse.org/M2E_plugin_execution_not_covered#execute_plugin_goal
And it's guaranteed to run JCasGen on all java executions:
http://stackoverflow.com/questions/6691723/m2e-generated-code-with-exec-maven-plugin
So we know we're doing it wrong, and I'm getting exactly the behavior m2e promises when we do that. ;-)
If people are opposed to doing it the way m2e suggests (writing a jcasgen-maven-plugin and a connector, as is done in my patch), then I think the only alternative would be to use <ignore/> instead of <execute/> so that JCasGen never runs in Eclipse.
Steve
>
> ________________________________________
> From: ctakes-dev-return-520-Masanz.James=mayo.edu@incubator.apache.org [ctakes-dev-return-520-Masanz.James=mayo.edu@incubator.apache.org] on behalf of Steven Bethard [steven.bethard@Colorado.EDU]
> Sent: Friday, October 05, 2012 4:27 PM
> To: ctakes-dev@incubator.apache.org
> Subject: Re: Eclipse, Maven and JCasGen
>
> On Sep 28, 2012, at 9:58 AM, Steven Bethard <St...@Colorado.EDU> wrote:
>> I have Eclipse set to "Build Automatically" and I'm constantly seeing tasks 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 result, 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 someone updates a pom.xml, I get merge conflicts and have to spend a bunch of time 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/browse/CTAKES-65?
>
> Steve
>
>> 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 on project import, or if target/generated-sources/jcasgen is missing, etc.).
>>
>> What do you all think? Does this approach sound okay? I have a working plugin 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.
>>
>> Steve
>>
>> P.S. For anyone was experiencing the same problem, could you try out the following fix?
>>
>> (1) Apply the attached 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."
>>
>> (3) Update the Maven projects as suggested.
>>
>> (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)"
>>
>> (5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help -> Install New Software…, add the update site http://cleartk.googlecode.com/git/jcasgen-m2e-connector/org.cleartk.plugin.jcasgen.m2e.repo/target/repository/ and install the "m2e connector for JCasGen Maven plugin". Eclipse 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 background. Go to the Progress view and make sure that eventually you see just "No operations to display at this time."
>>
>> (2) Modify a few non-type-system files and and make sure (in the Progress view again) that JCasGen does not run.
>>
>> (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.
>>
>>
>> <ctakes-jcasgen-maven-plugin.diff>
>
RE: Eclipse, Maven and JCasGen
Posted by "Masanz, James J." <Ma...@mayo.edu>.
Does it behave that way if you turn "Build Automatically" off? Would that be an OK work around for now?
Otherwise perhaps a post to UIMA's Users forum?
________________________________________
From: ctakes-dev-return-520-Masanz.James=mayo.edu@incubator.apache.org [ctakes-dev-return-520-Masanz.James=mayo.edu@incubator.apache.org] on behalf of Steven Bethard [steven.bethard@Colorado.EDU]
Sent: Friday, October 05, 2012 4:27 PM
To: ctakes-dev@incubator.apache.org
Subject: Re: Eclipse, Maven and JCasGen
On Sep 28, 2012, at 9:58 AM, Steven Bethard <St...@Colorado.EDU> wrote:
> I have Eclipse set to "Build Automatically" and I'm constantly seeing tasks 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 result, 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 someone updates a pom.xml, I get merge conflicts and have to spend a bunch of time 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/browse/CTAKES-65?
Steve
> 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 on project import, or if target/generated-sources/jcasgen is missing, etc.).
>
> What do you all think? Does this approach sound okay? I have a working plugin 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.
>
> Steve
>
> P.S. For anyone was experiencing the same problem, could you try out the following fix?
>
> (1) Apply the attached 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."
>
> (3) Update the Maven projects as suggested.
>
> (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)"
>
> (5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help -> Install New Software…, add the update site http://cleartk.googlecode.com/git/jcasgen-m2e-connector/org.cleartk.plugin.jcasgen.m2e.repo/target/repository/ and install the "m2e connector for JCasGen Maven plugin". Eclipse 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 background. Go to the Progress view and make sure that eventually you see just "No operations to display at this time."
>
> (2) Modify a few non-type-system files and and make sure (in the Progress view again) that JCasGen does not run.
>
> (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.
>
>
> <ctakes-jcasgen-maven-plugin.diff>
Re: Eclipse, Maven and JCasGen
Posted by Steven Bethard <st...@Colorado.EDU>.
On Sep 28, 2012, at 9:58 AM, Steven Bethard <St...@Colorado.EDU> wrote:
> I have Eclipse set to "Build Automatically" and I'm constantly seeing tasks 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 result, 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 someone updates a pom.xml, I get merge conflicts and have to spend a bunch of time 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/browse/CTAKES-65?
Steve
> 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 on project import, or if target/generated-sources/jcasgen is missing, etc.).
>
> What do you all think? Does this approach sound okay? I have a working plugin 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.
>
> Steve
>
> P.S. For anyone was experiencing the same problem, could you try out the following fix?
>
> (1) Apply the attached 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."
>
> (3) Update the Maven projects as suggested.
>
> (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)"
>
> (5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help -> Install New Software…, add the update site http://cleartk.googlecode.com/git/jcasgen-m2e-connector/org.cleartk.plugin.jcasgen.m2e.repo/target/repository/ and install the "m2e connector for JCasGen Maven plugin". Eclipse 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 background. Go to the Progress view and make sure that eventually you see just "No operations to display at this time."
>
> (2) Modify a few non-type-system files and and make sure (in the Progress view again) that JCasGen does not run.
>
> (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.
>
>
> <ctakes-jcasgen-maven-plugin.diff>
RE: Eclipse, Maven and JCasGen
Posted by "Chen, Pei" <Pe...@childrens.harvard.edu>.
Hi Steve,
The rebuilding only happens to me during the first time around if I didn't touch the code. I'm using an older version of Eclipse IDE, but I'll be sure to try this out again this once I upgrade (but I probably won't get a chance to try this out until a few weeks - after cTAKES trunk is in a stable state). Would you mind opening a Jira item as a future enhancement to track this? That way we won't forget...
Thanks,
Pei
> -----Original Message-----
> From: Steven Bethard [mailto:steven.bethard@Colorado.EDU]
> Sent: Saturday, September 29, 2012 9:00 AM
> To: ctakes-dev@incubator.apache.org
> Subject: Re: Eclipse, Maven and JCasGen
>
> On Sep 28, 2012, at 11:04 PM, "Masanz, James J."
> <Ma...@mayo.edu> wrote:
> > I have build automatically on and I am not seeing a problem with JCasGen
> running unexpectedly.
> > I am using
> > Eclipse 4.2.1 32bit
> > m2e 1.0.100.20110804-1717
> > Subversive SVN 1.7 SVN Kit Connector (3.0.0.I20120818-1700 Subversive
> > SVN Connectors (3.0.0.I20120818-1700 the UIMA plugin for 2.4.0
> >
> > This is on Win7
>
> Here's my setup:
>
> OSX 10.8.2 (Mountain Lion)
> Eclipse SDK 4.2.1.M20120914-1800
> m2e 1.2.0.20120903-1050
> UIMA tools (includes Runtime) 2.4.0
>
> I also had the same problem with m2e 1.1.0 - I upgraded to 1.2.0 in part to
> see if the problem would go away.
>
> For what it's worth, if I revert my patch and allow m2e to update the projects
> (as it demands), the JCasGen behavior starts back up again immediately.
>
> Steve
>
> >
> > -- James
> > ________________________________________
> > From: ctakes-dev-return-462-
> Masanz.James=mayo.edu@incubator.apache.org
> > [ctakes-dev-return-462-Masanz.James=mayo.edu@incubator.apache.org]
> on
> > behalf of Steven Bethard [steven.bethard@Colorado.EDU]
> > Sent: Friday, September 28, 2012 4:52 PM
> > To: ctakes-dev@incubator.apache.org
> > Subject: Re: Eclipse, Maven and JCasGen
> >
> > Yep, just checked out the trunk and imported it into Eclipse. I don't even
> need to make a change - it starts running JCasGen repeatedly before I do
> anything. Do you have "Build Automatically" on?
> >
> > I'm also interested in hearing how many other people have experienced
> this.
> >
> > That said, it's totally impossible for me to work on cTAKES as it currently
> stands, and the fix I proposed makes it possible again. So without the fix, or
> something like it, I probably won't be able to contribute to cTAKES very well.
> >
> > Steve
> >
> > On Sep 28, 2012, at 11:22 AM, Tim Miller
> <ti...@childrens.harvard.edu> wrote:
> >
> >> I'm having trouble recreating the behavior. You just have the trunk
> >> checked out and make a change in eclipse and it re-runs jcasgen?
> >> Anyone else seeing this before we try to fix it?
> >>
> >>
> >> On 09/28/2012 11:58 AM, Steven Bethard wrote:
> >>> Have any of you working on the new cTAKES trunk noticed JCasGen
> constantly running? I have Eclipse set to "Build Automatically" and I'm
> constantly seeing tasks 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
> result, my Eclipse runs very slowly. Are other people experiencing this too?
> >>>
> >>> 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 on project import, or if target/generated-sources/jcasgen is missing,
> etc.).
> >>>
> >>> What do you all think? Does this approach sound okay? I have a working
> plugin 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.
> >>>
> >>> Steve
> >>>
> >>> P.S. For anyone was experiencing the same problem, could you try out
> the following fix?
> >>>
> >>> (1) Apply the attached 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."
> >>>
> >>> (3) Update the Maven projects as suggested.
> >>>
> >>> (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)"
> >>>
> >>> (5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help -
> > Install New Software..., add the update site
> http://cleartk.googlecode.com/git/jcasgen-m2e-
> connector/org.cleartk.plugin.jcasgen.m2e.repo/target/repository/ and install
> the "m2e connector for JCasGen Maven plugin". Eclipse 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
> background. Go to the Progress view and make sure that eventually you see
> just "No operations to display at this time."
> >>>
> >>> (2) Modify a few non-type-system files and and make sure (in the
> Progress view again) that JCasGen does not run.
> >>>
> >>> (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.
> >>>
> >>>
> >>
> >
Re: Eclipse, Maven and JCasGen
Posted by Steven Bethard <st...@Colorado.EDU>.
On Sep 28, 2012, at 11:04 PM, "Masanz, James J." <Ma...@mayo.edu> wrote:
> I have build automatically on and I am not seeing a problem with JCasGen running unexpectedly.
> I am using
> Eclipse 4.2.1 32bit
> m2e 1.0.100.20110804-1717
> Subversive SVN 1.7 SVN Kit Connector (3.0.0.I20120818-1700
> Subversive SVN Connectors (3.0.0.I20120818-1700
> the UIMA plugin for 2.4.0
>
> This is on Win7
Here's my setup:
OSX 10.8.2 (Mountain Lion)
Eclipse SDK 4.2.1.M20120914-1800
m2e 1.2.0.20120903-1050
UIMA tools (includes Runtime) 2.4.0
I also had the same problem with m2e 1.1.0 - I upgraded to 1.2.0 in part to see if the problem would go away.
For what it's worth, if I revert my patch and allow m2e to update the projects (as it demands), the JCasGen behavior starts back up again immediately.
Steve
>
> -- James
> ________________________________________
> From: ctakes-dev-return-462-Masanz.James=mayo.edu@incubator.apache.org [ctakes-dev-return-462-Masanz.James=mayo.edu@incubator.apache.org] on behalf of Steven Bethard [steven.bethard@Colorado.EDU]
> Sent: Friday, September 28, 2012 4:52 PM
> To: ctakes-dev@incubator.apache.org
> Subject: Re: Eclipse, Maven and JCasGen
>
> Yep, just checked out the trunk and imported it into Eclipse. I don't even need to make a change - it starts running JCasGen repeatedly before I do anything. Do you have "Build Automatically" on?
>
> I'm also interested in hearing how many other people have experienced this.
>
> That said, it's totally impossible for me to work on cTAKES as it currently stands, and the fix I proposed makes it possible again. So without the fix, or something like it, I probably won't be able to contribute to cTAKES very well.
>
> Steve
>
> On Sep 28, 2012, at 11:22 AM, Tim Miller <ti...@childrens.harvard.edu> wrote:
>
>> I'm having trouble recreating the behavior. You just have the trunk
>> checked out and make a change in eclipse and it re-runs jcasgen? Anyone
>> else seeing this before we try to fix it?
>>
>>
>> On 09/28/2012 11:58 AM, Steven Bethard wrote:
>>> Have any of you working on the new cTAKES trunk noticed JCasGen constantly running? I have Eclipse set to "Build Automatically" and I'm constantly seeing tasks 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 result, my Eclipse runs very slowly. Are other people experiencing this too?
>>>
>>> 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 on project import, or if target/generated-sources/jcasgen is missing, etc.).
>>>
>>> What do you all think? Does this approach sound okay? I have a working plugin 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.
>>>
>>> Steve
>>>
>>> P.S. For anyone was experiencing the same problem, could you try out the following fix?
>>>
>>> (1) Apply the attached 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."
>>>
>>> (3) Update the Maven projects as suggested.
>>>
>>> (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)"
>>>
>>> (5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help -> Install New Software…, add the update site http://cleartk.googlecode.com/git/jcasgen-m2e-connector/org.cleartk.plugin.jcasgen.m2e.repo/target/repository/ and install the "m2e connector for JCasGen Maven plugin". Eclipse 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 background. Go to the Progress view and make sure that eventually you see just "No operations to display at this time."
>>>
>>> (2) Modify a few non-type-system files and and make sure (in the Progress view again) that JCasGen does not run.
>>>
>>> (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.
>>>
>>>
>>
>
RE: Eclipse, Maven and JCasGen
Posted by "Masanz, James J." <Ma...@mayo.edu>.
I have build automatically on and I am not seeing a problem with JCasGen running unexpectedly.
I am using
Eclipse 4.2.1 32bit
m2e 1.0.100.20110804-1717
Subversive SVN 1.7 SVN Kit Connector (3.0.0.I20120818-1700
Subversive SVN Connectors (3.0.0.I20120818-1700
the UIMA plugin for 2.4.0
This is on Win7
-- James
________________________________________
From: ctakes-dev-return-462-Masanz.James=mayo.edu@incubator.apache.org [ctakes-dev-return-462-Masanz.James=mayo.edu@incubator.apache.org] on behalf of Steven Bethard [steven.bethard@Colorado.EDU]
Sent: Friday, September 28, 2012 4:52 PM
To: ctakes-dev@incubator.apache.org
Subject: Re: Eclipse, Maven and JCasGen
Yep, just checked out the trunk and imported it into Eclipse. I don't even need to make a change - it starts running JCasGen repeatedly before I do anything. Do you have "Build Automatically" on?
I'm also interested in hearing how many other people have experienced this.
That said, it's totally impossible for me to work on cTAKES as it currently stands, and the fix I proposed makes it possible again. So without the fix, or something like it, I probably won't be able to contribute to cTAKES very well.
Steve
On Sep 28, 2012, at 11:22 AM, Tim Miller <ti...@childrens.harvard.edu> wrote:
> I'm having trouble recreating the behavior. You just have the trunk
> checked out and make a change in eclipse and it re-runs jcasgen? Anyone
> else seeing this before we try to fix it?
>
>
> On 09/28/2012 11:58 AM, Steven Bethard wrote:
>> Have any of you working on the new cTAKES trunk noticed JCasGen constantly running? I have Eclipse set to "Build Automatically" and I'm constantly seeing tasks 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 result, my Eclipse runs very slowly. Are other people experiencing this too?
>>
>> 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 on project import, or if target/generated-sources/jcasgen is missing, etc.).
>>
>> What do you all think? Does this approach sound okay? I have a working plugin 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.
>>
>> Steve
>>
>> P.S. For anyone was experiencing the same problem, could you try out the following fix?
>>
>> (1) Apply the attached 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."
>>
>> (3) Update the Maven projects as suggested.
>>
>> (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)"
>>
>> (5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help -> Install New Software…, add the update site http://cleartk.googlecode.com/git/jcasgen-m2e-connector/org.cleartk.plugin.jcasgen.m2e.repo/target/repository/ and install the "m2e connector for JCasGen Maven plugin". Eclipse 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 background. Go to the Progress view and make sure that eventually you see just "No operations to display at this time."
>>
>> (2) Modify a few non-type-system files and and make sure (in the Progress view again) that JCasGen does not run.
>>
>> (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.
>>
>>
>
Re: Eclipse, Maven and JCasGen
Posted by Steven Bethard <st...@Colorado.EDU>.
Yep, just checked out the trunk and imported it into Eclipse. I don't even need to make a change - it starts running JCasGen repeatedly before I do anything. Do you have "Build Automatically" on?
I'm also interested in hearing how many other people have experienced this.
That said, it's totally impossible for me to work on cTAKES as it currently stands, and the fix I proposed makes it possible again. So without the fix, or something like it, I probably won't be able to contribute to cTAKES very well.
Steve
On Sep 28, 2012, at 11:22 AM, Tim Miller <ti...@childrens.harvard.edu> wrote:
> I'm having trouble recreating the behavior. You just have the trunk
> checked out and make a change in eclipse and it re-runs jcasgen? Anyone
> else seeing this before we try to fix it?
>
>
> On 09/28/2012 11:58 AM, Steven Bethard wrote:
>> Have any of you working on the new cTAKES trunk noticed JCasGen constantly running? I have Eclipse set to "Build Automatically" and I'm constantly seeing tasks 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 result, my Eclipse runs very slowly. Are other people experiencing this too?
>>
>> 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 on project import, or if target/generated-sources/jcasgen is missing, etc.).
>>
>> What do you all think? Does this approach sound okay? I have a working plugin 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.
>>
>> Steve
>>
>> P.S. For anyone was experiencing the same problem, could you try out the following fix?
>>
>> (1) Apply the attached 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."
>>
>> (3) Update the Maven projects as suggested.
>>
>> (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)"
>>
>> (5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help -> Install New Software…, add the update site http://cleartk.googlecode.com/git/jcasgen-m2e-connector/org.cleartk.plugin.jcasgen.m2e.repo/target/repository/ and install the "m2e connector for JCasGen Maven plugin". Eclipse 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 background. Go to the Progress view and make sure that eventually you see just "No operations to display at this time."
>>
>> (2) Modify a few non-type-system files and and make sure (in the Progress view again) that JCasGen does not run.
>>
>> (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.
>>
>>
>
Re: Eclipse, Maven and JCasGen
Posted by Tim Miller <ti...@childrens.harvard.edu>.
I'm having trouble recreating the behavior. You just have the trunk
checked out and make a change in eclipse and it re-runs jcasgen? Anyone
else seeing this before we try to fix it?
On 09/28/2012 11:58 AM, Steven Bethard wrote:
> Have any of you working on the new cTAKES trunk noticed JCasGen constantly running? I have Eclipse set to "Build Automatically" and I'm constantly seeing tasks 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 result, my Eclipse runs very slowly. Are other people experiencing this too?
>
> 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 on project import, or if target/generated-sources/jcasgen is missing, etc.).
>
> What do you all think? Does this approach sound okay? I have a working plugin 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.
>
> Steve
>
> P.S. For anyone was experiencing the same problem, could you try out the following fix?
>
> (1) Apply the attached 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."
>
> (3) Update the Maven projects as suggested.
>
> (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)"
>
> (5) Install the m2e connector for the jcasgen-maven-plugin. Go to Help -> Install New Software…, add the update site http://cleartk.googlecode.com/git/jcasgen-m2e-connector/org.cleartk.plugin.jcasgen.m2e.repo/target/repository/ and install the "m2e connector for JCasGen Maven plugin". Eclipse 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 background. Go to the Progress view and make sure that eventually you see just "No operations to display at this time."
>
> (2) Modify a few non-type-system files and and make sure (in the Progress view again) that JCasGen does not run.
>
> (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.
>
>