I don’t think you have to be a maven expert, but you do have to be willing to give in to the maven way of doing things and go the whole hog. I currently have a development environment built on maven that I’m happy with, even though I started with no maven knowledge. It took a little while to get my head around maven, but in the end I like being able to quickly add a new library by adding a dependency to my pom.xml file, or even override a Wonder dependency in my local POM file. Granted, I haven’t yet had to deal with the maven deployment end of things, but I’m pretty confident that I’ll be able to jump that hurdle when the time comes. There are a couple of idiosyncrasies that I have to deal with, but overall, it is a very predictable environment.
I’m targeting my builds to run as true wars in a servlet container and it is extremely nice to be able to “mvn jetty:run-war” to see that it launches in a container. Mind you, I do my development in Eclipse with WOLips and I run with direct connect from within Eclipse. From my perspective, this gives me the best of both worlds: I can develop rapidly in WOLips and then deploy to Tomcat when I’m ready by just copying over a single war file. -- Faizel Dakri list...@dakri.com > On 2015-May-04, at 11:43 AM, Chuck Hill <ch...@gevityinc.com> wrote: > > I think that “Maven expert” is the key here. This is not a trivial thing to > setup correctly and maintain. It is trivial to setup and use incorrectly and > I have seen the pain resulting from that. To benefit from Maven you need to > really deeply understand Maven and its approach to dependancy management. > And you need to ensure that the whole team plays by The Maven Rules, even if > it makes more work short term and a bit of cheating does not seem that bad at > the moment. > > Chuck > > > > On 2015-05-04, 8:29 AM, "Jean-François Veillette" wrote: > > At my previous workplace, we did the switch to Maven. Luckily we had a real > maven expert to drive the move. > We started with around 50+ projects, all ant based, using the ‘standard’ > fluffy-bunny layout. He added pom.xml here and there, and everything just > started working with maven. We had choice to build/run with maven and/or ant > and it was (almost) transparent. The only exception was that if you decided > to use in maven, you had to change the class path to remove everything but > the maven and java dependencies (2 lines left), a simple .classpath that was > standard and could be copied from one project to the other. > The maven build was then integrated with Jenkins (CI) and SonarQube (so that > future ‘JF’ is happy with old ‘JF’, and all the team's work are standardized > a bit) with ease. > > From my experience, the team was happy with the Maven switch, none of us had > to become an expert (because we had one already). > Maven help a lot on easing the dependency management of your apps (a building > block only declare his direct dependency). Once you remove the noise of > declaring dependencies, you will be left with a clear graph of dependent > block. You will then have to tackle the real problem of incompatible > dependencies (A need B and Xv1, but B need Xv2). Maven will make the graph > simple and clear, it will try to provide helper but can’t really help much > after that. > > jfv > > >> On May 4, 2015, at 5:09 AM, David Avendasora <webobje...@avendasora.com >> <mailto:webobje...@avendasora.com>> wrote: >> >>> On May 1, 2015, at 6:35 PM, Chuck Hill <ch...@gevityinc.com >>> <mailto:ch...@gevityinc.com>> wrote: >>> >>> Maven seems like a better thought out and implemented solution. >> >> … >> >> Have you ever had one of those moments where things just seem so off-kilter >> you’re sure you’re having a dream, but no matter how many times you cry out >> for mommy you are left sitting there slowly realizing that there’s been some >> fundamental shift in the universe that you missed out on. (And your wife is >> slowly picking up her phone and dialing your therapist. Again.) >> >> ————————————————————————————— >> WebObjects - so easy that even Dave Avendasora can do it!™ >> ————————————————————————————— >> David Avendasora >> Senior Software Abuser >> Nekesto, Inc. > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/listfez%40dakri.com > > This email sent to list...@dakri.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
