wild guess: is the plugin in the build or the reporting section? I
don't know where it should go, but fiddling with its location may make
it work (talking about 'programming by coincidence' :) ).

hope it helps

On Fri, Dec 3, 2010 at 6:00 AM, Bastian Hofmann
<bashofm...@googlemail.com> wrote:
> Hi,
>
> apperantly we still have to add a doap file to Shindig to comply with
> the Apache Project Branding Requirements. I tried to do this by just
> adding the maven-doap-plugin
> (http://maven.apache.org/plugins/maven-doap-plugin/index.html) to the
> sites pom like this:
>
> Index: pom.xml
> ===================================================================
> --- pom.xml     (Revision 1041140)
> +++ pom.xml     (Arbeitskopie)
> @@ -61,6 +61,11 @@
>         </plugin>
>         <plugin>
>           <groupId>org.apache.maven.plugins</groupId>
> +          <artifactId>maven-doap-plugin</artifactId>
> +          <version>1.0</version>
> +        </plugin>
> +        <plugin>
> +          <groupId>org.apache.maven.plugins</groupId>
>           <artifactId>maven-pdf-plugin</artifactId>
>           <version>1.1</version>
>         </plugin>
> @@ -88,6 +93,19 @@
>       </plugin>
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
> +        <artifactId>maven-doap-plugin</artifactId>
> +        <executions>
> +          <execution>
> +            <id>doap</id>
> +            <phase>site</phase>
> +            <goals>
> +              <goal>generate</goal>
> +            </goals>
> +          </execution>
> +        </executions>
> +      </plugin>
> +      <plugin>
> +        <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-pdf-plugin</artifactId>
>         <executions>
>           <execution>
>
> Generation works fine, when I call plugin's goal directly, but the
> doap file doesn't get generated in the whole site phase. Since I'm no
> maven crack I'm possibly doing something wrong, but I can't find my
> error.
>
> Cheers
>
> Bastian
>
>
> ---------- Forwarded message ----------
> From: Shane Curcuru <a...@shanecurcuru.org>
> Date: 2010/10/15
> Subject: Please implement Apache Project Branding Requirements
> To: p...@apache.org
>
>
> Dear PMCs:
>
> To better showcase our projects and the "community of developers and
> users" that all Apache projects belong to, please plan to implement
> the new Apache Project Branding Requirements that the ASF Brand
> Management team has published.
>
>  http://www.apache.org/foundation/marks/pmcs
>
> Since some of these requirements for project websites are new, and
> many may not been clearly documented, it's expected that it may take
> time for projects to update their public presence to reflect the
> requirements. We certainly don't want to mandate technical
> requirements to projects, but we do believe that having some
> consistent elements and proper treatment of trademarks across all of
> our project's sites is important.
>
> PMC CHAIRS ACTION: To track your project's progress on these branding
> requirements, please include the below checklist in any reports
> submitted to the board until everything is complete (if you don't have
> time for an October report that's fine! 8-).  We'd like to see all
> projects updated to follow these requirements by the end of 2011 Q1.
>
>  http://www.apache.org/foundation/marks/pmcs#checklist
>
> Please email the tradema...@apache.org mailing list with all questions
> or suggestions (please do not reply-all, since that may include a lot
> of different p...@!)
>
> Note that I plan to checkin at least a basic DOAP for every Apache
> software product by the end of ApacheCon to help cover that
> requirement; so if you plan to add your own new DOAP file in your
> project repo, please let me know!
>
>  http://projects.apache.org/create.html
>
> - Shane Curcuru
> VP, Brand Management, The Apache Software Foundation
>    http://www.apache.org/foundation/
>    bcc: board@
>



-- 
Pablo Gra\~na
Chief Architect
Globant
Arg Office: +54 (11) 4109 1743
UK  Office: +44 (20) 7043 8269 int 8043
US  Office: +1 (212) 400 7686 int 8043

Reply via email to