maven-plugins

History

jvanzyl f29424087c o Resolving all snapshots in plugins

o Bumping all plugin version to release status
o Validated all plugins to make sure all snapshots were removed.

  I had to manually insert the versions for:

  1) ashkelon
  2) commons-dbcp

  Not sure how either of these got up there without the timestamp
  mapping.

PR:
Obtained from:
Submitted by:
Reviewed by:


git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113303 13f79535-47bb-0310-9956-ffa450edef68

2003-04-09 01:06:49 +00:00

src/plugin-resources

Initial revision

2003-01-24 03:44:26 +00:00

xdocs

jakarta.apache.org/turbine/maven -> maven.apache.org/

2003-03-19 05:54:20 +00:00

.cvsignore

Initial revision

2003-01-24 03:44:26 +00:00

plugin.jelly

Explicity use ant name space. In prep for removal of jeez etc

2003-03-29 12:40:46 +00:00

plugin.properties

o MAVEN-300: Multithreaded jalopy is not reliable. Non thread-safe perl5compiler

2003-02-27 12:27:50 +00:00

project.properties

Added license property

2003-02-10 08:26:57 +00:00

project.xml

o Resolving all snapshots in plugins

2003-04-09 01:06:49 +00:00

README

Initial revision

2003-01-24 03:44:26 +00:00

README

A simple plugin to make jalopy available to you.

Your maven.xml might look something like this:
  
  <goal name="format" prereqs="jalopy:taskdef">
    <jalopy fileformat="unix"
            loglevel="info"
            threads="2">
      <fileset dir="src/test" >
        <include name="**/*.java" />
      </fileset>
    </jalopy>
  </goal>