jcasgen-maven-plugin logs out to standard out in builds.

[GoogleCodeExporter]

The jcasgen-maven-plugin (because jcasgen does this) outputs lots of 
information to the console during execution. This can cause CI system such as 
Bamboo to see this information and possibly incorrectly include it in the error 
log.

Could we have one a way of making it use the Log4j Logger through the system 
property:
-Dorg.apache.uima.logger.class=org.apache.uima.util.impl.Log4jLogger_impl

Or have an maven property such as <useLog4J>true</useLog4J>

Additionally it would be nice to have the ability to define the path of the 
Log4J file to be used for configuration.

An alternative to all this is for jcasgen-maven-plugin to prevent the jcasgen 
tool from outputting to standard out.

Original issue reported on code.google.com by DDCru...@gmail.com on 3 Dec 2012 at 6:57

[GoogleCodeExporter]

Are you using the newest version, 0.9.3? I thought 
r24f52dcdbd2ae39876e64f423649055c928c97d2 fixed that issue.

If you are using 0.9.3, and you're still seeing JCasGen printing to standard 
out, could you copy-paste an example of this? With cTAKES, for example, I see 
JCasGen messages being routed correctly to Maven [INFO] like:

[INFO] --- jcasgen-maven-plugin:0.9.3:generate (default) @ ctakes-assertion ---
[INFO] JCasGen: Output going to 
'/.../ctakes/ctakes-assertion/target/generated-sources/jcasgen'
[INFO] JCasGen: Reading the XML TAE descriptor, and creating types, for xml 
input file 
'/.../ctakes/ctakes-assertion/src/main/resources/org/apache/ctakes/assertion/typ
es/TypeSystem.xml'.
[INFO] JCasGen: Replacing: 
'org.apache.ctakes.assertion.medfacts.types.Assertion'.
[INFO] JCasGen: Replacing: 
'org.apache.ctakes.assertion.medfacts.types.Assertion_Type'.
[INFO] JCasGen: Replacing: 'org.apache.ctakes.assertion.medfacts.types.Concept'.
[INFO] JCasGen: Replacing: 
'org.apache.ctakes.assertion.medfacts.types.Concept_Type'.

Original comment by steven.b...@gmail.com on 3 Dec 2012 at 8:52

• Added labels: Component-jcasgen-maven-plugin

[GoogleCodeExporter]

I am currently using 0.9.0 because it is the latest version on maven central.

Yeah ignore my comments about exposing the ability to change the logger. Using 
the Maven Logger is a much better solution. But yes that is exactly what I want.

Is there a maven repository that has the newest version or would you be able to 
organize a push of the new version to maven central? What is the turn around 
time on something like this?

Original comment by DDCru...@gmail.com on 4 Dec 2012 at 12:41

[GoogleCodeExporter]

0.9.3 is already in Maven Central (as are all the other versions):

http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.cleartk%22%20AND%20a%3A%2
2jcasgen-maven-plugin%22

Original comment by steven.b...@gmail.com on 4 Dec 2012 at 6:09

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Used the new version and I have confirmed it is using the Maven Log and it is 
not showing up in Bamboo Error Summary. Thank you.

I normally use a search and end up using mvnrepository.com to look up maven 
central versions. But I guess they are behind in their index. 
http://mvnrepository.com/artifact/org.cleartk/jcasgen-maven-plugin

This issue is resolved. Thank You.

Original comment by DDCru...@gmail.com on 4 Dec 2012 at 3:06

[GoogleCodeExporter]

Original comment by steven.b...@gmail.com on 5 Dec 2012 at 9:23

• Changed state: Fixed
• Added labels: Milestone-1.3