Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] Search for lifecycle mapping as part of import / create workflow

Thanks for reviewing this work.
Let's discuss that during Scrum.
Some notes embedded.

On 2011-02-28, at 5:44 AM, Milos Kleint wrote:

Hello,

I'd like to get some discussion and feedback on this issue:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=335701

Igor did a prototype in current HEAD. I've played with it today and here's my comments/ideas. 

1. analyzing the POMs takes too long. For a wizard that is. I've had like 100 of projects imported at once and I had to wait a significant amount of time. I'm not saying it's a show stopper for the feature but it's a significant user annoyance point. 
Would it be acceptable to have a progress bar at the bottom of the wizard that would allow the user to cancel this verification and just move on?

2. I was surprised that the discovery server was not contacted automatically on the second panel and I had to click the "search markertplace" button. what is the expected user interaction here? is there anything to do without the results from the markertplace?
The idea here was that the user may simply decide to not look for any resolution. There was also a concern of performance wrt contacting the m2e marketplace automatically.

3. is the discovery wizard panel considered optional in the wizard?
Not sure the one you are talking about. Any screenshot?

to the ui panel itself
a. I've this idea that we could reverse the displayed tree (currently it's project at the top with mappings below)
If we display the errors (or plain decision points) at the top of the tree structure and projects where the problem occurs below it, we have less items for the user to go through and ideally the user could decide on one problem across projects in one go (eg. decide which war plugin integration to use or to install a plugin connector for a code generating maven plugin)
I think showing the packaging type on top could be good, but I think that for each plugin execution, it is too contextual and we need the level of the project. 
The other thing about this wizard is that we should hide the things that say "execution irrelevant".

b. it's still unclear to me what are the actions and decisions user is supposed to take in the panel.
Pick and chose resolutions that are asosciated. However putting myself into the shoes of someone that does not know what is going on I can imagine this to not be easy to deal with or figure what is going on.


Regards

Milos

_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev


Back to the top