Am 15.11.20 um 22:48 schrieb Philippe Mouawad:
> Hello Felix,
> You are right, I didn't dig too much and I think I sent a mail too early.
>
> What version of Eclipse are you using ? And which Groovy plugin did you
> install ?
I have a long lived eclipse installation, that survived (more or less)
Am 15. November 2020 22:47:43 MEZ schrieb Vladimir Sitnikov
:
>Philippe>It is broken for me as it generates broken .classpath files.
>
>Have you tried File → Import... -> Existing Gradle project ?
>I'm not sure if "gradlew eclipse" works, however, I know "gradlew idea"
>has
>been deprecated lon
Hello,
Deleting and importing again projects helped a bit, thanks Vladimir.
I guess the issue you mention leads to error in dependant project:
"ResourceKeyUsageTest cannot be resolved to a type"
I think I am using a too old version of Eclipse for the project state now.
I'll upgrade and give feedba
Philippe>It is broken for me as it generates broken .classpath files.
Have you tried File → Import... -> Existing Gradle project ?
I'm not sure if "gradlew eclipse" works, however, I know "gradlew idea" has
been deprecated long ago (by both Gradle and IDEA).
Felix>I have another problem with the
Hello Felix,
You are right, I didn't dig too much and I think I sent a mail too early.
What version of Eclipse are you using ? And which Groovy plugin did you
install ?
Thanks
On Sun, Nov 15, 2020 at 10:15 PM Felix Schumacher <
felix.schumac...@internetallee.de> wrote:
>
> Am 14.11.20 um 19:47
Am 14.11.20 um 19:47 schrieb Philippe Mouawad:
> Hello folks,
> I pulled latest version of JMeter and ran
> ./gradlew eclipse
>
> It is broken for me as it generates broken .classpath files.
> The path to dependencies contains an additional UUID :
>
> For example:
> sourcepath="/Users/Ph
Hello folks,
I pulled latest version of JMeter and ran
./gradlew eclipse
It is broken for me as it generates broken .classpath files.
The path to dependencies contains an additional UUID :
For example:
Do you have the s
