search

bndtools / workspace

A starter Bnd workspace with plain OSGi dependencies and a Bnd Gradle build.
http://bndtools.org
Apache License 2.0
7 stars 13 forks source link

Prepare for contribution to Bndtools #7

Closed timothyjward closed 6 years ago

timothyjward commented 6 years ago

Contributed by Paremus based on customer sponsored work. Intermediate commits have been squashed to simplify the merge and review

Signed-off-by: Tim Ward timothyjward@apache.org

bjhargrave commented 6 years ago

Why are we checking a binary in here? How will someone update the template?

timothyjward commented 6 years ago

Why are we checking a binary in here?

This is an updated version of the binary that was there before.

How will someone update the template?

My preferred option is that we create a new project.templates repo which will hold the source code for these project templates, and that this can be released/tagged as necessary. The backup option is that we merge the updates for this version into the bndtools repo but this will:

a) Limit how often we can release the project templates b) Perpetuate the confusion about whether templates need to be part of Bndtools (which they don't) c) Force updated releases of the templates even if they don't change between Bndtools releases

Whichever option we choose for source control, the templates are "released" into the workspace template using a PR, i.e. the same as the current process.