We have multiple source projects that make up the codebase for our overall project. How would we use Glean to get some aggregate feedback from all of the code?
With the current release of Glean you cannot specify multiple source folders. A big part of the reason for this is that most of the tools that Glean drives have you specify the source or class files as a fileset, and a fileset only lets you specify a single directory. Without bringing in other libraries or scripting languages for iteration, there isn’t much to do within the confines of the Ant language. For now, you have a couple of choices: • create multiple project property files for Glean, and run each one separately • modify your build script to create a pseudo-project area, with all of the source files copied in to one tree. You can then point Glean at that area. The ideas behind Glean developed from working on a project where there were many component parts to the application, and generating feedback for the entire codebase was an important part of the daily build. That feedback process, however, was very much tuned for that application, but even there the feedback was not truly
Related Questions
- What are some projects I can add to the overall scope of my remodeling project, or do to make my existing houses space more "Green"?
- Can a QCP project be split up into several different disciplines or are QCP projects to be single source?
- How is the Pentaho BI Project different from other Open Source BI projects?
