[ https://issues.apache.org/jira/browse/CTAKES-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018151#comment-14018151 ]
ASF subversion and git services commented on CTAKES-292: -------------------------------------------------------- Commit 1600490 from chen...@apache.org in branch 'ctakes/trunk' [ https://svn.apache.org/r1600490 ] CTAKES-253 CTAKES-292 - Integrate YTEX with cTAKES 1) Removed <finalName> from ctakes-ytex-web. This caused the jars to be called ctakes-ytex-web.jar instead of the default ctakes-ytex-web-{version}.jar. Which will make downstream modules fail to recognize this if added as a dependency. 2) Removed the custom make-jar inside ctakes-ytext-web. Use built-in attachClasses attribute from war plugin instead. a. My guess is that you would like to jar all of the classes as well as have a war file. If true, then there is a feature already built-in for this. I noticed there are other xml properties included in the classes. Let me know if there was still a specific reason for the custom jar that I may have overlooked. <plugin> <artifactId>maven-war-plugin</artifactId> <version>2.4</version> <configuration> <attachClasses>true</attachClasses> </configuration> </plugin> By doing this, other modules can now depend on this by simply including the classes classifier. For example, in the distribution module: <dependency> <groupId>org.apache.ctakes</groupId> <artifactId>ctakes-ytex-web</artifactId> <version>${project.version}</version> <classifier>classes</classifier> </dependency> > Integrate YTEX with cTAKES > -------------------------- > > Key: CTAKES-292 > URL: https://issues.apache.org/jira/browse/CTAKES-292 > Project: cTAKES > Issue Type: Improvement > Affects Versions: 3.1.1 > Reporter: Pei Chen > Fix For: 3.2.0 > > > Placeholder for YTEX. > - Move YTEX from sandbox into trunk > - Apply and fixes to current ctakes > - Release ytex as another ctakes module -- This message was sent by Atlassian JIRA (v6.2#6252)