You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "squakez (via GitHub)" <gi...@apache.org> on 2023/03/01 08:22:06 UTC

[GitHub] [camel-k] squakez opened a new issue, #4086: Nightly release fail after 2.0

squakez opened a new issue, #4086:
URL: https://github.com/apache/camel-k/issues/4086

   ```
   go: errors parsing go.mod:
   /home/runner/work/camel-k/camel-k/go.mod:7:2: require github.com/apache/camel-k/pkg/apis/camel: version "v2.0.0-nightly" invalid: should be v0 or v1, not v2
   /home/runner/work/camel-k/camel-k/go.mod:8:2: require github.com/apache/camel-k/pkg/client/camel: version "v2.0.0-nightly" invalid: should be v0 or v1, not v2
   /home/runner/work/camel-k/camel-k/go.mod:9:2: require github.com/apache/camel-k/pkg/kamelet/repository: version "v2.0.0-nightly" invalid: should be v0 or v1, not v2
   make: *** [Makefile:345: build-resources] Error 1
   ```
   there must be some check limiting the major release.


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-k] squakez commented on issue #4086: Nightly release fail after 2.0

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4086:
URL: https://github.com/apache/camel-k/issues/4086#issuecomment-1450400534

   This one seems to be not straightforward as [moving to v2 in Go is quite complicated](https://go.dev/doc/modules/major-version). We have several modules and we may take the opportunity to move to [Go workpsaces](https://go.dev/doc/tutorial/workspaces).


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-k] squakez commented on issue #4086: Nightly release fail after 2.0

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4086:
URL: https://github.com/apache/camel-k/issues/4086#issuecomment-1449545000

   TestKameletClasspathLoading fails in v1.12 branch


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-k] squakez closed issue #4086: Nightly release fail after 2.0

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez closed issue #4086: Nightly release fail after 2.0
URL: https://github.com/apache/camel-k/issues/4086


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-k] squakez commented on issue #4086: Nightly release fail after 2.0

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4086:
URL: https://github.com/apache/camel-k/issues/4086#issuecomment-1453136270

   - [ ] main branch broken because issues with moving to v2
   - [ ] release 1.12 branch broken because TestKameletClasspathLoading check error
   - [ ] release 1.10 branch broken because Health and Jolokia trait errors


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-k] claudio4j commented on issue #4086: Nightly release fail after 2.0

Posted by "claudio4j (via GitHub)" <gi...@apache.org>.
claudio4j commented on issue #4086:
URL: https://github.com/apache/camel-k/issues/4086#issuecomment-1458931074

   The 1.10.x e2e jolokia test is failing because the of the [jolokia trait change](https://github.com/apache/camel-k/pull/4018) is present in 1.10.x branch, and the [accompanying change in camel-k-runtime](https://github.com/apache/camel-k-runtime/pull/964)  must be released as 1.15.3, which I already requested in camel dev mailing list.
   Note that camel-k 1.10.4 users are not affected, since the camel-k change was commited after 1.10.4 release.


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-k] squakez commented on issue #4086: Nightly release fail after 2.0

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4086:
URL: https://github.com/apache/camel-k/issues/4086#issuecomment-1456281641

   @claudio4j nightly releases smoke tests are failing in `release-1.10.x`: https://github.com/apache/camel-k/actions/runs/4338772318/jobs/7575742188 I think it would be enough to run the common test to reproduce.


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-k] claudio4j commented on issue #4086: Nightly release fail after 2.0

Posted by "claudio4j (via GitHub)" <gi...@apache.org>.
claudio4j commented on issue #4086:
URL: https://github.com/apache/camel-k/issues/4086#issuecomment-1456277472

   @squakez how the code is changed to reproduce the problem ? Do you have a branch ?


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-k] squakez commented on issue #4086: Nightly release fail after 2.0

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4086:
URL: https://github.com/apache/camel-k/issues/4086#issuecomment-1453137043

   @claudio4j I think you are familiar with the 1.10 issue that may be related to some missing backport after Jolokia switch, do you mind having a look?


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-k] claudio4j commented on issue #4086: Nightly release fail after 2.0

Posted by "claudio4j (via GitHub)" <gi...@apache.org>.
claudio4j commented on issue #4086:
URL: https://github.com/apache/camel-k/issues/4086#issuecomment-1459004426

   > This one seems to be not straightforward as [moving to v2 in Go is quite complicated](https://go.dev/doc/modules/major-version). We have several modules and we may take the opportunity to move to [Go workpsaces](https://go.dev/doc/tutorial/workspaces).
   
   It's my understanding go workspaces may help with the `replaces` directive in `go.mod`, but the major pain is to actually accomodate the `/v2` to upgrade the version, that's a pity.
   As an example, there is `github.com/google/go-github/v32` which is a lot. I suppose they must have some script to update the version, but that seems not good to force the client users to constantly update the versions in the import section.
   


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org