[JBoss JIRA] (JBIDE-17180) Disable custom deployment settings for remote servers without management port exposed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17180:
-------------------------------------
Experiencing following stacktrace:
{code}
!STACK 0
java.lang.NullPointerException
at org.jboss.ide.eclipse.as.ui.editor.internal.JBossDeploymentOptionsComposite$RadioClickedCommand.execute(JBossDeploymentOptionsComposite.java:581)
at org.eclipse.wst.server.ui.internal.command.ServerCommand.execute(ServerCommand.java:39)
at org.eclipse.wst.server.ui.internal.editor.GlobalCommandManager.executeCommand(GlobalCommandManager.java:345)
at org.eclipse.wst.server.ui.internal.editor.ServerResourceCommandManager.execute(ServerResourceCommandManager.java:54)
at org.jboss.ide.eclipse.as.ui.editor.DeploymentPage.execute(DeploymentPage.java:117)
at org.jboss.ide.eclipse.as.ui.editor.internal.JBossDeploymentOptionsComposite.radioSelected(JBossDeploymentOptionsComposite.java:486)
at org.jboss.ide.eclipse.as.ui.editor.internal.JBossDeploymentOptionsComposite$2.widgetSelected(JBossDeploymentOptionsComposite.java:288)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
{code}
> Disable custom deployment settings for remote servers without management port exposed
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-17180
> URL: https://issues.jboss.org/browse/JBIDE-17180
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.x
>
>
> JBIDE-13445 added the possibility to use custom deploy dir on remote server.
> {quote}
> Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail.
> {quote}
> We should disable this option in such case, because right now it just adds confusion - you have a server without management port exposed and not knowing about all the details you change the deployment dir, you will end up with non-working deployment.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (JBIDE-17180) Disable custom deployment settings for remote servers without management port exposed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17180:
-------------------------------------
Just a note: The workflow for this issue is to have a server configured as remote + fs/shell operations.
> Disable custom deployment settings for remote servers without management port exposed
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-17180
> URL: https://issues.jboss.org/browse/JBIDE-17180
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.x
>
>
> JBIDE-13445 added the possibility to use custom deploy dir on remote server.
> {quote}
> Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail.
> {quote}
> We should disable this option in such case, because right now it just adds confusion - you have a server without management port exposed and not knowing about all the details you change the deployment dir, you will end up with non-working deployment.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[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)
11 years
[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)
11 years
[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)
11 years
[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)
11 years
[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)
11 years
[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)
11 years