[JBoss JIRA] (JBIDE-10658) find place where description for category should live
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-10658:
-------------------------------------------
Summary: find place where description for category should live
Key: JBIDE-10658
URL: https://issues.jboss.org/browse/JBIDE-10658
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Fix For: 3.3.0.Beta1
Suggestion is that we add a category.xml that allows you to define category description to be used.
category.xm will basically work like a 'forced overwrite' of what is in the project examples.xml
if a category is found that does not exist in category.xml it still shows up.
if a category is found that does exist in category.xml it shows up with info from category.xml no matter what project example otherwise state.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBIDE-10763) Project examples cache logic is faulty
by Rob Cernich (JIRA)
Rob Cernich created JBIDE-10763:
-----------------------------------
Summary: Project examples cache logic is faulty
Key: JBIDE-10763
URL: https://issues.jboss.org/browse/JBIDE-10763
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 3.3.0.M5
Reporter: Rob Cernich
Assignee: Snjezana Peco
Project examples files that are provided by plugins using a plugin URL (e.g. platform:/plugin/plugin.id/...) fail to be refreshed. The only workaround is to delete the cached file from the workspace's .metadata.
The following logic in ProjectUtils.getProjectExamplesFile() is incorrect:
{code:java}
if (urlModified == 0) {
if (file.exists()) {
return file;
}
}
{code}
as '0' is the same as IRemoteFileInfo.NO_LAST_MODIFIED. If urlModified == IRemoteFileInfo.NO_LAST_MODIFIED, the file should always be updated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBIDE-10691) the "requirements" part of project examples should not 'disappear' when they are fullfilled
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-10691:
-------------------------------------------
Summary: the "requirements" part of project examples should not 'disappear' when they are fullfilled
Key: JBIDE-10691
URL: https://issues.jboss.org/browse/JBIDE-10691
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 3.3.0.M5
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.Beta1
I find it to be a usability issue that we "hide" the requirements for an example when they are fullfilled.
i.e. if an example says it supports as7 & eap6 and provide download of as7 then this requirements will disappear when you have eap6 installed even if you wanted to try out as7.
Would be better if these stayed around and showed an "Requirement fullfilled" indicator somehow (Green checkmark?) and allow users still to install/download additional runtime if that is what they wish to do.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBIDE-10264) Wizard-ify the project examples
by Fred Bricon (Created) (JIRA)
Wizard-ify the project examples
-------------------------------
Key: JBIDE-10264
URL: https://issues.jboss.org/browse/JBIDE-10264
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: project-examples
Affects Versions: 3.3.0.M4
Reporter: Fred Bricon
Assignee: Snjezana Peco
Fix For: 3.3.0.Beta1
In the wake of JBIDE-9776 and JBIDE-10140, it turns out that, in order for us to contribute 5 new wizards to the "New " menu under the Jboss perspective and in the "New project" section of JBoss central, "project examples" based projects should be created via a Wizard implementation from the get go.
Current project examples workflow involves :
- displaying a form dialog : to display missing runtimes and let the user install/download the required runtimes
- launching a workspace job, which in turn :
* downloads the example
* does the actual project import (launches a wizard for maven archetypes)
* resolve quickfixes
Ideally, all these steps would be part of a single wizard, spanning one to 3 pages (depending on the complexity/requirements of the examples). Everything contributed by the form dialog would be replaced by a wizard page, which would bring consistency to the UI.
I'm aware this is not a simple task to refactor the existing workflow to such an infrastructure but ultimately, that would allow us to easily contribute new project wizards to the IDE in a standard way.
Current target is 3.3.0.Beta1. Snjeza, WDYT?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month