> >> 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
Hi Patrick,
I asked the maven experts at Netbeans day around JavaOne and they
said that what works today is to define a separate project for each
compiler dependency (so in our case the 1.4-only code would be in a
separate project and the 1.5-code would be in a third project). I
said that
Hi Craig,
Any 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:
