[
https://jira.codehaus.org/browse/MAPPASM-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294221#comment-294221
]
Karl Heinz Marbaise commented on MAPPASM-149:
---------------------------------------------
Should be done with r16144.
> Chicken-egg problem with 'mvn test'
> -----------------------------------
>
> Key: MAPPASM-149
> URL: https://jira.codehaus.org/browse/MAPPASM-149
> Project: Mojo AppAssembler Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Windows XP, Maven 2.2.1, 3.0.3
> Reporter: Michael Osipov
> Fix For: 1.2.1
>
>
> Running 'mvn test' after a checkout with a clean repo fails:
> {noformat}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.codehaus.mojo.appassembler.booter.AppassemblerBooterTest
> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.141 sec <<<
> FA
> ILURE!
> Results :
> Tests in error:
>
> testSystemProperties(org.codehaus.mojo.appassembler.booter.AppassemblerBooterT
> est): Unresolved compilation problems:
> testRun(org.codehaus.mojo.appassembler.booter.AppassemblerBooterTest):
> Unresol
> ved compilation problems:
>
> testLargeConfig(org.codehaus.mojo.appassembler.booter.AppassemblerBooterTest):
> Unresolved compilation problems:
>
> testMainWithArgs(org.codehaus.mojo.appassembler.booter.AppassemblerBooterTest)
> : Unresolved compilation problems:
> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0
> {noformat}
> Looking into the tests output says:
> {noformat}
> -------------------------------------------------------------------------------
> Test set:
> org.codehaus.mojo.appassembler.daemon.booter.ShellDaemonGeneratorTest
> -------------------------------------------------------------------------------
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 6.265 sec <<<
> FAILURE!
> testGenerateWindowsShellDaemon(org.codehaus.mojo.appassembler.daemon.booter.ShellDaemonGeneratorTest)
> Time elapsed: 5.422 sec <<< ERROR!
> org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException:
> Missing:
> ----------
> 1) org.codehaus.mojo.appassembler:appassembler-booter:jar:1.2.1-SNAPSHOT
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.codehaus.mojo.appassembler
> -DartifactId=appassembler-booter -Dversion=1.2.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.codehaus.mojo.appassembler
> -DartifactId=appassembler-booter -Dversion=1.2.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.codehaus.mojo.appassembler:project-3:jar:1.0-SNAPSHOT
> 2) org.codehaus.mojo.appassembler:appassembler-booter:jar:1.2.1-SNAPSHOT
> 2) org.codehaus.mojo.appassembler:appassembler-model:jar:1.2.1-SNAPSHOT
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.codehaus.mojo.appassembler
> -DartifactId=appassembler-model -Dversion=1.2.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.codehaus.mojo.appassembler
> -DartifactId=appassembler-model -Dversion=1.2.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.codehaus.mojo.appassembler:project-3:jar:1.0-SNAPSHOT
> 2) org.codehaus.mojo.appassembler:appassembler-model:jar:1.2.1-SNAPSHOT
> ----------
> 2 required artifacts are missing.
> for artifact:
> org.codehaus.mojo.appassembler:project-3:jar:1.0-SNAPSHOT
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> {noformat}
> It's evidently clear that the test depends on the model snapshot in the local
> repo which is not there. A "mvn install" would help but is just a workaround
> since all tests run on a n-1 snapshot and not the reactor dependency. The
> pity is that building tags fail which should never happen. Dependencies have
> to made available somehow correctly. Can PlexusTestCase solve this somehow?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
