On 5/31/06, Craig L Russell <[EMAIL PROTECTED]> wrote:
Maven is pretty good at building, testing, and packaging for release
without a lot of manual intervention. I think we would need to create
a separate maven goal to repackage the jars into the final jar
distribution but maven allows you do cr
> >> Would it be ok to build three different jar files based on whether
> >> the target was 1.3, 1.4, or 1.5? Packaging the different jar files
> >> into one could be a post-build exercise.
> >> Or a specific build target that combined the three jar files.
> >>
> >> How is the source code structu
Maven is pretty good at building, testing, and packaging for release
without a lot of manual intervention. I think we would need to create
a separate maven goal to repackage the jars into the final jar
distribution but maven allows you do create pre- and post-goals to do
just what you need
For sure -- that would be simples, but I have to imagine (and could
be dreaming) that we can bend Maven to our will and have separate,
individually configured / built modules that can be rolled into a
single JAR file at the end.
That keeps the number of JARs from exploding (Maven's natural
tend
On May 30, 2006, at 5:27 PM, Patrick Linskey wrote:
Would it be ok to build three different jar files based on
whether the target was 1.3, 1.4, or 1.5? Packaging the
different jar files into one could be a post-build exercise.
Or a specific build target that combined the three jar files.
How i
> Would it be ok to build three different jar files based on
> whether the target was 1.3, 1.4, or 1.5? Packaging the
> different jar files into one could be a post-build exercise.
> Or a specific build target that combined the three jar files.
>
> How is the source code structured today?
That
further thoughts about maven and multiple language versions?
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 16, 2006 5:17 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: initial commit
I've been
rg
> Subject: Re: initial commit
>
> I've been told that "if you're already using maven 1, and it
> works, there's not much value in switching, but if you're
> starting a new project, you might as well use maven 2." by
> the maven mavens.
>
I've been told that "if you're already using maven 1, and it works,
there's not much value in switching, but if you're starting a new
project, you might as well use maven 2." by the maven mavens.
So I'd probably be in favor of maven 2 since we're starting from
scratch.
The question has c
Regarding Maven,
Are we considering using Maven 1, or Maven 2? The dependencies from Craig's
email work with Maven 2, but I'm just curious whether we have a consensus on
which version to use (if we go with Maven).
-Mike
On 5/15/06, Patrick Linskey <[EMAIL PROTECTED]> wrote:
> So, what is the
> So, what is the @nojavadoc concept? That these classes are so
> simple that javadoc would be meaningless?
That these clasess are things that are just noise in a javadoc release set.
-Patrick
___
Notice: This email message, to
scripts.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Sunday, May 14, 2006 10:31 PM
To: open-jpa-dev@incubator.apache.org
Cc: Abe White
Subject: Re: initial commit
Hi,
Good job!
With the new serp download bits
Patrick,
On 5/13/06, Patrick Linskey <[EMAIL PROTECTED]> wrote:
The code here should also be a good place to start to familiarize
yourselves with the Kodo code style. I've got an eclipse conf file for
it if anyone's interested.
Yes, I would be interested in your eclipse conf file. We use E
, 2006 10:31 PM
> To: open-jpa-dev@incubator.apache.org
> Cc: Abe White
> Subject: Re: initial commit
>
> Hi,
>
> Good job!
>
> With the new serp download bits, the project compiles ok
> under maven.
> All I had to do was to use the maven metadata files from
--
Patrick Linskey
BEA Systems, Inc.
-Original Message-
From: Abe White
Sent: Sunday, May 14, 2006 9:14 PM
To: Patrick Linskey
Subject: Re: initial commit
Can you push the serp changes back out to sf.net at some
point ple
EA Systems, Inc.
> -Original Message-
> From: Eddie O'Neil [mailto:[EMAIL PROTECTED]
> Sent: Sunday, May 14, 2006 2:15 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: initial commit
>
> Maven shouldn't have any trouble with the 1.5 language
>
Maven shouldn't have any trouble with the 1.5 language features;
I've switched from Ant to Maven2 for everything possible locally. To
configure Maven to compile with 1.5, just use the below to do
so.
FWIW, I'm totally +1 on Maven support and wish we had Beehive M2
enabled; it just makes thing
> I've tried to build the openjpa-lib but have one issue:
> ConstantPoolTable is not found. It's not in the serp library
> that I downloaded from sourceforge this morning. Are you
> using an unreleased version of serp perhaps?
Yep, we probably haven't synced back out to serp recently. Thanks f
> I noticed that all your .java files are marked as executable.
> This is a common problem with some Windows systems, but
> you're running MacOS, right?
Sadly, my corporate overlords have me on a Windows machine right now.
> Anyway, there's a web page describing the problem at http://
> db.apache
Hi Patrick,
I've tried to build the openjpa-lib but have one issue:
ConstantPoolTable is not found. It's not in the serp library that I
downloaded from sourceforge this morning. Are you using an unreleased
version of serp perhaps?
I easily enough defined a maven 1 project for this. If you
Hi Patrick,
I noticed that all your .java files are marked as executable. This is
a common problem with some Windows systems, but you're running MacOS,
right?
Anyway, there's a web page describing the problem at http://
db.apache.org/jdo/svn.html. Does this apply here?
I'm going to see i
21 matches
Mail list logo
