I am looking at strange behavior from my Maven 2.2.1 establishment while establishing a war.
Occasionally, I will update a class, but the updated version has not been packaged in the artifact created by mvn install.
So far, I have determined that an updated class file is created in the target directory and that the same name range in the generated. Water is not the same (different date modified, different size)
Debug output has been produced from the command line with the Running Maven-Ax flag:
[DEBUG] * Web-IF / Class / MyPackage / MyClas Class is up to date.
I think I did the same thing that was cached earlier (?) Was an incomplete compilation of eclipses, which caused errors of 'unceded compilation problem' from Maven Build. , But a working distortion from an Eclipse export
- How Maven determines whether a file is 'Updated' during the process?
- Where are the files being compared to Maven?
- Can I force Maven to create a package from scratch?
- Any other thoughts would be appreciated!
- should be created under scratch from the package?
So far, I have set an updated .class file The target is produced in the directory, and that the square of the same name in production is not equal. (Different date modified, different size)
Just make sure that the sections are Goal \ classes , targets .
You can force full build
mvn clean install install steps It runs clear (basically removes the target directory) before running
In addition - check copies of your classes outside the Maven Build directory. In this situation, because it is a webapp, src / main / webapp / WEB-INF / classes
Comments
Post a Comment