Right, what is the process to get our artifacts into a public repo, or in this case, the apache public maven repo?
Also, I have a ticket to track this: https://issues.apache.org/jira/browse/DMAP-25 Finally, not sure if 1.0.0 is suitable for being published to the public. The only issue is that we have svn.apache.org as the default URL loader location. I already have this patched in 1.0.1, so if anything, that is what we publish. If anything, maybe we wait until the 1.1 release before we publish to the public??? I have no problem pushing out 1.0.1, but if we have to go thru another voting process, might as well save that effort for 1.1. Thoughts? ________________________________ From: Werner Keil <[email protected]> To: Bertrand Delacretaz <[email protected]> Cc: "[email protected]" <[email protected]> Sent: Friday, July 25, 2014 1:22 PM Subject: Re: Reza, you can tally the incubator PMC vote now Btw., seems none of the artifacts already released as 1.0.0 are in a Maven repo yet. Especially not here: http://repo.maven.apache.org/maven2/org/apache/ And I doubt even the Snapshot equivalent gets a deployment yet. For those artifacts that are officially released and approved, could they go into a maven repository, too? Werner On Fri, Jul 25, 2014 at 5:21 PM, Bertrand Delacretaz <[email protected] > wrote: > On Fri, Jul 25, 2014 at 3:53 PM, Reza <[email protected]> > wrote: > > ...moving forward the Java client will likely see less releases and > activity and the data will constantly evolve. That's why > > I'm thinking version in wise they will diverge greatly.... > > IMO having (even very) different version numbers between different > modules is not a problem. > > -Bertrand >
