July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17930) Expose Forge APIs to downstream Plugins

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17930?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-17930. ------------------------------ > Expose Forge APIs to downstream Plugins > --------------------------------------- > > Key: JBIDE-17930 > URL: https://issues.jboss.org/browse/JBIDE-17930 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.Beta2 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.Beta3 > > > when using the forge2.runtime there were some classes that were not being exposed that the client needed access to. Exposing all of the wrapped forge packages via the forge2.runtime plugin fixes this issue for clients. Full discussion here: > https://github.com/jbosstools/jbosstools-forge/pull/78#issuecomment-49366663 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Karl Pietrzak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17960?page=com.atlassian.jira.plugi... ] Karl Pietrzak commented on JBIDE-17960: --------------------------------------- Maybe an even better solution is to bring up the "Runtime Environment" section for this specific error, or Eclipse's Execution Environments section? > "The specified JRE installation does not exist" > ----------------------------------------------- > > Key: JBIDE-17960 > URL: https://issues.jboss.org/browse/JBIDE-17960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 3.0.0.GA > Reporter: Karl Pietrzak > Priority: Minor > Attachments: jbossastools-bad.jre.swf > > > h3. What > If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. > h3. Screencast > !jbossastools-bad.jre.swf! > If the above embedded SWF doesn't work for you, you can watch it at http://screencast.com/t/bytN53lp -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Karl Pietrzak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17960?page=com.atlassian.jira.plugi... ] Karl Pietrzak updated JBIDE-17960: ---------------------------------- Description: h3. What If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. h3. Screencast !jbossastools-bad.jre.swf! If the above embedded SWF doesn't work for you, you can watch it at http://screencast.com/t/bytN53lp was: h3. What If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. h3. Screencast !jbossastools-bad.jre.swf! > "The specified JRE installation does not exist" > ----------------------------------------------- > > Key: JBIDE-17960 > URL: https://issues.jboss.org/browse/JBIDE-17960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 3.0.0.GA > Reporter: Karl Pietrzak > Priority: Minor > Attachments: jbossastools-bad.jre.swf > > > h3. What > If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. > h3. Screencast > !jbossastools-bad.jre.swf! > If the above embedded SWF doesn't work for you, you can watch it at http://screencast.com/t/bytN53lp -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17959) Cannot cancel editing server profile

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17959?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17959. --------------------------------- Assignee: Rob Stryker Resolution: Done Pushed to cr1. Not only should 'cancel' be active, but also, you should never see a change to the working copy if you press cancel. The server editor should remain clean (not dirty), and the working copy should not be contaminated. I would suggest doing something like the following to test: 1) Open server editor 2) open behavior / profile hyperlink 3) change all settings you can think of 4) cancel 5) Verify server does not appear dirty Then I'd try this: 1) Open server editor 2) Change a setting (like poller) 3) open behavior / profile hyperlink 4) change all settings you can think of 5) cancel 6) Save server 7) close and re-open server 8) Verify that settings you changed in the wizard dialog did not get saved > Cannot cancel editing server profile > ------------------------------------ > > Key: JBIDE-17959 > URL: https://issues.jboss.org/browse/JBIDE-17959 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > Self-explanatory topic. Cannot cancel the wizard when you edit profile. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17936) Remote deploy only server has wrong temp dir and unreadable entries in server editor

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17936?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-17936: --------------------------------------- [~rob.stryker] for all remote servers are just Deploy Only for now? Do you want another jira? > Remote deploy only server has wrong temp dir and unreadable entries in server editor > ------------------------------------------------------------------------------------ > > Key: JBIDE-17936 > URL: https://issues.jboss.org/browse/JBIDE-17936 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.Beta3b B193 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > Attachments: deploy-only-crop.png, deploy-only-full.png, JBIDE-17936.png > > > This is a follow up of JBIDE-17867. That one is now fixed. I believe this is actually a regression of that one: > When you create a remote deploy only server and set up a deploy and temp dir and then open the server editor, you will notice two problems: > 1. In the Server behavior section, the UI for the deploy and temp directories is unreadable unless your window is very big. > !deploy-only-crop.png! > See also the full JBDS window screenshot - it shows that it's not really that small. And I rarely have bigger window and never saw anything like this before. > 2. In the Deployment page, you can see that the deploy and temp dirs are the same - both use the deploy dir. I set up two distinct dirs there. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Karl Pietrzak (JIRA)

Karl Pietrzak created JBIDE-17960: ------------------------------------- Summary: "The specified JRE installation does not exist" Key: JBIDE-17960 URL: https://issues.jboss.org/browse/JBIDE-17960 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.GA Reporter: Karl Pietrzak Priority: Minor Attachments: jbossastools-bad.jre.swf h3. What If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. h3. Screencast !jbossastools-bad.jre.swf! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Karl Pietrzak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17960?page=com.atlassian.jira.plugi... ] Karl Pietrzak updated JBIDE-17960: ---------------------------------- Attachment: jbossastools-bad.jre.swf > "The specified JRE installation does not exist" > ----------------------------------------------- > > Key: JBIDE-17960 > URL: https://issues.jboss.org/browse/JBIDE-17960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 3.0.0.GA > Reporter: Karl Pietrzak > Priority: Minor > Attachments: jbossastools-bad.jre.swf > > > h3. What > If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. > h3. Screencast > !jbossastools-bad.jre.swf! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17936) Remote deploy only server has wrong temp dir and unreadable entries in server editor

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17936?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17936. --------------------------------- Resolution: Done These unused UI elements have been removed. > Remote deploy only server has wrong temp dir and unreadable entries in server editor > ------------------------------------------------------------------------------------ > > Key: JBIDE-17936 > URL: https://issues.jboss.org/browse/JBIDE-17936 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.Beta3b B193 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > Attachments: deploy-only-crop.png, deploy-only-full.png, JBIDE-17936.png > > > This is a follow up of JBIDE-17867. That one is now fixed. I believe this is actually a regression of that one: > When you create a remote deploy only server and set up a deploy and temp dir and then open the server editor, you will notice two problems: > 1. In the Server behavior section, the UI for the deploy and temp directories is unreadable unless your window is very big. > !deploy-only-crop.png! > See also the full JBDS window screenshot - it shows that it's not really that small. And I rarely have bigger window and never saw anything like this before. > 2. In the Deployment page, you can see that the deploy and temp dirs are the same - both use the deploy dir. I set up two distinct dirs there. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17959) Cannot cancel editing server profile

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17959?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17959: -------------------------------- Fix Version/s: 4.2.0.CR1 > Cannot cancel editing server profile > ------------------------------------ > > Key: JBIDE-17959 > URL: https://issues.jboss.org/browse/JBIDE-17959 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Rob Stryker > Fix For: 4.2.0.CR1 > > > Self-explanatory topic. Cannot cancel the wizard when you edit profile. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17536) JBoss Tools Core Nightly update site fails to install if a new build is published during install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17536?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17536: ------------------------------------ Based on lengthy debate in #jbosstools & http://ether-man.rhcloud.com/p/updatesitelayout here's the new plan: {quote} /updates/nightly/luna -> point to composite of a TBD amount of master builds (composited since it will often update and if not composited installs will often fail) content is here: http://download.jboss.org/jbosstools/builds/nightly/core/master/ (perfect fit) /updates/staging/luna -> point to latest respin build(s) at staging/<specific build>) *NEW* - another manual (I was expecting this could be automated) step when publishing to QE need a new "magicpublish" script to create content for the composite site {quote} > JBoss Tools Core Nightly update site fails to install if a new build is published during install > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-17536 > URL: https://issues.jboss.org/browse/JBIDE-17536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > When you install JBT nightly from http://download.jboss.org/jbosstools/updates/nightly/core/master/ into Eclipse and during the build, a new nightly build replaces the old one, you can get a failure like this: > {code}http://download.jboss.org/jbosstools/updates/nightly/core/master/features/org.jboss.tools.wtp.runtimes.tomcat.feature_1.1.0.Beta3-v20140603-0027-B526.jar cannot be found{code} > This is because during your install, the old jars were replaced with the new jars, i.e. different filenames. > I'm not sure if it's something we really need to fix, it's open for discussion. But it happened to me yesterday and it wasn't the first time, so I'm throwing it on the table. > Nick offered this alternative: > install from a specific build folder instead of the "latest nightly" > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > But obviously that's just a workaround, not a real solution. > One way this could be achieved is this: plugins/ and features/ would contain jars from both the latest and previous builds. This way if you start installing (latest=build N) and in the middle of your installation there is a new build (N+1), there would still be jars for both N and N+1 builds. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 July 2014