Didn't the Maven team announce that they were copying a bunch of the Java extension API's out into their repository? Maybe now that Java is GPL? I can't recall where I heard it, but I seem to recall it. If true, it would mean that the stuff we normally had to download individually might be available in Maven's repository now.
Jake Quoting Curt Arnold <[EMAIL PROTECTED]>: > > On Jan 25, 2007, at 10:39 PM, Elias Ross wrote: > > > > > I have finally started to code, and I'm not too keen on downloading or > > locating the various 10 or so libraries to build Log4j. I propose > > we simply > > copy the appropiate .jar files for building into a "thirdparty" > > directory and > > include all the licenses, etc. This is what many other projects > > do, I don't > > know if there is some policy against it, but anything to lower the > > barrier of > > entry is a good thing. > > > > Many of the dependencies have licenses that prohibit distribution. > > > > Yes, I know there is a Maven build. I gave it a go, and even it > > doesn't work > > without having to manually download a few files. > > > > The files that are missing from the Maven repository are most likely > ones where the license restrictions could not be addressed. > > > I'd like to both simplify my life a little and maybe a few others. > > > > What do people think? > > > > I would not have any problems a patch that "bootstraps" the Ant build > from resources from the Maven repository. I would prefer to do that > than to pull them from the SVN. However, I do not think that you > could achieve a zero configuration build (at least on earlier JDK's) > due to the restrictions on some of the components. > > > > --------------------------------------------------------------------- > 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]
