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

ASF subversion and git services commented on SOLR-15902:
--------------------------------------------------------

Commit 1bbe67514ccce3a08b539c0b554d1feb1abb0a8b in solr's branch 
refs/heads/branch_9_0 from Jan Høydahl
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=1bbe675 ]

SOLR-15902 Bring back AwaitsFix annotation for this test

(cherry picked from commit 3545594bcf6da136db6caf9ed27b468e5c12e5c0)


> PackageManagerCLITest.testPackageManager fails on main
> ------------------------------------------------------
>
>                 Key: SOLR-15902
>                 URL: https://issues.apache.org/jira/browse/SOLR-15902
>             Project: Solr
>          Issue Type: Task
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Gus Heck
>            Assignee: Houston Putman
>            Priority: Major
>             Fix For: 9.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> The version for main has advanced, but this test contains a package with an 
> upper version constraint of 9 and main has advanced to 10.0 It also contains 
> two binary jar files containing classes with a fullstory package and no 
> source code. There is a manifest.json, but there is also another copy baked 
> into one of the jars. This needs to be cleaned up such that these jar files 
> (containing packages to be installed during tests) can be rebuilt by a build 
> target and are not checked in as binary jars. (with a .tmp ending). Also all 
> classes run by the build should exist as source code. If the code for these 
> classes is owned by Fullstory, they should be replaced with something owned 
> by Apache.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to