August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20095) Application wizard: openshift template does not warn/errror on required values

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20095?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20095. --------------------------------- Resolution: Done Works in OSX > Application wizard: openshift template does not warn/errror on required values > ------------------------------------------------------------------------------ > > Key: JBIDE-20095 > URL: https://issues.jboss.org/browse/JBIDE-20095 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Labels: application_wizard, new_and_noteworthy, openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: eap6-basic-sti.json, required-value-missing.png, required-value-present.png > > > using https://github.com/jboss-openshift/application-templates/blob/master/eap/... (v1beta3) a lot of variables are shown, click next/next and all is created except build configs stating "values are required" > 1) why am I not warned *Before* starting to create things ? > 2) why cannot undo/delete the things that was created but now useless since buildconfig not created ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3465) Consider using SpringIDE 3.7 (or 3.6.4?)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3465?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3465: ---------------------------------- You asked "What are we actually dragging in and why does springIDE needs .core from yedit but not the rest ?" I listed what we are actually dragging in (it's those 3 new plugins), and explained why. Restating: The reason is that the features that we include in Central (same list as previous years) *now depend* on new upstream 3rd party plugins (Spring's features now include a yaml editor). That's what I explained above. * org.springframework.ide.eclipse.boot.properties.editor.yaml (part of *o.sf.ide.eclipse.feature*) depends on org.dadacoalition.yedit and org.yaml.snakeyaml * org.springframework.web (part of *o.sf.ide.eclipse.webflow.feature*, included in Central) depends on com.google.protobuf *H* ope *T* hat *H* elps! ( http://www.urbandictionary.com/define.php?term=HTH ) > Consider using SpringIDE 3.7 (or 3.6.4?) > ---------------------------------------- > > Key: JBDS-3465 > URL: https://issues.jboss.org/browse/JBDS-3465 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, target-platform > Affects Versions: 9.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Marián Labuda > Fix For: 9.0.0.CR1 > > Attachments: install-spring-all-features.png, install-spring-sites.png > > > There are new versions of SpringIDE available: > {code:title=http://dist.springsource.com/release/TOOLS/update/e4.5} > org.springframework.ide.eclipse.feature.feature.group 3.6.4.201503051146-RELEASE{code} > {code:title=http://dist.springsource.com/snapshot/TOOLS/nightly/e4.5} > org.springframework.ide.eclipse.feature.feature.group 3.7.0.201506181755-CI-B262{code} > Which would we like to include in Central? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20187) "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20187?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20187. ------------------------------ I've run the script without errors. Closing. Verified in Beta2b. > "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20187 > URL: https://issues.jboss.org/browse/JBIDE-20187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Beta1 > Reporter: Misha Ali > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.0.Beta2 > > > I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. > Steps to reproduce: > 1. Follow the steps here: https://access.redhat.com/articles/1367643 > Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux > The step where a groovy script is run results in the following output, which ends with an error: > << internal link removed >> Error is available here: http://pastebin.com/3XKt9x5i > Please let me know if any further information is required for this bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20438) Use of clientBehavior tag in composite component produces warning

by Rainer Schön (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20438?page=com.atlassian.jira.plugi... ] Rainer Schön commented on JBIDE-20438: -------------------------------------- Hi Viacheslav Thanks for the hint. Quite right, I used the first one, with the latter everything works correctly. Sorry for taking your time. Rainer > Use of clientBehavior tag in composite component produces warning > ------------------------------------------------------------------ > > Key: JBIDE-20438 > URL: https://issues.jboss.org/browse/JBIDE-20438 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.2.3.Final > Environment: Win 7 64, Eclipse Luna 64, JDK8 64 > Reporter: Rainer Schön > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.3.x > > > The use of a clientBehavior tag in a composite component produces a [Unknown composite component "clientBehavior"] warning > Possible solution: Check the jboss internal tagblib: composite.taglib.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20446) Hibernate 5.0 support

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20446?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20446: ---------------------------------------- OK. Taking into account your PTO this month it doesn't look we can do it for 9.0.0 to me. > Hibernate 5.0 support > --------------------- > > Key: JBIDE-20446 > URL: https://issues.jboss.org/browse/JBIDE-20446 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.3.0.Beta2 > Environment: JBDS 9.0.0.Beta2 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.3.x > > > Hibernate 5.0 is close to be released (CR4 at the time of writing this JIRA). JBoss Tools Hibernate Tools should support this latest version. Would be good to have it in JBDS 9.0.GA at least in form of early access or experimental feature. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20446) Hibernate 5.0 support

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20446?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20446: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.CR1) > Hibernate 5.0 support > --------------------- > > Key: JBIDE-20446 > URL: https://issues.jboss.org/browse/JBIDE-20446 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.3.0.Beta2 > Environment: JBDS 9.0.0.Beta2 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.3.x > > > Hibernate 5.0 is close to be released (CR4 at the time of writing this JIRA). JBoss Tools Hibernate Tools should support this latest version. Would be good to have it in JBDS 9.0.GA at least in form of early access or experimental feature. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20352) Projects wizard: Error show up when creating a new project on staging OpenShift v3

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20352?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-20352: ---------------------------------- Fix Version/s: 4.3.0.Beta2 > Projects wizard: Error show up when creating a new project on staging OpenShift v3 > ---------------------------------------------------------------------------------- > > Key: JBIDE-20352 > URL: https://issues.jboss.org/browse/JBIDE-20352 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Environment: built from branch jbosstools-4.3.0.Beta2x with latest commit latest commit 9a8e8785b0 (JBIDE-19335 Revert API changes in BrowserUtility.java) > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Blocker > Labels: projects_wizard, respin-a > Fix For: 4.3.0.Beta2 > > Attachments: project-created.png > > > When trying to create a new project on a OpenShift v3 stg connection, there is an following error and no project is created: > {code} > An internal error occurred during: "Creating project project033...". > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizard$1.doRun(NewProjectWizard.java:52) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20352) Projects wizard: Error show up when creating a new project on staging OpenShift v3

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20352?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20352. --------------------------------- Was verified in JBDS 9.0.0.Beta2 respin-b. > Projects wizard: Error show up when creating a new project on staging OpenShift v3 > ---------------------------------------------------------------------------------- > > Key: JBIDE-20352 > URL: https://issues.jboss.org/browse/JBIDE-20352 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Environment: built from branch jbosstools-4.3.0.Beta2x with latest commit latest commit 9a8e8785b0 (JBIDE-19335 Revert API changes in BrowserUtility.java) > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Blocker > Labels: projects_wizard, respin-a > Fix For: 4.3.0.Beta2 > > Attachments: project-created.png > > > When trying to create a new project on a OpenShift v3 stg connection, there is an following error and no project is created: > {code} > An internal error occurred during: "Creating project project033...". > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizard$1.doRun(NewProjectWizard.java:52) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20417) NPE while trying to create an OpenShift project

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20417?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-20417: --------------------------------------- It is because of access (authorization). User you are using does not have rights to create a new project, because cluster is something like top level access. We were having some issues related to scope of user/access rights/authorization because of cluster and there were done some fixes over time, but it seems that it is still happening :-/ > NPE while trying to create an OpenShift project > ----------------------------------------------- > > Key: JBIDE-20417 > URL: https://issues.jboss.org/browse/JBIDE-20417 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: openshift_v3 > Fix For: 4.3.0.CR1 > > > I'm running OS3 as a vagrant image (https://github.com/jcantrill/jctoolbox/blob/jimmi_based_box/openshift/Vag...) > When trying to create an openshift project, I get an exception when clicking finish : > !http://content.screencast.com/users/fbricon/folders/Jing/media/2ce1f1c3-892d-4f25-a991-bba7af592aa5/00000136.png|width=600! > {noformat} > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizard$1.doRun(NewProjectWizard.java:52) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > The NPE actually occurs in a catch block, where e.getStatus() is null: > {code} > } catch (OpenShiftException e) { > return OpenShiftUIActivator.statusFactory().errorStatus( > NLS.bind("Could not create project \"{0}\": {1}", getModel().getProjectName(), e.getStatus().getMessage()), e); > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20455) Preferences: "Browse" ("oc" location) opens home-dir even if I have an "oc" path set

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20455?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20455: ------------------------------------- Summary: Preferences: "Browse" ("oc" location) opens home-dir even if I have an "oc" path set (was: Preferences: "Browse" (oc location) opens home-dir even if I have a oc path set) > Preferences: "Browse" ("oc" location) opens home-dir even if I have an "oc" path set > ------------------------------------------------------------------------------------ > > Key: JBIDE-20455 > URL: https://issues.jboss.org/browse/JBIDE-20455 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.CR1 > > > Steps: > # EXEC: open preferences, go to "OpenShift v3", "Browse", choose some file (valid or invalid) > # ASSERT: path is shown in "oc location" > # EXEC: hit "Browse" > Result: > The filedialog is opened in your home directory > Expected result: > The filedialog should get opened for the directory/file that is set in the "oc location" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 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 August 2015