[
https://jira.jboss.org/jira/browse/JBIDE-5700?page=com.atlassian.jira.plu...
]
Snjezana Peco commented on JBIDE-5700:
--------------------------------------
2) Shouldn't these just be merged with the quick fixes dialog ?
Otherwise there are always two steps for the user or ? But for now its fine I guess, since
we can change the ui later on as long as the metadata is correct.
These fixes are different from quick fixes. They appear before importing a project and let
the user know what is necessary in order a project example to work correctly which is not
possible when using the quick fixes. In most of the cases, issues (missing wtp, seam ...)
would be fixed without any user intervention (especially in JBDS which contains the
default WTP Runtime, Seam Runtime and Connection Profile). And further, some issues like
"missing plugin" can't be solved using the Quick Fix dialog.
In most of the cases all the issues would be solved before the user downloads a project
example and the Quick Fix dialog wouldn't appear.
One of the most often issues is that the user and developer have different name for a Seam
or WTP Runtime. The user had to use the Quick Fix dialog before. Now, the Project Examples
engine renames the project runtimes without a user intervention. Neither the Fix nor the
Quick Fix dialog appears.
3) Shouldn't the short-description/description messages be part
of the fix-extension instead of part of each project example declaration ?
We could remove the short description message (can be determined based on the type of the
fix), but couldn't remove the description message because the developer has to let the
user know what the problem is and , eventually, how to fix it.
We could also add a button ("Fix", for instance) that would call the wizard to
create a WTP runtime, Seam Runtime, Connection Profile ...
It may be better this new dialog to rename to the Requirements dialog. It is related to
those requirements that the Project Examples engine can't solve.
Simplify project examples update process
-----------------------------------------
Key: JBIDE-5700
URL:
https://jira.jboss.org/jira/browse/JBIDE-5700
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: project-examples
Affects Versions: 3.1.0.CR2
Reporter: Brian Fitzpatrick
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.1.0.CR2, 3.2.next
Attachments: pexamples1.png, pexamples2.png, pexamples3.png
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Currently for the project examples, the user must either create a runtime instance in the
tooling that maps to the expected runtime name from the project example or go in and
update the references in the Quick Fix dialog by hand in the project properties.
Is there any way to make this process simpler? For example, could we match on the type of
server instead of the name?
How feasible is this type of change?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira