January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19036) Cleanup Central TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19036?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19036: ---------------------------------------- You're right. I saw the forge.m2e feature in my JBDS, but this was after I made tests of installation from Central. At least, removing the org.jboss.tools.forge.feature would save 35MB... > Cleanup Central TP > ------------------ > > Key: JBIDE-19036 > URL: https://issues.jboss.org/browse/JBIDE-19036 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: discovery > Affects Versions: 4.2.1.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > It seems that the jbtcentral targetplatform contains some features that are already included in JBT and JBDS. Namely: > * org.jboss.tools.forge.feature.feature.group > * org.jboss.tools.forge.m2e.feature.feature.group > So those features should probably trimmed out of the target platform. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12532) Open command doesn't open URLs in JBoss Tools

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12532?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-12532: ----------------------------------------- I reproduced this issue only when the {{Internal Web Browser}} is selected in Eclipse preferences (Window -> General / Web Browsers). Can you confirm this error does not happen when the external web browser is selected ? > Open command doesn't open URLs in JBoss Tools > --------------------------------------------- > > Key: JBIDE-12532 > URL: https://issues.jboss.org/browse/JBIDE-12532 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 3.3.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 4.2.2.Final > > > As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. > To reproduce, type the following in the Forge console: > {code} > open http://forge.jboss.org > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3315) 8.0.2 B378 does not contain updated Forge (possibly more)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3315?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3315: -------------------------------------- The reason seems simply to be that JBDS build did run too early, before the build of JBT that included newer forge. I remember I did some checks to avoid that situation, and I concluded everything was ok. Obviously, something was wrong, either I didn't check the right thing, or I didn't check correctly. Anyway, rebuild of JBDS 8.0.2 in progress. > 8.0.2 B378 does not contain updated Forge (possibly more) > --------------------------------------------------------- > > Key: JBDS-3315 > URL: https://issues.jboss.org/browse/JBDS-3315 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.2.GA > Reporter: Martin Malina > Assignee: Mickael Istria > Priority: Blocker > Fix For: 8.0.2.GA > > > I wanted to check the differences between JBDS 8.0.1 and 8.0.2 and was surprised that there is no change in Forge plugins - all of the time stamps are from 2014, exactly the same as was in 8.0.1. > You can see it in the online repo here: > http://www.qa.jboss.com/binaries/RHDS/updates/development/8.0.2.GA-update... > {code} > org.jboss.tools.forge.core_1.3.1.Final-v20141209-0343-B80.jar > org.jboss.tools.forge.m2e_1.1.1.Final-v20141209-0343-B80.jar > org.jboss.tools.forge.runtime.ext_1.3.1.Final-v20141209-0343-B80 > org.jboss.tools.forge.runtime_1.4.144.Final-v20141209-0343-B80 > org.jboss.tools.forge.ui.notifications_1.3.1.Final-v20141209-0343-B80.jar > org.jboss.tools.forge.ui_1.3.1.Final-v20141209-0343-B80.jar > org.jboss.tools.forge2.runtime_2.12.3.Final-v20141209-0343-B80 > {code} > You can see that it's ok in JBoss Tools 4.2.2.Final: > http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19038) Arquillian should not be in JBT EA catalog

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19038?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19038: ---------------------------------- Assignee: Nick Boldt > Arquillian should not be in JBT EA catalog > ------------------------------------------ > > Key: JBIDE-19038 > URL: https://issues.jboss.org/browse/JBIDE-19038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.2.Final > Reporter: Radim Hopp > Assignee: Nick Boldt > > In JBIDE-18995 Arquillian was removed from EA (by removing it from jbosstools-earlyaccess.properties), but on Software/Update page it is still displayed under EA features. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3314) Include JGit security patch

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3314?page=com.atlassian.jira.plugin.... ] Martin Malina edited comment on JBDS-3314 at 1/14/15 11:46 AM: --------------------------------------------------------------- I just checked this running JBDS 8.0.1 with the staging update site configured: https://devstudio.redhat.com/updates/8.0-staging/ This site contains JBDS 8.0.2. I was then prompted to update new software. In the update dialog, I could then see the updated jgit and egit in the details (timestamped 20141218). I wanted to post a screenshot, but unfortunately now I clicked Install and now it's too late to take a screenshot :( I will need to check again with the new build of JBDS 8.0.2.GA (the current build does not contain all the expected updates - see JBDS-3315 ). Also, I will check for JBoss Tools, too. was (Author: mmalina): I just checked this running JBDS 8.0.1 with the staging update site configured: https://devstudio.redhat.com/updates/8.0-staging/ This site contains JBDS 8.0.2. I was then prompted to update new software. In the update dialog, I could then see the updated jgit and egit in the details (timestamped 20141218). I wanted to post a screenshot, but unfortunately now I clicked Install and now it's too late to take a screenshot :( > Include JGit security patch > --------------------------- > > Key: JBDS-3314 > URL: https://issues.jboss.org/browse/JBDS-3314 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 8.0.1.GA > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 8.0.2.GA > > > A vulnerability was announced in most Git clients (including JGit). > JGit has provided a new version that fixes this vulnerability, and this has been included in a rebuild of Luna SR1. We should include it. > https://mmilinkov.wordpress.com/2015/01/12/eclipse-ships-luna-sr1a-git-se... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3314) Include JGit security patch

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3314?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3314: ------------------------------------- I just checked this running JBDS 8.0.1 with the staging update site configured: https://devstudio.redhat.com/updates/8.0-staging/ This site contains JBDS 8.0.2. I was then prompted to update new software. In the update dialog, I could then see the updated jgit and egit in the details (timestamped 20141218). I wanted to post a screenshot, but unfortunately now I clicked Install and now it's too late to take a screenshot :( > Include JGit security patch > --------------------------- > > Key: JBDS-3314 > URL: https://issues.jboss.org/browse/JBDS-3314 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 8.0.1.GA > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 8.0.2.GA > > > A vulnerability was announced in most Git clients (including JGit). > JGit has provided a new version that fixes this vulnerability, and this has been included in a rebuild of Luna SR1. We should include it. > https://mmilinkov.wordpress.com/2015/01/12/eclipse-ships-luna-sr1a-git-se... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19039) Window size shouldn't be computed proportionally to 'display' size but rather aligned with the components

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19039?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-19039: ------------------------------- Description: Wizard window size shouldn't be computed proportionally to 'display' size. But instead it should be aligned with the components that are in the wizard. You can see on the screenshots how it looks when you have your monitor in portrait orientation. was:Wizard window size shouldn't be computed proportionally to 'display' size. But instead it should be aligned with the components that are in the wizard. > Window size shouldn't be computed proportionally to 'display' size but rather aligned with the components > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19039 > URL: https://issues.jboss.org/browse/JBIDE-19039 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.2.Final > Reporter: Pavol Srna > Attachments: forge-scaffold-window.png, other-wizard.png > > > Wizard window size shouldn't be computed proportionally to 'display' size. But instead it should be aligned with the components that are in the wizard. > You can see on the screenshots how it looks when you have your monitor in portrait orientation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19039) Window size shouldn't be computed proportionally to 'display' size but rather aligned with the components

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19039?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-19039: ------------------------------- Fix Version/s: (was: 4.2.2.Final) > Window size shouldn't be computed proportionally to 'display' size but rather aligned with the components > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19039 > URL: https://issues.jboss.org/browse/JBIDE-19039 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.2.Final > Reporter: Pavol Srna > Attachments: forge-scaffold-window.png, other-wizard.png > > > Wizard window size shouldn't be computed proportionally to 'display' size. But instead it should be aligned with the components that are in the wizard. > You can see on the screenshots how it looks when you have your monitor in portrait orientation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19039) Window size shouldn't be computed proportionally to 'display' size but rather aligned with the components

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19039?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-19039: ------------------------------- Description: Wizard window size shouldn't be computed proportionally to 'display' size. But instead it should be aligned with the components that are in the wizard. > Window size shouldn't be computed proportionally to 'display' size but rather aligned with the components > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19039 > URL: https://issues.jboss.org/browse/JBIDE-19039 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.2.Final > Reporter: Pavol Srna > Fix For: 4.2.2.Final > > Attachments: forge-scaffold-window.png, other-wizard.png > > > Wizard window size shouldn't be computed proportionally to 'display' size. But instead it should be aligned with the components that are in the wizard. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19039) Window size shouldn't be computed proportionally to 'display' size but rather aligned with the components

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19039?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-19039: ------------------------------- Summary: Window size shouldn't be computed proportionally to 'display' size but rather aligned with the components (was: Window size shouldn't be computed proportionally to display size but rather aligned with the components) > Window size shouldn't be computed proportionally to 'display' size but rather aligned with the components > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19039 > URL: https://issues.jboss.org/browse/JBIDE-19039 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.2.Final > Reporter: Pavol Srna > Fix For: 4.2.2.Final > > Attachments: forge-scaffold-window.png, other-wizard.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 January 2015