Incremental changes and building AS trunk

[jaikiran]

I was recently trying a few things on AS trunk which now has the Maven builds. Initially i triggered a

mvn clean install

and generated the AS jboss6Alpha. Then while working on a few changes, i updated the versions of some components in the component-matrix pom.xml and triggered a

mvn install

However the AS jboss6Alpha still contained the old versions of the components. I had to delete the entire output/jboss6Alpha (or i think run a mvn clean install, don't remember which of these two fixed it) for the changes to be reflected. Is this expected?

[pgier]

The distribution build uses the Ant copy task to copy jar files from the local maven repository (~/.m2/repository). It's possible that if the file copied in the first build had a newer timestamp than the newer version jar in the local maven repo, that ant would skip the copy. I'm not sure if this is the cause of what you saw, but it seems possible.

I'm not sure what is the best way to fix this. I could set the copy tasks to overwrite=true, to force a copy every time, but this might slow down incremental builds a little bit.

[jaikiran]

I'll collect more info the next time i try something on trunk, to ensure that its the timestamp problem.