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
che.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, le
ailto:aha...@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.d...@c-ware.de"
> wrote:
>
files)
Chris
-Ursprüngliche Nachricht-
Von: Alex Harui [mailto:aha...@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.d...@c-ware.
On 11/29/12 11:48 AM, "christofer.d...@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
[mailto:aha...@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.d...@c-ware.de"
wrote:
> No you would not leave the key under the doormat ... the t
On 11/29/12 11:11 AM, "christofer.d...@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.
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 F
