Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-8110

Fuse EAP archetype generated pom.xml contains invalid configuration

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • fuse-7.0
    • fuse-7.0
    • Fuse EAP
    • None
    • % %
    • Fuse 7.0 Sprint 28

    Description

      mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate \
                             -DarchetypeGroupId=org.wildfly.camel.archetypes \
                             -DarchetypeArtifactId=wildfly-camel-archetype-spring \
                             -DarchetypeVersion=5.1.0.fuse-000062-redhat-1 \
                             -DgroupId=com.mycompany \
                             -DartifactId=my-camel-spring-application \
                             -Dversion=1.0-SNAPSHOT \ 
                             -DarchetypeCatalog=http://indy.cloud.pnc.engineering.redhat.com/api/group/builds-untested+shared-imports+public/
      

      The generated project pom.xml has the following issues:

      • Internal brew maven repository configuration is present
      • Incorrect definition of Fuse EA maven repository. origin-repository is used.
      • MRRC repositories are not configured
      • Incorrect property value for server.config. standalone-camel.xml does not exist on Fuse EAP, it should be standalone.xml
      • Generated archetype project README references community project naming / URLs

      Not sure if anyone has been testing these archetypes or whether anyone is using them. They were initially created for the Eclipse tooling, but I think they use some other method to generate Fuse EAP projects now.

      Attachments

        Activity

          People

            jnethert@redhat.com James Netherton
            jnethert@redhat.com James Netherton
            Emil Cervenan Emil Cervenan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: