[
http://jira.codehaus.org/browse/MHIBERNATE-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109669
]
Paul Shemansky commented on MHIBERNATE-57:
------------------------------------------
Since starting with Maven, I have used this config directory for build
configuration files and developer-oriented files which are only relevant to
describing "build-configuring" process. The Maven site certainly does not
"seem" to specify the true purpose of the "src/main/config" directory, although
it does mention it is used for "Configuration Files" here :
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
I may have missed it, or, as you mentioned, I suppose it is purely
philosophical, leaving much to the imagination. I will look for more
references and try to contribute something towards finding out more about this,
but my opinion was based on the following.
Templates very well may not fit into the "config" description, but they are
clearly a part of the build process, and are generally something which is
configured and customized to suit specialized needs. Before I changed it, it
was "${basedir}/", which seemed a little bit too general to me, and may be
confusing to other developers who join my projects. It was also clear to me
that "src/main/resources" which is included in the packaging phase of the build
would be the more likely place to store any "runtime" configuration files. It
is also evident that "src/main/config" does not get packaged, and if it doesn't
contain "runtime" configurations, I figured it may as well contain build
configuration files and configuration customizations which don't fit into
Maven's "filter"-ing paradigm.
Being the conventional developer that I am, I have since then changed my
original opinion that the templates directory should probably also contain a
"hibernate" directory to separate it from other "config" directories, making it
"src/main/config/hibernate/templates". Perhaps I am in fact too organized, but
falling short of extensive documentation writing in some of my projects, I try
to keep things as intuitive as possible.
I apologize for not explaining myself before, but if there is anything else I
can help with, please don't hesitate to let me know.
> Verify templatePath changes work. If they don't please apply the attached
> patch.
> ---------------------------------------------------------------------------------
>
> Key: MHIBERNATE-57
> URL: http://jira.codehaus.org/browse/MHIBERNATE-57
> Project: Maven 2.x Hibernate Plugin
> Issue Type: Sub-task
> Affects Versions: 2.0-alpha-3
> Reporter: Paul Shemansky
> Assignee: Johann Reyes
> Attachments: hibernate3-maven-plugin-templatepath-patch.txt
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> While trying out the latest changes to 2.0-alpha-3-SNAPSHOT, I noticed that
> my "templatepath" component variable was still being ignored.
> I made changes to my HibernateExporterMojo.java to accommodate for all other
> Exporters.
> I also changed my default templatepath directory to point to
> "${basedir}/src/main/config/templates", which I believe is more standard
> according to the Maven Standard Directory Layout.
> When, I applied the attached patch, I can override the plug-in using my
> custom templates directory.
> Your JUnit tests are sufficient enough to test my changes.
> If my corrections are wrong, make adjustments, and let me know.
> Sincerely,
> Paul Shemansky
> paul.shemansky[at]gmail[dot]com
> P.S. - Thank you to all that make this an extraordinary plug-in.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
