[jira] [Comment Edited] (CASSANDRA-7128) Upgrade NBHM

["Dave Brosius (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990274#comment-13990274 ] 

Dave Brosius edited comment on CASSANDRA-7128 at 5/6/14 4:59 AM:
-----------------------------------------------------------------

This patch converts high-scale-lib.jar to one fetched with a maven groupId of com.boundary.high-scale-lib

Unfortunately this version of the jar is not available on maven central, but only on http://maven.boundary.com/artifactory/repo

What this means if people now try to build from the pom it will fail. 

try:

mvn -f ~/.m2/repository/org/apache/cassandra/cassandra-all/2.1.0-beta2-SNAPSHOT/cassandra-all-2.1.0-beta2-SNAPSHOT.pom dependency:tree

to see the problem.

The solution is to either

1) add this repo to the published pom
    or
2) have users who want to build from the pom add the url to their settings.xml file

The first one is easier for users, but is discouraged, the second one is more complicated for users, unless they understand what's going on.

If we do 2) we should at least document somewhere what needs doing.

re-opening, just so we can choose one way or another.


----------

of course, really ideally is just to get the boundary folks to just publish to maven central like every other fool on the planet.


was (Author: dbrosius):
This patch converts high-scale-lib.jar to one fetched with a maven groupId of com.boundary.high-scale-lib

Unfortunately this version of the jar is not available on maven central, but only on http://maven.boundary.com/artifactory/repo

What this means if people now try to build from the pom it will fail. 

try:

mvn -f ~/.m2/repository/org/apache/cassandra/cassandra-all/2.1.0-beta2-SNAPSHOT/cassandra-all-2.1.0-beta2-SNAPSHOT.pom dependency:tree

to see the problem.

The solution is to either

1) add this repo to the published pom
    or
2) have users who want to build from the pom add the url to their settings.xml file

The first one is easier for users, but is discouraged, the second one is more complicated for users, unless they understand what's going on.

If we do 2) we should at least document somewhere what needs doing.

re-opening, just so we can choose one way or another.

> Upgrade NBHM
> ------------
>
>                 Key: CASSANDRA-7128
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7128
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: T Jake Luciani
>            Assignee: T Jake Luciani
>            Priority: Trivial
>              Labels: performance
>             Fix For: 2.1 rc1
>
>
> Upgrade NBHM to use the Boundary maintained version



--
This message was sent by Atlassian JIRA
(v6.2#6252)