Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ. As of October 27th, please open all new issues in the Red Hat Customer Portal .
Though ECLIPSE-31 is a better long term fix as it means we can include the archetypes inside the distro; so it'll work for folks who are offline
Description
If we add a dependency on bundle: org.maven.ide.eclipse
then we can add this extension point to define the remote archetype catalog:
<extension
point="org.maven.ide.eclipse.archetypeCatalogs">
</extension>
Though ECLIPSE-31 is a better long term fix as it means we can include the archetypes inside the distro; so it'll work for folks who are offline
if we do this we depend on m2eclipse (which we probably need to do anyway to be able to update the pom.xml nicely when folks add a component / language / camel-test case via the New Camel Test wizard - in this case I wonder if that means we end up tackling ECLIPSE-19 too?
James Strachan added a comment - 27/Jan/11 10:18 AM if we do this we depend on m2eclipse (which we probably need to do anyway to be able to update the pom.xml nicely when folks add a component / language / camel-test case via the New Camel Test wizard - in this case I wonder if that means we end up tackling ECLIPSE-19 too?
Improvement
Resolved
Major
auto-default the remote archetype catalog so users don't have to go through that step
ECLIPSE-19too?