July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20100: ---------------------------------------- This report is not only about changing a label, but really a strong criticism about the user experience with Early-Access. It's not the first time I hear bad things about it and not the last one, so I believe there is a real effort to do in re-thinking the user experience here. My comment is an answer to the part of original request, which was clearly blaming the filtering of early access "instead of filtered in between everything else", so did the new user who reported this to me. I agree with the fact that filtering by default is an anti-pattern of discovery, and that it would be much easier to actually show everything to users. By showing all connectors, Early-Access would definitely be more prominent, user would not have to dig to discover things. For the case when connectors aren't available yet, I'm not sure I understood what's actually the user-story behind that. But I believe if we stop hiding things by default, then people would immediately see the new Early-Access features when they're available and we wouldn't need to highlight them when they're not. > how to make users aware of fuse and other tooling only being available from earlyaccess? > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20100 > URL: https://issues.jboss.org/browse/JBIDE-20100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page. > Some comments: > "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list." > "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something." > Suggestion: > "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature." > I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ? > and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ? > But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9) > [~crobson], [~aileenc] and [~lhein] got any suggestions ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3470) Toolbars + Icons unusable on high resolution screens

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3470?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3470: --------------------------------- No problem, [~mmusaji]: https://issues.jboss.org/browse/TOOLSDOC-661 > Toolbars + Icons unusable on high resolution screens > ---------------------------------------------------- > > Key: JBDS-3470 > URL: https://issues.jboss.org/browse/JBDS-3470 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: ui/branding > Affects Versions: 9.0.0.Beta1 > Environment: Windows + UHD screens > Reporter: Mustafa Musaji > Fix For: 9.0.0.GA > > Attachments: hi-res-example.png, jbds-after-scaling.png, wordpad-scaling.png > > > When using JBDS on UHD screen the toolbar is unusable due to it not being resized and too small to use properly. > Upstream: https://bugs.eclipse.org/bugs/show_bug.cgi?id=382972 > I'm raising this for QE to ensure we test this in the next release as it was fixed upstream. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-661) JBDS RN: Ensure this issue is included in Known or Resolved issues

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-661: ---------------------------------- Summary: JBDS RN: Ensure this issue is included in Known or Resolved issues Key: TOOLSDOC-661 URL: https://issues.jboss.org/browse/TOOLSDOC-661 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-661) JBDS RN: Ensure this issue is included in Known or Resolved issues

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-661?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-661: ------------------------------- Description: Ensure https://issues.jboss.org/browse/JBDS-3470 is included in RN for all versions of JBDS 9.0 > JBDS RN: Ensure this issue is included in Known or Resolved issues > ------------------------------------------------------------------ > > Key: TOOLSDOC-661 > URL: https://issues.jboss.org/browse/TOOLSDOC-661 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Ensure https://issues.jboss.org/browse/JBDS-3470 is included in RN for all versions of JBDS 9.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3463) Headless installer should at least warn when running on Java 7

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3463?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3463: ------------------------------------- this is actually called automated mode. Headless mode is triggered by -console parameter and is not fully supported yet (see JBDS-3446). > Headless installer should at least warn when running on Java 7 > -------------------------------------------------------------- > > Key: JBDS-3463 > URL: https://issues.jboss.org/browse/JBDS-3463 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.0.0.Beta1 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > Attachments: InstallConfigRecord.xml > > > While the GUI installer won't let you complete the installation without choosing Java 8 or higher, the headless installer doesn't care. > If you give it a config with path to Java 7, it will install everything and set Java 7 as -vm in jbdevstudio.ini. I think it should behave consistently with the GUI or at least warn that the Java I'm installing with is not supported anymore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3463) Headless installer should at least warn when running on Java 7

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3463?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3463: ----------------------------------- Assignee: Denis Golovin > Headless installer should at least warn when running on Java 7 > -------------------------------------------------------------- > > Key: JBDS-3463 > URL: https://issues.jboss.org/browse/JBDS-3463 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.0.0.Beta1 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > Attachments: InstallConfigRecord.xml > > > While the GUI installer won't let you complete the installation without choosing Java 8 or higher, the headless installer doesn't care. > If you give it a config with path to Java 7, it will install everything and set Java 7 as -vm in jbdevstudio.ini. I think it should behave consistently with the GUI or at least warn that the Java I'm installing with is not supported anymore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3463) Headless installer should at least warn when running on Java 7

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3463?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3463: -------------------------------- Fix Version/s: 9.0.0.Beta2 > Headless installer should at least warn when running on Java 7 > -------------------------------------------------------------- > > Key: JBDS-3463 > URL: https://issues.jboss.org/browse/JBDS-3463 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.0.0.Beta1 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > Attachments: InstallConfigRecord.xml > > > While the GUI installer won't let you complete the installation without choosing Java 8 or higher, the headless installer doesn't care. > If you give it a config with path to Java 7, it will install everything and set Java 7 as -vm in jbdevstudio.ini. I think it should behave consistently with the GUI or at least warn that the Java I'm installing with is not supported anymore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20171) buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20171?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-20171: --------------------------------------- There should be no problems with xulrunner rebuild. we probably need to force the same build qualifiers like current build has to avoid unnecessary updates. > buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA > ------------------------------------------------------------------- > > Key: JBIDE-20171 > URL: https://issues.jboss.org/browse/JBIDE-20171 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta2 > > > Since the addition of a check that verifies exactly this condition: > https://github.com/jbosstools/jbosstools-maven-plugins/commit/916f4521ba6... > I've now got a situation where it's OK to have no SHA in the MANIFEST.MF, but a SHA in buildinfo.json. > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console} > [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files! > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json > [ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences > [ERROR] commitId . > [ERROR] If you have locally built projects which are aggregated here, > [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch. > [ERROR] Or, use -DskipCheckSHAs=true to bypass this check. > [ERROR] -> [Help 1]{code} > This happened after I put a buildinfo.json file here: > http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... > I've since moved the file here to temporarily work around the build failure: > http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3067) Use JBDevStudio.icns with higher resolution on mac

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3067?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3067: -------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Alpha1) > Use JBDevStudio.icns with higher resolution on mac > -------------------------------------------------- > > Key: JBDS-3067 > URL: https://issues.jboss.org/browse/JBDS-3067 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.0.0.Alpha1 > Environment: Mac OS X 10.9.3 (Mavericks) > Reporter: Denis Golovin > Assignee: Daniel Azarov > Priority: Minor > Attachments: jbds-in-finder.png > > > Current icon resolution is too low and looks like this > !jbds-in-finder.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3067) Use JBDevStudio.icns with higher resolution on mac

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3067?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3067: ----------------------------------- Resolution: (was: Done) Affects Version/s: 9.0.0.Alpha1 Assignee: Denis Golovin (was: Daniel Azarov) Fix Version/s: (was: 9.0.0.Beta2) > Use JBDevStudio.icns with higher resolution on mac > -------------------------------------------------- > > Key: JBDS-3067 > URL: https://issues.jboss.org/browse/JBDS-3067 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.0.0.Alpha1 > Environment: Mac OS X 10.9.3 (Mavericks) > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Attachments: jbds-in-finder.png > > > Current icon resolution is too low and looks like this > !jbds-in-finder.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 July 2015