You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Stefano Lenzi <ki...@interfree.it> on 2007/09/22 02:54:45 UTC
maven-obr-plugin: Some questions
Hi All,
I have some questions about the maven-obr-plugin:
- Should we keep the sandbox word in the package name? I think we can
rid of it.
- Should we replace PathFile class with FileUtils from plexus-util
artifact(http://plexus.codehaus.org/plexus-utils/apidocs/org/codehaus/plexus/util/FileUtils.html)
or with java.net.URL? IMHO we should remove it order to avoid
code-duplication.
- Why in the repository goal does the plugin look for obr.xml file?
Which is the difference between obr.xml and repository.xml?
Ciao,
Stefano "Kismet" Lenzi
RE: maven-obr-plugin: Some questions
Posted by Clement Escoffier <cl...@gmail.com>.
> -----Message d'origine-----
> De : Marcel Offermans [mailto:marcel.offermans@luminis.nl]
> Envoyé : dimanche 23 septembre 2007 11:35
> À : dev@felix.apache.org
> Objet : Re: maven-obr-plugin: Some questions
>
> On Sep 23, 2007, at 11:18 , clement escoffier wrote:
>
> > 2007/9/22, Marcel Offermans <ma...@luminis.nl>:
> >>
> >> On Sep 22, 2007, at 2:54 , Stefano Lenzi wrote:
> >>
> >>> - Should we keep the sandbox word in the package name? I think we
> >>> can rid of it.
> >>
> >> If my memory serves me well, I think we discussed this a while ago
> >> and concluded that all projects in the sandbox should also have the
> >> word sandbox in the package name.
> >
> > I is the convention for sandbox projects. However, we can remove
> > "sandbox"
> > as the project is no more in the sandbox.
>
> Whoops, my bad! :)
>
> >> - Why in the repository goal does the plugin look for obr.xml
> >>> file? Which is the difference between obr.xml and repository.xml?
> >>
> >> Probably, there is no difference. At least conceptually, an OBR
> >> compliant repository needs a file describing the (metadata of the)
> >> contents. This file is usually called repository.xml, but probably
> >> that is not a fixed name (correct me if I'm wrong, I did not re-read
> >> the RFC about OBR while replying).
> >
> > There is a difference. The OBR.xml file is a file that each project
> an
> > contain. This file describes OBR-metadata of the project that are not
> > computed by bindex. As OBR is extensible, we need a file where
> > describing
> > customized capabilities and requirements.
>
> Ok. Quick question, where is this described further, because I can
> find no reference to it in RFC-112 (that describes OBR)?
It is not in the RFC-112. We decide this when developing the
maven-obr-plugin. In our context, we have "non-standard" capabilities and
requirements (event producers and receivers, iPOJO factories ...). OBR allow
us to declare these information. So we required a way to declare all this
capabilities / requirements, we have find this way : writing a project
descriptor which is added to computed metadata. You have some information
about this on the maven-obr-plugin documentation
(http://clement.plop-plop.net/index.php?option=com_content&task=view&id=26&I
temid=37)
Clement
Re: maven-obr-plugin: Some questions
Posted by Marcel Offermans <ma...@luminis.nl>.
On Sep 23, 2007, at 11:18 , clement escoffier wrote:
> 2007/9/22, Marcel Offermans <ma...@luminis.nl>:
>>
>> On Sep 22, 2007, at 2:54 , Stefano Lenzi wrote:
>>
>>> - Should we keep the sandbox word in the package name? I think we
>>> can rid of it.
>>
>> If my memory serves me well, I think we discussed this a while ago
>> and concluded that all projects in the sandbox should also have the
>> word sandbox in the package name.
>
> I is the convention for sandbox projects. However, we can remove
> "sandbox"
> as the project is no more in the sandbox.
Whoops, my bad! :)
>> - Why in the repository goal does the plugin look for obr.xml
>>> file? Which is the difference between obr.xml and repository.xml?
>>
>> Probably, there is no difference. At least conceptually, an OBR
>> compliant repository needs a file describing the (metadata of the)
>> contents. This file is usually called repository.xml, but probably
>> that is not a fixed name (correct me if I'm wrong, I did not re-read
>> the RFC about OBR while replying).
>
> There is a difference. The OBR.xml file is a file that each project an
> contain. This file describes OBR-metadata of the project that are not
> computed by bindex. As OBR is extensible, we need a file where
> describing
> customized capabilities and requirements.
Ok. Quick question, where is this described further, because I can
find no reference to it in RFC-112 (that describes OBR)?
Re: maven-obr-plugin: Some questions
Posted by clement escoffier <cl...@gmail.com>.
Hello,
2007/9/22, Marcel Offermans <ma...@luminis.nl>:
>
> On Sep 22, 2007, at 2:54 , Stefano Lenzi wrote:
>
> > - Should we keep the sandbox word in the package name? I think we
> > can rid of it.
>
> If my memory serves me well, I think we discussed this a while ago
> and concluded that all projects in the sandbox should also have the
> word sandbox in the package name.
I is the convention for sandbox projects. However, we can remove "sandbox"
as the project is no more in the sandbox.
> - Why in the repository goal does the plugin look for obr.xml
> > file? Which is the difference between obr.xml and repository.xml?
>
> Probably, there is no difference. At least conceptually, an OBR
> compliant repository needs a file describing the (metadata of the)
> contents. This file is usually called repository.xml, but probably
> that is not a fixed name (correct me if I'm wrong, I did not re-read
> the RFC about OBR while replying).
There is a difference. The OBR.xml file is a file that each project an
contain. This file describes OBR-metadata of the project that are not
computed by bindex. As OBR is extensible, we need a file where describing
customized capabilities and requirements.
Clement
Greetings, Marcel
>
>
Re: maven-obr-plugin: Some questions
Posted by Marcel Offermans <ma...@luminis.nl>.
On Sep 22, 2007, at 2:54 , Stefano Lenzi wrote:
> - Should we keep the sandbox word in the package name? I think we
> can rid of it.
If my memory serves me well, I think we discussed this a while ago
and concluded that all projects in the sandbox should also have the
word sandbox in the package name.
> - Why in the repository goal does the plugin look for obr.xml
> file? Which is the difference between obr.xml and repository.xml?
Probably, there is no difference. At least conceptually, an OBR
compliant repository needs a file describing the (metadata of the)
contents. This file is usually called repository.xml, but probably
that is not a fixed name (correct me if I'm wrong, I did not re-read
the RFC about OBR while replying).
Greetings, Marcel