If you can not reorganize your project, you should probably stick with Ant.
Maven is a great tool but you have to use it in the way it was designed
to be use.
It relies a lot on the fact that your projects follow a set of
conventions and if they do not, you will spend a lot of time fighting
with Maven without getting very much benefit.
Maven simplifies your life but only if you are able and willing to
change your development processes.
There is nothing wrong with Ant and if you can not adapt to Maven, stick
with Ant.
We have a project that is similar in size to yours. It is a portal so it
has about 50 WAR files that implement Web Services and Servlets.
It includes another 20 projects that produce JAR files.
We build it 100% with Maven and use no custom Maven plug-ins.
We try to be as close to out-of-the-box with Maven as possible and have
structured the project to fit Maven.
This strategy has resulted in a project that:
is very stable, releases and new functionality only affects a small
number of projects
produces a robust application
is easy to maintain,
has very small POM files
has very few dependencies (5-8) in most of the POMs while we use over 50
third party libraries - Spring, Hibernate, JasperReports, CXF, Apache
Commons, MySQL, and more.
Ron
On 22/11/2010 7:56 AM, Ron Wheeler wrote:
A single project with 1500 files should be restructured into about 50
functionally independent projects that can be built, tested and
deployed individually.
All but one will produce JAR files.
Use aggregation projects to group the small JARs into larger JARs that
can be deployed and used as dependencies to simplify other POM files.
This will also help in a number of ways:
Increased stability of your code base
Start down the road to SOA.
Improve the team's ability to divide up the work and not get under
each other's feet.
Dramatically reduce build times by reducing the time wasted rebuilding
stuff that has not changed.
Reduce SCM download traffic
etc.
Ron
On 22/11/2010 5:54 AM, Jörg Schaible wrote:
Hi,
Kamran Yadav wrote:
I am using 2.3.2 now but no improvement.
I understand I can create a separate project for the classes only
but that
is not in my control.
Anyway is there anyway to produce the compiled class outside of
target/classes folder as in say C:\etc.etc.
Well, please reconsider your usage of Maven. While I am quite sure,
that a
way can be found to do this, you contradict the usage of Maven. This
is not
Ant. An essential part of Maven are conventions. If you decide not to
follow
them, you implicitly also call Maven into question. Therefore you
will often
get the answer "follow the Maven way". If you fight it, you will not
win a
lot.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
