Re: [mevenide-user] POMs and profiles

On Thu, Feb 14, 2008 at 9:53 PM, andy law (RI) <[email protected]> wrote:
> Milos,
>
>
>  >
>  > The only reason why it's in the pom is to mimick what the
>  > default ant based web projects do. There the server type is
>  > written to the nbproject/project.properties file and the
>  > server instance id into the non-sharable
>  > nbproject/private/private.properties.I've been told by the
>  > web support guys that it's what most people want as most
>  > webapps are developed against one particular appserver anyway.
>  >
>
>  We all develop against tomcat - it's just that we have versions of 5.0,
>  5.5 and 6.0 available. We also have different copies of the tomcat
>  codebase at different paths and so anything developer-specific will
>  break any-one else's build. My head says that the server type and all
>  the other details are not project-specific and so shouldn't be anywhere
>  near the pom but, like you, I'm open to debate. There are many ways that
>  I and my gang may well be doing things wrong.
>

the server type is a simple string like Tomcat55 I believe.. for
glassfish it's J2EE for some reason, for jboss it's JBOSS I think..
there should be no path whatsoever ending up in the pom.. The instance
id (that gets into the profiles.xml) can already contains such
things.. however I don't produce these myself, it's all passed to be
by the server integration plugins..

>
>
>  > In 3.1 I avoid creating a profile in pom, I only write the
>  > server type property in the pom. That has the same effect but
>  > writes much less content.
>
>  I noticed that when I switched to NB6. However, to add more mess to the
>  mix some of my guys are sticking to 5.5 for the meantime. Perhaps I need
>  to issue more dictats.
>

are they still using mevenide 2.3 then? I would recommend upgrading..

>
>
>  >
>  > I'm open to discussion here, however under some circumstances
>  > the web support in netbeans freaks out when no app server is
>  > defined. There's always one server assigned to a ant based
>  > project. I made it sort of optional, but it's still required
>  > for deployment. features like visual web, webframeworks
>  > support in general also require to have the server set. (not
>  > currently supported in released version, but work in progress
>  > already).
>  >
>  > what about if you don't have the server set, the first time
>  > you attempt to do "Run project", you get prompted for the
>  > server to deploy to and the value is kept for the  current
>  > IDE session? That way you don't need to persist anything in
>  > pom or profiles..
>
>  If I try to run without a server set, I get a dialog that tells me that
>  I have to set one before I can run. Perhaps I'm not holding my mouth
>  right.
>
>  I'll try again tomorrow when I'm back at work and see if I can get the
>  behaviour you are describing.


well, you won't get that behaviour now. That's a new feature I was
suggesting for the future that could help you out..

>
>
>  While I'm on, a big thanks from me and from my team for the job you've
>  done with this though. The netbeans/maven integration has saved us a
>  load of grief and time so please don't think I'm complaining. If we have
>  to keep on with manual tinkering around the pom and profiles then
>  so-be-it.

well, I'm not really satisfied with this part of the integration
myself. The Run/Debug project action mappings are generally out of
scope for Maven itself but it needs to be working within the IDE.
The goal is and always was to persist only the minimum information
needed by the IDE and have enerything based on the pom. There's 2
divergent points of view. Maven projects should have the same feature
set as the Ant based projects but at the same time need to play by the
Maven rules.

Milos

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

    http://xircles.codehaus.org/manage_email