Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move to Gradle, fix naming, publish to my maven repo #3

Closed
wants to merge 10 commits into from
Closed

Move to Gradle, fix naming, publish to my maven repo #3

wants to merge 10 commits into from

Conversation

apatrida
Copy link

Use what you want from this, but did some cleaning and standardized this library so it is useful for others.

JetBrains needs to use maven or gradle builds, not everyone wants to build from the IDE every library nor has automation for Intellij IDEA based builds. Also, if you use the gradle Pride plugin (from Prezi) you can develop multiple repositories side-by-side without problems treating them as one big project if you want. Research these gradle plugins: propdeps, pride ... and you won't have gradle complaints :-)

In Gradle use pride plugin for developing multiple libraries side-by-side when from seperate repos (https://github.com/prezi/pride)
In Gradle use propdeps plugin for provided and optional scopes (https://github.com/spring-projects/gradle-plugins/tree/master/propdeps-plugin)
Moved kotlin.* to kotlinx.* so name space is clearer.
Moved some files to correct directories.
Moved files to maven standard format directories
Added publishing to Collokia open-source repository (until someone publishes this at JetBrains)
Set Kotlin version to M10 version 0.10.4
Set version number to match Kotlin version number + -SNAPSHOT
@shafirov
Copy link
Contributor

Sorry, these mostly look obsolete by now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants