#8940: Maven functionality is a mess!

What happened to the Maven functionality in 8940??? Why is the tool bar in the Maven pane missing a bunch of buttons? Who's the genius that decided that it will be easier to configure Maven through the common Settings and Run Configurations only? Why does IDEA now force a Make before running any Maven target? It saves the task in the Run Configurations, and then re-saves it each time you run the target. So, if I uncheck the "Make before running" box in the configuration, the change gets ignored the next time I try to run the target, and Idea tries to compile and make the whole project internally before running Maven. Why did you guys break something that worked just fine? Seems like 8940 is raw and unstable - just when I thought that EAP releases were becoming usable for serious project work - not just for hackers with too much time on their hands... ;)

Wasted my time with 8940.

6 comments
Comment actions Permalink

Maven support seems to be completely broken for me: http://jetbrains.net/jira/browse/IDEA-20280

0
Comment actions Permalink

The problem with resetting the 'Make before launch' option will be fixed in the next eap. As a temporary workaround you may edit default settings for Maven Run Configuration Type.

As for the Run Configurations, they have their own settings and are not affected by general settings. I hope this inconsistency will be solved soon. For now you can configure Maven Home using the Edit Configurations action (and using Edit Configurations->Edit Defaults, if you want this settings to be applied to all run configurations)

Is there any necessity to return Edit Maven Settings/Edit Default Maven Settings back to the tool window's panel?

Thanks,
Anton Makeev

0
Comment actions Permalink

Placing the build configurations into the run/debug mechanism really is not the right place to have them.
You usually go between a build operation and a run/debug operation repeating that sequence over and over as code is developed.

With the new scheme, you have to reselect the desired run/debug each time because the build configuration replaces the last run/debug. Likewise after a run you would have to reselect the build configuration.

Toolbar space may be getting tight but having a separate control of build things vs run things would help a lot. Or perhaps placing the custom build configurations in the maven window, adding them to the existing goals, perhaps with decorated icons. http://www.jetbrains.net/jira/browse/IDEA-20303

Edited by: Dick Lieber on Oct 29, 2008 8:12 AM

0
Comment actions Permalink

I think it was very appropriate - and convenient - to have the Maven Settings buttons in the Maven tool bar. It never bothered me that the toolbar was getting too long, the slide-out behavior was just fine. At some point you did a good thing by re-arranging the buttons to make sure that the Refresh button was always in sight - since that button is most often used.

Run/Debug Configurations and Maven Builds - to me - are not the same thing. Although, it may be convenient to be able to save the Maven build configurations in the Run Configurations, but there should be a distinction between building with Maven, and building w/o it. In fact, I don't see the point at all of doing the Idea Make before running Maven to build the project. Well, perhaps, in some cases, someone might want to do it, but, generally, when I do a Maven build, I want to by-pass the Idea compilation and buld.

Thanks.

0
Comment actions Permalink

I see, the functionality will be returned in the next eap.

Thanks for the feedback,
Anton Makeev

0
Comment actions Permalink

Regarding the Run/Debug configuration I really like Eclipse' approach: Just
click the arrow right to the Run/Debug button to choose the configuration to
start running/debugging.

0

Please sign in to leave a comment.