https://bugs.eclipse.org/bugs/show_bug.cgi?id=360727
Requests upload of Maven artifact for JPA 2.0.
--
@matthewadams12
mailto:matt...@matthewadams.me
skype:matthewadams12
yahoo:matthewadams
aol:matthewadams12
google-talk:matthewadam...@gmail.com
msn:matt...@matthewadams.me
http://matthewadams.me
[
https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew T. Adams resolved JDO-684.
--
Resolution: Fixed
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> -
[
https://issues.apache.org/jira/browse/JDO-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127700#comment-13127700
]
Matthew T. Adams commented on JDO-696:
--
Feeback from conf call:
* minor patch changes (f
Attendees: Craig Russell, Matthew Adams
Agenda:
1. Fix OSGi Export-Package entries
https://issues.apache.org/jira/browse/JDO-684
Latest fix looks good. Resolve it.
2. JDO 3.0 dependency on JPA
3.0 (and 3.0.1) still depend on JPA 1.0. We decided that 3.1 did not
allow use of JPA 2.0 an
[
https://issues.apache.org/jira/browse/JDO-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew T. Adams updated JDO-696:
-
Attachment: (was: JDO-696.src.patch)
> Throw on unrecognized javax.jdo options
> ---
[
https://issues.apache.org/jira/browse/JDO-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew T. Adams updated JDO-696:
-
Attachment: JDO-684.src.patch
Aforementioned patch with changes as a result of conf call feedback.
[
https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew T. Adams updated JDO-684:
-
Attachment: (was: JDO-684.patch)
> Fix OSGi Export-Package entries in JDO 3.0 manifest to in
[
https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew T. Adams updated JDO-684:
-
Attachment: JDO-684.patch
Reviewed JDO-673 on conf call, so reverted JPA dependency range back to
[
Hi all,
I know we recently released 3.0, will release 3.0.1 soon, and are
planning 3.1. The thing is, we are planning on removing interface
JDOEntityManagerFactory, which I believe to be a breaking change.
IMHO, that should warrant a rev of the major version number, so that
JDO 3.1 really should
One minor clarification:
On Fri, Oct 14, 2011 at 12:07 PM, Craig L Russell
wrote:
> 2. JDO 3.0 dependency on JPA
>
> 3.0 (and 3.0.1) still depend on JPA 1.0. We decided that 3.1 did not allow
> use of JPA 2.0 and it doesn't make sense to continue to support JPA 1.0.
> Instead, we should just re
On Fri, Oct 14, 2011 at 12:07 PM, Craig L Russell
wrote:
> 3. Other issues
>
> https://issues.apache.org/jira/browse/JDO-696 applies to both JDOHelper as
> well as IUT if the PMF is constructed directly with a new
> VendorPersistenceManagerFactory. Add api test case and tck test case for IUT
> c
On Oct 14, 2011, at 12:27 PM, Matthew Adams wrote:
One minor clarification:
On Fri, Oct 14, 2011 at 12:07 PM, Craig L Russell
wrote:
2. JDO 3.0 dependency on JPA
3.0 (and 3.0.1) still depend on JPA 1.0. We decided that 3.1 did
not allow
use of JPA 2.0 and it doesn't make sense to contin
On Oct 14, 2011, at 12:31 PM, Matthew Adams wrote:
On Fri, Oct 14, 2011 at 12:07 PM, Craig L Russell
wrote:
3. Other issues
https://issues.apache.org/jira/browse/JDO-696 applies to both
JDOHelper as
well as IUT if the PMF is constructed directly with a new
VendorPersistenceManagerFactor
[
https://issues.apache.org/jira/browse/JDO-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew T. Adams updated JDO-696:
-
Attachment: (was: JDO-684.src.patch)
> Throw on unrecognized javax.jdo options
> ---
Refactored & attached patch. FYI, refactoring has spec ramifications.
See https://issues.apache.org/jira/browse/JDO-696.
On Fri, Oct 14, 2011 at 2:42 PM, Craig L Russell
wrote:
>
> On Oct 14, 2011, at 12:31 PM, Matthew Adams wrote:
>
>> On Fri, Oct 14, 2011 at 12:07 PM, Craig L Russell
>> wrot
[
https://issues.apache.org/jira/browse/JDO-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew T. Adams updated JDO-696:
-
Attachment: JDO-684.src.patch
Updated patch: moved method assertOnlyKnownStandardProperties to JDOI
Hi Andy,
FYI, https://issues.apache.org/jira/browse/JDO-696 introduces an API
behavior change and specification change that affects you, but most of
the work has been done already.
The only thing you have to do is ensure that the properties given to
you contain no unknown standard JDO options/pro
On Oct 14, 2011, at 12:31 PM, Matthew Adams wrote:
On Fri, Oct 14, 2011 at 12:07 PM, Craig L Russell
wrote:
3. Other issues
https://issues.apache.org/jira/browse/JDO-696 applies to both
JDOHelper as
well as IUT if the PMF is constructed directly with a new
VendorPersistenceManagerFactor
> So now we have three different classes involved in the mix.
>
> Constants defines the strings.
> JDOHelper defines the Map containing those strings.
> JDOImplHelper defines the method to check the Map.
>
> How about Constants creates the public static immutable Map
> containing the strings, and l
19 matches
Mail list logo
