the shortcut option "--clean" used to refer to --cleanconfig. however, now we have --cleanallconfig from bug #782612 so "--clean" is ambiguous and causes an error at startup. To support users who are used to --clean from previous versions, let's rename --cleanallconfig to something else like --allcleanconfig or something like that.
I'll also add a --token cmdline option that lets the user set the token to avoid having the user enter -Drhq.agent.security-token when setting it.
for release-3.0.1 branch: * make --cleanallconfig to be unambiguous (rename it) * change the error message to be clear that the user has to enter -Drhq.agent.security-token to set the token
adding reference to the doc BZ https://bugzilla.redhat.com/show_bug.cgi?id=783247 this BZ is for both the Wiki updates ... AND the required doc change to JON 2.4.2 docs
the new error will say: The server has rejected the agent registration request. Cause: [org.rhq.core.clientapi.server.core.AgentRegistrationException:The agent [fooagent] is attempting to re-register without a security token. Please consult an administrator to obtain the agent's proper security token and restart the agent with the option "-Drhq.agent.security-token=<the valid security token>"] the new option is now called --fullcleanconfig - the shortcut is still -L.
master commit: 1189549 release-3.0.1 commit: 1f42ac3 did not include a --token cmdline option in this comment
Fix went into JON2.4.2 and master, so setting target release versions appropriately.
Removing JON 2.4.2 from target list as this is a community BZ. This was tested and verified in downstream JON 3.0.1 as per Bug 786600 and is available in RHQ 4.3.
Bulk close of old bugs in VERIFIED state.