Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Java Build Systems - a sad state of affairs

grok-code.com

Post reply on HN
Print view View original

41–45 of 45 posts

Re: Java Build Systems - a sad state of affairs

#41

Post by hello_moto »

karthikm wrote: post #27

What's mentioned as drawbacks are powerful features Maven provides to handle the project/plugin dependencies better. It takes a bit of understanding and experience to appreciate these features and to use them effectively. I've used Maven the right way in one of the biggest enterprise environments as well as a couple of startups and the results have been nothing short of phenomenal. Am still baffled by how most of the…

I used to whine about Maven, but then I realized that it suck because 2 factors:

- I did not take my time to learn it

- Senior employees did stuff in a non-Maven way.

Re: Java Build Systems - a sad state of affairs

#43

Post by lsd5you »

lsd5you wrote: post #8

Actually I have my own contribution to this space: http://ebuild.origo.ethz.ch/wiki/ebuild Although unfortunately the documentation is not ready yet, it is quite capable and is designed to solve what I perceive to be critical short comings of maven.

I've added some documentation. Far from complete, but it should shed some light on the situation for the curious.

Re: Java Build Systems - a sad state of affairs

#44

Post by tonetheman »

karthikm wrote: post #27

What's mentioned as drawbacks are powerful features Maven provides to handle the project/plugin dependencies better. It takes a bit of understanding and experience to appreciate these features and to use them effectively. I've used Maven the right way in one of the biggest enterprise environments as well as a couple of startups and the results have been nothing short of phenomenal. Am still baffled by how most of the…

I have had to work with maven and integrating it to an existing project is insanely hard if not impossible. On other projects I worked with Maven it spends more time updating itself than doing any useful work.

Re: Java Build Systems - a sad state of affairs

#45

Post by jsvaughan »

hello_moto wrote: post #40
papaf wrote: post #37

Earlier quoted context omitted.

It may not be related to the build system but just look at logging in java versus logging in Ruby. I was in a meeting once where I was the lone "cowboy" Perl programmer amongst amongst a group of Java dudes. One Java dude told another off for doing logging wrong. He said "I have a book on this logging package if you want to borrow it." None of them knew why I laughed, but to me, logging was just a fancy print stateme…

The thing about Java developers is that some of them are probably seasoned developers. They've been through many projects with scars everywhere. From each project, they learned something new (not necessarily the best way, but albeit something new). Combine that with the fact that there are people out there who have been through these situations and wrote "best practices". When they build the next system, they will tr…

yes nothing beats inexperience
Post reply on HN