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: local policy)
From: "Masanz, James J." <Masanz.James@mayo.edu>
To: "'ctakes-dev@incubator.apache.org'" <ctakes-dev@incubator.apache.org>
Subject: RE: latest build instructions
Thread-Topic: latest build instructions
Thread-Index: 
 AQHNqxLN2Ahvijtz70GdpqoQet0iXpe610RAgABneoCAADSqgIACQnmAgACVuICAACeSAIABOy6AgAFLTgCAAAvSAIAAR5UAgAH9FgCAA9HFMIAAW/6A//+5nqA=
Date: Tue, 23 Oct 2012 17:43:09 +0000
Message-ID: 
 <996FC801C05DF64A84246A106FACACD0028191@MSGPEXCHA08A.mfad.mfroot.org>
References: 
 <5E12F7FD7D58D54DA5542ECC8B145198017949@MSGPEXCHA28B.mfad.mfroot.org>
 <FDF41938-3C31-410A-8B84-8803E7F723A1@colorado.edu>
 <924DE05C19409B438EB81DE683A942D920877B@CHEXMBX1A.CHBOSTON.ORG>
 <924DE05C19409B438EB81DE683A942D9208CC7@CHEXMBX1A.CHBOSTON.ORG>
 <5652E5352040D7429DEF7AAB8560EF0410852955@MCEXMB1.chmccorp.cchmc.org>
 <50816004.7090801@childrens.harvard.edu>
 <924DE05C19409B438EB81DE683A942D9209DA5@CHEXMBX1A.CHBOSTON.ORG>
 <D2A640BB-EB6F-44D3-BDCB-D973E37662C2@colorado.edu>
 <996FC801C05DF64A84246A106FACACD0028123@MSGPEXCHA08A.mfad.mfroot.org>
 <98F3B62F-C30D-4AAD-A5A9-BD83FEF87CDF@colorado.edu>
In-Reply-To: <98F3B62F-C30D-4AAD-A5A9-BD83FEF87CDF@colorado.edu>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

So my updated list of steps I needed, since I was using a downlevel version=
 of m2e:

 - download patch from issue CTAKES-65
 - execute 'svn patch ctakes-jcasgen-maven-plugin.diff'
 - refresh eclipse workspace
 - use context menu option Maven->Update Project Configuration
 - uninstall maven (m2e 1.0) and supporting plugins (Maven SCM Handler for =
Subversive 0.13 etc)
 - install m2e 1.2

Now with Build Automatically I am seeing that if I change a non type system=
 file, type systems are not regen'd.
And if I change a type system file, the type system classes are regenerated=
 and then compiled.

Note, I uninstalled m2e 1.0 because Help->Check for updates was giving me e=
rrors about=20
Cannot complete the install because of a conflicting dependency. Only one o=
f the following can be installed at once:

(full details of the errors are after my signature)

Thanks for the help.

Regards,=20
James Masanz

Cannot complete the install because of a conflicting dependency.
  Software being installed: m2e connector for build-helper-maven-plugin 0.1=
5.0.201109282249 (org.sonatype.m2e.buildhelper.feature.feature.group 0.15.0=
.201109282249)
  Software currently installed: Maven SCM Handler for Subversive 0.13.0.201=
106211115 (org.sonatype.m2e.subversive.feature.feature.group 0.13.0.2011062=
11115)
  Only one of the following can be installed at once:=20
    Maven Integration for Eclipse 1.0.0.20110607-2117 (org.eclipse.m2e.core=
 1.0.0.20110607-2117)
    Maven Integration for Eclipse 1.0.200.20111228-1245 (org.eclipse.m2e.co=
re 1.0.200.20111228-1245)
    Maven Integration for Eclipse 1.2.0.20120903-1050 (org.eclipse.m2e.core=
 1.2.0.20120903-1050)
    Maven Integration for Eclipse 1.1.0.20120530-0009 (org.eclipse.m2e.core=
 1.1.0.20120530-0009)
    Maven Integration for Eclipse 1.0.100.20110804-1717 (org.eclipse.m2e.co=
re 1.0.100.20110804-1717)
  Cannot satisfy dependency:
    From: m2e connector for build-helper-maven-plugin 0.15.0.201109282249 (=
org.sonatype.m2e.buildhelper 0.15.0.201109282249)
    To: bundle org.eclipse.m2e.core [1.1.0,1.2.0)
  Cannot satisfy dependency:
    From: m2e connector for build-helper-maven-plugin 0.15.0.201109282249 (=
org.sonatype.m2e.buildhelper.feature.feature.group 0.15.0.201109282249)
    To: org.sonatype.m2e.buildhelper [0.15.0.201109282249]
  Cannot satisfy dependency:
    From: Maven SCM Handler for Subversive 0.13.0.201106211115 (org.sonatyp=
e.m2e.subversive 0.13.0.201106211115)
    To: bundle org.eclipse.m2e.core [1.0.0,1.1.0)
  Cannot satisfy dependency:
    From: Maven SCM Handler for Subversive 0.13.0.201106211115 (org.sonatyp=
e.m2e.subversive.feature.feature.group 0.13.0.201106211115)
    To: org.sonatype.m2e.subversive [0.13.0.201106211115]


> -----Original Message-----
> From: ctakes-dev-return-669-Masanz.James=3Dmayo.edu@incubator.apache.org
> [mailto:ctakes-dev-return-669-
> Masanz.James=3Dmayo.edu@incubator.apache.org] On Behalf Of Steven Bethard
> Sent: Tuesday, October 23, 2012 11:41 AM
> To: ctakes-dev@incubator.apache.org
> Subject: Re: latest build instructions
>=20
> On Oct 23, 2012, at 10:21 AM, "Masanz, James J." <Masanz.James@mayo.edu>
> wrote:
> > I did these things:
> > - download patch from issue CTAKES-65
> > - svn patch ctakes-jcasgen-maven-plugin.diff
> > - refresh eclipse workspace
> > - use context menu option Maven->Update Project Configuration
> >
> > And I now have 8 errors similar to this shown in my Problems view:
> >
> > Plugin execution not covered by lifecycle configuration:
> org.cleartk:jcasgen-maven-plugin:0.9.3:generate (execution: default,
> phase: process-resources)	pom.xml	/ctakes-assertion	line 27
> 	Maven Project Build Lifecycle Mapping Problem
> >
> > I am still a maven newbie, so I may have missed something obvious. Any
> suggestions?
>=20
> What version of the m2e plugin do you have? You could get this error if
> you were using m2e < 1.1.0. (The current version is 1.2.0.)
>=20
> If you have a current version of m2e, you can check that the jcasgen-
> maven-plugin you have has the necessary "lifecycle-mapping-
> metadata.xml":
>=20
> $ unzip -l ~/.m2/repository/org/cleartk/jcasgen-maven-
> plugin/0.9.3/jcasgen-maven-plugin-0.9.3.jar
> Archive:  /Users/bethard/.m2/repository/org/cleartk/jcasgen-maven-
> plugin/0.9.3/jcasgen-maven-plugin-0.9.3.jar
>   Length     Date   Time    Name
>  --------    ----   ----    ----
>         0  10-20-12 14:08   META-INF/
>       132  10-20-12 14:08   META-INF/MANIFEST.MF
>         0  10-20-12 14:08   META-INF/m2e/
>         0  10-20-12 14:08   META-INF/maven/
>         0  10-20-12 14:08   META-INF/maven/org.cleartk/
>         0  10-20-12 14:08   META-INF/maven/org.cleartk/jcasgen-maven-
> plugin/
>         0  10-20-12 14:08   org/
>         0  10-20-12 14:08   org/cleartk/
>         0  10-20-12 14:08   org/cleartk/plugin/
>       445  10-20-12 14:08   META-INF/m2e/lifecycle-mapping-metadata.xml
>      1518  10-20-12 14:08   META-INF/maven/org.cleartk/jcasgen-maven-
> plugin/plugin-help.xml
>      8325  10-20-12 14:08   META-INF/maven/plugin.xml
>      1688  10-20-12 14:08
> org/cleartk/plugin/JCasGenMojo$JCasGenErrors.class
>       618  10-20-12 14:08
> org/cleartk/plugin/JCasGenMojo$JCasGenException.class
>      1366  10-20-12 14:08
> org/cleartk/plugin/JCasGenMojo$JCasGenProgressMonitor.class
>      8460  10-20-12 14:08   org/cleartk/plugin/JCasGenMojo.class
>      6162  10-20-12 14:08   META-INF/maven/org.cleartk/jcasgen-maven-
> plugin/pom.xml
>       116  10-20-12 14:08   META-INF/maven/org.cleartk/jcasgen-maven-
> plugin/pom.properties
>  --------                   -------
>     28830                   18 files
>=20
> Steve
>=20
> >
> >
> > Regards,
> > James Masanz
> >
> >> -----Original Message-----
> >> From:
> >> ctakes-dev-return-661-Masanz.James=3Dmayo.edu@incubator.apache.org
> >> [mailto:ctakes-dev-return-661-
> >> Masanz.James=3Dmayo.edu@incubator.apache.org] On Behalf Of Steven
> >> Bethard
> >> Sent: Saturday, October 20, 2012 7:52 PM
> >> To: ctakes-dev@incubator.apache.org
> >> Subject: Re: latest build instructions
> >>
> >> On Oct 19, 2012, at 12:29 PM, "Chen, Pei"
> >> <Pei.Chen@childrens.harvard.edu> wrote:
> >>> It seems like this issue is affected enough developers...
> >>> My vote would be to add the custom connector by default in the
> >>> various
> >> pom.xml's as Tim/Steve suggested.
> >>
> >> I've just updated the JCasGen Maven plugin and the cTAKES patch to
> >> use an approach that gets rid of the need for installing an m2e
> >> connector in Eclipse. So it should be a pretty obvious win now to
> >> switch from JCasGenPomFriendly + exec-maven-plugin +
> >> build-helper-maven-plugin to the jcasgen-maven-plugin.
> >>
> >> Please try out the patch as described here:
> >>
> >> https://issues.apache.org/jira/browse/CTAKES-65#comment-13480863
> >>
> >> Steve
> >>
> >> P.S. I think the UIMA folks are going to try to incorporate the
> >> jcasgen- maven-plugin in their next release:
> >>
> >> https://issues.apache.org/jira/browse/UIMA-2471
> >> http://permalink.gmane.org/gmane.comp.apache.uima.general/4368
> >>
> >> So we'd be jumping on the right bandwagon. ;-)
> >