For "affects" versions, this should be released versions. So in this
case, "affects" would be 1.2.0 (released) and "fixed" is properly
identified as 1.3.0 (not released). And the trunk patch would be
identified as fixed in 2.0.0.
Craig
On Jan 30, 2009, at 10:18 AM, Donald Woods (JIRA) wrot
Hi David,
I don't know if you are allowed to see it, but here is the list of all
workflows implemented by Apache JIRA:
https://issues.apache.org/jira/secure/admin/ViewWorkflowSchemes.jspa
I didn't notice it until now, but the only projects using the Geronimo
workflow are
DayTrader
GBuil
On Jan 30, 2009, at 4:54 PM, Craig L Russell wrote:
Looking at JIRA, the Geronimo workflow implements a Review-Then-
Commit workflow, which isn't what we want.
Somethings wrong here we haven't had review-then-commit for a long
time and I don't think jira was enforcing it.
The only
On Jan 30, 2009, at 2:00 PM, Donald Woods wrote:
Any updates on item (iii)? Can we just include the notice for EA-1
and revisit for the next release?
My interpretation of Geir's response is that we can't distribute stuff
with this restriction, so no, we have to wait until the conditions a
Looking at JIRA, the Geronimo workflow implements a Review-Then-Commit
workflow, which isn't what we want.
The only suitable workflow seems to be no-reopen-closed, patch-avail
workflow that, as its name suggests, makes two changes to the standard
workflow:
It does not permit closed bugs t
[
https://issues.apache.org/jira/browse/OPENJPA-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669072#action_12669072
]
Fay Wang commented on OPENJPA-870:
--
Thank you, Pinaki, for pointing out this. OrphanRemov
Hi,
1. Set
2. Send the query and the parameters being set.
--
View this message in context:
http://n2.nabble.com/snapshot-build-failing..-tp2246748p2247614.html
Sent from the OpenJPA Developers mailing list archive at Nabble.com.
That's probably it. Sadly I don't appear to have sufficient karma to change
the schemes. Craig or Kevin do either of you have the proper authority?
-mike
On Fri, Jan 30, 2009 at 4:22 PM, Donald Woods wrote:
> Might be because you're using the Default Issue Type Schema instead of the
> Apache De
[
https://issues.apache.org/jira/browse/OPENJPA-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669055#action_12669055
]
Fernando commented on OPENJPA-886:
--
Catalina Wei commented that the stacktrace looked to
Might be because you're using the Default Issue Type Schema instead of
the Apache Default Schema
-Donald
Michael Dick wrote:
I've thought that having a patch available field / phase / whatever would be
helpful.
Any ideas how / where we go to add it?
-mike
On Fri, Jan 30, 2009 at 3:48
thank you. I have a bug filed:
https://issues.apache.org/jira/browse/OPENJPA-886
:) :)
Michael Dick wrote:
Please do open a JIRA issue, even if it is a typo we need to add a testcase
for your scenario.
If there's anything you can put in the JIRA to help us reproduce the problem
it'll be gre
Certain query failing after svn:739123
--
Key: OPENJPA-886
URL: https://issues.apache.org/jira/browse/OPENJPA-886
Project: OpenJPA
Issue Type: Bug
Components: kernel
Affects Versions: 2.0.0
[
https://issues.apache.org/jira/browse/OPENJPA-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick resolved OPENJPA-882.
--
Resolution: Fixed
Thanks for the patch Donald!
> Upgrade to latest Geronimo Spec releases
> -
Support clear methods on EntityManager, including new CascadeType.CLEAR
Key: OPENJPA-885
URL: https://issues.apache.org/jira/browse/OPENJPA-885
Project: OpenJPA
Issue
Please do open a JIRA issue, even if it is a typo we need to add a testcase
for your scenario.
If there's anything you can put in the JIRA to help us reproduce the problem
it'll be greatly appreciated..
Thanks,
-mike
On Fri, Jan 30, 2009 at 3:59 PM, Fernando Padilla wrote:
> So the code start
I've thought that having a patch available field / phase / whatever would be
helpful.
Any ideas how / where we go to add it?
-mike
On Fri, Jan 30, 2009 at 3:48 PM, Donald Woods wrote:
> I have attached patches to both JIRAs and unassigned them from me, but
> thought I'd drop a note to everyone
Any updates on item (iii)? Can we just include the notice for EA-1 and
revisit for the next release?
-Donald
David Jencks wrote:
Looks like a problem.
I sent a note to legal-discuss about (iii).
I'll work on setting up a new release candidate.
thanks
david jencks
On Jan 29, 2009, at 7:4
So the code starts to fail at svn: 739123
Should I open a bug?? Or will ppoddar chime in, maybe there was a typo
in this large checkin.
r739123 | ppoddar | 2009-01-29 17:27:35 -0800 (Thu, 29 Jan 2009) | 1line
Changed paths:
M
/openjpa/trunk/openjpa-jdbc/src/main/java/org/apache/openjpa/j
I have attached patches to both JIRAs and unassigned them from me, but
thought I'd drop a note to everyone as there is no "Patch Available"
field like we used in Geronimo to denote JIRAs from contributors that
were ready for review.
-Donald
[
https://issues.apache.org/jira/browse/OPENJPA-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods reassigned OPENJPA-772:
Assignee: (was: Donald Woods)
Unassigning from me, so a committer can review the patch
[
https://issues.apache.org/jira/browse/OPENJPA-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-772:
-
Attachment: OPENJPA-772-trunk.patch
OPENJPA-772-branches13x.patch
Updated patche
[
https://issues.apache.org/jira/browse/OPENJPA-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on OPENJPA-772 stopped by Donald Woods.
> Proper maven pluginManagement and use ianal-maven-plugin for enforcing legal
> files
> --
[
https://issues.apache.org/jira/browse/OPENJPA-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-772:
-
Attachment: OPENJPA-772-branches12x.patch
OPENJPA-772-branches11x.patch
Hi Fernando,
If it is a JPQL query string, the stack trace should show JDBCStoreQuery. I
could be wrong about that.
Do you know the JPQL query string in your app that caused the following
generated SQL:
SELECT t0.JDOID, t0.CREATETIME, t0.BRACKET_JDOID, t0.GROUP0,
t0.USER_JDOID
FROM BRACKET
but my code is expecting to build JPQL queries. Could the api changed
some how so that it's now building Native Queries, while it should be
using JPQL??
catalina wei wrote:
Hi Fernando,
From the stack trace, it looks to me the parameters are for a native SQL.
We may have introduced problems
the thing is, that it's not a native sql.. it's jpql..
I did take it back to before 736881 and it's working. I'm trying to get
our developers that build, after that I'll try to narrow down which
revision breaks it.
catalina wei wrote:
Hi Fernando,
From the stack trace, it looks to me the
[
https://issues.apache.org/jira/browse/OPENJPA-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669012#action_12669012
]
Pinaki Poddar commented on OPENJPA-703:
---
This commit introduces few changes that may
[
https://issues.apache.org/jira/browse/OPENJPA-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669008#action_12669008
]
Jeremy Bauer commented on OPENJPA-849:
--
Thanks for submitting a revised patch and nic
Hi Fernando,
>From the stack trace, it looks to me the parameters are for a native SQL.
We may have introduced problems in handling parameters for native queries.
Could you help us isolating the problem ?
Could you extract svn revision r738940 and see if that commit introduced the
problem ?
If po
So.. we came in today and our app has stopped working. Simple queries
that worked yesterday are not working today. Anyone having this issue?
Any ideas before I have to start to figure out which commit caused this??
We have two entities, Bracketeer and User.
@Entity
public class Bracketeer e
[
https://issues.apache.org/jira/browse/OPENJPA-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-772:
-
Attachment: (was: OPENJPA-772-trunk.patch)
> Proper maven pluginManagement and use ianal-mav
[
https://issues.apache.org/jira/browse/OPENJPA-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-772:
-
Attachment: (was: OPENJPA-772-branches12x.patch)
> Proper maven pluginManagement and use ian
[
https://issues.apache.org/jira/browse/OPENJPA-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-772:
-
Attachment: (was: OPENJPA-772-branches10x.patch)
> Proper maven pluginManagement and use ian
[
https://issues.apache.org/jira/browse/OPENJPA-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-772:
-
Attachment: (was: OPENJPA-772-branches13x.patch)
> Proper maven pluginManagement and use ian
Hi Jeremy,
Thank you for reviewing the work. Really helps.
1. Few tests are included that performs a performance comparison
with/without cache and asserts any performance regression in terms of
execution time. Details are in:
org.apache.openjpa.persistence.jdbc.sqlcache.TestPreparedQu
[
https://issues.apache.org/jira/browse/OPENJPA-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-882:
-
Fix Version/s: 1.3.0
Affects Version/s: 1.3.0
> Upgrade to latest Geronimo Spec releases
Nice to see you have started to contribute already. We are happy to
have you engaged in OpenJPA.
Thanks,
Craig
On Jan 30, 2009, at 8:19 AM, Tim McConnell wrote:
Great, thanks Craig.
Craig L Russell wrote:
Granted. Welcome aboard.
Craig
On Jan 29, 2009, at 9:20 PM, Tim McConnell wrote:
[
https://issues.apache.org/jira/browse/OPENJPA-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-882:
-
Attachment: OPENJPA-882-branches13x.patch
Patch to upgrade to the latest Geronimo Specs for bran
[
https://issues.apache.org/jira/browse/OPENJPA-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-772:
-
Attachment: OPENJPA-772-branches13x.patch
Patch for branches/1.3.x at Rev738952.
> Proper maven
Hi Pinaki,
This is a very signficant change and it essentially replaces the former
QuerySQLCache. Your design looks very solid and fairly nonintrusive - which
is a major feat considering the complexity of this undertaking.
I reviewed the JIRA and expected to see some performance measurements
sho
[
https://issues.apache.org/jira/browse/OPENJPA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668911#action_12668911
]
Michael Dick commented on OPENJPA-881:
--
Hi Milosz,
I remember the conversation. All
[
https://issues.apache.org/jira/browse/OPENJPA-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell updated OPENJPA-770:
--
Assignee: Tim McConnell
> Use annotations instead of excluding tests in pom.xml
>
Great, thanks Craig.
Craig L Russell wrote:
Granted. Welcome aboard.
Craig
On Jan 29, 2009, at 9:20 PM, Tim McConnell wrote:
Hi, I'm a committer and a PMC member of the Apache Geronimo project,
and would also like to request Contributor rights to OpenJPA JIRAs so
that I can assign some
[
https://issues.apache.org/jira/browse/OPENJPA-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on OPENJPA-882 stopped by Donald Woods.
> Upgrade to latest Geronimo Spec releases
>
>
> Key: OPENJPA-882
>
[
https://issues.apache.org/jira/browse/OPENJPA-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods reassigned OPENJPA-882:
Assignee: (was: Donald Woods)
Ready for a committer to review and commit.
> Upgrade t
[
https://issues.apache.org/jira/browse/OPENJPA-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-882:
-
Attachment: OPENJPA-882-trunk.patch
Patch for trunk (Rev739297) to upgrade to latest Geronimo JM
[
https://issues.apache.org/jira/browse/OPENJPA-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on OPENJPA-772 started by Donald Woods.
> Proper maven pluginManagement and use ianal-maven-plugin for enforcing legal
> files
> --
[
https://issues.apache.org/jira/browse/OPENJPA-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on OPENJPA-882 started by Donald Woods.
> Upgrade to latest Geronimo Spec releases
>
>
> Key: OPENJPA-882
>
Hi Abe,
Along these lines, have you looked at OPENJPA-767 (
https://issues.apache.org/jira/browse/OPENJPA-767)? I had created a sandbox
for this experimentation some time back. I had come across this one issue
with using the proper classloader when loading our OpenJPA runtime in an
OSGi environme
[
https://issues.apache.org/jira/browse/OPENJPA-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milosz Tylenda updated OPENJPA-884:
---
Attachment: OPENJPA-884.patch
The patch fixes the logging issue and also corrects a few typo
Logging oversight in DB2Dictionary
--
Key: OPENJPA-884
URL: https://issues.apache.org/jira/browse/OPENJPA-884
Project: OpenJPA
Issue Type: Bug
Components: logging
Affects Versions: 1.2.0, 1.2.1,
[
https://issues.apache.org/jira/browse/OPENJPA-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milosz Tylenda updated OPENJPA-883:
---
Attachment: OPENJPA-883.patch
The patch brings javadoc and the manual up to date.
> Documen
Documentation is out of date for some MySQLDictionary properties
Key: OPENJPA-883
URL: https://issues.apache.org/jira/browse/OPENJPA-883
Project: OpenJPA
Issue Type: Bug
Setting MaxEmbeddedBlobSize=-1 did the trick. I was able to submit a 60K,
and 3.84M byte stream.
Thanks!
--
View this message in context:
http://n2.nabble.com/-jira--Created%3A-%28OPENJPA-526%29-Insert-text-more-than-4K-bytes-to-Clob-column-causes-SQLException%3A-Exhausted-Resultset-tp217177p2
[
https://issues.apache.org/jira/browse/OPENJPA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668836#action_12668836
]
Milosz Tylenda commented on OPENJPA-881:
Mike, we have once discussed it here [1],
55 matches
Mail list logo
