Another addition here: After looking at it again I'm curious if we really need to push our snapshots to http://oss.sonatype.org/content/repositories/ops4j-snapshots/ instead of https://oss.sonatype.org/content/repositories/snapshots/ where all snapshots of all other sonatype using projects are located. Just thinking that this would make things for most of our project a little bit easier since a) if they use sonatype oss-parent they'll automatically have access to our snapshots and b) they need one snapshot repo less in they definitions.
WDYT? Kind regards, Andreas On Wed, May 16, 2012 at 7:51 AM, Andreas Pieber <anpie...@gmail.com> wrote: > TBH I think this is nothing we could really fix in the root. This one > is rather a conceptional problem someone cooked up. We should rather > deploy EVERYTHING by default in the release profile. There could be > (optionally) additional profiles which e.g. skip the itests, but this > shouldn't be the default. > > 0.02€ > > Kind regards, > Andreas > > On Tue, May 15, 2012 at 8:16 PM, Harald Wellmann > <hwellmann...@googlemail.com> wrote: >> One more thing: >> >> We need to take care of extra stuff in special profiles. >> >> E.g. Pax Exam has an itest profile for integration tests which should not be >> pushed to Maven Central, But that means that the POM versions of the itest >> projects don't get updated automatically by the Maven Release plugin and >> need to be bumped manually (which I did for 2.5.0-SNAPSHOT on the master >> branch). >> >> I'm not sure if this is a point to be standardized, but at least we should >> be aware of it and mention it in the release process. >> >> Cheers, >> >> Harald >> >> _______________________________________________ >> general mailing list >> general@lists.ops4j.org >> http://lists.ops4j.org/mailman/listinfo/general _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
