| Summary: | JET: jet.transform throws ant failure on success | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Elias Balasis <eliasbalasis> |
| Component: | Jet | Assignee: | Project Inbox <m2t.jet-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | pelder.eclipse |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Elias Balasis
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... |