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 Deploy Source Set for Smart Contract Projects
See original GitHub issueA typical Java contract project consists of a main and test source set. Contract code goes into main and test code into test. These source sets are standard for any Java project. For a smart contract project, a third source set - deploy - would be convenient. That source set contains all code for deployment on private, test and main net. The IntelliJ IDE can pick up configured source sets from the Gradle build tool and integrate them in the UI and IDE workflows. We could add the deploy source set via the already existing neow3j Gradle plugin.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sure, no worries. Let’s keep it in mind for July. 🙏
Thinking about it again: The source set should no be called
deploybecause it will will probably contain other code that is not deployment related, e.g., invocation scripts that handle contract invocations. What would be a good name for such a source set?