crx-maven-plugin | Maven plugin to package a Chrome extension | Build Tool library
kandi X-RAY | crx-maven-plugin Summary
kandi X-RAY | crx-maven-plugin Summary
The [CRX Maven Plugin] is a [Maven] plugin that collects all the resources of a [Google Chrome Extensions] and packages them into a signed [CRX] archive.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Creates the CRX file
- Build a list of filter wrappers
- Splits the comma - separated list of directories and exclusion rules
- Returns true if the file should be filtered
- Copies files from a source directory to a destination directory
- Generate a ZIP file for the source directory and zip file
- Creates a ZIP file containing the resources
- Attempts to convert an RSA private key to a public key pair
- Read the public key pair from a PEM file
- Loads the crX archive
- Get the contents of the CRX archive
- Get the public key
- Get the signature for the contents of the CRX archive
- Reads a CRX archive from a file
- Read a 32 - bit integer from the stream
- Generates the CRX file
- Writes a 32 - bit integer to the stream
- Validates the signature using the public key algorithm
- Generates a signature for a byte array
crx-maven-plugin Key Features
crx-maven-plugin Examples and Code Snippets
Community Discussions
Trending Discussions on crx-maven-plugin
QUESTION
I am building a self-hosted chromium extension for Edge and Chrome. So far I got a nice working CI pipeline using maven with this plugin (https://github.com/bmatthews68/crx-maven-plugin) and I managed to automate the versioning, packaging and signing of the .crx file, and upload to Nexus repository without much hassle (our intent was to point the upload URL to Nexus releases using group policies to get the extension deployed to users).
But we have found that the plugin is a bit outdated and uses crx2 format for the extension packaging. Support for crx2 was dropped a while ago (chromium v75 or so), and current browser versions require crx3 or won't install the extension.
Seems like the only reliable way to package a crx3 extension right now is using the chrome executable itself, but it does not look like the best idea for a CI pipeline :-/
Any suggestion is welcome!
...ANSWER
Answered 2021-Nov-15 at 08:43As you mentioned, CRX2
was deprecated in Chrome 75 two years ago, there are some issues with CRX₂ and its support was completely removed in Chrome 78. Because all extensions must move to the CRX3 format!
I'm not sure how you built it with maven, maybe it was a script or something. In this case, you may need to modify your script appropriately, or find some reference documents that support CRX3
format related to the tools you are using to build the extension.
Otherwise you have to package it in crx3 format. Refer to this document.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install crx-maven-plugin
You can use crx-maven-plugin like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the crx-maven-plugin component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page