shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Les Hazlewood <...@stormpath.com>
Subject Re: Generating the shiro.doap.rdf file
Date Wed, 14 Dec 2016 23:43:54 GMT
Why wouldn't we want the release dates in there?

I'm generally in favor of no manual steps, so I'm currently a +1, I'm just
curious.

--
Les

On Wed, Dec 14, 2016 at 12:16 PM, Brian Demers <bdemers@apache.org> wrote:

> I started looking into using the maven-doap-plugin a little while back in
> order to remove one of the manual release steps.
>
> With a couple minor pom changes I was able to get this working:
> https://github.com/apache/shiro/pull/52
>
> After updating the reference to the new doap file in this file:
> https://svn.apache.org/repos/asf/comdev/projects.apache.
> org/data/projects.xml
>
> Our project pages is using this new generated version:
> https://projects.apache.org/project.html?shiro
>
> It took a little while to sync the new DOAP file and I had forgotten all
> about it, as generation code is only on a branch we either need to merge
> it, or revert back to the previous doap file.
>
>
> If you have made it this far, you might be wondering why I'm even brining
> this up instead of just merging it, two reasons:
> 1.) Generating the doap.rdf means we lose the release dates in the
>  'Versions' section, which was in the original version:
> https://github.com/apache/shiro/blob/master/shiro.doap.rdf
> 2.) Does anyone know if the doap file was submitted anywhere else?
>
> My opinions are we use the generated version, as that requires ZERO extra
> manual steps, the data is defined in a single place (the pom), it validates
> the file meets the ADF requirements.
>
> Unless I hear any -1's I'll merge this later this week.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message