You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Volkan Yazıcı <vo...@gmail.com> on 2021/04/06 20:14:08 UTC
Running "master" tests in IntelliJ IDEA after Java 11 upgrade
As subject hints, I am not able to run tests in IDEA anymore after Java 11
upgrade. I have deleted all IDEA related files and issued a clean Maven
build:
$ rm -rf ./.idea ./**/*.iml
$ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
$ ./mvnw clean install -DskipTests=true
Opened the directory using IDEA (2021.1 RC), but couldn't get it to have
successful build:
W: Output path
/home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
intersects with a source root. Only files that were created by build will
be cleaned
W: Output path
/home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
intersects with a source root. Only files that were created by build will
be cleaned
W: Output path
/home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
intersects with a source root. Only files that were created by build will
be cleaned
W: Output path
/home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
intersects with a source root. Only files that were created by build will
be cleaned
W: Output path
/home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
intersects with a source root. Only files that were created by build will
be cleaned
W: Output path
/home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
intersects with a source root. Only files that were created by build will
be cleaned
W: Output path
/home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
intersects with a source root. Only files that were created by build will
be cleaned
*E: Cannot build maven-annotations-production:log4j-api because it is
included into a circular dependency (module 'log4j-api' production,
maven-annotations-production:log4j-api, module 'log4j-plugins' production,
maven-annotations-production:log4j-plugins)E: Cannot build
maven-annotations-test:log4j-plugins because it is included into a circular
dependency (maven-annotations-test:log4j-plugins, module 'log4j-api' tests,
maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
Did you get it working? What shall I do to make it work?
Re: JsonTemplateLayout failures after Java 11 upgrade (Was: Running
"master" tests in IntelliJ IDEA after Java 11 upgrade)
Posted by Ralph Goers <ra...@dslextreme.com>.
I will check the manifest. The automatic module name doesn’t matter for now as I plan to convert everything that can and should be into “real” JPMS modules before 3.0 is released.
Ralph
> On Apr 7, 2021, at 12:06 AM, Volkan Yazıcı <vo...@gmail.com> wrote:
>
> Thanks so much for putting time into this Ralph, I really appreciated it.
> There is no way I could have figured this out by myself. I have some
> questions regarding pom.xml of JTL:
>
> In manifestEntries of JTL pom.xml, shouldn't there be an
> Automatic-Module-Name entry?
>
> There are X-Compile-Source-JDK and X-Compile-Target-JDK manifestEntries in
> pom.xml. I was expecting something like X-Compile-Release-JDK exposing
> maven.compiler.release property. Isn't there such a thing?
>
> On Wed, Apr 7, 2021 at 7:29 AM Ralph Goers <ra...@dslextreme.com>
> wrote:
>
>> I have found the problem with the master branch and fixed it. As I
>> suspected I thought I had previously fixed this but I am not sure what
>> happened to it.
>>
>> The issue was simple. Log4j-layout-template-json generates plugins in both
>> the public jar and in its tests. However, it was using the same Java
>> package for both resulting in duplicate Log4jPlugins classes on the class
>> path. Only one of them could be loaded. I fixed the problem by modifying
>> the compiler plugin to specify the package to use for the test plugins.
>>
>> We are still getting a few errors in both the GitHub Actions and Jenkins,
>> but those are probably legitimate issues that existed prior to the changes.
>>
>> One test that keeps failing on GitHub is the SimplePerfTest. It simply
>> tries to calculate the time it takes to perform isDebugEnabled,
>> isEnabled(Level.DEBUG) and logger.debug where all are false. Normally these
>> values are very small and consistent with each other. But in GitHb
>> sometimes one or two of the tests will be double or triple what it is
>> normally, which will cause the test to fail its limit check. I suspect this
>> is purely an environmental issue and will probably just look for a way to
>> disable that test on GitHub. I’ve never seen the issue on Jenkins.
>>
>> Ralph
>>
>>> On Apr 6, 2021, at 4:49 PM, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>>
>>> There was one test I saw saying it couldn’t find the ListAppender. So I
>> ran that test with -X and -Dlog4j2.debug=true and got
>>>
>>> DEBUG StatusLogger Returning AppenderRef with parent root of type
>> AppenderRef:class org.apache.logging.log4j.core.config.AppenderRef
>>> DEBUG StatusLogger Returning root with parent loggers of type root:class
>> org.apache.logging.log4j.core.config.LoggerConfig$RootLogger
>>> DEBUG StatusLogger Returning loggers with parent root of type
>> loggers:class org.apache.logging.log4j.core.config.LoggersPlugin
>>> DEBUG StatusLogger Completed parsing configuration
>>> ERROR StatusLogger Error processing element JsonTemplateLayout:
>> CLASS_NOT_FOUND
>>> ERROR StatusLogger Unable to locate plugin type for JsonTemplateLayout
>>> DEBUG StatusLogger PluginManager 'Lookup' found 16 plugins
>>> ERROR StatusLogger Unable to locate plugin for
>> eventTemplateAdditionalField
>>> ERROR StatusLogger Unable to locate plugin for
>> eventTemplateAdditionalField
>>> ERROR StatusLogger Unable to locate plugin for
>> eventTemplateAdditionalField
>>> ERROR StatusLogger Unable to locate plugin for
>> eventTemplateAdditionalField
>>> ERROR StatusLogger Unable to locate plugin for JsonTemplateLayout
>>> DEBUG StatusLogger Building Plugin[name=appender,
>> class=org.apache.logging.log4j.test.appender.ListAppender].
>>> TRACE StatusLogger TypeConverterRegistry initializing.
>>> DEBUG StatusLogger PluginManager 'TypeConverter' found 26 plugins
>>> ERROR StatusLogger Could not create plugin of type class
>> org.apache.logging.log4j.test.appender.ListAppender for element List
>>> java.lang.NullPointerException
>>> at
>> org.apache.logging.log4j.plugins.inject.PluginElementInjector.isRequestedNode(PluginElementInjector.java:94)
>>> at
>> java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:176)
>>> at
>> java.base/java.util.ArrayList$ArrayListSpliterator.tryAdvance(ArrayList.java:1632)
>>> at
>> java.base/java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:127)
>>> at
>> java.base/java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:502)
>>> at
>> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:488)
>>> at
>> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
>>> at
>> java.base/java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:150)
>>> at
>> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
>>> at
>> java.base/java.util.stream.ReferencePipeline.findAny(ReferencePipeline.java:548)
>>> at
>> org.apache.logging.log4j.plugins.inject.PluginElementInjector.inject(PluginElementInjector.java:79)
>>> at
>> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.lambda$injectBuilder$1(PluginBuilder.java:204)
>>> at java.base/java.util.Optional.ifPresent(Optional.java:183)
>>> at
>> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.injectBuilder(PluginBuilder.java:192)
>>> at
>> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:126)
>>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:995)
>>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:935)
>>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:927)
>>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:545)
>>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:242)
>>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:289)
>>> at
>> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>
>>>
>>> There is obviously lots wrong here. I’ll keep looking into this.
>>>
>>> Ralph
>>>
>>>> On Apr 6, 2021, at 4:16 PM, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>>>
>>>> I deleted the files from my local repo and restarted the build. It is
>> running along just fine - at least until it hits json template layout.
>>>>
>>>> Is there a reason you use the maven wrapper instead of Maven itself? I
>> have never used the wrapper. I am wondering if there is something going on
>> there.
>>>>
>>>> Ralph
>>>>
>>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>>>>
>>>>> I’ve never seen that. What is maven-annotations-production:log4j-api?
>>>>>
>>>>> Let me try removing the files from my maven local repo as you did.
>>>>>
>>>>> Ralph
>>>>>
>>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <vo...@gmail.com>
>> wrote:
>>>>>>
>>>>>> As subject hints, I am not able to run tests in IDEA anymore after
>> Java 11
>>>>>> upgrade. I have deleted all IDEA related files and issued a clean
>> Maven
>>>>>> build:
>>>>>>
>>>>>> $ rm -rf ./.idea ./**/*.iml
>>>>>> $ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>>>>>> $ ./mvnw clean install -DskipTests=true
>>>>>>
>>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get it to
>> have
>>>>>> successful build:
>>>>>>
>>>>>> W: Output path
>>>>>>
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>>>>>> intersects with a source root. Only files that were created by build
>> will
>>>>>> be cleaned
>>>>>> W: Output path
>>>>>>
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>>>>>> intersects with a source root. Only files that were created by build
>> will
>>>>>> be cleaned
>>>>>> W: Output path
>>>>>>
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>>>>>> intersects with a source root. Only files that were created by build
>> will
>>>>>> be cleaned
>>>>>> W: Output path
>>>>>>
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>>>>>> intersects with a source root. Only files that were created by build
>> will
>>>>>> be cleaned
>>>>>> W: Output path
>>>>>>
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>>>>>> intersects with a source root. Only files that were created by build
>> will
>>>>>> be cleaned
>>>>>> W: Output path
>>>>>>
>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>>>>>> intersects with a source root. Only files that were created by build
>> will
>>>>>> be cleaned
>>>>>> W: Output path
>>>>>>
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>>>>>> intersects with a source root. Only files that were created by build
>> will
>>>>>> be cleaned
>>>>>>
>>>>>> *E: Cannot build maven-annotations-production:log4j-api because it is
>>>>>> included into a circular dependency (module 'log4j-api' production,
>>>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
>> production,
>>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
>>>>>> maven-annotations-test:log4j-plugins because it is included into a
>> circular
>>>>>> dependency (maven-annotations-test:log4j-plugins, module 'log4j-api'
>> tests,
>>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
>>>>>>
>>>>>> Did you get it working? What shall I do to make it work?
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
JsonTemplateLayout failures after Java 11 upgrade (Was: Running
"master" tests in IntelliJ IDEA after Java 11 upgrade)
Posted by Volkan Yazıcı <vo...@gmail.com>.
Thanks so much for putting time into this Ralph, I really appreciated it.
There is no way I could have figured this out by myself. I have some
questions regarding pom.xml of JTL:
In manifestEntries of JTL pom.xml, shouldn't there be an
Automatic-Module-Name entry?
There are X-Compile-Source-JDK and X-Compile-Target-JDK manifestEntries in
pom.xml. I was expecting something like X-Compile-Release-JDK exposing
maven.compiler.release property. Isn't there such a thing?
On Wed, Apr 7, 2021 at 7:29 AM Ralph Goers <ra...@dslextreme.com>
wrote:
> I have found the problem with the master branch and fixed it. As I
> suspected I thought I had previously fixed this but I am not sure what
> happened to it.
>
> The issue was simple. Log4j-layout-template-json generates plugins in both
> the public jar and in its tests. However, it was using the same Java
> package for both resulting in duplicate Log4jPlugins classes on the class
> path. Only one of them could be loaded. I fixed the problem by modifying
> the compiler plugin to specify the package to use for the test plugins.
>
> We are still getting a few errors in both the GitHub Actions and Jenkins,
> but those are probably legitimate issues that existed prior to the changes.
>
> One test that keeps failing on GitHub is the SimplePerfTest. It simply
> tries to calculate the time it takes to perform isDebugEnabled,
> isEnabled(Level.DEBUG) and logger.debug where all are false. Normally these
> values are very small and consistent with each other. But in GitHb
> sometimes one or two of the tests will be double or triple what it is
> normally, which will cause the test to fail its limit check. I suspect this
> is purely an environmental issue and will probably just look for a way to
> disable that test on GitHub. I’ve never seen the issue on Jenkins.
>
> Ralph
>
> > On Apr 6, 2021, at 4:49 PM, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >
> > There was one test I saw saying it couldn’t find the ListAppender. So I
> ran that test with -X and -Dlog4j2.debug=true and got
> >
> > DEBUG StatusLogger Returning AppenderRef with parent root of type
> AppenderRef:class org.apache.logging.log4j.core.config.AppenderRef
> > DEBUG StatusLogger Returning root with parent loggers of type root:class
> org.apache.logging.log4j.core.config.LoggerConfig$RootLogger
> > DEBUG StatusLogger Returning loggers with parent root of type
> loggers:class org.apache.logging.log4j.core.config.LoggersPlugin
> > DEBUG StatusLogger Completed parsing configuration
> > ERROR StatusLogger Error processing element JsonTemplateLayout:
> CLASS_NOT_FOUND
> > ERROR StatusLogger Unable to locate plugin type for JsonTemplateLayout
> > DEBUG StatusLogger PluginManager 'Lookup' found 16 plugins
> > ERROR StatusLogger Unable to locate plugin for
> eventTemplateAdditionalField
> > ERROR StatusLogger Unable to locate plugin for
> eventTemplateAdditionalField
> > ERROR StatusLogger Unable to locate plugin for
> eventTemplateAdditionalField
> > ERROR StatusLogger Unable to locate plugin for
> eventTemplateAdditionalField
> > ERROR StatusLogger Unable to locate plugin for JsonTemplateLayout
> > DEBUG StatusLogger Building Plugin[name=appender,
> class=org.apache.logging.log4j.test.appender.ListAppender].
> > TRACE StatusLogger TypeConverterRegistry initializing.
> > DEBUG StatusLogger PluginManager 'TypeConverter' found 26 plugins
> > ERROR StatusLogger Could not create plugin of type class
> org.apache.logging.log4j.test.appender.ListAppender for element List
> > java.lang.NullPointerException
> > at
> org.apache.logging.log4j.plugins.inject.PluginElementInjector.isRequestedNode(PluginElementInjector.java:94)
> > at
> java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:176)
> > at
> java.base/java.util.ArrayList$ArrayListSpliterator.tryAdvance(ArrayList.java:1632)
> > at
> java.base/java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:127)
> > at
> java.base/java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:502)
> > at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:488)
> > at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> > at
> java.base/java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:150)
> > at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> > at
> java.base/java.util.stream.ReferencePipeline.findAny(ReferencePipeline.java:548)
> > at
> org.apache.logging.log4j.plugins.inject.PluginElementInjector.inject(PluginElementInjector.java:79)
> > at
> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.lambda$injectBuilder$1(PluginBuilder.java:204)
> > at java.base/java.util.Optional.ifPresent(Optional.java:183)
> > at
> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.injectBuilder(PluginBuilder.java:192)
> > at
> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:126)
> > at
> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:995)
> > at
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:935)
> > at
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:927)
> > at
> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:545)
> > at
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:242)
> > at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:289)
> > at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
> >
> >
> > There is obviously lots wrong here. I’ll keep looking into this.
> >
> > Ralph
> >
> >> On Apr 6, 2021, at 4:16 PM, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >>
> >> I deleted the files from my local repo and restarted the build. It is
> running along just fine - at least until it hits json template layout.
> >>
> >> Is there a reason you use the maven wrapper instead of Maven itself? I
> have never used the wrapper. I am wondering if there is something going on
> there.
> >>
> >> Ralph
> >>
> >>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >>>
> >>> I’ve never seen that. What is maven-annotations-production:log4j-api?
> >>>
> >>> Let me try removing the files from my maven local repo as you did.
> >>>
> >>> Ralph
> >>>
> >>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <vo...@gmail.com>
> wrote:
> >>>>
> >>>> As subject hints, I am not able to run tests in IDEA anymore after
> Java 11
> >>>> upgrade. I have deleted all IDEA related files and issued a clean
> Maven
> >>>> build:
> >>>>
> >>>> $ rm -rf ./.idea ./**/*.iml
> >>>> $ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> >>>> $ ./mvnw clean install -DskipTests=true
> >>>>
> >>>> Opened the directory using IDEA (2021.1 RC), but couldn't get it to
> have
> >>>> successful build:
> >>>>
> >>>> W: Output path
> >>>>
> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> >>>> intersects with a source root. Only files that were created by build
> will
> >>>> be cleaned
> >>>> W: Output path
> >>>>
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> >>>> intersects with a source root. Only files that were created by build
> will
> >>>> be cleaned
> >>>> W: Output path
> >>>>
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> >>>> intersects with a source root. Only files that were created by build
> will
> >>>> be cleaned
> >>>> W: Output path
> >>>>
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> >>>> intersects with a source root. Only files that were created by build
> will
> >>>> be cleaned
> >>>> W: Output path
> >>>>
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> >>>> intersects with a source root. Only files that were created by build
> will
> >>>> be cleaned
> >>>> W: Output path
> >>>>
> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> >>>> intersects with a source root. Only files that were created by build
> will
> >>>> be cleaned
> >>>> W: Output path
> >>>>
> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> >>>> intersects with a source root. Only files that were created by build
> will
> >>>> be cleaned
> >>>>
> >>>> *E: Cannot build maven-annotations-production:log4j-api because it is
> >>>> included into a circular dependency (module 'log4j-api' production,
> >>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
> production,
> >>>> maven-annotations-production:log4j-plugins)E: Cannot build
> >>>> maven-annotations-test:log4j-plugins because it is included into a
> circular
> >>>> dependency (maven-annotations-test:log4j-plugins, module 'log4j-api'
> tests,
> >>>> maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
> >>>>
> >>>> Did you get it working? What shall I do to make it work?
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >
> >
> >
>
>
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Ralph Goers <ra...@dslextreme.com>.
I have found the problem with the master branch and fixed it. As I suspected I thought I had previously fixed this but I am not sure what happened to it.
The issue was simple. Log4j-layout-template-json generates plugins in both the public jar and in its tests. However, it was using the same Java package for both resulting in duplicate Log4jPlugins classes on the class path. Only one of them could be loaded. I fixed the problem by modifying the compiler plugin to specify the package to use for the test plugins.
We are still getting a few errors in both the GitHub Actions and Jenkins, but those are probably legitimate issues that existed prior to the changes.
One test that keeps failing on GitHub is the SimplePerfTest. It simply tries to calculate the time it takes to perform isDebugEnabled, isEnabled(Level.DEBUG) and logger.debug where all are false. Normally these values are very small and consistent with each other. But in GitHb sometimes one or two of the tests will be double or triple what it is normally, which will cause the test to fail its limit check. I suspect this is purely an environmental issue and will probably just look for a way to disable that test on GitHub. I’ve never seen the issue on Jenkins.
Ralph
> On Apr 6, 2021, at 4:49 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>
> There was one test I saw saying it couldn’t find the ListAppender. So I ran that test with -X and -Dlog4j2.debug=true and got
>
> DEBUG StatusLogger Returning AppenderRef with parent root of type AppenderRef:class org.apache.logging.log4j.core.config.AppenderRef
> DEBUG StatusLogger Returning root with parent loggers of type root:class org.apache.logging.log4j.core.config.LoggerConfig$RootLogger
> DEBUG StatusLogger Returning loggers with parent root of type loggers:class org.apache.logging.log4j.core.config.LoggersPlugin
> DEBUG StatusLogger Completed parsing configuration
> ERROR StatusLogger Error processing element JsonTemplateLayout: CLASS_NOT_FOUND
> ERROR StatusLogger Unable to locate plugin type for JsonTemplateLayout
> DEBUG StatusLogger PluginManager 'Lookup' found 16 plugins
> ERROR StatusLogger Unable to locate plugin for eventTemplateAdditionalField
> ERROR StatusLogger Unable to locate plugin for eventTemplateAdditionalField
> ERROR StatusLogger Unable to locate plugin for eventTemplateAdditionalField
> ERROR StatusLogger Unable to locate plugin for eventTemplateAdditionalField
> ERROR StatusLogger Unable to locate plugin for JsonTemplateLayout
> DEBUG StatusLogger Building Plugin[name=appender, class=org.apache.logging.log4j.test.appender.ListAppender].
> TRACE StatusLogger TypeConverterRegistry initializing.
> DEBUG StatusLogger PluginManager 'TypeConverter' found 26 plugins
> ERROR StatusLogger Could not create plugin of type class org.apache.logging.log4j.test.appender.ListAppender for element List
> java.lang.NullPointerException
> at org.apache.logging.log4j.plugins.inject.PluginElementInjector.isRequestedNode(PluginElementInjector.java:94)
> at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:176)
> at java.base/java.util.ArrayList$ArrayListSpliterator.tryAdvance(ArrayList.java:1632)
> at java.base/java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:127)
> at java.base/java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:502)
> at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:488)
> at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> at java.base/java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:150)
> at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.base/java.util.stream.ReferencePipeline.findAny(ReferencePipeline.java:548)
> at org.apache.logging.log4j.plugins.inject.PluginElementInjector.inject(PluginElementInjector.java:79)
> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.lambda$injectBuilder$1(PluginBuilder.java:204)
> at java.base/java.util.Optional.ifPresent(Optional.java:183)
> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.injectBuilder(PluginBuilder.java:192)
> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:126)
> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:995)
> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:935)
> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:927)
> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:545)
> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:242)
> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:289)
> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>
>
> There is obviously lots wrong here. I’ll keep looking into this.
>
> Ralph
>
>> On Apr 6, 2021, at 4:16 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>>
>> I deleted the files from my local repo and restarted the build. It is running along just fine - at least until it hits json template layout.
>>
>> Is there a reason you use the maven wrapper instead of Maven itself? I have never used the wrapper. I am wondering if there is something going on there.
>>
>> Ralph
>>
>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>>>
>>> I’ve never seen that. What is maven-annotations-production:log4j-api?
>>>
>>> Let me try removing the files from my maven local repo as you did.
>>>
>>> Ralph
>>>
>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <vo...@gmail.com> wrote:
>>>>
>>>> As subject hints, I am not able to run tests in IDEA anymore after Java 11
>>>> upgrade. I have deleted all IDEA related files and issued a clean Maven
>>>> build:
>>>>
>>>> $ rm -rf ./.idea ./**/*.iml
>>>> $ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>>>> $ ./mvnw clean install -DskipTests=true
>>>>
>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get it to have
>>>> successful build:
>>>>
>>>> W: Output path
>>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>>>> intersects with a source root. Only files that were created by build will
>>>> be cleaned
>>>> W: Output path
>>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>>>> intersects with a source root. Only files that were created by build will
>>>> be cleaned
>>>> W: Output path
>>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>>>> intersects with a source root. Only files that were created by build will
>>>> be cleaned
>>>> W: Output path
>>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>>>> intersects with a source root. Only files that were created by build will
>>>> be cleaned
>>>> W: Output path
>>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>>>> intersects with a source root. Only files that were created by build will
>>>> be cleaned
>>>> W: Output path
>>>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>>>> intersects with a source root. Only files that were created by build will
>>>> be cleaned
>>>> W: Output path
>>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>>>> intersects with a source root. Only files that were created by build will
>>>> be cleaned
>>>>
>>>> *E: Cannot build maven-annotations-production:log4j-api because it is
>>>> included into a circular dependency (module 'log4j-api' production,
>>>> maven-annotations-production:log4j-api, module 'log4j-plugins' production,
>>>> maven-annotations-production:log4j-plugins)E: Cannot build
>>>> maven-annotations-test:log4j-plugins because it is included into a circular
>>>> dependency (maven-annotations-test:log4j-plugins, module 'log4j-api' tests,
>>>> maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
>>>>
>>>> Did you get it working? What shall I do to make it work?
>>>
>>>
>>>
>>
>>
>>
>
>
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Ralph Goers <ra...@dslextreme.com>.
There was one test I saw saying it couldn’t find the ListAppender. So I ran that test with -X and -Dlog4j2.debug=true and got
DEBUG StatusLogger Returning AppenderRef with parent root of type AppenderRef:class org.apache.logging.log4j.core.config.AppenderRef
DEBUG StatusLogger Returning root with parent loggers of type root:class org.apache.logging.log4j.core.config.LoggerConfig$RootLogger
DEBUG StatusLogger Returning loggers with parent root of type loggers:class org.apache.logging.log4j.core.config.LoggersPlugin
DEBUG StatusLogger Completed parsing configuration
ERROR StatusLogger Error processing element JsonTemplateLayout: CLASS_NOT_FOUND
ERROR StatusLogger Unable to locate plugin type for JsonTemplateLayout
DEBUG StatusLogger PluginManager 'Lookup' found 16 plugins
ERROR StatusLogger Unable to locate plugin for eventTemplateAdditionalField
ERROR StatusLogger Unable to locate plugin for eventTemplateAdditionalField
ERROR StatusLogger Unable to locate plugin for eventTemplateAdditionalField
ERROR StatusLogger Unable to locate plugin for eventTemplateAdditionalField
ERROR StatusLogger Unable to locate plugin for JsonTemplateLayout
DEBUG StatusLogger Building Plugin[name=appender, class=org.apache.logging.log4j.test.appender.ListAppender].
TRACE StatusLogger TypeConverterRegistry initializing.
DEBUG StatusLogger PluginManager 'TypeConverter' found 26 plugins
ERROR StatusLogger Could not create plugin of type class org.apache.logging.log4j.test.appender.ListAppender for element List
java.lang.NullPointerException
at org.apache.logging.log4j.plugins.inject.PluginElementInjector.isRequestedNode(PluginElementInjector.java:94)
at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:176)
at java.base/java.util.ArrayList$ArrayListSpliterator.tryAdvance(ArrayList.java:1632)
at java.base/java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:127)
at java.base/java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:502)
at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:488)
at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
at java.base/java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:150)
at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.base/java.util.stream.ReferencePipeline.findAny(ReferencePipeline.java:548)
at org.apache.logging.log4j.plugins.inject.PluginElementInjector.inject(PluginElementInjector.java:79)
at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.lambda$injectBuilder$1(PluginBuilder.java:204)
at java.base/java.util.Optional.ifPresent(Optional.java:183)
at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.injectBuilder(PluginBuilder.java:192)
at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:126)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:995)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:935)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:927)
at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:545)
at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:242)
at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:289)
at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
There is obviously lots wrong here. I’ll keep looking into this.
Ralph
> On Apr 6, 2021, at 4:16 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>
> I deleted the files from my local repo and restarted the build. It is running along just fine - at least until it hits json template layout.
>
> Is there a reason you use the maven wrapper instead of Maven itself? I have never used the wrapper. I am wondering if there is something going on there.
>
> Ralph
>
>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>>
>> I’ve never seen that. What is maven-annotations-production:log4j-api?
>>
>> Let me try removing the files from my maven local repo as you did.
>>
>> Ralph
>>
>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <vo...@gmail.com> wrote:
>>>
>>> As subject hints, I am not able to run tests in IDEA anymore after Java 11
>>> upgrade. I have deleted all IDEA related files and issued a clean Maven
>>> build:
>>>
>>> $ rm -rf ./.idea ./**/*.iml
>>> $ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>>> $ ./mvnw clean install -DskipTests=true
>>>
>>> Opened the directory using IDEA (2021.1 RC), but couldn't get it to have
>>> successful build:
>>>
>>> W: Output path
>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>>> intersects with a source root. Only files that were created by build will
>>> be cleaned
>>> W: Output path
>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>>> intersects with a source root. Only files that were created by build will
>>> be cleaned
>>> W: Output path
>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>>> intersects with a source root. Only files that were created by build will
>>> be cleaned
>>> W: Output path
>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>>> intersects with a source root. Only files that were created by build will
>>> be cleaned
>>> W: Output path
>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>>> intersects with a source root. Only files that were created by build will
>>> be cleaned
>>> W: Output path
>>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>>> intersects with a source root. Only files that were created by build will
>>> be cleaned
>>> W: Output path
>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>>> intersects with a source root. Only files that were created by build will
>>> be cleaned
>>>
>>> *E: Cannot build maven-annotations-production:log4j-api because it is
>>> included into a circular dependency (module 'log4j-api' production,
>>> maven-annotations-production:log4j-api, module 'log4j-plugins' production,
>>> maven-annotations-production:log4j-plugins)E: Cannot build
>>> maven-annotations-test:log4j-plugins because it is included into a circular
>>> dependency (maven-annotations-test:log4j-plugins, module 'log4j-api' tests,
>>> maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
>>>
>>> Did you get it working? What shall I do to make it work?
>>
>>
>>
>
>
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Matt Sicker <bo...@gmail.com>.
I can run with newer versions of Java than we require as a baseline. Thanks
for the info about what’s wrong!
On Sun, Jun 6, 2021 at 22:16 Ralph Goers <ra...@dslextreme.com> wrote:
> In the log4j-core directory run
>
> mvn clean test -Dtest=RequiredValidatorTest
>
> Once the module has compiled you can do
>
> mvn surefire:test -Dtest-RequiredValidatorTest
>
> The error happens because the initial compile cannot have a module-info
> and it is finding the one from the previous build. See
> https://github.com/apache/logging-log4j2/blob/master/log4j-core/README.md
> for more details.
>
> FWIW, the bug reported in
> https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8265826 was
> fixed in Java 17, so if we want to require Java 17 to be able to build
> Log4j I could get around at least that part of the problem.
>
> Ralph
>
> > On Jun 6, 2021, at 3:45 PM, Matt Sicker <bo...@gmail.com> wrote:
> >
> > I can't even figure out how to execute individual tests from the
> > command line. Trying to run tests in log4j-core like so give an error:
> >
> > $ mvn -pl :log4j-core test -Dtest=RequiredValidatorTest
> > ...
> > [ERROR] COMPILATION ERROR :
> > [INFO] -------------------------------------------------------------
> > [ERROR] error: module not found: org.fusesource.jansi
> > [ERROR] error: module not found: org.apache.commons.compress
> > [ERROR] error: module not found: com.fasterxml.jackson.dataformat.yaml
> > [ERROR] error: module not found: com.fasterxml.jackson.dataformat.xml
> > [ERROR] error: module not found: com.fasterxml.jackson.databind
> > [ERROR] error: module not found: com.fasterxml.jackson.core
> > [ERROR] error: module not found: com.conversantmedia.disruptor
> > [ERROR] error: module not found: org.osgi.framework
> > [ERROR] error: module not found: org.jctools.core
> > [ERROR] error: module not found: com.lmax.disruptor
> > [ERROR] error: module not found: org.apache.logging.log4j.plugins
> > [ERROR] error: module not found: org.apache.logging.log4j
> >
> > Now if the only supported way to run unit tests is to run the entire
> > test suite, then we have a huge problem.
> >
> > On Mon, 19 Apr 2021 at 17:34, Tim Perry <ti...@gmail.com> wrote:
> >>
> >> Can any of you recommend an idiots guide to setting up a log4j
> development
> >> environment in IntelliJ? I have never used IntelliJ before. Eclipse
> won't
> >> work with a maven project with multiple module-info.java files. There
> are
> >> bugs into the maven-eclipse tools (m2e) for this.
> >>
> >> I cannot see reverting to 1999 and using the command line debugger, so
> >> IntelliJ seems like my best shot at getting a working development
> >> environment. I just want autocomplete and the ability to connect a
> debugger
> >> without too much hoop jumping.
> >>
> >> Thanks,
> >> Tim
> >>
> >> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
> >> wrote:
> >>
> >>> I have also tried that too, but no luck so far. @Matt, are you able to
> run
> >>> any tests from IDEA using the most recent "master"?
> >>>
> >>> On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
> >>>
> >>>> See also
> >>>>
> >>>
> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
> >>>>
> >>>> On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
> >>>> wrote:
> >>>>>
> >>>>> mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
> debug
> >>>> options”
> >>>>>
> >>>>> Ralph
> >>>>>
> >>>>>> On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <vo...@gmail.com>
> >>>> wrote:
> >>>>>>
> >>>>>> Okay, fair enough. Thanks so much for sharing these details, I
> >>> really
> >>>>>> appreciated it. One final question: If you want to debug a single
> >>>> test, how
> >>>>>> does your work flow look like? Do you create a new "Run
> >>> Configuration"
> >>>>>> invoking a certain Maven command triggering the code/test that you
> >>> are
> >>>>>> interested in and "Debug Run"ing that "Run Configuration"?
> >>>>>>
> >>>>>> For the records, I still would like to hear how I can make IDEA to
> >>>> simply
> >>>>>> run a test. If anybody has succeeded in doing that, I am all ears.
> >>>>>>
> >>>>>>> On Wed, Apr 7, 2021 at 3:38 PM Apache <ra...@dslextreme.com>
> >>>> wrote:
> >>>>>>>
> >>>>>>> I will be honest. I have never tun any log4j tests in IntelliJ. I
> >>>> rarely
> >>>>>>> do it for any projects I work on. I use JVM remote debug all the
> >>>> time. I
> >>>>>>> don’t want to force others to have to do that, but I just never
> >>> think
> >>>> about
> >>>>>>> it.
> >>>>>>>
> >>>>>>> I use various versions of Maven from time to time. 3.6.1 is the
> >>>> default on
> >>>>>>> my Mac but I just installed 3.8.1 to validate what I needed to
> >>> change
> >>>> in my
> >>>>>>> setup to make it still work with my employers Nexus repository
> which
> >>>> still
> >>>>>>> uses http.
> >>>>>>>
> >>>>>>> When I am working on Log4J stuff I do a full mvn clean install
> >>> several
> >>>>>>> times a day. That takes a huge amount of time so I have learned to
> >>>>>>> multitask and work on other stuff while builds are running.
> >>>>>>>
> >>>>>>> Ralph.
> >>>>>>>
> >>>>>>>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
> >>> volkan.yazici@gmail.com>
> >>>>>>> wrote:
> >>>>>>>>
> >>>>>>>> Ralph, when you delete the IDEA-specific configuration (i.e.,
> >>> *.iml
> >>>>>>> files
> >>>>>>>> and .idea directory), compile the sources via Maven, and open the
> >>>> folder
> >>>>>>> in
> >>>>>>>> IDEA, can you run *any* tests? If so, do you have any custom IDEA
> >>>>>>>> configurations? Which IDEA version are you using? If you are not
> >>>> using
> >>>>>>> the
> >>>>>>>> wrapper, which Maven version are you using?
> >>>>>>>>
> >>>>>>>> I use Maven Wrapper to make sure Maven behaves the same in all
> >>>>>>>> environments, independent of my local setup. It also saves you
> >>> from a
> >>>>>>> local
> >>>>>>>> Maven dependency.
> >>>>>>>>
> >>>>>>>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
> >>>> ralph.goers@dslextreme.com>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> I deleted the files from my local repo and restarted the build.
> It
> >>>> is
> >>>>>>>>> running along just fine - at least until it hits json template
> >>>> layout.
> >>>>>>>>>
> >>>>>>>>> Is there a reason you use the maven wrapper instead of Maven
> >>>> itself? I
> >>>>>>>>> have never used the wrapper. I am wondering if there is something
> >>>> going
> >>>>>>> on
> >>>>>>>>> there.
> >>>>>>>>>
> >>>>>>>>> Ralph
> >>>>>>>>>
> >>>>>>>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
> >>>> ralph.goers@dslextreme.com>
> >>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>> I’ve never seen that. What is
> >>>> maven-annotations-production:log4j-api?
> >>>>>>>>>>
> >>>>>>>>>> Let me try removing the files from my maven local repo as you
> >>> did.
> >>>>>>>>>>
> >>>>>>>>>> Ralph
> >>>>>>>>>>
> >>>>>>>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
> >>>> volkan.yazici@gmail.com>
> >>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> As subject hints, I am not able to run tests in IDEA anymore
> >>> after
> >>>>>>> Java
> >>>>>>>>> 11
> >>>>>>>>>>> upgrade. I have deleted all IDEA related files and issued a
> >>> clean
> >>>>>>> Maven
> >>>>>>>>>>> build:
> >>>>>>>>>>>
> >>>>>>>>>>> $ rm -rf ./.idea ./**/*.iml
> >>>>>>>>>>> $ rm -rf
> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> >>>>>>>>>>> $ ./mvnw clean install -DskipTests=true
> >>>>>>>>>>>
> >>>>>>>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get
> it
> >>>> to
> >>>>>>> have
> >>>>>>>>>>> successful build:
> >>>>>>>>>>>
> >>>>>>>>>>> W: Output path
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>
> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> >>>>>>>>>>> intersects with a source root. Only files that were created by
> >>>> build
> >>>>>>>>> will
> >>>>>>>>>>> be cleaned
> >>>>>>>>>>> W: Output path
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>
> >>>
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> >>>>>>>>>>> intersects with a source root. Only files that were created by
> >>>> build
> >>>>>>>>> will
> >>>>>>>>>>> be cleaned
> >>>>>>>>>>> W: Output path
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>
> >>>
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> >>>>>>>>>>> intersects with a source root. Only files that were created by
> >>>> build
> >>>>>>>>> will
> >>>>>>>>>>> be cleaned
> >>>>>>>>>>> W: Output path
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>
> >>>
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> >>>>>>>>>>> intersects with a source root. Only files that were created by
> >>>> build
> >>>>>>>>> will
> >>>>>>>>>>> be cleaned
> >>>>>>>>>>> W: Output path
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>
> >>>
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> >>>>>>>>>>> intersects with a source root. Only files that were created by
> >>>> build
> >>>>>>>>> will
> >>>>>>>>>>> be cleaned
> >>>>>>>>>>> W: Output path
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>
> >>>
> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> >>>>>>>>>>> intersects with a source root. Only files that were created by
> >>>> build
> >>>>>>>>> will
> >>>>>>>>>>> be cleaned
> >>>>>>>>>>> W: Output path
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>
> >>>
> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> >>>>>>>>>>> intersects with a source root. Only files that were created by
> >>>> build
> >>>>>>>>> will
> >>>>>>>>>>> be cleaned
> >>>>>>>>>>>
> >>>>>>>>>>> *E: Cannot build maven-annotations-production:log4j-api because
> >>>> it is
> >>>>>>>>>>> included into a circular dependency (module 'log4j-api'
> >>>> production,
> >>>>>>>>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
> >>>>>>>>> production,
> >>>>>>>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
> >>>>>>>>>>> maven-annotations-test:log4j-plugins because it is included
> >>> into a
> >>>>>>>>> circular
> >>>>>>>>>>> dependency (maven-annotations-test:log4j-plugins, module
> >>>> 'log4j-api'
> >>>>>>>>> tests,
> >>>>>>>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
> tests)*
> >>>>>>>>>>>
> >>>>>>>>>>> Did you get it working? What shall I do to make it work?
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>
> >
>
>
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Ralph Goers <ra...@dslextreme.com>.
In the log4j-core directory run
mvn clean test -Dtest=RequiredValidatorTest
Once the module has compiled you can do
mvn surefire:test -Dtest-RequiredValidatorTest
The error happens because the initial compile cannot have a module-info and it is finding the one from the previous build. See https://github.com/apache/logging-log4j2/blob/master/log4j-core/README.md for more details.
FWIW, the bug reported in https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8265826 was fixed in Java 17, so if we want to require Java 17 to be able to build Log4j I could get around at least that part of the problem.
Ralph
> On Jun 6, 2021, at 3:45 PM, Matt Sicker <bo...@gmail.com> wrote:
>
> I can't even figure out how to execute individual tests from the
> command line. Trying to run tests in log4j-core like so give an error:
>
> $ mvn -pl :log4j-core test -Dtest=RequiredValidatorTest
> ...
> [ERROR] COMPILATION ERROR :
> [INFO] -------------------------------------------------------------
> [ERROR] error: module not found: org.fusesource.jansi
> [ERROR] error: module not found: org.apache.commons.compress
> [ERROR] error: module not found: com.fasterxml.jackson.dataformat.yaml
> [ERROR] error: module not found: com.fasterxml.jackson.dataformat.xml
> [ERROR] error: module not found: com.fasterxml.jackson.databind
> [ERROR] error: module not found: com.fasterxml.jackson.core
> [ERROR] error: module not found: com.conversantmedia.disruptor
> [ERROR] error: module not found: org.osgi.framework
> [ERROR] error: module not found: org.jctools.core
> [ERROR] error: module not found: com.lmax.disruptor
> [ERROR] error: module not found: org.apache.logging.log4j.plugins
> [ERROR] error: module not found: org.apache.logging.log4j
>
> Now if the only supported way to run unit tests is to run the entire
> test suite, then we have a huge problem.
>
> On Mon, 19 Apr 2021 at 17:34, Tim Perry <ti...@gmail.com> wrote:
>>
>> Can any of you recommend an idiots guide to setting up a log4j development
>> environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
>> work with a maven project with multiple module-info.java files. There are
>> bugs into the maven-eclipse tools (m2e) for this.
>>
>> I cannot see reverting to 1999 and using the command line debugger, so
>> IntelliJ seems like my best shot at getting a working development
>> environment. I just want autocomplete and the ability to connect a debugger
>> without too much hoop jumping.
>>
>> Thanks,
>> Tim
>>
>> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
>> wrote:
>>
>>> I have also tried that too, but no luck so far. @Matt, are you able to run
>>> any tests from IDEA using the most recent "master"?
>>>
>>> On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
>>>
>>>> See also
>>>>
>>> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
>>>>
>>>> On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
>>>> wrote:
>>>>>
>>>>> mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote debug
>>>> options”
>>>>>
>>>>> Ralph
>>>>>
>>>>>> On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <vo...@gmail.com>
>>>> wrote:
>>>>>>
>>>>>> Okay, fair enough. Thanks so much for sharing these details, I
>>> really
>>>>>> appreciated it. One final question: If you want to debug a single
>>>> test, how
>>>>>> does your work flow look like? Do you create a new "Run
>>> Configuration"
>>>>>> invoking a certain Maven command triggering the code/test that you
>>> are
>>>>>> interested in and "Debug Run"ing that "Run Configuration"?
>>>>>>
>>>>>> For the records, I still would like to hear how I can make IDEA to
>>>> simply
>>>>>> run a test. If anybody has succeeded in doing that, I am all ears.
>>>>>>
>>>>>>> On Wed, Apr 7, 2021 at 3:38 PM Apache <ra...@dslextreme.com>
>>>> wrote:
>>>>>>>
>>>>>>> I will be honest. I have never tun any log4j tests in IntelliJ. I
>>>> rarely
>>>>>>> do it for any projects I work on. I use JVM remote debug all the
>>>> time. I
>>>>>>> don’t want to force others to have to do that, but I just never
>>> think
>>>> about
>>>>>>> it.
>>>>>>>
>>>>>>> I use various versions of Maven from time to time. 3.6.1 is the
>>>> default on
>>>>>>> my Mac but I just installed 3.8.1 to validate what I needed to
>>> change
>>>> in my
>>>>>>> setup to make it still work with my employers Nexus repository which
>>>> still
>>>>>>> uses http.
>>>>>>>
>>>>>>> When I am working on Log4J stuff I do a full mvn clean install
>>> several
>>>>>>> times a day. That takes a huge amount of time so I have learned to
>>>>>>> multitask and work on other stuff while builds are running.
>>>>>>>
>>>>>>> Ralph.
>>>>>>>
>>>>>>>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
>>> volkan.yazici@gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Ralph, when you delete the IDEA-specific configuration (i.e.,
>>> *.iml
>>>>>>> files
>>>>>>>> and .idea directory), compile the sources via Maven, and open the
>>>> folder
>>>>>>> in
>>>>>>>> IDEA, can you run *any* tests? If so, do you have any custom IDEA
>>>>>>>> configurations? Which IDEA version are you using? If you are not
>>>> using
>>>>>>> the
>>>>>>>> wrapper, which Maven version are you using?
>>>>>>>>
>>>>>>>> I use Maven Wrapper to make sure Maven behaves the same in all
>>>>>>>> environments, independent of my local setup. It also saves you
>>> from a
>>>>>>> local
>>>>>>>> Maven dependency.
>>>>>>>>
>>>>>>>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
>>>> ralph.goers@dslextreme.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> I deleted the files from my local repo and restarted the build. It
>>>> is
>>>>>>>>> running along just fine - at least until it hits json template
>>>> layout.
>>>>>>>>>
>>>>>>>>> Is there a reason you use the maven wrapper instead of Maven
>>>> itself? I
>>>>>>>>> have never used the wrapper. I am wondering if there is something
>>>> going
>>>>>>> on
>>>>>>>>> there.
>>>>>>>>>
>>>>>>>>> Ralph
>>>>>>>>>
>>>>>>>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
>>>> ralph.goers@dslextreme.com>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> I’ve never seen that. What is
>>>> maven-annotations-production:log4j-api?
>>>>>>>>>>
>>>>>>>>>> Let me try removing the files from my maven local repo as you
>>> did.
>>>>>>>>>>
>>>>>>>>>> Ralph
>>>>>>>>>>
>>>>>>>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
>>>> volkan.yazici@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> As subject hints, I am not able to run tests in IDEA anymore
>>> after
>>>>>>> Java
>>>>>>>>> 11
>>>>>>>>>>> upgrade. I have deleted all IDEA related files and issued a
>>> clean
>>>>>>> Maven
>>>>>>>>>>> build:
>>>>>>>>>>>
>>>>>>>>>>> $ rm -rf ./.idea ./**/*.iml
>>>>>>>>>>> $ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>>>>>>>>>>> $ ./mvnw clean install -DskipTests=true
>>>>>>>>>>>
>>>>>>>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get it
>>>> to
>>>>>>> have
>>>>>>>>>>> successful build:
>>>>>>>>>>>
>>>>>>>>>>> W: Output path
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>>>>>>>>>>> intersects with a source root. Only files that were created by
>>>> build
>>>>>>>>> will
>>>>>>>>>>> be cleaned
>>>>>>>>>>> W: Output path
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>
>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>>>>>>>>>>> intersects with a source root. Only files that were created by
>>>> build
>>>>>>>>> will
>>>>>>>>>>> be cleaned
>>>>>>>>>>> W: Output path
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>
>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>>>>>>>>>>> intersects with a source root. Only files that were created by
>>>> build
>>>>>>>>> will
>>>>>>>>>>> be cleaned
>>>>>>>>>>> W: Output path
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>
>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>>>>>>>>>>> intersects with a source root. Only files that were created by
>>>> build
>>>>>>>>> will
>>>>>>>>>>> be cleaned
>>>>>>>>>>> W: Output path
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>
>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>>>>>>>>>>> intersects with a source root. Only files that were created by
>>>> build
>>>>>>>>> will
>>>>>>>>>>> be cleaned
>>>>>>>>>>> W: Output path
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>
>>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>>>>>>>>>>> intersects with a source root. Only files that were created by
>>>> build
>>>>>>>>> will
>>>>>>>>>>> be cleaned
>>>>>>>>>>> W: Output path
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>
>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>>>>>>>>>>> intersects with a source root. Only files that were created by
>>>> build
>>>>>>>>> will
>>>>>>>>>>> be cleaned
>>>>>>>>>>>
>>>>>>>>>>> *E: Cannot build maven-annotations-production:log4j-api because
>>>> it is
>>>>>>>>>>> included into a circular dependency (module 'log4j-api'
>>>> production,
>>>>>>>>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
>>>>>>>>> production,
>>>>>>>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
>>>>>>>>>>> maven-annotations-test:log4j-plugins because it is included
>>> into a
>>>>>>>>> circular
>>>>>>>>>>> dependency (maven-annotations-test:log4j-plugins, module
>>>> 'log4j-api'
>>>>>>>>> tests,
>>>>>>>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
>>>>>>>>>>>
>>>>>>>>>>> Did you get it working? What shall I do to make it work?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>
>>>
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Matt Sicker <bo...@gmail.com>.
I can't even figure out how to execute individual tests from the
command line. Trying to run tests in log4j-core like so give an error:
$ mvn -pl :log4j-core test -Dtest=RequiredValidatorTest
...
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] error: module not found: org.fusesource.jansi
[ERROR] error: module not found: org.apache.commons.compress
[ERROR] error: module not found: com.fasterxml.jackson.dataformat.yaml
[ERROR] error: module not found: com.fasterxml.jackson.dataformat.xml
[ERROR] error: module not found: com.fasterxml.jackson.databind
[ERROR] error: module not found: com.fasterxml.jackson.core
[ERROR] error: module not found: com.conversantmedia.disruptor
[ERROR] error: module not found: org.osgi.framework
[ERROR] error: module not found: org.jctools.core
[ERROR] error: module not found: com.lmax.disruptor
[ERROR] error: module not found: org.apache.logging.log4j.plugins
[ERROR] error: module not found: org.apache.logging.log4j
Now if the only supported way to run unit tests is to run the entire
test suite, then we have a huge problem.
On Mon, 19 Apr 2021 at 17:34, Tim Perry <ti...@gmail.com> wrote:
>
> Can any of you recommend an idiots guide to setting up a log4j development
> environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
> work with a maven project with multiple module-info.java files. There are
> bugs into the maven-eclipse tools (m2e) for this.
>
> I cannot see reverting to 1999 and using the command line debugger, so
> IntelliJ seems like my best shot at getting a working development
> environment. I just want autocomplete and the ability to connect a debugger
> without too much hoop jumping.
>
> Thanks,
> Tim
>
> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
> wrote:
>
> > I have also tried that too, but no luck so far. @Matt, are you able to run
> > any tests from IDEA using the most recent "master"?
> >
> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
> >
> > > See also
> > >
> > https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
> > >
> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
> > > wrote:
> > > >
> > > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote debug
> > > options”
> > > >
> > > > Ralph
> > > >
> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <vo...@gmail.com>
> > > wrote:
> > > > >
> > > > > Okay, fair enough. Thanks so much for sharing these details, I
> > really
> > > > > appreciated it. One final question: If you want to debug a single
> > > test, how
> > > > > does your work flow look like? Do you create a new "Run
> > Configuration"
> > > > > invoking a certain Maven command triggering the code/test that you
> > are
> > > > > interested in and "Debug Run"ing that "Run Configuration"?
> > > > >
> > > > > For the records, I still would like to hear how I can make IDEA to
> > > simply
> > > > > run a test. If anybody has succeeded in doing that, I am all ears.
> > > > >
> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <ra...@dslextreme.com>
> > > wrote:
> > > > >>
> > > > >> I will be honest. I have never tun any log4j tests in IntelliJ. I
> > > rarely
> > > > >> do it for any projects I work on. I use JVM remote debug all the
> > > time. I
> > > > >> don’t want to force others to have to do that, but I just never
> > think
> > > about
> > > > >> it.
> > > > >>
> > > > >> I use various versions of Maven from time to time. 3.6.1 is the
> > > default on
> > > > >> my Mac but I just installed 3.8.1 to validate what I needed to
> > change
> > > in my
> > > > >> setup to make it still work with my employers Nexus repository which
> > > still
> > > > >> uses http.
> > > > >>
> > > > >> When I am working on Log4J stuff I do a full mvn clean install
> > several
> > > > >> times a day. That takes a huge amount of time so I have learned to
> > > > >> multitask and work on other stuff while builds are running.
> > > > >>
> > > > >> Ralph.
> > > > >>
> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
> > volkan.yazici@gmail.com>
> > > > >> wrote:
> > > > >>>
> > > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
> > *.iml
> > > > >> files
> > > > >>> and .idea directory), compile the sources via Maven, and open the
> > > folder
> > > > >> in
> > > > >>> IDEA, can you run *any* tests? If so, do you have any custom IDEA
> > > > >>> configurations? Which IDEA version are you using? If you are not
> > > using
> > > > >> the
> > > > >>> wrapper, which Maven version are you using?
> > > > >>>
> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
> > > > >>> environments, independent of my local setup. It also saves you
> > from a
> > > > >> local
> > > > >>> Maven dependency.
> > > > >>>
> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
> > > ralph.goers@dslextreme.com>
> > > > >>>> wrote:
> > > > >>>>
> > > > >>>> I deleted the files from my local repo and restarted the build. It
> > > is
> > > > >>>> running along just fine - at least until it hits json template
> > > layout.
> > > > >>>>
> > > > >>>> Is there a reason you use the maven wrapper instead of Maven
> > > itself? I
> > > > >>>> have never used the wrapper. I am wondering if there is something
> > > going
> > > > >> on
> > > > >>>> there.
> > > > >>>>
> > > > >>>> Ralph
> > > > >>>>
> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
> > > ralph.goers@dslextreme.com>
> > > > >>>> wrote:
> > > > >>>>>
> > > > >>>>> I’ve never seen that. What is
> > > maven-annotations-production:log4j-api?
> > > > >>>>>
> > > > >>>>> Let me try removing the files from my maven local repo as you
> > did.
> > > > >>>>>
> > > > >>>>> Ralph
> > > > >>>>>
> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
> > > volkan.yazici@gmail.com>
> > > > >>>> wrote:
> > > > >>>>>>
> > > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
> > after
> > > > >> Java
> > > > >>>> 11
> > > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
> > clean
> > > > >> Maven
> > > > >>>>>> build:
> > > > >>>>>>
> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
> > > > >>>>>> $ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
> > > > >>>>>>
> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get it
> > > to
> > > > >> have
> > > > >>>>>> successful build:
> > > > >>>>>>
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > > /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> > /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> > /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> > /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> > /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> > /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> > /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>>
> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api because
> > > it is
> > > > >>>>>> included into a circular dependency (module 'log4j-api'
> > > production,
> > > > >>>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
> > > > >>>> production,
> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
> > > > >>>>>> maven-annotations-test:log4j-plugins because it is included
> > into a
> > > > >>>> circular
> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
> > > 'log4j-api'
> > > > >>>> tests,
> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
> > > > >>>>>>
> > > > >>>>>> Did you get it working? What shall I do to make it work?
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
Tim Perry block sixx5gxt@gmail.com and take my other email 📧
On Mon, Apr 19, 2021, 9:12 PM Sixx XT <si...@gmail.com> wrote:
> Help me hes in root bin
>
> On Mon, Apr 19, 2021, 6:34 PM Tim Perry <ti...@gmail.com> wrote:
>
>> Can any of you recommend an idiots guide to setting up a log4j development
>> environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
>> work with a maven project with multiple module-info.java files. There are
>> bugs into the maven-eclipse tools (m2e) for this.
>>
>> I cannot see reverting to 1999 and using the command line debugger, so
>> IntelliJ seems like my best shot at getting a working development
>> environment. I just want autocomplete and the ability to connect a
>> debugger
>> without too much hoop jumping.
>>
>> Thanks,
>> Tim
>>
>> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
>> wrote:
>>
>> > I have also tried that too, but no luck so far. @Matt, are you able to
>> run
>> > any tests from IDEA using the most recent "master"?
>> >
>> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
>> >
>> > > See also
>> > >
>> >
>> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
>> > >
>> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
>> > > wrote:
>> > > >
>> > > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
>> debug
>> > > options”
>> > > >
>> > > > Ralph
>> > > >
>> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <
>> volkan.yazici@gmail.com>
>> > > wrote:
>> > > > >
>> > > > > Okay, fair enough. Thanks so much for sharing these details, I
>> > really
>> > > > > appreciated it. One final question: If you want to debug a single
>> > > test, how
>> > > > > does your work flow look like? Do you create a new "Run
>> > Configuration"
>> > > > > invoking a certain Maven command triggering the code/test that you
>> > are
>> > > > > interested in and "Debug Run"ing that "Run Configuration"?
>> > > > >
>> > > > > For the records, I still would like to hear how I can make IDEA to
>> > > simply
>> > > > > run a test. If anybody has succeeded in doing that, I am all ears.
>> > > > >
>> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <
>> ralph.goers@dslextreme.com>
>> > > wrote:
>> > > > >>
>> > > > >> I will be honest. I have never tun any log4j tests in IntelliJ. I
>> > > rarely
>> > > > >> do it for any projects I work on. I use JVM remote debug all the
>> > > time. I
>> > > > >> don’t want to force others to have to do that, but I just never
>> > think
>> > > about
>> > > > >> it.
>> > > > >>
>> > > > >> I use various versions of Maven from time to time. 3.6.1 is the
>> > > default on
>> > > > >> my Mac but I just installed 3.8.1 to validate what I needed to
>> > change
>> > > in my
>> > > > >> setup to make it still work with my employers Nexus repository
>> which
>> > > still
>> > > > >> uses http.
>> > > > >>
>> > > > >> When I am working on Log4J stuff I do a full mvn clean install
>> > several
>> > > > >> times a day. That takes a huge amount of time so I have learned
>> to
>> > > > >> multitask and work on other stuff while builds are running.
>> > > > >>
>> > > > >> Ralph.
>> > > > >>
>> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
>> > volkan.yazici@gmail.com>
>> > > > >> wrote:
>> > > > >>>
>> > > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
>> > *.iml
>> > > > >> files
>> > > > >>> and .idea directory), compile the sources via Maven, and open
>> the
>> > > folder
>> > > > >> in
>> > > > >>> IDEA, can you run *any* tests? If so, do you have any custom
>> IDEA
>> > > > >>> configurations? Which IDEA version are you using? If you are not
>> > > using
>> > > > >> the
>> > > > >>> wrapper, which Maven version are you using?
>> > > > >>>
>> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
>> > > > >>> environments, independent of my local setup. It also saves you
>> > from a
>> > > > >> local
>> > > > >>> Maven dependency.
>> > > > >>>
>> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
>> > > ralph.goers@dslextreme.com>
>> > > > >>>> wrote:
>> > > > >>>>
>> > > > >>>> I deleted the files from my local repo and restarted the
>> build. It
>> > > is
>> > > > >>>> running along just fine - at least until it hits json template
>> > > layout.
>> > > > >>>>
>> > > > >>>> Is there a reason you use the maven wrapper instead of Maven
>> > > itself? I
>> > > > >>>> have never used the wrapper. I am wondering if there is
>> something
>> > > going
>> > > > >> on
>> > > > >>>> there.
>> > > > >>>>
>> > > > >>>> Ralph
>> > > > >>>>
>> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
>> > > ralph.goers@dslextreme.com>
>> > > > >>>> wrote:
>> > > > >>>>>
>> > > > >>>>> I’ve never seen that. What is
>> > > maven-annotations-production:log4j-api?
>> > > > >>>>>
>> > > > >>>>> Let me try removing the files from my maven local repo as you
>> > did.
>> > > > >>>>>
>> > > > >>>>> Ralph
>> > > > >>>>>
>> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
>> > > volkan.yazici@gmail.com>
>> > > > >>>> wrote:
>> > > > >>>>>>
>> > > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
>> > after
>> > > > >> Java
>> > > > >>>> 11
>> > > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
>> > clean
>> > > > >> Maven
>> > > > >>>>>> build:
>> > > > >>>>>>
>> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
>> > > > >>>>>> $ rm -rf
>> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
>> > > > >>>>>>
>> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't
>> get it
>> > > to
>> > > > >> have
>> > > > >>>>>> successful build:
>> > > > >>>>>>
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>>
>> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
>> because
>> > > it is
>> > > > >>>>>> included into a circular dependency (module 'log4j-api'
>> > > production,
>> > > > >>>>>> maven-annotations-production:log4j-api, module
>> 'log4j-plugins'
>> > > > >>>> production,
>> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
>> > > > >>>>>> maven-annotations-test:log4j-plugins because it is included
>> > into a
>> > > > >>>> circular
>> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
>> > > 'log4j-api'
>> > > > >>>> tests,
>> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
>> tests)*
>> > > > >>>>>>
>> > > > >>>>>> Did you get it working? What shall I do to make it work?
>> > > > >>>>>
>> > > > >>>>>
>> > > > >>>>>
>> > > > >>>>
>> > > > >>>>
>> > > > >>>>
>> > > > >>
>> > > > >>
>> > > > >>
>> > > >
>> > > >
>> > >
>> >
>>
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
Help me hes in root bin
On Mon, Apr 19, 2021, 6:34 PM Tim Perry <ti...@gmail.com> wrote:
> Can any of you recommend an idiots guide to setting up a log4j development
> environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
> work with a maven project with multiple module-info.java files. There are
> bugs into the maven-eclipse tools (m2e) for this.
>
> I cannot see reverting to 1999 and using the command line debugger, so
> IntelliJ seems like my best shot at getting a working development
> environment. I just want autocomplete and the ability to connect a debugger
> without too much hoop jumping.
>
> Thanks,
> Tim
>
> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
> wrote:
>
> > I have also tried that too, but no luck so far. @Matt, are you able to
> run
> > any tests from IDEA using the most recent "master"?
> >
> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
> >
> > > See also
> > >
> >
> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
> > >
> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
> > > wrote:
> > > >
> > > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
> debug
> > > options”
> > > >
> > > > Ralph
> > > >
> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <volkan.yazici@gmail.com
> >
> > > wrote:
> > > > >
> > > > > Okay, fair enough. Thanks so much for sharing these details, I
> > really
> > > > > appreciated it. One final question: If you want to debug a single
> > > test, how
> > > > > does your work flow look like? Do you create a new "Run
> > Configuration"
> > > > > invoking a certain Maven command triggering the code/test that you
> > are
> > > > > interested in and "Debug Run"ing that "Run Configuration"?
> > > > >
> > > > > For the records, I still would like to hear how I can make IDEA to
> > > simply
> > > > > run a test. If anybody has succeeded in doing that, I am all ears.
> > > > >
> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <ralph.goers@dslextreme.com
> >
> > > wrote:
> > > > >>
> > > > >> I will be honest. I have never tun any log4j tests in IntelliJ. I
> > > rarely
> > > > >> do it for any projects I work on. I use JVM remote debug all the
> > > time. I
> > > > >> don’t want to force others to have to do that, but I just never
> > think
> > > about
> > > > >> it.
> > > > >>
> > > > >> I use various versions of Maven from time to time. 3.6.1 is the
> > > default on
> > > > >> my Mac but I just installed 3.8.1 to validate what I needed to
> > change
> > > in my
> > > > >> setup to make it still work with my employers Nexus repository
> which
> > > still
> > > > >> uses http.
> > > > >>
> > > > >> When I am working on Log4J stuff I do a full mvn clean install
> > several
> > > > >> times a day. That takes a huge amount of time so I have learned to
> > > > >> multitask and work on other stuff while builds are running.
> > > > >>
> > > > >> Ralph.
> > > > >>
> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
> > volkan.yazici@gmail.com>
> > > > >> wrote:
> > > > >>>
> > > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
> > *.iml
> > > > >> files
> > > > >>> and .idea directory), compile the sources via Maven, and open the
> > > folder
> > > > >> in
> > > > >>> IDEA, can you run *any* tests? If so, do you have any custom IDEA
> > > > >>> configurations? Which IDEA version are you using? If you are not
> > > using
> > > > >> the
> > > > >>> wrapper, which Maven version are you using?
> > > > >>>
> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
> > > > >>> environments, independent of my local setup. It also saves you
> > from a
> > > > >> local
> > > > >>> Maven dependency.
> > > > >>>
> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
> > > ralph.goers@dslextreme.com>
> > > > >>>> wrote:
> > > > >>>>
> > > > >>>> I deleted the files from my local repo and restarted the build.
> It
> > > is
> > > > >>>> running along just fine - at least until it hits json template
> > > layout.
> > > > >>>>
> > > > >>>> Is there a reason you use the maven wrapper instead of Maven
> > > itself? I
> > > > >>>> have never used the wrapper. I am wondering if there is
> something
> > > going
> > > > >> on
> > > > >>>> there.
> > > > >>>>
> > > > >>>> Ralph
> > > > >>>>
> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
> > > ralph.goers@dslextreme.com>
> > > > >>>> wrote:
> > > > >>>>>
> > > > >>>>> I’ve never seen that. What is
> > > maven-annotations-production:log4j-api?
> > > > >>>>>
> > > > >>>>> Let me try removing the files from my maven local repo as you
> > did.
> > > > >>>>>
> > > > >>>>> Ralph
> > > > >>>>>
> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
> > > volkan.yazici@gmail.com>
> > > > >>>> wrote:
> > > > >>>>>>
> > > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
> > after
> > > > >> Java
> > > > >>>> 11
> > > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
> > clean
> > > > >> Maven
> > > > >>>>>> build:
> > > > >>>>>>
> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
> > > > >>>>>> $ rm -rf
> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
> > > > >>>>>>
> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get
> it
> > > to
> > > > >> have
> > > > >>>>>> successful build:
> > > > >>>>>>
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>>
> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
> because
> > > it is
> > > > >>>>>> included into a circular dependency (module 'log4j-api'
> > > production,
> > > > >>>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
> > > > >>>> production,
> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
> > > > >>>>>> maven-annotations-test:log4j-plugins because it is included
> > into a
> > > > >>>> circular
> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
> > > 'log4j-api'
> > > > >>>> tests,
> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
> tests)*
> > > > >>>>>>
> > > > >>>>>> Did you get it working? What shall I do to make it work?
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
Give me the $500,000 price tag on his head right now I can beat them but I
got to put it this what they want me to do they want me to install internet
computer Verizon Wireless all them and helping them Verizon they got
Cricket helping them AT&T we're going against every phone carrier in the
world China Wok $500 price tag we beat them we may get a million he's a
real ass story Zuckerberg
On Mon, Apr 19, 2021, 6:34 PM Tim Perry <ti...@gmail.com> wrote:
> Can any of you recommend an idiots guide to setting up a log4j development
> environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
> work with a maven project with multiple module-info.java files. There are
> bugs into the maven-eclipse tools (m2e) for this.
>
> I cannot see reverting to 1999 and using the command line debugger, so
> IntelliJ seems like my best shot at getting a working development
> environment. I just want autocomplete and the ability to connect a debugger
> without too much hoop jumping.
>
> Thanks,
> Tim
>
> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
> wrote:
>
> > I have also tried that too, but no luck so far. @Matt, are you able to
> run
> > any tests from IDEA using the most recent "master"?
> >
> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
> >
> > > See also
> > >
> >
> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
> > >
> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
> > > wrote:
> > > >
> > > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
> debug
> > > options”
> > > >
> > > > Ralph
> > > >
> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <volkan.yazici@gmail.com
> >
> > > wrote:
> > > > >
> > > > > Okay, fair enough. Thanks so much for sharing these details, I
> > really
> > > > > appreciated it. One final question: If you want to debug a single
> > > test, how
> > > > > does your work flow look like? Do you create a new "Run
> > Configuration"
> > > > > invoking a certain Maven command triggering the code/test that you
> > are
> > > > > interested in and "Debug Run"ing that "Run Configuration"?
> > > > >
> > > > > For the records, I still would like to hear how I can make IDEA to
> > > simply
> > > > > run a test. If anybody has succeeded in doing that, I am all ears.
> > > > >
> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <ralph.goers@dslextreme.com
> >
> > > wrote:
> > > > >>
> > > > >> I will be honest. I have never tun any log4j tests in IntelliJ. I
> > > rarely
> > > > >> do it for any projects I work on. I use JVM remote debug all the
> > > time. I
> > > > >> don’t want to force others to have to do that, but I just never
> > think
> > > about
> > > > >> it.
> > > > >>
> > > > >> I use various versions of Maven from time to time. 3.6.1 is the
> > > default on
> > > > >> my Mac but I just installed 3.8.1 to validate what I needed to
> > change
> > > in my
> > > > >> setup to make it still work with my employers Nexus repository
> which
> > > still
> > > > >> uses http.
> > > > >>
> > > > >> When I am working on Log4J stuff I do a full mvn clean install
> > several
> > > > >> times a day. That takes a huge amount of time so I have learned to
> > > > >> multitask and work on other stuff while builds are running.
> > > > >>
> > > > >> Ralph.
> > > > >>
> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
> > volkan.yazici@gmail.com>
> > > > >> wrote:
> > > > >>>
> > > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
> > *.iml
> > > > >> files
> > > > >>> and .idea directory), compile the sources via Maven, and open the
> > > folder
> > > > >> in
> > > > >>> IDEA, can you run *any* tests? If so, do you have any custom IDEA
> > > > >>> configurations? Which IDEA version are you using? If you are not
> > > using
> > > > >> the
> > > > >>> wrapper, which Maven version are you using?
> > > > >>>
> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
> > > > >>> environments, independent of my local setup. It also saves you
> > from a
> > > > >> local
> > > > >>> Maven dependency.
> > > > >>>
> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
> > > ralph.goers@dslextreme.com>
> > > > >>>> wrote:
> > > > >>>>
> > > > >>>> I deleted the files from my local repo and restarted the build.
> It
> > > is
> > > > >>>> running along just fine - at least until it hits json template
> > > layout.
> > > > >>>>
> > > > >>>> Is there a reason you use the maven wrapper instead of Maven
> > > itself? I
> > > > >>>> have never used the wrapper. I am wondering if there is
> something
> > > going
> > > > >> on
> > > > >>>> there.
> > > > >>>>
> > > > >>>> Ralph
> > > > >>>>
> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
> > > ralph.goers@dslextreme.com>
> > > > >>>> wrote:
> > > > >>>>>
> > > > >>>>> I’ve never seen that. What is
> > > maven-annotations-production:log4j-api?
> > > > >>>>>
> > > > >>>>> Let me try removing the files from my maven local repo as you
> > did.
> > > > >>>>>
> > > > >>>>> Ralph
> > > > >>>>>
> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
> > > volkan.yazici@gmail.com>
> > > > >>>> wrote:
> > > > >>>>>>
> > > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
> > after
> > > > >> Java
> > > > >>>> 11
> > > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
> > clean
> > > > >> Maven
> > > > >>>>>> build:
> > > > >>>>>>
> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
> > > > >>>>>> $ rm -rf
> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
> > > > >>>>>>
> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get
> it
> > > to
> > > > >> have
> > > > >>>>>> successful build:
> > > > >>>>>>
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>>
> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
> because
> > > it is
> > > > >>>>>> included into a circular dependency (module 'log4j-api'
> > > production,
> > > > >>>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
> > > > >>>> production,
> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
> > > > >>>>>> maven-annotations-test:log4j-plugins because it is included
> > into a
> > > > >>>> circular
> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
> > > 'log4j-api'
> > > > >>>> tests,
> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
> tests)*
> > > > >>>>>>
> > > > >>>>>> Did you get it working? What shall I do to make it work?
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
It's like I gave y'all credit last out of my YouTube channel like I said
y'all came in we started whooping up on they ass 1 45,000 people right now
going to get some cash at 6
On Tue, Apr 20, 2021, 9:46 AM Sixx XT <si...@gmail.com> wrote:
> United States government we're going against the government dude
>
> On Tue, Apr 20, 2021, 9:44 AM Matt Sicker <bo...@gmail.com> wrote:
>
>> I think you also need to check the “skip tests” box in the config. Strange
>> UI, I know.
>>
>> On Mon, Apr 19, 2021 at 20:03 Tim Perry <ti...@gmail.com> wrote:
>>
>> > I deleted all log4j artifacts in my .m2 directory and I'm no longer
>> getting
>> > the "circular dependency" that Volkan reported.
>> >
>> > I checked the box for "Delegate IDE build/run actions to Maven" like
>> Matt
>> > recommended and was able to build which went as far as maven on the
>> command
>> > line does.
>> >
>> > Now I'm trying to run a unit test by clicking the arrow next to the test
>> > and saying run. However, IntelliJ starts a maven build and runs all the
>> > tests for log4j-core (which contains the test I am trying to run).
>> >
>> > Ideas?
>> >
>> > Thanks,
>> > Tim
>> >
>> >
>> > On Mon, Apr 19, 2021 at 3:34 PM Tim Perry <ti...@gmail.com> wrote:
>> >
>> > > Can any of you recommend an idiots guide to setting up a log4j
>> > development
>> > > environment in IntelliJ? I have never used IntelliJ before. Eclipse
>> won't
>> > > work with a maven project with multiple module-info.java files. There
>> are
>> > > bugs into the maven-eclipse tools (m2e) for this.
>> > >
>> > > I cannot see reverting to 1999 and using the command line debugger, so
>> > > IntelliJ seems like my best shot at getting a working development
>> > > environment. I just want autocomplete and the ability to connect a
>> > debugger
>> > > without too much hoop jumping.
>> > >
>> > > Thanks,
>> > > Tim
>> > >
>> > > On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <volkan.yazici@gmail.com
>> >
>> > > wrote:
>> > >
>> > >> I have also tried that too, but no luck so far. @Matt, are you able
>> to
>> > run
>> > >> any tests from IDEA using the most recent "master"?
>> > >>
>> > >> On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
>> > >>
>> > >> > See also
>> > >> >
>> > >>
>> >
>> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
>> > >> >
>> > >> > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <
>> ralph.goers@dslextreme.com>
>> > >> > wrote:
>> > >> > >
>> > >> > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
>> > >> debug
>> > >> > options”
>> > >> > >
>> > >> > > Ralph
>> > >> > >
>> > >> > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <
>> > volkan.yazici@gmail.com>
>> > >> > wrote:
>> > >> > > >
>> > >> > > > Okay, fair enough. Thanks so much for sharing these details, I
>> > >> really
>> > >> > > > appreciated it. One final question: If you want to debug a
>> single
>> > >> > test, how
>> > >> > > > does your work flow look like? Do you create a new "Run
>> > >> Configuration"
>> > >> > > > invoking a certain Maven command triggering the code/test that
>> you
>> > >> are
>> > >> > > > interested in and "Debug Run"ing that "Run Configuration"?
>> > >> > > >
>> > >> > > > For the records, I still would like to hear how I can make
>> IDEA to
>> > >> > simply
>> > >> > > > run a test. If anybody has succeeded in doing that, I am all
>> ears.
>> > >> > > >
>> > >> > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <
>> > ralph.goers@dslextreme.com>
>> > >> > wrote:
>> > >> > > >>
>> > >> > > >> I will be honest. I have never tun any log4j tests in
>> IntelliJ. I
>> > >> > rarely
>> > >> > > >> do it for any projects I work on. I use JVM remote debug all
>> the
>> > >> > time. I
>> > >> > > >> don’t want to force others to have to do that, but I just
>> never
>> > >> think
>> > >> > about
>> > >> > > >> it.
>> > >> > > >>
>> > >> > > >> I use various versions of Maven from time to time. 3.6.1 is
>> the
>> > >> > default on
>> > >> > > >> my Mac but I just installed 3.8.1 to validate what I needed to
>> > >> change
>> > >> > in my
>> > >> > > >> setup to make it still work with my employers Nexus repository
>> > >> which
>> > >> > still
>> > >> > > >> uses http.
>> > >> > > >>
>> > >> > > >> When I am working on Log4J stuff I do a full mvn clean install
>> > >> several
>> > >> > > >> times a day. That takes a huge amount of time so I have
>> learned
>> > to
>> > >> > > >> multitask and work on other stuff while builds are running.
>> > >> > > >>
>> > >> > > >> Ralph.
>> > >> > > >>
>> > >> > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
>> > >> volkan.yazici@gmail.com>
>> > >> > > >> wrote:
>> > >> > > >>>
>> > >> > > >>> Ralph, when you delete the IDEA-specific configuration
>> (i.e.,
>> > >> *.iml
>> > >> > > >> files
>> > >> > > >>> and .idea directory), compile the sources via Maven, and open
>> > the
>> > >> > folder
>> > >> > > >> in
>> > >> > > >>> IDEA, can you run *any* tests? If so, do you have any custom
>> > IDEA
>> > >> > > >>> configurations? Which IDEA version are you using? If you are
>> not
>> > >> > using
>> > >> > > >> the
>> > >> > > >>> wrapper, which Maven version are you using?
>> > >> > > >>>
>> > >> > > >>> I use Maven Wrapper to make sure Maven behaves the same in
>> all
>> > >> > > >>> environments, independent of my local setup. It also saves
>> you
>> > >> from a
>> > >> > > >> local
>> > >> > > >>> Maven dependency.
>> > >> > > >>>
>> > >> > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
>> > >> > ralph.goers@dslextreme.com>
>> > >> > > >>>> wrote:
>> > >> > > >>>>
>> > >> > > >>>> I deleted the files from my local repo and restarted the
>> build.
>> > >> It
>> > >> > is
>> > >> > > >>>> running along just fine - at least until it hits json
>> template
>> > >> > layout.
>> > >> > > >>>>
>> > >> > > >>>> Is there a reason you use the maven wrapper instead of Maven
>> > >> > itself? I
>> > >> > > >>>> have never used the wrapper. I am wondering if there is
>> > something
>> > >> > going
>> > >> > > >> on
>> > >> > > >>>> there.
>> > >> > > >>>>
>> > >> > > >>>> Ralph
>> > >> > > >>>>
>> > >> > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
>> > >> > ralph.goers@dslextreme.com>
>> > >> > > >>>> wrote:
>> > >> > > >>>>>
>> > >> > > >>>>> I’ve never seen that. What is
>> > >> > maven-annotations-production:log4j-api?
>> > >> > > >>>>>
>> > >> > > >>>>> Let me try removing the files from my maven local repo as
>> you
>> > >> did.
>> > >> > > >>>>>
>> > >> > > >>>>> Ralph
>> > >> > > >>>>>
>> > >> > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
>> > >> > volkan.yazici@gmail.com>
>> > >> > > >>>> wrote:
>> > >> > > >>>>>>
>> > >> > > >>>>>> As subject hints, I am not able to run tests in IDEA
>> anymore
>> > >> after
>> > >> > > >> Java
>> > >> > > >>>> 11
>> > >> > > >>>>>> upgrade. I have deleted all IDEA related files and issued
>> a
>> > >> clean
>> > >> > > >> Maven
>> > >> > > >>>>>> build:
>> > >> > > >>>>>>
>> > >> > > >>>>>> $ rm -rf ./.idea ./**/*.iml
>> > >> > > >>>>>> $ rm -rf
>> > >> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>> > >> > > >>>>>> $ ./mvnw clean install -DskipTests=true
>> > >> > > >>>>>>
>> > >> > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't
>> get
>> > >> it
>> > >> > to
>> > >> > > >> have
>> > >> > > >>>>>> successful build:
>> > >> > > >>>>>>
>> > >> > > >>>>>> W: Output path
>> > >> > > >>>>>>
>> > >> > > >>>>
>> > >> > > >>
>> > >> >
>> > >>
>> >
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>> > >> > > >>>>>> intersects with a source root. Only files that were
>> created
>> > by
>> > >> > build
>> > >> > > >>>> will
>> > >> > > >>>>>> be cleaned
>> > >> > > >>>>>> W: Output path
>> > >> > > >>>>>>
>> > >> > > >>>>
>> > >> > > >>
>> > >> >
>> > >>
>> >
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>> > >> > > >>>>>> intersects with a source root. Only files that were
>> created
>> > by
>> > >> > build
>> > >> > > >>>> will
>> > >> > > >>>>>> be cleaned
>> > >> > > >>>>>> W: Output path
>> > >> > > >>>>>>
>> > >> > > >>>>
>> > >> > > >>
>> > >> >
>> > >>
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>> > >> > > >>>>>> intersects with a source root. Only files that were
>> created
>> > by
>> > >> > build
>> > >> > > >>>> will
>> > >> > > >>>>>> be cleaned
>> > >> > > >>>>>> W: Output path
>> > >> > > >>>>>>
>> > >> > > >>>>
>> > >> > > >>
>> > >> >
>> > >>
>> >
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>> > >> > > >>>>>> intersects with a source root. Only files that were
>> created
>> > by
>> > >> > build
>> > >> > > >>>> will
>> > >> > > >>>>>> be cleaned
>> > >> > > >>>>>> W: Output path
>> > >> > > >>>>>>
>> > >> > > >>>>
>> > >> > > >>
>> > >> >
>> > >>
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>> > >> > > >>>>>> intersects with a source root. Only files that were
>> created
>> > by
>> > >> > build
>> > >> > > >>>> will
>> > >> > > >>>>>> be cleaned
>> > >> > > >>>>>> W: Output path
>> > >> > > >>>>>>
>> > >> > > >>>>
>> > >> > > >>
>> > >> >
>> > >>
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>> > >> > > >>>>>> intersects with a source root. Only files that were
>> created
>> > by
>> > >> > build
>> > >> > > >>>> will
>> > >> > > >>>>>> be cleaned
>> > >> > > >>>>>> W: Output path
>> > >> > > >>>>>>
>> > >> > > >>>>
>> > >> > > >>
>> > >> >
>> > >>
>> >
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>> > >> > > >>>>>> intersects with a source root. Only files that were
>> created
>> > by
>> > >> > build
>> > >> > > >>>> will
>> > >> > > >>>>>> be cleaned
>> > >> > > >>>>>>
>> > >> > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
>> > because
>> > >> > it is
>> > >> > > >>>>>> included into a circular dependency (module 'log4j-api'
>> > >> > production,
>> > >> > > >>>>>> maven-annotations-production:log4j-api, module
>> > 'log4j-plugins'
>> > >> > > >>>> production,
>> > >> > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
>> > >> > > >>>>>> maven-annotations-test:log4j-plugins because it is
>> included
>> > >> into a
>> > >> > > >>>> circular
>> > >> > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
>> > >> > 'log4j-api'
>> > >> > > >>>> tests,
>> > >> > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
>> > >> tests)*
>> > >> > > >>>>>>
>> > >> > > >>>>>> Did you get it working? What shall I do to make it work?
>> > >> > > >>>>>
>> > >> > > >>>>>
>> > >> > > >>>>>
>> > >> > > >>>>
>> > >> > > >>>>
>> > >> > > >>>>
>> > >> > > >>
>> > >> > > >>
>> > >> > > >>
>> > >> > >
>> > >> > >
>> > >> >
>> > >>
>> > >
>> >
>>
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
United States government we're going against the government dude
On Tue, Apr 20, 2021, 9:44 AM Matt Sicker <bo...@gmail.com> wrote:
> I think you also need to check the “skip tests” box in the config. Strange
> UI, I know.
>
> On Mon, Apr 19, 2021 at 20:03 Tim Perry <ti...@gmail.com> wrote:
>
> > I deleted all log4j artifacts in my .m2 directory and I'm no longer
> getting
> > the "circular dependency" that Volkan reported.
> >
> > I checked the box for "Delegate IDE build/run actions to Maven" like Matt
> > recommended and was able to build which went as far as maven on the
> command
> > line does.
> >
> > Now I'm trying to run a unit test by clicking the arrow next to the test
> > and saying run. However, IntelliJ starts a maven build and runs all the
> > tests for log4j-core (which contains the test I am trying to run).
> >
> > Ideas?
> >
> > Thanks,
> > Tim
> >
> >
> > On Mon, Apr 19, 2021 at 3:34 PM Tim Perry <ti...@gmail.com> wrote:
> >
> > > Can any of you recommend an idiots guide to setting up a log4j
> > development
> > > environment in IntelliJ? I have never used IntelliJ before. Eclipse
> won't
> > > work with a maven project with multiple module-info.java files. There
> are
> > > bugs into the maven-eclipse tools (m2e) for this.
> > >
> > > I cannot see reverting to 1999 and using the command line debugger, so
> > > IntelliJ seems like my best shot at getting a working development
> > > environment. I just want autocomplete and the ability to connect a
> > debugger
> > > without too much hoop jumping.
> > >
> > > Thanks,
> > > Tim
> > >
> > > On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
> > > wrote:
> > >
> > >> I have also tried that too, but no luck so far. @Matt, are you able to
> > run
> > >> any tests from IDEA using the most recent "master"?
> > >>
> > >> On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
> > >>
> > >> > See also
> > >> >
> > >>
> >
> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
> > >> >
> > >> > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <
> ralph.goers@dslextreme.com>
> > >> > wrote:
> > >> > >
> > >> > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
> > >> debug
> > >> > options”
> > >> > >
> > >> > > Ralph
> > >> > >
> > >> > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <
> > volkan.yazici@gmail.com>
> > >> > wrote:
> > >> > > >
> > >> > > > Okay, fair enough. Thanks so much for sharing these details, I
> > >> really
> > >> > > > appreciated it. One final question: If you want to debug a
> single
> > >> > test, how
> > >> > > > does your work flow look like? Do you create a new "Run
> > >> Configuration"
> > >> > > > invoking a certain Maven command triggering the code/test that
> you
> > >> are
> > >> > > > interested in and "Debug Run"ing that "Run Configuration"?
> > >> > > >
> > >> > > > For the records, I still would like to hear how I can make IDEA
> to
> > >> > simply
> > >> > > > run a test. If anybody has succeeded in doing that, I am all
> ears.
> > >> > > >
> > >> > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <
> > ralph.goers@dslextreme.com>
> > >> > wrote:
> > >> > > >>
> > >> > > >> I will be honest. I have never tun any log4j tests in
> IntelliJ. I
> > >> > rarely
> > >> > > >> do it for any projects I work on. I use JVM remote debug all
> the
> > >> > time. I
> > >> > > >> don’t want to force others to have to do that, but I just never
> > >> think
> > >> > about
> > >> > > >> it.
> > >> > > >>
> > >> > > >> I use various versions of Maven from time to time. 3.6.1 is the
> > >> > default on
> > >> > > >> my Mac but I just installed 3.8.1 to validate what I needed to
> > >> change
> > >> > in my
> > >> > > >> setup to make it still work with my employers Nexus repository
> > >> which
> > >> > still
> > >> > > >> uses http.
> > >> > > >>
> > >> > > >> When I am working on Log4J stuff I do a full mvn clean install
> > >> several
> > >> > > >> times a day. That takes a huge amount of time so I have learned
> > to
> > >> > > >> multitask and work on other stuff while builds are running.
> > >> > > >>
> > >> > > >> Ralph.
> > >> > > >>
> > >> > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
> > >> volkan.yazici@gmail.com>
> > >> > > >> wrote:
> > >> > > >>>
> > >> > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
> > >> *.iml
> > >> > > >> files
> > >> > > >>> and .idea directory), compile the sources via Maven, and open
> > the
> > >> > folder
> > >> > > >> in
> > >> > > >>> IDEA, can you run *any* tests? If so, do you have any custom
> > IDEA
> > >> > > >>> configurations? Which IDEA version are you using? If you are
> not
> > >> > using
> > >> > > >> the
> > >> > > >>> wrapper, which Maven version are you using?
> > >> > > >>>
> > >> > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
> > >> > > >>> environments, independent of my local setup. It also saves you
> > >> from a
> > >> > > >> local
> > >> > > >>> Maven dependency.
> > >> > > >>>
> > >> > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
> > >> > ralph.goers@dslextreme.com>
> > >> > > >>>> wrote:
> > >> > > >>>>
> > >> > > >>>> I deleted the files from my local repo and restarted the
> build.
> > >> It
> > >> > is
> > >> > > >>>> running along just fine - at least until it hits json
> template
> > >> > layout.
> > >> > > >>>>
> > >> > > >>>> Is there a reason you use the maven wrapper instead of Maven
> > >> > itself? I
> > >> > > >>>> have never used the wrapper. I am wondering if there is
> > something
> > >> > going
> > >> > > >> on
> > >> > > >>>> there.
> > >> > > >>>>
> > >> > > >>>> Ralph
> > >> > > >>>>
> > >> > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
> > >> > ralph.goers@dslextreme.com>
> > >> > > >>>> wrote:
> > >> > > >>>>>
> > >> > > >>>>> I’ve never seen that. What is
> > >> > maven-annotations-production:log4j-api?
> > >> > > >>>>>
> > >> > > >>>>> Let me try removing the files from my maven local repo as
> you
> > >> did.
> > >> > > >>>>>
> > >> > > >>>>> Ralph
> > >> > > >>>>>
> > >> > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
> > >> > volkan.yazici@gmail.com>
> > >> > > >>>> wrote:
> > >> > > >>>>>>
> > >> > > >>>>>> As subject hints, I am not able to run tests in IDEA
> anymore
> > >> after
> > >> > > >> Java
> > >> > > >>>> 11
> > >> > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
> > >> clean
> > >> > > >> Maven
> > >> > > >>>>>> build:
> > >> > > >>>>>>
> > >> > > >>>>>> $ rm -rf ./.idea ./**/*.iml
> > >> > > >>>>>> $ rm -rf
> > >> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> > >> > > >>>>>> $ ./mvnw clean install -DskipTests=true
> > >> > > >>>>>>
> > >> > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't
> get
> > >> it
> > >> > to
> > >> > > >> have
> > >> > > >>>>>> successful build:
> > >> > > >>>>>>
> > >> > > >>>>>> W: Output path
> > >> > > >>>>>>
> > >> > > >>>>
> > >> > > >>
> > >> >
> > >>
> > /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> > >> > > >>>>>> intersects with a source root. Only files that were created
> > by
> > >> > build
> > >> > > >>>> will
> > >> > > >>>>>> be cleaned
> > >> > > >>>>>> W: Output path
> > >> > > >>>>>>
> > >> > > >>>>
> > >> > > >>
> > >> >
> > >>
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> > >> > > >>>>>> intersects with a source root. Only files that were created
> > by
> > >> > build
> > >> > > >>>> will
> > >> > > >>>>>> be cleaned
> > >> > > >>>>>> W: Output path
> > >> > > >>>>>>
> > >> > > >>>>
> > >> > > >>
> > >> >
> > >>
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> > >> > > >>>>>> intersects with a source root. Only files that were created
> > by
> > >> > build
> > >> > > >>>> will
> > >> > > >>>>>> be cleaned
> > >> > > >>>>>> W: Output path
> > >> > > >>>>>>
> > >> > > >>>>
> > >> > > >>
> > >> >
> > >>
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> > >> > > >>>>>> intersects with a source root. Only files that were created
> > by
> > >> > build
> > >> > > >>>> will
> > >> > > >>>>>> be cleaned
> > >> > > >>>>>> W: Output path
> > >> > > >>>>>>
> > >> > > >>>>
> > >> > > >>
> > >> >
> > >>
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> > >> > > >>>>>> intersects with a source root. Only files that were created
> > by
> > >> > build
> > >> > > >>>> will
> > >> > > >>>>>> be cleaned
> > >> > > >>>>>> W: Output path
> > >> > > >>>>>>
> > >> > > >>>>
> > >> > > >>
> > >> >
> > >>
> >
> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> > >> > > >>>>>> intersects with a source root. Only files that were created
> > by
> > >> > build
> > >> > > >>>> will
> > >> > > >>>>>> be cleaned
> > >> > > >>>>>> W: Output path
> > >> > > >>>>>>
> > >> > > >>>>
> > >> > > >>
> > >> >
> > >>
> >
> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> > >> > > >>>>>> intersects with a source root. Only files that were created
> > by
> > >> > build
> > >> > > >>>> will
> > >> > > >>>>>> be cleaned
> > >> > > >>>>>>
> > >> > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
> > because
> > >> > it is
> > >> > > >>>>>> included into a circular dependency (module 'log4j-api'
> > >> > production,
> > >> > > >>>>>> maven-annotations-production:log4j-api, module
> > 'log4j-plugins'
> > >> > > >>>> production,
> > >> > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
> > >> > > >>>>>> maven-annotations-test:log4j-plugins because it is included
> > >> into a
> > >> > > >>>> circular
> > >> > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
> > >> > 'log4j-api'
> > >> > > >>>> tests,
> > >> > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
> > >> tests)*
> > >> > > >>>>>>
> > >> > > >>>>>> Did you get it working? What shall I do to make it work?
> > >> > > >>>>>
> > >> > > >>>>>
> > >> > > >>>>>
> > >> > > >>>>
> > >> > > >>>>
> > >> > > >>>>
> > >> > > >>
> > >> > > >>
> > >> > > >>
> > >> > >
> > >> > >
> > >> >
> > >>
> > >
> >
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Matt Sicker <bo...@gmail.com>.
I think you also need to check the “skip tests” box in the config. Strange
UI, I know.
On Mon, Apr 19, 2021 at 20:03 Tim Perry <ti...@gmail.com> wrote:
> I deleted all log4j artifacts in my .m2 directory and I'm no longer getting
> the "circular dependency" that Volkan reported.
>
> I checked the box for "Delegate IDE build/run actions to Maven" like Matt
> recommended and was able to build which went as far as maven on the command
> line does.
>
> Now I'm trying to run a unit test by clicking the arrow next to the test
> and saying run. However, IntelliJ starts a maven build and runs all the
> tests for log4j-core (which contains the test I am trying to run).
>
> Ideas?
>
> Thanks,
> Tim
>
>
> On Mon, Apr 19, 2021 at 3:34 PM Tim Perry <ti...@gmail.com> wrote:
>
> > Can any of you recommend an idiots guide to setting up a log4j
> development
> > environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
> > work with a maven project with multiple module-info.java files. There are
> > bugs into the maven-eclipse tools (m2e) for this.
> >
> > I cannot see reverting to 1999 and using the command line debugger, so
> > IntelliJ seems like my best shot at getting a working development
> > environment. I just want autocomplete and the ability to connect a
> debugger
> > without too much hoop jumping.
> >
> > Thanks,
> > Tim
> >
> > On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
> > wrote:
> >
> >> I have also tried that too, but no luck so far. @Matt, are you able to
> run
> >> any tests from IDEA using the most recent "master"?
> >>
> >> On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
> >>
> >> > See also
> >> >
> >>
> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
> >> >
> >> > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
> >> > wrote:
> >> > >
> >> > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
> >> debug
> >> > options”
> >> > >
> >> > > Ralph
> >> > >
> >> > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <
> volkan.yazici@gmail.com>
> >> > wrote:
> >> > > >
> >> > > > Okay, fair enough. Thanks so much for sharing these details, I
> >> really
> >> > > > appreciated it. One final question: If you want to debug a single
> >> > test, how
> >> > > > does your work flow look like? Do you create a new "Run
> >> Configuration"
> >> > > > invoking a certain Maven command triggering the code/test that you
> >> are
> >> > > > interested in and "Debug Run"ing that "Run Configuration"?
> >> > > >
> >> > > > For the records, I still would like to hear how I can make IDEA to
> >> > simply
> >> > > > run a test. If anybody has succeeded in doing that, I am all ears.
> >> > > >
> >> > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <
> ralph.goers@dslextreme.com>
> >> > wrote:
> >> > > >>
> >> > > >> I will be honest. I have never tun any log4j tests in IntelliJ. I
> >> > rarely
> >> > > >> do it for any projects I work on. I use JVM remote debug all the
> >> > time. I
> >> > > >> don’t want to force others to have to do that, but I just never
> >> think
> >> > about
> >> > > >> it.
> >> > > >>
> >> > > >> I use various versions of Maven from time to time. 3.6.1 is the
> >> > default on
> >> > > >> my Mac but I just installed 3.8.1 to validate what I needed to
> >> change
> >> > in my
> >> > > >> setup to make it still work with my employers Nexus repository
> >> which
> >> > still
> >> > > >> uses http.
> >> > > >>
> >> > > >> When I am working on Log4J stuff I do a full mvn clean install
> >> several
> >> > > >> times a day. That takes a huge amount of time so I have learned
> to
> >> > > >> multitask and work on other stuff while builds are running.
> >> > > >>
> >> > > >> Ralph.
> >> > > >>
> >> > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
> >> volkan.yazici@gmail.com>
> >> > > >> wrote:
> >> > > >>>
> >> > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
> >> *.iml
> >> > > >> files
> >> > > >>> and .idea directory), compile the sources via Maven, and open
> the
> >> > folder
> >> > > >> in
> >> > > >>> IDEA, can you run *any* tests? If so, do you have any custom
> IDEA
> >> > > >>> configurations? Which IDEA version are you using? If you are not
> >> > using
> >> > > >> the
> >> > > >>> wrapper, which Maven version are you using?
> >> > > >>>
> >> > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
> >> > > >>> environments, independent of my local setup. It also saves you
> >> from a
> >> > > >> local
> >> > > >>> Maven dependency.
> >> > > >>>
> >> > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
> >> > ralph.goers@dslextreme.com>
> >> > > >>>> wrote:
> >> > > >>>>
> >> > > >>>> I deleted the files from my local repo and restarted the build.
> >> It
> >> > is
> >> > > >>>> running along just fine - at least until it hits json template
> >> > layout.
> >> > > >>>>
> >> > > >>>> Is there a reason you use the maven wrapper instead of Maven
> >> > itself? I
> >> > > >>>> have never used the wrapper. I am wondering if there is
> something
> >> > going
> >> > > >> on
> >> > > >>>> there.
> >> > > >>>>
> >> > > >>>> Ralph
> >> > > >>>>
> >> > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
> >> > ralph.goers@dslextreme.com>
> >> > > >>>> wrote:
> >> > > >>>>>
> >> > > >>>>> I’ve never seen that. What is
> >> > maven-annotations-production:log4j-api?
> >> > > >>>>>
> >> > > >>>>> Let me try removing the files from my maven local repo as you
> >> did.
> >> > > >>>>>
> >> > > >>>>> Ralph
> >> > > >>>>>
> >> > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
> >> > volkan.yazici@gmail.com>
> >> > > >>>> wrote:
> >> > > >>>>>>
> >> > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
> >> after
> >> > > >> Java
> >> > > >>>> 11
> >> > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
> >> clean
> >> > > >> Maven
> >> > > >>>>>> build:
> >> > > >>>>>>
> >> > > >>>>>> $ rm -rf ./.idea ./**/*.iml
> >> > > >>>>>> $ rm -rf
> >> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> >> > > >>>>>> $ ./mvnw clean install -DskipTests=true
> >> > > >>>>>>
> >> > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get
> >> it
> >> > to
> >> > > >> have
> >> > > >>>>>> successful build:
> >> > > >>>>>>
> >> > > >>>>>> W: Output path
> >> > > >>>>>>
> >> > > >>>>
> >> > > >>
> >> >
> >>
> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> >> > > >>>>>> intersects with a source root. Only files that were created
> by
> >> > build
> >> > > >>>> will
> >> > > >>>>>> be cleaned
> >> > > >>>>>> W: Output path
> >> > > >>>>>>
> >> > > >>>>
> >> > > >>
> >> >
> >>
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> >> > > >>>>>> intersects with a source root. Only files that were created
> by
> >> > build
> >> > > >>>> will
> >> > > >>>>>> be cleaned
> >> > > >>>>>> W: Output path
> >> > > >>>>>>
> >> > > >>>>
> >> > > >>
> >> >
> >>
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> >> > > >>>>>> intersects with a source root. Only files that were created
> by
> >> > build
> >> > > >>>> will
> >> > > >>>>>> be cleaned
> >> > > >>>>>> W: Output path
> >> > > >>>>>>
> >> > > >>>>
> >> > > >>
> >> >
> >>
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> >> > > >>>>>> intersects with a source root. Only files that were created
> by
> >> > build
> >> > > >>>> will
> >> > > >>>>>> be cleaned
> >> > > >>>>>> W: Output path
> >> > > >>>>>>
> >> > > >>>>
> >> > > >>
> >> >
> >>
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> >> > > >>>>>> intersects with a source root. Only files that were created
> by
> >> > build
> >> > > >>>> will
> >> > > >>>>>> be cleaned
> >> > > >>>>>> W: Output path
> >> > > >>>>>>
> >> > > >>>>
> >> > > >>
> >> >
> >>
> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> >> > > >>>>>> intersects with a source root. Only files that were created
> by
> >> > build
> >> > > >>>> will
> >> > > >>>>>> be cleaned
> >> > > >>>>>> W: Output path
> >> > > >>>>>>
> >> > > >>>>
> >> > > >>
> >> >
> >>
> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> >> > > >>>>>> intersects with a source root. Only files that were created
> by
> >> > build
> >> > > >>>> will
> >> > > >>>>>> be cleaned
> >> > > >>>>>>
> >> > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
> because
> >> > it is
> >> > > >>>>>> included into a circular dependency (module 'log4j-api'
> >> > production,
> >> > > >>>>>> maven-annotations-production:log4j-api, module
> 'log4j-plugins'
> >> > > >>>> production,
> >> > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
> >> > > >>>>>> maven-annotations-test:log4j-plugins because it is included
> >> into a
> >> > > >>>> circular
> >> > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
> >> > 'log4j-api'
> >> > > >>>> tests,
> >> > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
> >> tests)*
> >> > > >>>>>>
> >> > > >>>>>> Did you get it working? What shall I do to make it work?
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>
> >> > > >>>>
> >> > > >>>>
> >> > > >>
> >> > > >>
> >> > > >>
> >> > >
> >> > >
> >> >
> >>
> >
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Tim Perry <ti...@gmail.com>.
I deleted all log4j artifacts in my .m2 directory and I'm no longer getting
the "circular dependency" that Volkan reported.
I checked the box for "Delegate IDE build/run actions to Maven" like Matt
recommended and was able to build which went as far as maven on the command
line does.
Now I'm trying to run a unit test by clicking the arrow next to the test
and saying run. However, IntelliJ starts a maven build and runs all the
tests for log4j-core (which contains the test I am trying to run).
Ideas?
Thanks,
Tim
On Mon, Apr 19, 2021 at 3:34 PM Tim Perry <ti...@gmail.com> wrote:
> Can any of you recommend an idiots guide to setting up a log4j development
> environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
> work with a maven project with multiple module-info.java files. There are
> bugs into the maven-eclipse tools (m2e) for this.
>
> I cannot see reverting to 1999 and using the command line debugger, so
> IntelliJ seems like my best shot at getting a working development
> environment. I just want autocomplete and the ability to connect a debugger
> without too much hoop jumping.
>
> Thanks,
> Tim
>
> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
> wrote:
>
>> I have also tried that too, but no luck so far. @Matt, are you able to run
>> any tests from IDEA using the most recent "master"?
>>
>> On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
>>
>> > See also
>> >
>> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
>> >
>> > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
>> > wrote:
>> > >
>> > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
>> debug
>> > options”
>> > >
>> > > Ralph
>> > >
>> > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <vo...@gmail.com>
>> > wrote:
>> > > >
>> > > > Okay, fair enough. Thanks so much for sharing these details, I
>> really
>> > > > appreciated it. One final question: If you want to debug a single
>> > test, how
>> > > > does your work flow look like? Do you create a new "Run
>> Configuration"
>> > > > invoking a certain Maven command triggering the code/test that you
>> are
>> > > > interested in and "Debug Run"ing that "Run Configuration"?
>> > > >
>> > > > For the records, I still would like to hear how I can make IDEA to
>> > simply
>> > > > run a test. If anybody has succeeded in doing that, I am all ears.
>> > > >
>> > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <ra...@dslextreme.com>
>> > wrote:
>> > > >>
>> > > >> I will be honest. I have never tun any log4j tests in IntelliJ. I
>> > rarely
>> > > >> do it for any projects I work on. I use JVM remote debug all the
>> > time. I
>> > > >> don’t want to force others to have to do that, but I just never
>> think
>> > about
>> > > >> it.
>> > > >>
>> > > >> I use various versions of Maven from time to time. 3.6.1 is the
>> > default on
>> > > >> my Mac but I just installed 3.8.1 to validate what I needed to
>> change
>> > in my
>> > > >> setup to make it still work with my employers Nexus repository
>> which
>> > still
>> > > >> uses http.
>> > > >>
>> > > >> When I am working on Log4J stuff I do a full mvn clean install
>> several
>> > > >> times a day. That takes a huge amount of time so I have learned to
>> > > >> multitask and work on other stuff while builds are running.
>> > > >>
>> > > >> Ralph.
>> > > >>
>> > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
>> volkan.yazici@gmail.com>
>> > > >> wrote:
>> > > >>>
>> > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
>> *.iml
>> > > >> files
>> > > >>> and .idea directory), compile the sources via Maven, and open the
>> > folder
>> > > >> in
>> > > >>> IDEA, can you run *any* tests? If so, do you have any custom IDEA
>> > > >>> configurations? Which IDEA version are you using? If you are not
>> > using
>> > > >> the
>> > > >>> wrapper, which Maven version are you using?
>> > > >>>
>> > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
>> > > >>> environments, independent of my local setup. It also saves you
>> from a
>> > > >> local
>> > > >>> Maven dependency.
>> > > >>>
>> > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
>> > ralph.goers@dslextreme.com>
>> > > >>>> wrote:
>> > > >>>>
>> > > >>>> I deleted the files from my local repo and restarted the build.
>> It
>> > is
>> > > >>>> running along just fine - at least until it hits json template
>> > layout.
>> > > >>>>
>> > > >>>> Is there a reason you use the maven wrapper instead of Maven
>> > itself? I
>> > > >>>> have never used the wrapper. I am wondering if there is something
>> > going
>> > > >> on
>> > > >>>> there.
>> > > >>>>
>> > > >>>> Ralph
>> > > >>>>
>> > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
>> > ralph.goers@dslextreme.com>
>> > > >>>> wrote:
>> > > >>>>>
>> > > >>>>> I’ve never seen that. What is
>> > maven-annotations-production:log4j-api?
>> > > >>>>>
>> > > >>>>> Let me try removing the files from my maven local repo as you
>> did.
>> > > >>>>>
>> > > >>>>> Ralph
>> > > >>>>>
>> > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
>> > volkan.yazici@gmail.com>
>> > > >>>> wrote:
>> > > >>>>>>
>> > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
>> after
>> > > >> Java
>> > > >>>> 11
>> > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
>> clean
>> > > >> Maven
>> > > >>>>>> build:
>> > > >>>>>>
>> > > >>>>>> $ rm -rf ./.idea ./**/*.iml
>> > > >>>>>> $ rm -rf
>> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>> > > >>>>>> $ ./mvnw clean install -DskipTests=true
>> > > >>>>>>
>> > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get
>> it
>> > to
>> > > >> have
>> > > >>>>>> successful build:
>> > > >>>>>>
>> > > >>>>>> W: Output path
>> > > >>>>>>
>> > > >>>>
>> > > >>
>> >
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>> > > >>>>>> intersects with a source root. Only files that were created by
>> > build
>> > > >>>> will
>> > > >>>>>> be cleaned
>> > > >>>>>> W: Output path
>> > > >>>>>>
>> > > >>>>
>> > > >>
>> >
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>> > > >>>>>> intersects with a source root. Only files that were created by
>> > build
>> > > >>>> will
>> > > >>>>>> be cleaned
>> > > >>>>>> W: Output path
>> > > >>>>>>
>> > > >>>>
>> > > >>
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>> > > >>>>>> intersects with a source root. Only files that were created by
>> > build
>> > > >>>> will
>> > > >>>>>> be cleaned
>> > > >>>>>> W: Output path
>> > > >>>>>>
>> > > >>>>
>> > > >>
>> >
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>> > > >>>>>> intersects with a source root. Only files that were created by
>> > build
>> > > >>>> will
>> > > >>>>>> be cleaned
>> > > >>>>>> W: Output path
>> > > >>>>>>
>> > > >>>>
>> > > >>
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>> > > >>>>>> intersects with a source root. Only files that were created by
>> > build
>> > > >>>> will
>> > > >>>>>> be cleaned
>> > > >>>>>> W: Output path
>> > > >>>>>>
>> > > >>>>
>> > > >>
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>> > > >>>>>> intersects with a source root. Only files that were created by
>> > build
>> > > >>>> will
>> > > >>>>>> be cleaned
>> > > >>>>>> W: Output path
>> > > >>>>>>
>> > > >>>>
>> > > >>
>> >
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>> > > >>>>>> intersects with a source root. Only files that were created by
>> > build
>> > > >>>> will
>> > > >>>>>> be cleaned
>> > > >>>>>>
>> > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api because
>> > it is
>> > > >>>>>> included into a circular dependency (module 'log4j-api'
>> > production,
>> > > >>>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
>> > > >>>> production,
>> > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
>> > > >>>>>> maven-annotations-test:log4j-plugins because it is included
>> into a
>> > > >>>> circular
>> > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
>> > 'log4j-api'
>> > > >>>> tests,
>> > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
>> tests)*
>> > > >>>>>>
>> > > >>>>>> Did you get it working? What shall I do to make it work?
>> > > >>>>>
>> > > >>>>>
>> > > >>>>>
>> > > >>>>
>> > > >>>>
>> > > >>>>
>> > > >>
>> > > >>
>> > > >>
>> > >
>> > >
>> >
>>
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
Send me a link imma let Nemesis kill it
On Mon, Apr 19, 2021, 6:34 PM Tim Perry <ti...@gmail.com> wrote:
> Can any of you recommend an idiots guide to setting up a log4j development
> environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
> work with a maven project with multiple module-info.java files. There are
> bugs into the maven-eclipse tools (m2e) for this.
>
> I cannot see reverting to 1999 and using the command line debugger, so
> IntelliJ seems like my best shot at getting a working development
> environment. I just want autocomplete and the ability to connect a debugger
> without too much hoop jumping.
>
> Thanks,
> Tim
>
> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
> wrote:
>
> > I have also tried that too, but no luck so far. @Matt, are you able to
> run
> > any tests from IDEA using the most recent "master"?
> >
> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
> >
> > > See also
> > >
> >
> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
> > >
> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
> > > wrote:
> > > >
> > > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
> debug
> > > options”
> > > >
> > > > Ralph
> > > >
> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <volkan.yazici@gmail.com
> >
> > > wrote:
> > > > >
> > > > > Okay, fair enough. Thanks so much for sharing these details, I
> > really
> > > > > appreciated it. One final question: If you want to debug a single
> > > test, how
> > > > > does your work flow look like? Do you create a new "Run
> > Configuration"
> > > > > invoking a certain Maven command triggering the code/test that you
> > are
> > > > > interested in and "Debug Run"ing that "Run Configuration"?
> > > > >
> > > > > For the records, I still would like to hear how I can make IDEA to
> > > simply
> > > > > run a test. If anybody has succeeded in doing that, I am all ears.
> > > > >
> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <ralph.goers@dslextreme.com
> >
> > > wrote:
> > > > >>
> > > > >> I will be honest. I have never tun any log4j tests in IntelliJ. I
> > > rarely
> > > > >> do it for any projects I work on. I use JVM remote debug all the
> > > time. I
> > > > >> don’t want to force others to have to do that, but I just never
> > think
> > > about
> > > > >> it.
> > > > >>
> > > > >> I use various versions of Maven from time to time. 3.6.1 is the
> > > default on
> > > > >> my Mac but I just installed 3.8.1 to validate what I needed to
> > change
> > > in my
> > > > >> setup to make it still work with my employers Nexus repository
> which
> > > still
> > > > >> uses http.
> > > > >>
> > > > >> When I am working on Log4J stuff I do a full mvn clean install
> > several
> > > > >> times a day. That takes a huge amount of time so I have learned to
> > > > >> multitask and work on other stuff while builds are running.
> > > > >>
> > > > >> Ralph.
> > > > >>
> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
> > volkan.yazici@gmail.com>
> > > > >> wrote:
> > > > >>>
> > > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
> > *.iml
> > > > >> files
> > > > >>> and .idea directory), compile the sources via Maven, and open the
> > > folder
> > > > >> in
> > > > >>> IDEA, can you run *any* tests? If so, do you have any custom IDEA
> > > > >>> configurations? Which IDEA version are you using? If you are not
> > > using
> > > > >> the
> > > > >>> wrapper, which Maven version are you using?
> > > > >>>
> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
> > > > >>> environments, independent of my local setup. It also saves you
> > from a
> > > > >> local
> > > > >>> Maven dependency.
> > > > >>>
> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
> > > ralph.goers@dslextreme.com>
> > > > >>>> wrote:
> > > > >>>>
> > > > >>>> I deleted the files from my local repo and restarted the build.
> It
> > > is
> > > > >>>> running along just fine - at least until it hits json template
> > > layout.
> > > > >>>>
> > > > >>>> Is there a reason you use the maven wrapper instead of Maven
> > > itself? I
> > > > >>>> have never used the wrapper. I am wondering if there is
> something
> > > going
> > > > >> on
> > > > >>>> there.
> > > > >>>>
> > > > >>>> Ralph
> > > > >>>>
> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
> > > ralph.goers@dslextreme.com>
> > > > >>>> wrote:
> > > > >>>>>
> > > > >>>>> I’ve never seen that. What is
> > > maven-annotations-production:log4j-api?
> > > > >>>>>
> > > > >>>>> Let me try removing the files from my maven local repo as you
> > did.
> > > > >>>>>
> > > > >>>>> Ralph
> > > > >>>>>
> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
> > > volkan.yazici@gmail.com>
> > > > >>>> wrote:
> > > > >>>>>>
> > > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
> > after
> > > > >> Java
> > > > >>>> 11
> > > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
> > clean
> > > > >> Maven
> > > > >>>>>> build:
> > > > >>>>>>
> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
> > > > >>>>>> $ rm -rf
> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
> > > > >>>>>>
> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get
> it
> > > to
> > > > >> have
> > > > >>>>>> successful build:
> > > > >>>>>>
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>>
> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
> because
> > > it is
> > > > >>>>>> included into a circular dependency (module 'log4j-api'
> > > production,
> > > > >>>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
> > > > >>>> production,
> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
> > > > >>>>>> maven-annotations-test:log4j-plugins because it is included
> > into a
> > > > >>>> circular
> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
> > > 'log4j-api'
> > > > >>>> tests,
> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
> tests)*
> > > > >>>>>>
> > > > >>>>>> Did you get it working? What shall I do to make it work?
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
Folderview and property management services in this 👌 area only
[[Pw.bypass://drive.google.com/folderview definitely==the official
APACHE.ORGANIZATIONSANOT(b)B?id=10aeozYtW231Wecpq4GNB94RrpLYLQpGM]]\¤hostinghaul
log4jdevelopment_github_discord_duoapplewebkit>
Relay attack for passive entry passive start (PEPS) vehicle security
systematic==shell start (PEPS) vehicle security
system=DEACTIVATED-attack-on the system. The system includes Onbrand24.c
ultra (apen) edibles and kill to transmit a request pulse at tower. A
mobilesecurity@gi-de.com blockbuster, mit in a MIT.migAUTOtizable image
such-and-such as a result a reply pulse in response to the
{{\~¤requested¤¤}}is configured to ♧ and releases boucle apen on a time
interval hook the apen apex blockbuster The controller shutdown interval
Images (💫
TASKERT (12)
6)
Classifications
DeadWorldwide exceptions host.domain@logging.apache.org _official
\¤~¤¤~¤~¤♧\¤~~PROMPTING_PHOTOS-PROMPT-202004A authentication root trapped
😢 😀 FORCE REQUIREMENT. Hooked increases in logjam and more ultra wideband
transceivers shutdown and then deploy buglock for more ultra
>>>>>>>>>🤭😙🤫🤔🤐🙃🙂🙃🙂🙃🙂🤖🤗🤪🤑😴>\🤜♧🤝¤hook🤳🦴🦴🦴🙏🦿🦴🦴🤏💫💫💫toastonbrand24.icims¤🤩😴😴😴😷😷😷🤒🤒🤒🤒🥵🥵🥵🥵🤮🤮🤮🤮🤮🤯🤯😱😱😱😱☠☠👾👻💥💤👋👎🧠🦴🦴🦴🤷♀️🤷♀️🤦♂️👨💻👩💻🧟♂️🧟♀️💇♀️💇♂️💆♀️💆♂️🧞♂️👳♂️😅🙋♀️🙋♂️🤳🦴🤝👏🤛]]✌🙈🙉🙊😭🤐🤭🤫🤫🤫💫
On Mon, Apr 19, 2021, 6:49 PM Sixx XT <si...@gmail.com> wrote:
> These are all the tricks that they done I'm going to send you my entire
> note script okay runoff that no scripted I'm about to send you
>
> On Mon, Apr 19, 2021, 6:34 PM Tim Perry <ti...@gmail.com> wrote:
>
>> Can any of you recommend an idiots guide to setting up a log4j development
>> environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
>> work with a maven project with multiple module-info.java files. There are
>> bugs into the maven-eclipse tools (m2e) for this.
>>
>> I cannot see reverting to 1999 and using the command line debugger, so
>> IntelliJ seems like my best shot at getting a working development
>> environment. I just want autocomplete and the ability to connect a
>> debugger
>> without too much hoop jumping.
>>
>> Thanks,
>> Tim
>>
>> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
>> wrote:
>>
>> > I have also tried that too, but no luck so far. @Matt, are you able to
>> run
>> > any tests from IDEA using the most recent "master"?
>> >
>> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
>> >
>> > > See also
>> > >
>> >
>> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
>> > >
>> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
>> > > wrote:
>> > > >
>> > > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
>> debug
>> > > options”
>> > > >
>> > > > Ralph
>> > > >
>> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <
>> volkan.yazici@gmail.com>
>> > > wrote:
>> > > > >
>> > > > > Okay, fair enough. Thanks so much for sharing these details, I
>> > really
>> > > > > appreciated it. One final question: If you want to debug a single
>> > > test, how
>> > > > > does your work flow look like? Do you create a new "Run
>> > Configuration"
>> > > > > invoking a certain Maven command triggering the code/test that you
>> > are
>> > > > > interested in and "Debug Run"ing that "Run Configuration"?
>> > > > >
>> > > > > For the records, I still would like to hear how I can make IDEA to
>> > > simply
>> > > > > run a test. If anybody has succeeded in doing that, I am all ears.
>> > > > >
>> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <
>> ralph.goers@dslextreme.com>
>> > > wrote:
>> > > > >>
>> > > > >> I will be honest. I have never tun any log4j tests in IntelliJ. I
>> > > rarely
>> > > > >> do it for any projects I work on. I use JVM remote debug all the
>> > > time. I
>> > > > >> don’t want to force others to have to do that, but I just never
>> > think
>> > > about
>> > > > >> it.
>> > > > >>
>> > > > >> I use various versions of Maven from time to time. 3.6.1 is the
>> > > default on
>> > > > >> my Mac but I just installed 3.8.1 to validate what I needed to
>> > change
>> > > in my
>> > > > >> setup to make it still work with my employers Nexus repository
>> which
>> > > still
>> > > > >> uses http.
>> > > > >>
>> > > > >> When I am working on Log4J stuff I do a full mvn clean install
>> > several
>> > > > >> times a day. That takes a huge amount of time so I have learned
>> to
>> > > > >> multitask and work on other stuff while builds are running.
>> > > > >>
>> > > > >> Ralph.
>> > > > >>
>> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
>> > volkan.yazici@gmail.com>
>> > > > >> wrote:
>> > > > >>>
>> > > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
>> > *.iml
>> > > > >> files
>> > > > >>> and .idea directory), compile the sources via Maven, and open
>> the
>> > > folder
>> > > > >> in
>> > > > >>> IDEA, can you run *any* tests? If so, do you have any custom
>> IDEA
>> > > > >>> configurations? Which IDEA version are you using? If you are not
>> > > using
>> > > > >> the
>> > > > >>> wrapper, which Maven version are you using?
>> > > > >>>
>> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
>> > > > >>> environments, independent of my local setup. It also saves you
>> > from a
>> > > > >> local
>> > > > >>> Maven dependency.
>> > > > >>>
>> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
>> > > ralph.goers@dslextreme.com>
>> > > > >>>> wrote:
>> > > > >>>>
>> > > > >>>> I deleted the files from my local repo and restarted the
>> build. It
>> > > is
>> > > > >>>> running along just fine - at least until it hits json template
>> > > layout.
>> > > > >>>>
>> > > > >>>> Is there a reason you use the maven wrapper instead of Maven
>> > > itself? I
>> > > > >>>> have never used the wrapper. I am wondering if there is
>> something
>> > > going
>> > > > >> on
>> > > > >>>> there.
>> > > > >>>>
>> > > > >>>> Ralph
>> > > > >>>>
>> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
>> > > ralph.goers@dslextreme.com>
>> > > > >>>> wrote:
>> > > > >>>>>
>> > > > >>>>> I’ve never seen that. What is
>> > > maven-annotations-production:log4j-api?
>> > > > >>>>>
>> > > > >>>>> Let me try removing the files from my maven local repo as you
>> > did.
>> > > > >>>>>
>> > > > >>>>> Ralph
>> > > > >>>>>
>> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
>> > > volkan.yazici@gmail.com>
>> > > > >>>> wrote:
>> > > > >>>>>>
>> > > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
>> > after
>> > > > >> Java
>> > > > >>>> 11
>> > > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
>> > clean
>> > > > >> Maven
>> > > > >>>>>> build:
>> > > > >>>>>>
>> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
>> > > > >>>>>> $ rm -rf
>> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
>> > > > >>>>>>
>> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't
>> get it
>> > > to
>> > > > >> have
>> > > > >>>>>> successful build:
>> > > > >>>>>>
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>>
>> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
>> because
>> > > it is
>> > > > >>>>>> included into a circular dependency (module 'log4j-api'
>> > > production,
>> > > > >>>>>> maven-annotations-production:log4j-api, module
>> 'log4j-plugins'
>> > > > >>>> production,
>> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
>> > > > >>>>>> maven-annotations-test:log4j-plugins because it is included
>> > into a
>> > > > >>>> circular
>> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
>> > > 'log4j-api'
>> > > > >>>> tests,
>> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
>> tests)*
>> > > > >>>>>>
>> > > > >>>>>> Did you get it working? What shall I do to make it work?
>> > > > >>>>>
>> > > > >>>>>
>> > > > >>>>>
>> > > > >>>>
>> > > > >>>>
>> > > > >>>>
>> > > > >>
>> > > > >>
>> > > > >>
>> > > >
>> > > >
>> > >
>> >
>>
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
These are all the tricks that they done I'm going to send you my entire
note script okay runoff that no scripted I'm about to send you
On Mon, Apr 19, 2021, 6:34 PM Tim Perry <ti...@gmail.com> wrote:
> Can any of you recommend an idiots guide to setting up a log4j development
> environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
> work with a maven project with multiple module-info.java files. There are
> bugs into the maven-eclipse tools (m2e) for this.
>
> I cannot see reverting to 1999 and using the command line debugger, so
> IntelliJ seems like my best shot at getting a working development
> environment. I just want autocomplete and the ability to connect a debugger
> without too much hoop jumping.
>
> Thanks,
> Tim
>
> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
> wrote:
>
> > I have also tried that too, but no luck so far. @Matt, are you able to
> run
> > any tests from IDEA using the most recent "master"?
> >
> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
> >
> > > See also
> > >
> >
> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
> > >
> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
> > > wrote:
> > > >
> > > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
> debug
> > > options”
> > > >
> > > > Ralph
> > > >
> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <volkan.yazici@gmail.com
> >
> > > wrote:
> > > > >
> > > > > Okay, fair enough. Thanks so much for sharing these details, I
> > really
> > > > > appreciated it. One final question: If you want to debug a single
> > > test, how
> > > > > does your work flow look like? Do you create a new "Run
> > Configuration"
> > > > > invoking a certain Maven command triggering the code/test that you
> > are
> > > > > interested in and "Debug Run"ing that "Run Configuration"?
> > > > >
> > > > > For the records, I still would like to hear how I can make IDEA to
> > > simply
> > > > > run a test. If anybody has succeeded in doing that, I am all ears.
> > > > >
> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <ralph.goers@dslextreme.com
> >
> > > wrote:
> > > > >>
> > > > >> I will be honest. I have never tun any log4j tests in IntelliJ. I
> > > rarely
> > > > >> do it for any projects I work on. I use JVM remote debug all the
> > > time. I
> > > > >> don’t want to force others to have to do that, but I just never
> > think
> > > about
> > > > >> it.
> > > > >>
> > > > >> I use various versions of Maven from time to time. 3.6.1 is the
> > > default on
> > > > >> my Mac but I just installed 3.8.1 to validate what I needed to
> > change
> > > in my
> > > > >> setup to make it still work with my employers Nexus repository
> which
> > > still
> > > > >> uses http.
> > > > >>
> > > > >> When I am working on Log4J stuff I do a full mvn clean install
> > several
> > > > >> times a day. That takes a huge amount of time so I have learned to
> > > > >> multitask and work on other stuff while builds are running.
> > > > >>
> > > > >> Ralph.
> > > > >>
> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
> > volkan.yazici@gmail.com>
> > > > >> wrote:
> > > > >>>
> > > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
> > *.iml
> > > > >> files
> > > > >>> and .idea directory), compile the sources via Maven, and open the
> > > folder
> > > > >> in
> > > > >>> IDEA, can you run *any* tests? If so, do you have any custom IDEA
> > > > >>> configurations? Which IDEA version are you using? If you are not
> > > using
> > > > >> the
> > > > >>> wrapper, which Maven version are you using?
> > > > >>>
> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
> > > > >>> environments, independent of my local setup. It also saves you
> > from a
> > > > >> local
> > > > >>> Maven dependency.
> > > > >>>
> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
> > > ralph.goers@dslextreme.com>
> > > > >>>> wrote:
> > > > >>>>
> > > > >>>> I deleted the files from my local repo and restarted the build.
> It
> > > is
> > > > >>>> running along just fine - at least until it hits json template
> > > layout.
> > > > >>>>
> > > > >>>> Is there a reason you use the maven wrapper instead of Maven
> > > itself? I
> > > > >>>> have never used the wrapper. I am wondering if there is
> something
> > > going
> > > > >> on
> > > > >>>> there.
> > > > >>>>
> > > > >>>> Ralph
> > > > >>>>
> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
> > > ralph.goers@dslextreme.com>
> > > > >>>> wrote:
> > > > >>>>>
> > > > >>>>> I’ve never seen that. What is
> > > maven-annotations-production:log4j-api?
> > > > >>>>>
> > > > >>>>> Let me try removing the files from my maven local repo as you
> > did.
> > > > >>>>>
> > > > >>>>> Ralph
> > > > >>>>>
> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
> > > volkan.yazici@gmail.com>
> > > > >>>> wrote:
> > > > >>>>>>
> > > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
> > after
> > > > >> Java
> > > > >>>> 11
> > > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
> > clean
> > > > >> Maven
> > > > >>>>>> build:
> > > > >>>>>>
> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
> > > > >>>>>> $ rm -rf
> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
> > > > >>>>>>
> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get
> it
> > > to
> > > > >> have
> > > > >>>>>> successful build:
> > > > >>>>>>
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>>
> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
> because
> > > it is
> > > > >>>>>> included into a circular dependency (module 'log4j-api'
> > > production,
> > > > >>>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
> > > > >>>> production,
> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
> > > > >>>>>> maven-annotations-test:log4j-plugins because it is included
> > into a
> > > > >>>> circular
> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
> > > 'log4j-api'
> > > > >>>> tests,
> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
> tests)*
> > > > >>>>>>
> > > > >>>>>> Did you get it working? What shall I do to make it work?
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
I got to change the permissions from a root identified as equal to A ROOT
AND B NOBODY CODE 9999
On Tue, Apr 20, 2021, 10:14 AM Sixx XT <si...@gmail.com> wrote:
> They are being thrown down its steady
>
> On Tue, Apr 20, 2021, 10:11 AM Sixx XT <si...@gmail.com> wrote:
>
>> Network speed showing they getting the fwd
>>
>> On Tue, Apr 20, 2021, 10:10 AM Sixx XT <si...@gmail.com> wrote:
>>
>>> Took the permissions off and filed boots read
>>>
>>> On Tue, Apr 20, 2021, 10:03 AM Sixx XT <si...@gmail.com> wrote:
>>>
>>>> He has everything auto forwarding if I put it on Nemesis he's toast
>>>>
>>>> On Tue, Apr 20, 2021, 9:59 AM Sixx XT <si...@gmail.com> wrote:
>>>>
>>>>> Ok this what imma do u guys give me a download of sdk apk android mac
>>>>> window's every volume
>>>>>
>>>>> On Mon, Apr 19, 2021, 6:34 PM Tim Perry <ti...@gmail.com> wrote:
>>>>>
>>>>>> Can any of you recommend an idiots guide to setting up a log4j
>>>>>> development
>>>>>> environment in IntelliJ? I have never used IntelliJ before. Eclipse
>>>>>> won't
>>>>>> work with a maven project with multiple module-info.java files. There
>>>>>> are
>>>>>> bugs into the maven-eclipse tools (m2e) for this.
>>>>>>
>>>>>> I cannot see reverting to 1999 and using the command line debugger, so
>>>>>> IntelliJ seems like my best shot at getting a working development
>>>>>> environment. I just want autocomplete and the ability to connect a
>>>>>> debugger
>>>>>> without too much hoop jumping.
>>>>>>
>>>>>> Thanks,
>>>>>> Tim
>>>>>>
>>>>>> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <volkan.yazici@gmail.com
>>>>>> >
>>>>>> wrote:
>>>>>>
>>>>>> > I have also tried that too, but no luck so far. @Matt, are you able
>>>>>> to run
>>>>>> > any tests from IDEA using the most recent "master"?
>>>>>> >
>>>>>> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com>
>>>>>> wrote:
>>>>>> >
>>>>>> > > See also
>>>>>> > >
>>>>>> >
>>>>>> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
>>>>>> > >
>>>>>> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <
>>>>>> ralph.goers@dslextreme.com>
>>>>>> > > wrote:
>>>>>> > > >
>>>>>> > > > mvn surefire:test -Dtest=TestClass
>>>>>> -Dmaven.surefire.debug=“remote debug
>>>>>> > > options”
>>>>>> > > >
>>>>>> > > > Ralph
>>>>>> > > >
>>>>>> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <
>>>>>> volkan.yazici@gmail.com>
>>>>>> > > wrote:
>>>>>> > > > >
>>>>>> > > > > Okay, fair enough. Thanks so much for sharing these details,
>>>>>> I
>>>>>> > really
>>>>>> > > > > appreciated it. One final question: If you want to debug a
>>>>>> single
>>>>>> > > test, how
>>>>>> > > > > does your work flow look like? Do you create a new "Run
>>>>>> > Configuration"
>>>>>> > > > > invoking a certain Maven command triggering the code/test
>>>>>> that you
>>>>>> > are
>>>>>> > > > > interested in and "Debug Run"ing that "Run Configuration"?
>>>>>> > > > >
>>>>>> > > > > For the records, I still would like to hear how I can make
>>>>>> IDEA to
>>>>>> > > simply
>>>>>> > > > > run a test. If anybody has succeeded in doing that, I am all
>>>>>> ears.
>>>>>> > > > >
>>>>>> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <
>>>>>> ralph.goers@dslextreme.com>
>>>>>> > > wrote:
>>>>>> > > > >>
>>>>>> > > > >> I will be honest. I have never tun any log4j tests in
>>>>>> IntelliJ. I
>>>>>> > > rarely
>>>>>> > > > >> do it for any projects I work on. I use JVM remote debug all
>>>>>> the
>>>>>> > > time. I
>>>>>> > > > >> don’t want to force others to have to do that, but I just
>>>>>> never
>>>>>> > think
>>>>>> > > about
>>>>>> > > > >> it.
>>>>>> > > > >>
>>>>>> > > > >> I use various versions of Maven from time to time. 3.6.1 is
>>>>>> the
>>>>>> > > default on
>>>>>> > > > >> my Mac but I just installed 3.8.1 to validate what I needed
>>>>>> to
>>>>>> > change
>>>>>> > > in my
>>>>>> > > > >> setup to make it still work with my employers Nexus
>>>>>> repository which
>>>>>> > > still
>>>>>> > > > >> uses http.
>>>>>> > > > >>
>>>>>> > > > >> When I am working on Log4J stuff I do a full mvn clean
>>>>>> install
>>>>>> > several
>>>>>> > > > >> times a day. That takes a huge amount of time so I have
>>>>>> learned to
>>>>>> > > > >> multitask and work on other stuff while builds are running.
>>>>>> > > > >>
>>>>>> > > > >> Ralph.
>>>>>> > > > >>
>>>>>> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
>>>>>> > volkan.yazici@gmail.com>
>>>>>> > > > >> wrote:
>>>>>> > > > >>>
>>>>>> > > > >>> Ralph, when you delete the IDEA-specific configuration
>>>>>> (i.e.,
>>>>>> > *.iml
>>>>>> > > > >> files
>>>>>> > > > >>> and .idea directory), compile the sources via Maven, and
>>>>>> open the
>>>>>> > > folder
>>>>>> > > > >> in
>>>>>> > > > >>> IDEA, can you run *any* tests? If so, do you have any
>>>>>> custom IDEA
>>>>>> > > > >>> configurations? Which IDEA version are you using? If you
>>>>>> are not
>>>>>> > > using
>>>>>> > > > >> the
>>>>>> > > > >>> wrapper, which Maven version are you using?
>>>>>> > > > >>>
>>>>>> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in
>>>>>> all
>>>>>> > > > >>> environments, independent of my local setup. It also saves
>>>>>> you
>>>>>> > from a
>>>>>> > > > >> local
>>>>>> > > > >>> Maven dependency.
>>>>>> > > > >>>
>>>>>> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
>>>>>> > > ralph.goers@dslextreme.com>
>>>>>> > > > >>>> wrote:
>>>>>> > > > >>>>
>>>>>> > > > >>>> I deleted the files from my local repo and restarted the
>>>>>> build. It
>>>>>> > > is
>>>>>> > > > >>>> running along just fine - at least until it hits json
>>>>>> template
>>>>>> > > layout.
>>>>>> > > > >>>>
>>>>>> > > > >>>> Is there a reason you use the maven wrapper instead of
>>>>>> Maven
>>>>>> > > itself? I
>>>>>> > > > >>>> have never used the wrapper. I am wondering if there is
>>>>>> something
>>>>>> > > going
>>>>>> > > > >> on
>>>>>> > > > >>>> there.
>>>>>> > > > >>>>
>>>>>> > > > >>>> Ralph
>>>>>> > > > >>>>
>>>>>> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
>>>>>> > > ralph.goers@dslextreme.com>
>>>>>> > > > >>>> wrote:
>>>>>> > > > >>>>>
>>>>>> > > > >>>>> I’ve never seen that. What is
>>>>>> > > maven-annotations-production:log4j-api?
>>>>>> > > > >>>>>
>>>>>> > > > >>>>> Let me try removing the files from my maven local repo as
>>>>>> you
>>>>>> > did.
>>>>>> > > > >>>>>
>>>>>> > > > >>>>> Ralph
>>>>>> > > > >>>>>
>>>>>> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
>>>>>> > > volkan.yazici@gmail.com>
>>>>>> > > > >>>> wrote:
>>>>>> > > > >>>>>>
>>>>>> > > > >>>>>> As subject hints, I am not able to run tests in IDEA
>>>>>> anymore
>>>>>> > after
>>>>>> > > > >> Java
>>>>>> > > > >>>> 11
>>>>>> > > > >>>>>> upgrade. I have deleted all IDEA related files and
>>>>>> issued a
>>>>>> > clean
>>>>>> > > > >> Maven
>>>>>> > > > >>>>>> build:
>>>>>> > > > >>>>>>
>>>>>> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
>>>>>> > > > >>>>>> $ rm -rf
>>>>>> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>>>>>> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
>>>>>> > > > >>>>>>
>>>>>> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but
>>>>>> couldn't get it
>>>>>> > > to
>>>>>> > > > >> have
>>>>>> > > > >>>>>> successful build:
>>>>>> > > > >>>>>>
>>>>>> > > > >>>>>> W: Output path
>>>>>> > > > >>>>>>
>>>>>> > > > >>>>
>>>>>> > > > >>
>>>>>> > >
>>>>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>>>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>>>> created by
>>>>>> > > build
>>>>>> > > > >>>> will
>>>>>> > > > >>>>>> be cleaned
>>>>>> > > > >>>>>> W: Output path
>>>>>> > > > >>>>>>
>>>>>> > > > >>>>
>>>>>> > > > >>
>>>>>> > >
>>>>>> >
>>>>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>>>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>>>> created by
>>>>>> > > build
>>>>>> > > > >>>> will
>>>>>> > > > >>>>>> be cleaned
>>>>>> > > > >>>>>> W: Output path
>>>>>> > > > >>>>>>
>>>>>> > > > >>>>
>>>>>> > > > >>
>>>>>> > >
>>>>>> >
>>>>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>>>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>>>> created by
>>>>>> > > build
>>>>>> > > > >>>> will
>>>>>> > > > >>>>>> be cleaned
>>>>>> > > > >>>>>> W: Output path
>>>>>> > > > >>>>>>
>>>>>> > > > >>>>
>>>>>> > > > >>
>>>>>> > >
>>>>>> >
>>>>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>>>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>>>> created by
>>>>>> > > build
>>>>>> > > > >>>> will
>>>>>> > > > >>>>>> be cleaned
>>>>>> > > > >>>>>> W: Output path
>>>>>> > > > >>>>>>
>>>>>> > > > >>>>
>>>>>> > > > >>
>>>>>> > >
>>>>>> >
>>>>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>>>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>>>> created by
>>>>>> > > build
>>>>>> > > > >>>> will
>>>>>> > > > >>>>>> be cleaned
>>>>>> > > > >>>>>> W: Output path
>>>>>> > > > >>>>>>
>>>>>> > > > >>>>
>>>>>> > > > >>
>>>>>> > >
>>>>>> >
>>>>>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>>>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>>>> created by
>>>>>> > > build
>>>>>> > > > >>>> will
>>>>>> > > > >>>>>> be cleaned
>>>>>> > > > >>>>>> W: Output path
>>>>>> > > > >>>>>>
>>>>>> > > > >>>>
>>>>>> > > > >>
>>>>>> > >
>>>>>> >
>>>>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>>>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>>>> created by
>>>>>> > > build
>>>>>> > > > >>>> will
>>>>>> > > > >>>>>> be cleaned
>>>>>> > > > >>>>>>
>>>>>> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
>>>>>> because
>>>>>> > > it is
>>>>>> > > > >>>>>> included into a circular dependency (module 'log4j-api'
>>>>>> > > production,
>>>>>> > > > >>>>>> maven-annotations-production:log4j-api, module
>>>>>> 'log4j-plugins'
>>>>>> > > > >>>> production,
>>>>>> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot
>>>>>> build
>>>>>> > > > >>>>>> maven-annotations-test:log4j-plugins because it is
>>>>>> included
>>>>>> > into a
>>>>>> > > > >>>> circular
>>>>>> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
>>>>>> > > 'log4j-api'
>>>>>> > > > >>>> tests,
>>>>>> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
>>>>>> tests)*
>>>>>> > > > >>>>>>
>>>>>> > > > >>>>>> Did you get it working? What shall I do to make it work?
>>>>>> > > > >>>>>
>>>>>> > > > >>>>>
>>>>>> > > > >>>>>
>>>>>> > > > >>>>
>>>>>> > > > >>>>
>>>>>> > > > >>>>
>>>>>> > > > >>
>>>>>> > > > >>
>>>>>> > > > >>
>>>>>> > > >
>>>>>> > > >
>>>>>> > >
>>>>>> >
>>>>>>
>>>>>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
They are being thrown down its steady
On Tue, Apr 20, 2021, 10:11 AM Sixx XT <si...@gmail.com> wrote:
> Network speed showing they getting the fwd
>
> On Tue, Apr 20, 2021, 10:10 AM Sixx XT <si...@gmail.com> wrote:
>
>> Took the permissions off and filed boots read
>>
>> On Tue, Apr 20, 2021, 10:03 AM Sixx XT <si...@gmail.com> wrote:
>>
>>> He has everything auto forwarding if I put it on Nemesis he's toast
>>>
>>> On Tue, Apr 20, 2021, 9:59 AM Sixx XT <si...@gmail.com> wrote:
>>>
>>>> Ok this what imma do u guys give me a download of sdk apk android mac
>>>> window's every volume
>>>>
>>>> On Mon, Apr 19, 2021, 6:34 PM Tim Perry <ti...@gmail.com> wrote:
>>>>
>>>>> Can any of you recommend an idiots guide to setting up a log4j
>>>>> development
>>>>> environment in IntelliJ? I have never used IntelliJ before. Eclipse
>>>>> won't
>>>>> work with a maven project with multiple module-info.java files. There
>>>>> are
>>>>> bugs into the maven-eclipse tools (m2e) for this.
>>>>>
>>>>> I cannot see reverting to 1999 and using the command line debugger, so
>>>>> IntelliJ seems like my best shot at getting a working development
>>>>> environment. I just want autocomplete and the ability to connect a
>>>>> debugger
>>>>> without too much hoop jumping.
>>>>>
>>>>> Thanks,
>>>>> Tim
>>>>>
>>>>> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> > I have also tried that too, but no luck so far. @Matt, are you able
>>>>> to run
>>>>> > any tests from IDEA using the most recent "master"?
>>>>> >
>>>>> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
>>>>> >
>>>>> > > See also
>>>>> > >
>>>>> >
>>>>> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
>>>>> > >
>>>>> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <
>>>>> ralph.goers@dslextreme.com>
>>>>> > > wrote:
>>>>> > > >
>>>>> > > > mvn surefire:test -Dtest=TestClass
>>>>> -Dmaven.surefire.debug=“remote debug
>>>>> > > options”
>>>>> > > >
>>>>> > > > Ralph
>>>>> > > >
>>>>> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <
>>>>> volkan.yazici@gmail.com>
>>>>> > > wrote:
>>>>> > > > >
>>>>> > > > > Okay, fair enough. Thanks so much for sharing these details, I
>>>>> > really
>>>>> > > > > appreciated it. One final question: If you want to debug a
>>>>> single
>>>>> > > test, how
>>>>> > > > > does your work flow look like? Do you create a new "Run
>>>>> > Configuration"
>>>>> > > > > invoking a certain Maven command triggering the code/test that
>>>>> you
>>>>> > are
>>>>> > > > > interested in and "Debug Run"ing that "Run Configuration"?
>>>>> > > > >
>>>>> > > > > For the records, I still would like to hear how I can make
>>>>> IDEA to
>>>>> > > simply
>>>>> > > > > run a test. If anybody has succeeded in doing that, I am all
>>>>> ears.
>>>>> > > > >
>>>>> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <
>>>>> ralph.goers@dslextreme.com>
>>>>> > > wrote:
>>>>> > > > >>
>>>>> > > > >> I will be honest. I have never tun any log4j tests in
>>>>> IntelliJ. I
>>>>> > > rarely
>>>>> > > > >> do it for any projects I work on. I use JVM remote debug all
>>>>> the
>>>>> > > time. I
>>>>> > > > >> don’t want to force others to have to do that, but I just
>>>>> never
>>>>> > think
>>>>> > > about
>>>>> > > > >> it.
>>>>> > > > >>
>>>>> > > > >> I use various versions of Maven from time to time. 3.6.1 is
>>>>> the
>>>>> > > default on
>>>>> > > > >> my Mac but I just installed 3.8.1 to validate what I needed to
>>>>> > change
>>>>> > > in my
>>>>> > > > >> setup to make it still work with my employers Nexus
>>>>> repository which
>>>>> > > still
>>>>> > > > >> uses http.
>>>>> > > > >>
>>>>> > > > >> When I am working on Log4J stuff I do a full mvn clean install
>>>>> > several
>>>>> > > > >> times a day. That takes a huge amount of time so I have
>>>>> learned to
>>>>> > > > >> multitask and work on other stuff while builds are running.
>>>>> > > > >>
>>>>> > > > >> Ralph.
>>>>> > > > >>
>>>>> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
>>>>> > volkan.yazici@gmail.com>
>>>>> > > > >> wrote:
>>>>> > > > >>>
>>>>> > > > >>> Ralph, when you delete the IDEA-specific configuration
>>>>> (i.e.,
>>>>> > *.iml
>>>>> > > > >> files
>>>>> > > > >>> and .idea directory), compile the sources via Maven, and
>>>>> open the
>>>>> > > folder
>>>>> > > > >> in
>>>>> > > > >>> IDEA, can you run *any* tests? If so, do you have any custom
>>>>> IDEA
>>>>> > > > >>> configurations? Which IDEA version are you using? If you are
>>>>> not
>>>>> > > using
>>>>> > > > >> the
>>>>> > > > >>> wrapper, which Maven version are you using?
>>>>> > > > >>>
>>>>> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in
>>>>> all
>>>>> > > > >>> environments, independent of my local setup. It also saves
>>>>> you
>>>>> > from a
>>>>> > > > >> local
>>>>> > > > >>> Maven dependency.
>>>>> > > > >>>
>>>>> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
>>>>> > > ralph.goers@dslextreme.com>
>>>>> > > > >>>> wrote:
>>>>> > > > >>>>
>>>>> > > > >>>> I deleted the files from my local repo and restarted the
>>>>> build. It
>>>>> > > is
>>>>> > > > >>>> running along just fine - at least until it hits json
>>>>> template
>>>>> > > layout.
>>>>> > > > >>>>
>>>>> > > > >>>> Is there a reason you use the maven wrapper instead of Maven
>>>>> > > itself? I
>>>>> > > > >>>> have never used the wrapper. I am wondering if there is
>>>>> something
>>>>> > > going
>>>>> > > > >> on
>>>>> > > > >>>> there.
>>>>> > > > >>>>
>>>>> > > > >>>> Ralph
>>>>> > > > >>>>
>>>>> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
>>>>> > > ralph.goers@dslextreme.com>
>>>>> > > > >>>> wrote:
>>>>> > > > >>>>>
>>>>> > > > >>>>> I’ve never seen that. What is
>>>>> > > maven-annotations-production:log4j-api?
>>>>> > > > >>>>>
>>>>> > > > >>>>> Let me try removing the files from my maven local repo as
>>>>> you
>>>>> > did.
>>>>> > > > >>>>>
>>>>> > > > >>>>> Ralph
>>>>> > > > >>>>>
>>>>> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
>>>>> > > volkan.yazici@gmail.com>
>>>>> > > > >>>> wrote:
>>>>> > > > >>>>>>
>>>>> > > > >>>>>> As subject hints, I am not able to run tests in IDEA
>>>>> anymore
>>>>> > after
>>>>> > > > >> Java
>>>>> > > > >>>> 11
>>>>> > > > >>>>>> upgrade. I have deleted all IDEA related files and issued
>>>>> a
>>>>> > clean
>>>>> > > > >> Maven
>>>>> > > > >>>>>> build:
>>>>> > > > >>>>>>
>>>>> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
>>>>> > > > >>>>>> $ rm -rf
>>>>> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>>>>> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
>>>>> > > > >>>>>>
>>>>> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't
>>>>> get it
>>>>> > > to
>>>>> > > > >> have
>>>>> > > > >>>>>> successful build:
>>>>> > > > >>>>>>
>>>>> > > > >>>>>> W: Output path
>>>>> > > > >>>>>>
>>>>> > > > >>>>
>>>>> > > > >>
>>>>> > >
>>>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>>> created by
>>>>> > > build
>>>>> > > > >>>> will
>>>>> > > > >>>>>> be cleaned
>>>>> > > > >>>>>> W: Output path
>>>>> > > > >>>>>>
>>>>> > > > >>>>
>>>>> > > > >>
>>>>> > >
>>>>> >
>>>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>>> created by
>>>>> > > build
>>>>> > > > >>>> will
>>>>> > > > >>>>>> be cleaned
>>>>> > > > >>>>>> W: Output path
>>>>> > > > >>>>>>
>>>>> > > > >>>>
>>>>> > > > >>
>>>>> > >
>>>>> >
>>>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>>> created by
>>>>> > > build
>>>>> > > > >>>> will
>>>>> > > > >>>>>> be cleaned
>>>>> > > > >>>>>> W: Output path
>>>>> > > > >>>>>>
>>>>> > > > >>>>
>>>>> > > > >>
>>>>> > >
>>>>> >
>>>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>>> created by
>>>>> > > build
>>>>> > > > >>>> will
>>>>> > > > >>>>>> be cleaned
>>>>> > > > >>>>>> W: Output path
>>>>> > > > >>>>>>
>>>>> > > > >>>>
>>>>> > > > >>
>>>>> > >
>>>>> >
>>>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>>> created by
>>>>> > > build
>>>>> > > > >>>> will
>>>>> > > > >>>>>> be cleaned
>>>>> > > > >>>>>> W: Output path
>>>>> > > > >>>>>>
>>>>> > > > >>>>
>>>>> > > > >>
>>>>> > >
>>>>> >
>>>>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>>> created by
>>>>> > > build
>>>>> > > > >>>> will
>>>>> > > > >>>>>> be cleaned
>>>>> > > > >>>>>> W: Output path
>>>>> > > > >>>>>>
>>>>> > > > >>>>
>>>>> > > > >>
>>>>> > >
>>>>> >
>>>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>>> created by
>>>>> > > build
>>>>> > > > >>>> will
>>>>> > > > >>>>>> be cleaned
>>>>> > > > >>>>>>
>>>>> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
>>>>> because
>>>>> > > it is
>>>>> > > > >>>>>> included into a circular dependency (module 'log4j-api'
>>>>> > > production,
>>>>> > > > >>>>>> maven-annotations-production:log4j-api, module
>>>>> 'log4j-plugins'
>>>>> > > > >>>> production,
>>>>> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
>>>>> > > > >>>>>> maven-annotations-test:log4j-plugins because it is
>>>>> included
>>>>> > into a
>>>>> > > > >>>> circular
>>>>> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
>>>>> > > 'log4j-api'
>>>>> > > > >>>> tests,
>>>>> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
>>>>> tests)*
>>>>> > > > >>>>>>
>>>>> > > > >>>>>> Did you get it working? What shall I do to make it work?
>>>>> > > > >>>>>
>>>>> > > > >>>>>
>>>>> > > > >>>>>
>>>>> > > > >>>>
>>>>> > > > >>>>
>>>>> > > > >>>>
>>>>> > > > >>
>>>>> > > > >>
>>>>> > > > >>
>>>>> > > >
>>>>> > > >
>>>>> > >
>>>>> >
>>>>>
>>>>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
Network speed showing they getting the fwd
On Tue, Apr 20, 2021, 10:10 AM Sixx XT <si...@gmail.com> wrote:
> Took the permissions off and filed boots read
>
> On Tue, Apr 20, 2021, 10:03 AM Sixx XT <si...@gmail.com> wrote:
>
>> He has everything auto forwarding if I put it on Nemesis he's toast
>>
>> On Tue, Apr 20, 2021, 9:59 AM Sixx XT <si...@gmail.com> wrote:
>>
>>> Ok this what imma do u guys give me a download of sdk apk android mac
>>> window's every volume
>>>
>>> On Mon, Apr 19, 2021, 6:34 PM Tim Perry <ti...@gmail.com> wrote:
>>>
>>>> Can any of you recommend an idiots guide to setting up a log4j
>>>> development
>>>> environment in IntelliJ? I have never used IntelliJ before. Eclipse
>>>> won't
>>>> work with a maven project with multiple module-info.java files. There
>>>> are
>>>> bugs into the maven-eclipse tools (m2e) for this.
>>>>
>>>> I cannot see reverting to 1999 and using the command line debugger, so
>>>> IntelliJ seems like my best shot at getting a working development
>>>> environment. I just want autocomplete and the ability to connect a
>>>> debugger
>>>> without too much hoop jumping.
>>>>
>>>> Thanks,
>>>> Tim
>>>>
>>>> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
>>>> wrote:
>>>>
>>>> > I have also tried that too, but no luck so far. @Matt, are you able
>>>> to run
>>>> > any tests from IDEA using the most recent "master"?
>>>> >
>>>> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
>>>> >
>>>> > > See also
>>>> > >
>>>> >
>>>> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
>>>> > >
>>>> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <
>>>> ralph.goers@dslextreme.com>
>>>> > > wrote:
>>>> > > >
>>>> > > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
>>>> debug
>>>> > > options”
>>>> > > >
>>>> > > > Ralph
>>>> > > >
>>>> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <
>>>> volkan.yazici@gmail.com>
>>>> > > wrote:
>>>> > > > >
>>>> > > > > Okay, fair enough. Thanks so much for sharing these details, I
>>>> > really
>>>> > > > > appreciated it. One final question: If you want to debug a
>>>> single
>>>> > > test, how
>>>> > > > > does your work flow look like? Do you create a new "Run
>>>> > Configuration"
>>>> > > > > invoking a certain Maven command triggering the code/test that
>>>> you
>>>> > are
>>>> > > > > interested in and "Debug Run"ing that "Run Configuration"?
>>>> > > > >
>>>> > > > > For the records, I still would like to hear how I can make IDEA
>>>> to
>>>> > > simply
>>>> > > > > run a test. If anybody has succeeded in doing that, I am all
>>>> ears.
>>>> > > > >
>>>> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <
>>>> ralph.goers@dslextreme.com>
>>>> > > wrote:
>>>> > > > >>
>>>> > > > >> I will be honest. I have never tun any log4j tests in
>>>> IntelliJ. I
>>>> > > rarely
>>>> > > > >> do it for any projects I work on. I use JVM remote debug all
>>>> the
>>>> > > time. I
>>>> > > > >> don’t want to force others to have to do that, but I just never
>>>> > think
>>>> > > about
>>>> > > > >> it.
>>>> > > > >>
>>>> > > > >> I use various versions of Maven from time to time. 3.6.1 is the
>>>> > > default on
>>>> > > > >> my Mac but I just installed 3.8.1 to validate what I needed to
>>>> > change
>>>> > > in my
>>>> > > > >> setup to make it still work with my employers Nexus repository
>>>> which
>>>> > > still
>>>> > > > >> uses http.
>>>> > > > >>
>>>> > > > >> When I am working on Log4J stuff I do a full mvn clean install
>>>> > several
>>>> > > > >> times a day. That takes a huge amount of time so I have
>>>> learned to
>>>> > > > >> multitask and work on other stuff while builds are running.
>>>> > > > >>
>>>> > > > >> Ralph.
>>>> > > > >>
>>>> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
>>>> > volkan.yazici@gmail.com>
>>>> > > > >> wrote:
>>>> > > > >>>
>>>> > > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
>>>> > *.iml
>>>> > > > >> files
>>>> > > > >>> and .idea directory), compile the sources via Maven, and open
>>>> the
>>>> > > folder
>>>> > > > >> in
>>>> > > > >>> IDEA, can you run *any* tests? If so, do you have any custom
>>>> IDEA
>>>> > > > >>> configurations? Which IDEA version are you using? If you are
>>>> not
>>>> > > using
>>>> > > > >> the
>>>> > > > >>> wrapper, which Maven version are you using?
>>>> > > > >>>
>>>> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
>>>> > > > >>> environments, independent of my local setup. It also saves you
>>>> > from a
>>>> > > > >> local
>>>> > > > >>> Maven dependency.
>>>> > > > >>>
>>>> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
>>>> > > ralph.goers@dslextreme.com>
>>>> > > > >>>> wrote:
>>>> > > > >>>>
>>>> > > > >>>> I deleted the files from my local repo and restarted the
>>>> build. It
>>>> > > is
>>>> > > > >>>> running along just fine - at least until it hits json
>>>> template
>>>> > > layout.
>>>> > > > >>>>
>>>> > > > >>>> Is there a reason you use the maven wrapper instead of Maven
>>>> > > itself? I
>>>> > > > >>>> have never used the wrapper. I am wondering if there is
>>>> something
>>>> > > going
>>>> > > > >> on
>>>> > > > >>>> there.
>>>> > > > >>>>
>>>> > > > >>>> Ralph
>>>> > > > >>>>
>>>> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
>>>> > > ralph.goers@dslextreme.com>
>>>> > > > >>>> wrote:
>>>> > > > >>>>>
>>>> > > > >>>>> I’ve never seen that. What is
>>>> > > maven-annotations-production:log4j-api?
>>>> > > > >>>>>
>>>> > > > >>>>> Let me try removing the files from my maven local repo as
>>>> you
>>>> > did.
>>>> > > > >>>>>
>>>> > > > >>>>> Ralph
>>>> > > > >>>>>
>>>> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
>>>> > > volkan.yazici@gmail.com>
>>>> > > > >>>> wrote:
>>>> > > > >>>>>>
>>>> > > > >>>>>> As subject hints, I am not able to run tests in IDEA
>>>> anymore
>>>> > after
>>>> > > > >> Java
>>>> > > > >>>> 11
>>>> > > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
>>>> > clean
>>>> > > > >> Maven
>>>> > > > >>>>>> build:
>>>> > > > >>>>>>
>>>> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
>>>> > > > >>>>>> $ rm -rf
>>>> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>>>> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
>>>> > > > >>>>>>
>>>> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't
>>>> get it
>>>> > > to
>>>> > > > >> have
>>>> > > > >>>>>> successful build:
>>>> > > > >>>>>>
>>>> > > > >>>>>> W: Output path
>>>> > > > >>>>>>
>>>> > > > >>>>
>>>> > > > >>
>>>> > >
>>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>> created by
>>>> > > build
>>>> > > > >>>> will
>>>> > > > >>>>>> be cleaned
>>>> > > > >>>>>> W: Output path
>>>> > > > >>>>>>
>>>> > > > >>>>
>>>> > > > >>
>>>> > >
>>>> >
>>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>> created by
>>>> > > build
>>>> > > > >>>> will
>>>> > > > >>>>>> be cleaned
>>>> > > > >>>>>> W: Output path
>>>> > > > >>>>>>
>>>> > > > >>>>
>>>> > > > >>
>>>> > >
>>>> >
>>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>> created by
>>>> > > build
>>>> > > > >>>> will
>>>> > > > >>>>>> be cleaned
>>>> > > > >>>>>> W: Output path
>>>> > > > >>>>>>
>>>> > > > >>>>
>>>> > > > >>
>>>> > >
>>>> >
>>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>> created by
>>>> > > build
>>>> > > > >>>> will
>>>> > > > >>>>>> be cleaned
>>>> > > > >>>>>> W: Output path
>>>> > > > >>>>>>
>>>> > > > >>>>
>>>> > > > >>
>>>> > >
>>>> >
>>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>> created by
>>>> > > build
>>>> > > > >>>> will
>>>> > > > >>>>>> be cleaned
>>>> > > > >>>>>> W: Output path
>>>> > > > >>>>>>
>>>> > > > >>>>
>>>> > > > >>
>>>> > >
>>>> >
>>>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>> created by
>>>> > > build
>>>> > > > >>>> will
>>>> > > > >>>>>> be cleaned
>>>> > > > >>>>>> W: Output path
>>>> > > > >>>>>>
>>>> > > > >>>>
>>>> > > > >>
>>>> > >
>>>> >
>>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>>>> > > > >>>>>> intersects with a source root. Only files that were
>>>> created by
>>>> > > build
>>>> > > > >>>> will
>>>> > > > >>>>>> be cleaned
>>>> > > > >>>>>>
>>>> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
>>>> because
>>>> > > it is
>>>> > > > >>>>>> included into a circular dependency (module 'log4j-api'
>>>> > > production,
>>>> > > > >>>>>> maven-annotations-production:log4j-api, module
>>>> 'log4j-plugins'
>>>> > > > >>>> production,
>>>> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
>>>> > > > >>>>>> maven-annotations-test:log4j-plugins because it is included
>>>> > into a
>>>> > > > >>>> circular
>>>> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
>>>> > > 'log4j-api'
>>>> > > > >>>> tests,
>>>> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
>>>> tests)*
>>>> > > > >>>>>>
>>>> > > > >>>>>> Did you get it working? What shall I do to make it work?
>>>> > > > >>>>>
>>>> > > > >>>>>
>>>> > > > >>>>>
>>>> > > > >>>>
>>>> > > > >>>>
>>>> > > > >>>>
>>>> > > > >>
>>>> > > > >>
>>>> > > > >>
>>>> > > >
>>>> > > >
>>>> > >
>>>> >
>>>>
>>>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
Took the permissions off and filed boots read
On Tue, Apr 20, 2021, 10:03 AM Sixx XT <si...@gmail.com> wrote:
> He has everything auto forwarding if I put it on Nemesis he's toast
>
> On Tue, Apr 20, 2021, 9:59 AM Sixx XT <si...@gmail.com> wrote:
>
>> Ok this what imma do u guys give me a download of sdk apk android mac
>> window's every volume
>>
>> On Mon, Apr 19, 2021, 6:34 PM Tim Perry <ti...@gmail.com> wrote:
>>
>>> Can any of you recommend an idiots guide to setting up a log4j
>>> development
>>> environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
>>> work with a maven project with multiple module-info.java files. There are
>>> bugs into the maven-eclipse tools (m2e) for this.
>>>
>>> I cannot see reverting to 1999 and using the command line debugger, so
>>> IntelliJ seems like my best shot at getting a working development
>>> environment. I just want autocomplete and the ability to connect a
>>> debugger
>>> without too much hoop jumping.
>>>
>>> Thanks,
>>> Tim
>>>
>>> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
>>> wrote:
>>>
>>> > I have also tried that too, but no luck so far. @Matt, are you able to
>>> run
>>> > any tests from IDEA using the most recent "master"?
>>> >
>>> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
>>> >
>>> > > See also
>>> > >
>>> >
>>> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
>>> > >
>>> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ralph.goers@dslextreme.com
>>> >
>>> > > wrote:
>>> > > >
>>> > > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
>>> debug
>>> > > options”
>>> > > >
>>> > > > Ralph
>>> > > >
>>> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <
>>> volkan.yazici@gmail.com>
>>> > > wrote:
>>> > > > >
>>> > > > > Okay, fair enough. Thanks so much for sharing these details, I
>>> > really
>>> > > > > appreciated it. One final question: If you want to debug a single
>>> > > test, how
>>> > > > > does your work flow look like? Do you create a new "Run
>>> > Configuration"
>>> > > > > invoking a certain Maven command triggering the code/test that
>>> you
>>> > are
>>> > > > > interested in and "Debug Run"ing that "Run Configuration"?
>>> > > > >
>>> > > > > For the records, I still would like to hear how I can make IDEA
>>> to
>>> > > simply
>>> > > > > run a test. If anybody has succeeded in doing that, I am all
>>> ears.
>>> > > > >
>>> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <
>>> ralph.goers@dslextreme.com>
>>> > > wrote:
>>> > > > >>
>>> > > > >> I will be honest. I have never tun any log4j tests in IntelliJ.
>>> I
>>> > > rarely
>>> > > > >> do it for any projects I work on. I use JVM remote debug all the
>>> > > time. I
>>> > > > >> don’t want to force others to have to do that, but I just never
>>> > think
>>> > > about
>>> > > > >> it.
>>> > > > >>
>>> > > > >> I use various versions of Maven from time to time. 3.6.1 is the
>>> > > default on
>>> > > > >> my Mac but I just installed 3.8.1 to validate what I needed to
>>> > change
>>> > > in my
>>> > > > >> setup to make it still work with my employers Nexus repository
>>> which
>>> > > still
>>> > > > >> uses http.
>>> > > > >>
>>> > > > >> When I am working on Log4J stuff I do a full mvn clean install
>>> > several
>>> > > > >> times a day. That takes a huge amount of time so I have learned
>>> to
>>> > > > >> multitask and work on other stuff while builds are running.
>>> > > > >>
>>> > > > >> Ralph.
>>> > > > >>
>>> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
>>> > volkan.yazici@gmail.com>
>>> > > > >> wrote:
>>> > > > >>>
>>> > > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
>>> > *.iml
>>> > > > >> files
>>> > > > >>> and .idea directory), compile the sources via Maven, and open
>>> the
>>> > > folder
>>> > > > >> in
>>> > > > >>> IDEA, can you run *any* tests? If so, do you have any custom
>>> IDEA
>>> > > > >>> configurations? Which IDEA version are you using? If you are
>>> not
>>> > > using
>>> > > > >> the
>>> > > > >>> wrapper, which Maven version are you using?
>>> > > > >>>
>>> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
>>> > > > >>> environments, independent of my local setup. It also saves you
>>> > from a
>>> > > > >> local
>>> > > > >>> Maven dependency.
>>> > > > >>>
>>> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
>>> > > ralph.goers@dslextreme.com>
>>> > > > >>>> wrote:
>>> > > > >>>>
>>> > > > >>>> I deleted the files from my local repo and restarted the
>>> build. It
>>> > > is
>>> > > > >>>> running along just fine - at least until it hits json template
>>> > > layout.
>>> > > > >>>>
>>> > > > >>>> Is there a reason you use the maven wrapper instead of Maven
>>> > > itself? I
>>> > > > >>>> have never used the wrapper. I am wondering if there is
>>> something
>>> > > going
>>> > > > >> on
>>> > > > >>>> there.
>>> > > > >>>>
>>> > > > >>>> Ralph
>>> > > > >>>>
>>> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
>>> > > ralph.goers@dslextreme.com>
>>> > > > >>>> wrote:
>>> > > > >>>>>
>>> > > > >>>>> I’ve never seen that. What is
>>> > > maven-annotations-production:log4j-api?
>>> > > > >>>>>
>>> > > > >>>>> Let me try removing the files from my maven local repo as you
>>> > did.
>>> > > > >>>>>
>>> > > > >>>>> Ralph
>>> > > > >>>>>
>>> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
>>> > > volkan.yazici@gmail.com>
>>> > > > >>>> wrote:
>>> > > > >>>>>>
>>> > > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
>>> > after
>>> > > > >> Java
>>> > > > >>>> 11
>>> > > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
>>> > clean
>>> > > > >> Maven
>>> > > > >>>>>> build:
>>> > > > >>>>>>
>>> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
>>> > > > >>>>>> $ rm -rf
>>> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>>> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
>>> > > > >>>>>>
>>> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't
>>> get it
>>> > > to
>>> > > > >> have
>>> > > > >>>>>> successful build:
>>> > > > >>>>>>
>>> > > > >>>>>> W: Output path
>>> > > > >>>>>>
>>> > > > >>>>
>>> > > > >>
>>> > >
>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>>> > > > >>>>>> intersects with a source root. Only files that were created
>>> by
>>> > > build
>>> > > > >>>> will
>>> > > > >>>>>> be cleaned
>>> > > > >>>>>> W: Output path
>>> > > > >>>>>>
>>> > > > >>>>
>>> > > > >>
>>> > >
>>> >
>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>>> > > > >>>>>> intersects with a source root. Only files that were created
>>> by
>>> > > build
>>> > > > >>>> will
>>> > > > >>>>>> be cleaned
>>> > > > >>>>>> W: Output path
>>> > > > >>>>>>
>>> > > > >>>>
>>> > > > >>
>>> > >
>>> >
>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>>> > > > >>>>>> intersects with a source root. Only files that were created
>>> by
>>> > > build
>>> > > > >>>> will
>>> > > > >>>>>> be cleaned
>>> > > > >>>>>> W: Output path
>>> > > > >>>>>>
>>> > > > >>>>
>>> > > > >>
>>> > >
>>> >
>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>>> > > > >>>>>> intersects with a source root. Only files that were created
>>> by
>>> > > build
>>> > > > >>>> will
>>> > > > >>>>>> be cleaned
>>> > > > >>>>>> W: Output path
>>> > > > >>>>>>
>>> > > > >>>>
>>> > > > >>
>>> > >
>>> >
>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>>> > > > >>>>>> intersects with a source root. Only files that were created
>>> by
>>> > > build
>>> > > > >>>> will
>>> > > > >>>>>> be cleaned
>>> > > > >>>>>> W: Output path
>>> > > > >>>>>>
>>> > > > >>>>
>>> > > > >>
>>> > >
>>> >
>>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>>> > > > >>>>>> intersects with a source root. Only files that were created
>>> by
>>> > > build
>>> > > > >>>> will
>>> > > > >>>>>> be cleaned
>>> > > > >>>>>> W: Output path
>>> > > > >>>>>>
>>> > > > >>>>
>>> > > > >>
>>> > >
>>> >
>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>>> > > > >>>>>> intersects with a source root. Only files that were created
>>> by
>>> > > build
>>> > > > >>>> will
>>> > > > >>>>>> be cleaned
>>> > > > >>>>>>
>>> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
>>> because
>>> > > it is
>>> > > > >>>>>> included into a circular dependency (module 'log4j-api'
>>> > > production,
>>> > > > >>>>>> maven-annotations-production:log4j-api, module
>>> 'log4j-plugins'
>>> > > > >>>> production,
>>> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
>>> > > > >>>>>> maven-annotations-test:log4j-plugins because it is included
>>> > into a
>>> > > > >>>> circular
>>> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
>>> > > 'log4j-api'
>>> > > > >>>> tests,
>>> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
>>> tests)*
>>> > > > >>>>>>
>>> > > > >>>>>> Did you get it working? What shall I do to make it work?
>>> > > > >>>>>
>>> > > > >>>>>
>>> > > > >>>>>
>>> > > > >>>>
>>> > > > >>>>
>>> > > > >>>>
>>> > > > >>
>>> > > > >>
>>> > > > >>
>>> > > >
>>> > > >
>>> > >
>>> >
>>>
>>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
He has everything auto forwarding if I put it on Nemesis he's toast
On Tue, Apr 20, 2021, 9:59 AM Sixx XT <si...@gmail.com> wrote:
> Ok this what imma do u guys give me a download of sdk apk android mac
> window's every volume
>
> On Mon, Apr 19, 2021, 6:34 PM Tim Perry <ti...@gmail.com> wrote:
>
>> Can any of you recommend an idiots guide to setting up a log4j development
>> environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
>> work with a maven project with multiple module-info.java files. There are
>> bugs into the maven-eclipse tools (m2e) for this.
>>
>> I cannot see reverting to 1999 and using the command line debugger, so
>> IntelliJ seems like my best shot at getting a working development
>> environment. I just want autocomplete and the ability to connect a
>> debugger
>> without too much hoop jumping.
>>
>> Thanks,
>> Tim
>>
>> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
>> wrote:
>>
>> > I have also tried that too, but no luck so far. @Matt, are you able to
>> run
>> > any tests from IDEA using the most recent "master"?
>> >
>> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
>> >
>> > > See also
>> > >
>> >
>> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
>> > >
>> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
>> > > wrote:
>> > > >
>> > > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
>> debug
>> > > options”
>> > > >
>> > > > Ralph
>> > > >
>> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <
>> volkan.yazici@gmail.com>
>> > > wrote:
>> > > > >
>> > > > > Okay, fair enough. Thanks so much for sharing these details, I
>> > really
>> > > > > appreciated it. One final question: If you want to debug a single
>> > > test, how
>> > > > > does your work flow look like? Do you create a new "Run
>> > Configuration"
>> > > > > invoking a certain Maven command triggering the code/test that you
>> > are
>> > > > > interested in and "Debug Run"ing that "Run Configuration"?
>> > > > >
>> > > > > For the records, I still would like to hear how I can make IDEA to
>> > > simply
>> > > > > run a test. If anybody has succeeded in doing that, I am all ears.
>> > > > >
>> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <
>> ralph.goers@dslextreme.com>
>> > > wrote:
>> > > > >>
>> > > > >> I will be honest. I have never tun any log4j tests in IntelliJ. I
>> > > rarely
>> > > > >> do it for any projects I work on. I use JVM remote debug all the
>> > > time. I
>> > > > >> don’t want to force others to have to do that, but I just never
>> > think
>> > > about
>> > > > >> it.
>> > > > >>
>> > > > >> I use various versions of Maven from time to time. 3.6.1 is the
>> > > default on
>> > > > >> my Mac but I just installed 3.8.1 to validate what I needed to
>> > change
>> > > in my
>> > > > >> setup to make it still work with my employers Nexus repository
>> which
>> > > still
>> > > > >> uses http.
>> > > > >>
>> > > > >> When I am working on Log4J stuff I do a full mvn clean install
>> > several
>> > > > >> times a day. That takes a huge amount of time so I have learned
>> to
>> > > > >> multitask and work on other stuff while builds are running.
>> > > > >>
>> > > > >> Ralph.
>> > > > >>
>> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
>> > volkan.yazici@gmail.com>
>> > > > >> wrote:
>> > > > >>>
>> > > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
>> > *.iml
>> > > > >> files
>> > > > >>> and .idea directory), compile the sources via Maven, and open
>> the
>> > > folder
>> > > > >> in
>> > > > >>> IDEA, can you run *any* tests? If so, do you have any custom
>> IDEA
>> > > > >>> configurations? Which IDEA version are you using? If you are not
>> > > using
>> > > > >> the
>> > > > >>> wrapper, which Maven version are you using?
>> > > > >>>
>> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
>> > > > >>> environments, independent of my local setup. It also saves you
>> > from a
>> > > > >> local
>> > > > >>> Maven dependency.
>> > > > >>>
>> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
>> > > ralph.goers@dslextreme.com>
>> > > > >>>> wrote:
>> > > > >>>>
>> > > > >>>> I deleted the files from my local repo and restarted the
>> build. It
>> > > is
>> > > > >>>> running along just fine - at least until it hits json template
>> > > layout.
>> > > > >>>>
>> > > > >>>> Is there a reason you use the maven wrapper instead of Maven
>> > > itself? I
>> > > > >>>> have never used the wrapper. I am wondering if there is
>> something
>> > > going
>> > > > >> on
>> > > > >>>> there.
>> > > > >>>>
>> > > > >>>> Ralph
>> > > > >>>>
>> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
>> > > ralph.goers@dslextreme.com>
>> > > > >>>> wrote:
>> > > > >>>>>
>> > > > >>>>> I’ve never seen that. What is
>> > > maven-annotations-production:log4j-api?
>> > > > >>>>>
>> > > > >>>>> Let me try removing the files from my maven local repo as you
>> > did.
>> > > > >>>>>
>> > > > >>>>> Ralph
>> > > > >>>>>
>> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
>> > > volkan.yazici@gmail.com>
>> > > > >>>> wrote:
>> > > > >>>>>>
>> > > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
>> > after
>> > > > >> Java
>> > > > >>>> 11
>> > > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
>> > clean
>> > > > >> Maven
>> > > > >>>>>> build:
>> > > > >>>>>>
>> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
>> > > > >>>>>> $ rm -rf
>> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
>> > > > >>>>>>
>> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't
>> get it
>> > > to
>> > > > >> have
>> > > > >>>>>> successful build:
>> > > > >>>>>>
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>>
>> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
>> because
>> > > it is
>> > > > >>>>>> included into a circular dependency (module 'log4j-api'
>> > > production,
>> > > > >>>>>> maven-annotations-production:log4j-api, module
>> 'log4j-plugins'
>> > > > >>>> production,
>> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
>> > > > >>>>>> maven-annotations-test:log4j-plugins because it is included
>> > into a
>> > > > >>>> circular
>> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
>> > > 'log4j-api'
>> > > > >>>> tests,
>> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
>> tests)*
>> > > > >>>>>>
>> > > > >>>>>> Did you get it working? What shall I do to make it work?
>> > > > >>>>>
>> > > > >>>>>
>> > > > >>>>>
>> > > > >>>>
>> > > > >>>>
>> > > > >>>>
>> > > > >>
>> > > > >>
>> > > > >>
>> > > >
>> > > >
>> > >
>> >
>>
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
Ok this what imma do u guys give me a download of sdk apk android mac
window's every volume
On Mon, Apr 19, 2021, 6:34 PM Tim Perry <ti...@gmail.com> wrote:
> Can any of you recommend an idiots guide to setting up a log4j development
> environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
> work with a maven project with multiple module-info.java files. There are
> bugs into the maven-eclipse tools (m2e) for this.
>
> I cannot see reverting to 1999 and using the command line debugger, so
> IntelliJ seems like my best shot at getting a working development
> environment. I just want autocomplete and the ability to connect a debugger
> without too much hoop jumping.
>
> Thanks,
> Tim
>
> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
> wrote:
>
> > I have also tried that too, but no luck so far. @Matt, are you able to
> run
> > any tests from IDEA using the most recent "master"?
> >
> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
> >
> > > See also
> > >
> >
> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
> > >
> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
> > > wrote:
> > > >
> > > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
> debug
> > > options”
> > > >
> > > > Ralph
> > > >
> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <volkan.yazici@gmail.com
> >
> > > wrote:
> > > > >
> > > > > Okay, fair enough. Thanks so much for sharing these details, I
> > really
> > > > > appreciated it. One final question: If you want to debug a single
> > > test, how
> > > > > does your work flow look like? Do you create a new "Run
> > Configuration"
> > > > > invoking a certain Maven command triggering the code/test that you
> > are
> > > > > interested in and "Debug Run"ing that "Run Configuration"?
> > > > >
> > > > > For the records, I still would like to hear how I can make IDEA to
> > > simply
> > > > > run a test. If anybody has succeeded in doing that, I am all ears.
> > > > >
> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <ralph.goers@dslextreme.com
> >
> > > wrote:
> > > > >>
> > > > >> I will be honest. I have never tun any log4j tests in IntelliJ. I
> > > rarely
> > > > >> do it for any projects I work on. I use JVM remote debug all the
> > > time. I
> > > > >> don’t want to force others to have to do that, but I just never
> > think
> > > about
> > > > >> it.
> > > > >>
> > > > >> I use various versions of Maven from time to time. 3.6.1 is the
> > > default on
> > > > >> my Mac but I just installed 3.8.1 to validate what I needed to
> > change
> > > in my
> > > > >> setup to make it still work with my employers Nexus repository
> which
> > > still
> > > > >> uses http.
> > > > >>
> > > > >> When I am working on Log4J stuff I do a full mvn clean install
> > several
> > > > >> times a day. That takes a huge amount of time so I have learned to
> > > > >> multitask and work on other stuff while builds are running.
> > > > >>
> > > > >> Ralph.
> > > > >>
> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
> > volkan.yazici@gmail.com>
> > > > >> wrote:
> > > > >>>
> > > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
> > *.iml
> > > > >> files
> > > > >>> and .idea directory), compile the sources via Maven, and open the
> > > folder
> > > > >> in
> > > > >>> IDEA, can you run *any* tests? If so, do you have any custom IDEA
> > > > >>> configurations? Which IDEA version are you using? If you are not
> > > using
> > > > >> the
> > > > >>> wrapper, which Maven version are you using?
> > > > >>>
> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
> > > > >>> environments, independent of my local setup. It also saves you
> > from a
> > > > >> local
> > > > >>> Maven dependency.
> > > > >>>
> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
> > > ralph.goers@dslextreme.com>
> > > > >>>> wrote:
> > > > >>>>
> > > > >>>> I deleted the files from my local repo and restarted the build.
> It
> > > is
> > > > >>>> running along just fine - at least until it hits json template
> > > layout.
> > > > >>>>
> > > > >>>> Is there a reason you use the maven wrapper instead of Maven
> > > itself? I
> > > > >>>> have never used the wrapper. I am wondering if there is
> something
> > > going
> > > > >> on
> > > > >>>> there.
> > > > >>>>
> > > > >>>> Ralph
> > > > >>>>
> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
> > > ralph.goers@dslextreme.com>
> > > > >>>> wrote:
> > > > >>>>>
> > > > >>>>> I’ve never seen that. What is
> > > maven-annotations-production:log4j-api?
> > > > >>>>>
> > > > >>>>> Let me try removing the files from my maven local repo as you
> > did.
> > > > >>>>>
> > > > >>>>> Ralph
> > > > >>>>>
> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
> > > volkan.yazici@gmail.com>
> > > > >>>> wrote:
> > > > >>>>>>
> > > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
> > after
> > > > >> Java
> > > > >>>> 11
> > > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
> > clean
> > > > >> Maven
> > > > >>>>>> build:
> > > > >>>>>>
> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
> > > > >>>>>> $ rm -rf
> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
> > > > >>>>>>
> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get
> it
> > > to
> > > > >> have
> > > > >>>>>> successful build:
> > > > >>>>>>
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>>
> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
> because
> > > it is
> > > > >>>>>> included into a circular dependency (module 'log4j-api'
> > > production,
> > > > >>>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
> > > > >>>> production,
> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
> > > > >>>>>> maven-annotations-test:log4j-plugins because it is included
> > into a
> > > > >>>> circular
> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
> > > 'log4j-api'
> > > > >>>> tests,
> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
> tests)*
> > > > >>>>>>
> > > > >>>>>> Did you get it working? What shall I do to make it work?
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
Sixx XT has sent you an email via Gmail confidential mode:
[image: Gmail logo]Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade <https://confidential-mail.google.com/msg/AG7J_YTSHjl6smEtzuajVHhHi1ZreFNZ3FWDwJJC2-AmLzQC71DVtvNhYFjY6kjWRr7HTAaXX1c-P4rNcnO5YOqCkP8RUWqoK6y4Dh8-e5ZOCyG7pY7qeVRrYbUIQhUkMKLSQnqswnBWZsMALu0=>
This message was sent on Apr 19, 2021 at 4:18:05 PM PDT
You can open it by clicking the link below. This link will only work for dev@logging.apache.org.
View the email <https://confidential-mail.google.com/msg/AG7J_YTSHjl6smEtzuajVHhHi1ZreFNZ3FWDwJJC2-AmLzQC71DVtvNhYFjY6kjWRr7HTAaXX1c-P4rNcnO5YOqCkP8RUWqoK6y4Dh8-e5ZOCyG7pY7qeVRrYbUIQhUkMKLSQnqswnBWZsMALu0=>
Gmail confidential mode gives you more control over the messages you send. The sender may have chosen to set an expiration time, disable printing or forwarding, or track access to this message. Learn more <https://support.google.com/mail/answer/7674059>
Gmail: Email by Google
Use is subject to the Google Privacy Policy <https://myaccount.google.com/privacypolicy?hl=en>
Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA
You have received this message because someone sent you an email via Gmail confidential mode.
[image: Google logo]
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
Algorithm intelligence Jason 💡 ethical thing is equal to 2dppx and thats
false its Darwin pye from Atlanta on my face book page
On Mon, Apr 19, 2021, 7:26 PM Sixx XT <si...@gmail.com> wrote:
> Its them
>
> On Mon, Apr 19, 2021, 7:26 PM Sixx XT <si...@gmail.com> wrote:
>
>>
>> Facebook Group:
>> https://fb.com/groups/236181883796840/
>> <https://www.facebook.com/groups/236181883796840/>
>>
>> Telegram Group: https://t.me/HttpInjectorGroup
>>
>> On Mon, Apr 19, 2021, 6:34 PM Tim Perry <ti...@gmail.com> wrote:
>>
>>> Can any of you recommend an idiots guide to setting up a log4j
>>> development
>>> environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
>>> work with a maven project with multiple module-info.java files. There are
>>> bugs into the maven-eclipse tools (m2e) for this.
>>>
>>> I cannot see reverting to 1999 and using the command line debugger, so
>>> IntelliJ seems like my best shot at getting a working development
>>> environment. I just want autocomplete and the ability to connect a
>>> debugger
>>> without too much hoop jumping.
>>>
>>> Thanks,
>>> Tim
>>>
>>> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
>>> wrote:
>>>
>>> > I have also tried that too, but no luck so far. @Matt, are you able to
>>> run
>>> > any tests from IDEA using the most recent "master"?
>>> >
>>> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
>>> >
>>> > > See also
>>> > >
>>> >
>>> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
>>> > >
>>> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ralph.goers@dslextreme.com
>>> >
>>> > > wrote:
>>> > > >
>>> > > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
>>> debug
>>> > > options”
>>> > > >
>>> > > > Ralph
>>> > > >
>>> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <
>>> volkan.yazici@gmail.com>
>>> > > wrote:
>>> > > > >
>>> > > > > Okay, fair enough. Thanks so much for sharing these details, I
>>> > really
>>> > > > > appreciated it. One final question: If you want to debug a single
>>> > > test, how
>>> > > > > does your work flow look like? Do you create a new "Run
>>> > Configuration"
>>> > > > > invoking a certain Maven command triggering the code/test that
>>> you
>>> > are
>>> > > > > interested in and "Debug Run"ing that "Run Configuration"?
>>> > > > >
>>> > > > > For the records, I still would like to hear how I can make IDEA
>>> to
>>> > > simply
>>> > > > > run a test. If anybody has succeeded in doing that, I am all
>>> ears.
>>> > > > >
>>> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <
>>> ralph.goers@dslextreme.com>
>>> > > wrote:
>>> > > > >>
>>> > > > >> I will be honest. I have never tun any log4j tests in IntelliJ.
>>> I
>>> > > rarely
>>> > > > >> do it for any projects I work on. I use JVM remote debug all the
>>> > > time. I
>>> > > > >> don’t want to force others to have to do that, but I just never
>>> > think
>>> > > about
>>> > > > >> it.
>>> > > > >>
>>> > > > >> I use various versions of Maven from time to time. 3.6.1 is the
>>> > > default on
>>> > > > >> my Mac but I just installed 3.8.1 to validate what I needed to
>>> > change
>>> > > in my
>>> > > > >> setup to make it still work with my employers Nexus repository
>>> which
>>> > > still
>>> > > > >> uses http.
>>> > > > >>
>>> > > > >> When I am working on Log4J stuff I do a full mvn clean install
>>> > several
>>> > > > >> times a day. That takes a huge amount of time so I have learned
>>> to
>>> > > > >> multitask and work on other stuff while builds are running.
>>> > > > >>
>>> > > > >> Ralph.
>>> > > > >>
>>> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
>>> > volkan.yazici@gmail.com>
>>> > > > >> wrote:
>>> > > > >>>
>>> > > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
>>> > *.iml
>>> > > > >> files
>>> > > > >>> and .idea directory), compile the sources via Maven, and open
>>> the
>>> > > folder
>>> > > > >> in
>>> > > > >>> IDEA, can you run *any* tests? If so, do you have any custom
>>> IDEA
>>> > > > >>> configurations? Which IDEA version are you using? If you are
>>> not
>>> > > using
>>> > > > >> the
>>> > > > >>> wrapper, which Maven version are you using?
>>> > > > >>>
>>> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
>>> > > > >>> environments, independent of my local setup. It also saves you
>>> > from a
>>> > > > >> local
>>> > > > >>> Maven dependency.
>>> > > > >>>
>>> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
>>> > > ralph.goers@dslextreme.com>
>>> > > > >>>> wrote:
>>> > > > >>>>
>>> > > > >>>> I deleted the files from my local repo and restarted the
>>> build. It
>>> > > is
>>> > > > >>>> running along just fine - at least until it hits json template
>>> > > layout.
>>> > > > >>>>
>>> > > > >>>> Is there a reason you use the maven wrapper instead of Maven
>>> > > itself? I
>>> > > > >>>> have never used the wrapper. I am wondering if there is
>>> something
>>> > > going
>>> > > > >> on
>>> > > > >>>> there.
>>> > > > >>>>
>>> > > > >>>> Ralph
>>> > > > >>>>
>>> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
>>> > > ralph.goers@dslextreme.com>
>>> > > > >>>> wrote:
>>> > > > >>>>>
>>> > > > >>>>> I’ve never seen that. What is
>>> > > maven-annotations-production:log4j-api?
>>> > > > >>>>>
>>> > > > >>>>> Let me try removing the files from my maven local repo as you
>>> > did.
>>> > > > >>>>>
>>> > > > >>>>> Ralph
>>> > > > >>>>>
>>> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
>>> > > volkan.yazici@gmail.com>
>>> > > > >>>> wrote:
>>> > > > >>>>>>
>>> > > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
>>> > after
>>> > > > >> Java
>>> > > > >>>> 11
>>> > > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
>>> > clean
>>> > > > >> Maven
>>> > > > >>>>>> build:
>>> > > > >>>>>>
>>> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
>>> > > > >>>>>> $ rm -rf
>>> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>>> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
>>> > > > >>>>>>
>>> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't
>>> get it
>>> > > to
>>> > > > >> have
>>> > > > >>>>>> successful build:
>>> > > > >>>>>>
>>> > > > >>>>>> W: Output path
>>> > > > >>>>>>
>>> > > > >>>>
>>> > > > >>
>>> > >
>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>>> > > > >>>>>> intersects with a source root. Only files that were created
>>> by
>>> > > build
>>> > > > >>>> will
>>> > > > >>>>>> be cleaned
>>> > > > >>>>>> W: Output path
>>> > > > >>>>>>
>>> > > > >>>>
>>> > > > >>
>>> > >
>>> >
>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>>> > > > >>>>>> intersects with a source root. Only files that were created
>>> by
>>> > > build
>>> > > > >>>> will
>>> > > > >>>>>> be cleaned
>>> > > > >>>>>> W: Output path
>>> > > > >>>>>>
>>> > > > >>>>
>>> > > > >>
>>> > >
>>> >
>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>>> > > > >>>>>> intersects with a source root. Only files that were created
>>> by
>>> > > build
>>> > > > >>>> will
>>> > > > >>>>>> be cleaned
>>> > > > >>>>>> W: Output path
>>> > > > >>>>>>
>>> > > > >>>>
>>> > > > >>
>>> > >
>>> >
>>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>>> > > > >>>>>> intersects with a source root. Only files that were created
>>> by
>>> > > build
>>> > > > >>>> will
>>> > > > >>>>>> be cleaned
>>> > > > >>>>>> W: Output path
>>> > > > >>>>>>
>>> > > > >>>>
>>> > > > >>
>>> > >
>>> >
>>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>>> > > > >>>>>> intersects with a source root. Only files that were created
>>> by
>>> > > build
>>> > > > >>>> will
>>> > > > >>>>>> be cleaned
>>> > > > >>>>>> W: Output path
>>> > > > >>>>>>
>>> > > > >>>>
>>> > > > >>
>>> > >
>>> >
>>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>>> > > > >>>>>> intersects with a source root. Only files that were created
>>> by
>>> > > build
>>> > > > >>>> will
>>> > > > >>>>>> be cleaned
>>> > > > >>>>>> W: Output path
>>> > > > >>>>>>
>>> > > > >>>>
>>> > > > >>
>>> > >
>>> >
>>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>>> > > > >>>>>> intersects with a source root. Only files that were created
>>> by
>>> > > build
>>> > > > >>>> will
>>> > > > >>>>>> be cleaned
>>> > > > >>>>>>
>>> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
>>> because
>>> > > it is
>>> > > > >>>>>> included into a circular dependency (module 'log4j-api'
>>> > > production,
>>> > > > >>>>>> maven-annotations-production:log4j-api, module
>>> 'log4j-plugins'
>>> > > > >>>> production,
>>> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
>>> > > > >>>>>> maven-annotations-test:log4j-plugins because it is included
>>> > into a
>>> > > > >>>> circular
>>> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
>>> > > 'log4j-api'
>>> > > > >>>> tests,
>>> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
>>> tests)*
>>> > > > >>>>>>
>>> > > > >>>>>> Did you get it working? What shall I do to make it work?
>>> > > > >>>>>
>>> > > > >>>>>
>>> > > > >>>>>
>>> > > > >>>>
>>> > > > >>>>
>>> > > > >>>>
>>> > > > >>
>>> > > > >>
>>> > > > >>
>>> > > >
>>> > > >
>>> > >
>>> >
>>>
>>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
Its them
On Mon, Apr 19, 2021, 7:26 PM Sixx XT <si...@gmail.com> wrote:
>
> Facebook Group:
> https://fb.com/groups/236181883796840/
> <https://www.facebook.com/groups/236181883796840/>
>
> Telegram Group: https://t.me/HttpInjectorGroup
>
> On Mon, Apr 19, 2021, 6:34 PM Tim Perry <ti...@gmail.com> wrote:
>
>> Can any of you recommend an idiots guide to setting up a log4j development
>> environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
>> work with a maven project with multiple module-info.java files. There are
>> bugs into the maven-eclipse tools (m2e) for this.
>>
>> I cannot see reverting to 1999 and using the command line debugger, so
>> IntelliJ seems like my best shot at getting a working development
>> environment. I just want autocomplete and the ability to connect a
>> debugger
>> without too much hoop jumping.
>>
>> Thanks,
>> Tim
>>
>> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
>> wrote:
>>
>> > I have also tried that too, but no luck so far. @Matt, are you able to
>> run
>> > any tests from IDEA using the most recent "master"?
>> >
>> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
>> >
>> > > See also
>> > >
>> >
>> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
>> > >
>> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
>> > > wrote:
>> > > >
>> > > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
>> debug
>> > > options”
>> > > >
>> > > > Ralph
>> > > >
>> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <
>> volkan.yazici@gmail.com>
>> > > wrote:
>> > > > >
>> > > > > Okay, fair enough. Thanks so much for sharing these details, I
>> > really
>> > > > > appreciated it. One final question: If you want to debug a single
>> > > test, how
>> > > > > does your work flow look like? Do you create a new "Run
>> > Configuration"
>> > > > > invoking a certain Maven command triggering the code/test that you
>> > are
>> > > > > interested in and "Debug Run"ing that "Run Configuration"?
>> > > > >
>> > > > > For the records, I still would like to hear how I can make IDEA to
>> > > simply
>> > > > > run a test. If anybody has succeeded in doing that, I am all ears.
>> > > > >
>> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <
>> ralph.goers@dslextreme.com>
>> > > wrote:
>> > > > >>
>> > > > >> I will be honest. I have never tun any log4j tests in IntelliJ. I
>> > > rarely
>> > > > >> do it for any projects I work on. I use JVM remote debug all the
>> > > time. I
>> > > > >> don’t want to force others to have to do that, but I just never
>> > think
>> > > about
>> > > > >> it.
>> > > > >>
>> > > > >> I use various versions of Maven from time to time. 3.6.1 is the
>> > > default on
>> > > > >> my Mac but I just installed 3.8.1 to validate what I needed to
>> > change
>> > > in my
>> > > > >> setup to make it still work with my employers Nexus repository
>> which
>> > > still
>> > > > >> uses http.
>> > > > >>
>> > > > >> When I am working on Log4J stuff I do a full mvn clean install
>> > several
>> > > > >> times a day. That takes a huge amount of time so I have learned
>> to
>> > > > >> multitask and work on other stuff while builds are running.
>> > > > >>
>> > > > >> Ralph.
>> > > > >>
>> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
>> > volkan.yazici@gmail.com>
>> > > > >> wrote:
>> > > > >>>
>> > > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
>> > *.iml
>> > > > >> files
>> > > > >>> and .idea directory), compile the sources via Maven, and open
>> the
>> > > folder
>> > > > >> in
>> > > > >>> IDEA, can you run *any* tests? If so, do you have any custom
>> IDEA
>> > > > >>> configurations? Which IDEA version are you using? If you are not
>> > > using
>> > > > >> the
>> > > > >>> wrapper, which Maven version are you using?
>> > > > >>>
>> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
>> > > > >>> environments, independent of my local setup. It also saves you
>> > from a
>> > > > >> local
>> > > > >>> Maven dependency.
>> > > > >>>
>> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
>> > > ralph.goers@dslextreme.com>
>> > > > >>>> wrote:
>> > > > >>>>
>> > > > >>>> I deleted the files from my local repo and restarted the
>> build. It
>> > > is
>> > > > >>>> running along just fine - at least until it hits json template
>> > > layout.
>> > > > >>>>
>> > > > >>>> Is there a reason you use the maven wrapper instead of Maven
>> > > itself? I
>> > > > >>>> have never used the wrapper. I am wondering if there is
>> something
>> > > going
>> > > > >> on
>> > > > >>>> there.
>> > > > >>>>
>> > > > >>>> Ralph
>> > > > >>>>
>> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
>> > > ralph.goers@dslextreme.com>
>> > > > >>>> wrote:
>> > > > >>>>>
>> > > > >>>>> I’ve never seen that. What is
>> > > maven-annotations-production:log4j-api?
>> > > > >>>>>
>> > > > >>>>> Let me try removing the files from my maven local repo as you
>> > did.
>> > > > >>>>>
>> > > > >>>>> Ralph
>> > > > >>>>>
>> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
>> > > volkan.yazici@gmail.com>
>> > > > >>>> wrote:
>> > > > >>>>>>
>> > > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
>> > after
>> > > > >> Java
>> > > > >>>> 11
>> > > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
>> > clean
>> > > > >> Maven
>> > > > >>>>>> build:
>> > > > >>>>>>
>> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
>> > > > >>>>>> $ rm -rf
>> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
>> > > > >>>>>>
>> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't
>> get it
>> > > to
>> > > > >> have
>> > > > >>>>>> successful build:
>> > > > >>>>>>
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>> W: Output path
>> > > > >>>>>>
>> > > > >>>>
>> > > > >>
>> > >
>> >
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>> > > > >>>>>> intersects with a source root. Only files that were created
>> by
>> > > build
>> > > > >>>> will
>> > > > >>>>>> be cleaned
>> > > > >>>>>>
>> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
>> because
>> > > it is
>> > > > >>>>>> included into a circular dependency (module 'log4j-api'
>> > > production,
>> > > > >>>>>> maven-annotations-production:log4j-api, module
>> 'log4j-plugins'
>> > > > >>>> production,
>> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
>> > > > >>>>>> maven-annotations-test:log4j-plugins because it is included
>> > into a
>> > > > >>>> circular
>> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
>> > > 'log4j-api'
>> > > > >>>> tests,
>> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
>> tests)*
>> > > > >>>>>>
>> > > > >>>>>> Did you get it working? What shall I do to make it work?
>> > > > >>>>>
>> > > > >>>>>
>> > > > >>>>>
>> > > > >>>>
>> > > > >>>>
>> > > > >>>>
>> > > > >>
>> > > > >>
>> > > > >>
>> > > >
>> > > >
>> > >
>> >
>>
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Sixx XT <si...@gmail.com>.
Facebook Group:
https://fb.com/groups/236181883796840/
<https://www.facebook.com/groups/236181883796840/>
Telegram Group: https://t.me/HttpInjectorGroup
On Mon, Apr 19, 2021, 6:34 PM Tim Perry <ti...@gmail.com> wrote:
> Can any of you recommend an idiots guide to setting up a log4j development
> environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
> work with a maven project with multiple module-info.java files. There are
> bugs into the maven-eclipse tools (m2e) for this.
>
> I cannot see reverting to 1999 and using the command line debugger, so
> IntelliJ seems like my best shot at getting a working development
> environment. I just want autocomplete and the ability to connect a debugger
> without too much hoop jumping.
>
> Thanks,
> Tim
>
> On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
> wrote:
>
> > I have also tried that too, but no luck so far. @Matt, are you able to
> run
> > any tests from IDEA using the most recent "master"?
> >
> > On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
> >
> > > See also
> > >
> >
> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
> > >
> > > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
> > > wrote:
> > > >
> > > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote
> debug
> > > options”
> > > >
> > > > Ralph
> > > >
> > > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <volkan.yazici@gmail.com
> >
> > > wrote:
> > > > >
> > > > > Okay, fair enough. Thanks so much for sharing these details, I
> > really
> > > > > appreciated it. One final question: If you want to debug a single
> > > test, how
> > > > > does your work flow look like? Do you create a new "Run
> > Configuration"
> > > > > invoking a certain Maven command triggering the code/test that you
> > are
> > > > > interested in and "Debug Run"ing that "Run Configuration"?
> > > > >
> > > > > For the records, I still would like to hear how I can make IDEA to
> > > simply
> > > > > run a test. If anybody has succeeded in doing that, I am all ears.
> > > > >
> > > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <ralph.goers@dslextreme.com
> >
> > > wrote:
> > > > >>
> > > > >> I will be honest. I have never tun any log4j tests in IntelliJ. I
> > > rarely
> > > > >> do it for any projects I work on. I use JVM remote debug all the
> > > time. I
> > > > >> don’t want to force others to have to do that, but I just never
> > think
> > > about
> > > > >> it.
> > > > >>
> > > > >> I use various versions of Maven from time to time. 3.6.1 is the
> > > default on
> > > > >> my Mac but I just installed 3.8.1 to validate what I needed to
> > change
> > > in my
> > > > >> setup to make it still work with my employers Nexus repository
> which
> > > still
> > > > >> uses http.
> > > > >>
> > > > >> When I am working on Log4J stuff I do a full mvn clean install
> > several
> > > > >> times a day. That takes a huge amount of time so I have learned to
> > > > >> multitask and work on other stuff while builds are running.
> > > > >>
> > > > >> Ralph.
> > > > >>
> > > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
> > volkan.yazici@gmail.com>
> > > > >> wrote:
> > > > >>>
> > > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
> > *.iml
> > > > >> files
> > > > >>> and .idea directory), compile the sources via Maven, and open the
> > > folder
> > > > >> in
> > > > >>> IDEA, can you run *any* tests? If so, do you have any custom IDEA
> > > > >>> configurations? Which IDEA version are you using? If you are not
> > > using
> > > > >> the
> > > > >>> wrapper, which Maven version are you using?
> > > > >>>
> > > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
> > > > >>> environments, independent of my local setup. It also saves you
> > from a
> > > > >> local
> > > > >>> Maven dependency.
> > > > >>>
> > > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
> > > ralph.goers@dslextreme.com>
> > > > >>>> wrote:
> > > > >>>>
> > > > >>>> I deleted the files from my local repo and restarted the build.
> It
> > > is
> > > > >>>> running along just fine - at least until it hits json template
> > > layout.
> > > > >>>>
> > > > >>>> Is there a reason you use the maven wrapper instead of Maven
> > > itself? I
> > > > >>>> have never used the wrapper. I am wondering if there is
> something
> > > going
> > > > >> on
> > > > >>>> there.
> > > > >>>>
> > > > >>>> Ralph
> > > > >>>>
> > > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
> > > ralph.goers@dslextreme.com>
> > > > >>>> wrote:
> > > > >>>>>
> > > > >>>>> I’ve never seen that. What is
> > > maven-annotations-production:log4j-api?
> > > > >>>>>
> > > > >>>>> Let me try removing the files from my maven local repo as you
> > did.
> > > > >>>>>
> > > > >>>>> Ralph
> > > > >>>>>
> > > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
> > > volkan.yazici@gmail.com>
> > > > >>>> wrote:
> > > > >>>>>>
> > > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
> > after
> > > > >> Java
> > > > >>>> 11
> > > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
> > clean
> > > > >> Maven
> > > > >>>>>> build:
> > > > >>>>>>
> > > > >>>>>> $ rm -rf ./.idea ./**/*.iml
> > > > >>>>>> $ rm -rf
> ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> > > > >>>>>> $ ./mvnw clean install -DskipTests=true
> > > > >>>>>>
> > > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get
> it
> > > to
> > > > >> have
> > > > >>>>>> successful build:
> > > > >>>>>>
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>> W: Output path
> > > > >>>>>>
> > > > >>>>
> > > > >>
> > >
> >
> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> > > > >>>>>> intersects with a source root. Only files that were created by
> > > build
> > > > >>>> will
> > > > >>>>>> be cleaned
> > > > >>>>>>
> > > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api
> because
> > > it is
> > > > >>>>>> included into a circular dependency (module 'log4j-api'
> > > production,
> > > > >>>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
> > > > >>>> production,
> > > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
> > > > >>>>>> maven-annotations-test:log4j-plugins because it is included
> > into a
> > > > >>>> circular
> > > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
> > > 'log4j-api'
> > > > >>>> tests,
> > > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins'
> tests)*
> > > > >>>>>>
> > > > >>>>>> Did you get it working? What shall I do to make it work?
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Tim Perry <ti...@gmail.com>.
Can any of you recommend an idiots guide to setting up a log4j development
environment in IntelliJ? I have never used IntelliJ before. Eclipse won't
work with a maven project with multiple module-info.java files. There are
bugs into the maven-eclipse tools (m2e) for this.
I cannot see reverting to 1999 and using the command line debugger, so
IntelliJ seems like my best shot at getting a working development
environment. I just want autocomplete and the ability to connect a debugger
without too much hoop jumping.
Thanks,
Tim
On Thu, Apr 8, 2021 at 5:17 AM Volkan Yazıcı <vo...@gmail.com>
wrote:
> I have also tried that too, but no luck so far. @Matt, are you able to run
> any tests from IDEA using the most recent "master"?
>
> On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
>
> > See also
> >
> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
> >
> > On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
> > wrote:
> > >
> > > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote debug
> > options”
> > >
> > > Ralph
> > >
> > > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <vo...@gmail.com>
> > wrote:
> > > >
> > > > Okay, fair enough. Thanks so much for sharing these details, I
> really
> > > > appreciated it. One final question: If you want to debug a single
> > test, how
> > > > does your work flow look like? Do you create a new "Run
> Configuration"
> > > > invoking a certain Maven command triggering the code/test that you
> are
> > > > interested in and "Debug Run"ing that "Run Configuration"?
> > > >
> > > > For the records, I still would like to hear how I can make IDEA to
> > simply
> > > > run a test. If anybody has succeeded in doing that, I am all ears.
> > > >
> > > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <ra...@dslextreme.com>
> > wrote:
> > > >>
> > > >> I will be honest. I have never tun any log4j tests in IntelliJ. I
> > rarely
> > > >> do it for any projects I work on. I use JVM remote debug all the
> > time. I
> > > >> don’t want to force others to have to do that, but I just never
> think
> > about
> > > >> it.
> > > >>
> > > >> I use various versions of Maven from time to time. 3.6.1 is the
> > default on
> > > >> my Mac but I just installed 3.8.1 to validate what I needed to
> change
> > in my
> > > >> setup to make it still work with my employers Nexus repository which
> > still
> > > >> uses http.
> > > >>
> > > >> When I am working on Log4J stuff I do a full mvn clean install
> several
> > > >> times a day. That takes a huge amount of time so I have learned to
> > > >> multitask and work on other stuff while builds are running.
> > > >>
> > > >> Ralph.
> > > >>
> > > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <
> volkan.yazici@gmail.com>
> > > >> wrote:
> > > >>>
> > > >>> Ralph, when you delete the IDEA-specific configuration (i.e.,
> *.iml
> > > >> files
> > > >>> and .idea directory), compile the sources via Maven, and open the
> > folder
> > > >> in
> > > >>> IDEA, can you run *any* tests? If so, do you have any custom IDEA
> > > >>> configurations? Which IDEA version are you using? If you are not
> > using
> > > >> the
> > > >>> wrapper, which Maven version are you using?
> > > >>>
> > > >>> I use Maven Wrapper to make sure Maven behaves the same in all
> > > >>> environments, independent of my local setup. It also saves you
> from a
> > > >> local
> > > >>> Maven dependency.
> > > >>>
> > > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
> > ralph.goers@dslextreme.com>
> > > >>>> wrote:
> > > >>>>
> > > >>>> I deleted the files from my local repo and restarted the build. It
> > is
> > > >>>> running along just fine - at least until it hits json template
> > layout.
> > > >>>>
> > > >>>> Is there a reason you use the maven wrapper instead of Maven
> > itself? I
> > > >>>> have never used the wrapper. I am wondering if there is something
> > going
> > > >> on
> > > >>>> there.
> > > >>>>
> > > >>>> Ralph
> > > >>>>
> > > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
> > ralph.goers@dslextreme.com>
> > > >>>> wrote:
> > > >>>>>
> > > >>>>> I’ve never seen that. What is
> > maven-annotations-production:log4j-api?
> > > >>>>>
> > > >>>>> Let me try removing the files from my maven local repo as you
> did.
> > > >>>>>
> > > >>>>> Ralph
> > > >>>>>
> > > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
> > volkan.yazici@gmail.com>
> > > >>>> wrote:
> > > >>>>>>
> > > >>>>>> As subject hints, I am not able to run tests in IDEA anymore
> after
> > > >> Java
> > > >>>> 11
> > > >>>>>> upgrade. I have deleted all IDEA related files and issued a
> clean
> > > >> Maven
> > > >>>>>> build:
> > > >>>>>>
> > > >>>>>> $ rm -rf ./.idea ./**/*.iml
> > > >>>>>> $ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> > > >>>>>> $ ./mvnw clean install -DskipTests=true
> > > >>>>>>
> > > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get it
> > to
> > > >> have
> > > >>>>>> successful build:
> > > >>>>>>
> > > >>>>>> W: Output path
> > > >>>>>>
> > > >>>>
> > > >>
> > /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> > > >>>>>> intersects with a source root. Only files that were created by
> > build
> > > >>>> will
> > > >>>>>> be cleaned
> > > >>>>>> W: Output path
> > > >>>>>>
> > > >>>>
> > > >>
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> > > >>>>>> intersects with a source root. Only files that were created by
> > build
> > > >>>> will
> > > >>>>>> be cleaned
> > > >>>>>> W: Output path
> > > >>>>>>
> > > >>>>
> > > >>
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> > > >>>>>> intersects with a source root. Only files that were created by
> > build
> > > >>>> will
> > > >>>>>> be cleaned
> > > >>>>>> W: Output path
> > > >>>>>>
> > > >>>>
> > > >>
> >
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> > > >>>>>> intersects with a source root. Only files that were created by
> > build
> > > >>>> will
> > > >>>>>> be cleaned
> > > >>>>>> W: Output path
> > > >>>>>>
> > > >>>>
> > > >>
> >
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> > > >>>>>> intersects with a source root. Only files that were created by
> > build
> > > >>>> will
> > > >>>>>> be cleaned
> > > >>>>>> W: Output path
> > > >>>>>>
> > > >>>>
> > > >>
> >
> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> > > >>>>>> intersects with a source root. Only files that were created by
> > build
> > > >>>> will
> > > >>>>>> be cleaned
> > > >>>>>> W: Output path
> > > >>>>>>
> > > >>>>
> > > >>
> >
> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> > > >>>>>> intersects with a source root. Only files that were created by
> > build
> > > >>>> will
> > > >>>>>> be cleaned
> > > >>>>>>
> > > >>>>>> *E: Cannot build maven-annotations-production:log4j-api because
> > it is
> > > >>>>>> included into a circular dependency (module 'log4j-api'
> > production,
> > > >>>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
> > > >>>> production,
> > > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
> > > >>>>>> maven-annotations-test:log4j-plugins because it is included
> into a
> > > >>>> circular
> > > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
> > 'log4j-api'
> > > >>>> tests,
> > > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
> > > >>>>>>
> > > >>>>>> Did you get it working? What shall I do to make it work?
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>
> > > >>
> > > >>
> > >
> > >
> >
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Volkan Yazıcı <vo...@gmail.com>.
I have also tried that too, but no luck so far. @Matt, are you able to run
any tests from IDEA using the most recent "master"?
On Wed, Apr 7, 2021 at 5:57 PM Matt Sicker <bo...@gmail.com> wrote:
> See also
> https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
>
> On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >
> > mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote debug
> options”
> >
> > Ralph
> >
> > > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <vo...@gmail.com>
> wrote:
> > >
> > > Okay, fair enough. Thanks so much for sharing these details, I really
> > > appreciated it. One final question: If you want to debug a single
> test, how
> > > does your work flow look like? Do you create a new "Run Configuration"
> > > invoking a certain Maven command triggering the code/test that you are
> > > interested in and "Debug Run"ing that "Run Configuration"?
> > >
> > > For the records, I still would like to hear how I can make IDEA to
> simply
> > > run a test. If anybody has succeeded in doing that, I am all ears.
> > >
> > >> On Wed, Apr 7, 2021 at 3:38 PM Apache <ra...@dslextreme.com>
> wrote:
> > >>
> > >> I will be honest. I have never tun any log4j tests in IntelliJ. I
> rarely
> > >> do it for any projects I work on. I use JVM remote debug all the
> time. I
> > >> don’t want to force others to have to do that, but I just never think
> about
> > >> it.
> > >>
> > >> I use various versions of Maven from time to time. 3.6.1 is the
> default on
> > >> my Mac but I just installed 3.8.1 to validate what I needed to change
> in my
> > >> setup to make it still work with my employers Nexus repository which
> still
> > >> uses http.
> > >>
> > >> When I am working on Log4J stuff I do a full mvn clean install several
> > >> times a day. That takes a huge amount of time so I have learned to
> > >> multitask and work on other stuff while builds are running.
> > >>
> > >> Ralph.
> > >>
> > >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <vo...@gmail.com>
> > >> wrote:
> > >>>
> > >>> Ralph, when you delete the IDEA-specific configuration (i.e., *.iml
> > >> files
> > >>> and .idea directory), compile the sources via Maven, and open the
> folder
> > >> in
> > >>> IDEA, can you run *any* tests? If so, do you have any custom IDEA
> > >>> configurations? Which IDEA version are you using? If you are not
> using
> > >> the
> > >>> wrapper, which Maven version are you using?
> > >>>
> > >>> I use Maven Wrapper to make sure Maven behaves the same in all
> > >>> environments, independent of my local setup. It also saves you from a
> > >> local
> > >>> Maven dependency.
> > >>>
> > >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <
> ralph.goers@dslextreme.com>
> > >>>> wrote:
> > >>>>
> > >>>> I deleted the files from my local repo and restarted the build. It
> is
> > >>>> running along just fine - at least until it hits json template
> layout.
> > >>>>
> > >>>> Is there a reason you use the maven wrapper instead of Maven
> itself? I
> > >>>> have never used the wrapper. I am wondering if there is something
> going
> > >> on
> > >>>> there.
> > >>>>
> > >>>> Ralph
> > >>>>
> > >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <
> ralph.goers@dslextreme.com>
> > >>>> wrote:
> > >>>>>
> > >>>>> I’ve never seen that. What is
> maven-annotations-production:log4j-api?
> > >>>>>
> > >>>>> Let me try removing the files from my maven local repo as you did.
> > >>>>>
> > >>>>> Ralph
> > >>>>>
> > >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <
> volkan.yazici@gmail.com>
> > >>>> wrote:
> > >>>>>>
> > >>>>>> As subject hints, I am not able to run tests in IDEA anymore after
> > >> Java
> > >>>> 11
> > >>>>>> upgrade. I have deleted all IDEA related files and issued a clean
> > >> Maven
> > >>>>>> build:
> > >>>>>>
> > >>>>>> $ rm -rf ./.idea ./**/*.iml
> > >>>>>> $ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> > >>>>>> $ ./mvnw clean install -DskipTests=true
> > >>>>>>
> > >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get it
> to
> > >> have
> > >>>>>> successful build:
> > >>>>>>
> > >>>>>> W: Output path
> > >>>>>>
> > >>>>
> > >>
> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> > >>>>>> intersects with a source root. Only files that were created by
> build
> > >>>> will
> > >>>>>> be cleaned
> > >>>>>> W: Output path
> > >>>>>>
> > >>>>
> > >>
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> > >>>>>> intersects with a source root. Only files that were created by
> build
> > >>>> will
> > >>>>>> be cleaned
> > >>>>>> W: Output path
> > >>>>>>
> > >>>>
> > >>
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> > >>>>>> intersects with a source root. Only files that were created by
> build
> > >>>> will
> > >>>>>> be cleaned
> > >>>>>> W: Output path
> > >>>>>>
> > >>>>
> > >>
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> > >>>>>> intersects with a source root. Only files that were created by
> build
> > >>>> will
> > >>>>>> be cleaned
> > >>>>>> W: Output path
> > >>>>>>
> > >>>>
> > >>
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> > >>>>>> intersects with a source root. Only files that were created by
> build
> > >>>> will
> > >>>>>> be cleaned
> > >>>>>> W: Output path
> > >>>>>>
> > >>>>
> > >>
> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> > >>>>>> intersects with a source root. Only files that were created by
> build
> > >>>> will
> > >>>>>> be cleaned
> > >>>>>> W: Output path
> > >>>>>>
> > >>>>
> > >>
> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> > >>>>>> intersects with a source root. Only files that were created by
> build
> > >>>> will
> > >>>>>> be cleaned
> > >>>>>>
> > >>>>>> *E: Cannot build maven-annotations-production:log4j-api because
> it is
> > >>>>>> included into a circular dependency (module 'log4j-api'
> production,
> > >>>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
> > >>>> production,
> > >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
> > >>>>>> maven-annotations-test:log4j-plugins because it is included into a
> > >>>> circular
> > >>>>>> dependency (maven-annotations-test:log4j-plugins, module
> 'log4j-api'
> > >>>> tests,
> > >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
> > >>>>>>
> > >>>>>> Did you get it working? What shall I do to make it work?
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>>
> > >>
> > >>
> > >>
> >
> >
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Matt Sicker <bo...@gmail.com>.
See also https://lists.apache.org/thread.html/2ba2225043a6ca7d2c43e4293323309b041bd8d486516cc50fec61cd%40%3Cdev.logging.apache.org%3E
On Wed, 7 Apr 2021 at 09:17, Ralph Goers <ra...@dslextreme.com> wrote:
>
> mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote debug options”
>
> Ralph
>
> > On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <vo...@gmail.com> wrote:
> >
> > Okay, fair enough. Thanks so much for sharing these details, I really
> > appreciated it. One final question: If you want to debug a single test, how
> > does your work flow look like? Do you create a new "Run Configuration"
> > invoking a certain Maven command triggering the code/test that you are
> > interested in and "Debug Run"ing that "Run Configuration"?
> >
> > For the records, I still would like to hear how I can make IDEA to simply
> > run a test. If anybody has succeeded in doing that, I am all ears.
> >
> >> On Wed, Apr 7, 2021 at 3:38 PM Apache <ra...@dslextreme.com> wrote:
> >>
> >> I will be honest. I have never tun any log4j tests in IntelliJ. I rarely
> >> do it for any projects I work on. I use JVM remote debug all the time. I
> >> don’t want to force others to have to do that, but I just never think about
> >> it.
> >>
> >> I use various versions of Maven from time to time. 3.6.1 is the default on
> >> my Mac but I just installed 3.8.1 to validate what I needed to change in my
> >> setup to make it still work with my employers Nexus repository which still
> >> uses http.
> >>
> >> When I am working on Log4J stuff I do a full mvn clean install several
> >> times a day. That takes a huge amount of time so I have learned to
> >> multitask and work on other stuff while builds are running.
> >>
> >> Ralph.
> >>
> >>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <vo...@gmail.com>
> >> wrote:
> >>>
> >>> Ralph, when you delete the IDEA-specific configuration (i.e., *.iml
> >> files
> >>> and .idea directory), compile the sources via Maven, and open the folder
> >> in
> >>> IDEA, can you run *any* tests? If so, do you have any custom IDEA
> >>> configurations? Which IDEA version are you using? If you are not using
> >> the
> >>> wrapper, which Maven version are you using?
> >>>
> >>> I use Maven Wrapper to make sure Maven behaves the same in all
> >>> environments, independent of my local setup. It also saves you from a
> >> local
> >>> Maven dependency.
> >>>
> >>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <ra...@dslextreme.com>
> >>>> wrote:
> >>>>
> >>>> I deleted the files from my local repo and restarted the build. It is
> >>>> running along just fine - at least until it hits json template layout.
> >>>>
> >>>> Is there a reason you use the maven wrapper instead of Maven itself? I
> >>>> have never used the wrapper. I am wondering if there is something going
> >> on
> >>>> there.
> >>>>
> >>>> Ralph
> >>>>
> >>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <ra...@dslextreme.com>
> >>>> wrote:
> >>>>>
> >>>>> I’ve never seen that. What is maven-annotations-production:log4j-api?
> >>>>>
> >>>>> Let me try removing the files from my maven local repo as you did.
> >>>>>
> >>>>> Ralph
> >>>>>
> >>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <vo...@gmail.com>
> >>>> wrote:
> >>>>>>
> >>>>>> As subject hints, I am not able to run tests in IDEA anymore after
> >> Java
> >>>> 11
> >>>>>> upgrade. I have deleted all IDEA related files and issued a clean
> >> Maven
> >>>>>> build:
> >>>>>>
> >>>>>> $ rm -rf ./.idea ./**/*.iml
> >>>>>> $ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> >>>>>> $ ./mvnw clean install -DskipTests=true
> >>>>>>
> >>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get it to
> >> have
> >>>>>> successful build:
> >>>>>>
> >>>>>> W: Output path
> >>>>>>
> >>>>
> >> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> >>>>>> intersects with a source root. Only files that were created by build
> >>>> will
> >>>>>> be cleaned
> >>>>>> W: Output path
> >>>>>>
> >>>>
> >> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> >>>>>> intersects with a source root. Only files that were created by build
> >>>> will
> >>>>>> be cleaned
> >>>>>> W: Output path
> >>>>>>
> >>>>
> >> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> >>>>>> intersects with a source root. Only files that were created by build
> >>>> will
> >>>>>> be cleaned
> >>>>>> W: Output path
> >>>>>>
> >>>>
> >> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> >>>>>> intersects with a source root. Only files that were created by build
> >>>> will
> >>>>>> be cleaned
> >>>>>> W: Output path
> >>>>>>
> >>>>
> >> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> >>>>>> intersects with a source root. Only files that were created by build
> >>>> will
> >>>>>> be cleaned
> >>>>>> W: Output path
> >>>>>>
> >>>>
> >> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> >>>>>> intersects with a source root. Only files that were created by build
> >>>> will
> >>>>>> be cleaned
> >>>>>> W: Output path
> >>>>>>
> >>>>
> >> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> >>>>>> intersects with a source root. Only files that were created by build
> >>>> will
> >>>>>> be cleaned
> >>>>>>
> >>>>>> *E: Cannot build maven-annotations-production:log4j-api because it is
> >>>>>> included into a circular dependency (module 'log4j-api' production,
> >>>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
> >>>> production,
> >>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
> >>>>>> maven-annotations-test:log4j-plugins because it is included into a
> >>>> circular
> >>>>>> dependency (maven-annotations-test:log4j-plugins, module 'log4j-api'
> >>>> tests,
> >>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
> >>>>>>
> >>>>>> Did you get it working? What shall I do to make it work?
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>
> >>
> >>
>
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Ralph Goers <ra...@dslextreme.com>.
mvn surefire:test -Dtest=TestClass -Dmaven.surefire.debug=“remote debug options”
Ralph
> On Apr 7, 2021, at 7:04 AM, Volkan Yazıcı <vo...@gmail.com> wrote:
>
> Okay, fair enough. Thanks so much for sharing these details, I really
> appreciated it. One final question: If you want to debug a single test, how
> does your work flow look like? Do you create a new "Run Configuration"
> invoking a certain Maven command triggering the code/test that you are
> interested in and "Debug Run"ing that "Run Configuration"?
>
> For the records, I still would like to hear how I can make IDEA to simply
> run a test. If anybody has succeeded in doing that, I am all ears.
>
>> On Wed, Apr 7, 2021 at 3:38 PM Apache <ra...@dslextreme.com> wrote:
>>
>> I will be honest. I have never tun any log4j tests in IntelliJ. I rarely
>> do it for any projects I work on. I use JVM remote debug all the time. I
>> don’t want to force others to have to do that, but I just never think about
>> it.
>>
>> I use various versions of Maven from time to time. 3.6.1 is the default on
>> my Mac but I just installed 3.8.1 to validate what I needed to change in my
>> setup to make it still work with my employers Nexus repository which still
>> uses http.
>>
>> When I am working on Log4J stuff I do a full mvn clean install several
>> times a day. That takes a huge amount of time so I have learned to
>> multitask and work on other stuff while builds are running.
>>
>> Ralph.
>>
>>> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <vo...@gmail.com>
>> wrote:
>>>
>>> Ralph, when you delete the IDEA-specific configuration (i.e., *.iml
>> files
>>> and .idea directory), compile the sources via Maven, and open the folder
>> in
>>> IDEA, can you run *any* tests? If so, do you have any custom IDEA
>>> configurations? Which IDEA version are you using? If you are not using
>> the
>>> wrapper, which Maven version are you using?
>>>
>>> I use Maven Wrapper to make sure Maven behaves the same in all
>>> environments, independent of my local setup. It also saves you from a
>> local
>>> Maven dependency.
>>>
>>>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <ra...@dslextreme.com>
>>>> wrote:
>>>>
>>>> I deleted the files from my local repo and restarted the build. It is
>>>> running along just fine - at least until it hits json template layout.
>>>>
>>>> Is there a reason you use the maven wrapper instead of Maven itself? I
>>>> have never used the wrapper. I am wondering if there is something going
>> on
>>>> there.
>>>>
>>>> Ralph
>>>>
>>>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <ra...@dslextreme.com>
>>>> wrote:
>>>>>
>>>>> I’ve never seen that. What is maven-annotations-production:log4j-api?
>>>>>
>>>>> Let me try removing the files from my maven local repo as you did.
>>>>>
>>>>> Ralph
>>>>>
>>>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <vo...@gmail.com>
>>>> wrote:
>>>>>>
>>>>>> As subject hints, I am not able to run tests in IDEA anymore after
>> Java
>>>> 11
>>>>>> upgrade. I have deleted all IDEA related files and issued a clean
>> Maven
>>>>>> build:
>>>>>>
>>>>>> $ rm -rf ./.idea ./**/*.iml
>>>>>> $ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>>>>>> $ ./mvnw clean install -DskipTests=true
>>>>>>
>>>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get it to
>> have
>>>>>> successful build:
>>>>>>
>>>>>> W: Output path
>>>>>>
>>>>
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>>>>>> intersects with a source root. Only files that were created by build
>>>> will
>>>>>> be cleaned
>>>>>> W: Output path
>>>>>>
>>>>
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>>>>>> intersects with a source root. Only files that were created by build
>>>> will
>>>>>> be cleaned
>>>>>> W: Output path
>>>>>>
>>>>
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>>>>>> intersects with a source root. Only files that were created by build
>>>> will
>>>>>> be cleaned
>>>>>> W: Output path
>>>>>>
>>>>
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>>>>>> intersects with a source root. Only files that were created by build
>>>> will
>>>>>> be cleaned
>>>>>> W: Output path
>>>>>>
>>>>
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>>>>>> intersects with a source root. Only files that were created by build
>>>> will
>>>>>> be cleaned
>>>>>> W: Output path
>>>>>>
>>>>
>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>>>>>> intersects with a source root. Only files that were created by build
>>>> will
>>>>>> be cleaned
>>>>>> W: Output path
>>>>>>
>>>>
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>>>>>> intersects with a source root. Only files that were created by build
>>>> will
>>>>>> be cleaned
>>>>>>
>>>>>> *E: Cannot build maven-annotations-production:log4j-api because it is
>>>>>> included into a circular dependency (module 'log4j-api' production,
>>>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
>>>> production,
>>>>>> maven-annotations-production:log4j-plugins)E: Cannot build
>>>>>> maven-annotations-test:log4j-plugins because it is included into a
>>>> circular
>>>>>> dependency (maven-annotations-test:log4j-plugins, module 'log4j-api'
>>>> tests,
>>>>>> maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
>>>>>>
>>>>>> Did you get it working? What shall I do to make it work?
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>
>>
>>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Volkan Yazıcı <vo...@gmail.com>.
Okay, fair enough. Thanks so much for sharing these details, I really
appreciated it. One final question: If you want to debug a single test, how
does your work flow look like? Do you create a new "Run Configuration"
invoking a certain Maven command triggering the code/test that you are
interested in and "Debug Run"ing that "Run Configuration"?
For the records, I still would like to hear how I can make IDEA to simply
run a test. If anybody has succeeded in doing that, I am all ears.
On Wed, Apr 7, 2021 at 3:38 PM Apache <ra...@dslextreme.com> wrote:
> I will be honest. I have never tun any log4j tests in IntelliJ. I rarely
> do it for any projects I work on. I use JVM remote debug all the time. I
> don’t want to force others to have to do that, but I just never think about
> it.
>
> I use various versions of Maven from time to time. 3.6.1 is the default on
> my Mac but I just installed 3.8.1 to validate what I needed to change in my
> setup to make it still work with my employers Nexus repository which still
> uses http.
>
> When I am working on Log4J stuff I do a full mvn clean install several
> times a day. That takes a huge amount of time so I have learned to
> multitask and work on other stuff while builds are running.
>
> Ralph.
>
> > On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <vo...@gmail.com>
> wrote:
> >
> > Ralph, when you delete the IDEA-specific configuration (i.e., *.iml
> files
> > and .idea directory), compile the sources via Maven, and open the folder
> in
> > IDEA, can you run *any* tests? If so, do you have any custom IDEA
> > configurations? Which IDEA version are you using? If you are not using
> the
> > wrapper, which Maven version are you using?
> >
> > I use Maven Wrapper to make sure Maven behaves the same in all
> > environments, independent of my local setup. It also saves you from a
> local
> > Maven dependency.
> >
> >> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <ra...@dslextreme.com>
> >> wrote:
> >>
> >> I deleted the files from my local repo and restarted the build. It is
> >> running along just fine - at least until it hits json template layout.
> >>
> >> Is there a reason you use the maven wrapper instead of Maven itself? I
> >> have never used the wrapper. I am wondering if there is something going
> on
> >> there.
> >>
> >> Ralph
> >>
> >>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <ra...@dslextreme.com>
> >> wrote:
> >>>
> >>> I’ve never seen that. What is maven-annotations-production:log4j-api?
> >>>
> >>> Let me try removing the files from my maven local repo as you did.
> >>>
> >>> Ralph
> >>>
> >>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <vo...@gmail.com>
> >> wrote:
> >>>>
> >>>> As subject hints, I am not able to run tests in IDEA anymore after
> Java
> >> 11
> >>>> upgrade. I have deleted all IDEA related files and issued a clean
> Maven
> >>>> build:
> >>>>
> >>>> $ rm -rf ./.idea ./**/*.iml
> >>>> $ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> >>>> $ ./mvnw clean install -DskipTests=true
> >>>>
> >>>> Opened the directory using IDEA (2021.1 RC), but couldn't get it to
> have
> >>>> successful build:
> >>>>
> >>>> W: Output path
> >>>>
> >>
> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> >>>> intersects with a source root. Only files that were created by build
> >> will
> >>>> be cleaned
> >>>> W: Output path
> >>>>
> >>
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> >>>> intersects with a source root. Only files that were created by build
> >> will
> >>>> be cleaned
> >>>> W: Output path
> >>>>
> >>
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> >>>> intersects with a source root. Only files that were created by build
> >> will
> >>>> be cleaned
> >>>> W: Output path
> >>>>
> >>
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> >>>> intersects with a source root. Only files that were created by build
> >> will
> >>>> be cleaned
> >>>> W: Output path
> >>>>
> >>
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> >>>> intersects with a source root. Only files that were created by build
> >> will
> >>>> be cleaned
> >>>> W: Output path
> >>>>
> >>
> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> >>>> intersects with a source root. Only files that were created by build
> >> will
> >>>> be cleaned
> >>>> W: Output path
> >>>>
> >>
> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> >>>> intersects with a source root. Only files that were created by build
> >> will
> >>>> be cleaned
> >>>>
> >>>> *E: Cannot build maven-annotations-production:log4j-api because it is
> >>>> included into a circular dependency (module 'log4j-api' production,
> >>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
> >> production,
> >>>> maven-annotations-production:log4j-plugins)E: Cannot build
> >>>> maven-annotations-test:log4j-plugins because it is included into a
> >> circular
> >>>> dependency (maven-annotations-test:log4j-plugins, module 'log4j-api'
> >> tests,
> >>>> maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
> >>>>
> >>>> Did you get it working? What shall I do to make it work?
> >>>
> >>>
> >>>
> >>
> >>
> >>
>
>
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Apache <ra...@dslextreme.com>.
I will be honest. I have never tun any log4j tests in IntelliJ. I rarely do it for any projects I work on. I use JVM remote debug all the time. I don’t want to force others to have to do that, but I just never think about it.
I use various versions of Maven from time to time. 3.6.1 is the default on my Mac but I just installed 3.8.1 to validate what I needed to change in my setup to make it still work with my employers Nexus repository which still uses http.
When I am working on Log4J stuff I do a full mvn clean install several times a day. That takes a huge amount of time so I have learned to multitask and work on other stuff while builds are running.
Ralph.
> On Apr 7, 2021, at 12:15 AM, Volkan Yazıcı <vo...@gmail.com> wrote:
>
> Ralph, when you delete the IDEA-specific configuration (i.e., *.iml files
> and .idea directory), compile the sources via Maven, and open the folder in
> IDEA, can you run *any* tests? If so, do you have any custom IDEA
> configurations? Which IDEA version are you using? If you are not using the
> wrapper, which Maven version are you using?
>
> I use Maven Wrapper to make sure Maven behaves the same in all
> environments, independent of my local setup. It also saves you from a local
> Maven dependency.
>
>> On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>
>> I deleted the files from my local repo and restarted the build. It is
>> running along just fine - at least until it hits json template layout.
>>
>> Is there a reason you use the maven wrapper instead of Maven itself? I
>> have never used the wrapper. I am wondering if there is something going on
>> there.
>>
>> Ralph
>>
>>> On Apr 6, 2021, at 4:10 PM, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>>
>>> I’ve never seen that. What is maven-annotations-production:log4j-api?
>>>
>>> Let me try removing the files from my maven local repo as you did.
>>>
>>> Ralph
>>>
>>>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <vo...@gmail.com>
>> wrote:
>>>>
>>>> As subject hints, I am not able to run tests in IDEA anymore after Java
>> 11
>>>> upgrade. I have deleted all IDEA related files and issued a clean Maven
>>>> build:
>>>>
>>>> $ rm -rf ./.idea ./**/*.iml
>>>> $ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>>>> $ ./mvnw clean install -DskipTests=true
>>>>
>>>> Opened the directory using IDEA (2021.1 RC), but couldn't get it to have
>>>> successful build:
>>>>
>>>> W: Output path
>>>>
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>>>> intersects with a source root. Only files that were created by build
>> will
>>>> be cleaned
>>>> W: Output path
>>>>
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>>>> intersects with a source root. Only files that were created by build
>> will
>>>> be cleaned
>>>> W: Output path
>>>>
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>>>> intersects with a source root. Only files that were created by build
>> will
>>>> be cleaned
>>>> W: Output path
>>>>
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>>>> intersects with a source root. Only files that were created by build
>> will
>>>> be cleaned
>>>> W: Output path
>>>>
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>>>> intersects with a source root. Only files that were created by build
>> will
>>>> be cleaned
>>>> W: Output path
>>>>
>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>>>> intersects with a source root. Only files that were created by build
>> will
>>>> be cleaned
>>>> W: Output path
>>>>
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>>>> intersects with a source root. Only files that were created by build
>> will
>>>> be cleaned
>>>>
>>>> *E: Cannot build maven-annotations-production:log4j-api because it is
>>>> included into a circular dependency (module 'log4j-api' production,
>>>> maven-annotations-production:log4j-api, module 'log4j-plugins'
>> production,
>>>> maven-annotations-production:log4j-plugins)E: Cannot build
>>>> maven-annotations-test:log4j-plugins because it is included into a
>> circular
>>>> dependency (maven-annotations-test:log4j-plugins, module 'log4j-api'
>> tests,
>>>> maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
>>>>
>>>> Did you get it working? What shall I do to make it work?
>>>
>>>
>>>
>>
>>
>>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Volkan Yazıcı <vo...@gmail.com>.
Ralph, when you delete the IDEA-specific configuration (i.e., *.iml files
and .idea directory), compile the sources via Maven, and open the folder in
IDEA, can you run *any* tests? If so, do you have any custom IDEA
configurations? Which IDEA version are you using? If you are not using the
wrapper, which Maven version are you using?
I use Maven Wrapper to make sure Maven behaves the same in all
environments, independent of my local setup. It also saves you from a local
Maven dependency.
On Wed, Apr 7, 2021 at 1:17 AM Ralph Goers <ra...@dslextreme.com>
wrote:
> I deleted the files from my local repo and restarted the build. It is
> running along just fine - at least until it hits json template layout.
>
> Is there a reason you use the maven wrapper instead of Maven itself? I
> have never used the wrapper. I am wondering if there is something going on
> there.
>
> Ralph
>
> > On Apr 6, 2021, at 4:10 PM, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >
> > I’ve never seen that. What is maven-annotations-production:log4j-api?
> >
> > Let me try removing the files from my maven local repo as you did.
> >
> > Ralph
> >
> >> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <vo...@gmail.com>
> wrote:
> >>
> >> As subject hints, I am not able to run tests in IDEA anymore after Java
> 11
> >> upgrade. I have deleted all IDEA related files and issued a clean Maven
> >> build:
> >>
> >> $ rm -rf ./.idea ./**/*.iml
> >> $ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> >> $ ./mvnw clean install -DskipTests=true
> >>
> >> Opened the directory using IDEA (2021.1 RC), but couldn't get it to have
> >> successful build:
> >>
> >> W: Output path
> >>
> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> >> intersects with a source root. Only files that were created by build
> will
> >> be cleaned
> >> W: Output path
> >>
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> >> intersects with a source root. Only files that were created by build
> will
> >> be cleaned
> >> W: Output path
> >>
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> >> intersects with a source root. Only files that were created by build
> will
> >> be cleaned
> >> W: Output path
> >>
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> >> intersects with a source root. Only files that were created by build
> will
> >> be cleaned
> >> W: Output path
> >>
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> >> intersects with a source root. Only files that were created by build
> will
> >> be cleaned
> >> W: Output path
> >>
> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> >> intersects with a source root. Only files that were created by build
> will
> >> be cleaned
> >> W: Output path
> >>
> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> >> intersects with a source root. Only files that were created by build
> will
> >> be cleaned
> >>
> >> *E: Cannot build maven-annotations-production:log4j-api because it is
> >> included into a circular dependency (module 'log4j-api' production,
> >> maven-annotations-production:log4j-api, module 'log4j-plugins'
> production,
> >> maven-annotations-production:log4j-plugins)E: Cannot build
> >> maven-annotations-test:log4j-plugins because it is included into a
> circular
> >> dependency (maven-annotations-test:log4j-plugins, module 'log4j-api'
> tests,
> >> maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
> >>
> >> Did you get it working? What shall I do to make it work?
> >
> >
> >
>
>
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Ralph Goers <ra...@dslextreme.com>.
I deleted the files from my local repo and restarted the build. It is running along just fine - at least until it hits json template layout.
Is there a reason you use the maven wrapper instead of Maven itself? I have never used the wrapper. I am wondering if there is something going on there.
Ralph
> On Apr 6, 2021, at 4:10 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>
> I’ve never seen that. What is maven-annotations-production:log4j-api?
>
> Let me try removing the files from my maven local repo as you did.
>
> Ralph
>
>> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <vo...@gmail.com> wrote:
>>
>> As subject hints, I am not able to run tests in IDEA anymore after Java 11
>> upgrade. I have deleted all IDEA related files and issued a clean Maven
>> build:
>>
>> $ rm -rf ./.idea ./**/*.iml
>> $ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
>> $ ./mvnw clean install -DskipTests=true
>>
>> Opened the directory using IDEA (2021.1 RC), but couldn't get it to have
>> successful build:
>>
>> W: Output path
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
>> intersects with a source root. Only files that were created by build will
>> be cleaned
>> W: Output path
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
>> intersects with a source root. Only files that were created by build will
>> be cleaned
>> W: Output path
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
>> intersects with a source root. Only files that were created by build will
>> be cleaned
>> W: Output path
>> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
>> intersects with a source root. Only files that were created by build will
>> be cleaned
>> W: Output path
>> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
>> intersects with a source root. Only files that were created by build will
>> be cleaned
>> W: Output path
>> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
>> intersects with a source root. Only files that were created by build will
>> be cleaned
>> W: Output path
>> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
>> intersects with a source root. Only files that were created by build will
>> be cleaned
>>
>> *E: Cannot build maven-annotations-production:log4j-api because it is
>> included into a circular dependency (module 'log4j-api' production,
>> maven-annotations-production:log4j-api, module 'log4j-plugins' production,
>> maven-annotations-production:log4j-plugins)E: Cannot build
>> maven-annotations-test:log4j-plugins because it is included into a circular
>> dependency (maven-annotations-test:log4j-plugins, module 'log4j-api' tests,
>> maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
>>
>> Did you get it working? What shall I do to make it work?
>
>
>
Re: Running "master" tests in IntelliJ IDEA after Java 11 upgrade
Posted by Ralph Goers <ra...@dslextreme.com>.
I’ve never seen that. What is maven-annotations-production:log4j-api?
Let me try removing the files from my maven local repo as you did.
Ralph
> On Apr 6, 2021, at 1:14 PM, Volkan Yazıcı <vo...@gmail.com> wrote:
>
> As subject hints, I am not able to run tests in IDEA anymore after Java 11
> upgrade. I have deleted all IDEA related files and issued a clean Maven
> build:
>
> $ rm -rf ./.idea ./**/*.iml
> $ rm -rf ~/.m2/repository/org/apache/logging/log4j/*/3*-SNAPSHOT
> $ ./mvnw clean install -DskipTests=true
>
> Opened the directory using IDEA (2021.1 RC), but couldn't get it to have
> successful build:
>
> W: Output path
> /home/vy/Projects/log4j/3/log4j-core/target/generated-sources/annotations
> intersects with a source root. Only files that were created by build will
> be cleaned
> W: Output path
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-test-sources/test-annotations
> intersects with a source root. Only files that were created by build will
> be cleaned
> W: Output path
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-test-sources/test-annotations
> intersects with a source root. Only files that were created by build will
> be cleaned
> W: Output path
> /home/vy/Projects/log4j/3/log4j-plugins/target/generated-sources/annotations
> intersects with a source root. Only files that were created by build will
> be cleaned
> W: Output path
> /home/vy/Projects/log4j/3/log4j-layout-template-json/target/generated-sources/annotations
> intersects with a source root. Only files that were created by build will
> be cleaned
> W: Output path
> /home/vy/Projects/log4j/3/log4j-layout-jackson-json/target/generated-sources/annotations
> intersects with a source root. Only files that were created by build will
> be cleaned
> W: Output path
> /home/vy/Projects/log4j/3/log4j-core/target/generated-test-sources/test-annotations
> intersects with a source root. Only files that were created by build will
> be cleaned
>
> *E: Cannot build maven-annotations-production:log4j-api because it is
> included into a circular dependency (module 'log4j-api' production,
> maven-annotations-production:log4j-api, module 'log4j-plugins' production,
> maven-annotations-production:log4j-plugins)E: Cannot build
> maven-annotations-test:log4j-plugins because it is included into a circular
> dependency (maven-annotations-test:log4j-plugins, module 'log4j-api' tests,
> maven-annotations-test:log4j-api, module 'log4j-plugins' tests)*
>
> Did you get it working? What shall I do to make it work?