[jbosstools-issues] [JBoss JIRA] (JBDS-2674) Publish JBDS TP onto download.jboss.org instead of internal server so that JBDS can build from sources using -Dtpc.targetKind=unified as default

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBDS-2674:
----------------------------------

Also updating generated URLs used in staged discovery sites:

https://github.com/jbosstools/jbosstools-discovery/pull/23 (master)
https://github.com/jbosstools/jbosstools-discovery/pull/24 (41x)

                
> Publish JBDS TP onto download.jboss.org instead of internal server so that JBDS can build from sources using -Dtpc.targetKind=unified as default
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-2674
>                 URL: https://issues.jboss.org/browse/JBDS-2674
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Build, updatesite
>    Affects Versions: 7.0.0.Beta2
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>              Labels: respin-a
>             Fix For: 7.0.0.CR1
>
>
> As reported in JBDS-2673 (which conflicts with the needs of JBDS-2456), we need a solution which accommodates both Nick's and Max's definitions of "Correct" and "Simple". 
> Thus, to allow all JBDS builds to default to using the unified TP instead of the multiple one from which the unified is built, we must publish the TP to a site which is fully public (eg., on download.jboss.org instead of www.qa).
> Then the JBDS product root pom can be updated to default to "unified" and builds can be done by anyone regardless of VPN access, without needing a different config for Jenkins vs. non-VPN users.

--
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