You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Models (+ code) are published as a jar file to a maven repository that is then consumed as a dependency in the vodml tooling of child models. This works well as maven repositories have versioning rules within them.
At the moment they are published to the org.javastro group in maven central, as that is a group I own and have permission to publish to. (Note however that all models so far will not show up in standard searches as they have been published as snapshot versions)
From an authority point of view it might be better to publish to a github hosted "packages" repository to take advantage of the inherent permissions in the github organisations. However, this makes them slightly more difficult to consume as each packages repository has to be separately configured on the client side (in contrast to the central repository being built-in)
Another alternative is to host a maven repository at https://www.ivoa.net - the difficulty there is in having a nice CI workflow
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Models (+ code) are published as a jar file to a maven repository that is then consumed as a dependency in the vodml tooling of child models. This works well as maven repositories have versioning rules within them.
At the moment they are published to the org.javastro group in maven central, as that is a group I own and have permission to publish to. (Note however that all models so far will not show up in standard searches as they have been published as snapshot versions)
From an authority point of view it might be better to publish to a github hosted "packages" repository to take advantage of the inherent permissions in the github organisations. However, this makes them slightly more difficult to consume as each packages repository has to be separately configured on the client side (in contrast to the central repository being built-in)
Another alternative is to host a maven repository at https://www.ivoa.net - the difficulty there is in having a nice CI workflow
Beta Was this translation helpful? Give feedback.
All reactions