August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19852) Set default path for runtimes downloaded and installed via java -jar

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19852?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-19852: ------------------------------------------------- Emmett Underhill <eunderhi(a)redhat.com> changed the Status of [bug 1225450|https://bugzilla.redhat.com/show_bug.cgi?id=1225450] from MODIFIED to ON_QA > Set default path for runtimes downloaded and installed via java -jar > -------------------------------------------------------------------- > > Key: JBIDE-19852 > URL: https://issues.jboss.org/browse/JBIDE-19852 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > > I'm not sure if this is possible, but it would be nice if the installer would fill the installation path from Download Runtime wizard. > The same for runtime detection after the download and installation is finished. > Example scenario: > 1. Select JBoss DV 6.1 for download&installation > 2. On "Download Runtime" page of wizard fill some install folder (for example /home/<user>/downloadedDV) > 3. Click Finish - DV is downloaded and it's installer executed > ASSERT: /home/<user>/downloadedDV is default installation path in installer > 4. In the installer select different installation folder (for example /home/<user>/DV) > 5. Finish installer > ASSERT: /home/<user>/DV is added to runtime-detection paths instead of /home/<user>/downloadedDV -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20402) Contribute "Deploy to Openshift" menu in Docker Tools' Image view

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20402?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-20402: ---------------------------------- Description: To make this happen we will need docker tooling to provide: * ports * env variables * volumes A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be: * Ask user about ports, additional env besides those already provided in the image, volumes, * Ask about # of replicas, triggers * tag and push image to registry (tag=repo/project/stream) ** repo is either assumed to be Dockerhub, or the route to the OS registry * create a deploymentConfig for the selected image * create a service for the image * optionally create a route Consider running oc new-app on an image to see what it generates ================================================================== It's possible to contribute a new menu/handler to the Docker Tooling Images view. We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift" The following infos are required to actually be able to deploy the selected image onto OS: - the local docker registry. OS will need a route to be able to access it - the docker hub registry - environment variables - ports - volumes The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta... Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta... Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1 was: To make this happen we will need docker tooling to provide: * ports * env variables * volumes A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be: * Ask user about ports, additional env besides those already provided in the image, volumes, * Ask about # of replicas, triggers * push image to OS registry if ** image is not currently in Dockerhub ** OS registry has a route (this we might have to ask about. fail if it doesnt exist? ) * create an ImageStream for the selected image * create a deploymentConfig for the selected image * create a service for the image * optionally create a route Consider running oc new-app on an image to see what it generates ================================================================== It's possible to contribute a new menu/handler to the Docker Tooling Images view. We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift" The following infos are required to actually be able to deploy the selected image onto OS: - the local docker registry. OS will need a route to be able to access it - the docker hub registry - environment variables - ports - volumes The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta... Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta... Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1 > Contribute "Deploy to Openshift" menu in Docker Tools' Image view > ----------------------------------------------------------------- > > Key: JBIDE-20402 > URL: https://issues.jboss.org/browse/JBIDE-20402 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: deployment_config.json, run image - screen 1.png, run image 2.png > > > To make this happen we will need docker tooling to provide: > * ports > * env variables > * volumes > A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be: > * Ask user about ports, additional env besides those already provided in the image, volumes, > * Ask about # of replicas, triggers > * tag and push image to registry (tag=repo/project/stream) > ** repo is either assumed to be Dockerhub, or the route to the OS registry > * create a deploymentConfig for the selected image > * create a service for the image > * optionally create a route > Consider running oc new-app on an image to see what it generates > ================================================================== > It's possible to contribute a new menu/handler to the Docker Tooling Images view. > We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift" > The following infos are required to actually be able to deploy the selected image onto OS: > - the local docker registry. OS will need a route to be able to access it > - the docker hub registry > - environment variables > - ports > - volumes > The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git > The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta... > Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta... > Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-469) wrong description on update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-469?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-469: ----------------------------- Fix Version/s: 4.3.0.Alpha1 > wrong description on update site > -------------------------------- > > Key: JBTIS-469 > URL: https://issues.jboss.org/browse/JBTIS-469 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Fix For: 4.3.0.Alpha1 > > Attachments: JBDS-IS-update-site-descriptions.png, JBT-IS-update-site-descriptions-wrong.png > > > When I load up the JBT IS 4.3.0.Alpha1 update site [1] in Eclipse, I see this title: "JBDS Integration Stack Aggregate - Final" > [1] http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-468) Cannot resolve Teiid Designer dependencies in JBT IS at install-time

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-468?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-468: ----------------------------- Summary: Cannot resolve Teiid Designer dependencies in JBT IS at install-time (was: Cannot resolve Teiid Designer dependencies at install-time) > Cannot resolve Teiid Designer dependencies in JBT IS at install-time > -------------------------------------------------------------------- > > Key: JBTIS-468 > URL: https://issues.jboss.org/browse/JBTIS-468 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, target-platform, teiid > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > > Steps to repro: > 1. install eclipse-jee-mars-R-linux-gtk-x86_64.tar.gz and launch with sun-java2-8.0 (1.8.0-b132) > 2. Help > Install new > Add these URLs: > * http://download.jboss.org/jbosstools/mars/development/updates/ > * http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... > 3. select all features on the JBTIS site. Install all. Restart when prompted. > 4. Help > Install new > Add this URL: > * http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... > 5. Install everything but Teiid Designer 9.0.2, due to missing dependency on *org.jboss.tools.locus.sf.saxon [9.2.1,9.3.0)*: > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: Teiid Designer 9.0.2.Final-v20150615-1425-B1128 (org.teiid.designer.feature.feature.group 9.0.2.Final-v20150615-1425-B1128) > Missing requirement: Teiid DataTools Connectivity 9.0.2.Final-v20150615-1425-B1128 (org.teiid.datatools.connectivity.feature.feature.group 9.0.2.Final-v20150615-1425-B1128) requires 'org.jboss.tools.locus.sf.saxon [9.2.1,9.3.0)' but it could not be found > Cannot satisfy dependency: > From: Teiid Designer 9.0.2.Final-v20150615-1425-B1128 (org.teiid.designer.feature.feature.group 9.0.2.Final-v20150615-1425-B1128) > To: org.teiid.datatools.connectivity.feature.feature.group [9.0.2.Final-v20150615-1425-B1128]{code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-469) wrong description on update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-469?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-469: ---------------------------------- Note that just as "Final" shouldn't appear on the JBT IS site, nor should "GA" shouldn't appear on the JBDS site, because they're both only Alpha1. That's just ignorant... allegedly. :D https://www.youtube.com/watch?v=Z2Di716BBXQ > wrong description on update site > -------------------------------- > > Key: JBTIS-469 > URL: https://issues.jboss.org/browse/JBTIS-469 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Attachments: JBDS-IS-update-site-descriptions.png, JBT-IS-update-site-descriptions-wrong.png > > > When I load up the JBT IS 4.3.0.Alpha1 update site [1] in Eclipse, I see this title: "JBDS Integration Stack Aggregate - Final" > [1] http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-468) Cannot resolve Teiid Designer dependencies at install-time

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-468?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-468: ---------------------------------- Please note that installation for the JBDS IS 9 Alpha1 content DOES work, if you add the target platform(s) in too. 1. install eclipse-jee-mars-R-linux-gtk-x86_64.tar.gz and launch with sun-java2-8.0 (1.8.0-b132) 2. Help > Install new > Add these URLs: * https://devstudio.redhat.com/9.0/development/updates/ * http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... * http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... 3. select all features on the JBTIS site. Install all. Restart when prompted. 4. Help > Install new > Add these URLs: * http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... * http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... 5. Install everything (this time, Teiid can be installed). So... why isn't there a target platform for JBT IS ? Or, why isn't there a composite site which combines the two into a single URL, like we do here [1] or here [2] ? [1] http://download.jboss.org/jbosstools/mars/development/updates/compositeAr... [2] https://devstudio.redhat.com/9.0/development/updates/compositeContent.xml > Cannot resolve Teiid Designer dependencies at install-time > ---------------------------------------------------------- > > Key: JBTIS-468 > URL: https://issues.jboss.org/browse/JBTIS-468 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, target-platform, teiid > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > > Steps to repro: > 1. install eclipse-jee-mars-R-linux-gtk-x86_64.tar.gz and launch with sun-java2-8.0 (1.8.0-b132) > 2. Help > Install new > Add these URLs: > * http://download.jboss.org/jbosstools/mars/development/updates/ > * http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... > 3. select all features on the JBTIS site. Install all. Restart when prompted. > 4. Help > Install new > Add this URL: > * http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... > 5. Install everything but Teiid Designer 9.0.2, due to missing dependency on *org.jboss.tools.locus.sf.saxon [9.2.1,9.3.0)*: > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: Teiid Designer 9.0.2.Final-v20150615-1425-B1128 (org.teiid.designer.feature.feature.group 9.0.2.Final-v20150615-1425-B1128) > Missing requirement: Teiid DataTools Connectivity 9.0.2.Final-v20150615-1425-B1128 (org.teiid.datatools.connectivity.feature.feature.group 9.0.2.Final-v20150615-1425-B1128) requires 'org.jboss.tools.locus.sf.saxon [9.2.1,9.3.0)' but it could not be found > Cannot satisfy dependency: > From: Teiid Designer 9.0.2.Final-v20150615-1425-B1128 (org.teiid.designer.feature.feature.group 9.0.2.Final-v20150615-1425-B1128) > To: org.teiid.datatools.connectivity.feature.feature.group [9.0.2.Final-v20150615-1425-B1128]{code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-469) wrong description on update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-469?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-469: ----------------------------- Attachment: JBT-IS-update-site-descriptions-wrong.png JBDS-IS-update-site-descriptions.png Compare the names of the JBT IS sites: !JBT-IS-update-site-descriptions-wrong.png! vs. the JBDS IS sites: !JBDS-IS-update-site-descriptions.png! > wrong description on update site > -------------------------------- > > Key: JBTIS-469 > URL: https://issues.jboss.org/browse/JBTIS-469 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Attachments: JBDS-IS-update-site-descriptions.png, JBT-IS-update-site-descriptions-wrong.png > > > When I load up the JBT IS 4.3.0.Alpha1 update site [1] in Eclipse, I see this title: "JBDS Integration Stack Aggregate - Final" > [1] http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-469) wrong description on update site

by Nick Boldt (JIRA)

Nick Boldt created JBTIS-469: -------------------------------- Summary: wrong description on update site Key: JBTIS-469 URL: https://issues.jboss.org/browse/JBTIS-469 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 4.3.0.Alpha1 Reporter: Nick Boldt When I load up the JBT IS 4.3.0.Alpha1 update site [1] in Eclipse, I see this title: "JBDS Integration Stack Aggregate - Final" [1] http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-399) Cannot install Fuse/SwitchYard tooling in offline mode

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-399?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-399: ---------------------------------- Quick test today to see if Fuse stuff is available in JBTIS 4.3.0.Alpha1 build, and it's not. Yet. {quote}Fuse tooling will be ready for code freeze for alpha 1 code freeze on Aug 19.{quote} > Cannot install Fuse/SwitchYard tooling in offline mode > ------------------------------------------------------ > > Key: JBTIS-399 > URL: https://issues.jboss.org/browse/JBTIS-399 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 9.0.0.Alpha1 > > Attachments: error.txt, oi1.png, oi2.png, oi3.png > > > Cannot install JBDS-IS 8.0.0.GA early access in offline mode. Note that DV tooling (Teiid Designer and ModeShape) can be installed without any problem. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-468) Cannot resolve Teiid Designer dependencies at install-time

by Nick Boldt (JIRA)

Nick Boldt created JBTIS-468: -------------------------------- Summary: Cannot resolve Teiid Designer dependencies at install-time Key: JBTIS-468 URL: https://issues.jboss.org/browse/JBTIS-468 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution, target-platform, teiid Affects Versions: 4.3.0.Alpha1 Reporter: Nick Boldt Steps to repro: 1. install eclipse-jee-mars-R-linux-gtk-x86_64.tar.gz and launch with sun-java2-8.0 (1.8.0-b132) 2. Help > Install new > Add these URLs: * http://download.jboss.org/jbosstools/mars/development/updates/ * http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... 3. select all features on the JBTIS site. Install all. Restart when prompted. 4. Help > Install new > Add this URL: * http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... 5. Install everything but Teiid Designer 9.0.2, due to missing dependency on *org.jboss.tools.locus.sf.saxon [9.2.1,9.3.0)*: {code} Cannot complete the install because one or more required items could not be found. Software being installed: Teiid Designer 9.0.2.Final-v20150615-1425-B1128 (org.teiid.designer.feature.feature.group 9.0.2.Final-v20150615-1425-B1128) Missing requirement: Teiid DataTools Connectivity 9.0.2.Final-v20150615-1425-B1128 (org.teiid.datatools.connectivity.feature.feature.group 9.0.2.Final-v20150615-1425-B1128) requires 'org.jboss.tools.locus.sf.saxon [9.2.1,9.3.0)' but it could not be found Cannot satisfy dependency: From: Teiid Designer 9.0.2.Final-v20150615-1425-B1128 (org.teiid.designer.feature.feature.group 9.0.2.Final-v20150615-1425-B1128) To: org.teiid.datatools.connectivity.feature.feature.group [9.0.2.Final-v20150615-1425-B1128]{code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2015