You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@onami.apache.org by Christian Grobmeier <gr...@gmail.com> on 2013/01/03 11:36:27 UTC

DOAP files

I plan to create multiple doap files for each of our components.
Commons is doing it that way too. After that I am including them into

https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml

>From there they are used in the asf project index.

My plan is to use the /trunk/doap_onami-${componentname}.rdf
and not the /committer branch. I have not specific preference on that,
but it seems most projects put it into the trunk. Personally it feels
good to me to have them there (visible)

Any objections before I start the work?

Cheers

--
http://www.grobmeier.de
https://www.timeandbill.de

Re: DOAP files

Posted by Christian Grobmeier <gr...@gmail.com>.
Hi

I think it makes perfect sense. Dudnt know about the mvn plugin. But its
great

Cheers
On Jan 5, 2013 6:51 PM, "Simone Tripodi" <si...@apache.org> wrote:

> Hi again mate,
>
> I did some experiments with DOAP and I tracked progresses with a
> proposal on ONAMI-42.
>
> As reported to the issue, I propose publishing the DOAPs to each
> component site rather than having it committed in the source space, as
> our Maven fellows do, and having it totally managed by the
> doap-plugin.
>
> IMHO, managing 2 sets of metadata is useless, and the DOAP can be
> automatically and comfortably generated by the pom.
>
> WDYT?
>
> TIA and have a nice WE!
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
> On Thu, Jan 3, 2013 at 12:15 PM, Christian Grobmeier
> <gr...@gmail.com> wrote:
> > Ah cool.
> >
> > +1 to all you said, i will also test the maven module
> >
> > On Thu, Jan 3, 2013 at 11:54 AM, Simone Tripodi
> > <si...@apache.org> wrote:
> >> Hi mate,
> >>
> >> sure, just a small note: rather than adding
> >>
> >>> /trunk/doap_onami-${componentname}.rdf
> >>
> >> I'd add
> >>
> >> /trunk/${componentname}/doap.rdf
> >>
> >> No needs IMHO to add redundancies. WDYT?
> >>
> >> The maven-doap-plugin[1] could be a nice entry point to have initial
> >> doap skeletons and save time, for each module just run
> >>
> >> mvn org.apache.maven.plugins:maven-doap-plugin:1.1:generate
> >> -DdoapFile=doap.rdf  -DoutputDirectory=.
> >>
> >> You could even write a bash script that does that, cycling over the
> modules :P
> >>
> >> Green flag from my side, just fill a single issue valid for all
> >> components and thanks for taking care of it! :)
> >>
> >> Alles gute,
> >> -Simo
> >>
> >> [1] https://maven.apache.org/plugins/maven-doap-plugin/
> >>
> >> http://people.apache.org/~simonetripodi/
> >> http://simonetripodi.livejournal.com/
> >> http://twitter.com/simonetripodi
> >> http://www.99soft.org/
> >
> >
> >
> > --
> > http://www.grobmeier.de
> > https://www.timeandbill.de
>

Re: DOAP files

Posted by Simone Tripodi <si...@apache.org>.
Hi again mate,

I did some experiments with DOAP and I tracked progresses with a
proposal on ONAMI-42.

As reported to the issue, I propose publishing the DOAPs to each
component site rather than having it committed in the source space, as
our Maven fellows do, and having it totally managed by the
doap-plugin.

IMHO, managing 2 sets of metadata is useless, and the DOAP can be
automatically and comfortably generated by the pom.

WDYT?

TIA and have a nice WE!
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/


On Thu, Jan 3, 2013 at 12:15 PM, Christian Grobmeier
<gr...@gmail.com> wrote:
> Ah cool.
>
> +1 to all you said, i will also test the maven module
>
> On Thu, Jan 3, 2013 at 11:54 AM, Simone Tripodi
> <si...@apache.org> wrote:
>> Hi mate,
>>
>> sure, just a small note: rather than adding
>>
>>> /trunk/doap_onami-${componentname}.rdf
>>
>> I'd add
>>
>> /trunk/${componentname}/doap.rdf
>>
>> No needs IMHO to add redundancies. WDYT?
>>
>> The maven-doap-plugin[1] could be a nice entry point to have initial
>> doap skeletons and save time, for each module just run
>>
>> mvn org.apache.maven.plugins:maven-doap-plugin:1.1:generate
>> -DdoapFile=doap.rdf  -DoutputDirectory=.
>>
>> You could even write a bash script that does that, cycling over the modules :P
>>
>> Green flag from my side, just fill a single issue valid for all
>> components and thanks for taking care of it! :)
>>
>> Alles gute,
>> -Simo
>>
>> [1] https://maven.apache.org/plugins/maven-doap-plugin/
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de

Re: DOAP files

Posted by Christian Grobmeier <gr...@gmail.com>.
Ah cool.

+1 to all you said, i will also test the maven module

On Thu, Jan 3, 2013 at 11:54 AM, Simone Tripodi
<si...@apache.org> wrote:
> Hi mate,
>
> sure, just a small note: rather than adding
>
>> /trunk/doap_onami-${componentname}.rdf
>
> I'd add
>
> /trunk/${componentname}/doap.rdf
>
> No needs IMHO to add redundancies. WDYT?
>
> The maven-doap-plugin[1] could be a nice entry point to have initial
> doap skeletons and save time, for each module just run
>
> mvn org.apache.maven.plugins:maven-doap-plugin:1.1:generate
> -DdoapFile=doap.rdf  -DoutputDirectory=.
>
> You could even write a bash script that does that, cycling over the modules :P
>
> Green flag from my side, just fill a single issue valid for all
> components and thanks for taking care of it! :)
>
> Alles gute,
> -Simo
>
> [1] https://maven.apache.org/plugins/maven-doap-plugin/
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/



-- 
http://www.grobmeier.de
https://www.timeandbill.de

Re: DOAP files

Posted by Simone Tripodi <si...@apache.org>.
Hi mate,

sure, just a small note: rather than adding

> /trunk/doap_onami-${componentname}.rdf

I'd add

/trunk/${componentname}/doap.rdf

No needs IMHO to add redundancies. WDYT?

The maven-doap-plugin[1] could be a nice entry point to have initial
doap skeletons and save time, for each module just run

mvn org.apache.maven.plugins:maven-doap-plugin:1.1:generate
-DdoapFile=doap.rdf  -DoutputDirectory=.

You could even write a bash script that does that, cycling over the modules :P

Green flag from my side, just fill a single issue valid for all
components and thanks for taking care of it! :)

Alles gute,
-Simo

[1] https://maven.apache.org/plugins/maven-doap-plugin/

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/