[Anthill-pro] Bom content deletion

emerson cargnin echofloripa.yell at gmail.com
Thu May 29 10:07:04 CDT 2008


I just spent the entire day trying to find out why several files had
been removed as part of the deployment.

I had an artifact css that were added to codestation and deployed by
two different projects. I then decided to make only one project owner
of the css's.

Then when the project that I had removed the css's artifact was
deployed I noticed that the css's weren't there anymore.

After doing tests to try to reproduce I found out that the content of
bom file, which are all the files deployed on the last deployment are
actually removed.

This is a good thing, but I think it should be clearer in anthill
documentation (and even in the page) that the bom file is used to
clean up previous deployments.

The only thing that exist in the docs are about the BOM suppresion,
which is a bit hidden inside the eclipse plugins, which I don't use,
so I never actually look at it:


page 86, AHP 3.5 Documentation PDF:
Codestation BOM Suppression
Normally a Codestation resolve creates BOM files that describe what
artifacts were part of the resolve so that they can be cleaned up for
the next resolve. In scenarios where the cleanup is never performed,
the BOM files are unnecessary.
The Codestation BOM suppression feature can be used in three ways:
• Added to the codestation.properties file.
• Ant tasks have a boolean suppressBoms property.
• The CLI has a suppressBoms option.
If using the BOM suppression feature, the agent must be set to look
for a boolean variable called codestation.
suppress.boms. Once this has been set, the agent will ignore the
codestation.properties file.
Codestation (Developers)


More information about the Anthill-pro mailing list