Thanks Marc, that was it. I should have realized as I had used the BEA JDO tools
before.
Phill
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On Behalf Of Marc
Prud'hommeaux
Sent: April 8, 2007 11:14 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Mapping tool
Or you can also logon to #maven IRC channel at irc.codehaus.org for
help.
Rahul
- Original Message -
From: "Michael Dick" <[EMAIL PROTECTED]>
To:
Cc: ;
Sent: Monday, April 09, 2007 1:56 PM
Subject: Re: [repo]
/www/people.apache.org/repo/m2-incubating-repository/
Actually it lo
Phill-
It sounds like you have the tool set up to use the openjpa-all-0.9.6-
incubating.jar, but you haven't added any of the other required
dependencies to the environment's classpath. You should put
everything (except the derby jar) in the lib/ directory of the
OpenJPA distribution in th
Hi Michael,
It looks like the right people are involved in fixing this.
Please do document the results of this discussion in the "How To Make
An OpenJPA Release".
Craig
On Apr 8, 2007, at 6:56 PM, Michael Dick wrote:
Actually it looks like the link David sent us has the information. The
r
Has anyone installed the mapping tool in the external eclipse tools? I am
getting an error and little info or ways to debug. I am trying to set it up so
that it would validate the current file. I would be happy with all files in
workspace or package. Really just to get it to run so I can get to the
Craig,
The procedure you describe is exactly how all Maven plugin releases (and
Maven 2.0.5 and 2.0.6) now go through.
The release plugin is configured to activate a "release" profile that
does a few things:
1) Turns on the remote-resources plugin which injects the license/notice
files in
On Monday 09 April 2007 08:12, Marc Prud'hommeaux wrote:
> I think that will generally work, but there is the issue of the
> "maven-metadata.xml" file in the parent directory (e.g., http://
> people.apache.org/repo/m2-incubating-repository/org/apache/openjpa/
> openjpa-project/maven-metadata.xml)
Actually it looks like the link David sent us has the information. The
release plugin provides a mechanism to deploy to a staging area.
The catch is that migrating from the staging area to a production
repository. A quick excerpt follows:
"Once the release is deemed fit for public consumption it
Hi Marc,
I'll plead ignorance on this. I'd like to have some feedback from the
maven incubator experts here. I'm copying the maven user list in case
they can shed some light.
Perhaps we need a new maven-incubator-release plugin that allows you
to deploy to a ~mikedd repository that has no
Craig-
I think that will generally work, but there is the issue of the
"maven-metadata.xml" file in the parent directory (e.g., http://
people.apache.org/repo/m2-incubating-repository/org/apache/openjpa/
openjpa-project/maven-metadata.xml) that lists all of the releases.
If you release to a
Other projects use the people.apache.org/~mikedd/xxx as the staging
repository while working through the release issues and votes.
I think you just need to tell maven where your repository is. Once
the vote to release passes the incubator IPMC, you can just move the
release artifacts from t
there's no automatic way to do it. You may leave the xml files as is
until the release is approved.
On 4/8/07, Michael Dick <[EMAIL PROTECTED]> wrote:
What is the best way to recover from erroneously published binaries?
Per Craig's email I should have waited to deploy until after the release
pa
Thanks David, I'll take a look.
On 4/8/07, David Jencks <[EMAIL PROTECTED]> wrote:
Won't help with cleanup but There's support for releasing to a
staging repo:
http://maven.apache.org/developers/release/releasing.html
I think this is new since the 0.9.6-incubating release.
thanks
david j
Won't help with cleanup but There's support for releasing to a
staging repo:
http://maven.apache.org/developers/release/releasing.html
I think this is new since the 0.9.6-incubating release.
thanks
david jencks
On Apr 8, 2007, at 4:46 PM, Marc Prud'hommeaux wrote:
Michael-
I'd just do:
Michael-
I'd just do:
rm -rvi /www/people.apache.org/repo/m2-incubating-repository/org/
apache/openjpa/*/0.9.7-incubating/
I had to do this a bunch of times with the 0.9.6-incubating release,
and maven seemed to recover gracefully from a version listed in maven-
metadata.xml being deleted
Craig-
Yeah, we ran into this issue with the last release, where we kept re-
building release candidates that were all labeled "0.9.6-incubating"
and were getting re-deployed to the official repository.
It would be easy enough to deploy to an alternate repository for
release approval (I th
What is the best way to recover from erroneously published binaries?
Per Craig's email I should have waited to deploy until after the release
passed a vote on the open-jpa-dev mailing list. I took a look at the maven
repository and I noticed that some of the xml files were updated with the
new ve
Hi Mike,
Something is wrong with the openjpa release process. Artifacts should
not be uploaded to the repository until they are voted out of the
project. Until they are ready, you should stage the proposed release,
sign it, and after you're sure it's ready to go, call for a review on
the
Hi Dain,
I haven't looked in detail at the life cycle of CMP beans in a couple
of years, but in general you can't simply keep the state of the
underlying Entities through the life cycle. CMP beans are pooled and
reused in transaction contexts and you have to load the state at
specific poi
Hi Dain,
On Apr 8, 2007, at 1:02 PM, Dain Sundstrom wrote:
On Apr 8, 2007, at 10:20 AM, Craig L Russell wrote:
Hi Dain,
On Apr 8, 2007, at 12:17 AM, Dain Sundstrom wrote:
Is it possible to reuse instances from transaction to transaction?
I would like to be able to create a bean in one tra
Thanks for the great info Patrick.
For now, I'm going to leave my implementation the way it is, without
instance reuse, and wait until someone complains loudly.
BTW in CMP there are a several places in the lifecycle of entities
that people like to reuse beans...
1) Beans are created and t
On Apr 8, 2007, at 10:20 AM, Craig L Russell wrote:
Hi Dain,
On Apr 8, 2007, at 12:17 AM, Dain Sundstrom wrote:
Is it possible to reuse instances from transaction to transaction?
I would like to be able to create a bean in one transaction,
detach it and reattach the same instance in a new
Hi Dain,
On Apr 8, 2007, at 12:17 AM, Dain Sundstrom wrote:
Is it possible to reuse instances from transaction to transaction?
I would like to be able to create a bean in one transaction, detach
it and reattach the same instance in a new transaction. My goal
here is specifically to reuse
Hi,
The easy way to do this is with extended persistence contexts. In an
extended persistence context, your working set of objects lasts for the
duration of the entity manager, not the transaction.
In a JTA environment, the container is supposed to set things up so that
EMs are transactional by d
Is it possible to reuse instances from transaction to transaction?
I would like to be able to create a bean in one transaction, detach
it and reattach the same instance in a new transaction. My goal here
is specifically to reuse instances across transactions because they
have a very expens
25 matches
Mail list logo
