Closed afloarea closed 1 year ago
Merged all submitted PR's @afloarea
@vietj I have raised PRs for most of the approved names.
The ones missing are for kotlin. I have a question about that: should I only add for kotlin lang and coroutines? or should I wait for the kotlin.gen one as well. Also, what about the vertx-kotlin-compiler? I did not add it to the table but I noticed it in the repository.
Also, the vertx-codegen was a bit different than the others because it's using the assembly plugin so I did not use the parent pom there (FYI).
Apart from these, I believe there are no other approved names, only postponed and marked as 'under discussion' or 'Pending'.
for kotlin I think for now indeed we only add kotlin lang and coroutines indeed - I merged all open PR's
kotlin done
@vietj since all the approved names have merged PRs, what's next? I assume this issue will remain open until the postponed/under discussion names are resolved too, right?
Also, if you want, I could also have a look at merging the vertx-sql-common into vertx-jdbc-client.
for sql-common, I will have a look soon.
besides, I think what we need now is to capture the current state in a wiki page and write some documentation that defines the expectations and possibly at some point we need an how-to with JPMS for Vert.x 4 using automatic module names (https://how-to.vertx.io) that could be based on 4.0.0-milestone5 (cc @jponge)
I will create a wiki page with the current names soon I think in the vertx wiki
Here is the wiki page https://github.com/vert-x3/wiki/wiki/JPMS
I will close this issue for Vert.x 4
@vietj I've just noticed that as we missed vertx-bridge-common
in web a jpms application will fail to build if it attempts to configure the eventbus sockjs bridge as the classes are not made public.
I've re-open it because we faced a issue with:
https://github.com/vert-x3/vertx-bridge-common/pull/6
Can we settle on a name for it?
io.vertx.bridge.common
or io.vertx.eventbus.bridge.common
?
Is there any information on the status of the rxjava packages? They're listed as 'postponed' but I can't find any more information on why or if that will be resolved?
I don't remember why we didn't do it for rxjava
I'd like to remember the reason and get the context
rather
On Tue, Feb 28, 2023 at 8:02 PM Adrian Floarea @.***> wrote:
@vietj https://github.com/vietj Do you think it is worth adding automatic module names for the newer projects? I can raise some PRs if so.
- Web Proxy[Tech Preview] (vertx-web-proxy) -> io.verx.web.proxy
- URI Template[Tech Preview] (vertx-uri-template) -> io.vertx.uri.template
- Json Schema[Tech Preview] (vertx-json-schema) -> io.vertx.json.schema
- Http Proxy[Tech Preview] (vertx-http-proxy) -> io.vertx.http.proxy
Regarding rxjava, I unfortunately do not remember why it was postponed.
— Reply to this email directly, view it on GitHub https://github.com/vert-x3/issues/issues/524#issuecomment-1448706053, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABXDCWEN6NSANIYSF2KWM3WZZDVHANCNFSM4MF7SADQ . You are receiving this because you were mentioned.Message ID: @.***>
@afloarea can you provide PR soon ? we will release 4.4 tomorrow
we should also have io.vertx.web.openapi.router
I added Todo to the initial list in the issue.
I'm closing this issue, I moved the content to the vertx wiki https://github.com/eclipse-vertx/vert.x/wiki/Automatic-Module-Names
Actually I've done them myself for 4.4 as it was o the critical path of the release.
On Tue, Feb 28, 2023 at 10:02 PM Julien Viet @.***> wrote:
rather
- io.vertx.web.proxy
- io.vertx.uritemplate
- io.vertx.jsonschema
- io.vertx.httpproxy
On Tue, Feb 28, 2023 at 8:02 PM Adrian Floarea @.***> wrote:
@vietj https://github.com/vietj Do you think it is worth adding automatic module names for the newer projects? I can raise some PRs if so.
- Web Proxy[Tech Preview] (vertx-web-proxy) -> io.verx.web.proxy
- URI Template[Tech Preview] (vertx-uri-template) -> io.vertx.uri.template
- Json Schema[Tech Preview] (vertx-json-schema) -> io.vertx.json.schema
- Http Proxy[Tech Preview] (vertx-http-proxy) -> io.vertx.http.proxy
Regarding rxjava, I unfortunately do not remember why it was postponed.
— Reply to this email directly, view it on GitHub https://github.com/vert-x3/issues/issues/524#issuecomment-1448706053, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABXDCWEN6NSANIYSF2KWM3WZZDVHANCNFSM4MF7SADQ . You are receiving this because you were mentioned.Message ID: @.***>
Feature Description
Provide Automatic-Module-Name attribute in MANIFEST.MF file.
Use cases
Provides a reliable module name, instead of using the name derived from the JAR file, without having to target Java 9+ and/or use module-info java/class file. This can be used until there is a module-info file.
Contribution
If this feature request were to be approved I would be happy to work on it.
I believe that this change would require some additional configuration in the pom.xml maven jar plugin, for example:
Naming Scheme
When choosing module names, these rules should be taken into consideration.
Table of automatic module names and their status:
Notes:
-
,..
or Java keywords, as this article suggests.Core
Web
Data access
Reactive SQL clients
Reactive
Reactive Extensions
Microservices
Vertx Config
Vertx Service Discovery
Standards
HTTTP Proxy
MQTT
Authentication and Authorisation
Messaging
Integration
JCA Adaptor
Event Bus Bridge
Devops
Tracing
Testing
Clustering
Services
gRPC
Internal Magic
Languages
Kotlin
Scala