[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick commented on JBTIS-654:
-----------------------------------------
[~maxandersen] Good to know. :)
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22148) Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22148?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22148 at 4/14/16 10:31 AM:
--------------------------------------------------------------
To verify this was changed between respin-b and respin-c:
Diff these two:
http://download.jboss.org/jbosstools/mars/staging/updates/discovery.centr...
http://download.jboss.org/jbosstools/mars/staging/updates/discovery.centr...
or
https://devstudio.jboss.com/9.0/staging/updates/discovery.central/9.1.0.C...
https://devstudio.jboss.com/9.0/staging/updates/discovery.central/9.1.0.C...
was (Author: nickboldt):
To verify this is changed between respin-b and respin-c:
Diff these two:
http://download.jboss.org/jbosstools/mars/staging/updates/discovery.centr...
http://download.jboss.org/jbosstools/mars/staging/updates/discovery.centr...
or
https://devstudio.jboss.com/9.0/staging/updates/discovery.central/9.1.0.C...
https://devstudio.jboss.com/9.0/staging/updates/discovery.central/9.1.0.C...
> Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22148
> URL: https://issues.jboss.org/browse/JBIDE-22148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite, upstream
> Affects Versions: 4.1.2.Final, 4.2.3.Final, 4.3.0.Final, 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-c
> Fix For: 4.3.1.CR1
>
>
> {code}
> 09:26:43 [p2.dir] !ENTRY org.eclipse.equinox.p2.artifact.repository 4 1000 2016-04-09 09:26:43.985
> 09:26:43 [p2.dir] !MESSAGE No repository found at http://update.zeroturnaround.com/update-site-jboss/.
> {code}
> So, we need to use an alternate update site, such as the one linked from Eclipse Marketplace, eg., http://update.zeroturnaround.com/update-site/
> And we need to verify that the features we include in Central are still available on the new site.
> Affected jobs:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22148) Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22148?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22148:
------------------------------------
To verify this is changed between respin-b and respin-c:
Diff these two:
http://download.jboss.org/jbosstools/mars/staging/updates/discovery.centr...
http://download.jboss.org/jbosstools/mars/staging/updates/discovery.centr...
or
https://devstudio.jboss.com/9.0/staging/updates/discovery.central/9.1.0.C...
https://devstudio.jboss.com/9.0/staging/updates/discovery.central/9.1.0.C...
> Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22148
> URL: https://issues.jboss.org/browse/JBIDE-22148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite, upstream
> Affects Versions: 4.1.2.Final, 4.2.3.Final, 4.3.0.Final, 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-c
> Fix For: 4.3.1.CR1
>
>
> {code}
> 09:26:43 [p2.dir] !ENTRY org.eclipse.equinox.p2.artifact.repository 4 1000 2016-04-09 09:26:43.985
> 09:26:43 [p2.dir] !MESSAGE No repository found at http://update.zeroturnaround.com/update-site-jboss/.
> {code}
> So, we need to use an alternate update site, such as the one linked from Eclipse Marketplace, eg., http://update.zeroturnaround.com/update-site/
> And we need to verify that the features we include in Central are still available on the new site.
> Affected jobs:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22174) Deploy Image to OpenShift wizard could respect selected connection and project from OpenShift Explorer
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22174?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22174:
-----------------------------------------------
[~fbricon], please take a look at the pull request.
> Deploy Image to OpenShift wizard could respect selected connection and project from OpenShift Explorer
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22174
> URL: https://issues.jboss.org/browse/JBIDE-22174
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Minor
>
> When opening Deploy Image to OpenShift wizard via context menu of a docker image in Docker Explorer, selected project (or a connection if no project under a connection is selected) should be selected in combo in the wizard. At the moment, if there is precisely 1 connection, it is selected (if there are more connections, no connection is selected and following steps is not reachable) and if there is precisely 1 project, that one is selected (if there are more projects, no project is selected). This could be refined a bit. In case of selection would be the selected one in combo. In case of existence of more connections/projects and no selection, maybe the first one listed could be selected (but this is probably personal preference, maybe it is not a good idea).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years