One of the things that I did that helped get around the project changing was I added "ivy.run.classpath" to the "run.classpath" in the project.properties For each classpath, I setup an equivalent "ivy.*" classpath variable. Then in my lib\nblibraries-private.properties I define the values. I setup ant to update the properties after doing the ivy retrieve. Two drawbacks with my system. First, I have to run my ivy-retrieve separately (I can't run "ant ivy-retrieve compile test jar deploy", first I run "ant ivy-retrieve" and then I run "ant compile test jar deploy"). Second, I don't see the libs in the ide.
To get started, I took the build file that came with Netbeans ivy plugin and modified it. It had some assumptions that did not work for my environment. Then for each project, I include the ivy specific ant build file. -- Jeff On Mon, Feb 8, 2010 at 1:43 PM, CBy <[email protected]> wrote: > Hi, > > I was wondering what's the most convenient way to use Ivy in combination > with NetBeans 6.8. I am currently doing something similar to > http://wiki.netbeans.org/FaqIvy. It works save some minor details: > > 1) After checking out a project from a repository, NetBeans complains about > reference problems. Fair enough, but building the project does not make the > warning go away. I have to explicitly open the "Resolve Reference > Problems..." dialog and click Close - there is nothing to resolve anymore - > to calm NetBeans. > > 2) When managing dependencies manually, I can point to javadoc and sources > as well, which comes in handy when developing. How to get this feature using > Ivy? By manipulating project.properties? > > 3) My project.properties keeps on changing. I have to commit or revert it > after every build. > > Small annoyances, and more NetBeans than Ivy issues, but perhaps someone > knows how to address them? > > CBy >
