October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2250) Provide a "JBoss" CSS theme in JBT and enable it by default in JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2250?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2250: ------------------------------------------- I prefer a working UI over a pretty but broken UI :) eclipses theming just aren't good enough to make it clean. At least none of the themes i've seen have been an improvement and had glitches because not all ui elements are themable. > Provide a "JBoss" CSS theme in JBT and enable it by default in JBDS > ------------------------------------------------------------------- > > Key: JBDS-2250 > URL: https://issues.jboss.org/browse/JBDS-2250 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ui/branding > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Optional > Fix For: 6.0.0.Alpha2 > > Attachments: failed-to-get-bundle-net.jeeeeyul.eclipse.themes.png, snapshot9.png > > > We could leverage Eclipse 4 CSS styling and theming abilities to provide a "JBoss Theme" in JBoss Tools, and make it the default CSS/theme in JBDS. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2797) .ini upgrade issue for 7.0.1 users

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2797?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2797: -------------------------------------- > We could release an installer for JBDS 7.0.1... would that solve this problem? It wouldn't be enough. Problem seems to happen when the update is performed. Releasing an installer wouldn't prevent people from updating. It seems to me that the "laucher" part is not specific to JBDS. Can someone using Mac OS try the following: # get Kepler SR0 # see content of launcher in eclipse.ini # Run "Check for update" (ensure it installs Kepler SR1) # Restart and check value of "launcher" in eclipse.ini. Those values must be different. If they're not, it means that update mechanism is the culprit, if not, it means that it's specific to JBDS. For the discovery site, I tend to think it's a JBDS bug, which might be independent of the OS. > .ini upgrade issue for 7.0.1 users > ---------------------------------- > > Key: JBDS-2797 > URL: https://issues.jboss.org/browse/JBDS-2797 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer > Affects Versions: 7.0.1.GA > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > > User noticed issues with 7.0.0 to 7.0.1 updates at https://community.jboss.org/message/841477#841477 that needs investigation. > The post is about osx but I don't think this is limited to this OS, just that OSX has a different java behavior. > Worrisome issues are: > development url used in GA update: > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml > startup/launcher directories are hardcoded in the .ini file: > -startup > ../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar > --launcher.library > ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130807-1835 > Have these been forgotten/set wrong in the update or is this some specific update path that is failing ? -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2797) .ini upgrade issue for 7.0.1 users

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2797?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2797: ------------------------------------------- So are you saying the original app .ini is updated correctly and does not have broken references ? then this would be fixable if instead of copying we would create a symbolic link ? Thus original updates would fix the "linked" version too ? > .ini upgrade issue for 7.0.1 users > ---------------------------------- > > Key: JBDS-2797 > URL: https://issues.jboss.org/browse/JBDS-2797 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer > Affects Versions: 7.0.1.GA > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > > User noticed issues with 7.0.0 to 7.0.1 updates at https://community.jboss.org/message/841477#841477 that needs investigation. > The post is about osx but I don't think this is limited to this OS, just that OSX has a different java behavior. > Worrisome issues are: > development url used in GA update: > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml > startup/launcher directories are hardcoded in the .ini file: > -startup > ../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar > --launcher.library > ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130807-1835 > Have these been forgotten/set wrong in the update or is this some specific update path that is failing ? -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15645) Revisit archetype switching based on runtime (community/product) and runtime level (ee6 vs ee7)

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15645?page=com.atlassian.jira.plugi... ] Rafael Benevides commented on JBIDE-15645: ------------------------------------------ We didn't have labels, planned for Archetype, just for ArchetypeVersion: ( https://raw.github.com/jboss-jdf/jdf-stack/1.0.0.Final/fileformat.png ) If we add these Properties to the YAML file, old stacks-client versions will break and this should be considered a file format change. I can't apply this ASAP without further discussion. Can't we use those label's on ArchetypeVersion, only ? isBlank, target makes sense to the ArchetypeVersion instead of Archetype. > Revisit archetype switching based on runtime (community/product) and runtime level (ee6 vs ee7) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15645 > URL: https://issues.jboss.org/browse/JBIDE-15645 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples > Affects Versions: 4.1.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.1.Beta1 > > > Enterprise/Community versions of archetypes will no longer be switchable through the -Denterprise switch. Different GAV coordinates will need to be used instead. > We need to come up with changes in both stacks.yaml format and JBDS to cope with this > Some discussion on etherpad : http://ether-man.rhcloud.com/p/funkyarchetype -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-4731) use p2.mirror w/ comparator to verify plugin/feature versions are correctly incremented between builds/baselines

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-4731?page=com.atlassian.jira.plugin... ] Jiri Peterka commented on JBIDE-4731: ------------------------------------- Is there anything else needed beyond current behavior (version 0.3.0)? > use p2.mirror w/ comparator to verify plugin/feature versions are correctly incremented between builds/baselines > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-4731 > URL: https://issues.jboss.org/browse/JBIDE-4731 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Blocker > Fix For: 4.1.x, 4.2.x > > > This depends on having per-component builds and a buckminster/p2 aggregator to merge them into a single update site. > See http://aniefer.blogspot.com/2009/08/versioning-p2-slides-from-eclipsecon.... for details on using p2.mirror w/ a comparator -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15159) versionwatch should not report something red then yellow if nothing has changed (version not bumped)

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15159?page=com.atlassian.jira.plugi... ] Jiri Peterka resolved JBIDE-15159. ---------------------------------- Fix Version/s: 4.1.1.Alpha2 (was: 4.1.x) Resolution: Done Nick, VWatch version 0.3.0 should provide more transparent report and fix these issues. If you're ok with that, please close, reopen otherwise. > versionwatch should not report something red then yellow if nothing has changed (version not bumped) > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-15159 > URL: https://issues.jboss.org/browse/JBIDE-15159 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Affects Versions: 4.1.0.CR1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Fix For: 4.1.1.Alpha2 > > Attachments: 15159_1.png, 15159_2.png, 15159_3.png > > > For many 3rd party plugins, which haven't changed in years, the report will often start white, then because no version bump happens will report red... and then magically drop to yellow for a few releases. Then red again, and then yellow. > Surely if a version not increasing is bad it should STAY bad, rather than oscillating? > Reports to compare are here: > http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... > http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15428) No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15428?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-15428: ------------------------------------------- Assignee: Xavier Coulon (was: Max Rydahl Andersen) > No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15428 > URL: https://issues.jboss.org/browse/JBIDE-15428 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > Attachments: After import.png, After workaround.png, Before import.png > > > After importing Dynamic Web Project with JAX-RS support with HTTPMethod annotation without @Target and @Retention annotations, there is no error. > This looks like a regression of JBIDE-12690. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11294) Error is thrown in error log when testing improper URL of Web Service with Web Service Tester

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11294?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-11294: ------------------------------------------- Moving to 4.2.x. Will investigate as time allows. > Error is thrown in error log when testing improper URL of Web Service with Web Service Tester > --------------------------------------------------------------------------------------------- > > Key: JBIDE-11294 > URL: https://issues.jboss.org/browse/JBIDE-11294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 3.3.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Brian Fitzpatrick > Fix For: 4.2.x > > Attachments: jbide-11294.patch > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > In my opinion, if I want to test some web service with Web Service tester and provide some wsdl file with improper URL location, message in Response Body should be adequate. There is no need to throw error in error log. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11294) Error is thrown in error log when testing improper URL of Web Service with Web Service Tester

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11294?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-11294: -------------------------------------- Fix Version/s: 4.2.x (was: 4.1.x) > Error is thrown in error log when testing improper URL of Web Service with Web Service Tester > --------------------------------------------------------------------------------------------- > > Key: JBIDE-11294 > URL: https://issues.jboss.org/browse/JBIDE-11294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 3.3.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Brian Fitzpatrick > Fix For: 4.2.x > > Attachments: jbide-11294.patch > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > In my opinion, if I want to test some web service with Web Service tester and provide some wsdl file with improper URL location, message in Response Body should be adequate. There is no need to throw error in error log. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2790) "JBoss Tools" themes should not be part of JBDS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2790?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2790: --------------------------------- Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-product/pull/73, https://github.com/jbdevstudio/jbdevstudio-product/pull/74 Submitted PRs. > "JBoss Tools" themes should not be part of JBDS > ----------------------------------------------- > > Key: JBDS-2790 > URL: https://issues.jboss.org/browse/JBDS-2790 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 6.0.1.GA, 7.0.1.GA > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > "JBoss Tools" themes seem to be included in JBDS even though JBDS-2631 was rejected and not supposed to be included. > Now users are reporting issues on them in JBDS-2781 and JBDS-2782 we'll need to decide what to with them. > My suggestion is we remove them in JBDS 8 and if a missing theme does not affect a user having already used these themes I suggest we remove them in JBDS 7.1 too. > Thus setting suggested release target to 7.1 but if investigation shows it will hurt update path then at least remove them in 8.0. > WDYT ? -- 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, 6 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 October 2013