You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the Tycho connector doesn't support compile-time extra classpath elements.
I'm working with iPOJO annotations in my projects, which are defined in a simple JAR file, not in a bundle, as they are stored in the .class files and are not visible at runtime.
I declared these annotations in a parent pom file, using the extraClasspathElements configuration property of the tycho-compiler-plugin.
This property allows to use a Maven dependency in the compilation class path, and avoids to use the "jar.extra.classpath" property in the build.properties files and to have to store the JAR file somewhere during the compilation.
I have no public sample of this problem yet, I'll prepare a dummy sample workspace later this week, if necessary.
I was under impression that I marked config parameter as unsupported and discouraged in Tycho... not sure what happened there. In any case, I don't need this feature myself and have no immediate plans to implement it. If somebody provides a quality patch I will review and give feedback.
Let me know if you plan to work in the patch because in that case I will need to figure out if we require signed CLA or any other formalities before we accept contributions here.
Hi,
It seems that the Tycho connector doesn't support compile-time extra classpath elements.
I'm working with iPOJO annotations in my projects, which are defined in a simple JAR file, not in a bundle, as they are stored in the .class files and are not visible at runtime.
I declared these annotations in a parent pom file, using the extraClasspathElements configuration property of the tycho-compiler-plugin.
This property allows to use a Maven dependency in the compilation class path, and avoids to use the "jar.extra.classpath" property in the build.properties files and to have to store the JAR file somewhere during the compilation.
I have no public sample of this problem yet, I'll prepare a dummy sample workspace later this week, if necessary.
Here is a the plugin configuration :
Cheers,
Thomas
The text was updated successfully, but these errors were encountered: