Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re[2]: [higgins-dev] Output directories for higgins projects

Yeah, it was my mistake. I had to send an email before I did any
changes and now if we agree on this I'll have to change it again (and
make sure that the .cvsignore files are properly set up).



Tuesday, July 31, 2007, 10:44:20 PM, you wrote:

> That sounds okay to me as long as these are properly included in
> .cvsingore files.  I just got through updating to the new
> configuration code and noticed that it wasn't standard with the
> other ones ... it used build/bin so I changed it to the standard. 
> So, if you prechanged this one, you'll have to do it again.  Anyway,
> what was there would show changes that needed to be synchronized in
> the build directory so we just need to make sure the .cvsignore files are properly set up.

> Thanks,
> Tom

>>>> Valery Kokhan <vkokhan@xxxxxxxxxxxxxx> 7/31/2007 12:54 PM >>>
> In order to start running automated build scripts for higgins
> components we need to standardize output directories for our
> components.

> Right now output directories for higgins components looks like:
> build/ - location for project's class files
> build/lib/ - location for jar output
> build/doc/ - location for javadoc output
> build/plugins/ - location for output as plug-in

> Our new automated build script have a problem with output directory
> for class files because it need to use the same directory (build/) for
> temporary files which may cause unpredictable mistakes during builds.

> My proposal is to change output directory for project's class files to
> build/bin/ for all higgins projects to make sure that during automated
> builds we don't override or delete something by mistake.

> I'm going make proposed changes to all higgins projects and update
> build scripts respectively.

> Does anyone have problems with that?

Back to the top