[JBoss JIRA] (JBTIS-397) Missing source bundle for org.teiid.designer.webservice.lib
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-397?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-397:
----------------------------------
More specifically - remove the org.teiid.designer.webservice.lib plugin ID from the excludes configuration of the tycho-source-feature-plugin mojo.
> Missing source bundle for org.teiid.designer.webservice.lib
> -----------------------------------------------------------
>
> Key: JBTIS-397
> URL: https://issues.jboss.org/browse/JBTIS-397
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 8.0.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Barry LaFond
> Priority: Minor
>
> Source bundle for org.teiid.designer.webservice.lib is missing in JBDS-IS 8.0.0.CR3. Notice that this bundle contains only two classes
> * org/teiid/designer/webservice/lib/WebServiceLibPlugin.class
> * org/teiid/designer/webservice/lib/WebServiceLibConstants.class
> so I set the priority as minor.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21158) Improve BaseExplorerContentProvider.loadChildren()
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21158?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21158:
-----------------------------------------------
Loading tree children in a separate non-ui job implied that the process may take a long time and when this approach is chosen it should not leave a loophole for loading in ui thread.
By the way, the deriving class ExpressExplorerContentProvider (Openshift 2) overrides getChildren(Object) in such a way, that collection 'loadedElements' is never used to retrieve the children loaded in the non-ui job and always causes new call to getChildrenFor((Object) in ui thread, so that objects that get to 'loadedElements' may be considered as memory leaked. I have a guess why it was done this way: to prevent collapsing the expanded tree nodes at refreshes. Maybe that should be reported as a new issue, but since Openshift 2 is not a priority, I am not sure.
> Improve BaseExplorerContentProvider.loadChildren()
> --------------------------------------------------
>
> Key: JBIDE-21158
> URL: https://issues.jboss.org/browse/JBIDE-21158
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: performance
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> This method may be called concurrently while children for current parentElement are being loaded. Now for this case implementation calls directly getChildrenFor(parentElement) which loads children in ui thread. So, if by some reason loading children in a separate job took a lot of time, by the same reason this second call in ui thread may hang Eclipse for some time.
> Instead, it seams reasonable just to return the available loading stub as a child, when loading job is completed it will call refresh.
> [~adietish] please take a look at the pull request.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21158) Improve BaseExplorerContentProvider.loadChildren()
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21158?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21158:
-----------------------------------------------
If 'Loading...' node is lingering for some time (e.g. because of slow internet), then calling manually Refresh on its parent might double the time and make Eclipse unresponsive until children are loaded.
> Improve BaseExplorerContentProvider.loadChildren()
> --------------------------------------------------
>
> Key: JBIDE-21158
> URL: https://issues.jboss.org/browse/JBIDE-21158
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: performance
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> This method may be called concurrently while children for current parentElement are being loaded. Now for this case implementation calls directly getChildrenFor(parentElement) which loads children in ui thread. So, if by some reason loading children in a separate job took a lot of time, by the same reason this second call in ui thread may hang Eclipse for some time.
> Instead, it seams reasonable just to return the available loading stub as a child, when loading job is completed it will call refresh.
> [~adietish] please take a look at the pull request.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21158) Improve BaseExplorerContentProvider.loadChildren()
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21158?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-21158 at 12/1/15 2:35 PM:
--------------------------------------------------------------
Thanks for the patch Slava. Worked fine for me, although I couldn't spot any difference, as a user.
Applied in master and 4.3.x
was (Author: fbricon):
Thanks for the path Slava. Worked fine for me, although I couldn't spot any difference, as a user.
Applied in master and 4.3.x
> Improve BaseExplorerContentProvider.loadChildren()
> --------------------------------------------------
>
> Key: JBIDE-21158
> URL: https://issues.jboss.org/browse/JBIDE-21158
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: performance
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> This method may be called concurrently while children for current parentElement are being loaded. Now for this case implementation calls directly getChildrenFor(parentElement) which loads children in ui thread. So, if by some reason loading children in a separate job took a lot of time, by the same reason this second call in ui thread may hang Eclipse for some time.
> Instead, it seams reasonable just to return the available loading stub as a child, when loading job is completed it will call refresh.
> [~adietish] please take a look at the pull request.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21145) Component-install job does not reliably install all JBT IUs and so does not see changes between CI builds
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21145:
------------------------------------
{quote} I don't know why this downstream trigger was removed.{quote}
Because it was not needed -- having every single component kick off the JBT aggregate would mean lots of extra builds, including sometimes causing build failures due to missing changes in the stack.
For example, if Base changes something on which Server depends, and it rebuilds, then fires off the aggregate before Server updates to accept the API changes in Base, we could either end up with a broken aggregate build, or worse, a combination of incompatible Base + Server which wouldn't be installable and would waste QE's time testing something that should never have been built until Server was ready.
By pooling the changes and checking for composite changes every 3 hrs, we are more likely to get "changes affecting multiple components" to be all committed at the same time, resulting in more blue builds.
> Component-install job does not reliably install all JBT IUs and so does not see changes between CI builds
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21145
> URL: https://issues.jboss.org/browse/JBIDE-21145
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> We have often seen old artifacts on nightly sites (mars and neon too).
> It seems that the composite-install job [0], [1] is not reliable. So, the downstream JBT aggregate builds [2], [3] are not triggered automatically to pick up all new changes in the upstream JBT component site builds.
> [0] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-...
> [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-...
> [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... (latest build shows: "Nov 27, 2015 6:15 AM NOT PUBLISHED: UNCHANGED")
> [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... (latest build shows: "Nov 27, 2015 3:43 AM NOT PUBLISHED: UNCHANGED")
> Please investigate.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21166) AJDT can't install against 4.4/Neon
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21166?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-21166:
----------------------------------
Assignee: Nick Boldt
> AJDT can't install against 4.4/Neon
> -----------------------------------
>
> Key: JBIDE-21166
> URL: https://issues.jboss.org/browse/JBIDE-21166
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: discovery
> Affects Versions: 4.4.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
> Attachments: spring-ide373-all-features-except-ajdt-and-roo.png
>
>
> AJDT fails to install on JBoss Tools 4.4/Eclipse Neon
> Various contraint show that AJDT is not compatible with newer JDT.
> {code}
> !ENTRY org.eclipse.equinox.p2.operations 4 0 2015-11-27 20:08:18.692
> !MESSAGE Operation details
> !SUBENTRY 1 org.eclipse.equinox.p2.operations 2 10001 2015-11-27 20:08:18.692
> !MESSAGE Your original request has been modified.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Mylyn Commons" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Eclipse Git Team Provider" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Mylyn Task-Focused Interface" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.692
> !MESSAGE "Eclipse Git Team Provider - Task focused interface" will be ignored because a newer version is already installed.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Atlassian JIRA Connector (Recommended)" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Java implementation of Git" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Mylyn Task List" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Mylyn Tasks Connector: Bugzilla" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.693
> !MESSAGE "Mylyn Context Connector: Eclipse IDE" will be ignored because a newer version is already installed.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.693
> !MESSAGE "Mylyn Context Connector: Java Development" will be ignored because a newer version is already installed.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.693
> !MESSAGE "Mylyn Context Connector: Team Support" will be ignored because a newer version is already installed.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.693
> !MESSAGE "Atlassian Connector for Eclipse Usage Monitoring" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10005 2015-11-27 20:08:18.693
> !MESSAGE "JBoss Tools Common - Mylyn" will be ignored because it is already installed.
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 10054 2015-11-27 20:08:18.693
> !MESSAGE Cannot complete the install because of a conflicting dependency.
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE Software being installed: Spring IDE AJDT Integration (optional) 3.7.0.201506251244-RELEASE (org.springframework.ide.eclipse.ajdt.feature.feature.group 3.7.0.201506251244-RELEASE)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.6.0.20151001-0600 (epp.package.jee 4.6.0.20151001-0600)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
> !MESSAGE Only one of the following can be installed at once:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE Java Code Manipulation Functionality 1.5.0.v20120523-1543 (org.eclipse.jdt.core.manipulation 1.5.0.v20120523-1543)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE Java Code Manipulation Functionality 1.7.0.v20150713-1605 (org.eclipse.jdt.core.manipulation 1.7.0.v20150713-1605)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE From: Eclipse IDE for Java EE Developers 4.6.0.20151001-0600 (epp.package.jee 4.6.0.20151001-0600)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE To: org.eclipse.epp.package.jee.feature.feature.group [4.6.0.20151001-0600]
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE From: AspectJ Development Tools Core 2.2.4.e44x-20140516-1000 (org.eclipse.ajdt.core 2.2.4.e44x-20140516-1000)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE To: bundle org.eclipse.jdt.core.manipulation [1.3.0,1.7.0)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: EPP Java EE IDE Feature 4.6.0.20151001-0600 (org.eclipse.epp.package.jee.feature.feature.group 4.6.0.20151001-0600)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: org.eclipse.jdt.feature.group 0.0.0
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: Eclipse Java Development Tools 3.11.0.v20150805-2000 (org.eclipse.jdt.feature.group 3.11.0.v20150805-2000)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: org.eclipse.jdt.core.manipulation [1.7.0.v20150713-1605]
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: Eclipse Java Development Tools 3.12.0.v20150916-2000 (org.eclipse.jdt.feature.group 3.12.0.v20150916-2000)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: org.eclipse.jdt.core.manipulation [1.7.0.v20150713-1605]
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: Eclipse Java Development Tools 3.12.0.v20151029-1349 (org.eclipse.jdt.feature.group 3.12.0.v20151029-1349)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: org.eclipse.jdt.core.manipulation [1.7.0.v20150713-1605]
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: Spring IDE AJDT Integration (optional) 3.7.0.201506251244-RELEASE (org.springframework.ide.eclipse.ajdt.feature.feature.group 3.7.0.201506251244-RELEASE)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: org.springframework.ide.eclipse.ajdt.ui.xref [3.7.0.201506251244-RELEASE]
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: Spring IDE AOP Xref UI 3.7.0.201506251244-RELEASE (org.springframework.ide.eclipse.ajdt.ui.xref 3.7.0.201506251244-RELEASE)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: package org.eclipse.ajdt.core 0.0.0
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months