Hello...
I am revamping our build environment with Maven. And am
meeting with stiff resistance from the group, despite
its obvious advantages. In that context:
From: Dennis Lundberg <[EMAIL PROTECTED]>
>
> What is painful about it?
We are dealing with the problem of 'hot deployment' - after
the initial drop of the warfile into the (locally installed) instance of
Tomcat, we'd like a way to incrementally deploy changes to
class files as a part of our test-debug cycle. So we do this by
having idea deposit the changed class files and class path resources
onto WEB-INF/classes.
Whenever the project has to be regenerated, they have to reconfigure the
project again to map the classes that need to be hot-deployed.
All this is being added to the yet-another-way-maven-is-complicated
argument that is being raised.
The problem of hot deployment is a common one; could you pl advice
on how it may be solved easily, even when the project has to be
regenerated?
Regards
/U
-------------- Original message ----------------------
From: Dennis Lundberg <[EMAIL PROTECTED]>
> [EMAIL PROTECTED] wrote:
> > The Maben Idea Plugin works great - except when I have to add a new
> > dependency to the project after I have regenerated the idea project.
> > It appears that I must regenerate the idea project file everytime the
> > dependencies change. Is this correct? This is very painful - I hope
> > there is a way to incrementally update the previously generated
> > idea project file when dependencies change - either manually or
> > using the plugin.
>
> What is painful about it?
>
> You just run 'mvn idea:idea' once more and then you are done.
>
> > Thanks,
> > /U
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
