Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: neutral (nike.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: Thu, 24 May 2012 14:40:58 +0200
Subject: AW: Library Versions used in Flex SDK
Thread-Topic: Library Versions used in Flex SDK
Thread-Index: Ac05pMTQwGyoJXNRT3WEeUkTElWIzgABS6dg
Message-ID: 
 <66E38C42347D6446BF7FCB22C3D3878072C87DD922@ECCR06PUBLIC.exchange.local>
References: 
 <CAMFKFRgQ7oOaCp2u7qvJFakORk-kfO_zZ5nqGU9s+rnyT1iW=w@mail.gmail.com>
 <CBE2A9B5.40C17%aharui@adobe.com>
 <CAMFKFRhrGSB3fDm=HYX3Ob3wXWE8-j3+wr=5NM_Z=LEyvzMiUw@mail.gmail.com>
 <D4A5F52B-C424-4AEF-8AB6-B5130831C528@classsoftware.com>
In-Reply-To: <D4A5F52B-C424-4AEF-8AB6-B5130831C528@classsoftware.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

Hi Justin,

well there actually is no change at all to Flex nessessary to use it in Mav=
en, you only have to provide metadata to each jar/swf/swc/swz in the SDK. T=
his metadata tells maven, which libraries a library depends on and automati=
cally takes care of downloading them. The second thing needed would be some=
one to publish the SDK together with it's metadata in a public repository (=
Ideally Maven Central).

Besides the ASDoc issues, I currently don't know of any pressing issues, bu=
t currently I have to take care of generating the Metadata on my own and I =
thought it would be a good thing for the people maintaining Flex to also ma=
intain its Metadata :-)

Chris


-----Urspr=FCngliche Nachricht-----
Von: Justin Mclean [mailto:justin@classsoftware.com]=20
Gesendet: Donnerstag, 24. Mai 2012 13:59
An: flex-dev@incubator.apache.org
Betreff: Re: Library Versions used in Flex SDK

Hi,

> We don't have to miss the main point: get Apache Flex coexist with=20
> other technologies
I think we all agree that is a good way forward/outcome. However I don't re=
ally know (and I assume other people as well) the details on exactly what a=
re the issues are in getting the Flex SDK working with Mavin.

> What is real is that refactoring Apache Flex SDK to take into account=20
> this kind of build management system will help a lot in this necesity.
What changes would be required to the current structure to make like easier=
 for Mavin? Are there any simple changes that would make it easier for the =
Flex SDK to work with Mavin?

Thanks,
Justin