[ https://issues.jboss.org/browse/JBIDE-15647?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15647: --------------------------------------- {code} which internal API would you remove that others in JBT uses ? {code} No one component uses arquillian. I have meant we can't use the same JBT code for Luna and Kepler because the most of our components (arquillian, central, project examples, maven, portlet, hibernate, archives, server, common, foundation, openshift... ) use internal Eclipse API. {quote} dont you mean stop using interal api or ? {quote} I mean we should stop using internal API whenever it is possible to do that. {quote} btw. this change sounds to me Eclipse are making public API internal between Kepler and Luna ? {quote} No, they aren't making public API internal. The org.eclipse.osgi.framework.adaptor.BundleClassLoader class has been internal API and is renamed in Luna. However, it seems the RuntimeProcess class (JBIDE-15649 - forge) has been changed although it is a public API. Forge doesn't use internal API. {quote} That should be trivial to do dynamic test instead of hardcoded version ? {quote} I have removed the BundleClassLoader class because the Arquillian classloader isn't used within an Eclipse bundle. Now, the arquillian component builds against the Kepler and/or Luna target. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira