Comments (12)
Certainly, as long as it's independent. I'll likely need docs on how to execute the build
from cyclonedx-gradle-plugin.
I think I covered that in the document. It's a one time thing to approve 'ownership' of the plugin's namespace.
If this is the first time the plugin has been published, the name may need to be approved by the portal maintainers. This typically takes about 12 hours during the work week. You will see on your portal user console page that your plugin is marked 'Pending approval'. After it is approved, the API credentials used to publish will 'own' the plugin name, and plugins will be available in the portal immediately after publishing.
from cyclonedx-gradle-plugin.
If there is a Maven way of adding the plugin to the plugin portal, this project accepts pull requests. However, the project will not be migrating from maven to gradle.
from cyclonedx-gradle-plugin.
However, the project will not be migrating from maven to gradle.
Hmm, while I respect your personal preference here, does that restriction really make sense from a technical perspective? To me, it feels more native to build a Gradle plugin with Gradle, and you could make use of helpers like the Java Gradle Plugin Development Plugin.
from cyclonedx-gradle-plugin.
I agree, however, this project doesn't have a maintainer that knows Gradle. If that changes in the future, I have no objection, but if the maintainer is going to continue to be myself, I need something I know how to maintain (which is not Gradle).
from cyclonedx-gradle-plugin.
would you be open to having a separate gradle build that does the portal publishing?
from cyclonedx-gradle-plugin.
see #36
from cyclonedx-gradle-plugin.
With the merge of #36, will there be an upcoming publishing of the plugin to the Gradle Plugin Portal? New version, or 1.1.1?
from cyclonedx-gradle-plugin.
When will the plugin get published to the gradle plugin portal?
from cyclonedx-gradle-plugin.
Its been published, but it doesn't seem to be automated. Received the following after a successful publish:
Publishing plugin org.cyclonedx.bom version 1.1.2
Thank you. Your new plugin org.cyclonedx.bom has been submitted for approval by Gradle engineers. The request should be processed within the next 24 hours, at which point you will be contacted via email.
Hopefully this is a one-time thing and not for every update.
from cyclonedx-gradle-plugin.
Thanks @llamahunter for all the info and quality PR.
https://plugins.gradle.org/plugin/org.cyclonedx.bom
from cyclonedx-gradle-plugin.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
from cyclonedx-gradle-plugin.
Related Issues (20)
- Add dependencies of `type=zip` to dependency-graph
- Incorrect (empty) tool entry may appear in SBOMs if project also uses a plugin which uses org.eclipse.jgit
- Metadata component is missing entries for hashes etc
- Kotlin Script, Android Support? HOT 5
- Dependencies field is incomplete for POM artifacts in sbom file HOT 2
- Gradle 8.4: org.xml.sax.SAXNotRecognizedException: Property 'http://javax.xml.XMLConstants/property/accessExternalSchema' is not recognized. HOT 5
- Version 1.8.0 and compatibility with java8 HOT 1
- Hello, I have encountered such an error, I do not know how to solve it HOT 3
- Plugin version 1.8.0 referencing version 1.7.4 in output HOT 1
- Version 1.8.0 doesn't actually produce SBOMs with 1.5 schema version HOT 1
- I made an error building the BOM table for multiple projects by using the --init-script option. I don't know what happened HOT 3
- Gradle configurations not being merged, resulting bom is made by a single random configuration
- I generated the SBOM error through init.gradle. Do you need to make any configuration changes? The error and configuration are as follows.
- Latest version 1.8.1 is not compatible with gradle 7.5.1. HOT 1
- Regex support for skipped and included configurations
- Capture Input Task Names and Extra Build Arguments in BOM
- Publish BOM files to Artifact repository with JAR file, like Maven plugin HOT 2
- Dependencies list is empty for :app module in Android project. HOT 1
- Android project: The BOM does not conform to the CycloneDX BOM standard HOT 4
- Cyclonedx version 1.7.3 causes "No signature of method: org.apache.maven.model.profile.activation.FileProfileActivator.setPathTranslator() is applicable for argument types: (org.apache.maven.model.path.DefaultPathTranslator) "
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cyclonedx-gradle-plugin.