[mevenide-user] POMs and profiles

I am not sufficiently conversant with all the maven/mevenide conventions
to be able to address the following with any degree of certainty, but I
*do* know that I'm having a problem with the current default way of the
world with Netbeans and mevenide.

The problem is as follows:

We have a number of modules within a given project, shared across a
number of developers. We store all code in subversion.

One of our modules is a web application.

When one of the developers sets up to run the web application, it seems
that mevenide squirts a profile into the pom.

The pom file is then marked as modified and checking in the project
pushes the pom changes out to all the other developers.

Since each developer may have different tomcat settings and may wish to
try out on different versions within the same codebase, we are
potentially forcing meaningless profiles on each other.


To my mind, the 'correct' place for the required profiles is either in
the local m2 settings.xml (developer-specific, outside of subversion) or
in profiles.xml (developer-specific, easily excluded from subversion
with an ignore tag) but *not* in pom.xml.

I note from the mevenide website that if I set the value in the
profiles.xml file then 'the UI shall respect that'. However, that then
requires *all* my developers to manually create profiles.xml files with
the settings in. Seems to me that the 'local' settings option should be
the default for Netbeans UI items, or at the very least configurable to
be so.

Have I missed a trick with why it currently goes into the pom? (and I
apologise in advance if I am talking rubbish or if this has been
discussed before)

Later,

Andy

-------------
Yada, yada, yada...

Roslin Institute is a company limited by guarantee, registered in
Scotland (registered number SC157100) and a Scottish Charity (registered
number SC023592). Our registered office is at Roslin, Midlothian, EH25
9PS. VAT registration number 847380013.

The information contained in this e-mail (including any attachments) is
confidential and is intended for the use of the addressee only.   The
opinions expressed within this e-mail (including any attachments) are
the opinions of the sender and do not necessarily constitute those of
Roslin Institute (Edinburgh) ("the Institute") unless specifically
stated by a sender who is duly authorised to do so on behalf of the
Institute.
 

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email