[jbosstools-issues] [JBoss JIRA] (JBIDE-18590) Split /discovery/ staging site into 3 sites: Core+Central, EA, and Discovery
Max Rydahl Andersen (JIRA)
issues at jboss.org
Fri Oct 10 18:04:12 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-18590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010837#comment-13010837 ]
Max Rydahl Andersen commented on JBIDE-18590:
---------------------------------------------
a) since this site did not provide a proper test I do not see this as a problem. Or rather continuing using this site is more problematic than actually using the ide-properties properly and have it point to the individual sites/urils as it would at release time.
b) are linking not what we do anyway for release ? and is this not what the "tripod" facade-generation can be used for ? Have the site generate with a link to a TP in a subfolder to make it an associate link instead of composite for the TP ? Having the subfolder of central under luna is what I suggested in other jiras since it among other things should make the publishing wether to staging, development or stable uniform. I'm still rather convinced that using relative urls in majority of these sites would be very helpful and result in less manual intervention being needed if anything at all.
c) Okey - but this have been required/expected since day one. Earlyaccess and Central TP's or sites are not to be merged/combined.
> Split /discovery/ staging site into 3 sites: Core+Central, EA, and Discovery
> ----------------------------------------------------------------------------
>
> Key: JBIDE-18590
> URL: https://issues.jboss.org/browse/JBIDE-18590
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.2.0.CR2
> Reporter: Nick Boldt
>
> Old org (Central, EA, Discovery, and EA Properties co-located in a single folder for ease of offline testing):
> http://download.jboss.org/jbosstools/discovery/development/ <version>
> Using /discovery/ URLs to test Central was still the recommended approach up to Beta2d [1]. We dropped that blurb for Beta3, because it became an internal detail exposed through ide-config.properties, and was no longer needed.
> * http://lists.jboss.org/pipermail/jbosstools-dev/2014-June/009001.html (Beta2d)
> * http://lists.jboss.org/pipermail/jbosstools-dev/2014-July/009090.html (Beta3)
> [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/jbosstools-4.2.0.Beta2x/release_guide/8.0/JBT_4.2.0.Beta2_Staging_For_QE.adoc
> ----
> New org, to do for JBT 4.3:
> http://download.jboss.org/jbosstools/updates/staging/luna/ (needs to include Central now)
> http://download.jboss.org/jbosstools/earlyaccess/staging/luna/ (needs to include latest EA now, and the EA properties file)
> http://download.jboss.org/jbosstools/discovery/staging/luna/ (just the discovery plugin)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the jbosstools-issues
mailing list