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
If all schemas were published to a central repository, maven central for example, it'll be a help for people who try to develop editors, or for implementors.
The text was updated successfully, but these errors were encountered:
No. Well, at least, you publish artifacts ; and artifacts may be other file types than jar files. For examples, most of open-source projects publish sources and javadoc to maven. It's packaged as jar, but does not contains any .class files.
I'm not sure the way you want to do it, but when I have to publish various things to maven, I use build-helper:attach-artifact to attach additional artifacts to publish.
If you look at maven artifact definition you see standard groupId, artifactId, version, scope to define the use, and more important, type and classifier.
classifier is the role : sources / javadoc, and so on.
You may add as many artifact as you want, and (artifacts, pom, checksum) is the component.
You may also have a look at deploy:deploy-file who allows you to deploy one or many files to a remote repository, outside of a maven project. Better, it's able to generate the pom.xml file if you do not provide one. It may be useful in this case.
If all schemas were published to a central repository, maven central for example, it'll be a help for people who try to develop editors, or for implementors.
The text was updated successfully, but these errors were encountered: