[xdoclet-plugins-interest] [jira] Created: (XDP-51) Support for prefix in Componet

2005-05-05 Thread Yuval Carmel (JIRA)
Support for prefix in Componet -- Key: XDP-51 URL: http://jira.codehaus.org/browse/XDP-51 Project: XDoclet 2 Plugins Type: New Feature Environment: Win32, Hibernate 3.0, xdoclet-2.0.2.jar , xdoclet-plugin-hibernate-1.0.jar Reporter:

[xdoclet-plugins-interest] [jira] Created: (XDP-50) hibernate.one-to-one property-ref tag generates incorrect hbm.xml

2005-05-05 Thread Donald Armstrong (JIRA)
hibernate.one-to-one property-ref tag generates incorrect hbm.xml - Key: XDP-50 URL: http://jira.codehaus.org/browse/XDP-50 Project: XDoclet 2 Plugins Type: Bug Components: hibernate Versions: hi

Re: [xdoclet-plugins-interest] Hibernate XDoclet<>XDoclet 2 tag migration

2005-05-05 Thread Anatol Pomozov
I think that from user's point of view there shouldn't be differences between XDoclet1 and XDoclet2. And I have started to persuading myself to make xdoclet2 hibernate tags compatibilÐ with xdoclet1. From the developer's side I would say that xdoclet much better designed. It uses Jelly, Velocit

Re: [xdoclet-plugins-interest] Hibernate XDoclet<>XDoclet 2 tag migration

2005-05-05 Thread John Latham
>> But we can decide what to do with Xdoclet1 - 2 incompatibility. The main reason in doclet-tag naming was accordance with xml tag names. << There is a fundamental question for the plugin: is it a goal to have tag compatibility with XDoclet1? I'm struggling to understand the positioning of the

Re: [xdoclet-plugins-interest] Hibernate XDoclet<>XDoclet 2 tag migration

2005-05-05 Thread Anatol Pomozov
Oops sorry +1 @hibernate.key -> @hibernate.collection-key Anatol Pomozov wrote: I cant help you with such tool. But we can decide what to do with Xdoclet1 - 2 incompatibility. The main reason in doclet-tag naming was accordance with xml tag names. That is why we use @hibernate.key-property inst

[xdoclet-plugins-interest] [jira] Commented: (XDP-49) Support for union-subclass

2005-05-05 Thread Anatol Pomozov (JIRA)
[ http://jira.codehaus.org/browse/XDP-49?page=comments#action_38580 ] Anatol Pomozov commented on XDP-49: --- Concerinig 1 item: use @hibernate.key instead of @hibernate.key-property > Support for union-subclass > -- > >

Re: [xdoclet-plugins-interest] Hibernate XDoclet<>XDoclet 2 tag migration

2005-05-05 Thread Anatol Pomozov
I cant help you with such tool. But we can decide what to do with Xdoclet1 - 2 incompatibility. The main reason in doclet-tag naming was accordance with xml tag names. That is why we use @hibernate.key-property instead of @hibernate.collection-key. But personnaly for me @hibernate.collection-ke

[xdoclet-plugins-interest] Hibernate XDoclet<>XDoclet 2 tag migration

2005-05-05 Thread John Latham
Hi, For my project right now, the Hibernate plugin for XDoclet seems better than the equivalent for XDoclet2 (or perhaps I'm not using the right tags yet). So far, I've gone from XDoclet->XDoclet2 and back again I would like to switch back and forth like this as both systems develop. This is pa

[xdoclet-plugins-interest] Rights to XDP JIRA

2005-05-05 Thread Anatol Pomozov
Hello, Konstantin. I would like to assign XDP-49 to me but I cant. Seems that I have no developer rights in Jira on XDP project. Reason message:*Worklog*: You don''t have permission to work on this issue. Could you grant me rights? --- Th

[xdoclet-plugins-interest] [jira] Created: (XDP-49) Support for union-subclass

2005-05-05 Thread John Latham (JIRA)
Support for union-subclass -- Key: XDP-49 URL: http://jira.codehaus.org/browse/XDP-49 Project: XDoclet 2 Plugins Type: New Feature Components: hibernate Versions: hibernate-1.0 Environment: Win32, Eclipse IDE Reporter: John La