Fix issues reported by checkstyle in api20 subproject
-
Key: JDO-353
URL: http://issues.apache.org/jira/browse/JDO-353
Project: JDO
Type: Improvement
Components: api20
Versions: JDO 2 rc1
Reporter: M
Hi,
This is clearly a bug, from your description. The reason it was
working before was a counterbalancing bug in JPOX?
Michelle, can you take a look at it?
Thanks,
Craig
On Mar 27, 2006, at 11:35 PM, Andy Jefferson wrote:
Some more information, having tried with Erik's recent changes to
Yes, I'll look into this.
-- Michelle
Craig L Russell wrote:
Hi,
This is clearly a bug, from your description. The reason it was
working before was a counterbalancing bug in JPOX?
Michelle, can you take a look at it?
Thanks,
Craig
On Mar 27, 2006, at 11:35 PM, Andy Jefferson wrote:
S
Hi,
configurations "schemaAttributeOrm.conf" (Mapping 5),
"schemaAttributePackage.conf" (Mapping 6), and
"schemaAttributeClass.conf" (Mapping 7) run test MakePersistent which
inherits from PersistenceManagerTest.
Class PersistentManagerTest implements localSetUp adding tear down
classes PCR
org.apache.jdo.tck.api.persistencemanager.lifecycle.MakePersistent may fail on
teardown
---
Key: JDO-354
URL: http://issues.apache.org/jira/browse/JDO-354
Project: JDO
Type: Bug
Co
[
http://issues.apache.org/jira/browse/JDO-354?page=comments#action_12372125 ]
Michelle Caisse commented on JDO-354:
-
Comment by Michael Watzek:
configurations "schemaAttributeOrm.conf" (Mapping 5),
"schemaAttributePackage.conf" (Mapping 6), and "schem
[ http://issues.apache.org/jira/browse/JDO-354?page=all ]
Michelle Caisse reassigned JDO-354:
---
Assign To: Michelle Caisse
> org.apache.jdo.tck.api.persistencemanager.lifecycle.MakePersistent may fail
> on teardown
> ---
[ http://issues.apache.org/jira/browse/JDO-353?page=all ]
Michael Bouschen updated JDO-353:
-
Attachment: JDO-353.patch
Please review the attached patch JDO-353.patch.
> Fix issues reported by checkstyle in api20 subproject
>
[
http://issues.apache.org/jira/browse/JDO-353?page=comments#action_12372149 ]
Craig Russell commented on JDO-353:
---
A few of the lines now or still exceed 80 characters. Can you run the
stlyecheck again with the new files?
These are the files I found whe
Hi Andy,
Thanks for the quick reply to this issue.
On Mar 27, 2006, at 10:30 PM, Andy Jefferson wrote:
Hi Craig,
I don't read the spec (as it currently is) to allow identity to
utilise
sequences. You have a sequence option for that.
My problem is that there are a couple of ways to use se
[ http://issues.apache.org/jira/browse/JDO-353?page=all ]
Michael Bouschen resolved JDO-353:
--
Resolution: Fixed
Checked in the fix.
Sende api20\src\java\javax\jdo\JDODetachedFieldAccessException.java
Sende api20\src\java\javax\jd
[ http://issues.apache.org/jira/browse/JDO-354?page=all ]
Michelle Caisse updated JDO-354:
Attachment: JDO-354.patch
This simple patch gives the following results with an otherwise clean build &
latest JPOX download:
[java] Total tests run: 1239. Fa
[ http://issues.apache.org/jira/browse/JDO-354?page=all ]
Michelle Caisse updated JDO-354:
Comment: was deleted
> org.apache.jdo.tck.api.persistencemanager.lifecycle.MakePersistent may fail
> on teardown
> ---
[
http://issues.apache.org/jira/browse/JDO-354?page=comments#action_12372161 ]
Michelle Caisse commented on JDO-354:
-
This simple patch gives the following results with an otherwise clean build &
latest JPOX download:
[java] Total tests run: 1239.
[
http://issues.apache.org/jira/browse/JDO-354?page=comments#action_12372169 ]
Craig Russell commented on JDO-354:
---
Two comments:
1. The patch looks good. I think this should solve the issue. Ok with me to
check it in.
2. I think the description in the
Javadogs,I'm planning on cutting the release branch for JDO 2.0 tomorrow. There are three open issues that I'm aware of:1. The test with persistent interfaces doesn't work yet; I believe that this is a JPOX bug that will be fixed without a new release of the API or TCK.2. The TCK only supports data
[ http://issues.apache.org/jira/browse/JDO-354?page=all ]
Michelle Caisse resolved JDO-354:
-
Resolution: Fixed
Fixed with revision 389639
> org.apache.jdo.tck.api.persistencemanager.lifecycle.MakePersistent may fail
> on teardown
> ---
Craig,
Does this mean there will be no more check-ins? Or will we just check
in to both trunk and release branch for the few remaining issues?
-- Michelle
Craig L Russell wrote:
Javadogs,
I'm planning on cutting the release branch for JDO 2.0 tomorrow. There
are three open issues that I'
If we do need checkins to the trunk after the branch is created (the branch is an svn activity that sends a message to jdo-commits alias) then they will need to be done to both the trunk and branch. Of course, there are some branch-only things (changing from SNAPSHOT to 2.0 in project.xml). But I d
I have JDO-293, which is dependent on JDO-273 finishing touches.
There's also JDO-64 that is still open. And JDO-349.
-- Michelle
Craig L Russell wrote:
If we do need checkins to the trunk after the branch is created (the
branch is an svn activity that sends a message to jdo-commits alias)
Hi Craig,
> Using both identity and sequence makes sense for schema generation
> where you want the identity strategy (JDO implementation doesn't
> generate key values) and automatic key generation using the sequence
> named (JDO implementation generates the trigger and stored procedure
> to us
Hi Andy,
On Mar 28, 2006, at 10:33 PM, Andy Jefferson wrote:
Hi Craig,
Using both identity and sequence makes sense for schema generation
where you want the identity strategy (JDO implementation doesn't
generate key values) and automatic key generation using the sequence
named (JDO implementa
Hi Craig,
> I've confirmed with the JDBC4 spec lead that you can retrieve the
> keys using getGeneratedKeys if you use this strategy.
Thanks. That's useful if targeting software at JDK 1.4 and above.
We're still trying to support 1.3 so when the JDK is 1.3x will likely stick to
our current met
23 matches
Mail list logo
