Cargo
  1. Cargo
  2. CARGO-953

Need to remove reference to the JBoss Maven repo in the jboss remote deployer projects

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.0.6, 1.1.0
    • Fix Version/s: None
    • Component/s: Build, JBoss
    • Labels:
      None
    • Environment:
      n/a
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      The projects with the JBoss Remote Deployer support classes (cargo-core-tools-jboss-deployer-5 and cargo-core-tools-jboss-deployer-5.1-and-onwards) have a declaration to the JBoss Maven repo. This is not allowed by the rules of Maven central, as Maven central needs to be self-contained. We need to solve this somehow!

        Issue Links

          Activity

          Hide
          Savas Ali Tokmen added a comment -

          https://issues.jboss.org/browse/JBBUILD-597 is now closed. The rsync is now active for certain groupIds. Some additional information is on the jboss build blog: http://community.jboss.org/en/build/blog/2011/05/24/rsync-jbossorg-to-maven-central

          Here is a list of the groupIds currently being synced on a nightly basis:

          javassist
          jgroups
          org.jgroups
          org.jboss.netty
          org.hibernate
          org.hornetq
          org.resteasy

          ... which does not include the artifact CARGO needs ... yet

          Show
          Savas Ali Tokmen added a comment - https://issues.jboss.org/browse/JBBUILD-597 is now closed. The rsync is now active for certain groupIds. Some additional information is on the jboss build blog: http://community.jboss.org/en/build/blog/2011/05/24/rsync-jbossorg-to-maven-central Here is a list of the groupIds currently being synced on a nightly basis: javassist jgroups org.jgroups org.jboss.netty org.hibernate org.hornetq org.resteasy ... which does not include the artifact CARGO needs ... yet
          Hide
          Savas Ali Tokmen added a comment -

          Progress to be tracked on http://community.jboss.org/wiki/MavenRepositoryCentralSynchronization

          They have more and more groupIds, but not org.jboss.integration ... yet!

          Show
          Savas Ali Tokmen added a comment - Progress to be tracked on http://community.jboss.org/wiki/MavenRepositoryCentralSynchronization They have more and more groupIds, but not org.jboss.integration ... yet!
          Hide
          Savas Ali Tokmen added a comment -

          The "currently under review for sync" now includes org.jboss.integration ... let's stay tuned!

          Show
          Savas Ali Tokmen added a comment - The "currently under review for sync" now includes org.jboss.integration ... let's stay tuned!
          Hide
          Savas Ali Tokmen added a comment -

          Committed revision 3137 and updated http://cargo.codehaus.org/JBoss+Remote+Deployer since the JBoss 7 dependencies are now in the Maven central.

          Now waiting for the older ones

          Show
          Savas Ali Tokmen added a comment - Committed revision 3137 and updated http://cargo.codehaus.org/JBoss+Remote+Deployer since the JBoss 7 dependencies are now in the Maven central. Now waiting for the older ones
          Hide
          Savas Ali Tokmen added a comment -

          JBoss did its best, so now all org.jboss artifacts are on Maven central.

          Unfortunately, these have some transitive dependencies, for example apache-xerces:xml-apis, which are only available on the JBoss third party repository (and cannot be put anywhere else since they exist with a different official name in central; for example Xerces is under org.apache).

          We therefore need to have:

          <!--
            Some transitive dependencies of JBoss artifacts, for example apache-xerces:xml-apis, are
            only available on the JBoss third party repository.
            -->
          <pluginRepositories>
            <pluginRepository>
              <id>repository.jboss.org_thirdparty-releases</id>
              <name>JBoss.org third party releases repository</name>
              <url></url>
              <releases>
                <enabled>true</enabled>
              </releases>
              <snapshots>
                <enabled>false</enabled>
              </snapshots>
            </pluginRepository>
            <pluginRepository>
              <id>repository.jboss.org_thirdparty-uploads</id>
              <name>JBoss.org third party uploads repository</name>
              <url></url>
              <releases>
                <enabled>true</enabled>
              </releases>
              <snapshots>
                <enabled>false</enabled>
              </snapshots>
            </pluginRepository>
          </pluginRepositories>
           
          <repositories>
            <repository>
              <id>repository.jboss.org_thirdparty-releases</id>
              <name>JBoss.org third party releases repository</name>
              <url></url>
              <releases>
                <enabled>true</enabled>
              </releases>
              <snapshots>
                <enabled>false</enabled>
              </snapshots>
            </repository>
            <repository>
              <id>repository.jboss.org_thirdparty-uploads</id>
              <name>JBoss.org third party uploads repository</name>
              <url></url>
              <releases>
                <enabled>true</enabled>
              </releases>
              <snapshots>
                <enabled>false</enabled>
              </snapshots>
            </repository>
          </repositories>
          
          Show
          Savas Ali Tokmen added a comment - JBoss did its best, so now all org.jboss artifacts are on Maven central. Unfortunately, these have some transitive dependencies, for example apache-xerces:xml-apis, which are only available on the JBoss third party repository (and cannot be put anywhere else since they exist with a different official name in central; for example Xerces is under org.apache). We therefore need to have: <!-- Some transitive dependencies of JBoss artifacts, for example apache-xerces:xml-apis, are only available on the JBoss third party repository. --> <pluginRepositories> <pluginRepository> <id>repository.jboss.org_thirdparty-releases</id> <name>JBoss.org third party releases repository</name> <url></url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </pluginRepository> <pluginRepository> <id>repository.jboss.org_thirdparty-uploads</id> <name>JBoss.org third party uploads repository</name> <url></url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </pluginRepository> </pluginRepositories> <repositories> <repository> <id>repository.jboss.org_thirdparty-releases</id> <name>JBoss.org third party releases repository</name> <url></url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> <repository> <id>repository.jboss.org_thirdparty-uploads</id> <name>JBoss.org third party uploads repository</name> <url></url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> </repositories>

            People

            • Assignee:
              Unassigned
              Reporter:
              Anders Hammar
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: