Yeah, we probably need to change the package name to o.a.c.vfs2 and the artifactId to commons-vfs2. Or, go back the other way, as you suggest (provided it's backward compatible).
On Wed, Aug 19, 2009 at 10:45 AM, Ralph Goers<[email protected]> wrote: > The maven group id for 2.0 is currently org.apache.commons. It was > commons-vfs for VFS 1.0, so it would already be possible to have both jars > simultaneously. So if the package names are not changed then the pom needs > to be changed to use commons-vfs as the groupId before 2.0 is formally > released. > > Ralph > > On Aug 19, 2009, at 7:38 AM, James Carman wrote: > >> What about the maven2 group/artifact id? >> >> >> On Wed, Aug 19, 2009 at 10:34 AM, Ralph Goers<[email protected]> >> wrote: >>> >>> The packages haven't been changed so far. But this would definitely have >>> to >>> be considered whether we would want to take on the package renaming right >>> now. >>> >>> The minimum JDK for 1.0 was 1.3, although it isn't clear that that was >>> correct. The minimum JDK for 2.0 has already been changed to 1.4 since >>> some >>> of the code actually required that version to run. >>> >>> Ralph >>> >>> On Aug 19, 2009, at 7:24 AM, James Carman wrote: >>> >>>> Are they going to change the package name? >>>> >>>> On Wed, Aug 19, 2009 at 10:18 AM, Ralph >>>> Goers<[email protected]> >>>> wrote: >>>>> >>>>> Currently the minimum Java version for VFS 2.0 is 1.4. VFS 2.0 has not >>>>> been >>>>> released and the developers are considering making the minimum version >>>>> JDK >>>>> 5. We are interested in getting feedback from the community however >>>>> before >>>>> this change is made. So please respond with your thoughts on this. >>>>> >>>>> Ralph >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
