Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename Maven module to avoid confusion with artifact id #1677

Open
sbernard31 opened this issue Nov 21, 2024 · 3 comments
Open

Rename Maven module to avoid confusion with artifact id #1677

sbernard31 opened this issue Nov 21, 2024 · 3 comments
Labels
enhancement Improvement of existing features

Comments

@sbernard31
Copy link
Contributor

See #1670 (comment) for more details.

@sbernard31 sbernard31 added the enhancement Improvement of existing features label Nov 21, 2024
@sbernard31
Copy link
Contributor Author

Current Names are :

[INFO] leshan ............................................. SUCCESS [  0.905 s]
[INFO] leshan-shared build config ......................... SUCCESS [  0.043 s]
[INFO] leshan-shared library build config ................. SUCCESS [  0.305 s]
[INFO] leshan-core ........................................ SUCCESS [  0.082 s]
[INFO] leshan-client ...................................... SUCCESS [  0.019 s]
[INFO] leshan-servers-shared .............................. SUCCESS [  0.011 s]
[INFO] leshan-bsserver .................................... SUCCESS [  0.015 s]
[INFO] leshan-server ...................................... SUCCESS [  0.013 s]
[INFO] leshan-server redis ................................ SUCCESS [  0.022 s]
[INFO] leshan-transport-californium-shared ................ SUCCESS [  0.027 s]
[INFO] leshan-transport-californium-bsserver-coap ......... SUCCESS [  0.029 s]
[INFO] leshan-transport-californium-client-coap ........... SUCCESS [  0.010 s]
[INFO] leshan-transport-californium-server-coap ........... SUCCESS [  0.011 s]
[INFO] leshan-transport-californium-shared oscore ......... SUCCESS [  0.015 s]
[INFO] leshan-transport-californium-bsserver-coap oscore .. SUCCESS [  0.012 s]
[INFO] leshan-transport-californium-client-coap oscore .... SUCCESS [  0.017 s]
[INFO] leshan-transport-californium-server-coap oscore .... SUCCESS [  0.010 s]
[INFO] leshan-transport-javacoap-shared ................... SUCCESS [  0.008 s]
[INFO] leshan-transport-javacoap-server-coap .............. SUCCESS [  0.009 s]
[INFO] leshan-transport-javacoap-client-coap .............. SUCCESS [  0.061 s]
[INFO] leshan-transport-javacoap-server-coap+tcp .......... SUCCESS [  0.037 s]
[INFO] leshan-transport-javacoap-client-coap+tcp .......... SUCCESS [  0.008 s]
[INFO] leshan-integration tests ........................... SUCCESS [  0.072 s]
[INFO] leshan-shared demo build config .................... SUCCESS [  0.005 s]
[INFO] leshan-demo-shared ................................. SUCCESS [  0.018 s]
[INFO] leshan-demo-client ................................. SUCCESS [  0.010 s]
[INFO] leshan-demo-servers shared ......................... SUCCESS [  0.099 s]
[INFO] leshan-demo-server ................................. SUCCESS [  0.043 s]
[INFO] leshan-demo-bsserver ............................... SUCCESS [  0.018 s]

I agree that we probably should avoid that artifact name looks too much to artifact id
But I would like to keep how readability of each group of module (demo/transport Californium / Transport javacoap / ...)

So I propose something like :

[INFO] Leshan ............................................. SUCCESS [  0.905 s]
[INFO] Leshan shared build config ......................... SUCCESS [  0.043 s]
[INFO] Leshan shared library build config ................. SUCCESS [  0.305 s]
[INFO] Leshan core ........................................ SUCCESS [  0.082 s]
[INFO] Leshan Client ...................................... SUCCESS [  0.019 s]
[INFO] Leshan servers shared .............................. SUCCESS [  0.011 s]
[INFO] Leshan BS Server ................................... SUCCESS [  0.015 s]
[INFO] Leshan Server ...................................... SUCCESS [  0.013 s]
[INFO] Leshan Server Redis ................................ SUCCESS [  0.022 s]
[INFO] Leshan Transport Californium shared ................ SUCCESS [  0.027 s]
[INFO] Leshan Transport Californium BS Server coap ........ SUCCESS [  0.029 s]
[INFO] Leshan Transport Californium Client coap ........... SUCCESS [  0.010 s]
[INFO] Leshan Transport Californium Server coap ........... SUCCESS [  0.011 s]
[INFO] Leshan Transport Californium shared oscore ......... SUCCESS [  0.015 s]
[INFO] Leshan Transport Californium BS Server coap oscore . SUCCESS [  0.012 s]
[INFO] Leshan Transport Californium Client coap oscore .... SUCCESS [  0.017 s]
[INFO] Leshan Transport Californium Server coap oscore .... SUCCESS [  0.010 s]
[INFO] Leshan Transport javacoap shared ................... SUCCESS [  0.008 s]
[INFO] Leshan Transport javacoap Server coap .............. SUCCESS [  0.009 s]
[INFO] Leshan Transport javacoap Client coap .............. SUCCESS [  0.061 s]
[INFO] Leshan Transport javacoap Server coap+tcp .......... SUCCESS [  0.037 s]
[INFO] Leshan Transport javacoap Client coap+tcp .......... SUCCESS [  0.008 s]
[INFO] Leshan Integration Tests ........................... SUCCESS [  0.072 s]
[INFO] Leshan shared demo build config .................... SUCCESS [  0.005 s]
[INFO] Leshan Demo shared ................................. SUCCESS [  0.018 s]
[INFO] Leshan Demo Client ................................. SUCCESS [  0.010 s]
[INFO] Leshan Demo servers shared ......................... SUCCESS [  0.099 s]
[INFO] Leshan Demo Server ................................. SUCCESS [  0.043 s]
[INFO] Leshan Demo BS Server .............................. SUCCESS [  0.018 s]

@jvermillard let me know if this is OK ? (Feel free to propose something else)

@jvermillard
Copy link
Contributor

looks good, thanks!

@sbernard31
Copy link
Contributor Author

it should be done by : #1687

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement of existing features
Projects
None yet
Development

No branches or pull requests

2 participants