File modification detection

[alesj]

I started working on this MC/VFS issue:
- http://jira.jboss.com/jira/browse/JBMICROCONT-160

Just to get a better feel for who tracks down the changes to deployed files I stumbled on the following behaviour:
I have this structure:
- my-test.jar
-- META-INF
--- test-beans.xml

When dropped in deploy directory, it get deployed as expected.
But when I do some property change in the test-beans.xml nothing happens.
Is this expected?

Are we only checking top level deployments?
I guess tracking the changes to metadata wouldn't hurt.
Since that's what is somehow the problem with JBMICROCONT-160 + how to actually rebuild the whole parent structure if a change occurs ...

[starksm64]

Its the ProfileImpl.getModifiedDeployments that determines what has been modified. This only checks the root currently. It could be updated to check metadata files as well, there is a todo for that.

[alesj]

It could be updated to check metadata files as well, there is a todo for that.

OK, I'll have a look at that - making it more generic.
Should I update the repository profile version as well?

[starksm64]

Yes.

[alesj]

"alesj" wrote:

It could be updated to check metadata files as well, there is a todo for that.

OK, I'll have a look at that - making it more generic.

I guess if a component changes, we need to re-deploy the whole top deployment?
Or how else to guess what the change triggers?

Or there could be user defined changes, e.g. -beans.xml change could just uninstall and re-install those beans.