I am still a bit lost. Maybe it's better if Matt does it?
On Thu, Mar 9, 2017 at 5:22 PM, Ralph Goers
wrote:
> The distribution zip and tarball contain all the artifacts that are being
> released - i.e. the jars. The Log4j distribution includes all the jars
> from all the sub projects. Obviousl
The distribution zip and tarball contain all the artifacts that are being
released - i.e. the jars. The Log4j distribution includes all the jars from
all the sub projects. Obviously, the Scala distribution will only contain the
Scala jars. So the assembly xml file needs to be modified to only
I am a bit lost here.
On Thu, Mar 9, 2017 at 4:56 PM, Mikael Ståldal
wrote:
> Change to what?
>
> On Thu, Mar 9, 2017 at 4:32 PM, Ralph Goers
> wrote:
>
>> 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 Sicke
Change to what?
On Thu, Mar 9, 2017 at 4:32 PM, Ralph Goers
wrote:
> 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 wrote:
>
> If you have time before the weekend, you could try copying over the
> log4j-dis
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 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 sh
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 wrote:
> Nice! Tell me if
Nice! Tell me if there is anything I can do to help out.
On Thu, Mar 9, 2017 at 5:07 AM, Matt Sicker 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 ar
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.
