I have built the Java 9 code. Now I am copying the classes into the log4j-api
jar. They have to be placed at META-INF/versions/9. However, when I do this I
am getting an error from the Maven bundle plugin.
[INFO] --- maven-bundle-plugin:3.2.0:manifest (default) @ log4j-api ---
[ERROR] Manifest o
[
https://issues.apache.org/jira/browse/LOG4J2-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-1849.
-
Resolution: Fixed
Fix Version/s: 2.8.2
Fixed in commit c822338.
Please verify and close.
[
https://issues.apache.org/jira/browse/LOG4J2-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926483#comment-15926483
]
ASF subversion and git services commented on LOG4J2-1849:
-
Commit
I don’t see a problem with it. What is released will still run fine on Java 7.
It will just have some Java 9 components in the jar. The release is scheduled
for late July. I haven’t seen any indication that it will be pushed again. I
would rather be ready to take advantage of Java 9 on the day
It would be bad to require Java 9 to build the main project as long as Java
9 is not released.
On Wed, Mar 15, 2017 at 4:27 PM, Ralph Goers
wrote:
> I can’t change the JDK from JDK 1.7. The rest of the build must be
> compiled at Java 7 since that is what we support. I only want to compile
> the
[
https://issues.apache.org/jira/browse/LOG4J2-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926324#comment-15926324
]
shishir chaturvedi edited comment on LOG4J2-1849 at 3/15/17 3:57 PM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926324#comment-15926324
]
shishir chaturvedi edited comment on LOG4J2-1849 at 3/15/17 3:56 PM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksym Novoseltsev updated LOG4J2-1852:
---
Issue Type: Bug (was: Improvement)
> Plugins lookup by package is not compatible wit
Maksym Novoseltsev created LOG4J2-1852:
--
Summary: Plugins lookup by package is not compatible with Spring
Boot jar packaging
Key: LOG4J2-1852
URL: https://issues.apache.org/jira/browse/LOG4J2-1852
I can’t change the JDK from JDK 1.7. The rest of the build must be compiled at
Java 7 since that is what we support. I only want to compile the new classes
with Java 9.
Using a profile is a very good solution. We would have to run the build twice
but that would be OK. I will give that a try.
Sorry, no idea. A separate repo sounds cleaner, but I haven't spent as much
time as you thinking about this, so perhaps I'm wrong. It would be nice to
not require Java 9 unless you want to compile the StackWalker stuff...
On Thu, Mar 16, 2017 at 12:07 AM, Ralph Goers
wrote:
> I know how to impl
You can change the JDK from "JDK 1.7 (latest)" to one of the JDK 9
versions. Since there's no official release of 9 yet, they don't seem to
have a "JDK 9 (latest)" profile set up on Jenkins yet.
As for building this, the best solution I've seen so far basically involves
a bit of manual configurati
[
https://issues.apache.org/jira/browse/LOG4J2-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926338#comment-15926338
]
Matt Sicker commented on LOG4J2-1849:
-
It also appears that Jenkins runs in UTC or so
I know how to implement the StackWalker code but I don’t quite know how to get
it into the build. The main build needs to keep using Java 7 but of course the
StackWalker stuff needs to be compiled with Java 9. Technically, I know how I
could do that except I have no idea how it would work in Jen
[
https://issues.apache.org/jira/browse/LOG4J2-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926324#comment-15926324
]
shishir chaturvedi commented on LOG4J2-1849:
Matt, we are the blessed ones. :
[
https://issues.apache.org/jira/browse/LOG4J2-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926313#comment-15926313
]
Ralph Goers commented on LOG4J2-1849:
-
Neither is Arizona so I wouldn't see the probl
[
https://issues.apache.org/jira/browse/LOG4J2-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926282#comment-15926282
]
Matt Sicker commented on LOG4J2-1849:
-
I see that Japan isn't cursed with daylight sa
[
https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-1841:
Fix Version/s: 2.8.2
Setting fix version to prevent this issue from dropping below the horizon.
>
[
https://issues.apache.org/jira/browse/LOG4J2-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926127#comment-15926127
]
Remko Popma commented on LOG4J2-1849:
-
Thanks for the test. I will need to modify it
19 matches
Mail list logo
