Yeah, this is what we do in Beehive as well. My suggestion would be
to document the SVN configuration settings for OpenJPA committers in
something like DEVELOPING.txt at the top-level of the project. Over
time as new committers come on board, just make sure that they're
aware of this and use it
I went ahead and changed it to "enhance", just because I think it is
a little more descriptive than "openjpac". If anyone has any strong
feelings, I am open to switching it back, or changing it to something
else...
On Feb 1, 2007, at 3:51 PM, Dain Sundstrom wrote:
openjpac looks like "
[
https://issues.apache.org/jira/browse/OPENJPA-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469868
]
Kevin Sutter commented on OPENJPA-119:
--
Here's what I decided to do... I introduced a new boolean on the
deta
[
https://issues.apache.org/jira/browse/OPENJPA-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Sutter resolved OPENJPA-119.
--
Resolution: Fixed
Resolved.
> EntityManager.clear() should not implicitly invoke the flush op
Hi,
To date, almost all of the OpenJPA code uses single-line-style comments
inside method blocks, instead of multi-line comments. I prefer sticking
with this convention; my excuse is that it makes it easier to comment
out blocks of code during debugging, since you can use /*-style comments
when de
I'm okay with the single line convention. I'm flexible. I'll change these
two comment blocks if that's the direction we want to go.
On 2/2/07, Patrick Linskey <[EMAIL PROTECTED]> wrote:
Hi,
To date, almost all of the OpenJPA code uses single-line-style comments
inside method blocks, instead
interesting. I always did it the other way - use /* */ in code,
and // for commenting out blocks :)
On Feb 2, 2007, at 4:55 PM, Patrick Linskey wrote:
Hi,
To date, almost all of the OpenJPA code uses single-line-style
comments
inside method blocks, instead of multi-line comments. I prefer
For some reason, my reply seems to have gotten lost... I don't care which
way we do it. I'm flexible. If we decide to go with the single line
comments, then I'll change the two blocks that Patrick pointed out in the
original note.
P.S. I kind of side with Geir on this. I just use Eclipse to
Well, I don't use the block comment feature, and sometimes I even
have to use vi to comment out blocks.
So I guess I'd be happier with single-line comments a la
+// Check for null here because _brokers is a weak
reference collection
if ((broker != null) &&
Hi,
Is version 0.9.6 available on a Maven repo. I couldn't find it anywhere.
I am wanting to prepare a release for OpenJPA Maven plugin.
Cheers,
Rahul
Due to Apache Incubator policy the archives are only available via
the separate incubator repo at apache.
http://people.apache.org/repo/m2-incubating-repository
For example, the openjpa-all 0.9.6 jar is located here:
http://people.apache.org/repo/m2-incubating-repository/org/apache/
openjpa/
11 matches
Mail list logo
