July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22758) Context menu for multiple selected server modules has two 'remove' options

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22758?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-22758. --------------------------------- Resolution: Done The action existed before wtp finally added support. I guess we forgot to remove it. Also fixed the icons to use the wtp publish actions, because our old arrow with a j icon is horrible. > Context menu for multiple selected server modules has two 'remove' options > -------------------------------------------------------------------------- > > Key: JBIDE-22758 > URL: https://issues.jboss.org/browse/JBIDE-22758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.1.AM2 > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.4.1.AM2 > > Attachments: remove.png > > > I have multiple projects deployed to a server (wildfly in my case) and when I select at least 2 and right click on them, the context menu shows two remove entries. > They both have different icons and they pretty much do the same, except the second one also opens an empty shell along with the confirm prompt. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22758) Context menu for multiple selected server modules has two 'remove' options

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22758?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22758: -------------------------------- Fix Version/s: 4.4.1.AM2 > Context menu for multiple selected server modules has two 'remove' options > -------------------------------------------------------------------------- > > Key: JBIDE-22758 > URL: https://issues.jboss.org/browse/JBIDE-22758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.1.AM2 > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.4.1.AM2 > > Attachments: remove.png > > > I have multiple projects deployed to a server (wildfly in my case) and when I select at least 2 and right click on them, the context menu shows two remove entries. > They both have different icons and they pretty much do the same, except the second one also opens an empty shell along with the confirm prompt. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-508) Update documentation for git based installation

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-508?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-508: ------------------------------------ [~gercan], I'm clearing out some of the lower priority issues we've had open for some time. Could you comment on whether this issue is still relevant, and if it is, I'll document it, otherwise we'll just close it as outdated. Thank you in advance! > Update documentation for git based installation > ------------------------------------------------ > > Key: TOOLSDOC-508 > URL: https://issues.jboss.org/browse/TOOLSDOC-508 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Affects Versions: 4.2.0.Beta3 > Reporter: Gorkem Ercan > Assignee: Misha Ali > Labels: documentation_update > Fix For: 4.2.0.Final > > Attachments: updated git tab.png > > > Eclipse Thym bug [1] enhances the cordova plugin discovery dialog so that the dialog can now accept urls that specify git-refs (tags, branches) and a sub directory as described on Cordova documentation [2]. We need to update our docs so that the format for such git urls are explained. > [1] 441910: Support for git-ref and sub directory is incomplete for installing Cordova plug-ins > https://bugs.eclipse.org/bugs/show_bug.cgi?id=441910 > [2] http://cordova.apache.org/docs/en/3.5.0/guide_cli_index.md.html#The%20Com... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-536) Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-536?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-536: ------------------------------------ This is potentially worth documenting in the new Forge doc if it is still valid. [~supriya.bharadwaj], since you recently worked on Forge, can you touch base with the relevant SMEs about whether this is still valid for devstudio or if we can just close this as outdated? > Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only > ----------------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-536 > URL: https://issues.jboss.org/browse/TOOLSDOC-536 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Story > Components: Installation Guide > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Michelle Murray > Attachments: jbds8b2-windows8.1-child-user-private-install-updated-via-central.png, jbds8b2-windows8.1-shared-install-readonly-now-installs-into-users-kid-.eclipse-folder.png, jbds8b2-windows8.1-standard-user-install-error-in-central.png, jbds8b2-windows8.1-standard-user-private-install-was-able-to-update-via-central.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error2.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid.png, jbds8b2-windows8.1-standard-user-shared-install-was-able-to-install-into-shared-install-folder.png, w-shared-install-jbdevstudio-security-permissions-remove-authenticated-users.png, w-shared-install-jbdevstudio-security-permissions.png, win81pro-details.png > > > To test the user experience on Windows, I created three accounts: > * nboldt (my own admin user) > * {color:orange}*dummy*{color} (a standard user) > * {color:green}*kid*{color} (a child user, which is a standard user but with Family Safety logging - http://windows.microsoft.com/en-ca/windows-8/create-child-account ) > Both the child and standard users were able to install JBDS into their own home folders and perform an installation from Central: > !jbds8b2-windows8.1-child-user-private-install-updated-via-central.png! > !jbds8b2-windows8.1-standard-user-private-install-was-able-to-update-via-central.png! > ------ > However, there are problems when using an Admin user-installed shared install folder for JBDS. > Steps to repro: > *As nboldt / admin user* > * install JBDS 8.0.0.Beta2 (B104) into W:\shared-install\jbdevstudio (using default ownership/permissions) > *As dummy / standard user* > * Log in > * Launch the shared JBDS > * Install something from Central > !jbds8b2-windows8.1-standard-user-shared-install-was-able-to-install-into-shared-install-folder.png! > *PROBLEM*: standard user should not be able to install new features into the shared install folder > *As kid / child user* > * Log in > * Launch the shared JBDS > * Noted that the suggested path for workspace was the one last used by *dummy user*, to which that user doesn't have read permission > !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid.png! > !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error.png! > !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error2.png! > *PROBLEM*: should default to current user's home dir, not another user's previous workspace selection -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-494) Add info on BrowserSim web engines + options

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-494?page=com.atlassian.jira.plug... ] Misha Ali closed TOOLSDOC-494. ------------------------------ Resolution: Out of Date > Add info on BrowserSim web engines + options > -------------------------------------------- > > Key: TOOLSDOC-494 > URL: https://issues.jboss.org/browse/TOOLSDOC-494 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.2.0.Beta1 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0.Beta2 > > > Alternative web engine available for BrowserSim/CordovaSim. > This lifts previous Windows restrictions (need for Safari 32-bit). > Both web engines are available for Mac OS X. > Only JavaFX is available for Windows (unless install Safari and go down 32-bit route). > Both web engines are available for RHEL, providing Oracle JDK installed and happy to use GTK2 or GTK3. > Only SWT WebKit is available for Fedora/Ubuntu, as Oracle JDK not supported by RH for use with IDE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22758) Context menu for multiple selected server modules has two 'remove' options

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22758?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-22758: ----------------------------------- Assignee: Rob Stryker > Context menu for multiple selected server modules has two 'remove' options > -------------------------------------------------------------------------- > > Key: JBIDE-22758 > URL: https://issues.jboss.org/browse/JBIDE-22758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.1.AM2 > Reporter: Jan Richter > Assignee: Rob Stryker > Attachments: remove.png > > > I have multiple projects deployed to a server (wildfly in my case) and when I select at least 2 and right click on them, the context menu shows two remove entries. > They both have different icons and they pretty much do the same, except the second one also opens an empty shell along with the confirm prompt. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22734) Please clarify CDK usage

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22734?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-22734. --------------------------------- Fix Version/s: 4.4.1.AM2 Resolution: Rejected I'm closing this as rejected. Seems the bug for JBDS is the proper place for it to be fixed.... as part of the installer. > Please clarify CDK usage > ------------------------ > > Key: JBIDE-22734 > URL: https://issues.jboss.org/browse/JBIDE-22734 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, docker > Environment: CDK, as used in DevStudio and installed via Development Suite. > Reporter: Rick Wagner > Fix For: 4.4.1.AM2 > > > * * This use case may be attributable to user error. Please weigh implementation cost accordingly. * * > After using the Development Suite installer, the user arrives in a newly installed DevStudio instance but without clear instructions on how to use the CDK. In my first attempt, I relied upon previous CDK experience and went to a command-line to start the CDK with 'vagrant up'. This resulted in a failure of later DevStudio components. > The proper trail is to go to the 'Servers' tab in DevStudio to bring up the environment. (Then DevStudio components like the Docker explorer will properly self-configure. This does *not* happen when the CDK is brought up manually as I had done.) > Please consider, look for ways to prevent other users from taking a similar path. Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-443) Simple guide to show app signing and deploying for iOS and Android

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-443?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-443: ------------------------------------ This is worth evaluating as a DYK addition for somewhere in the docs about exporting mobile. Moving to new project for evaluation for sprints later. > Simple guide to show app signing and deploying for iOS and Android > ------------------------------------------------------------------ > > Key: TOOLSDOC-443 > URL: https://issues.jboss.org/browse/TOOLSDOC-443 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.1.1 > Reporter: Tadeas Kriz > Assignee: Misha Ali > Fix For: 4.2.0.Final > > > The documentation shows how to export "Mobile Application" in chapter 8.3.7. It says "ready-to-sign applications", but I'd be good to show, what can the user then do with the exported application, as readers of this guide might not be aware of how native packages work. > When export is made for iOS, the output is a single .app package. For Android, it's an .apk archive. It should be made clear to user what those packages are and possibly link to official documentation on given topic if it exists. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22772) jbosstools-server build fails - EAP 7 url needs updating

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22772?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22772: ------------------------------------- This was pushed, but no idea whats causing the failures in test suite. > jbosstools-server build fails - EAP 7 url needs updating > -------------------------------------------------------- > > Key: JBIDE-22772 > URL: https://issues.jboss.org/browse/JBIDE-22772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.1.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > > jbosstools-server build has been failing since July 11. > This is the error: > {code} > 02:30:17 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-7.0.0) on project itests: IO Error: Could not get content -> [Help 1] > 02:30:17 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-7.0.0) on project itests: IO Error > 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) > 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > 02:30:17 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > 02:30:17 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > 02:30:17 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > 02:30:17 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) > 02:30:17 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355) > 02:30:17 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) > 02:30:17 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > 02:30:17 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216) > 02:30:17 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160) > 02:30:17 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 02:30:17 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > 02:30:17 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 02:30:17 at java.lang.reflect.Method.invoke(Method.java:498) > 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > 02:30:17 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error > 02:30:17 at com.googlecode.WGet.execute(WGet.java:260) > 02:30:17 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) > 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > 02:30:17 ... 19 more > 02:30:17 Caused by: org.apache.maven.plugin.MojoFailureException: Could not get content > 02:30:17 at com.googlecode.WGet.execute(WGet.java:248) > 02:30:17 ... 21 more > 02:30:17 [ERROR] > 02:30:17 [ERROR] Re-run Maven using the -X switch to enable full debug logging. > 02:30:17 [ERROR] > 02:30:17 [ERROR] For more information about the errors and possible solutions, please read the following articles: > 02:30:17 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > 02:30:17 [ERROR] > 02:30:17 [ERROR] After correcting the problems, you can resume the build with the command > 02:30:17 [ERROR] mvn <goals> -rf :itests > {code} > See here: > https://github.com/jbosstools/jbosstools-server/blob/master/as/itests/pom... > It contains an outdated link to EAP 7 ER5 build. EAP 7 GA is available for some time now, so we need to update the url. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22771) Remove Add and Remove page from new server wizard for CDK

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22771?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22771: -------------------------------- Fix Version/s: LATER > Remove Add and Remove page from new server wizard for CDK > --------------------------------------------------------- > > Key: JBIDE-22771 > URL: https://issues.jboss.org/browse/JBIDE-22771 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: LATER > > > Maybe this is just not possible, I don't know. > But I noticed that when you create a cdk server, you still go through the Add or Remove page which is not really relevant here. > And then in the Servers view, in the context menu (right-click the cdk adapter), you also have Add or Remove - could we possibly remove it from there too? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 July 2016