January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16290) Fixing SWT issues in Luna

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16290: ------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.x) > Fixing SWT issues in Luna > ------------------------- > > Key: JBIDE-16290 > URL: https://issues.jboss.org/browse/JBIDE-16290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Mickael Istria > Assignee: Snjezana Peco > Fix For: 4.2.0.Alpha2 > > Attachments: Java - Eclipse _001.png, luna-crashing-on-outcomplete.ogv > > > This ticket is meant to list the bugs related to GTK3 affecting JBDS: > * JBIDE-16280 VPE/XulRunner crashes workbench > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581 > * Central tests uses SWT_GTK3=0 in its pom. > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=425123 > We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA. > On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16290) Fixing SWT issues in Luna

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-16290: ----------------------------------- Description: This ticket is meant to list the bugs related to GTK3 affecting JBDS: * JBIDE-16280 VPE/XulRunner crashes workbench * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581 * Central tests uses SWT_GTK3=0 in its pom. * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 * https://bugs.eclipse.org/bugs/show_bug.cgi?id=425123 We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA. On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future. was: This ticket is meant to list the bugs related to GTK3 affecting JBDS: * JBIDE-16280 VPE/XulRunner crashes workbench * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581 * Central tests uses SWT_GTK3=0 in its pom. * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA. On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future. > Fixing SWT issues in Luna > ------------------------- > > Key: JBIDE-16290 > URL: https://issues.jboss.org/browse/JBIDE-16290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Mickael Istria > Assignee: Snjezana Peco > Fix For: 4.2.x > > Attachments: Java - Eclipse _001.png, luna-crashing-on-outcomplete.ogv > > > This ticket is meant to list the bugs related to GTK3 affecting JBDS: > * JBIDE-16280 VPE/XulRunner crashes workbench > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581 > * Central tests uses SWT_GTK3=0 in its pom. > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=425123 > We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA. > On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16314) Avoid loading xulrunner on Linux

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16314?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-16314. ---------------------------------- Resolution: Done Closed as a DUP JBIDE-16280 > Avoid loading xulrunner on Linux > -------------------------------- > > Key: JBIDE-16314 > URL: https://issues.jboss.org/browse/JBIDE-16314 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: xulrunner > Reporter: Mickael Istria > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.Alpha2 > > > In order to avoid crash described in JBIDE-16280, we should avoid loading (or providing)the xulrunner binaries we ship on Windows until they are compatible with GTK3. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16314) Avoid loading xulrunner on Linux

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16314?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-16314: ----------------------------------- Fix Version/s: (was: 4.2.0.Alpha2) > Avoid loading xulrunner on Linux > -------------------------------- > > Key: JBIDE-16314 > URL: https://issues.jboss.org/browse/JBIDE-16314 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: xulrunner > Reporter: Mickael Istria > Assignee: Konstantin Marmalyukov > > In order to avoid crash described in JBIDE-16280, we should avoid loading (or providing)the xulrunner binaries we ship on Windows until they are compatible with GTK3. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16314) Avoid loading xulrunner on Linux

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16314?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-16314. ---------------------------------- Resolution: Duplicate Issue > Avoid loading xulrunner on Linux > -------------------------------- > > Key: JBIDE-16314 > URL: https://issues.jboss.org/browse/JBIDE-16314 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: xulrunner > Reporter: Mickael Istria > Assignee: Konstantin Marmalyukov > > In order to avoid crash described in JBIDE-16280, we should avoid loading (or providing)the xulrunner binaries we ship on Windows until they are compatible with GTK3. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-447) Explain how to configure SSL options for connecting to Enterprise Servers.

by Eric Rich (JIRA)

Eric Rich created TOOLSDOC-447: ---------------------------------- Summary: Explain how to configure SSL options for connecting to Enterprise Servers. Key: TOOLSDOC-447 URL: https://issues.jboss.org/browse/TOOLSDOC-447 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: User Guide Environment: Build Name: 22443, User Guide-7.1 Build Date: 11-12-2013 15:10:49 Topic ID: 25166-566980 [Latest] Reporter: Eric Rich Assignee: Michelle Murray Priority: Minor Title: Customizing Overview Describe the issue: It would be good to explain configuration options for connecting to multiple or different Enterprise Servers. Also explaining how to manage your SSL certificates or update them for connection to Enterprise Servers or Online would be helpful. Suggestions for improvement: Additional information: -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16309: ---------------------------------------- * Some properties could be used for factorization (jbosstools-site-base) * Communicate with QE and JBTIS to make sure they don't use composite * Get rid of the tests/ site (which probably won't be useful any more) > Move inter-JBT dependencies to component poms > --------------------------------------------- > > Key: JBIDE-16309 > URL: https://issues.jboss.org/browse/JBIDE-16309 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > > It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build. > The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous. > So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309 > You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... -- 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, 3 months

1
0
0 / 0

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

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-16368: -------------------------------------- Summary: 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 Fix For: 4.2.0.Alpha1 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2515) JBDS70_0011: [Commit] (Dev) (P3) Scan ~/jboss-runtimes automatically

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2515?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2515: ------------------------------------------- Your explanation is correct for the current behavior. The idea with this jira is simply to add ${user.home}/jboss-runtimes to the list of paths to scan automatically. This would most useful if our other installers would install them self into ~/jboss-runtimes by default too. But main reason is just to have a stable default location trainers and users can use to avoid having to configure their runtime directory on every new eclipse workspace. > JBDS70_0011: [Commit] (Dev) (P3) Scan ~/jboss-runtimes automatically > -------------------------------------------------------------------- > > Key: JBDS-2515 > URL: https://issues.jboss.org/browse/JBDS-2515 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Max Rydahl Andersen > Priority: Minor > > Usecase is to not have to setup runtimes every time you create a new workspace. Useful for demos and training sessions and those using many runtimes (e.g. EAP 5.0.1, EAP 6.0.0, EAP 6.0.1, SOA-P 5.x.y, etc) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16367) Drop sourceforge.net archiving?

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-16367: -------------------------------------- Summary: Drop sourceforge.net archiving? Key: JBIDE-16367 URL: https://issues.jboss.org/browse/JBIDE-16367 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: build Reporter: Mickael Istria Fix For: 4.2.x We currently do archive stuff on sf.net. This adds an extra piece in build process and infrastructure, which does not seem to provide additional value upon keeping binaries on download.jboss.org. I'd be in favour of abandoning sf.net to find something which is more comfortable for us to use (download.jboss.org is IMO the best candidate). -- 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, 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 2014