Groovy compilation errors after switching from pro 2.0.2 to pro 2.5
Hi Ole,
I am happy to be able to use Groovy. We couldn't do what we do at the moment without it.
But, after downloading and using pro version 2.5 (at the moment nightly build 24-11) soapUI gives compiliation errors. It is unable to resolve classes where the Pro version 2.0.2 had no problems.
The classes are not located at the default location. I keep the classes in a project in Eclipse right next to the project that implements the other side of the SOAP interface. Using Eclipse I keep versions of the classes in CVS. So the final location the classes are stored is something like:
C:\eclipse3.2.1\workspace\\src\\
This set up gives me three advantages and worked well in 2.0.2: 1. CVS access. 2. Syntax sensitive editor. 3. All code kept together (tagging).
I do not want to acces the soapUI functionality from Eclipse. I like the soapUI GUI as it is.
Is there a new setting for Groovy to set with 2.5, am I missing something else or did I just find a bug?
Marc.
I am happy to be able to use Groovy. We couldn't do what we do at the moment without it.
But, after downloading and using pro version 2.5 (at the moment nightly build 24-11) soapUI gives compiliation errors. It is unable to resolve classes where the Pro version 2.0.2 had no problems.
The classes are not located at the default location. I keep the classes in a project in Eclipse right next to the project that implements the other side of the SOAP interface. Using Eclipse I keep versions of the classes in CVS. So the final location the classes are stored is something like:
C:\eclipse3.2.1\workspace\
This set up gives me three advantages and worked well in 2.0.2: 1. CVS access. 2. Syntax sensitive editor. 3. All code kept together (tagging).
I do not want to acces the soapUI functionality from Eclipse. I like the soapUI GUI as it is.
Is there a new setting for Groovy to set with 2.5, am I missing something else or did I just find a bug?
Marc.
