From: John M. <joh...@gm...> - 2014-03-13 21:17:39
|
Hi Cyrus, To ensure the local version is used, don’t include the ebi snapshot repository in the configuration of downstream project. Repositories should be defined on a per-project database. To change the version in the XML you can use - http://mojo.codehaus.org/versions-maven-plugin/, no additional configuration needed. I would recommend just removing the repository though as it keeps things cleanr. > mvn versions:set -DnewVersion=1.5.6-LOCAL The versions are stored separately as some project increment the module versions independently. This is a lot more work, and makes things very confusing but basically if there are no changes to a module since the last release the existing version can be used. You can do this locally, if for example I made a change to fix the fingerprints, I could change just that version and use that in the downstream project. > mvn versions:set -DnewVersion=1.5.6-withfpfix -DartifactId=cdk-version J On 13 Mar 2014, at 21:00, Cyrus Harmon <ch...@bo...> wrote: > > Following up on this from long ago, it turns out JAVA_HOME wasn’t properly set. I think that fixed things. > > But now on to my next issue with the new source tree… I’ve been installing a build from the new version which gets installed as 1.5.6-SNAPSHOT. This is fine until some time passes and I have some other maven-equipped software that triggers a resolution (is this the right term?) of the maven dependencies and it goes and looks at EBI for a newer version of the snapshot. Not necessarily what i want. How do others deal with this problem? Just using the version from EBI? I suppose I should figure out how to make the other maven-equipped piece of software work in offline mode, but that isn’t necessarily the best solution. > > One option I’ve considered is renaming the version to something like 1.5.6-LOCAL, but that brings me to my next problem, which is that it seems that the version is hardcoded in each of the pom.xml files. find . -name pom.xml | xargs grep -i 1.5.6-snapshot | wc -l tells me that there are 70 files with the version hardcoded. Do we fire off some sort of sed/perl script to change this automatically when a new release is called for? Surely there must be a way to store this information once and refer to that rather than sprinkling it throughout pom files scattered across the tree. > > thanks, > > Cyrus > > On Feb 26, 2014, at 12:56 PM, John May <joh...@gm...> wrote: > >> Which JDK are you using? According to docs this is correct for the default location. >> >> http://maven.apache.org/general.html#tools-jar-dependency >> >> J >> >> On 26 Feb 2014, at 20:52, John May <joh...@gm...> wrote: >> >>> It’s looking for the JDK tools dependency - this is a system dependency. If java is installed correctly it is located - >>> >>> ${java.home}/../lib/tools.jar >>> >>> try this from the command line, what do you get? >>> >>> ls $JAVA_HOME/lib >> >> ------------------------------------------------------------------------------ >> Flow-based real-time traffic analytics software. Cisco certified tool. >> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >> Customize your own dashboards, set traffic alerts and generate reports. >> Network behavioral analysis & security monitoring. All-in-one tool. >> http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk_______________________________________________ >> Cdk-devel mailing list >> Cdk...@li... >> https://lists.sourceforge.net/lists/listinfo/cdk-devel > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech_______________________________________________ > Cdk-devel mailing list > Cdk...@li... > https://lists.sourceforge.net/lists/listinfo/cdk-devel |