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: domain of espen.skogen@jpmorgan.com
 designates 159.53.78.135 as permitted sender)
From: "Skogen, Espen" <espen.skogen@jpmorgan.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Subject: RE: Flex and Maven
Thread-Topic: Flex and Maven
Thread-Index: 
 AczRJKmN5/nABKJOQiWxnrWP5sBOmQAFnFCAAAdaUYAAAA4CgAAF0mqAAAW2jAAACMYNgAAW6PMAAAGmO1A=
Date: Fri, 13 Jan 2012 15:59:59 +0000
Message-ID: 
 <20269C1D2B00D24682F1C89E6F0A90A028F2C7@SBOCMX001.exchad.jpmchase.net>
References: 
 <20269C1D2B00D24682F1C89E6F0A90A028D6CA@SBOCMX001.exchad.jpmchase.net>
	<CAKWVykUxvgRxwtVo=YN5S4GFaWV_HWF4PQSQvYv4nOnDLw3ptA@mail.gmail.com>
	<CAHysGrpBaecZGPXBMfDz93F3u=XNcnUMSHkaeTZ=QU=L4GWP1Q@mail.gmail.com>
	<CABRWxwdCwG4ro0i1r2qGSBXG=UmS9jV_Pi+oBvJZ=aFDech=_g@mail.gmail.com>
	<CAKuZoVKKVy0PWLXEq1OtoBUHN4vpsqGdfVSkOV=Lfq2ArUmatw@mail.gmail.com>
	<CABT4z6sYfVyG0d3VoGV8LYx3JSjPZ1sj3xkrvOnVDkJoir_S5Q@mail.gmail.com>
	<CAJNVnFGeDM8oG-==g7HnZYEKeJ_tdZJ00NZZ8tSfyONYDO-6BQ@mail.gmail.com>
 <CABT4z6sELOdEL3FDuqDAAnStGYqB6k-o2FAZf7LBRPbBO53JQA@mail.gmail.com>
In-Reply-To: 
 <CABT4z6sELOdEL3FDuqDAAnStGYqB6k-o2FAZf7LBRPbBO53JQA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"

Apache has it's own maven repo=2E I certainly wouldn't encourage using SVN =
for a maven repo simulation:)=0D=0A=0D=0AIt's available here: http://reposi=
tory=2Eapache=2Eorg/=0D=0A=0D=0A=0D=0A=0D=0A=0D=0A=0D=0A=0D=0AEspen Skogen =
| Vice President | IB Tech Market | Investment Bank | J=2EP=2E Morgan | 125=
 London Wall, EC2Y 5AJ,  London, United Kingdom | T: +442077420836 | espen=
=2Eskogen@jpmorgan=2Ecom | jpmorgan=2Ecom=0D=0A=0D=0A=0D=0A-----Original Me=
ssage-----=0D=0AFrom: Scott Delamater [mailto:scott=2Edelamater@gmail=2Ecom=
] =0D=0ASent: 13 January 2012 15:11=0D=0ATo: flex-dev@incubator=2Eapache=2E=
org=0D=0ASubject: Re: Flex and Maven=0D=0A=0D=0AOne consideration, though, =
is that Apache doesn't allow binaries in the=0D=0Asource code=2E (Or maybe =
I've misunderstood some of the rules?) So our swcs=0D=0Awould need to live =
in some other repo, which may be outside the=0D=0Aresponsibilities of this =
group=2E (Although it does seem like a good=0D=0A"extracurricular" activity=
 for this group=2E)=0D=0A=0D=0AsD=0D=0A=0D=0AOn Thu, Jan 12, 2012 at 9:15 P=
M, Gautam Pandey <gkp590@gmail=2Ecom> wrote:=0D=0A=0D=0A> +1 Yes we need be=
tter maven support for flex=2E Because of unavailability of=0D=0A> maven su=
pport  we r not migrating to newer version=2E=0D=0A>=0D=0A> Thanks=0D=0A> G=
autam=0D=0A>  On Jan 13, 2012 5:34 AM, "Scott Delamater" <scott=2Edelamater=
@gmail=2Ecom>=0D=0A> wrote:=0D=0A>=0D=0A> > I agree, this would be a huge a=
dd for enterprise work=2E=0D=0A> >=0D=0A> > Especially with the recent XSS =
patch fiasco, having artifacts for the "A"=0D=0A> > variants of the SDKs av=
ailable would've been a big help for our team at=0D=0A> > Shutterfly=2E I a=
ssume other enterprise consumers have generated similar=0D=0A> > artifacts,=
 and assuming we were all willing to share those artifacts, I=0D=0A> > coul=
d see it being mutually beneficial=2E=0D=0A> >=0D=0A> > sD=0D=0A> >=0D=0A> =
> On Thu, Jan 12, 2012 at 2:20 PM, Remi P <rpatriar@gmail=2Ecom> wrote:=0D=
=0A> >=0D=0A> > > +1=0D=0A> > >=0D=0A> > > It's really a major point for en=
treprise developments that Flex SDK=0D=0A> > > artifacts can be deployed on=
 central repo=0D=0A> > > Just for example, the last Adobe release of Flex S=
DK 4=2E6 has not yet=0D=0A> been=0D=0A> > > deployed on sonatype repository=
=0D=0A> > >=0D=0A> > > Remi=0D=0A> > >=0D=0A> > >=0D=0A> > > On Thu, Jan 12=
, 2012 at 7:33 PM, John Childress <=0D=0A> > john=2Echildress@gmail=2Ecom=
=0D=0A> > > >wrote:=0D=0A> > >=0D=0A> > > > +1=0D=0A> > > >=0D=0A> > > > On=
 Thu, Jan 12, 2012 at 12:32 PM, Michel Boudreau=0D=0A> > > > <michelboudrea=
u@gmail=2Ecom>wrote:=0D=0A> > > >=0D=0A> > > > > +1 on this=2E  Totally agr=
ee that Flex should have better maven=0D=0A> > support=2E=0D=0A> > > > >=0D=
=0A> > > > > On Thu, Jan 12, 2012 at 10:01 AM, Greg Reddin <gredbug@gmail=
=2Ecom>=0D=0A> > > wrote:=0D=0A> > > > >=0D=0A> > > > > > On Thu, Jan 12, 2=
012 at 6:21 AM, Skogen, Espen=0D=0A> > > > > > <espen=2Eskogen@jpmorgan=2Ec=
om> wrote:=0D=0A> > > > > > > Hi all,=0D=0A> > > > > > >=0D=0A> > > > > > >=
 How do you all feel about publishing Flex as Maven artifacts,=0D=0A> now=
=0D=0A> > > > that=0D=0A> > > > > > we get going?=0D=0A> > > > > > > JPM an=
d other banks I've worked in all rely on Maven and=0D=0A> > Flexmojos=0D=0A=
> > > > for=0D=0A> > > > > > their Flex build process - It would make sense=
 if the Apache Flex=0D=0A> > > > project=0D=0A> > > > > > used Maven as wel=
l, so that as we release, it's immediately=0D=0A> > available=0D=0A> > > > =
> from=0D=0A> > > > > > the Apache maven repo=2E=0D=0A> > > > > > >=0D=0A> =
> > > > > > Thoughts? This wouldn't limit the use of Ant for those who=0D=
=0A> prefer=0D=0A> > > > that=0D=0A> > > > > -=0D=0A> > > > > > it would ju=
st simplify the process for everybody using Flexmojos=2E=0D=0A> > > > > >=
=0D=0A> > > > > > As soon as there is code to publish I intend to take a lo=
ok at=0D=0A> it=2E=0D=0A> > > I'd=0D=0A> > > > > > really like to see us pu=
blish to Maven repos=2E=0D=0A> > > > > >=0D=0A> > > > >=0D=0A> > > > >=0D=
=0A> > > > >=0D=0A> > > > > --=0D=0A> > > > > Michel Boudreau=0D=0A> > > > =
>=0D=0A> > > > > "If at first you don't succeed, use a bigger hammer=2E" - =
Unofficial=0D=0A> > > motto=0D=0A> > > > of=0D=0A> > > > > the Royal Electr=
ical and Mechanical Engineers=0D=0A> > > > >=0D=0A> > > >=0D=0A> > > >=0D=
=0A> > > >=0D=0A> > > > --=0D=0A> > > > John Childress=0D=0A> > > > 713-234=
-0427=0D=0A> > > > john=2Echildress@gmail=2Ecom=0D=0A> > > >=0D=0A> > >=0D=
=0A> >=0D=0A>=0D=0AThis email is confidential and subject to important disc=
laimers and=0D=0Aconditions including on offers for the purchase or sale of=
=0D=0Asecurities, accuracy and completeness of information, viruses,=0D=0Ac=
onfidentiality, legal privilege, and legal entity disclaimers,=0D=0Aavailab=
le at http://www=2Ejpmorgan=2Ecom/pages/disclosures/email=2E