The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 3.14.0
The Compiler Plugin is used to compile the sources of your project.
https://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your project's p
The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 4.0.0-beta-2
The Compiler Plugin is used to compile the sources of your project.
NOTE: This plugin is a Maven 4 plugin and requires Maven 4.x to run.
https://maven.apache.org/plugins/maven
Hello Chen
Le 2024-11-19 à 06 h 52, Chen Zhang a écrit :
I’m curious about the decision-making process for removing parameters
in each release of the Maven Compiler Plugin. Do you have a specific
strategy for evaluating which parameters should be deprecated or
removed? For instance, if you
Nov 18, 2024 at 4:21 PM Chen Zhang
wrote:
> Hi ,
>
> I’m a researcher specializing in software engineering, and I'm currently
> exploring configuration issues related to Maven, with a particular focus on
> the `maven-compiler-plugin`. I have some questions and observations I'd
[Re-sending to the list.]
On Tue, Nov 12, 2024, 10:37 Grégory Jevardat De Fombelle wrote:
Ok I found the exact explanation:
This specific library has a MANIFEST file containing a classpath as follow:
Class-Path: .:lib
Obviously it breaks the rule of class separator.
Shouldn't the manifest
To: Maven Users List
Subject: [EXTERNAL] Re: RE: RE: RE: Re: maven compiler plugin question
It's a dirty workaround but you could run ant task to replace the manifest in
that jar, asuming you don't care about signatures.
jar uvf foo.jar META-INF/MANIFEST.MF
Where the new manifest is th
parator.
>
> So I'am not sure how to deal with this situation with maven and or javac.
>
>
> -Original Message-
> From: Alexander Kriegisch
> Sent: Tuesday, November 12, 2024 9:31 AM
> To: Maven Users List
> Subject: [EXTERNAL] RE: RE: RE: Re: maven co
Le 2024-11-12 à 08 h 29, Grégory Jevardat De Fombelle a écrit :
Actually I wanted to use arg files to solve the too long class path on
Windows... I though fork would be enough but there is something else
that I don't understand.
Just for information, the proposed 4.0.0-beta-2 version of the c
From: Alexander Kriegisch
Sent: Tuesday, November 12, 2024 9:31 AM
To: Maven Users List
Subject: [EXTERNAL] RE: RE: RE: Re: maven compiler plugin question
On Windows, the path separator is not a colon but a semicolon.
Am 12. November 2024 15:25:58 GMT+07:00 schrieb "Grégory Jevardat De Fombel
lved and there is no issue on the
>compiler side
>Cheers
>
>-Original Message-
>From: Grégory Jevardat De Fombelle
>Sent: Tuesday, November 12, 2024 8:38 AM
>To: Maven Users List
>Subject: [EXTERNAL] RE: RE: Re: maven compiler plugin question
>
>I spotted the
some conflicting jar
libs ?
...
Good news is that the problem is being solved and there is no issue on the
compiler side
Cheers
-Original Message-
From: Grégory Jevardat De Fombelle
Sent: Tuesday, November 12, 2024 8:38 AM
To: Maven Users List
Subject: [EXTERNAL] RE: RE: Re: maven
ardat De Fombelle
Sent: Tuesday, November 12, 2024 8:29 AM
To: Maven Users List
Subject: [EXTERNAL] RE: Re: maven compiler plugin question
Indeed, you are right.
Actually I wanted to use arg files to solve the too long class path on
Windows... I though fork would be enough but there is some
To: users@maven.apache.org
Subject: [EXTERNAL] Re: maven compiler plugin question
Hello
Le 2024-11-11 à 13 h 16, Grégory Jevardat De Fombelle a écrit :
> I have difficulties finding documentation on the support of Java arguments
> files on the maven compiler plugin.
> I'd like to put my
Hello
Le 2024-11-11 à 13 h 16, Grégory Jevardat De Fombelle a écrit :
I have difficulties finding documentation on the support of Java arguments
files on the maven compiler plugin.
I'd like to put my long classpath in a file and use it as in javac
documentation for : javac @clas
Hello
I have difficulties finding documentation on the support of Java arguments
files on the maven compiler plugin.
I'd like to put my long classpath in a file and use it as in javac
documentation for : javac @classpath
In maven I started to generate this file and try to add it i
OK. Adding an explicit on plexus-java 1.3.0 fixed the issue
(maven-compiler-plugin 3.13.0 uses 1.2.0), probably because plexus-java
1.3.0 uses a later version of ASM as you say.
On Thu, Oct 24, 2024 at 6:13 PM Olivier Lamy wrote:
> Well, TBH, the ASM upgrade is the usual/famous pain with
wrote:
>
> I'm using maven-compiler-plugin 3.13.0, which is the latest non-beta
> release as of this writing.
>
> I'm using toolchains. I have a JDK 23 set up.
>
> I have a module-info.java.
>
> The compile goal works fine (my code is compiled successfully us
I'm using maven-compiler-plugin 3.13.0, which is the latest non-beta
release as of this writing.
I'm using toolchains. I have a JDK 23 set up.
I have a module-info.java.
The compile goal works fine (my code is compiled successfully using my
toolchain's JDK 23).
The testCom
t;
> hope this is the right place to report a possible bug in the Maven Compiler
> plugin. I encountered an issue with the maven compiler plugin.
>
> The problem seems to be a combination of
> * a class using unescaped double quotes in Java TextBlocks and
> * the same cl
Hello everybody,
hope this is the right place to report a possible bug in the Maven
Compiler plugin. I encountered an issue with the maven compiler plugin.
The problem seems to be a combination of
* a class using unescaped double quotes in Java TextBlocks and
* the same class being registered
The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 3.13.0
The Compiler Plugin is used to compile the sources of your project.
https://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your project's p
The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 3.12.1
The Compiler Plugin is used to compile the sources of your project.
https://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your project's p
compiler plugin 3.12.0 and Kotlin project
I tried to update Maven compiler plugin version to the latest 3.12.0 version,
and got the error message like the following when compiling the
projects:
[INFO] --- compiler:3.12.0:compile (default-compile) @ mongodb-kotlin ---
[INFO] Recompiling the module
hantsy bai napisał(a):
> I tried to update Maven compiler plugin version to the latest 3.12.0
> version, and got the error message like the following when compiling the
> projects:
>
> [INFO] --- compiler:3.12.0:compile (default-compile) @ mongodb-kotlin ---
> [INFO] Recompiling
I tried to update Maven compiler plugin version to the latest 3.12.0
version, and got the error message like the following when compiling the
projects:
[INFO] --- compiler:3.12.0:compile (default-compile) @ mongodb-kotlin ---
[INFO] Recompiling the module because of changed dependency.
[INFO
The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 3.12.0
The Compiler Plugin is used to compile the sources of your project.
https://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your project's p
Hello Siddharth
Le 2023-10-13 à 00 h 02, Siddharth Jain a écrit :
IIUC, this is a separate issue. At minimum we need to make the
behavior of compile vs. testCompile consistent. Currently it is not.
Understood, but what I think is the common point is that Maven currently
uses heuristic rules
Hi Martin,
Thanks for your response. please see inline:
> Which approach did you choose for the tests? One approach is to
> duplicate the module-info.java file in the test directory [1], but this
> is not the only way.
>
Yes, that is the approach I took. Basically, the test code is put in its
o
Hello Siddharth
I do not have a precise answer to your question, but below is a few notes.
Le 2023-10-12 à 23 h 07, Siddharth Jain a écrit :
I have observed the maven-compiler-plugin behaves differently for test
vs. main compilation.
Which approach did you choose for the tests? One approach
Hello,
I am building a project that uses modules (JPMS)
I have observed the maven-compiler-plugin behaves differently for test vs.
main compilation. I have a project and the main compilation works but the
test code does not compile. when i looked at the logs, i see during the
test-compile phase
The Apache Maven team is pleased to announce the release of the
Maven Compiler Plugin 3.11.0
https://maven.apache.org/plugins/maven-compiler-plugin/
Release Notes - Maven Compiler Plugin - Version 3.11.0
** Bug
* [MCOMPILER-347] - Includes and excludes not passed into
CompilerConfiguration
Von: KARR, DAVID
Gesendet: Friday, April 1, 2022 8:02:37 PM
An: Maven Users List
Betreff: How can I tell what value of "maxmem" the maven-compiler-plugin is
using by default?
I noticed that we have one build that is trying to compile so many files t
, DAVID
> > Sent: Friday, April 1, 2022 11:03 AM
> > To: Maven Users List
> > Subject: How can I tell what value of "maxmem" the maven-compiler-plugin
> > is using by default?
> >
> > I noticed that we have one build that is trying to compile so many f
> -Original Message-
> From: KARR, DAVID
> Sent: Friday, April 1, 2022 11:03 AM
> To: Maven Users List
> Subject: How can I tell what value of "maxmem" the maven-compiler-plugin
> is using by default?
>
> I noticed that we have one build that is trying
I noticed that we have one build that is trying to compile so many files that
it is running out of memory in the maven-compiler-plugin execution. I see that
I can set the "maxmem" property in that plugin's configuration. What would be
nice to know is what the default value is.
The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 3.10.1
The Compiler Plugin is used to compile the sources of your project.
https://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your project's p
Hi
The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 3.10.0
The Compiler Plugin is used to compile the sources of your project.
https://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your project's p
The Apache Maven team is pleased to announce the release of the Maven
Compiler Plugin version 3.9.0.
https://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-compiler-plugin
> > implementations? Have you tried cooling without preview features?
> > > > >
> > > > > On Mon, 8 Feb 2021, 15:30 Andrea Vacondio, <
> > andrea.vacon...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Thanks for the re
for the reply. I tried that and I got:
> > > > > [ERROR] Failed to execute goal
> > > > > org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile
> > > > > (default-compile) on project pdfblack-model: Execution
> default-compile of
> > > > > g
> goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile
> > > failed: A
> > > > required class was missing while executing
> > > > org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile:
> > > >
> > > org/codehaus/plex
PathsResult$ModuleNameSource
> > > [ERROR] -------------
> > > [ERROR] realm =
> > > plugin>org.apache.maven.plugins:maven-compiler-plugin:3.8.1
> > > [ERROR] strategy =
> > > org.codehaus.plexus.c
codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> > [ERROR] urls[0] =
> >
> file:/home/torakiki/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/3.8.1/maven-compiler-plugin-3.8.1.jar
> > [ERROR] urls[1] =
> >
> file:/home/torakiki/.m2/repository/org/c
iler-plugin:3.8.1
> [ERROR] strategy =
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/home/torakiki/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/3.8.1/maven-compiler-plugin-3.8.1.jar
> [ERROR] urls[1] =
> file:/home/torakiki/.m2/repository/org/codehaus/plexus/plexus-java/0.9.11/p
ven-compiler-plugin:3.8.1
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/home/torakiki/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/3.8.1/maven-compiler-plugin-3.8.1.jar
[ERROR] urls[1] =
file:/home/torakiki/.m2/repository/
Hi Andrea,
looking at the maven-compiler-plugin, it uses plexus-java 0.9.10 which
in turn uses an old 6.x asm version.
Try adding a more recent version of plexus-java (which uses asm 9.0)
and see if that works.
org.apache.maven.plugins
maven-compiler-plugin
3.8.1
15
Hi,
I hope this is the right channel.
I have a multi module project that I'm trying to modularize in the JPMS
sense.
It's configured to run maven with java 11 and run the compiler plugin using
java 15 through the toolchain plugin and this is what I get:
[INFO] --- maven-compiler-pl
Thank you for the feedback.
I should have been using –verbose not –version. When using –verbose the plugin
is working as expected.
Thank you for your time.
From: Thomas Broyer
Sent: Friday, March 13, 2020 3:02 AM
To: Maven Users List
Subject: Re: Problem with the maven-compiler-plugin
ler-plugin is not working or I am doing
> something wrong.*
>
>
>
> *I have the following in the POM file.*
>
>
>
>
>
>
>
> org.apache.maven.plugins
>
>
It appears that the maven-compiler-plugin is not working or I am doing
something wrong.
I have the following in the POM file.
org.apache.maven.plugins
maven-compiler-plugin
3.8.1
arbaise" wrote:
>
> Hi,
>
> this is documented on the documentation page[1]
>
> which can be achieved by using the following:
>
>
>[...]
>
> [...]
&g
Hello,
I'd like to pass -parameters and enable-preview arguments to the test compiler
but I can't figure out how, the closest I got is:
How can I pass two arguments to the test compiler where one of them requires
double dash?
Best Regards,
[https://cf-cdn.infobip.com/email_sign
/2019, 14:46, "Karl Heinz Marbaise" wrote:
>
> Hi,
>
> this is documented on the documentation page[1]
>
> which can be achieved by using the following:
>
>
>[...]
>
> [...]
>
>
Can't you use a profile for the test case, where you redefine the
maven-compiler-plugin settings to what you need for test ?
I thinks settings in profiles overrides previously seen definitions, but I'm
not 100% sure of that. In worst case you might need 2 different profiles.
Che
this is documented on the documentation page[1]
which can be achieved by using the following:
[...]
[...]
org.apache.maven.plugins
maven-compiler-plugin
3.8.1
Hi,
this is documented on the documentation page[1]
which can be achieved by using the following:
[...]
[...]
org.apache.maven.plugins
maven-compiler-plugin
3.8.1
--enable-preview
wished supplemental
Hello,
I'd like to pass -parameters and enable-preview arguments to the test compiler
but I can't figure out how, the closest I got is:
How can I pass two arguments to the test compiler where one of them requires
double dash?
Best Regards,
[https://cf-cdn.infobip.com/email_sig
The Apache Maven team is pleased to announce the release of the
Apache Maven Compiler Plugin Version 3.8.1
https://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your project's plugin configuration:
Important Notes since Version 3.8.0
* The default
r it, but can't find it.
> Looks like you found a bug.
>
> Robert
>
> On Tue, 12 Feb 2019 20:03:10 +0100, Russell Gold
> wrote:
>
>> But it doesn’t appear to be working for me.
>>
>>> [INFO] --- maven-compiler-plugin:3.8.0:comp
I thought I had written an IT for it, but can't find it.
Looks like you found a bug.
Robert
On Tue, 12 Feb 2019 20:03:10 +0100, Russell Gold
wrote:
But it doesn’t appear to be working for me.
[INFO] --- maven-compiler-plugin:3.8.0:compile (java9) @ pfl-basic ---
[DEBUG] Configuring
But it doesn’t appear to be working for me.
> [INFO] --- maven-compiler-plugin:3.8.0:compile (java9) @ pfl-basic ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile from plugin
> realm ClassRealm[plugin>org.apache.maven.plugins:maven-
Hi Russ,
There's no way to configure this, the plugin will do it for you[1]
thanks,
Robert
[1]
https://github.com/apache/maven-compiler-plugin/blob/master/src/main/java/org/apache/maven/plugin/compiler/CompilerMojo.java#L328-L346
On Tue, 12 Feb 2019 18:56:52 +0100, Russell Gold
Version 3.8.0 of the maven-compiler-plugin supports a multiReleaseOutput option
which can compile classes directly to the appropriate
META-INF/versions/{release} directory, which is very nice. What I don’t see,
though, is how to tell it to use the previous release as its dependency. That
is
Le 01/12/2018 à 21:17, Robert Scholte a écrit :
> This is a dangerous advice.
>
> Yes, it'll only compile the touched files, but not the source files
> using it. For example method signature changes are not detected and
> you will hit that issue at runtime with a NoSuchMethodException, which
> is
xpect):
maven-compiler-plugin
false
Martin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: us
Hello Francesco
Have you tried following configuration? It seems counter-intuitive, but
last time I tried it made compilation much faster (i.e. it seems to have
the opposite effect of what we would expect):
maven-compiler-plugin
false
asses
that call this method (and throw a compilation error if you forgot to
change this class).
Basically there are 2 options: analyze every class and decide if it must
be recompiled OR simply recompile everything. The maven-compiler-plugin
does the latter by default because the java compiler s
ingle source file changed, among 2680 others left
unchanged): 01:06 min
In case 3 I'm expecting a time closer to case 2, not to case 1. Both case 1 and
3 reports "Compiling 2680 source files".
Are there some options to make maven-compiler-plugin skip compiling sources
where the
/in/nigamnaman>
>
>
> On Mon, Jul 30, 2018 at 2:10 AM Karl Heinz Marbaise >
> wrote:
>
> > The Apache Maven team is pleased to announce the release of the
> > Apache Maven Compiler Plugin Version 3.8.0
> >
> > https://maven.apache.org/plugins/maven-comp
m is pleased to announce the release of the
> Apache Maven Compiler Plugin Version 3.8.0
>
> https://maven.apache.org/plugins/maven-compiler-plugin/
>
> You should specify the version in your project's plugin configuration:
>
> Important Notes since Version 3.8.0
>
> * The
The Apache Maven team is pleased to announce the release of the
Apache Maven Compiler Plugin Version 3.8.0
https://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your project's plugin configuration:
Important Notes since Version 3.8.0
* The default
responses.
IMHO What the maven-compiler-plugin currently offers matches the specs
quite good.
thanks,
Robert
[1]
http://mail.openjdk.java.net/pipermail/jpms-spec-experts/2017-May/000687.html
On Mon, 16 Apr 2018 11:58:03 +0200, Roman Grigoriadi
wrote:
I see your point. But wouldn't
f the main jar and let up to users to decide how to make
available jars from mylib/lib to the runtime. During compilation of the
project I still want to force maven-compiler-plugin to reference them on
module path so I can see if there are any JPMS issues.
Thank you,
Roman
On Fri, Apr 13, 2018 at
Here you hit the nail on the head! This is exactly my concern and I've
spoken about this on several conferences.
TLDR: Don't publish libraries to Maven Central that depend on at least one
filename-based automatic module. You must wait until all your dependencies
are explicit modules.
In the
I guess you are right. I wasn't sure if it is a good idea to include a name
for a module in my descriptor for a dependency which is actually not named
(automatic) and release with such descriptor. But given this dependency is
fixed version, it will not get any other name than I am referencing and i
But that means that the dependency is actually required at runtime.
Looks to me there are 2 options:
- make that dependency a requirement
- restructure your code so it can be a static requirement
One of the benefits I do like about the modularization is that it forces
you to do clean coding. I
Hi Robert,
I don't think my case is suitable for requires static / optional. Runtime
will fail with ClassNotFound exception if classes are neither on CP or MP.
Roman
On Thu, Apr 12, 2018 at 12:46 PM, Martin Desruisseaux <
martin.desruisse...@geomatys.com> wrote:
> Hello Robert
>
> Le 11/04/201
Hello Robert
Le 11/04/2018 à 18:45, Robert Scholte a écrit :
> I am not aware of such problem. Did you create a Jira[1] issue for it?
>
Done: https://issues.apache.org/jira/browse/MCOMPILER-336
Thanks
Martin
-
To
odule-info.java
mvn install -Pjdk9
But maven-compiler-plugin then fails on the next module, unless I touch
the module-info.java of that next module too, /etc./
I will see if I can do a new attempt at creating a minimal test case
later this week.
Martin
[1] https://github.com/opengeospatial/geoapi
at it.
thanks,
Robert
[1] https://issues.apache.org/jira/projects/MCOMPILER
On Wed, 11 Apr 2018 14:24:36 +0200, Martin Desruisseaux
wrote:
I also have the case where maven-compiler-plugin puts a dependency in
classpath while it should be in modulepath. Strangely, the plugin does
the
ule-path to
make them automatic "derived name" modules during project compilation.
I
can see that maven-compiler-plugin:3.7.0 tries to find
module-info.class
and Automatic-Module-Name entry in MANIFEST. If found it uses those
jars
as
modules.
Is there any way I can force placement
I also have the case where maven-compiler-plugin puts a dependency in
classpath while it should be in modulepath. Strangely, the plugin does
the correct thing when executed with "mvn _clean_ install" but not when
executing "mvn install" without clean. This issue
0200, Roman Grigoriadi <
> roman.grigori...@gmail.com> wrote:
>
> Hi,
>>
>> I would like to place some of the project dependencies to --module-path to
>> make them automatic "derived name" modules during project compilation. I
>> can see that maven-c
project compilation. I
can see that maven-compiler-plugin:3.7.0 tries to find module-info.class
and Automatic-Module-Name entry in MANIFEST. If found it uses those jars
as
modules.
Is there any way I can force placement non-modularized dependencies on
module path
Hi,
I would like to place some of the project dependencies to --module-path to
make them automatic "derived name" modules during project compilation. I
can see that maven-compiler-plugin:3.7.0 tries to find module-info.class
and Automatic-Module-Name entry in MANIFEST. If found it uses
The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 3.7.0
The Compiler Plugin is used to compile the sources of your project.
https://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your project's p
Hi
The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler plugin, version 3.6.2.
http://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-compiler-plugin
The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 3.6.1
Most important change is the support for test-compile when using JDK 9
build b148+
https://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your
I use maven-compiler-plugin to load /lib/*.jar files, like this in pom.xml:
org.apache.maven.plugins
maven-compiler-plugin
3.0
1.7
1.7
UTF-8
The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 3.6.0
The Compiler Plugin is used to compile the sources of your project.
This version introduces support of several new features of Java 9, such as:
JEP 247: Compile for Older Platform
I've been fixing and closing quite some issues for the
maven-compiler-plugin lately.
There are still 2 categories with several issues: incremental builds and
annotation processing.
It's too much to fix for 3.6.0 (Java 9 prep-release), but we should have a
good look at all these is
:-)
>
>
> -Original Message-
> From: Christopher [mailto:ctubb...@apache.org ]
> Sent: Sunday, October 23, 2016 12:02 PM
> To: Maven Users List; Robert Patrick
> Subject: Re: Maven Compiler Plugin 3.5.1 bug
>
> I agree. You can also manually add the directory as a sour
bert Patrick
> Gesendet: Sonntag, 23. Oktober 2016 18:45
> An: Maven Users List
> Betreff: RE: Maven Compiler Plugin 3.5.1 bug
>
> That's why we use IntelliJ :-)
>
> It understands Maven projects and uses Maven to build them. In the
> IDE, you simply cancel the exclusio
ag, 23. Oktober 2016 18:45
> An: Maven Users List
> Betreff: RE: Maven Compiler Plugin 3.5.1 bug
>
> That's why we use IntelliJ :-)
>
> It understands Maven projects and uses Maven to build them. In the IDE,
> you simply cancel the exclusion on the target directory and mark the
&
An: Maven Users List
Betreff: RE: Maven Compiler Plugin 3.5.1 bug
That's why we use IntelliJ :-)
It understands Maven projects and uses Maven to build them. In the IDE, you
simply cancel the exclusion on the target directory and mark the appropriate
subdirectory(ies) as a generated sour
ssage-
From: Christopher [mailto:ctubb...@apache.org]
Sent: Sunday, October 23, 2016 11:42 AM
To: Maven Users List
Subject: Re: Maven Compiler Plugin 3.5.1 bug
The build-helper-maven-plugin method has the advantage of having a
corresponding build-helper plugin in Eclipse, to automatically ad
other plugin to fill the functionality gaps...don't you think?
>
>
> -Original Message-
> From: Curtis Rueden [mailto:ctrue...@wisc.edu]
> Sent: Saturday, October 22, 2016 5:48 PM
> To: Maven Users List
> Subject: RE: Maven Compiler Plugin 3.5.1 bug
>
> You can ad
c.edu]
Sent: Saturday, October 22, 2016 5:48 PM
To: Maven Users List
Subject: RE: Maven Compiler Plugin 3.5.1 bug
You can add source directories using the build-helper-maven-plugin.
On Oct 22, 2016 4:39 PM, "Robert Patrick" wrote:
> I am using the section of the POM, not
ld.directory}/generated-sources/
> annotations
>
>
>
> The documentation claims that the default value for the
> generatedSourcesDirectory is this directory so you are saying that somehow
> the fact that the maven-compiler-plugin no longer includes the directory in
> the build is a
maven-compiler-plugin no longer includes the directory in the
build is a feature?
I looked through the compiler plugin's documentation and couldn't figure out a
way to add a directory to the build. I know how to add the directory to the
build if I write my own plugin but that se
1 - 100 of 554 matches
Mail list logo
