Hi,
sorry I dismissed the affect version of plug-in 0.14. I thought we
are discussing the trunk features.
My fault, sorry once again for may stupid income.
PZn/
Pavel Znamenáček wrote:
Hi all,
ad 1) Just a small aside of discussion, in this situation of
embedding the maven to non Java based system, could be this tool helpful?
http://www.ikvm.net/index.html
ad 2) How many interactions can jetty handle, I mean how many
running devenv.exe can be serviced with responses to requests at once?
It would be probably 1:1, one devenv serviced via one jetty. => Memory
and network requirements.
ad 3) I would prefer following requirements from following
common needs and usage: (Just my opinion and feeling, pleas skip
irrelevant/stupid needs and requirements to Maven or NMaven)
Some of needs and usage:
u1: I spent all day in VS with managing code and the project
contents with a lot of my own internal project builds in scope of
solution.
u2: I use refactoring tools (ReSharper, DevExpress, ...)
very often which implies actions like renaming the files and some time
the project also.
u3: I debug in the unit test often within built and dependent
assemblies.
Requirements:
r1: Memory requirements - my usual devenv.exe process
occupies about 200MB of memory. How much occupies maven and java? And
how much all of them together? I think there could be situations where
more then one devenv.exe will run at once.
r2: The maven embedder have to be really reflective if you
really want to embed one.
r3: The IDEs' add-ins change the content of the project file,
and I think csproj is not the same as pom.xml. The pom.xml declares
much more then building rules. I see csproj as a subset of pom.xml.
r4: Give as ability to generate {cs|vb|js}proj from pom.xml -
with filled dependencies to other pom.xml or assemblies.
r5: Give as ability to generate sln for all pom.xml - and I
use special editor VS to edit, debug and run the projects.
r6: Give as ability to start VS for pom.xml (modules) of
generated sln to start working at morning and let us resolve changes
like back-port into pom.xml at evening.
r7: If you embed maven, how do the maven distinguish between
debug and release assemblies?
r8: Save the maven's position at the best continuum system.
PZn/
Shane Isbell wrote:
On Mon, Mar 31, 2008 at 10:51 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
There is some discussion on NMAVEN-106 [1] about the embedder in a
long-running Jetty process vs. one-off 'mvn' invocations.
I think it needs more discussion before moving to JIRA as an
enhancement request.
One question I have is, what would making that change mean for the
feature that keeps the pom in sync with the solution and .csproj
files?
The VS addin directly handles the modification of the poms,
independent of
the maven embedder service, so that part would not be affected by either
solution.
Shane
[1] http://jira.codehaus.org/browse/NMAVEN-106
Thanks,
--
Wendy
--
**Pavel Znamenacek**
*Software Developer*
**CN Resources International (CZ) a.s.**
Ve Smeckach 20, Prague 1, 110 00
*VoIP Line: +420 234 375 383* | Fixed Line: +420 234 375 183
E-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> | Web:
http://www.cncz.cz
