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

ProcessImplementation module cleanup #7677

Merged
merged 1 commit into from
Aug 22, 2024
Merged

Conversation

mbien
Copy link
Member

@mbien mbien commented Aug 16, 2024

small cleanup while debugging #7676

  • module can use the API without reflection since build requires JDK 17 by now
  • added more info to the logger

@mbien mbien added Code cleanup Platform [ci] enable platform tests (platform/*) labels Aug 16, 2024
@mbien mbien added this to the NB24 milestone Aug 16, 2024
@mbien
Copy link
Member Author

mbien commented Aug 16, 2024

wondering what we should do with the JDK 8 version ide/extexecution.process.

It would be good if we could remove it since it won't run in current NB releases + it would also remove two (small) dependencies. Platform apps which depend on it could continue using prior releases of this module from central.

@neilcsmith-net
Copy link
Member

I would replace the code in ide/extexecution.process with the JDK 9+ code, and remove the JDK 9+ module.

@sdedic
Copy link
Member

sdedic commented Aug 17, 2024

I would replace the code in ide/extexecution.process with the JDK 9+ code, and remove the JDK 9+ module.

  • use module-auto-deps to auto-replace possible plugin dependencies to the obsolete module

@mbien mbien added ci:dev-build [ci] produce a dev-build zip artifact (7 days expiration, see link on workflow summary page) ci:all-tests [ci] enable all tests labels Aug 17, 2024
@mbien
Copy link
Member Author

mbien commented Aug 17, 2024

added another commit which:

  • moves the impl into ide/extexecution.process
  • bumps the spec version to 2.0, bumps release to 11, updates dependencies in project.xml
  • removes now redundant ide/extexecution.process.jdk9
  • adds module-auto-deps.xml

not sure yet but will probably squash before merge

Comment on lines 25 to 39
<transformations version="1.0">
<transformationgroup>
<description>Merged o.n.m.extexecution.process.jdk9 into o.n.m.extexecution.process</description>
<transformation>
<trigger-dependency type="cancel">
<module-dependency codenamebase="org.netbeans.modules.extexecution.process.jdk9"/>
</trigger-dependency>
<implies>
<result>
<module-dependency codenamebase="org.netbeans.modules.extexecution.process" spec="2.0"/>
</result>
</implies>
</transformation>
</transformationgroup>
</transformations>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i hope this is correct

Copy link
Contributor

@matthiasblaesing matthiasblaesing Aug 18, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At least looks sane to me, XML validator is happy and the file is registered in the SystemFileSystem.

@mbien mbien added Upgrade JDK Upgrade to the JDK requirements of a module. Need Squashing labels Aug 17, 2024
Copy link
Contributor

@matthiasblaesing matthiasblaesing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks sane to me. Minimal comment inline.

@@ -2,5 +2,5 @@ Manifest-Version: 1.0
AutoUpdate-Show-In-Client: false
OpenIDE-Module: org.netbeans.modules.extexecution.process
OpenIDE-Module-Localizing-Bundle: org/netbeans/modules/extexecution/process/resources/Bundle.properties
OpenIDE-Module-Specification-Version: 1.53
OpenIDE-Module-Specification-Version: 2.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have mixed feelings here. On the one hand there is a massive change in the implementation (dependency bump, drop of native implementation), on the other hand the API did not change in any way. This is still marked a compatible change (same major release version), but to me the specification major bump implies different. I would just count it up to 1.54.

Copy link
Member Author

@mbien mbien Aug 18, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this might sound weird, but i did actually use 1.54 first but then I thought @matthiasblaesing will probably suggest to go to 2.x just to be sure, since it bumps the lang level, the position in the lookup and changes the impl at the same time.

I do think staying on 1.54 should be probably fine too. I have to squash anyway so i can change it if everyone is ok with 1.54.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

going to change it to 1.54 and squash, planning to merge once green

 - module can use the API without reflection since build requires JDK
   17 by now (impl itself was not altered)
 - added some logging

remove now redundant module

 - merge ide/extexecution.process.jdk9 into ide/extexecution.process
 - module-auto-deps.xml should delegate at build time to use the right
   module
@mbien mbien force-pushed the proc-module-cleanup branch 2 times, most recently from 3f435c2 to ffcc646 Compare August 22, 2024 04:51
@mbien
Copy link
Member Author

mbien commented Aug 22, 2024

@mbien mbien merged commit 6c6beed into apache:master Aug 22, 2024
40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci:all-tests [ci] enable all tests ci:dev-build [ci] produce a dev-build zip artifact (7 days expiration, see link on workflow summary page) Code cleanup Platform [ci] enable platform tests (platform/*) Upgrade JDK Upgrade to the JDK requirements of a module.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants