> On 26 Nov 2024, at 14:38, nor...@gies.team wrote:
>
> Hi Martin,
> Thanks a lot for your response.
>
> This is a handy feature I have already used during my investigations.
>
> It shows the recognized behavior (that the profiles of the parent pom modules
> are n
Hi Martin,
Thanks a lot for your response.
This is a handy feature I have already used during my investigations.
It shows the recognized behavior (that the profiles of the parent pom modules
are not available in the project).
My current question is, should it be like this, or should the
26. Nov. 2024 schrieb nor...@gies.team:
> Good day,
>
> I am trying to use maven profiles separated into modules ( in a
> parent pom).
>
> After successfully installing the parent pom (and the modules), I tried to
> use the profiles.
>
> Profiles located in the pare
Am 26. Nov. 2024 schrieb nor...@gies.team:
> Good day,
>
> I am trying to use maven profiles separated into modules ( in a
> parent pom).
>
> After successfully installing the parent pom (and the modules), I tried to
> use the profiles.
>
> Profiles located in t
use maven profiles separated into modules ( in a
> parent pom).
>
> After successfully installing the parent pom (and the modules), I tried to
> use the profiles.
>
> Profiles located in the parent POM still work as before, but new profiles
> located in a module do not.
>
> I t
Good day,
I am trying to use maven profiles separated into modules ( in a parent
pom).
After successfully installing the parent pom (and the modules), I tried to use
the profiles.
Profiles located in the parent POM still work as before, but new profiles
located in a module do not.
I tried
THANK YOU Tama, you rock !
I've downloaded latest SNAPSHOT from here (
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/apache-maven/3.9.10-SNAPSHOT/
) and on a very simple example this works as expected.
My test is really simple so I do not pretend to validate the who
Maven4 fixes this issue, yes, it is "aware" differently than Maven3 is
(where excluded projects are fully removed from line of sight).
In Maven3 is not doable sadly, at least not with some simple change. I
did some experiments about this long time ago, see
https://github.com/apache/maven/pull/1406
Eh, sorry, am a bit overwhelmed
It seems this is FIXED in Maven-3.9.x branch? :)
https://github.com/apache/maven/commit/45201347c417896b57159221130333f5fa4bbfb6
So once 3.9.10 is out, it should be workable? Can you test the
maven-3.9.x branch?
Thanks
T
On Thu, Nov 14, 2024 at 3:14 PM Tamás
Thanks for the info Tamás.
Do you know if:
1- a workaround is planned ?
2- Maven 4 will solve this problem ?
3- commands like "-pl :myModule -am " also suffer from this kind of problem
?
I'm trying to convince everyone at work to move to a large Monorepo and my
argument is "learn how to use Maven
Howdy,
This is a problem with Maven 3 and how it "reduces" the reactor (when
using -rf, -pl etc, basically when reactor < full project).
This was already discussed once on this ML but let me shortly explain
what happens:
You basically "moved" B out of the reactor, and your "snake" looks like this
Hello,
I just faced a problem and would like your input if it is really a problem
or not.
I have a multimodule project where dependencies are like:
A --> B --> C --> D(A depends upon B which depends upon C and so on...)
I would have expected those 2 commands to exhibit the exact same behavio
I am developing an application using Java modules. when i try to run it
using exec:java it seems the exec-plugin adds all dependencies to the
classpath. i verified this using the -X option. the behavior expected is
the modularized dependencies should be added to the module path. i am using
plugin
Hi,
Your pom module inherit from your own pom parent which will inherit from
sprint boot-starter.
Regardes,
Arnaud
Le ven. 30 sept. 2022, 16:52, Thai Le a écrit :
> Thank you, this makes sense to me now that I added the profiles to all the
> pom of the modules. Most of our modul
Thank you, this makes sense to me now that I added the profiles to all the
pom of the modules. Most of our modules are inherited from
spring-boot-starter so it is not possible to add the profiles there.
Thai Le
On Fri, 30 Sept 2022 at 02:26, Arnaud bourree
wrote:
> Hi,
>
> Your pom
Here is my aggregator pom (taking out other 67 modules)
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.
pom.
> Delany
>
> On Wed, 28 Sep 2022, 23:15 Thai Le, wrote:
>
> > Thanks for your input. That's the first thing I tried. Unfortunately, if
> I
> > do that none of the modules recognized the profiles.
> >
> > On Wed, Sep 28, 2022, 17:08 Delany wrote:
>
Shouldn't matter. Please give full pom.
Delany
On Wed, 28 Sep 2022, 23:15 Thai Le, wrote:
> Thanks for your input. That's the first thing I tried. Unfortunately, if I
> do that none of the modules recognized the profiles.
>
> On Wed, Sep 28, 2022, 17:08 Delany wr
Thanks for your input. That's the first thing I tried. Unfortunately, if I
do that none of the modules recognized the profiles.
On Wed, Sep 28, 2022, 17:08 Delany wrote:
> Why did you duplicate modules in the profiles? Just leave them under
> project.
> Delany
>
>
> On
Why did you duplicate modules in the profiles? Just leave them under
project.
Delany
On Wed, 28 Sep 2022, 21:32 Thai Le, wrote:
> Hello,
>
> I have an aggregator pom with 70 modules to be built.
>
> 4.0.0
> company
> packaging-pom
> 1
> pom
>70 modu
Hello,
I have an aggregator pom with 70 modules to be built.
4.0.0
company
packaging-pom
1
pom
70 modules listed here
Recently we are introducing pact testing into our build pipeline so I made
2 profiles. One is for running pact consumer test which excludes all the
unit tests
> | +- org.codehaus.groovy:groovy-servlet:jar:3.0.9:runtime
> > | +- org.codehaus.groovy:groovy-sql:jar:3.0.9:runtime
> > | +- org.codehaus.groovy:groovy-swing:jar:3.0.9:runtime
> > | +- org.codehaus.groovy:groovy-templates:jar:3.0.9:runtime
> > | \- org.codehaus.groo
Hallo Ryan.
I would have expected the shaded package names here. Or did you forget
to shade the sources, too? Do you want the ASM stuff included in the
Javadocs anyway?
I think for a question like this there are too many variables to do
anything but speculate. Therefore, a minimal reproducer proj
Hey folks,
I've been banging my head against an issue with generating javadocs for a
module I'm working on.
The module shades and relocates ASM into the final result - this is fine.
However, when attempting to generate the javadocs for this, it fails with:
(package org.objectweb.asm is declared
werp: Shading, relocation and modules?
Hi,
I have a project ( https://yauaa.basjes.nl/ ) which is a library that is
used by others as a dependency.
My project uses (among other things) Antlr4 as a building block.
Antlr4 is a code generator that is (rightfully) very strict about the
Antlr4-run
do not want to impose "my" Antlr4 version onto the users of my
> > library
> > > so
> > > > I have shaded and relocated the correct Antlr4 version into my final
> > jar.
> > > > Now anyone can use it next to a different Antrl4 version in t
have shaded and relocated the correct Antlr4 version into my final
> jar.
> > > Now anyone can use it next to a different Antrl4 version in the same
> > > application without any conflicts.
> > >
> > > Entering JPMS...
> > >
> > > I'm trying to
; >
> > Entering JPMS...
> >
> > I'm trying to make my library as "JPMS" as possible.
> >
> > From what I understand at this time: when I shade some dependencies into
> my
> > final jar the modules-info is removed by the maven-shade-plugin as t
ing to make my library as "JPMS" as possible.
>
> From what I understand at this time: when I shade some dependencies into my
> final jar the modules-info is removed by the maven-shade-plugin as this
> would break everything.
>
> In general I agree with this; yet in my c
ering JPMS...
I'm trying to make my library as "JPMS" as possible.
>From what I understand at this time: when I shade some dependencies into my
final jar the modules-info is removed by the maven-shade-plugin as this
would break everything.
In general I agree with this; yet
Try https://github.com/aleksandr-m/gitflow-maven-plugin
So for me dropping the -SNAPSHOT would mean I'm creating a gitflow release
branch for testing, which would be as simply using that plugin as `mvn
gitflow:release-start`.
Not tried it with different modules having different version so it
, Mar 4, 2022, 7:53 AM Mike Deitrick
> wrote:
>
> > Hello,
> >
> > A couple days ago I submitted a question on Stack Overflow about this
> > topic. It can be found here
> > <
> https://stackoverflow.com/questions/71329400/remove-snapshot-from-all-maven-sub-m
Hi Mike,
The convention to keep modules versions the same can be enforced
https://maven.apache.org/enforcer/enforcer-rules/reactorModuleConvergence.html
When they're the same you can drop the version tag and let children inherit
that from the parent.
But you'll still need to edit
Any guidance on this matter?
On Fri, Mar 4, 2022, 7:53 AM Mike Deitrick wrote:
> Hello,
>
> A couple days ago I submitted a question on Stack Overflow about this
> topic. It can be found here
> <https://stackoverflow.com/questions/71329400/remove-snapshot-from-all-maven-sub
Hello,
A couple days ago I submitted a question on Stack Overflow about this
topic. It can be found here
<https://stackoverflow.com/questions/71329400/remove-snapshot-from-all-maven-sub-modules-but-honor-version>.
For the purposes of preserving this conversation, I will also provide my
qu
at 09:32, Alexander Kriegisch <
> >> alexan...@kriegisch.name>
> >> wrote:
> >>
> >>> Delany,
> >>>
> >>> you are completely misunderstanding my use case. I am building with
> >>> every push, that is the pain, because I
s with '-fn' but get a wrong build result
(passed)
-- or fewer test results with '-fae' and a correct build result
(failed).
I do *not* wish to run tests in a later phase. I have no idea where you
got that idea from. I simply want the build to continue for modules
; > (passed)
> >
> > -- or fewer test results with '-fae' and a correct build result
> > (failed).
> >
> > I do *not* wish to run tests in a later phase. I have no idea where you
> > got that idea from. I simply want the build to continue fo
ect build result
> (failed).
>
> I do *not* wish to run tests in a later phase. I have no idea where you
> got that idea from. I simply want the build to continue for modules
> dependent on ones with failing tests, so I can find out if they build
> successfully and whether
correct build result
(failed).
I do *not* wish to run tests in a later phase. I have no idea where you
got that idea from. I simply want the build to continue for modules
dependent on ones with failing tests, so I can find out if they build
successfully and whether or not they also have failing te
Oh its not, im just being thorough.
It just seems like your build iteration isn't frequent enough. If you're
not building on every MR/PR or with every push, maybe you need a separate
test build. Or maybe your reactor is too large and you need to split it
into separate projects. You could also leave
Thanks for digging, Delany. However, I am failing to see how this is
meant to solve my problem. Could you elaborate, please?
--
Alexander Kriegisch
https://scrum-master.de
Delany schrieb am 25.02.2022 18:05 (GMT +07:00):
> Alexander, here it is: https://github.com/raydac/mvn-finisher
> Delany
>
Alexander, here it is: https://github.com/raydac/mvn-finisher
Delany
On Mon, 7 Feb 2022 at 08:17, Delany wrote:
> Someone already wrote an "at end maven plugin". I used it for a while but
> removed it. Can't for the life of me find it in
> github/google/confluence/git log. Sorry!
> Delany
>
>
>
fail at the end in order to ensure that all tests in
modules which compile successfully are executed.
So, lacking basic understtanding of what you described, I also do not
feel comfortable simply quoting you and asking on another mailing list,
because I do not intend to develop a Surefire or general
>> > and execute the Project's Mojo as if the Mojo was executed in a
>> traditional
>> > way.
>> >
>> > T
>> >
>> > On Sat, Feb 5, 2022 at 5:27 AM Alexander Kriegisch <
>> alexan...@kriegisch.name>
>> > wrote:
>> &
> >
> >> I know that this probably is a classic question, because there suggested
> >> answers on Stack Overflow (and maybe also somewhere here in this mailing
> >> list), but I did not found anything satisfying the following criteria:
> >>
> >> 1. R
gt; I know that this probably is a classic question, because there suggested
> >> answers on Stack Overflow (and maybe also somewhere here in this mailing
> >> list), but I did not found anything satisfying the following criteria:
> >>
> >> 1. Run all Surefire test
wrote:
>
>> I know that this probably is a classic question, because there suggested
>> answers on Stack Overflow (and maybe also somewhere here in this mailing
>> list), but I did not found anything satisfying the following criteria:
>>
>> 1. Run all Surefire tes
question, because there suggested
> answers on Stack Overflow (and maybe also somewhere here in this mailing
> list), but I did not found anything satisfying the following criteria:
>
> 1. Run all Surefire tests, if compilation succeeds, also those of
> dependent modules, even
his mailing
> list), but I did not found anything satisfying the following criteria:
>
> 1. Run all Surefire tests, if compilation succeeds, also those of
> dependent modules, even if there are tests with failurer or errors.
> (We leave Failsafe out of the picture for now fo
Someone already wrote an "at end maven plugin". I used it for a while but
removed it. Can't for the life of me find it in
github/google/confluence/git log. Sorry!
Delany
On Mon, 7 Feb 2022 at 04:38, Alexander Kriegisch
wrote:
> >> In case you are ready to make you own plugin, it is relatively e
>> In case you are ready to make you own plugin, it is relatively easy.
I am not, Lasse. I also want this to work on the command line and not
depend on CI-system-specific workarounds. But thank you for your
insightful ideas, I really appreciate them.
Tibor, actually I wanted to avoid a potentiall
eating a report for all failing tests without cheating the
> > > build result to be successful would simply be useful.
> > >
> > > --
> > > Alexander Kriegisch
> > > https://scrum-master.de
> > >
> > >
> > > Tibor Digana schr
;
> > Tibor Digana schrieb am 06.02.2022 01:45 (GMT +07:00):
> >
> > > It is basically the same feature known in the maven-deploy-plugin
> > >
> >
> https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#deployAtEnd
> > >
> > >
r Kriegisch
> https://scrum-master.de
>
>
> Tibor Digana schrieb am 06.02.2022 01:45 (GMT +07:00):
>
> > It is basically the same feature known in the maven-deploy-plugin
> >
> https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#deployAtEnd
> >
to be successful would simply be useful.
> >>
> >> --
> >> Alexander Kriegisch
> >> https://scrum-master.de
> >>
> >>
> >> Tibor Digana schrieb am 06.02.2022 01:45 (GMT +07:00):
> >>
> >> > It is basically the same fe
It is basically the same feature known in the maven-deploy-plugin
>> >
>> https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#deployAtEnd
>> >
>> > Not sure if the command
>> > mvn deploy -DdeployAtEnd
>> > would fail to deploy dependent
>
> Tibor Digana schrieb am 06.02.2022 01:45 (GMT +07:00):
>
> > It is basically the same feature known in the maven-deploy-plugin
> >
> https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#deployAtEnd
> >
> > Not sure if the command
> > mvn de
tml#deployAtEnd
>
> Not sure if the command
> mvn deploy -DdeployAtEnd
> would fail to deploy dependent modules if the first module fails.
>
> We discussed this feature some time and we said that these features
> xxxAtEnd are a hack.
> The question is regarding Maven 4
It is basically the same feature known in the maven-deploy-plugin
https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#deployAtEnd
Not sure if the command
mvn deploy -DdeployAtEnd
would fail to deploy dependent modules if the first module fails.
We discussed this feature some
dependent modules, even if there are tests with failurer or errors.
(We leave Failsafe out of the picture for now for simplicity's
sake, but basically the same would apply to Failsafe tests for
modules which can be compiled and packaged, despite failing
Surefire tests.)
2. Fai
Hi, you need to import all modules via "Import... > Maven > Existing Maven
Projects". This is available either from File menu or from context menu
(right mouse click) on existing project or repository inside Git
Repositories view.
M2e will also automatically link imported projec
Gary
>
> On Mon, Dec 27, 2021 at 10:30 AM Ed Dowgiallo
> wrote:
>
> > Slawomir,
> >
> > Yes, all works fine at command line. All 31 modules work for mvn clean,
> and
> > I currently get a package not found in module 25 which is my bug.
> >
> &g
line. All 31 modules work for mvn clean, and
> I currently get a package not found in module 25 which is my bug.
>
> It is not publicly accessible.
>
> Is this supposed to work strictly off the pom.xmls? Or are there eclipse
> configuration files involved?
>
> Ed
>
> On
Slawomir,
Yes, all works fine at command line. All 31 modules work for mvn clean, and
I currently get a package not found in module 25 which is my bug.
It is not publicly accessible.
Is this supposed to work strictly off the pom.xmls? Or are there eclipse
configuration files involved?
Ed
On
Hi,
Does your fresh project after git checkout build correctly with all modules
by standard Maven command, like
mvn clean verify
from command line?
Is your project accessible publicly?
pon., 27 gru 2021 o 15:56 Ed Dowgiallo napisał(a):
> Hi,
>
> First time poster.
>
> I
Hi,
First time poster.
I like the Maven approach to modules and am using it for my projects with
the Eclipse IDE. Not quite getting something right though. After I have
committed a project to git and do a fresh checkout of it on a different
computer, it appears to forget all the module structure
"" && ! -e "$path/$1" ]]; do
> path=${path%/*}
> done
> echo "$path/$1"
> }
> find-up "$@"
>
> So: this lets me run Maven from a subdirectory. Nice and convenient.
>
> I found that when I run Maven in this manner from s
g my module-info.java file, then test-compile fails, with
several hundred error messages complaining that none of the modules in
module-info are in the module graph. Regular compilation of main sources
during this run works fine.
If I run it from, say, just src/main, everything works fine. If I run it
f
Yes, 'mvn compile javadoc:javadoc' helped. Thank you very much.
--
Best regards, Alex Orlov
>Воскресенье, 6 июня 2021, 1:20 +03:00 от Robert Scholte :
>
>In case of modules, javadoc requires a compiles module descriptor, so try 'mvn
>compile javadoc:javadoc
In case of modules, javadoc requires a compiles module descriptor, so try 'mvn
compile javadoc:javadoc'
Robert
On 4-6-2021 05:42:11, Alex Orlov wrote:
Hi all,
I have a sample project with two jpms modules. It is a maven project with one
parent and two child modules.
A
Hi all,
I have a sample project with two jpms modules. It is a maven project with one
parent and two child modules.
A parent pom:
...
foo.api
foo.impl
...
API module pom:
...
com.foo
foo.api
...
API module-info:
module com.foo.api {
requires org.slf4j;
exports com.foo.api
How should I configure maven parent pom to checkout code before Module list
fails because the pom cannot be found.
It seems the maven's reactor test for a module's pom occurs before the
generate-sources phase when scm checkouts the projects with the projects'
pom.
How can I fix this ?
thanks
I don't need to build the reactor project, i just need the
maven-dependency-plugin, with the task dependency:copy-dependencies to
download in a specific folder, its dependencies, but only the external ones,
excluding other projects that may be in the reactor.
E.g.
A depends on EXT.1 EXT.2 and B
'Ello.
On 2018-12-06T03:29:43 -0700
matteosilv wrote:
> This is the exact same behavior i need to acomplish, but i can't do it after
> package phase, because i need the dependencies (excluding the ones that are
> projects in my multi-module build) in a specific folder in order to run a
> develop
This is the exact same behavior i need to acomplish, but i can't do it after
package phase, because i need the dependencies (excluding the ones that are
projects in my multi-module build) in a specific folder in order to run a
development server.
It's pretty weird imho, that, when excluding a grou
for that, you can copy content to the generatedSiteDirectory [1]:
either $generatedSiteDirectory/resources if you already have html content, or
$generatedSiteDirectory/markdown if the generated content is in Markdown, and
so on
another option that I sometimes use is to include generated content
You can use the skip parameter in the individual modules..
https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#skip
That said ... I think since you want some resources from the you are better off
NOT skipping but instead just making it work for the multi module setup.
You just
configure m-site-p:site:skip via property, then in parent set to
false, and children set to true
https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#skip
or create a separate module called docs or site or something, and only
produce the site in that module
On Thu, Nov 8, 2018 at 2:1
And at the same time, I would like to copy to the site directory some files
that were generated during the build (and are now in one of the module jars).
> On Nov 8, 2018, at 1:31 PM, Russell Gold wrote:
>
> I want to generate a site for my multi-module project only from the
> top-level. How
I want to generate a site for my multi-module project only from the top-level.
How do I tell maven to skip running the site plugin on each module?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional command
I've put together a small plugin to address this issue:
https://github.com/io7m/halite
--
Mark Raynsford | http://www.io7m.com
pgpX3tqYJgKgO.pgp
Description: OpenPGP digital signature
OK, so I've apparently run into a dead end with this (which I find
pretty mind-blowing - this should be utterly trivial to accomplish).
The maven-dependency-plugin approach would work, except that it'll fail
due to trying to resolve reactor modules from the repository - even if
those m
On 2018-10-21T22:27:28 +0200
mark wrote:
>
> I'd look into a packaging plugin like m-assembly-p with a "dir" format
> and not a dependency gathering plugin because project artifacts are not
> dependencies
>
> https://maven.apache.org/plugins/maven-assembly-plugin/
'Ello.
Thanks for the sugge
On 10/21/18 8:02 PM, Mark Raynsford wrote:
Hello.
I'd like to, for an arbitrary project (in other words, a project for
which I cannot edit the pom.xml files), copy the project's artifacts
and the project's dependency artifacts into a directory.
The maven-dependency-plugin copy-dependencies goal
Hello.
I'd like to, for an arbitrary project (in other words, a project for
which I cannot edit the pom.xml files), copy the project's artifacts
and the project's dependency artifacts into a directory.
The maven-dependency-plugin copy-dependencies goal *nearly* does this,
but it'll fail as soon a
Hi,
> I want to test my JPMS module using maven surefire plugin (2.22)
> with junit5. For this I added the following to my pom:
>
> ...
>
>org.junit.jupiter
>junit-jupiter-engine
>5.3.0
>test
>
> ...
>
Hi all,
I want to test my JPMS module using maven surefire plugin (2.22) with junit5.
For this I added the following to my pom:
...
org.junit.jupiter
junit-jupiter-engine
5.3.0
test
...
Hi Pete,
On 03/07/18 22:43, Peter Nabbefeld wrote:
Hello,
I'm experimenting with a doxia module, using
org.apache.maven.doxia/doxia-modules/1.8 as parent. When looking at the
effective graph, I see every dependency with version 1.0-SNAPSHOT,
though release version is 1.8
Hello,
I'm experimenting with a doxia module, using
org.apache.maven.doxia/doxia-modules/1.8 as parent. When looking at the
effective graph, I see every dependency with version 1.0-SNAPSHOT,
though release version is 1.8, e.g.:
org.apache.maven.doxia
doxia
On Mon, 02 Jul 2018 12:30:05 +0200, Andreas Sewe
wrote:
Robert Scholte wrote:
If you still think there's a reliable solution to let Maven use Java
Modules, I'd like to see your solution, there are probably more people
interested.
Let me just jump into the discussion at this p
Robert Scholte wrote:
> If you still think there's a reliable solution to let Maven use Java
> Modules, I'd like to see your solution, there are probably more people
> interested.
Let me just jump into the discussion at this point:
For all the reasons Robert mention, Maven p
rvices will fix, but it won't solve the
critical issue of split packages.
Saying it very simple: Services (already available in Java 6) is like
JSR330 (@Inject + @Named) but without CDI container. Maven uses a CDI
container, so services won't help here.
If you still think there
s deal with this. Or don't
they?
It is hard to believe that there would be no way forward for Maven in some
fashion.
>
>
> On Thu, 28 Jun 2018 12:59:13 +0200, Václav Haisman
> wrote:
>
> Hi.
>>
>> Is there any effort to make Maven Java 9 friendly and provide
y and provide modules? I
have hit some issues when I was trying to compile a 3rd party Maven
plugin
(nashorn-maven-plugin) as Java 9. When I tried to provide it with
module-info.java I got stuck on errors like this:
[ERROR] error: the unnamed module reads package org.apache.maven.plugin
from
On Thu, Jun 28, 2018 at 5:59 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> On 28/06/18 12:59, Václav Haisman wrote:
> > Hi.
> >
> > Is there any effort to make Maven Java 9 friendly and provide modules? I
> > have hit some issues when I was trying to compile a 3rd
Hi,
On 28/06/18 12:59, Václav Haisman wrote:
Hi.
Is there any effort to make Maven Java 9 friendly and provide modules? I
have hit some issues when I was trying to compile a 3rd party Maven plugin
(nashorn-maven-plugin) as Java 9. When I tried to provide it with
module-info.java I got stuck on
Hi.
Is there any effort to make Maven Java 9 friendly and provide modules? I
have hit some issues when I was trying to compile a 3rd party Maven plugin
(nashorn-maven-plugin) as Java 9. When I tried to provide it with
module-info.java I got stuck on errors like this:
[ERROR] error: the unnamed
, January 14, 2018 3:32 AM
To: Maven Users List
Subject: Re: Running tomcat maven plugin in a multi modules project
Oh great, thanks for the heads up! (I had asked for this years ago and then
they moved to Eclipse and I lost track)
Le sam. 13 janv. 2018 23:24, Olivier Lamy a écrit :
> Hi,
> Well
in-2.2/run-mojo-features.html
> > > NOTE If you have a multi module Maven project and use Maven3,
> > > you don't need to install all modules before using the run goal, just
> > > use tomcat6/7:run from the root module and the plugin will auto
> > > detect the
1 - 100 of 1731 matches
Mail list logo
