It might still be easier to have cayenne-core and cayenne-jdk1.[x+1]
at all times. That avoids us having to move 99% of the code to a new
project and update all the maven paths, plus all the Confluence docs
every time a JDK update is required.
Although I guess with the right svn commands the history of all the
files will be preserved however we move things around, so it
shouldn't matter too much.
Ari
On 24/10/2007, at 5:39 PM, Andrus Adamchik wrote:
I think no - somehow I feel there will be "cayenne-jdk1.6-
unpublished" in a not so distant future.
Andrus
On Oct 24, 2007, at 10:28 AM, Aristedes Maniatis wrote:
On 24/10/2007, at 2:15 AM, Kevin Menard wrote:
It's to differentiate between assemblies that are published as
JARs and
those that are used simply to build larger assemblies that are
published as
JARs.
Now that 1.4 and 1.5 are being merged, do we want to rename that
project cayenne-core?
Ari
-------------------------->
Aristedes Maniatis
phone +61 2 9660 9700
PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8
-------------------------->
Aristedes Maniatis
phone +61 2 9660 9700
PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8
