Hello all!

I've been using Maven since a long time. But still I haven't found an answer
of how to control the workflow on a global level while still having the
opportunity to override confiuration on a system basis. What I want to do is
to configure plugins in a company global pom-file just to make it easier for
other projects to use our build concept - but still I don't want it to be a
requirement to use the global pom as a parent.

In a huge system with about 50 subprojects we may have som simple
jar-projects, some ejb-projects, some war-projects etc., etc. It would be
great to be able to configure the build process for all these projects types
in one or several company global files. But the implementataions of these
files still want to use some project specific configurations.

Doing this we might end up with

------------------------------------------------------------------------------------

GLOBAL

GLOBAL_JAR (enherits global) GLOBAL_EJB (inherits global)

MY_SYSTEM_GLOBAL (inherits ?)

MY_SYSTEM_JAR_IMPL (inherits GLOBAL_JAR), MY_SYSTEM_EJB_IMPL (inherits
GLOBAL_EJB)

--------------------------------------------------------------------------------------

Doing this way makes i possible to control the build process/build flow. On
the other hand it is impossible to add global overriding configuration from
my system, except for properties in a settings.xml. So this is not an
optimal solution.

Doing the other way having one global pom where I can put global
configuration s.a. reporting, properties etc. This concpet won't make it
possible to control the build flow, but it give a relative huge amount of
freedom for each project.

------------------------------------------------------------------------------------

GLOBAL

MY_SYSTEM_GLOBAL (inherits global)

MY_SYSTEM_JAR_IMPL (inherits MY_SYSTEM_GLOBAL), MY_SYSTEM_EJB_IMPL (inherits
MY_SYSTEM_GLOBAL)

--------------------------------------------------------------------------------------


So, do you have any ideas about any good solution where I can control the
build process on a company basis, override it on a system basis and finally
make it possible to reconfigure everyting in each single project but still
take part of system specific properties/configurations.


Best regards
Oskar

-- 
View this message in context: 
http://www.nabble.com/Controling-workflow-an-a-global-level-tp24050579p24050579.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to