August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18136) iBeacon plugin problem, can´t compile app

by eduardo de souza (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18136?page=com.atlassian.jira.plugi... ] eduardo de souza commented on JBIDE-18136: ------------------------------------------ JBOSS: Version: 8.0.0.Beta3 Build id: Beta3-v20140722-2011-B194 Build date: 20140722-2011 Cordova iBeacon Plugin: version=2.1.0 Log: eclipse.buildId=unknown java.version=1.7.0_60-ea java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US Framework arguments: -product com.jboss.devstudio.core.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product org.eclipse.core.jobs Error Wed Aug 27 14:59:30 BRT 2014 An internal error occurred during: "Launching TesteApp2 (Android Device)". java.lang.NullPointerException at org.jboss.tools.aerogear.hybrid.core.plugin.actions.ActionVariableHelper.replaceVariables(ActionVariableHelper.java:18) at org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.getConfigFileActionsForPlatform(CordovaPluginManager.java:629) at org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.completePluginInstallationToPlatform(CordovaPluginManager.java:493) at org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.completePluginInstallationsForPlatform(CordovaPluginManager.java:253) at org.jboss.tools.aerogear.hybrid.core.platform.AbstractProjectGeneratorDelegate.completeCordovaPluginInstallations(AbstractProjectGeneratorDelegate.java:192) at org.jboss.tools.aerogear.hybrid.core.platform.AbstractProjectGeneratorDelegate.generateNow(AbstractProjectGeneratorDelegate.java:147) at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:48) at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > iBeacon plugin problem, can´t compile app > ----------------------------------------- > > Key: JBIDE-18136 > URL: https://issues.jboss.org/browse/JBIDE-18136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: eduardo de souza > Assignee: Gorkem Ercan > Priority: Critical > > I have created a Hybrid Mobile App, then added an iBeacon plugin: > https://github.com/petermetz/cordova-plugin-ibeacon.git > Then I tried to compile to see if there was any problem. I got this message: > An internal error occurred during: "Launching TesteApp4 (Android Device)". > java.lang.NullPointerException -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3086) Change Central Discovery URLs?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3086?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3086: ------------------------------------------- But yes, central can be updated with different schedule if need be. it is a composite after all, right ? > Change Central Discovery URLs? > ------------------------------ > > Key: JBDS-3086 > URL: https://issues.jboss.org/browse/JBDS-3086 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build, discovery, updatesite > Affects Versions: 8.0.0.Beta3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.0.CR1 > > Attachments: jbds3086_no-change-to-categorized-view.png, jbds3086_uncategorized-view-sample1.png, jbds3086_uncategorized-view-sample2.png > > > Today, the Central discovery plugin for JBDS is points to this URL: > <site>/central/core/ > and for Early Access discovery: > <site>/central/earlyaccess/ > However, Max has suggested that we simplify the first, and change the second. > I believe he wants something like this: > https://devstudio.jboss.com/updates/8.0-staging/ > https://devstudio.jboss.com/updates/8.0-development > https://devstudio.jboss.com/updates/8.0/ > and > https://devstudio.jboss.com/earlyaccess/8.0-staging/ > https://devstudio.jboss.com/earlyaccess/8.0-development/ > https://devstudio.jboss.com/earlyaccess/8.0/ > What do people think about this proposed change? > [~mickael_istria] [~maxandersen] [~dgolovin] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3086) Change Central Discovery URLs?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3086?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3086 at 8/27/14 1:54 PM: ----------------------------------------------------------- New PR keeps EA in a separate place. This PR also requires that the TPs be placed on the server (rather than remotely accessed from download.jboss.org - see JBDS-3125). https://github.com/jbdevstudio/jbdevstudio-website/pull/141 https://devstudio.redhat.com/updates/8.0-staging_JBDS-3086_prototype2/ https://devstudio.jboss.com/updates/8.0-staging_JBDS-3086_prototype2/comp... and https://devstudio.jboss.com/earlyaccess/8.0-staging_JBDS-3086_prototype2 https://devstudio.jboss.com/earlyaccess/8.0-staging_JBDS-3086_prototype2/... was (Author: nickboldt): New PR keeps EA in a separate place. This PR also requires that the TPs be placed on the server (rather than remotely accessed from download.jboss.org - see JBDS-3125). https://github.com/jbdevstudio/jbdevstudio-website/pull/141 > Change Central Discovery URLs? > ------------------------------ > > Key: JBDS-3086 > URL: https://issues.jboss.org/browse/JBDS-3086 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build, discovery, updatesite > Affects Versions: 8.0.0.Beta3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.0.CR1 > > Attachments: jbds3086_no-change-to-categorized-view.png, jbds3086_uncategorized-view-sample1.png, jbds3086_uncategorized-view-sample2.png > > > Today, the Central discovery plugin for JBDS is points to this URL: > <site>/central/core/ > and for Early Access discovery: > <site>/central/earlyaccess/ > However, Max has suggested that we simplify the first, and change the second. > I believe he wants something like this: > https://devstudio.jboss.com/updates/8.0-staging/ > https://devstudio.jboss.com/updates/8.0-development > https://devstudio.jboss.com/updates/8.0/ > and > https://devstudio.jboss.com/earlyaccess/8.0-staging/ > https://devstudio.jboss.com/earlyaccess/8.0-development/ > https://devstudio.jboss.com/earlyaccess/8.0/ > What do people think about this proposed change? > [~mickael_istria] [~maxandersen] [~dgolovin] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-297) Update JBTIS TP and composites for BPMN2 Modeler

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-297?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-297: ---------------------------------- https://github.com/jbosstools/jbosstools-integration-stack/commit/a2c0936... Got the new modeler - need to spin a new JBTIS TP and have SwitchYard build with it. This will be in JBTIS 4.2.0.Alpha2 > Update JBTIS TP and composites for BPMN2 Modeler > ------------------------------------------------ > > Key: JBTIS-297 > URL: https://issues.jboss.org/browse/JBTIS-297 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BPMN2 > Affects Versions: 4.2.0.Alpha7-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.2.0.Alpha8-TP > > > Update the JBTIS TP 4.2.0.Alpha8 with > http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/1... >  > - <unit id="org.eclipse.bpmn2.modeler.feature.feature.group" version="1.0.2.201402102317"/> > - <unit id="org.eclipse.bpmn2.modeler.jboss.runtime.feature.feature.group" version="1.0.2.201402102317"/> > - <repository location="http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/1..."/> > + <unit id="org.eclipse.bpmn2.modeler.feature.group" version="1.1.0.201408072130"/> > + <unit id="org.eclipse.bpmn2.modeler.runtime.jboss.feature.group" version="1.1.0.201408072130"/> > + <repository location="http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/1..."/> > org.eclipse.bpmn2.modeler.feature is now org.eclipse.bpmn2.modeler and > org.eclipse.bpmn2.modeler.jboss.runtime.feature is now org.eclipse.bpmn2.modeler.runtime.jboss > Then have SwitchYard build its 2.0.0.Alpha3 and create the JBTIS Alpha2 release. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3086) Change Central Discovery URLs?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3086?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3086 at 8/27/14 1:51 PM: ----------------------------------------------------------- New PR keeps EA in a separate place. This PR also requires that the TPs be placed on the server (rather than remotely accessed from download.jboss.org - see JBDS-3125). https://github.com/jbdevstudio/jbdevstudio-website/pull/141 was (Author: nickboldt): New PR keeps EA in a separate place. This PR also requires that the TPs be placed on the server (rather than remotely accessed from download.jboss.org - see JBDS-3125) > Change Central Discovery URLs? > ------------------------------ > > Key: JBDS-3086 > URL: https://issues.jboss.org/browse/JBDS-3086 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build, discovery, updatesite > Affects Versions: 8.0.0.Beta3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.0.CR1 > > Attachments: jbds3086_no-change-to-categorized-view.png, jbds3086_uncategorized-view-sample1.png, jbds3086_uncategorized-view-sample2.png > > > Today, the Central discovery plugin for JBDS is points to this URL: > <site>/central/core/ > and for Early Access discovery: > <site>/central/earlyaccess/ > However, Max has suggested that we simplify the first, and change the second. > I believe he wants something like this: > https://devstudio.jboss.com/updates/8.0-staging/ > https://devstudio.jboss.com/updates/8.0-development > https://devstudio.jboss.com/updates/8.0/ > and > https://devstudio.jboss.com/earlyaccess/8.0-staging/ > https://devstudio.jboss.com/earlyaccess/8.0-development/ > https://devstudio.jboss.com/earlyaccess/8.0/ > What do people think about this proposed change? > [~mickael_istria] [~maxandersen] [~dgolovin] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18134) Port forwarding: Free ports should be used from range 49152–65535

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18134?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18134: ------------------------------------- Fix Version/s: 4.3.x > Port forwarding: Free ports should be used from range 49152–65535 > ----------------------------------------------------------------- > > Key: JBIDE-18134 > URL: https://issues.jboss.org/browse/JBIDE-18134 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.3.x > > > Currently port forwarding use as free ports any port received via java client which is calling some RHC function to get a free port. There are many ports in those so-called free ports which are under range 49152–65535. This range is declared by IANA for dynamic, private... let's call them free ports. > Problem could occur in case of getting a port number lesser than 49152 which is currently not in use, but it is registered and user could start a service using this port number. Then there could be a conflict. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18136) iBeacon plugin problem, can´t compile app

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18136?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-18136: -------------------------------------- I was not able to reproduce this with the latest snapshot build. Can you give the version you have used. Also do you have anything at the error logs that may help. > iBeacon plugin problem, can´t compile app > ----------------------------------------- > > Key: JBIDE-18136 > URL: https://issues.jboss.org/browse/JBIDE-18136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: eduardo de souza > Assignee: Gorkem Ercan > Priority: Critical > > I have created a Hybrid Mobile App, then added an iBeacon plugin: > https://github.com/petermetz/cordova-plugin-ibeacon.git > Then I tried to compile to see if there was any problem. I got this message: > An internal error occurred during: "Launching TesteApp4 (Android Device)". > java.lang.NullPointerException -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16502) FrameworkEvent ERROR after JBT installation (tracker for upstream issue)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16502?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16502: ---------------------------------------- Assignee: Max Rydahl Andersen (was: Denis Golovin) > FrameworkEvent ERROR after JBT installation (tracker for upstream issue) > ------------------------------------------------------------------------ > > Key: JBIDE-16502 > URL: https://issues.jboss.org/browse/JBIDE-16502 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2, L64, Fedora 19, OpenJDK 1.7 > Reporter: Jiri Peterka > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.2.0.CR1 > > > After Eclipse Luna M5 JEE + JBT 4.2.0.Alpha2 installation there is: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.eclipse.jpt.dbws.eclipselink.ui [388] > Bundle was not resolved because of a uses contraint violation. > org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"] because it is exposed to package 'javax.xml.bind' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains. > Chain 1: > org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"] > require: (&(osgi.wiring.bundle=org.eclipse.wst.common.project.facet.ui)(&(bundle-version>=1.3.0)(!(bundle-version>=2.0.0)))) > | > provide: osgi.wiring.bundle: org.eclipse.wst.common.project.facet.ui > org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"] > Chain 2: > org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"] > require: (&(osgi.wiring.bundle=org.eclipse.persistence.dbws.builder)(&(bundle-version>=2.3.0)(!(bundle-version>=3.0.0)))) > | > provide: osgi.wiring.bundle; osgi.wiring.bundle="org.eclipse.persistence.dbws.builder"; bundle-version:Version="2.6.0.v20130815-a4708b6" > org.eclipse.persistence.dbws.builder [osgi.identity; osgi.identity="org.eclipse.persistence.dbws.builder"; type="osgi.bundle"; version:Version="2.6.0.v20130815-a4708b6"] > import: (osgi.wiring.package=javax.xml.bind) > | > export: osgi.wiring.package: javax.xml.bind > javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] > at org.eclipse.osgi.container.Module.start(Module.java:424) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1551) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1502) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1445) > 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) > Caused by: org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"] because it is exposed to package 'javax.xml.bind' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains. > Chain 1: > org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"] > require: (&(osgi.wiring.bundle=org.eclipse.wst.common.project.facet.ui)(&(bundle-version>=1.3.0)(!(bundle-version>=2.0.0)))) > | > provide: osgi.wiring.bundle: org.eclipse.wst.common.project.facet.ui > org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"] > Chain 2: > org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"] > require: (&(osgi.wiring.bundle=org.eclipse.persistence.dbws.builder)(&(bundle-version>=2.3.0)(!(bundle-version>=3.0.0)))) > | > provide: osgi.wiring.bundle; osgi.wiring.bundle="org.eclipse.persistence.dbws.builder"; bundle-version:Version="2.6.0.v20130815-a4708b6" > org.eclipse.persistence.dbws.builder [osgi.identity; osgi.identity="org.eclipse.persistence.dbws.builder"; type="osgi.bundle"; version:Version="2.6.0.v20130815-a4708b6"] > import: (osgi.wiring.package=javax.xml.bind) > | > export: osgi.wiring.package: javax.xml.bind > javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] > at org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1286) > at org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1078) > at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:249) > at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolveSingleRevision(ModuleResolver.java:948) > at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:874) > at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:111) > at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:471) > at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:429) > at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:419) > at org.eclipse.osgi.container.Module.start(Module.java:406) > ... 7 more > Root exception: > org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"] because it is exposed to package 'javax.xml.bind' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains. > Chain 1: > org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"] > require: (&(osgi.wiring.bundle=org.eclipse.wst.common.project.facet.ui)(&(bundle-version>=1.3.0)(!(bundle-version>=2.0.0)))) > | > provide: osgi.wiring.bundle: org.eclipse.wst.common.project.facet.ui > org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"] > Chain 2: > org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"] > require: (&(osgi.wiring.bundle=org.eclipse.persistence.dbws.builder)(&(bundle-version>=2.3.0)(!(bundle-version>=3.0.0)))) > | > provide: osgi.wiring.bundle; osgi.wiring.bundle="org.eclipse.persistence.dbws.builder"; bundle-version:Version="2.6.0.v20130815-a4708b6" > org.eclipse.persistence.dbws.builder [osgi.identity; osgi.identity="org.eclipse.persistence.dbws.builder"; type="osgi.bundle"; version:Version="2.6.0.v20130815-a4708b6"] > import: (osgi.wiring.package=javax.xml.bind) > | > export: osgi.wiring.package: javax.xml.bind > javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] > at org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1286) > at org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1078) > at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:249) > at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolveSingleRevision(ModuleResolver.java:948) > at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:874) > at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:111) > at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:471) > at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:429) > at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:419) > at org.eclipse.osgi.container.Module.start(Module.java:406) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1551) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1502) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1445) > 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 (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18137) Update Thym release on TP

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18137?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-18137: -------------------------------------- +1 > Update Thym release on TP > ------------------------- > > Key: JBIDE-18137 > URL: https://issues.jboss.org/browse/JBIDE-18137 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.0.CR1 > > > *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/thym/snapshots > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... > *Sources:* https://github.com/eclipse/thym > *Affected projects:* jbosstools-aerogear > *Include in JBDS:* YES > *Type of dependency:* build > *List of bundles added/removed:* > {code} > mistria@mistria--rh:~/git/jbosstools-target-platforms/jbosstools/multiple$ ~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64/p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... file:$(pwd)/target/jbosstools-multiple.target.repo/ > < org.eclipse.thym.feature.feature.group [0.1.0.201408251101] > < org.eclipse.thym.core [0.1.0.201408251101] > < org.eclipse.thym.ios.ui [0.1.0.201408251101] > < org.eclipse.thym.android.core [0.1.0.201408251101] > < org.eclipse.thym.android.ui [0.1.0.201408251101] > < org.eclipse.thym.ios.core [0.1.0.201408251101] > < org.eclipse.thym.ui [0.1.0.201408251101] > < org.eclipse.thym.feature.feature.jar [0.1.0.201408251101] > > org.eclipse.thym.ios.ui [0.1.0.201408271516] > > org.eclipse.thym.android.ui [0.1.0.201408271516] > > org.eclipse.thym.core [0.1.0.201408271516] > > org.eclipse.thym.feature.feature.group [0.1.0.201408271516] > > org.eclipse.thym.android.core [0.1.0.201408271516] > > org.eclipse.thym.ui [0.1.0.201408271516] > > org.eclipse.thym.feature.feature.jar [0.1.0.201408271516] > > org.eclipse.thym.ios.core [0.1.0.201408271516] > === Summary === > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 8 unique IUs > file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 8 unique IUs > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17550) When Install/Update button pressed no progress reported about installation preparation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17550?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17550: ---------------------------------------- Labels: f2f2014 (was: ) > When Install/Update button pressed no progress reported about installation preparation > -------------------------------------------------------------------------------------- > > Key: JBIDE-17550 > URL: https://issues.jboss.org/browse/JBIDE-17550 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: f2f2014 > Fix For: 4.2.0.CR1 > > > When big features like ADT or set of features requested to be installed from central there is no indication in eclipse by any means that something is going on. Meantime central calls > {code} > computeInstallableUnits(monitor.newChild(50)); > {code} > and > {code}resolveInstall(monitor.newChild(50));{code} > which can take considerable amount of time. > I think progress for Preparation to install requested features should be visible in eclipse. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

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 August 2014