question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add documentation on how to build from source

See original GitHub issue

I’m interested in using the new functionality for signing MSI files, specifically the Gradle plugin. But since version 3.0 hasn’t been released yet (and there’s no 3.0-SNAPSHOT or similar available in public repos), I’ll have to build from source.

Unfortunately, I’m having trouble figuring out how. I’m not very familiar with Maven, so I’m unsure of the proper way to do this. I don’t see any sort of wrapper, so I installed the latest version of Maven, and tried running mvn compile, but it didn’t seem to produce a Gradle plugin. I tried going to jsign-gradle-plugin and running gradle build (again, no wrapper) and got the following error:

> Could not resolve all files for configuration ':compileClasspath'.
   > Could not find net.jsign:jsign-core:2.0.
     Searched in the following locations:
       - file:/~/.m2/repository/net/jsign/jsign-core/2.0/jsign-core-2.0.pom
     If the artifact you are trying to retrieve can be found in the repository but without metadata in 'Maven POM' format, you need to adjust the 'metadataSources { ... }' of the repository declaration.
     Required by:
         project :

I assume I’m doing something wrong, but I have no idea what. If directions on building from source could be added to either the readme or to a separate file in the root project, I would appreciate it.

Issue Analytics

  • State:open
  • Created 4 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
ebourgcommented, Jan 7, 2020

@Thunderforge the version 3.0 has just been released.

1reaction
ebourgcommented, Dec 13, 2019

Building with Maven is just a matter of typing mvn package -DskipTests at the root of the project, not in the plugin directory. You’ll need jsign-core-3.0-SNAPSHOT.jar and jsign-gradle-plugin-3.0-SNAPSHOT.jar on the classpath to use the plugin.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Writing symbol documentation in your source files
Add reference documentation to your symbols that explains how to use them. ... Alternatively, choose Product > Build Documentation to compile your ...
Read more >
How to Write a Good Documentation: Home
Best Practices for Documenting Your Project · Include a README file that contains · Allow issue tracker for others · Write an API...
Read more >
Build Your Python Project Documentation With MkDocs
In this tutorial, you'll learn how to build professional documentation for a Python package using MkDocs and mkdocstrings.
Read more >
Adding Source Code Documentation
Adding Source Code Documentation · Type a forward slash and two asterisks (/**) and press Enter. · Click the readNumberOf class to highlight...
Read more >
Publish Your Project Documentation with GitHub Pages
Create a /docs/index.md file on your repository's master branch. · Add your content and any necessary Jekyll front matter, then commit your ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found