Re: Problems building latest beam source

2021-01-27 Thread Tomo Suzuki
Thank you. I confirmed that I can build the source now. On Tue, Jan 26, 2021 at 7:59 PM Kyle Weaver wrote: > This should be fixed now. > > On Tue, Jan 26, 2021 at 10:23 AM Kyle Weaver wrote: > >> I missed this thread and filed a JIRA for it: >> https://issues.apache.org/jira/browse/BEAM-11689

Re: Problems building latest beam source

2021-01-26 Thread Kyle Weaver
This should be fixed now. On Tue, Jan 26, 2021 at 10:23 AM Kyle Weaver wrote: > I missed this thread and filed a JIRA for it: > https://issues.apache.org/jira/browse/BEAM-11689 > > > We could swap the spring.io repo for the pentaho nexus one > public.nexus.pentaho.org (here probably in Beam >

Re: Problems building latest beam source

2021-01-26 Thread Kyle Weaver
I missed this thread and filed a JIRA for it: https://issues.apache.org/jira/browse/BEAM-11689 > We could swap the spring.io repo for the pentaho nexus one public.nexus.pentaho.org (here probably in Beam

Re: Problems building latest beam source

2021-01-26 Thread Tyson Hamilton
I saw this issue on another OSS repo ( https://github.com/apache/hudi/issues/2479), they just removed the spring.io repository but I'm not sure where their dep would come from then. We could swap the spring.io repo for the pentaho nexus one public.nexus.pentaho.org (here probably in Beam

Re: Problems building latest beam source

2021-01-25 Thread Tomo Suzuki
I'm seeing the same problem. * What went wrong: Execution failed for task ':sdks:java:io:hcatalog:compileJava'. > Could not resolve all files for configuration ':sdks:java:io:hcatalog:provided'. > Could not resolve org.pentaho:pentaho-aggdesigner-algorithm:5.1.5-jhyde. Required by:

Problems building latest beam source

2021-01-25 Thread Steve Niemitz
I ran into issues resolving org.pentaho:pentaho-aggdesigner-algorithm:5.1.5-jhyde, it looks like the spring repo hosting it has locked the artifact, I get a 401 unauthorized trying to download it. Has anyone else run into this? I assume many people have the artifact cached locally and so haven't