Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: "christofer.dutz@c-ware.de" <christofer.dutz@c-ware.de>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Tue, 16 Oct 2012 22:36:00 +0200
Subject: AW: AW: AW: AW: Flex Maven FDK Generator RC1
Thread-Topic: AW: AW: AW: Flex Maven FDK Generator RC1
Thread-Index: Ac2rzOvIz1NE6pieRz2jBhz7GvdzpQAAHQr5AAD09tAAAM/jdAACUT3g
Message-ID: 
 <66E38C42347D6446BF7FCB22C3D3878072DFAA5966@ECCR06PUBLIC.exchange.local>
References: 
 <66E38C42347D6446BF7FCB22C3D3878072DFAA595A@ECCR06PUBLIC.exchange.local>
 <CCA3037A.473AA%aharui@adobe.com>
In-Reply-To: <CCA3037A.473AA%aharui@adobe.com>
Accept-Language: de-DE
Content-Language: de-DE
acceptlanguage: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Well you could disable the accounts if accepting a changed license agreemen=
t is needed and provide the means to re-activate it by accepting the licens=
es ... just a thought.


[ C h r i s t o f e r=A0 D u t z ]

C-Ware IT-Service
Inhaber
Dipl. Inf. Christofer Dutz
Karlstra=DFe. 104, 64285 Darmstadt


=A0=A0 IT- und Systemh=E4user

fon:=A0 0 61 51 / 27315 - 61
fax:=A0 0 61 51 / 27315 - 64
mobil:=A0 0171 / 7 444 2 33
email:=A0 christofer.dutz@c-ware.de
http://www.c-ware.de

UStId-Nr. DE195700962


-----Urspr=FCngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]=20
Gesendet: Dienstag, 16. Oktober 2012 21:29
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: Flex Maven FDK Generator RC1


On 10/16/12 12:11 PM, "christofer.dutz@c-ware.de"
<christofer.dutz@c-ware.de> wrote:
> Maven doesn't provide the means to stall a dependency resolution and=20
> prompt the user for accepting a license. The only thing you could do=20
> is to protect access to the repository.
It looks like the antrun plugin would allow me to use ant to prompt the use=
r.  Haven't tried it yet.

> One way you could simuplate this would by by starting any turnkey=20
> nexus or artifactory server. There you could deploy some artifacts and=20
> configure the repo not to allow anonymous access.
> Now someone would need a login in order to fetch the libs. You could=20
> link the process of creating an account to accepting the licenses you=20
> want. As soon as someone creates a new account and accpts the licennse=20
> agreement, the nexus account is created and the user could use this=20
> account to access the artifacts.
>=20
I'm not sure that would be sufficient for Adobe.  For example, we altered t=
he license between Flex 4 and Flex 4.5.  A login wouldn't let you pick up t=
hat change.

Maybe Apache Flex or Adobe could provide a plugin to show the licenses like=
 we do in the installer and additionally, remember which ones you accepted =
so that subsequent builds can be unattended.

--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui