[JBoss JIRA] (JBIDE-14566) Replace .blobstore by siblings in mirrors
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14566?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-14566:
------------------------------------
I think I got all the places where this was missing fixed in master.
> Replace .blobstore by siblings in mirrors
> -----------------------------------------
>
> Key: JBIDE-14566
> URL: https://issues.jboss.org/browse/JBIDE-14566
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.1.0.Beta2
>
>
> Because we've already made some time-consuming mistakes because of invisible .blobstore, it would be more comfortable and less error-prone to have .pack.gz artifacts as siblings rather than in .blobstore.
> The general idea is to have a "template" repository that sets the right properties while mirroring.
--
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 Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14660?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-14660:
---------------------------------------
There is a problem with J2EE metamodel loading and I finally found the way to replicate it even for plain JavaEE IDE Pacakge. Will update JBIDE-13989 and open issue in bugzilla.
> 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-14708) Opening xml files with multiple editor tabs
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14708?page=com.atlassian.jira.plugi... ]
Victor Rubezhny edited comment on JBIDE-14708 at 5/31/13 1:58 PM:
------------------------------------------------------------------
Sorry, was wrong. Looks like any our XML editor isn't activated when opened by double-clicking on a file.
was (Author: vrubezhny):
If you're changing the order of editors start - then it looks like working "ok". I see the only Faces Config Editor has this issue. It looks like Web XML Editor works fine.
> Opening xml files with multiple editor tabs
> -------------------------------------------
>
> Key: JBIDE-14708
> URL: https://issues.jboss.org/browse/JBIDE-14708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: XML Structured Editor
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1
> Reporter: Tomas Remes
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> Create for example new Seam Web Project. At first open web.xml file, then open e.g. faces-config.xml file. In this point I would assume this file active in the view (not the first one) as it was in previous JBDS release. It does not seem to be perspective dependant and I open it from package explorer. Both files opened by JBoss Tools XML Editor.
--
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-14708) Opening xml files with multiple editor tabs
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14708?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-14708:
-----------------------------------------
If you're changing the order of editors start - then it looks like working "ok". I see the only Faces Config Editor has this issue. It looks like Web XML Editor works fine.
> Opening xml files with multiple editor tabs
> -------------------------------------------
>
> Key: JBIDE-14708
> URL: https://issues.jboss.org/browse/JBIDE-14708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: XML Structured Editor
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1
> Reporter: Tomas Remes
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> Create for example new Seam Web Project. At first open web.xml file, then open e.g. faces-config.xml file. In this point I would assume this file active in the view (not the first one) as it was in previous JBDS release. It does not seem to be perspective dependant and I open it from package explorer. Both files opened by JBoss Tools XML Editor.
--
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-14709) Error in server log when redeploying datasource
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14709?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-14709:
-----------------------------------
Fix Version/s: 4.1.x
> Error in server log when redeploying datasource
> ------------------------------------------------
>
> Key: JBIDE-14709
> URL: https://issues.jboss.org/browse/JBIDE-14709
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam 2
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1, EAP 6.1.0.GA
> Reporter: Tomas Remes
> Assignee: Alexey Kazakov
> Fix For: 4.1.x
>
>
> I am not sure, if this problem is related to JBT, but is best reproducible by this way. Steps to reproduce:
> 1. Create and run EAP 6.1.0 server
> 2. Create Seam Web Project (I used MySQL datasource)
> 3. Try to edit newly created datasource file in the project and save it.
> 4. Redeploy is triggered.
> 5. However the datasource is redeployed, notice the following exception in the server.log:
> {noformat}
> 11:07:34,057 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.naming.context.java.testProjectEntityManagerFactory: org.jboss.msc.service.StartException in service jboss.naming.context.java.testProjectEntityManagerFactory: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> Caused by: org.jboss.msc.inject.InjectionException: Value already set for this injector
> at org.jboss.msc.inject.RetainingInjector.inject(RetainingInjector.java:50) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler$1.inject(PersistenceUnitServiceHandler.java:386)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler$1.inject(PersistenceUnitServiceHandler.java:382)
> at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1549) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl.access$1900(ServiceControllerImpl.java:49) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1780) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1741) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> ... 3 more
> {noformat}
--
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-14709) Error in server log when redeploying datasource
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14709?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-14709:
--------------------------------------
Assignee: Alexey Kazakov
> Error in server log when redeploying datasource
> ------------------------------------------------
>
> Key: JBIDE-14709
> URL: https://issues.jboss.org/browse/JBIDE-14709
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam 2
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1, EAP 6.1.0.GA
> Reporter: Tomas Remes
> Assignee: Alexey Kazakov
>
> I am not sure, if this problem is related to JBT, but is best reproducible by this way. Steps to reproduce:
> 1. Create and run EAP 6.1.0 server
> 2. Create Seam Web Project (I used MySQL datasource)
> 3. Try to edit newly created datasource file in the project and save it.
> 4. Redeploy is triggered.
> 5. However the datasource is redeployed, notice the following exception in the server.log:
> {noformat}
> 11:07:34,057 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.naming.context.java.testProjectEntityManagerFactory: org.jboss.msc.service.StartException in service jboss.naming.context.java.testProjectEntityManagerFactory: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> Caused by: org.jboss.msc.inject.InjectionException: Value already set for this injector
> at org.jboss.msc.inject.RetainingInjector.inject(RetainingInjector.java:50) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler$1.inject(PersistenceUnitServiceHandler.java:386)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler$1.inject(PersistenceUnitServiceHandler.java:382)
> at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1549) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl.access$1900(ServiceControllerImpl.java:49) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1780) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1741) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> ... 3 more
> {noformat}
--
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-14708) Opening xml files with multiple editor tabs
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14708?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-14708:
-----------------------------------------
Tomas, could write some details on your configuration like OS, architecture, java vendor and version as well as attach log-file from <your workspace>/.metadata/.log if possible.
> Opening xml files with multiple editor tabs
> -------------------------------------------
>
> Key: JBIDE-14708
> URL: https://issues.jboss.org/browse/JBIDE-14708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: XML Structured Editor
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1
> Reporter: Tomas Remes
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> Create for example new Seam Web Project. At first open web.xml file, then open e.g. faces-config.xml file. In this point I would assume this file active in the view (not the first one) as it was in previous JBDS release. It does not seem to be perspective dependant and I open it from package explorer. Both files opened by JBoss Tools XML Editor.
--
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-14708) Opening xml files with multiple editor tabs
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14708?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-14708:
--------------------------------------
Assignee: Victor Rubezhny
I can reproduce it with JBoss Tools XML Editor only. Works fine with WTP XML Editor. Weird.
> Opening xml files with multiple editor tabs
> -------------------------------------------
>
> Key: JBIDE-14708
> URL: https://issues.jboss.org/browse/JBIDE-14708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: XML Structured Editor
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1
> Reporter: Tomas Remes
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> Create for example new Seam Web Project. At first open web.xml file, then open e.g. faces-config.xml file. In this point I would assume this file active in the view (not the first one) as it was in previous JBDS release. It does not seem to be perspective dependant and I open it from package explorer. Both files opened by JBoss Tools XML Editor.
--
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