Re: AW: [FlexJS] First successful build of a FlexJS application using Flexmojos

2014-11-14 Thread Erik de Bruin
27;s up to me, I don't need > another > >> release ;-) > >> > >> I was more thinking of using the lessons learned when releasing other > >> parts. > >> > >> Chris > >> > >> ________ >

Re: AW: [FlexJS] First successful build of a FlexJS application using Flexmojos

2014-11-14 Thread OmPrakash Muppirala
: Alex Harui >> Gesendet: Freitag, 14. November 2014 22:35 >> An: dev@flex.apache.org >> Betreff: Re: AW: [FlexJS] First successful build of a FlexJS application >> using Flexmojos >> >> On 11/14/14, 1:13 PM, "Christofer Dutz" >> wrote: >> >>

Re: AW: [FlexJS] First successful build of a FlexJS application using Flexmojos

2014-11-14 Thread OmPrakash Muppirala
t; Gesendet: Freitag, 14. November 2014 22:35 > An: dev@flex.apache.org > Betreff: Re: AW: [FlexJS] First successful build of a FlexJS application > using Flexmojos > > On 11/14/14, 1:13 PM, "Christofer Dutz" wrote: > > >Hi, > > > >Actually I did

Re: AW: [FlexJS] First successful build of a FlexJS application using Flexmojos

2014-11-14 Thread Erik de Bruin
Given the rate at which Chris is contributing, I'm sure we'll have a hard time just trying to keep up with the votes ;-) EdB On Fri, Nov 14, 2014 at 4:17 PM, Alex Harui wrote: > > > On 11/14/14, 2:07 PM, "Erik de Bruin" wrote: > > >> > >> >I would suggest to release the staged ones and use t

Re: AW: [FlexJS] First successful build of a FlexJS application using Flexmojos

2014-11-14 Thread Alex Harui
On 11/14/14, 2:07 PM, "Erik de Bruin" wrote: >> >> >I would suggest to release the staged ones and use the optimized pom >>for >> >the next release. >> >> OK, but is there going to be a next release? I was hoping for >> one-and-done. >> > >Let's not drag this out. This is a utility release, an

Re: AW: [FlexJS] First successful build of a FlexJS application using Flexmojos

2014-11-14 Thread Erik de Bruin
> > >I would suggest to release the staged ones and use the optimized pom for > >the next release. > > OK, but is there going to be a next release? I was hoping for > one-and-done. > Let's not drag this out. This is a utility release, and 'good enough to work with' should mean 'good enough to rel

Re: AW: [FlexJS] First successful build of a FlexJS application using Flexmojos

2014-11-14 Thread Alex Harui
On 11/14/14, 1:13 PM, "Christofer Dutz" wrote: >Hi, > >Actually I did create that tag ... wonder why it wasn't transferred to >the Apache Git ... do Tags not get pushed automatically? I think in Git you need to "push --tags”. > >I would suggest to release the staged ones and use the optimized

Re: AW: [FlexJS] First successful build of a FlexJS application using Flexmojos

2014-11-14 Thread OmPrakash Muppirala
> > What you write below is why Maven is hard. Because it wraps up complex > patterns into small entities like commands and profiles, you aren’t always > able to tell what is going to happen until you try it. Whereas in Ant, > you can always read the script. But that’s not to say it is bad, it j

Re: AW: [FlexJS] First successful build of a FlexJS application using Flexmojos

2014-11-14 Thread Alex Harui
Yes, the release manager gets to vote on the release. Do these config changes invalidate the vote? IMO, I’d just make sure the tag is in Git and ship what we have voted on. (everything below is not important, just me musing about Maven and Ant) What you write below is why Maven is hard. Because