Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add documentation #2

Open
helpermethod opened this issue Nov 20, 2019 · 6 comments
Open

Add documentation #2

helpermethod opened this issue Nov 20, 2019 · 6 comments

Comments

@helpermethod
Copy link
Collaborator

helpermethod commented Nov 20, 2019

  • Usage
  • Features
  • Authentication
@pwhittlesea
Copy link

Hi @helpermethod

I'm looking to help out (time permitting) as this is something I would be interested in using.

Has any start been made on this?

Do you mean code docs or are you looking at creating online documentation similar to other Maven projects? (example)

@helpermethod
Copy link
Collaborator Author

helpermethod commented Dec 12, 2019

Hi @pwhittlesea,

I'm currently a little busy with other things but will get back to the project within the next few days.

Help in any form is always welcome :)!

The doc is currently extremely lacking (basically non-existent), especially with regards to:

  • Which types of authentication are supported?
  • Which steps need to be taken to let the plugin authenticate via SSH, Authentication Tokens or Username Password?

A static site (like other Maven plugins have) which describes its goals (currently only update), basic usage etc. would also be welcome.

@pwhittlesea
Copy link

So from what I can currently gather the plug-in has 1 property which can be set:

Both the connectionUrl and developerConnectionUrl are read from the pom.xml and Maven settings in the settings.xml file will be used to configure the authentication settings to those URLs.

Is this correct?

@helpermethod
Copy link
Collaborator Author

helpermethod commented Dec 22, 2019

This this correct except one minor detail:

If the connection contains a username/password pair then that will be used for authentication.

This is to allow authentication via Personal Access Tokens which GitLab requires to be part of the URL.

For a deep dive into JGit Auth I'd recommend JGit Authentication Explained.

@pwhittlesea
Copy link

So if we were using this plug-in in GitLab CI/CD we would have a .gitlab-ci.yaml with:

mvn dependency-update-maven-plugin:update \
    -DconnectionUrl=$CI_REPOSITORY_URL?private_token=$MY_PERSONAL_TOKEN

Where:

@bmarwell
Copy link
Contributor

bmarwell commented Oct 2, 2022

There's now a help mojo for a start: #61
Site generation is also in a PR and already merged: #51

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants