Skip to content

[NETBEANS-5846] Minimal support of java-platfom Gradle projects. - #3293

Merged
lkishalmi merged 1 commit into
apache:masterfrom
lkishalmi:NETBEANS-5846
Nov 20, 2021
Merged

[NETBEANS-5846] Minimal support of java-platfom Gradle projects.#3293
lkishalmi merged 1 commit into
apache:masterfrom
lkishalmi:NETBEANS-5846

Conversation

@lkishalmi

Copy link
Copy Markdown
Contributor

Slightly more than just disabling the warnings on java-platform Gradle projects.
Did some testing on the weekend including the test why api and some other configurations are not showing up in the UI.
Those are the configurations the users often use. It turned out that Gradle marks those configurations as non-resolvabe (canBeResolved property is false).
So I made some adjustments to let them displayed.
Before:
image

After:
image

@neilcsmith-net

Copy link
Copy Markdown
Member

Sorry, missed this was opened against delivery as missing a milestone. Intended for 12.6? I've only given it a glance. If you think it needs to go in RC2, please feel free to merge before tomorrow.

@lkishalmi lkishalmi added this to the 12.6 milestone Nov 2, 2021
def name = it.name
def version = it.version != null ? ':' + it.version : ''
def id = group + ':' + name + version;
componentIds.add(id)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

is it OK to pass on malformed component IDs, e.g. no name or no group ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

No group, no version names are valid.


private boolean needsResolve() {
GradleBaseProject gbp = GradleBaseProject.get(project);
return !gbp.isResolved() && !gbp.hasPlugins("java-platform"); //NOI18N

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Hm, this means that if a configuration is NOT resolved , but the project does use java-platform plugin - the project as a whole ceases needing to be resolved ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Well it is about the warning badge and the tooltip. We put warning the configuration is not resolved in general.
However java-platform project can't be resolved by definition. So we do not place warning badge and unresolved config hint on the node.

@neilcsmith-net neilcsmith-net added the do not merge Don't merge this PR, it is not ready or just demonstration purposes. label Nov 3, 2021
@neilcsmith-net

Copy link
Copy Markdown
Member

I'm going to sync and trigger RC2 now, so given review in progress, please don't merge now. We'll likely have an RC3 so we can merge for that once review process complete. Thanks!

@neilcsmith-net

Copy link
Copy Markdown
Member

@sdedic @lkishalmi what's the status of review here now? Thanks!

@lkishalmi lkishalmi removed this from the 12.6 milestone Nov 8, 2021
@lkishalmi

Copy link
Copy Markdown
Contributor Author

Let's have this on early 13.0 instead. I'm going to rebase this on master.

@neilcsmith-net
neilcsmith-net changed the base branch from delivery to master November 11, 2021 18:36
@neilcsmith-net neilcsmith-net added this to the NB13 milestone Nov 11, 2021
@lkishalmi lkishalmi removed the do not merge Don't merge this PR, it is not ready or just demonstration purposes. label Nov 20, 2021
@lkishalmi

lkishalmi commented Nov 20, 2021

Copy link
Copy Markdown
Contributor Author

I'm merging this to the master, let's see how this works out

@lkishalmi
lkishalmi merged commit 224dfc0 into apache:master Nov 20, 2021
@junichi11 junichi11 added the Gradle [ci] enable "build tools" tests label Nov 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Gradle [ci] enable "build tools" tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants