2007/8/23, Stephane Nicoll <[EMAIL PROTECTED]>: > > Well, you hit part of the actual problem we're facing as well. > > The documentation referred by your link is wrong. There's a flag that > allows to include the metadata in order for the repository to be used > as a standard remote repository
<ignore>but that is the official page of the plugin! I would expect some accurate information here. </ignore> ok, thank you for that information :) <snip> > includeMetadata If set to true, this property will trigger the > creation of repository metadata which will allow the repository to be > used as a functional remote repository. The default value is false > <snip> > > Now the actual problem is to deploy this to your remote repository. > The first time will work but for subsequent deployments, you'll need > to merge the metadata and there's no tool out there that is stable > enough to do that. We're working on the staging plugin and I do hope > we'll find a solution. If you want to hack a bit, check the > reposiorytools plugin in the mojo sandbox. For simple use cases, it > will work. My open source project is very simple with only a few dependencies. I could live with fact that I wipe out the complete remote repository and upload all the dependencies again for now. So if I let the assembly plugin generate that zip file, unzip that file onto a directory that the site plugin will upload (target/site or target/staging), I should get a remote repository on my website. Is this correct? thank you for your help, regards, Wim Cheers, > Stéphane > > On 8/23/07, Wim Deblauwe <[EMAIL PROTECTED]> wrote: > > But according to the documentation of the assembly plugin[1]: "This > example > > demonstrates the creation of repository artifacts in an assembly so that > the > > archive can easily be used to update an *internal* repository with the > > artifacts used by your project." > > > > I want to create a directory structure that I can upload to sourceforge > and > > serve as a remote repository or is it the same structure? > > > > regards, > > > > Wim > > > > [1] > > > http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/using-repositories.html > > > > > > 2007/8/23, Stephane Nicoll <[EMAIL PROTECTED]>: > > > > > > You gather the dependencies you need in a project (either directly or > > > transitively) and you add a repository section in your assembly > > > descriptor, something like that: > > > > > > <repositories> > > > <repository> > > > > > > > <outputDirectory>build-integration/repository</outputDirectory> > > > <scope>test</scope> > > > </repository> > > > </repositories> > > > > > > Regards from a belgian fellow, > > > > > > Stéphane > > > > > > On 8/23/07, Wim Deblauwe <[EMAIL PROTECTED]> wrote: > > > > And how do you do this? > > > > > > > > 2007/8/23, Stephane Nicoll <[EMAIL PROTECTED]>: > > > > > > > > > > Hi, > > > > > > > > > > Yes, I'm doing this for one of my project but it's a bit messy > with > > > > > snapshots. Regardnig plugins, it's not possible as far as I know. > Only > > > > > the project's dependencies can be included in a repository. > > > > > > > > > > HTH, > > > > > Stéphane > > > > > > > > > > On 8/22/07, Wim Deblauwe <[EMAIL PROTECTED]> wrote: > > > > > > Hi, > > > > > > > > > > > > is it possible to use the maven assembly plugin to create a > remote > > > > > > repository? I have some custom artifacts that my build needs. I > > > don't > > > > > want > > > > > > to force my users to have to manually do 'mvn > install:install-file' > > > for > > > > > each > > > > > > of those. I have seen you can create a local repository which > you > > > need > > > > > to > > > > > > unzip then, but it would be easier if they can just include a > new > > > > > repository > > > > > > url. My project is an open-source sourceforge project, so I can > only > > > > > upload > > > > > > static files and not install something like archiva or > proximity. > > > > > > > > > > > > 1) Is this possible? > > > > > > > > > > > > 2) Is it possible to also include the plugin versions? I'm using > > > some > > > > > > SNAPSHOT versions of plugins, but I can't wait forever to > release, > > > so I > > > > > > would like to give those a custom version and make them > available. > > > > > > > > > > > > regards, > > > > > > > > > > > > Wim > > > > > > > > > > > > -- > > > > > > Vigilog - an open source log file viewer: > > > http://vigilog.sourceforge.net > > > > > > Blog: http://www.jroller.com/page/Fester > > > > > > > > > > > > > > > > > > > > > -- > > > > > Large Systems Suck: This rule is 100% transitive. If you build > one, > > > > > you suck" -- S.Yegge > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > -- > > > > Vigilog - an open source log file viewer: > http://vigilog.sourceforge.net > > > > Blog: http://www.jroller.com/page/Fester > > > > > > > > > > > > > -- > > > Large Systems Suck: This rule is 100% transitive. If you build one, > > > you suck" -- S.Yegge > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > Vigilog - an open source log file viewer: http://vigilog.sourceforge.net > > Blog: http://www.jroller.com/page/Fester > > > > > -- > Large Systems Suck: This rule is 100% transitive. If you build one, > you suck" -- S.Yegge > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Vigilog - an open source log file viewer: http://vigilog.sourceforge.net Blog: http://www.jroller.com/page/Fester
