June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19944) JBoss Central URL's need rewiring since yahoo pipes is shutting down

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19944?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-19944: ----------------------------------- Assignee: Fred Bricon > JBoss Central URL's need rewiring since yahoo pipes is shutting down > -------------------------------------------------------------------- > > Key: JBIDE-19944 > URL: https://issues.jboss.org/browse/JBIDE-19944 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.0.Beta2 > > > " Yahoo Pipes: Pipes creation will not be supported as of Aug. 30 this year. Pipes infrastructure will run until Sept. 30, 2015 in read-only mode to help developers migrate their data. Please visit http://pipes.yahoo.com/pipes for additional details." > from http://yahoo.tumblr.com/post/120700756894/q2-2015-progress-report-on-our-... > Deadline is thus August 30th - we should before that have migrated all feedburners that pointed to our yahoo pipes to *something* else. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19765) Add description to easy import wizard

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19765?page=com.atlassian.jira.plugi... ] Lucia Jelinkova updated JBIDE-19765: ------------------------------------ Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Add description to easy import wizard > ------------------------------------- > > Key: JBIDE-19765 > URL: https://issues.jboss.org/browse/JBIDE-19765 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Lucia Jelinkova > Fix For: 4.3.0.Beta2 > > Attachments: wizard.png > > > There is no descrption of the wizard (see picture attached). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19947) OpenShift v3 plugin can't work after update

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19947?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-19947. ----------------------------------- Resolution: Rejected Therefore marking as rejected. If I am wrong, please [~adietish] correct me. > OpenShift v3 plugin can't work after update > ------------------------------------------- > > Key: JBIDE-19947 > URL: https://issues.jboss.org/browse/JBIDE-19947 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Ma Deshuai > > Description of problem: > 1)The uri : http://download.jboss.org/jbosstools/updates/nightly/mars/ don't have any jar package > 2)After update openshift v3 plugin from uri:http://download.jboss.org/jbosstools/updates/nightly/trunk/. Can't launch openshift v3 in eclipse. > Version-Release number of selected component (if applicable): > Eclipse: mars > OpenShift plug : 3.0.0.Beta1-v20150604-1037-B825 > How reproducible: > Always > Steps to Reproduce: > 1.Update OpenShift v3 plugin from http://download.jboss.org/jbosstools/updates/nightly/trunk/ > 2.Restart eclipse and open "OpenShift Explorer" > Actual results: > 2.Open "OpenShift Explorer" with error > Could not create the view: org.jboss.tools.openshift.express.ui.explorer.expressConsoleView > Expected results: > 2.Open "OpenShift Explorer" corectly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19947) OpenShift v3 plugin can't work after update

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19947?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-19947: --------------------------------------- I Think this is not an issue. URL http://download.jboss.org/jbosstools/updates/nightly/mars/ is update site for nightly mars builds (4.3.0) and you have tu use this link in Install New Software... It is not supposed to contain any *.jars inside directly. I have used nightly build from last night (B825, same as yours) and it was updated as expected, without any issue and error in error log. > OpenShift v3 plugin can't work after update > ------------------------------------------- > > Key: JBIDE-19947 > URL: https://issues.jboss.org/browse/JBIDE-19947 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Ma Deshuai > > Description of problem: > 1)The uri : http://download.jboss.org/jbosstools/updates/nightly/mars/ don't have any jar package > 2)After update openshift v3 plugin from uri:http://download.jboss.org/jbosstools/updates/nightly/trunk/. Can't launch openshift v3 in eclipse. > Version-Release number of selected component (if applicable): > Eclipse: mars > OpenShift plug : 3.0.0.Beta1-v20150604-1037-B825 > How reproducible: > Always > Steps to Reproduce: > 1.Update OpenShift v3 plugin from http://download.jboss.org/jbosstools/updates/nightly/trunk/ > 2.Restart eclipse and open "OpenShift Explorer" > Actual results: > 2.Open "OpenShift Explorer" with error > Could not create the view: org.jboss.tools.openshift.express.ui.explorer.expressConsoleView > Expected results: > 2.Open "OpenShift Explorer" corectly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19947) OpenShift v3 plugin can't work after update

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19947?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-19947: ---------------------------------- Affects Version/s: 4.3.0.Beta1 > OpenShift v3 plugin can't work after update > ------------------------------------------- > > Key: JBIDE-19947 > URL: https://issues.jboss.org/browse/JBIDE-19947 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Ma Deshuai > > Description of problem: > 1)The uri : http://download.jboss.org/jbosstools/updates/nightly/mars/ don't have any jar package > 2)After update openshift v3 plugin from uri:http://download.jboss.org/jbosstools/updates/nightly/trunk/. Can't launch openshift v3 in eclipse. > Version-Release number of selected component (if applicable): > Eclipse: mars > OpenShift plug : 3.0.0.Beta1-v20150604-1037-B825 > How reproducible: > Always > Steps to Reproduce: > 1.Update OpenShift v3 plugin from http://download.jboss.org/jbosstools/updates/nightly/trunk/ > 2.Restart eclipse and open "OpenShift Explorer" > Actual results: > 2.Open "OpenShift Explorer" with error > Could not create the view: org.jboss.tools.openshift.express.ui.explorer.expressConsoleView > Expected results: > 2.Open "OpenShift Explorer" corectly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19787) As a user I want to import existing OpenShift projects into my Eclipse workspace

by Ma Deshuai (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19787?page=com.atlassian.jira.plugi... ] Ma Deshuai commented on JBIDE-19787: ------------------------------------ [~adietish] I can't update the jbt, here is the issue https://issues.jboss.org/browse/JBIDE-19947. Help to view it . thanks. > As a user I want to import existing OpenShift projects into my Eclipse workspace > -------------------------------------------------------------------------------- > > Key: JBIDE-19787 > URL: https://issues.jboss.org/browse/JBIDE-19787 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: import_wizard > Fix For: 4.3.0.Beta1 > > > This is the case where a user has added resources via the CLI or console and wants to create an Eclipse project in order to start developing. > The Eclipse project nature will be of the appropriate type as inferred from the source. > Main focus is to correctly import java/maven projects or “General” project otherwise. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19947) OpenShift v3 plugin can't work after update

by Ma Deshuai (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19947?page=com.atlassian.jira.plugi... ] Ma Deshuai updated JBIDE-19947: ------------------------------- Issue Type: Bug (was: Feature Request) > OpenShift v3 plugin can't work after update > ------------------------------------------- > > Key: JBIDE-19947 > URL: https://issues.jboss.org/browse/JBIDE-19947 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Ma Deshuai > > Description of problem: > 1)The uri : http://download.jboss.org/jbosstools/updates/nightly/mars/ don't have any jar package > 2)After update openshift v3 plugin from uri:http://download.jboss.org/jbosstools/updates/nightly/trunk/. Can't launch openshift v3 in eclipse. > Version-Release number of selected component (if applicable): > Eclipse: mars > OpenShift plug : 3.0.0.Beta1-v20150604-1037-B825 > How reproducible: > Always > Steps to Reproduce: > 1.Update OpenShift v3 plugin from http://download.jboss.org/jbosstools/updates/nightly/trunk/ > 2.Restart eclipse and open "OpenShift Explorer" > Actual results: > 2.Open "OpenShift Explorer" with error > Could not create the view: org.jboss.tools.openshift.express.ui.explorer.expressConsoleView > Expected results: > 2.Open "OpenShift Explorer" corectly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19947) OpenShift v3 plugin can't work after update

by Ma Deshuai (JIRA)

Ma Deshuai created JBIDE-19947: ---------------------------------- Summary: OpenShift v3 plugin can't work after update Key: JBIDE-19947 URL: https://issues.jboss.org/browse/JBIDE-19947 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Ma Deshuai Description of problem: 1)The uri : http://download.jboss.org/jbosstools/updates/nightly/mars/ don't have any jar package 2)After update openshift v3 plugin from uri:http://download.jboss.org/jbosstools/updates/nightly/trunk/. Can't launch openshift v3 in eclipse. Version-Release number of selected component (if applicable): Eclipse: mars OpenShift plug : 3.0.0.Beta1-v20150604-1037-B825 How reproducible: Always Steps to Reproduce: 1.Update OpenShift v3 plugin from http://download.jboss.org/jbosstools/updates/nightly/trunk/ 2.Restart eclipse and open "OpenShift Explorer" Actual results: 2.Open "OpenShift Explorer" with error Could not create the view: org.jboss.tools.openshift.express.ui.explorer.expressConsoleView Expected results: 2.Open "OpenShift Explorer" corectly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19085) tools.jboss.org devstudio downloads does not mention it is update site content only and to use 8.0.0 installer

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19085?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-19085: ------------------------------------- Assignee: Max Rydahl Andersen (was: Xavier Coulon) > tools.jboss.org devstudio downloads does not mention it is update site content only and to use 8.0.0 installer > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19085 > URL: https://issues.jboss.org/browse/JBIDE-19085 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta1 > > > from grdryn on irc: > "Hi folks, tools.jboss.org/downloads/ shows latest devstudio as 8.0.2.GA, but jboss.org/products/devstudio/download/ still lists 8.0.0.GA > ^Just FYI...I'm not sure if that's normal, or if the latter should be updated" > and yes, we should look at making it possible to mark an install as "updatesite" only or somehow refer to the "nearest" installer. > i.e. maybe something like: > {code} > updatesite_only: true > {code} > and then just refer to old installer link in the download ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3258) Docker Tooling (Advanced Integration)

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3258?page=com.atlassian.jira.plugin.... ] Xavier Coulon commented on JBDS-3258: ------------------------------------- Postponing to 9.0.0.Beta2 since not all request features have been implemen > Docker Tooling (Advanced Integration) > ------------------------------------- > > Key: JBDS-3258 > URL: https://issues.jboss.org/browse/JBDS-3258 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: docker, requirements > Reporter: Burr Sutter > Assignee: Xavier Coulon > Fix For: 9.0.0.Beta2 > > > Once significant delta between the "basic" and advanced scenarios is that here I wish to custom craft my own docker images instead of using an existing one - where my custom crafted image includes my .war or .ear. > In addition to the basic integrations of pull, run, stop, commit and push > boot2docker init > boot2docker up > boot2docker down > boot2docker ip > docker run -d > docker ps > docker rm > docker rmi > docker build > End-user steps: > 0) assumes boot2docker has been dowloaded and installed > 1) boot2docker init : required to to insure boot2docker-vm is properly initialized > 2) boot2docker up : starts the VirtualBox boot2docker-vm > 3) boot2docker ip : returns the IP address - this will be vital when it comes to testing - it would need to be integrated with our Run - As on Docker capability. > 4) docker run -i -t -p 80:8080 jboss/wildfly -d : the -d means detached, I may need to run N containers simultaneously > 5) docker ps : allows me to see all my currently running containers > 6) docker rm : allows me to kill a currently running container > 7) docker rmi : allows me to remove a local image > 8) docker build : assumes that I have crafted a Dockerfile - this will create the local image - with my .war or .ear embedded > 9) docker run : this new created image > The docker build scenario can be triggered via a Maven plugin > The docker build scenario can also be triggered via an Eclipse menu option (like a Maven install) > We need to figure out the file-system layout so that the Dockerfile and the maven project are all nicely checked into git/svn. So that Jenkins can pick up this repository and perform an automated "docker build" (post Maven install) and then run all the appropriate unit, integration and functional tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015