compilerArgs can accept any inner tags, is it expected behaviour?

2025-04-28 Thread Alexander Bubenchikov
Could anyone tell me, is it an expected behaviour, and is it an issue in Javadoc (I think it worth documenting), or the second configuration should be treated as invalid? -- Alexander Bubenchikov JetBrains - To unsubscribe, e-mail

Re: Found Issues - Release Apache Maven Version 3.6.2

2019-09-02 Thread Alexander Bubenchikov
/maven/cli/MavenCli.java#L276-L288 > > Cheers > Tibor17 > > On Thu, Aug 29, 2019 at 3:39 PM Alexander Bubenchikov < > alexander.bubenchi...@jetbrains.com> wrote: > > > Hi Stuart > > E.g. > > > https://github.com/JetBrains/intellij-community/blob

Re: Found Issues - Release Apache Maven Version 3.6.2

2019-08-29 Thread Alexander Bubenchikov
ution.rmi.RemoteUtil$1$1.invoke(RemoteUtil.java:153) > >> > at com.sun.proxy.$Proxy216.customize(Unknown Source) > >> > at > >> > > >> > org.jetbrains.idea.maven.server.MavenEmbedderWrapper.doCustomize(MavenEmbedderWrapper.java:92) > >> > at > >> > > >> > org.jetbrains.idea.maven.server.MavenEmbedderWrapper.onWrappeeCreated(MavenEmbedderWrapper.java:45) > >> > at > >> > > >> > org.jetbrains.idea.maven.server.RemoteObjectWrapper.getOrCreateWrappee(RemoteObjectWrapper.java:42) > >> > at > >> > > >> > org.jetbrains.idea.maven.server.MavenEmbedderWrapper.doCustomize(MavenEmbedderWrapper.java:92) > >> > at > >> > > >> > org.jetbrains.idea.maven.server.MavenEmbedderWrapper.lambda$customizeForResolve$1(MavenEmbedderWrapper.java:65) > >> > at > >> > > >> > org.jetbrains.idea.maven.server.RemoteObjectWrapper.perform(RemoteObjectWrapper.java:76) > >> > at > >> > > >> > org.jetbrains.idea.maven.server.MavenEmbedderWrapper.customizeForResolve(MavenEmbedderWrapper.java:64) > >> > at > >> > > >> > org.jetbrains.idea.maven.project.MavenProjectsTree.resolve(MavenProjectsTree.java:1261) > >> > at > >> > > >> > org.jetbrains.idea.maven.project.MavenProjectsProcessorResolvingTask.perform(MavenProjectsProcessorResolvingTask.java:45) > >> > at > >> > > >> > org.jetbrains.idea.maven.project.MavenProjectsProcessor.doProcessPendingTasks(MavenProjectsProcessor.java:140) > >> > at > >> > > >> > org.jetbrains.idea.maven.project.MavenProjectsProcessor.access$000(MavenProjectsProcessor.java:33) > >> > at > >> > > >> > org.jetbrains.idea.maven.project.MavenProjectsProcessor$2.run(MavenProjectsProcessor.java:114) > >> > at > >> > > >> > org.jetbrains.idea.maven.utils.MavenUtil.lambda$runInBackground$5(MavenUtil.java:468) > >> > at > >> > > >> > com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:294) > >> > at > >> > > >> > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > >> > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > >> > at > >> > > >> > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > >> > at > >> > > >> > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > >> > at java.base/java.lang.Thread.run(Thread.java:834) > >> > >> > -- Alexander Bubenchikov Software developer JetBrains http://www.jetbrains.com The Drive to Develop

Re: Found Issues - Release Apache Maven Version 3.6.2

2019-08-29 Thread Alexander Bubenchikov
original component in core (assuming that they have the same JSR330 name or > Plexus hint) > > On Thu, 29 Aug 2019 at 11:46, Alexander Bubenchikov < > alexander.bubenchi...@jetbrains.com> wrote: > > > Hi Enrico, my name is Alex, I've joined to Jetbrains this year and