Archiva

Upload (deploy) artifacts to a repository - via a web form (not using wagon)

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.1
  • Component/s: Web Interface
  • Labels:
    None
  • Number of attachments :
    1

Description

The web interface should allow to upload artifacts to the repository. For M1 one could just ftp the artifacts as neededm but with M2 having to go through the file:deploy plugin is a pain. Archiva could help a lot here

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

I think, for now, the webdav interface will be sufficient.

This shouldn't just be a file upload, but a bundle upload, which requires more work.

Show
Brett Porter added a comment - I think, for now, the webdav interface will be sufficient. This shouldn't just be a file upload, but a bundle upload, which requires more work.
Hide
Permalink
Arnaud Heritier added a comment -

It's not sufficient because to use the webdav with maven 2.0.X we have to be in a directory where maven 2 can find a pom with the webdav extension. It's really annoying for our users who are trying by default to do it from where the jar is. I agree with the need of the bundle but we can certainly begin with something really simple :

  • pom
  • pom + artifact
  • artifactId + groupId + version + type + artifact
    With this 3 cases with certainly cover the majority of the needs.
Show
Arnaud Heritier added a comment - It's not sufficient because to use the webdav with maven 2.0.X we have to be in a directory where maven 2 can find a pom with the webdav extension. It's really annoying for our users who are trying by default to do it from where the jar is. I agree with the need of the bundle but we can certainly begin with something really simple :
  • pom
  • pom + artifact
  • artifactId + groupId + version + type + artifact With this 3 cases with certainly cover the majority of the needs.
Hide
Permalink
Wendy Smoak added a comment -

Individual artifact file upload should be supported. Bundles are fine but shouldn't be required.

Show
Wendy Smoak added a comment - Individual artifact file upload should be supported. Bundles are fine but shouldn't be required.
Hide
Permalink
Wendy Smoak added a comment -

MRM-216-20070818-1935.patch has initial work to support uploading a single artifact.

Build, start the webapp with "mvn jetty:run" and go to http://localhost:9091/upload.action

You can use 'internal' as the repositoryId. Success just goes back to the same page. Look at the console for the location of the temp file and the path within the repository.

Show
Wendy Smoak added a comment - MRM-216-20070818-1935.patch has initial work to support uploading a single artifact. Build, start the webapp with "mvn jetty:run" and go to http://localhost:9091/upload.action You can use 'internal' as the repositoryId. Success just goes back to the same page. Look at the console for the location of the temp file and the path within the repository.
Hide
Permalink
Maria Odea Ching added a comment -

Will take a look at this issue and adjust the patch to the changes in the Archiva code.
Thanks Wendy!

Show
Maria Odea Ching added a comment - Will take a look at this issue and adjust the patch to the changes in the Archiva code. Thanks Wendy!
Hide
Permalink
Maria Odea Ching added a comment -

Applied the patch in archiva-trunk -r635836.
I commented out some parts in the UploadAction class which need to be modified due to the changes in the Archiva components used.

I made an initial list of what I think still needs to be done and can be improved:

  • modify the commented parts to adapt to the changes in the components (like the repository layout)
  • add 'Upload/Deploy Artifact' in the navigation menu
  • form validation
  • maybe we could have a drop-down box for the repository ids
  • include this feature in the documentation
Show
Maria Odea Ching added a comment - Applied the patch in archiva-trunk -r635836. I commented out some parts in the UploadAction class which need to be modified due to the changes in the Archiva components used. I made an initial list of what I think still needs to be done and can be improved:
  • modify the commented parts to adapt to the changes in the components (like the repository layout)
  • add 'Upload/Deploy Artifact' in the navigation menu
  • form validation
  • maybe we could have a drop-down box for the repository ids
  • include this feature in the documentation
Hide
Permalink
Wendy Smoak added a comment -

The upload feature also needs to be secured based on repository permissions.

Show
Wendy Smoak added a comment - The upload feature also needs to be secured based on repository permissions.
Hide
Permalink
Maria Odea Ching added a comment - - edited

The following has already been finished in -r636284 and -r636703:

  • 'Upload Artifact' already in navigation menu
  • dropdown box for the repository ids
  • check for write permissions before allowing deployment in repo
  • allow user to specify whether to generate a pom for the artifact (for Maven 2 artifacts)
  • update metadata file
Show
Maria Odea Ching added a comment - - edited The following has already been finished in -r636284 and -r636703:
  • 'Upload Artifact' already in navigation menu
  • dropdown box for the repository ids
  • check for write permissions before allowing deployment in repo
  • allow user to specify whether to generate a pom for the artifact (for Maven 2 artifacts)
  • update metadata file
Hide
Permalink
Maria Odea Ching added a comment -

Additional fix:

  • Added form validation and other validations in action class (-r636953)
Show
Maria Odea Ching added a comment - Additional fix:
  • Added form validation and other validations in action class (-r636953)
Hide
Permalink
Maria Odea Ching added a comment -

Additional fix:

  • generate or update checksums of metadata file (-r636957)
Show
Maria Odea Ching added a comment - Additional fix:
  • generate or update checksums of metadata file (-r636957)
Hide
Permalink
Maria Odea Ching added a comment -

Added instructions on how to deploy an artifact via the web UI form in archiva-docs (-r636970)

Show
Maria Odea Ching added a comment - Added instructions on how to deploy an artifact via the web UI form in archiva-docs (-r636970)

People

Vote (11)
Watch (9)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.