Closed mtholder closed 10 years ago
I think that at least part of our epic struggles to deploy oti today were caused by all of the jar's having version 0.0.0a. So maven thinks that it can use its cache. That or our pom files in oti are not correct.
We decided not to poke this potential hornets' nest for now.
I think that at least part of our epic struggles to deploy oti today were caused by all of the jar's having version 0.0.0a. So maven thinks that it can use its cache. That or our pom files in oti are not correct.