Is there not a way to conditionally enable the source packaging instead of these "fixes" ? Denis Golovin <https://source.jboss.org/user/dgolovin> committed 35852 <https://source.jboss.org/changelog/JBossTools?cs=35852> on branch trunk <https://source.jboss.org/changelog/~br=trunk/JBossTools> in JBossTools <https://source.jboss.org/browse/JBossTools> added src folder to fix source gathering related errors · /trunk/forge/plugins/org.jboss.tools.forge.runtime/.classpath (-0, +1) | History <https://source.jboss.org/browse/JBossTools/trunk/forge/plugins/org.jboss.... | Source <https://source.jboss.org/browse/JBossTools/trunk/forge/plugins/org.jboss.... | Diff <https://source.jboss.org/browse/JBossTools/trunk/forge/plugins/org.jboss.... · /trunk/forge/plugins/org.jboss.tools.forge.runtime/src (-0, +0) | History <https://source.jboss.org/browse/JBossTools/trunk/forge/plugins/org.jboss.... | Source <https://source.jboss.org/browse/JBossTools/trunk/forge/plugins/org.jboss.... https://source.jboss.org/changelog/JBossTools?cs=35852 Sent with MobileRSS HD <http://itunes.apple.com/app/mobilerss-hd-google-rss-news/id375300540?mt=8... Sent from a mobile device _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

> Digging further I noticed another potential problem. bin folder has two files that never gets into bundle. Do we need them? These files are the scripts to launch Forge from the command line. They are not strictly needed but it's probably a good idea to add them as ultimately JBDS will be the mechanism to distribute Forge.

I'm not sure but I believe Tycho may filter the output directory. And, given the way Eclipse build.properties work, you probably need to add bin/forge and bin/forge.bat to the list of includes, which means they will be in the bin dir in the resulting archive.

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...).

Best, Rob Digging further I noticed another potential problem. bin folder has two files that never gets into bundle. Do we need them? <screenshot132.png> 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 <Mail Attachment.png> which means only build.properties should be changed like shown below <Mail Attachment.png> 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: Is there not a way to conditionally enable the source packaging instead of these "fixes" ? Denis Golovin committed 35852 on branch trunk in JBossTools added src folder to fix source gathering related errors · /trunk/forge/plugins/org.jboss.tools.forge.runtime/.classpath (-0, +1) | History | Source | Diff · /trunk/forge/plugins/org.jboss.tools.forge.runtime/src (-0, +0) | History | Source https://source.jboss.org/changelog/JBossTools?cs=35852 Sent with MobileRSS HD Sent from a mobile device _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

>>> Digging further I noticed another potential problem. bin folder has two files that never gets into bundle. Do we need them? >> >> These files are the scripts to launch Forge from the command line. They are not strictly needed but it's probably a good idea to add them as ultimately JBDS will be the mechanism to distribute Forge. > > > eh - the forge we distribute aren't intended for local runs is it ? Strictly speaking this is not the intention but I don't see why we should restrict this.