Thanks, I did get it to work as per my other post. I didn't realise maven put all the metadata into the plugin.xml file though!

On 5 Sep 2005, at 12:22, Edward Yakop wrote:

1. Check your plugin.xml.
2. Right at the bottom you will find something like
    Note: this is taken from maven-jar-plugin
      <configuration>
        <outputDirectory
implementation="java.lang.String">${project.build.outputDirectory}</ outputDirectory>
        <project
implementation="org.apache.maven.project.MavenProject">${project}</ project>
        <basedir
implementation="java.lang.String">${project.build.directory}</basedir>
        <finalName
implementation="java.lang.String">${project.build.finalName}</ finalName>
      </configuration>

Anything in between <configuration> can be passed via <build> inside pom.xml
  <project>
        ...
    <!-- Add build node -->
    <build>
      <plugins>
        <plugin>
          <artifactId>maven-eclipseproject-plugin</artifactId>
          <configuration>
            <finalName>bla</finalName> <!-- Notice the finalName node
in between <configuration> -->
          </configuration>
        </plugin>
      </plugins>
    </build>
    <!-- End Add build node -->

  </project>

Regards,
Edward Yakop

On 9/5/05, Ashley Williams <[EMAIL PROTECTED]> wrote:

Great that does work (when I tag :version on the end as well).

However I can't get it to recognize my @parameter values when I
specify them as -D command line variables. Is there some other way to
smuggle them in??



On 10 Sep 2005, at 10:03, Johnny R. Ruiz wrote:


Ashley Williams wrote:



I've written a simple plugin that I wish to call from the command
line rather than as part of the project, just like m2 clean:clean,
so  as such I've used the 'execute' goal annotation.

However no matter what I try maven seems to look for a RELEASE
plugin  somewhere in the org.apache package structure. For example
specifying  -Dpackage -Dversion settings didn't work. Additionally
there will be additional configuration settings I'd need to
specify depending on  the project.

Any ideas?

------------------------------------------------------------------- --
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



have you tried  "m2 groupId:artifactId:goal"?

-------------------------------------------------------------------- -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to