[JBoss JIRA] (JBIDE-14582) VJET context menu in OpenShift Explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14582?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14582:
-------------------------------------
Description:
After installing Eclipse VJET from JBoss Central:
!openshift_vjet.png|thumbnail!
steps to reproduce:
# ASSERT: make sure you have VJET installed
# ASSERT: make sure you have OpenShift Exlorer openened
# ASSERT: make sure you dont have ANY item selected in OpenShift
# EXEC: open up context menu
Result:
!openshift_vjet.png|thumbnail!
was:
After installing Eclipse VJET from JBoss Central:
!openshift_vjet.png|thumbnail!
> VJET context menu in OpenShift Explorer
> ---------------------------------------
>
> Key: JBIDE-14582
> URL: https://issues.jboss.org/browse/JBIDE-14582
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta2
>
> Attachments: openshift_vjet.png
>
>
> After installing Eclipse VJET from JBoss Central:
> !openshift_vjet.png|thumbnail!
> steps to reproduce:
> # ASSERT: make sure you have VJET installed
> # ASSERT: make sure you have OpenShift Exlorer openened
> # ASSERT: make sure you dont have ANY item selected in OpenShift
> # EXEC: open up context menu
> Result:
> !openshift_vjet.png|thumbnail!
--
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, 10 months
[JBoss JIRA] (JBIDE-14305) Error popup when runing schema ddl with Hibernate Configurations
by labdoui labdoui (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14305?page=com.atlassian.jira.plugi... ]
labdoui labdoui commented on JBIDE-14305:
-----------------------------------------
Hi Koen,
I've resolved the probleme by updating SLF4J (I'm using 1.5.8 version).$
Thnak you so much
> Error popup when runing schema ddl with Hibernate Configurations
> -----------------------------------------------------------------
>
> Key: JBIDE-14305
> URL: https://issues.jboss.org/browse/JBIDE-14305
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Reporter: labdoui labdoui
> Assignee: Koen Aers
> Priority: Minor
> Fix For: 4.1.0.CR1
>
>
> Using Hibernate 4, and slf4j 1.7.2, I can't runing my ddl schema
> to reproduce the problem just explore the database from hibernate console
> java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V
> at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:133)
> at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:26)
> at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476)
> at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:116)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:107)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:63)
> 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:54)
--
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, 10 months
[JBoss JIRA] (JBIDE-14660) project facet error after importing openshift application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14660?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14660:
------------------------------------------
In JBIDE-13989 Denis found out that he could not reproduce it with the latest RC3 Kepler. [~sbunciak] could you please verify if you can reproduce it in OpenShift once we use the latest Kepler RC3?
> project facet error after importing openshift application
> ---------------------------------------------------------
>
> Key: JBIDE-14660
> URL: https://issues.jboss.org/browse/JBIDE-14660
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta1
> Reporter: Stefan Bunciak
> Assignee: Denis Golovin
> Fix For: 4.1.0.Beta2
>
> Attachments: openshift_id, openshift_id.pub
>
>
> User is not affected but in error log and workspace log an error messages are present:
> {code}
> !ENTRY org.eclipse.jst.j2ee 4 0 2013-05-28 10:26:43.097
> !MESSAGE Version 7.0 of project facet jst.appclient does not exist.
> !STACK 0
> java.lang.IllegalArgumentException: Version 7.0 of project facet jst.appclient does not exist.
> at org.eclipse.wst.common.project.facet.core.util.internal.Versionable.getVersion(Versionable.java:80)
> at org.eclipse.wst.common.project.facet.core.internal.ProjectFacet.getVersion(ProjectFacet.java:1)
> at org.eclipse.jst.j2ee.model.J2EEModelProviderRegistry.readElement(J2EEModelProviderRegistry.java:85)
> at org.eclipse.wst.common.core.util.RegistryReader.internalReadElement(RegistryReader.java:81)
> at org.eclipse.wst.common.core.util.RegistryReader.readRegistry(RegistryReader.java:122)
> at org.eclipse.jst.j2ee.model.J2EEModelProviderRegistry.getInstance(J2EEModelProviderRegistry.java:43)
> at org.eclipse.jst.j2ee.model.ModelProviderManager.initProviders(ModelProviderManager.java:262)
> at org.eclipse.jst.j2ee.model.ModelProviderManager.getProviders(ModelProviderManager.java:338)
> at org.eclipse.jst.j2ee.model.ModelProviderManager.getProvider(ModelProviderManager.java:223)
> at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProvider(ModelProviderManager.java:93)
> at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProvider(ModelProviderManager.java:281)
> at org.eclipse.jst.ws.jaxrs.core.internal.project.facet.JAXRSUtils.getModelProvider(JAXRSUtils.java:83)
> at org.eclipse.jst.ws.jaxrs.core.internal.project.facet.JAXRSFacetInstallDelegate.execute(JAXRSFacetInstallDelegate.java:97)
> 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.wst.common.project.facet.core.internal.FacetedProject.installProjectFacet(FacetedProject.java:255)
> at org.eclipse.m2e.wtp.jaxrs.internal.configurators.JaxRsProjectConfigurator.installJaxRsFacet(JaxRsProjectConfigurator.java:128)
> at org.eclipse.m2e.wtp.jaxrs.internal.configurators.JaxRsProjectConfigurator.configureInternal(JaxRsProjectConfigurator.java:94)
> at org.eclipse.m2e.wtp.jaxrs.internal.configurators.JaxRsProjectConfigurator.configure(JaxRsProjectConfigurator.java:64)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:109)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:457)
> 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:450)
> 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.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.project.MavenProjectImportOperation.importToWorkspace(MavenProjectImportOperation.java:51)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.ImportNewProject.importProjectsFrom(ImportNewProject.java:130)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.ImportNewProject.execute(ImportNewProject.java:79)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftExpressApplicationWizardModel.importProject(OpenShiftExpressApplicationWizardModel.java:101)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftExpressApplicationWizard$ImportJob.runInWorkspace(OpenShiftExpressApplicationWizard.java:345)
> 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 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, 10 months
[JBoss JIRA] (JBIDE-14660) project facet error after importing openshift application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14660?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14660:
-------------------------------------
Assignee: Stefan Bunciak (was: Denis Golovin)
> project facet error after importing openshift application
> ---------------------------------------------------------
>
> Key: JBIDE-14660
> URL: https://issues.jboss.org/browse/JBIDE-14660
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta1
> Reporter: Stefan Bunciak
> Assignee: Stefan Bunciak
> Fix For: 4.1.0.Beta2
>
> Attachments: openshift_id, openshift_id.pub
>
>
> User is not affected but in error log and workspace log an error messages are present:
> {code}
> !ENTRY org.eclipse.jst.j2ee 4 0 2013-05-28 10:26:43.097
> !MESSAGE Version 7.0 of project facet jst.appclient does not exist.
> !STACK 0
> java.lang.IllegalArgumentException: Version 7.0 of project facet jst.appclient does not exist.
> at org.eclipse.wst.common.project.facet.core.util.internal.Versionable.getVersion(Versionable.java:80)
> at org.eclipse.wst.common.project.facet.core.internal.ProjectFacet.getVersion(ProjectFacet.java:1)
> at org.eclipse.jst.j2ee.model.J2EEModelProviderRegistry.readElement(J2EEModelProviderRegistry.java:85)
> at org.eclipse.wst.common.core.util.RegistryReader.internalReadElement(RegistryReader.java:81)
> at org.eclipse.wst.common.core.util.RegistryReader.readRegistry(RegistryReader.java:122)
> at org.eclipse.jst.j2ee.model.J2EEModelProviderRegistry.getInstance(J2EEModelProviderRegistry.java:43)
> at org.eclipse.jst.j2ee.model.ModelProviderManager.initProviders(ModelProviderManager.java:262)
> at org.eclipse.jst.j2ee.model.ModelProviderManager.getProviders(ModelProviderManager.java:338)
> at org.eclipse.jst.j2ee.model.ModelProviderManager.getProvider(ModelProviderManager.java:223)
> at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProvider(ModelProviderManager.java:93)
> at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProvider(ModelProviderManager.java:281)
> at org.eclipse.jst.ws.jaxrs.core.internal.project.facet.JAXRSUtils.getModelProvider(JAXRSUtils.java:83)
> at org.eclipse.jst.ws.jaxrs.core.internal.project.facet.JAXRSFacetInstallDelegate.execute(JAXRSFacetInstallDelegate.java:97)
> 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.wst.common.project.facet.core.internal.FacetedProject.installProjectFacet(FacetedProject.java:255)
> at org.eclipse.m2e.wtp.jaxrs.internal.configurators.JaxRsProjectConfigurator.installJaxRsFacet(JaxRsProjectConfigurator.java:128)
> at org.eclipse.m2e.wtp.jaxrs.internal.configurators.JaxRsProjectConfigurator.configureInternal(JaxRsProjectConfigurator.java:94)
> at org.eclipse.m2e.wtp.jaxrs.internal.configurators.JaxRsProjectConfigurator.configure(JaxRsProjectConfigurator.java:64)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:109)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:457)
> 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:450)
> 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.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.project.MavenProjectImportOperation.importToWorkspace(MavenProjectImportOperation.java:51)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.ImportNewProject.importProjectsFrom(ImportNewProject.java:130)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.ImportNewProject.execute(ImportNewProject.java:79)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftExpressApplicationWizardModel.importProject(OpenShiftExpressApplicationWizardModel.java:101)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftExpressApplicationWizard$ImportJob.runInWorkspace(OpenShiftExpressApplicationWizard.java:345)
> 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 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, 10 months
[JBoss JIRA] (JBIDE-14818) there's no "deployments" page for OpenShift that would allow me to rename a module
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14818:
-------------------------------------
Fix Version/s: 4.1.x
(was: 4.1.0.Beta2)
> there's no "deployments" page for OpenShift that would allow me to rename a module
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-14818
> URL: https://issues.jboss.org/browse/JBIDE-14818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.1.x
>
>
> In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment.
--
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, 10 months
[JBoss JIRA] (JBIDE-14818) there's no "deployments" page for OpenShift that would allow me to rename a module
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14818:
------------------------------------------
moving this to 4.1.x since Ron went out of time for this.
> there's no "deployments" page for OpenShift that would allow me to rename a module
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-14818
> URL: https://issues.jboss.org/browse/JBIDE-14818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment.
--
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, 10 months