Re: [wildfly-dev] jboss-common-beans not synced to Maven Central

Hi Bob, inline... On 2015-12-18 15:31, Bob McWhirter wrote: > There’s quite a few WF dependencies not in central. > > There’s a variety of -jbossorg-1 dependencies we’ve had to fork for one > reason or another. jboss-common-beans is not a fork. > Plus a handful of dependencies that’ve never sync’d to central for one > reason or another. Could please somebody name the reason(s) relevant for jboss-common-beans? > Unfortunately you need to use repository.jboss.org > <http://repository.jboss.org>;. I do not think we have to. Either the sync can be turned on or we just copy the PropertiesValueResolver. -- P > *sigh* > > -Bob > > On Fri, Dec 18, 2015 at 8:02 AM, Peter Palaga <ppalaga(a)redhat.com > <mailto:ppalaga@redhat.com>> wrote: > > Hi Carlo, > > should not jboss-common-beans [1][2] be synced to Maven Central [3][4]? > > We use PropertiesValueResolver in Hawkular and try to be buildable with > Maven Central only. > > WildFly depends on it too [5] and because WF is synced to Central, all > its deps should be synced too. > > [1] https://github.com/jboss/jboss-common-beans/commits/master > [2] > http://origin-repository.jboss.org/nexus/content/repositories/public/org/... > > [3] > http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.jboss.common%22%20A... > [4] http://repo1.maven.org/maven2/org/jboss/common > > [5] https://github.com/wildfly/wildfly/blob/master/pojo/pom.xml#L58 > > Thanks, > > Peter > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/wildfly-dev > > _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev