[jbossts-issues] [JBoss JIRA] (JBTM-1828) doc build fails due to missing dependencies

Michael Musgrove (JIRA) jira-events at lists.jboss.org
Mon Jul 8 11:27:21 EDT 2013


    [ https://issues.jboss.org/browse/JBTM-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788209#comment-12788209 ] 

Michael Musgrove edited comment on JBTM-1828 at 7/8/13 11:26 AM:
-----------------------------------------------------------------

Adding a repositories section to the pom and specifying the JBoss Release and Thirdparty release repositories (and removing JBoss Release Repository from the distributionManagement section) seems more reliable, as in:

{code}
  <repositories>
    <repository>
      <id>jboss-thirdparty-releases-repository</id>
      <name>JBoss Thirdparty Release Repository</name>
      <url>https://repository.jboss.org/nexus/content/repositories/thirdparty-releases</url>
    </repository>
    <repository>
      <id>jboss-releases-repository</id>
      <name>JBoss Release Repository</name>
      <url>https://repository.jboss.org/nexus/content/repositories/releases/</url>
    </repository>
  </repositories>
{code}
I don't know why we have been using the staging repository so I am reluctant to commit the fix until someone can explain why we might need staging?
                
      was (Author: mmusgrov):
    Adding a repositories section to the pom and specifying the JBoss Release and Thirdparty release repositories (and removing JBoss Release Repository from the distributionManagement section) seems more reliable, as in:

<repositories>
    <repository>
      <id>jboss-thirdparty-releases-repository</id>
      <name>JBoss Thirdparty Release Repository</name>
      <url>https://repository.jboss.org/nexus/content/repositories/thirdparty-releases</url>
    </repository>
    <repository>
      <id>jboss-releases-repository</id>
      <name>JBoss Release Repository</name>
      <url>https://repository.jboss.org/nexus/content/repositories/releases/</url>
    </repository>
</repositories>

I don't know why we have been using the staging repository so I am reluctant to commit the fix until someone can explain why we might need staging?
                  
> doc build fails due to missing dependencies
> -------------------------------------------
>
>                 Key: JBTM-1828
>                 URL: https://issues.jboss.org/browse/JBTM-1828
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Testing
>    Affects Versions: 5.0.0.M3
>            Reporter: Michael Musgrove
>            Assignee: Tom Jenkinson
>             Fix For: 5.0.0.M4
>
>
> The build depends on the staging repository for jdocbook dependencies but when this is down the build fails. We should be relying on a more accessible repository. See the workaround on how to manually install the dependencies.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbossts-issues mailing list