Do you think it's possible to add a feature to the SDK Installer so that
it
can also deploy FDK into Sonatype Nexus server?
In order to do that, that's what is needed to be done on the Installer as I
see it:
- Check the machine on which the SDK will be installed has Java and Maven
installed and show an option of installing a Mavenized version.
- Ask the user if he wants a local or remote deployment (for remote, he need
to have its maven settings xml ready and be granted)
- Either compile the Mavenizer/Deployer on the client or have a released
version ready to download.
- Harmonized the Installer directory structure of the downloaded stuffs with
the one used by the Mavenizer in order to be able to mavenize the SDK on
it's computer.
- Launch the Mavenizer/Deployer accordingly.
It's not a 5mn work.
At the moment, you can do all of that with the Mavenizer/Deployer, the
source directory of the SDKs (Air/Flex) is particular to this tool, look
closely at the readme.
-Fred
-----Message d'origine-----
From: Gary Young
Sent: Tuesday, July 16, 2013 3:45 PM
To: dev@flex.apache.org
Subject: Re: Apache Flex 4.10 release
Do you think it's possible to add a feature to the SDK Installer so that it
can also deploy FDK into Sonatype Nexus server? Thanks. -Gary
On Tue, Jul 16, 2013 at 9:27 AM, Nicholas Kwiatkowski
<nicho...@spoon.as>wrote:
Justin,
On Win7, x64, JDK 1.7
Things you already know :
- RAT runs fine
- checkin tests run fine
- Mustella runs fine
My tests :
- My mobile apps compile and test fine.
- A few spot-checks of previously known bugs are now corrected
- Desktop apps compile fine.
Failures :
- IDE scripts are missing (I see you just committed those to the repo)
- IDE scripts in the repo are not pointing to the correct URL for the AIR
SDK for Windows (I get a 404 error on that URL).
- IntelliJ is giving me an invalid namespace error for this build
(binaries). I'm trying to track that down to see what is causing it.
I still need to pick over the readme and release notes... I ran out of
time
last night.
-Nick
On Sun, Jul 14, 2013 at 11:10 PM, Justin Mclean <jus...@classsoftware.com
>wrote:
> Hi,
>
> About time we got this release out the door! If there's no one that
> going
> to step forward and fix some of the outstanding issue we'll should just
> release with out them, what we currently have in the develop branch is
> significantly better than the 4.9 release so lets get it out there so
> people can use it.
>
> To start the process off I've updated the README and RELEASE_NOTE (a
> little more work is required) and created a release branch
"release4.10.0",
> who's willing to help out?
>
> Thanks,
> Justin
