Re: [mevenide-user] mveneide is more like an island in netbean ?

Currently, I can do just that.

In fact, I was doing it the other way round. I first started use maven
because of appfuse which generates a maven project and everything is done in
command line. But testing with it is so slow (mvn jetty:run every time and
wait for all those steps).

So I started it the eclipse way, just create a web project and drop the
appfuse POM into the project. Now I can take this to anywhere and the maven
way still works but I have much easier/faster test cycle. the project
itself, being in standard maven layout with the right POM can be imported to
any IDE that have good maven support. The .classpath now contains basically
only one entry, the m2eclipse managed libraries. Of course I can still drop
things to WEB-INF/lib for things that is not in maven or using the old
eclipse way to add more to .classpath(mainly for things that is not intended
to be deployed but helpful during development).

I found lots of mis-information about eclipse and maven.



Laurent Forêt-2 wrote:
> 
> Eclipse users now they had discovered Netbeans, should learned that the
> *POM
> is the key word *of a project (not the .classpath etc ...). The only
> purpose
> of an IDE as for java sources is to help you to create and manage it.
> That's
> all !
> 
> I am working with eclipse users, and it is very hard to explain them that
> if
> it works in Eclipse it is not enough. It should work on every
> ernvironnement, like continuum[1] or other continuous integration tool.
> And
> it is very hard stuff to deal with boths, poms and .classpaths.
> 

-- 
View this message in context: http://www.nabble.com/mveneide-is-more-like-an-island-in-netbean---tp14544683p14563065.html
Sent from the mevenide - user mailing list archive at Nabble.com.


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

    http://xircles.codehaus.org/manage_email