+1 Good and simple idea We have the same problem with our internal frameworks. This would be nice indeed.
Jacques "Kirk Woll" <[EMAIL PROTECTED]> wrote in message ai9n1o$e0g$[EMAIL PROTECTED]">news:ai9n1o$e0g$[EMAIL PROTECTED]... > Each and every time I create a new project I always want to utilize our > internal APIs. However, since I need to be able to actively modify files in > those APIs I set up them up to take advantage of the Multiple Output Path > feature. This works quite well but requires a quite tedious chore of > setting up those output paths for every new project. The Required Library > system solves this problem for me for non-changing APIs (those contained in > jars, basically) but does not help me in maintaining multiple output paths. > > It seems to me that if the two-way tree list (Source Path / Output Path) > used to configure the multiple output paths in the main Paths section was > also used in the Required Libraries subsystem this would solve the problem > nicely. > > Essentially my request boils down to: Please allow us to include the Output > Path in Required Library definitions. > > Kirk > > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
