I always add try to add the version after having a bad experience with the gradle dependency
Some times while upgrading some of the api's get deperecated and you end up on the wrong side. So better be safe than regret. Atleast this gives you full control on what response you can expect from a call. Regards, Jav Angelo Getting started with Java Swing - http://bit.ly/1RQcam7 On Thu, Jun 2, 2016 at 1:33 PM, Greg Thomas <greg.d.tho...@gmail.com> wrote: > Is there a correct syntax to use the BOM dependency with gradle? > > I've currently got the following ... > > compile group: 'org.apache.logging.log4j,' name: 'log4j-bom', version: > '2.6' > compile group: 'org.apache.logging.log4j', name: 'log4j-api' > compile group: 'org.apache.logging.log4j', name: 'log4j-core' > > But dependency resolution fails ... > > C:\Greg\test>gradlew dependencies > :dependencies > > ------------------------------------------------------------ > Root project > ------------------------------------------------------------ > > archives - Configuration for archive artifacts. > No dependencies > > compile - Dependencies for source set 'main'. > +--- org.apache.logging.log4j:log4j-bom:2.6 > +--- org.apache.logging.log4j:log4j-api: FAILED > +--- org.apache.logging.log4j:log4j-core: FAILED > ... > > What's the right syntax, if it's even possible? > > Thanks, > > Greg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > >
