search

micha149 / gulp-maven-deploy

Gulp wrapper for the maven-deploy plugin
MIT License
12 stars 11 forks source link

How to deal with side artifacts? #17

Open micha149 opened 8 years ago

micha149 commented 8 years ago

I have two files in a stream. The first is the main package. The second one is a zip file which contains the api documentation. It will be marked with a classifier called apidoc. My expected result is:

com.example
└── my-artifact-id
    ├── 0.3.0
    │   ├── my-artifact-id-0.3.0.zip
    │   ├── my-artifact-id-0.3.0.zip.md5
    │   ├── my-artifact-id-0.3.0.zip.sha1
    │   ├── my-artifact-id-0.3.0-apidoc.zip
    │   ├── my-artifact-id-0.3.0-apidoc.zip.md5
    │   └── my-artifact-id-0.3.0-apidoc.zip.sha1
    ├── 0.2.0
    │   └── ...
    └── 0.1.0
        └── ...

Was it the right choice to use the filename as the artifactId? How can we handle classifiers and multiple files per deploy?

micha149 commented 8 years ago

I think this issue can only be done with a huge change on this project. This might cause that we can't use maven-deploy any more. I don't want to block the 1.0.0 release, so I created a new v2.0.0 Milestone where we can implement this new behavior.