I'm ASTools component lead, but I didn't set up the dependencies /
plugins initially... I just continued whatever practice was in place
without thinking much on it. I don't know of any issues that require
inclusion in this component, and as far as I know it's always been this
way.
It seems dependency should be fine, but I'll need to test post-build to
ensure nothing is broken. Honestly I'm not even sure how to test aside
from a normal smoke test, since I'm uncertain of what kind of use cases
might break from this change. I'm not very familiar on the exact osgi /
eclipse rules governing this.
Are there any pro-tips on what use cases might be broken by this?
On 03/20/2012 07:19 PM, Mickael Istria wrote:
On 03/20/2012 11:33 AM, Max Rydahl Andersen wrote:
> either open a jira for these modules with a patch or send the fisheye
> changeset here when done so its easy to look at.
Issue created. If you are concerned, please watch it:
https://issues.jboss.org/browse/JBIDE-11358
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
My blog <
http://mickaelistria.wordpress.com> - My Tweets
<
http://twitter.com/mickaelistria>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev