December 2015 - jbosstools-issues

[JBoss JIRA] (JBDS-2512) JBDS70_0010: [Commit] (Dev) (P1) Download of EAP and setup of runtime

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2512?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-2512: -------------------------------- > JBDS70_0010: [Commit] (Dev) (P1) Download of EAP and setup of runtime > --------------------------------------------------------------------- > > Key: JBDS-2512 > URL: https://issues.jboss.org/browse/JBDS-2512 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, runtime > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 8.0.0.Beta2 > > > - Downloading of EAP6 with the appropriate Ts & Cs agreement > - Login/registration process > - All versions EAP6.x (and 7.x) available while the default is latest > - Align project examples/central download -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2512) JBDS70_0010: [Commit] (Dev) (P1) Download of EAP and setup of runtime

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-2512?page=com.atlassian.jira.plugin.... ] Rob Stryker updated JBDS-2512: ------------------------------ Fix Version/s: 8.0.0.Beta2 > JBDS70_0010: [Commit] (Dev) (P1) Download of EAP and setup of runtime > --------------------------------------------------------------------- > > Key: JBDS-2512 > URL: https://issues.jboss.org/browse/JBDS-2512 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, runtime > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 8.0.0.Beta2 > > > - Downloading of EAP6 with the appropriate Ts & Cs agreement > - Login/registration process > - All versions EAP6.x (and 7.x) available while the default is latest > - Align project examples/central download -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-20609: ------------------------------------ And if I may reply to some previous comments: bq. As a normal user and as us wanting to make sure the software the normal user install I do not think it is valuable at all to have them see Early access by default. I thought that this is what we wanted. Typical normal user for us was guy, who wanted to install Fuse or something like that to latest JBDS. But since that stuff was EA, he couldn't find it. Wasn't that the reason which started the fuzz of changing Central? bq. Having a dialog popping up making them select between two options that looks exactly identical is not helping the user to understand he is installing something "special"; nor why he needs to make a choice. I think that this is just a bug... If you look at this screenshot http://i.imgur.com/yR2lkWO.png you'll see, that both connectors have "Certified" certification, which is wrong. One of those certifications should be "Experimental - Early Access". When this is fixed, we have to make sure, that desriptions of those connectors are descriptive enough, that normal user can make a decison. If that's not the case, we have a problem and we have to change those descriptions. bq. I'd recommend not rushing this feature into Beta1 until we can get a better/wider consensus from everyone. Thx! Correct. I can work with Mickael and try his branch from time to time and when we'll be happy enough, we can push it further. bq. Can someone remind me why the current situation is not okey now that we have the "advertisable" connectors where we can selectively make Fuse or other components showup with info on how to get them ? I agree with Michael here. Those "advertisable" connectors are useful when the feature is not available yet. But when it'll be available (as EA or normal connector) tha "advertisable" connector will be replaced by EA/normal one. User workflow will be like: Open central -> see advertisable connector -> "Oh... I have to wait". Next week... Open Central -> see EA connector -> "Finally it's here!" -> install. > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2512) JBDS70_0010: [Commit] (Dev) (P1) Download of EAP and setup of runtime

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-2512?page=com.atlassian.jira.plugin.... ] Rob Stryker closed JBDS-2512. ----------------------------- Resolution: Duplicate Issue > JBDS70_0010: [Commit] (Dev) (P1) Download of EAP and setup of runtime > --------------------------------------------------------------------- > > Key: JBDS-2512 > URL: https://issues.jboss.org/browse/JBDS-2512 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, runtime > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 8.0.0.Beta2 > > > - Downloading of EAP6 with the appropriate Ts & Cs agreement > - Login/registration process > - All versions EAP6.x (and 7.x) available while the default is latest > - Align project examples/central download -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21161) various UI issues on new cdk server adapter

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21161?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-21161. --------------------------------- Resolution: Done pushed to master and maintenance. > various UI issues on new cdk server adapter > ------------------------------------------- > > Key: JBIDE-21161 > URL: https://issues.jboss.org/browse/JBIDE-21161 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, openshift > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1 > > Attachments: JBIDE-21161c.png, JBIDE-21161d.png, New_Server_and_Java_EE_-_Eclipse.png > > > the cDK server adapter page has some "weird" UI layout. > see attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21190) Should we update wildfly icon / banner?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21190?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-21190. --------------------------------- Resolution: Done pushed to master and maintenance. > Should we update wildfly icon / banner? > --------------------------------------- > > Key: JBIDE-21190 > URL: https://issues.jboss.org/browse/JBIDE-21190 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1 > > Attachments: JBIDE-21190.png, JBIDE-21190_v2.png > > > Wildfly is still using the jboss-by-redhat logo. Is this still appropriate? How about for the icon for the server itself? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21193) runtime detection detects *any* folder as a CDK and jboss multiple times

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21193?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-21193. --------------------------------- Resolution: Done Did not notice this was re-opened. It's fixed. > runtime detection detects *any* folder as a CDK and jboss multiple times > ------------------------------------------------------------------------ > > Key: JBIDE-21193 > URL: https://issues.jboss.org/browse/JBIDE-21193 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.Beta1 > > Attachments: Java_EE_-_jboss-eap-6_1_CDK_Server_-_Eclipse.png > > > with build from last week I now get this list of runtime detected in my folder of servers. > At first I thought it was the CDK being weird but something is also very weird about the basic runtime detection since I seem to have multiple WildFly 8.0's...as opposed to using the folder name. > Here is the content of my folder > {code} > apache-karaf-2.3.5 > apache-tomcat-7.0.35 > app.js > app.js.1 > fsw-6 > jboss as 7 > jboss-5.1.0.GA > jboss-as-7.0.1.Final > jboss-as-7.1.0.Final > jboss-as-7.1.1.Final > jboss-as-web-7.0.0.Final > jboss-as-web-7.0.2.Final > jboss-eap-6.0.1 > jboss-eap-6.1 > weld-1.1.0.Final > weld-1.1.5.Final > wildfly-10.0.0.CR4 > wildfly-8.0.0.Beta1 > wildfly-8.0.0.Final > wildfly-8.1.0.Final > wildfly-8.2.0 > wildfly-core-8.0.0.Final > {code} > and attached is the list I get. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20609: ---------------------------------------- Thanks Radim. Indeed, most of your remarks are bugs. {quote}First, there is no way how to figure out which connectors are both EA&non-EA. This should be somehow displayed on list of connectors. We have to make that more visible, noticeable.{quote} Well, I believe that's the core paradigm of this change. In my opinion, and as the change was designed, no-one needs to know whether a connector is EA or not before-hand. People install features, they're just interested in what they will be able to do with it. Whether it's EA or not is IMO secondary and isn't something that should be presented so early to users. > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-20609: ------------------------------------ I tried mickaels branch today and here is my input (I guess most of the points were made already): * I like this approach. It makes installing EA stuff easier and more visible (even though it's kinda confusing. But I hope we can figure out how to make it less confusing) * Installing connector which has both EA and non-EA is currently very confusing. ** First, there is no way how to figure out which connectors are both EA&non-EA. This should be somehow displayed on list of connectors. We have to make that more visible, noticeable. ** Second, when user selects that connector to install, dialog pops up and even there it's not obvious which one is EA adn which one isn't - http://i.imgur.com/yR2lkWO.png (I guess, that this is a bug... that one of them should have EA certificationId ("Experimental - Early Access") according to earlyaccess discovery jar.) * In current version of JBDS (9.0.0), there is information about EA being enabled/disabled on Software/Update page shown in form of "Enable EA" checkbox... This information disappeared from Software/Update page (one has to either look at Getting Started page or open EA installation dialog - click "Manage Early Access" button). I would like to see that information directly on Software/Update page, even if that's just a simple label/warning. * Hmm... looking around now I noticed, that all connectors have "Certified" certification (even EA ones)... this is definitely a bug (the tooltip of certification is correct though...) and it's affecting also the "Select extension flavor" dialog. * another bug - in Manage Early Access dialog, the "Disable EA and related software sites" button is allways disabled. That's because the "is EA enabled" property is stored in discovery plugin preferences, but it is read from central preferences. * Another thing I noticed is that the property I was talking in bullet above is stored in workspace specific preferences (Instance scope). I believe, that storing it in eclipse specific preferences (configuration scope) would be imo better. > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21278) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [Webservices]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21278?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-21278. --------------------------------- Release Notes Text: Rejecting since no changes occurred on this branch since 4.3.0.Final Assignee: Xavier Coulon Resolution: Done > For JBIDE 4.3.1.Beta1: Code Freeze + Branch [Webservices] > --------------------------------------------------------- > > Key: JBIDE-21278 > URL: https://issues.jboss.org/browse/JBIDE-21278 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Webservices]: Please perform the following tasks: > 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.1.Beta1, 9.1.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101 > *NOTE:* If you already did this earlier when we were preparing for Beta1 (after 4.3.0.Final was released), you do *not* need to do so again. > Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.1.Beta1-SNAPSHOT. > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT). > {code} > mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch; > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > git checkout -b jbosstools-4.3.1.Beta1x > git push origin jbosstools-4.3.1.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*. > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > {code} > 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and > * *{color:orange}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 December 2015