correct. Just create an infra jira for repo @ asf asking karma for incubator group to deploy to groupId org.apache.jclouds
2013/5/10 Adrian Cole <[email protected]>: > sounds like we need a jira to change the groupId and parent pom. following > that publish to apache snapshot repo instead of sonatype. Is this correct? > > -A > > > On Thu, May 9, 2013 at 4:04 PM, Olivier Lamy <[email protected]> wrote: > >> Hi, >> >> We must inherit the Apache parent pom. >> >> <parent> >> <groupId>org.apache</groupId> >> <artifactId>apache</artifactId> >> <version>13</version> >> </parent> >> >> Then have this section in your pom: >> <server> >> <id>apache.snapshots.https</id> >> <username></username> >> <password></password> >> </server> >> >> With username/password ASF valid ones. >> >> I think we have to change the groupId to something like org.apache.jclouds. >> Then load an infra issue for setup this groupId. >> >> The trouble is still the user/password store somewhere (doh you will >> think I'm security paranoid :-) ). >> But the Jenkins asf instance use a generic user/password so deploy to >> asf snapshot repo is easy. >> >> >> >> >> >> 2013/5/10 Adrian Cole <[email protected]>: >> > Hi, team. >> > >> > relating to: https://issues.apache.org/jira/browse/JCLOUDS-4 >> > >> > We are now publishing snapshots of 1.5.x, 1.6.x, and 1.7.x to sonatype >> from >> > our ASF repositories. I've tentatively set the build fail email to dev. >> > >> > Note that karaf build has been broke for some time, so this is hopefully >> > one of the first fixes we can address here! >> > >> > Cheers, >> > -A >> >> >> >> -- >> Olivier Lamy >> Ecetera: http://ecetera.com.au >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy
