[JBoss JIRA] (JBIDE-23391) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [central]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23391?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-23391:
----------------------------------------
I downgraded it to minor. [~nickboldt] if it's just a warning when building central then it's not a blocker. But if we have a failing build (we should not) or something then please upgrade it to Blocker again. We will need to fix our build. Such stuff shouldn't block us.
> For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [central]
> ----------------------------------------------------------------
>
> Key: JBIDE-23391
> URL: https://issues.jboss.org/browse/JBIDE-23391
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: central
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Minor
> Labels: task
> Fix For: 4.4.x
>
>
> For JBIDE 4.4.2.AM3 [central]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.tools.discovery.core is a Core plugin, but depends on these UI plugins directly or transitively:
> > org.eclipse.ui.workbench
> > org.eclipse.equinox.p2.ui
> > org.eclipse.mylyn.discovery.ui
> --
> [CoreUIDependency] org.jboss.tools.maven.core is a Core plugin, but depends on these UI plugins directly or transitively:
> > org.eclipse.jdt.ui
> > org.eclipse.ui.workbench
> > org.eclipse.m2e.core.ui
> --
> [CoreUIDependency] org.jboss.tools.maven.sourcelookup.core is a Core plugin, but depends on these UI plugins directly or transitively:
> > org.eclipse.ui
> > org.eclipse.jdt.ui
> > org.eclipse.ui.workbench
> > org.eclipse.m2e.core.ui{code}
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-22382:
--------------------------------
Fix Version/s: LATER
(was: 4.4.2.AM3)
> Use different icons for EAP server and Red Hat Central
> ------------------------------------------------------
>
> Key: JBIDE-22382
> URL: https://issues.jboss.org/browse/JBIDE-22382
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central, server
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Priority: Minor
> Fix For: LATER
>
> Attachments: central-rhd-icon.png, fullIDE.png, tools_rebrand.png
>
>
> If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23380) MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23380:
-------------------------------------
> But the enforcer is completely missing one big chunk of functionality: we're not checking Import-Package declarations, only Require-Bundle. Rob Stryker can you add that?
No, I can't, really. Just knowing the package does not mean there's any way to know what bundle is contributing it. I think I've taken this issue as far as I can.
> MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-23380
> URL: https://issues.jboss.org/browse/JBIDE-23380
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM3
>
>
> At a minimum, the mojo should:
> foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all.
> However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm.
> So... we may wish to check transitive dependencies *only in the same repo*. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23364) Two different versions of code recommenders and docker tooling in JBT composite site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23364?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23364:
------------------------------------
I've enabled the jbt sites to be built with MAX TP:
https://github.com/jbosstools/jbosstools-build-sites/commit/e1d42d7e2ebc4...
> Two different versions of code recommenders and docker tooling in JBT composite site
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-23364
> URL: https://issues.jboss.org/browse/JBIDE-23364
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: target-platform
> Affects Versions: 4.4.2.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM3
>
> Attachments: docker_versions.png, snipmatch_versions.png
>
>
> This remediation error occurs when trying to install JBT 4.4.2.AM2 into Eclipse JEE bundle Neon.1a:
> {code}
> Your original request has been modified.
> "JavaScript Development Tools" will be ignored because a newer version is already installed.
> "Eclipse JSON Editors and Tools" will be ignored because a newer version is already installed.
> "WST JSON Core" will be ignored because a newer version is already installed.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
> Software currently installed: Code Recommenders for Java Developers 2.4.3.v20160913-0645 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160913-0645)
> Only one of the following can be installed at once:
> Code Recommenders Dependency Identification UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.coordinates.rcp 2.4.0.v20160607-1609)
> Code Recommenders Dependency Identification UI 2.4.3.v20160913-0645 (org.eclipse.recommenders.coordinates.rcp 2.4.3.v20160913-0645)
> Cannot satisfy dependency:
> From: Code Recommenders for Java Developers 2.4.3.v20160913-0645 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160913-0645)
> To: org.eclipse.recommenders.coordinates.rcp [2.4.3.v20160913-0645]
> Cannot satisfy dependency:
> From: Code Recommenders Snipmatch UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp 2.4.0.v20160607-1609)
> To: bundle org.eclipse.recommenders.coordinates.rcp [2.4.0,2.4.1)
> Cannot satisfy dependency:
> From: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
> To: org.eclipse.recommenders.snipmatch.rcp [2.4.0.v20160607-1609]{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months