Thanks for your efforts. I went ahead and specified 1.5.6-SNAPSHOT and it
seems one jar is missing:
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 29.525s
[INFO] Finished at: Sun Mar 09 10:19:29 EDT 2014
[INFO] Final Memory: 6M/81M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal on project cdkdescui: Could not resolve
dependencies for project net.rguha:cdkdescui:jar:1.4.0: Could not find
artifact uk.ac.ebi.beam:beam-core:jar:0.5 in java.net (
http://download.java.net/maven/2) -> [Help 1]
On Sun, Mar 9, 2014 at 7:53 AM, John May <[email protected]> wrote:
> Okay,
>
> The ebi-repo metadata was being updated on deployment but the
> ebi-repo-snapshots was not. Reading around a bit it looks like LATEST is
> really only for plugins and there are other ways to get the newest version,
> see -
> http://stackoverflow.com/questions/30571/how-do-i-tell-maven-to-use-the-latest-version-of-a-dependency
> .
>
> I'll try one more thing to see if LATEST works but otherwise I think you
> can use: '[1.5.0,1.6.0)' or an explicit version such as '1.5.6-SNAPSHOT'.
>
> I've just wiped the existing snapshots which should avoid the first
> problem of missing release. The latest snapshot build is deploying now.
>
> J
>
> On 8 Mar 2014, at 23:31, Rajarshi Guha <[email protected]> wrote:
>
> Hmm, doing mvn dependency:analyze gives me
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Total time: 5.229s
>
> [INFO] Finished at: Sat Mar 08 18:30:35 EST 2014
>
> [INFO] Final Memory: 7M/81M
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal on project cdkdescui: Could not resolve
> dependencies for project net.rguha:cdkdescui:jar:1.4.0: The following
> artifacts could not be resolved:
> org.openscience.cdk:cdk-fingerprint:jar:LATEST,
> org.openscience.cdk:cdk-qsarmolecular:jar:LATEST,
> org.openscience.cdk:cdk-signature:jar:LATEST: Could not find artifact
> org.openscience.cdk:cdk-fingerprint:jar:1.5.0-SNAPSHOT in java.net(
> http://download.java.net/maven/2) -> [Help 1]
>
> [ERROR]
>
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
>
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
>
>
> On Sat, Mar 8, 2014 at 5:03 PM, John May <[email protected]> wrote:
>
>> Yep - it pulls down the metadata.xml to inspect what is in the repo. I
>> messed up when I deployed the 1.5.0-SNAPSHOT and it is listed in the
>> metadata<
>> http://www.ebi.ac.uk/intact/maven/nexus/content/repositories/ebi-repo-snapshots/org/openscience/cdk/cdk-fingerprint/maven-metadata.xml>
>> but isn't actually in the folder<
>> http://www.ebi.ac.uk/intact/maven/nexus/content/repositories/ebi-repo-snapshots/org/openscience/cdk/cdk-fingerprint/>.
>> Also note the metadata list 1.5.0 as the latest.
>>
>> I haven't worked out how to force the metadata to update... or if it's even
>> possible. What do you get for
>>
>> mvn dependency:analyze
>>
>> or is it still failing to build?
>>
>> J
>>
>> On 8 Mar 2014, at 21:32, Rajarshi Guha <[email protected]<mailto:
>> [email protected]>> wrote:
>>
>> Looks it works with LATEST as the version. However, when I refershed my
>> local repo it's pulling down
>>
>> 1.5.0-SNAPSHOT
>>
>> but then says that
>>
>>
>> [WARNING] The POM for
>> org.openscience.cdk:cdk-fingerprint:jar:1.5.0-SNAPSHOT is missing, no
>> dependency information available
>>
>> Shouldn't it be retrieving 1.5.6-SNAPSHOT?
>>
>>
>>
>> On Sat, Mar 8, 2014 at 3:59 PM, John May <[email protected]<mailto:
>> [email protected]>> wrote:
>> Okay,
>>
>> You need to add
>>
>> <releases>
>> <enabled>false</enabled>
>> </releases>
>>
>> to the snapshot repo. I'll add that to the README. This could be
>> something I mess up last year by deploying a release to snapshots by
>> mistakes (I used to have perl scripts to do it :-)).
>>
>> With that added, mvn dependency:analyze shows that is picks up the 1.5.5
>> release. Failing that also make sure you're using Maven 3. I'm pretty sure
>> the RELEASE also worked pre v 3. Also no harm in turning of snapshots from
>> the release repo.
>>
>> <repository>
>> <id>ebi-repo</id>
>> <url>
>> http://www.ebi.ac.uk/intact/maven/nexus/content/repositories/ebi-repo/
>> </url>
>> <snapshots>
>> <enabled>false</enabled>
>> </snapshots>
>> </repository>
>> <repository>
>> <id>ebi-repo-snapshots</id>
>> <url>
>> http://www.ebi.ac.uk/intact/maven/nexus/content/repositories/ebi-repo-snapshots/
>> </url>
>> <releases>
>> <enabled>false</enabled>
>> </releases>
>> </repository>
>>
>> J
>>
>>
>>
>>
>> --
>> Rajarshi Guha | http://blog.rguha.net<http://blog.rguha.net/>
>> NIH Center for Advancing Translational Science
>>
>>
>
>
> --
> Rajarshi Guha | http://blog.rguha.net
> NIH Center for Advancing Translational Science
>
>
>
>
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries. Built-in WAN optimization and
> the
> freedom to use Git, Perforce or both. Make the move to Perforce.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Cdk-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/cdk-user
>
>
--
Rajarshi Guha | http://blog.rguha.net
NIH Center for Advancing Translational Science
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Cdk-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cdk-user
