[jboss-dev] Re: jpa-deployers

Carlo de Wolf cdewolf at redhat.com
Tue Jan 27 06:33:48 EST 2009


I've reconstructed the history a bit. Some issues are still left behind 
in the old projects, because commits spanned multiple projects:
Issue -> Fix Version
- https://jira.jboss.org/jira/browse/JBCTS-822 -> 0.1.1
- https://jira.jboss.org/jira/browse/JBAS-5940 -> 0.1.2
- https://jira.jboss.org/jira/browse/JBAS-6111 -> 1.0.0-Beta1
- https://jira.jboss.org/jira/browse/JBAS-6093 -> 1.0.0-Beta2
- https://jira.jboss.org/jira/browse/JBAS-6382 -> 1.0.0-Beta5

Now that I'm looking at the new issues I see that commit information is 
lost anyway: https://developer.atlassian.com/jira/browse/SVN-100

Bugger,

Carlo

Dimitris Andreadis wrote:
> Carlo de Wolf wrote:
>
>> Dimitris Andreadis wrote:
>>> Is the jpa-deployers in Branch_5_0 complete?
>>>
>>> (I think so)
>>> https://jira.jboss.org/jira/browse/JBAS-6384
>>>
>>> And what about those JIRA with no component, no affects version, no 
>>> fixed version?
>>>
>>> https://jira.jboss.org/jira/browse/JBAS-6382 - Allow for 
>>> configuration of spec compliant persistence unit resolving
>>>
>>> https://jira.jboss.org/jira/browse/JBAS-6377 - Allow for persistence 
>>> unit resolving beyond enterprise application archives (e.g. whole 
>>> server)
>>>
>>> How are we suppose to track what goes into which release???
>> Very good question. :-)
>>
>> I think we need a JBJPA project.
>
> Okey-dokey :)
>
> https://jira.jboss.org/jira/secure/admin/ViewProject.jspa?pid=12310781




More information about the jboss-development mailing list