July 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-118) Inclusion of Aries plugins in Locus causing console errors

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/JBTIS-118?page=com.atlassian.jira.plugin.... ] Paul Richardson commented on JBTIS-118: --------------------------------------- Messages still appear, when using Locus 1.0.0.Final-B31. Investigation shows that installing [aries.jmx.core|http://download.jboss.org/jbosstools/updates/integration/l...] and [aries.blueprint|http://download.jboss.org/jbosstools/updates/integration/...] in a new eclipse installation and workspace causes [osgi.enterprise_4.2|http://download.jboss.org/jbosstools/updates/requirem...] to also be installed, presumably because the installer is clever enough to try and satisfy 'Imported Package' requirements of plugins. osgi.enterprise exports the relevant packages hence is installed as an implicit dependency. However, using JBT-IS as a TP must skip this particular step hence anyone developing with JBT-IS as their TP will see these errors. To mitigate, it should just require osgi.enterprise to be included in the base target definition. This, I have successfully tested by adding this to teiid designer's target: {code}  <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit"> <unit id="osgi.enterprise" version="4.2.0.v201108120515"/> <repository location="http://download.jboss.org/jbosstools/updates/requirements/kepler/20130626..."/> </location> {code} In a similar manner, I note that the felix plugins are also complaining about missing a service: {code} !SUBENTRY 2 org.apache.felix.configadmin 2 0 2013-07-29 16:53:08.750 !MESSAGE Missing required capability Require-Capability: service-reference; filter="(objectClass=org.osgi.service.log.LogService)". {code} So I would imagine another plugin should be included from the requirements repository to fix this as well. > Inclusion of Aries plugins in Locus causing console errors > ---------------------------------------------------------- > > Key: JBTIS-118 > URL: https://issues.jboss.org/browse/JBTIS-118 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.0.Final > Reporter: Paul Richardson > Assignee: Paul Leacu > > Errors generated in the console when executing Eclipse IDE based on JBT-IS base.target target platform. This occurred while executing Teiid Designer, which makes no use of the Aries plugins. > {code} > !ENTRY org.eclipse.osgi 2 0 2013-07-25 15:15:59.174 > !MESSAGE One or more bundles are not resolved because the following root constraints are not resolved: > !SUBENTRY 1 org.eclipse.osgi 2 0 2013-07-25 15:15:59.175 > !MESSAGE Bundle reference:file:/home/phantomjinx/programming/java/workspace/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.apache.aries.jmx.core_1.0.1.redhat-610-SNAPSHOT.jar was not resolved. > !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.175 > !MESSAGE Missing imported package org.osgi.jmx.service.provisioning_[1.2.0,1.3.0). > !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.175 > !MESSAGE Missing imported package org.osgi.jmx_[1.0.0,2.0.0). > !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.176 > !MESSAGE Missing imported package org.osgi.jmx.service.permissionadmin_[1.2.0,1.3.0). > !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.176 > !MESSAGE Missing imported package org.osgi.jmx.service.useradmin_[1.1.0,1.2.0). > !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.176 > !MESSAGE Missing imported package org.osgi.jmx.service.cm_[1.3.0,1.4.0). > !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.177 > !MESSAGE Missing imported package org.osgi.jmx.framework_[1.5.0,1.6.0). > !SUBENTRY 1 org.eclipse.osgi 2 0 2013-07-25 15:15:59.177 > !MESSAGE Bundle reference:file:/home/phantomjinx/programming/java/workspace/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.apache.felix.configadmin_1.4.0.redhat-610-SNAPSHOT.jar was not resolved. > !SUBENTRY 2 org.apache.felix.configadmin 2 0 2013-07-25 15:15:59.177 > !MESSAGE Missing required capability Require-Capability: service-reference; filter="(objectClass=org.osgi.service.log.LogService)". > !ENTRY org.eclipse.osgi 2 0 2013-07-25 15:15:59.280 > !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists: > !SUBENTRY 1 org.eclipse.osgi 2 0 2013-07-25 15:15:59.281 > !MESSAGE Bundle org.apache.aries.jmx.core_1.0.1.redhat-610-SNAPSHOT [89] was not resolved. > !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.281 > !MESSAGE Missing imported package org.osgi.jmx_[1.0.0,2.0.0). > !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.282 > !MESSAGE Missing imported package org.osgi.jmx.framework_[1.5.0,1.6.0). > !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.282 > !MESSAGE Missing imported package org.osgi.jmx.service.cm_[1.3.0,1.4.0). > !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.283 > !MESSAGE Missing imported package org.osgi.jmx.service.permissionadmin_[1.2.0,1.3.0). > !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.283 > !MESSAGE Missing imported package org.osgi.jmx.service.provisioning_[1.2.0,1.3.0). > !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.284 > !MESSAGE Missing imported package org.osgi.jmx.service.useradmin_[1.1.0,1.2.0). > {code} > Understand that Fuse is the main beneficiary of these plugins. Are the Aries plugins essential to the Fuse project (or any other projects)? > The missing imports all relate to the osgi jmx specification, which is implemented by the [Eclipse Gemini|http://eclipse.org/gemini] project. Can / should its plugins be included to satisfy the import errors or does Fuse rely on another implementation? -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15301) Locus 1.0.0.Final contains some unwanted jars

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15301?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-15301: ------------------------------------------- Assignee: Paul Leacu (was: Mickael Istria) afaics its not [~phantomjinx] asking for these dependencies, but [~pleacu] and [~lhein]. The two issues I got with what is suggested / in locus now is primarily figuring out why we got -snapshot builds (we can't, at least not in a 1.0.0.final) and finally why they are coming from redhat internal/fuse specific builds and why we need custom builds for these ? > Locus 1.0.0.Final contains some unwanted jars > --------------------------------------------- > > Key: JBIDE-15301 > URL: https://issues.jboss.org/browse/JBIDE-15301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: locus > Affects Versions: 1.0.0-LOCUS > Reporter: Mickael Istria > Assignee: Paul Leacu > Priority: Critical > Fix For: 1.0.1-LOCUS > > > Locus contains some jars that are against Locus rules because: > * They are SNAPSHOTs > * They are -redhat- build. > Instead, it should be public releases only. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15301) Locus 1.0.0.Final contains some unwanted jars

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15301?page=com.atlassian.jira.plugi... ] Paul Richardson reassigned JBIDE-15301: --------------------------------------- Assignee: Mickael Istria (was: Paul Richardson) > Locus 1.0.0.Final contains some unwanted jars > --------------------------------------------- > > Key: JBIDE-15301 > URL: https://issues.jboss.org/browse/JBIDE-15301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: locus > Affects Versions: 1.0.0-LOCUS > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 1.0.1-LOCUS > > > Locus contains some jars that are against Locus rules because: > * They are SNAPSHOTs > * They are -redhat- build. > Instead, it should be public releases only. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15301) Locus 1.0.0.Final contains some unwanted jars

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15301?page=com.atlassian.jira.plugi... ] Paul Richardson commented on JBIDE-15301: ----------------------------------------- Teiid has no dependency on these jars. TD only requires mockito, jcip-annotations and saxon. > Locus 1.0.0.Final contains some unwanted jars > --------------------------------------------- > > Key: JBIDE-15301 > URL: https://issues.jboss.org/browse/JBIDE-15301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: locus > Affects Versions: 1.0.0-LOCUS > Reporter: Mickael Istria > Assignee: Paul Richardson > Priority: Critical > Fix For: 1.0.1-LOCUS > > > Locus contains some jars that are against Locus rules because: > * They are SNAPSHOTs > * They are -redhat- build. > Instead, it should be public releases only. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15302) CordovaSim: support of Cordova 3.0

by Yahor Radtsevich (JIRA)

Yahor Radtsevich created JBIDE-15302: ---------------------------------------- Summary: CordovaSim: support of Cordova 3.0 Key: JBIDE-15302 URL: https://issues.jboss.org/browse/JBIDE-15302 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: browsersim Affects Versions: 4.1.0.Final Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 4.2.x The next major release of Cordova 3.0 is already available for download. CordovaSim should support it. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15301) Locus 1.0.0.Final contains some unwanted jars

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15301?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-15301 at 7/29/13 11:19 AM: ------------------------------------------------------------------ [~phantomjinx]: it seems to me that the addition of these jars comes from the changes you suggested as part of JBTIS-102 . We cannot allow Locus to contain a SNAPSHOT repository such as the one added here: https://github.com/jbosstools/jbosstools-locus/blob/1.0.0.x/site/pom.xml#... And in general, we cannot allow redhat specific builds. Can Teiid depend on the community release artifacts instead? was (Author: mickael_istria): [~phantomjinx]: it seems to me that the addition of these jars comes from the changes you suggested as part of JBTIS-102 . We cannot allow Locus to contain a SNAPSHOT repository such as the one added here: https://issues.jboss.org/browse/JBIDE-15301 And in general, we cannot allow redhat specific builds. Can Teiid depend on the community release artifacts instead? > Locus 1.0.0.Final contains some unwanted jars > --------------------------------------------- > > Key: JBIDE-15301 > URL: https://issues.jboss.org/browse/JBIDE-15301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: locus > Affects Versions: 1.0.0-LOCUS > Reporter: Mickael Istria > Assignee: Paul Richardson > Priority: Critical > Fix For: 1.0.1-LOCUS > > > Locus contains some jars that are against Locus rules because: > * They are SNAPSHOTs > * They are -redhat- build. > Instead, it should be public releases only. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15301) Locus 1.0.0.Final contains some unwanted jars

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15301?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-15301: -------------------------------------- Assignee: Paul Richardson [~phantomjinx]: it seems to me that the addition of these jars comes from the changes you suggested as part of JBTIS-102 . We cannot allow Locus to contain a SNAPSHOT repository such as the one added here: https://issues.jboss.org/browse/JBIDE-15301 And in general, we cannot allow redhat specific builds. Can Teiid depend on the community release artifacts instead? > Locus 1.0.0.Final contains some unwanted jars > --------------------------------------------- > > Key: JBIDE-15301 > URL: https://issues.jboss.org/browse/JBIDE-15301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: locus > Affects Versions: 1.0.0-LOCUS > Reporter: Mickael Istria > Assignee: Paul Richardson > Priority: Critical > Fix For: 1.0.1-LOCUS > > > Locus contains some jars that are against Locus rules because: > * They are SNAPSHOTs > * They are -redhat- build. > Instead, it should be public releases only. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15301) Locus 1.0.0.Final contains some unwanted jars

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-15301: -------------------------------------- Summary: Locus 1.0.0.Final contains some unwanted jars Key: JBIDE-15301 URL: https://issues.jboss.org/browse/JBIDE-15301 Project: Tools (JBoss Tools) Issue Type: Bug Components: locus Affects Versions: 1.0.0-LOCUS Reporter: Mickael Istria Priority: Critical Fix For: 1.0.1-LOCUS Locus contains some jars that are against Locus rules because: * They are SNAPSHOTs * They are -redhat- build. Instead, it should be public releases only. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14505) CordovaSim: Device API should know which device (BS skin) is selected

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14505?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-14505: -------------------------------- Description: Cordova's "Device API" ( http://docs.phonegap.com/en/3.0.0/cordova_device_device.md.html#Device ) should return different data for different devices (BS skins) (was: Ripple original select device controls ('Devices' Tab) was removed in CordovaSim. Need to add analogous tab with BrowserSim skins. Selected skin will be displayed on this tab, and user will have a possibility of changing BS skins via controls. ) > CordovaSim: Device API should know which device (BS skin) is selected > --------------------------------------------------------------------- > > Key: JBIDE-14505 > URL: https://issues.jboss.org/browse/JBIDE-14505 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.0.Alpha1 > > > Cordova's "Device API" ( http://docs.phonegap.com/en/3.0.0/cordova_device_device.md.html#Device ) should return different data for different devices (BS skins) -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14505) CordovaSim: BrowserSim's change skin controls should be used instead of Ripple's select device controls (Device API should know which device is selected)

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14505?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-14505: ------------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.1.x) > CordovaSim: BrowserSim's change skin controls should be used instead of Ripple's select device controls (Device API should know which device is selected) > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14505 > URL: https://issues.jboss.org/browse/JBIDE-14505 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.0.Alpha1 > > > Ripple original select device controls ('Devices' Tab) was removed in CordovaSim. Need to add analogous > tab with BrowserSim skins. Selected skin will be displayed on this tab, and user will have a possibility of changing BS skins via controls. -- 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

13 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2013