Wow, I agree. I just let my Mac Mini do that update this morning. What if the new Ant and Maven aren't 100% backwards compatible? Suddenly builds could start failing and no one will know why. Fortunately, I'm not doing much Java work on that machine at the moment.
Ulf Dittmer wrote:I've never used the built-in versions of Ant and Maven, instead preferring to install up-to-date versions myself. Do the built-in ones have any advantage other than not having to install them?
I updated my JDK, Safari and iTunes yesterday. The surprising thing was it asked be for a reboot. I was wondering why. Does it mean some OS level updates?
The last time I remember being asked for a reboot after an update was after an OS security patch or something.
Greg Charles wrote:Wow, I agree. I just let my Mac Mini do that update this morning. What if the new Ant and Maven aren't 100% backwards compatible? Suddenly builds could start failing and no one will know why. Fortunately, I'm not doing much Java work on that machine at the moment.
Sorry for just registering and then replying to a slightly old thread but after the week I've had I felt compelled enough to do so. Actually it looks like this could be a very useful place so I'm glad I stumbled across it!
So, yes, Maven 3 is indeed not 100% compatible and not only could it break builds but it did
I'd been doing some minor issue fixing on a project on my work laptop. Changing company name references following a buyout and the like but I'd been doing all of that in Netbeans. One night last week I thought I ought to update the copy on my home machine so I pulled the changes, dropped to the command line and off I went. Oh man! This is a project with about a dozen or so modules and it failed on the first one. This was odd!
Due to some badly formed POMs in the project (I inherited this project - approx. 500,000 lines of code) the local repository must be offline when building or hibernate and a bunch of other stuff will update and break. Yeah, yeah, I need to fix that but timescales are too tight right now.
Long story short I had to put the repo online due to the maven update, let it update itself, fix a few things, rinse and repeat. Two days later I have something that builds again. What a pain!! This has tought me that I need to bypass Apples version of maven in future.
Maven 3 no longer support maven 1 repos via the legacy tag. That's probably fair enough but this project was dormant for two years so there was some of that in there. Having said that, I removed the repo from the pom and it still built so I don't really know what it was using from the legacy repo! Re-reading that, yep, it's going to be cached in my local copy so that'll probably break when someone new comes along
An odd one was that the webstart JNLP plugin v 1.0-alpha-1 that had always worked suddenly started sayingit couldn't find the inline goal. Very odd. Thankfully that was easy to upgrade to beta 1 with no knock on issues.
End result is that I have a project that is slightly upgraded in certain areas which is good but sadly still needs to build in offline mode or hibernate breaks. It really, really would have been nice to have known that maven was going to update in that Java update though. I could have done without these issues at this time (trying to get a release out!)
Anyway, be warned!
I'm off to browse the forums. They look interesting