Hi,
We got hold of a project in our company that uses Maven. I have been going
through the code and Maven. The problem is that the previous team that had
the code was new to Maven and all the plugin usage and fixes that are in
place were the workarounds that came to their mind first. I have noticed a
lot many places where better code and newer plugins can be used as well as
the build as of now seems too complicated but working. They also seem to
have developed their own maven plugins for activities such as ssh transfer
of the build to a server location and such stuff.
The biggest problem is there is no documentation, neither with the code
nor in the code. :-(
The current layout of the code is something like...
Project1
|
===> pom.xml
===> module 1
===> module n
Project2
|
===> pom.xml
===> module 1
===> module n
Project3
|
===> pom.xml
===> module 1
===> module n
The current procedure is to include all the three in a single workspace in
eclipse and work with it. I have the maven plugin for eclipse installed
but no idea how am i going to use it in this scenario.
I'm thinking of proposing a complete makeover of the code but due to time
issues this is a low priority thing. Also I was thinking if all the three
can be clubbed under a single project with a pom.xml...
I don't have any idea about the last statement that I have written.
Could anyone please give some directions as to what ways can I go about to
organize the code.
Santosh Patel
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
