The instructions for what will be in the zip and tar balls will have to change.

Ralph

> On Mar 9, 2017, at 8:01 AM, Matt Sicker <boa...@gmail.com> wrote:
> 
> If you have time before the weekend, you could try copying over the 
> log4j-distribution section from the main pom files. The "release" maven 
> profile should activate it I believe, so you should see the generated zips 
> and tarballs.
> 
> On 9 March 2017 at 03:01, Mikael Ståldal <mikael.stal...@magine.com 
> <mailto:mikael.stal...@magine.com>> wrote:
> Nice! Tell me if there is anything I can do to help out.
> 
> On Thu, Mar 9, 2017 at 5:07 AM, Matt Sicker <boa...@gmail.com 
> <mailto:boa...@gmail.com>> wrote:
> We've established that this will need to be released before we can officially 
> remove the equivalent modules from the main log4j repository (and release 
> cycle). Since the artifacts are no longer tied directly to log4j-api/core, 
> we've also agreed that it makes sense to version it separately as well. The 
> latest releases are 2.8.1, so the next version number proposed is 11.0. I dig 
> the Spinal Tap reference, so let's go for it.
> 
> I know that the source and binary distributions assemblies need to be ported 
> over in order to properly create a release candidate. The site is pretty bare 
> bones, and Ralph has mentioned that he should be able to take care of 
> integrating it into the main site. Otherwise, I'll be ready to start a 
> release candidate hopefully by this weekend.
> 
> -- 
> Matt Sicker <boa...@gmail.com <mailto:boa...@gmail.com>>
> 
> 
> 
> -- 
>  
> 
> Mikael Ståldal
> Senior software developer 
> 
> Magine TV
> mikael.stal...@magine.com <mailto:mikael.stal...@magine.com>    
> Grev Turegatan 3  | 114 46 Stockholm, Sweden  |   www.magine.com  
> <http://www.magine.com/>
> 
> Privileged and/or Confidential Information may be contained in this message. 
> If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not 
> copy or deliver this message to anyone. In such case, 
> you should destroy this message and kindly notify the sender by reply email.  
>  
> 
> 
> 
> -- 
> Matt Sicker <boa...@gmail.com <mailto:boa...@gmail.com>>

Reply via email to