<!-- 
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Thu Jun 20 05:12:15 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/DC-287/DC-287.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>[DC-287] Schema: package property for model</title>
                <link>http://www.doctrine-project.org/jira/browse/DC-287</link>
                <project id="10031" key="DC">Doctrine 1</project>
                        <description>&lt;p&gt;There is a property &quot;package&quot; for the schema.yml file.&lt;br/&gt;
&lt;a href=&quot;http://www.doctrine-project.org/documentation/manual/1_0/en/yaml-schema-files#features-examples:packages&quot; class=&quot;external-link&quot;&gt;http://www.doctrine-project.org/documentation/manual/1_0/en/yaml-schema-files#features-examples:packages&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;But this should be used only for plugin symfony.&lt;/p&gt;

&lt;p&gt;It will be good to have the same feature for classic model (not plugin), to be available to organize the model inside of the model folder.&lt;/p&gt;

&lt;p&gt;This feature is critical for huge project. Indeed having 200 files at the root of the folder model/doctrine is very difficult to maintain.&lt;/p&gt;
</description>
                <environment></environment>
            <key id="10503">DC-287</key>
            <summary>Schema: package property for model</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</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="titang">Mickael HOAREAU</reporter>
                        <labels>
                    </labels>
                <created>Wed, 25 Nov 2009 04:03:02 +0000</created>
                <updated>Tue, 8 Jun 2010 16:19:51 +0000</updated>
                                                                    <component>Schema Files</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="11294" author="titang" created="Fri, 25 Dec 2009 03:05:58 +0000"  >&lt;p&gt;Here a possible patch for doctrine 1.2, it is working for the basic cases.&lt;/p&gt;

&lt;p&gt;It probably needs to be improved.&lt;/p&gt;</comment>
                    <comment id="12195" author="jwage" created="Mon, 15 Mar 2010 11:41:05 +0000"  >&lt;p&gt;I agree this is a problem, but your patch is not good. It doesn&apos;t follow the coding standards and has some formatting problems. Also, it doesn&apos;t seem like a good solution. What do you think?&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                    <attachment id="10259" name="DC-287.patch" size="4117" author="titang" created="Fri, 25 Dec 2009 03:05:58 +0000" />
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>