Hi Jörg 2 issues for this approach
1. Both modules use the same local repo, so I dont think maven-dep-plugin would resolve the file to timestamp filename format that i am looking for. It is just be artifactId-versoin-SNAPSHOT.xxxx 2. Even if it resolves to the desired file name, I still have to extract the file name and use in my test report ( ie run test result is from the artifact that already deploy at maven repo Thanks -Dan On Fri, Jul 17, 2015 at 12:34 AM, Jörg Schaible < [email protected]> wrote: > Hi Dan, > > Dan Tran wrote: > > > Hi Jörg > > > > Base on your idea, I guess I can pull down the maven-metadata.xml to > > figure out the latest name in my next test phase which is already a maven > > module of its own > > Simply add it as dependency and let the dependency plugin copy it (you may > even rename it) into target. There's no reason to meddle with maven- > metadata.xml. > > > This may not be correct if a user directly invokes the second test > > project, but it is good enough for now > > If it was deployed before, it will use the correct version (unless your > user > has some obscure configuration in his settings.xml). > > Cheers, > Jörg > > > > > Thanks > > > > -Dan > > > > On Thu, Jul 16, 2015 at 11:30 PM, Jörg Schaible < > > [email protected]> wrote: > > > >> Hi Dan, > >> > >> Dan Tran wrote: > >> > >> > Hi > >> > > >> > Is there a hook into after maven deploy to retrieve the snapshot > deploy > >> > name? > >> > > >> > User case: > >> > > >> > * Maven build, smoke test, and deploy huge artifacts (OVA) > >> > * After deploy, continue with more tests but need to know the deploy > >> > name > >> > > >> > (artifactid-version-timesamp.ova), to reference again the test > >> > report > >> > > >> > > >> > I can write a custom plugin to execute after deploy phase > >> > >> If it is deployed, it is published - even if a later test might fail. > >> Therefore you can move those tests simply into a second project > depending > >> on > >> the original and let the dependency plugin resolve the name. > >> > >> Cheers, > >> Jörg > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
