<!-- 
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Wed Jun 19 03:26:22 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/DCOM-73/DCOM-73.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>[DCOM-73] CodeGeneration using Doctrine\Common\Persistence\Mapping\ObjectMetadata</title>
                <link>http://www.doctrine-project.org/jira/browse/DCOM-73</link>
                <project id="10043" key="DCOM">Doctrine Common</project>
                        <description>&lt;p&gt;Currently we have tons of code in the ODM/ORMs regarding code generation that are ugly to extend and maintain. We should extract all them into a new component, for example named: doctrine-code-generator&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;It should be feed by only instances of Doctrine\Common\Persistence\Mapping\ObjectMetadata into a twig template.&lt;/li&gt;
	&lt;li&gt;A base template for an entity/document is shipped&lt;/li&gt;
	&lt;li&gt;Maybe ORM/ODM specific child templates or twig traits are necessary to handle writing annotations. This could also be done by adding hooks into the code-generation somehow.&lt;/li&gt;
	&lt;li&gt;Each entity of the user can provide its own template, for examples from a configurable directory &quot;code_templates/Vendor.ProjectBundle.Entity.User.twig&quot; to extend the base template and add own code.&lt;/li&gt;
	&lt;li&gt;As a perspective we should aim for 5.4 generating a trait so that you can have your entity &quot;class User 
{ use UserBase; }
&lt;p&gt;&quot;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
            <key id="13121">DCOM-73</key>
            <summary>CodeGeneration using Doctrine\Common\Persistence\Mapping\ObjectMetadata</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</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="jwage">Jonathan H. Wage</assignee>
                                <reporter username="beberlei">Benjamin Eberlei</reporter>
                        <labels>
                    </labels>
                <created>Mon, 24 Oct 2011 07:07:23 +0000</created>
                <updated>Thu, 16 Feb 2012 19:27:38 +0000</updated>
                                                    <fixVersion>2.3</fixVersion>
                                        <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>