Thanks for all the polishes! This vote ends without enough votes to pass.
I'll make an RC2 when I get a chance.
On 24 April 2017 at 04:24, Mikael Ståldal wrote:
> I have now clean-up the build instructions and added an exclusion for
> README.md so that the RAT check works.
>
> Ready for new rele
I have now clean-up the build instructions and added an exclusion for
README.md so that the RAT check works.
Ready for new release candidate.
On Sat, Apr 22, 2017 at 6:24 AM, Matt Sicker wrote:
> I'm not sure if the staging part is necessary technically since we're
> slicing up the site artifac
I'm not sure if the staging part is necessary technically since we're
slicing up the site artifacts anyways, but we do need some more specific
deployment instructions once that's figured out anyways.
I may start a second release candidate vote soon if this one isn't
sufficient. There are some wort
When I try "mvn site:stage-deploy -DstagingSiteURL=file:///$HOME/log4j-scala
"
it fails with:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.6:stage-deploy (default-cli)
on project log4j-scala: Missing site information in the distribution
management of the project Apa
When running RAT check, it fails with:
Unapproved licenses:
README.md
src/site/resources/js/jquery.min.js
I got rid of jquery issue by copying the RAT config in pom.xml from the
main project.
For some reason the RAT check does not complain about README.md in the main
repo. I cannot see why.
Added BUILDING.md to logging-log4j-scala repo.
On Fri, Apr 21, 2017 at 9:51 AM, Matt Sicker wrote:
> We still need two more votes, or one more after I add mine.
>
> On 21 April 2017 at 02:50, Mikael Ståldal
> wrote:
>
> > Older versions have the same issue. I haven't noticed before since I have
We still need two more votes, or one more after I add mine.
On 21 April 2017 at 02:50, Mikael Ståldal wrote:
> Older versions have the same issue. I haven't noticed before since I have
> already specified a dependency to log4j-api explicitly in build.sbt.
>
> So I guess we cannot do anything abo
Older versions have the same issue. I haven't noticed before since I have
already specified a dependency to log4j-api explicitly in build.sbt.
So I guess we cannot do anything about it. Let's move on with the release.
On Thu, Apr 20, 2017 at 8:25 PM, Matt Sicker wrote:
> Oh right, that's a diff
Oh right, that's a difference. Anyways, if this isn't working with SBT, how
does it work properly with older versions?
On Thu, Apr 20, 2017 at 02:38, Mikael Ståldal
wrote:
> You need to build it with Java 8.
>
> On Thu, Apr 20, 2017 at 2:15 AM, Matt Sicker wrote:
>
> > It's the same maven build
You need to build it with Java 8.
On Thu, Apr 20, 2017 at 2:15 AM, Matt Sicker wrote:
> It's the same maven build as log4j. Copying over the BUILDING.txt file
> would be a good idea, though.
>
> On 19 April 2017 at 11:52, Gary Gregory wrote:
>
> > Adding a BUILDING.txt to the root of the src zi
It's the same maven build as log4j. Copying over the BUILDING.txt file
would be a good idea, though.
On 19 April 2017 at 11:52, Gary Gregory wrote:
> Adding a BUILDING.txt to the root of the src zip would help. Especially,
> since there might (or not) be some scalaness to the build. Can you post
Adding a BUILDING.txt to the root of the src zip would help. Especially,
since there might (or not) be some scalaness to the build. Can you post
build help here if you need more VOTEs?
TY,
Gary
On Sat, Apr 15, 2017 at 10:53 AM, Matt Sicker wrote:
> Hello all, this is the first release candidate
OK, then
+1
On Tue, Apr 18, 2017 at 11:23 PM, Matt Sicker wrote:
> I've had the opposite problem at work before where a jar published from SBT
> wasn't giving transitive dependencies in Gradle. I blame Ivy.
>
> On Tue, Apr 18, 2017 at 02:25, Mikael Ståldal
> wrote:
>
> > I just tested this, an
I've had the opposite problem at work before where a jar published from SBT
wasn't giving transitive dependencies in Gradle. I blame Ivy.
On Tue, Apr 18, 2017 at 02:25, Mikael Ståldal
wrote:
> I just tested this, and it works. But I encountered one issue, when testing
> from an SBT project, the
I just tested this, and it works. But I encountered one issue, when testing
from an SBT project, the transitive dependency for log4j-api did not work,
I had to specify log4j-api explicitly. When testing from a Maven project,
it worked as expected. Have anyone else tried this from SBT? Is this a bug
As all PMC members should be subscribed to the dev list it is no longer
necessary to send release vote emails there.
Ralph
> On Apr 15, 2017, at 10:53 AM, Matt Sicker wrote:
>
> Hello all, this is the first release candidate for the first stand alone
> release of the log4j-api-scala modules u
Hello all, this is the first release candidate for the first stand alone
release of the log4j-api-scala modules under their own repository. In order
to decouple the version from the log4j-core version release train, we've
decided to jump right ahead to 11.
Staging repository:
https://repository.ap
17 matches
Mail list logo
