[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-18837:
-------------------------------------
No. Examples can be installed without central.
> because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18837
> URL: https://issues.jboss.org/browse/JBIDE-18837
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central, common/jst/core, project-examples
> Affects Versions: 4.2.1.CR1
> Reporter: Nick Boldt
> Labels: respin-a
> Fix For: 4.2.1.CR1
>
>
> When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples.
> Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating.
> And we need to use the maven enforcer plugin to fail the build if these versions get out of sync.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18837:
----------------------------------------
Should Central be the provider of the version then (and not Foundation) ?
> because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18837
> URL: https://issues.jboss.org/browse/JBIDE-18837
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central, common/jst/core, project-examples
> Affects Versions: 4.2.1.CR1
> Reporter: Nick Boldt
> Labels: respin-a
> Fix For: 4.2.1.CR1
>
>
> When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples.
> Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating.
> And we need to use the maven enforcer plugin to fail the build if these versions get out of sync.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBTIS-260) Teiid designer server management tasks fail for JBDS 7.1.1.GA + JBDSIS 7.0.1.CR2
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBTIS-260?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBTIS-260:
-----------------------------------------------
asmigala(a)redhat.com changed the Status of [bug 1082001|https://bugzilla.redhat.com/show_bug.cgi?id=1082001] from ON_QA to VERIFIED
> Teiid designer server management tasks fail for JBDS 7.1.1.GA + JBDSIS 7.0.1.CR2
> --------------------------------------------------------------------------------
>
> Key: JBTIS-260
> URL: https://issues.jboss.org/browse/JBTIS-260
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: teiid
> Environment: JBDS 7.1.1.GA, JBDSIS 7.0.1.CR2, server DV6 GA
> Reporter: Lucie Fabrikova
> Assignee: Paul Richardson
> Priority: Blocker
> Fix For: 4.1.4.Final
>
> Attachments: DriverValidator-1.2.11
>
>
> In teiid designer, start server latest DV6 GA and create new model project. Create some source model.
> - preview of data in table causes error with empty stack trace, development perspective is not opened
> - create and execute vdb: development perspective is opened, but vdb is not connected; trying to connect causes NPE:
> java.lang.NullPointerException
> at org.eclipse.datatools.connectivity.drivers.DriverValidator.validateJarListFiles(DriverValidator.java:161)
> at org.eclipse.datatools.connectivity.drivers.DriverValidator.isValid(DriverValidator.java:92)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.getDriverDefinitionJarPaths(JDBCConnection.java:217)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.getJdbcDriverJars(JDBCConnection.java:169)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.<init>(JDBCConnection.java:67)
> at org.teiid.datatools.connectivity.TeiidJDBCConnection.<init>(TeiidJDBCConnection.java:31)
> at org.teiid.datatools.connectivity.TeiidJDBCConnectionFactory.createConnection(TeiidJDBCConnectionFactory.java:21)
> at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83)
> at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359)
> at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.initializeJDBCConnection(ConnectionInfoImpl.java:705)
> at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.<init>(ConnectionInfoImpl.java:690)
> at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:38)
> at org.eclipse.datatools.connectivity.sqm.core.SQMConnectionFactory.createConnection(SQMConnectionFactory.java:45)
> at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:59)
> at org.eclipse.datatools.connectivity.internal.ConnectionFactoryAdapterProvider.createConnection(ConnectionFactoryAdapterProvider.java:114)
> at org.eclipse.datatools.connectivity.internal.ManagedConnection.createConnection(ManagedConnection.java:163)
> at org.eclipse.datatools.connectivity.internal.CreateConnectionJob.run(CreateConnectionJob.java:56)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18826) ClassNotFoundException for creating new Hybrid project
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18826?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-18826:
---------------------------------
Component/s: build
upstream
> ClassNotFoundException for creating new Hybrid project
> ------------------------------------------------------
>
> Key: JBIDE-18826
> URL: https://issues.jboss.org/browse/JBIDE-18826
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, build, upstream
> Affects Versions: 4.3.0.Alpha1
> Reporter: Ilya Buziuk
> Assignee: Gorkem Ercan
> Fix For: 4.3.0.Alpha1
>
>
> stack trace:
> {code}
> Caused by: java.lang.ClassNotFoundException: org.apache.http.client.cache.HttpCacheStorage cannot be found by org.eclipse.thym.core_0.1.0.201411202306
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 64 more
> {code}
> this is most likely a version range issue - http://snag.gy/6EHNd.jpg
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18826) ClassNotFoundException for creating new Hybrid project
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18826?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-18826:
--------------------------------------
org.apache.httpcomponents.httpclient_4.3.4.v201409180530 that is shipped together with Equinox does not export the *.cache packages. Eclipse Orbit actually carries a http components 4.3.4 with correct manifest but it is not picked up by the TP.
> ClassNotFoundException for creating new Hybrid project
> ------------------------------------------------------
>
> Key: JBIDE-18826
> URL: https://issues.jboss.org/browse/JBIDE-18826
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.0.Alpha1
> Reporter: Ilya Buziuk
> Assignee: Gorkem Ercan
> Fix For: 4.3.0.Alpha1
>
>
> stack trace:
> {code}
> Caused by: java.lang.ClassNotFoundException: org.apache.http.client.cache.HttpCacheStorage cannot be found by org.eclipse.thym.core_0.1.0.201411202306
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 64 more
> {code}
> this is most likely a version range issue - http://snag.gy/6EHNd.jpg
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-18837:
-------------------------------------
Max, you're right, 4.2.1 and 4.2.0 should and will be the same. But do I need to remind you that *you* asked to be able to fine tune properties lookups, down to the incremental version? Without this lockstep, we have *no* way to ensure we'll be able to use specific x.y.z settings *should we need to*.
So I have no problem not locking the incremental version down, because we'll be fine, however we need enforcer rules to ensure the foundation requirement is bumped between minor versions : make sure central in 4.3 requires foundation 4.3.
> because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18837
> URL: https://issues.jboss.org/browse/JBIDE-18837
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central, common/jst/core, project-examples
> Affects Versions: 4.2.1.CR1
> Reporter: Nick Boldt
> Labels: respin-a
> Fix For: 4.2.1.CR1
>
>
> When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples.
> Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating.
> And we need to use the maven enforcer plugin to fail the build if these versions get out of sync.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18681) 'Invalid thread access' error in central during shutdown
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18681?page=com.atlassian.jira.plugi... ]
Radim Hopp updated JBIDE-18681:
-------------------------------
Labels: need-info (was: )
> 'Invalid thread access' error in central during shutdown
> --------------------------------------------------------
>
> Key: JBIDE-18681
> URL: https://issues.jboss.org/browse/JBIDE-18681
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Final
> Reporter: Denis Golovin
> Assignee: Snjezana Peco
> Labels: need-info
> Fix For: 4.2.1.CR1, 4.3.0.Alpha1
>
>
> {code}Caused by: org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.widgets.Display.error(Display.java:1083)
> at org.eclipse.swt.widgets.Display.createDisplay(Display.java:840)
> at org.eclipse.swt.widgets.Display.create(Display.java:823)
> at org.eclipse.swt.graphics.Device.<init>(Device.java:130)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:714)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:705)
> at org.eclipse.swt.widgets.Display.getDefault(Display.java:1403)
> at org.jboss.tools.central.JBossCentralActivator.stop(JBossCentralActivator.java:215)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:827)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:820)
> ... 13 more{code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18681) 'Invalid thread access' error in central during shutdown
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18681?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-18681:
------------------------------------
[~dgolovin], [~xcoulon] have you seen this bug recently (CR1)? I haven't been successfull in reproducing it even on some older builds (4.2.0.Final). Do you think we can close this one?
> 'Invalid thread access' error in central during shutdown
> --------------------------------------------------------
>
> Key: JBIDE-18681
> URL: https://issues.jboss.org/browse/JBIDE-18681
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Final
> Reporter: Denis Golovin
> Assignee: Snjezana Peco
> Labels: need-info
> Fix For: 4.2.1.CR1, 4.3.0.Alpha1
>
>
> {code}Caused by: org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.widgets.Display.error(Display.java:1083)
> at org.eclipse.swt.widgets.Display.createDisplay(Display.java:840)
> at org.eclipse.swt.widgets.Display.create(Display.java:823)
> at org.eclipse.swt.graphics.Device.<init>(Device.java:130)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:714)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:705)
> at org.eclipse.swt.widgets.Display.getDefault(Display.java:1403)
> at org.jboss.tools.central.JBossCentralActivator.stop(JBossCentralActivator.java:215)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:827)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:820)
> ... 13 more{code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18845) Birt depends on Hibernate 3.8, but 4.0.1 is available in JBT
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18845?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18845:
-------------------------------
Assignee: Snjezana Peco
> Birt depends on Hibernate 3.8, but 4.0.1 is available in JBT
> ------------------------------------------------------------
>
> Key: JBIDE-18845
> URL: https://issues.jboss.org/browse/JBIDE-18845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: birt, build, hibernate, updatesite
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
>
> org.jboss.tools.birt.oda.ui 1.7.0.Alpha1-v20141006-1612-B585 requires org.hibernate.eclipse.libs 3.8.0. But the latest nightly site for Hibernate from master branch [1] contains no such IU.
> [1] http://download.jboss.org/jbosstools/builds/staging/jbosstools-hibernate_...
> {code}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.jboss.tools.site.core raw:4.3.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.0-SNAPSHOT
> [ERROR] Missing requirement: org.jboss.tools.birt.oda.ui 1.7.0.Alpha1-v20141006-1612-B585 requires 'bundle org.hibernate.eclipse.libs 3.8.0' but it could not be found
> [ERROR] Cannot satisfy dependency: org.jboss.tools.birt.feature.feature.group 1.7.0.Alpha1-v20141006-1612-B585 depends on: org.jboss.tools.birt.oda.ui [1.7.0.Alpha1-v20141006-1612-B585]
> [ERROR] Cannot satisfy dependency: org.jboss.tools.site.core raw:4.3.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.0-SNAPSHOT depends on: org.jboss.tools.birt.feature.feature.group 0.0.0
> [ERROR]
> [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.7.0.Alpha1-v20141006-1612-B585 to bundle org.hibernate.eclipse.libs 3.8.0.; No solution found because the problem is unsatisfiable.] -> [Help 1]
> {code}
> Due to this problem, the JBT aggregate builds are failing:
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> NOTE: This issue may be a duplicate of JBIDE-18795.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18845) Birt depends on Hibernate 3.8, but 4.0.1 is available in JBT
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18845:
----------------------------------
Summary: Birt depends on Hibernate 3.8, but 4.0.1 is available in JBT
Key: JBIDE-18845
URL: https://issues.jboss.org/browse/JBIDE-18845
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: birt, build, hibernate, updatesite
Affects Versions: 4.3.0.Alpha1
Reporter: Nick Boldt
Priority: Blocker
org.jboss.tools.birt.oda.ui 1.7.0.Alpha1-v20141006-1612-B585 requires org.hibernate.eclipse.libs 3.8.0. But the latest nightly site for Hibernate from master branch [1] contains no such IU.
[1] http://download.jboss.org/jbosstools/builds/staging/jbosstools-hibernate_...
{code}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.jboss.tools.site.core raw:4.3.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.0-SNAPSHOT
[ERROR] Missing requirement: org.jboss.tools.birt.oda.ui 1.7.0.Alpha1-v20141006-1612-B585 requires 'bundle org.hibernate.eclipse.libs 3.8.0' but it could not be found
[ERROR] Cannot satisfy dependency: org.jboss.tools.birt.feature.feature.group 1.7.0.Alpha1-v20141006-1612-B585 depends on: org.jboss.tools.birt.oda.ui [1.7.0.Alpha1-v20141006-1612-B585]
[ERROR] Cannot satisfy dependency: org.jboss.tools.site.core raw:4.3.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.0-SNAPSHOT depends on: org.jboss.tools.birt.feature.feature.group 0.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.7.0.Alpha1-v20141006-1612-B585 to bundle org.hibernate.eclipse.libs 3.8.0.; No solution found because the problem is unsatisfiable.] -> [Help 1]
{code}
Due to this problem, the JBT aggregate builds are failing:
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
NOTE: This issue may be a duplicate of JBIDE-18795.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
