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: ---------------------------------------- 1) in such case, we could show the 2 connectors and add some rules to prevent from installing both simultaneously (such as avoiding both checkbox to be ticked, or only showing one checkbox). Or maybe have a single connector entry, but with a radio or a dropdown to change its "flavor" (regular or early-access). 2) can't the Fuse connectors be forward-compatible and JBDS be backward-compatible enough? So that the former release of Fuse would work in upcoming release of JBT/JBDS. With that, there is always a good Fuse release and everyone (users, JBT, Fuse) is happy with this. 3-4) seems ok as it. > 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] (JBIDE-19637) Runtime download hyperlink not working from New Server dialog on Mac

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19637: --------------------------------------- Today I wanted to to install additional server adapters in a clean Eclipse and the link in the New Server dialog does not work for me either. I reported it here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=471655 It could be the same cause, right? > Runtime download hyperlink not working from New Server dialog on Mac > -------------------------------------------------------------------- > > Key: JBIDE-19637 > URL: https://issues.jboss.org/browse/JBIDE-19637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: help_wanted > Fix For: 4.3.0.Beta2 > > > When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything. > If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work. > This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20179) Error installing Atlassian eclipse plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20179?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20179: --------------------------------------------- that is a very generic error. Does it fail with other plugins ? Please try again ;) > Error installing Atlassian eclipse plugin > ----------------------------------------- > > Key: JBIDE-20179 > URL: https://issues.jboss.org/browse/JBIDE-20179 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta1 > Reporter: Len DiMaggio > > Trying to the Atlassian plugin install (via JBoss Central): > Install Atlassion connector for eclipse from Central > Atlassian Connector for Eclipse 3.2.5.v20150427 com.atlassian.connector.eclipse.feature.group > This error is raised: > Problems occurred while performing installation: Unable to read repository at http://download.eclipse.org/releases/mars. > Unable to read repository at http://download.eclipse.org/releases/mars. > No repository found at http://download.eclipse.org/technology/epp/packages/mars/. -- 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20171?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20171: --------------------------------------------- no, we should not force same build qualifiers. Either we build this and release it or we don't ;) Releasing different binaries with same verison/build qualifiers is just a big nono. > 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] (JBIDE-19598) Use "Build other project (extended)" to cascade aggregation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19598?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19598: --------------------------------------------- The only thing I could find that says "build other project (Extended)" is the pipeline job (https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin) ? if that is the one you mean then yes, buildchow supports that natively and one of the things I wanted to experiment with once we had buildchow in place. Don't grok how that make composite install tests irrelevant though. > Use "Build other project (extended)" to cascade aggregation > ----------------------------------------------------------- > > Key: JBIDE-19598 > URL: https://issues.jboss.org/browse/JBIDE-19598 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > > In order to decide whether to cascade aggregation when components are build, we could use the "Build other project (extended)" plugin in order to trigger 2 aggregate jobs (site, coretests-site) when component has SCM changes. > This would require changing all 17 component jobs (per stream = 34 jobs), but would eliminate the need for the composite-install test jobs [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19598) Use "Build other project (extended)" to cascade aggregation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19598?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19598: --------------------------------------------- btw. I dont follow why composite install test jobs becomes irrelevant when we trigger these jobs btw ? > Use "Build other project (extended)" to cascade aggregation > ----------------------------------------------------------- > > Key: JBIDE-19598 > URL: https://issues.jboss.org/browse/JBIDE-19598 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > > In order to decide whether to cascade aggregation when components are build, we could use the "Build other project (extended)" plugin in order to trigger 2 aggregate jobs (site, coretests-site) when component has SCM changes. > This would require changing all 17 component jobs (per stream = 34 jobs), but would eliminate the need for the composite-install test jobs [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19598) Use "Build other project (extended)" to cascade aggregation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19598?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19598: --------------------------------------------- what plugin is it exactly ? And buildchow has "raw" support now so even if it does not support it natively we can add the raw xml for it until that happens. About save snapshot of what is on the server in github to easily track things that seems wrong to me. The easy way to track things are to have the changes recorded in buildchow and then if we wanted (for backup reasons) to commit the generated config.xml files. We should stop taking any configs from the server and commit - only reason to take from server is to try find what the diff is in case of some error. > Use "Build other project (extended)" to cascade aggregation > ----------------------------------------------------------- > > Key: JBIDE-19598 > URL: https://issues.jboss.org/browse/JBIDE-19598 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > > In order to decide whether to cascade aggregation when components are build, we could use the "Build other project (extended)" plugin in order to trigger 2 aggregate jobs (site, coretests-site) when component has SCM changes. > This would require changing all 17 component jobs (per stream = 34 jobs), but would eliminate the need for the composite-install test jobs [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3478) Toolbar icons don't scale with different ui scaling factors

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3478?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3478: ------------------------------ Attachment: scale2x.png Added a screenshot for JBDS/JBT on full HD resolution using scaling factor of 2. > Toolbar icons don't scale with different ui scaling factors > ----------------------------------------------------------- > > Key: JBDS-3478 > URL: https://issues.jboss.org/browse/JBDS-3478 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: ui/branding > Affects Versions: 9.0.0.Beta1 > Environment: Fedora 20, gnome 3.10.1, gtk3-3.10.9 > Reporter: Jan Richter > Attachments: scale2x.png > > > Using the desktop interface scaling factor to change the ui size (comes in handy on high resolutions) with this command: > {noformat} > gsettings set org.gnome.desktop.interface scaling-factor 2 > {noformat} > Most of the gui scales nicely except for toolbar icons, which stay the same, only the spacing between them increases. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20100: --------------------------------------------- okey, so you are stating the same as the comments. Show earlyaccess content more prominently. We agree on this. Now can we go over the issues that are beyond this ? 1) just showing all by default does not handle the case when earlyaccess is adding/changing an existing connector - so how do we handle these if EA are shown by default ? 2) Fuse and others will not have an earlyaccess build before later how do we handle this (suggestion: add a way for these to tell user need to use devstudio 7 and/or 8 instead, i.e. "advertise-connector") 3) How do we handle installs from project examples - will we just keep that as is so it will install whatever is configured and only get earlyaccess when installed ? 4) How about the proxy wizards - these also are on/off based on earlyaccess. I think 3 and 4 is just handled by keeping as is, thus main issue for this is still 1 and 2. > 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-3478) Toolbar icons don't scale with different ui scaling factors

by Jan Richter (JIRA)

Jan Richter created JBDS-3478: --------------------------------- Summary: Toolbar icons don't scale with different ui scaling factors Key: JBDS-3478 URL: https://issues.jboss.org/browse/JBDS-3478 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: ui/branding Affects Versions: 9.0.0.Beta1 Environment: Fedora 20, gnome 3.10.1, gtk3-3.10.9 Reporter: Jan Richter Using the desktop interface scaling factor to change the ui size (comes in handy on high resolutions) with this command: {noformat} gsettings set org.gnome.desktop.interface scaling-factor 2 {noformat} Most of the gui scales nicely except for toolbar icons, which stay the same, only the spacing between them increases. -- 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