incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Skogen, Espen" <espen.sko...@jpmorgan.com>
Subject RE: Flex and Maven
Date Fri, 13 Jan 2012 15:59:59 GMT
Apache has it's own maven repo. I certainly wouldn't encourage using SVN for a maven repo simulation:)

It's available here: http://repository.apache.org/






Espen Skogen | Vice President | IB Tech Market | Investment Bank | J.P. Morgan | 125 London
Wall, EC2Y 5AJ,  London, United Kingdom | T: +442077420836 | espen.skogen@jpmorgan.com | jpmorgan.com


-----Original Message-----
From: Scott Delamater [mailto:scott.delamater@gmail.com] 
Sent: 13 January 2012 15:11
To: flex-dev@incubator.apache.org
Subject: Re: Flex and Maven

One consideration, though, is that Apache doesn't allow binaries in the
source code. (Or maybe I've misunderstood some of the rules?) So our swcs
would need to live in some other repo, which may be outside the
responsibilities of this group. (Although it does seem like a good
"extracurricular" activity for this group.)

sD

On Thu, Jan 12, 2012 at 9:15 PM, Gautam Pandey <gkp590@gmail.com> wrote:

> +1 Yes we need better maven support for flex. Because of unavailability of
> maven support  we r not migrating to newer version.
>
> Thanks
> Gautam
>  On Jan 13, 2012 5:34 AM, "Scott Delamater" <scott.delamater@gmail.com>
> wrote:
>
> > I agree, this would be a huge add for enterprise work.
> >
> > Especially with the recent XSS patch fiasco, having artifacts for the "A"
> > variants of the SDKs available would've been a big help for our team at
> > Shutterfly. I assume other enterprise consumers have generated similar
> > artifacts, and assuming we were all willing to share those artifacts, I
> > could see it being mutually beneficial.
> >
> > sD
> >
> > On Thu, Jan 12, 2012 at 2:20 PM, Remi P <rpatriar@gmail.com> wrote:
> >
> > > +1
> > >
> > > It's really a major point for entreprise developments that Flex SDK
> > > artifacts can be deployed on central repo
> > > Just for example, the last Adobe release of Flex SDK 4.6 has not yet
> been
> > > deployed on sonatype repository
> > >
> > > Remi
> > >
> > >
> > > On Thu, Jan 12, 2012 at 7:33 PM, John Childress <
> > john.childress@gmail.com
> > > >wrote:
> > >
> > > > +1
> > > >
> > > > On Thu, Jan 12, 2012 at 12:32 PM, Michel Boudreau
> > > > <michelboudreau@gmail.com>wrote:
> > > >
> > > > > +1 on this.  Totally agree that Flex should have better maven
> > support.
> > > > >
> > > > > On Thu, Jan 12, 2012 at 10:01 AM, Greg Reddin <gredbug@gmail.com>
> > > wrote:
> > > > >
> > > > > > On Thu, Jan 12, 2012 at 6:21 AM, Skogen, Espen
> > > > > > <espen.skogen@jpmorgan.com> wrote:
> > > > > > > Hi all,
> > > > > > >
> > > > > > > How do you all feel about publishing Flex as Maven artifacts,
> now
> > > > that
> > > > > > we get going?
> > > > > > > JPM and other banks I've worked in all rely on Maven and
> > Flexmojos
> > > > for
> > > > > > their Flex build process - It would make sense if the Apache
Flex
> > > > project
> > > > > > used Maven as well, so that as we release, it's immediately
> > available
> > > > > from
> > > > > > the Apache maven repo.
> > > > > > >
> > > > > > > Thoughts? This wouldn't limit the use of Ant for those
who
> prefer
> > > > that
> > > > > -
> > > > > > it would just simplify the process for everybody using Flexmojos.
> > > > > >
> > > > > > As soon as there is code to publish I intend to take a look
at
> it.
> > > I'd
> > > > > > really like to see us publish to Maven repos.
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Michel Boudreau
> > > > >
> > > > > "If at first you don't succeed, use a bigger hammer." - Unofficial
> > > motto
> > > > of
> > > > > the Royal Electrical and Mechanical Engineers
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > John Childress
> > > > 713-234-0427
> > > > john.childress@gmail.com
> > > >
> > >
> >
>
This email is confidential and subject to important disclaimers and
conditions including on offers for the purchase or sale of
securities, accuracy and completeness of information, viruses,
confidentiality, legal privilege, and legal entity disclaimers,
available at http://www.jpmorgan.com/pages/disclosures/email.  

Mime
View raw message