[JBoss JIRA] (JBIDE-24357) JSF New and Noteworthy for 4.4.4.Final
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24357?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-24357.
------------------------------
Resolution: Rejected
> JSF New and Noteworthy for 4.4.4.Final
> -----------------------------------------------------
>
> Key: JBIDE-24357
> URL: https://issues.jboss.org/browse/JBIDE-24357
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsf, jsp/jsf/xml/html-source-editing
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.4.4.Final
>
>
> Jeff MAURY,
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed JSF JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...]
> * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...]
> If no N&N issues are found for JSF, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for JSF by submitting a pull request against:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> If your PR's commit comment is of the form... {code}JBIDE-24345 #comment Create N&N for JSF 4.4.4.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied.
> If there is nothing new or noteworthy for JSF for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.4.4.Final since the AM3 release of JSF, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents.
> If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.4.Final.adoc file here:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc.
> However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.4.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24354) Base New and Noteworthy for 4.4.4.Final
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24354?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-24354.
------------------------------
Resolution: Rejected
> Base New and Noteworthy for 4.4.4.Final
> -----------------------------------------------------
>
> Key: JBIDE-24354
> URL: https://issues.jboss.org/browse/JBIDE-24354
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common, foundation, usage
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.4.4.Final
>
>
> Jeff MAURY,
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed Base JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...]
> * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...]
> If no N&N issues are found for Base, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for Base by submitting a pull request against:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> If your PR's commit comment is of the form... {code}JBIDE-24345 #comment Create N&N for Base 4.4.4.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied.
> If there is nothing new or noteworthy for Base for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.4.4.Final since the AM3 release of Base, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents.
> If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.4.Final.adoc file here:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc.
> However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.4.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-3635) Add the ability to detect/select existing dependencies/tools
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3635?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3635.
-----------------------------
Resolution: Done
I'm closing this, since the work here is done, I believe.
> Add the ability to detect/select existing dependencies/tools
> ------------------------------------------------------------
>
> Key: JBDS-3635
> URL: https://issues.jboss.org/browse/JBDS-3635
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Critical
> Labels: havoc, ui
> Fix For: 11.0.0.AM1
>
> Attachments: Technologies 5.pdf, pdkinstaller.png
>
>
> Generic rules for detection and validation are:
> 1. We do our best to detect what is installed on user's machine: vagrant, virtualbox, java and do not detect cdk, cygwin, or DevStudio;
> 2. When version is detected it must be verified against the range of what we believe valid versions; it might be defined as a set or condition.
> vagrant: minimal and tested version is 1.7.4, all newer releases are good to continue with warning except 1.8.0 which is known to have networking problems;
> virtualbox: minimal and tested 5.0.8 and all newer releases are good to continue with warning;
> jvm: minimal and tested is 1.8 and all newer releases are good to continue with warning;
> 3. For vagrant and virtual box if detected version is out of the range, installer shows error message with explanation and doesn't let go any further until detected version is uninstalled, which should be done manually and then installer should be restarted; If nothing is detected included versions can be installed or installer could be configured to use specific location;
> 4. For JVM if not supported version is detected, included one can be used or installer could be pointed to right location to use.
> 5. When location for required software set manually installer try will try detect version and verify it using (2);
> 6. When version cannot be detected and manually selected location looks like required install, installer should let to proceed with warning.
> It would be great if the installer allowed the user to use some of the required tools they have already installed.
> The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc.
> The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter):
> !pdkinstaller.png|thumbnail!
> [~dgolovin] & [~crobson], what's your opinion on this?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months