[JBoss JIRA] (JBIDE-23068) Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23068?page=com.atlassian.jira.plugi... ]
Lukáš Valach closed JBIDE-23068.
--------------------------------
I can't reproduce this issue in AM3-v20161107-1219. So closing as resolved.
> Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23068
> URL: https://issues.jboss.org/browse/JBIDE-23068
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Dmitrii Bocharov
> Assignee: Dmitrii Bocharov
> Fix For: 4.4.2.Final
>
> Attachments: magic_error_disapperance.webm
>
>
> Builds in terminal (mvn clean install) run successfully. However in eclipse i have 3 errors for jjbt-base and 3 for jbt-server:
> jbt-base:
> Unknown extension point: 'org.eclipse.mylyn.tasks.bugs.support' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.mylyn.tasks.core.templates' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.ui.activities' plugin.xml in /org.jboss.tools.common.model.ui.capabilities
> jbt-server:
> Bundle 'org.jboss.ide.eclipse.as.management.eap61plus' cannot be resolved in /org.jboss.tools.as.management.itests/META-INF
> Unknown extension point: 'org.eclipse.help.contexts' in /org.jboss.ide.eclipse.as.doc.user
> Unknown extension point: 'org.eclipse.help.toc' in /org.jboss.ide.eclipse.as.doc.user
> [dbocharo@dbocharo jbosstools-target-platforms]$ git pull upstream 4.60.x
> From https://github.com/jbosstools/jbosstools-target-platforms
> * branch 4.60.x -> FETCH_HEAD
> Already up-to-date.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4014) Track rh-eclipse46-devstudio-*.rpm version usage
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBDS-4014?page=com.atlassian.jira.plugin.... ]
Radim Hopp closed JBDS-4014.
----------------------------
Verified in rh-eclipse46-devstudio.x86_64 10.2-0.20161109.0748.el7
rh-eclipse46-eclipse-usage was installed as dependency, devstudio.usage.branding is also present and correct useragent is reported in analytics: http://imgur.com/kyspoAn
> Track rh-eclipse46-devstudio-*.rpm version usage
> ------------------------------------------------
>
> Key: JBDS-4014
> URL: https://issues.jboss.org/browse/JBDS-4014
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: rpm, usage
> Reporter: Alexey Kazakov
> Assignee: Mat Booth
> Fix For: 10.2.0.AM3
>
>
> We need to distinguish the following use cases:
> 1) Devstudio installed via RPM
> 2) Devstudio installed via P2 but on top of the "base" eclipse rpm
> 3) Devstudio installed traditionally (jar installer or p2)
> As a bonus we could want to track if the DTS + devstudio rpms were both installed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23420) Update RedDeer in TP for JBT 4.4.2.Final
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23420?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23420:
---------------------------------------
We actually have one more update on this. We released RedDeer 1.2.1 and we'll want that instead of 1.2.0. I updated the PR.
> Update RedDeer in TP for JBT 4.4.2.Final
> ----------------------------------------
>
> Key: JBIDE-23420
> URL: https://issues.jboss.org/browse/JBIDE-23420
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: target-platform
> Affects Versions: 4.4.2.AM2
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.4.2.Final
>
>
> We'd like to update the TP for JBT 4.4.2.Final to include RedDeer 1.2.0.Final - which we'll have to release first.
> The deadline for a PR for Nick is Nov 23.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with PDE Source Lookup)
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-23481:
----------------------------------------
Why having split repositories for data and src? Why not simply include sources in the aggregated TP site directly? We have the options to do it, and it has been requested multiple times already. Then it can be used by target platform/regular PDE lookup and by this additional lookup.
> build target platform sources site (for use with PDE Source Lookup)
> -------------------------------------------------------------------
>
> Key: JBIDE-23481
> URL: https://issues.jboss.org/browse/JBIDE-23481
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.2.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to:
> [1] https://github.com/fbricon/pde.source.lookup/
> [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
> * build a targetplatform with all the sources
> * split that repo into two pieces: all the .source files, and everything else
> * regen the metadata (featureandbundlepublisher) in each new repo so that all the features/plugins are uncategorized
> OR...
> * build a targetplatform without the sources
> * transform the .target file so that each IU ends with .source
> * build the target platform repo from the new .target file
> * verify that sources repo includes the sources of nested features, and those features' plugins' sources too
> ----
> Then once we have the targetplatform.source repo, publish that and verify it works with the PDE Source Lookup plugin:
> 1. install the PDE source lookup plugin
> 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site
> 3. for something you want sources, use the plugin and see if it can resolve soources
> ----
> Then, if that works, we can consider adding the new tp.source site into the JBT/devstudio composite sites, along with jbt + tp + central + central tp (or ds + ds tp + central + central tp) as a 5th child site.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4120) CDK Installer doesn't work on Mac OS X
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4120?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4120:
-------------------------------------
[~jrichter1] I forgot to resolve it, thanks for taking care of it.
> CDK Installer doesn't work on Mac OS X
> --------------------------------------
>
> Key: JBDS-4120
> URL: https://issues.jboss.org/browse/JBDS-4120
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.AM2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM3
>
>
> Current version is bound to power shell execution to set PATH environment variable for user.
> On Mac OS X it also requires elevated privileges to setup PATH var through modification of /etc/paths file
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months