[JBoss JIRA] (JBIDE-22815) JavaModelException below AttachSourcesActionDelegate.setActiveEditor (thrown in JavaElement.newJavaModelException)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22815?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-22815:
----------------------------------
Assignee: Fred Bricon
> JavaModelException below AttachSourcesActionDelegate.setActiveEditor (thrown in JavaElement.newJavaModelException)
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22815
> URL: https://issues.jboss.org/browse/JBIDE-22815
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.4.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Fred Bricon
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> org.eclipse.jdt.core.JavaModelException: HIDDEN
> at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
> at org.eclipse.jdt.internal.core.PackageFragmentRoot.getKind(PackageFragmentRoot.java:486)
> at org.eclipse.jdt.internal.core.PackageFragmentRoot.getSourceAttachmentPath(PackageFragmentRoot.java:600)
> at org.jboss.tools.maven.sourcelookup.ui.actions.AttachSourcesActionDelegate.setActiveEditor(AttachSourcesActionDelegate.java:93)
> at org.eclipse.ui.internal.EditorPluginAction.editorChanged(EditorPluginAction.java:71)
> at org.eclipse.ui.internal.EditorActionBuilder$EditorContribution.editorChanged(EditorActionBuilder.java:80)
> at org.eclipse.ui.internal.EditorActionBuilder$ExternalContributor.setActiveEditor(EditorActionBuilder.java:129)
> at org.eclipse.ui.internal.EditorActionBars.partChanged(EditorActionBars.java:344)
> at org.eclipse.ui.internal.WorkbenchPage.updateActivations(WorkbenchPage.java:302)
> at org.eclipse.ui.internal.WorkbenchPage.access$18(WorkbenchPage.java:284)
> at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:202)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:245)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:242)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:711)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:639)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:634)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1164)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3252)
> at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3167)
> at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3149)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3144)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3108)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3098)
> at org.eclipse.ui.ide.IDE.openEditor(IDE.java:541)
> at org.eclipse.ui.ide.IDE.openEditor(IDE.java:500)
> at org.eclipse.ui.internal.ide.handlers.OpenResourceHandler.execute(OpenResourceHandler.java:132)
> at org.eclipse.ui.internal.ide.handlers.OpenResourceHandler.run(OpenResourceHandler.java:187)
> at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute(ActionDelegateHandlerProxy.java:299)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor.invoke(null:-1)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> {noformat}
> Bundles:
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
> | org.eclipse.dltk.ui | 5.4.0.201602110510 | 5.4.0.201602110510 |
> | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.6.0.v20160319-0612 |
> | org.eclipse.e4.ui.workbench | 1.3.0.v20150531-1948 | 1.4.0.v20160517-1624 |
> | org.eclipse.e4.ui.workbench.renderers.swt | 0.13.0.v20150901-1347 | 0.14.0.v20160525-0940 |
> | org.eclipse.e4.ui.workbench.swt | 0.13.0.v20150504-0621 | 0.14.0.v20160523-1900 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.12.0.v20160516-2131 |
> | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.12.0.v20160525-1829 |
> | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 |
> | org.eclipse.jst.servlet.ui | 1.1.801.v201409042158 | 1.1.801.v201409042158 |
> | org.eclipse.php.ui | 3.7.0.201602121754 | 3.7.0.201602121754 |
> | org.eclipse.search | 3.10.0.v20150318-0856 | 3.10.0.v20150318-0856 |
> | org.eclipse.swt | 3.104.1.v20150825-0743 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.eclipse.ui.ide | 3.11.0.v20150825-2158 | 3.12.0.v20160601-1609 |
> | org.eclipse.ui.navigator | 3.6.0.v20150422-0725 | 3.6.100.v20160518-1929 |
> | org.eclipse.ui.views | 3.8.0.v20150422-0725 | 3.8.0.v20150422-0725 |
> | org.jboss.tools.maven.sourcelookup.ui | 1.7.1.Final-v20160401-1059-B103 | 1.8.0.Final-v20160613-2000-B8 |
> Operating Systems:
> | Linux | 3.13.0 | 4.4.0 |
> | MacOSX | 10.11.5 | 10.11.5 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5719d0a3e4b04d6a2b...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23128) Eclipse Neon.1 Blog
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23128?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-23128:
--------------------------------
Issue Type: Task (was: Feature Request)
> Eclipse Neon.1 Blog
> --------------------
>
> Key: JBIDE-23128
> URL: https://issues.jboss.org/browse/JBIDE-23128
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: upstream, website
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Fix For: 4.4.2.AM1
>
>
> Need to write blog about Neon.1 JSDT improvements. Tentative structure:
> - Node.js Debugger improvements
> - New JavaScript Debugger
> - npm scripts support
> - OMPH installer support
> - Important bug fixes (provide a query with all Neon.1 bug fixes)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-772) New Hibernate Project
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-772?page=com.atlassian.jira.plugin.... ]
Koen Aers resolved JBIDE-772.
-----------------------------
Fix Version/s: (was: LATER)
Resolution: Out of Date
We now use Maven to do the project setup and library management for us. If anything else is needed, feel free to reopen the issue.
> New Hibernate Project
> ---------------------
>
> Key: JBIDE-772
> URL: https://issues.jboss.org/browse/JBIDE-772
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: z - Legacy - libmanagement
> Reporter: Max Rydahl Andersen
> Assignee: Koen Aers
> Priority: Minor
> Labels: libmanagement
>
> Provide a New Hibernate project wizard that setups the basics. Libraries etc.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-18535) Opening of wizards from forge cheatsheet does not result in "attached cheatsheet"
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18535?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-18535:
-----------------------------------
[~gastaldi] Not sure if this issue is still current? Should it be closed?
> Opening of wizards from forge cheatsheet does not result in "attached cheatsheet"
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-18535
> URL: https://issues.jboss.org/browse/JBIDE-18535
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge, project-examples
> Reporter: Max Rydahl Andersen
> Assignee: Koen Aers
> Fix For: 4.4.x
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> I'm not sure what is the cause of this but I just noticed that when I launch a forge wizard from the forge cheat sheets the cheat sheet is "stuck" in the overall perspective.
> But when I open a wizard in the Java Development/Create a Hello World Application the cheatsheet behaves as expected and is attached to the wizard (see screenshot)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22626:
-------------------------------------
Description:
In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok.
But if user deploys image with tag e.g. :0.8 to OpenShift, resources are created for this specific tag. When I am trying to Deploy to OS image with tag :0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag :0.8 and thus new deployment is not done.
Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it.
In order to add this version tag after semicolon, right-click on the image -> Add tag -> Re-type namespace/imagename + add ":0.8" e.g.
was:
In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok.
But if user deploys image with tag e.g. 0.8 to OpenShift, resources are created for this specific tag. When I am trying to push image with tag 0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag 0.8 and thus new deployment is not done.
Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it.
> Updating deployed docker image on OpenShift does not work
> ---------------------------------------------------------
>
> Key: JBIDE-22626
> URL: https://issues.jboss.org/browse/JBIDE-22626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Priority: Critical
> Labels: docker, openshift_v3
> Fix For: 4.4.1.Final
>
>
> In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok.
> But if user deploys image with tag e.g. :0.8 to OpenShift, resources are created for this specific tag. When I am trying to Deploy to OS image with tag :0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag :0.8 and thus new deployment is not done.
> Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it.
> In order to add this version tag after semicolon, right-click on the image -> Add tag -> Re-type namespace/imagename + add ":0.8" e.g.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months