Ah, I forgot to mention the parent pom. Glad you spotted it. On Tue, Jul 24, 2018 at 10:32 PM Joseph Glanville <jos...@meteor.com> wrote:
> Hi Gian, > > I was able to publish our own artifacts by creating a new oss-parent pom > pointing to our Maven repository and updating the Druid root pom to point > to it. > It was non-obvious where the release plugin was configured until I spotted > the parent reference. > > Joseph. > > On Tue, Jul 24, 2018 at 9:09 AM, Gian Merlino <g...@apache.org> wrote: > > > Hi Joseph, > > > > For official releases we just do mvn release:prepare release:perform. The > > poms encode everything that has to happen, including sources jars, > javadocs > > jars, signing everything, and pushing it up to Maven Central. You might > be > > able to modify them to push to a different repo. > > > > On Mon, Jul 23, 2018 at 5:06 PM Joseph Glanville <jos...@meteor.com> > > wrote: > > > > > Hi, > > > > > > Is the release process for publishing Maven artifacts documented > > somewhere? > > > We have been building tar archives with `mvn package` successfully but > we > > > would like to publish our own Maven artifacts also, including > `-sources` > > > JARs so we can add them as dependencies to projects outside of the > Druid > > > source tree. > > > > > > Joseph. > > > > > >
