Bug 831607 - Torquebox sources cannot be built out of the box
Summary: Torquebox sources cannot be built out of the box
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: TorqueBox
Version: 2.0.0.ER7
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ER1
: 2.1.0
Assignee: Ben Browning
QA Contact: Karel Piwko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-13 12:31 UTC by Karel Piwko
Modified: 2012-11-30 15:34 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
A number of artifacts required to build TorqueBox from source are not present in the Maven Central and Enterprise Maven repositories. The TorqueBox documentation has been updated to clarify that the JBoss Nexus repository must be enabled, as it contains the required artifacts. Refer to the TorqueBox User Guide for further information on building TorqueBox from source and the Red Hat Maven Guide for details about configuring repositories.
Clone Of:
Environment:
Last Closed: 2012-11-30 15:34:49 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Karel Piwko 2012-06-13 12:31:55 UTC 
TorqueBox compilation requires artifacts which are not present in Maven Central nor distributed Maven repositories, you have to enable JBoss Nexus repository according to instructions at https://community.jboss.org/wiki/MavenGettingStarted-Users


<profile>
      <id>jboss-public-repository</id>
      <repositories>
        <repository>
          <id>jboss-public-repository-group</id>
          <name>JBoss Public Maven Repository Group</name>
          <url>https://repository.jboss.org/nexus/content/groups/public-jboss/</url>
          <layout>default</layout>
          <releases>
            <enabled>true</enabled>
            <updatePolicy>never</updatePolicy>
          </releases>
          <snapshots>
            <enabled>true</enabled>
            <updatePolicy>never</updatePolicy>
          </snapshots>
        </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <id>jboss-public-repository-group</id>
          <name>JBoss Public Maven Repository Group</name>
          <url>https://repository.jboss.org/nexus/content/groups/public-jboss/</url>
          <layout>default</layout>
          <releases>
            <enabled>true</enabled>
            <updatePolicy>never</updatePolicy>
          </releases>
          <snapshots>
            <enabled>true</enabled>
            <updatePolicy>never</updatePolicy>
          </snapshots>
        </pluginRepository>
      </pluginRepositories>
    </profile>


  <activeProfiles>
    <activeProfile>jboss-public-repository</activeProfile>
  </activeProfiles>
Comment 1 Karel Piwko 2012-06-13 12:33:11 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Compilation of TorqueBox requires artifacts which are not present in Maven Central nor distributed Maven repositories. You have to enable JBoss Nexus repository according to instructions at https://community.jboss.org/wiki/MavenGettingStarted-Users, namely include following snippet into settings.xml file:

<profile>
      <id>jboss-public-repository</id>
      <repositories>
        <repository>
          <id>jboss-public-repository-group</id>
          <name>JBoss Public Maven Repository Group</name>
          <url>https://repository.jboss.org/nexus/content/groups/public-jboss/</url>
          <layout>default</layout>
          <releases>
            <enabled>true</enabled>
            <updatePolicy>never</updatePolicy>
          </releases>
          <snapshots>
            <enabled>true</enabled>
            <updatePolicy>never</updatePolicy>
          </snapshots>
        </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <id>jboss-public-repository-group</id>
          <name>JBoss Public Maven Repository Group</name>
          <url>https://repository.jboss.org/nexus/content/groups/public-jboss/</url>
          <layout>default</layout>
          <releases>
            <enabled>true</enabled>
            <updatePolicy>never</updatePolicy>
          </releases>
          <snapshots>
            <enabled>true</enabled>
            <updatePolicy>never</updatePolicy>
          </snapshots>
        </pluginRepository>
      </pluginRepositories>
    </profile>


  <activeProfiles>
    <activeProfile>jboss-public-repository</activeProfile>
  </activeProfiles>
Comment 2 Rebecca Newton 2012-06-18 04:51:03 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,42 +1,5 @@
-Compilation of TorqueBox requires artifacts which are not present in Maven Central nor distributed Maven repositories. You have to enable JBoss Nexus repository according to instructions at https://community.jboss.org/wiki/MavenGettingStarted-Users, namely include following snippet into settings.xml file:
+TorqueBox sources cannot be built out of the box due to a compilation of required TorqueBox artifacts which are not present in Maven Central or distributed in the Enterprise Maven repository. To workaround this issue, enable the JBoss Nexus repository by including the following snippet in the settings.xml file:
 
-<profile>
-      <id>jboss-public-repository</id>
-      <repositories>
-        <repository>
-          <id>jboss-public-repository-group</id>
-          <name>JBoss Public Maven Repository Group</name>
-          <url>https://repository.jboss.org/nexus/content/groups/public-jboss/</url>
-          <layout>default</layout>
-          <releases>
-            <enabled>true</enabled>
-            <updatePolicy>never</updatePolicy>
-          </releases>
-          <snapshots>
-            <enabled>true</enabled>
-            <updatePolicy>never</updatePolicy>
-          </snapshots>
-        </repository>
-      </repositories>
-      <pluginRepositories>
-        <pluginRepository>
-          <id>jboss-public-repository-group</id>
-          <name>JBoss Public Maven Repository Group</name>
-          <url>https://repository.jboss.org/nexus/content/groups/public-jboss/</url>
-          <layout>default</layout>
-          <releases>
-            <enabled>true</enabled>
-            <updatePolicy>never</updatePolicy>
-          </releases>
-          <snapshots>
-            <enabled>true</enabled>
-            <updatePolicy>never</updatePolicy>
-          </snapshots>
-        </pluginRepository>
-      </pluginRepositories>
-    </profile>
+<snipped for brevity>
 
-
+More information on setting the public repository is available here: https://community.jboss.org/wiki/MavenGettingStarted-Users-  <activeProfiles>
-    <activeProfile>jboss-public-repository</activeProfile>
-  </activeProfiles>
Comment 4 Karel Piwko 2012-09-24 13:15:18 UTC 
This is related to Torquebox Maven repository configuration bug 849695. There should be a single place where Maven configuration is shown in documenation.
Comment 5 Marek Novotny 2012-09-25 08:48:31 UTC 
Just to be precise, what artifacts are missing?
Comment 7 rfalhar 2012-09-27 10:23:16 UTC 
It seems only Maven plugins, that have -redhat-1 version are missing. Adding plugin repository http://download.devel.redhat.com/brewroot/repos/mead-jb-eap-6-rhel-6-maven-plugins/latest/maven/ makes it build correctly.
Comment 8 Marek Novotny 2012-09-27 10:37:07 UTC 
That is expected, so we could close this issue, right?
Comment 9 Karel Piwko 2012-09-27 13:50:44 UTC 
Yes, marking as verified.
Comment 10 Karel Piwko 2012-11-30 15:34:49 UTC 
Distributed as a part of WFK 2.1.0.GA release.
Note You need to log in before you can comment on or make changes to this bug.