From the same tool...



  • From the same tool who said But it's where I'm working... this just happened.

    Like most folks, we have ten-ish sub projects in our project. Most sub projects are on java 1.5. One person is working on something that requires java 1.6. One person decided to try java 1.7.

    Then they all committed everything. Now our build tree is littered with ant files containing condition/fail checks for java compiler versions. Since most of the system is on java 1.5, we can no longer build the entire project because the tools who are using the newer compilers are refusing to do the work of making sure everything ELSE builds correctly and they also put THEIR build projects first in the target list, so when their project build fails, the whole thing stops.

    My boss went nuts. We are now enjoying an email storm as to who is going to get to migrate everything to 1.6/7 (including the do-we-want-to-be-early-adopter wars).

    I temporarily moved their builds to the end of the target list (e.g.: build all the 1.5 stuff, then the 1.6 stuff, then the 1.7 stuff). This way, everyone elses stuff will build and only the folks who are working on the projects with the newer compiler requirements (who have the newer compilers) will be able to build those projects.

    Wheeee!

     

     



  • Wheeee!

    (If I ever apply for a job on your team, tell me so I can run away)



  • @Sutherlands said:

    Wheeee!

    (If I ever apply for a job on your team, tell me so I can run away)

    Why? So he can hog all the fun for himself?!  :)




  • Wheeee!

    But why are you still using Java 5 anyway? The migration from 5 to 6 is a non-event. (I hear 7 was released with some show-stoppers though. Tell the bleeding edge guy to go bleed.)



  • @Xyro said:


    Wheeee!

    But why are you still using Java 5 anyway? The migration from 5 to 6 is a non-event. (I hear 7 was released with some show-stoppers though. Tell the bleeding edge guy to go bleed.)

     

    If it's like where I work, corporate bureaucracy.

     



  • @Xyro said:


    Wheeee!

    But why are you still using Java 5 anyway? The migration from 5 to 6 is a non-event. (I hear 7 was released with some show-stoppers though. Tell the bleeding edge guy to go bleed.)

    Probably for the same reason that blakey's stuck on .NET 3.5. As for Java 7... how Oracle managed to break for() loops is just mind-boggling. It's as if they don't test their software before release OH WAIT.

    snoofle, if the 1.6 guy really requires it, that's probably a sign you should upgrade all your projects. As for the guy using 1.7, give him a kick in the nuts for being a jerk.



  • @snoofle said:

    who is going to get to migrate everything to 1.6/7 (including the do-we-want-to-be-early-adopter wars).

     Simple, lock the people who choose break the build system in a room, no food (you have to provide water), no pay, until everything works.

     <at least that is what I am allowed to do in my warped dreams...>



  • @The_Assimilator said:

    Probably for the same reason that blakey's stuck on .NET 3.5.

    Because .net 4 doesn't ship on the default Amazon AWS Windows Server 2008 image? That's a stupid reason to not upgrade Java.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.