Theoretically, you should not need to include .classpath or .project or .settings as m2eclipse w/tycho should take care of configuring the project correctly. If you want to get fancy, you could also configure a dependency:copy execution to pull in the relevant jars (e.g. jboss-modules.jar) and place them in the correct locations. This would save having jars checked into svn (drawback is that you have to run process-(re)sources, to copy down the jars, before the project will configure correctly). It would also allow you to more easily update the jars used (at the cost of potentially pulling down an unstable snapshot, if that's what you're using). If you'd like an example, you can look at the org.switchyard.tools.core plugin in the switchyard tools git repo (https://github.com/jboss-switchyard/tools/tree/master/eclipse/plugins/org.switchyard.tools.core).
Best,
Rob
Digging further I noticed another potential problem. bin folder has two files that never gets into bundle. Do we need them?
On 10/20/2011 04:53 PM, Denis Golovin wrote:It looks like it is fine do not have src folder in tycho 0.13.0. No failures, but no .source.jars as well.
The right fix is
add '.' into libraries list like this
which means only build.properties should be changed like shown below
This fix forks for both tycho versions 0.12.0 and 0.13.0
Denis
On 10/20/2011 01:40 PM, Max Andersen wrote:
Sent from a mobile device
_______________________________________________ jbosstools-dev mailing list jbosstools-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________ jbosstools-dev mailing list jbosstools-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev