December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21295) Server Adpater: implement Show in > Web Browser works

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21295?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21295: ------------------------------------------ merged and pushed to jbosstools-4.3.x > Server Adpater: implement Show in > Web Browser works > ----------------------------------------------------- > > Key: JBIDE-21295 > URL: https://issues.jboss.org/browse/JBIDE-21295 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.Beta1 > > > Current code in OpenShiftServerExtendedProperties#getWelcomePage only takes the 1st route which will open the wrong page if there are several ones in the same page. It is therefore commented. We need to find a way to either give the user a chance to choose the route among the available ones or find a way to programmatically choose the right one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21307) Server Adapter: ensure oc binary that's used for rsync is v1.1.0.1+

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21307?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21307: ------------------------------------- Labels: oc_binary openshift_v3 server_adapter (was: ) > Server Adapter: ensure oc binary that's used for rsync is v1.1.0.1+ > ------------------------------------------------------------------- > > Key: JBIDE-21307 > URL: https://issues.jboss.org/browse/JBIDE-21307 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: oc_binary, openshift_v3, server_adapter > Fix For: 4.3.1.Beta2 > > > Because of https://github.com/openshift/origin/issues/6109 publishing with the server adapter (which does a oc rsync behind the scenes) only properly works with oc v1.1.0.1. Versions below require the user to manually > {code} > oc login --server=<server that we publish to> --token=... > {code} > We should check the version and warn if the user is using an oc that is older than this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21307) Server Adapter: ensure oc binary that's used for rsync is v1.1.0.1+

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21307?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21307: ------------------------------------- Fix Version/s: 4.3.1.Beta2 > Server Adapter: ensure oc binary that's used for rsync is v1.1.0.1+ > ------------------------------------------------------------------- > > Key: JBIDE-21307 > URL: https://issues.jboss.org/browse/JBIDE-21307 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: oc_binary, openshift_v3, server_adapter > Fix For: 4.3.1.Beta2 > > > Because of https://github.com/openshift/origin/issues/6109 publishing with the server adapter (which does a oc rsync behind the scenes) only properly works with oc v1.1.0.1. Versions below require the user to manually > {code} > oc login --server=<server that we publish to> --token=... > {code} > We should check the version and warn if the user is using an oc that is older than this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21307) Server Adapter: ensure oc binary that's used for rsync is v1.1.0.1+

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21307: ---------------------------------------- Summary: Server Adapter: ensure oc binary that's used for rsync is v1.1.0.1+ Key: JBIDE-21307 URL: https://issues.jboss.org/browse/JBIDE-21307 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Andre Dietisheim Because of https://github.com/openshift/origin/issues/6109 publishing with the server adapter (which does a oc rsync behind the scenes) only properly works with oc v1.1.0.1. Versions below require the user to manually {code} oc login --server=<server that we publish to> --token=... {code} We should check the version and warn if the user is using an oc that is older than this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20609: --------------------------------------------- {quote} I thought that this is what we wanted. Typical normal user for us was guy, who wanted to install Fuse or something like that to latest JBDS. But since that stuff was EA, he couldn't find it. Wasn't that the reason which started the fuzz of changing Central? {quote} Yes, but the original proposal for that change to make things like Fuse more visible was the "advertise" feature. This change about making *all* earlyaccess content available by default was a separate suggestion/experiment. {quote}I agree with Michael here. Those "advertisable" connectors are useful when the feature is not available yet. But when it'll be available (as EA or normal connector) tha "advertisable" connector will be replaced by EA/normal one. User workflow will be like: Open central -> see advertisable connector -> "Oh... I have to wait". Next week... Open Central -> see EA connector -> "Finally it's here!" -> install.{quote} so...why not have the advertisable connector be able to ask the user to enable earlyaccess ? That would work fine when we are talking about *new* connecors (like Fuse) and allow us to avoid the issue of having user to see or choose between two options all the time. > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-20764 at 12/11/15 4:24 PM: -------------------------------------------------------------------- https://github.com/openshift/origin/issues/6109 was fixed and works in {code} oc v1.1.0.1 {code} which is available as official release here [oc v1.1.0.1|https://github.com/openshift/origin/releases/tag/v1.1.0.1] was (Author: adietish): https://github.com/openshift/origin/issues/6109 was fixed and works in {code} oc v1.1.0.1 {code} which is not available as official release here [oc v1.1.0.1|https://github.com/openshift/origin/releases/tag/v1.1.0.1] > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: server adapter wizard.bmml, server adapter wizard.png > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-20764 at 12/11/15 4:23 PM: -------------------------------------------------------------------- https://github.com/openshift/origin/issues/6109 was fixed and works in {code} oc v1.1.0.1 {code} which is not available as official release here [oc v1.1.0.1|https://github.com/openshift/origin/releases/tag/v1.1.0.1] was (Author: adietish): https://github.com/openshift/origin/issues/6109 was fixed and works in {code} oc v1.1.0.1 {code} which is not available as official release yet, you have to manually build it for now > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: server adapter wizard.bmml, server adapter wizard.png > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) stop linking skipRequirements and tests.skip to download of requirements

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15332: ---------------------------------------- Summary: stop linking skipRequirements and tests.skip to download of requirements (was: why are skipRequirements controlling download of normal maven dependencies ?) > stop linking skipRequirements and tests.skip to download of requirements > ------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: LATER > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21232) parent pom should never allow skipTests to prevent download of required libraries

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21232?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-21232. --------------------------------------- Resolution: Duplicate Issue okey, so lets close this since the discussion on the other jira has the actual solution outlined. > parent pom should never allow skipTests to prevent download of required libraries > --------------------------------------------------------------------------------- > > Key: JBIDE-21232 > URL: https://issues.jboss.org/browse/JBIDE-21232 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, forge, hibernate, openshift > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > {quote} > {quote}I think at this time obviously we have to change > maven-dependency-plugin declaration > in *parent/pom.xml#build/pluginManagement* to never skip downloading > dependencies, because it is most common use case. After it is done we can > remove unnecessary *<skip>false</skip>* throughout the projects.{quote} > Yes - your conclusion matches mine on the jira and what mistria suggestion for fixes > and with my updates handles. > Can you make it happen ? :) > {quote} > If there are libs for (2) and (3) downloaded from external URL using > download-maven-plugin/maven-download-plugin we should probably move them to > locus.{quote} > Main problem I know is forge, hibernate and openshift afaik. > forge and openshift would not be able to move very fast if we moved their libs for Locus. > Hibernate - we don't actually want/intend to expose the internal apis of hibernate so not > sure if pushing all variations of hibernate into Locus is such a good idea....but it could > be considered. > One thing that might be worth looking for are those bundling mockito or other testing libs > that we might already have put into locus or use from orbit so these are not even relevant anymore.{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21215) IUs missing from snapshot update site while site is being published / outdated metadata needs to be refreshed within Eclipse

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21215?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21215: --------------------------------------------- it is not contradictory. If I do the updates rare (i.e. a few times a month) and *still* is able to have the issue often relatively to how rare I do it (every few months) then that to me indicates that many will bump into this issues across the team/community members. > IUs missing from snapshot update site while site is being published / outdated metadata needs to be refreshed within Eclipse > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21215 > URL: https://issues.jboss.org/browse/JBIDE-21215 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > running updates from: http://download.jboss.org/jbosstools/mars/snapshots/updates/ > I get this error: > {quote} > An error occurred while collecting items to be installed > session context was:(profile=_Users_max_products_eclipse_jee-mars3_Eclipse.app_Contents_Eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.common,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.core,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.el.core,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.jdt.debug,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.jdt.debug.ui,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.resref.core,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.text.xml,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.ui,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.validation,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.foundation.checkup,1.2.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.foundation.core,1.2.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.foundation.ui,1.2.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.cdk.server,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.client,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.common.core,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.common.ui,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.core,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.egit.core,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.egit.ui,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.client,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.core,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.ui,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.ui,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.runtime.core,3.1.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.runtime.ui,3.1.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.stacks.core,1.2.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.usage,2.1.1.Beta1-v20151204-0542-B55 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.cdk.feature,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.express.feature,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.feature,3.1.0.Beta1-v20151205-0342-B106 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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