July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3112) Karaf cannot be started in debug

by Jason Shepherd (JIRA)

[ https://issues.jboss.org/browse/JBDS-3112?page=com.atlassian.jira.plugin.... ] Jason Shepherd commented on JBDS-3112: -------------------------------------- Fixed by > Karaf cannot be started in debug > -------------------------------- > > Key: JBDS-3112 > URL: https://issues.jboss.org/browse/JBDS-3112 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: integration > Affects Versions: 7.1.1.GA > Environment: JBoss Fuse Server Extension Feature 7.2.1.v20140613-0455-H79-Final org.fusesource.ide.server.extensions.feature.feature.group JBoss by Red Hat > Reporter: Jason Shepherd > Priority: Minor > > Cannot start a Fuse server in DEBUG mode, see: > FUSETOOL-1132 > Please update JBoss Fuse Server Extension Feature to include version 7.3 which is now fixed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3112) Karaf cannot be started in debug

by Jason Shepherd (JIRA)

Jason Shepherd created JBDS-3112: ------------------------------------ Summary: Karaf cannot be started in debug Key: JBDS-3112 URL: https://issues.jboss.org/browse/JBDS-3112 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: integration Affects Versions: 7.1.1.GA Environment: JBoss Fuse Server Extension Feature 7.2.1.v20140613-0455-H79-Final org.fusesource.ide.server.extensions.feature.feature.group JBoss by Red Hat Reporter: Jason Shepherd Priority: Minor Cannot start a Fuse server in DEBUG mode, see: FUSETOOL-1132 Please update JBoss Fuse Server Extension Feature to include version 7.3 which is now fixed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17989) keyword used for plugin tracking is missing majority of times on GA

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17989?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17989: --------------------------------------------- Usage should not require features to be branded. Very weird for me why this seem to work "sometimes" according to stats. > keyword used for plugin tracking is missing majority of times on GA > ------------------------------------------------------------------- > > Key: JBIDE-17989 > URL: https://issues.jboss.org/browse/JBIDE-17989 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.2.0.CR1 > > > looking at tracking numbers i'm seeing more and more requests where the keywords are not making it into the result. > Meaning we can't see how many have installed the various plugins. > What is weird *some* do and others do not have it. > Need to track down the reason for that being missed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17996) Server Runtime Environment wizard says "C:standalone" even if corrected

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17996?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17996: ------------------------------------- The display is taking two IPaths and performing the following: path1.removeFirstSegments(path2.segmentCount()).toString(); This is insufficient, because the toString() will also include the device, in this case c: The proper solution is to do a substring. Pushed to cr1 > Server Runtime Environment wizard says "C:standalone" even if corrected > ----------------------------------------------------------------------- > > Key: JBIDE-17996 > URL: https://issues.jboss.org/browse/JBIDE-17996 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Environment: Eclipse Luna > JBossAS Tools 3.0.0.Beta3-v20140718-1832-B70 > Windows 7 x64 > Java 8u11 > Reporter: Karl Pietrzak > Fix For: 4.2.0.CR1 > > > h3. What > For some reason, the Server Environment Runtime wizard for Wildfly (probably JBoss too) auto-detects the "Configuration Base Directory" as "C:standalone". > Even if I try to overwrite it to just "standalone", it overwrites it to "C:standalone". > h3. Screencast > http://screencast.com/t/1wC8B2loj4H > h3. Found Bug location? > My guess is {{org.jboss.ide.eclipse.as.core.util.ServerUtil::makeRelative}}, but I'm not sure why. > At first I thought it had something to do with the fact that I originally put my Wildfly install into {{c:\program files}} (note the space), but then I moved it to a location that does not have spaces and the same thing occurred. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17996) Server Runtime Environment wizard says "C:standalone" even if corrected

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17996?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17996. --------------------------------- Assignee: Rob Stryker Resolution: Done pushed > Server Runtime Environment wizard says "C:standalone" even if corrected > ----------------------------------------------------------------------- > > Key: JBIDE-17996 > URL: https://issues.jboss.org/browse/JBIDE-17996 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Environment: Eclipse Luna > JBossAS Tools 3.0.0.Beta3-v20140718-1832-B70 > Windows 7 x64 > Java 8u11 > Reporter: Karl Pietrzak > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > h3. What > For some reason, the Server Environment Runtime wizard for Wildfly (probably JBoss too) auto-detects the "Configuration Base Directory" as "C:standalone". > Even if I try to overwrite it to just "standalone", it overwrites it to "C:standalone". > h3. Screencast > http://screencast.com/t/1wC8B2loj4H > h3. Found Bug location? > My guess is {{org.jboss.ide.eclipse.as.core.util.ServerUtil::makeRelative}}, but I'm not sure why. > At first I thought it had something to do with the fact that I originally put my Wildfly install into {{c:\program files}} (note the space), but then I moved it to a location that does not have spaces and the same thing occurred. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17996) Server Runtime Environment wizard says "C:standalone" even if corrected

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17996?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17996: -------------------------------- Fix Version/s: 4.2.0.CR1 > Server Runtime Environment wizard says "C:standalone" even if corrected > ----------------------------------------------------------------------- > > Key: JBIDE-17996 > URL: https://issues.jboss.org/browse/JBIDE-17996 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Environment: Eclipse Luna > JBossAS Tools 3.0.0.Beta3-v20140718-1832-B70 > Windows 7 x64 > Java 8u11 > Reporter: Karl Pietrzak > Fix For: 4.2.0.CR1 > > > h3. What > For some reason, the Server Environment Runtime wizard for Wildfly (probably JBoss too) auto-detects the "Configuration Base Directory" as "C:standalone". > Even if I try to overwrite it to just "standalone", it overwrites it to "C:standalone". > h3. Screencast > http://screencast.com/t/1wC8B2loj4H > h3. Found Bug location? > My guess is {{org.jboss.ide.eclipse.as.core.util.ServerUtil::makeRelative}}, but I'm not sure why. > At first I thought it had something to do with the fact that I originally put my Wildfly install into {{c:\program files}} (note the space), but then I moved it to a location that does not have spaces and the same thing occurred. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2740) Support multiple namespaces in OpenShift

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-2740?page=com.atlassian.jira.plugin.... ] Marián Labuda closed JBDS-2740. ------------------------------- > Support multiple namespaces in OpenShift > ---------------------------------------- > > Key: JBDS-2740 > URL: https://issues.jboss.org/browse/JBDS-2740 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Andy Goldstein > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift > Fix For: 7.1.0.Beta1 > > Attachments: namespace.png > > > OpenShift will soon add support for a user to have access to multiple namespaces. This includes: > - a user creates and owns multiple namespaces > - a user has permission to work with a domain owned by another user (with differing permission levels) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2777) Support Team Management operations in openshift UI

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-2777?page=com.atlassian.jira.plugin.... ] Marián Labuda closed JBDS-2777. ------------------------------- Verified in JBDS 8.0.0.Beta3c. > Support Team Management operations in openshift UI > -------------------------------------------------- > > Key: JBDS-2777 > URL: https://issues.jboss.org/browse/JBDS-2777 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Optional > Labels: domain_wizard, new_and_noteworthy > Fix For: 8.0.0.Beta3 > > Attachments: application-wizard-manage-domains.png, could-not-find-webconsole.png, domain-wizard-edit-members.png, edit-domain-link-validated.png, edit-domain-members.png, explorer-edit-domain.png, explorer-manage-domains.png > > > OpenShift is providing a team API where teams may be created. Users or groups may get assigned to a team. There's always only 1 group per team and there is no finer-grained role based acl. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2750) cannot log into OpenShift (even though credentials are valid)

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-2750?page=com.atlassian.jira.plugin.... ] Marián Labuda closed JBDS-2750. ------------------------------- > cannot log into OpenShift (even though credentials are valid) > ------------------------------------------------------------- > > Key: JBDS-2750 > URL: https://issues.jboss.org/browse/JBDS-2750 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 6.0.x > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Attachments: cannot-login.png > > > You cannot log into OpenShift Online using JBDS6 (JBDS7 and OpenShift Enterprise are not affected) any more. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-9900) if validating credentials timeouts, you get invalid credentials reported

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9900?page=com.atlassian.jira.plugin... ] Marián Labuda closed JBIDE-9900. -------------------------------- > if validating credentials timeouts, you get invalid credentials reported > ------------------------------------------------------------------------ > > Key: JBIDE-9900 > URL: https://issues.jboss.org/browse/JBIDE-9900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.M4 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 3.3.x, 4.0.x > > Attachments: credentials-timeout.png > > > #ASSERT: have a valid account in openshift express > #EXEC: open the openshift wizard (new wizard->Other->Openshift/Openshift Express Application) > #EXEC: use a valid username and password > #EXEC: unplug your net connection > #EXEC: validate the credentials > Result: > You get invalid credentials reported > Expected: > Yuu get an error dialog that tells you that the validation timeouted. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014