April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19382) Explorer: Prompt for credentials for existing v3 connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19382?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19382: ------------------------------------- Summary: Explorer: Prompt for credentials for existing v3 connection (was: Prompt for credentials for existing v3 connection) > Explorer: Prompt for credentials for existing v3 connection > ----------------------------------------------------------- > > Key: JBIDE-19382 > URL: https://issues.jboss.org/browse/JBIDE-19382 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19555) Migrate Openshift code to use openshift-restclient-java for v3

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19555?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19555: ------------------------------------- Labels: new_and_noteworthy (was: ) > Migrate Openshift code to use openshift-restclient-java for v3 > -------------------------------------------------------------- > > Key: JBIDE-19555 > URL: https://issues.jboss.org/browse/JBIDE-19555 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19555) Migrate Openshift code to use openshift-restclient-java for v3

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19555?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19555. ------------------------------------ Resolution: Done re-closing > Migrate Openshift code to use openshift-restclient-java for v3 > -------------------------------------------------------------- > > Key: JBIDE-19555 > URL: https://issues.jboss.org/browse/JBIDE-19555 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19681) OpenShift New and Noteworthy for 4.3.0.Alpha2

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19681?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19681: ---------------------------------------- Assignee: Andre Dietisheim > OpenShift New and Noteworthy for 4.3.0.Alpha2 > --------------------------------------------- > > Key: JBIDE-19681 > URL: https://issues.jboss.org/browse/JBIDE-19681 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If OpenShift is not listed here check if there are issues that should be added and add them. > Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3408: ------------------------------------------- running latest installer fro devstudio 9. No there are no sites in the installer about jboss.org afaics. But that would be separate issue. somehow the metadata we got for devstudio product refers to jboss.org - it should not. it should actually not need to refer or fetch anything for an offline install. > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18772: --------------------------------------------- im not wrong ;) just because the current parent pom has all these shared variables does not automatically mean it should be munged in together with deployment setup. The shared parameters could stay in the "root" parent pom, but another specific parent could be made to handle the project type specific deployment. I'm not saying this is what we should go do blindly, just saying there are ways to better split the different concerns to avoid conflict/unnecessary churn. btw. I thought the suggestion was to just use mvn deploy - not that everything would use the same mojo. i.e. my expectations would have been that the pom of the "non-module" projects would override what the parent says about deploy and configure it properly for them using whatever scripts etc. we need for them ? > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19697: --------------------------------------------- [~snjeza] the surprise is that it is being filled with a non-standard location. So this does not seem like normal behavior. > org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19697 > URL: https://issues.jboss.org/browse/JBIDE-19697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Snjezana Peco > > When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs' > Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs > {code} > This is inside the file: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat > eclipse.preferences.version=1 > runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n > {code} > It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen? > I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now. > Can somebody explain what's going on? > Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15884: --------------------------------------------- if they get to be duplicated and no way to somehow hide them in quickaccess then I suggest we keep using the old id/name for the command to retain backwards compatibility. > Allow the runBrowserSim command to accept a URL as a parameter > -------------------------------------------------------------- > > Key: JBIDE-15884 > URL: https://issues.jboss.org/browse/JBIDE-15884 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.0.Final > Reporter: Vineet Reynolds > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.3.0.Beta1 > > > Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected. > When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19628) Update QA Arquillian tests to be in sync with Red Deer changes

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19628?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19628. ------------------------------- Verified > Update QA Arquillian tests to be in sync with Red Deer changes > -------------------------------------------------------------- > > Key: JBIDE-19628 > URL: https://issues.jboss.org/browse/JBIDE-19628 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.3.Final > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19628) Update QA Arquillian tests to be in sync with Red Deer changes

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19628?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-19628: ------------------------------------- Thanks for noticing this. We have branches only for major releases so we do not have branch for 4.3.0.Alpha2 in integration tests. Yes we should update master to use Beta1 parent pom > Update QA Arquillian tests to be in sync with Red Deer changes > -------------------------------------------------------------- > > Key: JBIDE-19628 > URL: https://issues.jboss.org/browse/JBIDE-19628 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.3.Final > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

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 April 2015