[jira] [Commented] (LUCENENET-456) Create a Build Target that outputs compiled artifacts in apache release format
[ https://issues.apache.org/jira/browse/LUCENENET-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13400493#comment-13400493 ] michael herndon commented on LUCENENET-456: --- taking issue. Create a Build Target that outputs compiled artifacts in apache release format -- Key: LUCENENET-456 URL: https://issues.apache.org/jira/browse/LUCENENET-456 Project: Lucene.Net Issue Type: Improvement Components: Lucene.Net Core Reporter: Prescott Nasser Assignee: michael herndon Priority: Trivial Fix For: Lucene.Net 3.0.3 When building in release the artifacts are sent to various folders. It would be great if we could model the output of the release to mirror the output we use when cutting a release (saving some time). /bin/Contrib/*files /bin/Demo/*files /bin/Lucene.Net.dll /doc/Contrib/*files /doc/Demo/*files /doc/Lucene.Net.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (LUCENENET-456) Create a Build Target that outputs compiled artifacts in apache release format
[ https://issues.apache.org/jira/browse/LUCENENET-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael herndon reassigned LUCENENET-456: - Assignee: michael herndon Create a Build Target that outputs compiled artifacts in apache release format -- Key: LUCENENET-456 URL: https://issues.apache.org/jira/browse/LUCENENET-456 Project: Lucene.Net Issue Type: Improvement Components: Lucene.Net Core Reporter: Prescott Nasser Assignee: michael herndon Priority: Trivial Fix For: Lucene.Net 3.0.3 When building in release the artifacts are sent to various folders. It would be great if we could model the output of the release to mirror the output we use when cutting a release (saving some time). /bin/Contrib/*files /bin/Demo/*files /bin/Lucene.Net.dll /doc/Contrib/*files /doc/Demo/*files /doc/Lucene.Net.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Assigned] (LUCENENET-443) SpellChecker finaliser calls close regardless of if closed already
[
https://issues.apache.org/jira/browse/LUCENENET-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael herndon reassigned LUCENENET-443:
-
Assignee: michael herndon
SpellChecker finaliser calls close regardless of if closed already
--
Key: LUCENENET-443
URL: https://issues.apache.org/jira/browse/LUCENENET-443
Project: Lucene.Net
Issue Type: Improvement
Components: Lucene.Net Contrib
Affects Versions: Lucene.Net 2.9.2
Reporter: Stuart Robinson
Assignee: michael herndon
Labels: lucene, spellcheck, spellchecker
The SpellChecker Class currently has no publicly visible way of accessing the
closed field. It also calls close in the finaliser killing the process it is
in upon GC as this can throw an exceptin. I propose two changes:
Change the already existing method IsClosed() to public:
public bool IsClosed()
{
return closed;
}
and add a check on this in the finaliser:
~SpellChecker()
{
if (!IsClosed())
this.Close();
}
Ideally this class should implement IDisposable but I think this would be a
bigger job than this two line change.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-443) SpellChecker finaliser calls close regardless of if closed already
[
https://issues.apache.org/jira/browse/LUCENENET-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13107632#comment-13107632
]
michael herndon commented on LUCENENET-443:
---
Stuart, trunk was updated with typical MS style IDisposable pattern which
replaced the this.Close() in the finalizer. Calling Dispose() will check to see
if the SpellChecker is still open before calling Close() and suppress the
finalizer.
Leaving this open for a few days before resolving.
- Michael
SpellChecker finaliser calls close regardless of if closed already
--
Key: LUCENENET-443
URL: https://issues.apache.org/jira/browse/LUCENENET-443
Project: Lucene.Net
Issue Type: Improvement
Components: Lucene.Net Contrib
Affects Versions: Lucene.Net 2.9.2
Reporter: Stuart Robinson
Assignee: michael herndon
Labels: lucene, spellcheck, spellchecker
The SpellChecker Class currently has no publicly visible way of accessing the
closed field. It also calls close in the finaliser killing the process it is
in upon GC as this can throw an exceptin. I propose two changes:
Change the already existing method IsClosed() to public:
public bool IsClosed()
{
return closed;
}
and add a check on this in the finaliser:
~SpellChecker()
{
if (!IsClosed())
this.Close();
}
Ideally this class should implement IDisposable but I think this would be a
bigger job than this two line change.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-443) SpellChecker finaliser calls close regardless of if closed already
[
https://issues.apache.org/jira/browse/LUCENENET-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13105348#comment-13105348
]
michael herndon commented on LUCENENET-443:
---
I should have some over the weekend to fix it, though it would go into trunk
and the next release.
SpellChecker finaliser calls close regardless of if closed already
--
Key: LUCENENET-443
URL: https://issues.apache.org/jira/browse/LUCENENET-443
Project: Lucene.Net
Issue Type: Improvement
Components: Lucene.Net Contrib
Affects Versions: Lucene.Net 2.9.2
Reporter: Stuart Robinson
Labels: lucene, spellcheck, spellchecker
The SpellChecker Class currently has no publicly visible way of accessing the
closed field. It also calls close in the finaliser killing the process it is
in upon GC as this can throw an exceptin. I propose two changes:
Change the already existing method IsClosed() to public:
public bool IsClosed()
{
return closed;
}
and add a check on this in the finaliser:
~SpellChecker()
{
if (!IsClosed())
this.Close();
}
Ideally this class should implement IDisposable but I think this would be a
bigger job than this two line change.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-443) SpellChecker finaliser calls close regardless of if closed already
[
https://issues.apache.org/jira/browse/LUCENENET-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13105288#comment-13105288
]
michael herndon commented on LUCENENET-443:
---
Is there a good reason to bump IsClosed's access to public ? The Close()
method is being used as Dispose() would be.
Most likely classes that implement Close because of the Closable interface will
implement IDisposable instead in a future version. The shortest path to fixing
the bug would be to amend the finalizer.
SpellChecker finaliser calls close regardless of if closed already
--
Key: LUCENENET-443
URL: https://issues.apache.org/jira/browse/LUCENENET-443
Project: Lucene.Net
Issue Type: Improvement
Components: Lucene.Net Contrib
Affects Versions: Lucene.Net 2.9.2
Reporter: Stuart Robinson
Labels: lucene, spellcheck, spellchecker
The SpellChecker Class currently has no publicly visible way of accessing the
closed field. It also calls close in the finaliser killing the process it is
in upon GC as this can throw an exceptin. I propose two changes:
Change the already existing method IsClosed() to public:
public bool IsClosed()
{
return closed;
}
and add a check on this in the finaliser:
~SpellChecker()
{
if (!IsClosed())
this.Close();
}
Ideally this class should implement IDisposable but I think this would be a
bigger job than this two line change.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Resolved] (LUCENENET-400) Evaluate tooling for continuous integration server
[ https://issues.apache.org/jira/browse/LUCENENET-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael herndon resolved LUCENENET-400. --- Resolution: Fixed Fix Version/s: Lucene.Net 2.9.4g Evaluate tooling for continuous integration server -- Key: LUCENENET-400 URL: https://issues.apache.org/jira/browse/LUCENENET-400 Project: Lucene.Net Issue Type: Task Components: Build Automation, Project Infrastructure Reporter: Troy Howard Assignee: michael herndon Fix For: Lucene.Net 2.9.4g We would like to have a CI server setup for Lucene.Net. It has been suggested to do this outside of the ASF infrastructure, but this would not work for ASF. Please review the available options at http://ci.apache.org/ and evaluate which CI server system would be preferred for our setup. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Closed] (LUCENENET-400) Evaluate tooling for continuous integration server
[ https://issues.apache.org/jira/browse/LUCENENET-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael herndon closed LUCENENET-400. - https://cwiki.apache.org/LUCENENET/build-system-scripts.html the evaluation of tools over. the next thing to do is to put the scripts into trunk, make sure at least all the tests pass and get this setup in hudkins (jenkins) Evaluate tooling for continuous integration server -- Key: LUCENENET-400 URL: https://issues.apache.org/jira/browse/LUCENENET-400 Project: Lucene.Net Issue Type: Task Components: Build Automation, Project Infrastructure Reporter: Troy Howard Assignee: michael herndon Fix For: Lucene.Net 2.9.4g We would like to have a CI server setup for Lucene.Net. It has been suggested to do this outside of the ASF infrastructure, but this would not work for ASF. Please review the available options at http://ci.apache.org/ and evaluate which CI server system would be preferred for our setup. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Assigned] (LUCENENET-440) Some of the links on the website don't work
[ https://issues.apache.org/jira/browse/LUCENENET-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael herndon reassigned LUCENENET-440: - Assignee: michael herndon Some of the links on the website don't work --- Key: LUCENENET-440 URL: https://issues.apache.org/jira/browse/LUCENENET-440 Project: Lucene.Net Issue Type: Bug Components: Project Infrastructure Reporter: David Betteridge Assignee: michael herndon Priority: Minor The link to download the binarys from the home page doesn't work. I'm using I.E. 9 and it thinks the link is http://http//www.apache.org/dist/incubator/lucene.net/binaries/ Note the duplicate http at the front! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Closed] (LUCENENET-440) Some of the links on the website don't work
[ https://issues.apache.org/jira/browse/LUCENENET-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael herndon closed LUCENENET-440. - Some of the links on the website don't work --- Key: LUCENENET-440 URL: https://issues.apache.org/jira/browse/LUCENENET-440 Project: Lucene.Net Issue Type: Bug Components: Project Infrastructure Reporter: David Betteridge Assignee: michael herndon Priority: Minor Fix For: Lucene.Net 2.9.4 The link to download the binarys from the home page doesn't work. I'm using I.E. 9 and it thinks the link is http://http//www.apache.org/dist/incubator/lucene.net/binaries/ Note the duplicate http at the front! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-440) Some of the links on the website don't work
[ https://issues.apache.org/jira/browse/LUCENENET-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082664#comment-13082664 ] michael herndon commented on LUCENENET-440: --- Fixes have been posted to staging. http://lucene.net.staging.apache.org/lucene.net/ I'm leaving this issue open in case there are other dead or malformed links. The mailing archive looks like it was merged. Some of the links on the website don't work --- Key: LUCENENET-440 URL: https://issues.apache.org/jira/browse/LUCENENET-440 Project: Lucene.Net Issue Type: Bug Components: Project Infrastructure Reporter: David Betteridge Priority: Minor The link to download the binarys from the home page doesn't work. I'm using I.E. 9 and it thinks the link is http://http//www.apache.org/dist/incubator/lucene.net/binaries/ Note the duplicate http at the front! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Created] (LUCENENET-439) Correctly Rethrow exceptions in C#
Correctly Rethrow exceptions in C#
--
Key: LUCENENET-439
URL: https://issues.apache.org/jira/browse/LUCENENET-439
Project: Lucene.Net
Issue Type: Sub-task
Components: Lucene.Net Core, Lucene.Net Test
Affects Versions: Lucene.Net 2.9.2, Lucene.Net 2.9.4, Lucene.Net 2.9.4g
Environment: all
Reporter: michael herndon
There are a few places in the tests and possibly in the code where exceptions
are being rethrown incorrectly and erasing stacktrace.
Please fix these as you come across them and add the ticket number in the
commit message.
BaseTokenStreamTestCase.cs has a good example of this. Inside the RunBare
method:
// Do the test again with onlyUseNewAPI=true
try
{
onlyUseNewAPI = true;
base.RunBare();
}
catch(Exception ex)
{
System.Console.Out.WriteLine(Test failure of ' + GetType() + '
occurred with onlyUseNewAPI=true);
throw ex;
}
in this case you don't need to specify the exception, and we're trapping to
write out the context of the exception problem.
try
{
onlyUseNewAPI = true;
base.RunBare();
}
catch
{
Type type = this.GetType();
Console.WriteLine(Test failure of ' + type.Name + ' occurred with
onlyUseNewAPI=true);
throw;
}
http://msdn.microsoft.com/en-us/library/ms182363(v=vs.80).aspx
http://winterdom.com/2002/09/rethrowingexceptionsinc
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Created] (LUCENENET-438) replace java doc notation with ms style xml comments notation.
replace java doc notation with ms style xml comments notation.
Key: LUCENENET-438
URL: https://issues.apache.org/jira/browse/LUCENENET-438
Project: Lucene.Net
Issue Type: Improvement
Components: Lucene.Net Contrib, Lucene.Net Core
Affects Versions: Lucene.Net 2.9.4g
Environment: all
Reporter: michael herndon
The are a ton of java doc style notations inside the xml code comments, i.e.
{@link #IncrementToken}
These need to use the ms xml code comment style if there is an existing
equivalent. I'm not assigning this one. If you come across this on code you
are working on, please take an extra few minutes to fix up the comments.
If you need help, grab me on #lucene.net on irc or michaelherndon on skype.
Just let me know who you are and what help you need.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Updated] (LUCENENET-400) Evaluate tooling for continuous integration server
[ https://issues.apache.org/jira/browse/LUCENENET-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael herndon updated LUCENENET-400: -- Due Date: 30/Sep/11 (was: 28/Feb/11) Evaluate tooling for continuous integration server -- Key: LUCENENET-400 URL: https://issues.apache.org/jira/browse/LUCENENET-400 Project: Lucene.Net Issue Type: Task Components: Build Automation, Project Infrastructure Reporter: Troy Howard Assignee: michael herndon We would like to have a CI server setup for Lucene.Net. It has been suggested to do this outside of the ASF infrastructure, but this would not work for ASF. Please review the available options at http://ci.apache.org/ and evaluate which CI server system would be preferred for our setup. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-418) LuceneTestCase should not have a static method could throw exceptions.
[ https://issues.apache.org/jira/browse/LUCENENET-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13058781#comment-13058781 ] michael herndon commented on LUCENENET-418: --- r1132085 under the Lucene.Net_2_9_4g branch. The exception was removed. The static constructor still exists, but will be re-factored out at a later date. The paths for the TestBackwardsCompatability tests were also fixed. LuceneTestCase should not have a static method could throw exceptions. Key: LUCENENET-418 URL: https://issues.apache.org/jira/browse/LUCENENET-418 Project: Lucene.Net Issue Type: Bug Components: Lucene.Net Test Affects Versions: Lucene.Net 3.x Environment: Linux, OSX, etc Reporter: michael herndon Assignee: michael herndon Labels: test Original Estimate: 2m Remaining Estimate: 2m Throwing an exception in a base classes for 90% tests in a static method makes it hard to debug the issue in nunit. The test results came back saying that TestFixtureSetup was causing an issue even though it was the Static Constructor causing problems and this then propagates to all the tests that stem from LuceneTestCase. The TEMP_DIR needs to be moved to a static util class as a property or even a mixin method. This caused me hours to debug and figure out the real issue as the underlying exception method never bubbled up. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Created] (LUCENENET-418) LuceneTestCase should not have a static method could throw exceptions.
LuceneTestCase should not have a static method could throw exceptions. Key: LUCENENET-418 URL: https://issues.apache.org/jira/browse/LUCENENET-418 Project: Lucene.Net Issue Type: Bug Components: Lucene.Net Test Affects Versions: Lucene.Net 3.x Environment: Linux, OSX, etc Reporter: michael herndon Assignee: michael herndon Throwing an exception in a base classes for 90% tests in a static method makes it hard to debug the issue in nunit. The test results came back saying that TestFixtureSetup was causing an issue even though it was the Static Constructor causing problems and this then propagates to all the tests that stem from LuceneTestCase. The TEMP_DIR needs to be moved to a static util class as a property or even a mixin method. This caused me hours to debug and figure out the real issue as the underlying exception method never bubbled up. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-400) Evaluate tooling for continuous integration server
[ https://issues.apache.org/jira/browse/LUCENENET-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13037451#comment-13037451 ] michael herndon commented on LUCENENET-400: --- At the moment we're going to attempt to use hudkins (jenkins). However before closing this, I'd to ensure that we can get everything to work on hudkins. * Clean bin directories. * Increment Build Number. * Build All Build subsets of projects. * SandCastle for msdn style documentation. * Executing NUnit Tests (and evaluating mbunit on windows builds since their unit testing reporting is better out of the box). * Executing NCover. * Run xbuild on mono. Evaluate tooling for continuous integration server -- Key: LUCENENET-400 URL: https://issues.apache.org/jira/browse/LUCENENET-400 Project: Lucene.Net Issue Type: Task Components: Build Automation, Project Infrastructure Reporter: Troy Howard Assignee: michael herndon We would like to have a CI server setup for Lucene.Net. It has been suggested to do this outside of the ASF infrastructure, but this would not work for ASF. Please review the available options at http://ci.apache.org/ and evaluate which CI server system would be preferred for our setup. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Work started] (LUCENENET-400) Evaluate tooling for continuous integration server
[ https://issues.apache.org/jira/browse/LUCENENET-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LUCENENET-400 started by michael herndon. Evaluate tooling for continuous integration server -- Key: LUCENENET-400 URL: https://issues.apache.org/jira/browse/LUCENENET-400 Project: Lucene.Net Issue Type: Task Components: Build Automation, Project Infrastructure Reporter: Troy Howard Assignee: michael herndon We would like to have a CI server setup for Lucene.Net. It has been suggested to do this outside of the ASF infrastructure, but this would not work for ASF. Please review the available options at http://ci.apache.org/ and evaluate which CI server system would be preferred for our setup. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[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-tabpanelfocusedCommentId=12999512#comment-12999512 ] michael herndon commented on LUCENENET-377: --- I would suggestion just creating the 2008 solution files. The project files (unless it has version specific msbuild targets like in web projects) are generally compatible for both solutions. If they do have version specific msbuild targets: its not terribly hard to do conditionals so that the project files work for both vs 2008 vs 2010 solution 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
[jira] Issue Comment Edited: (LUCENENET-379) Clean up Lucene.Net website
[ https://issues.apache.org/jira/browse/LUCENENET-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995283#comment-12995283 ] michael herndon edited comment on LUCENENET-379 at 2/16/11 1:32 PM: I think anything would be better than the current one (which would look cool if it was cleaned up and put on the side of a chevelle. But I don't know how would help brand lucene.net). I'd say keep doing a few more variations. Open it up for the public to make some submissions as well. (giving credit to whoever's design is chosen maybe even give them some social media love). The final one needs to work well with both rgb and cymk color formats and in a scalable graphics format so that it can be resized cleanly. Also it should have a visual aspect of it that can be turned into a decent 16 x 16 favicon. (like the 3 yellow hexagons that is in the jpg). Though keep in mind basic color theory. Yellow is irritating on the eyes. Its definitely grabs attention, but its harder on the eyes for an extended period of time. Green is the most relaxing. But above all else: keep moving forward towards something new. :: edited due to posting this while on an empty stomach, never wise :: was (Author: michaelherndon): I think anything would be better than the current one (which would look cool if was cleaned up and put on the side of a chevelle, but I don't know how would help brand lucene.net). I'd say keep doing a few more variations. open it up for the public to make some submissions as well. (giving credit to whoever's design is chosen maybe even give them some social media love). The final one needs to work well with both rgb and cymk color formats and in a scalable graphics format so that it can be resized cleanly. Also it should have a visual aspect of it that can be turned into a decent 16 x 16 favicon. (like the 3 yellow hexagons that is in the jpg). Though keep in mind basic color theory. Yellow is irritating on the eyes. Its definitely grabs attention, but its harder on the eyes for an extended period of time. Green is the most relaxing. But above all else keep moving forward towards something new. Clean up Lucene.Net website --- Key: LUCENENET-379 URL: https://issues.apache.org/jira/browse/LUCENENET-379 Project: Lucene.Net Issue Type: Task Reporter: George Aroush Attachments: Lucene.zip, New Logo Idea.jpg, asfcms.zip, asfcms_1.patch The existing Lucene.Net home page at http://lucene.apache.org/lucene.net/ is still based on the incubation, out of date design. This JIRA task is to bring it up to date with other ASF project's web page. The existing website is here: https://svn.apache.org/repos/asf/lucene/lucene.net/site/ See http://www.apache.org/dev/project-site.html to get started. It would be best to start by cloning an existing ASF project's website and adopting it for Lucene.Net. Some examples, https://svn.apache.org/repos/asf/lucene/pylucene/site/ and https://svn.apache.org/repos/asf/lucene/java/site/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (LUCENENET-379) Clean up Lucene.Net website
[ https://issues.apache.org/jira/browse/LUCENENET-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995283#comment-12995283 ] michael herndon commented on LUCENENET-379: --- I think anything would be better than the current one (which would look cool if was cleaned up and put on the side of a chevelle, but I don't know how would help brand lucene.net). I'd say keep doing a few more variations. open it up for the public to make some submissions as well. (giving credit to whoever's design is chosen maybe even give them some social media love). The final one needs to work well with both rgb and cymk color formats and in a scalable graphics format so that it can be resized cleanly. Also it should have a visual aspect of it that can be turned into a decent 16 x 16 favicon. (like the 3 yellow hexagons that is in the jpg). Though keep in mind basic color theory. Yellow is irritating on the eyes. Its definitely grabs attention, but its arder on the eyes for an extended period of time. Green is the most relaxing. But above all else keep moving forward towards something new. Clean up Lucene.Net website --- Key: LUCENENET-379 URL: https://issues.apache.org/jira/browse/LUCENENET-379 Project: Lucene.Net Issue Type: Task Reporter: George Aroush Attachments: Lucene.zip, New Logo Idea.jpg, asfcms.zip, asfcms_1.patch The existing Lucene.Net home page at http://lucene.apache.org/lucene.net/ is still based on the incubation, out of date design. This JIRA task is to bring it up to date with other ASF project's web page. The existing website is here: https://svn.apache.org/repos/asf/lucene/lucene.net/site/ See http://www.apache.org/dev/project-site.html to get started. It would be best to start by cloning an existing ASF project's website and adopting it for Lucene.Net. Some examples, https://svn.apache.org/repos/asf/lucene/pylucene/site/ and https://svn.apache.org/repos/asf/lucene/java/site/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (LUCENENET-379) Clean up Lucene.Net website
[ https://issues.apache.org/jira/browse/LUCENENET-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995283#comment-12995283 ] michael herndon edited comment on LUCENENET-379 at 2/16/11 1:21 PM: I think anything would be better than the current one (which would look cool if was cleaned up and put on the side of a chevelle, but I don't know how would help brand lucene.net). I'd say keep doing a few more variations. open it up for the public to make some submissions as well. (giving credit to whoever's design is chosen maybe even give them some social media love). The final one needs to work well with both rgb and cymk color formats and in a scalable graphics format so that it can be resized cleanly. Also it should have a visual aspect of it that can be turned into a decent 16 x 16 favicon. (like the 3 yellow hexagons that is in the jpg). Though keep in mind basic color theory. Yellow is irritating on the eyes. Its definitely grabs attention, but its harder on the eyes for an extended period of time. Green is the most relaxing. But above all else keep moving forward towards something new. was (Author: michaelherndon): I think anything would be better than the current one (which would look cool if was cleaned up and put on the side of a chevelle, but I don't know how would help brand lucene.net). I'd say keep doing a few more variations. open it up for the public to make some submissions as well. (giving credit to whoever's design is chosen maybe even give them some social media love). The final one needs to work well with both rgb and cymk color formats and in a scalable graphics format so that it can be resized cleanly. Also it should have a visual aspect of it that can be turned into a decent 16 x 16 favicon. (like the 3 yellow hexagons that is in the jpg). Though keep in mind basic color theory. Yellow is irritating on the eyes. Its definitely grabs attention, but its arder on the eyes for an extended period of time. Green is the most relaxing. But above all else keep moving forward towards something new. Clean up Lucene.Net website --- Key: LUCENENET-379 URL: https://issues.apache.org/jira/browse/LUCENENET-379 Project: Lucene.Net Issue Type: Task Reporter: George Aroush Attachments: Lucene.zip, New Logo Idea.jpg, asfcms.zip, asfcms_1.patch The existing Lucene.Net home page at http://lucene.apache.org/lucene.net/ is still based on the incubation, out of date design. This JIRA task is to bring it up to date with other ASF project's web page. The existing website is here: https://svn.apache.org/repos/asf/lucene/lucene.net/site/ See http://www.apache.org/dev/project-site.html to get started. It would be best to start by cloning an existing ASF project's website and adopting it for Lucene.Net. Some examples, https://svn.apache.org/repos/asf/lucene/pylucene/site/ and https://svn.apache.org/repos/asf/lucene/java/site/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
