February 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-2923) Verify whether JBDS really needs PDE

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2923?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2923: ------------------------------------- common.model.ui uses PDE internal classes, so it rather not possible to get rid of it entirely. > Verify whether JBDS really needs PDE > ------------------------------------ > > Key: JBDS-2923 > URL: https://issues.jboss.org/browse/JBDS-2923 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build > Reporter: Mickael Istria > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 8.0.0.Beta1 > > > It looks like by default, JBDS embeds PDE and its UI contributions, which are totally off-topic. > We should consider removing PDE. For this we need to check what depends on it first. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16368) Clean useless features from TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16368?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16368: ------------------------------------ I cannot +1 this until we have test-built the new code and verified that the full install of the new JBDS + Central and JBT + Central looks the same / works the same. Will attempt to find time to do this today. > Clean useless features from TP > ------------------------------ > > Key: JBIDE-16368 > URL: https://issues.jboss.org/browse/JBIDE-16368 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.x > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Optional > Fix For: 4.2.0.Beta1 > > > In order to trim some stuff out of our target-platform, we should: > * Install JBDS from installer > * Look at its content in plugins/ and features/ and compare it with content of the TP site. > Everything that is in TP site but not in JBDS is probably worth being removed from TP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16640) Avoid bumping dependencies versions unless it is required

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16640?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-16640: --------------------------------------- I don't see any problems here, JBoss Tools 4.2.0 is for luna release so dependencies were bumped to avoid installation on earlier versions. Do you really want to target two Eclipse releases and double testing and build efforts? It also depends on server module and that means servers module is also must support Kepler. > Avoid bumping dependencies versions unless it is required > --------------------------------------------------------- > > Key: JBIDE-16640 > URL: https://issues.jboss.org/browse/JBIDE-16640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.2.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta1 > > > Problem occurred when trying to install LiveReload 1.2.0.Alpha2 on Kepler: > {code} > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss Tools LiveReload 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.feature.feature.group 1.2.0.Alpha2-v20140207-2102-B6) > Software currently installed: Eclipse Standard/SDK 2.0.1.20130919-0803 (epp.package.standard 2.0.1.20130919-0803) > Only one of the following can be installed at once: > Browser Support 3.4.100.v20130527-1656 (org.eclipse.ui.browser 3.4.100.v20130527-1656) > Browser Support 3.4.200.v20131003-1453 (org.eclipse.ui.browser 3.4.200.v20131003-1453) > Cannot satisfy dependency: > From: Eclipse Standard/SDK 2.0.1.20130919-0803 (epp.package.standard 2.0.1.20130919-0803) > To: org.eclipse.epp.package.standard.feature.feature.group [2.0.1.20130919-0803] > Cannot satisfy dependency: > From: Eclipse Standard/SDK Feature 2.0.1.20130919-0803 (org.eclipse.epp.package.standard.feature.feature.group 2.0.1.20130919-0803) > To: org.eclipse.platform.feature.group [4.3.1.v20130911-1000] > Cannot satisfy dependency: > From: Eclipse Platform 4.3.1.v20130911-1000 (org.eclipse.platform.feature.group 4.3.1.v20130911-1000) > To: org.eclipse.ui.browser [3.4.100.v20130527-1656] > Cannot satisfy dependency: > From: JBoss Tools LiveReload Core 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.core 1.2.0.Alpha2-v20140207-2102-B6) > To: bundle org.eclipse.ui.browser 3.4.200 > Cannot satisfy dependency: > From: JBoss Tools LiveReload 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.feature.feature.group 1.2.0.Alpha2-v20140207-2102-B6) > To: org.jboss.tools.livereload.core [1.2.0.Alpha2-v20140207-2102-B6] > {code} > AFAIR, there was no real need to bump org.eclipse.ui.browser from 3.4.100 to 3.4.200. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2939) Verify swtbot/2.2.0.201401081015 with JBDS 8.0

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2939?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2939: -------------------------------------- SWTBot 2.2.0 is not part of JBDS nor Central. It's just a tool we use for development, but it's not shipped to user. Then, I believe this ticket can be rejected. > Verify swtbot/2.2.0.201401081015 with JBDS 8.0 > ---------------------------------------------- > > Key: JBDS-2939 > URL: https://issues.jboss.org/browse/JBDS-2939 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Jiri Peterka > Fix For: 8.0.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2939) Verify swtbot/2.2.0.201401081015 with JBDS 8.0

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2939?page=com.atlassian.jira.plugin.... ] Mickael Istria edited comment on JBDS-2939 at 2/21/14 12:25 PM: ---------------------------------------------------------------- SWTBot 2.2.0 is not part of JBDS nor Central. It's just a tool we use for development of tests, but it's not shipped to user. Then, I believe this ticket can be rejected. was (Author: mickael_istria): SWTBot 2.2.0 is not part of JBDS nor Central. It's just a tool we use for development, but it's not shipped to user. Then, I believe this ticket can be rejected. > Verify swtbot/2.2.0.201401081015 with JBDS 8.0 > ---------------------------------------------- > > Key: JBDS-2939 > URL: https://issues.jboss.org/browse/JBDS-2939 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Jiri Peterka > Fix For: 8.0.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16614) skipRevisionCheckWhenPublishing is misleading in aggregators

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16614?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-16614. ------------------------------------ Assignee: Mickael Istria Resolution: Done Chaged with https://github.com/jbdevstudio/jbdevstudio-ci/commit/49469b0c4a2aed31cdbc... > skipRevisionCheckWhenPublishing is misleading in aggregators > ------------------------------------------------------------ > > Key: JBIDE-16614 > URL: https://issues.jboss.org/browse/JBIDE-16614 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Beta1 > > > As the *aggregate* and devstudio-product_* are only run for good reasons (change in a component, or change in aggregation repository - category.xml and other, there is no reason why using the skipRevisionCheckWhenPublishing, which is furthermore a bit error prone and misleading (some manual builds are ignored whereas there has been changes). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16631) After stopping/restarting F2 the inputstream is closed

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16631?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-16631. ------------------------------- Resolution: Done > After stopping/restarting F2 the inputstream is closed > ------------------------------------------------------ > > Key: JBIDE-16631 > URL: https://issues.jboss.org/browse/JBIDE-16631 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.2.0.Beta1 > > > This results in an IOException: > java.io.IOException: Pipe closed > at java.io.PipedInputStream.checkStateForReceive(PipedInputStream.java:261) > at java.io.PipedInputStream.receive(PipedInputStream.java:227) > at java.io.PipedOutputStream.write(PipedOutputStream.java:149) > at java.io.OutputStream.write(OutputStream.java:75) > at org.jboss.tools.aesh.core.io.AeshInputStream.append(AeshInputStream.java:24) > at org.jboss.tools.aesh.core.console.AeshConsole.sendInput(AeshConsole.java:132) > at org.jboss.tools.aesh.ui.view.AeshTextViewer.handleVerifyEvent(AeshTextViewer.java:149) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-15394) Add arquillian.xml GUI editor to jbosstools-arquillian

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15394?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15394: --------------------------------------------- snjezana - if you got a branch with your sapphire version why not share that on github ? then [~kuniim] and others can compare/see it ? > Add arquillian.xml GUI editor to jbosstools-arquillian > ------------------------------------------------------ > > Key: JBIDE-15394 > URL: https://issues.jboss.org/browse/JBIDE-15394 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: testing-tools > Reporter: Masao Kunii > Assignee: Snjezana Peco > Priority: Optional > Fix For: 4.2.0.Beta1 > > > The arquillian.xml editor is an editor to edit arquillian.xml easily and visually. This is a feature for jbosstools-arquillian(https://github.com/jbosstools/jbosstools-arquillian) and enables to: > - Edit containers, container groups, extensions, protocols and engines > - Modify pom.xml automatically corresponding settings in arquillian.xml > - Register favorite container/container groups from Eclipse preferences -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-9212) Consider introducing Profiles of AS Server adapteres

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9212?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9212: -------------------------------------------- Rob - could you please add some comment/steps to use/screenshot or similar on what you made since the last comment before you said "this is done" was "this is poorly defined" - so lets fix that before resolving it fully ;) > Consider introducing Profiles of AS Server adapteres > ---------------------------------------------------- > > Key: JBIDE-9212 > URL: https://issues.jboss.org/browse/JBIDE-9212 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta1 > > > With all the different combinations of server behaviors and pollers dependent if you are runnig locally, remotely, openshift express or openshift flex it becomes hard to configure/tweak. > Idea is to introduce the notion of profiles, provide a set of default ones users can apply in Server Wizard or even in the server editor and allow them to create new ones based on existing ones. > These profiles would cover: > ports, start/stop behavior, pollers, deployments and launch setup. (more?) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-9212) Consider introducing Profiles of AS Server adapteres

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9212?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-9212: --------------------------------------- Labels: new_and_noteworthy (was: ) > Consider introducing Profiles of AS Server adapteres > ---------------------------------------------------- > > Key: JBIDE-9212 > URL: https://issues.jboss.org/browse/JBIDE-9212 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta1 > > > With all the different combinations of server behaviors and pollers dependent if you are runnig locally, remotely, openshift express or openshift flex it becomes hard to configure/tweak. > Idea is to introduce the notion of profiles, provide a set of default ones users can apply in Server Wizard or even in the server editor and allow them to create new ones based on existing ones. > These profiles would cover: > ports, start/stop behavior, pollers, deployments and launch setup. (more?) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

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 February 2014