first of all, it never really worked. Many of the editing elements in the 
advanced tabs didn't do anything or did the wrong thing.  Some even displayed 
wrong content AFAIK. Personally it leads me to believe it wasn't actually being 
by many (as the bug reports were not filed for it)

Then the flat 1 on 1 mapping of xml elements to form field didn't add much 
additional value. And there were navigational problems as well eg. when you 
want to see what goals got executed for a particular plugin in a particular 
execution, you had the select the plugin in the list, in the details select the 
execution and then you would see the goals. If it were in a plugin, it's one 
more master/detai level added .. If you were to change the configuration of the 
plugin, you were out of luck anyway and had to switch to xml editor for it..

We've kept what is being used by the majority of users frequently and tried to 
improve it. The Add dependency/plugin/parent dialog, the dependencies tab, xml 
editing, navigation..

Regards

Milos


On Jun 23, 2011, at 8:45 PM, Clark, Shawn wrote:

> Where has it all gone???
>  
> I was very upset to see that the POM editor has lost the ability to view the 
> different elements of the pom.xml. At first I thought it was just because the 
> “advanced tabs” option wasn’t enabled but after a few minutes of not finding 
> the option I realized that the functionality has just been removed. I was 
> really looking forward to the tighter integration of m2e within the Indigo 
> release and so far I am liking everything other than the POM editor changes.
>  
> There was another post to the list with a response that the other tabs were 
> for “obscure pom.xml elements”. I thought that plugins and reporting are a 
> primary feature of maven?!? How about the “Repositories” tab, not being able 
> to conveniently enter the release and snapshot repositories seems essential 
> to releasing a maven project. Then there are profiles which some development 
> shops use fairly consistently.
>  
> Please let the community know the reasoning behind the removal of these 
> features as they were allowing for the creation of the pom.xml to be quick 
> and efficient. Now I can’t say the same.
>  
> --
> Shawn Clark
>  
> _______________________________________________
> m2e-users mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/m2e-users

_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users

Reply via email to