To tell you would have to look at the zip file. If it contains
/classes/META-INF/versions/9 you should be fine. To be sure look at the
log4j-api jar. It should contain
META-INF/versions/9/org/apache/logging/log4j/util/StackLocator.class
Ralph
> On Jun 18, 2017, at 10:23 PM, Gary Gregory wrote
Yup. I just tried and the failsafe plugin failed in the parent pom.
Ralph
> On Jun 18, 2017, at 11:31 PM, Ralph Goers wrote:
>
> As I recall plugins blow up when I have tried that.
>
> Ralph
>
>> On Jun 18, 2017, at 9:35 PM, Gary Gregory wrote:
>>
>> OK, thanks.
>>
>> I just made an update
As I recall plugins blow up when I have tried that.
Ralph
> On Jun 18, 2017, at 9:35 PM, Gary Gregory wrote:
>
> OK, thanks.
>
> I just made an updated to the POM to allow building to proceed a little
> further with Java 9 as the JDK. Has anyone managed to run a whole build on
> Java 9?
>
> G
When I build (with Java 8) I now see:
[INFO] --- maven-assembly-plugin:3.0.0:single (zip) @ log4j-api-java9 ---
[INFO] Reading assembly descriptor: src/assembly/java9.xml
*[ERROR] OS=Windows and the assembly descriptor contains a *nix-specific
root-relative-reference (starting with slash) /classes
OK, thanks.
I just made an updated to the POM to allow building to proceed a little
further with Java 9 as the JDK. Has anyone managed to run a whole build on
Java 9?
Gary
On Sun, Jun 18, 2017 at 5:24 PM, Ralph Goers
wrote:
> Log4j-perf, log4j-samples, log4j-distribution, log4j-core-its.
>
> R
Log4j-perf, log4j-samples, log4j-distribution, log4j-core-its.
Ralph
> On Jun 18, 2017, at 4:27 PM, Gary Gregory wrote:
>
> Hi,
>
> What modules are not supposed to make it to Maven Central?
>
> Gary
>
> On Sun, Jun 18, 2017 at 12:39 PM, Ralph Goers
> wrote:
>
>> I have modified the Java 9
Thanks - I didn’t notice I had left that lying around. I have deleted it.
Ralph
> On Jun 18, 2017, at 5:12 PM, Gary Gregory wrote:
>
> I am confused by the layout: there is a log4j-api-java9 folder inside
> the log4j-api-java9 folder?
>
> Gary
>
> On Sun, Jun 18, 2017 at 4:35 PM, Remko Popma
I am confused by the layout: there is a log4j-api-java9 folder inside
the log4j-api-java9 folder?
Gary
On Sun, Jun 18, 2017 at 4:35 PM, Remko Popma wrote:
> Ralph, thank you!!
> I just tried it and it works great. All I needed to do was tell IntelliJ
> IDEA to use Java 9 for the log4j-api-java9
[
https://issues.apache.org/jira/browse/LOG4J2-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory closed LOG4J2-1945.
Resolution: Fixed
In Git master already.
> Generate source jas for all test jars
> ---
[
https://issues.apache.org/jira/browse/LOG4J2-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053345#comment-16053345
]
ASF subversion and git services commented on LOG4J2-1945:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1945:
-
Description: Generate source jas for all test jars and publish them to our
Maven repositories. Cu
[
https://issues.apache.org/jira/browse/LOG4J2-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1945:
-
Description: Generate source jas for all test jars and publish them to our
Maven repositories. (
Gary Gregory created LOG4J2-1945:
Summary: Generate source jas for all test jars
Key: LOG4J2-1945
URL: https://issues.apache.org/jira/browse/LOG4J2-1945
Project: Log4j 2
Issue Type: New Featu
Ralph, thank you!!
I just tried it and it works great. All I needed to do was tell IntelliJ
IDEA to use Java 9 for the log4j-api-java9 module and it all just works in
the IDE again.
Great, thanks again!
Remko
On Mon, Jun 19, 2017 at 4:39 AM, Ralph Goers
wrote:
> I have modified the Java 9 sup
Hi,
What modules are not supposed to make it to Maven Central?
Gary
On Sun, Jun 18, 2017 at 12:39 PM, Ralph Goers
wrote:
> I have modified the Java 9 support yet again. I was having a problem with
> a Maven plugin I am building where the Maven annotation processor was
> failing because it was
I have modified the Java 9 support yet again. I was having a problem with a
Maven plugin I am building where the Maven annotation processor was failing
because it was finding a Java 9 class that it couldn’t read. To fix this I have
separated the Java 9 support to its own module and then am overl
[
https://issues.apache.org/jira/browse/LOG4J2-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053089#comment-16053089
]
ASF subversion and git services commented on LOG4J2-1874:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-1874.
-
Resolution: Fixed
Thank you for your patience.
Pull request #71, with some minor changes, has bee
[
https://issues.apache.org/jira/browse/LOG4J2-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053086#comment-16053086
]
ASF subversion and git services commented on LOG4J2-1874:
-
Commit
19 matches
Mail list logo
