I can't think of any reason to not use ${project.version}. There
are plenty of projects that do it that way, e.g.
https://github.com/jersey/jersey/blob/master/bom/pom.xml. The
linked issue, and the source netty issue also don't give a reason
for that 'rule'.On Thu, Jun 8, 2017, at 14:35, Joakim Erdfelt wrote: > > > Joakim Erdfelt / [email protected] > > On Thu, Jun 8, 2017 at 12:03 AM, Greg Wilkins > <[email protected]> wrote:>> Olivier, >> >> It is listed in the parent pom as a module, but I'm guessing it was >> excluded from the release because it contained SNAPSHOT dependencies >> that were not updated?>> >> I've modified the jetty-bom/pom.xml to use ${project.version} for all >> it's dependencies.> > You can't do that with a bom apparently (using ${project.version}) > See https://github.com/eclipse/jetty.project/issues/1527 > > - Joakim > _________________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or > unsubscribe from this list, visit> > https://dev.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
