I think that section is worth a slight rewrite.
I think Heiko's and my usecase is the one described in the first green box.
I used to redefine the rhq.containerDir (by issuing
-Drhq.containerDir=</home/me/rhq/build>, where as the sources would be in
/home/me/rhq/src).
This no longer worked, because "rhq-data" was set to go directly into
rhq.rootDir (i.e. it is NOT setup relative to rhq.containerDir).
I've checked all the usages of rhq.rootDir in poms and in code and we ONLY use it to
figure out the dev container location.
Therefore, for people like Heiko and me who want the complete dev runtime out of the
source tree, it is no longer enough to redefine rhq.containerDir as above,
rhq.rootDir needs to be redefined, too (or rather rhq.containerDir no longer needs to be
redefined but rhq.rootDir does).
So I think we should actually either stop using rhq.containerDir altogether and rely on
the "rhq.defaultDevContainerPath" to define a path UNDER rhq.rootDir
(so that it is no longer possible for rhq.containerDir to be outside of rhq.rootDir) or
come up with a slightly more elaborate scheme where the paths of all installable
components (server, agent, storage and data) are specifiable at buildtime and are
essentially independent of each other.
----- Original Message -----
From: "Jay Shaughnessy" <jshaughn(a)redhat.com>
To: rhq-devel(a)lists.fedorahosted.org
Sent: Monday, June 3, 2013 5:05:56 PM
Subject: Re: Cassandra branch merging into master in the next couple of hours (dbsetup
thread)
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...
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel