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 complicated to be affected 
drastically. We could always 'pin' a version for the odd plugins that 
were affected. Thus, I wanted to give that a go. This works well from 
the CLI (typically what I use for build).

The intent for tweaking the poms were primarily to:
- reduce the size of pom by discarding the optional/default settings
- remove redundant settings in multiple pom
- add some inline docu to stop one running away from a pom.xml
- contribute a little in making maven not 'download the internet'

Too bad the IDEs are not co-operating! Thanks Kris/David for raising 
this. I am going to add versions for all the plugins and extensions 
tonight. Unstable pom.xml is the last thing we want (even if that means 
redundant/optional settings make their way into the poms).

Cheers, Indrajit

On 24/10/09 7:22 AM, Kris Nuttycombe wrote:
> 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
> <>  wrote:
>> Folks,
>> Any idea why NetBeans doesn't like the new Lift pom structure?
>> Thanks,
>> David
>> --
>> Lift, the simply functional web framework
>> Beginning Scala
>> Follow me:
>> Surf the harmonics
> >

You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to