You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by Julien Nioche <li...@gmail.com> on 2012/05/22 11:15:49 UTC
1.5 RC2
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
Re: 1.5 RC2
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
+1 happy for Lewis to try I've been swamped!
Sent from my iPhone
On May 22, 2012, at 2:16 AM, "Julien Nioche" <li...@gmail.com>> 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.jar 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
--
[http://digitalpebble.com/img/logo.gif]
Open Source Solutions for Text Engineering
http://digitalpebble.blogspot.com/
http://www.digitalpebble.com
http://twitter.com/digitalpebble
Re: 1.5 RC2
Posted by Lewis John Mcgibbney <le...@gmail.com>.
An update on 2.0 RC.
The maven stuff has been done, but I've run into a problemm generating the
project artifacts, which I can't seem to solve so I've headed over to
user@ant to see if they can help me out.
Hopefully I can spin the RC for 2.0 on Thursday as I won't be able to do it
tomorrow.
Thanks
Lewis
On Tue, May 22, 2012 at 9:16 PM, Julien Nioche <
lists.digitalpebble@gmail.com> wrote:
> Brilliant! Thanks Lewis
>
>
> On 22 May 2012 20:30, Lewis John Mcgibbney <le...@gmail.com>wrote:
>
>> 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 <
>> lewis.mcgibbney@gmail.com> 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 <
>>> lists.digitalpebble@gmail.com> 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 <le...@gmail.com>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 <
>>>>> lists.digitalpebble@gmail.com> 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*
>>
>>
>
>
> --
> *
> *Open Source Solutions for Text Engineering
>
> http://digitalpebble.blogspot.com/
> http://www.digitalpebble.com
> http://twitter.com/digitalpebble
>
>
--
*Lewis*
Re: 1.5 RC2
Posted by Julien Nioche <li...@gmail.com>.
Brilliant! Thanks Lewis
On 22 May 2012 20:30, Lewis John Mcgibbney <le...@gmail.com>wrote:
> 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 <
> lewis.mcgibbney@gmail.com> 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 <
>> lists.digitalpebble@gmail.com> 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 <le...@gmail.com>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 <
>>>> lists.digitalpebble@gmail.com> 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*
>
>
--
*
*Open Source Solutions for Text Engineering
http://digitalpebble.blogspot.com/
http://www.digitalpebble.com
http://twitter.com/digitalpebble
Re: 1.5 RC2
Posted by Lewis John Mcgibbney <le...@gmail.com>.
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 <
lewis.mcgibbney@gmail.com> 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 <
> lists.digitalpebble@gmail.com> 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 <le...@gmail.com>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 <
>>> lists.digitalpebble@gmail.com> 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*
Re: 1.5 RC2
Posted by Lewis John Mcgibbney <le...@gmail.com>.
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 <
lists.digitalpebble@gmail.com> 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 <le...@gmail.com>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 <
>> lists.digitalpebble@gmail.com> 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*
Re: 1.5 RC2
Posted by Julien Nioche <li...@gmail.com>.
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 <le...@gmail.com>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 <
> lists.digitalpebble@gmail.com> 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
Re: 1.5 RC2
Posted by Lewis John Mcgibbney <le...@gmail.com>.
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 <
lists.digitalpebble@gmail.com> 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*
RE: 1.5 RC2
Posted by Markus Jelsma <ma...@openindex.io>.
Sounds great!
-----Original message-----
> From:Lewis John Mcgibbney <le...@gmail.com>
> Sent: Tue 22-May-2012 13:43
> To: dev@nutch.apache.org
> Subject: Re: 1.5 RC2
>
> Hi,
>
> As I say, I am able to stick time in tonight to roll this RC, however does anyone have a problem with me rolling the 2.0 RC tonight after the 1.5RC2?
>
> I would like to get them out the way saving me time during this week if possible.
>
> Thanks
>
> Lewis
>
> On Tue, May 22, 2012 at 10:35 AM, Lewis John Mcgibbney <lewis.mcgibbney@gmail.com <ma...@gmail.com> > wrote:
> OK doke this sounds fine to me then. I will make the relevant commits to the 1.5 branch then work at it later this evening.
>
> I'll make a new thread when the stuff is sorted out and we are ready to VOTE on the new RC.
>
> Thanks
>
> Lewis
>
>
> On Tue, May 22, 2012 at 10:15 AM, Julien Nioche <lists.digitalpebble@gmail.com <ma...@gmail.com> > 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.jar 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
>
>
> --
> <http://digitalpebble.com/img/logo.gif>
> Open Source Solutions for Text Engineering
>
> http://digitalpebble.blogspot.com/ <http://digitalpebble.blogspot.com/>
> http://www.digitalpebble.com <http://www.digitalpebble.com>
> http://twitter.com/digitalpebble <http://twitter.com/digitalpebble>
>
>
>
>
> --
> Lewis
>
>
>
>
> --
> Lewis
>
>
Re: 1.5 RC2
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
+1
Sent from my iPhone
On May 22, 2012, at 4:43 AM, "Lewis John Mcgibbney" <le...@gmail.com>> wrote:
Hi,
As I say, I am able to stick time in tonight to roll this RC, however does anyone have a problem with me rolling the 2.0 RC tonight after the 1.5RC2?
I would like to get them out the way saving me time during this week if possible.
Thanks
Lewis
On Tue, May 22, 2012 at 10:35 AM, Lewis John Mcgibbney <le...@gmail.com>> wrote:
OK doke this sounds fine to me then. I will make the relevant commits to the 1.5 branch then work at it later this evening.
I'll make a new thread when the stuff is sorted out and we are ready to VOTE on the new RC.
Thanks
Lewis
On Tue, May 22, 2012 at 10:15 AM, Julien Nioche <li...@gmail.com>> 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.jar 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
--
[http://digitalpebble.com/img/logo.gif]
Open Source Solutions for Text Engineering
http://digitalpebble.blogspot.com/
http://www.digitalpebble.com
http://twitter.com/digitalpebble
--
Lewis
--
Lewis
Re: 1.5 RC2
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hi,
As I say, I am able to stick time in tonight to roll this RC, however does
anyone have a problem with me rolling the 2.0 RC tonight after the 1.5RC2?
I would like to get them out the way saving me time during this week if
possible.
Thanks
Lewis
On Tue, May 22, 2012 at 10:35 AM, Lewis John Mcgibbney <
lewis.mcgibbney@gmail.com> wrote:
> OK doke this sounds fine to me then. I will make the relevant commits to
> the 1.5 branch then work at it later this evening.
>
> I'll make a new thread when the stuff is sorted out and we are ready to
> VOTE on the new RC.
>
> Thanks
>
> Lewis
>
>
> On Tue, May 22, 2012 at 10:15 AM, Julien Nioche <
> lists.digitalpebble@gmail.com> 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*
>
>
--
*Lewis*
Re: 1.5 RC2
Posted by Lewis John Mcgibbney <le...@gmail.com>.
OK doke this sounds fine to me then. I will make the relevant commits to
the 1.5 branch then work at it later this evening.
I'll make a new thread when the stuff is sorted out and we are ready to
VOTE on the new RC.
Thanks
Lewis
On Tue, May 22, 2012 at 10:15 AM, Julien Nioche <
lists.digitalpebble@gmail.com> 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*