In the past (before rhqctl) the mvn builds would build the agent in agent/target/rhq-agent
(so we'd run teh agent out of the actual agent/target/rhq-agent directory). Yes,
you'd have to build things like plugin-container module separately before building the
agent if you needed to test changes to the PC. We did (and I believe still do) have a
-Pagent profile defined that builds just the agent modules - so you'd build from the
root directory with -Pagent and your agent/target/rhq-agent would be your agent. It
didn't use the -Pdev profile IIRC.
That's just the history.
Now that we have rhqctl, there is dev-container/rhq-agent that now exists (assuming you
ran "rhqctl install") - so I don't have a problem if the agent and its
dependency modules put things in there when built with -Pdev.
----- Original Message -----
Hi,
When working with the agent's modules (such as plugin-container), these files
are not currently updated when compiling with -Pdev, unlike many server
modules. Does anyone have an objection on why it shouldn't be done? I'm
currently targeting ${rhq.defaultDevContainerPath}/rhq-agent (like the
rhq-server path), but I'm assuming someone could have changed the agent's
path, in which case this wouldn't work. Is anyone actually changing the
agent-path on dev-container? Or have any other objections?
I opened PR #126 for comments also.
- Micke
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel