lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Digy" <digyd...@gmail.com>
Subject RE: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010
Date Sat, 26 Feb 2011 00:25:03 GMT
First of all, I don't want to start a flame war. What I want to say is: "This is just what
made sense while building this release" might not make sense for all.
(I must admit, it is better than the previous one)

DIGY

-----Original Message-----
From: Troy Howard [mailto:thoward37@gmail.com] 
Sent: Saturday, February 26, 2011 1:58 AM
To: lucene-net-dev@lucene.apache.org
Subject: Re: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010

Well, the changes are currently only on a branch. Migrating these
changes into trunk can be a slower process... or we could decide to go
a different way altogether. This is just what made sense while
building this release.

That said, change, whenever it comes, does require a certain amount of
adjustment for everyone. Hopefully the changes are valuable enough
that they justify the costs.

Thanks,
Troy

On Fri, Feb 25, 2011 at 3:53 PM, Digy <digydigy@gmail.com> wrote:
> If this directory structure is to be used also in trunk, I must say that that I am not
comfortable with this rapid changes without any previous warnings(although I understand Troy's
arguments). Now, I have to reorganize all my local works.
>
> DIGY
>
> -----Original Message-----
> From: Troy Howard [mailto:thoward37@gmail.com]
> Sent: Saturday, February 26, 2011 1:06 AM
> To: lucene-net-dev@lucene.apache.org
> Cc: Wyatt Barnett
> Subject: Re: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010
>
> I prefer it that way as well, but the current setup has one for each
> project. I guess it makes sense for the Contrib projects because the
> folks who developed them probably worked on them in isolation from the
> rest of Lucene.Net.
>
> Anyway, I'd be happy to have less files to maintain. ;)
>
> If they don't have a solid and obvious purpose, axe them.
>
> Thanks,
> Troy
>
> On Fri, Feb 25, 2011 at 2:59 PM, Wyatt Barnett <wyatt.barnett@gmail.com> wrote:
>> One thing I'm not quite following -- why does one need a solution for
>> every single project? Point of solution files is so one can have
>> multiple projects linked in realish time, so we probably need a single
>> solution for everything or perhaps two covering core lucene and
>> contrib.
>>
>>
>> On Fri, Feb 25, 2011 at 5:51 PM, Prescott Nasser (JIRA) <jira@apache.org> wrote:
>>>
>>>    [ https://issues.apache.org/jira/browse/LUCENENET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999618#comment-12999618
]
>>>
>>> Prescott Nasser commented on LUCENENET-377:
>>> -------------------------------------------
>>>
>>> probably should wipe out the vs2010 branch in all honesty...
>>>
>>>> Upgrade solution to VS2010
>>>> --------------------------
>>>>
>>>>                 Key: LUCENENET-377
>>>>                 URL: https://issues.apache.org/jira/browse/LUCENENET-377
>>>>             Project: Lucene.Net
>>>>          Issue Type: Task
>>>>          Components: Lucene.Net Core
>>>>    Affects Versions: Lucene.Net 2.9.2, Lucene.Net 2.9.4, Lucene.Net 3.x
>>>>            Reporter: Jeffrey Cameron
>>>>            Assignee: Prescott Nasser
>>>>              Labels: solution
>>>>             Fix For: Lucene.Net 2.9.4
>>>>
>>>>         Attachments: lucene.zip
>>>>
>>>>   Original Estimate: 10m
>>>>  Remaining Estimate: 10m
>>>>
>>>> VS2005 is quite out of date now and there are many new improvements in VS2010.
 You can still leave the framework support at .NET 2.0 if you like.
>>>
>>> --
>>> This message is automatically generated by JIRA.
>>> -
>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>
>>>
>>>
>>
>
>


Mime
View raw message