You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Benoit Mangez <be...@denali.be> on 2005/11/03 09:56:59 UTC
Producing directory artifacts
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Producing directory artifacts
Posted by Brett Porter <br...@gmail.com>.
Does WebObjects have any file format for distributing these files together?
You can use the assembly plugin (there are a few docs on the site
about this now) to create a tarball/zip file from this structure,
deploy it to the repo, and later depend on it. I believe the assembly
plugin can also unpack it when you depend on it.
Regards,
Brett
On 11/4/05, Benoit Mangez <be...@denali.be> wrote:
> Hello,
>
> Here is more precisely what I need:
>
> We are working with WebObjects frameworks with the following structure:
>
> FrameworkName.framework
> |
> - Resources
> | |
> | - Java
> | |
> | - frameworkname.jar
> | - ... (resources: files and directories fitered according filter A)
> - WebServerResources
> |
> - ... (resources: files and directories fitered according filter B)
>
> A framework may depends on a set of other frameworks (and jar files of
> those frameworks must be in the classpath).
>
> I already have a package phase that produce this structure. (it works
> for frameworks that doesn't depends on other frameworks)
>
> A tarball may be a good solution to achieve the package phase. Is there
> any example of tarball somewhere ?
>
> Le 3 nov. 05, à 22:54, Brett Porter a écrit :
>
> > 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 <be...@denali.be> 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: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> Benoit Mangez
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Producing directory artifacts
Posted by Benoit Mangez <be...@denali.be>.
Hello,
Here is more precisely what I need:
We are working with WebObjects frameworks with the following structure:
FrameworkName.framework
|
- Resources
| |
| - Java
| |
| - frameworkname.jar
| - ... (resources: files and directories fitered according filter A)
- WebServerResources
|
- ... (resources: files and directories fitered according filter B)
A framework may depends on a set of other frameworks (and jar files of
those frameworks must be in the classpath).
I already have a package phase that produce this structure. (it works
for frameworks that doesn't depends on other frameworks)
A tarball may be a good solution to achieve the package phase. Is there
any example of tarball somewhere ?
Le 3 nov. 05, à 22:54, Brett Porter a écrit :
> 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 <be...@denali.be> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Benoit Mangez
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Producing directory artifacts
Posted by Brett Porter <br...@gmail.com>.
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 <be...@denali.be> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org