Howdy,
On Fri, May 6, 2022 at 4:01 PM Thomas Broyer wrote:
> Fwiw, my "daily routine" with That Other Build Tool is to just ask it to
> build and let it handle everything for me: never need to clean (through git
> clean or the clean task), never need to nuke my local cache because it
> really
On Fri, May 6, 2022 at 12:29 PM Tamás Cservenák wrote:
> Howdy,
>
> no, not my memory, I rely on my "daily routine": I use Maven Repository
> Manager, I regularly nuke my local repo, regularly execute `git clean -fdx`
> on my checkout, and on checkout/branch change regularly do "quick-build"
>
On Fri, May 6, 2022 at 1:24 PM Tamás Cservenák wrote:
> Hm, I need to look more into MCOMPILER-496, as I found a m-compiler-p IT
> that does exactly what Thomas described:
>
> https://github.com/apache/maven-compiler-plugin/tree/master/src/it/MCOMPILER-203-processorpath
>
> 3 module multi module
reason why I mention this, is that you use
> terms from the "Maven2 era", like "reactor". Maven2 had the well known
> "maven-reactor-plugin", that ceased to exist in Maven3. IMHO, let's clear
> up the terms as otherwise we will just accumulate more misunderstandings
: I believe you are quite
> experienced, and I'd bet you did not start with Maven3, but most probably
> Maven2 or even Maven1 :) The reason why I mention this, is that you use
> terms from the "Maven2 era", like "reactor". Maven2 had the well known
> "maven-reac
Howdy,
no, not my memory, I rely on my "daily routine": I use Maven Repository
Manager, I regularly nuke my local repo, regularly execute `git clean -fdx`
on my checkout, and on checkout/branch change regularly do "quick-build"
`mvn clean install` (usually `mvn clean install -Dtest=void`) as very
eactor". Maven2 had the well known
"maven-reactor-plugin", that ceased to exist in Maven3. IMHO, let's clear
up the terms as otherwise we will just accumulate more misunderstandings.
For start, let's take Maven Extensions (core or build, does not matter).
IMHO, having
On Thu, May 5, 2022 at 10:22 PM Tamás Cservenák wrote:
> IMHO the antipattern here is the idea that "mvn install" is bad.
>
> But let's take it step by step. For simplicity sake, let's ignore remote
> deploys/downloads for now.
> Also, let's assume a developer workstation for the same reason
>
On Thu, May 5, 2022 at 10:16 PM Tamás Cservenák wrote:
> Hm,
>
> By reading this blog entry from 2012 (!), I see it summarizes nicely at the
> end:
> * You may be using some broken plugins that you will need to fix, or
> replace.
> * You may be battling a circular dependency hell (which was why
e.
> > > Maven CLI will basically complain that it cannot resolve the module
> > needed
> > > by the plugin and fail, even if I explicitly list that module in the
> > > project list.
> > >
> > > That occurs both with Maven 3 and 4.
> >
t cannot resolve the module
> > needed
> > > by the plugin and fail, even if I explicitly list that module in the
> > > project list.
> > >
> > > That occurs both with Maven 3 and 4.
> > >
> > > The obvious workaround is to install the required module first and then
> > run
> > > the plugin but I'm trying to get rid of the need for `mvn install`
> > > entirely.
> > >
> > > Is there a particular reason plugin dependencies are not considered by
> > > Maven Reactor?
> > > Is module-as-plugin-dependency a Maven antipattern?
> > >
> > > Thanks a lot for your help!
> > > Florent
> > >
> >
>
and then run
> the plugin but I'm trying to get rid of the need for `mvn install`
> entirely.
>
> Is there a particular reason plugin dependencies are not considered by
> Maven Reactor?
> Is module-as-plugin-dependency a Maven antipattern?
>
> Thanks a lot for your help!
> Florent
>
gt; >
> > The obvious workaround is to install the required module first and then
> run
> > the plugin but I'm trying to get rid of the need for `mvn install`
> > entirely.
> >
> > Is there a particular reason plugin dependencies are not considered by
> > Maven Reactor?
> > Is module-as-plugin-dependency a Maven antipattern?
> >
> > Thanks a lot for your help!
> > Florent
> >
>
t; That occurs both with Maven 3 and 4.
>
> The obvious workaround is to install the required module first and then run
> the plugin but I'm trying to get rid of the need for `mvn install`
> entirely.
>
> Is there a particular reason plugin dependencies are not considered by
> Maven Rea
here a particular reason plugin dependencies are not considered by
> Maven Reactor?
> Is module-as-plugin-dependency a Maven antipattern?
>
> Thanks a lot for your help!
> Florent
>
is to install the required module first and then run
the plugin but I'm trying to get rid of the need for `mvn install` entirely.
Is there a particular reason plugin dependencies are not considered by
Maven Reactor?
Is module-as-plugin-dependency a Maven antipattern?
Thanks a lot for your help!
Florent
to 3.0 or even 3.0-SNAPSHOT.
Regards,
Stefan
František
http://calavera.info
Původní zpráva
Od: Ron Wheeler
Odesláno: středa, 1. července 2015 17:14
Komu: users@maven.apache.org
Odpovědět: Maven Users List
Předmět: Re: How to arrange dependency management for maven reactor if child
: Maven Users List
Předmět: Re: How to arrange dependency management for maven reactor if
child
modules are versioned independently?
What is the relationship between the independent modules?
If a child module gets a new version, should that trigger a change for
other modules that depend
: How to arrange dependency management for maven reactor if child
modules are versioned independently?
What is the relationship between the independent modules?
If a child module gets a new version, should that trigger a change for
other modules that depend on it?
It seems to me from your description
.
František
http://calavera.info
Původní zpráva
Od: Ron Wheeler
Odesláno: středa, 1. července 2015 17:14
Komu: users@maven.apache.org
Odpovědět: Maven Users List
Předmět: Re: How to arrange dependency management for maven reactor if child
modules are versioned independently?
What is the relationship
as a
last hope for solution or expert insight.
http://stackoverflow.com/questions/30253133/how-to-arrange-dependency-management-for-maven-reactor-if-child-modules-are-vers
We have a reactor pom whose child modules are versioned independently, ie.
child module declares it's own version
after a long time, I'm sending it here as a
last hope for solution or expert insight.
http://stackoverflow.com/questions/30253133/how-to-arrange-dependency-management-for-maven-reactor-if-child-modules-are-vers
We have a reactor pom whose child modules are versioned independently, ie.
child module
to wide audience.
Since it's still unanswered after a long time, I'm sending it here as a
last hope for solution or expert insight.
http://stackoverflow.com/questions/30253133/how-to-arrange-dependency-management-for-maven-reactor-if-child-modules-are-vers
We have a reactor pom whose child modules
dependency management for maven reactor if child
modules are versioned independently?
What is the relationship between the independent modules?
If a child module gets a new version, should that trigger a change for
other modules that depend on it?
It seems to me from your description, that you do
issue):
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11831version=20210
Based on my mistake, the files are already on final ASF repository:
http://repository.apache.org/content/groups/public/
http://repository.apache.org/content/groups/public/org/apache/maven/plugins/maven-reactor
Hi to all,
after the vote for the retiring of the plugin has succeeded now the
final release of the plugin.
The vote is open for 72 hours.
[ ] +1 Yes, it's about time
[ ] -1 No, because...
Kind regards
Karl-Heinz Marbaise
Canceled.
Sorry...forget things to mentioned...
On 3/30/14 5:05 PM, Karl Heinz Marbaise wrote:
Hi to all,
after the vote for the retiring of the plugin has succeeded now the
final release of the plugin.
The vote is open for 72 hours.
[ ] +1 Yes, it's about time
[ ] -1 No, because...
Kind
Hi,
the vote has passed with the following results:
+1 (binding):
Hervé Boutemy,
Olivier Lamy,
Kristian Rosenvold,
Stephen Connolly,
Stephane Nicoll,
+1 (non binding):
Mirko Friedenhagen,
Jason van Zyl,
Toni Chemit,
Anders Hammar,
Dominik
Hi,
sorry i missed Robert Scholte +1 (binding)...
Kind regards
Karl-Heinz Marbaise
On 3/24/14 12:11 PM, Karl Heinz Marbaise wrote:
Hi,
the vote has passed with the following results:
+1 (binding):
Hervé Boutemy,
Olivier Lamy,
Kristian Rosenvold,
Stephen Connolly,
+1
On 22.03.2014, at 22:52, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi,
based on the decision we have made on the 18. february 2014 to define End Of
Life of Maven 2 http://maven.apache.org/maven-2.x-eol.html
I would suggest to retire the Maven Reactor Plugin.
The last release has
Hi,
based on the decision we have made on the 18. february 2014 to define
End Of Life of Maven 2 http://maven.apache.org/maven-2.x-eol.html
I would suggest to retire the Maven Reactor Plugin.
The last release has been made on 23rd of september 2008 version 1.0.
Apart from that the complete
Hi Francis,
Under maven 3.0 building a multi module project, I need to customize the
reactor building the multimodule as the last project instead of the first
project as now.
The first question which comes into my mind is: Why do you need such
customization?
The order in the reactor is
You cannot change Maven's behavior for aggregate projects. If, for
example, want to make a package at the end, add one more module that
makes the package. The order of the build in terms of executions in
the aggregate project versus the build of the modules is not
customizable.
In a pinch the
Is the maven-reactor-plugin still alive and viable? I want to make sure
that if I include it in my pom for a particular task it isn't doing anything
outmoded.
Thanks,
Laird
--
http://about.me/lairdnelson
Hello,
No real maintenance on this as some features are now included in core with 3.x
2011/10/21 Laird Nelson ljnel...@gmail.com:
Is the maven-reactor-plugin still alive and viable? I want to make sure
that if I include it in my pom for a particular task it isn't doing anything
outmoded
While trying to use reactor:resume to resume a build, I see the order of
build changing. See the output below. The order as reported initially is
not same as the order reactor plugin is following. Why?
glassf...@~/WS/gf/v3.trunk.new$ mvn reactor:resume -DprintOnly=true
Is there a way to call Maven to get the output of the Reactor only? I am
interested in knowing the order in which the various POMs will be built only
as information first
--
View this message in context:
http://www.nabble.com/Maven-Reactor-tp19858666p19858666.html
Sent from the Maven - Users
Validate is the first phase that usually has nothing bound to it. (only
the enforcer does that I know of) so you could use that.
-Original Message-
From: solo1970 [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 07, 2008 6:52 AM
To: users@maven.apache.org
Subject: Maven Reactor
has nothing bound to it. (only
the enforcer does that I know of) so you could use that.
-Original Message-
From: solo1970 [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 07, 2008 6:52 AM
To: users@maven.apache.org
Subject: Maven Reactor
Is there a way to call Maven to get
in your modules list. (That's what a Maven reactor is: a
multimodule build.)
The reactor plugin has no way to build third-party libraries like
Hibernate; it would have to pull the code down out from some remote SCM
to do that.
Would it work if I have a domain module which is used by several
a dependency, not part of a
multimodule build) to make that part of the chain (in either direction), if
of course the source code is available on the building pc.
regards,
Wim
2008/9/28 Dan Fabulich [EMAIL PROTECTED]
The Maven team is pleased to announce the release of the Maven Reactor
Plugin
. (That's what a Maven reactor is: a
multimodule build.)
The reactor plugin has no way to build third-party libraries like
Hibernate; it would have to pull the code down out from some remote SCM to
do that.
Would it work if I have a domain module which is used by several
applications (but is just
? Do you mean this page?
http://maven.apache.org/plugins/maven-reactor-plugin/
I feel like that page pretty clearly outlines what you can do with Maven
Reactor Plugin. Does that not make (enough) sense?
There's a more detailed explanation of use cases for the reactor plugin
here: http
The Maven team is pleased to announce the release of the Maven Reactor
Plugin, version 1.0.
This plugin can build a subset of interdependent projects in a reactor. It
should be useful in large reactor builds that include irrelevant stuff
you're not working on.
http://maven.apache.org
Dan,
Congrats on the plugin. Could you maybe add to the plugin home page
why this plugin is required or useful? What common problem is it
trying to solve? It would be nice to know that background, because I
am grasping to find its purpose.
Paul
I've checked in a new plugin to the sandbox called the Maven Reactor
Plugin. You can use it to build a subset of interdependent projects in a
reactor. It should be useful in large reactor builds that include
irrelevant stuff you're not working on.
It includes the following goals
on the start up, I need to copy my bundle in
the plugin resources. In the specific case, Maven reactor doesnt find the
bundle (exactly the goal of the plugin called by maven:reactor).
Well, my god feeling is that the maven:reactor loads the environment of all
plugins at the start up and doesnt
maven:reactor, a loader problem appears:
* if the bundle was already copied in the plugin resources, the bundle is
correctly found, then it works very well.
* if the bundle doesnt exist on the start up, I need to copy my bundle in
the plugin resources. In the specific case, Maven reactor doesnt
http://jira.codehaus.org/browse/MPMULTIPROJECT-39 ?
On Wed, 6 Oct 2004 11:21:57 +0200, Stéphane Nicoll
[EMAIL PROTECTED] wrote:
Hello list,
I have a structure of maven projects. In the root project, I have defined parameters
related to deployment (site and artifacts). Other projects
=**/project.xml
goals=bsb:site
banner=Deploying site for
ignoreFailures=true/
/goal
Cheers,
s/
-Original Message-
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: mercredi 6 octobre 2004 16:23
To: Maven Users List
Subject: Re: maven reactor does not inherit from
I'm a java developer at a portuguese company and where
trying/using Maven for our nightly builds/ distribution builds.
And my problem is that where using the Multiproject plugin (that
uses
the reactor tag) to compile a list of projects and distribuitions and
using our own
Maven will always try to download dependencies from the project.xml in the directory
from where
you run Maven before it attempts to execute any goals. You should only specify the
dependencies
for the subprojects that need them. The top level project.xml should only contain
dependencies
that
generation, app creation deployment) needs some
specific guidance and therefore the multiproject goal is used instead of the maven
reactor? I'm just trying to figure which is the preferred way of working: either to
use the reactor or to use the multiproject goal.
regards,
Johan
instead of the maven reactor? I'm just trying to figure which is the
preferred way of working: either to use the reactor or to use the
multiproject goal.
regards,
Johan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
than Maven here... :-)
Thanks
-Vincent
-Original Message-
From: Eric Berenguier [mailto:[EMAIL PROTECTED]
Sent: 08 October 2003 12:05
To: Maven Users List
Subject: Maven reactor and versions
Hi,
I'm using maven reactor to execute a goal on several projects in
subdirectories
I've had some good luck integrating Maven Reactor with my product. In this
process I've come up with a few questions (I couldn't find answers in the
Wiki):
I have
project.xml
maven.xml
|
--Project A (project.xml, maven.xml)
|
--Project B (project.xml, maven.xml
Hi,
I'm using maven 1.0 b10 on a win32 platform, to build the sample everest
project provided with Vincent Massol TSSS slides about Maven. The build
process uses up to 150M of RAM : is it a normal behavior ?
Sebastien BRUNOT
-
57 matches
Mail list logo
