You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Grant Ingersoll (JIRA)" <ji...@apache.org> on 2007/05/22 16:24:16 UTC
[jira] Created: (SOLR-245) Coding Style
Coding Style
------------
Key: SOLR-245
URL: https://issues.apache.org/jira/browse/SOLR-245
Project: Solr
Issue Type: New Feature
Environment: Intellij IDEA 6.x
Reporter: Grant Ingersoll
Priority: Trivial
Attachments: Lucene.xml
Per discussion at http://www.mail-archive.com/solr-dev@lucene.apache.org/msg04068.html, here is my attempt at an IntelliJ coding style template that more or less fits the Lucene/Solr style. Please feel free to change as needed, it is just a starting point.
As per Doug's discussion way back when (http://www.gossamer-threads.com/lists/lucene/java-dev/18320?search_string=code%20style;#18320), I don't think it is a big deal if submitted code isn't 100% formatted the way we want.
Attachment to follow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-245) Coding Style
Posted by "Grant Ingersoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grant Ingersoll updated SOLR-245:
---------------------------------
Attachment: Lucene.xml
IntelliJ code style. Has to be installed under the codestyles configuration in IntelliJ
> Coding Style
> ------------
>
> Key: SOLR-245
> URL: https://issues.apache.org/jira/browse/SOLR-245
> Project: Solr
> Issue Type: New Feature
> Environment: Intellij IDEA 6.x
> Reporter: Grant Ingersoll
> Priority: Trivial
> Attachments: Lucene.xml
>
>
> Per discussion at http://www.mail-archive.com/solr-dev@lucene.apache.org/msg04068.html, here is my attempt at an IntelliJ coding style template that more or less fits the Lucene/Solr style. Please feel free to change as needed, it is just a starting point.
> As per Doug's discussion way back when (http://www.gossamer-threads.com/lists/lucene/java-dev/18320?search_string=code%20style;#18320), I don't think it is a big deal if submitted code isn't 100% formatted the way we want.
> Attachment to follow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-245) Coding Style
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Otis Gospodnetic updated SOLR-245:
----------------------------------
Attachment: lucene-eclipse-3.2.xml
And here is an Eclipse 3.2 code style for Lucene and its children.
> Coding Style
> ------------
>
> Key: SOLR-245
> URL: https://issues.apache.org/jira/browse/SOLR-245
> Project: Solr
> Issue Type: New Feature
> Environment: Intellij IDEA 6.x
> Reporter: Grant Ingersoll
> Priority: Trivial
> Attachments: lucene-eclipse-3.2.xml, Lucene.xml
>
>
> Per discussion at http://www.mail-archive.com/solr-dev@lucene.apache.org/msg04068.html, here is my attempt at an IntelliJ coding style template that more or less fits the Lucene/Solr style. Please feel free to change as needed, it is just a starting point.
> As per Doug's discussion way back when (http://www.gossamer-threads.com/lists/lucene/java-dev/18320?search_string=code%20style;#18320), I don't think it is a big deal if submitted code isn't 100% formatted the way we want.
> Attachment to follow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-245) Coding Style
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502923 ]
Hoss Man commented on SOLR-245:
-------------------------------
FYI: these are now attached to the wiki so they are easier to find...
http://wiki.apache.org/solr/HowToContribute
> Coding Style
> ------------
>
> Key: SOLR-245
> URL: https://issues.apache.org/jira/browse/SOLR-245
> Project: Solr
> Issue Type: New Feature
> Environment: Intellij IDEA 6.x
> Reporter: Grant Ingersoll
> Priority: Trivial
> Attachments: lucene-eclipse-3.2.xml, Lucene.xml
>
>
> Per discussion at http://www.mail-archive.com/solr-dev@lucene.apache.org/msg04068.html, here is my attempt at an IntelliJ coding style template that more or less fits the Lucene/Solr style. Please feel free to change as needed, it is just a starting point.
> As per Doug's discussion way back when (http://www.gossamer-threads.com/lists/lucene/java-dev/18320?search_string=code%20style;#18320), I don't think it is a big deal if submitted code isn't 100% formatted the way we want.
> Attachment to follow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SOLR-245) Coding Style
Posted by "Grant Ingersoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grant Ingersoll closed SOLR-245.
--------------------------------
Resolution: Fixed
This probably hits the main two IDE's that people use. People can feel free to add new styles for other ones, if they see fit.
> Coding Style
> ------------
>
> Key: SOLR-245
> URL: https://issues.apache.org/jira/browse/SOLR-245
> Project: Solr
> Issue Type: New Feature
> Environment: Intellij IDEA 6.x
> Reporter: Grant Ingersoll
> Priority: Trivial
> Attachments: lucene-eclipse-3.2.xml, Lucene.xml
>
>
> Per discussion at http://www.mail-archive.com/solr-dev@lucene.apache.org/msg04068.html, here is my attempt at an IntelliJ coding style template that more or less fits the Lucene/Solr style. Please feel free to change as needed, it is just a starting point.
> As per Doug's discussion way back when (http://www.gossamer-threads.com/lists/lucene/java-dev/18320?search_string=code%20style;#18320), I don't think it is a big deal if submitted code isn't 100% formatted the way we want.
> Attachment to follow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.