No, this wouldn't work at present. Can you describe the use case rather than your proposed solution? Perhaps there is an alternative. Many people use a tarball that is unpacked after downloading.
Some of the components documentation is under the lifecycle guide in the web site. - Brett On 11/3/05, Benoit Mangez <[EMAIL PROTECTED]> wrote: > Dear All, > > I would like to produce a new kind of artifact which will be a > directory. And I've some questions about that. > > 1) Is it possible for an artifact to be a directory ? > 2) Is it possible to install such kind of artifact in the repository ? > (the default install goal is not very happy with a > directory-artifact... should I write an other install goal ?) > 3) A jar will contains classes in a sub-directory of my > artifact-directory. And this jar must be added to the classpath when > the artifact is included in dependencies of other artifacts. How should > I do this ? > > I found the META-INF/plexus/components.xml file. I see that it is > possible to define an alternate LifecycleMapping (but I think that I > only need a specific configuration of the DefaultLyfecycleMapping) and > an alternate ArtifactHandler. > What is an ArtifactHandler ? > And more generally is there a secret place where I can find > informations about components that can be re-define in this file ? > > Thanks. > > Benoit Mangez > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
