November 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18216) [Config Editor] Error when adding Plugins from git

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18216?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-18216. ------------------------------- Verified with JBDS 8.0.1.CR1-v20141124-0632-B334 > [Config Editor] Error when adding Plugins from git > -------------------------------------------------- > > Key: JBIDE-18216 > URL: https://issues.jboss.org/browse/JBIDE-18216 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.CR1 > Environment: Linux, JBDS 8.0.0.CR1-v20140831-0335-B201, Mobile tooling installed via JBoss Central > Reporter: Vlado Pakan > Assignee: Gorkem Ercan > Fix For: 4.2.1.CR1 > > > 1. Download ionic-weather example > 2. Import it as cordova project > 3. Open config.xml, Platform Properties tab > 4. Add device plugin via github url > {noformat} > !ENTRY Error invoking the Node constructor for config model object 4 0 2014-09-01 12:28:47.057 > !MESSAGE org.eclipse.thym.core > !STACK 0 > org.eclipse.core.runtime.AssertionFailedException: assertion failed: This operation must be run within the observable's realm > at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110) > at org.eclipse.core.databinding.observable.AbstractObservable.checkRealm(AbstractObservable.java:98) > at org.eclipse.core.databinding.observable.value.AbstractObservableValue.setValue(AbstractObservableValue.java:54) > at org.eclipse.thym.ui.config.internal.EssentialsPage$1.propertyChange(EssentialsPage.java:252) > at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335) > at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:328) > at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:263) > at org.eclipse.thym.core.config.AbstractConfigObject$Property.setValue(AbstractConfigObject.java:44) > at org.eclipse.thym.core.config.Widget.loadItem(Widget.java:111) > at org.eclipse.thym.core.config.Widget.init(Widget.java:94) > at org.eclipse.thym.core.config.Widget.reload(Widget.java:83) > at org.eclipse.thym.core.config.WidgetModel.reloadEditableWidget(WidgetModel.java:230) > at org.eclipse.thym.core.config.WidgetModel.processPostModelEvent(WidgetModel.java:372) > at org.eclipse.wst.sse.core.internal.model.LifecycleNotificationManager.signalLifecycleEvent(LifecycleNotificationManager.java:114) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.signalLifecycleEvent(AbstractStructuredModel.java:1501) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.setDirtyState(AbstractStructuredModel.java:1299) > at org.eclipse.wst.sse.core.internal.FileBufferModelManager$FileBufferMapper.dirtyStateChanged(FileBufferModelManager.java:379) > at org.eclipse.core.internal.filebuffers.TextFileBufferManager$3.run(TextFileBufferManager.java:706) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.filebuffers.TextFileBufferManager.fireDirtyStateChanged(TextFileBufferManager.java:704) > at org.eclipse.core.internal.filebuffers.ResourceFileBuffer.commit(ResourceFileBuffer.java:337) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.saveModel(ModelManagerImpl.java:2054) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.save(AbstractStructuredModel.java:1149) > at org.eclipse.thym.core.config.WidgetModel.save(WidgetModel.java:239) > at org.eclipse.thym.core.plugin.actions.ConfigXMLUpdateAction.install(ConfigXMLUpdateAction.java:70) > at org.eclipse.thym.core.plugin.PluginInstallActionsRunOperation.run(PluginInstallActionsRunOperation.java:69) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295) > at org.eclipse.thym.core.plugin.CordovaPluginManager.runActions(CordovaPluginManager.java:491) > at org.eclipse.thym.core.plugin.CordovaPluginManager.installPlugin(CordovaPluginManager.java:150) > at org.eclipse.thym.core.plugin.CordovaPluginManager.installPlugin(CordovaPluginManager.java:208) > at org.eclipse.thym.ui.plugins.internal.CordovaPluginWizard$PluginInstallOperation.execute(CordovaPluginWizard.java:120) > at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > !ENTRY Parent node could not be retrieved on config.xml with expression /widget/rim:permissions 4 0 2014-09-01 12:28:47.615 > !MESSAGE org.eclipse.thym.core > {noformat} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18732) CordovaSim must save preferences (tabs / settings / etc.)

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18732?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18732: ------------------------------------- [~kaloyan-raev] in this PR I change the default proxy to local, as we have discussed in JBIDE-18404 > CordovaSim must save preferences (tabs / settings / etc.) > --------------------------------------------------------- > > Key: JBIDE-18732 > URL: https://issues.jboss.org/browse/JBIDE-18732 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cordovasim > Affects Versions: 4.2.0.Final, 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > For now all CordovaSim's preferences are hardcoded - https://github.com/jbosstools/incubator-ripple/commit/d2b46fdc5cfa74cc8c6... > CordovaSim must save all user's preferences: tab order, setting, etc. > NOTE: Preferences will *not* be saved for *javaFX* web engine oracle *JDK 7*, due to localstorage absence. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18732) CordovaSim must save preferences (tabs / settings / etc.)

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18732?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18732: ------------------------------------- Ripple specific preferences will be saved on CordovaSim close PR for master - https://github.com/jbosstools/jbosstools-aerogear/pull/91 [~akazakov], [~maxandersen] is this PR save enough for 4.2.1.Final [~vpakan], will you be able to test this stuff before 4.2.1.Final? For now I have checked it only on windows. If we are going to apply it for 4.2.1.Final it will require testing on all platforms > CordovaSim must save preferences (tabs / settings / etc.) > --------------------------------------------------------- > > Key: JBIDE-18732 > URL: https://issues.jboss.org/browse/JBIDE-18732 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cordovasim > Affects Versions: 4.2.0.Final, 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > For now all CordovaSim's preferences are hardcoded - https://github.com/jbosstools/incubator-ripple/commit/d2b46fdc5cfa74cc8c6... > CordovaSim must save all user's preferences: tab order, setting, etc. > NOTE: Preferences will *not* be saved for *javaFX* web engine oracle *JDK 7*, due to localstorage absence. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-358) Use wrapper features to simplify the install and clean up the Marketplace UI?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-358?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-358: ---------------------------------- Part of the reason I thought we were moving to fewer Marketplace entries for IS was because we were ALSO moving to having fewer installers. Seemed logical that we wanted less entry points [1 installer, 1 marketplace entry] for the first rollout, as that would simplify both the QE experience and also that of the user. And I also assumed that we'd want one marketplace entry for JBTIS with all the individual features (like we do for JBT), then one marketplace entry for JBDS IS, with all the individual products (like we do for JBDS, with its single product). TL;DR: I assumed we wanted a parallel release process for JBTIS/JBDSIS as for JBT/JBDS so that we could have a similar user experience for both community and product. Aside: what are discovery centrals? Max, sometimes your clarifications need clarification. :) > Use wrapper features to simplify the install and clean up the Marketplace UI? > ----------------------------------------------------------------------------- > > Key: JBTIS-358 > URL: https://issues.jboss.org/browse/JBTIS-358 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 7.0.3.GA > Reporter: Nick Boldt > Fix For: 7.1.0.GA-JBDSIS > > Attachments: is-marketplace1.png, is-marketplace2.png > > > For 7.1.0, could consider having wrapper features to simplify the install and clean up the Marketplace UI. Doing so would mean instead of a laundry list of features in the UI, we could list only 3 features. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18772: ---------------------------------------- Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Artifact: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3238) Early Access update site is active by default

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3238?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3238: -------------------------------------- Just tried a fresh installation on a fresh workspace and it behaves as expected out of the box. So can't reproduce on my side. However, you may have executed a sequence of installations/EA enablement actions that cause this unexpected behaviour. It would be helpful if you could find the steps to reproduce. If you can't, then it may be that you've used an older workpsace when EA site was accessible (available sites are stored per workspace IIRC). > Early Access update site is active by default > --------------------------------------------- > > Key: JBDS-3238 > URL: https://issues.jboss.org/browse/JBDS-3238 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Environment: JBDS Version: 8.0.0.GA > Build id: GA-v20141020-1042-B317 > Build date: 20141020-1042 > Reporter: Fred Bricon > Assignee: Mickael Istria > Priority: Blocker > > When opening JBDS on a clean new workspace, the early access update site is enabled by default. > Check Preferences > Install/Updates > Available Software sites > or Install New Software > select https://devstudio.redhat.com/earlyaccess/8.0/ > The early access update site should only be active if Early Access is enabled in JBoss Central -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3238) Early Access update site is active by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3238?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3238: ----------------------------------- This is a JDBS installation I haven't tampered yet. See http://screencast.com/t/gSOqFBAnha7 I installed it a few weeks ago, but haven't done anything yet. I can try with a fresher install though > Early Access update site is active by default > --------------------------------------------- > > Key: JBDS-3238 > URL: https://issues.jboss.org/browse/JBDS-3238 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Environment: JBDS Version: 8.0.0.GA > Build id: GA-v20141020-1042-B317 > Build date: 20141020-1042 > Reporter: Fred Bricon > Assignee: Mickael Istria > Priority: Blocker > > When opening JBDS on a clean new workspace, the early access update site is enabled by default. > Check Preferences > Install/Updates > Available Software sites > or Install New Software > select https://devstudio.redhat.com/earlyaccess/8.0/ > The early access update site should only be active if Early Access is enabled in JBoss Central -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3238) Early Access update site is active by default

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3238?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3238: -------------------------------------- Do you mean just after installation, or on a new workspace? Early-Access state is not much something that is related to a specific workspace, but more to the whole installation. So if EA is enabled in some workpsace, and if some EA bundles are installed from a workspace, then EA is normally available for the whole application. > Early Access update site is active by default > --------------------------------------------- > > Key: JBDS-3238 > URL: https://issues.jboss.org/browse/JBDS-3238 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Environment: JBDS Version: 8.0.0.GA > Build id: GA-v20141020-1042-B317 > Build date: 20141020-1042 > Reporter: Fred Bricon > Assignee: Mickael Istria > Priority: Blocker > > When opening JBDS on a clean new workspace, the early access update site is enabled by default. > Check Preferences > Install/Updates > Available Software sites > or Install New Software > select https://devstudio.redhat.com/earlyaccess/8.0/ > The early access update site should only be active if Early Access is enabled in JBoss Central -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3238) Early Access update site is active by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3238?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3238: ----------------------------------- I have : - https://devstudio.redhat.com/earlyaccess/8.0/ - JBoss Developer Studio 8.0 Updates - https://devstudio.redhat.com/updates/8.0/ in that order > Early Access update site is active by default > --------------------------------------------- > > Key: JBDS-3238 > URL: https://issues.jboss.org/browse/JBDS-3238 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Environment: JBDS Version: 8.0.0.GA > Build id: GA-v20141020-1042-B317 > Build date: 20141020-1042 > Reporter: Fred Bricon > Assignee: Mickael Istria > Priority: Blocker > > When opening JBDS on a clean new workspace, the early access update site is enabled by default. > Check Preferences > Install/Updates > Available Software sites > or Install New Software > select https://devstudio.redhat.com/earlyaccess/8.0/ > The early access update site should only be active if Early Access is enabled in JBoss Central -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3238) Early Access update site is active by default

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3238?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3238: ------------------------------------------- what updatesites do you have exactly ? > Early Access update site is active by default > --------------------------------------------- > > Key: JBDS-3238 > URL: https://issues.jboss.org/browse/JBDS-3238 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Environment: JBDS Version: 8.0.0.GA > Build id: GA-v20141020-1042-B317 > Build date: 20141020-1042 > Reporter: Fred Bricon > Assignee: Mickael Istria > Priority: Blocker > > When opening JBDS on a clean new workspace, the early access update site is enabled by default. > Check Preferences > Install/Updates > Available Software sites > or Install New Software > select https://devstudio.redhat.com/earlyaccess/8.0/ > The early access update site should only be active if Early Access is enabled in JBoss Central -- This message was sent by Atlassian JIRA (v6.3.8#6338)

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