[JBoss JIRA] (JBIDE-22507) Debugging: cannot debug kitchensink, no breakpoint is being hit
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22507?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22507:
-------------------------------------
[~scabanovich] - that's really not related to the issue here. The launchbar stuff is unrelated. I'll open a new issue to target that.
However, as for breakpoints not being hit: I am able to have breakpoints hit, but not the specific breakpoint that OP is indicating i should set.
MemberListProducer.getMembers() is being hit. Member.getId() is being hit.
MemberResourceRESTService.listAllMembers() is NOT being hit, but others are.
> Debugging: cannot debug kitchensink, no breakpoint is being hit
> ---------------------------------------------------------------
>
> Key: JBIDE-22507
> URL: https://issues.jboss.org/browse/JBIDE-22507
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.4.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: debug, openshift_v3
> Fix For: 4.4.0.Final
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22152) Unknown launch is left in Debug view after deletion of an OS 3 server adapter
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22152:
-----------------------------------
Fix Version/s: 4.4.x
(was: 4.4.0.Final)
> Unknown launch is left in Debug view after deletion of an OS 3 server adapter
> -----------------------------------------------------------------------------
>
> Key: JBIDE-22152
> URL: https://issues.jboss.org/browse/JBIDE-22152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.x
>
> Attachments: AfterDeleteLaunchConfiguration.png, BeforeDeleteLaunchConfiguration.png, launches.png
>
>
> When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them.
> !launches.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18876:
-----------------------------------
Fix Version/s: 4.4.x
(was: 4.4.0.Final)
> Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18876
> URL: https://issues.jboss.org/browse/JBIDE-18876
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.4.x
>
>
> Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task.
> So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus.
> Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-19738) Failed runtime download offers no error message
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19738?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19738:
-----------------------------------
Fix Version/s: 4.4.x
(was: 4.4.0.Final)
> Failed runtime download offers no error message
> -----------------------------------------------
>
> Key: JBIDE-19738
> URL: https://issues.jboss.org/browse/JBIDE-19738
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.3.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.4.x
>
>
> While verifying JBIDE-19571 the runtime download failed and there was no error whatsoever. The download of FSW 6.0 almost started, but after a few seconds on the progress bar an error window showed up for a moment and then disappeared again and the download window was gone, too. After this, there was no error in the error view or the workspace log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21755) Properties: "Eager-er" loading of the project properties
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21755?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21755:
-----------------------------------
Fix Version/s: 4.4.x
(was: 4.4.0.Final)
> Properties: "Eager-er" loading of the project properties
> --------------------------------------------------------
>
> Key: JBIDE-21755
> URL: https://issues.jboss.org/browse/JBIDE-21755
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Minor
> Labels: openshift_v3, properties
> Fix For: 4.4.x
>
>
> Once I logged in the OpenShift Explorer, if I expand the connection and select my project, all tables on the tabbed properties view are empty. I need to expand the project in the OpenShift Explorer view to trigger a loading which then allows for displaying the data in the properties view. This is somehow confusing because the user may think that the OpenShift project is empty.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22385) Show Console Output When Standard Out Changes toggle item is always triggered
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22385?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22385:
-----------------------------------
Fix Version/s: 4.4.x
(was: 4.4.0.Final)
> Show Console Output When Standard Out Changes toggle item is always triggered
> -----------------------------------------------------------------------------
>
> Key: JBIDE-22385
> URL: https://issues.jboss.org/browse/JBIDE-22385
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.x
>
>
> Tool item Show Console Output When Standard Out Changes placed in console view of rsync output is triggerable. If it is not triggered, console view should not be shown forcefully if different console view is opened. At the moment when I am having opened 2 console views, first one with log of an application pod and another one with rsync output for a server adapter, the pod log console view is forced to display rsync output even if the tool item is in the other console view (for rsync) not triggered.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22386) Server Editor: Select different service takes too long
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22386?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22386:
-----------------------------------
Fix Version/s: 4.4.x
(was: 4.4.0.Final)
> Server Editor: Select different service takes too long
> ------------------------------------------------------
>
> Key: JBIDE-22386
> URL: https://issues.jboss.org/browse/JBIDE-22386
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Labels: openshift_v3, server_editor
> Fix For: 4.4.x
>
>
> Trying to select a different service for an OpenShift 3 Server Adapter in Server Editor takes too long. After click on the Select... button it takes ~2-3 seconds to open dialog to select a different service. It would be ok to take it that time if there would be some indication that something is happening, but there is no job while "something" is happening.
> Also clicking on the button multiple times (if it is not responsible, I clicked again and again and again), it takes a bit longer and open multiple dialogs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months