On Aug 28, 2006, at 10:14 AM, Marc Prud'hommeaux wrote:
If the snapshot deploy directory /x1/www/people.apache.org/repo/
m2-snapshot-repository/org/apache/openjpa/ is available from the
continuum server, I might be able to override the
snapshotRepository to deploy straight to that direct
If the snapshot deploy directory /x1/www/people.apache.org/repo/m2-
snapshot-repository/org/apache/openjpa/ is available from the
continuum server, I might be able to override the
snapshotRepository to deploy straight to that directly, in which
case we'd have automatic deployment of the s
Yep
An oversight by me. Thanks for pointing it out. I'll get the comments
(along with the follow up comments) in JIRA...
Craig L Russell wrote:
Hi Bryan,
As a matter of team communication, I'd like to see all comments
related to JIRA issues attached to the JIRAs themselves. That way w
Hi Bryan,
As a matter of team communication, I'd like to see all comments
related to JIRA issues attached to the JIRAs themselves. That way we
don't need to scour the archives to find JIRA-related comments.
Until a discussion results in a JIRA, email threads make sense.
Does this seem like
On Aug 24, 2006, at 12:46 PM, Marc Prud'hommeaux wrote:
David-
I added it in (that's the easy part). See http://
vmbuild.apache.org/continuum/servlet/continuum
That machine is terribly slow
I notice that there is both a "OpenJPA" and a "OpenJPA Project"
build configured in continuu
David-
I added it in (that's the easy part). See http://
vmbuild.apache.org/continuum/servlet/continuum
That machine is terribly slow
I notice that there is both a "OpenJPA" and a "OpenJPA Project" build
configured in continuum, and "OpenJPA" doesn't seem to actually be
building any
On Aug 23, 2006, at 4:20 PM, Bryan Noll wrote:
So... I saw that David created the following two JIRA's, so I
wanted to follow up on the thread.
http://issues.apache.org/jira/browse/OPENJPA-29
http://issues.apache.org/jira/browse/OPENJPA-30
Regarding OPENJPA-29:
openjpa-0.9.0-full.jar //
So... I saw that David created the following two JIRA's, so I wanted to
follow up on the thread.
http://issues.apache.org/jira/browse/OPENJPA-29
http://issues.apache.org/jira/browse/OPENJPA-30
Regarding OPENJPA-29:
openjpa-0.9.0-full.jar // contains all openjpa code, openjpa-*.jars
merged
On Aug 16, 2006, at 2:41 PM, Kevin Sutter wrote:
David,
Not sure if Confluence provides any additional functionality, but
OpenJPA
already has a wiki:
http://wiki.apache.org/incubator/openjpa/FrontPage?action=show
We could log this discussion on that wiki, right?
That's really why I'm ask
Hi David,
I guess this would be the place. There's no content yet. So I added a
pointer to the DistributionStrategy page but it didn't quite work.
I'm used to "the other wiki" and all you do there is type a page name
and the wiki creates a link to it. So I need to get used to Confluence!
David,
Not sure if Confluence provides any additional functionality, but OpenJPA
already has a wiki:
http://wiki.apache.org/incubator/openjpa/FrontPage?action=show
We could log this discussion on that wiki, right?
Kevin
On 8/16/06, David Blevins <[EMAIL PROTECTED]> wrote:
Speaking of wikis,
Speaking of wikis, I created a Confluence space in cwiki at Geir's
request some time ago. (http://cwiki.apache.org/confluence/display/
openjpa/Index)
Is that something you guys want to use?
-David
On Aug 15, 2006, at 8:08 PM, Craig L Russell wrote:
This discussion would be great to capture
This discussion would be great to capture on the wiki for the time
(not too far away) when we will actually package and ship some code.
Craig
On Aug 15, 2006, at 7:20 PM, David Blevins wrote:
On Aug 15, 2006, at 7:42 AM, Craig L Russell wrote:
On Aug 15, 2006, at 6:38 AM, Patrick Linskey
On Aug 15, 2006, at 7:42 AM, Craig L Russell wrote:
On Aug 15, 2006, at 6:38 AM, Patrick Linskey wrote:
Check out the Assembly plugin and it's predefined
"jar-with-dependencies" descriptor[1]. I'm pretty sure that
most people
using Maven will just have a runtime dependency on the core OpenJP
David-
But you might consider making
"org.apache.openjpa.conf.ProductDerivation" a directory that holds
files that contain the implementation class names. Then you can
have more than one in a jar.
That would solve the problem, but since there is no generic
classloader-based way of gett
On Aug 15, 2006, at 12:56 PM, Marc Prud'hommeaux wrote:
David-
are there any jars of our own that contain the same file in the
same place in the jar and those contents are different and need to
be merged together?
The only cases I know of are some of the files in services/. E.g.:
open
David-
are there any jars of our own that contain the same file in the
same place in the jar and those contents are different and need to
be merged together?
The only cases I know of are some of the files in services/. E.g.:
openjpa-jdbc/src/main/resources/META-INF/services/
org.apache.
> > So would it be easier to write a merge-manifest method or to
> > restrict manifest services with the same name to one of the build
> > modules?
>
> Sorry, I think I'm making things clear as mud :) I get the feeling
> we don't even have the issue Brett was mentioning. Aside from the
On Aug 15, 2006, at 11:40 AM, Craig L Russell wrote:
On Aug 15, 2006, at 11:06 AM, David Blevins wrote:
On Aug 15, 2006, at 6:37 AM, Patrick Linskey wrote:
Note that that will not merge anything you need in the META-INF
directory. It does do it for plexus components.xml files
though, so
On Aug 15, 2006, at 11:06 AM, David Blevins wrote:
On Aug 15, 2006, at 6:37 AM, Patrick Linskey wrote:
Note that that will not merge anything you need in the META-INF
directory. It does do it for plexus components.xml files though, so
maybe it's a good time to make that pluggable.
It'll d
On Aug 15, 2006, at 6:37 AM, Patrick Linskey wrote:
Note that that will not merge anything you need in the META-INF
directory. It does do it for plexus components.xml files though, so
maybe it's a good time to make that pluggable.
It'll definitely add the files from all the META-INF
director
On Aug 15, 2006, at 6:38 AM, Patrick Linskey wrote:
Check out the Assembly plugin and it's predefined
"jar-with-dependencies" descriptor[1]. I'm pretty sure that
most people
using Maven will just have a runtime dependency on the core OpenJPA
library and be done with it, but it's always nice for
> > Note that that will not merge anything you need in the META-INF
> > directory. It does do it for plexus components.xml files though, so
> > maybe it's a good time to make that pluggable.
> >
>
> It'll definitely add the files from all the META-INF
> directories into
> the resulting jar. I
> Check out the Assembly plugin and it's predefined
> "jar-with-dependencies" descriptor[1]. I'm pretty sure that
> most people
> using Maven will just have a runtime dependency on the core OpenJPA
> library and be done with it, but it's always nice for Ant users.
Exactly -- mvn users will use th
On Aug 14, 2006, at 10:11 PM, Brett Porter wrote:
On 15/08/06, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
On Mon, 2006-08-14 at 20:57 -0700, Patrick Linskey wrote:
> Does anyone know of existing mvn technology to merge resource
files? To
> easily assemble jars together?
Check out the Assem
On Aug 14, 2006, at 8:52 PM, Craig L Russell wrote:
Hi Marc,
On Aug 14, 2006, at 6:53 PM, Marc Prud'hommeaux wrote:
Patrick-
What's the difference between SNAPSHOT and -dev, in mavenese? I
wasn't
suggesting that what we talked about was better; just tossing
some more
fuel on the fire.
Note that that will not merge anything you need in the META-INF
directory. It does do it for plexus components.xml files though, so
maybe it's a good time to make that pluggable.
- Brett
On 15/08/06, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
On Mon, 2006-08-14 at 20:57 -0700, Patrick Linskey w
On Mon, 2006-08-14 at 20:57 -0700, Patrick Linskey wrote:
> > It might be good to run through the common dev scenarios in
> > detail to
> > see which model would work best for this project, since there are so
> > many sub-projects.
>
> Good point. I think that we should move to a model where
> It might be good to run through the common dev scenarios in
> detail to
> see which model would work best for this project, since there are so
> many sub-projects.
Good point. I think that we should move to a model where we have a project
that assembles a single unified jar (including mergi
Hi Marc,
On Aug 14, 2006, at 6:53 PM, Marc Prud'hommeaux wrote:
Patrick-
What's the difference between SNAPSHOT and -dev, in mavenese? I
wasn't
suggesting that what we talked about was better; just tossing some
more
fuel on the fire.
I don't know how well documented it is, but my unders
Patrick-
What's the difference between SNAPSHOT and -dev, in mavenese? I wasn't
suggesting that what we talked about was better; just tossing some
more
fuel on the fire.
I don't know how well documented it is, but my understanding is that
the -SNAPSHOT suffix (which, I believe, is automat
> > I spoke to Geir about this a bunch last week; he suggested we use a
> > number-dev nomenclature, so that it'd be clear that the current
> > build is
> > a dev build rather than a well-known numbered release. So,
> this would
> > mean we'd have 0.9.0-dev, meaning that there are
> differences
On Aug 14, 2006, at 2:47 PM, Patrick Linskey wrote:
I spoke to Geir about this a bunch last week; he suggested we use a
number-dev nomenclature, so that it'd be clear that the current
build is
a dev build rather than a well-known numbered release. So, this would
mean we'd have 0.9.0-dev, mean
I spoke to Geir about this a bunch last week; he suggested we use a
number-dev nomenclature, so that it'd be clear that the current build is
a dev build rather than a well-known numbered release. So, this would
mean we'd have 0.9.0-dev, meaning that there are differences since the
0.9.0 release its
34 matches
Mail list logo
