January 2015 - jbosstools-issues - Jboss List Archives

[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 commented on JBDS-3199: ----------------------------------- [~manaRH] : when will WFK 2.7 be released? [~rafabene] : I assume this is also fixed in the wildfly archetype > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18692) Jenkins build for jbosstools-incubator-ripple

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18692?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18692: ---------------------------------------- Yep, this job should deploy changes to Nexus. PR for aerogear doesn't require new changes. > Jenkins build for jbosstools-incubator-ripple > --------------------------------------------- > > Key: JBIDE-18692 > URL: https://issues.jboss.org/browse/JBIDE-18692 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > We need a jenkins job to build for jbosstools-incubator-ripple, and have it > invoking "./configure && jake" and distribute the builds to Nexus so that cordovasim can start using ripple from this repo. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ] Rafael Benevides commented on JBDS-3199: ---------------------------------------- [~manaRH] fixed this with this commit: https://github.com/jboss-developer/jboss-wfk-archetypes/commit/0dac5f4192... > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18096) could not complete update project configuration - illegalargumentexception

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18096?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18096: -------------------------------- Fix Version/s: 4.3.0.Alpha1 > could not complete update project configuration - illegalargumentexception > -------------------------------------------------------------------------- > > Key: JBIDE-18096 > URL: https://issues.jboss.org/browse/JBIDE-18096 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Labels: f2f2014 > Fix For: 4.3.0.Alpha1 > > > while trying to fix import of javaee-samples I bumped into this happening when running update project configuration. > java.lang.IllegalArgumentException > at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.removeProjectFacet(FacetedProjectWorkingCopy.java:876) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:309) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339) > at org.eclipse.m2e.wtp.WebProjectConfiguratorDelegate.configure(WebProjectConfiguratorDelegate.java:150) > at org.eclipse.m2e.wtp.AbstractProjectConfiguratorDelegate.configureProject(AbstractProjectConfiguratorDelegate.java:93) > at org.eclipse.m2e.wtp.WTPProjectConfigurator.configure(WTPProjectConfigurator.java:70) > at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:408) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:321) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96) > at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1344) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:318) > at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:77) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > It happened on ~100 projects so was quite invasive ;/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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: ------------------------------ Fix Version/s: 8.1.0.GA > 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, 3 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: ------------------------------ Target Release: 8.1.0.GA (was: 8.0.1.GA) > 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 > > 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, 3 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.Alpha1 > 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.Alpha1 > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3273: ------------------------------ Fix Version/s: 9.0.0.Beta1 > JBoss Central: Automatic upstream quickstart integration > --------------------------------------------------------- > > Key: JBDS-3273 > URL: https://issues.jboss.org/browse/JBDS-3273 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 9.0.0.Beta1 > > > Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18692) Jenkins build for jbosstools-incubator-ripple

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18692?page=com.atlassian.jira.plugi... ] Ilya Buziuk edited comment on JBIDE-18692 at 1/15/15 9:50 AM: -------------------------------------------------------------- [~mickael_istria] great job. Thanks for your help ;-) misunderstand about jenkins :/ one question: does https://github.com/jbosstools/jbosstools-aerogear/pull/92 need update? was (Author: ibuziuk): [~mickael_istria] great job. Thanks for your help ;-) < Ability to deploy requires additional permission, and it's usually done by Jenkins. Is it enough for you? It's fine for me for local development. But the question is who will deploy stuff? And one more question: does https://github.com/jbosstools/jbosstools-aerogear/pull/92 need update? > Jenkins build for jbosstools-incubator-ripple > --------------------------------------------- > > Key: JBIDE-18692 > URL: https://issues.jboss.org/browse/JBIDE-18692 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > We need a jenkins job to build for jbosstools-incubator-ripple, and have it > invoking "./configure && jake" and distribute the builds to Nexus so that cordovasim can start using ripple from this repo. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3263) Remove JSF Visual/Source and Preview Tabs

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3263?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3263: -------------------------------- > Remove JSF Visual/Source and Preview Tabs > ----------------------------------------- > > Key: JBDS-3263 > URL: https://issues.jboss.org/browse/JBDS-3263 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: visual-page-editor-core > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Fix For: 9.0.0.Alpha1 > > > Removal of the Visual/Source and Preview tabs, which normally provide an error message as it does not run on 64-bit JVMs. > http://www.screencast.com/t/wettTf6s6cU > http://www.screencast.com/t/zur1sCXmZ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 January 2015