Hi, While they might help us as a one-time thing, this should become a standard part of our release process. Automation would be nice ;)
The older files under ASL 1.1 license do not need to be touched. Only releases made since last year need to have the 2.0 license, retro-fitting is prohibited. And this is not some strange bit of social engineering ;) On the contrary, I feel bad for having forgotten this... Yoav Shapira System Design and Management Fellow MIT Sloan School of Management Cambridge, MA [EMAIL PROTECTED] / [EMAIL PROTECTED] > -----Original Message----- > From: Curt Arnold [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 28, 2005 12:02 PM > To: Log4J Developers List > Subject: Re: Log4j 1.2.9 at ibiblio > > > On Jun 28, 2005, at 12:30 AM, Carlos Sanchez wrote: > > > Hi, > > > > I'm a maven PMC member and responsible of mantaining the maven repo at > > ibiblio. We're getting requests to upload the latest log4j 1.2.9. The > > point is that apache projects should use the apache java repo at > > www.apache.org/dist/java-repository (that it's synced to ibiblio), so > > could you put this jar there? > > (/www/www.apache.org/dist/java-repository/log4j/jars at > > people.apache.org) > > > > Thanks > > > > Carlos Sanchez > > > > The latest 1.2.x is 1.2.11 which was released last week. It is a > minor maintenance release which fixes a build issue which caused the > JMSAppender to be missing. (1.2.10 was recalled). > > I do have not objections, but I really have little idea of what is > being asked and could find very little in the way of documentation > for java-repository. The best I could find is similar responses from > other projects (Batik in particular) when they were asked to add > their jars. It would seem like a very strange piece of social > engineering, but I'm always a little leery. > > I looked at dist/java-repository/log4j, the license files are still > ASL 1.1 not 2.0. Should those be updated as well? I saw that there > were MD5 hashes, but didn't see any PGP signatures for jars in my > browsing. > > I assume that you could probably do the task yourself as you are as > or more likely to have write access to dist/java-repository than any > of the log4j committers. The sources are already in www.apache.org, > so you could extract the jars from the distributions in your shell > accound on cvs.apache.org. > > As far as I can gather, the following should be close (once for > log4j-1.2.9 and log4j-1.2.11 please) > > ssh -l username cvs.apache.org > tar -xvzf /www/www.apache.org/dist/logging/log4j/logging- > log4j-1.2.9.tar.gz logging-log4j-1.2.9/dist/lib/log4j-1.2.9.jar > cd logging-log4j-1.2.9/dist/lib > openssl md5 < log4j-1.2.9.jar > log4j-1.2.9.jar.md5 > cp log4j-1.2.9.jar* /www/www.apache.org/dist/java-repository/log4j/jars > > > p.s.: I having problems originating mail from my apache.org address. > I noticed that you weren't using yours either. Please let me know > off-list if you are having problems too. > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
BEGIN:VCARD VERSION:2.1 N:Shapira;Yoav FN:[EMAIL PROTECTED] ORG:MIT Sloan School of Management TITLE:System Design and Management Fellow URL;WORK:http://www.yoavshapira.com EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20050611T145830Z END:VCARD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
