From dev-return-27704-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Thu Oct 09 10:51:11 2008 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 97435 invoked from network); 9 Oct 2008 10:51:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Oct 2008 10:51:11 -0000 Received: (qmail 2565 invoked by uid 500); 9 Oct 2008 10:51:09 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 2523 invoked by uid 500); 9 Oct 2008 10:51:09 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 2512 invoked by uid 99); 9 Oct 2008 10:51:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Oct 2008 03:51:09 -0700 X-ASF-Spam-Status: No, hits=2.1 required=10.0 tests=DNS_FROM_SECURITYSAGE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pajbam@gmail.com designates 209.85.200.174 as permitted sender) Received: from [209.85.200.174] (HELO wf-out-1314.google.com) (209.85.200.174) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Oct 2008 10:50:05 +0000 Received: by wf-out-1314.google.com with SMTP id 27so4871776wfd.31 for ; Thu, 09 Oct 2008 03:50:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=UUNIQ+oSuiH0NaqCgHhmyo8JbodoJxfL9uNeATgvLmw=; b=e7RPiWrlXSwMvlr9Ntr69yqJLdy5gpxhXVn3uZ+Wg4zBUkYRnxlFClVHU3XQJ9zo0M Eu4pTXSx8YA4ITQrHYPbkNwS2qaymwopIUjExXNvULp8mowpUSe1YOTXHuF4OWjcIeOQ DaumCSrm+uqu2ZO/ac4aOUXfUXfgPbpvIH5+M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=h6yc2Se5YtDcR+aEPxwU0PP/RfmgRRKnnoZOIVIuID1EFZLIEs+qHq2q1b/jBZWZT0 MKa08QPQ64dzV0v/Hn8aonh0rLot3da05rrSsWdg/SQuorbc/V0Ps7uoOaTj5bLXgXCY RM9bRPw6lR6VatihtSE7Y49Li2QowU5iCTUKg= Received: by 10.142.207.8 with SMTP id e8mr4230747wfg.281.1223549431438; Thu, 09 Oct 2008 03:50:31 -0700 (PDT) Received: by 10.143.6.6 with HTTP; Thu, 9 Oct 2008 03:50:31 -0700 (PDT) Message-ID: <98d8c0860810090350s2c9233d8v520f785b4b1ce6f1@mail.gmail.com> Date: Thu, 9 Oct 2008 12:50:31 +0200 From: "Pierre-Arnaud Marcelot" Sender: pajbam@gmail.com To: "Apache Directory Developers List" Subject: Re: [Studio] Using the Maven Release Plugin In-Reply-To: <98d8c0860810030908w2efd320j539cfdc9e7ea047f@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_41371_14452480.1223549431458" References: <98d8c0860809190454q4a3356d1q9b45e6b9e735f197@mail.gmail.com> <48E3B129.2080401@apache.org> <98d8c0860810020449j7e3cb8dm2346bfd53c1cf03c@mail.gmail.com> <98d8c0860810020458h2ba75587kf0e07a34eae4c6f7@mail.gmail.com> <48E4BB01.8030708@apache.org> <98d8c0860810030302v4cf0622fq3e6866b85a5ad049@mail.gmail.com> <98d8c0860810030606n53d53a3dxa40bd2ded7260c73@mail.gmail.com> <98d8c0860810030724p5795c03kd79b344729fa8f18@mail.gmail.com> <48E62C63.9010202@apache.org> <98d8c0860810030908w2efd320j539cfdc9e7ea047f@mail.gmail.com> X-Google-Sender-Auth: da7376629711a914 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_41371_14452480.1223549431458 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Felix, I need your help to fix the use of the release plugin in Studio's build. At the moment, when I try to release I get an error when performing the 'release:perform' goal: ================================================================ [INFO] [deploy:deploy-file {execution: deploy-dist-macosx}] Uploading: scpexe:// vm094.oxylos.org/var/www/html/mirror-maven2/org/apache/directory/studio/ApacheDirectoryStudio/1.3.0-macosx/ApacheDirectoryStudio-1.3.0-macosx.tar.gz [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error deploying artifact: Error executing command for transfer Exit code 255 - Host key verification failed. [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4 minutes 58 seconds [INFO] Finished at: Thu Oct 09 12:36:56 CEST 2008 [INFO] Final Memory: 69M/147M [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ ================================================================ Maven is trying to deploy the distribution on the Oxylos machine instead of the release maven repository. The configuration for the deploy plugin is this one: ================================================================ maven-deploy-plugin deploy-dist-macosx deploy ../target/distributions/ApacheDirectoryStudio-macosx-${pom.version}-dist.tar.gz ${pom.distributionManagement.snapshotRepository.url} ApacheDirectoryStudio ${pom.groupId} tar.gz ${pom.version}-macosx false deploy-file ================================================================ Felix, do you know how I can tweak the configuration so the file gets deployed on the correct repository (without breaking the deployment for the Oxylos machine)? Thanks, Pierre-Arnaud On Fri, Oct 3, 2008 at 6:08 PM, Pierre-Arnaud Marcelot wrote: > Hi Felix, > > On Fri, Oct 3, 2008 at 4:29 PM, Felix Knecht wrote: > >> I think we should put this deployment into a profile CI (exists already >> somewhere) to have it deployed only when using this profile. >> > > Yeah, that's exactly what I was thinking. > > >> > I'm also wondering if it makes sense to deploy the distributions >> > during the 'release' phase, because only one distribution (the one for >> > your OS) will be generated and not all the distribution. >> You can add the profiles for the missing OSs to generate the dists. >> > > Yeah, it's true. I didn't think at that. > We could add that the configuration of the release plugin. > But, once again, the deployed distributions won't be the final ones for Mac > OS X and Windows. > The question is "Is this really a problem?"... I don't know... Maybe not... > > Regards, > Pierre-Arnaud > > ------=_Part_41371_14452480.1223549431458 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Hi Felix,

I need your help to fix the use of the release plugin in Studio's build.

At the moment, when I try to release I get an error when performing the 'release:perform' goal:
================================================================
        [INFO] [deploy:deploy-file {execution: deploy-dist-macosx}]
        Uploading: scpexe://vm094.oxylos.org/var/www/html/mirror-maven2/org/apache/directory/studio/ApacheDirectoryStudio/1.3.0-macosx/ApacheDirectoryStudio-1.3.0-macosx.tar.gz
        [INFO] ------------------------------------------------------------------------
        [ERROR] BUILD ERROR
        [INFO] ------------------------------------------------------------------------
        [INFO] Error deploying artifact: Error executing command for transfer
       
    Exit code 255 - Host key verification failed.
       
    [INFO] ------------------------------------------------------------------------
        [INFO] For more information, run Maven with the -e switch
        [INFO] ------------------------------------------------------------------------
        [INFO] Total time: 4 minutes 58 seconds
        [INFO] Finished at: Thu Oct 09 12:36:56 CEST 2008
        [INFO] Final Memory: 69M/147M
        [INFO] ------------------------------------------------------------------------
        [INFO] ------------------------------------------------------------------------
================================================================

Maven is trying to deploy the distribution on the Oxylos machine instead of the release maven repository.

The configuration for the deploy plugin is this one:
================================================================
          <plugin>
            <artifactId>maven-deploy-plugin</artifactId>
            <executions>
              <execution>
                <id>deploy-dist-macosx</id>
                <phase>deploy</phase>
                <configuration>
                  <file>../target/distributions/ApacheDirectoryStudio-macosx-${pom.version}-dist.tar.gz</file>
                  <url>${pom.distributionManagement.snapshotRepository.url}</url>
                  <artifactId>ApacheDirectoryStudio</artifactId>
                  <groupId>${pom.groupId}</groupId>
                  <packaging>tar.gz</packaging>
                  <version>${pom.version}-macosx</version>
                  <uniqueVersion>false</uniqueVersion>
                  <!-- generatePom>false</generatePom -->
                </configuration>
                <goals>
                  <goal>deploy-file</goal>
                </goals>
              </execution>
            </executions>
          </plugin>
================================================================

Felix, do you know how I can tweak the configuration so the file gets deployed on the correct repository (without breaking the deployment for the Oxylos machine)?

Thanks,
Pierre-Arnaud

On Fri, Oct 3, 2008 at 6:08 PM, Pierre-Arnaud Marcelot <pa@marcelot.net> wrote:
Hi Felix,


On Fri, Oct 3, 2008 at 4:29 PM, Felix Knecht <felixk@apache.org> wrote:
I think we should put this deployment into a profile CI (exists already
somewhere) to have it deployed only when using this profile.

Yeah, that's exactly what I was thinking.
 
> I'm also wondering if it makes sense to deploy the distributions
> during the 'release' phase, because only one distribution (the one for
> your OS) will be generated and not all the distribution.
You can add the profiles for the missing OSs to generate the dists.

Yeah, it's true. I didn't think at that.
We could add that the configuration of the release plugin.
But, once again, the deployed distributions won't be the final ones for Mac OS X and Windows.
The question is "Is this really a problem?"... I don't know... Maybe not...

Regards,
Pierre-Arnaud


------=_Part_41371_14452480.1223549431458--