November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20744) Application wizard: Defined Resources are not available for a local template

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20744?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20744. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > Application wizard: Defined Resources are not available for a local template > ---------------------------------------------------------------------------- > > Key: JBIDE-20744 > URL: https://issues.jboss.org/browse/JBIDE-20744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > > In a New OpenShift Application wizard on the first wizard page we have a button "Defined Resources" which opens a new shell with defined resources in a user friendly way. But If I select a local template the button is disabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20759) Add project name validation

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20759?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20759. --------------------------------- Verified in nightly 4.3.1.Beta1 build with plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > Add project name validation > --------------------------- > > Key: JBIDE-20759 > URL: https://issues.jboss.org/browse/JBIDE-20759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.1.Beta1 > > > We have validation of a project name just for its length which is supposed to be between 2 and 63 characters. But we have no validation on the form of a project name which has to be matching regex [a-z0-9]([-a-z0-9]*[a-z0-9]. Currently it is possible to type name e.g. "myProject" and there is no validation although it is not a valid name and creation fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21139) OpenShift 3 connection in OpenShift Explorer view is not refreshed upon editing

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21139: ------------------------------------- Summary: OpenShift 3 connection in OpenShift Explorer view is not refreshed upon editing Key: JBIDE-21139 URL: https://issues.jboss.org/browse/JBIDE-21139 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Marián Labuda Attachments: connection.png After editing a connection which was without credentials (e.g. token was not stored in secure storage and eclipse got restarted) and there is tree item informing about such an error, editing the connection does not refresh connection item in OpenShift explorer view and it is necessary to refresh it via context menu of the connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21139) OpenShift 3 connection in OpenShift Explorer view is not refreshed upon editing

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21139?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21139: ---------------------------------- Labels: connection_wizard explorer openshift_v3 (was: ) > OpenShift 3 connection in OpenShift Explorer view is not refreshed upon editing > ------------------------------------------------------------------------------- > > Key: JBIDE-21139 > URL: https://issues.jboss.org/browse/JBIDE-21139 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: connection_wizard, explorer, openshift_v3 > Attachments: connection.png > > > After editing a connection which was without credentials (e.g. token was not stored in secure storage and eclipse got restarted) and there is tree item informing about such an error, editing the connection does not refresh connection item in OpenShift explorer view and it is necessary to refresh it via context menu of the connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21138) "Show In -> Web Browser" on EJB module does nothing.

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-21138: ---------------------------------- Summary: "Show In -> Web Browser" on EJB module does nothing. Key: JBIDE-21138 URL: https://issues.jboss.org/browse/JBIDE-21138 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.3.1.Beta1 Environment: JBDS 9.1.0.Beta1-v20151122-1948-B143 Reporter: Radim Hopp As title says... Selecting "Show In -> Web Browser" on EJB module does nothing. I would expect this option to be disabled, or web browser to be opened with 404 page. Instead of this, nothing happens. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15332: ---------------------------------------- I agree that the parent pom should restore put skipRequirements to false as default, or maybe even simply remove it since we will never need/want it to take another value. Test that require downloads should directly consume skipTests or equivalent to skip downloads. > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: LATER > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for 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 Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20609: ---------------------------------------- {quote}Looking at Fred's video I can only say that this is not making central easier to use - it is making it harder. {quote} Can you please elaborate the user stories that are harder? Keep in mind that our users may not know, and most not even care, about Early Access, so the purpose it to remove the expectation that they know about beforehand, and to present them connectors in a way that they can go forward and only be bugged by Early Access when it makes sense. For us, a checkbox "Show Early Access" is clear and explicit because we know what to expect from it, as its designers; but "Early Access" has no obvious meaning for users and I believe some users simply leave the checkbox unchecked and are never seeing Early-Access connectors just because they don't get what is Early Access, whereas it may make sense to them to try the EA components. So the purpose is that a user can make the choice when necessary to enable EA or not, when it makes sense to them; not before as a pre-requisite to know about. {quote}And yes, the about page is not at all simple enough to be the first thing we point users to when clicking "Manage Early access".{quote} Can you please advise then? Alexey had simple suggestions to make the page simpler, I'll try them. {quote}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 ?{quote} Why give info when we can give simple and efficient user workflows? Since its inception, I've diskiked those advertisable connectors. There just polluting my list of additional software with some softwre I cannot 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.Beta1, 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20609: --------------------------------------------- Looking at Fred's video I can only say that this is not making central easier to use - it is making it harder. And yes, the about page is not at all simple enough to be the first thing we point users to when clicking "Manage Early access". 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 ? > 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.Beta1, 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-21137) Consistency of sorting in EmbedCartridgesJob

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21137?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-21137: ------------------------------------------ Description: Sorting with CartridgeAddRemovePriorityComparator implies that cartridges should be stored in IApplication in a specific order, for instance, "mysql" should precede all other cartridges. If Edit Embedded Cartridges wizard is run once, the desirable order is guaranteed. However, if wizard is run twice, with "postgresql" selected on the first run and "mysql" added on the second run, the cartridges will be added to IApplication unsorted by the comparator. > Consistency of sorting in EmbedCartridgesJob > -------------------------------------------- > > Key: JBIDE-21137 > URL: https://issues.jboss.org/browse/JBIDE-21137 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Environment: Sorting with CartridgeAddRemovePriorityComparator implies that cartridges should be stored in IApplication in a specific order, for instance, "mysql" should precede all other cartridges. If Edit Embedded Cartridges wizard is run once, the desirable order is guaranteed. However, if wizard is run twice, with "postgresql" selected on the first run and "mysql" added on the second run, the cartridges will be added to IApplication unsorted by the comparator. > Reporter: Viacheslav Kabanovich > Assignee: Andre Dietisheim > > Sorting with CartridgeAddRemovePriorityComparator implies that cartridges should be stored in IApplication in a specific order, for instance, "mysql" should precede all other cartridges. If Edit Embedded Cartridges wizard is run once, the desirable order is guaranteed. However, if wizard is run twice, with "postgresql" selected on the first run and "mysql" added on the second run, the cartridges will be added to IApplication unsorted by the comparator. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21137) Consistency of sorting in EmbedCartridgesJob

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21137?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-21137: ------------------------------------------ Environment: (was: Sorting with CartridgeAddRemovePriorityComparator implies that cartridges should be stored in IApplication in a specific order, for instance, "mysql" should precede all other cartridges. If Edit Embedded Cartridges wizard is run once, the desirable order is guaranteed. However, if wizard is run twice, with "postgresql" selected on the first run and "mysql" added on the second run, the cartridges will be added to IApplication unsorted by the comparator. ) > Consistency of sorting in EmbedCartridgesJob > -------------------------------------------- > > Key: JBIDE-21137 > URL: https://issues.jboss.org/browse/JBIDE-21137 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Viacheslav Kabanovich > Assignee: Andre Dietisheim > > Sorting with CartridgeAddRemovePriorityComparator implies that cartridges should be stored in IApplication in a specific order, for instance, "mysql" should precede all other cartridges. If Edit Embedded Cartridges wizard is run once, the desirable order is guaranteed. However, if wizard is run twice, with "postgresql" selected on the first run and "mysql" added on the second run, the cartridges will be added to IApplication unsorted by the comparator. -- 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 November 2015