Thanks David, that's pretty much the plan for me too.
If you come across something out of the way in the current build
configs, feel free to point them. It would be very helpful.
Cheers, Indrajit
On 25/10/09 12:26 AM, David Bernard wrote:
At work, I configure the root pom.xml with (increase
Plugin and extension versions are optional in Maven pom. Not providing
the version has a small advantage - it defaults to RELEASE and pulls up
the latest release automatically.
While it's possible that a plugin version would have backward incomplete
changes, in Lift we hardly do anything
Not setting version of plugin :
* create un-reproductible build (over time and developer configuration).
* using le last release is not always a good idea (eg : the last 2
version of maven-eclipse-plugin introduce regression).
/davidB
On 2009-10-24, Indrajit Raychaudhuri indraj...@gmail.com
Thanks davidB for pointing!
On 24/10/09 9:19 PM, David Bernard wrote:
Not setting version of plugin :
* create un-reproductible build (over time and developer configuration).
Just found this one too:
http://www.mail-archive.com/d...@maven.apache.org/msg82398.html. I had no
idea that the
At work, I configure the root pom.xml with (increase size of parent
pom.xml but define the rules for every children (idem for
dependencies))
pluginManagement
plugins
plugin
groupIdorg.scala-tools/groupId
artifactIdmaven-scala-plugin/artifactId
Just want to mention that m2eclipse also had a problem. Thanks for addressing
it.
-
Indrajit Raychaudhuriindraj...@gmail.com wrote:
Plugin and extension versions are optional in Maven pom. Not providing
the version has a small advantage - it defaults to
I ran into that -it's a missing version number in the root pom. Fixed
in my kjn-loc-wip branch if you just want to grab it from there.
On Fri, Oct 23, 2009 at 3:41 PM, David Pollak
feeder.of.the.be...@gmail.com wrote:
Folks,
Any idea why NetBeans doesn't like the new Lift pom structure?
