|
part of my build process produces files in the form: <module>_package-<version>-dev.zip
I want to setup an artifactory repository to keep these packaged zip files separate from the regular ear/war/jar artifacts. Ive tried several variations of include patterns, but the zip files always go to the wrong repository. Currently I have the following virtual repositories (in order) deploy_packages prod dev everything_else The prod, dev and everything_else work fine. but the deploy_packages will not intercept deployments and store the *_package zip files like I want. The other non-virtual repositories all have the default **/* includes pattern. The deploy_packages group only has a single repository. How do i set things up so the *_package zip files go into deploy_packages repository? |
|
You cannot direct deployment requests to virtual repositories, only local ones.
So when deploying, simply point the request to the relevant storing repository (the one contained within the deploy_packages virtual, in your case). Cheers, Noam On Tue, Jan 10, 2012 at 1:55 AM, kittle <[hidden email]> wrote: part of my build process produces files in the form: ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Artifactory-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/artifactory-users |
|
Noam,
Yes i know you cant deploy to a virtual repository - Everything errors out when I try that. Im using maven to deploy to the "generic" repository 'repo': <repositories> <repository> <id>central</id> <url>http://hostname:8081/artifactory/repo/</url> ...... All the other deployments work fine. They go into the 'dev' repository as expected. Is there a way to intercept the deployment? Id rather not have to re-write things on the maven side for this one case. |
|
You can't deploy to "repo" either; it's Artifactory's global virtual repository and aggregates all configured repositories.
Cheers, Noam On Tue, Jan 10, 2012 at 8:02 PM, kittle <[hidden email]> wrote: Noam, ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Artifactory-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/artifactory-users |
|
Currently I have maven sending deployments to http://hostname:8081/artifactory/repo/ and this works as expected. remote artifacts are downloaded from maven central, local artifacts are downloaded from locally hosted repositories (dev, thirdparty, etc). Deploying to the same URL works as well - jar/ear/war files are all uploaded to the dev repository.
Without editing my maven config, I want to redirect deployment of the *_package*.zip files to my new 'package' repository. |
| Powered by Nabble | See how NAML generates this page |
