On Thu, Feb 1, 2018 at 12:50 PM, Robert Varga <n...@hq.sk> wrote: > On 01/02/18 12:27, Michael Vorburger wrote: > > On Thu, Feb 1, 2018 at 6:37 AM, Anil Belur <abe...@linuxfoundation.org > > <mailto:abe...@linuxfoundation.org>> wrote: > > > > Hello Controller-dev: > > > > The below errors suggests the pom file dependencies might be > > breaking the build. > > Can anyone take a look at this and provide a fix? > > > > > > I'm puzzled, because this worked (and autorelease passed) until very > > very recently... am trying to understand the context here - version > > bumps? New releases? >
Why is the merge https://git.opendaylight.org/gerrit/#/c/65941/ (based on https://git.opendaylight.org/gerrit/#/c/39484/) that went in 10 days ago popping up as a problem only now? We've had successful autorelease builds since then. > This is rather simple: it works on verify/merge because it is pulling > things from nexus, where they have been populated by mdsal-merge jobs. > Thanks a lot for the hint, I think I see what you are getting at... as this probablem doesn't show up outside of autorelease, for a reliable fix we should reproduce locally. I've no idea if how run whatever script produces those version replacements that drop SNAPSHOT locally. But I'm guessing running autorelease with -P!opendaylight-snapshots (tx skitt!) and that mvn option to only build what the archetype depends on should lead to a similar effect and also fail locally? I will try to do that... BTW: Can anyone think of any smart way to make this fail fast outside of autorelease during regular validate jobs? More for future non-regression than for fixing this in the short term. Because I feel even after we fix this, it will hit us again, every time we change some dependency of the archetype. Validate will pass, we'll merge, and boum possibly break autorelease again. > The project does not list a dependency on mdsal-model-sources, hence > that artifact is not built in autorelease until after the archetype: > So where would we best add these dependencies we need to "help" Maven figure out the dependency tree correctly? Are we saying we need to (today and remember in the future...) put everything that the archetype needs into a <dependencies> in controller/opendaylight/archetypes/pom.xml ? > [INFO] archetypes-parent .................................. SUCCESS [ > 1.964 s] > [INFO] opendaylight-startup-archetype ..................... FAILURE [ > 6.915 s] > [INFO] controller ......................................... SKIPPED > > [...] > > [INFO] features-mdsal-model-aggregator .................... SKIPPED > [INFO] mdsal-model-artifacts .............................. SKIPPED > [INFO] iana-if-type ....................................... SKIPPED > > Bye, > Robert >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev