Closed bmuschko closed 12 years ago
well. it's mostly up to you. it's your baby ;)
I don't prefer huge multiprojects Git repositories. In fact, I would prefer split gaelyk itself to separate ones so I'm against the migration :)
@codeconsole, @glaforge what do you say?
What would you like to split in Gaelyk?
I personally would prefer the group ID org.gradle.api.plugins
as it would keep all my Gradle plugins in a central place. In the long run I'd imagine that Gradleware will propose a common group ID once they set up their central repository for plugins. I don't like them to be scattered all over the place.
@glaforge just personal feelings :-) I just like to have one project=one repo (gaelyk-core, gaelyk-template-project, gaelyk-website). for example if we have template project as separate repo, people could use just git clone to always get the latest one instead of downloading the archive file.
@bmuschko so just do it :-) sounds 100% reasonable :-)
I guess at some point we could create a Gaelyk github org? And then we split the project there across different repos, and we could also host Gaelyk plugins there. We can discuss that on the google group once we've released 1.2.
@glaforge +1 Gaelyk GitHub org
@musketyr Added configuration. Feel free to add your email address to the POM configuration.
@bmuschko done
It's up on Maven Central.
The plugin should be accessible on Maven Central. For that reason prepare the Gradle build file to sign and upload the JAR/POM. We'd need to agree on a group ID for this plugin. Maybe in the future it would also make sense to fully move this plugin under the Gaelyk repository.