Fuse Tools
  1. Fuse Tools
  2. FUSETOOLS-66

auto-default the remote archetype catalog so users don't have to go through that step

    Details

    • Type: Enhancement Enhancement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.1
    • Component/s: Camel Editor
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      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

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            James Strachan added a comment -

            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?

            Show
            James Strachan added a comment - 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?

              People

              • Assignee:
                James Strachan
                Reporter:
                James Strachan
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: