Xavier Hanin wrote:
On 11/13/06, easyproglife <[EMAIL PROTECTED]> wrote:
Xavier,
Changing packages names IMO is a major change. I don't think 1.5 is a
good
candidate for such a version.
IMO, you should start from ivy 2.0 with apache package names.
On one hand I agree, 2.0 would better reflect the changes of package names
and the refactorings. On the other hand, a 2.0 with no major new feature
would not necessarily be well understood. Anyway, I have no strong opinion
on the subject, but Ivy 1.4 already break some code at API level, the main
difference here is that it would break all code :-)
well, you could make the package renaming the 2.0 milestone. A lot of
projects, commercial and OSS have trouble at v2.0, as its the
uncontrolled feature edition. In Apache, Axis 2.0 is a case in point
(though its really Apache SOAP 3.0), and Ant has never got to a 2.0
release because it got so controversial.
That way, fixes to previous (backwards compatible) version would still be
able to be done on ivy 1.x branch.
I know you are going to tell me that no more changes are planned on
1.xbranch but from my experience in software development IT WILL BE!
(keep my
words :))
What I do not see is how could a new version with fr.jayasoft packages be
done? AFAIK nobody has the right to do so except jayasoft, and jayasoft
won't. Now that we are incubating on Apache, we should try to make a new
version with Apache package names as soon as possible, with only a small
set
of changes, so that "1.x" developments could be made on the new apache
stream.
I think you need to keep the old package around with a copy of the
antlib (it can relay to the new antlib) so that old build files load it.
So the jayasoft package would be empty but for the antlib declaration.
