Anything I should know or do before getting myself started??
- Browse around the wiki: http://xdoclet.sourceforge.net/wiki/wakka.php?wakka=XDoclet2Architecture. Feel free to update it.
- Subscribe to the xdoclet-plugins SF project's mailing list.
- Browse the source code for the existing xdoclet-plugins plugins and try to follow the patterns used there.
- Yell if something is not clear :-)
- Submit your code to xdoclet-plugins' JIRA: http://jira.codehaus.org/secure/BrowseProject.jspa?id=10231
After a few contributions, we'll grant you write access to the CVS tree.
Aslak
Thanks !
I'm actually already subscribed to the plugins' MLs, wrong copy paste made me cc the previous to the commits' ML instead of interest's... (it's late)
The traffic on xdoclet-plugins' mailing list is still kind of low, because people are used to talking on [EMAIL PROTECTED] I'm copying both lists, and encourage people to do so for a while. When we have formed enough activity around xdoclet-plugins, I suggest we drop xdoclet 2 plugins discussions out of the old mailing list. (but not yet).
I already lurked around the wiki, I'll try to starting looking at the
sources from tomorrow on. (Well, <blog-style>I have some dishwashing and
other cleaning to do first</blog-style>)
If you run into trouble and then see some light, it would be great if you documented some of your findings/tricks/tips in the wiki too :-)
I guess it should at least provide backwards compatibility with
xdoclet1.2 tags.
Yes, that's very important in order to encourage users to switch from 1.2 to 2.0. But if you can make some tags/tag attributes optional (by having the plugin provide sensible defaults) that is a good thing. Because it makes it easier for people to @tag up their sources without having to add a gazillion of tags.
Were there any unit tests for the web plugins in 1.2? (Yes, i'm going to look on cvs ;))
Unfortunately not :-(
But! There are samples in the 1.2 codebase. I suggest you pick one (or several) of the files with @web tags and use them as sample input to your unit tests. I recommend you create a new folder called testapp-web and stick those @web tagged sources there. This will make it easier for future say jboss-web plugin writers to use the same sources as test-input.
You should also run XDoclet 1.2 and copy the generated web.xml into your 2.0 plugin's source tree and use that as expected result.
This should be enough to provide an acceptance test that tests the basics at least.
Take a look at the hibernate mapping plugin in xdoclet-plugins. Your plugin's file structure and general coding standards should look kind of similar to that.
I hope this is enough to get you started. If not, we're here to help. Your contribution is much appreciated!
Cheers, Aslak
greg
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ xdoclet-plugins-interest mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-plugins-interest
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
-- http://blogs.codehaus.org/people/rinkrank/
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
