[JBoss JIRA] (JBIDE-15669) Compile Errors While Building Server Component Against Luna Based Target Platform
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15669?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-15669:
-------------------------------------
This is concerning.
> Compile Errors While Building Server Component Against Luna Based Target Platform
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-15669
> URL: https://issues.jboss.org/browse/JBIDE-15669
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Alpha1
> Reporter: Denis Golovin
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
>
> {code}[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.18.1:compile (default-compile) on project org.jboss.ide.eclipse.as.core: Compilation failure: Compilation failure:
> [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[18,0]
> [ERROR] import org.eclipse.core.runtime.internal.adaptor.EclipseEnvironmentInfo;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.eclipse.core.runtime.internal.adaptor.EclipseEnvironmentInfo cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[19,0]
> [ERROR] import org.eclipse.osgi.framework.internal.core.FrameworkProperties;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.eclipse.osgi.framework.internal.core cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[160,0]
> [ERROR] String ts = FrameworkProperties.getProperty("eclipse.startTime"); //$NON-NLS-1$
> [ERROR] ^^^^^^^^^^^^^^^^^^^
> [ERROR] FrameworkProperties cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[188,0]
> [ERROR] String value = FrameworkProperties.getProperty(key, "unknown"); //$NON-NLS-1$
> [ERROR] ^^^^^^^^^^^^^^^^^^^
> [ERROR] FrameworkProperties cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[208,0]
> [ERROR] write("BootLoader constants: OS=" + EclipseEnvironmentInfo.getDefault().getOS()); //$NON-NLS-1$
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] EclipseEnvironmentInfo cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[209,0]
> [ERROR] write(", ARCH=" + EclipseEnvironmentInfo.getDefault().getOSArch()); //$NON-NLS-1$
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] EclipseEnvironmentInfo cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[210,0]
> [ERROR] write(", WS=" + EclipseEnvironmentInfo.getDefault().getWS()); //$NON-NLS-1$
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] EclipseEnvironmentInfo cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[211,0]
> [ERROR] writeln(", NL=" + EclipseEnvironmentInfo.getDefault().getNL()); //$NON-NLS-1$
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] EclipseEnvironmentInfo cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[214,0]
> [ERROR] writeArgs("Framework arguments: ", EclipseEnvironmentInfo.getDefault().getNonFrameworkArgs()); //$NON-NLS-1$
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] EclipseEnvironmentInfo cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[215,0]
> [ERROR] writeArgs("Command-line arguments: ", EclipseEnvironmentInfo.getDefault().getCommandLineArgs()); //$NON-NLS-1$
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] EclipseEnvironmentInfo cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[335,0]
> [ERROR] FrameworkProperties.setProperty(PROP_LOGFILE, newFile == null ? "" : newFile.getAbsolutePath()); //$NON-NLS-1$
> [ERROR] ^^^^^^^^^^^^^^^^^^^
> [ERROR] FrameworkProperties cannot be resolved{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15269) Enterprise servers should be listed under 'Red Hat JBoss Middleware'
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15269?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-15269.
---------------------------------
Resolution: Done
This has been pushed to master.
> Enterprise servers should be listed under 'Red Hat JBoss Middleware'
> --------------------------------------------------------------------
>
> Key: JBIDE-15269
> URL: https://issues.jboss.org/browse/JBIDE-15269
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Final
> Reporter: Michelle Murray
> Assignee: Rob Stryker
> Fix For: 4.2.0.Alpha1
>
> Attachments: Server_RedHatJBossEnterpriseMiddleware.png
>
>
> In the IDE, when adding new servers, EAP is listed under 'JBoss Enterprise Middleware'. This should be updated to 'Red Hat JBoss Middleware'.
> This is to reflect the rebranding:
> * 'Red Hat' is being added in front of JBoss.
> * 'Enterprise' is being dropped from everywhere, except in the title of EAP.
> For example, on the customer service portal (access.redhat.com), EAP is listed under 'Red Hat JBoss Middleware' - screen capture attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15162) User must install and reference an installed local EAP instance to create a remote server definition
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15162?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-15162:
--------------------------------
Fix Version/s: LATER
> User must install and reference an installed local EAP instance to create a remote server definition
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15162
> URL: https://issues.jboss.org/browse/JBIDE-15162
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: LATER
>
> Attachments: Van_1.png, Van_2.png, Van_3.png
>
>
> See the attached screenshots - it seems counter-intuitive for a user to have to reference an installed local EAP instance to too create a remote server definition
> - open the "Servers" tab (where servers are stopped/started)
> - click in the area
> - now right mouse click and select "New->Server"
> - select JBoss Middleware EAP 6.1, click next
> - this next panel requires you to enter a directory to a local EAP install
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months