[ 
https://issues.apache.org/jira/browse/HDDS-1510?focusedWorklogId=253614&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-253614
 ]

ASF GitHub Bot logged work on HDDS-1510:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Jun/19 08:24
            Start Date: 04/Jun/19 08:24
    Worklog Time Spent: 10m 
      Work Description: elek commented on pull request #900: HDDS-1510. 
Classpath files are deployed to the maven repository as pom/jar files
URL: https://github.com/apache/hadoop/pull/900
 
 
   1. Classpath files are plain text files which are generatede for each ozone 
projects. Classpath files are used to defined the classpath of a module (om, 
scm, etc) based on the maven classpath.
   
   Example classpath file:
   
   {code}
   
classpath=$HDDS_LIB_JARS_DIR/kerb-simplekdc-1.0.1.jar:$HDDS_LIB_JARS_DIR/hk2-utils-2.5.0.jar:$HDDS_LIB_JARS_DIR/jackson-core-2.9.5.jar:$HDDS_LIB_JARS_DIR/ratis-netty-0.4.0-fe2b15d-SNAPSHOT.jar:$HDDS_LIB_JARS_DIR/protobuf-java-2.5.0.jar:...
 
   {code}
   
   Classpath files are maven artifacts and copied to share/ozone/classpath in 
the distribution
   
   2. 0.4.0 was the first release when we deployed the artifacts to the apache 
nexus. [~ajayydv] reported the problem that the staging repository can't be 
closed: INFRA-18344
   
   It turned out that the classpath files are uploaded with jar extension to 
the repository. We deleted all the classpath files manually and the repository 
became closable.
   
   To avoid similar issues we need to fix this problem and make sure that the 
classpath files are not uploaded to the repository during a 'mvn deploy' or 
uploaded but with a good extension.
   
   ps: I don't know the exact solution yet, but I can imagine that bumping the 
version of maven deploy plugin can help. Seems to be a bug in the plugin.
   
   ps2: This is blocker as we need to fix it before the next release
   
   See: https://issues.apache.org/jira/browse/HDDS-1510
 
----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 253614)
            Time Spent: 10m
    Remaining Estimate: 0h

> Classpath files are deployed to the maven repository as pom/jar files
> ---------------------------------------------------------------------
>
>                 Key: HDDS-1510
>                 URL: https://issues.apache.org/jira/browse/HDDS-1510
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: build
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Blocker
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 1. Classpath files are plain text files which are generatede for each ozone 
> projects. Classpath files are used to defined the classpath of a module (om, 
> scm, etc) based on the maven classpath.
> Example classpath file:
> {code}
> classpath=$HDDS_LIB_JARS_DIR/kerb-simplekdc-1.0.1.jar:$HDDS_LIB_JARS_DIR/hk2-utils-2.5.0.jar:$HDDS_LIB_JARS_DIR/jackson-core-2.9.5.jar:$HDDS_LIB_JARS_DIR/ratis-netty-0.4.0-fe2b15d-SNAPSHOT.jar:$HDDS_LIB_JARS_DIR/protobuf-java-2.5.0.jar:...
>  
> {code}
> Classpath files are maven artifacts and copied to share/ozone/classpath in 
> the distribution
> 2. 0.4.0 was the first release when we deployed the artifacts to the apache 
> nexus. [~ajayydv] reported the problem that the staging repository can't be 
> closed: INFRA-18344
> It turned out that the classpath files are uploaded with jar extension to the 
> repository. We deleted all the classpath files manually and the repository 
> became closable.
> To avoid similar issues we need to fix this problem and make sure that the 
> classpath files are not uploaded to the repository during a 'mvn deploy' or 
> uploaded but with a good extension.
> ps: I don't know the exact solution yet, but I can imagine that bumping the 
> version of maven deploy plugin can help. Seems to be a bug in the plugin.
> ps2: This is blocker as we need to fix it before the next release



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to