Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of shazron@gmail.com designates
 209.85.216.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <etPan.54346ccb.66334873.3de@HooperX.local>
References: 
 <CANDRhHD45TvHJq4289kqF7ufhBpxFH=siVUWCY=iJijOSTnQ2Q@mail.gmail.com>
 <CABiQX1VpGDUYgEQVXujcrnVczd2uMeGSOy7XACoMBavDqRt9-w@mail.gmail.com>
 <D0586855.4BEB1%jsoref@blackberry.com>
 <7a4401fb930347aa952b456b85e5fc97@DM2PR03MB366.namprd03.prod.outlook.com>
 <CAFNH95QQxZOwj7fix7zxaobYKKhbQqVewbobqp1LemW-N95KEg@mail.gmail.com>
 <etPan.54346ccb.66334873.3de@HooperX.local>
From: Shazron <shazron@gmail.com>
Date: Tue, 7 Oct 2014 15:52:27 -0700
Message-ID: 
 <CAE6O_-bUjMTuZN5krJYD61tJWNCebtdDkwfpbe-_gX4s1hdWHQ@mail.gmail.com>
Subject: Re: Build signed archives using CLI
To: tommy-carlos williams <tommy@devgeeks.org>
Cc: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=001a1134778011edce0504dd1062

--001a1134778011edce0504dd1062
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I did open an issue for this two years ago:
https://issues.apache.org/jira/browse/CB-1369
and we did discuss this as well 2 yrs ago:
http://apache.markmail.org/thread/xxlmjjzgnctvsqnm

Seems to be of great value - so let's get going on this ;)
The CLI has (I think) matured more since then to allow this


On Tue, Oct 7, 2014 at 3:44 PM, tommy-carlos williams <tommy@devgeeks.org>
wrote:

> Frederico=E2=80=99s workflow is the same as ours. I would love to see som=
ething
> happen To improve this, the less time I spend in Xcode, the happier I am =
;)
>
>
>
> On 7 October 2014 at 8:48:40, Frederico Galv=C3=A3o (
> frederico.galvao@pontoget.com.br) wrote:
>
> I can already get the ultimate .apk through "cordova build android
> --release", but I already have the required .properties properly configur=
ed
> in my platform/android folder, specifying the path and name to my
> keystores. The "cordova build android --release" already gives me the
> signed and ready .apk, all I have to do is upload it to play.google.com.
>
> I have never, however, used cordova's CLI to build the final artifact for
> iOS (IPA) for iTunes. All I do is run "cordova prepare", and use xCode fr=
om
> then on to build, package, sign, and upload.
>
> 2014-10-06 16:52 GMT-03:00 Parashuram Narasimhan (MS OPEN TECH) <
> panarasi@microsoft.com>:
>
> > How about a "cordova package" command, that would be for packaging the
> app
> > for the store? Note that different platforms may have different
> > requirements for certs, signing etc. So it may make sense to promote th=
is
> > to a different command and let each command take care of packaging the
> app
> > for the store. This command will also mean that developers don=E2=80=99=
t have to
> go
> > over to the native projects when they finally want to publish their app=
s
> to
> > the store.
> >
> > -----Original Message-----
> > From: Josh Soref [mailto:jsoref@blackberry.com]
> > Sent: Monday, October 6, 2014 12:46 PM
> > To: dev
> > Subject: Re: Build signed archives using CLI
> >
> > if you do:
> > Cordova build --release,
> > The blackberry10 platform will generate a signed image...
> >
> > On 10/6/14, 3:18 PM, "Andrew Grieve" <agrieve@chromium.org> wrote:
> >
> > >AFAIK, I don't think there's any technical roadblocks. Just need a
> > >proposal for how it should look, and then a patch & docs to add it!
> > >
> > >For Android's hot-off-the-press gradle support, you can set an
> > >environment variable that points to a .properties file for signing
> > >builds. This shows one way to go about it, but I'm not in love with th=
e
> > .properties idea.
> > >
> > >On Mon, Oct 6, 2014 at 2:48 PM, Victor Sosa <sosah.victor@gmail.com>
> > >wrote:
> > >
> > >> Hi community.
> > >>
> > >> Been looking at this topic and wondering why the build command does
> > >>not create signed archives. Digging a little bit found a lot of
> > >>differences in the platforms to create these archives.
> > >>
> > >> For instance, in Android you need to
> > >> 1. Export your APK in release mode (--release flag) 2. Sign your APK
> > >> (you already need a RSA key)
> > >>
> > >> In iOS, you need to:
> > >> 1. Export your APP using --device flag (--release seems to export fo=
r
> > >>emulator only) 2. Either use XCode (UI-based) and sign the archive or
> > >>use xcrun (headless
> > >> process)
> > >>
> > >> Besides these differences, what is preventing Cordova from providing
> > >> a generic one-way to build these signed, ready-to-publish archives?
> > >>
> > >> Perhaps I'm missing something here...? I really appreciate your
> > >>insights on this topic
> > >>
> > >> Thanks!
> > >>
> > >> --
> > >> Victor Adrian Sosa Herrera
> > >> IBM Software Engineer
> > >> Guadalajara, Jalisco
> > >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
>
>
>
> --
>
> *Frederico Galv=C3=A3o*
>
> Diretor de Tecnologia
>
> PontoGet Inova=C3=A7=C3=A3o Web
>
>
> ( +55(62) 8131-5720
>
> * www.pontoget.com.br <http://www.pontoget.com/>
>

--001a1134778011edce0504dd1062--