Setting up Eclipse or Netbeans WindchillDev.Environment

[jessh]

I also use NetBeans -- and directly use the codebase directory.

I'd use a jar, though, if not for particulars about developing Windchill
itself vs. customizing.

I've not had /any /luck with ScanOnDemand, though.

[ddemay]

Depending on what you customize or extend, there are many more jars you need that aren't even under codebase. i.e JCA customization for the work group manager UI.

Ideally the reflection project for Windchill API that Lawrence, Matt, and I are working on will need to look at every jar.





Sent from my Verizon Wireless BlackBerry

[jessh]

This is why I'd suggested a project classpath of

WT_HOME/codebase (or a jar form thereof)
WT_HOME/codebase/WEB-INF/lib/*.jar
WT_HOME/lib/*.jar

That should suffice for any server-side development.

Now if you're talking about developing a remote Java client, however,
then that's different. Then you could do something like:

WT_HOME/codebase (or a jar form thereof)

and then possibly add additional jars as needed, e.g.:

WT_HOME/codebase/wt/security/security.jar
WT_HOME/codebase/lib/WtHttpClientAddOns.jar

Instead you might reference specific existing client jars, e.g.:

WT_HOME/codebase/wtApplet*.jar
WT_HOME/codebase/ptcCore*.jar

and thus keep track specifically of which jars your client will directly
need (there may be indirect runtime dependencies, of course) to run.

For most cases, however, you're talking about server-side development
and things are quite simple.