org.eclipse.xtext.xbase.tests.URIsInEcoreFilesTest fails in Eclipse about xtext-extras HOT 14 CLOSED

sry i have no idea on that. this has to be investigated. unfortunately the classpath regarding model/ is different in gradle and eclipse. maybe a issue with buildship.

in buildship model/* is added to the jar and this makes it part of the classpath.
i guess someone who knows gradle should have a look

from xtext-extras.

Exactly the same problem here: org.eclipse.xtext.xtext.URIsInEcoreFilesTest

from xtext-extras.

@oehme do you have an idea how that could be solved?

from xtext-extras.

I don't know gradle, but if it behaves like tycho-surefire-plugin then it executes the tests in an OSGI environment (without the UI) and this would make platform URIs work

from xtext-extras.

no, these uris actually work. the problem is that the classpath uri does not work cause model/* is not on classpath in eclipse. same for org/..../Xtext.ecore/genmodel.

these files are jared like

jar {
    from('.') {
        include 'org/**', 'modeling32.png'
    }
}

or

jar {
    from ('.') {
        include 'about*.*', 'plugin.xml', 'schema/**', 'model/**'
    }
    metaInf {
        from 'META-INF'
    }
}

from xtext-extras.

but these tests used to work before the repo splitting, didn't they? I guess because at that time they were Eclipse plug-in projects (PDE nature). Could that be?

Or probably setting 'model' as a source folder would do the trick, because then their contents would be copied to the bin folder?

from xtext-extras.

I did not look at the old state. I don't know why this is done this way / why the files are not in a src folder

from xtext-extras.

For setting model as source folder the places that look for model/xxxx.ecore/genmodel would have to be changed

from xtext-extras.

This is indeed caused by switching off the plugin nature. The model folder was added to the output of the project through a declaration in build.properties.

You cannot make model a source folder because of how platform resource URIs work: They require the resource to have the same relative path inside the workspace project and the final jar file.

The only solution I can think of is to add the project root folder as a source folder with a single include for model. For now you'd have to check in that customization in your .classpath file. With Gradle 3.0/Buildship 1.0.18 (both out soon), you'll be able to automate this customization.

from xtext-extras.

and what about simply adding the plugin nature back? It will be used only when opening the project in Eclipse and it should not disturb anything else, I guess.

from xtext-extras.

I see no problem with that. I was only offering the alternative if for some reason you really don't want the plugin nature :)

from xtext-extras.

Oh another obvious solution I missed: Use classpath URIs and put the model in src/main/resources.

from xtext-extras.

ill try to fix this using a custom urlclassloader

from xtext-extras.

Fixed in 2.13

from xtext-extras.