You can also do it the other way round, so that ant will get the
dependencies from maven and copy them to the lib folder:

http://groups.google.com/group/javaposse/browse_thread/thread/f862b782de787bfd/fb5631472de76e6b

http://wiki.netbeans.org/FaqMavenAntTasks

Cheers,
 Adam

On May 31, 6:01 am, Manfred Moser <[email protected]> wrote:
> On Thursday May 28 2009, Peter Becker wrote:
>
> > While I haven't tried that particular combination yet, I suspect
> > you get similar problems to what happens when combining Grails and
> > Maven. Just today I decided to add POI to my little Grails
> > prototype and found out that adding the dependency in the POM is
> > just not good enough for NetBeans, I had to place a copy into the
> > "lib" folder, too. Otherwise all POI classes will be unknown to the
> > editor.
>
> in a situation like that I would recommend to configure the maven-
> dependency- plugin to copy all the dependencies into the lib folder as
> part of the process-resources lifecycle phase and additionally the
> clean plugin to delete the file from the lib folder.
>
> That way mvn clean will remove the files in the lib folder but mvn
> compile or mvn install or whatever will pretty much as first step
> after clean copy the jars of all dependencies (including transitive
> ones) into the lib folder. Then you just have to configure your ide to
> look that.
>
> I have had good experience with this migrating from ant builds to
> maven build as well. Maven could at a minimum take over the dependency
> management with this with a simple mvn call from ant..
>
> manfred
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "The 
Java Posse" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to