July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17817) Management / Filesystem operations offerred when changing the profile of EAP 5

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17817?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17817: ------------------------------------- I actually squeezed that 1 line change into https://github.com/jbosstools/jbosstools-server/pull/239/files and https://github.com/jbosstools/jbosstools-server/pull/238/files > Management / Filesystem operations offerred when changing the profile of EAP 5 > ------------------------------------------------------------------------------ > > Key: JBIDE-17817 > URL: https://issues.jboss.org/browse/JBIDE-17817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > This is a followup of JBIDE-17636 which added the possibility to change the server profile after creating it. > But for EAP 5.x, the only thing you should be allowed to change is local/remote, not management/filesystem - this is as7/eap6/wf only. > Sorry if you already have a JIRA for this, I couldn't find it. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3086) Change Central Discovery URLs?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3086?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3086: -------------------------------------- Description: Today, the Central discovery plugin for JBDS is points to this URL: <site>/central/core/ and for Early Access discovery: <site>/central/earlyaccess/ However, Max has suggested that we simplify the first, and change the second. I believe he wants something like this: https://devstudio.jboss.com/updates/8.0-staging/ https://devstudio.jboss.com/updates/8.0-development https://devstudio.jboss.com/updates/8.0/ and https://devstudio.jboss.com/earlyaccess/8.0-staging/ https://devstudio.jboss.com/earlyaccess/8.0-development/ https://devstudio.jboss.com/earlyaccess/8.0/ What do people think about this proposed change? [~mickael_istria] [~maxandersen] [~dgolovin] was: Today, the Central discovery plugin for JBDS is points to this URL: https://devstudio.jboss.com/updates/8.0-staging/central/core/ https://devstudio.jboss.com/updates/8.0-development/central/core/ https://devstudio.jboss.com/updates/8.0/central/core/ and for Early Access discovery: https://devstudio.jboss.com/updates/8.0-staging/central/earlyaccess/ https://devstudio.jboss.com/updates/8.0-development/central/earlyaccess/ https://devstudio.jboss.com/updates/8.0/central/earlyaccess/ However, Max has suggested that we simplify the first, and change the second. I believe he wants something like this: https://devstudio.jboss.com/updates/8.0-staging/ https://devstudio.jboss.com/updates/8.0-development https://devstudio.jboss.com/updates/8.0/ and https://devstudio.jboss.com/earlyaccess/8.0-staging/ https://devstudio.jboss.com/earlyaccess/8.0-development/ https://devstudio.jboss.com/earlyaccess/8.0/ What do people think about this proposed change? [~mickael_istria] [~maxandersen] [~dgolovin] > Change Central Discovery URLs? > ------------------------------ > > Key: JBDS-3086 > URL: https://issues.jboss.org/browse/JBDS-3086 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build, discovery, updatesite > Affects Versions: 8.0.0.Beta3 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Today, the Central discovery plugin for JBDS is points to this URL: > <site>/central/core/ > and for Early Access discovery: > <site>/central/earlyaccess/ > However, Max has suggested that we simplify the first, and change the second. > I believe he wants something like this: > https://devstudio.jboss.com/updates/8.0-staging/ > https://devstudio.jboss.com/updates/8.0-development > https://devstudio.jboss.com/updates/8.0/ > and > https://devstudio.jboss.com/earlyaccess/8.0-staging/ > https://devstudio.jboss.com/earlyaccess/8.0-development/ > https://devstudio.jboss.com/earlyaccess/8.0/ > What do people think about this proposed change? > [~mickael_istria] [~maxandersen] [~dgolovin] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17808) Identify which installed IUs are from Early Access vs. supported/tested versions

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17808: --------------------------------------------- [~mickael_istria] we already discussed this in past - the usecase was part of the discussion regarding requirement for the early access feature: see https://issues.jboss.org/browse/JBDS-2745?focusedCommentId=12800808&page=... "Thus the idea of "blessed features/plugins" came about. Have some representation of plugins/features incl. version ranges we are ok with (supported) and which we consider (earlyaccess). This list would be stored in the discovery plugin (assuming we can make it small enough) Then central could crosscheck this list of plugins/features with what is actually running inside eclipse and mark/highlight wether there are earlyaccess parts PLUS it could report on "foreign" parts which we had no explicit knowledge/info on. To summarize my idea would be: A) add "earlyaccess" notion to connectors on central B) have explicit list of plugins/features that are considered supported vs earlyaccess C) add visual hints and UI to make it clear you installed some of this and you can figure out what you've installed that are experimental." You'll notice that we only have 2 out of 3. > Identify which installed IUs are from Early Access vs. supported/tested versions > -------------------------------------------------------------------------------- > > Key: JBIDE-17808 > URL: https://issues.jboss.org/browse/JBIDE-17808 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Nick Boldt > Fix For: 4.2.0.Beta3 > > > [~maxandersen] brought up a good point on a call today: > we have no way from within JBDS of identifying which installed IUs were installed from Early Access vs. those what were installed from Central or another "supported" location. > Thus we need some sort of UI to list installed IUs that are "Early Access". > This could be... (brainstorming now): > * a text file with the list of things installed from Early Access (features and plugins) > * a set of asterisks added to the Help > About dialogs when browsing for installed features / plugins > * a way to filter the plugin view (Help > About) to show only EA content (or exclude it) > * ... ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3085) Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3085?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3085: ------------------------------------------- Just to be clear - I never suggested we do this for JBDS 8 and the current setup. I said the whole idea about earlyaccess was to *eventually* allow for this scenario. To answer the questions: A) There is zero difference here from any other earlyaccess content. No, we don't support easily uninstalling/downgrading that either. We *should* but we don't at the moment since we always remove the old versions, only keep the new ones. But in short - zero difference from this to other things in early access. B) support already said they were ok with earlyaccess providing alpha/beta releases - that is what the whole point of earlyaccess is. Wether that is JBDS itself or just addons like JBDS-IS really should have zero difference from support POV. C) I don't see a problem here since we now have the global properties to handle that jbds will go fetch the right examples based on your installed version, this situation with EAP 6.x differences is not at all related to this issue - i.e. its an issue that already exist today and we already have multiple version support for that and finally its early access, some stuff are expected to break D) plenty of things which is why I have not raised any jiras about this but simply discussed it in comments to not make it sound more scary than it is. This is part of why there are jiras discussing making sure we can actually identifiy earlyaccess content is installed and provide a list of the plugins/bundles that are supported vs non-supported and yes we'll need to handle the uninstall usecases better to allow installing early access. All that being said I don't think first attempt at this would be *FULL* JBDS update - but simply *parts* of it. Like, a newer version of Thym or maybe even Tern as opposed to full 8.1.0.Alpha1 content. > Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access? > --------------------------------------------------------------------------- > > Key: JBDS-3085 > URL: https://issues.jboss.org/browse/JBDS-3085 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > > Max brought up a question on a call today: > *Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?* > This was supposedly in the original scope for the creation of a Early Access site, but I never saw that. So, in order to get some eyeballs on this idea, and to get buy-in from QE/doc/dev/PM/PgM/PL, I'm cc:'ing some people here so we can discuss the cons and cons of this idea. > cc: [~mmusaji] [~mmurray] [~mmalina] [~maxandersen] [~mickael_istria][~ldimaggio] [~burrsutter] [~jpallich] [~rruss] [~fbricon] > (Aside: has anyone noticed that there's an plethora of people with "M" names on this team?) > Things to consider: > a) what happens if an 8.0.0.GA user suddenly finds they've updated to an Alpha or Beta release? Can they uninstall? (Probably not, if they started with the installer; probably yes if they started from BYOE / Marketplace.) > b) how will GSS support these "I was on GA but not I'm on Beta" users? > c) What about project examples that might / might not be compatible between 8.0 and 8.x, eg., because of changes in Eclipse Luna or a new default runtime (EAP 6.3, 6.4) ? > d) what could possibly go wrong? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17817) Management / Filesystem operations offerred when changing the profile of EAP 5

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17817?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-17817: ---------------------------------- Description: This is a followup of JBIDE-17636 which added the possibility to change the server profile after creating it. But for EAP 5.x, the only thing you should be allowed to change is local/remote, not management/filesystem - this is as7/eap6/wf only. Sorry if you already have a JIRA for this, I couldn't find it. was: This is a followup of JBIDE-17636 which added the possibility to change the server profile after creating it. But for EAP 5.x, the only thing you should be allowed to change is local/remote, not management/filesystem - this is as7/eap6/wf only. > Management / Filesystem operations offerred when changing the profile of EAP 5 > ------------------------------------------------------------------------------ > > Key: JBIDE-17817 > URL: https://issues.jboss.org/browse/JBIDE-17817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > This is a followup of JBIDE-17636 which added the possibility to change the server profile after creating it. > But for EAP 5.x, the only thing you should be allowed to change is local/remote, not management/filesystem - this is as7/eap6/wf only. > Sorry if you already have a JIRA for this, I couldn't find it. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17817) Management / Filesystem operations offerred when changing the profile of EAP 5

by Martin Malina (JIRA)

Martin Malina created JBIDE-17817: ------------------------------------- Summary: Management / Filesystem operations offerred when changing the profile of EAP 5 Key: JBIDE-17817 URL: https://issues.jboss.org/browse/JBIDE-17817 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.0.Beta3 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.2.0.Beta3 This is a followup of JBIDE-17636 which added the possibility to change the server profile after creating it. But for EAP 5.x, the only thing you should be allowed to change is local/remote, not management/filesystem - this is as7/eap6/wf only. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17507) Central's error message when no connectors can be found needs help

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17507?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-17507. ------------------------------ Verified in JBT 4.2.0.Beta3 > Central's error message when no connectors can be found needs help > ------------------------------------------------------------------ > > Key: JBIDE-17507 > URL: https://issues.jboss.org/browse/JBIDE-17507 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.2.0.Beta3 > > > Using vmargs in eclipse.ini / jbdevstudio.ini which pointed to URLs that didn't exist, such as: > {code} > -vmargs > -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/master/BAD-jbosstools-directory.xml > -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/nightly/core/BAD-master/ > -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/BAD-master/ > {code} > ... I was able to get this error message in JBDS 8 Beta2: > !https://issues.jboss.org/secure/attachment/12382857/12382857_JBDS8beta2-error-message-squished.png! > Problems: > a) copy is squished into a narrow field - should fill the whole screen > b) "Web" is capitalized. > c) Rather than just saying "you may have a Web connection issue" how about linking the user to the proxy preferences page? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17534) JBoss Central: It is possible to install Early Access features after uncheck "I understand those conditions" check-box

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17534?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-17534. ------------------------------ Verified in JBT 4.2.0.Beta3 > JBoss Central: It is possible to install Early Access features after uncheck "I understand those conditions" check-box > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-17534 > URL: https://issues.jboss.org/browse/JBIDE-17534 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Daniel Azarov > Assignee: Mickael Istria > Labels: early-access > Fix For: 4.2.0.Beta3 > > Attachments: Central1.png, Central2.png, Central3.png > > > Test case: > 1. Start JBDS > 2. Open JBoss Central > 3. Select tab "Software/Update" > !Central1.png! > 4. Select "I understand those conditions..." check-box > 5. Select some experemental features > !Central2.png! > 6. Uncheck "I understand those conditions..." check-box > FAIL: > It is stiil possible to install those features > !Central3.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17816) [regression] Default values for Project name, Archetype ID etc. are not filled for archetype project wizards

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17816?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-17816: -------------------------------- Summary: [regression] Default values for Project name, Archetype ID etc. are not filled for archetype project wizards (was: Default values for Project name, Archetype ID etc. are not filled for archetype project wizards) > [regression] Default values for Project name, Archetype ID etc. are not filled for archetype project wizards > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-17816 > URL: https://issues.jboss.org/browse/JBIDE-17816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.2.0.Beta3 > Reporter: Radim Hopp > Assignee: Fred Bricon > > In JBT 4.2.0.Beta2 and earlier version New project example wizard for archetypes (HTML5 project, Richfaces project, ...) fileld lot of fields automatically. > Now almost all fields are left blank (Project Name, Package, Group Id, Artifact Id) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17816) Default values for Project name, Archetype ID etc. are not filled for archetype project wizards

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17816?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-17816: ----------------------------------- Assignee: Fred Bricon > Default values for Project name, Archetype ID etc. are not filled for archetype project wizards > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-17816 > URL: https://issues.jboss.org/browse/JBIDE-17816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.2.0.Beta3 > Reporter: Radim Hopp > Assignee: Fred Bricon > > In JBT 4.2.0.Beta2 and earlier version New project example wizard for archetypes (HTML5 project, Richfaces project, ...) fileld lot of fields automatically. > Now almost all fields are left blank (Project Name, Package, Group Id, Artifact Id) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 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 2014