May 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3025) Installer duplicates last folder in path causing errors (Mac OS X)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3025?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3025: -------------------------------- Fix Version/s: 8.0.0.Beta2 > Installer duplicates last folder in path causing errors (Mac OS X) > ------------------------------------------------------------------ > > Key: JBDS-3025 > URL: https://issues.jboss.org/browse/JBDS-3025 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta1 > Reporter: Michelle Murray > Fix For: 8.0.0.Beta2 > > Attachments: Installer_jrelocationerror.png > > > Mac OS X Mavericks > Universal installer, step 4 - choose JVM: > * Click 'Specific Java JVM' > * Click Browse to locate JDK or JRE > * Navigate to find folder and click ok in file browser > the last folder is added twice to the displayed path > In most cases this path now doesn't exist and causes error messages to this extent. > !Installer_jrelocationerror.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3025) Installer duplicates last folder in path causing errors (Mac OS X)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3025?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3025: ------------------------------------- There was a problem on previous OS X versions, when file chooser always returned parent folder instead of created one. I'll check if I can replicate it on 10.8.5. > Installer duplicates last folder in path causing errors (Mac OS X) > ------------------------------------------------------------------ > > Key: JBDS-3025 > URL: https://issues.jboss.org/browse/JBDS-3025 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta1 > Reporter: Michelle Murray > Attachments: Installer_jrelocationerror.png > > > Mac OS X Mavericks > Universal installer, step 4 - choose JVM: > * Click 'Specific Java JVM' > * Click Browse to locate JDK or JRE > * Navigate to find folder and click ok in file browser > the last folder is added twice to the displayed path > In most cases this path now doesn't exist and causes error messages to this extent. > !Installer_jrelocationerror.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9479) Enhance custom classpath containers for additional support such as as7's modules tag

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9479?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9479: -------------------------------------------- [~rawb] could you add some screenshots for this ? Trying to understand what this is doing but fileset is definitely not what I would expect so i'm wondering if just overloading of terms. > Enhance custom classpath containers for additional support such as as7's modules tag > ------------------------------------------------------------------------------------ > > Key: JBIDE-9479 > URL: https://issues.jboss.org/browse/JBIDE-9479 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 3.3.0.M3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.Beta2 > > > Enhance /JBIDE-1354 to allow for additional types of filesets. > 1) Maintain backwards compatibility in terms of reading legacy files stores and functioning properly > 2) If user makes a change, save in new persistance format > 3) Add core elements for a 'module id' based classpath provider, only for jboss servers that have jboss-modules as a base > 4) Expand UI to allow creation of a classpath element by using a module id instead of a basedir/includes/excludes pattern > Out of scope for this issue: Core/UI for a per-facet customized response. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3023) Universal installer step4 Java statement needs updating

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3023?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3023: ----------------------------------- Assignee: Denis Golovin > Universal installer step4 Java statement needs updating > ------------------------------------------------------- > > Key: JBDS-3023 > URL: https://issues.jboss.org/browse/JBDS-3023 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta1 > Reporter: Michelle Murray > Assignee: Denis Golovin > Priority: Blocker > Fix For: 8.0.0.Beta2 > > > Universal installer, step 4 states: > "JBoss Developer Studio works with Java 6 and 7 and has been tested with OpenJDK, Oracle and Apple JDK." > According to the approved QE test plan (mojo DOC-932620): > * Only Java 7 and Java 8 are supported for running the IDE (Java 6 support for app development only) > * Apple JDK (which is Java 6) is not supported for running the IDE; it's supported for app development only > For clarity, suggest changing text to: > "JBoss Developer Studio can be run with Java 7 and 8 and has been tested with OpenJDK and Oracle JDK." -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3023) Universal installer step4 Java statement needs updating

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3023?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3023: -------------------------------- Fix Version/s: 8.0.0.Beta2 > Universal installer step4 Java statement needs updating > ------------------------------------------------------- > > Key: JBDS-3023 > URL: https://issues.jboss.org/browse/JBDS-3023 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta1 > Reporter: Michelle Murray > Priority: Blocker > Fix For: 8.0.0.Beta2 > > > Universal installer, step 4 states: > "JBoss Developer Studio works with Java 6 and 7 and has been tested with OpenJDK, Oracle and Apple JDK." > According to the approved QE test plan (mojo DOC-932620): > * Only Java 7 and Java 8 are supported for running the IDE (Java 6 support for app development only) > * Apple JDK (which is Java 6) is not supported for running the IDE; it's supported for app development only > For clarity, suggest changing text to: > "JBoss Developer Studio can be run with Java 7 and 8 and has been tested with OpenJDK and Oracle JDK." -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3014) On Mac Maverick JVM shared library points to wrong directory

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3014?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3014: ------------------------------------------- If the same thing happened my guess is you didn't point the installer onto a JDK. Both [~robb.greathouse] and [~eabrand] comments suggest to me you are not running the installer or JBDS with a JDK but with a JRE installed into your webbrowser. Is that correct ? > On Mac Maverick JVM shared library points to wrong directory > ------------------------------------------------------------ > > Key: JBDS-3014 > URL: https://issues.jboss.org/browse/JBDS-3014 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta1 > Environment: Mac on Maverick > Reporter: Robb Greathouse > > The JVM shared library "/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/../lib/server/libjvm.dylib" > does not contain the JNI_CreateJavaVM symbol. > This prevents it from starting. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16931) Support for linked folders in cordovasim

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16931?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16931: --------------------------------------------- doesn't the CS use a embedded server to serve its content ? how else do you navigate the workspace content ? passing linked folder name to actual location of the folder wont work since eclipse linked folders can be more than that. Seems easier to just run the CS serving side inside eclipse and let CS connect to it ? > Support for linked folders in cordovasim > ---------------------------------------- > > Key: JBIDE-16931 > URL: https://issues.jboss.org/browse/JBIDE-16931 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, browsersim > Affects Versions: 4.2.0.Alpha2 > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Fix For: 4.2.0.Beta2 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Linked folders are not honored when project is run on CordovaSim -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-492) Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-492?page=com.atlassian.jira.plug... ] Max Rydahl Andersen commented on TOOLSDOC-492: ---------------------------------------------- I commented on the PR - great progress but could we keep this about docs first, website/webcontent later ? > Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process) > ------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-492 > URL: https://issues.jboss.org/browse/TOOLSDOC-492 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Guide > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Michelle Murray > Fix For: 4.2.0.Beta2 > > Attachments: converted-adoc-asciidoc-css-not-github-css.png, converted-adoc-github-css-actual.png, converted-adoc-github-css.png, openshift-chapter-generated-epub.png, openshift-chapter-generated-pdf.png > > > With the release of the new tools.jboss.org site, it's time to migrate the docs to the same skin / format / markup. Docbook is dead, long live Asciidoc! > What [~mmurray] and I are thinking is that we would have a new landing page similar to one of these: > http://tools.jboss.org/features/ (with icons that link to projects' latest doc) > or > http://tools.jboss.org/documentation/whatsnew/ (with the latest doc linked) > And then under that landing page we'd have doc for each of projects' contributions to the User Guide, by milestone or Final release. > Questions: > a. [~maxandersen] [~burrsutter] [~mmusaji] Do we still need to provide 3 formats of doc - HTML, HTML-single, and PDF? Or can we replace that with this new content, PLUS include inline help doc within Eclipse? (That's another issue - see [~dgolovin] 's https://github.com/dgolovin/jbosstools-eclipse-docs/blob/master/docs/scen... for prototype) > b. [~maxandersen] Should we include docs for "dead" projects like Freemarker, Portal, etc.? I'm guessing YES, even if the doc becomes out of date (ie., the doc for JBT 4.2 for Freemarker won't have changed much (or at all) since JBT 4.0/4.1). > c. [~maxandersen] Should we convert old JBT 4.1.x (and/or 4.0.x, 3.3.x) doc to the new adoc format, or just start w/ the JBT 4.2.0.Beta1/2 doc? I'd be OK with 4.1 and maybe 4.0, but can we skip 3.3 since JBDS 5 is no longer fully supported? > d. Will docbook2asciidoc [0] work for batch-converting docbook docs to adoc? @nick will try. If conversion works easily, then converting older User Guides is definitely more doable / less time consuming. > [0] https://github.com/oreillymedia/docbook2asciidoc > e. [~xcoulon] Is :page-component_version: still used, eg., in [1], or is the filename version itself used to categorize the content by milestone? > [1] https://github.com/jbosstools/jbosstools-website/blob/master/documentatio... > f. If we decide to continue to include other formats (eg., html-single, pdf) should we link to those from these places [2], [3]? > [2] http://tools.jboss.org/downloads/overview.html > [3] http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15897) Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15897 at 5/5/14 11:22 AM: ------------------------------------------------------------------- we're missing the following in the server context menu: - Import Application (not shown if the project already exists) - Edit Embedded Cartidges - Application Details - Refresh the following dont make a lot of sense: - Delete Application (if we delete the application, we'd have to delete the adapter too. An adapter without it's application is useless) was (Author: adietish): we're missing the following in the server context menu: - Import Application - Edit Embedded Cartidges - Application Details - Refresh the following dont make a lot of sense: - Delete Application (if we delete the application, we'd have to delete the adapter too. An adapter without it's application is useless) > Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15897 > URL: https://issues.jboss.org/browse/JBIDE-15897 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Labels: server_adapter > Fix For: 4.2.0.Beta2 > > Attachments: explorer-context-menu.png, explorer-context-menu.png, server-adapter-context-menu.png, server-adapter-context-menu.png > > Original Estimate: 1 day > Remaining Estimate: 1 day > > JBIDE-11841 was done earlier but only added the missing actions - when new actions are added we tend to forget to add them. > Explorer: > !explorer-context-menu.png! > Server adapter: > !server-adapter-context-menu.png! > We should make it so these actions (when relevant) gets added to both places (openshift explorer / server adapter) and optimally also available in an OpenShift context menu on a project. > Meaning you don't have to navigate to explorer view constantly. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15897) Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15897: ------------------------------------------ [~maxandersen] please comment > Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15897 > URL: https://issues.jboss.org/browse/JBIDE-15897 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Labels: server_adapter > Fix For: 4.2.0.Beta2 > > Attachments: explorer-context-menu.png, explorer-context-menu.png, server-adapter-context-menu.png, server-adapter-context-menu.png > > Original Estimate: 1 day > Remaining Estimate: 1 day > > JBIDE-11841 was done earlier but only added the missing actions - when new actions are added we tend to forget to add them. > Explorer: > !explorer-context-menu.png! > Server adapter: > !server-adapter-context-menu.png! > We should make it so these actions (when relevant) gets added to both places (openshift explorer / server adapter) and optimally also available in an OpenShift context menu on a project. > Meaning you don't have to navigate to explorer view constantly. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 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 May 2014