"Baeriswyl Kuno - Extern (IT-BA-MV)" <[EMAIL PROTECTED]> wrote on 15/05/2008 16:47:26:
> That's why I'm using the runtime argument. I guess that my point, is that I do not really have a good idea on the fit of and the point in having the eclipse plugin itself. Having to specify the workspace, not only not being portable (ok, you can specify it on the command line, but that is a hack at best) just smells to me of something utterly wrong - at the base concept level. > However, the workspace must be indicated, otherwise it won't generate > correct eclipse files. If you have a bit more time, the you should have a > closer look to the eclipse plugin source code. The plugin does consider > the target application server and generates the files according to the > needs of the specified environement. That's why the workspace argument is > required. It looks up your applications server configuration in your > workspace that matches with configuration given in <wtpdefaultserver>. > The recognising of an EJB project is a matter the maven packaging option. All of which has to be specified in the POM. It is issues like this that leads me to agree with the original Maven 1 developers point of view. Keep the build and descriptive details separate. However, those philosophical issues aside, I did get my approach to work and not having to supply the workspace. Once I cleaned up the facet issues that is. The issue was that RSA was not showing the deployment descriptor in the Project Navigator View of the J2EE Perspective. If I get a sec, I'll have a look further at your approach. -Chris ********************************************************************** CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. If you are not the intended recipient of this message you must: - Not use, copy, distribute or disclose it to anyone other than the addressee; - Notify the sender via return email; and - Delete the message (and any related attachments) from your computer immediately. Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent. Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI. ********************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
