I think we can't merge this b/c it references an external repository:

https://blog.sonatype.com/2010/03/why-external-repos-are-being-phased-out-of-central/
https://blog.sonatype.com/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/

Before it can be merged it needs to be uploaded to OSSRH and synced....
 


On 2/5/18, 9:01 AM, "Chris Mattmann" <[email protected]> wrote:

    Hmmm...the problem here is that Sonatype won't let us publish to Central 
with
    the below. It's not even an ASF policy thing - it's a Sonatype thing
    
    
    On 2/5/18, 5:55 AM, "Allison, Timothy B." <[email protected]> wrote:
    
        Sorry for the duplication, but I wanted to check on this and didn't 
want it to get lost in a github comment.
        
        
        >Fellow devs on Apache Tika, are we ok with relying on a non-Maven 
central repo?
        
        -----Original Message-----
        From: ASF GitHub Bot (JIRA) [mailto:[email protected]] 
        Sent: Monday, February 5, 2018 8:47 AM
        To: [email protected]
        Subject: [jira] [Commented] (TIKA-2565) Upgrade edu.ucar dependencies 
to 4.6.11
        
        
            [ 
https://issues.apache.org/jira/browse/TIKA-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352395#comment-16352395
 ] 
        
        ASF GitHub Bot commented on TIKA-2565:
        --------------------------------------
        
        tballison commented on a change in pull request #218: TIKA-2565 Upgrade 
edu.ucar dependencies to 4.6.11
        URL: https://github.com/apache/tika/pull/218#discussion_r165975019
         
         
        
         ##########
         File path: tika-parsers/pom.xml
         ##########
         @@ -44,14 +44,22 @@
             <vorbis.version>0.8</vorbis.version>
             <pdfbox.version>2.0.8</pdfbox.version>
             <jempbox.version>1.8.13</jempbox.version>
        -    <netcdf-java.version>4.5.5</netcdf-java.version>
        +    <netcdf-java.version>4.6.11</netcdf-java.version>
             <sis.version>0.8</sis.version>
             <!-- used by POI, PDFBox and Jackcess ...try to sync -->
             <bouncycastle.version>1.54</bouncycastle.version>
             <commonsexec.version>1.3</commonsexec.version>
             <httpcomponents.version>4.5.4</httpcomponents.version>
           </properties>
         
        +  <repositories>
        +    <repository>
        +        <id>unidata-all</id>
        +        <name>Unidata All</name>
        +        
        + <url>https://artifacts.unidata.ucar.edu/repository/unidata-all/</url>
         
         Review comment:
           Fellow devs on Apache Tika, are we ok with relying on a non-Maven 
central repo?
        
        ----------------------------------------------------------------
        This is an automated message from the Apache Git Service.
        To respond to the message, please log on GitHub and use the URL above 
to go to the specific comment.
         
        For queries about this service, please contact Infrastructure at:
        [email protected]
        
        
        > Upgrade edu.ucar dependencies to 4.6.11
        > ---------------------------------------
        >
        >                 Key: TIKA-2565
        >                 URL: https://issues.apache.org/jira/browse/TIKA-2565
        >             Project: Tika
        >          Issue Type: Wish
        >          Components: parser
        >    Affects Versions: 1.17
        >            Reporter: Lewis John McGibbney
        >            Assignee: Lewis John McGibbney
        >            Priority: Minor
        >             Fix For: 2.0
        >
        >
        > An [existing PR|https://github.com/apache/tika/pull/212/files] 
suggests to upgrade the netcdf4-java dependency, however it does not address 
the issue.
        > This PR will add the correct Maven repository configuration and then 
make the upgrade(s).
        > https://www.unidata.ucar.edu/software/thredds/current/netcdf-java/refe
        > rence/BuildDependencies.html
        
        
        
        --
        This message was sent by Atlassian JIRA
        (v7.6.3#76005)
        
        
    
    
    


Reply via email to