You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Alex Harui <ah...@adobe.com> on 2012/11/27 19:46:02 UTC
[POLL] Maven and Apache Flex
Hi Folks,
There have been some recent discussions about Maven and how it could work
with Apache Flex. There are several possibilities, but none of them are
perfect because of Adobe licensing requirements. This poll is only about
how you use or plan to use Apache Flex and Maven to build apps that use an
Adobe runtime (Adobe Flash Player or Adobe AIR including Adobe AIR packaged
for Android or IOS). We¹ll worry about other Apache Flex scenarios in the
future. This poll also assumes that the Adobe will not change its SDK
licensing and requires that you accept the licensing terms at least once.
Also, you can substitute the word "Maven" for any Maven-like tool that uses
Maven files.
Please answer the following:
1. Number of people who will use Maven to develop Flex apps at your company
(0 if you have no interest in using Maven).
2. Maven would be used to develop apps for FlashPlayer in the browser (yes
or no)
3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
no)
4. Maven would be used to develop apps for AIR on Android (yes or no)
5. Maven would be used to develop apps for AIR on IOS (yes or no)
6. Rate the following proposed implementations (-1 = not acceptable, 0 =
neutral, 1 = acceptable, 2 = preferred)
a) You must manually download the Player SDK and AIR SDK from the Adobe
site and set up environment variables pointing to them
b) You must download and install a Maven plug-in from the Apache Flex
site. The first time you use Maven on a computer, it will ask you
to accept the Adobe license agreement.
c) You must download and install a Maven plug-in from the Adobe
site. The first time you use Maven on a computer, it will ask you
to accept the Adobe license agreement.
d) Maven can be used as-is for FlashPlayer apps and AIR apps on
desktops/laptops, but not for AIR apps on Android/IOS. To target
Android/IOS, you must use one of the first three implementations
e) We will manually download the Player SDKs and AIR SDKs and put them
in our local/private Maven repo.
f) We would use a utility application that would download the Player
SDKs and AIR SDKs (prompting you to accept the license) and put them
in our local/private Maven repo.
Thanks in advance. Remember that polls are not binding, but your input is
much appreciated.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: [POLL] Maven and Apache Flex
Posted by Simon Morvan <ga...@zone84.net>.
Le 28/11/2012 18:35, Alex Harui a écrit :
>
>
> On 11/28/12 2:22 AM, "Bertrand Delacretaz" <bd...@apache.org> wrote:
>
>> On Tue, Nov 27, 2012 at 7:46 PM, Alex Harui <ah...@adobe.com> wrote:
>>> ...6. Rate the following proposed implementations (-1 = not acceptable, 0 =
>>> neutral, 1 = acceptable, 2 = preferred)
>>> a) You must manually download the Player SDK and AIR SDK from the Adobe
>>> site and set up environment variables pointing to them...
>> Doesn't the Flex installer already download those files?
> It was my understanding that Maven users won't need to use the Apache Flex
> installer.
The opposite would cancel any benefit of using Maven's dependency
management features.
Re: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
On 11/28/12 2:22 AM, "Bertrand Delacretaz" <bd...@apache.org> wrote:
> On Tue, Nov 27, 2012 at 7:46 PM, Alex Harui <ah...@adobe.com> wrote:
>> ...6. Rate the following proposed implementations (-1 = not acceptable, 0 =
>> neutral, 1 = acceptable, 2 = preferred)
>> a) You must manually download the Player SDK and AIR SDK from the Adobe
>> site and set up environment variables pointing to them...
>
> Doesn't the Flex installer already download those files?
It was my understanding that Maven users won't need to use the Apache Flex
installer.
>
> If yes, you just need to provide a script to add them to one's local
> Maven repository, no need to set environment variables if the build
> then gets them from there.
>
> -Bertrand
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: [POLL] Maven and Apache Flex
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, Nov 27, 2012 at 7:46 PM, Alex Harui <ah...@adobe.com> wrote:
> ...6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> neutral, 1 = acceptable, 2 = preferred)
> a) You must manually download the Player SDK and AIR SDK from the Adobe
> site and set up environment variables pointing to them...
Doesn't the Flex installer already download those files?
If yes, you just need to provide a script to add them to one's local
Maven repository, no need to set environment variables if the build
then gets them from there.
-Bertrand
AW: AW: [POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
This was something we had discussed here not just once and it seemed that Adobe was not willing to provide such an option.
Chris
________________________________________
Von: Simon Morvan [garphy@zone84.net]
Gesendet: Mittwoch, 28. November 2012 16:18
An: flex-dev@incubator.apache.org
Betreff: Re: AW: [POLL] Maven and Apache Flex
Le 28/11/2012 13:56, christofer.dutz@c-ware.de a écrit :
> Then it outputs the license text to the console (and hereby to the screen and/or log). If this is an interactive build, it prompts the user to accept the license, if it's a non-interactive build it generates a token (UUID) and outputs that so it is written to the log.
> Now you can set a property "adobe.accept-licence-token" and provide the previously generated token ... now the user has to do a second run. This time when checking that the artifacts are present the tool will see that a token is provided and compares that to the previously generated one. If these match, it downloads and mavenizes the missing resources.
Chris,
Given that licensed artifacts would be shipped from Adobe's repository,
couldn't it be a License you implicitly accept by using the repository ?
Adobe could require that user registers a contact email to be notified
of licensing updates as it was done in the past for Flashplayer
redistribution policy.
Re: AW: [POLL] Maven and Apache Flex
Posted by Simon Morvan <ga...@zone84.net>.
Le 28/11/2012 13:56, christofer.dutz@c-ware.de a écrit :
> Then it outputs the license text to the console (and hereby to the screen and/or log). If this is an interactive build, it prompts the user to accept the license, if it's a non-interactive build it generates a token (UUID) and outputs that so it is written to the log.
> Now you can set a property "adobe.accept-licence-token" and provide the previously generated token ... now the user has to do a second run. This time when checking that the artifacts are present the tool will see that a token is provided and compares that to the previously generated one. If these match, it downloads and mavenizes the missing resources.
Chris,
Given that licensed artifacts would be shipped from Adobe's repository,
couldn't it be a License you implicitly accept by using the repository ?
Adobe could require that user registers a contact email to be notified
of licensing updates as it was done in the past for Flashplayer
redistribution policy.
AW: [POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Ok ... then how about this option:
You can set the plugin to run in non-interactive mode so it doesn't block in CI Servers.
If the artifacts are missing it outputs a message telling the uses that artifacts are missing and that the Adobe license has to be accepted.
Then it outputs the license text to the console (and hereby to the screen and/or log). If this is an interactive build, it prompts the user to accept the license, if it's a non-interactive build it generates a token (UUID) and outputs that so it is written to the log.
Now you can set a property "adobe.accept-licence-token" and provide the previously generated token ... now the user has to do a second run. This time when checking that the artifacts are present the tool will see that a token is provided and compares that to the previously generated one. If these match, it downloads and mavenizes the missing resources.
This way it is guaranteed to have somehow presented the license text and the user has to willingly accept it and isn't able to automate the acceptance.
BUT ... it is not guaranteed that the user has actually read the text :-)
BUT ... I would really like to have it the simpler way :-)
Chris
________________________________________
Von: Maxime Cowez [maxime.cowez@gmail.com]
Gesendet: Mittwoch, 28. November 2012 13:23
An: flex-dev@incubator.apache.org
Betreff: Re: [POLL] Maven and Apache Flex
Sounds perfect to me.
I just have one question regarding the option for non-interactive builds:
would that be acceptable for Adobe?
In this case no one would explicitly accept the license and there's nothing
that prohibits a "human" developer to use this property as well.
On Wed, Nov 28, 2012 at 12:49 PM, christofer.dutz@c-ware.de <
christofer.dutz@c-ware.de> wrote:
> No Offense taken ... after all .. I didn't write the tool, I simply took
> over maintaining it and got the code back on track (Testsuite was failling
> in more than 30 Tests).
>
> I think the maven pluigin would be automatically downloaded as is the case
> with all other maven plugins, so I guess no manual step would have to be
> done.
>
> What would you all think of the following solution:
> - Apache deploys the Apache Flex FDK artifacts in a public maven repo
> (Without the Apache stuff you need a license for)
> - In the maven-flex-plugin suite there is one mojo that binds to mavens
> "initialize" phase and checks the availability of the Apache artifacts. If
> they are missing it prompts the user if he accepts the license agreement
> (An option to allow a non-interactive build would be good for running on
> CI-Servers)
> - The Adobe-Stuff-Deployer mojo internally uses part of the Mavenizer to
> deploy artifacts to the local maven repo.
> - The rest of the maven-flex-plugin suite uses the atrifacts in the repo
> as in any normal build.
>
> I think this solution should suite the needs of:
> - Adobe, because people need to accept the licenses
> - Developers, because they don't have to manually do more than accept a
> license agreement by typing: "y".
> - Coporates, because the generated artifacts could be deployed to local
> Maven repos.
>
> Chris
>
> ________________________________________
> Von: Maxime Cowez [maxime.cowez@gmail.com]
> Gesendet: Mittwoch, 28. November 2012 12:24
> An: flex-dev@incubator.apache.org
> Betreff: Re: [POLL] Maven and Apache Flex
>
> I am actually using Gradle with GradleFx plugin (sorry Chris, had too many
> issues with FlexMojos :-/ ). Gradle uses Maven under the hood. My answers
> to the first 5 questions should be interpreted from that angle.
>
>
> > 1. Number of people who will use Maven to develop Flex apps at your
> company
> > (0 if you have no interest in using Maven).
> >
>
> 1 (I'm the only Flex dev)
> 9, if you count the java devs that need my build scripts to build their web
> apps
>
>
> > 2. Maven would be used to develop apps for FlashPlayer in the browser
> (yes
> > or no)
> >
>
> yes
>
>
> >
> > 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> > no)
> >
>
> no (not yet, but possibly in the future)
>
>
> > 4. Maven would be used to develop apps for AIR on Android (yes or no)
> >
>
> no (not yet, but possibly in the future)
>
>
> >
> > 5. Maven would be used to develop apps for AIR on IOS (yes or no)
> >
>
> no (not yet, but possibly in the future)
>
>
> >
> > 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> > neutral, 1 = acceptable, 2 = preferred)
> > a) You must manually download the Player SDK and AIR SDK from the
> Adobe
> > site and set up environment variables pointing to them
> >
>
> -1
>
>
> > b) You must download and install a Maven plug-in from the Apache Flex
> > site. The first time you use Maven on a computer, it will ask you
> > to accept the Adobe license agreement.
> >
>
> 0 (see remarks below)
>
>
> > c) You must download and install a Maven plug-in from the Adobe
> > site. The first time you use Maven on a computer, it will ask you
> > to accept the Adobe license agreement.
> >
>
> 0 (see remarks below)
>
>
> > d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> > desktops/laptops, but not for AIR apps on Android/IOS. To target
> > Android/IOS, you must use one of the first three implementations
> >
>
> 0
>
>
> > e) We will manually download the Player SDKs and AIR SDKs and put
> them
> > in our local/private Maven repo.
> >
>
> 0
>
>
> > f) We would use a utility application that would download the Player
> > SDKs and AIR SDKs (prompting you to accept the license) and put
> them
> > in our local/private Maven repo.
> >
>
> 0
>
> Remarks:
> - The number of steps to be taken by a Java developer that needs to compile
> my Flex apps should be 0 (accepting a license would be acceptable).
> - I haven't given a positive number to any of the proposed implementations,
> because all of them require at least one manual step, which violates my
> previous requirement. Unless I didn't understand them correctly; if
> downloading the Maven plugin is part of the build process, then my answer
> should be "2" for those solutions. Otherwise downloading the Maven plugin
> manually would be closest to acceptable because I assume it comes closest
> to what the java devs are already used to do.
> - For reference, this is how it is handled in GradleFx:
> - the GradleFx plugin is downloaded and cached automatically by Gradle
> - the Flex SDK is downloaded and cached automatically by
> Gradle/GradleFx, including Adobe's proprietary libraries; the licenses must
> be accepted once
> - other dependencies are downloaded and cached, and the application is
> built
> - the Java devs don't even have to install Gradle because I commit the
> Flex app with a so-called Gradle "wrapper", a lightweight standalone build
> tool. Unfortunately this feature is specific to Gradle and doesn't exist in
> Maven (as far as I know).
>
> >
> > Thanks in advance. Remember that polls are not binding, but your input
> is
> > much appreciated.
> >
> > --
> > Alex Harui
> > Flex SDK Team
> > Adobe Systems, Inc.
> > http://blogs.adobe.com/aharui
> >
> >
>
Re: [POLL] Maven and Apache Flex
Posted by Maxime Cowez <ma...@gmail.com>.
Sounds perfect to me.
I just have one question regarding the option for non-interactive builds:
would that be acceptable for Adobe?
In this case no one would explicitly accept the license and there's nothing
that prohibits a "human" developer to use this property as well.
On Wed, Nov 28, 2012 at 12:49 PM, christofer.dutz@c-ware.de <
christofer.dutz@c-ware.de> wrote:
> No Offense taken ... after all .. I didn't write the tool, I simply took
> over maintaining it and got the code back on track (Testsuite was failling
> in more than 30 Tests).
>
> I think the maven pluigin would be automatically downloaded as is the case
> with all other maven plugins, so I guess no manual step would have to be
> done.
>
> What would you all think of the following solution:
> - Apache deploys the Apache Flex FDK artifacts in a public maven repo
> (Without the Apache stuff you need a license for)
> - In the maven-flex-plugin suite there is one mojo that binds to mavens
> "initialize" phase and checks the availability of the Apache artifacts. If
> they are missing it prompts the user if he accepts the license agreement
> (An option to allow a non-interactive build would be good for running on
> CI-Servers)
> - The Adobe-Stuff-Deployer mojo internally uses part of the Mavenizer to
> deploy artifacts to the local maven repo.
> - The rest of the maven-flex-plugin suite uses the atrifacts in the repo
> as in any normal build.
>
> I think this solution should suite the needs of:
> - Adobe, because people need to accept the licenses
> - Developers, because they don't have to manually do more than accept a
> license agreement by typing: "y".
> - Coporates, because the generated artifacts could be deployed to local
> Maven repos.
>
> Chris
>
> ________________________________________
> Von: Maxime Cowez [maxime.cowez@gmail.com]
> Gesendet: Mittwoch, 28. November 2012 12:24
> An: flex-dev@incubator.apache.org
> Betreff: Re: [POLL] Maven and Apache Flex
>
> I am actually using Gradle with GradleFx plugin (sorry Chris, had too many
> issues with FlexMojos :-/ ). Gradle uses Maven under the hood. My answers
> to the first 5 questions should be interpreted from that angle.
>
>
> > 1. Number of people who will use Maven to develop Flex apps at your
> company
> > (0 if you have no interest in using Maven).
> >
>
> 1 (I'm the only Flex dev)
> 9, if you count the java devs that need my build scripts to build their web
> apps
>
>
> > 2. Maven would be used to develop apps for FlashPlayer in the browser
> (yes
> > or no)
> >
>
> yes
>
>
> >
> > 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> > no)
> >
>
> no (not yet, but possibly in the future)
>
>
> > 4. Maven would be used to develop apps for AIR on Android (yes or no)
> >
>
> no (not yet, but possibly in the future)
>
>
> >
> > 5. Maven would be used to develop apps for AIR on IOS (yes or no)
> >
>
> no (not yet, but possibly in the future)
>
>
> >
> > 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> > neutral, 1 = acceptable, 2 = preferred)
> > a) You must manually download the Player SDK and AIR SDK from the
> Adobe
> > site and set up environment variables pointing to them
> >
>
> -1
>
>
> > b) You must download and install a Maven plug-in from the Apache Flex
> > site. The first time you use Maven on a computer, it will ask you
> > to accept the Adobe license agreement.
> >
>
> 0 (see remarks below)
>
>
> > c) You must download and install a Maven plug-in from the Adobe
> > site. The first time you use Maven on a computer, it will ask you
> > to accept the Adobe license agreement.
> >
>
> 0 (see remarks below)
>
>
> > d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> > desktops/laptops, but not for AIR apps on Android/IOS. To target
> > Android/IOS, you must use one of the first three implementations
> >
>
> 0
>
>
> > e) We will manually download the Player SDKs and AIR SDKs and put
> them
> > in our local/private Maven repo.
> >
>
> 0
>
>
> > f) We would use a utility application that would download the Player
> > SDKs and AIR SDKs (prompting you to accept the license) and put
> them
> > in our local/private Maven repo.
> >
>
> 0
>
> Remarks:
> - The number of steps to be taken by a Java developer that needs to compile
> my Flex apps should be 0 (accepting a license would be acceptable).
> - I haven't given a positive number to any of the proposed implementations,
> because all of them require at least one manual step, which violates my
> previous requirement. Unless I didn't understand them correctly; if
> downloading the Maven plugin is part of the build process, then my answer
> should be "2" for those solutions. Otherwise downloading the Maven plugin
> manually would be closest to acceptable because I assume it comes closest
> to what the java devs are already used to do.
> - For reference, this is how it is handled in GradleFx:
> - the GradleFx plugin is downloaded and cached automatically by Gradle
> - the Flex SDK is downloaded and cached automatically by
> Gradle/GradleFx, including Adobe's proprietary libraries; the licenses must
> be accepted once
> - other dependencies are downloaded and cached, and the application is
> built
> - the Java devs don't even have to install Gradle because I commit the
> Flex app with a so-called Gradle "wrapper", a lightweight standalone build
> tool. Unfortunately this feature is specific to Gradle and doesn't exist in
> Maven (as far as I know).
>
> >
> > Thanks in advance. Remember that polls are not binding, but your input
> is
> > much appreciated.
> >
> > --
> > Alex Harui
> > Flex SDK Team
> > Adobe Systems, Inc.
> > http://blogs.adobe.com/aharui
> >
> >
>
AW: AW: [POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
I think I will not do any real work on FM6.
Currently you are able to use FM6 with the Mavenizer and I would rather concentrate on building a new plugin.
Chris
________________________________________
Von: Frédéric THOMAS [webdoublefx@hotmail.com]
Gesendet: Mittwoch, 28. November 2012 13:48
An: flex-dev@incubator.apache.org
Betreff: Re: AW: [POLL] Maven and Apache Flex
+1 - Nice one.
- In the maven-flex-plugin suite there is one mojo that binds to mavens
"initialize" phase and checks the availability of the Apache artifacts. If
they are missing it prompts the user if he accepts the license agreement (An
option to allow a non-interactive build would be good for running on
CI-Servers)
Is that a proposal for flexmojos 6.x too or we'll have to wait for flexmojos
next (maven-flex-plugin) ?
(The optional part is not an option IMO)
- Fred.
-----Message d'origine-----
From: christofer.dutz@c-ware.de
Sent: Wednesday, November 28, 2012 12:49 PM
To: flex-dev@incubator.apache.org
Subject: AW: [POLL] Maven and Apache Flex
No Offense taken ... after all .. I didn't write the tool, I simply took
over maintaining it and got the code back on track (Testsuite was failling
in more than 30 Tests).
I think the maven pluigin would be automatically downloaded as is the case
with all other maven plugins, so I guess no manual step would have to be
done.
What would you all think of the following solution:
- Apache deploys the Apache Flex FDK artifacts in a public maven repo
(Without the Apache stuff you need a license for)
- In the maven-flex-plugin suite there is one mojo that binds to mavens
"initialize" phase and checks the availability of the Apache artifacts. If
they are missing it prompts the user if he accepts the license agreement (An
option to allow a non-interactive build would be good for running on
CI-Servers)
- The Adobe-Stuff-Deployer mojo internally uses part of the Mavenizer to
deploy artifacts to the local maven repo.
- The rest of the maven-flex-plugin suite uses the atrifacts in the repo as
in any normal build.
I think this solution should suite the needs of:
- Adobe, because people need to accept the licenses
- Developers, because they don't have to manually do more than accept a
license agreement by typing: "y".
- Coporates, because the generated artifacts could be deployed to local
Maven repos.
Chris
________________________________________
Von: Maxime Cowez [maxime.cowez@gmail.com]
Gesendet: Mittwoch, 28. November 2012 12:24
An: flex-dev@incubator.apache.org
Betreff: Re: [POLL] Maven and Apache Flex
I am actually using Gradle with GradleFx plugin (sorry Chris, had too many
issues with FlexMojos :-/ ). Gradle uses Maven under the hood. My answers
to the first 5 questions should be interpreted from that angle.
> 1. Number of people who will use Maven to develop Flex apps at your
> company
> (0 if you have no interest in using Maven).
>
1 (I'm the only Flex dev)
9, if you count the java devs that need my build scripts to build their web
apps
> 2. Maven would be used to develop apps for FlashPlayer in the browser (yes
> or no)
>
yes
>
> 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> no)
>
no (not yet, but possibly in the future)
> 4. Maven would be used to develop apps for AIR on Android (yes or no)
>
no (not yet, but possibly in the future)
>
> 5. Maven would be used to develop apps for AIR on IOS (yes or no)
>
no (not yet, but possibly in the future)
>
> 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> neutral, 1 = acceptable, 2 = preferred)
> a) You must manually download the Player SDK and AIR SDK from the
> Adobe
> site and set up environment variables pointing to them
>
-1
> b) You must download and install a Maven plug-in from the Apache Flex
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
0 (see remarks below)
> c) You must download and install a Maven plug-in from the Adobe
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
0 (see remarks below)
> d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> desktops/laptops, but not for AIR apps on Android/IOS. To target
> Android/IOS, you must use one of the first three implementations
>
0
> e) We will manually download the Player SDKs and AIR SDKs and put them
> in our local/private Maven repo.
>
0
> f) We would use a utility application that would download the Player
> SDKs and AIR SDKs (prompting you to accept the license) and put
> them
> in our local/private Maven repo.
>
0
Remarks:
- The number of steps to be taken by a Java developer that needs to compile
my Flex apps should be 0 (accepting a license would be acceptable).
- I haven't given a positive number to any of the proposed implementations,
because all of them require at least one manual step, which violates my
previous requirement. Unless I didn't understand them correctly; if
downloading the Maven plugin is part of the build process, then my answer
should be "2" for those solutions. Otherwise downloading the Maven plugin
manually would be closest to acceptable because I assume it comes closest
to what the java devs are already used to do.
- For reference, this is how it is handled in GradleFx:
- the GradleFx plugin is downloaded and cached automatically by Gradle
- the Flex SDK is downloaded and cached automatically by
Gradle/GradleFx, including Adobe's proprietary libraries; the licenses must
be accepted once
- other dependencies are downloaded and cached, and the application is
built
- the Java devs don't even have to install Gradle because I commit the
Flex app with a so-called Gradle "wrapper", a lightweight standalone build
tool. Unfortunately this feature is specific to Gradle and doesn't exist in
Maven (as far as I know).
>
> Thanks in advance. Remember that polls are not binding, but your input is
> much appreciated.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: AW: [POLL] Maven and Apache Flex
Posted by Frédéric THOMAS <we...@hotmail.com>.
+1 - Nice one.
- In the maven-flex-plugin suite there is one mojo that binds to mavens
"initialize" phase and checks the availability of the Apache artifacts. If
they are missing it prompts the user if he accepts the license agreement (An
option to allow a non-interactive build would be good for running on
CI-Servers)
Is that a proposal for flexmojos 6.x too or we'll have to wait for flexmojos
next (maven-flex-plugin) ?
(The optional part is not an option IMO)
- Fred.
-----Message d'origine-----
From: christofer.dutz@c-ware.de
Sent: Wednesday, November 28, 2012 12:49 PM
To: flex-dev@incubator.apache.org
Subject: AW: [POLL] Maven and Apache Flex
No Offense taken ... after all .. I didn't write the tool, I simply took
over maintaining it and got the code back on track (Testsuite was failling
in more than 30 Tests).
I think the maven pluigin would be automatically downloaded as is the case
with all other maven plugins, so I guess no manual step would have to be
done.
What would you all think of the following solution:
- Apache deploys the Apache Flex FDK artifacts in a public maven repo
(Without the Apache stuff you need a license for)
- In the maven-flex-plugin suite there is one mojo that binds to mavens
"initialize" phase and checks the availability of the Apache artifacts. If
they are missing it prompts the user if he accepts the license agreement (An
option to allow a non-interactive build would be good for running on
CI-Servers)
- The Adobe-Stuff-Deployer mojo internally uses part of the Mavenizer to
deploy artifacts to the local maven repo.
- The rest of the maven-flex-plugin suite uses the atrifacts in the repo as
in any normal build.
I think this solution should suite the needs of:
- Adobe, because people need to accept the licenses
- Developers, because they don't have to manually do more than accept a
license agreement by typing: "y".
- Coporates, because the generated artifacts could be deployed to local
Maven repos.
Chris
________________________________________
Von: Maxime Cowez [maxime.cowez@gmail.com]
Gesendet: Mittwoch, 28. November 2012 12:24
An: flex-dev@incubator.apache.org
Betreff: Re: [POLL] Maven and Apache Flex
I am actually using Gradle with GradleFx plugin (sorry Chris, had too many
issues with FlexMojos :-/ ). Gradle uses Maven under the hood. My answers
to the first 5 questions should be interpreted from that angle.
> 1. Number of people who will use Maven to develop Flex apps at your
> company
> (0 if you have no interest in using Maven).
>
1 (I'm the only Flex dev)
9, if you count the java devs that need my build scripts to build their web
apps
> 2. Maven would be used to develop apps for FlashPlayer in the browser (yes
> or no)
>
yes
>
> 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> no)
>
no (not yet, but possibly in the future)
> 4. Maven would be used to develop apps for AIR on Android (yes or no)
>
no (not yet, but possibly in the future)
>
> 5. Maven would be used to develop apps for AIR on IOS (yes or no)
>
no (not yet, but possibly in the future)
>
> 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> neutral, 1 = acceptable, 2 = preferred)
> a) You must manually download the Player SDK and AIR SDK from the
> Adobe
> site and set up environment variables pointing to them
>
-1
> b) You must download and install a Maven plug-in from the Apache Flex
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
0 (see remarks below)
> c) You must download and install a Maven plug-in from the Adobe
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
0 (see remarks below)
> d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> desktops/laptops, but not for AIR apps on Android/IOS. To target
> Android/IOS, you must use one of the first three implementations
>
0
> e) We will manually download the Player SDKs and AIR SDKs and put them
> in our local/private Maven repo.
>
0
> f) We would use a utility application that would download the Player
> SDKs and AIR SDKs (prompting you to accept the license) and put
> them
> in our local/private Maven repo.
>
0
Remarks:
- The number of steps to be taken by a Java developer that needs to compile
my Flex apps should be 0 (accepting a license would be acceptable).
- I haven't given a positive number to any of the proposed implementations,
because all of them require at least one manual step, which violates my
previous requirement. Unless I didn't understand them correctly; if
downloading the Maven plugin is part of the build process, then my answer
should be "2" for those solutions. Otherwise downloading the Maven plugin
manually would be closest to acceptable because I assume it comes closest
to what the java devs are already used to do.
- For reference, this is how it is handled in GradleFx:
- the GradleFx plugin is downloaded and cached automatically by Gradle
- the Flex SDK is downloaded and cached automatically by
Gradle/GradleFx, including Adobe's proprietary libraries; the licenses must
be accepted once
- other dependencies are downloaded and cached, and the application is
built
- the Java devs don't even have to install Gradle because I commit the
Flex app with a so-called Gradle "wrapper", a lightweight standalone build
tool. Unfortunately this feature is specific to Gradle and doesn't exist in
Maven (as far as I know).
>
> Thanks in advance. Remember that polls are not binding, but your input is
> much appreciated.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: AW: AW: [POLL] Maven and Apache Flex
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Wed, Nov 28, 2012 at 8:48 PM, Alex Harui <ah...@adobe.com> wrote:
> ...I think the download server is just a file server on Akamai. I don't know
> what it would take to install server-side code on it, but I would much
> rather not...
Note that AFAIK an http Maven repository is just static files, you
don't need server-side code for a read-only repository.
-Bertrand
Re: AW: AW: AW: AW: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache
Flex
Posted by Alex Harui <ah...@adobe.com>.
On 11/29/12 2:43 PM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
wrote:
> Well this part should actually be a "mojo" ... that's sort of part of a
> complete plugin. What I could do, would be to sort of start off with creating
> this mojo (Without placing the code in the public Apache SVN). As soon as
> Adobe gives the ok, we would add it there.
>
> As it is possible to fragment a plugin into multiple jars, even if Adobe
> requested the mojo to remain closed source, we could deploy the mojos jar in a
> public repo and the user wouldn't see a difference.
Legal seemed ok with having the source being open once they are convinced it
gives them sufficient legal protection, so wouldn't worry about it never
being opened if we end up using it.
>
> What do the others here in the list think about this? Would this be a solution
> that you and Apache could live with? (Hopefully people are still reading this
> thread even if there are quite a lot of "AW's" in the title ;-) )
>
> Chris
>
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Donnerstag, 29. November 2012 23:28
> An: flex-dev@incubator.apache.org
> Betreff: Re: AW: AW: AW: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
>
> Yes, if we don't have to touch the Adobe packages we will be much better off.
>
> I just got tentative approval from legal, but still need approval from runtime
> product management.
>
> One important thing, legal may want you to develop this plug-in without
> checking it into any public source code repository until they have a chance to
> see it work. They may change their minds later and let us develop the plug-in
> in the open, but that's their position for now. I guess you'd give me the
> plug-in and I would get Maven working on my computer and screen-share with
> them.
>
> So, I think you can get started on this, but don't check in into Apache SVN or
> GitHub just yet.
>
> Thanks,
> -Alex
>
> On 11/29/12 1:59 PM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
> wrote:
>
>> In maven if you want to use a library or a ressource, you define a
>> dependency to a groupId, artifactId and version (Optionally even a
>> classifier). These 4 attributes define the identity of the ressource.
>> Think of the pom.xml as being something similar to the tags soldiers
>> wear around their necks. They identify the person whos waering the
>> tag. Just in case of maven there is no chain around the neck of the
>> ressource, but the link is the naming convention. I guess you will not
>> have to do anything to mavenize the Air SDKs, I allrady did most of
>> the coding needed to mavenize the content, so I would simply re-use
>> that code and do the mavenizing on the client side (I got the
>> impression that Adobe wouldn't like me providing you with a mavenized
>> zip ... even if it were nothing else than a zip containing the
>> original ,but renamed, libs just accompanied by a set of pom.xml
>> files)
>>
>> Chris
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Alex Harui [mailto:aharui@adobe.com]
>> Gesendet: Donnerstag, 29. November 2012 22:37
>> An: flex-dev@incubator.apache.org
>> Betreff: Re: AW: AW: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache
>> Flex
>>
>>
>>
>>
>> On 11/29/12 11:48 AM, "christofer.dutz@c-ware.de"
>> <ch...@c-ware.de> wrote:
>>
>>> Hi Alex,
>>>
>>> a local maven repo is on the machine the build is running ... that's
>>> one repo per machine. Think of it as a Maven-Cache. So if I run the
>>> build on my machine, the artifacts are available on that machine, but
>>> not on any other one.
>> Ah ok. I get it now.
>>>
>>> My idea was that if the build is set to "non-interactive" and the
>>> mojo detects missing runtime artifacts from Adobe, that it would
>>> output the license agreement and at the bottom output a message, that
>>> if the user accepts this agreement he has to run the build again and
>>> provide a system-property
>>> "-DIAcceptTheAdobeLicense=34854395704857204572098457024870" (The
>>> number is generated every time the mojo is run and no
>>> IAcceptTheAdobeLicense property is prvided). The generated token is
>>> saved in a place the plugin can find it again the next time it runs
>>> (temp-dir). If the token is provided in the next run, the mojo will
>>> download the stuff and deploy it on the local machine only.
>>>
>>> Ok so this is not 100% fool-proof but at least as fool-proof as
>>> creating an automated http-downloader that checks the "i agree"
>>> checkbox on the Adobe download.
>> I will try to get this approved.
>>
>> One more question about the AIR SDK zip: Why do you need pom.xml
>> files in the subfolders of the AIR SDK to run the tools in there?
>>
>> Thanks,
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: AW: AW: AW: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Well this part should actually be a "mojo" ... that's sort of part of a complete plugin. What I could do, would be to sort of start off with creating this mojo (Without placing the code in the public Apache SVN). As soon as Adobe gives the ok, we would add it there.
As it is possible to fragment a plugin into multiple jars, even if Adobe requested the mojo to remain closed source, we could deploy the mojos jar in a public repo and the user wouldn't see a difference.
What do the others here in the list think about this? Would this be a solution that you and Apache could live with? (Hopefully people are still reading this thread even if there are quite a lot of "AW's" in the title ;-) )
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Donnerstag, 29. November 2012 23:28
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Yes, if we don't have to touch the Adobe packages we will be much better off.
I just got tentative approval from legal, but still need approval from runtime product management.
One important thing, legal may want you to develop this plug-in without checking it into any public source code repository until they have a chance to see it work. They may change their minds later and let us develop the plug-in in the open, but that's their position for now. I guess you'd give me the plug-in and I would get Maven working on my computer and screen-share with them.
So, I think you can get started on this, but don't check in into Apache SVN or GitHub just yet.
Thanks,
-Alex
On 11/29/12 1:59 PM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
wrote:
> In maven if you want to use a library or a ressource, you define a
> dependency to a groupId, artifactId and version (Optionally even a
> classifier). These 4 attributes define the identity of the ressource.
> Think of the pom.xml as being something similar to the tags soldiers
> wear around their necks. They identify the person whos waering the
> tag. Just in case of maven there is no chain around the neck of the
> ressource, but the link is the naming convention. I guess you will not
> have to do anything to mavenize the Air SDKs, I allrady did most of
> the coding needed to mavenize the content, so I would simply re-use
> that code and do the mavenizing on the client side (I got the
> impression that Adobe wouldn't like me providing you with a mavenized
> zip ... even if it were nothing else than a zip containing the
> original ,but renamed, libs just accompanied by a set of pom.xml
> files)
>
> Chris
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Donnerstag, 29. November 2012 22:37
> An: flex-dev@incubator.apache.org
> Betreff: Re: AW: AW: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache
> Flex
>
>
>
>
> On 11/29/12 11:48 AM, "christofer.dutz@c-ware.de"
> <ch...@c-ware.de> wrote:
>
>> Hi Alex,
>>
>> a local maven repo is on the machine the build is running ... that's
>> one repo per machine. Think of it as a Maven-Cache. So if I run the
>> build on my machine, the artifacts are available on that machine, but
>> not on any other one.
> Ah ok. I get it now.
>>
>> My idea was that if the build is set to "non-interactive" and the
>> mojo detects missing runtime artifacts from Adobe, that it would
>> output the license agreement and at the bottom output a message, that
>> if the user accepts this agreement he has to run the build again and
>> provide a system-property
>> "-DIAcceptTheAdobeLicense=34854395704857204572098457024870" (The
>> number is generated every time the mojo is run and no
>> IAcceptTheAdobeLicense property is prvided). The generated token is
>> saved in a place the plugin can find it again the next time it runs
>> (temp-dir). If the token is provided in the next run, the mojo will
>> download the stuff and deploy it on the local machine only.
>>
>> Ok so this is not 100% fool-proof but at least as fool-proof as
>> creating an automated http-downloader that checks the "i agree"
>> checkbox on the Adobe download.
> I will try to get this approved.
>
> One more question about the AIR SDK zip: Why do you need pom.xml
> files in the subfolders of the AIR SDK to run the tools in there?
>
> Thanks,
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: [POLL] Maven and Apache Flex
Posted by Frédéric THOMAS <we...@hotmail.com>.
+10 :)
-----Message d'origine-----
From: Leif Wells
Sent: Monday, December 03, 2012 10:55 PM
To: flex-dev@incubator.apache.org
Subject: Re: [POLL] Maven and Apache Flex
Alex,
I'd like to publicly acknowledge that I would have probably blown my head
off by now if I were in your shoes and had to deal with all the issues on
the Adobe side.
Thanks for keeping things moving.
Leif
Re: [POLL] Maven and Apache Flex
Posted by Leif Wells <le...@gmail.com>.
Alex,
I'd like to publicly acknowledge that I would have probably blown my head
off by now if I were in your shoes and had to deal with all the issues on
the Adobe side.
Thanks for keeping things moving.
Leif
Re: [POLL] Maven and Apache Flex
Posted by Greg Reddin <gr...@gmail.com>.
That's good to hear. Thanks for staying with it.
Sent from my mobile device.
On Dec 3, 2012, at 12:07 PM, Alex Harui <ah...@adobe.com> wrote:
> Update:
>
> Adobe legal says we (probably Chris) can code up a mockup that runs against
> some dummy assets (as Chris suggested) in the open. Then Legal can review
> the basic flow from that mockup and decide if it will be sufficient.
>
> -Alex
>
> On 11/29/12 11:28 PM, "christofer.dutz@c-ware.de"
> <ch...@c-ware.de> wrote:
>
>> Hi Greg,
>>
>> we are not talking about the entire plugin ... just one fragment (assumably
>> not even 5% of the entire suite) that deals with downloading stuff from Adobe.
>> All the other parts of the plugin would be developed in the open :-)
>>
>> Chris
>>
>> ________________________________________
>> Von: Greg Reddin [gredbug@gmail.com]
>> Gesendet: Freitag, 30. November 2012 01:49
>> An: flex-dev@incubator.apache.org
>> Betreff: Re: [POLL] Maven and Apache Flex
>>
>> Personally I don't see any way I can support being forced to develop this in
>> private. Apache doesn't work that way. I suppose if that's the only choice
>> they give us and Chris is willing to do it on his own he can submit it to us
>> as a patch but there's no guarantee it will be accepted. For myself I'd prefer
>> to manually download the artifacts than to accept an agreement like that.
>>
>> At this point I don't guess I would veto a commit if this is what it comes to
>> but this is a horrible way to develop a plugin that is essential to many Flex
>> users. It should be developed in the open in a way that addresses everybody's
>> needs including Adobe's and the community's. This is a slap in the face to the
>> Apache Way.
>>
>> Sent from my mobile device.
>>
>> On Nov 29, 2012, at 5:01 PM, Alex Harui <ah...@adobe.com> wrote:
>>
>>> Our legal team requested a few days to consider whether they really need
>>> this developed in private. So if they come back that they want it to be
>>> private I will present this option.
>>>
>>> If you want to wait to get their answer that is fine, or you can start now
>>> but please do it in private.
>>>
>>>
>>> On 11/29/12 2:52 PM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
>>> wrote:
>>>
>>>> Another option would be to place dummy files on the Adobe download servers
>>>> (but allready with the real names) and to develop the mojo publically ... as
>>>> soon as Adobe is sattisfied with the license accepting and downloading part,
>>>> they could replace the dummy files with real ones and we could concentrate
>>>> on
>>>> "mavenizing" the donload.
>>>>
>>>> Chris
>>>>
>>>> -----Ursprüngliche Nachricht-----
>>>> Von: Justin Mclean [mailto:justinmclean@gmail.com] Im Auftrag von Justin
>>>> Mclean
>>>> Gesendet: Donnerstag, 29. November 2012 23:43
>>>> An: flex-dev@incubator.apache.org
>>>> Betreff: Re: [POLL] Maven and Apache Flex
>>>>
>>>> HI,
>>>>
>>>>> One important thing, legal may want you to develop this plug-in
>>>>> without checking it into any public source code repository until they
>>>>> have a chance to see it work.
>>>> Can you give their reasons behind this?
>>>>
>>>> Wouldn't it be better to have it worked on collaboratively in the open by
>>>> the
>>>> community?
>>>>
>>>> Thanks,
>>>> Justin
>>>
>>> --
>>> Alex Harui
>>> Flex SDK Team
>>> Adobe Systems, Inc.
>>> http://blogs.adobe.com/aharui
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
Re: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
Update:
Adobe legal says we (probably Chris) can code up a mockup that runs against
some dummy assets (as Chris suggested) in the open. Then Legal can review
the basic flow from that mockup and decide if it will be sufficient.
-Alex
On 11/29/12 11:28 PM, "christofer.dutz@c-ware.de"
<ch...@c-ware.de> wrote:
> Hi Greg,
>
> we are not talking about the entire plugin ... just one fragment (assumably
> not even 5% of the entire suite) that deals with downloading stuff from Adobe.
> All the other parts of the plugin would be developed in the open :-)
>
> Chris
>
> ________________________________________
> Von: Greg Reddin [gredbug@gmail.com]
> Gesendet: Freitag, 30. November 2012 01:49
> An: flex-dev@incubator.apache.org
> Betreff: Re: [POLL] Maven and Apache Flex
>
> Personally I don't see any way I can support being forced to develop this in
> private. Apache doesn't work that way. I suppose if that's the only choice
> they give us and Chris is willing to do it on his own he can submit it to us
> as a patch but there's no guarantee it will be accepted. For myself I'd prefer
> to manually download the artifacts than to accept an agreement like that.
>
> At this point I don't guess I would veto a commit if this is what it comes to
> but this is a horrible way to develop a plugin that is essential to many Flex
> users. It should be developed in the open in a way that addresses everybody's
> needs including Adobe's and the community's. This is a slap in the face to the
> Apache Way.
>
> Sent from my mobile device.
>
> On Nov 29, 2012, at 5:01 PM, Alex Harui <ah...@adobe.com> wrote:
>
>> Our legal team requested a few days to consider whether they really need
>> this developed in private. So if they come back that they want it to be
>> private I will present this option.
>>
>> If you want to wait to get their answer that is fine, or you can start now
>> but please do it in private.
>>
>>
>> On 11/29/12 2:52 PM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
>> wrote:
>>
>>> Another option would be to place dummy files on the Adobe download servers
>>> (but allready with the real names) and to develop the mojo publically ... as
>>> soon as Adobe is sattisfied with the license accepting and downloading part,
>>> they could replace the dummy files with real ones and we could concentrate
>>> on
>>> "mavenizing" the donload.
>>>
>>> Chris
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Justin Mclean [mailto:justinmclean@gmail.com] Im Auftrag von Justin
>>> Mclean
>>> Gesendet: Donnerstag, 29. November 2012 23:43
>>> An: flex-dev@incubator.apache.org
>>> Betreff: Re: [POLL] Maven and Apache Flex
>>>
>>> HI,
>>>
>>>> One important thing, legal may want you to develop this plug-in
>>>> without checking it into any public source code repository until they
>>>> have a chance to see it work.
>>> Can you give their reasons behind this?
>>>
>>> Wouldn't it be better to have it worked on collaboratively in the open by
>>> the
>>> community?
>>>
>>> Thanks,
>>> Justin
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
[POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Hi Greg,
we are not talking about the entire plugin ... just one fragment (assumably not even 5% of the entire suite) that deals with downloading stuff from Adobe. All the other parts of the plugin would be developed in the open :-)
Chris
________________________________________
Von: Greg Reddin [gredbug@gmail.com]
Gesendet: Freitag, 30. November 2012 01:49
An: flex-dev@incubator.apache.org
Betreff: Re: [POLL] Maven and Apache Flex
Personally I don't see any way I can support being forced to develop this in private. Apache doesn't work that way. I suppose if that's the only choice they give us and Chris is willing to do it on his own he can submit it to us as a patch but there's no guarantee it will be accepted. For myself I'd prefer to manually download the artifacts than to accept an agreement like that.
At this point I don't guess I would veto a commit if this is what it comes to but this is a horrible way to develop a plugin that is essential to many Flex users. It should be developed in the open in a way that addresses everybody's needs including Adobe's and the community's. This is a slap in the face to the Apache Way.
Sent from my mobile device.
On Nov 29, 2012, at 5:01 PM, Alex Harui <ah...@adobe.com> wrote:
> Our legal team requested a few days to consider whether they really need
> this developed in private. So if they come back that they want it to be
> private I will present this option.
>
> If you want to wait to get their answer that is fine, or you can start now
> but please do it in private.
>
>
> On 11/29/12 2:52 PM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
> wrote:
>
>> Another option would be to place dummy files on the Adobe download servers
>> (but allready with the real names) and to develop the mojo publically ... as
>> soon as Adobe is sattisfied with the license accepting and downloading part,
>> they could replace the dummy files with real ones and we could concentrate on
>> "mavenizing" the donload.
>>
>> Chris
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Justin Mclean [mailto:justinmclean@gmail.com] Im Auftrag von Justin
>> Mclean
>> Gesendet: Donnerstag, 29. November 2012 23:43
>> An: flex-dev@incubator.apache.org
>> Betreff: Re: [POLL] Maven and Apache Flex
>>
>> HI,
>>
>>> One important thing, legal may want you to develop this plug-in
>>> without checking it into any public source code repository until they
>>> have a chance to see it work.
>> Can you give their reasons behind this?
>>
>> Wouldn't it be better to have it worked on collaboratively in the open by the
>> community?
>>
>> Thanks,
>> Justin
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
Re: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
Hopefully legal will change their opinion. If not I will try to see if
there is some alternative.
I understand that software is supposed to be developed in the open at
Apache. But if the goal of the code is to meet a legal requirement and it
doesn't, it seems reasonable that traces of it shouldn't remain in the open
source world to be potentially proliferated.
-Alex
On 11/29/12 4:49 PM, "Greg Reddin" <gr...@gmail.com> wrote:
> Personally I don't see any way I can support being forced to develop this in
> private. Apache doesn't work that way. I suppose if that's the only choice
> they give us and Chris is willing to do it on his own he can submit it to us
> as a patch but there's no guarantee it will be accepted. For myself I'd prefer
> to manually download the artifacts than to accept an agreement like that.
>
> At this point I don't guess I would veto a commit if this is what it comes to
> but this is a horrible way to develop a plugin that is essential to many Flex
> users. It should be developed in the open in a way that addresses everybody's
> needs including Adobe's and the community's. This is a slap in the face to the
> Apache Way.
>
> Sent from my mobile device.
>
> On Nov 29, 2012, at 5:01 PM, Alex Harui <ah...@adobe.com> wrote:
>
>> Our legal team requested a few days to consider whether they really need
>> this developed in private. So if they come back that they want it to be
>> private I will present this option.
>>
>> If you want to wait to get their answer that is fine, or you can start now
>> but please do it in private.
>>
>>
>> On 11/29/12 2:52 PM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
>> wrote:
>>
>>> Another option would be to place dummy files on the Adobe download servers
>>> (but allready with the real names) and to develop the mojo publically ... as
>>> soon as Adobe is sattisfied with the license accepting and downloading part,
>>> they could replace the dummy files with real ones and we could concentrate
>>> on
>>> "mavenizing" the donload.
>>>
>>> Chris
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Justin Mclean [mailto:justinmclean@gmail.com] Im Auftrag von Justin
>>> Mclean
>>> Gesendet: Donnerstag, 29. November 2012 23:43
>>> An: flex-dev@incubator.apache.org
>>> Betreff: Re: [POLL] Maven and Apache Flex
>>>
>>> HI,
>>>
>>>> One important thing, legal may want you to develop this plug-in
>>>> without checking it into any public source code repository until they
>>>> have a chance to see it work.
>>> Can you give their reasons behind this?
>>>
>>> Wouldn't it be better to have it worked on collaboratively in the open by
>>> the
>>> community?
>>>
>>> Thanks,
>>> Justin
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: [POLL] Maven and Apache Flex
Posted by Greg Reddin <gr...@gmail.com>.
Personally I don't see any way I can support being forced to develop this in private. Apache doesn't work that way. I suppose if that's the only choice they give us and Chris is willing to do it on his own he can submit it to us as a patch but there's no guarantee it will be accepted. For myself I'd prefer to manually download the artifacts than to accept an agreement like that.
At this point I don't guess I would veto a commit if this is what it comes to but this is a horrible way to develop a plugin that is essential to many Flex users. It should be developed in the open in a way that addresses everybody's needs including Adobe's and the community's. This is a slap in the face to the Apache Way.
Sent from my mobile device.
On Nov 29, 2012, at 5:01 PM, Alex Harui <ah...@adobe.com> wrote:
> Our legal team requested a few days to consider whether they really need
> this developed in private. So if they come back that they want it to be
> private I will present this option.
>
> If you want to wait to get their answer that is fine, or you can start now
> but please do it in private.
>
>
> On 11/29/12 2:52 PM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
> wrote:
>
>> Another option would be to place dummy files on the Adobe download servers
>> (but allready with the real names) and to develop the mojo publically ... as
>> soon as Adobe is sattisfied with the license accepting and downloading part,
>> they could replace the dummy files with real ones and we could concentrate on
>> "mavenizing" the donload.
>>
>> Chris
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Justin Mclean [mailto:justinmclean@gmail.com] Im Auftrag von Justin
>> Mclean
>> Gesendet: Donnerstag, 29. November 2012 23:43
>> An: flex-dev@incubator.apache.org
>> Betreff: Re: [POLL] Maven and Apache Flex
>>
>> HI,
>>
>>> One important thing, legal may want you to develop this plug-in
>>> without checking it into any public source code repository until they
>>> have a chance to see it work.
>> Can you give their reasons behind this?
>>
>> Wouldn't it be better to have it worked on collaboratively in the open by the
>> community?
>>
>> Thanks,
>> Justin
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
Re: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
Our legal team requested a few days to consider whether they really need
this developed in private. So if they come back that they want it to be
private I will present this option.
If you want to wait to get their answer that is fine, or you can start now
but please do it in private.
On 11/29/12 2:52 PM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
wrote:
> Another option would be to place dummy files on the Adobe download servers
> (but allready with the real names) and to develop the mojo publically ... as
> soon as Adobe is sattisfied with the license accepting and downloading part,
> they could replace the dummy files with real ones and we could concentrate on
> "mavenizing" the donload.
>
> Chris
>
> -----Ursprüngliche Nachricht-----
> Von: Justin Mclean [mailto:justinmclean@gmail.com] Im Auftrag von Justin
> Mclean
> Gesendet: Donnerstag, 29. November 2012 23:43
> An: flex-dev@incubator.apache.org
> Betreff: Re: [POLL] Maven and Apache Flex
>
> HI,
>
>> One important thing, legal may want you to develop this plug-in
>> without checking it into any public source code repository until they
>> have a chance to see it work.
> Can you give their reasons behind this?
>
> Wouldn't it be better to have it worked on collaboratively in the open by the
> community?
>
> Thanks,
> Justin
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
[POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Another option would be to place dummy files on the Adobe download servers (but allready with the real names) and to develop the mojo publically ... as soon as Adobe is sattisfied with the license accepting and downloading part, they could replace the dummy files with real ones and we could concentrate on "mavenizing" the donload.
Chris
-----Ursprüngliche Nachricht-----
Von: Justin Mclean [mailto:justinmclean@gmail.com] Im Auftrag von Justin Mclean
Gesendet: Donnerstag, 29. November 2012 23:43
An: flex-dev@incubator.apache.org
Betreff: Re: [POLL] Maven and Apache Flex
HI,
> One important thing, legal may want you to develop this plug-in
> without checking it into any public source code repository until they
> have a chance to see it work.
Can you give their reasons behind this?
Wouldn't it be better to have it worked on collaboratively in the open by the community?
Thanks,
Justin
Re: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
On 11/29/12 2:43 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
> HI,
>
>> One important thing, legal may want you to develop this plug-in without
>> checking it into any public source code repository until they have a chance
>> to see it work.
> Can you give their reasons behind this?
If legal decides the plug-in doesn't give sufficient legal protection to
Adobe and we decide to abandon it, there is no way to eradicate it from
existence.
>
> Wouldn't it be better to have it worked on collaboratively in the open by the
> community?
Sure, from the Apache perspective.
>
> Thanks,
> Justin
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: [POLL] Maven and Apache Flex
Posted by Justin Mclean <ju...@classsoftware.com>.
HI,
> One important thing, legal may want you to develop this plug-in without
> checking it into any public source code repository until they have a chance
> to see it work.
Can you give their reasons behind this?
Wouldn't it be better to have it worked on collaboratively in the open by the community?
Thanks,
Justin
Re: AW: AW: AW: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
Yes, if we don't have to touch the Adobe packages we will be much better
off.
I just got tentative approval from legal, but still need approval from
runtime product management.
One important thing, legal may want you to develop this plug-in without
checking it into any public source code repository until they have a chance
to see it work. They may change their minds later and let us develop the
plug-in in the open, but that's their position for now. I guess you'd give
me the plug-in and I would get Maven working on my computer and screen-share
with them.
So, I think you can get started on this, but don't check in into Apache SVN
or GitHub just yet.
Thanks,
-Alex
On 11/29/12 1:59 PM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
wrote:
> In maven if you want to use a library or a ressource, you define a dependency
> to a groupId, artifactId and version (Optionally even a classifier). These 4
> attributes define the identity of the ressource. Think of the pom.xml as being
> something similar to the tags soldiers wear around their necks. They identify
> the person whos waering the tag. Just in case of maven there is no chain
> around the neck of the ressource, but the link is the naming convention. I
> guess you will not have to do anything to mavenize the Air SDKs, I allrady did
> most of the coding needed to mavenize the content, so I would simply re-use
> that code and do the mavenizing on the client side (I got the impression that
> Adobe wouldn't like me providing you with a mavenized zip ... even if it were
> nothing else than a zip containing the original ,but renamed, libs just
> accompanied by a set of pom.xml files)
>
> Chris
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Donnerstag, 29. November 2012 22:37
> An: flex-dev@incubator.apache.org
> Betreff: Re: AW: AW: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
>
>
>
>
> On 11/29/12 11:48 AM, "christofer.dutz@c-ware.de"
> <ch...@c-ware.de> wrote:
>
>> Hi Alex,
>>
>> a local maven repo is on the machine the build is running ... that's
>> one repo per machine. Think of it as a Maven-Cache. So if I run the
>> build on my machine, the artifacts are available on that machine, but
>> not on any other one.
> Ah ok. I get it now.
>>
>> My idea was that if the build is set to "non-interactive" and the mojo
>> detects missing runtime artifacts from Adobe, that it would output the
>> license agreement and at the bottom output a message, that if the user
>> accepts this agreement he has to run the build again and provide a
>> system-property
>> "-DIAcceptTheAdobeLicense=34854395704857204572098457024870" (The
>> number is generated every time the mojo is run and no
>> IAcceptTheAdobeLicense property is prvided). The generated token is
>> saved in a place the plugin can find it again the next time it runs
>> (temp-dir). If the token is provided in the next run, the mojo will download
>> the stuff and deploy it on the local machine only.
>>
>> Ok so this is not 100% fool-proof but at least as fool-proof as
>> creating an automated http-downloader that checks the "i agree"
>> checkbox on the Adobe download.
> I will try to get this approved.
>
> One more question about the AIR SDK zip: Why do you need pom.xml files in the
> subfolders of the AIR SDK to run the tools in there?
>
> Thanks,
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: AW: AW: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
In maven if you want to use a library or a ressource, you define a dependency to a groupId, artifactId and version (Optionally even a classifier). These 4 attributes define the identity of the ressource. Think of the pom.xml as being something similar to the tags soldiers wear around their necks. They identify the person whos waering the tag. Just in case of maven there is no chain around the neck of the ressource, but the link is the naming convention. I guess you will not have to do anything to mavenize the Air SDKs, I allrady did most of the coding needed to mavenize the content, so I would simply re-use that code and do the mavenizing on the client side (I got the impression that Adobe wouldn't like me providing you with a mavenized zip ... even if it were nothing else than a zip containing the original ,but renamed, libs just accompanied by a set of pom.xml files)
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Donnerstag, 29. November 2012 22:37
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
On 11/29/12 11:48 AM, "christofer.dutz@c-ware.de"
<ch...@c-ware.de> wrote:
> Hi Alex,
>
> a local maven repo is on the machine the build is running ... that's
> one repo per machine. Think of it as a Maven-Cache. So if I run the
> build on my machine, the artifacts are available on that machine, but
> not on any other one.
Ah ok. I get it now.
>
> My idea was that if the build is set to "non-interactive" and the mojo
> detects missing runtime artifacts from Adobe, that it would output the
> license agreement and at the bottom output a message, that if the user
> accepts this agreement he has to run the build again and provide a
> system-property
> "-DIAcceptTheAdobeLicense=34854395704857204572098457024870" (The
> number is generated every time the mojo is run and no
> IAcceptTheAdobeLicense property is prvided). The generated token is
> saved in a place the plugin can find it again the next time it runs (temp-dir). If the token is provided in the next run, the mojo will download the stuff and deploy it on the local machine only.
>
> Ok so this is not 100% fool-proof but at least as fool-proof as
> creating an automated http-downloader that checks the "i agree"
> checkbox on the Adobe download.
I will try to get this approved.
One more question about the AIR SDK zip: Why do you need pom.xml files in the subfolders of the AIR SDK to run the tools in there?
Thanks,
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: AW: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
On 11/29/12 11:48 AM, "christofer.dutz@c-ware.de"
<ch...@c-ware.de> wrote:
> Hi Alex,
>
> a local maven repo is on the machine the build is running ... that's one repo
> per machine. Think of it as a Maven-Cache. So if I run the build on my
> machine, the artifacts are available on that machine, but not on any other
> one.
Ah ok. I get it now.
>
> My idea was that if the build is set to "non-interactive" and the mojo detects
> missing runtime artifacts from Adobe, that it would output the license
> agreement and at the bottom output a message, that if the user accepts this
> agreement he has to run the build again and provide a system-property
> "-DIAcceptTheAdobeLicense=34854395704857204572098457024870" (The number is
> generated every time the mojo is run and no IAcceptTheAdobeLicense property is
> prvided). The generated token is saved in a place the plugin can find it again
> the next time it runs (temp-dir). If the token is provided in the next run,
> the mojo will download the stuff and deploy it on the local machine only.
>
> Ok so this is not 100% fool-proof but at least as fool-proof as creating an
> automated http-downloader that checks the "i agree" checkbox on the Adobe
> download.
I will try to get this approved.
One more question about the AIR SDK zip: Why do you need pom.xml files in
the subfolders of the AIR SDK to run the tools in there?
Thanks,
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: AW: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Hi Alex,
a local maven repo is on the machine the build is running ... that's one repo per machine. Think of it as a Maven-Cache. So if I run the build on my machine, the artifacts are available on that machine, but not on any other one.
My idea was that if the build is set to "non-interactive" and the mojo detects missing runtime artifacts from Adobe, that it would output the license agreement and at the bottom output a message, that if the user accepts this agreement he has to run the build again and provide a system-property "-DIAcceptTheAdobeLicense=34854395704857204572098457024870" (The number is generated every time the mojo is run and no IAcceptTheAdobeLicense property is prvided). The generated token is saved in a place the plugin can find it again the next time it runs (temp-dir). If the token is provided in the next run, the mojo will download the stuff and deploy it on the local machine only.
Ok so this is not 100% fool-proof but at least as fool-proof as creating an automated http-downloader that checks the "i agree" checkbox on the Adobe download.
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Donnerstag, 29. November 2012 20:39
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
On 11/29/12 11:11 AM, "christofer.dutz@c-ware.de"
<ch...@c-ware.de> wrote:
> No you would not leave the key under the doormat ... the token would
> be generated for every request and would be different every time you
> use it. If the token wouldn't change, there would be no point in
> implementing this that way.
Maybe I'm not understanding how the token works. We will have to document the non-interactive mode. Why wouldn't everyone use it to bypass the license acceptance?
>
> I was more thinking of headless CI servers. Such as the Apache Flex
> Build-Servers. I couln't see a way to allow interaction in those cases.
I'm also thinking of headless CI servers. But I would expect that before a Maven script gets submitted to a CI server some developer has run a Maven script on his own computer which forced him to accept the license and then downloaded the artifacts to the same local repo the CI server will be using.
Then the CI server will never need to accept a license, so there should be no need for a non-interactive mode.
>
> Chri
>
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Donnerstag, 29. November 2012 19:22
> An: flex-dev@incubator.apache.org
> Betreff: Re: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
>
> Hi Chris,
>
> I can ask, but the non-interactive mode sounds like leaving the key
> under the doormat and telling everyone where it is.
>
> It would seem to me that you would never need a non-interactive mode.
> Once anyone from your company runs the mojo, wouldn't the artifacts be
> in the local repo after that so for any CI server the mojo wouldn't do
> anything and just keep on going?
>
> Thanks,
> -Alex
>
> On 11/29/12 10:02 AM, "christofer.dutz@c-ware.de"
> <ch...@c-ware.de> wrote:
>
>> Hi Alex,
>>
>> Oh ... I already had completely abandoned all hope of being able to
>> download without a custom downloader ... so that's no big deal :-)
>>
>> There is no need for the browser plugin. The projector seems to be
>> enough (Think it doesn't even have to be the debugger.
>>
>> So let us focus on a plugin that takes care of presenting the license
>> agreement tot he user and downloading the stuff after the user accepted it.
>> Would this be a valid approach?
>> I wrote down the workflow of such a plugin in the
>> maven-plugin-brainstorming page oft he Flex wiki:
>> https://cwiki.apache.org/confluence/display/FLEX/deploy-artifacts-moj
>> o Would you and Adobe agree to such a solution?
>>
>> Chris
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Alex Harui [mailto:aharui@adobe.com]
>> Gesendet: Donnerstag, 29. November 2012 18:19
>> An: flex-dev@incubator.apache.org
>> Betreff: Re: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
>>
>>
>>
>>
>> On 11/28/12 11:22 PM, "christofer.dutz@c-ware.de"
>> <ch...@c-ware.de> wrote:
>>
>>> Hi Alex,
>>>
>>> well regarding the Flashplayer ... is is actually needed during the
>>> build. Not for actually building the SWF, but more for running the
>>> unit-tests.
>> Rats, I hadn't noticed that you needed the Flash runtimes in Maven.
>> It is always the standalone projector debuggers? Or are there
>> browser plugins?
>>
>> There is definitely no way I can imagine Adobe allowing the runtime
>> to be downloaded without user acceptance, so I guess the maven plugin
>> that accepts the license will definitely be required.
>>>
>>> Ok ... I would then suggest that we decide a fixed url pattern in
>>> which I could build a tool to automatically download zip files of
>>> flash-runtime (player + playerglobal) and air-runtime (sdk
>>> containing
>>> airglobal) for the different versions and platforms. The tool would
>>> then deal with mavenizing them on the client side. What would be
>>> good though, if all the zips had the same structure. Especially the
>>> flashplayer did have multiple names in the different Flex SDKs it
>>> would be cool if they were all called "flashplayer" ...
>>> at least this would make my life a lot easier :-). In this case you
>>> don't need any poms at all ... after all writing a pom to download a
>>> zip-file that you need to unpack an process before you can use it's
>>> content doesn't sound very Maven like to me.
>>>
>>> Would this be possible?
>> Well, I would have to check with the runtime folks if we start
>> messing with the packaging they distribute. Right now I think you
>> are talking about four different downloads from the Adobe site
>> (playerglobal, FlashPlayer, AIR SDK, AIR Desktop Runtime). Can we leave it at those four?
>>
>> Regarding their names, I would have to see if we can get permission
>> to change packaging names. I'm pretty sure I can choose folder names
>> for storing them if that helps. Would it work if Adobe had an .xml
>> file somewhere that mapped some id and version to the actual package names?
>>
>> Since you say you could write a tool, that sounds different from the
>> maven plugin that is winning in the poll, is that true?
>>
>> I'm not sure what you have to process in an AIR SDK after you unpack
>> it. Do you really need to put individual pom.xmls in the AIR SDK
>> tree? IMO, they are all interdependent. I don't think you should be
>> mixing pieces from different versions of the AIR SDK.
>>
>> We are all Maven-ignorant at Adobe, so for any extra piece of work we
>> have to do, it will help you can explain how it will improve adoption
>> of Apache Flex.
>>
>> Thanks,
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
On 11/29/12 11:11 AM, "christofer.dutz@c-ware.de"
<ch...@c-ware.de> wrote:
> No you would not leave the key under the doormat ... the token would be
> generated for every request and would be different every time you use it. If
> the token wouldn't change, there would be no point in implementing this that
> way.
Maybe I'm not understanding how the token works. We will have to document
the non-interactive mode. Why wouldn't everyone use it to bypass the
license acceptance?
>
> I was more thinking of headless CI servers. Such as the Apache Flex
> Build-Servers. I couln't see a way to allow interaction in those cases.
I'm also thinking of headless CI servers. But I would expect that before a
Maven script gets submitted to a CI server some developer has run a Maven
script on his own computer which forced him to accept the license and then
downloaded the artifacts to the same local repo the CI server will be using.
Then the CI server will never need to accept a license, so there should be
no need for a non-interactive mode.
>
> Chri
>
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Donnerstag, 29. November 2012 19:22
> An: flex-dev@incubator.apache.org
> Betreff: Re: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
>
> Hi Chris,
>
> I can ask, but the non-interactive mode sounds like leaving the key under the
> doormat and telling everyone where it is.
>
> It would seem to me that you would never need a non-interactive mode. Once
> anyone from your company runs the mojo, wouldn't the artifacts be in the local
> repo after that so for any CI server the mojo wouldn't do anything and just
> keep on going?
>
> Thanks,
> -Alex
>
> On 11/29/12 10:02 AM, "christofer.dutz@c-ware.de"
> <ch...@c-ware.de> wrote:
>
>> Hi Alex,
>>
>> Oh ... I already had completely abandoned all hope of being able to
>> download without a custom downloader ... so that's no big deal :-)
>>
>> There is no need for the browser plugin. The projector seems to be
>> enough (Think it doesn't even have to be the debugger.
>>
>> So let us focus on a plugin that takes care of presenting the license
>> agreement tot he user and downloading the stuff after the user accepted it.
>> Would this be a valid approach?
>> I wrote down the workflow of such a plugin in the
>> maven-plugin-brainstorming page oft he Flex wiki:
>> https://cwiki.apache.org/confluence/display/FLEX/deploy-artifacts-mojo
>> Would you and Adobe agree to such a solution?
>>
>> Chris
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Alex Harui [mailto:aharui@adobe.com]
>> Gesendet: Donnerstag, 29. November 2012 18:19
>> An: flex-dev@incubator.apache.org
>> Betreff: Re: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
>>
>>
>>
>>
>> On 11/28/12 11:22 PM, "christofer.dutz@c-ware.de"
>> <ch...@c-ware.de> wrote:
>>
>>> Hi Alex,
>>>
>>> well regarding the Flashplayer ... is is actually needed during the
>>> build. Not for actually building the SWF, but more for running the
>>> unit-tests.
>> Rats, I hadn't noticed that you needed the Flash runtimes in Maven.
>> It is always the standalone projector debuggers? Or are there browser
>> plugins?
>>
>> There is definitely no way I can imagine Adobe allowing the runtime to
>> be downloaded without user acceptance, so I guess the maven plugin
>> that accepts the license will definitely be required.
>>>
>>> Ok ... I would then suggest that we decide a fixed url pattern in
>>> which I could build a tool to automatically download zip files of
>>> flash-runtime (player + playerglobal) and air-runtime (sdk containing
>>> airglobal) for the different versions and platforms. The tool would
>>> then deal with mavenizing them on the client side. What would be good
>>> though, if all the zips had the same structure. Especially the
>>> flashplayer did have multiple names in the different Flex SDKs it
>>> would be cool if they were all called "flashplayer" ...
>>> at least this would make my life a lot easier :-). In this case you
>>> don't need any poms at all ... after all writing a pom to download a
>>> zip-file that you need to unpack an process before you can use it's
>>> content doesn't sound very Maven like to me.
>>>
>>> Would this be possible?
>> Well, I would have to check with the runtime folks if we start messing
>> with the packaging they distribute. Right now I think you are talking
>> about four different downloads from the Adobe site (playerglobal,
>> FlashPlayer, AIR SDK, AIR Desktop Runtime). Can we leave it at those four?
>>
>> Regarding their names, I would have to see if we can get permission to
>> change packaging names. I'm pretty sure I can choose folder names for
>> storing them if that helps. Would it work if Adobe had an .xml file
>> somewhere that mapped some id and version to the actual package names?
>>
>> Since you say you could write a tool, that sounds different from the
>> maven plugin that is winning in the poll, is that true?
>>
>> I'm not sure what you have to process in an AIR SDK after you unpack
>> it. Do you really need to put individual pom.xmls in the AIR SDK
>> tree? IMO, they are all interdependent. I don't think you should be
>> mixing pieces from different versions of the AIR SDK.
>>
>> We are all Maven-ignorant at Adobe, so for any extra piece of work we
>> have to do, it will help you can explain how it will improve adoption of
>> Apache Flex.
>>
>> Thanks,
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
No you would not leave the key under the doormat ... the token would be generated for every request and would be different every time you use it. If the token wouldn't change, there would be no point in implementing this that way.
I was more thinking of headless CI servers. Such as the Apache Flex Build-Servers. I couln't see a way to allow interaction in those cases.
Chri
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Donnerstag, 29. November 2012 19:22
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Hi Chris,
I can ask, but the non-interactive mode sounds like leaving the key under the doormat and telling everyone where it is.
It would seem to me that you would never need a non-interactive mode. Once anyone from your company runs the mojo, wouldn't the artifacts be in the local repo after that so for any CI server the mojo wouldn't do anything and just keep on going?
Thanks,
-Alex
On 11/29/12 10:02 AM, "christofer.dutz@c-ware.de"
<ch...@c-ware.de> wrote:
> Hi Alex,
>
> Oh ... I already had completely abandoned all hope of being able to
> download without a custom downloader ... so that's no big deal :-)
>
> There is no need for the browser plugin. The projector seems to be
> enough (Think it doesn't even have to be the debugger.
>
> So let us focus on a plugin that takes care of presenting the license
> agreement tot he user and downloading the stuff after the user accepted it.
> Would this be a valid approach?
> I wrote down the workflow of such a plugin in the
> maven-plugin-brainstorming page oft he Flex wiki:
> https://cwiki.apache.org/confluence/display/FLEX/deploy-artifacts-mojo
> Would you and Adobe agree to such a solution?
>
> Chris
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Donnerstag, 29. November 2012 18:19
> An: flex-dev@incubator.apache.org
> Betreff: Re: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
>
>
>
>
> On 11/28/12 11:22 PM, "christofer.dutz@c-ware.de"
> <ch...@c-ware.de> wrote:
>
>> Hi Alex,
>>
>> well regarding the Flashplayer ... is is actually needed during the
>> build. Not for actually building the SWF, but more for running the
>> unit-tests.
> Rats, I hadn't noticed that you needed the Flash runtimes in Maven.
> It is always the standalone projector debuggers? Or are there browser plugins?
>
> There is definitely no way I can imagine Adobe allowing the runtime to
> be downloaded without user acceptance, so I guess the maven plugin
> that accepts the license will definitely be required.
>>
>> Ok ... I would then suggest that we decide a fixed url pattern in
>> which I could build a tool to automatically download zip files of
>> flash-runtime (player + playerglobal) and air-runtime (sdk containing
>> airglobal) for the different versions and platforms. The tool would
>> then deal with mavenizing them on the client side. What would be good
>> though, if all the zips had the same structure. Especially the
>> flashplayer did have multiple names in the different Flex SDKs it
>> would be cool if they were all called "flashplayer" ...
>> at least this would make my life a lot easier :-). In this case you
>> don't need any poms at all ... after all writing a pom to download a
>> zip-file that you need to unpack an process before you can use it's
>> content doesn't sound very Maven like to me.
>>
>> Would this be possible?
> Well, I would have to check with the runtime folks if we start messing
> with the packaging they distribute. Right now I think you are talking
> about four different downloads from the Adobe site (playerglobal,
> FlashPlayer, AIR SDK, AIR Desktop Runtime). Can we leave it at those four?
>
> Regarding their names, I would have to see if we can get permission to
> change packaging names. I'm pretty sure I can choose folder names for
> storing them if that helps. Would it work if Adobe had an .xml file
> somewhere that mapped some id and version to the actual package names?
>
> Since you say you could write a tool, that sounds different from the
> maven plugin that is winning in the poll, is that true?
>
> I'm not sure what you have to process in an AIR SDK after you unpack
> it. Do you really need to put individual pom.xmls in the AIR SDK
> tree? IMO, they are all interdependent. I don't think you should be
> mixing pieces from different versions of the AIR SDK.
>
> We are all Maven-ignorant at Adobe, so for any extra piece of work we
> have to do, it will help you can explain how it will improve adoption of Apache Flex.
>
> Thanks,
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
Hi Chris,
I can ask, but the non-interactive mode sounds like leaving the key under
the doormat and telling everyone where it is.
It would seem to me that you would never need a non-interactive mode. Once
anyone from your company runs the mojo, wouldn't the artifacts be in the
local repo after that so for any CI server the mojo wouldn't do anything and
just keep on going?
Thanks,
-Alex
On 11/29/12 10:02 AM, "christofer.dutz@c-ware.de"
<ch...@c-ware.de> wrote:
> Hi Alex,
>
> Oh ... I already had completely abandoned all hope of being able to download
> without a custom downloader ... so that's no big deal :-)
>
> There is no need for the browser plugin. The projector seems to be enough
> (Think it doesn't even have to be the debugger.
>
> So let us focus on a plugin that takes care of presenting the license
> agreement tot he user and downloading the stuff after the user accepted it.
> Would this be a valid approach?
> I wrote down the workflow of such a plugin in the maven-plugin-brainstorming
> page oft he Flex wiki:
> https://cwiki.apache.org/confluence/display/FLEX/deploy-artifacts-mojo
> Would you and Adobe agree to such a solution?
>
> Chris
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Donnerstag, 29. November 2012 18:19
> An: flex-dev@incubator.apache.org
> Betreff: Re: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
>
>
>
>
> On 11/28/12 11:22 PM, "christofer.dutz@c-ware.de"
> <ch...@c-ware.de> wrote:
>
>> Hi Alex,
>>
>> well regarding the Flashplayer ... is is actually needed during the
>> build. Not for actually building the SWF, but more for running the
>> unit-tests.
> Rats, I hadn't noticed that you needed the Flash runtimes in Maven. It is
> always the standalone projector debuggers? Or are there browser plugins?
>
> There is definitely no way I can imagine Adobe allowing the runtime to be
> downloaded without user acceptance, so I guess the maven plugin that accepts
> the license will definitely be required.
>>
>> Ok ... I would then suggest that we decide a fixed url pattern in
>> which I could build a tool to automatically download zip files of
>> flash-runtime (player + playerglobal) and air-runtime (sdk containing
>> airglobal) for the different versions and platforms. The tool would
>> then deal with mavenizing them on the client side. What would be good
>> though, if all the zips had the same structure. Especially the
>> flashplayer did have multiple names in the different Flex SDKs it would be
>> cool if they were all called "flashplayer" ...
>> at least this would make my life a lot easier :-). In this case you
>> don't need any poms at all ... after all writing a pom to download a
>> zip-file that you need to unpack an process before you can use it's
>> content doesn't sound very Maven like to me.
>>
>> Would this be possible?
> Well, I would have to check with the runtime folks if we start messing with
> the packaging they distribute. Right now I think you are talking about four
> different downloads from the Adobe site (playerglobal, FlashPlayer, AIR SDK,
> AIR Desktop Runtime). Can we leave it at those four?
>
> Regarding their names, I would have to see if we can get permission to change
> packaging names. I'm pretty sure I can choose folder names for storing them
> if that helps. Would it work if Adobe had an .xml file somewhere that mapped
> some id and version to the actual package names?
>
> Since you say you could write a tool, that sounds different from the maven
> plugin that is winning in the poll, is that true?
>
> I'm not sure what you have to process in an AIR SDK after you unpack it. Do
> you really need to put individual pom.xmls in the AIR SDK tree? IMO, they are
> all interdependent. I don't think you should be mixing pieces from different
> versions of the AIR SDK.
>
> We are all Maven-ignorant at Adobe, so for any extra piece of work we have to
> do, it will help you can explain how it will improve adoption of Apache Flex.
>
> Thanks,
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Hi Alex,
Oh ... I already had completely abandoned all hope of being able to download without a custom downloader ... so that's no big deal :-)
There is no need for the browser plugin. The projector seems to be enough (Think it doesn't even have to be the debugger.
So let us focus on a plugin that takes care of presenting the license agreement tot he user and downloading the stuff after the user accepted it. Would this be a valid approach?
I wrote down the workflow of such a plugin in the maven-plugin-brainstorming page oft he Flex wiki: https://cwiki.apache.org/confluence/display/FLEX/deploy-artifacts-mojo
Would you and Adobe agree to such a solution?
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Donnerstag, 29. November 2012 18:19
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
On 11/28/12 11:22 PM, "christofer.dutz@c-ware.de"
<ch...@c-ware.de> wrote:
> Hi Alex,
>
> well regarding the Flashplayer ... is is actually needed during the
> build. Not for actually building the SWF, but more for running the unit-tests.
Rats, I hadn't noticed that you needed the Flash runtimes in Maven. It is always the standalone projector debuggers? Or are there browser plugins?
There is definitely no way I can imagine Adobe allowing the runtime to be downloaded without user acceptance, so I guess the maven plugin that accepts the license will definitely be required.
>
> Ok ... I would then suggest that we decide a fixed url pattern in
> which I could build a tool to automatically download zip files of
> flash-runtime (player + playerglobal) and air-runtime (sdk containing
> airglobal) for the different versions and platforms. The tool would
> then deal with mavenizing them on the client side. What would be good
> though, if all the zips had the same structure. Especially the
> flashplayer did have multiple names in the different Flex SDKs it would be cool if they were all called "flashplayer" ...
> at least this would make my life a lot easier :-). In this case you
> don't need any poms at all ... after all writing a pom to download a
> zip-file that you need to unpack an process before you can use it's
> content doesn't sound very Maven like to me.
>
> Would this be possible?
Well, I would have to check with the runtime folks if we start messing with the packaging they distribute. Right now I think you are talking about four different downloads from the Adobe site (playerglobal, FlashPlayer, AIR SDK, AIR Desktop Runtime). Can we leave it at those four?
Regarding their names, I would have to see if we can get permission to change packaging names. I'm pretty sure I can choose folder names for storing them if that helps. Would it work if Adobe had an .xml file somewhere that mapped some id and version to the actual package names?
Since you say you could write a tool, that sounds different from the maven plugin that is winning in the poll, is that true?
I'm not sure what you have to process in an AIR SDK after you unpack it. Do you really need to put individual pom.xmls in the AIR SDK tree? IMO, they are all interdependent. I don't think you should be mixing pieces from different versions of the AIR SDK.
We are all Maven-ignorant at Adobe, so for any extra piece of work we have to do, it will help you can explain how it will improve adoption of Apache Flex.
Thanks,
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
On 11/30/12 9:29 AM, "Omar Gonzalez" <om...@gmail.com> wrote:
> On Fri, Nov 30, 2012 at 9:23 AM, Alex Harui <ah...@adobe.com> wrote:
>
>
>> Anyway, I would like your thoughts on Adobe Legal's desire to review the
>> way
>> the code will work before it gets checked into SVN.
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>>
>
> Just thinking out loud here as I don't really know the level of review
> Adobe Legal requires to make their assessments...
>
> But, would it be sufficient for Adobe Legal if they were provided a
> sequence diagram to explain how the code would work? We could create the
> diagram and refine it on the mailing list and once its ready have Adobe
> Legal take a look. If the assumptions/design in the diagram are OK then we
> can continue with code development in the open in Apache repos?
It might be sufficient, but I think they want to see it actually run. Many
sequence diagrams never actually get implemented in the way they are drawn
up. But it doesn't have to be complete or even actually download anything,
just enough to see that you can stop maven and ask a question and abort if
the answer is no, and in the case of non-interactive mode that there isn't
some easy way around it. Once they see that, I'm pretty sure it can be
finished in the open. And there's still a chance that when I ask them again
on Monday they will have relaxed their position.
I haven't looked to see if there is any Apache precedence for this kind of
issue. It would seem to me that if some of us were discussing on the list
about adding some feature and someone else lurking on the list spoke up and
said "hey, I have a patent/copyright on stuff like that and I'm not willing
to donate it", that we might also give them a private copy of early code to
review to see if they would have objections.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by Omar Gonzalez <om...@gmail.com>.
On Fri, Nov 30, 2012 at 9:23 AM, Alex Harui <ah...@adobe.com> wrote:
> Anyway, I would like your thoughts on Adobe Legal's desire to review the
> way
> the code will work before it gets checked into SVN.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Just thinking out loud here as I don't really know the level of review
Adobe Legal requires to make their assessments...
But, would it be sufficient for Adobe Legal if they were provided a
sequence diagram to explain how the code would work? We could create the
diagram and refine it on the mailing list and once its ready have Adobe
Legal take a look. If the assumptions/design in the diagram are OK then we
can continue with code development in the open in Apache repos?
Just a thought...
-omar
Re: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Fri, Nov 30, 2012 at 6:49 PM, Alex Harui <ah...@adobe.com> wrote:
> ...It appears that Adobe doesn't want to invest in a login infrastructure, they
> just want you to have made one easy positive action. I think I see that a
> lot when downloading stuff from other places as well....
You might then just require users to type something like "I agree with
the conditions of http://example.com/foo" somewhere before being able
to download.
-Bertrand
Re: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
On 11/30/12 9:41 AM, "Bertrand Delacretaz" <bd...@apache.org> wrote:
> On Fri, Nov 30, 2012 at 6:23 PM, Alex Harui <ah...@adobe.com> wrote:
>> ...Anyway, I would like your thoughts on Adobe Legal's desire to review the
>> way
>> the code will work before it gets checked into SVN....
>
> My opinion is that if someone requires people to accept a license
> agreement before downloading stuff, it's a server-side problem.
> Whatever client tool is used, if the server exposes the content via
> http without credentials and a secure connection, it's very easy to
> bypass the client.
>
> The way Oracle solves that for Java is that the VMs that require
> accepting something are only available via a web page where you have
> to login and click through an agreement - that's not fun, but I'm not
> sure there's a better way if the owner of those bits insists on
> *people* agreeing to something before downloading.
>
It appears that Adobe doesn't want to invest in a login infrastructure, they
just want you to have made one easy positive action. I think I see that a
lot when downloading stuff from other places as well.
> I don't think the "develop the secret bits in a hidden place" makes
> sense in a world where javap exists ;-)
I don't think Adobe never wants the code to be open. They just want to make
sure that it meets their legal requirements before it gets opened.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Fri, Nov 30, 2012 at 6:23 PM, Alex Harui <ah...@adobe.com> wrote:
> ...Anyway, I would like your thoughts on Adobe Legal's desire to review the way
> the code will work before it gets checked into SVN....
My opinion is that if someone requires people to accept a license
agreement before downloading stuff, it's a server-side problem.
Whatever client tool is used, if the server exposes the content via
http without credentials and a secure connection, it's very easy to
bypass the client.
The way Oracle solves that for Java is that the VMs that require
accepting something are only available via a web page where you have
to login and click through an agreement - that's not fun, but I'm not
sure there's a better way if the owner of those bits insists on
*people* agreeing to something before downloading.
I don't think the "develop the secret bits in a hidden place" makes
sense in a world where javap exists ;-)
-Bertrand
Re: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by Dave Fisher <da...@comcast.net>.
Sent from my iPhone
On Nov 30, 2012, at 4:07 AM, Bertrand Delacretaz <bd...@apache.org> wrote:
> On Thu, Nov 29, 2012 at 6:18 PM, Alex Harui <ah...@adobe.com> wrote:
>> ...We are all Maven-ignorant at Adobe...
>
> Huh? There's lots of Adobe folks involved in Apache Jackrabbit, Felix,
> Sling and other projects [1] which are almost all built using Maven.
>
> (not that it matters for this discussion, but the generalization looks
> wrong to me ;-)
Adobe CQ5 is a very fine looking product! ;-)
Regards,
Dave
>
> -Bertrand
>
> [1] http://www.adobe.com/devnet/opensource.html
Re: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
On 11/30/12 1:07 AM, "Bertrand Delacretaz" <bd...@apache.org> wrote:
> On Thu, Nov 29, 2012 at 6:18 PM, Alex Harui <ah...@adobe.com> wrote:
>> ...We are all Maven-ignorant at Adobe...
>
> Huh? There's lots of Adobe folks involved in Apache Jackrabbit, Felix,
> Sling and other projects [1] which are almost all built using Maven.
>
> (not that it matters for this discussion, but the generalization looks
> wrong to me ;-)
>
> -Bertrand
>
> [1] http://www.adobe.com/devnet/opensource.html
Yes, my apologies. I should have just said "the Adobe folks working on
getting the Flash stuff under Maven".
Anyway, I would like your thoughts on Adobe Legal's desire to review the way
the code will work before it gets checked into SVN.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Thu, Nov 29, 2012 at 6:18 PM, Alex Harui <ah...@adobe.com> wrote:
> ...We are all Maven-ignorant at Adobe...
Huh? There's lots of Adobe folks involved in Apache Jackrabbit, Felix,
Sling and other projects [1] which are almost all built using Maven.
(not that it matters for this discussion, but the generalization looks
wrong to me ;-)
-Bertrand
[1] http://www.adobe.com/devnet/opensource.html
Re: AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
On 11/28/12 11:22 PM, "christofer.dutz@c-ware.de"
<ch...@c-ware.de> wrote:
> Hi Alex,
>
> well regarding the Flashplayer ... is is actually needed during the build. Not
> for actually building the SWF, but more for running the unit-tests.
Rats, I hadn't noticed that you needed the Flash runtimes in Maven. It is
always the standalone projector debuggers? Or are there browser plugins?
There is definitely no way I can imagine Adobe allowing the runtime to be
downloaded without user acceptance, so I guess the maven plugin that accepts
the license will definitely be required.
>
> Ok ... I would then suggest that we decide a fixed url pattern in which I
> could build a tool to automatically download zip files of flash-runtime
> (player + playerglobal) and air-runtime (sdk containing airglobal) for the
> different versions and platforms. The tool would then deal with mavenizing
> them on the client side. What would be good though, if all the zips had the
> same structure. Especially the flashplayer did have multiple names in the
> different Flex SDKs it would be cool if they were all called "flashplayer" ...
> at least this would make my life a lot easier :-). In this case you don't need
> any poms at all ... after all writing a pom to download a zip-file that you
> need to unpack an process before you can use it's content doesn't sound very
> Maven like to me.
>
> Would this be possible?
Well, I would have to check with the runtime folks if we start messing with
the packaging they distribute. Right now I think you are talking about four
different downloads from the Adobe site (playerglobal, FlashPlayer, AIR SDK,
AIR Desktop Runtime). Can we leave it at those four?
Regarding their names, I would have to see if we can get permission to
change packaging names. I'm pretty sure I can choose folder names for
storing them if that helps. Would it work if Adobe had an .xml file
somewhere that mapped some id and version to the actual package names?
Since you say you could write a tool, that sounds different from the maven
plugin that is winning in the poll, is that true?
I'm not sure what you have to process in an AIR SDK after you unpack it. Do
you really need to put individual pom.xmls in the AIR SDK tree? IMO, they
are all interdependent. I don't think you should be mixing pieces from
different versions of the AIR SDK.
We are all Maven-ignorant at Adobe, so for any extra piece of work we have
to do, it will help you can explain how it will improve adoption of Apache
Flex.
Thanks,
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Hi Alex,
well regarding the Flashplayer ... is is actually needed during the build. Not for actually building the SWF, but more for running the unit-tests.
Ok ... I would then suggest that we decide a fixed url pattern in which I could build a tool to automatically download zip files of flash-runtime (player + playerglobal) and air-runtime (sdk containing airglobal) for the different versions and platforms. The tool would then deal with mavenizing them on the client side. What would be good though, if all the zips had the same structure. Especially the flashplayer did have multiple names in the different Flex SDKs it would be cool if they were all called "flashplayer" ... at least this would make my life a lot easier :-). In this case you don't need any poms at all ... after all writing a pom to download a zip-file that you need to unpack an process before you can use it's content doesn't sound very Maven like to me.
Would this be possible?
Chris
________________________________________
Von: Alex Harui [aharui@adobe.com]
Gesendet: Mittwoch, 28. November 2012 22:34
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: AW: [POLL] Maven and Apache Flex
I think I asked this already, but can't find a prior answer. Can the
resource be a .zip file of the AIR SDK? In your example, I think you only
were concerned about airglobal.swc, but I think we need the entire set of
files as a single downloadable entity, especially to build mobile packages.
I wouldn't really want to have unzipped AIR SDKs with a hierarchy of pom.xml
files in them.
So in my mind, there is an artifact for playerglobal.swc and an artifact
that is the AIR SDK zip file. Or maybe different artifacts for Mac vs Win?
The playerglobal.swc should be cross-platform.
I hadn't planned to put the actual FlashPlayer under Maven. You only need
it to run, not build.
What are the other resource files you are referring to?
-Alex
On 11/28/12 1:19 PM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
wrote:
> Well It's one pom.xml for every jar or resource you want to povide access to.
> How many artifacts are you talking about? As far as I understood it this would
> be one swc and all the resource files as well as one binary for each platform
> for the flash player but a whole bunch for the AIR SDK. I did send you a
> zipped archive of my mavenized SDKs so if you look at the com/adobe/flash and
> com/adobe/air directories I think you should get an idea of what I'm talking
> about.
>
> Chris
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Mittwoch, 28. November 2012 21:09
> An: flex-dev@incubator.apache.org
> Betreff: Re: AW: AW: AW: [POLL] Maven and Apache Flex
>
>
>
>
> On 11/28/12 11:58 AM, "christofer.dutz@c-ware.de"
> <ch...@c-ware.de> wrote:
>
>> Ok,
>>
>> so if it was possible to place archives on Adobe servers and download
>> stuff from there using the maven plugin that would be great. In the
>> simplest case I guess simply a url and naming convention would do.
>> Ideally I would volunteer to prepare archives containing mavenized
>> stuff that the plugin could simply download and extract without having
>> to do any processing. This would make the plugin a lot easier without adding
>> any work for Adobe.
>>
>> Chris
> Hi Chris, what do you mean by "archives"? Adobe will probably frown on
> non-Adobe folks providing binary content for the download server. At least
> the pom.xml is "text".
>
> In one repo I looked at, I thought I just saw a pom.xml file next to a .jar
> file. Why can't our solution be as simple as that?
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
I think I asked this already, but can't find a prior answer. Can the
resource be a .zip file of the AIR SDK? In your example, I think you only
were concerned about airglobal.swc, but I think we need the entire set of
files as a single downloadable entity, especially to build mobile packages.
I wouldn't really want to have unzipped AIR SDKs with a hierarchy of pom.xml
files in them.
So in my mind, there is an artifact for playerglobal.swc and an artifact
that is the AIR SDK zip file. Or maybe different artifacts for Mac vs Win?
The playerglobal.swc should be cross-platform.
I hadn't planned to put the actual FlashPlayer under Maven. You only need
it to run, not build.
What are the other resource files you are referring to?
-Alex
On 11/28/12 1:19 PM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
wrote:
> Well It's one pom.xml for every jar or resource you want to povide access to.
> How many artifacts are you talking about? As far as I understood it this would
> be one swc and all the resource files as well as one binary for each platform
> for the flash player but a whole bunch for the AIR SDK. I did send you a
> zipped archive of my mavenized SDKs so if you look at the com/adobe/flash and
> com/adobe/air directories I think you should get an idea of what I'm talking
> about.
>
> Chris
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Mittwoch, 28. November 2012 21:09
> An: flex-dev@incubator.apache.org
> Betreff: Re: AW: AW: AW: [POLL] Maven and Apache Flex
>
>
>
>
> On 11/28/12 11:58 AM, "christofer.dutz@c-ware.de"
> <ch...@c-ware.de> wrote:
>
>> Ok,
>>
>> so if it was possible to place archives on Adobe servers and download
>> stuff from there using the maven plugin that would be great. In the
>> simplest case I guess simply a url and naming convention would do.
>> Ideally I would volunteer to prepare archives containing mavenized
>> stuff that the plugin could simply download and extract without having
>> to do any processing. This would make the plugin a lot easier without adding
>> any work for Adobe.
>>
>> Chris
> Hi Chris, what do you mean by "archives"? Adobe will probably frown on
> non-Adobe folks providing binary content for the download server. At least
> the pom.xml is "text".
>
> In one repo I looked at, I thought I just saw a pom.xml file next to a .jar
> file. Why can't our solution be as simple as that?
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Well It's one pom.xml for every jar or resource you want to povide access to. How many artifacts are you talking about? As far as I understood it this would be one swc and all the resource files as well as one binary for each platform for the flash player but a whole bunch for the AIR SDK. I did send you a zipped archive of my mavenized SDKs so if you look at the com/adobe/flash and com/adobe/air directories I think you should get an idea of what I'm talking about.
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Mittwoch, 28. November 2012 21:09
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: [POLL] Maven and Apache Flex
On 11/28/12 11:58 AM, "christofer.dutz@c-ware.de"
<ch...@c-ware.de> wrote:
> Ok,
>
> so if it was possible to place archives on Adobe servers and download
> stuff from there using the maven plugin that would be great. In the
> simplest case I guess simply a url and naming convention would do.
> Ideally I would volunteer to prepare archives containing mavenized
> stuff that the plugin could simply download and extract without having
> to do any processing. This would make the plugin a lot easier without adding any work for Adobe.
>
> Chris
Hi Chris, what do you mean by "archives"? Adobe will probably frown on non-Adobe folks providing binary content for the download server. At least the pom.xml is "text".
In one repo I looked at, I thought I just saw a pom.xml file next to a .jar file. Why can't our solution be as simple as that?
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: AW: AW: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
On 11/28/12 11:58 AM, "christofer.dutz@c-ware.de"
<ch...@c-ware.de> wrote:
> Ok,
>
> so if it was possible to place archives on Adobe servers and download stuff
> from there using the maven plugin that would be great. In the simplest case I
> guess simply a url and naming convention would do. Ideally I would volunteer
> to prepare archives containing mavenized stuff that the plugin could simply
> download and extract without having to do any processing. This would make the
> plugin a lot easier without adding any work for Adobe.
>
> Chris
Hi Chris, what do you mean by "archives"? Adobe will probably frown on
non-Adobe folks providing binary content for the download server. At least
the pom.xml is "text".
In one repo I looked at, I thought I just saw a pom.xml file next to a .jar
file. Why can't our solution be as simple as that?
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: AW: AW: [POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Ok,
so if it was possible to place archives on Adobe servers and download stuff from there using the maven plugin that would be great. In the simplest case I guess simply a url and naming convention would do. Ideally I would volunteer to prepare archives containing mavenized stuff that the plugin could simply download and extract without having to do any processing. This would make the plugin a lot easier without adding any work for Adobe.
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Mittwoch, 28. November 2012 20:48
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: [POLL] Maven and Apache Flex
On 11/28/12 11:27 AM, "christofer.dutz@c-ware.de"
<ch...@c-ware.de> wrote:
> Ok so this is good news :-)
>
> Well perhaps some other guys could join the discussion, because
> currently I don't have an idea how we want to enforce the accceptance
> of the licenses from the side of the download-server - I mean on http level.
>
> My proposal for an automated downloader would take care of integrating
> the license acceptance into the maven build, unfortunately it woudn't
> prevent someone from simply downloading the stuff from the Adobe
> servers manually without accepting any license.
I'm pretty sure we don't have to worry about that but I will check with legal if we decide to pursue this approach. Today the Adobe downloads page eventually hits a URL on the actual download server that starts the download of the bits. If you had a network monitor you would see the actual request for the bits and one you know that you can go back and get it directly. I'm pretty sure we haven't installed any defenses.
> What exaclty would "manage the download server"
> mean? Are you allowed to place stuff in certain directories, or could
> you setup stuff on the server itself?
I think the download server is just a file server on Akamai. I don't know what it would take to install server-side code on it, but I would much rather not. There would be extra scrutiny about that, I would expect.
> Just to sort of give the thoughts a
> direction. I still think of a Nexus instance with
> creating/reactivating accounts linked to accepting the Licenses of
> being the best and safest solution. It would definitely reduce the
> amount of work having tob e done at Adobes side and we could simply rely on the existing maven features.
How would that save on Adobe time? Wouldn't a Nexus instance require maintenance and security management?
>
> And to the point of Adobe not earning Money with it ... I would think
> of it as customer support. After all ... as a european citizen I payed
> double the US price for my Adobe products, just for hearing that they
> are dopping support for the parts I was interested in just a few weeks
> after purchasing the update to the latest (and last) version. So I
> would treat this as post-product support and it would definitely
> enlarge the chance of me being willing to give Adobe money for any
> products they might create in the future :-)
Yes, that's why Adobe is willing to even listen to this request: to support our loyal customers. But product management could not find Gaming developers who want to use Maven or related tools so the only folks benefiting are Flex folks right now, and so they want to limit resource commitment to Maven support. But at least it isn't zero resources.
>
> Chris
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Mittwoch, 28. November 2012 19:37
> An: flex-dev@incubator.apache.org
> Betreff: Re: AW: [POLL] Maven and Apache Flex
>
>
>
>
> On 11/28/12 10:01 AM, "christofer.dutz@c-ware.de"
> <ch...@c-ware.de> wrote:
>
>> Yeah ... I meant Adobe :-)
>>
>> Well I think the form in which Adobe provides the stuff would be a
>> thing we could discuss ...
>> I guess there are a lot of options.
>> - The one side would be downloader-mojo simply downloading the normal
>> zip files containinig AIR SDK or Flash Player stuff and mavenizing
>> that on the client.
>> - The other side would be downloading fully mavenized resources
>> directly from an Adobe server.
>> I guess there could be a number of options inbetween too.
>>
>> I would prefer the option with fully mavenized resources being
>> downloaded directly from Adobe, but I am assuming it would probably
>> be the other side that would be more realistic to hope for.
>> (I think Adobe doesn't want to do anything to support us in regard of
>> Maven ... at least that's my current assumption).
> Actually, I have the ok from Runtime product management to let me
> manage the download server and place pom.xmls as needed. But that's
> about it. And they want assurance that licenses are being accepted
> before downloading. So, if we can make this work by giving me or
> showing me how to set up pom.xmls I will go ask for login credentials
> to the downloads server, setup a couple of folders and we can start actually trying it.
>
> Adobe does want to support us, but the fact is, Adobe isn't getting
> any money from this so they aren't going to spend a lot of time on it.
>
>> With this option it would be good if there was a systematic way of
>> providing them so we wouldn't have to maintain a mapping table for
>> mapping versions to URLs but could calculate the url.
>> Something like
>> "http://download.adobe.com/runtimes/flash/{flashversion}-{os}.zip" or
>> "http://download.adobe.com/runtimes/air/{airversion}-{os}.zip" would
>> be great.
>> Doesnt actually have to be that URL, just that we could calculate the
>> URL for it by setting "type" (flash/air), "version" and "os" (win/mac/lnx).
> I believe I get to control a new set of folders containing runtime SDKs.
> The runtime team will probably keep using their current scheme. They
> will not update our new folder area when a new release goes out so we
> will have to keep track and maintain that ourselves. But I think I
> can use whatever folder naming scheme you want to use.
>>
>> Chris
>>
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Alex Harui [mailto:aharui@adobe.com]
>> Gesendet: Mittwoch, 28. November 2012 18:34
>> An: flex-dev@incubator.apache.org
>> Betreff: Re: [POLL] Maven and Apache Flex
>>
>>
>>
>>
>> On 11/28/12 8:23 AM, "Greg Reddin" <gr...@gmail.com> wrote:
>>
>>> On Wed, Nov 28, 2012 at 5:49 AM, christofer.dutz@c-ware.de <
>>> christofer.dutz@c-ware.de> wrote:
>>>
>>>> What would you all think of the following solution:
>>>> - Apache deploys the Apache Flex FDK artifacts in a public maven
>>>> repo (Without the Apache stuff you need a license for)
>> Apache stuff or Adobe Stuff?
>>
>>>> - In the maven-flex-plugin suite there is one mojo that binds to
>>>> mavens "initialize" phase and checks the availability of the Apache
>>>> artifacts. If they are missing it prompts the user if he accepts
>>>> the license agreement (An option to allow a non-interactive build
>>>> would be good for running on
>>>> CI-Servers)
>> So, if I understand correctly, you will use the presence of the Adobe
>> artifacts to skip prompting the user to accept the license?
>>
>> That sounds good to me. So then all Adobe needs to do is put pom.xml
>> files alongside the different AIR SDK downloads?
>>
>> Thanks,
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: AW: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
On 11/28/12 11:27 AM, "christofer.dutz@c-ware.de"
<ch...@c-ware.de> wrote:
> Ok so this is good news :-)
>
> Well perhaps some other guys could join the discussion, because currently I
> don't have an idea how we want to enforce the accceptance of the licenses from
> the side of the download-server - I mean on http level.
>
> My proposal for an automated downloader would take care of integrating the
> license acceptance into the maven build, unfortunately it woudn't prevent
> someone from simply downloading the stuff from the Adobe servers manually
> without accepting any license.
I'm pretty sure we don't have to worry about that but I will check with
legal if we decide to pursue this approach. Today the Adobe downloads page
eventually hits a URL on the actual download server that starts the download
of the bits. If you had a network monitor you would see the actual request
for the bits and one you know that you can go back and get it directly. I'm
pretty sure we haven't installed any defenses.
> What exaclty would "manage the download server"
> mean? Are you allowed to place stuff in certain directories, or could you
> setup stuff on the server itself?
I think the download server is just a file server on Akamai. I don't know
what it would take to install server-side code on it, but I would much
rather not. There would be extra scrutiny about that, I would expect.
> Just to sort of give the thoughts a
> direction. I still think of a Nexus instance with creating/reactivating
> accounts linked to accepting the Licenses of being the best and safest
> solution. It would definitely reduce the amount of work having tob e done at
> Adobes side and we could simply rely on the existing maven features.
How would that save on Adobe time? Wouldn't a Nexus instance require
maintenance and security management?
>
> And to the point of Adobe not earning Money with it ... I would think of it as
> customer support. After all ... as a european citizen I payed double the US
> price for my Adobe products, just for hearing that they are dopping support
> for the parts I was interested in just a few weeks after purchasing the update
> to the latest (and last) version. So I would treat this as post-product
> support and it would definitely enlarge the chance of me being willing to give
> Adobe money for any products they might create in the future :-)
Yes, that's why Adobe is willing to even listen to this request: to support
our loyal customers. But product management could not find Gaming
developers who want to use Maven or related tools so the only folks
benefiting are Flex folks right now, and so they want to limit resource
commitment to Maven support. But at least it isn't zero resources.
>
> Chris
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Mittwoch, 28. November 2012 19:37
> An: flex-dev@incubator.apache.org
> Betreff: Re: AW: [POLL] Maven and Apache Flex
>
>
>
>
> On 11/28/12 10:01 AM, "christofer.dutz@c-ware.de"
> <ch...@c-ware.de> wrote:
>
>> Yeah ... I meant Adobe :-)
>>
>> Well I think the form in which Adobe provides the stuff would be a
>> thing we could discuss ...
>> I guess there are a lot of options.
>> - The one side would be downloader-mojo simply downloading the normal
>> zip files containinig AIR SDK or Flash Player stuff and mavenizing
>> that on the client.
>> - The other side would be downloading fully mavenized resources
>> directly from an Adobe server.
>> I guess there could be a number of options inbetween too.
>>
>> I would prefer the option with fully mavenized resources being
>> downloaded directly from Adobe, but I am assuming it would probably be
>> the other side that would be more realistic to hope for.
>> (I think Adobe doesn't want to do anything to support us in regard of
>> Maven ... at least that's my current assumption).
> Actually, I have the ok from Runtime product management to let me manage the
> download server and place pom.xmls as needed. But that's about it. And they
> want assurance that licenses are being accepted before downloading. So, if we
> can make this work by giving me or showing me how to set up pom.xmls I will go
> ask for login credentials to the downloads server, setup a couple of folders
> and we can start actually trying it.
>
> Adobe does want to support us, but the fact is, Adobe isn't getting any money
> from this so they aren't going to spend a lot of time on it.
>
>> With this option it would be good if there was a systematic way of
>> providing them so we wouldn't have to maintain a mapping table for
>> mapping versions to URLs but could calculate the url.
>> Something like
>> "http://download.adobe.com/runtimes/flash/{flashversion}-{os}.zip" or
>> "http://download.adobe.com/runtimes/air/{airversion}-{os}.zip" would be
>> great.
>> Doesnt actually have to be that URL, just that we could calculate the
>> URL for it by setting "type" (flash/air), "version" and "os" (win/mac/lnx).
> I believe I get to control a new set of folders containing runtime SDKs.
> The runtime team will probably keep using their current scheme. They will not
> update our new folder area when a new release goes out so we will have to keep
> track and maintain that ourselves. But I think I can use whatever folder
> naming scheme you want to use.
>>
>> Chris
>>
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Alex Harui [mailto:aharui@adobe.com]
>> Gesendet: Mittwoch, 28. November 2012 18:34
>> An: flex-dev@incubator.apache.org
>> Betreff: Re: [POLL] Maven and Apache Flex
>>
>>
>>
>>
>> On 11/28/12 8:23 AM, "Greg Reddin" <gr...@gmail.com> wrote:
>>
>>> On Wed, Nov 28, 2012 at 5:49 AM, christofer.dutz@c-ware.de <
>>> christofer.dutz@c-ware.de> wrote:
>>>
>>>> What would you all think of the following solution:
>>>> - Apache deploys the Apache Flex FDK artifacts in a public maven
>>>> repo (Without the Apache stuff you need a license for)
>> Apache stuff or Adobe Stuff?
>>
>>>> - In the maven-flex-plugin suite there is one mojo that binds to
>>>> mavens "initialize" phase and checks the availability of the Apache
>>>> artifacts. If they are missing it prompts the user if he accepts the
>>>> license agreement (An option to allow a non-interactive build would
>>>> be good for running on
>>>> CI-Servers)
>> So, if I understand correctly, you will use the presence of the Adobe
>> artifacts to skip prompting the user to accept the license?
>>
>> That sounds good to me. So then all Adobe needs to do is put pom.xml
>> files alongside the different AIR SDK downloads?
>>
>> Thanks,
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: AW: [POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Ok so this is good news :-)
Well perhaps some other guys could join the discussion, because currently I don't have an idea how we want to enforce the accceptance of the licenses from the side of the download-server - I mean on http level.
My proposal for an automated downloader would take care of integrating the license acceptance into the maven build, unfortunately it woudn't prevent someone from simply downloading the stuff from the Adobe servers manually without accepting any license. What exaclty would "manage the download server" mean? Are you allowed to place stuff in certain directories, or could you setup stuff on the server itself? Just to sort of give the thoughts a direction. I still think of a Nexus instance with creating/reactivating accounts linked to accepting the Licenses of being the best and safest solution. It would definitely reduce the amount of work having tob e done at Adobes side and we could simply rely on the existing maven features.
And to the point of Adobe not earning Money with it ... I would think of it as customer support. After all ... as a european citizen I payed double the US price for my Adobe products, just for hearing that they are dopping support for the parts I was interested in just a few weeks after purchasing the update to the latest (and last) version. So I would treat this as post-product support and it would definitely enlarge the chance of me being willing to give Adobe money for any products they might create in the future :-)
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Mittwoch, 28. November 2012 19:37
An: flex-dev@incubator.apache.org
Betreff: Re: AW: [POLL] Maven and Apache Flex
On 11/28/12 10:01 AM, "christofer.dutz@c-ware.de"
<ch...@c-ware.de> wrote:
> Yeah ... I meant Adobe :-)
>
> Well I think the form in which Adobe provides the stuff would be a
> thing we could discuss ...
> I guess there are a lot of options.
> - The one side would be downloader-mojo simply downloading the normal
> zip files containinig AIR SDK or Flash Player stuff and mavenizing
> that on the client.
> - The other side would be downloading fully mavenized resources
> directly from an Adobe server.
> I guess there could be a number of options inbetween too.
>
> I would prefer the option with fully mavenized resources being
> downloaded directly from Adobe, but I am assuming it would probably be
> the other side that would be more realistic to hope for.
> (I think Adobe doesn't want to do anything to support us in regard of
> Maven ... at least that's my current assumption).
Actually, I have the ok from Runtime product management to let me manage the download server and place pom.xmls as needed. But that's about it. And they want assurance that licenses are being accepted before downloading. So, if we can make this work by giving me or showing me how to set up pom.xmls I will go ask for login credentials to the downloads server, setup a couple of folders and we can start actually trying it.
Adobe does want to support us, but the fact is, Adobe isn't getting any money from this so they aren't going to spend a lot of time on it.
> With this option it would be good if there was a systematic way of
> providing them so we wouldn't have to maintain a mapping table for
> mapping versions to URLs but could calculate the url.
> Something like
> "http://download.adobe.com/runtimes/flash/{flashversion}-{os}.zip" or
> "http://download.adobe.com/runtimes/air/{airversion}-{os}.zip" would be great.
> Doesnt actually have to be that URL, just that we could calculate the
> URL for it by setting "type" (flash/air), "version" and "os" (win/mac/lnx).
I believe I get to control a new set of folders containing runtime SDKs.
The runtime team will probably keep using their current scheme. They will not update our new folder area when a new release goes out so we will have to keep track and maintain that ourselves. But I think I can use whatever folder naming scheme you want to use.
>
> Chris
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Mittwoch, 28. November 2012 18:34
> An: flex-dev@incubator.apache.org
> Betreff: Re: [POLL] Maven and Apache Flex
>
>
>
>
> On 11/28/12 8:23 AM, "Greg Reddin" <gr...@gmail.com> wrote:
>
>> On Wed, Nov 28, 2012 at 5:49 AM, christofer.dutz@c-ware.de <
>> christofer.dutz@c-ware.de> wrote:
>>
>>> What would you all think of the following solution:
>>> - Apache deploys the Apache Flex FDK artifacts in a public maven
>>> repo (Without the Apache stuff you need a license for)
> Apache stuff or Adobe Stuff?
>
>>> - In the maven-flex-plugin suite there is one mojo that binds to
>>> mavens "initialize" phase and checks the availability of the Apache
>>> artifacts. If they are missing it prompts the user if he accepts the
>>> license agreement (An option to allow a non-interactive build would
>>> be good for running on
>>> CI-Servers)
> So, if I understand correctly, you will use the presence of the Adobe
> artifacts to skip prompting the user to accept the license?
>
> That sounds good to me. So then all Adobe needs to do is put pom.xml
> files alongside the different AIR SDK downloads?
>
> Thanks,
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
On 11/28/12 10:01 AM, "christofer.dutz@c-ware.de"
<ch...@c-ware.de> wrote:
> Yeah ... I meant Adobe :-)
>
> Well I think the form in which Adobe provides the stuff would be a thing we
> could discuss ...
> I guess there are a lot of options.
> - The one side would be downloader-mojo simply downloading the normal zip
> files containinig AIR SDK or Flash Player stuff and mavenizing that on the
> client.
> - The other side would be downloading fully mavenized resources directly from
> an Adobe server.
> I guess there could be a number of options inbetween too.
>
> I would prefer the option with fully mavenized resources being downloaded
> directly from Adobe, but I am assuming it would probably be the other side
> that would be more realistic to hope for.
> (I think Adobe doesn't want to do anything to support us in regard of Maven
> ... at least that's my current assumption).
Actually, I have the ok from Runtime product management to let me manage the
download server and place pom.xmls as needed. But that's about it. And they
want assurance that licenses are being accepted before downloading. So, if
we can make this work by giving me or showing me how to set up pom.xmls I
will go ask for login credentials to the downloads server, setup a couple of
folders and we can start actually trying it.
Adobe does want to support us, but the fact is, Adobe isn't getting any
money from this so they aren't going to spend a lot of time on it.
> With this option it would be good if there was a systematic way of providing
> them so we wouldn't have to maintain a mapping table for mapping versions to
> URLs but could calculate the url.
> Something like
> "http://download.adobe.com/runtimes/flash/{flashversion}-{os}.zip" or
> "http://download.adobe.com/runtimes/air/{airversion}-{os}.zip" would be great.
> Doesnt actually have to be that URL, just that we could calculate the URL for
> it by setting "type" (flash/air), "version" and "os" (win/mac/lnx).
I believe I get to control a new set of folders containing runtime SDKs.
The runtime team will probably keep using their current scheme. They will
not update our new folder area when a new release goes out so we will have
to keep track and maintain that ourselves. But I think I can use whatever
folder naming scheme you want to use.
>
> Chris
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Mittwoch, 28. November 2012 18:34
> An: flex-dev@incubator.apache.org
> Betreff: Re: [POLL] Maven and Apache Flex
>
>
>
>
> On 11/28/12 8:23 AM, "Greg Reddin" <gr...@gmail.com> wrote:
>
>> On Wed, Nov 28, 2012 at 5:49 AM, christofer.dutz@c-ware.de <
>> christofer.dutz@c-ware.de> wrote:
>>
>>> What would you all think of the following solution:
>>> - Apache deploys the Apache Flex FDK artifacts in a public maven repo
>>> (Without the Apache stuff you need a license for)
> Apache stuff or Adobe Stuff?
>
>>> - In the maven-flex-plugin suite there is one mojo that binds to
>>> mavens "initialize" phase and checks the availability of the Apache
>>> artifacts. If they are missing it prompts the user if he accepts the
>>> license agreement (An option to allow a non-interactive build would
>>> be good for running on
>>> CI-Servers)
> So, if I understand correctly, you will use the presence of the Adobe
> artifacts to skip prompting the user to accept the license?
>
> That sounds good to me. So then all Adobe needs to do is put pom.xml files
> alongside the different AIR SDK downloads?
>
> Thanks,
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: [POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Yeah ... I meant Adobe :-)
Well I think the form in which Adobe provides the stuff would be a thing we could discuss ...
I guess there are a lot of options.
- The one side would be downloader-mojo simply downloading the normal zip files containinig AIR SDK or Flash Player stuff and mavenizing that on the client.
- The other side would be downloading fully mavenized resources directly from an Adobe server.
I guess there could be a number of options inbetween too.
I would prefer the option with fully mavenized resources being downloaded directly from Adobe, but I am assuming it would probably be the other side that would be more realistic to hope for.
(I think Adobe doesn't want to do anything to support us in regard of Maven ... at least that's my current assumption).
With this option it would be good if there was a systematic way of providing them so we wouldn't have to maintain a mapping table for mapping versions to URLs but could calculate the url.
Something like "http://download.adobe.com/runtimes/flash/{flashversion}-{os}.zip" or "http://download.adobe.com/runtimes/air/{airversion}-{os}.zip" would be great. Doesnt actually have to be that URL, just that we could calculate the URL for it by setting "type" (flash/air), "version" and "os" (win/mac/lnx).
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Mittwoch, 28. November 2012 18:34
An: flex-dev@incubator.apache.org
Betreff: Re: [POLL] Maven and Apache Flex
On 11/28/12 8:23 AM, "Greg Reddin" <gr...@gmail.com> wrote:
> On Wed, Nov 28, 2012 at 5:49 AM, christofer.dutz@c-ware.de <
> christofer.dutz@c-ware.de> wrote:
>
>> What would you all think of the following solution:
>> - Apache deploys the Apache Flex FDK artifacts in a public maven repo
>> (Without the Apache stuff you need a license for)
Apache stuff or Adobe Stuff?
>> - In the maven-flex-plugin suite there is one mojo that binds to
>> mavens "initialize" phase and checks the availability of the Apache
>> artifacts. If they are missing it prompts the user if he accepts the
>> license agreement (An option to allow a non-interactive build would
>> be good for running on
>> CI-Servers)
So, if I understand correctly, you will use the presence of the Adobe artifacts to skip prompting the user to accept the license?
That sounds good to me. So then all Adobe needs to do is put pom.xml files alongside the different AIR SDK downloads?
Thanks,
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: [POLL] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
On 11/28/12 8:23 AM, "Greg Reddin" <gr...@gmail.com> wrote:
> On Wed, Nov 28, 2012 at 5:49 AM, christofer.dutz@c-ware.de <
> christofer.dutz@c-ware.de> wrote:
>
>> What would you all think of the following solution:
>> - Apache deploys the Apache Flex FDK artifacts in a public maven repo
>> (Without the Apache stuff you need a license for)
Apache stuff or Adobe Stuff?
>> - In the maven-flex-plugin suite there is one mojo that binds to mavens
>> "initialize" phase and checks the availability of the Apache artifacts. If
>> they are missing it prompts the user if he accepts the license agreement
>> (An option to allow a non-interactive build would be good for running on
>> CI-Servers)
So, if I understand correctly, you will use the presence of the Adobe
artifacts to skip prompting the user to accept the license?
That sounds good to me. So then all Adobe needs to do is put pom.xml files
alongside the different AIR SDK downloads?
Thanks,
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: [POLL] Maven and Apache Flex
Posted by Greg Reddin <gr...@gmail.com>.
On Wed, Nov 28, 2012 at 5:49 AM, christofer.dutz@c-ware.de <
christofer.dutz@c-ware.de> wrote:
> What would you all think of the following solution:
> - Apache deploys the Apache Flex FDK artifacts in a public maven repo
> (Without the Apache stuff you need a license for)
> - In the maven-flex-plugin suite there is one mojo that binds to mavens
> "initialize" phase and checks the availability of the Apache artifacts. If
> they are missing it prompts the user if he accepts the license agreement
> (An option to allow a non-interactive build would be good for running on
> CI-Servers)
> - The Adobe-Stuff-Deployer mojo internally uses part of the Mavenizer to
> deploy artifacts to the local maven repo.
> - The rest of the maven-flex-plugin suite uses the atrifacts in the repo
> as in any normal build.
>
Just about as close to perfect as you could get. +1.
Greg
AW: [POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
No Offense taken ... after all .. I didn't write the tool, I simply took over maintaining it and got the code back on track (Testsuite was failling in more than 30 Tests).
I think the maven pluigin would be automatically downloaded as is the case with all other maven plugins, so I guess no manual step would have to be done.
What would you all think of the following solution:
- Apache deploys the Apache Flex FDK artifacts in a public maven repo (Without the Apache stuff you need a license for)
- In the maven-flex-plugin suite there is one mojo that binds to mavens "initialize" phase and checks the availability of the Apache artifacts. If they are missing it prompts the user if he accepts the license agreement (An option to allow a non-interactive build would be good for running on CI-Servers)
- The Adobe-Stuff-Deployer mojo internally uses part of the Mavenizer to deploy artifacts to the local maven repo.
- The rest of the maven-flex-plugin suite uses the atrifacts in the repo as in any normal build.
I think this solution should suite the needs of:
- Adobe, because people need to accept the licenses
- Developers, because they don't have to manually do more than accept a license agreement by typing: "y".
- Coporates, because the generated artifacts could be deployed to local Maven repos.
Chris
________________________________________
Von: Maxime Cowez [maxime.cowez@gmail.com]
Gesendet: Mittwoch, 28. November 2012 12:24
An: flex-dev@incubator.apache.org
Betreff: Re: [POLL] Maven and Apache Flex
I am actually using Gradle with GradleFx plugin (sorry Chris, had too many
issues with FlexMojos :-/ ). Gradle uses Maven under the hood. My answers
to the first 5 questions should be interpreted from that angle.
> 1. Number of people who will use Maven to develop Flex apps at your company
> (0 if you have no interest in using Maven).
>
1 (I'm the only Flex dev)
9, if you count the java devs that need my build scripts to build their web
apps
> 2. Maven would be used to develop apps for FlashPlayer in the browser (yes
> or no)
>
yes
>
> 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> no)
>
no (not yet, but possibly in the future)
> 4. Maven would be used to develop apps for AIR on Android (yes or no)
>
no (not yet, but possibly in the future)
>
> 5. Maven would be used to develop apps for AIR on IOS (yes or no)
>
no (not yet, but possibly in the future)
>
> 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> neutral, 1 = acceptable, 2 = preferred)
> a) You must manually download the Player SDK and AIR SDK from the Adobe
> site and set up environment variables pointing to them
>
-1
> b) You must download and install a Maven plug-in from the Apache Flex
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
0 (see remarks below)
> c) You must download and install a Maven plug-in from the Adobe
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
0 (see remarks below)
> d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> desktops/laptops, but not for AIR apps on Android/IOS. To target
> Android/IOS, you must use one of the first three implementations
>
0
> e) We will manually download the Player SDKs and AIR SDKs and put them
> in our local/private Maven repo.
>
0
> f) We would use a utility application that would download the Player
> SDKs and AIR SDKs (prompting you to accept the license) and put them
> in our local/private Maven repo.
>
0
Remarks:
- The number of steps to be taken by a Java developer that needs to compile
my Flex apps should be 0 (accepting a license would be acceptable).
- I haven't given a positive number to any of the proposed implementations,
because all of them require at least one manual step, which violates my
previous requirement. Unless I didn't understand them correctly; if
downloading the Maven plugin is part of the build process, then my answer
should be "2" for those solutions. Otherwise downloading the Maven plugin
manually would be closest to acceptable because I assume it comes closest
to what the java devs are already used to do.
- For reference, this is how it is handled in GradleFx:
- the GradleFx plugin is downloaded and cached automatically by Gradle
- the Flex SDK is downloaded and cached automatically by
Gradle/GradleFx, including Adobe's proprietary libraries; the licenses must
be accepted once
- other dependencies are downloaded and cached, and the application is
built
- the Java devs don't even have to install Gradle because I commit the
Flex app with a so-called Gradle "wrapper", a lightweight standalone build
tool. Unfortunately this feature is specific to Gradle and doesn't exist in
Maven (as far as I know).
>
> Thanks in advance. Remember that polls are not binding, but your input is
> much appreciated.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: [POLL] Maven and Apache Flex
Posted by Maxime Cowez <ma...@gmail.com>.
I am actually using Gradle with GradleFx plugin (sorry Chris, had too many
issues with FlexMojos :-/ ). Gradle uses Maven under the hood. My answers
to the first 5 questions should be interpreted from that angle.
> 1. Number of people who will use Maven to develop Flex apps at your company
> (0 if you have no interest in using Maven).
>
1 (I'm the only Flex dev)
9, if you count the java devs that need my build scripts to build their web
apps
> 2. Maven would be used to develop apps for FlashPlayer in the browser (yes
> or no)
>
yes
>
> 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> no)
>
no (not yet, but possibly in the future)
> 4. Maven would be used to develop apps for AIR on Android (yes or no)
>
no (not yet, but possibly in the future)
>
> 5. Maven would be used to develop apps for AIR on IOS (yes or no)
>
no (not yet, but possibly in the future)
>
> 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> neutral, 1 = acceptable, 2 = preferred)
> a) You must manually download the Player SDK and AIR SDK from the Adobe
> site and set up environment variables pointing to them
>
-1
> b) You must download and install a Maven plug-in from the Apache Flex
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
0 (see remarks below)
> c) You must download and install a Maven plug-in from the Adobe
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
0 (see remarks below)
> d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> desktops/laptops, but not for AIR apps on Android/IOS. To target
> Android/IOS, you must use one of the first three implementations
>
0
> e) We will manually download the Player SDKs and AIR SDKs and put them
> in our local/private Maven repo.
>
0
> f) We would use a utility application that would download the Player
> SDKs and AIR SDKs (prompting you to accept the license) and put them
> in our local/private Maven repo.
>
0
Remarks:
- The number of steps to be taken by a Java developer that needs to compile
my Flex apps should be 0 (accepting a license would be acceptable).
- I haven't given a positive number to any of the proposed implementations,
because all of them require at least one manual step, which violates my
previous requirement. Unless I didn't understand them correctly; if
downloading the Maven plugin is part of the build process, then my answer
should be "2" for those solutions. Otherwise downloading the Maven plugin
manually would be closest to acceptable because I assume it comes closest
to what the java devs are already used to do.
- For reference, this is how it is handled in GradleFx:
- the GradleFx plugin is downloaded and cached automatically by Gradle
- the Flex SDK is downloaded and cached automatically by
Gradle/GradleFx, including Adobe's proprietary libraries; the licenses must
be accepted once
- other dependencies are downloaded and cached, and the application is
built
- the Java devs don't even have to install Gradle because I commit the
Flex app with a so-called Gradle "wrapper", a lightweight standalone build
tool. Unfortunately this feature is specific to Gradle and doesn't exist in
Maven (as far as I know).
>
> Thanks in advance. Remember that polls are not binding, but your input is
> much appreciated.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: [POLL] Maven and Apache Flex
Posted by Jeffry Houser <je...@dot-com-it.com>.
On 11/27/2012 1:46 PM, Alex Harui wrote:
> Hi Folks,
>
> There have been some recent discussions about Maven and how it could work
> with Apache Flex. There are several possibilities, but none of them are
> perfect because of Adobe licensing requirements. This poll is only about
> how you use or plan to use Apache Flex and Maven to build apps that use an
> Adobe runtime (Adobe Flash Player or Adobe AIR including Adobe AIR packaged
> for Android or IOS). We¹ll worry about other Apache Flex scenarios in the
> future. This poll also assumes that the Adobe will not change its SDK
> licensing and requires that you accept the licensing terms at least once.
>
> Also, you can substitute the word "Maven" for any Maven-like tool that uses
> Maven files.
>
> Please answer the following:
>
> 1. Number of people who will use Maven to develop Flex apps at your company
> (0 if you have no interest in using Maven).
0
And I guess I can add nothing of value to the other questions.
Re: [POLL] Maven and Apache Flex
Posted by Miguel Serrano <ms...@gmail.com>.
Company: Plumbee Ltd.
1. Number of people who will use Maven to develop Flex apps at your company
> (0 if you have no interest in using Maven).
>
8
> 2. Maven would be used to develop apps for FlashPlayer in the browser (yes
> or no)
>
Yes
3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> no)
>
Yes
4. Maven would be used to develop apps for AIR on Android (yes or no)
>
Yes
> 5. Maven would be used to develop apps for AIR on IOS (yes or no)
>
Yes
> 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> neutral, 1 = acceptable, 2 = preferred)
> a) You must manually download the Player SDK and AIR SDK from the Adobe
> site and set up environment variables pointing to them
>
-1
> b) You must download and install a Maven plug-in from the Apache Flex
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
2
> c) You must download and install a Maven plug-in from the Adobe
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
1
> d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> desktops/laptops, but not for AIR apps on Android/IOS. To target
> Android/IOS, you must use one of the first three implementations
>
1
> e) We will manually download the Player SDKs and AIR SDKs and put them
> in our local/private Maven repo.
>
0
> f) We would use a utility application that would download the Player
> SDKs and AIR SDKs (prompting you to accept the license) and put them
> in our local/private Maven repo.
>
1
>
> Thanks in advance. Remember that polls are not binding, but your input is
> much appreciated.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
--
Miguel Serrano Milano
mserranom@gmail.com
Re: [POLL] Maven and Apache Flex
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Here's my responses:
> Please answer the following:
>
> 1. Number of people who will use Maven to develop Flex apps at your company
> (0 if you have no interest in using Maven).
>
15
>
> 2. Maven would be used to develop apps for FlashPlayer in the browser (yes
> or no)
>
>
yes
> 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> no)
>
>
yes
> 4. Maven would be used to develop apps for AIR on Android (yes or no)
>
>
yes
> 5. Maven would be used to develop apps for AIR on IOS (yes or no)
>
>
yes
> 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> neutral, 1 = acceptable, 2 = preferred)
> a) You must manually download the Player SDK and AIR SDK from the Adobe
> site and set up environment variables pointing to them
>
-1
> b) You must download and install a Maven plug-in from the Apache Flex
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
1
> c) You must download and install a Maven plug-in from the Adobe
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
2
> d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> desktops/laptops, but not for AIR apps on Android/IOS. To target
> Android/IOS, you must use one of the first three implementations
>
1
> e) We will manually download the Player SDKs and AIR SDKs and put them
> in our local/private Maven repo.
>
-1
> f) We would use a utility application that would download the Player
> SDKs and AIR SDKs (prompting you to accept the license) and put them
> in our local/private Maven repo.
>
1
>
> Thanks in advance. Remember that polls are not binding, but your input is
> much appreciated.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 35 57 77
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es
Re: [POLL] Maven and Apache Flex
Posted by Stefan Horochovec <st...@gmail.com>.
Sorry for my last email, it´s incomplete...
1. +1000
2. Yes
3. No (don´t use AIR)
4. No (don´t use AIR)
5. No (don´t use AIR)
6 a) 0
6 b) 1
6 c) -1
6 d) 0
6 e) -1
6 f) 2
Stefan Horochovec
2012/11/28 Stefan Horochovec <st...@gmail.com>
> 1. +1000
>
> 2. Yes
>
> 3. No (don´t use AIR)
>
> 4. No (don´t use AIR)
>
> 5. No (don´t use AIR)
>
> 6 a) 0
> 6 a) 0
> 6 a) 0
> 6 a) 0
>
Re: [POLL] Maven and Apache Flex
Posted by Stefan Horochovec <st...@gmail.com>.
1. +1000
2. Yes
3. No (don´t use AIR)
4. No (don´t use AIR)
5. No (don´t use AIR)
6 a) 0
6 a) 0
6 a) 0
6 a) 0
6. Rate the following proposed implementations (-1 = not acceptable, 0 =
neutral, 1 = acceptable, 2 = preferred)
a) You must manually download the Player SDK and AIR SDK from the Adobe
site and set up environment variables pointing to them
b) You must download and install a Maven plug-in from the Apache Flex
site. The first time you use Maven on a computer, it will ask you
to accept the Adobe license agreement.
c) You must download and install a Maven plug-in from the Adobe
site. The first time you use Maven on a computer, it will ask you
to accept the Adobe license agreement.
d) Maven can be used as-is for FlashPlayer apps and AIR apps on
desktops/laptops, but not for AIR apps on Android/IOS. To target
Android/IOS, you must use one of the first three implementations
e) We will manually download the Player SDKs and AIR SDKs and put them
in our local/private Maven repo.
f) We would use a utility application that would download the Player
SDKs and AIR SDKs (prompting you to accept the license) and put them
in our local/private Maven repo.
Stefan Horochovec
2012/11/27 Alex Harui <ah...@adobe.com>
> Hi Folks,
>
> There have been some recent discussions about Maven and how it could work
> with Apache Flex. There are several possibilities, but none of them are
> perfect because of Adobe licensing requirements. This poll is only about
> how you use or plan to use Apache Flex and Maven to build apps that use an
> Adobe runtime (Adobe Flash Player or Adobe AIR including Adobe AIR packaged
> for Android or IOS). We¹ll worry about other Apache Flex scenarios in the
> future. This poll also assumes that the Adobe will not change its SDK
> licensing and requires that you accept the licensing terms at least once.
>
> Also, you can substitute the word "Maven" for any Maven-like tool that uses
> Maven files.
>
> Please answer the following:
>
> 1. Number of people who will use Maven to develop Flex apps at your company
> (0 if you have no interest in using Maven).
>
> 2. Maven would be used to develop apps for FlashPlayer in the browser (yes
> or no)
>
> 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> no)
>
> 4. Maven would be used to develop apps for AIR on Android (yes or no)
>
> 5. Maven would be used to develop apps for AIR on IOS (yes or no)
>
> 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> neutral, 1 = acceptable, 2 = preferred)
> a) You must manually download the Player SDK and AIR SDK from the Adobe
> site and set up environment variables pointing to them
> b) You must download and install a Maven plug-in from the Apache Flex
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
> c) You must download and install a Maven plug-in from the Adobe
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
> d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> desktops/laptops, but not for AIR apps on Android/IOS. To target
> Android/IOS, you must use one of the first three implementations
> e) We will manually download the Player SDKs and AIR SDKs and put them
> in our local/private Maven repo.
> f) We would use a utility application that would download the Player
> SDKs and AIR SDKs (prompting you to accept the license) and put them
> in our local/private Maven repo.
>
> Thanks in advance. Remember that polls are not binding, but your input is
> much appreciated.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: [POLL] Maven and Apache Flex
Posted by João Fernandes <jo...@gmail.com>.
I don't use Maven but if I would this would be my answers
1. Number of people who will use Maven to develop Flex apps at your company
(0 if you have no interest in using Maven).
0
2. Maven would be used to develop apps for FlashPlayer in the browser (yes
or no)
*yes*
3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
no)
*yes*
4. Maven would be used to develop apps for AIR on Android (yes or no)
*yes*
5. Maven would be used to develop apps for AIR on IOS (yes or no)
*yes*
6. Rate the following proposed implementations (-1 = not acceptable, 0 =
neutral, 1 = acceptable, 2 = preferred)
a) You must manually download the Player SDK and AIR SDK from the Adobe
site and set up environment variables pointing to them
*-1*
b) You must download and install a Maven plug-in from the Apache Flex
site. The first time you use Maven on a computer, it will ask you
to accept the Adobe license agreement.
*2*
c) You must download and install a Maven plug-in from the Adobe
site. The first time you use Maven on a computer, it will ask you
to accept the Adobe license agreement.
*0*
d) Maven can be used as-is for FlashPlayer apps and AIR apps on
desktops/laptops, but not for AIR apps on Android/IOS. To target
Android/IOS, you must use one of the first three implementations
*0*
e) We will manually download the Player SDKs and AIR SDKs and put them
in our local/private Maven repo.
*-1*
f) We would use a utility application that would download the Player
SDKs and AIR SDKs (prompting you to accept the license) and put them
in our local/private Maven repo.
*-1*
--
João Fernandes
RE: [POLL] Maven and Apache Flex
Posted by Neil Madsen <li...@cranialinteractive.com>.
> 1. Number of people who will use Maven to develop Flex apps at your
company (0 if you have no interest in using Maven).
0
It probably comes more from never having used it or seen what kind of
benefits there could be for a small shop.
RE: [POLL] Maven and Apache Flex
Posted by Frank Morawietz <Mo...@mhh-solartechnik.de>.
> 1. Number of people who will use Maven to develop Flex apps at your company
> (0 if you have no interest in using Maven).
>
3
> 2. Maven would be used to develop apps for FlashPlayer in the browser (yes
> or no)
>
yes
> 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> no)
>
no
> 4. Maven would be used to develop apps for AIR on Android (yes or no)
Yes
> 5. Maven would be used to develop apps for AIR on IOS (yes or no)
>
Yes
> 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> neutral, 1 = acceptable, 2 = preferred)
> a) You must manually download the Player SDK and AIR SDK from the Adobe
> site and set up environment variables pointing to them
>
-1
> b) You must download and install a Maven plug-in from the Apache Flex
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
2
c) You must download and install a Maven plug-in from the Adobe
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
0
> d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> desktops/laptops, but not for AIR apps on Android/IOS. To target
> Android/IOS, you must use one of the first three implementations
>
-1
> e) We will manually download the Player SDKs and AIR SDKs and put them
> in our local/private Maven repo.
>
0
> f) We would use a utility application that would download the Player
> SDKs and AIR SDKs (prompting you to accept the license) and put them
> in our local/private Maven repo.
>
1
Dr. Frank Morawietz
Lead Software Architect
MHH Solartechnik GmbH
Eisenbahnstr. 150
D-72072 Tübingen
Fon +49 7071 98987-186
Fax +49 7071 98987-10
mailto:morawietz@mhh-solartechnik.de
www.mhh-solartechnik.de
MHH Solartechnik GmbH
Sitz der Gesellschaft: Tübingen
Registergericht: Amtsgericht Stuttgart, HRB 381351
Geschäftsführer: Günter Haug
Re: [POLL] Maven and Apache Flex
Posted by Petr Svoboda <wo...@gmail.com>.
Hi,
here are some poll anwers. For the question 6e resp. 6f - I'd prefer
solution with proper license handling, but tight integration with local
maven repo might be quite overhead (like it will offer feature to upload to
nexus/artifactory?). Remote mvn repo proxied by local artifact cache (as we
use artifactory) is not offered as one of the options if I understand well.
Regards
Petr
On Tue, Nov 27, 2012 at 7:46 PM, Alex Harui <ah...@adobe.com> wrote:
> 1. Number of people who will use Maven to develop Flex apps at your company
> (0 if you have no interest in using Maven).
>
20
> 2. Maven would be used to develop apps for FlashPlayer in the browser (yes
> or no)
>
yes
> 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> no)
>
> no (at the moment, but maybe in future)
> 4. Maven would be used to develop apps for AIR on Android (yes or no)
>
> no
> 5. Maven would be used to develop apps for AIR on IOS (yes or no)
>
> no
> 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> neutral, 1 = acceptable, 2 = preferred)
> a) You must manually download the Player SDK and AIR SDK from the Adobe
> site and set up environment variables pointing to them
>
1
> b) You must download and install a Maven plug-in from the Apache Flex
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
1
c) You must download and install a Maven plug-in from the Adobe
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
1
> d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> desktops/laptops, but not for AIR apps on Android/IOS. To target
> Android/IOS, you must use one of the first three implementations
>
1
> e) We will manually download the Player SDKs and AIR SDKs and put them
> in our local/private Maven repo.
>
0
> f) We would use a utility application that would download the Player
> SDKs and AIR SDKs (prompting you to accept the license) and put them
> in our local/private Maven repo.
>
2
Re: AW: [Discuss] Maven and Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
On 11/28/12 7:00 AM, "Simon Morvan" <ga...@zone84.net> wrote:
> Chris,
>
> Velo's communication policy is disruptive* yet Flexmojos is open-source.
> Nothing blocks us from make it a true Apache project, in the scope of
> Flex (preferably) or in it's own scope. Communication policy would be
> then ruled by the community.
Actually, that's probably not true. Even though it is open-source, it is
"owned" and we cannot copy it into Apache without the owner's permission.
Well, we probably "can" but it is against Apache policy to do so.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: [Discuss] Maven and Apache Flex
Posted by Simon Morvan <ga...@zone84.net>.
Le 27/11/2012 23:04, christofer.dutz@c-ware.de a écrit :
> Even if I'm currently the project lead of Flexmojos, I would strongly suggest not to go that road.
>
> There is far too much legacy stuff to carry with Flexmojos and I have to admit that the rather restricive communication policy of Velo is rather discouraging.
>
> I think IF WE WERE TO GO THAT ROAD, developing an Apache Flex plugin first and using that to compile the Framework libs sounds like a far better solution.
> This way we would have controll over the entire stack needed to build Flex.
Chris,
Velo's communication policy is disruptive* yet Flexmojos is open-source.
Nothing blocks us from make it a true Apache project, in the scope of
Flex (preferably) or in it's own scope. Communication policy would be
then ruled by the community.
*well... in my opinion, it's just self defence of a sole individual
overflowed by its user-base rants and complaints.
--
Simon
AW: [Discuss] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Even if I'm currently the project lead of Flexmojos, I would strongly suggest not to go that road.
There is far too much legacy stuff to carry with Flexmojos and I have to admit that the rather restricive communication policy of Velo is rather discouraging.
I think IF WE WERE TO GO THAT ROAD, developing an Apache Flex plugin first and using that to compile the Framework libs sounds like a far better solution.
This way we would have controll over the entire stack needed to build Flex.
Chris
-----Ursprüngliche Nachricht-----
Von: omuppi1@gmail.com [mailto:omuppi1@gmail.com] Im Auftrag von Om
Gesendet: Dienstag, 27. November 2012 20:41
An: flex-dev@incubator.apache.org; jeffry@dot-com-it.com
Betreff: Re: [Discuss] Maven and Apache Flex
I have initiated a thread with my UI architecture team. Will send out the poll responses soon.
In the meantime, here is a gauge of the popularity of this feature. This is the most voted-on issue in our JIRA base.
https://issues.apache.org/jira/browse/FLEX-33086
https://issues.apache.org/jira/secure/ViewVoters!default.jspa?id=12538816
Thanks,
Om
On Tue, Nov 27, 2012 at 11:28 AM, Jeffry Houser <je...@dot-com-it.com>wrote:
>
> As I understand it, Maven is an automated build tool. Kind of like
> ANT on steroids.
>
>
> On 11/27/2012 2:20 PM, Harbs wrote:
>
>> 0. I have never quite figured out what Maven is or why I'd want to
>> use it. (and I do speak yiddish.) ;-)
>>
>> If someone could enlighten me, I could change my mind.
>>
>> Harbs
>>
>> On Nov 27, 2012, at 8:46 PM, Alex Harui wrote:
>>
>> 1. Number of people who will use Maven to develop Flex apps at your
>>> company
>>> (0 if you have no interest in using Maven).
>>>
>>
>>
>
Re: [Discuss] Maven and Apache Flex
Posted by Om <bi...@gmail.com>.
I have initiated a thread with my UI architecture team. Will send out the
poll responses soon.
In the meantime, here is a gauge of the popularity of this feature. This
is the most voted-on issue in our JIRA base.
https://issues.apache.org/jira/browse/FLEX-33086
https://issues.apache.org/jira/secure/ViewVoters!default.jspa?id=12538816
Thanks,
Om
On Tue, Nov 27, 2012 at 11:28 AM, Jeffry Houser <je...@dot-com-it.com>wrote:
>
> As I understand it, Maven is an automated build tool. Kind of like ANT
> on steroids.
>
>
> On 11/27/2012 2:20 PM, Harbs wrote:
>
>> 0. I have never quite figured out what Maven is or why I'd want to use
>> it. (and I do speak yiddish…) ;-)
>>
>> If someone could enlighten me, I could change my mind…
>>
>> Harbs
>>
>> On Nov 27, 2012, at 8:46 PM, Alex Harui wrote:
>>
>> 1. Number of people who will use Maven to develop Flex apps at your
>>> company
>>> (0 if you have no interest in using Maven).
>>>
>>
>>
>
Re: [Discuss] Maven and Apache Flex
Posted by Jeffry Houser <je...@dot-com-it.com>.
As I understand it, Maven is an automated build tool. Kind of like
ANT on steroids.
On 11/27/2012 2:20 PM, Harbs wrote:
> 0. I have never quite figured out what Maven is or why I'd want to use it. (and I do speak yiddish…) ;-)
>
> If someone could enlighten me, I could change my mind…
>
> Harbs
>
> On Nov 27, 2012, at 8:46 PM, Alex Harui wrote:
>
>> 1. Number of people who will use Maven to develop Flex apps at your company
>> (0 if you have no interest in using Maven).
>
Re: [POLL] Maven and Apache Flex
Posted by Harbs <ha...@gmail.com>.
0. I have never quite figured out what Maven is or why I'd want to use it. (and I do speak yiddish…) ;-)
If someone could enlighten me, I could change my mind…
Harbs
On Nov 27, 2012, at 8:46 PM, Alex Harui wrote:
> 1. Number of people who will use Maven to develop Flex apps at your company
> (0 if you have no interest in using Maven).
Re: [POLL] Maven and Apache Flex
Posted by Simon Morvan <ga...@zone84.net>.
Le 27/11/2012 19:46, Alex Harui a écrit :
> 1. Number of people who will use Maven to develop Flex apps at your company
> (0 if you have no interest in using Maven).
5-10
(Small agency, we're using maven to build /every/ Flash/Flex based
project since Flex 3).
> 2. Maven would be used to develop apps for FlashPlayer in the browser (yes
> or no)
yes (currently used)
> 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> no)
yes (currently used)
> 4. Maven would be used to develop apps for AIR on Android (yes or no)
yes (currently used, with home made scripts for the final apk packaging)
> 5. Maven would be used to develop apps for AIR on IOS (yes or no)
yes (currently used, with home made scripts for the final apk packaging)
> 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> neutral, 1 = acceptable, 2 = preferred)
> a) You must manually download the Player SDK and AIR SDK from the Adobe
> site and set up environment variables pointing to them
-1 : the whole point of using maven project descriptor is to streamline
project builds would it be on the developper station, the integration
server or the release process. Dependent artifacts have to be
'mavenized' and available on a shared repo (private or public).
> b) You must download and install a Maven plug-in from the Apache Flex
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
2
> c) You must download and install a Maven plug-in from the Adobe
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
1 Aactually, it's more to be sure that every artifact needed for a given
Flex version will be gathered a the same place instead of living on
several repositories, leading to potential issues. But if versioning of
playerglobal/air sdk is completely independant of flex versioning AND if
the compatiblity matrix between each others can be expressed in form of
maven dependency graph, it wouldn't be an issue to ship some artifact
from Adobe's repo and others from Apache's repo.
> d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> desktops/laptops, but not for AIR apps on Android/IOS. To target
> Android/IOS, you must use one of the first three implementations
2, this is currently the case with Velo's mavenized SDK (prior SDK
"Apachization")
> e) We will manually download the Player SDKs and AIR SDKs and put them
> in our local/private Maven repo.
0
> f) We would use a utility application that would download the Player
> SDKs and AIR SDKs (prompting you to accept the license) and put them
> in our local/private Maven repo.
1 (actually, "e" is implemented by Christopher's toolset but an
"official" and maintained tool would be preferable).
b & c : I think there's a confusion between the maven plugin that would
be required to actually build something with mxmlc API and the SDK
dependency artifact.
There should no be licensing issue with the plugin itself but with the
SDK artifact (AIR & playerglobal) only. And it'll be prompted for a
license approval each time you use a SDK version for the first time.
--
Simon
AW: [POLL] Maven and Apache Flex
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
I'll reply to this as I never really got the initial post
1. Number of people who will use Maven to develop Flex apps at your company
(0 if you have no interest in using Maven).
1 (I'm a one-man-show)
2. Maven would be used to develop apps for FlashPlayer in the browser (yes
or no)
yes
3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
no)
yes
4. Maven would be used to develop apps for AIR on Android (yes or no)
yes
5. Maven would be used to develop apps for AIR on IOS (yes or no)
no
6. Rate the following proposed implementations (-1 = not acceptable, 0 =
neutral, 1 = acceptable, 2 = preferred)
a) You must manually download the Player SDK and AIR SDK from the Adobe
site and set up environment variables pointing to them
0
b) You must download and install a Maven plug-in from the Apache Flex
site. The first time you use Maven on a computer, it will ask you
to accept the Adobe license agreement.
2
c) You must download and install a Maven plug-in from the Adobe
site. The first time you use Maven on a computer, it will ask you
to accept the Adobe license agreement.
1
d) Maven can be used as-is for FlashPlayer apps and AIR apps on
desktops/laptops, but not for AIR apps on Android/IOS. To target
Android/IOS, you must use one of the first three implementations
2 (Would prefer normal Flex applications to be built without setting up or having to agree to anything and to have an Apache Plugin handling the download of restricted Air stuff)
e) We will manually download the Player SDKs and AIR SDKs and put them
in our local/private Maven repo.
0 (This ist he current situation using the Mavenizer)
f) We would use a utility application that would download the Player
SDKs and AIR SDKs (prompting you to accept the license) and put them
in our local/private Maven repo.
1 (Would be an extended Mavenizer that also does downloads)
Chris
Von: Jose Barragan Andrade [mailto:pepebarragan@me.com]
Gesendet: Dienstag, 27. November 2012 22:07
An: flex-dev@incubator.apache.org
Betreff: Re: [POLL] Maven and Apache Flex
My votes:
1. Number of people who will use Maven to develop Flex apps at your company
(0 if you have no interest in using Maven).
10
2. Maven would be used to develop apps for FlashPlayer in the browser (yes
or no)
yes
3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
no)
yes
4. Maven would be used to develop apps for AIR on Android (yes or no)
yes
5. Maven would be used to develop apps for AIR on IOS (yes or no)
no
6. Rate the following proposed implementations (-1 = not acceptable, 0 =
neutral, 1 = acceptable, 2 = preferred)
a) You must manually download the Player SDK and AIR SDK from the Adobe
site and set up environment variables pointing to them
0
b) You must download and install a Maven plug-in from the Apache Flex
site. The first time you use Maven on a computer, it will ask you
to accept the Adobe license agreement.
2
c) You must download and install a Maven plug-in from the Adobe
site. The first time you use Maven on a computer, it will ask you
to accept the Adobe license agreement.
1
d) Maven can be used as-is for FlashPlayer apps and AIR apps on
desktops/laptops, but not for AIR apps on Android/IOS. To target
Android/IOS, you must use one of the first three implementations
1
e) We will manually download the Player SDKs and AIR SDKs and put them
in our local/private Maven repo.
-1
f) We would use a utility application that would download the Player
SDKs and AIR SDKs (prompting you to accept the license) and put them
in our local/private Maven repo.
1
--
Jose Barragan
Software Architect Chief
Re: [POLL] Maven and Apache Flex
Posted by Jose Barragan Andrade <pe...@me.com>.
My votes:
> 1. Number of people who will use Maven to develop Flex apps at your company
> (0 if you have no interest in using Maven).
10
>
> 2. Maven would be used to develop apps for FlashPlayer in the browser (yes
> or no)
yes
>
> 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> no)
yes
>
> 4. Maven would be used to develop apps for AIR on Android (yes or no)
yes
>
> 5. Maven would be used to develop apps for AIR on IOS (yes or no)
no
>
> 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> neutral, 1 = acceptable, 2 = preferred)
> a) You must manually download the Player SDK and AIR SDK from the Adobe
> site and set up environment variables pointing to them
0
> b) You must download and install a Maven plug-in from the Apache Flex
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
2
> c) You must download and install a Maven plug-in from the Adobe
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
1
> d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> desktops/laptops, but not for AIR apps on Android/IOS. To target
> Android/IOS, you must use one of the first three implementations
1
> e) We will manually download the Player SDKs and AIR SDKs and put them
> in our local/private Maven repo.
-1
> f) We would use a utility application that would download the Player
> SDKs and AIR SDKs (prompting you to accept the license) and put them
> in our local/private Maven repo.
1
--
Jose Barragan
Software Architect Chief
RE: [POLL] Maven and Apache Flex
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
Clarifying my answer... we have a private/closed development network. It becomes difficult to get outside resources in on these machines. Servers/clients on this network do not communicate with the outside world.
Tools that download files directly require lots of work arounds.
-Mark
-----Original Message-----
From: Kessler CTR Mark J [mailto:mark.kessler.ctr@usmc.mil]
Sent: Wednesday, November 28, 2012 6:47
To: flex-dev@incubator.apache.org
Subject: RE: [POLL] Maven and Apache Flex
0 - Not using maven.
-Mark
-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Tuesday, November 27, 2012 13:46
To: flex-dev@incubator.apache.org
Subject: [POLL] Maven and Apache Flex
Hi Folks,
There have been some recent discussions about Maven and how it could work
with Apache Flex. There are several possibilities, but none of them are
perfect because of Adobe licensing requirements. This poll is only about
how you use or plan to use Apache Flex and Maven to build apps that use an
Adobe runtime (Adobe Flash Player or Adobe AIR including Adobe AIR packaged
for Android or IOS). We¹ll worry about other Apache Flex scenarios in the
future. This poll also assumes that the Adobe will not change its SDK
licensing and requires that you accept the licensing terms at least once.
Also, you can substitute the word "Maven" for any Maven-like tool that uses
Maven files.
Please answer the following:
1. Number of people who will use Maven to develop Flex apps at your company
(0 if you have no interest in using Maven).
2. Maven would be used to develop apps for FlashPlayer in the browser (yes
or no)
3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
no)
4. Maven would be used to develop apps for AIR on Android (yes or no)
5. Maven would be used to develop apps for AIR on IOS (yes or no)
6. Rate the following proposed implementations (-1 = not acceptable, 0 =
neutral, 1 = acceptable, 2 = preferred)
a) You must manually download the Player SDK and AIR SDK from the Adobe
site and set up environment variables pointing to them
b) You must download and install a Maven plug-in from the Apache Flex
site. The first time you use Maven on a computer, it will ask you
to accept the Adobe license agreement.
c) You must download and install a Maven plug-in from the Adobe
site. The first time you use Maven on a computer, it will ask you
to accept the Adobe license agreement.
d) Maven can be used as-is for FlashPlayer apps and AIR apps on
desktops/laptops, but not for AIR apps on Android/IOS. To target
Android/IOS, you must use one of the first three implementations
e) We will manually download the Player SDKs and AIR SDKs and put them
in our local/private Maven repo.
f) We would use a utility application that would download the Player
SDKs and AIR SDKs (prompting you to accept the license) and put them
in our local/private Maven repo.
Thanks in advance. Remember that polls are not binding, but your input is
much appreciated.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
RE: [POLL] Maven and Apache Flex
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
0 - Not using maven.
-Mark
-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Tuesday, November 27, 2012 13:46
To: flex-dev@incubator.apache.org
Subject: [POLL] Maven and Apache Flex
Hi Folks,
There have been some recent discussions about Maven and how it could work
with Apache Flex. There are several possibilities, but none of them are
perfect because of Adobe licensing requirements. This poll is only about
how you use or plan to use Apache Flex and Maven to build apps that use an
Adobe runtime (Adobe Flash Player or Adobe AIR including Adobe AIR packaged
for Android or IOS). We¹ll worry about other Apache Flex scenarios in the
future. This poll also assumes that the Adobe will not change its SDK
licensing and requires that you accept the licensing terms at least once.
Also, you can substitute the word "Maven" for any Maven-like tool that uses
Maven files.
Please answer the following:
1. Number of people who will use Maven to develop Flex apps at your company
(0 if you have no interest in using Maven).
2. Maven would be used to develop apps for FlashPlayer in the browser (yes
or no)
3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
no)
4. Maven would be used to develop apps for AIR on Android (yes or no)
5. Maven would be used to develop apps for AIR on IOS (yes or no)
6. Rate the following proposed implementations (-1 = not acceptable, 0 =
neutral, 1 = acceptable, 2 = preferred)
a) You must manually download the Player SDK and AIR SDK from the Adobe
site and set up environment variables pointing to them
b) You must download and install a Maven plug-in from the Apache Flex
site. The first time you use Maven on a computer, it will ask you
to accept the Adobe license agreement.
c) You must download and install a Maven plug-in from the Adobe
site. The first time you use Maven on a computer, it will ask you
to accept the Adobe license agreement.
d) Maven can be used as-is for FlashPlayer apps and AIR apps on
desktops/laptops, but not for AIR apps on Android/IOS. To target
Android/IOS, you must use one of the first three implementations
e) We will manually download the Player SDKs and AIR SDKs and put them
in our local/private Maven repo.
f) We would use a utility application that would download the Player
SDKs and AIR SDKs (prompting you to accept the license) and put them
in our local/private Maven repo.
Thanks in advance. Remember that polls are not binding, but your input is
much appreciated.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: [POLL] Maven and Apache Flex
Posted by Bogdan DINU <fl...@gmail.com>.
Hello,
here are my answers
> 1. Number of people who will use Maven to develop Flex apps at your company
> (0 if you have no interest in using Maven).
>
3
> 2. Maven would be used to develop apps for FlashPlayer in the browser (yes
> or no)
>
yes
>
> 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> no)
>
>
yes
> 4. Maven would be used to develop apps for AIR on Android (yes or no)
>
no
>
> 5. Maven would be used to develop apps for AIR on IOS (yes or no)
>
no
>
> 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> neutral, 1 = acceptable, 2 = preferred)
> a) You must manually download the Player SDK and AIR SDK from the Adobe
> site and set up environment variables pointing to them
>
-1
> b) You must download and install a Maven plug-in from the Apache Flex
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
0
> c) You must download and install a Maven plug-in from the Adobe
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
0
> d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> desktops/laptops, but not for AIR apps on Android/IOS. To target
> Android/IOS, you must use one of the first three implementations
>
2
> e) We will manually download the Player SDKs and AIR SDKs and put them
> in our local/private Maven repo.
>
-1
> f) We would use a utility application that would download the Player
> SDKs and AIR SDKs (prompting you to accept the license) and put them
> in our local/private Maven repo.
>
-1
Best regards,
Bogdan
Re: [POLL] Maven and Apache Flex
Posted by Omar Gonzalez <om...@gmail.com>.
On Tue, Nov 27, 2012 at 10:46 AM, Alex Harui <ah...@adobe.com> wrote:
> Hi Folks,
>
> There have been some recent discussions about Maven and how it could work
> with Apache Flex. There are several possibilities, but none of them are
> perfect because of Adobe licensing requirements. This poll is only about
> how you use or plan to use Apache Flex and Maven to build apps that use an
> Adobe runtime (Adobe Flash Player or Adobe AIR including Adobe AIR packaged
> for Android or IOS). We¹ll worry about other Apache Flex scenarios in the
> future. This poll also assumes that the Adobe will not change its SDK
> licensing and requires that you accept the licensing terms at least once.
>
> Also, you can substitute the word "Maven" for any Maven-like tool that uses
> Maven files.
>
> Please answer the following:
>
> 1. Number of people who will use Maven to develop Flex apps at your company
> (0 if you have no interest in using Maven).
>
0.
No input on other points.
-omar
Re: [POLL] Maven and Apache Flex
Posted by Greg Reddin <gr...@gmail.com>.
Just realized I answered one of the questions incorrectly. See below:
On Tue, Nov 27, 2012 at 1:58 PM, Greg Reddin <gr...@gmail.com> wrote:
> b) You must download and install a Maven plug-in from the Apache Flex
>> site. The first time you use Maven on a computer, it will ask you
>> to accept the Adobe license agreement.
>>
>
> +1
>
This should have been a 2.
Re: [POLL] Maven and Apache Flex
Posted by Greg Reddin <gr...@gmail.com>.
On Tue, Nov 27, 2012 at 12:46 PM, Alex Harui <ah...@adobe.com> wrote:
> 1. Number of people who will use Maven to develop Flex apps at your company
> (0 if you have no interest in using Maven).
>
6 - 8
> 2. Maven would be used to develop apps for FlashPlayer in the browser (yes
> or no)
>
Yes
>
> 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> no)
>
No.
>
> 4. Maven would be used to develop apps for AIR on Android (yes or no)
>
Yes.
>
> 5. Maven would be used to develop apps for AIR on IOS (yes or no)
>
Yes
>
> 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> neutral, 1 = acceptable, 2 = preferred)
> a) You must manually download the Player SDK and AIR SDK from the Adobe
> site and set up environment variables pointing to them
>
-1
> b) You must download and install a Maven plug-in from the Apache Flex
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
+1
> c) You must download and install a Maven plug-in from the Adobe
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
>
0
> d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> desktops/laptops, but not for AIR apps on Android/IOS. To target
> Android/IOS, you must use one of the first three implementations
>
-1
> e) We will manually download the Player SDKs and AIR SDKs and put them
> in our local/private Maven repo.
>
Who is "we"? If "we" is my company, the answer is 0 to somewhere near +1.
If "we" is Apache Flex, I'll have to think about the ramifications of that.
I don't mind putting dependencies in my company's private repo for things
like that, but if Option b was available I'd prefer that.
> f) We would use a utility application that would download the Player
> SDKs and AIR SDKs (prompting you to accept the license) and put them
> in our local/private Maven repo.
>
-1 Would rather do this manually according to my own repo methodology
(artifactory vs. nexus, choosing where to put them, etc.
Greg
Re: [POLL] Maven and Apache Flex
Posted by Paras Sheth <pa...@morebinary.com>.
Hi,
Here are my answers
> Alex Harui <ma...@adobe.com>
> 27 November 2012 18:46
> Hi Folks,
>
> There have been some recent discussions about Maven and how it could work
> with Apache Flex. There are several possibilities, but none of them are
> perfect because of Adobe licensing requirements. This poll is only about
> how you use or plan to use Apache Flex and Maven to build apps that use an
> Adobe runtime (Adobe Flash Player or Adobe AIR including Adobe AIR
> packaged
> for Android or IOS). We¹ll worry about other Apache Flex scenarios in the
> future. This poll also assumes that the Adobe will not change its SDK
> licensing and requires that you accept the licensing terms at least once.
>
> Also, you can substitute the word "Maven" for any Maven-like tool that
> uses
> Maven files.
>
> Please answer the following:
>
> 1. Number of people who will use Maven to develop Flex apps at your
> company
> (0 if you have no interest in using Maven).
10
>
> 2. Maven would be used to develop apps for FlashPlayer in the browser (yes
> or no)
yes
>
> 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or
> no)
yes
>
> 4. Maven would be used to develop apps for AIR on Android (yes or no)
no
>
> 5. Maven would be used to develop apps for AIR on IOS (yes or no)
no
>
> 6. Rate the following proposed implementations (-1 = not acceptable, 0 =
> neutral, 1 = acceptable, 2 = preferred)
> a) You must manually download the Player SDK and AIR SDK from the Adobe
> site and set up environment variables pointing to them
-1
> b) You must download and install a Maven plug-in from the Apache Flex
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
1
> c) You must download and install a Maven plug-in from the Adobe
> site. The first time you use Maven on a computer, it will ask you
> to accept the Adobe license agreement.
0
> d) Maven can be used as-is for FlashPlayer apps and AIR apps on
> desktops/laptops, but not for AIR apps on Android/IOS. To target
> Android/IOS, you must use one of the first three implementations
2
> e) We will manually download the Player SDKs and AIR SDKs and put them
> in our local/private Maven repo.
-1
> f) We would use a utility application that would download the Player
> SDKs and AIR SDKs (prompting you to accept the license) and put them
> in our local/private Maven repo.
-1
>
> Thanks in advance. Remember that polls are not binding, but your input is
> much appreciated.
>
Thanks
Paras