[
https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin....
]
Paul Leacu commented on JBTIS-508:
----------------------------------
Here's my proposal for the most pressing issue - removal of unwanted early access URLs
in the Eclipse Luna
install update site list (without rebuilding anything):
1. Update
http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4...
composites to contain the following children:
{code}
<children size='3'>
<child
location='http://download.jboss.org/jbosstools/updates/stable/luna/...
<child
location='http://download.jboss.org/jbosstools/updates/stable/luna/in...
<child
location='http://download.jboss.org/jbosstools/targetplatforms/jbtist...
</children>
{code}
2. Create
http://download.jboss.org/jbosstools/discovery/stable/integration-stack/e...
- composites to contain:
{code}
<children size='3'>
<child
location='http://download.jboss.org/jbosstools/updates/stable/luna/...
<child
location='http://download.jboss.org/jbosstools/updates/stable/luna/in...
<child
location='http://download.jboss.org/jbosstools/targetplatforms/jbtist...
</children>
{code}
- modify the plugin.xml in the EA discovery jar to establish the following as the
siteUrl:
{code}
siteUrl="${jboss.discovery.earlyaccess.site.integration-stack.url}"
{code}
3. The current jbosstools-directory.xml
http://download.jboss.org/jbosstools/updates/stable/luna/jbosstools-direc... appears
as follows:
{code}
<directory
xmlns="http://www.eclipse.org/mylyn/discovery/directory/">
<entry
url="plugins/org.jboss.tools.central.discovery.earlyaccess_4.2.3.Final-v20150327-0914-B526.jar"
permitCategories="true"/>
<entry
url="plugins/org.jboss.tools.central.discovery_4.2.3.Final-v20150409-0637-B528.jar"
permitCategories="true"/>
<entry permitCategories="true"
url="plugins/org.jboss.tools.central.discovery.integration-stack_4.2.3.Final-v20150824-1515-B22.jar"/>
<entry permitCategories="true"
url="plugins/org.jboss.tools.central.discovery.integration-stack.earlyaccess_4.2.3.Final-v20150824-1515-B22.jar"/>
</directory>
{code}
I'll copy the updated IS EA jar into the parent plugins directory.
4. Create a composite site
http://download.jboss.org/jbosstools/discovery/stable/integration-stack/e... which
references
http://download.jboss.org/jbosstools/discovery/stable/integration-stack/e...
5. Modify ide-config.properties to set the
jboss.discovery.earlyaccess.site.integration-stack.url property:
{code}
jboss.discovery.earlyaccess.site.integration-stack.url|jbosstools|4.2.4=h...
jboss.discovery.earlyaccess.site.integration-stack.url|jbosstools|4.2=htt...
{code}
That should do it for JBT. I'd like to complete everything there and then proceed to
do similar things to devstudio. It works locally for me.
integration stack update sites mix discovery and earlyaccess causing
inconsistent update mechanism
--------------------------------------------------------------------------------------------------
Key: JBTIS-508
URL:
https://issues.jboss.org/browse/JBTIS-508
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: releng
Reporter: Max Rydahl Andersen
Assignee: Paul Leacu
Priority: Blocker
While reviewing JBIDE-20803 I noticed the following:
{code}
jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo...
{code}
The stable release for 4.2.4 is stated to point to the stable integration stack url which
on surface looks good:
But there are a few problems:
1) why not just point to
http://download.jboss.org/jbosstools/updates/stable/luna/ and
have the above internal detail url composited in ?
2) the actual composite behind it right now is
http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4...
which links in
http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4...
(our main sites should never composite earlyaccees since then when users install supported
versions they suddenly will now also have access to earlyaccess.
#1 is mainly just to reduce the number of updatesites actually necessary for users to
work with
#2 seems to be something inherent broken in the IS build since earlyaccess shold *never*
be aggregated into the release site.
Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site.
I would also have expected that the discovery site with the discovery plugins was kept
*separate* from the actual update sites to avoid any coupling between these.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)