geniusjoe commented on PR #382:
URL: https://github.com/apache/flume/pull/382#issuecomment-1235786489

   > @busbey Hello, my bro. I notice that you have changed `repository` 
properties in `flume-ng-morphline-solr-sink` pom.xml.
   > 
   > ```
   > <repositories>
   >     <!-- Morphlines needs the ua-parser library, which isn't published to 
Maven central.
   >          This repo from Twitter is where Morphlines gets this dependency 
from normally,
   >          but we need to specify HTTPS so that Maven won't ignore the repo.
   >     -->
   >     <repository>
   >       <id>maven-twttr</id>
   >       <name>Twitter Public Maven Repo</name>
   >       <url>https://maven.twttr.com</url>
   >       <snapshots>
   >         <enabled>false</enabled>
   >       </snapshots>
   >     </repository>
   >     <!-- Morphlines brings in a version of solr-core that needs the 
restlet jar which isn't
   >          in Maven central. We need to include the HTTPS version of the 
repo Solr gives in
   >          order to keep Maven using the repo.
   >     -->
   >     <repository>
   >       <id>maven-restlet</id>
   >       <name>Restlet Public Maven Repo</name>
   >       <url>https://maven.restlet.org</url>
   >       <snapshots>
   >         <enabled>false</enabled>
   >       </snapshots>
   >     </repository>
   > </repositories>
   > ```
   > 
   > And because current repo xml config not contains maven central, will it 
leads to the above fetching `json-smart` timeout exception in CI? If so, should 
we need to add maven central again?
   
   @busbey 
   Emm exactly I know little about maven advanced setting. Can you help me to 
see why the CodeQL CI autoBuild phase ran failed? I think the CI was failed in 
compiling `Flume NG Morphline Solr Sink` step. I'm new to this component and do 
not change in this commit. 😂
   
![image](https://user-images.githubusercontent.com/37236056/188213976-4c3adce9-66a7-469c-a217-067453a54f15.png)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@flume.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to