correct,
Its configuration is here.
http://scm.dspace.org/svn/repo/modules/dspace-pom/trunk/pom.xml
and looks like
<plugin>
<groupId>com.google.code.maven-license-plugin</groupId>
<artifactId>maven-license-plugin</artifactId>
<version>1.4.0</version>
<configuration>
<header>http://scm.dspace.org/svn/repo/licenses/LICENSE_HEADER</header>
<excludes>
<exclude>target/**</exclude>
<exclude>m2-target/**</exclude>
<exclude>**/*.properties</exclude>
</excludes>
<properties />
<encoding>UTF-8</encoding>
</configuration>
<executions>
<execution>
<goals>
<goal>check</goal>
</goals>
</execution>
</executions>
</plugin>
The pom is versioned separately from the rest of the modules and tagged here:
http://scm.dspace.org/svn/repo/modules/dspace-pom/tags/
You can see use of it in modules like dspace-services.
http://scm.dspace.org/svn/repo/modules/dspace-services/trunk/pom.xml
You'll see I avoid relying on the dspace-services/pom.xml directly in its
subprojects. Instead relying on the released parent whenever possible.
http://scm.dspace.org/svn/repo/modules/dspace-services/trunk/impl/pom.xml
The reason for this is that it liberates the developer to work with the
subprojects individually without needing the dspace-services/pom.xml available
in the filesystem in the directory above the project or in the maven repository
at all. the dspace-service/pom.xml is strictly just used as a execution point
for running maven commands against, not consolidating configuration into. This
leaves Eclipse users free to checkout individual projects and work with them
with fewer headaches and it is also a recommended practice to not overload your
multimodule project hierarchy with a great deal of dependencies.
Finally, you'll see the repository distribution configuration is changing in
these poms as we work to target using oss.sonatype.org as our maven repository
rather than maven.dspace.org. A process that will get our maven artifacts more
in line with the central repository requirements.
Mark
On Jun 17, 2010, at 11:17 AM, Mark H. Wood wrote:
> The license insertion plugin that was mentioned on IRC yesterday -- I
> presume that is:
>
> http://code.google.com/p/maven-license-plugin/
>
> There is one (http://maven.apache.org/maven-1.x/plugins/license/)
> described at the Maven site, but it seems to be a reporting plugin to
> turn your license into part of the 'mvn site' output...I guess...it's
> hard to tell. Anyway it seems to be for Maven v1.
>
> --
> Mark H. Wood, Lead System Programmer [email protected]
> Balance your desire for bells and whistles with the reality that only a
> little more than 2 percent of world population has broadband.
> -- Ledford and Tyler, _Google Analytics 2.0_
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit. See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo_______________________________________________
> Dspace-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-devel
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
