Task #16235

Changes in org.gcube.common.HEAD

Added by Manuele Simi 11 months ago. Updated 11 months ago.

Status:ClosedStart date:Mar 07, 2019
Priority:NormalDue date:
Assignee:Luca Frosini% Done:

100%

Category:common
Sprint:zz - GXRest
Milestones:
Duration:

Description

Add the following two configurations to org.gcube.common.HEAD:

gxRest-gxJRS.HEAD
gxRest-gxHTTP.HEAD

Remove the following configuration from org.gcube.common.HEAD:

gxRest.HEAD

History

#1 Updated by Luca Frosini 11 months ago

  • Status changed from New to In Progress

#2 Updated by Luca Frosini 11 months ago

I added both of them but I think that it is not possible to remove gxRest. gxRest-gxJRS and gxRest-gxHTTP could depend on it.

Let me know if you want to try to remove gxRest to see what happen.

#3 Updated by Manuele Simi 11 months ago

Luca Frosini wrote:

I added both of them but I think that it is not possible to remove gxRest. gxRest-gxJRS and gxRest-gxHTTP could depend on it.

Let me know if you want to try to remove gxRest to see what happen.

The new configs do not depend on gxRest. I know the dependency resolver of Etics did add the dependency but that's not correct. @gabriele.giammatteo@eng.it is working on fixing this misbehavior.

Meanwhile, please, remove gxRest from common.HEAD.

#4 Updated by Gabriele Giammatteo 11 months ago

I think I managed to fix it. Now, even if gxRest is still known by ETICS as one of the providers of the org.gcube.common:gxHTTP and org.gcube.common:gxJRS Maven coordinated, it should not be selected when dependencies are added in other components. I specifically added a property to exclude it (more info at the bottom of this [1] section in the wiki).

I triggered the update of the dependencies in all the components (in HEAD) that depends on gxRest. In the tomorrow nightly build we should see that nobody depends on gxRest, so we can remove it from the HEAD

[1] https://wiki.gcube-system.org/gcube/ETICS#ETICS_ModelSync

#5 Updated by Luca Frosini 11 months ago

  • % Done changed from 0 to 100
  • Status changed from In Progress to Closed

#6 Updated by Manuele Simi 11 months ago

  • % Done changed from 100 to 90
  • Status changed from Closed to In Progress

Let's wait until the new build is available (as suggested by @gabriele.giammatteo@eng.it ) before closing this issue.

#7 Updated by Luca Frosini 11 months ago

  • Status changed from In Progress to Feedback

#8 Updated by Manuele Simi 11 months ago

There was an error in the install path and the two new configs were not building properly. I just fixed the path in both configs but since remote builds do not work, we can only wait for the next scheduled build.

#9 Updated by Manuele Simi 11 months ago

  • % Done changed from 90 to 100
  • Status changed from Feedback to Closed

gxHTTP and gxJRS now build properly on HEAD.

Also available in: Atom PDF