Return-Path: X-Original-To: apmail-flex-dev-archive@www.apache.org Delivered-To: apmail-flex-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 70FD8104B6 for ; Fri, 14 Nov 2014 00:32:32 +0000 (UTC) Received: (qmail 99881 invoked by uid 500); 14 Nov 2014 00:32:32 -0000 Delivered-To: apmail-flex-dev-archive@flex.apache.org Received: (qmail 99846 invoked by uid 500); 14 Nov 2014 00:32:32 -0000 Mailing-List: contact dev-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list dev@flex.apache.org Received: (qmail 99833 invoked by uid 99); 14 Nov 2014 00:32:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Nov 2014 00:32:31 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of omuppi1@gmail.com designates 209.85.220.175 as permitted sender) Received: from [209.85.220.175] (HELO mail-vc0-f175.google.com) (209.85.220.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Nov 2014 00:32:05 +0000 Received: by mail-vc0-f175.google.com with SMTP id hy10so325049vcb.34 for ; Thu, 13 Nov 2014 16:30:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=tZbwcLWWM6Z1Zsyjvo5ECnHGQQcco1shqzwcR4aqTSc=; b=kWx+jsnqzSZIHI/T2X/ZG+J5RfisStOdyIujzNquUSGNOQ7lOCs0hQ/SPDizw2hdWH xWHj4W7oErwqvjJHKYwJNbUYfKjSnW4KPiToGsQ3ZuhXTP9Ce26P597owvckp86HBzrJ nOFLv/g/OHVhhfGAtfMJL8EsrmFzo6uteeFXESMpqZwrIEIi79sYTrUo9UckZ92f6uIV oCQr2U0DSGdCiq856q7PJwmhx/82MBvqf7u6DkGsyN9xNX1hF2mVARIiZgp3zXH+bwG1 vPSxf0p4Z8vWJPKDlV+E0K/JMUf6ZAk9GQUaP04D89OIvzYdBgOkopkPgkTBoZojffN4 PdAg== X-Received: by 10.52.53.71 with SMTP id z7mr3681340vdo.7.1415925034249; Thu, 13 Nov 2014 16:30:34 -0800 (PST) MIME-Version: 1.0 Sender: omuppi1@gmail.com Received: by 10.31.54.19 with HTTP; Thu, 13 Nov 2014 16:30:03 -0800 (PST) In-Reply-To: References: <1415891012850.15754@c-ware.de> From: OmPrakash Muppirala Date: Thu, 13 Nov 2014 16:30:03 -0800 X-Google-Sender-Auth: EoFcy4fN4AJhn1sFngMeH-S1waE Message-ID: Subject: Re: [FlexJS] First successful build of a FlexJS application using Flexmojos To: "dev@flex.apache.org" Content-Type: multipart/alternative; boundary=089e012291e8b1f3970507c6bc0f X-Virus-Checked: Checked by ClamAV on apache.org --089e012291e8b1f3970507c6bc0f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Okay, I see what's happening. There is no 'build source package' target for this project. Usually, we use Ant to zip all the relevant files into a .zip and .tz file. I will see what it takes to add an equivalent mvn target to achieve the same thing. Thanks, Om On Thu, Nov 13, 2014 at 3:52 PM, OmPrakash Muppirala wrote: > On Thu, Nov 13, 2014 at 3:30 PM, Alex Harui wrote: > >> >> >> On 11/13/14, 3:19 PM, "OmPrakash Muppirala" wrote= : >> >> >> >> >> In fact, when trying to review the potential release candidate, it >> >>turned >> >> out to be difficult (impossible?) for Maven to provide the source >> >>artifact >> >> on the CI server without actually deploying the artifact to a Maven >> >> server. >> > >> > >> >Can you please explain what "for Maven to provide the source artifact o= n >> >the CI server" means? What are you trying to do? >> >> In our new no-RC workflow, we are trying to get Jenkins to post builds >> with artifacts. For TDF, we have this: >> >> http://apacheflexbuild.cloudapp.net:8080/job/flex-utilities_tour-de-flex= -re >> lease/ >> >> >> Click on =E2=80=9CLast Successful Artifacts=E2=80=9D and somewhere in th= ere is the source >> package. >> >> Over at https://builds.apache.org/view/E-G/view/Flex/job/flex-tool-api/ >> We have =E2=80=9CLast Successful Artifacts=E2=80=9D, but despite my aski= ng several times, >> Chris was unable to get the build to leave the source-release.zip file >> there. He said that would require running the =E2=80=9Cdeploy=E2=80=9D = command which >> would try to upload the artifacts to the Maven staging server. My >> takeaway was that Maven didn=E2=80=99t have a =E2=80=9Cbuild=E2=80=9D co= mmand that would just >> compile artifacts and not deploy them. That=E2=80=99s why I drew the ana= logy to >> not being able to get pepperoni on one side and sausage on the other. T= he >> Maven assumption is that you would always deploy any built artifacts. >> >> > Are we sure that the source-release.zip is actually getting built? I > don't see it in the 'target' directory in the workspace. > I do see a flex-tool-api-1.1.0-SNAPSHOT.jar here[1] which seems to be th= e > only artifact getting built. > > Thanks, > Om > > [1] > https://builds.apache.org/view/E-G/view/Flex/job/flex-tool-api/lastSucces= sfulBuild/artifact/flex-tool-api/target/ > > >> -Alex >> >> > --089e012291e8b1f3970507c6bc0f--