Hi, Seb
But Onami does not appear in projects.apache.org!
I could not find the Onami DOAP - where is it?
each Onami's component website's page has a link / element which
points to its related DOAP, i.e.
* the main site http://onami.incubator.apache.org/ points to the parent doap:
link
In my humble opinion, DOAP files should be auto-generated and
published to public components sites.
What's the reason to distribute it in the source archive, when
releasing? DOAPs are intended to be consumed by crawlers/robots/...
and doesn't affect the build at all.
In Apache Onami we are using
Hi Simo,
2013/3/12 Simone Tripodi simonetrip...@apache.org
In my humble opinion, DOAP files should be auto-generated and
published to public components sites.
What's the reason to distribute it in the source archive, when
releasing? DOAPs are intended to be consumed by crawlers/robots/...
Hi Bene,
As far as I understand, this was the intention of sebb's proposal (making
sure that the DOAP doesn't get included in source distributions by moving
it out of a components SVN directory).
my question was a remark indeed, I was not really looking for a reply.
On 12 March 2013 07:26, Simone Tripodi simonetrip...@apache.org wrote:
In my humble opinion, DOAP files should be auto-generated and
published to public components sites.
Provided that it is possible to control the contents adequately, that
seems sensible.
What's the reason to distribute it
The DOAP files are currently held under
/commons/proper/component/trunk/doap_component.rdf
This is sort of convenient for editting, but means the doap file gets
included in tags and branches and may get included in source.
If included in source, the release date may be missing or inaccurate.
On 2013-03-12, sebb wrote:
The DOAP files are currently held under
/commons/proper/component/trunk/doap_component.rdf
This is sort of convenient for editting, but means the doap file gets
included in tags and branches and may get included in source.
If included in source, the release date
