<!-- 
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Mon May 20 16:47:33 UTC 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://www.doctrine-project.org/jira/si/jira.issueviews:issue-xml/DDC-2287/DDC-2287.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Doctrine Project</title>
    <link>http://www.doctrine-project.org/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>5.2.7</version>
        <build-number>850</build-number>
        <build-date>21-02-2013</build-date>
    </build-info>

<item>
            <title>[DDC-2287] Getter/Setter: generate &quot;isEnabled()&quot; instead of &quot;getEnabled()&quot; for boolean field in entity classes</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-2287</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;It would be better if doctrine generated &quot;isEnabled()&quot; instead of &quot;getEnabled()&quot; for boolean field in entity classes. Because, it is more meaningful.&lt;/p&gt;</description>
                <environment></environment>
            <key id="14467">DDC-2287</key>
            <summary>Getter/Setter: generate &quot;isEnabled()&quot; instead of &quot;getEnabled()&quot; for boolean field in entity classes</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="beberlei">Benjamin Eberlei</assignee>
                                <reporter username="sukhrob">Sukhrob Khakimov</reporter>
                        <labels>
                    </labels>
                <created>Fri, 8 Feb 2013 09:36:14 +0000</created>
                <updated>Tue, 26 Feb 2013 08:50:40 +0000</updated>
                                                                    <component>ORM</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>2</watches>
                        <comments>
                    <comment id="19486" author="ocramius" created="Fri, 8 Feb 2013 09:40:45 +0000"  >&lt;p&gt;Not sure this kind of check should be handled. Starting to add all this kind of rules makes me think that it is becoming a big ball of mud&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>