I inherited a 7-year-old Java-based product containing about 750 thousand lines of code. As expected, given age, it is not based on the Maven structure. Maven is used to build and release the application. However, Maven is inherited for the project and is commonly used to invoke Ant scripts.
I would like to move to Maven, as in the current setup when landing any of the new (er) instruments such as Sonar, Hudson, etc. - this is a hassle.
I will interview a group to ask what should be a good strategy to make this change? Assuming I can somehow get the time and money to move the code and get it to lure it into my eyes, which is an effective way to check that none of the functions were broken due to mavenization. Needless to say, we cannot rely on unit / integration testing because the code coverage is below 10%.
If I make a distinction between a war created by an existing installation and a war created after mavenization, should the two wars be the same (in size and content)? If so, is this a necessary and sufficient condition to guarantee the lack of functionality?
Thank.
source
share