On 6/3/2013 8:29 AM, Heiko W.Rupp wrote:
Am 03.06.2013 um 14:21 schrieb Lukas Krejci:
> There's been a silent assumption that rhq.rootDir is a parent of
> rhq.containerDir.
"silent" *sigh*
> As I've been told, the rhq-data is intentionally pushed outside of the
> container dir (using the rhq.rootDir, hence the assumption above) so that you
> keep your data across multiple dev builds.
That makes a lot of sense, as the dev-container should be read-only.
We are far from that as we store pid and logs and so on inside the container dir.
For dev builds the rhq-data dir should be rhq.rootDir/rhq-data. In
appserver/pom.xml, for the dev profile, rhq.rootDir defaults to:
<rhq.rootDir>../../../..</rhq.rootDir>
Is that not what you were seeing? The rhq-data directory is placed
outside, typically alongside, the dev-container directory so that it
survives cleans of the dev-container, just like the RDB. It wouldn't
make sense to clean the dev-container and lose all of your metric data
while all other data survives. The cassandra db is basically part of
the overall rhq persistant store.
> So, if you're like me and you like your builds outside of
your source tree,
> just exchange your -Drhq.containerDir for -Drhq.rootDir when you build.
So I don't need rhq.containerDir anymore?
> Your env will then look like:
> <rhq.rootDir>
> + dev-container
> + rhq-agent
> + rhq-storage
> + ... RHQ server files ...
> + rhq-data
Looks ok, I guess - thanks.
As far as I know, rhq.rootDir and rhq.containerDir should behave as
described here:
https://docs.jboss.org/author/display/RHQ/Advanced+Build+Notes#AdvancedBu...