[JBoss JIRA] (JBIDE-22625) Remote server with FS operations: Unable to retrieve a list of remote deployment scanners
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22625?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22625:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.AM2)
> Remote server with FS operations: Unable to retrieve a list of remote deployment scanners
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22625
> URL: https://issues.jboss.org/browse/JBIDE-22625
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
>
> Previously I reported this as part of JBIDE-22605, but I think it deserves its own issue.
> When I setup a remote EAP 7 server with FS operations and then start it, I always get this in the error log:
> Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 7.0
> Today, I also noticed this info message in the error view:
> org.eclipse.rse.core
> Saved passwords are not available for migration to secure storage. Deprecated authorization classes (org.eclipse.core.runtime.compatibility.auth) are not installed.
> I wonder if this is related? Do we require authentication to get the list of deployment scanners?
> BTW, org.eclipse.core.runtime.compatibility was removed in JBIDE-21382 and I suggested org.eclipse.core.runtime.compatibility.auth may be removed too - JBIDE-22602. But as of now it's still in the TP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24579) Can't import push-helloworld-cordova project
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24579?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24579:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.AM2)
> Can't import push-helloworld-cordova project
> --------------------------------------------
>
> Key: JBIDE-24579
> URL: https://issues.jboss.org/browse/JBIDE-24579
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.5.0.AM1
> Environment: JBT 4.5.0.AM1 (stage) or devstudio-11.0.0.AM1-v20170622-1352-B295, Fedora 25 (wayland disabled), openjdk version "1.8.0_131"
> Reporter: Lukáš Valach
> Assignee: Fred Bricon
> Fix For: 4.5.x
>
> Attachments: push-helloworld-cordova.png
>
>
> I can't install "push-helloworld-cordova" project from RH Central. During the installation I got a window with message *"push-helloworld-cordova project has not been fully imported. Check if it is defined correctly"*. I see that the project has been downloaded successfully but it wasn't imported (it isn't displayed in Project Explorer).
> I tried to import project from the disk into the Eclipse and it worked without problems. There is no error in the log.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21857:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.AM1)
> Hot code replacement doesn't work on OpenShift
> ----------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-18565) Default generated entity is invalid
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18565?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18565:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.AM1)
> Default generated entity is invalid
> -----------------------------------
>
> Key: JBIDE-18565
> URL: https://issues.jboss.org/browse/JBIDE-18565
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate, upstream
> Reporter: Arun Gupta
> Assignee: Koen Aers
> Fix For: 4.5.x
>
>
> Code for a default generated JPA entity looks like:
> package org.svcc;
> import java.io.Serializable;
> import javax.persistence.*;
> /**
> * Entity implementation class for Entity: Student
> *
> */
> @Entity
> public class Student implements Serializable {
>
> private static final long serialVersionUID = 1L;
> public Student() {
> super();
> }
>
> }
> This is an invalid entity because each JPA entity must have a primary key.
> For a simpler OOTB experience, generate a default primary key.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21719:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.AM1)
> Move Properties view to its previous position
> ---------------------------------------------
>
> Key: JBIDE-21719
> URL: https://issues.jboss.org/browse/JBIDE-21719
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2
> JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build)
> Reporter: Andrej Podhradsky
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.5.x
>
> Attachments: JBossPerspective_PropertiesMayBeWider.png, jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png, jbds910_narrow_properties_view.png
>
>
> I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-19568) Disable the "Check for update" button while a check for update is in progress
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-19568:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.AM1)
> Disable the "Check for update" button while a check for update is in progress
> -----------------------------------------------------------------------------
>
> Key: JBIDE-19568
> URL: https://issues.jboss.org/browse/JBIDE-19568
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Fix For: 4.5.x
>
>
> while trying to check JBIDE-18559 I clicked "checked for updates" in central and got nothing, not even a dialog.
> In error log it was reporting this:
> org.eclipse.equinox.p2.core.ProvisionException: No repository found at file:/Users/max/code/jbdevstudio/linuxtools-docker/org.eclipse.linuxtools.docker.core/target/.
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
> at sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:116)
> at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.fail(CachingRepositoryManager.java:284)
> at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:191)
> at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:378)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102)
> at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83)
> at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> would have expected we told the user about this error.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months