[JBoss JIRA] (JBIDE-18274) AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18274?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18274:
--------------------------------
Fix Version/s: 4.3.0.Alpha1
(was: 4.2.x)
> AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
> -------------------------------------------------------------------------------
>
> Key: JBIDE-18274
> URL: https://issues.jboss.org/browse/JBIDE-18274
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.0.Alpha1
>
> Attachments: server-adapter.png, server-editor.png, server-logs.png, server-runtime.png
>
>
> This is a follow up of JBIDE-17935 .
> Previously, Rob fixed this:
> {quote}
> I've surprisingly been able to replicate this and it's a race-condition. I'll need to synchronize some variables in this class here.
> {quote}
> But in this rare case it still fails for me.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (JBIDE-18274) AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18274?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18274:
-------------------------------------
I'm also not able to replicate this. I tried using wf8 and web poller as well as mgmt poller. All seems to work as expected.
I'm going to downgrade to minor for now. Unless we can get anyone else to replicate, I may close the issue in a month or two.
> AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
> -------------------------------------------------------------------------------
>
> Key: JBIDE-18274
> URL: https://issues.jboss.org/browse/JBIDE-18274
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha1
>
> Attachments: server-adapter.png, server-editor.png, server-logs.png, server-runtime.png
>
>
> This is a follow up of JBIDE-17935 .
> Previously, Rob fixed this:
> {quote}
> I've surprisingly been able to replicate this and it's a race-condition. I'll need to synchronize some variables in this class here.
> {quote}
> But in this rare case it still fails for me.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (JBIDE-18274) AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18274?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18274:
--------------------------------
Priority: Minor (was: Major)
> AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
> -------------------------------------------------------------------------------
>
> Key: JBIDE-18274
> URL: https://issues.jboss.org/browse/JBIDE-18274
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: server-adapter.png, server-editor.png, server-logs.png, server-runtime.png
>
>
> This is a follow up of JBIDE-17935 .
> Previously, Rob fixed this:
> {quote}
> I've surprisingly been able to replicate this and it's a race-condition. I'll need to synchronize some variables in this class here.
> {quote}
> But in this rare case it still fails for me.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-3200:
-------------------------------------
For reference, here's a link to Apple KB detailing the workaround: http://support.apple.com/kb/PH14369?viewlocale=en_US&locale=en_US
> Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning
> --------------------------------------------------------------------------------------------
>
> Key: JBDS-3200
> URL: https://issues.jboss.org/browse/JBDS-3200
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 8.0.0.GA
> Environment: Mac OS X 10.10, JDK 1.8.0
> Reporter: Manuel Blechschmidt
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: LATER
>
> Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png
>
>
> Hello,
> I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here:
> https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014...
> Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store.
> {panel}
> "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer.
> Your security preferences allow installation of only app from the Mac App Store and identified developers.
> {panel}
> Right click on the file and then selecting open gives me the opportunity to ignore this warning.
> Nevertheless it might happen that users don't know this solution.
> Hope that helps
> Manuel
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (JBIDE-18714) Invalid error message when @Target is missing on a custom Name Binding annotation
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18714?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-18714:
----------------------------------
Description:
With the following code:
{code}
@NameBinding
@Retention(RetentionPolicy.RUNTIME)
public @interface LoggingBinding {
}
{code}
The error message is
{quote}
The Name Binding should have a @Target(ElementType.METHOD) annotation on its type.
{quote}
but it should be
{quote}
The Name Binding should have a @Target(\{ElementType.TYPE, ElementType.METHOD\}) annotation on its type.
{quote}
Note that the QuickFix adds the correct {{(a)Target(\{ElementType.TYPE, ElementType.METHOD\})}}, it's just that the initial error message was misleading
was:
With the following code:
{code}
@NameBinding
@Retention(RetentionPolicy.RUNTIME)
public @interface LoggingBinding {
}
{code}
The error message is
{quote}
The Name Binding should have a @Target(ElementType.METHOD) annotation on its type.
{quote}
but it should be
{quote}
The Name Binding should have a @Target({ElementType.TYPE, ElementType.METHOD}) annotation on its type.
{quote}
Note that the QuickFix adds the correct {{(a)Target({ElementType.TYPE, ElementType.METHOD})}}, but the error message was misleading
> Invalid error message when @Target is missing on a custom Name Binding annotation
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-18714
> URL: https://issues.jboss.org/browse/JBIDE-18714
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> With the following code:
> {code}
> @NameBinding
> @Retention(RetentionPolicy.RUNTIME)
> public @interface LoggingBinding {
> }
> {code}
> The error message is
> {quote}
> The Name Binding should have a @Target(ElementType.METHOD) annotation on its type.
> {quote}
> but it should be
> {quote}
> The Name Binding should have a @Target(\{ElementType.TYPE, ElementType.METHOD\}) annotation on its type.
> {quote}
> Note that the QuickFix adds the correct {{(a)Target(\{ElementType.TYPE, ElementType.METHOD\})}}, it's just that the initial error message was misleading
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (JBIDE-18714) Invalid error message when @Target is missing on a custom Name Binding annotation
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-18714:
-------------------------------------
Summary: Invalid error message when @Target is missing on a custom Name Binding annotation
Key: JBIDE-18714
URL: https://issues.jboss.org/browse/JBIDE-18714
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.2.0.Final
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.2.1.Final, 4.3.0.Alpha1
With the following code:
{code}
@NameBinding
@Retention(RetentionPolicy.RUNTIME)
public @interface LoggingBinding {
}
{code}
The error message is
{quote}
The Name Binding should have a @Target(ElementType.METHOD) annotation on its type.
{quote}
but it should be
{quote}
The Name Binding should have a @Target({ElementType.TYPE, ElementType.METHOD}) annotation on its type.
{quote}
Note that the QuickFix adds the correct {{(a)Target({ElementType.TYPE, ElementType.METHOD})}}, but the error message was misleading
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-3200:
-------------------------------------
Thanks for the report. I just verified that this happens to me also, but I never experienced it since I usually start the installer from the command line.
And that's also documented here:
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu...
{quote}
Start the installer
{code}
$ cd /path/to/.jar
$ java -jar jboss-devstudio-version-installer-standalone.jar
{code}
Alternatively, you may be able to start the installer by double-clicking the .jar file.
{quote}
[~mmurray], perhaps this could be added as a note to the install guide?
Otherwise I agree it would be nice to avoid this, but after a few minutes of googling I couldn't find if there is any way to sign a jar the same way an app on os x is signed (using an apple identified developer ID).
> Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning
> --------------------------------------------------------------------------------------------
>
> Key: JBDS-3200
> URL: https://issues.jboss.org/browse/JBDS-3200
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 8.0.0.GA
> Environment: Mac OS X 10.10, JDK 1.8.0
> Reporter: Manuel Blechschmidt
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: LATER
>
> Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png
>
>
> Hello,
> I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here:
> https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014...
> Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store.
> {panel}
> "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer.
> Your security preferences allow installation of only app from the Mac App Store and identified developers.
> {panel}
> Right click on the file and then selecting open gives me the opportunity to ignore this warning.
> Nevertheless it might happen that users don't know this solution.
> Hope that helps
> Manuel
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (JBIDE-18572) NPE while calling a diff between 2 versions of a JS file
by Andrei Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18572?page=com.atlassian.jira.plugi... ]
Andrei Ivanov edited comment on JBIDE-18572 at 10/29/14 7:04 AM:
-----------------------------------------------------------------
Can you try this scenario?
Go into synchronize view, double click an existing file, modify it in the compare view and save.
Then click on another file to compare.
I see this triggers the problem for me.
was (Author: andrei.ivanov):
Can you try this scenario?
Go into synchronize view, double click and existing file, modify it in the compare view and save.
Then click on another file to compare.
I see this triggers the problem for me.
> NPE while calling a diff between 2 versions of a JS file
> --------------------------------------------------------
>
> Key: JBIDE-18572
> URL: https://issues.jboss.org/browse/JBIDE-18572
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Fix For: 4.2.1.Final
>
>
> Not sure if the error is related {{summarry}}, but here's the stacktrace:
> I did compare my current JS file with the first version in my history, which was an empty file, then I called the diff with the next version and I got this error. I kept having this error when comparing the current version with any other version of the file (if that can help to reproduce/identify the problem)
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.vpe.preview.editor.VpvEditor.formRequestToServer(VpvEditor.java:572)
> at org.jboss.tools.vpe.preview.editor.VpvEditor.access$0(VpvEditor.java:551)
> at org.jboss.tools.vpe.preview.editor.VpvEditor$EditorListener.partInputChanged(VpvEditor.java:674)
> at org.eclipse.ui.internal.WorkbenchPage$28.run(WorkbenchPage.java:5151)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartInputChanged(WorkbenchPage.java:5148)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$4.propertyChanged(CompatibilityPart.java:369)
> at org.eclipse.ui.part.WorkbenchPart.firePropertyChange(WorkbenchPart.java:132)
> at org.eclipse.compare.internal.CompareEditor.doSetInput(CompareEditor.java:313)
> at org.eclipse.compare.internal.CompareEditor.setInput(CompareEditor.java:254)
> at org.eclipse.compare.internal.CompareUIPlugin$1.run(CompareUIPlugin.java:546)
> at org.eclipse.compare.internal.CompareUIPlugin.syncExec(CompareUIPlugin.java:1413)
> at org.eclipse.compare.internal.CompareUIPlugin.internalOpenEditor(CompareUIPlugin.java:567)
> at org.eclipse.compare.internal.CompareUIPlugin.openEditorInBackground(CompareUIPlugin.java:537)
> at org.eclipse.compare.internal.CompareUIPlugin.openCompareEditor(CompareUIPlugin.java:526)
> at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:199)
> at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:180)
> at org.eclipse.team.internal.ui.actions.CompareRevisionAction.openInCompare(CompareRevisionAction.java:139)
> at org.eclipse.team.internal.ui.actions.CompareRevisionAction.run(CompareRevisionAction.java:102)
> at org.eclipse.team.internal.ui.history.LocalHistoryPage$9.open(LocalHistoryPage.java:414)
> at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48)
> at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:853)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178)
> at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:850)
> at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1142)
> at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1249)
> at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:278)
> at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:272)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:313)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:484)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months