Replies: 1 comment 1 reply
-
As it seems there are no concern I plan to disable the test and apply the filtering of non existing items next week. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently ECJ complains about folders/jars that do not exits at the time the compiler is invoked.
The obvious fix for Tycho seems to exclude non existing locations in
tycho/tycho-compiler-plugin/src/main/java/org/eclipse/tycho/compiler/AbstractOsgiCompilerMojo.java
Lines 489 to 494 in 02e406b
But there is actually an explicit test that tycho return non existing locations here:
tycho/tycho-compiler-plugin/src/test/java/org/eclipse/tycho/osgicompiler/test/OsgiCompilerTest.java
Lines 143 to 152 in 02e406b
AbstractOsgiCompilerMojo#getClasspathElements() is effectively called right at the execute phase so I really don't see any chance that a non existing item is created/copied anywhere and assume the test is either wrong or incomplete.
@mickaelistria @akurtakov do you have any insights if/how non existing items can be important at this phase? If not I'd like to adjust the test and skip non existing items to prevent unnecessary error printouts.
FYI @iloveeclipse
Beta Was this translation helpful? Give feedback.
All reactions