tag:blogger.com,1999:blog-3237724005744642470.post72819880331784158..comments2020-07-30T12:43:10.297+01:00Comments on Captain Debug's Blog: Deploying Applications to Weblogic Using MavenRoger Hugheshttp://www.blogger.com/profile/07042290171112551665[email protected]Blogger2125tag:blogger.com,1999:blog-3237724005744642470.post-71559177289218682402011-09-21T10:36:05.986+01:002011-09-21T10:36:05.986+01:00Thanks for the comment and a good observation. You...Thanks for the comment and a good observation. You should remember that these are only samples and so, yes, I have hard coded the classpath, URL and other bits and pieces. In a real world project, whatever the solution chosen, I’d make use of a Maven profile, so that the hard coded values were replaced by the usual ${variable} notation, and/or ensure that all developer machines use a common configuration. The use of Ant is just personal preference (and I’m not a big fan of Ant) - if Oracle did organise some public Maven repositories, I’d use them, and the weblogic-maven-plugin in a flash.Roger Hugheshttps://www.blogger.com/profile/07042290171112551665[email protected]tag:blogger.com,1999:blog-3237724005744642470.post-71199361760625376212011-09-21T10:08:51.534+01:002011-09-21T10:08:51.534+01:00Thanks for the writeup! When you say the ant-way ...Thanks for the writeup!<br /><br />When you say the ant-way is &quot;less hassle&quot; though, it looks to me its primarily because you use that hardcoded classpath /Users/Roger/...<br /><br />Much worse, imho, since it means the pom.xml only works on your machine, and needs to be modified by every other programmer working in the project -- just the kind of awkward stuff mvn was designed to avoid.Anonymous[email protected]