1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 <2013> 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 <2013> 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Maven central and deprecating sourceforge maven repo |
From: | "Carcassi, Gabriele" <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Mon, 4 Mar 2013 13:58:28 +0000 |
Hi all, We have started publishing jca/caj/pvmanager in maven central: http://search.maven.org/#search|ga|1|g%3A%22org.epics%22 Which means: no need to configure a repository and we get an index (you can search). The same repository can also be used, as before, with apache ivy or to manually download the jars. Snapshots (dev builds) are being published at: https://oss.sonatype.org/content/repositories/snapshots/org/epics/ which automatically removes older versions. If you want to use them, you’ll have to explicitly add: <repositories> <repository> <id>sonatype-nexus-snapshots</id> <name>Sonatype Nexus Snapshots</name> <url>https://oss.sonatype.org/content/repositories/snapshots</url> <releases> <enabled>false</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> </repository> </repositories> But most of you will not. The groupId for the coordinates had to change to “org.epics” as per the maven best practices, but they allowed us to publish libraries under that groupId even though their package does not match. The plan would be to remove the old repository once we finished moving pvaccess/pvdata. If this conflicts with somebody else’s plan, please let me know. Thanks! Gabriele |