Digy
2011-02-25, 20:20
Troy Howard
2011-02-25, 20:35
Wyatt Barnett
2011-02-25, 22:59
Troy Howard
2011-02-25, 23:05
Digy
2011-02-25, 23:53
Troy Howard
2011-02-25, 23:58
Digy
2011-02-26, 00:25
Michael Herndon
2011-03-06, 19:28
Stefan Bodewig
2011-03-07, 05:02
Michael Herndon
2011-03-07, 05:11
Ruben Pierich
2011-03-29, 03:09
-
RE: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010Digy 2011-02-25, 20:20
What about this source tree?
RC2
....build
....contrib
....core
........Lucene.Net
........Test
....demo
"src" doesn't mean anything since other dirs contain sources as well.
DIGY
-----Original Message-----
From: Troy Howard (JIRA) [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 25, 2011 9:18 PM
To: [EMAIL PROTECTED]
Subject: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010
[ https://issues.apache.org/jira/browse/LUCENENET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999481#comment-12999481 ]
Troy Howard commented on LUCENENET-377:
---------------------------------------
I did another version of this for the 2.9.2-incubating-RC2 build.
Have a look at:
https://svn.apache.org/repos/asf/incubator/lucene.net/tags/Lucene.Net_2_9_2_RC2
I placed all .sln files, as VS2010 format, in a ~/build/ directory, and updated the Release profiles to build to a ~/bin/ and ~/doc/ directories. This makes for better releases packaging structure and consolidates all solution files to a single directory (no more hunting them down).
I made my changes on that branch, but could merge them in somewhere (vs2010 branch or trunk) if we like this layout/design. We also really need to address naming and namespaces. They are all over the place. I had to update a lot of things to make it all make sense. Test.dll is really inadequate naming!! I'll say more on namespaces later, in another context...
Regarding VS2010 files in general, Neal brings up an interesting problem case: MsBuild 2.0 or 3.5 pre SP1 can't build a VS2010 file (even if it's target version is set to 2.0). We either need to set our standard high for end users (require .NET 3.5 SP1 or higher, and/or Visual Studio 2010), or provide VS2008 compatible versions of the solution and project files.
> 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
RC2
....build
....contrib
....core
........Lucene.Net
........Test
....demo
"src" doesn't mean anything since other dirs contain sources as well.
DIGY
-----Original Message-----
From: Troy Howard (JIRA) [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 25, 2011 9:18 PM
To: [EMAIL PROTECTED]
Subject: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010
[ https://issues.apache.org/jira/browse/LUCENENET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999481#comment-12999481 ]
Troy Howard commented on LUCENENET-377:
---------------------------------------
I did another version of this for the 2.9.2-incubating-RC2 build.
Have a look at:
https://svn.apache.org/repos/asf/incubator/lucene.net/tags/Lucene.Net_2_9_2_RC2
I placed all .sln files, as VS2010 format, in a ~/build/ directory, and updated the Release profiles to build to a ~/bin/ and ~/doc/ directories. This makes for better releases packaging structure and consolidates all solution files to a single directory (no more hunting them down).
I made my changes on that branch, but could merge them in somewhere (vs2010 branch or trunk) if we like this layout/design. We also really need to address naming and namespaces. They are all over the place. I had to update a lot of things to make it all make sense. Test.dll is really inadequate naming!! I'll say more on namespaces later, in another context...
Regarding VS2010 files in general, Neal brings up an interesting problem case: MsBuild 2.0 or 3.5 pre SP1 can't build a VS2010 file (even if it's target version is set to 2.0). We either need to set our standard high for end users (require .NET 3.5 SP1 or higher, and/or Visual Studio 2010), or provide VS2008 compatible versions of the solution and project files.
> 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
-
Re: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010Troy Howard 2011-02-25, 20:35
Sounds good to me.
At some point I'd like to address namespace mappings too... But
perhaps that's best deferred for the 3.x reworking?
Also, there are a number of less-than-useful documentation files
(html) and other random files that seem to come from the Java world.
It would be nice to clean up the source tree and get rid of that
stuff.
Also, we don't have a system for generating the MSDN style
documentation at the moment. When we set up the CI server, it'd be
nice if it could convert the XML documentation files we're generating
into HTML docs.
Thanks,
Troy
On Fri, Feb 25, 2011 at 12:20 PM, Digy <[EMAIL PROTECTED]> wrote:
> What about this source tree?
> RC2
> ....build
> ....contrib
> ....core
> ........Lucene.Net
> ........Test
> ....demo
>
> "src" doesn't mean anything since other dirs contain sources as well.
>
> DIGY
>
> -----Original Message-----
> From: Troy Howard (JIRA) [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 25, 2011 9:18 PM
> To: [EMAIL PROTECTED]
> Subject: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010
>
>
> [ https://issues.apache.org/jira/browse/LUCENENET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999481#comment-12999481 ]
>
> Troy Howard commented on LUCENENET-377:
> ---------------------------------------
>
> I did another version of this for the 2.9.2-incubating-RC2 build.
>
> Have a look at:
>
> https://svn.apache.org/repos/asf/incubator/lucene.net/tags/Lucene.Net_2_9_2_RC2
>
> I placed all .sln files, as VS2010 format, in a ~/build/ directory, and updated the Release profiles to build to a ~/bin/ and ~/doc/ directories. This makes for better releases packaging structure and consolidates all solution files to a single directory (no more hunting them down).
>
> I made my changes on that branch, but could merge them in somewhere (vs2010 branch or trunk) if we like this layout/design. We also really need to address naming and namespaces. They are all over the place. I had to update a lot of things to make it all make sense. Test.dll is really inadequate naming!! I'll say more on namespaces later, in another context...
>
> Regarding VS2010 files in general, Neal brings up an interesting problem case: MsBuild 2.0 or 3.5 pre SP1 can't build a VS2010 file (even if it's target version is set to 2.0). We either need to set our standard high for end users (require .NET 3.5 SP1 or higher, and/or Visual Studio 2010), or provide VS2008 compatible versions of the solution and project files.
>
>
>
>
>> 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
>
>
>
>
At some point I'd like to address namespace mappings too... But
perhaps that's best deferred for the 3.x reworking?
Also, there are a number of less-than-useful documentation files
(html) and other random files that seem to come from the Java world.
It would be nice to clean up the source tree and get rid of that
stuff.
Also, we don't have a system for generating the MSDN style
documentation at the moment. When we set up the CI server, it'd be
nice if it could convert the XML documentation files we're generating
into HTML docs.
Thanks,
Troy
On Fri, Feb 25, 2011 at 12:20 PM, Digy <[EMAIL PROTECTED]> wrote:
> What about this source tree?
> RC2
> ....build
> ....contrib
> ....core
> ........Lucene.Net
> ........Test
> ....demo
>
> "src" doesn't mean anything since other dirs contain sources as well.
>
> DIGY
>
> -----Original Message-----
> From: Troy Howard (JIRA) [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 25, 2011 9:18 PM
> To: [EMAIL PROTECTED]
> Subject: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010
>
>
> [ https://issues.apache.org/jira/browse/LUCENENET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999481#comment-12999481 ]
>
> Troy Howard commented on LUCENENET-377:
> ---------------------------------------
>
> I did another version of this for the 2.9.2-incubating-RC2 build.
>
> Have a look at:
>
> https://svn.apache.org/repos/asf/incubator/lucene.net/tags/Lucene.Net_2_9_2_RC2
>
> I placed all .sln files, as VS2010 format, in a ~/build/ directory, and updated the Release profiles to build to a ~/bin/ and ~/doc/ directories. This makes for better releases packaging structure and consolidates all solution files to a single directory (no more hunting them down).
>
> I made my changes on that branch, but could merge them in somewhere (vs2010 branch or trunk) if we like this layout/design. We also really need to address naming and namespaces. They are all over the place. I had to update a lot of things to make it all make sense. Test.dll is really inadequate naming!! I'll say more on namespaces later, in another context...
>
> Regarding VS2010 files in general, Neal brings up an interesting problem case: MsBuild 2.0 or 3.5 pre SP1 can't build a VS2010 file (even if it's target version is set to 2.0). We either need to set our standard high for end users (require .NET 3.5 SP1 or higher, and/or Visual Studio 2010), or provide VS2008 compatible versions of the solution and project files.
>
>
>
>
>> 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
>
>
>
>
-
Re: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010Wyatt Barnett 2011-02-25, 22:59
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) <[EMAIL PROTECTED]> 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
>
>
>
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) <[EMAIL PROTECTED]> 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
>
>
>
-
Re: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010Troy Howard 2011-02-25, 23:05
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 <[EMAIL PROTECTED]> 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) <[EMAIL PROTECTED]> 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
>>
>>
>>
>
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 <[EMAIL PROTECTED]> 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) <[EMAIL PROTECTED]> 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
>>
>>
>>
>
-
RE: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010Digy 2011-02-25, 23:53
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:[EMAIL PROTECTED]]
Sent: Saturday, February 26, 2011 1:06 AM
To: [EMAIL PROTECTED]
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 <[EMAIL PROTECTED]> 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) <[EMAIL PROTECTED]> 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
>>
>>
>>
>
DIGY
-----Original Message-----
From: Troy Howard [mailto:[EMAIL PROTECTED]]
Sent: Saturday, February 26, 2011 1:06 AM
To: [EMAIL PROTECTED]
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 <[EMAIL PROTECTED]> 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) <[EMAIL PROTECTED]> 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
>>
>>
>>
>
-
Re: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010Troy Howard 2011-02-25, 23:58
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 <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED]]
> Sent: Saturday, February 26, 2011 1:06 AM
> To: [EMAIL PROTECTED]
> 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 <[EMAIL PROTECTED]> 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) <[EMAIL PROTECTED]> 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
>>>
>>>
>>>
>>
>
>
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 <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED]]
> Sent: Saturday, February 26, 2011 1:06 AM
> To: [EMAIL PROTECTED]
> 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 <[EMAIL PROTECTED]> 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) <[EMAIL PROTECTED]> 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
>>>
>>>
>>>
>>
>
>
-
RE: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010Digy 2011-02-26, 00:25
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:[EMAIL PROTECTED]]
Sent: Saturday, February 26, 2011 1:58 AM
To: [EMAIL PROTECTED]
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 <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED]]
> Sent: Saturday, February 26, 2011 1:06 AM
> To: [EMAIL PROTECTED]
> 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 <[EMAIL PROTECTED]> 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) <[EMAIL PROTECTED]> 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
>>>
>>>
>>>
>>
>
>
(I must admit, it is better than the previous one)
DIGY
-----Original Message-----
From: Troy Howard [mailto:[EMAIL PROTECTED]]
Sent: Saturday, February 26, 2011 1:58 AM
To: [EMAIL PROTECTED]
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 <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED]]
> Sent: Saturday, February 26, 2011 1:06 AM
> To: [EMAIL PROTECTED]
> 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 <[EMAIL PROTECTED]> 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) <[EMAIL PROTECTED]> 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
>>>
>>>
>>>
>>
>
>
-
Re: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010Michael Herndon 2011-03-06, 19:28
Hey All,
I Hope everyone is having a good weekend.
Sometime this week, could we get a consensus & input on a clean
directory structure?
We'll need this done so that we start writing a first iteration of a
build scripts that works. If possible we should like this done before
we ask put in a jira hudkins ticket for putting this slaves for a
windows and mono build.
I'd also like to go ahead and see if we can put the .gitignore files &
hgignore files in. As well as find out how to get this project
mirrored again on github.com similar to how other apache projects are.
(It used to be mirrored but then it just keeps pulling the same tag
currently).
- Michael
On Fri, Feb 25, 2011 at 7:25 PM, Digy <[EMAIL PROTECTED]> wrote:
> 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:[EMAIL PROTECTED]]
> Sent: Saturday, February 26, 2011 1:58 AM
> To: [EMAIL PROTECTED]
> 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 <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED]]
>> Sent: Saturday, February 26, 2011 1:06 AM
>> To: [EMAIL PROTECTED]
>> 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 <[EMAIL PROTECTED]> 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) <[EMAIL PROTECTED]> 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
I Hope everyone is having a good weekend.
Sometime this week, could we get a consensus & input on a clean
directory structure?
We'll need this done so that we start writing a first iteration of a
build scripts that works. If possible we should like this done before
we ask put in a jira hudkins ticket for putting this slaves for a
windows and mono build.
I'd also like to go ahead and see if we can put the .gitignore files &
hgignore files in. As well as find out how to get this project
mirrored again on github.com similar to how other apache projects are.
(It used to be mirrored but then it just keeps pulling the same tag
currently).
- Michael
On Fri, Feb 25, 2011 at 7:25 PM, Digy <[EMAIL PROTECTED]> wrote:
> 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:[EMAIL PROTECTED]]
> Sent: Saturday, February 26, 2011 1:58 AM
> To: [EMAIL PROTECTED]
> 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 <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED]]
>> Sent: Saturday, February 26, 2011 1:06 AM
>> To: [EMAIL PROTECTED]
>> 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 <[EMAIL PROTECTED]> 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) <[EMAIL PROTECTED]> 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
-
Re: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010Stefan Bodewig 2011-03-07, 05:02
On 2011-03-06, Michael Herndon wrote:
> I'd also like to go ahead and see if we can put the .gitignore files &
> hgignore files in. As well as find out how to get this project
> mirrored again on github.com similar to how other apache projects are.
> (It used to be mirrored but then it just keeps pulling the same tag
> currently).
Projects can have read-only GIT mirrors at the ASF itself, no need to go
to github: <http://git.apache.org/>
Stefan
> I'd also like to go ahead and see if we can put the .gitignore files &
> hgignore files in. As well as find out how to get this project
> mirrored again on github.com similar to how other apache projects are.
> (It used to be mirrored but then it just keeps pulling the same tag
> currently).
Projects can have read-only GIT mirrors at the ASF itself, no need to go
to github: <http://git.apache.org/>
Stefan
-
Re: [Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010Michael Herndon 2011-03-07, 05:11
well this repo exists is mirrored from apache on github
https://github.com/apache/lucene.net
http://support.github.com/discussions/repos/3794-lucenenet-apache-mirror
While it might not officially be our concern, it would probably be
beneficial to the community if the mirror was up to date.
On Mon, Mar 7, 2011 at 12:02 AM, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> On 2011-03-06, Michael Herndon wrote:
>
>> I'd also like to go ahead and see if we can put the .gitignore files &
>> hgignore files in. As well as find out how to get this project
>> mirrored again on github.com similar to how other apache projects are.
>> (It used to be mirrored but then it just keeps pulling the same tag
>> currently).
>
> Projects can have read-only GIT mirrors at the ASF itself, no need to go
> to github: <http://git.apache.org/>
>
> Stefan
>
https://github.com/apache/lucene.net
http://support.github.com/discussions/repos/3794-lucenenet-apache-mirror
While it might not officially be our concern, it would probably be
beneficial to the community if the mirror was up to date.
On Mon, Mar 7, 2011 at 12:02 AM, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> On 2011-03-06, Michael Herndon wrote:
>
>> I'd also like to go ahead and see if we can put the .gitignore files &
>> hgignore files in. As well as find out how to get this project
>> mirrored again on github.com similar to how other apache projects are.
>> (It used to be mirrored but then it just keeps pulling the same tag
>> currently).
>
> Projects can have read-only GIT mirrors at the ASF itself, no need to go
> to github: <http://git.apache.org/>
>
> Stefan
>
-
RE: [Lucene.Net] [jira] [Commented] (LUCENENET-408) Mark assembly as CLS compliant; make AlreadyClosedException serializableRuben Pierich 2011-03-29, 03:09
Unsubscribe.
> Date: Mon, 28 Mar 2011 21:35:05 +0000
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: [Lucene.Net] [jira] [Commented] (LUCENENET-408) Mark assembly as CLS compliant; make AlreadyClosedException serializable
>
>
> [ https://issues.apache.org/jira/browse/LUCENENET-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012236#comment-13012236 ]
>
> Digy commented on LUCENENET-408:
> --------------------------------
>
> Thanks Itamar.
>
> DIGY
>
> > Mark assembly as CLS compliant; make AlreadyClosedException serializable
> > ------------------------------------------------------------------------
> >
> > Key: LUCENENET-408
> > URL: https://issues.apache.org/jira/browse/LUCENENET-408
> > Project: Lucene.Net
> > Issue Type: Improvement
> > Components: Lucene.Net Core
> > Reporter: Itamar Syn-Hershko
> > Priority: Minor
> > Fix For: Lucene.Net 2.9.2, Lucene.Net 2.9.4, Lucene.Net 3.x
> >
> > Attachments: commit-40f81a3.patch
> >
> >
> > * Making sure that the AlreadyClosedException exception can be serialized
> > * Making sure that Lucene is marked as cls compliant
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
