Done. The artifacts will be signed and uploaded in a couple of mins.
Thanks On Tue, May 22, 2012 at 8:22 PM, Lewis John Mcgibbney < [email protected]> wrote: > I've been working on it, so I'll try to commit and do it ASAP. > > Thanks Julien > > Lewis > > > On Tue, May 22, 2012 at 8:17 PM, Julien Nioche < > [email protected]> wrote: > >> we'd need to duplicate the tasks tar and zip so that they operate on what >> package-bin produces + rename the output of the standard package into >> nutch-X-src. The modif I made to build.xml does not deal with that :-( >> >> >> On 22 May 2012 19:43, Lewis John Mcgibbney <[email protected]>wrote: >> >>> As you will have seen the staging repository is closed so we are half >>> way there. I'm now about to sign then upload the generated artifacts to my >>> Apache area for us to view and VOTE, however I am struggling to produce >>> anything other than the nutch-1.5.tar.gz and the nutch-1.5.zip e.g. no >>> nutch-1.5-src.tar.gz, nutch-1.5-bin.tar.gz and nutch-1.5-src.zip, >>> nutch-1.5-src.zip respectively. >>> >>> If you do 'ant tar' and 'ant zip' from trunk you will see exactly what >>> I'm dealing with... however this goes no lengths what-so-ever to address >>> the issues you raised Julien w.r.t the packe-bin ant task... or the package >>> task for that matter... >>> >>> Any ideas troops? >>> >>> Thanks >>> >>> Lewis >>> >>> On Tue, May 22, 2012 at 10:15 AM, Julien Nioche < >>> [email protected]> wrote: >>> >>>> Hi Lewis, >>>> >>>> I am sure that Chris will have no problem with you doing the RC2. >>>> Chris? It would be a good thing to have more than one person who knows how >>>> to do it anyway :-) >>>> Note that to generate a fresh pom.xml you need to >>>> >>>> - get *maven-ant-tasks-2.1.3.ja*r and put it in the ivy dir >>>> - ant -lib ivy deploy >>>> >>>> The resulting pom.xml file should reflect the content of the main >>>> ivy.xml. I have committed some minor changes to the pom template in trunk, >>>> this will need to be copied to the 1.5 branch as well. We recently >>>> discussed a move to Maven, another option would be to manage the >>>> dependencies with the Maven Ant task, which would save us the hassle of >>>> having to keep the ivy.xml and pom.xml in sync. We'll see >>>> >>>> Thanks >>>> >>>> Julien >>>> >>>> >>>> -- >>>> * >>>> *Open Source Solutions for Text Engineering >>>> >>>> http://digitalpebble.blogspot.com/ >>>> http://www.digitalpebble.com >>>> http://twitter.com/digitalpebble >>>> >>>> >>> >>> >>> -- >>> *Lewis* >>> >>> >> >> >> -- >> * >> *Open Source Solutions for Text Engineering >> >> http://digitalpebble.blogspot.com/ >> http://www.digitalpebble.com >> http://twitter.com/digitalpebble >> >> > > > -- > *Lewis* > > -- *Lewis*
