[JBoss JIRA] (JBIDE-15575) Creation of foundation.ui to hold TaskWizard framework
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15575?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-15575.
---------------------------------
Resolution: Done
merged in.
> Creation of foundation.ui to hold TaskWizard framework
> ------------------------------------------------------
>
> Key: JBIDE-15575
> URL: https://issues.jboss.org/browse/JBIDE-15575
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.2.0.Alpha1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.2.0.Alpha1
>
>
> Creation of a foundation.ui is required for a few reasons:
> 1) runtimes should not depend on common. A foundation.ui is needed for that
> 2) Hold taskwizard, a framework from wtp internals which is very very useful and many have expressed interest in using. Runtimes will be using this framework very soon and others will convert in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15577) Hibernate Console problem while creating session factory
by Guillaume JOUVELOT (JIRA)
Guillaume JOUVELOT created JBIDE-15577:
------------------------------------------
Summary: Hibernate Console problem while creating session factory
Key: JBIDE-15577
URL: https://issues.jboss.org/browse/JBIDE-15577
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate, testing-tools
Affects Versions: 4.2.x
Environment: Eclipse 4.3 (kepler), hibernate tools 3.7.0, Hibernate 4.2.2, jdk1.6.0.38
Reporter: Guillaume JOUVELOT
When I try to use hibernate console in order to test HQL queries I've the following error message from eclipse :
{color:red}java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;{color}
And the eclipse log file :
!ENTRY org.hibernate.eclipse.console 4 4 2013-09-27 15:57:20.198
!MESSAGE Problems while creating sessionfactory
!SUBENTRY 1 org.hibernate.eclipse.console 4 150 2013-09-27 15:57:20.198
!MESSAGE java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;
!STACK 0
java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;
at org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider.<clinit>(C3P0ConnectionProvider.java:58)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at org.hibernate.connection.ConnectionProviderFactory.initializeConnectionProviderFromConfig(ConnectionProviderFactory.java:174)
at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:102)
at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:84)
at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:438)
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:91)
at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2163)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2159)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1383)
at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954)
at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:278)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:107)
at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:273)
at org.hibernate.eclipse.console.workbench.LazySessionFactoryAdapter.getChildren(LazySessionFactoryAdapter.java:43)
at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100)
at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
!SUBENTRY 2 org.hibernate.eclipse.console 4 150 2013-09-27 15:57:20.198
!MESSAGE java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;
!STACK 0
java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;
at org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider.<clinit>(C3P0ConnectionProvider.java:58)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at org.hibernate.connection.ConnectionProviderFactory.initializeConnectionProviderFromConfig(ConnectionProviderFactory.java:174)
at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:102)
at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:84)
at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:438)
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:91)
at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2163)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2159)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1383)
at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954)
at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:278)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:107)
at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:273)
at org.hibernate.eclipse.console.workbench.LazySessionFactoryAdapter.getChildren(LazySessionFactoryAdapter.java:43)
at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100)
at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
I've well configured my session factory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2767 at 9/27/13 9:18 AM:
-----------------------------------------------------------
PRs applied - sorry about that typo, and thanks for the fix.
Spinning https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=385
was (Author: nickboldt):
PRs applied - sorry about that typo, and thanks for the fix.
> Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection
> ---------------------------------------------------------------------
>
> Key: JBDS-2767
> URL: https://issues.jboss.org/browse/JBDS-2767
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: servers, updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 7.1.0.Alpha2
>
> Attachments: 15498.png
>
>
> Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0.
> Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances.
> Original from Nick:
> Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7.
> Comparing the update sites for JBT 4.1.x and JBDS 7.1.x:
> !15498.png!
> Was it intentionally excluded from the update site, or forgotten?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2767:
----------------------------------
PRs applied - sorry about that typo, and thanks for the fix.
> Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection
> ---------------------------------------------------------------------
>
> Key: JBDS-2767
> URL: https://issues.jboss.org/browse/JBDS-2767
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: servers, updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 7.1.0.Alpha2
>
> Attachments: 15498.png
>
>
> Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0.
> Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances.
> Original from Nick:
> Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7.
> Comparing the update sites for JBT 4.1.x and JBDS 7.1.x:
> !15498.png!
> Was it intentionally excluded from the update site, or forgotten?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15261) Cannot create wordpress example
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15261?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15261:
-------------------------------------
Labels: new_and_noteworthy (was: )
> Cannot create wordpress example
> -------------------------------
>
> Key: JBIDE-15261
> URL: https://issues.jboss.org/browse/JBIDE-15261
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: nan wei
> Assignee: Max Rydahl Andersen
> Labels: new_and_noteworthy
> Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1
>
> Attachments: create-wordpress-example.png, initial-build-failed.png
>
>
> Version:
> JBoss Deverloper Studio 7 Beta
> OpenShift Plugin: 2.5.0.Beta2-v20130621-1052-B65
> OpenShift Enterprise 1.2/2013-07-18.4
> How reproducible:
> always
> Steps to Reproduce:
> 1. Create an app in the JBoss Deverloper Studio.
> Name: mysqltest
> Type: PHP 5.3(php-5.3)
> Embeddable Cartridges: MySQL Database 5.1(mysql-5.1)
> 2. Click Advanced
> Add Source Code:https://github.com/openshift/wordpress-example
> !create-wordpress-example.png!
> Actual results:
> When creating an app, check mysql cartridge and add source code together, it will fail, and return the following error:
> !initial-build-failed.png!
> {code}
> Could not create application "a3"
> Could not request https://broker.ose0717.com/broker/rest/domains/nwei/applications: The initial build for the application failed. Last 10 kB of build output:
> httpd (no pid file) not running
> Could not find mysql database. Please run:
> rhc cartridge add -a a3 -c mysql-5.1
> then make a sample commit (add whitespace somewhere) and re-push
> An error occurred executing 'gear postreceive'
> For more details about the problem, try running the command again with the '--trace' option.
> {code}
> But if use rhc client, there is no such problem, it is created successfully.
> # rhc app create mysqltest1 php-5.3 mysql-5.1 --from-code=https://github.com/openshift/wordpress-example
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months