gradle-plugins | This project contains a set of useful gradle plugins | Plugin library

I'm trying to offload build logic into a gradle init script, which gets included in a custom gradle wrapper. It seems promising. One of the things I need to do is to apply the artifactory plugin prior to configuring it, while the following code works fine in build.gradle, it fails to find the plugin when the code is shifted into an init script.

build.gradle:

I have an offline (no internet) eclipse install that I would like to install some plugins from the eclipse marketplace. It used to be that the marketplace site would provide link to download the 'update site' (Downloading Eclipse plug-in from Eclipse Marketplace for offline usage), but this is no longer the case. The 'install' and 'download' buttons in the marketplace are just a reference urls that only eclipse seems to understand what to do with.

The few recent examples that I have been able to find involve downloading the update sites from non-eclipse sites:

• Installing Groovy and Gradle plugins in Eclipse 4.17 (2020-09) offline
• Install sonarlint plugin in eclipse offline
• How to offline install of Spring Boot Tools Plugin into Eclipse IDE?
• How to Install ADT and CDT plugins for Eclipse Neon in offline mode

Is there not a way to get the download url from the marketplace?

Alternatively some posts talk about mirroring the p2 repo. Downloading a full repo isn't optimal (I just want a few plugins), but I can't even find up-to-date instructions for that either.

I tried to convert the Groovy script from shadow plugin's guide

Since upgrading from Gradle 6.7.1 to 7.0 (which may be a red herring), Black Duck scans of my Gradle project now fail.

Here is the error message:

In the last couple of days, I have gone through some unmet dependencies issues while upgrading. I tried to install those packages separately but couldn't come up with a solution.

I know one solution that is to remove the antivirus from the system. But I'm not permitted for me to remove the antivirus. I want another solution without removing anti-virus from the system.

It shows while unpacking the package:

In the spring-security project, in the build.gradle file, the following plugins are made available:

I have a Spring Boot + Kotlin + Gradle project. I'd like to create a small library for my use-cases. This library should use AOP to remove some cross cutting concerns I observed.

Therefore I started adding these two dependencies to my gradle build file.

build.gradle.kts

I have whittled down my problem to a very simple project that declares a module dependency on a module artifact served from my client's artifactory instance. This is working fine with 5.3.1. As can be seen from the logs below there is a line which indicates DefaultExternalResourceArtifactResolver is loading the associated .jar for this dependency from my maven2 repo (see: {{{ A }}})

However, when I attempted to upgrade to Gradle 6.5, I get the message

I have two situations I need a checkstyle check for. Let's say I have a bunch of objects with the annotation @BusinessLogic. I want to do a first pass through all *.java files creating a Set with the full classnames of these objects. Let's say ONE of the classes here is MyBusinessLogic. NEXT, and as part of a custom checkstyle checker, I want to go through and fail the build if there is any lines of code that say "new MyBusinessLogic()" in any of the code. We want to force DI when objects are annotated with @BusinessLogic. Is this possible with checkstyle? I am not sure checkstyle does a dual pass.

Another option I am considering is some gradle plugin perhaps that scans all java files and writes to a file the list of classes annotated with @BusinessLogic and then running checkstyle after that where my checker reads in the file?

My next situation is I have a library delivered as a jar so in that jar, I also have classes annotated with @BusinessLogic and I need to make sure those are also added to my list of classes that should not be newed up manually and only created with dependency injection.

Follow up question from the previous question here after reading through checkstyle docs:

How to enforce this pattern via gradle plugins?

thanks, Dean