[JBoss JIRA] (JBIDE-14762) cannot install jboss tools into Kepler JavaEE
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-14762:
-------------------------------------------
Summary: cannot install jboss tools into Kepler JavaEE
Key: JBIDE-14762
URL: https://issues.jboss.org/browse/JBIDE-14762
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, maven
Affects Versions: 4.1.0.Beta1
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Blocker
Fix For: 4.1.0.Beta2
something is amiss in our TP seems like Kepler includes a version incompatible with our includes.
http://screencast.com/t/tyy5O8bQj
Cannot complete the install because of a conflicting dependency.
Software being installed: JBoss Maven Project Examples 1.5.0.Beta1-v20130523-1233-B39 (org.jboss.tools.maven.project.examples.feature.feature.group 1.5.0.Beta1-v20130523-1233-B39)
Software currently installed: Maven Integration for WTP 0.15.3.20120830-0850 (org.maven.ide.eclipse.wtp.feature.feature.group 0.15.3.20120830-0850)
Only one of the following can be installed at once:
This version of m2e-wtp cannot be installed on top of the already installed m2eclipse-wtp. Uninstall the previous version of m2eclipse-wtp and try the install again. 1.0.0.20130507-1357 (org.maven.ide.eclipse.wtp 1.0.0.20130507-1357)
Maven Integration for Eclipse WTP 0.15.3.20120830-0850 (org.maven.ide.eclipse.wtp 0.15.3.20120830-0850)
This version of m2e-wtp cannot be installed on top of the already installed m2eclipse-wtp. Uninstall the previous version of m2eclipse-wtp and try the install again. 1.0.0.20130528-1157 (org.maven.ide.eclipse.wtp 1.0.0.20130528-1157)
Cannot satisfy dependency:
From: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130507-1357 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130507-1357)
To: bundle org.maven.ide.eclipse.wtp [1.0.0.20130507-1357]
Cannot satisfy dependency:
From: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130528-1157 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130528-1157)
To: bundle org.maven.ide.eclipse.wtp [1.0.0.20130528-1157]
Cannot satisfy dependency:
From: JBoss Maven Project Examples 1.5.0.Beta1-v20130523-1233-B39 (org.jboss.tools.maven.project.examples.feature.feature.group 1.5.0.Beta1-v20130523-1233-B39)
To: org.eclipse.m2e.wtp.feature.feature.group 0.16.0
Cannot satisfy dependency:
From: Maven Integration for WTP 0.15.3.20120830-0850 (org.maven.ide.eclipse.wtp.feature.feature.group 0.15.3.20120830-0850)
To: org.maven.ide.eclipse.wtp [0.15.3.20120830-0850]
--
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] (JBDS-2653) Can't update m2e-wtp to latest version in JBDS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2653?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2653:
-------------------------------------------
not following.
we said earlier we would make sure m2e was upgradable but now we keep a feature instead of listing the maven features ?
> Can't update m2e-wtp to latest version in JBDS
> ----------------------------------------------
>
> Key: JBDS-2653
> URL: https://issues.jboss.org/browse/JBDS-2653
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build, maven
> Affects Versions: 7.0.0.Beta1
> Reporter: Fred Bricon
> Fix For: 7.0.0.Beta2
>
>
> {quote}
> [19:26] <@fbricon> using latest JBDS beta1, I can't upgrade m2e-wtp to the version sitting in http://download.eclipse.org/m2e-wtp/milestones/kepler/1.0.0/1.0.0.2013060...
> [19:26] <@fbricon> though it seems JPA, JAXRS and JSF features can be updated
> [19:27] <@fbricon> nboldt: that can't be a range restriction from the features/plugins in central, otherwise m2e-wtp 1.0.0 wouldn't be installed in JBDS at all
> [19:28] <@fbricon> nboldt: m2e itself can be updated
> {quote}
> I can see the remediation screen and some option seems to be to uninstall JBDS to fix the issue. I also found the original error message buried in the UI :
> {noformat}
> Your original request has been modified.
> "m2e-wtp - Maven Integration for WTP (Incubation)" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130604-1618 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130604-1618)
> Software currently installed: JBoss Developer Studio (Branded Product) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.all 7.0.0.Beta1-v20130529-0631-B257)
> Only one of the following can be installed at once:
> Overlay support for Eclipse WTP - UI (Incubation) 1.0.0.20130507-1357 (org.eclipse.m2e.wtp.overlay.ui 1.0.0.20130507-1357)
> Overlay support for Eclipse WTP - UI (Incubation) 1.0.0.20130528-1157 (org.eclipse.m2e.wtp.overlay.ui 1.0.0.20130528-1157)
> Overlay support for Eclipse WTP - UI (Incubation) 1.0.0.20130604-1618 (org.eclipse.m2e.wtp.overlay.ui 1.0.0.20130604-1618)
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Branded Product) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.all 7.0.0.Beta1-v20130529-0631-B257)
> To: com.jboss.jbds.product.feature.feature.group [7.0.0.Beta1-v20130529-0631-B257]
> Cannot satisfy dependency:
> From: Maven Integration (Selected) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.m2e.feature.feature.group 7.0.0.Beta1-v20130529-0631-B257)
> To: org.eclipse.m2e.wtp.feature.feature.group [1.0.0.20130507-1357]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.product.feature.feature.group 7.0.0.Beta1-v20130529-0631-B257)
> To: com.jboss.jbds.m2e.feature.feature.group [7.0.0.Beta1-v20130529-0631-B257]
> Cannot satisfy dependency:
> From: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130507-1357 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130507-1357)
> To: org.eclipse.m2e.wtp.overlay.ui [1.0.0.20130507-1357]
> Cannot satisfy dependency:
> From: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130604-1618 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130604-1618)
> To: org.eclipse.m2e.wtp.overlay.ui [1.0.0.20130604-1618]
> {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-14564) Runtime detection prompt shown on every IDE start
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14564?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-14564:
-------------------------------------
This continues to happen in Build id: Beta1-v20130529-0631-B257
No embedded EAP
> Runtime detection prompt shown on every IDE start
> -------------------------------------------------
>
> Key: JBIDE-14564
> URL: https://issues.jboss.org/browse/JBIDE-14564
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.1.0.Beta1
> Reporter: Michelle Murray
> Assignee: Snjezana Peco
> Attachments: Server_RTDwindow.png
>
>
> I installed JBDS with the universal installer (Beta1-v20130519-0601-B206) and did not set up runtime detection.
> On every IDE start, the runtime detection prompt is now displayed (screen capture attached). Not sure if this is a bug or desired behavior.
> If it is desired behavior, I can understand showing the prompt on the first start after an install to encourage users to use this function. But showing it on every start is annoying, particularly if a user does not want to use runtime detection.
--
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] (JBDS-2653) Can't update m2e-wtp to latest version in JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2653?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2653:
----------------------------------
Everything BUT the m2e one because we need a container for uncollected plugins, IIRC.
> Can't update m2e-wtp to latest version in JBDS
> ----------------------------------------------
>
> Key: JBDS-2653
> URL: https://issues.jboss.org/browse/JBDS-2653
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build, maven
> Affects Versions: 7.0.0.Beta1
> Reporter: Fred Bricon
> Fix For: 7.0.0.Beta2
>
>
> {quote}
> [19:26] <@fbricon> using latest JBDS beta1, I can't upgrade m2e-wtp to the version sitting in http://download.eclipse.org/m2e-wtp/milestones/kepler/1.0.0/1.0.0.2013060...
> [19:26] <@fbricon> though it seems JPA, JAXRS and JSF features can be updated
> [19:27] <@fbricon> nboldt: that can't be a range restriction from the features/plugins in central, otherwise m2e-wtp 1.0.0 wouldn't be installed in JBDS at all
> [19:28] <@fbricon> nboldt: m2e itself can be updated
> {quote}
> I can see the remediation screen and some option seems to be to uninstall JBDS to fix the issue. I also found the original error message buried in the UI :
> {noformat}
> Your original request has been modified.
> "m2e-wtp - Maven Integration for WTP (Incubation)" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130604-1618 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130604-1618)
> Software currently installed: JBoss Developer Studio (Branded Product) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.all 7.0.0.Beta1-v20130529-0631-B257)
> Only one of the following can be installed at once:
> Overlay support for Eclipse WTP - UI (Incubation) 1.0.0.20130507-1357 (org.eclipse.m2e.wtp.overlay.ui 1.0.0.20130507-1357)
> Overlay support for Eclipse WTP - UI (Incubation) 1.0.0.20130528-1157 (org.eclipse.m2e.wtp.overlay.ui 1.0.0.20130528-1157)
> Overlay support for Eclipse WTP - UI (Incubation) 1.0.0.20130604-1618 (org.eclipse.m2e.wtp.overlay.ui 1.0.0.20130604-1618)
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Branded Product) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.all 7.0.0.Beta1-v20130529-0631-B257)
> To: com.jboss.jbds.product.feature.feature.group [7.0.0.Beta1-v20130529-0631-B257]
> Cannot satisfy dependency:
> From: Maven Integration (Selected) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.m2e.feature.feature.group 7.0.0.Beta1-v20130529-0631-B257)
> To: org.eclipse.m2e.wtp.feature.feature.group [1.0.0.20130507-1357]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.product.feature.feature.group 7.0.0.Beta1-v20130529-0631-B257)
> To: com.jboss.jbds.m2e.feature.feature.group [7.0.0.Beta1-v20130529-0631-B257]
> Cannot satisfy dependency:
> From: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130507-1357 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130507-1357)
> To: org.eclipse.m2e.wtp.overlay.ui [1.0.0.20130507-1357]
> Cannot satisfy dependency:
> From: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130604-1618 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130604-1618)
> To: org.eclipse.m2e.wtp.overlay.ui [1.0.0.20130604-1618]
> {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-14541) fetching is not cancable/waits "forever"
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14541?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-14541:
-----------------------------------
Assignee: Fred Bricon
> fetching is not cancable/waits "forever"
> ----------------------------------------
>
> Key: JBIDE-14541
> URL: https://issues.jboss.org/browse/JBIDE-14541
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.1.0.Beta2
>
>
> started up, took a long time for central to show up (as if it was waiting for something to timeout)
> Then gets stuck in refreshing examples - cannot cancel it nor will it stop when closing central.
> here is the stacktrace it was "locked" at.
> at same time m2e index was downloading causing some slowness - not sure if related.
> Worker-3" prio=5 tid=0x000000010081b000 nid=0x9b17 in Object.wait() [0x000000010c985000]
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000007dd974978> (a org.eclipse.core.internal.jobs.Semaphore)
> at org.eclipse.core.internal.jobs.Semaphore.acquire(Semaphore.java:39)
> - locked <0x00000007dd974978> (a org.eclipse.core.internal.jobs.Semaphore)
> at org.jboss.tools.common.core.ecf.internal.WaitJob.customJoin(WaitJob.java:72)
> at org.jboss.tools.common.core.ecf.internal.WaitJob.waitForSynchronous(WaitJob.java:40)
> at org.jboss.tools.common.core.ecf.internal.InternalECFTransport.waitFor(InternalECFTransport.java:466)
> at org.jboss.tools.common.core.ecf.internal.InternalECFTransport.transfer(InternalECFTransport.java:311)
> at org.jboss.tools.common.core.ecf.internal.InternalECFTransport.performDownload(InternalECFTransport.java:224)
> at org.jboss.tools.common.core.ecf.internal.InternalECFTransport.download(InternalECFTransport.java:184)
> at org.jboss.tools.common.core.ecf.ECFTransportUtility.download(ECFTransportUtility.java:84)
> at org.jboss.tools.common.core.ecf.ECFTransport.download(ECFTransport.java:58)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjectExamplesFile(ProjectExampleUtil.java:805)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.handleCategories(ProjectExampleUtil.java:556)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:503)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:310)
> at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:53)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
--
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-14541) fetching is not cancable/waits "forever"
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14541?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-14541:
--------------------------------
Fix Version/s: 4.1.0.Beta2
> fetching is not cancable/waits "forever"
> ----------------------------------------
>
> Key: JBIDE-14541
> URL: https://issues.jboss.org/browse/JBIDE-14541
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Beta1
> Reporter: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.1.0.Beta2
>
>
> started up, took a long time for central to show up (as if it was waiting for something to timeout)
> Then gets stuck in refreshing examples - cannot cancel it nor will it stop when closing central.
> here is the stacktrace it was "locked" at.
> at same time m2e index was downloading causing some slowness - not sure if related.
> Worker-3" prio=5 tid=0x000000010081b000 nid=0x9b17 in Object.wait() [0x000000010c985000]
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000007dd974978> (a org.eclipse.core.internal.jobs.Semaphore)
> at org.eclipse.core.internal.jobs.Semaphore.acquire(Semaphore.java:39)
> - locked <0x00000007dd974978> (a org.eclipse.core.internal.jobs.Semaphore)
> at org.jboss.tools.common.core.ecf.internal.WaitJob.customJoin(WaitJob.java:72)
> at org.jboss.tools.common.core.ecf.internal.WaitJob.waitForSynchronous(WaitJob.java:40)
> at org.jboss.tools.common.core.ecf.internal.InternalECFTransport.waitFor(InternalECFTransport.java:466)
> at org.jboss.tools.common.core.ecf.internal.InternalECFTransport.transfer(InternalECFTransport.java:311)
> at org.jboss.tools.common.core.ecf.internal.InternalECFTransport.performDownload(InternalECFTransport.java:224)
> at org.jboss.tools.common.core.ecf.internal.InternalECFTransport.download(InternalECFTransport.java:184)
> at org.jboss.tools.common.core.ecf.ECFTransportUtility.download(ECFTransportUtility.java:84)
> at org.jboss.tools.common.core.ecf.ECFTransport.download(ECFTransport.java:58)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjectExamplesFile(ProjectExampleUtil.java:805)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.handleCategories(ProjectExampleUtil.java:556)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:503)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:310)
> at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:53)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
--
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-14662) Hibernate configuration view fails if multiple persistence.xml are found
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14662?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-14662:
--------------------------------
Summary: Hibernate configuration view fails if multiple persistence.xml are found (was: Hibernate configuration for html5 from central is not ready after import project )
Assignee: Koen Aers
Project contains 2 persistence.xml, one for production, one for tests. Hibernate Tooling doesn't support it apparently.
Assigning to [~koen.aers] for investigation/fix
> Hibernate configuration view fails if multiple persistence.xml are found
> ------------------------------------------------------------------------
>
> Key: JBIDE-14662
> URL: https://issues.jboss.org/browse/JBIDE-14662
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, hibernate
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1a,64
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Fix For: 4.1.0.Beta2
>
>
> When importing HTML5 project form Central, Hibernate console isn't properly configured and cannot be expanded and used without errors.
> {code}
> javax.persistence.PersistenceException: No name provided and several persistence units found
> at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:337)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.hibernate.console.ConfigurationFactory.buildJPAConfiguration(ConfigurationFactory.java:218)
> at org.hibernate.console.ConfigurationFactory.buildConfiguration(ConfigurationFactory.java:161)
> at org.hibernate.console.ConfigurationFactory.createConfiguration(ConfigurationFactory.java:96)
> at org.hibernate.console.ConsoleConfiguration$3.execute(ConsoleConfiguration.java:240)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:107)
> at org.hibernate.console.ConsoleConfiguration.buildWith(ConsoleConfiguration.java:237)
> at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:188)
> at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:42)
> 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)
> {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