remove composer.lock so Github vuln scanner will not be confused
This commit is contained in:
parent
b6ecde250f
commit
ea5af0b533
2 changed files with 1 additions and 1570 deletions
|
@ -82,7 +82,6 @@ public class AbstractRpmMojoTest {
|
|||
Paths.get(testOutputPath, "mojo/AbstractRpmMojo-template-expected");
|
||||
Path actualScriptFile =
|
||||
Paths.get(testOutputPath, "mojo/AbstractRpmMojo-template-actual");
|
||||
//assertFalse(Files.exists(actualScriptFile));
|
||||
renderer.render(templateScriptFile, actualScriptFile);
|
||||
assertTrue(Files.exists(actualScriptFile));
|
||||
char[] buff = new char[1024];
|
||||
|
@ -166,6 +165,6 @@ public class AbstractRpmMojoTest {
|
|||
mojo.setBuildPath(String.format("%s%sfiles", testOutputPath, File.separator));
|
||||
mojo.scanMasterFiles();
|
||||
Set<String> masterFiles = mojo.getMasterFiles();
|
||||
assertEquals(64, masterFiles.size());
|
||||
assertEquals(63, masterFiles.size());
|
||||
}
|
||||
}
|
||||
|
|
1568
maven-plugin-rpm/src/test/resources/files/composer.lock
generated
1568
maven-plugin-rpm/src/test/resources/files/composer.lock
generated
File diff suppressed because it is too large
Load diff
Loading…
Reference in a new issue