News for hackers. Stuff that matters.
Re:Maven is broken by design by dschiptsov on Saturday October 05, 2013 @03:55AM (#6499925)
Just maven or the whole Java philosophy of avoiding any understanding/researching/thinking before beginning to pile it up inside an IDE?)
Re:Maven is broken by design by GlennS on Saturday October 05, 2013 @11:02AM (#6500840)
Running joke in my office: whenever you waste a day on some trivial task because you had to edit some stupid XML config file, you lose a sanity point.

I have learned the hard way to read some of the source code of any external library or tool, no matter how widely accepted, in case the person who wrote it didn't attend the class on not using global variables or depending on undocumented internals of the JVM (I'm looking at you Log4j 2). Or in case they were just plain bonkers, like everyone who was involved in writing Spring.

Re:Maven is broken by design by bun-neh on Saturday October 05, 2013 @09:15AM (#6500588)
I wouldn't call it the "Java" philosophy. Rather, I would call it the "wet behind the ears" philosophy. It just so happens that they correlate because of the way people are trained.
Re:Maven is broken by design by brown9-2 on Saturday October 05, 2013 @11:35AM (#6500963)
To suggest that this is an effect of the language rather than various teams of different people building different tools at various points in times seems silly.

What other language hasn't had multiple build solutions that were each "the one solution" at some point in time, only to be supplanted later?

How many build solutions are there for C++, or Ruby?

Re:Maven is broken by design by cuillevel3 on Saturday October 05, 2013 @07:52AM (#6500404)
I don't think there is an actual maven IDE. You normally use it from the command line, since it's integration into IDEs is serverly (eclipse...) lacking.
Re:Maven is broken by design by chii on Saturday October 05, 2013 @09:00AM (#6500544)
If you use Intellij IDEA, their maven integration is top notch. light years ahead of eclipse.
Re:Maven is broken by design by chinpokomon on Saturday October 05, 2013 @09:49PM (#6502768)
I concur.

I'm the only developer in my shop using IntelliJ. Everyone else uses NetBeans. Whenever someone asks me how to setup NetBeans to handle builds as easily as I do, I have to shrug. Simple things, like switching to offline mode or turning off tests is a chore for NetBeans, but it is just a simple button click for me. If I want to target a specific build profile, I check a check box.

As I'm the one who maintains the build, configuring pom.xml files and setting up modules, I can see how it can become difficult for someone who doesn't have the experience I do. OTOH, I've yet to find a problem that stumps me when I'm doing things the Maven way, and I rather enjoy the flexibility and power it provides me. Once I've got the basics in place, maintaining the system is almost trivial.

Re:Maven is broken by design by smrtinsert on Saturday October 05, 2013 @10:51AM (#6500803)
I don't use maven for my builds these days but that's completely wrong. configuring deps is painless as is adding plugins. I've used it to build maven projs as well as osgi projs.
Re:Maven is broken by design by liveoneggs on Saturday October 05, 2013 @01:51PM (#6501408)
netbeans can use maven out of the box