Open wildone opened 1 year ago
Are you able to update pipeline to push maven release artifacts into a branch so that we can use this in project without any setup ok tokens.
There is a guide on how to do this https://gist.github.com/cleberjamaral/6c9b0a615e51e26c94ffe407a641f531
Currently, if we add this to our project it needs auth:
<repositories> <repository> <id>github-neva-dev-felix-search-webconsole-plugin</id> <url>https://maven.pkg.github.com/neva-dev/felix-search-webconsole-plugin</url> <snapshots> <enabled>true</enabled> </snapshots> </repository> </repositories> <distributionManagement> <repository> <id>github-neva-dev-felix-search-webconsole-plugin</id> <url>https://maven.pkg.github.com/neva-dev/felix-search-webconsole-plugin</url> </repository> </distributionManagement>
It would streamline adoption to do this without auth, as updating setting.xml is a bit 1990's.
After this update we can just add this to our POM without any other hidden updates.
<repositories> <repository> <id>github-neva-dev-felix-search-webconsole-plugin</id> <url>https://github.com/neva-dev/felix-search-webconsole-plugin/raw/maven2</url> <snapshots> <enabled>true</enabled> </snapshots> </repository> </repositories> <distributionManagement> <repository> <id>github-neva-dev-felix-search-webconsole-plugin</id> <url>https://github.com/neva-dev/felix-search-webconsole-plugin/raw/maven2</url> </repository> </distributionManagement>
this approach looks quite hack'ish ;) I will consider that; thanks
Are you able to update pipeline to push maven release artifacts into a branch so that we can use this in project without any setup ok tokens.
There is a guide on how to do this https://gist.github.com/cleberjamaral/6c9b0a615e51e26c94ffe407a641f531
Currently, if we add this to our project it needs auth:
It would streamline adoption to do this without auth, as updating setting.xml is a bit 1990's.
After this update we can just add this to our POM without any other hidden updates.