Comments (7)
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)?
from tycho.
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
from tycho.
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.
from tycho.
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?
from tycho.
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.
from tycho.
Is this one fixed now? If not what is still pending here?
from tycho.
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.
from tycho.
Related Issues (20)
- set-version fails to update MANIFEST.MF if CI-firendly versions are in use
- Improve output for missing requirements on dependencies
- Building fails because of `Inconsistent reactor project` HOT 2
- Broken links in the Eclipse/Github wiki HOT 1
- Unconsidered linked .classpath files and test source folders HOT 1
- [tycho-version-plugin] Since 4.0.5 non-matching version of child modules are forcefully overwritten HOT 3
- forceContextQualifier has been broken since Tycho 4.0.5 HOT 1
- sort order of root nodes in dependency-tree is unstable HOT 1
- Linked .classpath files: linked classpath entries paths not resolve against project base directory
- Parsing custom variables in linked project resources HOT 2
- [DS] Validation of transitive generated 'osgi.extender=osgi.component' requirement fails HOT 11
- support reuseFork option in tycho-surefire-plugin
- Unable to build eclipse application repository or site with patch features HOT 3
- The application packaged by Tycho can't start on MacOS 14.4 HOT 1
- Missing p2 dependencies in maven dependency:tree output HOT 1
- Goal `publish-features-and-bundles` inherits metadata available in reactor HOT 3
- Not possible to remove qualifier for release build from bundles/features and product when using CI friendly versions HOT 1
- Strange error with Tycho 4.0.8 HOT 4
- [sbom] BOM is calculated multiple times for the same unit HOT 3
- DumpStackTracesTimer fails to log during platform shutdown
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from tycho.