[JBoss JIRA] (JBDS-4694) 'Could not resolve module: org.eclipse.buildship.core' exception occurs when running on RHEL 7
by Denis Golovin (JIRA)
Denis Golovin created JBDS-4694:
-----------------------------------
Summary: 'Could not resolve module: org.eclipse.buildship.core' exception occurs when running on RHEL 7
Key: JBDS-4694
URL: https://issues.jboss.org/browse/JBDS-4694
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: rpm
Affects Versions: 11.3.0.GA
Environment: RHEL 7
Reporter: Denis Golovin
{code}!SESSION 2018-04-18 06:54:36.009 -----------------------------------------------
eclipse.buildId=4.7.2.v20171217-1501
java.version=1.8.0_161
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86_64
!ENTRY org.eclipse.buildship.core 4 0 2018-04-18 06:54:48.570
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.buildship.core [1180]
Unresolved requirement: Require-Bundle: com.gradleware.tooling.utils; bundle-version="[0.19.3,0.20.0)"
-> Bundle-SymbolicName: com.gradleware.tooling.utils; bundle-version="0.19.4.v20171108133209"
com.gradleware.tooling.utils [1155]
Unresolved requirement: Require-Bundle: com.google.gson; bundle-version="2.7.0"
Unresolved requirement: Require-Bundle: com.gradleware.tooling.model; bundle-version="[0.19.3,0.20.0)"
-> Bundle-SymbolicName: com.gradleware.tooling.model; bundle-version="0.19.4.v20171108133209"
com.gradleware.tooling.model [1154]
Unresolved requirement: Require-Bundle: com.gradleware.tooling.utils; bundle-version="[0.19.4,0.20.0)"
-> Bundle-SymbolicName: com.gradleware.tooling.utils; bundle-version="0.19.4.v20171108133209"
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1634)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1613)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1585)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1528)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
!ENTRY org.eclipse.buildship.ui 4 0 2018-04-18 06:54:48.610
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.buildship.ui [1182]
Unresolved requirement: Require-Bundle: com.gradleware.tooling.model; bundle-version="[0.19.3,0.20.0)"
-> Bundle-SymbolicName: com.gradleware.tooling.model; bundle-version="0.19.4.v20171108133209"
com.gradleware.tooling.model [1154]
Unresolved requirement: Require-Bundle: com.gradleware.tooling.utils; bundle-version="[0.19.4,0.20.0)"
-> Bundle-SymbolicName: com.gradleware.tooling.utils; bundle-version="0.19.4.v20171108133209"
com.gradleware.tooling.utils [1155]
Unresolved requirement: Require-Bundle: com.google.gson; bundle-version="2.7.0"
Unresolved requirement: Require-Bundle: org.eclipse.buildship.core
-> Bundle-SymbolicName: org.eclipse.buildship.core; bundle-version="2.2.1.v20180125-1441"; singleton:="true"
org.eclipse.buildship.core [1180]
Unresolved requirement: Require-Bundle: com.gradleware.tooling.utils; bundle-version="[0.19.3,0.20.0)"
-> Bundle-SymbolicName: com.gradleware.tooling.utils; bundle-version="0.19.4.v20171108133209"
Unresolved requirement: Require-Bundle: com.gradleware.tooling.model; bundle-version="[0.19.3,0.20.0)"
-> Bundle-SymbolicName: com.gradleware.tooling.model; bundle-version="0.19.4.v20171108133209"
Unresolved requirement: Require-Bundle: com.gradleware.tooling.utils; bundle-version="[0.19.3,0.20.0)"
-> Bundle-SymbolicName: com.gradleware.tooling.utils; bundle-version="0.19.4.v20171108133209"
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1634)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1613)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1585)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1528)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-25597:
------------------------------------
Got a RedDeer problem while building jbosstools-base see [^base.log]
> TP: create target platforms based on Eclipse Photon
> ---------------------------------------------------
>
> Key: JBIDE-25597
> URL: https://issues.jboss.org/browse/JBIDE-25597
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.5.2.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: target-platform
> Fix For: 4.6.0.AM1, 4.6.0.Final
>
> Attachments: base.log
>
>
> In order to start Photon based builds, we need a working Photon based target platform
> For sprint 148 / AM1: Photon.0.M6
> For sprint 149 / AM2: Photon.0.M7
> For sprint 150 / AM3: Photon.0.RC3
> For sprint 151 / GA: Photon.0.GA
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-24789) Find a way to avoid freeze of master for several days
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24789?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-24789:
-----------------------------------------
we don't have the infrastructure for topic branch for now.
we work on doc along the sprints.
this is really not convenient to have this long code freeze, it is slowing us down.
Anyway, it has not been put in our priority list to work on that, so if it's not on yours I guess it will never be done.
> Find a way to avoid freeze of master for several days
> -----------------------------------------------------
>
> Key: JBIDE-24789
> URL: https://issues.jboss.org/browse/JBIDE-24789
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.5.0.Final
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Fix For: 4.5.3.Final
>
>
> Currently, for each milestone, final release, the master branch is frozen for several days which is decreasing productivity and increase risk at the end of code freeze (as everybody wants to merge a lot of PRs at the same time)
> it would be nice to find a way to avoid the freeze on the master branch.
> Proposal:
> - create a branch for each milestone/release:
> -- it allows to continue working on master
> -- it allows to provide blocker/critical fix if needed on the branch
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-23396) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [webservices]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23396?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23396:
-------------------------------
Affects Version/s: 4.4.2.Final
> For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [webservices]
> --------------------------------------------------------------------
>
> Key: JBIDE-23396
> URL: https://issues.jboss.org/browse/JBIDE-23396
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: webservices
> Affects Versions: 4.4.2.Final
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: task
> Fix For: 4.6.x
>
>
> For JBIDE 4.4.2.AM3 [webservices]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.tools.ws.core is a Core plugin, but depends on these UI plugins directly or transitively:
> > org.eclipse.ui
> > org.eclipse.jst.jsf.ui
> > org.eclipse.jst.ws.consumption.ui
> --
> [CoreUIDependency] org.jboss.tools.ws.creation.core is a Core plugin, but depends on these UI plugins directly or transitively:
> > org.eclipse.ui
> > org.eclipse.jdt.ui
> > org.eclipse.jst.jsf.ui
> > org.eclipse.jst.ws.consumption.ui
> --
> [CoreUIDependency] org.jboss.tools.ws.jaxrs.core is a Core plugin, but depends on these UI plugins directly or transitively:
> > org.eclipse.wst.common.frameworks.ui
> --
> [CoreUIDependency] org.jboss.tools.websockets.core is a Core plugin, but depends on these UI plugins directly or transitively:
> > org.eclipse.ui{code}
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-23396) UI dependencies from Core plugins [webservices]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23396?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23396:
-------------------------------
Summary: UI dependencies from Core plugins [webservices] (was: For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [webservices])
> UI dependencies from Core plugins [webservices]
> -----------------------------------------------
>
> Key: JBIDE-23396
> URL: https://issues.jboss.org/browse/JBIDE-23396
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: webservices
> Affects Versions: 4.4.2.Final
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: task
> Fix For: 4.6.x
>
>
> For JBIDE 4.4.2.AM3 [webservices]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.tools.ws.core is a Core plugin, but depends on these UI plugins directly or transitively:
> > org.eclipse.ui
> > org.eclipse.jst.jsf.ui
> > org.eclipse.jst.ws.consumption.ui
> --
> [CoreUIDependency] org.jboss.tools.ws.creation.core is a Core plugin, but depends on these UI plugins directly or transitively:
> > org.eclipse.ui
> > org.eclipse.jdt.ui
> > org.eclipse.jst.jsf.ui
> > org.eclipse.jst.ws.consumption.ui
> --
> [CoreUIDependency] org.jboss.tools.ws.jaxrs.core is a Core plugin, but depends on these UI plugins directly or transitively:
> > org.eclipse.wst.common.frameworks.ui
> --
> [CoreUIDependency] org.jboss.tools.websockets.core is a Core plugin, but depends on these UI plugins directly or transitively:
> > org.eclipse.ui{code}
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months