At 06:55 AM 12/6/2023, mark.yagnatin...@barclays.com.INVALID wrote:
>Pretty sure that plugin is flexible enough to just copy what you tell it to?
>https://maven.apache.org/plugins/maven-resources-plugin/examples/include-exclude.html
Thanks. I just hadn't encountered the right examples!
:
>On 2023/12/06 03:34:58 Dave Dyer wrote:
>>
>> I'm trying to tune up my maven build, which requires that I construct
>> a source directory on the fly by copying from the canonical location.
>>
>> The best advice I've found is to use mavin-resources-plugin, but
I'm trying to tune up my maven build, which requires that I construct
a source directory on the fly by copying from the canonical location.
The best advice I've found is to use mavin-resources-plugin, but
that's a bit inelegant because it copies everything, not just the
sources.
Is there a
I think I've peeled the next layer of the onion. The maven
build I'm using doesn't call javac as part of the build process;
Instead it uses the classes already produced by Eclipse, which
supports debugging and development. These classes are not optimized
at all, and in particular each class is
>
>Maven, by default uses maven-compiler-plugin, but that plugin itself is
>pluggable (can use javac, which is default, but also eclipse compiler, etc).
>The plugin by default uses javac.
The build I'm using seems to not be using javac - where is guidance
to configuring it?
The problem I'm investigating is that the code produced by a
maven build is different, and inferior, to the code produced
but any javac I can find. My questions are, what java compiler
is it actually using, and of course, how can I change it?
The best info I have is that it's using
>
>Inferior bytecode means what in this case?
It's a little outside my comfort zone, but it appears that some
virtual methods are inlined by most java compilers, but are real
funcion calls as produced by maven. There may be more
but that was the smoking gun. It's not a bleeding edge
javac
the compilation) you
>> must configure it via the fork option
>> (https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#fork)
>>
>>
>> On Mon, 4 Dec 2023 at 07:07, Dave Dyer wrote:
>>>
>>>
>>> >
>>> >Ma
fels wrote:
>Hallo,
>
>Dave Dyer wrote on 4. Dec 2023 08:27 (GMT +01:00):
>
>> It seems odd to me for maven to have its own javac,
>
>It does not, when you use the compiler plugin in the default config it uses
>the Java compiler from the JDK you started maven with
