I wrote simply Torque -> Hibernate schema converter (just a jelly file)
It's not perfect but it did simplify my conversion a little bit.
Michal Maczka wrote:
-----Original Message----- From: news [mailto:[EMAIL PROTECTED] Behalf Of Leo Simons Sent: Saturday, May 31, 2003 1:26 PM To: [EMAIL PROTECTED] Subject: basic forrest plugin for maven
Hi gang,
I've written a very basic forrest plugin:
http://cvs.apache.org/~leosimons/maven-forrest-plugin.zip (12 megs!)
I've copied over a forrest snapshot build from feb 19 into the plugin-resources directory, tweaked the forrest.build.xml file (see the forrest.build.xml.patch.txt), added a plugin.properties, project.properties, then added a minimal plugin.jelly script which just calls the ant buildfile.
---
You can see it in use in the avalon-excalibur cvs:
1 - install maven beta 9 (or later, probably) 2 - unzip the plugin into your maven plugins/ dir 3 - checkout the avalon and avalon-excalibur cvses 4 - cd avalon-excalibur/compatibility 5 - maven xdoc
Current usage:
<postGoal name="xdoc"> <attainGoal name="forrest:generate"/> </postGoal>
or call "maven forrest:generate" directly.
---
I am sure there is a better way to do this, but given the lack of plugin writing docs this was the easiest thing I could figure out that would make things work.
Is there interest in improving this? Anyone want to help out here? I think most of the things that need doing are just an hour of two of work for those among you who know maven well :D
---
Partial todo ------------ - add plugin to forrest cvs or maven cvs (which one?)
I will just refer to this single point. I believe that Maven should just host a small bunch of core plugins which will be deeply tested and documented.
I myself recently added skeleton of Hibernate plugin..and already regret, because I cannot improve (too many private Methods in Hibernate code) and I am not using Hibernate so often. I am not following the changes in Hibernate code .. so it could be that plugin will be broken soon.
Other example: Somebody recently provide a patch for Maven-JBuilder plugin. It seems that not so many (if someone) of active Maven developers use JBuilder. So there is almost no one who can test this patch and apply it. Committing the code which is untested is very bad practice.
So my opinion is: better host maven-forrest plugin @ http://xml.apache.org/forrest/
Because this is only way to assure the quality of Maven itself and the quality of plugins.
Surly Maven can help to "catalog" the plugins etc. But this is a different subject...
Michal
P.S.
I used JBuilder Plugin patch just as example and I don't know anything about the quality of the patch.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
