April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3416) clean up devstudio 8 marketplace entry

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3416?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen edited comment on JBDS-3416 at 4/29/15 5:29 AM: -------------------------------------------------------------------- removed the anchor + marked the main feature as required. was (Author: maxandersen): removed the content + marked the main feature as required. > clean up devstudio 8 marketplace entry > -------------------------------------- > > Key: JBDS-3416 > URL: https://issues.jboss.org/browse/JBDS-3416 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: updatesite > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 8.1.0.GA > > > https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-luna contains mention of old JRE and beta's in its text making it more about workarounds than actual features. > we should clean that up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3416) clean up devstudio 8 marketplace entry

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3416?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen resolved JBDS-3416. --------------------------------------- Resolution: Done > clean up devstudio 8 marketplace entry > -------------------------------------- > > Key: JBDS-3416 > URL: https://issues.jboss.org/browse/JBDS-3416 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: updatesite > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 8.1.0.GA > > > https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-luna contains mention of old JRE and beta's in its text making it more about workarounds than actual features. > we should clean that up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3416) clean up devstudio 8 marketplace entry

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3416?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3416: ------------------------------------------- removed the content + marked the main feature as required. > clean up devstudio 8 marketplace entry > -------------------------------------- > > Key: JBDS-3416 > URL: https://issues.jboss.org/browse/JBDS-3416 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: updatesite > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 8.1.0.GA > > > https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-luna contains mention of old JRE and beta's in its text making it more about workarounds than actual features. > we should clean that up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3416) clean up devstudio 8 marketplace entry

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3416?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen reassigned JBDS-3416: ----------------------------------------- Resolution: (was: Done) Assignee: Max Rydahl Andersen (was: Nick Boldt) please assign issue to the one you are expecting response from. I'll fix the entry. > clean up devstudio 8 marketplace entry > -------------------------------------- > > Key: JBDS-3416 > URL: https://issues.jboss.org/browse/JBDS-3416 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: updatesite > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 8.1.0.GA > > > https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-luna contains mention of old JRE and beta's in its text making it more about workarounds than actual features. > we should clean that up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2044: ------------------------------------------- so this boils down to reporting to [~fbricon] and asking why they drag in org.eclipse.platform ? > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Labels: discuss > Fix For: 8.x > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19719: --------------------------------------------- +1 for not logging an error/warning if it is not a real issue. maybe do it when tracing enabled ? would it make sense to put a warning on the project ? > EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19719: ---------------------------------------- Component/s: aerogear-hybrid > EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19733) Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19733?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19733: ---------------------------------------- Component/s: easymport (was: integration-platform) set proper component for easymport issues > Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19733 > URL: https://issues.jboss.org/browse/JBIDE-19733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Len DiMaggio > Attachments: Problems_before_import_completes.png > > > The sequence of user actions and import processing is such that, if an error occurs (for example - as described in JBIDE-19719), the error is reported after the import has been performed. Pressing cancel does not cancel/rollback the import. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19728) Easy Import - The first and second screens in the dialog should be merged into one

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19728?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19728: ---------------------------------------- Component/s: easymport (was: integration-platform) (was: aerogear-hybrid) set proper component for easymport issues > Easy Import - The first and second screens in the dialog should be merged into one > ---------------------------------------------------------------------------------- > > Key: JBIDE-19728 > URL: https://issues.jboss.org/browse/JBIDE-19728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Mickael Istria > Attachments: import_1.png, import_2.png > > > See the attached screenshots - in the first dialog screen (1/6), the user is presented with a largely blank display. After he/she selects "next" the dialog (2/6) shows the projects that are eligible to be imported. > Why not simply skip the first screen and start with the second? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19719: ---------------------------------------- Component/s: easymport (was: integration-platform) set proper component for easymport issues > EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-19719: ------------------------------------------- Assignee: Max Rydahl Andersen (was: Gorkem Ercan) > EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19697: --------------------------------------- OK, [~snjeza], I understand it can find the properties file in the structure, but I still don't quite understand how it found it in my other installations of JBDS - clearly it cannot search your whole disk during the p2 installation to find any instances of Eclipse/JBDS and the properties files. So it seems to me it searches everything under ECLIPSE_HOME/../* ? Meaning it will search all other Eclipse or JBDS installs in the same directory as your currently running Eclipse? > org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19697 > URL: https://issues.jboss.org/browse/JBIDE-19697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Snjezana Peco > > When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs' > Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs > {code} > This is inside the file: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat > eclipse.preferences.version=1 > runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n > {code} > It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen? > I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now. > Can somebody explain what's going on? > Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19291) "Unable to execute early startup code ..." exception after starup.

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19291?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-19291: ---------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > "Unable to execute early startup code ..." exception after starup. > ------------------------------------------------------------------ > > Key: JBIDE-19291 > URL: https://issues.jboss.org/browse/JBIDE-19291 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > After startup in error log there is this error: > {noformat:title=Unable to execute early startup code for the org.eclipse.ui.IStartup extension contributed by the 'org.jboss.ide.eclipse.as.ui' plug-in.} > org.eclipse.core.runtime.CoreException: Executable extension definition for "class" not found. > at org.eclipse.core.internal.registry.ConfigurationElement.throwException(ConfigurationElement.java:62) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:222) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:293) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52) > at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:288) > at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:102) > at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:54) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench$56.run(Workbench.java:2801) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19438) Module is not in Started state after deploy even though it is deployed correctly - 4.3.x

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19438?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19438. --------------------------------- Verified in JBDS 9.0.0.Alpha2 BYOE. > Module is not in Started state after deploy even though it is deployed correctly - 4.3.x > ---------------------------------------------------------------------------------------- > > Key: JBIDE-19438 > URL: https://issues.jboss.org/browse/JBIDE-19438 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha2 > > > When deploying project to running server (I've tried it with Wildfly 8 and EAP 6.3), the project remains in state [Synchronized] instead of [Started, Synchronized] even though the project is correctly deployed and running. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19532: --------------------------------------- I tried your steps, Rob, and for some odd reason when I open the symlink in the Browse dialog (your step 5), it will automatically take me to the linked dir - apparently that's how the OS works. In Terminal, I can cd to the symlink and it will act as a directory. But in Finder / Open File dialog if I double click an item which is a symlink to a directory, it will take me to the target directory. So I end up which the actual path in the "Server base directory" field and there is no error. But if I manually enter the path with the symlink, it will validate the config properly: {code} /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final_sym/standalone {code} If I change one character, it will show the error saying it can't find the config. If I fix the path again, the error will disappear. So for me it works correctly. And the server starts ok, too - it will contain this parameter: -Djboss.server.base.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final_sym/standalone > "Edit Server Runtime Environment" Dialog configuration validation is broken > --------------------------------------------------------------------------- > > Key: JBIDE-19532 > URL: https://issues.jboss.org/browse/JBIDE-19532 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > Attachments: data-folder-config.png, Edit Server Runtime Environment _102.png, JBIDE-19532.png > > > If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start. > {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist. > at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213) > at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-431) Designer requires a new luna IS-TP complete with new version of LOCUS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-431?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen edited comment on JBTIS-431 at 4/29/15 3:58 AM: -------------------------------------------------------------------- Just to grok this - does this mean Designer 9.x is backwards compatible from a user perspective been using JBDS 8.0 and upwards ? i.e. Designer 9 does not remove any features or support for runtimes that been targeted since JBDS 8.0 ? was (Author: maxandersen): Just to grok this - does this mean Designer 9.x is backwards compatible from a user perspective been using JBDS 8.0 and upwards ? i.e. Designer 9 does not remove any features or support for runtimes that been targeted with JBDS 8.0 ? > Designer requires a new luna IS-TP complete with new version of LOCUS > --------------------------------------------------------------------- > > Key: JBTIS-431 > URL: https://issues.jboss.org/browse/JBTIS-431 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Final-TP > Reporter: Paul Richardson > > https://issues.jboss.org/browse/LOCUS-23 defines a new requirement in locus that results in a new version of the locus update site. > Once a new build is available, Teiid Designer will need this locus version integrated into a new LUNA build of the IS-TP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-431) Designer requires a new luna IS-TP complete with new version of LOCUS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-431?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-431: ------------------------------------------- Just to grok this - does this mean Designer 9.x is backwards compatible from a user perspective been using JBDS 8.0 and upwards ? i.e. Designer 9 does not remove any features or support for runtimes that been targeted with JBDS 8.0 ? > Designer requires a new luna IS-TP complete with new version of LOCUS > --------------------------------------------------------------------- > > Key: JBTIS-431 > URL: https://issues.jboss.org/browse/JBTIS-431 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Final-TP > Reporter: Paul Richardson > > https://issues.jboss.org/browse/LOCUS-23 defines a new requirement in locus that results in a new version of the locus update site. > Once a new build is available, Teiid Designer will need this locus version integrated into a new LUNA build of the IS-TP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3395) JBDS Installer should let to include additional features and provide panel to select for installation

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3395?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3395. ----------------------------- Verified for 9.0.0 Alpha2, closing > JBDS Installer should let to include additional features and provide panel to select for installation > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-3395 > URL: https://issues.jboss.org/browse/JBDS-3395 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Alpha2 > > > Installer should let include additional p2 repositories and provide the way to select additional features (IU's) during installation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18786) Bump LiveReload version to 1.3.0 on master branch

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18786?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-18786. ------------------------------- Verified for 4.3.0 Alpha1, closing > Bump LiveReload version to 1.3.0 on master branch > ------------------------------------------------- > > Key: JBIDE-18786 > URL: https://issues.jboss.org/browse/JBIDE-18786 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18787) Build failures with Mars M3 TP

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18787?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-18787. ------------------------------- The build succeeds, closing > Build failures with Mars M3 TP > ------------------------------- > > Key: JBIDE-18787 > URL: https://issues.jboss.org/browse/JBIDE-18787 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha1 > > > In relation with JBIDE-18748. > There are compilation errors because of API changes in the TP (using Servlet-API 3.1 now) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9563) AS7 does not pick hot-deployed jsp files

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9563?page=com.atlassian.jira.plugin... ] Martin Malina closed JBIDE-9563. -------------------------------- > AS7 does not pick hot-deployed jsp files > ---------------------------------------- > > Key: JBIDE-9563 > URL: https://issues.jboss.org/browse/JBIDE-9563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.M3 > Environment: AS7 Final, JBDS 5.0 trunk build H737, JBossAS Tools 2.3.0.v20110817-1604-H645-M3 > Reporter: Libor Zoubek > Assignee: Max Rydahl Andersen > Priority: Minor > > When saving jsp file, hotdeployment copies it over to server's deploy dir, but server does not notice that. Server should compile this jsp file and return new content via web browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19494) Migrate Livereload to Jetty 9

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19494?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-19494. ------------------------------- Verified, closing > Migrate Livereload to Jetty 9 > ----------------------------- > > Key: JBIDE-19494 > URL: https://issues.jboss.org/browse/JBIDE-19494 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > Following JBIDE-18804 which migrates to Jetty 9, we should also do the move to have a single version of the Jetty bundles in our TP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17545) Can't Full Publish project to WildFly (8.0 or 8.1)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17545?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17545. --------------------------------- Closing. Feel free to reopen if still relevant. > Can't Full Publish project to WildFly (8.0 or 8.1) > -------------------------------------------------- > > Key: JBIDE-17545 > URL: https://issues.jboss.org/browse/JBIDE-17545 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Lincoln Baxter III > Assignee: Rob Stryker > Fix For: 4.2.1.Final > > > The following error is logged and publishing fails when attempting to Full Publish this project: > https://github.com/forgeide/forgeide > {code} > Publishing failed > Error renaming /Users/lb3/lib/wildfly-8.1.0.Final/standalone/tmp/tmp1118502157688228046.jar to /Users/lb3/lib/wildfly-8.1.0.Final/standalone/deployments/forgeide.war/WEB-INF/lib/furnace-se-2.6.1-SNAPSHOT.jar/bootpath/forge-javassist-2.jar. > This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination. > You may adjust these settings in the server editor. > Error renaming /Users/lb3/lib/wildfly-8.1.0.Final/standalone/tmp/tmp1738236936180964755.jar to /Users/lb3/lib/wildfly-8.1.0.Final/standalone/deployments/forgeide.war/WEB-INF/lib/furnace-se-2.6.1-SNAPSHOT.jar/bootpath/jboss-modules-1.3.0.Final-forge.jar. > This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination. > You may adjust these settings in the server editor. > Error renaming /Users/lb3/lib/wildfly-8.1.0.Final/standalone/tmp/tmp2320075067441042997.jar to /Users/lb3/lib/wildfly-8.1.0.Final/standalone/deployments/forgeide.war/WEB-INF/lib/furnace-se-2.6.1-SNAPSHOT.jar/bootpath/jgrapht-0.8.3.jar. > This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination. > You may adjust these settings in the server editor. > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17314) Much UI from JVM Monitor documentation is missing

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17314?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17314. --------------------------------- Nothing to do here :) Closing. > Much UI from JVM Monitor documentation is missing > ------------------------------------------------- > > Key: JBIDE-17314 > URL: https://issues.jboss.org/browse/JBIDE-17314 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jmx > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Assignee: Paul Leacu > Fix For: 4.2.1.Final > > Attachments: create-conn.png, ss-pref-tools.png, ss1.png > > > Much of the UI from http://www.jvmmonitor.org/doc/index.html#Monitoring_JVM_on_remote_host is missing and disabled. We must discover where it's gone, why it's disabled, and whether it can be re-activated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-594) Offline Install does not mention the Target Platform zip

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-594?page=com.atlassian.jira.plug... ] Martin Malina closed TOOLSDOC-594. ---------------------------------- The correct target platform zip is available at https://devstudio.jboss.com/updates/8.0/ and the doc contains the correct info: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... Closing. > Offline Install does not mention the Target Platform zip > -------------------------------------------------------- > > Key: TOOLSDOC-594 > URL: https://issues.jboss.org/browse/TOOLSDOC-594 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Affects Versions: 4.2.2.Final > Environment: Build Name: 22661, Install Red Hat JBoss Developer Studio-8.0 > Build Date: 25-11-2014 14:18:18 > Topic ID: 41914-716354 [Latest] > Reporter: Nick Boldt > Assignee: Michelle Murray > Priority: Blocker > Fix For: 4.2.3.Final > > > Title: Install JBoss Developer Studio BYOE when Offline > Describe the issue: > See JBDS-3361. User cannot install from JBDS zip alone because some eclipse dependencies are unavailable in that zip. > > Suggestions for improvement: > TP zip should be linked from CSP, jboss.org, and devstudio.redhat.com. > Doc (in CSP and on access.redhat.com) should tell users about the target platform zip, too. > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > Additional information: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19727) An error of "0" is displayed to the user after a failed Cordova mobile engine install

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19727?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-19727: ------------------------------------ This is a dup of https://issues.jboss.org/browse/JBIDE-19639 > An error of "0" is displayed to the user after a failed Cordova mobile engine install > ------------------------------------------------------------------------------------- > > Key: JBIDE-19727 > URL: https://issues.jboss.org/browse/JBIDE-19727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: error.png, jbosstools-diagnostics-20150428131923.zip > > > When trying to install a 4.0 Cordova mobile engine, this error dialog is displayed: > An error has occurred. See error log for more details. > 0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19587) Build failure on Jenkins after TP upgrade

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19587?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-19587. ------------------------------- Closing as this is no longer an issue > Build failure on Jenkins after TP upgrade > ----------------------------------------- > > Key: JBIDE-19587 > URL: https://issues.jboss.org/browse/JBIDE-19587 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > Some build failures reported on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-livereload... after JBIDE-19585 (although the exception do not seem to be related to Jetty but rather to Mockito) > {code} > java.lang.ClassCastException: org.mockito.internal.creation.jmock.ClassImposterizer$ClassWithSuperclassToWorkAroundCglibBug$$EnhancerByMockitoWithCGLIB$$4e962fbf cannot be cast to org.eclipse.wst.server.core.model.ServerBehaviourDelegate > at org.jboss.tools.livereload.internal.util.WSTUtilsTestCase.setup(WSTUtilsTestCase.java:72) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3430) Creating a AngularJS project from scratch fails with an error installing tern

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3430: ---------------------------------- Summary: Creating a AngularJS project from scratch fails with an error installing tern Key: JBDS-3430 URL: https://issues.jboss.org/browse/JBDS-3430 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: build Affects Versions: 9.0.0.Alpha2 Reporter: Len DiMaggio Assignee: Nick Boldt The error is: Your original request has been modified. "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead. Cannot complete the install because of a conflicting dependency. Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150417-0104-B13) Software currently installed: JBoss Developer Studio (Branded Product) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.package 9.0.0.Alpha2-v20150405-1144-B2918) Only one of the following can be installed at once: JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822) JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150417-0104-B13) Cannot satisfy dependency: From: JBoss Developer Studio (Core Features) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.feature.feature.group 9.0.0.Alpha2-v20150405-1144-B2918) To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha2-v20150322-0547-B822] Cannot satisfy dependency: From: JBoss Developer Studio (Branded Product) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.package 9.0.0.Alpha2-v20150405-1144-B2918) To: com.jboss.devstudio.core.feature.feature.group [9.0.0.Alpha2-v20150405-1144-B2918] Cannot satisfy dependency: From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822) To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822] Cannot satisfy dependency: From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150417-0104-B13) To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150417-0104-B13] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3430) Creating a AngularJS project from scratch fails with an error installing tern

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3430?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3430: ----------------------------- CDW docs_ack: ? CDW devel_ack: ? CDW pm_ack: + CDW qa_ack: ? > Creating a AngularJS project from scratch fails with an error installing tern > ----------------------------------------------------------------------------- > > Key: JBDS-3430 > URL: https://issues.jboss.org/browse/JBDS-3430 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Nick Boldt > > The error is: > Your original request has been modified. > "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead. > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150417-0104-B13) > Software currently installed: JBoss Developer Studio (Branded Product) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.package 9.0.0.Alpha2-v20150405-1144-B2918) > Only one of the following can be installed at once: > JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822) > JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150417-0104-B13) > Cannot satisfy dependency: > From: JBoss Developer Studio (Core Features) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.feature.feature.group 9.0.0.Alpha2-v20150405-1144-B2918) > To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha2-v20150322-0547-B822] > Cannot satisfy dependency: > From: JBoss Developer Studio (Branded Product) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.package 9.0.0.Alpha2-v20150405-1144-B2918) > To: com.jboss.devstudio.core.feature.feature.group [9.0.0.Alpha2-v20150405-1144-B2918] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822) > To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150417-0104-B13) > To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150417-0104-B13] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3430) Creating a AngularJS project from scratch fails with an error installing tern

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3430?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3430: ------------------------------- CDW release: ? Status: New (was: New) Target Release: 9.0.0.GA > Creating a AngularJS project from scratch fails with an error installing tern > ----------------------------------------------------------------------------- > > Key: JBDS-3430 > URL: https://issues.jboss.org/browse/JBDS-3430 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Nick Boldt > > The error is: > Your original request has been modified. > "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead. > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150417-0104-B13) > Software currently installed: JBoss Developer Studio (Branded Product) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.package 9.0.0.Alpha2-v20150405-1144-B2918) > Only one of the following can be installed at once: > JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822) > JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150417-0104-B13) > Cannot satisfy dependency: > From: JBoss Developer Studio (Core Features) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.feature.feature.group 9.0.0.Alpha2-v20150405-1144-B2918) > To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha2-v20150322-0547-B822] > Cannot satisfy dependency: > From: JBoss Developer Studio (Branded Product) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.package 9.0.0.Alpha2-v20150405-1144-B2918) > To: com.jboss.devstudio.core.feature.feature.group [9.0.0.Alpha2-v20150405-1144-B2918] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822) > To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150417-0104-B13) > To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150417-0104-B13] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3430) Creating a AngularJS project from scratch fails with an error installing tern

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3430?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3430: ------------------------------- CDW qa_ack: + (was: ?) > Creating a AngularJS project from scratch fails with an error installing tern > ----------------------------------------------------------------------------- > > Key: JBDS-3430 > URL: https://issues.jboss.org/browse/JBDS-3430 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Nick Boldt > > The error is: > Your original request has been modified. > "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead. > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150417-0104-B13) > Software currently installed: JBoss Developer Studio (Branded Product) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.package 9.0.0.Alpha2-v20150405-1144-B2918) > Only one of the following can be installed at once: > JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822) > JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150417-0104-B13) > Cannot satisfy dependency: > From: JBoss Developer Studio (Core Features) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.feature.feature.group 9.0.0.Alpha2-v20150405-1144-B2918) > To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha2-v20150322-0547-B822] > Cannot satisfy dependency: > From: JBoss Developer Studio (Branded Product) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.package 9.0.0.Alpha2-v20150405-1144-B2918) > To: com.jboss.devstudio.core.feature.feature.group [9.0.0.Alpha2-v20150405-1144-B2918] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822) > To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150417-0104-B13) > To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150417-0104-B13] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19735) Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)"

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19735?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-19735: -------------------------------------- Yes - I am not seeing that error with JBDS 9.0.0.alpha2 > Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19735 > URL: https://issues.jboss.org/browse/JBIDE-19735 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Attachments: jbosstools-diagnostics-20150428160436.zip > > > To recreate: > * Create from scratch a new AngularJS with Forge project. > * Have the project creation install AngularJS Eclipse > Observe this error reported in a dialog in the UI: > An error has occurred. See error log for more details. > invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" > The full .log is in the attached diagnostic file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18815) Include latest freemarker-2.3.22.jar in FreeMarker IDE as maven dependency

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18815?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18815: ---------------------------------- Summary: Include latest freemarker-2.3.22.jar in FreeMarker IDE as maven dependency (was: Include freemarker.jar in FreeMarker IDE as maven dependency) > Include latest freemarker-2.3.22.jar in FreeMarker IDE as maven dependency > -------------------------------------------------------------------------- > > Key: JBIDE-18815 > URL: https://issues.jboss.org/browse/JBIDE-18815 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Affects Versions: 4.2.0.Final > Reporter: Daniel Dekany > Assignee: Denis Golovin > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > > FreeMarker IDE still comes with FreeMarker 2.3.18 from 2011. As the plugin uses FreeMarker for parsing templates (for error markers), this means that no constructs introduced since then are recognized by it (there's a quite a few), and also that it doesn't benefit from the error message fixes/improvements made since then. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19725) EasyImport plugin title misspelled

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19725?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19725: ---------------------------------------- The name is intended. It sounds pretty good for non-native-English speakers, but American people don't get the pun. > EasyImport plugin title misspelled > ---------------------------------- > > Key: JBIDE-19725 > URL: https://issues.jboss.org/browse/JBIDE-19725 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Mickael Istria > Attachments: import.png > > > The plugin name is spelled as: > JBoss Easymport for Aerogear -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3322) JSR-356: Websockets. Content-assist for annotations

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3322?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3322: --------------------------------- Sprint: Sprint #3 May 2015 > JSR-356: Websockets. Content-assist for annotations > --------------------------------------------------- > > Key: JBDS-3322 > URL: https://issues.jboss.org/browse/JBDS-3322 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, webservices > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: websockets > Fix For: 9.0.0.Beta1 > > > As a Java EE developer, I wish to take advantage of the new Websockets capability. > Content-assist for annotations such as @ServerEndpoint, @OnMessage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19474) org.jboss.tools.foundation.help.ui is not included into foundation feature

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19474?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19474: --------------------------------------- this bundle is included into jbosstools-base/site/category.xml as a standalone uncategorized bundle not included to any feature, that is the reason why it is already included into p2 repository without being part of the feature. > org.jboss.tools.foundation.help.ui is not included into foundation feature > -------------------------------------------------------------------------- > > Key: JBIDE-19474 > URL: https://issues.jboss.org/browse/JBIDE-19474 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19474) org.jboss.tools.foundation.help.ui is not included into foundation feature

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19474?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19474: --------------------------------------- product build is fine now because of JBDS-3361 fixed by including all required dependencies into product p2 repository. > org.jboss.tools.foundation.help.ui is not included into foundation feature > -------------------------------------------------------------------------- > > Key: JBIDE-19474 > URL: https://issues.jboss.org/browse/JBIDE-19474 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19590: --------------------------------------- I'll try to implement this for hibernate as an example. > Update module's README.md files with information about dependencies to other modules > ------------------------------------------------------------------------------------ > > Key: JBIDE-19590 > URL: https://issues.jboss.org/browse/JBIDE-19590 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > > For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development: > 1. Set up target platform in preferences > 2. Import JBT module sources into workspace > 3. Import required JBT module sources into worksapce > (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9563) AS7 does not pick hot-deployed jsp files

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9563?page=com.atlassian.jira.plugin... ] Rob Stryker resolved JBIDE-9563. -------------------------------- Fix Version/s: (was: LATER) Resolution: Won't Fix This old issue won't be fixed. It's a runtime issue at its heart. > AS7 does not pick hot-deployed jsp files > ---------------------------------------- > > Key: JBIDE-9563 > URL: https://issues.jboss.org/browse/JBIDE-9563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.M3 > Environment: AS7 Final, JBDS 5.0 trunk build H737, JBossAS Tools 2.3.0.v20110817-1604-H645-M3 > Reporter: Libor Zoubek > Assignee: Max Rydahl Andersen > Priority: Minor > > When saving jsp file, hotdeployment copies it over to server's deploy dir, but server does not notice that. Server should compile this jsp file and return new content via web browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19708) Runtime-detection is not supporting Servlet only distribution of Wildfly 9

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19708?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19708. --------------------------------- Resolution: Done Pushed a commit simply adding a serverbean for this installation type. > Runtime-detection is not supporting Servlet only distribution of Wildfly 9 > -------------------------------------------------------------------------- > > Key: JBIDE-19708 > URL: https://issues.jboss.org/browse/JBIDE-19708 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > Runtime detection correctly detects servlet-only distribution of wildfly 9, but fails to add it. Error log is silent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19708) Runtime-detection is not supporting Servlet only distribution of Wildfly 9

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19708?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19708: -------------------------------- Fix Version/s: 4.3.0.Beta1 > Runtime-detection is not supporting Servlet only distribution of Wildfly 9 > -------------------------------------------------------------------------- > > Key: JBIDE-19708 > URL: https://issues.jboss.org/browse/JBIDE-19708 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > Runtime detection correctly detects servlet-only distribution of wildfly 9, but fails to add it. Error log is silent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19731) Selecting "remove" before a hybrid mobile engine is created logs exception - no feeback is provided to users in the UI

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19731?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-19731. ---------------------------------- Resolution: Duplicate Issue > Selecting "remove" before a hybrid mobile engine is created logs exception - no feeback is provided to users in the UI > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19731 > URL: https://issues.jboss.org/browse/JBIDE-19731 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Priority: Minor > > To recreate: > * With no hybrid mobile engines defined > * Preferences->Hybrid Mobile-> Engines > * Click on "remove" and the exception is logged - no feedback is provided to the user in the UI > !ENTRY org.eclipse.ui 4 0 2015-04-28 14:30:25.700 > !MESSAGE Unhandled event loop exception > !STACK 0 > java.lang.ClassCastException: org.eclipse.thym.core.extensions.PlatformSupport cannot be cast to org.eclipse.thym.core.engine.HybridMobileEngine > at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection.handleRemoveEngine(AvailableCordovaEnginesSection.java:606) > at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection.access$4(AvailableCordovaEnginesSection.java:598) > at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection$5.handleEvent(AvailableCordovaEnginesSection.java:378) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) > at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:63) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19736) Update template list page to get 'openshift' templates and group accordingly

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19736?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-19736: ------------------------------------- Assignee: Jeff Cantrill > Update template list page to get 'openshift' templates and group accordingly > ---------------------------------------------------------------------------- > > Key: JBIDE-19736 > URL: https://issues.jboss.org/browse/JBIDE-19736 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > > When creating a template, a user should be able to choose from their project templates and those that are part of the configured (openshift) namespace. Update The template list page get templates from openshift namespace and to group templates under an appropriate folder (project or openshift) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19737) Add template info page after template list in create from app flow

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19737: ------------------------------------- Summary: Add template info page after template list in create from app flow Key: JBIDE-19737 URL: https://issues.jboss.org/browse/JBIDE-19737 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Jeff Cantrill Add a template info page that identifies key aspects of a template that a user has choosen so they can ensure they want to continue -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19736) Update template list page to get 'openshift' templates and group accordingly

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19736: ------------------------------------- Summary: Update template list page to get 'openshift' templates and group accordingly Key: JBIDE-19736 URL: https://issues.jboss.org/browse/JBIDE-19736 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Jeff Cantrill When creating a template, a user should be able to choose from their project templates and those that are part of the configured (openshift) namespace. Update The template list page get templates from openshift namespace and to group templates under an appropriate folder (project or openshift) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19478) Application wizard: Add template filtering by tag

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19478?page=com.atlassian.jira.plugi... ] Jeff Cantrill resolved JBIDE-19478. ----------------------------------- Resolution: Done > Application wizard: Add template filtering by tag > ------------------------------------------------- > > Key: JBIDE-19478 > URL: https://issues.jboss.org/browse/JBIDE-19478 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Labels: application_wizard > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19735) Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)"

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19735?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19735: ------------------------------------- Can you check if it works in JBDS? (I tried that and it worked for me). There might be an issue with the discovery catalog > Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19735 > URL: https://issues.jboss.org/browse/JBIDE-19735 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Attachments: jbosstools-diagnostics-20150428160436.zip > > > To recreate: > * Create from scratch a new AngularJS with Forge project. > * Have the project creation install AngularJS Eclipse > Observe this error reported in a dialog in the UI: > An error has occurred. See error log for more details. > invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" > The full .log is in the attached diagnostic file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19735) Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)"

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19735?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19735: --------------------------------- Attachment: jbosstools-diagnostics-20150428160436.zip > Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19735 > URL: https://issues.jboss.org/browse/JBIDE-19735 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Attachments: jbosstools-diagnostics-20150428160436.zip > > > To recreate: > * Create from scratch a new AngularJS with Forge project. > * Have the project creation install AngularJS Eclipse > Observe this error reported in a dialog in the UI: > An error has occurred. See error log for more details. > invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" > The full .log is in the attached diagnostic file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19735) Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)"

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-19735: ------------------------------------ Summary: Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" Key: JBIDE-19735 URL: https://issues.jboss.org/browse/JBIDE-19735 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.3.0.Alpha2 Reporter: Len DiMaggio Attachments: jbosstools-diagnostics-20150428160436.zip To recreate: * Create from scratch a new AngularJS with Forge project. * Have the project creation install AngularJS Eclipse Observe this error reported in a dialog in the UI: An error has occurred. See error log for more details. invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" The full .log is in the attached diagnostic file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-431) Designer requires a new luna IS-TP complete with new version of LOCUS

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-431?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-431: ---------------------------------- Updated JBTIS TP 4.2.3.CR1a repo and nexus. [~phantomjinx] - please try rebuilding teiid designer w/ jbtis tp version 4.2.3.CR1a . Also - Barry gave me a teiid des to use for the first CR1 capture for QE to test: 9.0.2.Beta1 . Should I hold off giving this to QE (waiting for an update with this TP) or should I go ahead with 9.0.2.Beta1? https://github.com/jbosstools/jbosstools-integration-stack/commit/73d3c92... http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.3.CR1a/ > Designer requires a new luna IS-TP complete with new version of LOCUS > --------------------------------------------------------------------- > > Key: JBTIS-431 > URL: https://issues.jboss.org/browse/JBTIS-431 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Final-TP > Reporter: Paul Richardson > > https://issues.jboss.org/browse/LOCUS-23 defines a new requirement in locus that results in a new version of the locus update site. > Once a new build is available, Teiid Designer will need this locus version integrated into a new LUNA build of the IS-TP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19734) JAX-RS Validator NPEs with wildcard type arguments

by Kory Markevich (JIRA)

Kory Markevich created JBIDE-19734: -------------------------------------- Summary: JAX-RS Validator NPEs with wildcard type arguments Key: JBIDE-19734 URL: https://issues.jboss.org/browse/JBIDE-19734 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Environment: Eclipse Mars, JDK 1.7 32-bit Reporter: Kory Markevich JBoss JAX-RS Tools feature version: 1.8.0.Beta1-v20150417-0152-B698 The JAX-RS validator throws an NPE when using generic types with wildcards. Specifically, the call to typeArgumentBinding.getJavaElement() in SourceType.from(VariableDeclaration) can return null, which the SourceType constructor then tries to use, resulting in the following stack trace. Depending on the code, the validator could trigger this exception as frequently as every pause in typing, resulting in a modal error box popping up constantly. The sample code provided only triggers it on save though. java.lang.NullPointerException at org.jboss.tools.ws.jaxrs.core.jdt.SourceType.<init>(SourceType.java:157) at org.jboss.tools.ws.jaxrs.core.jdt.SourceType.from(SourceType.java:49) at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignature(JdtUtils.java:1109) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResource$Builder.build(JaxrsResource.java:169) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResource.update(JaxrsResource.java:273) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElement(JaxrsMetamodel.java:647) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processResourceChange(JaxrsMetamodel.java:608) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processAffectedResources(JaxrsMetamodel.java:574) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:77) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19645) Remove seam 3 features from JBDS, JBT default install; add new connector to Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19645?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-19645. ----------------------------------------- Resolution: Won't Fix After discussion with [~akazakov] we've come to the conclusion the overhead and packaging of seam3 CDI extensions are minimal thus deciding to keep them in. We will open a separate Jira for seeing if there are reasons to support the deltaspike alternatives for these features. > Remove seam 3 features from JBDS, JBT default install; add new connector to Central > ----------------------------------------------------------------------------------- > > Key: JBIDE-19645 > URL: https://issues.jboss.org/browse/JBIDE-19645 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi-extensions, central, updatesite > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > Attachments: jbds8alpha2-features-cdi-seam.png, jbds8alpha2-plugins-cdi.png, jbds8alpha2-plugins-seam.png, jbt43alpha2-features-cdi.png, jbt43alpha2-features-seam.png, jbt43alpha2-plugins-cdi.png, jbt43alpha2-plugins-seam-3-and-seam3.png, validation.png > > > Burr has requested we also remove Seam 3. So I've assumed we'll do it the same way we did for Seam 2: > * remove from CoreTools categories on update sites > * remove from JBDS core.feature > * create new connectors in JBT and JBDS Central > [~burrsutter] [~maxandersen] please confirm this is the path you want taken for all the renaming features with "seam" in their name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19645) Remove seam 3 features from JBDS, JBT default install; add new connector to Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19645?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19645: ---------------------------------------- Sprint: Sprint #2 April 2015 > Remove seam 3 features from JBDS, JBT default install; add new connector to Central > ----------------------------------------------------------------------------------- > > Key: JBIDE-19645 > URL: https://issues.jboss.org/browse/JBIDE-19645 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi-extensions, central, updatesite > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > Attachments: jbds8alpha2-features-cdi-seam.png, jbds8alpha2-plugins-cdi.png, jbds8alpha2-plugins-seam.png, jbt43alpha2-features-cdi.png, jbt43alpha2-features-seam.png, jbt43alpha2-plugins-cdi.png, jbt43alpha2-plugins-seam-3-and-seam3.png, validation.png > > > Burr has requested we also remove Seam 3. So I've assumed we'll do it the same way we did for Seam 2: > * remove from CoreTools categories on update sites > * remove from JBDS core.feature > * create new connectors in JBT and JBDS Central > [~burrsutter] [~maxandersen] please confirm this is the path you want taken for all the renaming features with "seam" in their name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17103) No warning/error is shown when detected runtime fails to be added

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17103: -------------------------------- Attachment: JBIDE-17103.png Screenshot of how the error appears. To verify this screenshot exists: 1) Go to JBoss Runtime Detection page 2) Add a path pointing to a WF installation 3) Wait for dialog indicating 1 new runtime found 4) Delete the entire folder from your HD 5) Press "OK" in the "searching for runtimes..." page 6) See error dialog appear. > No warning/error is shown when detected runtime fails to be added > ----------------------------------------------------------------- > > Key: JBIDE-17103 > URL: https://issues.jboss.org/browse/JBIDE-17103 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: JBIDE-17103.png > > > When there is a new version of a runtime, e.g. WildFly 8.1, that is not yet supported by the tooling, runtime detection usually detects it alright, but when you then click OK, the runtime+server are not added. And there is no error anywhere at all - we should fix that. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17103) No warning/error is shown when detected runtime fails to be added

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17103: -------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.2.x) > No warning/error is shown when detected runtime fails to be added > ----------------------------------------------------------------- > > Key: JBIDE-17103 > URL: https://issues.jboss.org/browse/JBIDE-17103 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: JBIDE-17103.png > > > When there is a new version of a runtime, e.g. WildFly 8.1, that is not yet supported by the tooling, runtime detection usually detects it alright, but when you then click OK, the runtime+server are not added. And there is no error anywhere at all - we should fix that. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3416) clean up devstudio 8 marketplace entry

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3416?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3416. ---------------------------- Resolution: Done Closing since no response after a week. > clean up devstudio 8 marketplace entry > -------------------------------------- > > Key: JBDS-3416 > URL: https://issues.jboss.org/browse/JBDS-3416 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: updatesite > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 8.1.0.GA > > > https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-luna contains mention of old JRE and beta's in its text making it more about workarounds than actual features. > we should clean that up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3416) clean up devstudio 8 marketplace entry

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3416?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3416: ----------------------------- Fix Version/s: 8.1.0.GA > clean up devstudio 8 marketplace entry > -------------------------------------- > > Key: JBDS-3416 > URL: https://issues.jboss.org/browse/JBDS-3416 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: updatesite > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 8.1.0.GA > > > https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-luna contains mention of old JRE and beta's in its text making it more about workarounds than actual features. > we should clean that up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19733) Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-19733: ------------------------------------ Summary: Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs Key: JBIDE-19733 URL: https://issues.jboss.org/browse/JBIDE-19733 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration-platform Reporter: Len DiMaggio Attachments: Problems_before_import_completes.png The sequence of user actions and import processing is such that, if an error occurs (for example - as described in JBIDE-19719), the error is reported after the import has been performed. Pressing cancel does not cancel/rollback the import. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19733) Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19733?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19733: --------------------------------- Attachment: Problems_before_import_completes.png > Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19733 > URL: https://issues.jboss.org/browse/JBIDE-19733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Reporter: Len DiMaggio > Attachments: Problems_before_import_completes.png > > > The sequence of user actions and import processing is such that, if an error occurs (for example - as described in JBIDE-19719), the error is reported after the import has been performed. Pressing cancel does not cancel/rollback the import. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19067) org.eclipse.wst.server_ui.feature_3.3.401.v201409112028 version decreased in JBDS 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19067?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19067: ------------------------------------ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... is no longer excluding org.eclipse.wst.server_ui.feature. Should have updated the jobs a couple months ago. Oops. > org.eclipse.wst.server_ui.feature_3.3.401.v201409112028 version decreased in JBDS 9 > ----------------------------------------------------------------------------------- > > Key: JBIDE-19067 > URL: https://issues.jboss.org/browse/JBIDE-19067 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19724) Provide bundled JBT releases

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19724?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19724: ---------------------------------- Assignee: Max Rydahl Andersen (was: Nick Boldt) > Provide bundled JBT releases > ---------------------------- > > Key: JBIDE-19724 > URL: https://issues.jboss.org/browse/JBIDE-19724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: ehsavoie Hugonnet > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta1 > > > As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. > Could you provide such a bundle à la JBDS during the testing periods ? > http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19724) Provide bundled JBT releases

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19724?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19724: ------------------------------- Summary: Provide bundled JBT releases (was: Provide public version of alpha releases for testing JBT) > Provide bundled JBT releases > ---------------------------- > > Key: JBIDE-19724 > URL: https://issues.jboss.org/browse/JBIDE-19724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: ehsavoie Hugonnet > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. > Could you provide such a bundle à la JBDS during the testing periods ? > http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19719: --------------------------------- Summary: EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI (was: EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI) > EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2044: ------------------------------------- This .eclipseproduct marker file supposed to mark 'main product' among many possibly installed. see wiki article ["FAQ What is an Eclipse product?" | https://wiki.eclipse.org/FAQ_What_is_an_Eclipse_product%3F]. At the same time if one of included in product features has reference to "org.eclipse.platform.feature.grop" this file is installed as "root file" and there is no way to replace its content. It can be done after installation, but that would be overwritten during update from product p2.repositry. The only way to get rid of it is to remove reference to org.eclipse.platform feature and replace it with org.eclipse.platform bundle. It would work, but m2e* features for some reason has reference to org.eclipse.platform feature and that drags in .eclipseproduct file in JBDS installation. So it looks like we cannot fix it right now, but it does no harm to us because the name for final file to store state use not only product id but also installation folder hash. > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Labels: discuss > Fix For: 8.x > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19732) Misleading error logged when a new hybrid mobile engine configured

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-19732: ------------------------------------ Summary: Misleading error logged when a new hybrid mobile engine configured Key: JBIDE-19732 URL: https://issues.jboss.org/browse/JBIDE-19732 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.3.0.Alpha2 Reporter: Len DiMaggio Priority: Minor There's no functional impact, but the error message is confusing. When a new mobile hybrid engine is configured, this error is logged: !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 14:38:54.071 !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/3.7.1/framework/cordova-3.7.1.jar The file, however, is right where it belongs: ll /home/ldimaggi/.cordova/lib/android/cordova/3.7.1/framework/cordova-3.7.1.jar -rw-rw-r--. 1 ldimaggi ldimaggi 357355 Apr 28 14:38 /home/ldimaggi/.cordova/lib/android/cordova/3.7.1/framework/cordova-3.7.1.jar -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19724) Provide public version of alpha releases for testing JBT

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19724?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19724 at 4/28/15 2:46 PM: ------------------------------------------------------------- I doubt there's a plan to create "JBoss Tools w/ Eclipse" bundled installers. And, currently, it's not possible to provide pre-release JBDS installers. But starting from Beta1 we WILL have JBDS 9 installers available on http://tools.jboss.org/downloads/overview.html as we did for JBDS 8.x. was (Author: nickboldt): Currently, it's not possible to provide pre-release JBDS installers. But starting from Beta1 we WILL have JBDS 9 installers available on http://tools.jboss.org/downloads/overview.html as we did for JBDS 8.x. > Provide public version of alpha releases for testing JBT > -------------------------------------------------------- > > Key: JBIDE-19724 > URL: https://issues.jboss.org/browse/JBIDE-19724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: ehsavoie Hugonnet > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. > Could you provide such a bundle à la JBDS during the testing periods ? > http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19724) Provide public version of alpha releases for testing JBT

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19724?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19724: ------------------------------- Fix Version/s: 4.3.0.Beta1 > Provide public version of alpha releases for testing JBT > -------------------------------------------------------- > > Key: JBIDE-19724 > URL: https://issues.jboss.org/browse/JBIDE-19724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: ehsavoie Hugonnet > Fix For: 4.3.0.Beta1 > > > As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. > Could you provide such a bundle à la JBDS during the testing periods ? > http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19724) Provide public version of alpha releases for testing JBT

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19724?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19724: ---------------------------------- Assignee: Nick Boldt > Provide public version of alpha releases for testing JBT > -------------------------------------------------------- > > Key: JBIDE-19724 > URL: https://issues.jboss.org/browse/JBIDE-19724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: ehsavoie Hugonnet > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. > Could you provide such a bundle à la JBDS during the testing periods ? > http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19724) Provide public version of alpha releases for testing JBT

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19724?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19724: ------------------------------------ Currently, it's not possible to provide pre-release JBDS installers. But starting from Beta1 we WILL have JBDS 9 installers available on http://tools.jboss.org/downloads/overview.html as we did for JBDS 8.x. > Provide public version of alpha releases for testing JBT > -------------------------------------------------------- > > Key: JBIDE-19724 > URL: https://issues.jboss.org/browse/JBIDE-19724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: ehsavoie Hugonnet > Fix For: 4.3.0.Beta1 > > > As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. > Could you provide such a bundle à la JBDS during the testing periods ? > http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19729) Version Auditing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19729?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19729: ------------------------------- Epic Colour: ghx-label-6 (was: ghx-label-4) > Version Auditing > ---------------- > > Key: JBIDE-19729 > URL: https://issues.jboss.org/browse/JBIDE-19729 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > > Epic to track issues related to auditing and quality control. > This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19072) Improve plugin version auditing & how we build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19072?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-19072. ------------------------------ Resolution: Done Had to reopen to mark the Epic as "Done". Closing again. > Improve plugin version auditing & how we build > ---------------------------------------------- > > Key: JBIDE-19072 > URL: https://issues.jboss.org/browse/JBIDE-19072 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Alpha1: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3246) As part of JBoss Tools team I would like to gather usage, feedback, download statistics to get better insight into what are our users do/struggle with so I can fix issues and implement features that matters and help the user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3246?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3246: ----------------------------- Epic Name: Usage analytics/Error feedback (was: Usage analytis/Error feedback) > As part of JBoss Tools team I would like to gather usage, feedback, download statistics to get better insight into what are our users do/struggle with so I can fix issues and implement features that matters and help the user > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3246 > URL: https://issues.jboss.org/browse/JBDS-3246 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 9.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19072) Improve plugin version auditing & how we build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19072?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19072: ------------------------------- Epic Status: Done > Improve plugin version auditing & how we build > ---------------------------------------------- > > Key: JBIDE-19072 > URL: https://issues.jboss.org/browse/JBIDE-19072 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Alpha1: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17265) Build should be easy to use on jenkins and locally with predictable results

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17265?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-17265. ------------------------------ Resolution: Done Closed. Please use JBIDE-19730 for future Epic grouping. > Build should be easy to use on jenkins and locally with predictable results > --------------------------------------------------------------------------- > > Key: JBIDE-17265 > URL: https://issues.jboss.org/browse/JBIDE-17265 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19731) Selecting "remove" before a hybrid mobile engine is created logs exception - no feeback is provided to users in the UI

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-19731: ------------------------------------ Summary: Selecting "remove" before a hybrid mobile engine is created logs exception - no feeback is provided to users in the UI Key: JBIDE-19731 URL: https://issues.jboss.org/browse/JBIDE-19731 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.3.0.Alpha2 Reporter: Len DiMaggio Priority: Minor To recreate: * With no hybrid mobile engines defined * Preferences->Hybrid Mobile-> Engines * Click on "remove" and the exception is logged - no feedback is provided to the user in the UI !ENTRY org.eclipse.ui 4 0 2015-04-28 14:30:25.700 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.ClassCastException: org.eclipse.thym.core.extensions.PlatformSupport cannot be cast to org.eclipse.thym.core.engine.HybridMobileEngine at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection.handleRemoveEngine(AvailableCordovaEnginesSection.java:606) at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection.access$4(AvailableCordovaEnginesSection.java:598) at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection$5.handleEvent(AvailableCordovaEnginesSection.java:378) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) at org.eclipse.jface.window.Window.open(Window.java:803) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:63) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1438) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17265) Build should be easy to use on jenkins and locally with predictable results

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17265?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17265: ------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.x) > Build should be easy to use on jenkins and locally with predictable results > --------------------------------------------------------------------------- > > Key: JBIDE-17265 > URL: https://issues.jboss.org/browse/JBIDE-17265 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19727) An error of "0" is displayed to the user after a failed Cordova mobile engine install

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19727?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-19727: -------------------------------------- Alternate steps to recreate: * With no Mobile Engine configured: ** Preferences->Hybrid Mobile->Engines ** Select Android - the error dialog is displayed and the exception is logged > An error of "0" is displayed to the user after a failed Cordova mobile engine install > ------------------------------------------------------------------------------------- > > Key: JBIDE-19727 > URL: https://issues.jboss.org/browse/JBIDE-19727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: error.png, jbosstools-diagnostics-20150428131923.zip > > > When trying to install a 4.0 Cordova mobile engine, this error dialog is displayed: > An error has occurred. See error log for more details. > 0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19072) Improve plugin version auditing & how we build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19072?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-19072. ------------------------------ Resolution: Done Closing. Unresolved issues are now under one of two epics: JBIDE-19729 - Version Auditing JBIDE-19730 - Build Improvement > Improve plugin version auditing & how we build > ---------------------------------------------- > > Key: JBIDE-19072 > URL: https://issues.jboss.org/browse/JBIDE-19072 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Alpha1: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17103) No warning/error is shown when detected runtime fails to be added

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17103: ------------------------------------- Again, the patch as submitted should be 100% source-compatible, for both callers AND implementers... so as long as all teams are compiling against the version they'll be using, there shouldn't be a problem. The only problem here would be if IS guys compile against our luna version but then run against our Mars plugins. But yes, it should be raised to them for awareness. > No warning/error is shown when detected runtime fails to be added > ----------------------------------------------------------------- > > Key: JBIDE-17103 > URL: https://issues.jboss.org/browse/JBIDE-17103 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.x > > > When there is a new version of a runtime, e.g. WildFly 8.1, that is not yet supported by the tooling, runtime detection usually detects it alright, but when you then click OK, the runtime+server are not added. And there is no error anywhere at all - we should fix that. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19726) Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19726?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19726: --------------------------------- Attachment: IMG_2768.MOV An error dialog is displayed, but it is only visible for a fraction of a second. See the attached cell phone movie - I was working on RHEL and did not have a good screencast tool. > Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19726 > URL: https://issues.jboss.org/browse/JBIDE-19726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: IMG_2768.MOV > > > Attempts to configure Cordova version 4.0 fail - another case of changes in directory tree - the errors are written to the .log, and are not communicated to the user via the UI > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/cordova-4.0.0.jar > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/assets/www/cordova.js > !ENTRY org.eclipse.thym.ios.core 4 0 2015-04-28 11:28:43.882 > !MESSAGE Can not detect version. VERSION file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/CordovaLib/VERSION is missing -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19730) Build Improvement

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19730?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19730: ------------------------------- Description: Epic to track issues related to improving how we release software. This may include tools & workflows to improve how we build, what we build, how we release, process automation, Jenkins, etc. was: Epic to track issues related to auditing and quality control. This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc. > Build Improvement > ----------------- > > Key: JBIDE-19730 > URL: https://issues.jboss.org/browse/JBIDE-19730 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > > Epic to track issues related to improving how we release software. > This may include tools & workflows to improve how we build, what we build, how we release, process automation, Jenkins, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19730) Build Improvements

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19730: ---------------------------------- Summary: Build Improvements Key: JBIDE-19730 URL: https://issues.jboss.org/browse/JBIDE-19730 Project: Tools (JBoss Tools) Issue Type: Epic Components: build Affects Versions: 4.3.0.Alpha2 Reporter: Nick Boldt Epic to track issues related to auditing and quality control. This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19730) Build Improvements

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19730?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19730: ------------------------------- Epic Name: Build Improvement (was: Version Auditing) > Build Improvements > ------------------ > > Key: JBIDE-19730 > URL: https://issues.jboss.org/browse/JBIDE-19730 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > > Epic to track issues related to auditing and quality control. > This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19730) Build Improvement

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19730?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19730: ------------------------------- Summary: Build Improvement (was: Build Improvements) > Build Improvement > ----------------- > > Key: JBIDE-19730 > URL: https://issues.jboss.org/browse/JBIDE-19730 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > > Epic to track issues related to auditing and quality control. > This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19726) Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19726?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19726: --------------------------------- Summary: Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second (was: Error messages related to failures configuring Cordova version 4 engine are written to .log, not displayed to user) > Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19726 > URL: https://issues.jboss.org/browse/JBIDE-19726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > > Attempts to configure Cordova version 4.0 fail - another case of changes in directory tree - the errors are written to the .log, and are not communicated to the user via the UI > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/cordova-4.0.0.jar > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/assets/www/cordova.js > !ENTRY org.eclipse.thym.ios.core 4 0 2015-04-28 11:28:43.882 > !MESSAGE Can not detect version. VERSION file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/CordovaLib/VERSION is missing -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19729) Version Auditing

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19729: ---------------------------------- Summary: Version Auditing Key: JBIDE-19729 URL: https://issues.jboss.org/browse/JBIDE-19729 Project: Tools (JBoss Tools) Issue Type: Epic Components: build Affects Versions: 4.3.0.Alpha2 Reporter: Nick Boldt Epic to track issues related to auditing and quality control. This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17103) No warning/error is shown when detected runtime fails to be added

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17103: --------------------------------------------- since this is used by seam, drools, esb, and I assume others this should be raised to IS guys on jbosstools-dev at least. > No warning/error is shown when detected runtime fails to be added > ----------------------------------------------------------------- > > Key: JBIDE-17103 > URL: https://issues.jboss.org/browse/JBIDE-17103 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.x > > > When there is a new version of a runtime, e.g. WildFly 8.1, that is not yet supported by the tooling, runtime detection usually detects it alright, but when you then click OK, the runtime+server are not added. And there is no error anywhere at all - we should fix that. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19714) seam.core test failure

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19714?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19714: ----------------------------------- Sprint: Sprint #2 April 2015 (was: Sprint #3 May 2015) > seam.core test failure > ---------------------- > > Key: JBIDE-19714 > URL: https://issues.jboss.org/browse/JBIDE-19714 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.3.0.Alpha2 > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Fix For: 4.3.0.Beta1 > > > Failed tests: > SeamComponentRefactoringTest.testSeamComponentRename:90->renameComponent:142 There is unexpected number of changes expected:<7> but was:<3> > SeamContextVariableRefactoringTest.testSeamContextVariable_Component_Rename:76->AbstractRefactorTest.checkRename:33 expected:<2> but was:<1> > SeamEARTest.testEarProject:80 War project must see component 'org.jboss.seam.core.interpolator' declared in ejb project -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19467) repository-utils :: FetchSourcesFromManifests should create its own source zip, not rely on publish.sh

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19467?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19467: ------------------------------------ I've merged PR #38. Things to fix in the next iteration: * remove commented block about md5 generation * use enum instead of two ints for CACHE_ZIPS, etc. * decide what to put in target/repository/ instead of target/fullSite/all/ * investigate using truezip? * make output filename more generic / parameterized, not just jbosstools-src.zip Things suggested today by Max: * include buildinfo.json files in the zip * compare SHA from buildinfo.json files w/ the value found in MANIFEST.MF files; if they don't match, break the build * get more properties into buildinfo.json for ALL builds (including those in _master branch, which currently show nulls) ** TARGET_PLATFORM_* ** BUILD_ID, BUILD_NUMBER, BUILD_ALIAS ** JOB_NAME ** jbosstools_site_stream ? > repository-utils :: FetchSourcesFromManifests should create its own source zip, not rely on publish.sh > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19467 > URL: https://issues.jboss.org/browse/JBIDE-19467 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > In repository-utils, FetchSourcesFromManifests should create its own source zip, not rely on publish.sh. Because we no longer use publish.sh and don't want to have rsync.sh produce artifacts, only rsync them. > Here's what publish.sh does: > {code} > # collect component zips from upstream aggregated build jobs > if [[ ${JOB_NAME/.aggregate} != ${JOB_NAME} ]] && [[ -d ${WORKSPACE}/sources/aggregate/site/zips ]]; then > mkdir -p ${STAGINGDIR}/components > for z in $(find ${WORKSPACE}/sources/aggregate/site/zips -name "*updatesite-*.zip"); do > # generate MD5 sum for zip (file contains only the hash, not the hash + filename) > for m in $(md5sum ${z}); do if [[ $m != ${z} ]]; then echo $m > ${z}.MD5; fi; done > mv $z ${z}.MD5 ${STAGINGDIR}/components > done > # TODO :: JBIDE-9870 When we have a -Update-Sources- zip, this can be removed > mkdir -p ${STAGINGDIR}/all/sources > # OLD: unpack component source zips like jbosstools-pi4soa-3.1_trunk-Sources-SNAPSHOT.zip or jbosstools-3.2_trunk.component--ws-Sources-SNAPSHOT.zip > # NEW: JBIDE-16632: unpack component source zips like jbosstools-base_Alpha2-v20140221-1555-B437_184e18cc3ac7c339ce406974b6a4917f73909cc4_sources.zip > for z in $(find ${WORKSPACE}/sources/aggregate/site/zips -name "*Sources*.zip" -o -name "*_sources.zip" -o -name "*-src.zip"); do > zn=${z%*-Sources*.zip}; zn=${zn%*_sources.zip}; zn=${zn%*-src.zip}; zn=${zn#*--}; zn=${zn##*/}; zn=${zn#jbosstools-}; > # zn=${zn%_trunk}; zn=${zn%_stable_branch}; > mkdir -p ${STAGINGDIR}/all/sources/${zn}/ > # remove one level of folder nesting - don't want an extra jbosstools-base-184e18cc3ac7c339ce406974b6a4917f73909cc4 folder under jbosstools-base_Alpha2-v20140221-1555-B437_184e18cc3ac7c339ce406974b6a4917f73909cc4 > unzip -qq -o -d ${tmpdir}/${zn}/ $z > mkdir -p ${STAGINGDIR}/all/sources/${zn}/ > mv ${tmpdir}/${zn}/jbosstools-*/* ${STAGINGDIR}/all/sources/${zn}/ > rm -fr ${tmpdir}/${zn}/ > done > # add component sources into sources zip > pushd ${STAGINGDIR}/all/sources > zip ${STAGINGDIR}/all/${SRCSNAME} -q -r * -x hudson_workspace\* -x documentation\* -x download.jboss.org\* -x requirements\* \ > -x workingset\* -x labs\* -x build\* -x \*test\* -x \*target\* -x \*.class -x \*classes\* -x \*bin\* -x \*.zip \ > -x \*docs\* -x \*reference\* -x \*releng\* -x \*.git\* -x \*/lib/\*.jar -x \*getRemoteFile\* > popd > rm -fr ${STAGINGDIR}/all/sources > z=${STAGINGDIR}/all/${SRCSNAME}; for m in $(md5sum ${z}); do if [[ $m != ${z} ]]; then echo $m > ${z}.MD5; fi; done > # JBIDE-7444 get aggregate metadata xml properties file > if [[ -f ${WORKSPACE}/sources/aggregate/site/zips/build.properties.all.xml ]]; then > rsync -aq ${WORKSPACE}/sources/aggregate/site/zips/build.properties.all.xml ${STAGINGDIR}/logs/ > fi > fi > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19532: -------------------------------- Attachment: JBIDE-19532.png Screenshot showing error ;) > "Edit Server Runtime Environment" Dialog configuration validation is broken > --------------------------------------------------------------------------- > > Key: JBIDE-19532 > URL: https://issues.jboss.org/browse/JBIDE-19532 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > Attachments: data-folder-config.png, Edit Server Runtime Environment _102.png, JBIDE-19532.png > > > If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start. > {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist. > at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213) > at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-19532: ----------------------------------- Assignee: Denis Golovin (was: Rob Stryker) > "Edit Server Runtime Environment" Dialog configuration validation is broken > --------------------------------------------------------------------------- > > Key: JBIDE-19532 > URL: https://issues.jboss.org/browse/JBIDE-19532 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > Attachments: data-folder-config.png, Edit Server Runtime Environment _102.png > > > If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start. > {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist. > at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213) > at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-19697: --------------------------------------- This is the old code assuming the following JBDS file structure: JBDS_HOME/runtimes JBDS_HOME/studio JBDS_HOME/studio/features JBDS_HOME/studio/plugins JBDS_HOME/studio/configuration In your case, Eclipse has found EAP 6.3 in one of the following directories: /Users/rasp/jbossqa/JBDS/9.0.0/jbdevstudio-9.0.0.Alpha1-java8/studio/runtime_locations.properties /Users/rasp/jbossqa/JBDS/9.0.0/jbdevstudio-9.0.0.Alpha2-24/studio/runtime_locations.properties See also JBIDE-19713. > org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19697 > URL: https://issues.jboss.org/browse/JBIDE-19697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Snjezana Peco > > When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs' > Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs > {code} > This is inside the file: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat > eclipse.preferences.version=1 > runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n > {code} > It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen? > I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now. > Can somebody explain what's going on? > Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19725) EasyImport plugin title misspelled

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19725?page=com.atlassian.jira.plugi... ] Gorkem Ercan reassigned JBIDE-19725: ------------------------------------ Assignee: Mickael Istria (was: Ilya Buziuk) > EasyImport plugin title misspelled > ---------------------------------- > > Key: JBIDE-19725 > URL: https://issues.jboss.org/browse/JBIDE-19725 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Mickael Istria > Attachments: import.png > > > The plugin name is spelled as: > JBoss Easymport for Aerogear -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19725) EasyImport plugin title misspelled

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19725?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19725: -------------------------------------- Assigning to [~mickael_istria] so that he can have the pleasure to explain "Easymport" is in fact correct.. [~mickael_istria] we do not use "aerogear" on user visible strings.. It is Hybrid Mobile for user strings. > EasyImport plugin title misspelled > ---------------------------------- > > Key: JBIDE-19725 > URL: https://issues.jboss.org/browse/JBIDE-19725 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Mickael Istria > Attachments: import.png > > > The plugin name is spelled as: > JBoss Easymport for Aerogear -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19719: --------------------------------- Component/s: integration-platform (was: aerogear-hybrid) > EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19725) EasyImport plugin title misspelled

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19725?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19725: ------------------------------------ Assignee: Ilya Buziuk (was: Gorkem Ercan) > EasyImport plugin title misspelled > ---------------------------------- > > Key: JBIDE-19725 > URL: https://issues.jboss.org/browse/JBIDE-19725 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Ilya Buziuk > Attachments: import.png > > > The plugin name is spelled as: > JBoss Easymport for Aerogear -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19719: --------------------------------- Component/s: aerogear-hybrid (was: integration-platform) > EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19728) Easy Import - The first and second screens in the dialog should be merged into one

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19728?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19728: -------------------------------------- These are not aerogear dialogs. [~mickael_istria] Do you know the correct component for easy import > Easy Import - The first and second screens in the dialog should be merged into one > ---------------------------------------------------------------------------------- > > Key: JBIDE-19728 > URL: https://issues.jboss.org/browse/JBIDE-19728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Mickael Istria > Attachments: import_1.png, import_2.png > > > See the attached screenshots - in the first dialog screen (1/6), the user is presented with a largely blank display. After he/she selects "next" the dialog (2/6) shows the projects that are eligible to be imported. > Why not simply skip the first screen and start with the second? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19726) Error messages related to failures configuring Cordova version 4 engine are written to .log, not displayed to user

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19726?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19726: --------------------------------- Component/s: aerogear-hybrid (was: integration-platform) > Error messages related to failures configuring Cordova version 4 engine are written to .log, not displayed to user > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19726 > URL: https://issues.jboss.org/browse/JBIDE-19726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > > Attempts to configure Cordova version 4.0 fail - another case of changes in directory tree - the errors are written to the .log, and are not communicated to the user via the UI > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/cordova-4.0.0.jar > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/assets/www/cordova.js > !ENTRY org.eclipse.thym.ios.core 4 0 2015-04-28 11:28:43.882 > !MESSAGE Can not detect version. VERSION file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/CordovaLib/VERSION is missing -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19726) Error messages related to failures configuring Cordova version 4 engine are written to .log, not displayed to user

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19726?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19726: ------------------------------------ Assignee: Gorkem Ercan > Error messages related to failures configuring Cordova version 4 engine are written to .log, not displayed to user > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19726 > URL: https://issues.jboss.org/browse/JBIDE-19726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > > Attempts to configure Cordova version 4.0 fail - another case of changes in directory tree - the errors are written to the .log, and are not communicated to the user via the UI > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/cordova-4.0.0.jar > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/assets/www/cordova.js > !ENTRY org.eclipse.thym.ios.core 4 0 2015-04-28 11:28:43.882 > !MESSAGE Can not detect version. VERSION file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/CordovaLib/VERSION is missing -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2015