Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apt.tests don't need org.eclipse.pde.core #1918

Closed
wants to merge 0 commits into from

Conversation

akurtakov
Copy link
Contributor

What it does

Remove unneded dependency of o.e.jdat.apt.tests. Uncovered while working on eclipse-pde/eclipse.pde#1060

How to test

Verification builds completes without failing tests in the bundle.

Author checklist

@akurtakov
Copy link
Contributor Author

@stephan-herrmann Is "%ECLIPSE_HOME% resolving (

) crucial for the test?
I ask as it's provided by pde.core (https://github.com/eclipse-pde/eclipse.pde/blob/69eb1b7bcf20d6316a6d164c28de7fdbe083877e/ui/org.eclipse.pde.core/plugin.xml#L28) and thus it creates one more build cycle between jdt and pde repositories. In theory smth similar is achievable by using core.variables plugin but considering this is only for testing purposes and ECLIPSE_HOME will continue to be evaluated just fine if pde.core is installed maybe some other test improvement (another classpath variable replacement?) would serve the same purpose.

@stephan-herrmann
Copy link
Contributor

@stephan-herrmann Is "%ECLIPSE_HOME% resolving (


) crucial for the test?

Wow, that's asking about events from 2005, which was slightly before my participation :)

See

It looks like the test just uses %ECLIPSE_HOME% as an example for a variable with is "known" to exist. With that it seems possible, but not trivial to replace this var with another one (defined by the test itself?).

@akurtakov akurtakov closed this Feb 2, 2024
akurtakov added a commit to akurtakov/eclipse.jdt.core that referenced this pull request Feb 9, 2024
Introduce new classpath variable in the test project to not rely on the
pde.core one.
Result of discussion in
eclipse-jdt#1918
akurtakov added a commit to akurtakov/eclipse.jdt.core that referenced this pull request Feb 9, 2024
Introduce new classpath variable in the test project to not rely on the
pde.core one.
Result of discussion in
eclipse-jdt#1918
akurtakov added a commit to akurtakov/eclipse.jdt.core that referenced this pull request Feb 9, 2024
Introduce new classpath variable in the test project to not rely on the
pde.core one.
Result of discussion in
eclipse-jdt#1918
akurtakov added a commit to akurtakov/eclipse.jdt.core that referenced this pull request Feb 9, 2024
Introduce new classpath variable in the test project to not rely on the
pde.core one.
Result of discussion in
eclipse-jdt#1918
akurtakov added a commit that referenced this pull request Feb 9, 2024
Introduce new classpath variable in the test project to not rely on the
pde.core one.
Result of discussion in
#1918
mickaelistria pushed a commit to mickaelistria/eclipse.jdt.core that referenced this pull request Feb 16, 2024
Introduce new classpath variable in the test project to not rely on the
pde.core one.
Result of discussion in
eclipse-jdt#1918
robstryker pushed a commit to robstryker/eclipse.jdt.core that referenced this pull request Jul 18, 2024
Introduce new classpath variable in the test project to not rely on the
pde.core one.
Result of discussion in
eclipse-jdt#1918
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants