Re: [ui] Compiled Classes B.T.
Jan Rojcek <[email protected]>
| Newsgroups | gmane.comp.java.netbeans.modules.projects.devel |
|---|---|
| Message-ID | <[email protected]> |
I think the motivation for adding java roots into a build target was to allow the user to control which of the java roots are compiled. However, I am thinking about an example of when this might be needed. Java developers, any help? Adding of the source roots to a build target will be removed from the spec. The source roots should contain non-compilable objects. Jano Jan Pokorsky wrote: > FYI: I filed a similar issue for this earlier. Please update it with > your resolution. > > http://www.netbeans.org/issues/show_bug.cgi?id=32770 > > Jan > > Svata Dedic wrote: > >> Hello, Chris, >> >> Can you provide me with details how is supposed "Add Roots to <build >> target>" affect the way how things are processed during build ? >> And specifically, what should happen when the user adds something to >> that list, what is not present in Packages node (e.g. is not an >> existing java root) ? >> >> Thanks, >> -Svata > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >