[ 
https://issues.apache.org/jira/browse/GEODE-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16570873#comment-16570873
 ] 

ASF subversion and git services commented on GEODE-5533:
--------------------------------------------------------

Commit 3f51242334260c1e13f56690b3b698a707ee0130 in geode's branch 
refs/heads/develop from [~rhoughton]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3f51242 ]

GEODE-5533 Support Gradle 4.9 publication enhancements (#2264)

* GEODE-5533 Support Gradle 4.9 publication enhancements

Upgrading to Gradle 4.9 broke publish/install due to a non-existent jar
output from geode-assembly. More diligent pruning of the archives
configuration has fixed the problem.

* include `install` task in Concourse build

Co-authored-by: Patrick Rhomberg <prhomb...@pivotal.io>


> ./gradlew install fails with "Could not publish configuration 'archives'"
> -------------------------------------------------------------------------
>
>                 Key: GEODE-5533
>                 URL: https://issues.apache.org/jira/browse/GEODE-5533
>             Project: Geode
>          Issue Type: Task
>          Components: build
>            Reporter: Patrick Rhomberg
>            Assignee: Patrick Rhomberg
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Some targets changed in gradle 4.8 -> 4.9.  The configuration step of 
> removing jar inclusion to the publication or the archives was invalidated.  
> This step needs to be updated to conform to the new targets.
> {noformat}
> > Task :geode-assembly:install FAILED
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':geode-assembly:install'.
> > Could not publish configuration 'archives'
>    > Cannot publish artifact 'geode-assembly.jar' 
> (/Users/prhomberg/workspace/gemfire/open/geode-assembly/build/libs/geode-assembly-1.8.0-SNAPSHOT.jar)
>  as it does not exist.
> {noformat}



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

Reply via email to