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 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 just requires more learning. Another analogy is manufacturing companies that periodically change what they produce by reconfiguring the assembly line. If they are baking cookies for one retailer, they simply plug in different boxes for the packaging part and different ingredients in the mixing part. Then they cah bake for a different retailer by changing boxes and ingredients. That’s Maven. The default behavior is designed to mix something, bake something, cool it, and package it. But if you want to vary from that formula, it takes experts to do it. Ant is baking at home. My mom has made dozen’s of batches of cookies of a particular recipe, but when she passed the recipe on to me, I can make changes to the process because the steps are smaller and easier to learn, but in doing so I can also goof up and forget to cool it, or put the frosting on before putting it in to bake. -Alex On 11/14/14, 1:08 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Hi Alex, > >ok ... I'll write one mail summing up all ;-) > >1. First of all ... it was not that Maven isn't able to, it was just that >it wasn't configured to. Unfortunately I didn't have the time to spend on >fine-tuning the build as I did want to get FlexJS flying ;-) > >2. In the apache master pom there are some settings that are inherited. >These default values were only active if the "apache-release" plugin is >activated. Unfortunately as soon as that's active the artifacts are >automatically PGP signed and this was what was causing the problems as >this is not possible on the build.apache.org agents. > >3. What Om did, was to manually add the same (or similar) descriptors >(sort of an xml pack list on how to build a distribution) and confiugred >that in the pluginManagement section of Maven. This doesn't enable a >plugin, but if it is manually enabled, it's where it gets it's >configuration from. He then added "assembly:single" to the maven command, >which tells maven to enable the "assembly" plugin and execute the >"single" goal. In general this shouldn't have any influence on the build >itself. What I'm a little concerned about though is that I'm not quite >sure, if this doesn't overwrite the configuration of the "apache-release" >profile. So mabe it would be a good idea to wrap that change in a >"flex-ci-build" profile (or whatever name we want to give it). Then we're >safe. > >But thanks Om that you solved this ... I just thought it wasn't that >critical to stop working on Falcon. > >Just another question ... does someone wanting to release something >usually vote +1 for that? > >Chris > >________________________________________ >Von: Alex Harui <aha...@adobe.com> >Gesendet: Freitag, 14. November 2014 06:14 >An: dev@flex.apache.org >Betreff: Re: [FlexJS] First successful build of a FlexJS application >using Flexmojos > >Maybe I misunderstood Chris, but his explanation was that “mvn deploy” >would create the source-release.zip. Which it does just fine, so I’m not >sure we need or should have another target to create it. We’ll see what >Chris says. But that’s why I was saying that Maven seems less flexible >(at least from the defaults). It sort expects that nobody needs a source >zip until you deploy it to the staging repo. Feels like Maven is saying >“that’s just the way we do it”. > >-Alex > >On 11/13/14, 5:18 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: > >>I added the source release target and updated the Jenkins job. >> >>The source packages can be found here now: >>https://builds.apache.org/view/E-G/view/Flex/job/flex-tool-api/lastSucces >>s >>fulBuild/artifact/flex-tool-api/target/ >> >>Thanks, >>Om >> >>On Thu, Nov 13, 2014 at 4:30 PM, OmPrakash Muppirala >><bigosma...@gmail.com> >>wrote: >> >>> Okay, I see what's happening. There is no 'build source package' >>>target >>> for this project. Usually, we use Ant to zip all the relevant files >>>into a >>> .zip and .tz file. >>> >>> I will see what it takes to add an equivalent mvn target to achieve the >>> same thing. >>> >>> Thanks, >>> Om >>> >>> On Thu, Nov 13, 2014 at 3:52 PM, OmPrakash Muppirala >>><bigosma...@gmail.com >>> > wrote: >>> >>>> On Thu, Nov 13, 2014 at 3:30 PM, Alex Harui <aha...@adobe.com> wrote: >>>> >>>>> >>>>> >>>>> On 11/13/14, 3:19 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> >>>>> wrote: >>>>> >>>>> >> >>>>> >> In fact, when trying to review the potential release candidate, it >>>>> >>turned >>>>> >> out to be difficult (impossible?) for Maven to provide the source >>>>> >>artifact >>>>> >> on the CI server without actually deploying the artifact to a >>>>>Maven >>>>> >> server. >>>>> > >>>>> > >>>>> >Can you please explain what "for Maven to provide the source >>>>>artifact on >>>>> >the CI server" means? What are you trying to do? >>>>> >>>>> In our new no-RC workflow, we are trying to get Jenkins to post >>>>>builds >>>>> with artifacts. For TDF, we have this: >>>>> >>>>> >>>>>http://apacheflexbuild.cloudapp.net:8080/job/flex-utilities_tour-de-fl >>>>>e >>>>>x-re >>>>> lease/ >>>>> >>>>><http://apacheflexbuild.cloudapp.net:8080/job/flex-utilities_tour-de-f >>>>>l >>>>>ex-release/> >>>>> >>>>> Click on “Last Successful Artifacts” and somewhere in there is the >>>>>source >>>>> package. >>>>> >>>>> Over at >>>>>https://builds.apache.org/view/E-G/view/Flex/job/flex-tool-api/ >>>>> We have “Last Successful Artifacts”, but despite my asking several >>>>>times, >>>>> Chris was unable to get the build to leave the source-release.zip >>>>>file >>>>> there. He said that would require running the “deploy” command which >>>>> would try to upload the artifacts to the Maven staging server. My >>>>> takeaway was that Maven didn’t have a “build” command that would just >>>>> compile artifacts and not deploy them. That’s why I drew the analogy >>>>>to >>>>> not being able to get pepperoni on one side and sausage on the other. >>>>> The >>>>> Maven assumption is that you would always deploy any built artifacts. >>>>> >>>>> >>>> Are we sure that the source-release.zip is actually getting built? I >>>> don't see it in the 'target' directory in the workspace. >>>> I do see a flex-tool-api-1.1.0-SNAPSHOT.jar here[1] which seems to be >>>> the only artifact getting built. >>>> >>>> Thanks, >>>> Om >>>> >>>> [1] >>>> >>>>https://builds.apache.org/view/E-G/view/Flex/job/flex-tool-api/lastSucc >>>>e >>>>ssfulBuild/artifact/flex-tool-api/target/ >>>> >>>> >>>>> -Alex >>>>> >>>>> >>>> >>>
