Community
Participate
Working Groups
Build Identifier: On successful completion, the jet.transform ant task throws ant failure and inevitably stops ant script I called jet.transform from a custom ant script within an Eclipse IDE project and got a "Successful Execution" failure Haven't called it from command line but I assume same will occur Same problem does not occur when running transformation as a "Transformation Input" (Eclipse Run configuration) Reproducible: Always Steps to Reproduce: 1.Create a JET transformation project 2.create an ant script within the new project with a target calling jet.transform task 3.Create and run an "External Tool Configuration" for the above ant target 4, Observe that on success an error message is displayed and output console displays the outcome as error
I forgot to mention: I am using Eclipse Galileo with JET 1.0.2
Same behaviour on Eclipse Helios with JET 1.1 Both from within Eclipse and externally (with antRunner application) successful execution stops the build Surprisingly, generated JET Plugin needs to be registered in Eclipse plugins folder for transformation to be discovered Additionally, projects referenced by the JET plugin have to be discovered with workbench application which is impossible outside eclipse (CIS environment) Any ideas?
False alarm It seems "JET 1.1.1 RC3" resolves this "BUILD FAILURE" issue Successfully used "Eclipse SDK 3.6.1" with "JET 1.1.1 RC3" without JET transformation interrupting external build Assuming same behaviour from within Eclipse >> Surprisingly, generated JET Plugin needs to be registered in Eclipse plugins >> folder for transformation to be discovered This was my mistake I used "eclipseTools.importProject" ant task to programmatically import the referenced project into eclipse workspace The Ant Task is available with the "CodePro AnalytiX" product, more specifically the "CodePro - Ant" plugin I recommend this technique, it has worked successfully for me >> Additionally, projects referenced by the JET plugin have to be discovered with >> workbench application which is impossible outside eclipse (CIS environment) This is also my mistake. identical cause/resolution to previous Closing...
