February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-14651) Moving Tutorial section according to selected quickstart category

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14651?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-14651: -------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.1.x) > Moving Tutorial section according to selected quickstart category > ----------------------------------------------------------------- > > Key: JBIDE-14651 > URL: https://issues.jboss.org/browse/JBIDE-14651 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Beta1 > Reporter: Radim Hopp > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.0.Beta1 > > > Tutorial section is changing position according to which category is selected in "Start from a sample" section (see screencast: http://youtu.be/YeeA3I2TSN0 ) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2834) NPE when WFK Spring projects are imported

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2834?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2834: ----------------------------------- [~jpeterka] or [~rawagner] : any of you guys can check that one using latest JBDS 8? > NPE when WFK Spring projects are imported > ----------------------------------------- > > Key: JBDS-2834 > URL: https://issues.jboss.org/browse/JBDS-2834 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 7.1.0.CR1 > Environment: JBDS 7.1.0.CR1a, L64, Spring IDE 3.4 installed from JBoss Central > Reporter: Jiri Peterka > Assignee: Fred Bricon > Fix For: 8.x > > > {code} > java.lang.NullPointerException > at org.eclipse.wst.xml.core.internal.document.XMLModelUpdater.replaceSource(XMLModelUpdater.java:1627) > at org.eclipse.wst.xml.core.internal.document.XMLModelUpdater.replaceChild(XMLModelUpdater.java:1585) > at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.childReplaced(DOMModelImpl.java:192) > at org.eclipse.wst.xml.core.internal.document.NodeContainer.notifyChildReplaced(NodeContainer.java:361) > at org.eclipse.wst.xml.core.internal.document.NodeContainer.insertBefore(NodeContainer.java:302) > at org.eclipse.wst.common.internal.emf.utilities.DOMUtilities.insertBeforeNode(DOMUtilities.java:356) > at org.eclipse.wst.common.internal.emf.utilities.DOMUtilities.insertBeforeNodeAndWhitespace(DOMUtilities.java:381) > at org.eclipse.wst.common.internal.emf.resource.EMF2DOMAdapterImpl.primUpdateDOMMultiFeature(EMF2DOMAdapterImpl.java:405) > at org.eclipse.wst.common.internal.emf.resource.EMF2DOMAdapterImpl.updateDOMRootFeature(EMF2DOMAdapterImpl.java:1002) > at org.eclipse.wst.common.internal.emf.resource.EMF2DOMAdapterImpl.primUpdateDOM(EMF2DOMAdapterImpl.java:978) > at org.eclipse.wst.xml.core.internal.emf2xml.EMF2DOMSSEAdapter.updateDOM(EMF2DOMSSEAdapter.java:477) > at org.eclipse.wst.common.internal.emf.resource.EMF2DOMRenderer.createDOMTree(EMF2DOMRenderer.java:129) > at org.eclipse.wst.xml.core.internal.emf2xml.EMF2DOMSSERenderer.createDOMTreeIfNecessary(EMF2DOMSSERenderer.java:194) > at org.eclipse.wst.xml.core.internal.emf2xml.EMF2DOMSSERenderer.doSave(EMF2DOMSSERenderer.java:251) > at org.eclipse.wst.common.internal.emf.resource.TranslatorResourceImpl.doSave(TranslatorResourceImpl.java:190) > at org.eclipse.wst.common.internal.emf.resource.TranslatorResourceImpl.save(TranslatorResourceImpl.java:170) > at org.eclipse.wst.common.internal.emf.resource.ReferencedXMIResourceImpl.saveIfNecessary(ReferencedXMIResourceImpl.java:287) > at org.eclipse.jpt.common.core.internal.resource.xml.AbstractJptXmlResourceProvider.createResourceAndUnderlyingFile(AbstractJptXmlResourceProvider.java:152) > at org.eclipse.jpt.common.core.internal.resource.xml.AbstractJptXmlResourceProvider$CreateFileAndResourceWorkspaceRunnable.run(AbstractJptXmlResourceProvider.java:181) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) > at org.eclipse.jpt.common.core.internal.resource.xml.AbstractJptXmlResourceProvider.createFileAndResource(AbstractJptXmlResourceProvider.java:168) > at org.eclipse.jpt.common.core.internal.operations.AbstractJptFileCreationOperation.createFile(AbstractJptFileCreationOperation.java:94) > at org.eclipse.jpt.common.core.internal.operations.AbstractJptFileCreationOperation.execute(AbstractJptFileCreationOperation.java:48) > at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:385) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) > at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:410) > at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:360) > at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:247) > at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:219) > at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89) > at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:207) > at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createPersistenceXml(JpaFacetInstallDelegate.java:111) > at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createProjectXml(JpaFacetInstallDelegate.java:100) > at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.execute_(JpaFacetInstallDelegate.java:61) > at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetActionDelegate.execute(JpaFacetActionDelegate.java:35) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339) > at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:153) > at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:107) > at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:109) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:472) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:465) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:245) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:159) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:89) > at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1305) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:134) > at org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$1.doCreateMavenProjects(MavenImportWizard.java:172) > at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:74) > at org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$3.runInWorkspace(MavenImportWizard.java:257) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19218) Fix startup extension point error "Attribute 'class' of element 'startup' must be defined"

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19218?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19218: ---------------------------------- Affects Version/s: 4.3.0.Alpha1 > Fix startup extension point error "Attribute 'class' of element 'startup' must be defined" > ------------------------------------------------------------------------------------------ > > Key: JBIDE-19218 > URL: https://issues.jboss.org/browse/JBIDE-19218 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > > Current usage of extension point is not correct. There is no class attribute for startup element and plugin activator class implements IStartup interface. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18982) Refreshing JBoss Central moves the refresh icon to the right in the display

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18982?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18982: -------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.2.3.Beta1) > Refreshing JBoss Central moves the refresh icon to the right in the display > --------------------------------------------------------------------------- > > Key: JBIDE-18982 > URL: https://issues.jboss.org/browse/JBIDE-18982 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Final > Environment: JBDS 8.0.CR2.respin-a > Java 1.7 - OpenJDK > RHEL6 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Fix For: 4.3.0.Beta1 > > Attachments: Screenshot-2.png, Screenshot-3.png, Screenshot-4.png, Screenshot-5.png > > > See the attached screenshots - each time the user presses the refresh icon, the icon is moved more to the right. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18813) Convert JBoss Central to an HTML5 page

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18813?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18813: -------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.2.3.Beta1) > Convert JBoss Central to an HTML5 page > -------------------------------------- > > Key: JBIDE-18813 > URL: https://issues.jboss.org/browse/JBIDE-18813 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.3.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.0.Beta1 > > Attachments: Central Design Concept A.bmml, Central Design Concept A.bmml, Central Design Concept A.png, Central Design Concept B.bmml, Central Design Concept B.bmml, Central Design Concept B.png, JBoss Access Panel Concept.bmml, JBoss Access Panel Concept.png, JBoss Central User Stories and Flows.gliffy, Screen Shot 2015-01-16 at 4.38.58 PM.png > > > Central Page requires new capabilities : > - needs more customization (display content depending on user preferences) > - needs to scale with JBDS-IS, Fuse content > - access to more examples, with filtering capabilities > Given that the existing page is pretty hard to maintain and suffers from scalability/UI bugs, we're heading towards an HTML5 approach : > - use an embedded SWT Browser widget (or Java FX), depending on the platform compatibility > - webpage and its content could be served remotely (as zip), and downloaded locally for offline use. this would give us more flexibility to update the content. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18998) Floating 'Welcome to JBoss' title in Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18998?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18998: -------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.2.3.Beta1) > Floating 'Welcome to JBoss' title in Central > -------------------------------------------- > > Key: JBIDE-18998 > URL: https://issues.jboss.org/browse/JBIDE-18998 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.1.Final > Environment: Linux x86_64 > SWT_GTK3=1 > OpenJDK 7 > Reporter: Denis Golovin > Assignee: Fred Bricon > Fix For: 4.3.0.Beta1 > > Attachments: jumping-weclome.ogg > > > See attached screen recording in [^jumping-weclome.ogg] > "Welcome to JBoss" title moves down and right when mouse is moving over "JBoss Buzz" section. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18733) Replace icon to open additional example by a "More..." link just after top #3

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18733?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18733: -------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.2.3.Beta1) > Replace icon to open additional example by a "More..." link just after top #3 > ----------------------------------------------------------------------------- > > Key: JBIDE-18733 > URL: https://issues.jboss.org/browse/JBIDE-18733 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Final > Reporter: Mickael Istria > Assignee: Fred Bricon > Fix For: 4.3.0.Beta1 > > > The icon to open additional examples is not something that user seem to find easily. Instead, we could think of something simpler such as a "More..." link under the main 3 examples. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19208) BrowserSim New and Noteworthy for 4.3.0.Alpha1

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19208?page=com.atlassian.jira.plugi... ] Ilya Buziuk reassigned JBIDE-19208: ----------------------------------- Assignee: Ilya Buziuk > BrowserSim New and Noteworthy for 4.3.0.Alpha1 > ---------------------------------------------- > > Key: JBIDE-19208 > URL: https://issues.jboss.org/browse/JBIDE-19208 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.3.0.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If BrowserSim is not listed here check if there are issues that should be added and add them. > Document the ones relevant for BrowserSim by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3199) Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ] Fred Bricon resolved JBDS-3199. ------------------------------- Fix Version/s: 8.1.0.Beta1 (was: 8.1.0.GA) Resolution: Partially Completed Projects created for Wildfly and EAP 6.3 use the updated archetypes (resp wildfly 8.2.0 and WFK 2.7.0). Older versions of the runtimes will still target the old (broken) archetypes > Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3199 > URL: https://issues.jboss.org/browse/JBDS-3199 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, upstream > Affects Versions: 8.0.0.GA > Reporter: Len DiMaggio > Assignee: Fred Bricon > Fix For: 8.1.0.Beta1 > > > These "kitchensink" strings are retained: > grep -ir kitchen * > main/resources/META-INF/persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source> > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS" > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: pool-name="kitchensink-quickstart" enabled="true" > test/resources/arquillian-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileTestDS" > test/resources/META-INF/test-persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileTestDS</jta-data-source> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3199) Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3199: ------------------------------ CDW devel_ack: + (was: ?) Status: New (was: New) > Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3199 > URL: https://issues.jboss.org/browse/JBDS-3199 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, upstream > Affects Versions: 8.0.0.GA > Reporter: Len DiMaggio > Assignee: Fred Bricon > Fix For: 8.1.0.GA > > > These "kitchensink" strings are retained: > grep -ir kitchen * > main/resources/META-INF/persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source> > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS" > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: pool-name="kitchensink-quickstart" enabled="true" > test/resources/arquillian-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileTestDS" > test/resources/META-INF/test-persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileTestDS</jta-data-source> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 February 2015