[JBoss JIRA] (JBIDE-14854) Compilation errors in org.jboss.tools.vpe.browsersim
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14854?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich commented on JBIDE-14854:
------------------------------------------
Same problems with some CordovaSim files. The reason of these errors is that on Windows git does not see files with different cases.
> Compilation errors in org.jboss.tools.vpe.browsersim
> ----------------------------------------------------
>
> Key: JBIDE-14854
> URL: https://issues.jboss.org/browse/JBIDE-14854
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 4.1.0.Beta2
> Reporter: Alexey Kazakov
> Assignee: Yahor Radtsevich
> Priority: Blocker
> Fix For: 4.1.0.Beta2
>
>
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.17.0:compile (default-compile) on project org.jboss.tools.vpe.browsersim: Compilation failure: Compilation failure:
> [ERROR] /home/igels/Projects/jbt-4.0/contribution/jbosstools-vpe/plugins/org.jboss.tools.vpe.browsersim/src/org/jboss/tools/vpe/browsersim/model/preferences/BrowsersimSpecificPreferencesStorage.java:[36,0]
> [ERROR] public class BrowserSimSpecificPreferencesStorage extends SpecificPreferencesStorage{
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The public type BrowserSimSpecificPreferencesStorage must be defined in its own file
> [ERROR] /home/igels/Projects/jbt-4.0/contribution/jbosstools-vpe/plugins/org.jboss.tools.vpe.browsersim/src/org/jboss/tools/vpe/browsersim/model/preferences/BrowserSimSpecificPreferencesStorage.java:[36,0]
> [ERROR] public class BrowserSimSpecificPreferencesStorage extends SpecificPreferencesStorage{
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The type BrowserSimSpecificPreferencesStorage is already defined
> [ERROR] /home/igels/Projects/jbt-4.0/contribution/jbosstools-vpe/plugins/org.jboss.tools.vpe.browsersim/src/org/jboss/tools/vpe/browsersim/model/preferences/BrowsersimSpecificPreferences.java:[18,0]
> [ERROR] public class BrowserSimSpecificPreferences extends SpecificPreferences{
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The type BrowserSimSpecificPreferences is already defined
> [ERROR] 3 problems (3 errors)
> [ERROR] -> [Help 1]
> {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-14854) Compilation errors in org.jboss.tools.vpe.browsersim
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14854?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich updated JBIDE-14854:
-------------------------------------
Assignee: Yahor Radtsevich (was: Alexey Kazakov)
> Compilation errors in org.jboss.tools.vpe.browsersim
> ----------------------------------------------------
>
> Key: JBIDE-14854
> URL: https://issues.jboss.org/browse/JBIDE-14854
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 4.1.0.Beta2
> Reporter: Alexey Kazakov
> Assignee: Yahor Radtsevich
> Priority: Blocker
> Fix For: 4.1.0.Beta2
>
>
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.17.0:compile (default-compile) on project org.jboss.tools.vpe.browsersim: Compilation failure: Compilation failure:
> [ERROR] /home/igels/Projects/jbt-4.0/contribution/jbosstools-vpe/plugins/org.jboss.tools.vpe.browsersim/src/org/jboss/tools/vpe/browsersim/model/preferences/BrowsersimSpecificPreferencesStorage.java:[36,0]
> [ERROR] public class BrowserSimSpecificPreferencesStorage extends SpecificPreferencesStorage{
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The public type BrowserSimSpecificPreferencesStorage must be defined in its own file
> [ERROR] /home/igels/Projects/jbt-4.0/contribution/jbosstools-vpe/plugins/org.jboss.tools.vpe.browsersim/src/org/jboss/tools/vpe/browsersim/model/preferences/BrowserSimSpecificPreferencesStorage.java:[36,0]
> [ERROR] public class BrowserSimSpecificPreferencesStorage extends SpecificPreferencesStorage{
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The type BrowserSimSpecificPreferencesStorage is already defined
> [ERROR] /home/igels/Projects/jbt-4.0/contribution/jbosstools-vpe/plugins/org.jboss.tools.vpe.browsersim/src/org/jboss/tools/vpe/browsersim/model/preferences/BrowsersimSpecificPreferences.java:[18,0]
> [ERROR] public class BrowserSimSpecificPreferences extends SpecificPreferences{
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The type BrowserSimSpecificPreferences is already defined
> [ERROR] 3 problems (3 errors)
> [ERROR] -> [Help 1]
> {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-14854) Compilation errors in org.jboss.tools.vpe.browsersim
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14854?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich updated JBIDE-14854:
-------------------------------------
Assignee: Alexey Kazakov
> Compilation errors in org.jboss.tools.vpe.browsersim
> ----------------------------------------------------
>
> Key: JBIDE-14854
> URL: https://issues.jboss.org/browse/JBIDE-14854
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 4.1.0.Beta2
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Priority: Blocker
> Fix For: 4.1.0.Beta2
>
>
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.17.0:compile (default-compile) on project org.jboss.tools.vpe.browsersim: Compilation failure: Compilation failure:
> [ERROR] /home/igels/Projects/jbt-4.0/contribution/jbosstools-vpe/plugins/org.jboss.tools.vpe.browsersim/src/org/jboss/tools/vpe/browsersim/model/preferences/BrowsersimSpecificPreferencesStorage.java:[36,0]
> [ERROR] public class BrowserSimSpecificPreferencesStorage extends SpecificPreferencesStorage{
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The public type BrowserSimSpecificPreferencesStorage must be defined in its own file
> [ERROR] /home/igels/Projects/jbt-4.0/contribution/jbosstools-vpe/plugins/org.jboss.tools.vpe.browsersim/src/org/jboss/tools/vpe/browsersim/model/preferences/BrowserSimSpecificPreferencesStorage.java:[36,0]
> [ERROR] public class BrowserSimSpecificPreferencesStorage extends SpecificPreferencesStorage{
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The type BrowserSimSpecificPreferencesStorage is already defined
> [ERROR] /home/igels/Projects/jbt-4.0/contribution/jbosstools-vpe/plugins/org.jboss.tools.vpe.browsersim/src/org/jboss/tools/vpe/browsersim/model/preferences/BrowsersimSpecificPreferences.java:[18,0]
> [ERROR] public class BrowserSimSpecificPreferences extends SpecificPreferences{
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The type BrowserSimSpecificPreferences is already defined
> [ERROR] 3 problems (3 errors)
> [ERROR] -> [Help 1]
> {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-14305) Error popup when runing schema ddl with Hibernate Configurations
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14305?page=com.atlassian.jira.plugi... ]
Koen Aers resolved JBIDE-14305.
-------------------------------
Fix Version/s: 4.1.0.Beta2
(was: 4.1.0.CR1)
Resolution: Cannot Reproduce Bug
Great! Thanks for reporting back!
> 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.Beta2
>
>
> 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 Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14660?page=com.atlassian.jira.plugi... ]
Stefan Bunciak reassigned JBIDE-14660:
--------------------------------------
Assignee: Andre Dietisheim (was: Stefan Bunciak)
Assigning back to DEV.
> 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: Andre Dietisheim
> 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 Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14660?page=com.atlassian.jira.plugi... ]
Stefan Bunciak commented on JBIDE-14660:
----------------------------------------
I've installed JBoss Tools 4.1.0.Beta1 to Eclipse Kepler RC3 and was not able to reproduce this issue.
> 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-14858) Wildfly needs to be started using java7
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-14858:
--------------------------------------
Summary: Wildfly needs to be started using java7
Key: JBIDE-14858
URL: https://issues.jboss.org/browse/JBIDE-14858
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, server
Reporter: Mickael Istria
Assignee: Nick Boldt
Wildfly needs to be started using Java 7. However, JBT/JBDS needs to work on Java 6, so it seems necessary to
* Use path to a Java7 to start Wildfly
* Pass this path to Java7 in job config.
--
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-14292) Link under 'Other resources' on JBoss Central is incorrect for JBDS
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14292?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-14292:
-----------------------------------
Assignee: Max Rydahl Andersen (was: Fred Bricon)
Assigning to [~maxandersen] as I don't have god power to write directly to the jbds repos
> Link under 'Other resources' on JBoss Central is incorrect for JBDS
> -------------------------------------------------------------------
>
> Key: JBIDE-14292
> URL: https://issues.jboss.org/browse/JBIDE-14292
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha2
> Reporter: Michelle Murray
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Beta2
>
>
> I realise that JBoss Central is still under development but I wanted to point out an issue. Under 'Other resources' there is a link titled 'Product documentation' that links to http://docs.jboss.org/tools/latest/.
> 1. Is this the right link for community docs? /tools/latest will store documentation under development for the next release. Should this link point to the community docs for the version of JBT installed (for example, tools/4.1.0 for JBT 4.1.0)? There is ongoing debate about what exactly the link will be - see TOOLSDOC-310.
> 2. This link does not point to the right place for JBDS users. JBDS documentation is stored here: https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ So how can the issue of two separate documentation locations for JBT and JBDS be got around?
--
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-14292) Link under 'Other resources' on JBoss Central is incorrect for JBDS
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14292?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-14292:
-------------------------------------
Scratch my last comment. I need to wake up. Didn't realized the link to JBDS actually changed.
> Link under 'Other resources' on JBoss Central is incorrect for JBDS
> -------------------------------------------------------------------
>
> Key: JBIDE-14292
> URL: https://issues.jboss.org/browse/JBIDE-14292
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha2
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Fix For: 4.1.0.Beta2
>
>
> I realise that JBoss Central is still under development but I wanted to point out an issue. Under 'Other resources' there is a link titled 'Product documentation' that links to http://docs.jboss.org/tools/latest/.
> 1. Is this the right link for community docs? /tools/latest will store documentation under development for the next release. Should this link point to the community docs for the version of JBT installed (for example, tools/4.1.0 for JBT 4.1.0)? There is ongoing debate about what exactly the link will be - see TOOLSDOC-310.
> 2. This link does not point to the right place for JBDS users. JBDS documentation is stored here: https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ So how can the issue of two separate documentation locations for JBT and JBDS be got around?
--
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