Tycho should respect "only visible for test sources" about tycho

[mickaelistria]

I'm surprised you only notice it now. I thought your whole plans were build around this feature and the fact that .classpath was actually containing info to do "test" scope dependency resolution.
How do you want to see it supported specifically? I'm not sure anything is needed beyond everything we already discussed (eg building a kind of "test" scope and dependency resolution result that takes into account the .classpath content to be used by compilation and surefire execution)?

[laeubi]

I only was aware about test source-folder and newer saw this before and just found that eclipse already supports this while trying to prepare an enhancement request for JDT ;-)

How do you want to see it supported specifically? I'm not sure anything is needed beyond everything we already discussed (eg building a kind of "test" scope and dependency resolution result that takes into account the .classpath content to be used by compilation and surefire execution)?

If it can be done easily later on I won't complain 👍 at least currently only source-folder are checked for the test attributes and the same needs to happen for classpath-container accordingly

So what I would expect would be the following:

• I have a project with a plain source folder and a test folder
• I have a plain classpathcontainer and this is available to the compile and test-compile mojo
• I have a "test" classpathcontainer that is only available to the test-compile mojo but not to the compile-mojo

[laeubi]

A source of confusion might be that "source-folders" are also stored in the .classpath-file.... (they are called classpathentries there).

So yes my plans are build around that feature but I have not noticed until now that "con" can have generic test attribute as well as "src" types.

[mickaelistria]

I have a "test" classpathcontainer that is only available to the test-compile mojo but not to the compile-mojo

More specifically, do I get right that what you want at the moment is to have the JUnit container ( #49 ) annotated as tests in .classpath, and thus the Tycho JUnit requirements added to the compiler classpath and tycho-surefire-plugin target?

[laeubi]

Actually this needs to be added to the "test-compile" classpath, only just like in maven where I have a scope of "test" versus "compile". tycho-surefire-plugin would mostly using test+compile scopes.

At the moment JUNIT containers are added as "default" classpathcontainers but I created https://bugs.eclipse.org/bugs/show_bug.cgi?id=572820 to make it more visible that these are also possible as "test" container.

I also think this is more to prevent users from accidentally using test-dependecies in regular code for the compile part so the compiler complains about missing references.

So another task would probably for to change in "computeclasspath" to distinguish between both class spaces.

[akurtakov]

Is this one fixed now? If not what is still pending here?

[laeubi]

This is not fixed yet, actually there is only limited support for test dependencies but sources are still compiled regardless of the classpath scope if I remember correctly.