Hi Willem, We rely on a plug-in called cup-maven-plugin. This plugin is indeed maintained by Cloudera. He did not put this plug-in in the mvn repo. And Cloudera's repo often changes its address, which leads to this problem.
Or do we have any other solutions? Ling Miao Willem Jiang <willem.ji...@gmail.com> 于2020年10月27日周二 下午2:48写道： > Could you explain why we have these third party dependencies? > Are they introduced by Cloudera's plugin? > > I don't think hosting these jars in our own repo is a good way to go :( > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Oct 26, 2020 at 7:38 PM ling miao <lingm...@apache.org> wrote: > > > > Hi, > > > > Currently, some fe dependencies that we rely on are not in the maven > repo. > > For example, cup-maven-plugin and java-cup are located at the Cloudera > > 3rd-P. > > This will lead to the risk that our code will not be compiled when the > > third-party repo changes. > > > > I have also tried whether it is possible to replace these dependencies > with > > other packages or versions, but unfortunately the only thing we can use > at > > the moment is this. > > > > So I propose whether we can maintain these jar packages in our own repo > to > > ensure that they can be found every time we compile? > > > > Or do you have any better solutions? > > > > Ling Miao > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@doris.apache.org > For additional commands, e-mail: dev-h...@doris.apache.org > >
