Return-Path: X-Original-To: apmail-repository-archive@www.apache.org Delivered-To: apmail-repository-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B451310744 for ; Tue, 2 Dec 2014 12:31:25 +0000 (UTC) Received: (qmail 81025 invoked by uid 500); 2 Dec 2014 12:31:25 -0000 Delivered-To: apmail-repository-archive@apache.org Received: (qmail 80955 invoked by uid 500); 2 Dec 2014 12:31:25 -0000 Mailing-List: contact repository-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: repository@apache.org List-Id: Delivered-To: mailing list repository@apache.org Received: (qmail 80936 invoked by uid 99); 2 Dec 2014 12:31:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Dec 2014 12:31:25 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of daddywri@gmail.com designates 209.85.213.46 as permitted sender) Received: from [209.85.213.46] (HELO mail-yh0-f46.google.com) (209.85.213.46) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Dec 2014 12:31:20 +0000 Received: by mail-yh0-f46.google.com with SMTP id t59so5896137yho.33 for ; Tue, 02 Dec 2014 04:29:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rPPhFNFvk2j86GgnT1jqmYUR+bJu8PvV88VeDDx7p+g=; b=qcUBKM3AHV7TbXEpr2dut5dhfteOXFj0Qpkd19OiOCxxguxmQdtPtzjT5zggJIGmdU BX0xcVGzk0D5qbD7tK6KMyLmIosMrDTz0hp8GA4VmzQQBODQTVrg4t+awobmX/sYTpKu 8Jt8GCoTC2ukNcQhb5ls9gnFkBk51I5geo04UNkUqgzpLug3y+857akrtkTkdODgxUMw AN63S8ePRgADs5S4d3V3Wg4LHlI3aXx7lTQxOeug+62BaQjJczPhRBADHA2s+S9BqU23 1lVNIFjunN7RKy0YczAtu6IsUqBCDQXF0kbvUps6gpKDpsCM6K/6jX7IeB5at4VD88Zl mlrQ== MIME-Version: 1.0 X-Received: by 10.236.47.196 with SMTP id t44mr66125553yhb.59.1417523370038; Tue, 02 Dec 2014 04:29:30 -0800 (PST) Received: by 10.170.205.65 with HTTP; Tue, 2 Dec 2014 04:29:29 -0800 (PST) In-Reply-To: References: Date: Tue, 2 Dec 2014 07:29:29 -0500 Message-ID: Subject: Re: Forbidden Snapshot deployment on repository.apache.org From: Karl Wright To: Lukasz Lenart Cc: "repository@apache.org" , Maurizio Pillitu Content-Type: multipart/alternative; boundary=001a11c1dcdeee9d9105093ae0a8 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c1dcdeee9d9105093ae0a8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Lukasz, ManifoldCF has a rather complicated build infrastructure already, supporting both ant and maven builds, but we currently do not have a way of delivering our maven-built artifacts to the central repo upon release. We've been trying to get this to work using instructions such as this: http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env Your suggestion to use Jenkins would be fine but it does not appear to allow signing of artifacts, or use of an alternate profile (we have to use -P apache-mcf-release because otherwise we get a 1GB source file, for instance). How would you recommend that we proceed? Thanks, Karl On Tue, Dec 2, 2014 at 3:24 AM, Lukasz Lenart wrote: > Leave it to Jenkins (if you use it), your build should just perform > 'mvn install' and add Post-build Action: > > 'Deploy Artifacts to Maven Repository' with params: > - Repository URL =3D > https://repository.apache.org/content/repositories/snapshots > - Repository ID =3D apache.snapshots.https > - uncheck 'Assign unique versions to snapshots' > > > Regards > -- > =C5=81ukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > 2014-12-02 9:07 GMT+01:00 Maurizio Pillitu : > > Hi, > > > > I'm in the process of configuring Apache ManifoldCF to deploy/release > > artifacts (using Apache Maven) in repository.apache.org. > > > > Unfortunately I get the following exception when trying to run "mvn > deploy" > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy > (default-deploy) > > on project mcf-parent: Failed to deploy artifacts: Could not transfer > > artifact org.apache.manifoldcf:mcf-parent:pom:2.0-20141202.080304-1 > from/to > > apache.snapshots.https > > (https://repository.apache.org/content/repositories/snapshots): Access > > denied to: > > > https://repository.apache.org/content/repositories/snapshots/org/apache/m= anifoldcf/mcf-parent/2.0-SNAPSHOT/mcf-parent-2.0-20141202.080304-1.pom > , > > ReasonPhrase: Forbidden. > > > > Maven configuration can be found at > > http://svn.apache.org/repos/asf/manifoldcf/trunk/pom.xml > > > > Is there anything wrong with our configuration? > > > > Thanks, > > mao > --001a11c1dcdeee9d9105093ae0a8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Lukasz,

ManifoldCF has a ra= ther complicated build infrastructure already, supporting both ant and mave= n builds, but we currently do not have a way of delivering our maven-built = artifacts to the central repo upon release.=C2=A0 We've been trying to = get this to work using instructions such as this:

http://www.apac= he.org/dev/publishing-maven-artifacts.html#dev-env

Yo= ur suggestion to use Jenkins would be fine but it does not appear to allow = signing of artifacts, or use of an alternate profile (we have to use -P apa= che-mcf-release because otherwise we get a 1GB source file, for instance).<= br>
How would you recommend that we proceed?

Thanks,=
Karl



On Tue, Dec 2, 2014 at= 3:24 AM, Lukasz Lenart <lukaszlenart@apache.org> wrot= e:
Leave it to Jenkins (if you use it), y= our build should just perform
'mvn install' and add Post-build Action:

'Deploy Artifacts to Maven Repository' with params:
- Repository URL =3D https://repository.apache.org/content/= repositories/snapshots
- Repository ID =3D apache.snapshots.https
- uncheck 'Assign unique versions to snapshots'


Regards
--
=C5=81ukasz
+ 48 606 = 323 122=C2=A0ht= tp://www.lenart.org.pl/

2014-12-02 9:07 GMT+01:00 Maurizio Pillitu <maoo@apache.org>:
> Hi,
>
> I'm in the process of configuring Apache ManifoldCF to deploy/rele= ase
> artifacts (using Apache Maven) in repository.apache.org.
>
> Unfortunately I get the following exception when trying to run "m= vn deploy"
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-dep= loy)
> on project mcf-parent: Failed to deploy artifacts: Could not transfer<= br> > artifact org.apache.manifoldcf:mcf-parent:pom:2.0-20141202.080304-1 fr= om/to
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/sn= apshots): Access
> denied to:
> https://repository.apache.org/content/reposito= ries/snapshots/org/apache/manifoldcf/mcf-parent/2.0-SNAPSHOT/mcf-parent-2.0= -20141202.080304-1.pom,
> ReasonPhrase: Forbidden.
>
> Maven configuration can be found at
> http://svn.apache.org/repos/asf/manifoldcf/trunk/pom.xml
>
> Is there anything wrong with our configuration?
>
> Thanks,
>=C2=A0 =C2=A0mao

--001a11c1dcdeee9d9105093ae0a8--