I have not, and it may just be my ignorance of groovy's build infrastructure. It works fine with 1.4, before the profiles were introduced.
I was only working against 1.6-snapshot because I was working on a patch for accumulo. I normally work off of 1.4 for application code but realized that there was this problem when I upgraded the Groovy Grab Annotation to 1.6 because I already had that version running. It isn't a high priority or anything ... but will come into play when I upgrade my application to 1.5. --Kevin On Thu, Feb 28, 2013 at 11:27 AM, John Vines <[email protected]> wrote: > Have you done this before with any other variable maven items? I wonder if > this is possibly a bug with Groovy's Grab. > > On a side note, is there any particular reason you're using the trunk > release? We just branched 1.5, so the code bases are almost identical, with > the caveat that 1.5 is going to be released soon. > > > On Thu, Feb 28, 2013 at 9:23 AM, Kevin Faro <[email protected]> wrote: > > > I am trying to write a groovy script to ingest some data into accumulo > > using: > > > > @Grapes([@Grab(group='org.apache.accumulo', module='accumulo-core', > > version='1.6.0-SNAPSHOT')]) > > > > and it tries to resolve the slf4j dependency as: > > > > > > > http://download.java.net/maven/2/org/slf4j/slf4j-log4j12/${slf4j.version}/slf4j-log4j12-${slf4j.version}.jar > > > > It looks like the profiles in the accumulo/pom.xml are being ignored, so > > the version is never set ... any way to override this? > > > > Any ideas? > > > > --Kevin > > >
