You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hivemind.apache.org by James Carman <ja...@carmanconsulting.com> on 2007/01/19 23:49:48 UTC

Re: svn commit: r497977 - /hivemind/hivemind2/trunk/.project

I don't know about this one.  We don't want to be renaming the
hivemind project itself.  We don't want the jar file to be named
hivemind-2.jar.  The project is still hivemind, we're just working on
a different version.

On 1/19/07, ahuegen@apache.org <ah...@apache.org> wrote:
> Author: ahuegen
> Date: Fri Jan 19 14:33:34 2007
> New Revision: 497977
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=497977
> Log:
> Change project name to hivemind-2
>
> Modified:
>     hivemind/hivemind2/trunk/.project
>
> Modified: hivemind/hivemind2/trunk/.project
> URL: http://svn.apache.org/viewvc/hivemind/hivemind2/trunk/.project?view=diff&rev=497977&r1=497976&r2=497977
> ==============================================================================
> --- hivemind/hivemind2/trunk/.project (original)
> +++ hivemind/hivemind2/trunk/.project Fri Jan 19 14:33:34 2007
> @@ -1,7 +1,7 @@
>  <?xml version="1.0" encoding="UTF-8"?>
>  <projectDescription>
> -       <name>jakarta-hivemind-2</name>
> -       <comment>HiveMind is a dynamic services and configuration microkernel. Its primary feature is the dynamic creation of a runtime registry of services and configuration data, where any HiveMind module may contribute extensions to any other HiveMind module.</comment>
> +       <name>hivemind-2</name>
> +       <comment>HiveMind is a services and configuration microkernel.</comment>
>         <projects>
>         </projects>
>         <buildSpec>
>
>
>

Re: svn commit: r497977 - /hivemind/hivemind2/trunk/.project

Posted by James Carman <ja...@carmanconsulting.com>.
Oh, I thought that was the pom.xml file.  No big deal, then.  Should
we be checking in the eclipse files now that mvn can generate those
(and IntelliJ IDEA) for us?


On 1/22/07, Achim Hügen <ac...@gmx.de> wrote:
> I changed the eclipse project file only, which comes in handy
> if you have different versions of hivemind in the same workspace.
> But that's no must have.
>
> Achim
>
> Am Fri, 19 Jan 2007 23:49:48 +0100 schrieb James Carman
> <ja...@carmanconsulting.com>:
>
> > I don't know about this one.  We don't want to be renaming the
> > hivemind project itself.  We don't want the jar file to be named
> > hivemind-2.jar.  The project is still hivemind, we're just working on
> > a different version.
> >
> > On 1/19/07, ahuegen@apache.org <ah...@apache.org> wrote:
> >> Author: ahuegen
> >> Date: Fri Jan 19 14:33:34 2007
> >> New Revision: 497977
> >>
> >> URL: http://svn.apache.org/viewvc?view=rev&rev=497977
> >> Log:
> >> Change project name to hivemind-2
> >>
> >> Modified:
> >>     hivemind/hivemind2/trunk/.project
> >>
> >> Modified: hivemind/hivemind2/trunk/.project
> >> URL:
> >> http://svn.apache.org/viewvc/hivemind/hivemind2/trunk/.project?view=diff&rev=497977&r1=497976&r2=497977
> >> ==============================================================================
> >> --- hivemind/hivemind2/trunk/.project (original)
> >> +++ hivemind/hivemind2/trunk/.project Fri Jan 19 14:33:34 2007
> >> @@ -1,7 +1,7 @@
> >>  <?xml version="1.0" encoding="UTF-8"?>
> >>  <projectDescription>
> >> -       <name>jakarta-hivemind-2</name>
> >> -       <comment>HiveMind is a dynamic services and configuration
> >> microkernel. Its primary feature is the dynamic creation of a runtime
> >> registry of services and configuration data, where any HiveMind module
> >> may contribute extensions to any other HiveMind module.</comment>
> >> +       <name>hivemind-2</name>
> >> +       <comment>HiveMind is a services and configuration
> >> microkernel.</comment>
> >>         <projects>
> >>         </projects>
> >>         <buildSpec>
> >>
> >>
> >>
>
>
>

Re: svn commit: r497977 - /hivemind/hivemind2/trunk/.project

Posted by Achim Hügen <ac...@gmx.de>.
I changed the eclipse project file only, which comes in handy
if you have different versions of hivemind in the same workspace.
But that's no must have.

Achim

Am Fri, 19 Jan 2007 23:49:48 +0100 schrieb James Carman  
<ja...@carmanconsulting.com>:

> I don't know about this one.  We don't want to be renaming the
> hivemind project itself.  We don't want the jar file to be named
> hivemind-2.jar.  The project is still hivemind, we're just working on
> a different version.
>
> On 1/19/07, ahuegen@apache.org <ah...@apache.org> wrote:
>> Author: ahuegen
>> Date: Fri Jan 19 14:33:34 2007
>> New Revision: 497977
>>
>> URL: http://svn.apache.org/viewvc?view=rev&rev=497977
>> Log:
>> Change project name to hivemind-2
>>
>> Modified:
>>     hivemind/hivemind2/trunk/.project
>>
>> Modified: hivemind/hivemind2/trunk/.project
>> URL:  
>> http://svn.apache.org/viewvc/hivemind/hivemind2/trunk/.project?view=diff&rev=497977&r1=497976&r2=497977
>> ==============================================================================
>> --- hivemind/hivemind2/trunk/.project (original)
>> +++ hivemind/hivemind2/trunk/.project Fri Jan 19 14:33:34 2007
>> @@ -1,7 +1,7 @@
>>  <?xml version="1.0" encoding="UTF-8"?>
>>  <projectDescription>
>> -       <name>jakarta-hivemind-2</name>
>> -       <comment>HiveMind is a dynamic services and configuration  
>> microkernel. Its primary feature is the dynamic creation of a runtime  
>> registry of services and configuration data, where any HiveMind module  
>> may contribute extensions to any other HiveMind module.</comment>
>> +       <name>hivemind-2</name>
>> +       <comment>HiveMind is a services and configuration  
>> microkernel.</comment>
>>         <projects>
>>         </projects>
>>         <buildSpec>
>>
>>
>>