Re: Wrong Exports and Automatic Module Name

2018-08-09 Thread Ralph Goers 
Is this related to 
https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8208269? 


Ralph

> On Aug 9, 2018, at 2:08 PM, Sverre Moe  wrote:
> 
> still no solution
> 
> I have even tried with latest snapshots of JDK 11 and JDK 12, same problem.
> 
> Den tor. 28. jun. 2018 kl. 00:07 skrev Sverre Moe :
> 
>> Are there any known problems with the javadoc tool and log4j automatic
>> module?
>> 
>> Running javadoc when having a requires org.apache.logging.log4j fail
>> as it cannot find the module.
>> 
>> I have done the same as I do for compile, adding all jars on classpath
>> to the modulepath, then clearing the classpath. Compile works fine.
>> 
>> djviking@machine:~/workspace/movies> /usr/java/jdk-10.0.1/bin/javadoc
>> --class-path '' --module-path
>> 
>> '/home/djviking/workspace/movies/build/classes/java/main:/home/djviking/workspace/movies/build/resources/main:/home/djviking/.gradle/caches/modules-2/files-2.1/org.controlsfx/controlsfx/9.0.0/8e009b653a2a6eb3336016ad314c040e72395914/controlsfx-9.0.0.jar:/home/djviking/.gradle/caches/modules-2/files-2.1/com.jfoenix/jfoenix/9.0.4/b630dd9c840a8d4610a6f2f38706e21eddfebcd8/jfoenix-9.0.4.jar:/home/djviking/.gradle/caches/modules-2/files-2.1/org.jfxtras/jfxtras-controls/9.0-r1/125ff6b0e22dcd7c9471dd0d849a2f4254b2ad84/jfxtras-controls-9.0-r1.jar:/home/djviking/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-core/2.11.0/e6b751e02120c08702d98750f6a80bc25343b7f5/log4j-core-2.11.0.jar:/home/djviking/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-api/2.11.0/bede79a3f150711634a3047985517431bf6499f2/log4j-api-2.11.0.jar:/home/djviking/.gradle/caches/modules-2/files-2.1/com.lmax/disruptor/3.3.7/8549fdcbda5d64db98871e64a4cd0045611686d1/disruptor-3.3.7.jar:/home/djviking/.gradle/caches/modules-2/files-2.1/org.jfxtras/jfxtras-common/9.0-r1/db8dbe26d4a41643e46320a1ec9ac193efc59c64/jfxtras-common-9.0-r1.jar:/home/djviking/.gradle/caches/modules-2/files-2.1/org.jfxtras/jfxtras-fxml/9.0-r1/dfd376482bee9a70532f35f97881a8d7785e1e02/jfxtras-fxml-9.0-r1.jar'
>> -d '/home/djviking/workspace/movies/build/docs/javadoc' -doctitle
>> 'movies 1.0-SNAPSHOT-SNAPSHOT API' -html5 -verbose -windowtitle
>> 'movies 1.0-SNAPSHOT-SNAPSHOT API'
>> 
>> '/home/djviking/workspace/movies/src/main/java/no/smeaworks/movies/MoviesController.java'
>> 
>> '/home/djviking/workspace/movies/src/main/java/no/smeaworks/movies/MoviesApplication.java'
>> '/home/djviking/workspace/movies/src/main/java/module-info.java'
>> Loading source file
>> 
>> /home/djviking/workspace/movies/src/main/java/no/smeaworks/movies/MoviesController.java...
>> [parsing started
>> 
>> SimpleFileObject[/home/djviking/workspace/movies/src/main/java/no/smeaworks/movies/MoviesController.java]]
>> [parsing completed 11ms]
>> Loading source file
>> 
>> /home/djviking/workspace/movies/src/main/java/no/smeaworks/movies/MoviesApplication.java...
>> [parsing started
>> 
>> SimpleFileObject[/home/djviking/workspace/movies/src/main/java/no/smeaworks/movies/MoviesApplication.java]]
>> [parsing completed 3ms]
>> Loading source file
>> /home/djviking/workspace/movies/src/main/java/module-info.java...
>> /home/djviking/workspace/movies/src/main/java/module-info.java:18:
>> error: module not found: org.apache.logging.log4j
>>requires org.apache.logging.log4j;
>>   ^
>> [parsing started
>> 
>> SimpleFileObject[/home/djviking/workspace/movies/src/main/java/module-info.java]]
>> [parsing completed 1ms]
>> [loading /modules/javafx.controls/module-info.class]
>> [loading /modules/javafx.graphics/module-info.class]
>> [loading /modules/javafx.base/module-info.class]
>> [loading /modules/java.desktop/module-info.class]
>> [loading /modules/java.xml/module-info.class]
>> [loading /modules/java.base/module-info.class]
>> [loading /modules/java.datatransfer/module-info.class]
>> [loading /modules/java.prefs/module-info.class]
>> [loading /modules/javafx.fxml/module-info.class]
>> [loading /modules/java.scripting/module-info.class]
>> [loading /modules/java.logging/module-info.class]
>> [loading /modules/javafx.web/module-info.class]
>> [loading /modules/jdk.jsobject/module-info.class]
>> [loading /modules/jdk.xml.dom/module-info.class]
>> [loading /modules/javafx.media/module-info.class]
>> [loading
>> /home/djviking/.gradle/caches/modules-2/files-2.1/org.jfxtras/jfxtras-controls/9.0-r1/125ff6b0e22dcd7c9471dd0d849a2f4254b2ad84/jfxtras-controls-9.0-r1.jar(/module-info.class)]
>> [loading
>> /home/djviking/.gradle/caches/modules-2/files-2.1/org.jfxtras/jfxtras-common/9.0-r1/db8dbe26d4a41643e46320a1ec9ac193efc59c64/jfxtras-common-9.0-r1.jar(/module-info.class)]
>> [loading
>> /home/djviking/.gradle/caches/modules-2/files-2.1/org.jfxtras/jfxtras-fxml/9.0-r1/dfd376482bee9a70532f35f97881a8d7785e1e02/jfxtras-fxml-9.0-r1.jar(/module-info.class)]
>> [loading
>>

Re: Lilith 8.2.0 has been released!

2018-08-09 Thread Ray Tayek 

On 8/9/2018 4:30 AM, Jörn Huxhorn wrote:

This version of Lilith demands ...


hi, using java 10 and trying to open one of my log files (please see 
below). lilith complains that it is not a valid log file.


also, i got some warnings.

any pointers will be appreciated.

thanks


D:\ray\dev\conradapps\rabbit2>java -jar D:/dev/lilith-8.2.0/lib/lilith.jar
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
org.codehaus.groovy.vmplugin.v7.Java7$1 (f
ile:/D:/dev/lilith-8.2.0/lib/groovy-2.5.1.jar) to constructor 
java.lang.invoke.M

ethodHandles$Lookup(java.lang.Class,int)
WARNING: Please consider reporting this to the maintainers of 
org.codehaus.groov

y.vmplugin.v7.Java7$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflect

ive access operations
WARNING: All illegal access operations will be denied in a future release




    Aug 9, 2018 1:58:31 PM
    1533848311326
    663
    xyzzy
    INFO
    p.Main
    loop
    1
    added socket handler to: 192.168.1.8


-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org

Re: Wrong Exports and Automatic Module Name

2018-08-09 Thread Sverre Moe 
still no solution

I have even tried with latest snapshots of JDK 11 and JDK 12, same problem.

Den tor. 28. jun. 2018 kl. 00:07 skrev Sverre Moe :

> Are there any known problems with the javadoc tool and log4j automatic
> module?
>
> Running javadoc when having a requires org.apache.logging.log4j fail
> as it cannot find the module.
>
> I have done the same as I do for compile, adding all jars on classpath
> to the modulepath, then clearing the classpath. Compile works fine.
>
> djviking@machine:~/workspace/movies> /usr/java/jdk-10.0.1/bin/javadoc
> --class-path '' --module-path
>
> '/home/djviking/workspace/movies/build/classes/java/main:/home/djviking/workspace/movies/build/resources/main:/home/djviking/.gradle/caches/modules-2/files-2.1/org.controlsfx/controlsfx/9.0.0/8e009b653a2a6eb3336016ad314c040e72395914/controlsfx-9.0.0.jar:/home/djviking/.gradle/caches/modules-2/files-2.1/com.jfoenix/jfoenix/9.0.4/b630dd9c840a8d4610a6f2f38706e21eddfebcd8/jfoenix-9.0.4.jar:/home/djviking/.gradle/caches/modules-2/files-2.1/org.jfxtras/jfxtras-controls/9.0-r1/125ff6b0e22dcd7c9471dd0d849a2f4254b2ad84/jfxtras-controls-9.0-r1.jar:/home/djviking/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-core/2.11.0/e6b751e02120c08702d98750f6a80bc25343b7f5/log4j-core-2.11.0.jar:/home/djviking/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-api/2.11.0/bede79a3f150711634a3047985517431bf6499f2/log4j-api-2.11.0.jar:/home/djviking/.gradle/caches/modules-2/files-2.1/com.lmax/disruptor/3.3.7/8549fdcbda5d64db98871e64a4cd0045611686d1/disruptor-3.3.7.jar:/home/djviking/.gradle/caches/modules-2/files-2.1/org.jfxtras/jfxtras-common/9.0-r1/db8dbe26d4a41643e46320a1ec9ac193efc59c64/jfxtras-common-9.0-r1.jar:/home/djviking/.gradle/caches/modules-2/files-2.1/org.jfxtras/jfxtras-fxml/9.0-r1/dfd376482bee9a70532f35f97881a8d7785e1e02/jfxtras-fxml-9.0-r1.jar'
> -d '/home/djviking/workspace/movies/build/docs/javadoc' -doctitle
> 'movies 1.0-SNAPSHOT-SNAPSHOT API' -html5 -verbose -windowtitle
> 'movies 1.0-SNAPSHOT-SNAPSHOT API'
>
> '/home/djviking/workspace/movies/src/main/java/no/smeaworks/movies/MoviesController.java'
>
> '/home/djviking/workspace/movies/src/main/java/no/smeaworks/movies/MoviesApplication.java'
> '/home/djviking/workspace/movies/src/main/java/module-info.java'
> Loading source file
>
> /home/djviking/workspace/movies/src/main/java/no/smeaworks/movies/MoviesController.java...
> [parsing started
>
> SimpleFileObject[/home/djviking/workspace/movies/src/main/java/no/smeaworks/movies/MoviesController.java]]
> [parsing completed 11ms]
> Loading source file
>
> /home/djviking/workspace/movies/src/main/java/no/smeaworks/movies/MoviesApplication.java...
> [parsing started
>
> SimpleFileObject[/home/djviking/workspace/movies/src/main/java/no/smeaworks/movies/MoviesApplication.java]]
> [parsing completed 3ms]
> Loading source file
> /home/djviking/workspace/movies/src/main/java/module-info.java...
> /home/djviking/workspace/movies/src/main/java/module-info.java:18:
> error: module not found: org.apache.logging.log4j
> requires org.apache.logging.log4j;
>^
> [parsing started
>
> SimpleFileObject[/home/djviking/workspace/movies/src/main/java/module-info.java]]
> [parsing completed 1ms]
> [loading /modules/javafx.controls/module-info.class]
> [loading /modules/javafx.graphics/module-info.class]
> [loading /modules/javafx.base/module-info.class]
> [loading /modules/java.desktop/module-info.class]
> [loading /modules/java.xml/module-info.class]
> [loading /modules/java.base/module-info.class]
> [loading /modules/java.datatransfer/module-info.class]
> [loading /modules/java.prefs/module-info.class]
> [loading /modules/javafx.fxml/module-info.class]
> [loading /modules/java.scripting/module-info.class]
> [loading /modules/java.logging/module-info.class]
> [loading /modules/javafx.web/module-info.class]
> [loading /modules/jdk.jsobject/module-info.class]
> [loading /modules/jdk.xml.dom/module-info.class]
> [loading /modules/javafx.media/module-info.class]
> [loading
> /home/djviking/.gradle/caches/modules-2/files-2.1/org.jfxtras/jfxtras-controls/9.0-r1/125ff6b0e22dcd7c9471dd0d849a2f4254b2ad84/jfxtras-controls-9.0-r1.jar(/module-info.class)]
> [loading
> /home/djviking/.gradle/caches/modules-2/files-2.1/org.jfxtras/jfxtras-common/9.0-r1/db8dbe26d4a41643e46320a1ec9ac193efc59c64/jfxtras-common-9.0-r1.jar(/module-info.class)]
> [loading
> /home/djviking/.gradle/caches/modules-2/files-2.1/org.jfxtras/jfxtras-fxml/9.0-r1/dfd376482bee9a70532f35f97881a8d7785e1e02/jfxtras-fxml-9.0-r1.jar(/module-info.class)]
> [loading
> /home/djviking/.gradle/caches/modules-2/files-2.1/com.jfoenix/jfoenix/9.0.4/b630dd9c840a8d4610a6f2f38706e21eddfebcd8/jfoenix-9.0.4.jar(/module-info.class)]
> [loading /modules/jdk.unsupported/module-info.class]
> [done in 322 ms]
> 1 error
> Den tir. 26. jun. 2018 kl. 01:48 skrev Ralph Goers <
> ralph.go...@dslextreme.com>:
> >
> > I can’t really answer that. I personally

Re: Log4j2 example required for java enterprise application

2018-08-09 Thread Matt Sicker 
Oh, and for some context, the JndiContextSelector can be useful if you
install your log4j2.xml config into JNDI and make it available throughout
your cluster. Then you don't even need to copy the file to each deployment
(and could potentially update it at runtime as well without, again,
redeploying the config file to N servers).

On Thu, 9 Aug 2018 at 10:50, Matt Sicker  wrote:

> From what I remember, you can add log4j-api and log4j-core (and any other
> logging bridges) to your EE server's shared lib folder (or install as a
> module in JBoss for example), though if it's all in one ear, you could just
> make it a normal library in there.
>
> As for a shared configuration, you can point them all to the same
> log4j2.xml config file, though you can also do the opposite and use a
> config per application (see <
> http://logging.apache.org/log4j/2.x/manual/webapp.html#ContextParams> for
> some more info). The docs about web applications apply equally well to an
> EAR containing a WAR (or more). As for EJBs specifically, I think there's
> an open issue about it already. If not, feel free to submit an issue (and
> PR if possible).
>
> On Thu, 9 Aug 2018 at 04:19, Rajvinder Pal 
> wrote:
>
>> Hi,
>>
>> I am looking for an example to configure log4j2 in a java enterprise
>> application consisting of Ejbs, WAR and Utility jars. I want to understand
>> where to place the logging jars, configuration file in a Java EE
>> application. Can i use a common log4j2.xml for the complete application?
>>
>> Thanks,
>> Raj
>>
>
>
> --
> Matt Sicker 
>


-- 
Matt Sicker

Re: Log4j2 example required for java enterprise application

2018-08-09 Thread Matt Sicker 
>From what I remember, you can add log4j-api and log4j-core (and any other
logging bridges) to your EE server's shared lib folder (or install as a
module in JBoss for example), though if it's all in one ear, you could just
make it a normal library in there.

As for a shared configuration, you can point them all to the same
log4j2.xml config file, though you can also do the opposite and use a
config per application (see <
http://logging.apache.org/log4j/2.x/manual/webapp.html#ContextParams> for
some more info). The docs about web applications apply equally well to an
EAR containing a WAR (or more). As for EJBs specifically, I think there's
an open issue about it already. If not, feel free to submit an issue (and
PR if possible).

On Thu, 9 Aug 2018 at 04:19, Rajvinder Pal  wrote:

> Hi,
>
> I am looking for an example to configure log4j2 in a java enterprise
> application consisting of Ejbs, WAR and Utility jars. I want to understand
> where to place the logging jars, configuration file in a Java EE
> application. Can i use a common log4j2.xml for the complete application?
>
> Thanks,
> Raj
>


-- 
Matt Sicker

Lilith 8.2.0 has been released!

2018-08-09 Thread Jörn Huxhorn 
This version of Lilith demands Java 8 update 181 or higher and will
says so if you try to start it with an older version. It has also
been built and tested with Java 10.0.2.

You can still receive event from previous versions so if your application is
still running Java 7 or lower just keep using the 0.9.44 artifacts.
Keep in mind that Java SE 7 End of Public Updates has already been reached.

See http://lilithapp.com/releases/8.2.0.xhtml for details.

-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org

Log4j2 example required for java enterprise application

2018-08-09 Thread Rajvinder Pal 
Hi,

I am looking for an example to configure log4j2 in a java enterprise
application consisting of Ejbs, WAR and Utility jars. I want to understand
where to place the logging jars, configuration file in a Java EE
application. Can i use a common log4j2.xml for the complete application?

Thanks,
Raj