[JBoss JIRA] (JBIDE-20850) target platform matrix job's install test step fails silently when using incompatible Eclipse version
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20850?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20850:
-------------------------------
Sprint: (was: devex #114 May 2016)
> target platform matrix job's install test step fails silently when using incompatible Eclipse version
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20850
> URL: https://issues.jboss.org/browse/JBIDE-20850
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.x
>
>
> For some reason, the targetplatforms-matrix job is ignoring this, and still getting blue balls when it can't install the built target platform:
> {code}
> [p2.dir] !MESSAGE Software being installed: Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755)
> [p2.dir] !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.5.1.20150910-0554 (epp.package.jee 4.5.1.20150910-0554)
> [p2.dir] !MESSAGE Only one of the following can be installed at once:
> [p2.dir] !MESSAGE Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755)
> [p2.dir] !MESSAGE Eclipse IDE UI 3.11.0.v20150825-2158 (org.eclipse.ui.ide 3.11.0.v20150825-2158)
>
> BUILD FAILED
> /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/85031d6f/director.xml:62: exec returned: 13
> {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> {code}
> [p2.dir] !MESSAGE Only one of the following can be installed at once:
> [p2.dir] !MESSAGE Refactoring Core 3.6.201.v20150819-1034 (org.eclipse.ltk.core.refactoring 3.6.201.v20150819-1034)
> [p2.dir] !MESSAGE Refactoring Core 3.6.200.v20140826-0859 (org.eclipse.ltk.core.refactoring 3.6.200.v20140826-0859)
> {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> And yet the build is successful here:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> This is most likely because all three configs are set to use the same Eclipse JEE bundle:
> {code}downloadURL=http://www.eclipse.org/downloads/download.php?r=1&file=/technology/epp/downloads/release/mars/1/eclipse-jee-mars-1-linux-gtk.tar.gz
> {code}
> So... I guess there are two things we need here:
> a) ensure that the TP and Eclipse versions are compatible (4.50 == mars-R, 4.51 == mars-1, 4.60 == neon-M1) in the job config, rather than trying to install the 4.50 or 4.60 TPs onto Eclipse Mars.1
> b) ensure that the log is checked for the string "BUILD FAILED" or "director.xml .* exec returned: 13" and if found, fail the build
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-19715) Get rid of "fullSite", stick with "repository"
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19715:
-------------------------------
Sprint: (was: devex #114 May 2016)
> Get rid of "fullSite", stick with "repository"
> ----------------------------------------------
>
> Key: JBIDE-19715
> URL: https://issues.jboss.org/browse/JBIDE-19715
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.4.x
>
>
> Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2044:
-----------------------------
Sprint: (was: devex #114 May 2016)
> .eclipseproduct file no longer refers to JBDS
> ---------------------------------------------
>
> Key: JBDS-2044
> URL: https://issues.jboss.org/browse/JBDS-2044
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 5.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Labels: discuss
> Fix For: 10.0.0.Alpha3
>
>
> Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read:
> {code}
> name=JBoss Developer Studio
> id=com.jboss.jbds.all
> version=5.0.0.v201202271832M-H79-Beta1
> {code}
> Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads:
> {code}
> name=Eclipse Platform
> id=org.eclipse.platform
> version=3.7.0
> {code}
> Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ]
Martin Malina edited comment on JBDS-3739 at 5/24/16 12:02 PM:
---------------------------------------------------------------
I can confirm that it doesn't work for me either.
When I start JBDS 10.0.0.Alpha2, set up cdk and start it for the first time (clean workspace), it works. Then I stop it, start again.
This time the docker connection in docker explorer was grey/inactive and the cdk adapter was stuck on Starting. And eventually my jbds froze and kept exhausting my cpu.
Then I killed it and repeated with a new workspace. This time I got exactly the same result as Marian - on second start of cdk, Docker connection didn't work and I got this error:
{code}
Error contacting OpenShift
The CDK VM is up and running, but OpenShift is unreachable at url https://10.1.2.2:8443/healthz/ready
{code}
Eventually, Eclipse froze again.
So just to be superclear, let me repeat the steps:
1. Start with a new workspace
2. Set up a CDK server
3. Start CDK
4. Stop CDK
5. Open Docker Explorer
6. Start CDK
7. Once started, try to expand the docker connection in Docker Explorer view
Now the docker connection is displayed in grey and my Eclipse instance froze right away (sometimes it may take a few minutes before it freezes)
was (Author: mmalina):
I can confirm that it doesn't work for me either.
When I start JBDS 10.0.0.Alpha2, set up cdk and start it for the first time (clean workspace), it works. Then I stop it, start again.
This time the docker connection in docker explorer was grey/inactive and the cdk adapter was stuck on Starting. And eventually my jbds froze and kept exhausting my cpu.
Then I killed it and repeated with a new workspace. This time I got exactly the same result as Marian - on second start of cdk, Docker connection didn't work and I got this error:
{code}
Error contacting OpenShift
The CDK VM is up and running, but OpenShift is unreachable at url https://10.1.2.2:8443/healthz/ready
{code}
> Docker connection does not work after cdk restart
> -------------------------------------------------
>
> Key: JBDS-3739
> URL: https://issues.jboss.org/browse/JBDS-3739
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: cdk, platform-installer, upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Martin Malina
> Assignee: Marián Labuda
> Priority: Blocker
> Labels: havoc
> Fix For: 10.x
>
>
> When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work.
> This is caused by a bug in vagrant-service-manager 0.0.4:
> https://github.com/projectatomic/vagrant-service-manager/issues/80
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22247) Reorganize context menus of OpenShift Resources in properties view
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22247?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22247:
---------------------------------------
Deployment config could have Scale item and Deploy Latest in same section, those items do not have to be separated by separator.
Image stream should have Refresh item in same section as Show In (it should be moved to the top of the context menu).
Build should have Refresh item in same section as Show In (it should be moved to the top of the context menu). Delete context menu item should be in following section (in 2nd section).
> Reorganize context menus of OpenShift Resources in properties view
> ------------------------------------------------------------------
>
> Key: JBIDE-22247
> URL: https://issues.jboss.org/browse/JBIDE-22247
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, properties, ux
> Fix For: 4.4.x
>
> Attachments: bc_cm.png, build_cm.png, dc_cm.png, pod_cm.png, rc_cm.png, route_cm.png, service_cm.png
>
>
> Context menus of OpenShift resources in Properties view are quite messy. It could be ordered better. For reference check Eclipse guidelines on context menus of objects in views https://wiki.eclipse.org/User_Interface_Guidelines#Context_Menus_2
> See screenshots of context menus
> *Build config*
> !bc_cm.png!
> *Build*
> !build_cm.png!
> *Deployment Config*
> !dc_cm.png!
> *Pod*
> !pod_cm.png!
> *Service*
> !service_cm.png!
> *Route*
> !route_cm.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-191) ClassCastException from KeywordCompletionProposalComputer & IdentifierCompletionProposalComputer witn Neon M7 [EBZ#493393]
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/ERT-191?page=com.atlassian.jira.plugin.sy... ]
Victor Rubezhny reassigned ERT-191:
-----------------------------------
Assignee: Victor Rubezhny
> ClassCastException from KeywordCompletionProposalComputer & IdentifierCompletionProposalComputer witn Neon M7 [EBZ#493393]
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: ERT-191
> URL: https://issues.jboss.org/browse/ERT-191
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Victor Rubezhny
> Labels: General, bzira
>
> The Eclipse Neon M7 provides KeywordCompletionProposalComputer & IdentifierCompletionProposalComputer classes which doesn't use "instanceof" to check that the given ContentAssistInvocationContext is a JavaContentAssistInvocationContext:
> ```
> public class IdentifierCompletionProposalComputer implements IJavaCompletionProposalComputer {
> public List computeCompletionProposals(ContentAssistInvocationContext context, IProgressMonitor monitor) {
> JavaContentAssistInvocationContext javaContext = (JavaContentAssistInvocationContext) context;
> ```
> It's a big problem for typescript.java which is based on JSDT and which defines TypeScriptContentAssistInvocationContext (see issue at
> https://github.com/angelozerr/typescript.java/issues/56)
> So with oEclipse Neon M7, when I do completion with my TypeScriptEditor based on JSDT Edit, I have a popup error with this error
> ```
> java.lang.ClassCastException: ts.eclipse.ide.jsdt.internal.ui.editor.contentassist.TypeScriptContentAssistInvocationContext cannot be cast to org.eclipse.wst.jsdt.ui.text.java.JavaContentAssistInvocationContext
> at org.eclipse.wst.jsdt.internal.ui.text.java.KeywordCompletionProposalComputer.computeCompletionProposals(KeywordCompletionProposalComputer.java:45)
> ```
> and
> ```
> java.lang.ClassCastException: ts.eclipse.ide.jsdt.internal.ui.editor.contentassist.TypeScriptContentAssistInvocationContext cannot be cast to org.eclipse.wst.jsdt.ui.text.java.JavaContentAssistInvocationContext
> at org.eclipse.wst.jsdt.internal.ui.text.java.IdentifierCompletionProposalComputer.computeCompletionProposals(IdentifierCompletionProposalComputer.java:49)
> ```
> It should b every cool if you could check that ContentAssistInvocationContext is an instanceof JavaContentAssistInvocationContext:
> ```
> public class IdentifierCompletionProposalComputer implements IJavaCompletionProposalComputer {
> public List computeCompletionProposals(ContentAssistInvocationContext context, IProgressMonitor monitor) {
> if (context instanceof JavaContentAssistInvocationContext) {
> JavaContentAssistInvocationContext javaContext = (JavaContentAssistInvocationContext) context;
> ```
> for :
> * http://git.eclipse.org/c/jsdt/webtools.jsdt.git/tree/bundles/org.eclipse....
> * http://git.eclipse.org/c/jsdt/webtools.jsdt.git/tree/bundles/org.eclipse....
> For your infomration, I have created my own TypeScriptContentAssistInvocationContext, because I need IResource and I don't use IJavaCompilationUnit. If http://git.eclipse.org/c/jsdt/webtools.jsdt.git/tree/bundles/org.eclipse.... could just define a getter for the Editor, I think I could use directly JavaContentAssistInvocationContext to retrieve my IResource from the getEditor getter.
> Hope this issue will be able to fixed for Neon release, otherwise typescript.java will not work with Eclipse Neon release -( (we must desactivate the whole JSDT completions to avoid having those 2 popup errors)
> Many thanks for your help!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22197) Icon in template Details of Local Template is not loaded for some templates file
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22197?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22197:
-------------------------------
Sprint: devex #115 May 2016
> Icon in template Details of Local Template is not loaded for some templates file
> --------------------------------------------------------------------------------
>
> Key: JBIDE-22197
> URL: https://issues.jboss.org/browse/JBIDE-22197
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.4.0.Alpha3
>
> Attachments: quickstart-template.json, screenshot-1.png
>
>
> {noformat}
> java.io.FileNotFoundException: /icons/apps/java.png
> at org.eclipse.osgi.storage.url.bundleentry.Handler.findBundleEntry(Handler.java:37)
> at org.eclipse.osgi.storage.url.BundleResourceHandler.openConnection(BundleResourceHandler.java:169)
> at java.net.URL.openConnection(Unknown Source)
> at org.eclipse.osgi.storage.url.BundleURLConverter.toFileURL(BundleURLConverter.java:32)
> at org.eclipse.core.runtime.FileLocator.toFileURL(FileLocator.java:207)
> at org.eclipse.jface.resource.URLImageDescriptor.getFilePath(URLImageDescriptor.java:219)
> at org.eclipse.jface.resource.URLImageDescriptor.createImage(URLImageDescriptor.java:283)
> at org.eclipse.jface.resource.ImageDescriptor.createResource(ImageDescriptor.java:164)
> at org.eclipse.jface.resource.DeviceResourceManager.allocate(DeviceResourceManager.java:52)
> at org.eclipse.jface.resource.AbstractResourceManager.create(AbstractResourceManager.java:86)
> at org.eclipse.jface.resource.ResourceManager.createImageWithDefault(ResourceManager.java:192)
> at org.eclipse.jface.resource.ImageRegistry.get(ImageRegistry.java:214)
> at org.jboss.tools.openshift.internal.common.ui.ImageRepository.getImage(ImageRepository.java:85)
> at org.jboss.tools.openshift.internal.ui.OpenShiftImages.getAppImage(OpenShiftImages.java:62)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateDetailViews$TemplateDetailView.updateImage(TemplateDetailViews.java:106)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateDetailViews$TemplateDetailView.onVisible(TemplateDetailViews.java:102)
> at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews.showView(AbstractStackedDetailViews.java:90)
> at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews.showView(AbstractStackedDetailViews.java:79)
> at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews$1.handleValueChange(AbstractStackedDetailViews.java:73)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:57)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:99)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months