Plugin tutorial

Skip to end of metadata
Go to start of metadata

This document, together with the hello-world plugin, shows you how to get started with the plugin development.

Table of Contents

What Can Plugins Do?

Jenkins defines extensibility points, which are interfaces or abstract classes that model an aspect of a build system. Those interfaces define contracts of what need to be implemented, and Jenkins allows plugins to contribute those implementations. See this document for more about extension points.

In this document, we'll be implementing a Builder that says hello. (built-in builders include Ant, Maven, and shell script. Builders build a project.)

Setting Up Environment

To develop a plugin, you need Maven 3 (why?) and JDK 6.0 or later. If this is the first time you use Maven, make sure Maven can download stuff over the internet.

Nexus Users
If you are using the Nexus Maven Repository Manager, you can ignore these instructions, and instead, click here for instructions on how to add Jenkins build prerequisites and the proper settings.xml entries.

It may be helpful to add the following to your ~/.m2/settings.xml (Windows users will find them in %USERPROFILE%\.m2\settings.xml):

<settings>
  <pluginGroups>
    <pluginGroup>org.jenkins-ci.tools</pluginGroup>
  </pluginGroups>

  <profiles>
    <!-- Give access to Jenkins plugins -->
    <profile>
      <id>jenkins</id>
      <activation>
        <activeByDefault>true</activeByDefault> <!-- change this to false, if you don't like to have it on per default -->
      </activation>
      <repositories>
        <repository>
          <id>repo.jenkins-ci.org</id>
          <url>http://repo.jenkins-ci.org/public/</url>
        </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <id>repo.jenkins-ci.org</id>
          <url>http://repo.jenkins-ci.org/public/</url>
        </pluginRepository>
      </pluginRepositories>
    </profile>
  </profiles>
  <mirrors>
    <mirror>
      <id>repo.jenkins-ci.org</id>
      <url>http://repo.jenkins-ci.org/public/</url>
      <mirrorOf>m.g.o-public</mirrorOf>
    </mirror>
  </mirrors>
</settings>

This will let you use short names for Jenkins Maven plugins (i.e. hpi:create instead of org.jenkins-ci.tools:maven-hpi-plugin:1.61:create),
though this is unnecessary once you are already working in a plugin project (only useful for initial hpi:create).
Note that adding the Jenkins repositories in a profile like this is not really necessary since most (all?) plugins already define these repositories.
And the mirror declaration is probably unnecessary.

Creating a New Plugin

To start a new plugin, use the online skeleton generator, or use an IDE (below).
Alternatively, if you are more comfortable with Maven, run the following command:

$ mvn -U org.jenkins-ci.tools:maven-hpi-plugin:create

This will ask you a few questions, like the groupId (the Maven jargon for the package name) and the artifactId (the Maven jargon for your project name), then create a skeleton plugin from which you can start with. Make sure you can build this:

$ cd newly-created-directory
$ mvn package

Explanations:

-U means that Maven should update all relevant Maven plugins (check for plugin updates)
hpi: this prefix specifies that the Jenkins HPI Plugin is being invoked, a plugin that supports development of Jenkins plugins
create is the goal which creates the directory layout and the POM for your new Jenkins plugin and it adds it to the module list
package is a standard phase which compiles all sources, runs the tests and creates a package - when used by the HPI plugin it will create an *.hpi file

Building a Plugin

To build a plugin, run mvn install. This will create the file ./target/pluginname.hpi that you can deploy to Jenkins.

$ mvn install

Setting up a productive environment with your IDE

NetBeans

NetBeans users can use the IDE's Maven support to open the project directly.

As you navigate through the code, you can tell NetBeans to attach source code JAR files by clicking the "Attach" button that appears in the top of the main content window. This allows you to read the Jenkins core source code as you develop plugins. (Or just select Download Sources on the Dependencies node.)

You are advised to use the NetBeans plugin for Jenkins/Stapler development. This offers many Jenkins-specific features. Most visibly, create a new plugin using New Project » Maven » Jenkins Plugin, and use Run Project to test it.

IntelliJ IDEA

IntelliJ 7.0 (or later) users can load pom.xml directly from IDE, and you should see all the source code of libraries and Jenkins core all the way to the bottom. Consider installing IntelliJ IDEA plugin for Stapler to make the development easier.

IntelliJ defaults to downloading sources and JavaDocs on demand. So, to see the source, you may need to click the Download artifacts button in the Maven Projects tab.

Eclipse

Use Eclipse Juno (4.2) or later for the best experience.

As Jenkins plugins are Maven projects, Eclipse users have two ways to load a Jenkins plugin project. One is to use m2e, which tries to make Eclipse understand Maven "natively", and the other is to use Maven Eclipse plugin, which makes Maven generate Eclipse project definitions. At the moment, unless you have some prior experience with m2e, we currently recommend plugin developers to go with the Maven Eclipse plugin.

Eclipse users can run the following Maven command to generate Eclipse project files (the custom outputDirectory parameter is used to work around the lack of JSR-269 annotation processor support in Eclipse:)

$ mvn -DdownloadSources=true -DdownloadJavadocs=true -DoutputDirectory=target/eclipse-classes eclipse:eclipse

Once this command completes successfully, use "Import..." (under the File menu in Eclipse) and select "General" > "Existing Projects into Workspace".

Do not select "Existing Maven Projects", which takes you to the m2e route

See Jenkins plugin development with Eclipse for gotchas and other known Eclipse/Maven related issues with Jenkins plugin development.

See Eclipse alternative build setup for an alternative way of setting up the Eclipse build environment, that is a bit more technically involved than using maven, but can give faster build times.

Plugin Workspace Layout

The plugin workspace consists of the following major pieces:

pom.xml

Maven uses it for building your plugin.

src/main/java

Java source files of the plugin.

src/main/resources

Jelly/Groovy views of the plugin. See this document for more about it.

src/main/webapp

Static resources of the plugin, such as images and HTML files.

Source Code

Let's take a look at the source code. A plugin's main entry point is a PluginImpl class that extends from Plugin. Once Jenkins detects your plugin class (via its inheritance relationship from Plugin), it will create an instance, and invoke methods. A Plugin class is optional; a plugin may simply implement extensions:

Most of the time, a plugin class just registers extension points, and your main work involves implementing those extension points. See the source code for more about how a Builder is implemented and what it does.

Debugging a Plugin

NetBeans 6.7+ users can just hit Debug. For all others, run the following command to launch Jenkins with your plugin:
Convenient:

mvnDebug hpi:run

Unix:

$ export MAVEN_OPTS="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n"
$ mvn hpi:run

Windows:

> set MAVEN_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n
> mvn hpi:run

If you open http://localhost:8080/jenkins in your browser, you should see the Jenkins page running in Jetty. The MAVEN_OPTS portion launches this whole thing with the debugger port 8000, so you should be able to start a debug session to this port from your IDE.

Once this starts running, keep it running. Jetty will pick up all the changes automatically.

  1. When you make changes to view files in src/main/resources or resource files in src/main/webapp, just hit F5 in your browser to see the changes.
  2. When you change Java source files, compile them in your IDE (NetBeans 6.7+: Debug > Apply Code Changes) and Jetty should automatically redeploy Jenkins to pick up those changes. There is no need to run mvn at all.
    MAVEN_OPTS can be used to specify all sorts of other JVM parameters, like -Xmx

Changing port

If you need to launch the Jenkins on a different port than 8080, set the port through the system property jetty.port.

$ mvn hpi:run -Djetty.port=8090

Setting context path

maven-hpi-plugin 1.65 or later (used by parent POM 1.401 or later) can set the context path by using a system property. On more recent versions of Jenkins the "/jenkins" prefix is added automatically.

$ mvn hpi:run -Dhpi.prefix=/jenkins

Changing code while debugging

Depending on what you change, you can see it in the running instance without restarting the whole Maven process:

  • Views: Groovy/Jelly views are re-compiled every time a browser requests a page, so just reload a page in the browser and you'll see the changes. This is also true for help files you write.
  • Java code: If you are debugging, JVM's hot swap feature can be used to reload code so long as you don't touch the method signature. Beyond that, you can hit ENTER in the Maven process and it'll reload the Jenkins webapp. See Developing with JRebel for how to get a JRebel license for OSS projects to improve this experience.
  • POM: If you change POM, you'll have to stop and restart Maven to see the changes.

Distributing a Plugin

To create a distribution image of your plugin, run the following Maven command:

$ mvn package

This should create target/*.hpi file. Other users can use Jenkins' web UI to upload this plugin to Jenkins (or place it in $JENKINS_HOME/plugins.)

Releasing a Plugin and Hosting a Plugin on jenkins-ci.org

If you got to this point, you should definitely consider hosting your plugin on jenkins-ci.org. Move on to this document for how to do that. This includes the instructions for releasing the plugin.

Using custom builds of plugins included in the Jenkins WAR

If you are building a patched version of one of the plugins in the Jenkins core, the deployment process is a bit different. This is because Jenkins will itself manage these plugins unless you tell it not to.

Deploying a custom build of a core plugin

  1. Stop Jenkins
  2. Copy the custom HPI file to $JENKINS_HOME/plugins
  3. Remove the previously expanded plugin directory
  4. Create an empty file called <plugin>.hpi.pinned - e.g. maven-plugin.hpi.pinned
  5. Start Jenkins

Other tips

  1. Consider running Maven like this mvn -o ... to avoid hitting repositories every time. This will make various operations considerably faster.
  2. Subscribe to the users' alias from here so that we can get in touch with you.
  3. When you bump up the version of Jenkins you depend on, make sure to run mvn clean once, in particular to delete target/work that Jetty uses. Newer versions may just use work, not target/work. Otherwise your Jetty may continue to pick up old left-over JAR files.
  4. If you have a high latency network connection to the Maven repository, you might find it faster to first run the build once on a server near to the maven repository, then rsync the .m2/repository folder across to your local computer
  5. The 'package' and 'install' targets will by default run many tests. You can add '-DskipTests' on the command-line to skip these (of course you should run the tests before committing any changes)
  6. The 'compiler:compile' goal is faster than 'compile', because it is a goal, rather than a lifecycle event, and therefore avoids certain earlier goals, such as setting up resources

Other resources

Besides this tutorial, there are other tutorials and examples available on line:

Labels

plugin plugin Delete
setup setup Delete
maven maven Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jul 18, 2007

    Anonymous says:

    I think that the pom mentioned in this page is out of date. You will need to edi...

    I think that the pom mentioned in this page is out of date. You will need to edit it to have the following:

     java.net
    url = http://download.java.net/maven/1

     java.net2
    url = http://download.java.net/maven/2

    1. Jul 23, 2007

      Kohsuke Kawaguchi says:

      Thanks. Fixed.

      Thanks. Fixed.

      1. Oct 02, 2012

        Rahim Nathani says:

        Hi Kohsuke, I am trying to create a plugin for jenkins. I added metioned above ...

        Hi Kohsuke,

        I am trying to create a plugin for jenkins. I added metioned above xml to my settings.xml uder /.m2 and when I run mvn -cpu hpi:create I get the following error 

        settings.xml

        settings.xmlorg.apache.maven.plugins:maven-hpi-plugin' does not exist or no valid version could be found

        maven version that I have is 

        Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400). 

        Can you please help. I have attached settings.xml which I modified.

        Thanks.

  2. Jul 24, 2007

    Stephen Connolly says:

    We need to update the hpi plugin so that the httpPort bound during hpi:run is us...

    We need to update the hpi plugin so that the httpPort bound during hpi:run is user configurable form the command line.

    E.g. something like

     mvn hpi:run -DhttpPort=xxxx

    As in some cases I already have a tomcat instance on 8080 that I'm not exactly keep to restart (as I'm doing hudson development while waiting for the tomcat instance to do some other stuff

    1. Aug 04, 2007

      Kohsuke Kawaguchi says:

      Added https://hudson.dev.java.net/nonav/maven-hpi-plugin/
      1. Apr 25, 2012

        Sudhakar N says:

        Hi, I have been getting the following errors while doing "mvn package" even tho...

        Hi,

        I have been getting the following errors while doing "mvn package" even though i have added proxy settings correctly.

        [INFO] Scanning for projects...
        Downloading: http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/plugin/1.410/plugin-1.410.pom
        Downloading: http://guice-maven.googlecode.com/svn/trunk/org/jenkins-ci/plugins/plugin/1.410/plugin-1.410.pom
        Downloading: http://repo.maven.apache.org/maven2/org/jenkins-ci/plugins/plugin/1.410/plugin-1.410.pom
        [ERROR] The build could not read 1 project -> [Help 1]
        [ERROR]
        [ERROR]   The project org.jenkins-ci.plugins:xunit:1.44-SNAPSHOT (C:\Sudhakar\MavenPlugins\jenkinsci-xunit-plugin-eca700
        2\pom.xml) has 1 error
        [ERROR]     Non-resolvable parent POM: Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:1.410 from/to repo.
        jenkins-ci.org (http://repo.jenkins-ci.org/public/): Not authorized by proxy, ReasonPhrase:Proxy Authentication Required
         ( Forefront TMG requires authorization to fulfill the request. Access to the Web Proxy filter is denied.  ). and 'paren
        t.relativePath' points at wrong local POM @ line 4, column 13 -> [Help 2]
        [ERROR]
        [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
        [ERROR] Re-run Maven using the -X switch to enable full debug logging.
        [ERROR]
        [ERROR] For more information about the errors and possible solutions, please read the following articles:
        [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
        [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

        I am new to jenkins and maven. can any one help me out in this regard.

        Thanks in advance.

  3. Aug 20, 2007

    Anonymous says:

    Hi - I followed the instructions and I got the following error when I tried 'mv...

    Hi -

    I followed the instructions and I got the following error when I tried 'mvn package' in the project the hpi archetype created:

    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] Internal error in the plugin manager executing goal 'org.jvnet.hudson.tools:maven-hpi-plugin:1.11:apt-compi
    le': Unable to find the mojo 'org.jvnet.hudson.tools:maven-hpi-plugin:1.11:apt-compile' in the plugin 'org.jvnet.h
    udson.tools:maven-hpi-plugin'
    com/sun/mirror/apt/AnnotationProcessorFactory
    [INFO] ------------------------------------------------------------------------
    [INFO] For more information, run Maven with the -e switch
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 5 seconds
    [INFO] Finished at: Mon Aug 20 22:25:53 PDT 2007
    [INFO] Final Memory: 27M/64M
    [INFO] ------------------------------------------------------------------------

    1. Aug 21, 2007

      Kohsuke Kawaguchi says:

      Could you please file this as an issue in the issue tracker, and run the same wi...

      Could you please file this as an issue in the issue tracker, and run the same with "mvn -X" and attach the log file?
      (You'd need to request the observer role in the project to do this — thanks!)

  4. Aug 29, 2007

    Anonymous says:

    Hi, I followed your instructions (downloading Maven2, then getting the pom.xml ...

    Hi,

    I followed your instructions (downloading Maven2, then getting the pom.xml and doing mvn package) but I can't modify the settings.xml... I don't have that file in my .m2 directory

    Could you help?

    Thanx

    1. Sep 03, 2007

      Frank LaFond says:

      I was able to get past this point with the simple settings.xml file: <settin...

      I was able to get past this point with the simple settings.xml file:

      <settings>
         <pluginGroups>
            <pluginGroup>org.jvnet.hudson.tools</pluginGroup>
         </pluginGroups>
      </settings>
      

       It worked for me.

      Frank LaFond. 

  5. Nov 24, 2007

    kleinmantara - says:

    I get the following error with the maven-hpi-plugin version 1.11: E:\coder\hgsl...

    I get the following error with the maven-hpi-plugin version 1.11:

    E:\coder\hgsls\java\skype>mvn org.jvnet.hudson.tools:maven-hpi-plugin:1.11:create
    [INFO] Scanning for projects...
    Downloading: http://repo1.maven.org/maven2/org/jvnet/hudson/tools/maven-hpi-plugin/1.11/maven-hpi-plugin-1.11.pom
    Downloading: http://repo1.maven.org/maven2/org/jvnet/hudson/tools/maven-hpi-plugin/1.11/maven-hpi-plugin-1.11.pom
    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] Failed to resolve artifact.
    
    GroupId: org.jvnet.hudson.tools
    ArtifactId: maven-hpi-plugin
    Version: 1.11
    
    Reason: Unable to download the artifact from any repository
    
      org.jvnet.hudson.tools:maven-hpi-plugin:pom:1.11
    
    from the specified remote repositories:
      central (http://repo1.maven.org/maven2)
    

    But when i use maven-hpi-plugin version 1.14 it works. BTW it took 31 minutes 46 seconds.

  6. Dec 12, 2007

    Anonymous says:

    Yo Kawaguchi... just have to say that Hudson's architecture (and your Stapler pr...

    Yo Kawaguchi... just have to say that Hudson's architecture (and your Stapler project) are just insanely elegant. High fives all around.

    1. Dec 12, 2007

      Mike Caron says:

      Uh, yeah... I wasn't logged in. This is me.

      Uh, yeah... I wasn't logged in. This is me.

  7. Feb 23, 2008

    frizbog - says:

    I got Maven 2.0.8 and installed it according to their directions, downloaded the...

    I got Maven 2.0.8 and installed it according to their directions, downloaded the pom.xml file into a new directory, and ran mvn package and got this error:

    [INFO] Scanning for projects...
    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] The plugin 'org.jvnet.hudson.tools:maven-hpi-plugin' does not exist or no valid version could be found
    [INFO] ------------------------------------------------------------------------
    [INFO] For more information, run Maven with the -e switch
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: < 1 second
    [INFO] Finished at: Sat Feb 23 11:00:40 EST 2008
    [INFO] Final Memory: 1M/254M
    [INFO] ------------------------------------------------------------------------
    

    I also tried using a settings.xml file as described (the "crude" way) and got the same error.  I am not behind any proxy.

    Any ideas?  Since I am new to Maven I am pretty sure its some dumb thing I'm doing.... 

    1. Feb 24, 2008

      hoshposh - says:

      I got the same problem that Matthew did with version 2.08 of maven.  I trie...

      I got the same problem that Matthew did with version 2.08 of maven.  I tried going back to 2.04 and that did not seem to help.

      Cheers!

      1. Feb 24, 2008

        hoshposh - says:

        Oh never mind.  I looked in the ~/.m2/repository and found the version...

        Oh never mind.  I looked in the ~/.m2/repository and found the version is 1.17 at this point.  Sorry!!

    2. Feb 24, 2008

      frizbog - says:

      Turns out I was right.  It was something dumb I was doing.  My firewal...

      Turns out I was right.  It was something dumb I was doing.  My firewall software was not allowing java.exe to access the internet.

  8. Feb 29, 2008

    Anonymous says:

    I want to download the source for a plugin and make a patch.  But I can't e...

    I want to download the source for a plugin and make a patch.  But I can't even get the source!

    I'm behind a proxy that uses a username/password. I got Maven to download everything, but no source!

    And then I tried checking it out of CVS and got this:

    $ cvs "-d:pserver;proxy=proxyhost.com;proxyport=3128:guest@cvs.dev.java.net:/cvs" co hudson/hudson/plugin/co
    zsh: correct 'cvs' to '_cvs' [nyae]? n
    cvs checkout: WARNING: Ignoring method options found in CVSROOT: `proxy=proxyhost.com;proxyport=3128'.
    cvs checkout: Use CVS version 1.12.7 or later to handle method options.
    cvs checkout: warning: skipping invalid entry in password file at line 1
    cvs server: cannot find module `hudson/hudson/plugin/cobertura' - ignored
    cvs [checkout aborted]: cannot expand modules
    

    Any help?

    1. Feb 29, 2008

      Kohsuke Kawaguchi says:

      The error message says it all. There's no such module `hudson/hudson/plugin/cobe...

      The error message says it all. There's no such module `hudson/hudson/plugin/cobertura'
      You made a typo. It's "plugins".

  9. Mar 04, 2008

    Dan Lewis says:

     I followed the instructions and I get the following error when I do mvn hp...

     I followed the instructions and I get the following error when I do mvn hpi:run:[INFO] Started Jetty Server
    [INFO] Starting scanner at interval of 1 seconds.
    2008-03-04 13:15:12.765:/:INFO:  Stapler: init
    2008-03-04 13:15:12.781::WARN:  EXCEPTION
    javax.servlet.ServletException: there's no "app" attribute in the application context.
            at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:446)
            at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:370)
            at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:468)
            at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1074)
            at hudson.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:79)
            at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
            at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
            at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185)
            at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
            at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689)
            at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391)
            at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:146)
            at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
            at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
            at org.mortbay.jetty.Server.handle(Server.java:285)
            at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457)
            at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:751)
            at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:500)
            at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
            at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357)
            at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:329)
            at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
    I am using Maven 2.0.8, Java 1.6.0_02 on Windows XP Pro SP2.  Am I doing something wrong?  I am new to Maven.

  10. Mar 13, 2008

    Erling Linde says:

    I have problems with external dependencies: I get lots of these: Caused by: jav...

    I have problems with external dependencies:

    I get lots of these: Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.sun.syndication.propono.atom.client.AtomClientFactory

    I have referenced the libraries using Maven 2, e.g.:

        <dependency>
          <groupId>propono</groupId>
          <artifactId>propono</artifactId>
          <version>0.6</version>
        </dependency> 

    The libraries are included in WEB-INF/lib

    I have also tried putting the libraries in tomcat/lib and also tomcat/webapps/hudson/WEB-INF/lib 

    Where should external jars be put? How should they be referenced?

    Thanks, Erling 


  11. Mar 23, 2008

    turbouser - says:

    Any help is appreciated...How do I resolve the error? C:\Program Files\Apache S...

    Any help is appreciated...How do I resolve the error?

    C:\Program Files\Apache Software Foundation\apache-maven-2.0.8\tmp>mvn package
    [INFO] Scanning for projects...
    Downloading: http://download.java.net/maven/1//org.jvnet.hudson.tools/poms/tools&#45;1.4.pom
    Downloading: http://download.java.net/maven/2//org/jvnet/hudson/tools/tools/1.4/tools-1.4.pom
    Downloading: http://download.java.net/maven/2/org/jvnet/hudson/tools/tools/1.4/tools-1.4.pom
    Downloading: http://repo1.maven.org/maven2/org/jvnet/hudson/tools/tools/1.4/tools-1.4.pom
    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] Error building POM (may not be this project's POM).

    Project ID: null:maven-hpi-plugin:maven-plugin:1.18

    Reason: Cannot find parent: org.jvnet.hudson.tools:tools for project: null:maven
    -hpi-plugin:maven-plugin:1.18 for project null:maven-hpi-plugin:maven-plugin:1.1
    8

    [INFO] ------------------------------------------------------------------------
    [INFO] For more information, run Maven with the -e switch
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: < 1 second
    [INFO] Finished at: Sun Mar 23 23:00:15 PDT 2008
    [INFO] Final Memory: 1M/4M
    [INFO] ------------------------------------------------------------------------

    1. Mar 24, 2008

      David Hayes says:

      This is basically to do with the fact that the java.net maven source and the hud...

      This is basically to do with the fact that the java.net maven source and the hudson source are slightly out of sync. Not to worry, a simple fix locally will fix this:

       Change the file:

      c:\documents and settings\your user\.m2\repository\org\jvnet\hudson\tools\maven-hpi-plugin\1.18\maven-hpi-plugin-1.18.pom
      (change this to whatever suits your operating system)

      Right near the top of the file, you'll see the following block:

        <parent>
          <groupId>org.jvnet.hudson.tools</groupId>
          <artifactId>tools</artifactId>
          <version>1.4</version>
          <relativePath>../pom.xml</relativePath>
        </parent>
      

       Change this to:

        <parent>
          <groupId>org.jvnet.hudson.tools</groupId>
          <artifactId>tools</artifactId>
          <version>1.1</version>
          <relativePath>../pom.xml</relativePath>
        </parent>
      


      Note the change of the version number. Now try again, and everything should work!

      1. Mar 25, 2008

        turbouser - says:

        You were 100% right.  Everything is working now.  -Thanks.

        You were 100% right.  Everything is working now.  -Thanks.

      2. Mar 28, 2008

        Max Sauer says:

        Thanks for this, the tools-1.4.pom is not present inside repository. It would be...

        Thanks for this, the tools-1.4.pom is not present inside repository. It would be fine to have a note in the tutorial above.

      3. Mar 31, 2008

        Kohsuke Kawaguchi says:

        This is fixed now. In the future, please report these issues to the issue tracke...

        This is fixed now. In the future, please report these issues to the issue tracker, so that we can fix it, instead of asking everyone to work around the problem.

  12. Apr 08, 2008

    Wojtek Gworek says:

    Can anybody send me pom.xml from https://hudson.dev.java.net/source/browse/*chec...

    Can anybody send me pom.xml from https://hudson.dev.java.net/source/browse/*checkout*/hudson/hudson/tools/bootstrap/pom.xml
    Any time I try to access it I do see response about Unknown location: hudson/tools/bootstrap/pom.xml

    1. Apr 08, 2008

      Kohsuke Kawaguchi says:

      Link fixed. This was due to CVS->SVN migration.

      Link fixed. This was due to CVS->SVN migration.

  13. May 14, 2008

    Munish Gopal says:

    When i run mvn package command, I get this error: [INFO] [hpi:apt-compile] [INF...

    When i run mvn package command, I get this error:

    [INFO] [hpi:apt-compile]
    [INFO] Compiling 2 source files to /opt/setups/apache-maven-2.0.9/agitar/target/classes
    [FATAL ERROR] org.jvnet.hudson.maven.plugins.hpi.AptMojo#execute() caused a linkage error (java.lang.NoClassDefFoundError) and may be out-of-date. Check the realms:
    [FATAL ERROR] Plugin realm = app0.child-container[org.jvnet.hudson.tools:maven-hpi-plugin]
    urls[0] = file:/root/.m2/repository/org/jvnet/hudson/tools/maven-hpi-plugin/1.20/maven-hpi-plugin-1.20.jar
    urls[1] = file:/root/.m2/repository/org/apache/maven/maven-archiver/2.0.1/maven-archiver-2.0.1.jar
    urls[2] = file:/root/.m2/repository/org/codehaus/plexus/plexus-utils/1.0.4/plexus-utils-1.0.4.jar
    urls[3] = file:/root/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-4/plexus-archiver-1.0-alpha-4.jar
    urls[4] = file:/root/.m2/repository/org/mortbay/jetty/maven-jetty-plugin/6.1.1/maven-jetty-plugin-6.1.1.jar
    urls[5] = file:/root/.m2/repository/commons-el/commons-el/1.0/commons-el-1.0.jar
    urls[6] = file:/root/.m2/repository/org/mortbay/jetty/jetty/6.1.1/jetty-6.1.1.jar
    urls[7] = file:/root/.m2/repository/org/mortbay/jetty/jetty-util/6.1.1/jetty-util-6.1.1.jar
    urls[8] = file:/root/.m2/repository/org/mortbay/jetty/servlet-api-2.5/6.1.1/servlet-api-2.5-6.1.1.jar
    urls[9] = file:/root/.m2/repository/org/apache/maven/maven-plugin-tools-api/2.0/maven-plugin-tools-api-2.0.jar
    urls[10] = file:/root/.m2/repository/org/mortbay/jetty/jetty-plus/6.1.1/jetty-plus-6.1.1.jar

    ..............

    .........

    [FATAL ERROR] Container realm = plexus.core
    urls[0] = file:/opt/setups/apache-maven-2.0.9/lib/maven-2.0.9-uber.jar
    [INFO] ------------------------------------------------------------------------
    [ERROR] FATAL ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] com.sun.tools.apt.Main
    [INFO] ------------------------------------------------------------------------
    [INFO] Trace
    java.lang.NoClassDefFoundError: com.sun.tools.apt.Main
            at org.jvnet.hudson.maven.plugins.hpi.AptCompiler.compileInProcess(AptCompiler.java:62)
            at org.jvnet.hudson.maven.plugins.hpi.AptCompiler.compile(AptCompiler.java:50)
            at org.jvnet.hudson.maven.plugins.hpi.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:486)
            at org.jvnet.hudson.maven.plugins.hpi.CompilerMojo.execute(CompilerMojo.java:111)
            at org.jvnet.hudson.maven.plugins.hpi.AptMojo.execute(AptMojo.java:21)
            at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
            at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:615)
            at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
            at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
            at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
            at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

    I am struck at this point. Can anyone help?

  14. May 14, 2008

    Jeff Berkowitz says:

    Munish, I take it from the appearance of codehaus in your stack backtrace that y...

    Munish, I take it from the appearance of codehaus in your stack backtrace that you may be using the "mevenide" plugin for netbeans.  If so, please look at the email archives for the last few days at http://www.nabble.com/codehaus---mevenide-f11958.html because there appears to be a problem with the latest version of the plugin.

  15. Jul 13, 2008

    mikegr - says:

    If you get an error like this: >mvn org.jvnet.hudson.tools:maven-hpi-plugin:...

    If you get an error like this:

    >mvn org.jvnet.hudson.tools:maven-hpi-plugin:1.20:create

    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) com.sun:tools:jar:1.5

    You probably haven't set JAVA_HOME correctly.

  16. Oct 08, 2008

    Kenneth Kumentas says:

    $ mvn org.jvnet.hudson.tools:maven-hpi-plugin:1.20:create [INFO] Scanning for p...
    $ mvn org.jvnet.hudson.tools:maven-hpi-plugin:1.20:create
    [INFO] Scanning for projects...
    Downloading: http://repo1.maven.org/maven2/org/jvnet/hudson/tools/maven-hpi-plug
    in/1.20/maven-hpi-plugin-1.20.jar
    [INFO] Cannot find mojo descriptor for: 'org.jvnet.hudson.tools:maven-hpi-plugin
    :1.20:create' - Treating as non-aggregator.
    [INFO] ------------------------------------------------------------------------
    [INFO] Building Maven Default Project
    [INFO]    task-segment: [org.jvnet.hudson.tools:maven-hpi-plugin:1.20:create]
    [INFO] ------------------------------------------------------------------------
    Downloading: http://repo1.maven.org/maven2/org/jvnet/hudson/tools/maven-hpi-plug
    in/1.20/maven-hpi-plugin-1.20.jar
    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] A required plugin was not found: Plugin could not be found - check that t
    he goal name is correct: Unable to download the artifact from any repository
    


    I like Hudson, and would like to contribute a plugin. However, in spite of the fact that I've built and deployed more than 100 enterprise Java projects since 1999, Maven absolutely makes me sick. I cringe at all the wonderful projects that are adopting it.

    I followed all the directions above, and tried anything in the comments that looked like it would help. Please reconsider your choice of this miserable tool.

    1. Oct 09, 2008

      Ulli Hafner says:

      Did you update your settings file as described in section "Setting Up Environmen...

      Did you update your settings file as described in section "Setting Up Environment"?

      1. Oct 09, 2008

        Kenneth Kumentas says:

        Yes I did. I was able to get it to create the sample project by downloading the ...

        Yes I did. I was able to get it to create the sample project by downloading the failed plugin manually. Did I mention that Maven sucks?

        However, with the help of the sample project and the documentation, I see how easy it is to create my plugin using Ant.

        1. Oct 14, 2008

          MeTAlMollY - says:

          Hi Kenneth, The version should be 1.21 instead of 1.20. Then it should work fin...

          Hi Kenneth,

          The version should be 1.21 instead of 1.20. Then it should work fine.

  17. Nov 18, 2008

    Victor Hugo Germano says:

    Hello!While creating a project, i'm receiving the following error:  $>...

    Hello!While creating a project, i'm receiving the following error:

     $> mvn org.jvnet.hudson.tools:maven-hpi-plugin:1.23:create -e
    
    + Error stacktraces are turned on.
    [INFO] Scanning for projects...
    [INFO] ------------------------------------------------------------------------
    [INFO] Building Maven Default Project
    [INFO]    task-segment: [org.jvnet.hudson.tools:maven-hpi-plugin:1.23:create] (aggregator-style)
    [INFO] ------------------------------------------------------------------------
    [INFO] ------------------------------------------------------------------------
    [ERROR] FATAL ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] Lorg/apache/maven/archetype/Archetype;
    org.apache.maven.archetype.Archetype
    [INFO] ------------------------------------------------------------------------
    [INFO] Trace
    java.lang.NoClassDefFoundError: Lorg/apache/maven/archetype/Archetype;
        at java.lang.Class.getDeclaredFields0(Native Method)
        at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
        at java.lang.Class.getDeclaredField(Class.java:1880)
        at hidden.org.codehaus.plexus.util.ReflectionUtils.getFieldByNameIncludingSuperclasses(ReflectionUtils.java:31)
        at org.codehaus.plexus.component.composition.FieldComponentComposer.getFieldByName(FieldComponentComposer.java:212)
        at org.codehaus.plexus.component.composition.FieldComponentComposer.findMatchingField(FieldComponentComposer.java:171)
        at org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:62)
        at org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68)
        at org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486)
        at org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29)
        at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:101)
        at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:105)
        at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:95)
        at org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:48)
        at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
        at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:312)
        at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
        at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:609)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:429)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    Caused by: java.lang.ClassNotFoundException: org.apache.maven.archetype.Archetype
        at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195)
        at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255)
        at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
        ... 36 more
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 9 seconds
    [INFO] Finished at: Tue Nov 18 20:41:43 BRST 2008
    [INFO] Final Memory: 8M/18M
    [INFO] ------------------------------------------------------------------------
     
    

    System: Ubuntu 8.10

    I didn't install maven as an ubuntu's package, but as a zip file... the following program works well (creating a simples web application):

    $> mvn archetype:create
    


    Any suggestions?

    Thanks a lot!

  18. Nov 19, 2008

    Teemu Kolehmainen says:

    Could you add the instructions on how to do it the "right" way (with pluginRepos...

    Could you add the instructions on how to do it the "right" way (with pluginRepository) now that the Maven bug has been resolved?

    1. Dec 20, 2008

      ppawel - says:

      Done.

      Done.

  19. Apr 13, 2009

    Brian Lalor says:

    hpi:create isn't working for me. I'm using maven-hpi-plugin 1.34 with Maven 2.0....

    hpi:create isn't working for me. I'm using maven-hpi-plugin 1.34 with Maven 2.0.9.

    [blalor@vm-fc8 ...d_roots/hudson_deploy_plugin/checkout]> emacs_mvn_helper.sh -Phudson-plugin-dev  org.jvnet.hudson.tools:maven-hpi-plugin:1.34:create -e
    + Error stacktraces are turned on.
    [INFO] Scanning for projects...
    [INFO] ------------------------------------------------------------------------
    [INFO] Building Maven Default Project
    [INFO]    task-segment: [org.jvnet.hudson.tools:maven-hpi-plugin:1.34:create] (aggregator-style)
    [INFO] ------------------------------------------------------------------------
    [INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
    [INFO] Setting property: velocimacro.messages.on => 'false'.
    [INFO] Setting property: resource.loader => 'classpath'.
    [INFO] Setting property: resource.manager.logwhenfound => 'false'.
    [INFO] **************************************************************
    [INFO] Starting Jakarta Velocity v1.4
    [INFO] RuntimeInstance initializing.
    [INFO] Default Properties File: org/apache/velocity/runtime/defaults/velocity.properties
    [INFO] Default ResourceManager initializing. (class org.apache.velocity.runtime.resource.ResourceManagerImpl)
    [INFO] Resource Loader Instantiated: org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
    [INFO] ClasspathResourceLoader : initialization starting.
    [INFO] ClasspathResourceLoader : initialization complete.
    [INFO] ResourceCache : initialized. (class org.apache.velocity.runtime.resource.ResourceCacheImpl)
    [INFO] Default ResourceManager initialization complete.
    [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
    [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
    [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
    [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include
    [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
    [INFO] Created: 20 parsers.
    [INFO] Velocimacro : initialization starting.
    [INFO] Velocimacro : adding VMs from VM library template : VM_global_library.vm
    [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader.
    [INFO] Velocimacro : error using  VM library template VM_global_library.vm : org.apache.velocity.exception.ResourceNotFoundException: Unable to find resource 'VM_global_library.vm'
    [INFO] Velocimacro :  VM library template macro registration complete.
    [INFO] Velocimacro : allowInline = true : VMs can be defined inline in templates
    [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT replace previous VM definitions
    [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be  global in scope if allowed.
    [INFO] Velocimacro : initialization complete.
    [INFO] Velocity successfully started.
    [INFO] [hpi:create]
    Enter the groupId of your plugin: foo
    [INFO] Defaulting package to group ID: foo
    Enter the artifactId of your plugin: bar
    [INFO] ----------------------------------------------------------------------------
    [INFO] Using following parameters for creating Archetype: maven-hpi-plugin:1.34
    [INFO] ----------------------------------------------------------------------------
    [INFO] Parameter: groupId, Value: foo
    [INFO] Parameter: packageName, Value: foo
    [INFO] Parameter: basedir, Value: /
    [INFO] Parameter: package, Value: foo
    [INFO] Parameter: version, Value: 1.0-SNAPSHOT
    [INFO] Parameter: artifactId, Value: bar
    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] Failed to create a new Hudson plugin
    
    Embedded error: Error merging velocity templates
    /bar/pom.xml (No such file or directory)
    [INFO] ------------------------------------------------------------------------
    [INFO] Trace
    org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create a new Hudson plugin
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
            at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:585)
            at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
            at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
            at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
            at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create a new Hudson plugin
            at org.jvnet.hudson.maven.plugins.hpi.CreateMojo.execute(CreateMojo.java:195)
            at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
            ... 16 more
    Caused by: org.apache.maven.archetype.ArchetypeTemplateProcessingException: Error merging velocity templates
            at org.apache.maven.archetype.DefaultArchetype.processTemplate(DefaultArchetype.java:876)
            at org.apache.maven.archetype.DefaultArchetype.processTemplate(DefaultArchetype.java:730)
            at org.apache.maven.archetype.DefaultArchetype.processTemplates(DefaultArchetype.java:475)
            at org.apache.maven.archetype.DefaultArchetype.createArchetype(DefaultArchetype.java:329)
            at org.jvnet.hudson.maven.plugins.hpi.CreateMojo.execute(CreateMojo.java:174)
            ... 18 more
    Caused by: java.io.FileNotFoundException: /bar/pom.xml (No such file or directory)
            at java.io.FileOutputStream.open(Native Method)
            at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
            at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
            at org.apache.maven.archetype.DefaultArchetype.processTemplate(DefaultArchetype.java:866)
            ... 22 more
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 20 seconds
    [INFO] Finished at: Mon Apr 13 12:36:16 GMT-05:00 2009
    [INFO] Final Memory: 10M/19M
    [INFO] ------------------------------------------------------------------------
    
    
  20. Apr 27, 2009

    Fredrik Eldh says:

    When following the instructions above, and running mvn hpi:create I receive a me...

    When following the instructions above, and running mvn hpi:create I receive a message saying that it is missing: com.sun:tools:jar:1.5. When running in debug mode I can see that it is looking for the file C:\Program Files\Java\jdk1.6.0_13\..\lib\tools.jar. Where did the ..\ came from? My JAVA_HOME path is set to C:\Program Files\Java\jdk1.6.0_13. 

    Kindly regards,

    Fredrik

    1. Apr 27, 2009

      Fredrik Eldh says:

      It actually worked fine if I just changed the JAVA_HOME to the jre subfolder.

      It actually worked fine if I just changed the JAVA_HOME to the jre subfolder.

  21. May 27, 2009

    stuart barlow says:

    I am running instructions on wndows with java 1.5 on windows with mvn (Apache Ma...

    I am running instructions on wndows with java 1.5 on windows with mvn (Apache Maven 2.1.0 (r755702; 2009-03-18 19:10:27+0000)) and I get the following error...

    C:\stuartb\java\HUDSON~1>mvn -e hpi:create
    + Error stacktraces are turned on.
    [INFO] Scanning for projects...
    [INFO] Searching repository for plugin with prefix: 'hpi'.
    [INFO] org.jvnet.hudson.tools: checking for updates from m.g.o-public
    [WARNING] repository metadata for: 'org.jvnet.hudson.tools' could not be retrieved from repository: m.g.o-public due to
    an error: Error transferring file: maven.glassfish.org
    [INFO] Repository 'm.g.o-public' will be blacklisted
    [INFO] org.jvnet.hudson.tools: checking for updates from central
    [WARNING] repository metadata for: 'org.jvnet.hudson.tools' could not be retrieved from repository: central due to an er
    ror: Error transferring file: repo1.maven.org
    [INFO] Repository 'central' will be blacklisted
    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] The plugin 'org.apache.maven.plugins:maven-hpi-plugin' does not exist or no valid version could be found
    [INFO] ------------------------------------------------------------------------
    [INFO] Trace
    org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-hpi-plugin' does not
    exist or no valid version could be found
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1546)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1786)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto
    r.java:446)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:176)
            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
            at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:585)
            at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
            at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
            at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
            at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The plugin 'org.apache.maven.plugins:maven-hp
    i-plugin' does not exist or no valid version could be found
            at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.
    java:229)
            at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.
    java:91)
            at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:172)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1517)
            ... 14 more
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: < 1 second
    [INFO] Finished at: Tue May 26 12:08:54 BST 2009
    [INFO] Final Memory: 1M/3M
    [INFO] ------------------------------------------------------------------------
    C:\stuartb\java\HUDSON~1>
    

    Any thoughts on this?
    Looks like mvn is not all together happy. Possible network issue?
    The path to mvn is strewn with small hurdles. A clever but not simple build process.

    1. May 28, 2009

      stuart barlow says:

      Solved it! Hudson did not say anytyhing but this was a network proxy issue. Once...

      Solved it! Hudson did not say anytyhing but this was a network proxy issue. Once I had the proxy definded in the settings.xml file everything worked fine.
      Thanks mvn for hiding the real error.

      1. Jul 15, 2010

        Jeffrey Chyan says:

        Can you explain what you did? How do you define the proxy? I'm getting the same ...

        Can you explain what you did? How do you define the proxy? I'm getting the same error you did but I don't know how to fix it.

  22. Jun 02, 2009

    Gabriel Falkenberg says:

    If you get an error like this: [INFO] [hpi:apt-compile] [INFO] ------------...

    If you get an error like this:

    [INFO] [hpi:apt-compile]
    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] JDK6 or later is necessary to build a Hudson plugin
    [INFO] ------------------------------------------------------------------------
    

    when compiling on OS X even though java -version says you are using Java > 1.6 you might need to set JAVA_HOME manually to /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home or something like that, to be sure that maven uses JDK6.

  23. Jun 08, 2009

    Ola Johnsson says:

    I have a problem with running/debugging my plugin. I have set up everything acco...

    I have a problem with running/debugging my plugin. I have set up everything according to the guide and it compiles nicely. I can even create a .hpi-package and install in Hudson with the tutorial. But I can't seem to debug.

    I try to run "mvn hpi:run" which shows some output and from what I can see everything goes well, but I can't connect to localhost?

    Anyone that know what I have done wrong?

  24. Jul 15, 2009

    Heiko Janssen says:

    Hi,  I am totally new to hudson and want to write a plugin. So I followed ...

    Hi,

     I am totally new to hudson and want to write a plugin. So I followed the instructions on this site and did the following:

    01. Downloaded Maven 2.2.0

    02. Modified the Maven settings.xml file due to the xml snippet described on this page

    03. Want to setup a new plugin with mvn hpi:create

    The third step failed with the error message:

    [INFO] Internal error in the plugin manager executing goal 'org.jvnet.hudson.tools:maven-hpi-plugin:1.40:create': Unable to load the mojo 'org.jvnet.hudson.
    tools:maven-hpi-plugin:1.40:create' in the plugin 'org.jvnet.hudson.tools:maven-hpi-plugin'. A required class is missing: Lorg/apache/maven/archetype/Archetype; org.apache.maven.archetype.Archetype

    To resolve this problem I checked whether the class 'Archetype' is in the Maven repository on my disk. I found a directory in %USERPROFILE%\.m2\repository\org\apache\maven\archetype so I thought that I have to add this path to any Maven configuration file or something like this.

    Could anybody give me some suggestions or some keywords where I could read on to get started on writing the plugin?

    Kind regards,

    Heiko

    1. Jul 16, 2009

      Cameron Falkenhagen says:

      Hi, I am having the exact same issue with the exact same error. When I check th...

      Hi,

      I am having the exact same issue with the exact same error.
      When I check the ~/.m2 directory there is no archetype directory in ~/.m2/repository/org/apache/maven

      I'm new to Maven and Hudson plugin development, so it could easily be a rookie mistake.

      Thoughts?

  25. Jul 20, 2009

    oliviera - says:

    This thread of the mailing list may help you: http://www.nabble.com/Plugin-creat...
  26. Jul 28, 2009

    Adrian Smith says:

    Everything builds as described, but I can't get the plugin to show up anywhere i...

    Everything builds as described, but I can't get the plugin to show up anywhere in the running Hudson apart from on the installed plugins pages.

     What am I missing please?

    1. Nov 02, 2009

      Christophe Furmaniak says:

      If you are an eclipse user and that you used mvn eclipse:eclipse, check the JDK ...

      If you are an eclipse user and that you used mvn eclipse:eclipse, check the JDK compliance of your project. It is set by default to 1.5 but you have to force it to 1.6 and it will work.

    2. Aug 24, 2012

      Kolos Tatar says:

      I know this is an old thread, but this might save some time for other newbies - ...

      I know this is an old thread, but this might save some time for other newbies - I ran into this same problem and I was able to solve it by removing my custom groupId from the pom.

      Kolos

  27. Jan 08, 2010

    Russ Hickingbottom says:

    I am in the same boat as Adrian - I have it built, I have it installed but I don...

    I am in the same boat as Adrian - I have it built, I have it installed but I don't see anywhere where this manifests itself in my hudson instance?  Any ideas?  I checked my eclipse project and it is JDK 1.6 compliant.

    Any help would be appreciated.

    1. Dec 12, 2010

      Blaine Simpson says:

      An I am in the same boat as Adrian and Russ, a year later. Christophe's suggest...

      An I am in the same boat as Adrian and Russ, a year later.

      Christophe's suggestion doesn't help me as I am not using any IDE.  I'm using command line with OpenJDK 1.6 (except that for my standalone Hudson webapp I'm running Tomcat 6 with Sun JDK 1.6).

      I have the same exact situation as Adrian Smith explained, regardless whether I use "mvn...: run" or install the .hpi into a standalone Hudson webapp.

      As the problem persists after  year and a half, surely others will continue to run into this.  Could somebody give us a clue about where we should see the plugin in the Hudson UI?  Like on which Hudson page(s).  Seeing that the new plugin is a "Builder", I expected to see a new item on the Hudson "New Job" page, but I do not.

      I'm a tutorial writer, and I don't understand why somebody would dedicate the time to write one but end at the installation step-- giving no hint about how to use or verify the final product.

      1. Dec 12, 2010

        Blaine Simpson says:

        Sorry to self-reply, but I wanted to report back that my issues are resolved. T...

        Sorry to self-reply, but I wanted to report back that my issues are resolved.

        The reason it took me so long is that Hudson either does very little validation of installed plugins, or that validation is poor.  Hudson has no idea when incompatible and non-functional plugins are installed.

        The answer to my primary question is, when a plugin is installed successfully, a stanza for that plugin will appear in the global config page ("Configure System" link, URL /CONTEXT-ROOT/configure).  I deduced this after reading one of the Confluence pages about Jelly.

        My problems were due to not-knowing-where-to-look, compounded by building an incompatible version of the plugin.  When installing the plugin whose source was incompatible with my Hudson web app, the plugin did install but was crippled and did not appear on the global config screen.

        1. Sep 23, 2011

          Anna Pakkala says:

          Any chance you could share exactly how your plugin was incompatible and how you ...

          Any chance you could share exactly how your plugin was incompatible and how you fixed it (or did you?)

          I'm trying to build a plugin that is based on an existing (working) plugin, it does not show up but I have no idea how to debug it.

          1. Mar 29, 2012

            Yehui Wang says:

            I also couldn't find hello world builder in the global config page at the b...

            I also couldn't find hello world builder in the global config page at the beginning. But I change the version of jenkins in pom.xml to the newest one and rerun it, then it works. 

            <groupId>org.jenkins-ci.plugins</groupId>

                <artifactId>plugin</artifactId>

                <version>1.457</version><!-- which version of Jenkins is this plugin built against? --> 

  28. Jan 19, 2010

    Vedran Lerenc says:

    Hi, is there an update on the issue with missing class AnnotationProcessorFacto...

    Hi,

    is there an update on the issue with missing class AnnotationProcessorFactory?
    I used the hpi archetype from within Eclipse and set the version of the parent pom to the version I use of Hudson (also tried 1.323 and 1.310):

    <parent>
    <groupId>org.jvnet.hudson.plugins</groupId>
    <artifactId>plugin</artifactId>
    <version>1.329</version>
    </parent>

    What I get is similar to a former post here (it had no resolution):

    Internal error in the plugin manager executing goal 'org.jvnet.hudson.tools:maven-hpi-plugin:1.45:apt-compile': Unable to load the mojo 'org.jvnet.hudson.tools:maven-hpi-plugin:1.45:apt-compile' in the plugin 'org.jvnet.hudson.tools:maven-hpi-plugin'. A required class is missing: com/sun/mirror/apt/AnnotationProcessorFactory

    Does anyone have a hint for me?

    Thanks, Vedran

    1. Jan 19, 2010

      Vedran Lerenc says:

      After some deeper analysis, the problem was related to my JVM. It's slightly dif...

      After some deeper analysis, the problem was related to my JVM. It's slightly different and missed that class. Need to find out why, but since the hpi plugins expect the above mentioned class to be present they couldn't work in my case. Maybe declaring an explicit dependency could improve the situation? I found the class also in other artifacts on Maven Central and Glassfish (which first confused me), so others have repackaged the stuff (it's not strictly part of the main runtime libraries, but the apt tools library). Ok, that was just fyi. Cheers, Vedran

      1. Jan 19, 2010

        Sylvain V. says:

        Hello Vedran, I just started a plugin project with the tutorial, and had exactl...

        Hello Vedran,

        I just started a plugin project with the tutorial, and had exactly the same problem, so it is (probably) not specific of your installation.

        1. Jan 19, 2010

          Vedran Lerenc says:

          Hi Sylvain, at least in my case switching back to Sun Hotspot JVM of jdk1.6.0_16...

          Hi Sylvain, at least in my case switching back to Sun Hotspot JVM of jdk1.6.0_16 fixed the problem immediately and it works now for me. Regards, Vedran

          1. Jan 19, 2010

            Sylvain V. says:

            OK, after investigation, the issue for me is from Eclipse IAM (Maven integration...

            OK, after investigation, the issue for me is from Eclipse IAM (Maven integration) that does not include JDK jars (only JRE), so tools.jar is not included, even if everything is pointing on the JDK. Its a classical Eclipse/JRE/JDK classpath hell. It is not a hudson maven packaging issue (command-line maven works fine in all cases).

  29. Apr 01, 2010

    Thomas Wilson says:

    I created a new plugin using mvn -cpu hpi:create which went fine. The plugin...

    I created a new plugin using mvn -cpu hpi:create which went fine. The plugin worked for a while and I could modify it, adding new things and whatnot, but eventually I ended up with the following error. I also ended up with the error if I left the plugin untouched and just rebuilt it frequently. mvn clean does nothing to help the situation.

    [INFO] Compiling 6 source files to /home/thomas/Development/Java/Workspace/WorkOrder/test/target/classes
    Note: Generating com/thomaspwilson/HelloWorldBuilder.stapler
    Note: Generating com/thomaspwilson/HelloWorldBuilder/DescriptorImpl/doCheckName.stapler
    /home/thomas/Development/Java/Workspace/WorkOrder/test/src/main/java/com/thomaspwilson/HelloWorldBuilder.java:35: com.thomaspwilson.HelloWorldBuilder clashes with package of same name
    public class HelloWorldBuilder extends Builder {
           ^
    /home/thomas/Development/Java/Workspace/WorkOrder/test/target/generated-sources/localizer/com/thomaspwilson/HelloWorldBuilder/Messages.java:3: package com.thomaspwilson.HelloWorldBuilder clashes with class of same name
    package com.thomaspwilson.HelloWorldBuilder;
    ^
    /home/thomas/Development/Java/Workspace/WorkOrder/test/src/main/java/com/thomaspwilson/HelloWorldBuilder.java:35: com.thomaspwilson.HelloWorldBuilder clashes with package of same name
    public class HelloWorldBuilder extends Builder {
           ^
    /home/thomas/Development/Java/Workspace/WorkOrder/test/target/generated-sources/localizer/com/thomaspwilson/HelloWorldBuilder/Messages.java:3: package com.thomaspwilson.HelloWorldBuilder clashes with class of same name
    package com.thomaspwilson.HelloWorldBuilder;
    ^
    

    Does anyone have any ideas?

  30. May 02, 2010

    manohar says:

    Hello  All, Greetings for the day. I am working on Hudson Plugin develope...

    Hello  All,

    Greetings for the day.

    I am working on Hudson Plugin developement.

    Following steps i followed to develope huson plugin.

    1. installed maven 2.2.1

    2. executed command mvn -e -cpu  hpi:create

    3. It failed to complete with following exception. I would be good if you please help me.

    [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '9af237d289
    6530e8d4d661e448d0d46fe3783491'; remote = '0de20e1eea680fc277fddb66bc24ba40d4491
    68b' - IGNORING
    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] Internal error in the plugin manager executing goal 'org.jvnet.hudson.too
    ls:maven-hpi-plugin:1.51:create': Unable to load the mojo 'org.jvnet.hudson.tool
    s:maven-hpi-plugin:1.51:create' in the plugin 'org.jvnet.hudson.tools:maven-hpi-
    plugin'. A required class is missing: Lorg/apache/maven/archetype/Archetype;
    [INFO] ------------------------------------------------------------------------

    Can anyone please help me on this.. Thanks in Advance.

    Manohar

  31. May 05, 2010

    Mikael F says:

    When I do this:  $ cd newly-created-directory $ mvn package I can downlo...

    When I do this: 

    $ cd newly-created-directory

    $ mvn package

    I can download almost everything but then I get this error:

    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) org.jvnet.hudson.main:hudson-war:war:1.319

      Try downloading the file manually from the project website.

      Then, install it using the command:
          mvn install:install-file -DgroupId=org.jvnet.hudson.main -DartifactId=hudson-war -Dversion=1.319 -Dpackaging=war -Dfile=/path/to/file

      Alternatively, if you host your own repository you can deploy the file there:
          mvn deploy:deploy-file -DgroupId=org.jvnet.hudson.main -DartifactId=hudson-war -Dversion=1.319 -Dpackaging=war -Dfile=/path/to/file -Durl=[url] -Dreposito
    ryId=[id]

      Path to dependency:
            1) org.jvnet.hudson.plugins:email-ext:hpi:2.6-SNAPSHOT
            2) org.jvnet.hudson.main:hudson-war:war:1.319

    2) org.jvnet.hudson.main:hudson-war:jar:war-for-test:1.319

      Try downloading the file manually from the project website.

      Then, install it using the command:
          mvn install:install-file -DgroupId=org.jvnet.hudson.main -DartifactId=hudson-war -Dversion=1.319 -Dclassifier=war-for-test -Dpackaging=jar -Dfile=/path/to
    /file

      Alternatively, if you host your own repository you can deploy the file there:
          mvn deploy:deploy-file -DgroupId=org.jvnet.hudson.main -DartifactId=hudson-war -Dversion=1.319 -Dclassifier=war-for-test -Dpackaging=jar -Dfile=/path/to/f
    ile -Durl=[url] -DrepositoryId=[id]

      Path to dependency:
            1) org.jvnet.hudson.plugins:email-ext:hpi:2.6-SNAPSHOT
            2) org.jvnet.hudson.main:hudson-test-harness:jar:1.319
            3) org.jvnet.hudson.main:hudson-war:jar:war-for-test:1.319

    ----------
    2 required artifacts are missing.

    for artifact:
      org.jvnet.hudson.plugins:email-ext:hpi:2.6-SNAPSHOT

    from the specified remote repositories:
      m.g.o-public (http://maven.glassfish.org/content/groups/public/),
      central (http://repo1.maven.org/maven2)

    [INFO] ------------------------------------------------------------------------
    [INFO] For more information, run Maven with the -e switch
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 27 minutes 56 seconds
    [INFO] Finished at: Wed May 05 12:55:50 CEST 2010
    [INFO] Final Memory: 29M/69M
    [INFO] ------------------------------------------------------------------------

    So my question is what am I missing? I have tried diffrent plugin releases but still get the same error

  32. Dec 12, 2010

    Blaine Simpson says:

    Not fatal to the tutorial, since I can use the (very) long Maven plugin strings,...

    Not fatal to the tutorial, since I can use the (very) long Maven plugin strings, but the [Setting Up Environment] step above is completely useless for me.  Although I have put the setup.xml file in place, the mvn commands only work if I give the long strings.  I.e., hpi:ANYTHING does not work.

    As required by the instructions here, I am using a fairly recent version of Maven (ie. 2.0.9 or newer). Namely 3.0.1 (which they say is backwards compatible and still uses $HOME/.m2/setup.xml).  As of today, this is the main public release of Maven and the one recommended by the Maven project.

    Warning
    If (like me) you can't use short Maven plugin strings, do not supply a version number like "1.23" in [the tutorial] unless you really want to work with an old version of Hudson.

    If you want to deploy the .hpi to an app server and are running a recent Hudson distribution webapp, you will want to get the latest version of plugin source by specifying no version label.

  33. Dec 12, 2010

    Blaine Simpson says:

    The [Building a Plugin] section above is useless for the purpose stated....

    The [Building a Plugin] section above is useless for the purpose stated.

    mvn package

    does build the .hpi file at the indicated location, so

    mvn install

    is completely unnecessary for that purpose.

  34. Feb 12, 2011

    Larry Cai says:

    For chapter setting up environment , in nexus hints, "you can ignore these instr...

    For chapter setting up environment , in nexus hints, "you can ignore these instructions" it leads misunderstanding, since I think no matter nexus or not, we still need to set "org.jvnet.hudson.tools" for plugins group in settings.xml

  35. Mar 01, 2011

    Lubos Pochman says:

    I cannot run hpi:create target if settings.xml contains:     <...

    I cannot run hpi:create target if settings.xml contains:

        <pluginGroup>org.jenkins-ci.tools</pluginGroup>
        <pluginGroup>org.jenkins-ci.tools</pluginGroup>

    get error:

    $ mvn -e -cpu hpi:create

    + Error stacktraces are turned on.

    [INFO] Scanning for projects...

    [INFO] Searching repository for plugin with prefix: 'hpi'.

    [INFO] ------------------------------------------------------------------------

    [ERROR] BUILD ERROR

    [INFO] ------------------------------------------------------------------------

    [INFO] The plugin 'org.apache.maven.plugins:maven-hpi-plugin' does not exist or no valid version could be found

    [INFO] ------------------------------------------------------------------------

    [INFO] Trace

    org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-hpi-plugin' does not

    exist or no valid version could be found

            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1569)

    works fine with:

        <pluginGroup>org.jvnet.hudson.tools</pluginGroup>

    1. Mar 07, 2011

      Lubos Pochman says:

      <settings>  <!- Added Jenkins repositories ->  ...

      <settings>
       <!- Added Jenkins repositories ->
       <profiles>
         <profile>
           <id>jenkins</id>
           <activation>
             <activeByDefault>true</activeByDefault>
           </activation>
           <repositories>
             <repository>
               <id>java.net-m2-repository</id>
               <url>http://maven.jenkins-ci.org:8081/content/repositories/releases/
               </url>
             </repository>
           </repositories>
           <pluginRepositories>
             <pluginRepository>
               <id>jenkins-m2-repository</id>
               <name>Jenkins Plugin Repository</name>
               <url>http://maven.jenkins-ci.org:8081/content/repositories/releases/</url>
               <layout>default</layout>
             </pluginRepository>
           </pluginRepositories>
         </profile>
       </profiles>
       <pluginGroups>
         <pluginGroup>org.jenkins-ci.tools</pluginGroup>
       </pluginGroups>
      <!-- Hudson plugin group 
         <pluginGroups>
          <pluginGroup>org.jvnet.hudson.tools</pluginGroup>
        </pluginGroups>
      -->
      </settings>
      Thanks to Vojtech Juranek, here is working version of settings.xml:

      <settings>

       <!- Added Jenkins repositories ->

       <profiles>

         <profile>

           <id>jenkins</id>

           <activation>

             <activeByDefault>true</activeByDefault>

           </activation>

           <repositories>

             <repository>

               <id>java.net-m2-repository</id>

               <url>http://maven.jenkins-ci.org:8081/content/repositories/releases/

               </url>

             </repository>

           </repositories>

           <pluginRepositories>

             <pluginRepository>

               <id>jenkins-m2-repository</id>

               <name>Jenkins Plugin Repository</name>

               <url>http://maven.jenkins-ci.org:8081/content/repositories/releases/</url>

               <layout>default</layout>

             </pluginRepository>

           </pluginRepositories>

         </profile>

       </profiles>

       <pluginGroups>

         <pluginGroup>org.jenkins-ci.tools</pluginGroup>

       </pluginGroups>

      <!-- Hudson plugin group 

         <pluginGroups>

          <pluginGroup>org.jvnet.hudson.tools</pluginGroup>

        </pluginGroups>

      -->

      </settings>

  36. Mar 23, 2011

    Terence Miller says:

    Our Jenkins is in a DMZ, where we can't have acces to the jekins-ci.orh maven re...

    Our Jenkins is in a DMZ, where we can't have acces to the jekins-ci.orh maven repo. We haven our own nexus server  mirroing jenkins nexus. We can access our own nexus, where all jenkins plugins are mirrored. How can we creat an "update-center.json" file with our nexus domain url?

  37. Jun 17, 2011

    mark lemay says:

    Ok so after many attempts on both 2.2.1 and 3.0.x I always get the same inexplic...

    Ok so after many attempts on both 2.2.1 and 3.0.x I always get the same inexplicable JellyTestSuiteBuilder error in the "tests" phase.

    C:\eclipse\eclipse\stuff\aaaaaaahhh>mvn package \-e
    + Error stacktraces are turned on.
    \[INFO\] Scanning for projects...
    \[INFO\] \-----------------------------------------------------------------------\-
    \[INFO\] Building Unnamed - gggahhhh:aaaaaaahhh:hpi:1.0-SNAPSHOT
    \[INFO\] task-segment: \[package\]
    \[INFO\] \-----------------------------------------------------------------------\-
    \[INFO\] \[enforcer:display-info {execution: default}\]
    \[INFO\] Maven Version: 2.2.1
    \[INFO\] JDK Version: 1.6.0_26 normalized as: 1.6.0-26
    \[INFO\] OS Info: Arch: x86 Family: windows Name: windows xp Version: 5.1
    \[INFO\] \[localizer:generate {execution: default}\]
    \[INFO\] \[resources:resources {execution: default-resources}\]
    \[WARNING\] Using platform encoding (Cp1252 actually) to copy filtered resources,
    i.e. build is platform dependent\!
    \[INFO\] Copying 4 resources
    \[INFO\] \[hpi:apt-compile {execution: default-apt-compile}\]
    \[INFO\] Nothing to compile - all classes are up to date
    \[INFO\] \[access-modifier-checker:enforce {execution: default-enforce}\]
    \[INFO\] \[hpi:insert-test {execution: default-insert-test}\]
    \[INFO\] \[groovy:generateTestStubs {execution: test-in-groovy}\]
    \[INFO\] No sources found for Java stub generation
    \[INFO\] \[resources:testResources {execution: default-testResources}\]
    \[WARNING\] Using platform encoding (Cp1252 actually) to copy filtered resources,
    i.e. build is platform dependent\!
    \[INFO\] skip non existing resourceDirectory C:\eclipse\eclipse\stuff\aaaaaaahhh\s
    rc\test\resources
    \[INFO\] \[compiler:testCompile {execution: default-testCompile}\]
    \[INFO\] Nothing to compile - all classes are up to date
    \[INFO\] \[hpi:test-hpl {execution: default-test-hpl}\]
    \[INFO\] Generating C:\eclipse\eclipse\stuff\aaaaaaahhh\target\test-classes\the.hp
    l
    \[INFO\] \[hpi:resolve-test-dependencies {execution: default-resolve-test-dependenc
    ies}\]
    \[INFO\] \[groovy:testCompile {execution: test-in-groovy}\]
    \[INFO\] No sources found to compile
    \[WARNING\] DEPRECATED \[systemProperties\]: Use systemPropertyVariables instead.
    \[INFO\] \[surefire:test {execution: default-test}\]
    \[INFO\] Surefire report directory: C:\eclipse\eclipse\stuff\aaaaaaahhh\target\sur
    efire-reports
    
    \------------------------------------------------------\-
    &nbsp;T E S T S
    \------------------------------------------------------\-
    Running InjectedTest
    Exploding jenkins.war at \Redirected$\mlemay\.m2\repository\org\jenkins-ci\main\
    jenkins-war\1.399\jenkins-war-1.399-war-for-test.jar
    Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.437 sec <<< FA
    ILURE\!
    
    Results :
    
    Tests in error:
     org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite(org.jvnet.hudson.te
    st.junit.FailedTest): Failed to initialize exploded war
    
    Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
    
    \[INFO\] \-----------------------------------------------------------------------\-
    \[ERROR\] BUILD FAILURE
    \[INFO\] \-----------------------------------------------------------------------\-
    \[INFO\] There are test failures.
    
    Please refer to C:\eclipse\eclipse\stuff\aaaaaaahhh\target\surefire-reports for
    the individual test results.
    \[INFO\] \-----------------------------------------------------------------------\-
    \[INFO\] Trace
    org.apache.maven.BuildFailureException: There are test failures.
    
    Please refer to C:\eclipse\eclipse\stuff\aaaaaaahhh\target\surefire-reports for
    the individual test results.
     at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
    ultLifecycleExecutor.java:715)
     at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
    fecycle(DefaultLifecycleExecutor.java:556)
     at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
    ltLifecycleExecutor.java:535)
     at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
    dleFailures(DefaultLifecycleExecutor.java:387)
     at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
    ts(DefaultLifecycleExecutor.java:348)
     at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
    fecycleExecutor.java:180)
     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
     at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
     at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
    0)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
     at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
     at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    
     at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures
    .
    
    Please refer to C:\eclipse\eclipse\stuff\aaaaaaahhh\target\surefire-reports for
    the individual test results.
     at org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(Suref
    ireHelper.java:74)
     at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugi
    n.java:642)
     at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
    nManager.java:490)
     at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
    ultLifecycleExecutor.java:694)
     ... 17 more
    \[INFO\] \-----------------------------------------------------------------------\-
    \[INFO\] Total time: 52 seconds
    \[INFO\] Finished at: Fri Jun 17 16:52:40 EDT 2011
    \[INFO\] Final Memory: 46M/110M
    \[INFO\] \-----------------------------------------------------------------------\-
    

    (sorry about the escape chars) Any help at all would be much appreciated.

    1. Jun 23, 2011

      mark lemay says:

      For the record the cause of this problem was that the repo directory was, by def...

      For the record the cause of this problem was that the repo directory was, by default, on the network. The solution was making it local.

  38. Aug 26, 2011

    Bogdan Suta says:

    Hi, This may be a dumb problem, but I can't seem to build any plug-in from sourc...

    Hi, This may be a dumb problem, but I can't seem to build any plug-in from source.

    I followed the instructions on this page: installed Maven 3.0.3, edited the settingx.xml as instructed on this page, got the source for the Doxygen plug-in, ran 'mvn install' waited for a bit for all the packages to be downloaded and I finally got this:

     C:\Temp\jenkinsci-doxygen-plugin-197189b>mvn install
    [INFO] Scanning for projects...
    [INFO]
    [INFO] ------------------------------------------------------------------------
    [INFO] Building Jenkins Doxygen Plug-in 0.9
    [INFO] ------------------------------------------------------------------------
    [INFO]
    [INFO] --- maven-enforcer-plugin:1.0:display-info (default) @ doxygen ---
    [INFO] Maven Version: 3.0.3
    [INFO] JDK Version: 1.7.0 normalized as: 1.7.0
    [INFO] OS Info: Arch: x86 Family: windows Name: windows xp Version: 5.1
    [INFO]
    [INFO] --- maven-localizer-plugin:1.8:generate (default) @ doxygen ---
    [INFO]
    [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ doxygen
    ---
    [WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources,
    i.e. build is platform dependent!
    [INFO] Copying 3 resources
    [INFO]
    [INFO] --- maven-hpi-plugin:1.64:apt-compile (default-apt-compile) @ doxygen ---
    
    Aug 26, 2011 9:11:33 AM org.sonatype.guice.bean.reflect.NamedClass
    WARNING: Error injecting: org.jvnet.hudson.maven.plugins.hpi.AptCompiler
    java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory
            at java.lang.Class.getDeclaredConstructors0(Native Method)
            at java.lang.Class.privateGetDeclaredConstructors(Class.java:2404)
            at java.lang.Class.getDeclaredConstructors(Class.java:1853)
            at com.google.inject.spi.InjectionPoint.forConstructorOf(InjectionPoint.
    java:243)
            at com.google.inject.internal.ConstructorBindingImpl.create(ConstructorB
    indingImpl.java:96)
            at com.google.inject.internal.InjectorImpl.createUninitializedBinding(In
    jectorImpl.java:628)
            at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(Injec
    torImpl.java:835)
            at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecurs
    ive(InjectorImpl.java:769)
            at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(Injector
    Impl.java:254)
            at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImp
    l.java:205)
            at com.google.inject.internal.InjectorImpl.getInternalFactory(InjectorIm
    pl.java:843)
            at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorIm
    pl.java:957)
            at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java
    :990)
            at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java
    :951)
            at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java
    :1003)
            at org.sonatype.guice.bean.reflect.AbstractDeferredClass.get(AbstractDef
    erredClass.java:47)
            at com.google.inject.internal.InternalFactoryToProviderAdapter.get(Inter
    nalFactoryToProviderAdapter.java:40)
            at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(Pr
    oviderToInternalFactoryAdapter.java:46)
            at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.ja
    va:1021)
            at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(Provi
    derToInternalFactoryAdapter.java:40)
            at com.google.inject.Scopes$1$1.get(Scopes.java:59)
            at com.google.inject.internal.InternalFactoryToProviderAdapter.get(Inter
    nalFactoryToProviderAdapter.java:40)
            at com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:96
    8)
            at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.ja
    va:1014)
            at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:964)
            at org.sonatype.guice.bean.locators.LazyBeanEntry.getValue(LazyBeanEntry
    .java:79)
            at org.sonatype.guice.plexus.locators.LazyPlexusBean.getValue(LazyPlexus
    Bean.java:53)
            at java.util.AbstractMap.get(AbstractMap.java:182)
            at org.codehaus.plexus.compiler.manager.DefaultCompilerManager.getCompil
    er(DefaultCompilerManager.java:54)
            at org.jvnet.hudson.maven.plugins.hpi.AbstractCompilerMojo.execute(Abstr
    actCompilerMojo.java:260)
            at org.jvnet.hudson.maven.plugins.hpi.CompilerMojo.execute(CompilerMojo.
    java:111)
            at org.jvnet.hudson.maven.plugins.hpi.AptMojo.execute(AptMojo.java:24)
            at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
    BuildPluginManager.java:101)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
    .java:209)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
    .java:153)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
    .java:145)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
    ct(LifecycleModuleBuilder.java:84)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
    ct(LifecycleModuleBuilder.java:59)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu
    ild(LifecycleStarter.java:183)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
    eStarter.java:161)
            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
            at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
            at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
            at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:57)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:601)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
    cher.java:290)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
    a:230)
            at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
    uncher.java:409)
            at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
    352)
    Caused by: java.lang.ClassNotFoundException: com.sun.mirror.apt.AnnotationProces
    sorFactory
            at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(
    SelfFirstStrategy.java:50)
            at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm
    .java:244)
            at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm
    .java:230)
            ... 53 more
    
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 4.797s
    [INFO] Finished at: Fri Aug 26 09:11:33 EEST 2011
    [INFO] Final Memory: 9M/23M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.jenkins-ci.tools:maven-hpi-plugin:1.64:apt-co
    mpile (default-apt-compile) on project doxygen: Execution default-apt-compile of
     goal org.jenkins-ci.tools:maven-hpi-plugin:1.64:apt-compile failed: Guice provi
    sion errors:
    [ERROR]
    [ERROR] 1) Error injecting: org.jvnet.hudson.maven.plugins.hpi.AptCompiler
    [ERROR] at ClassRealm[plugin>org.jenkins-ci.tools:maven-hpi-plugin:1.64, parent:
     sun.misc.Launcher$AppClassLoader@2a340e]
    [ERROR] at ClassRealm[plugin>org.jenkins-ci.tools:maven-hpi-plugin:1.64, parent:
     sun.misc.Launcher$AppClassLoader@2a340e]
    [ERROR] while locating org.codehaus.plexus.compiler.Compiler annotated with @com
    .google.inject.name.Named(value=hpi-apt)
    [ERROR]
    [ERROR] 1 error: com/sun/mirror/apt/AnnotationProcessorFactory: com.sun.mirror.a
    pt.AnnotationProcessorFactory
    [ERROR] -> [Help 1]
    [ERROR]
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
    ch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR]
    [ERROR] For more information about the errors and possible solutions, please rea
    d the following articles:
    [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutio
    nException
    

    At this point, I am baffled. I tried to compile other plugins, but I get the same error. Any ideas?

    Thanks.

    1. Sep 21, 2011

      Oliver Giles says:

      I've been battling the same issue for the past couple of days on Arch Linux. It ...

      I've been battling the same issue for the past couple of days on Arch Linux. It used to work ok.

      $ java -version
      java version "1.7.0"
      Java(TM) SE Runtime Environment (build 1.7.0-b147)
      Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
      $ /opt/maven/bin/mvn -v
      Apache Maven 3.0.3 (rNON-CANONICAL_2011-03-19_21-46_root; 2011-03-20 10:46:53+1300)
      Maven home: /opt/maven
      Java version: 1.7.0, vendor: Oracle Corporation
      Java home: /opt/java/jre
      Default locale: en_US, platform encoding: UTF-8
      OS name: "linux", version: "2.6.39-arch", arch: "amd64", family: "unix"

      Any tips on how to advance from here are greatly appreciated

      1. Sep 26, 2011

        Oliver Giles says:

        I found the issue. Summarized from this thread : JDK version 7 has rem...

        I found the issue. Summarized from this thread : JDK version 7 has removed an API depended on by apt-compile. Fixed by depending on a newer jenkins plugin pom.xml.

        1. Nov 02, 2011

          Chris Jones says:

          To depend on a newer jenkins plugin: After running mvn hpi:create go into the n...

          To depend on a newer jenkins plugin:

          After running mvn hpi:create go into the new folder (called whatever your entered for artifactID) and modify the pom.xml file. The section of interest is:

          <parent>
              <groupId>org.jenkins-ci.plugins</groupId>
              <artifactId>plugin</artifactId>
              <version>1.399</version><!-- which version of Jenkins is this plugin built against? -->  
          </parent>
          

          Change the version to something more recent. I used 1.437 at the time of writing.

          Having never used maven, how to depend on a newer jenkins plugin pom.xml was not clear to me.

  39. Feb 24, 2012

    Oliver Hoffmann says:

    Hi, I'm using Maven with Eclipse and I don't have a mvn executable because Maven...

    Hi, I'm using Maven with Eclipse and I don't have a mvn executable because Maven is integrated in the Eclipse plugin structure.

    But I have a "New Maven Project" wizard in Eclipse. Does someone know how to create new Maven plugins suitable for Jenkins with this Maven-Eclipse-Integration (i.e. without the need for a standalone maven command-line version)?

  40. Mar 16, 2012

    Dhan Dark says:

    I get following error, multiple attempts. HTTP ERROR: 500INTERNAL_SERVER_ERRORR...

    I get following error, multiple attempts.

    HTTP ERROR: 500INTERNAL_SERVER_ERRORRequestURI=/job/test/configSubmit

    Caused by:java.lang.UnsupportedOperationException

    at org.jvnet.hudson.test.HudsonTestCase$TestBuildWrapper$TestBuildWrapperDescriptor.newInstance(HudsonTestCase.java:1962)
    at org.jvnet.hudson.test.HudsonTestCase$TestBuildWrapper$TestBuildWrapperDescriptor.newInstance(HudsonTestCase.java:1953)
    at hudson.util.DescribableList.rebuild(DescribableList.java:154)
    at hudson.model.Project.submit(Project.java:196)
    at hudson.model.Job.doConfigSubmit(Job.java:989)

  41. Jul 08, 2012

    Jamie Cramb says:

    Let's take a look at the source code. A plugin's main entry point is a PluginImp...

    Let's take a look at the source code. A plugin's main entry point is a PluginImpl class that extends from Plugin.

    Hey all, just getting started here and I've been working through this tutorial... is the above statement still correct? I don't think this matches the source code created by hpi:create any more.

  42. Sep 15, 2012

    punit jain says:

    hi i am trying to packaging this project using mvn package but getting one error...

    hi i am trying to packaging this project using mvn package but getting one error, here is the stack trace, can anyone please help me in this:

    C:\maven\punit>mvn package -e 
    [INFO] Error stacktraces are turned on. 
    [INFO] Scanning for projects... 
    [INFO] 
    [INFO] ------------------------------------------------------------------------ 
    [INFO] Building punit 1.0-SNAPSHOT 
    [INFO] ------------------------------------------------------------------------ 
    Downloading: http://repo.jenkins-ci.org/public/org/jenkins-ci/main/jenkins-test- 
    harness/1.466/jenkins-test-harness-1.466.jar 
    Downloading: http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/subversion 
    /1.26/subversion-1.26.jar 
    Downloading: http://repo.jenkins-ci.org/public/org/jenkins-ci/main/jenkins-war/1 
    .466/jenkins-war-1.466.war 
    Downloading: http://repo.jenkins-ci.org/public/org/jenkins-ci/main/jenkins-core/ 
    1.466/jenkins-core-1.466.jar 
    Downloading: http://repo.jenkins-ci.org/public/org/jenkins-ci/main/jenkins-war/1 
    .466/jenkins-war-1.466-war-for-test.jar 
    Downloaded: http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/subversion/ 
    1.26/subversion-1.26.jar (306 KB at 2.0 KB/sec) 
    [INFO] ------------------------------------------------------------------------ 
    [INFO] BUILD FAILURE 
    [INFO] ------------------------------------------------------------------------ 
    [INFO] Total time: 2:37:14.226s 
    [INFO] Finished at: Sat Sep 15 11:27:04 IST 2012 
    [INFO] Final Memory: 10M/27M 
    [INFO] ------------------------------------------------------------------------ 
    [ERROR] Failed to execute goal on project punit: Could not resolve dependencies 
    for project com.punit:punit:hpi:1.0-SNAPSHOT: The following artifacts could not 
    be resolved: org.jenkins-ci.main:jenkins-war:war:1.466, org.jenkins-ci.main:jenk 
    ins-core:jar:1.466, org.jenkins-ci.main:jenkins-test-harness:jar:1.466, org.jenk 
    ins-ci.main:jenkins-war:jar:war-for-test:1.466: Could not transfer artifact org. 
    jenkins-ci.main:jenkins-war:war:1.466 from/to repo.jenkins-ci.org (http://repo.j 
    enkins-ci.org/public/): GET request of: org/jenkins-ci/main/jenkins-war/1.466/je 
    nkins-war-1.466.war from repo.jenkins-ci.org failed: Read timed out -> [Help 1] 
    org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal o 
    n project punit: Could not resolve dependencies for project com.punit:punit:hpi: 
    1.0-SNAPSHOT: The following artifacts could not be resolved: org.jenkins-ci.main 
    :jenkins-war:war:1.466, org.jenkins-ci.main:jenkins-core:jar:1.466, org.jenkins- 
    ci.main:jenkins-test-harness:jar:1.466, org.jenkins-ci.main:jenkins-war:jar:war- 
    for-test:1.466: Could not transfer artifact org.jenkins-ci.main:jenkins-war:war: 
    1.466 from/to repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/): GET requ 
    est of: org/jenkins-ci/main/jenkins-war/1.466/jenkins-war-1.466.war from repo.je 
    nkins-ci.org failed 
    at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDe 
    pendencies(LifecycleDependencyResolver.java:210) 
    at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resol 
    veProjectDependencies(LifecycleDependencyResolver.java:117) 
    at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAr 
    eResolved(MojoExecutor.java:258) 
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor 
    .java:201) 
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor 
    .java:153) 
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor 
    .java:145) 
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje 
    ct(LifecycleModuleBuilder.java:84) 
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje 
    ct(LifecycleModuleBuilder.java:59) 
    at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu 
    ild(LifecycleStarter.java:183) 
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl 
    eStarter.java:161) 
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) 
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) 
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) 
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) 
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. 
    java:57) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces 
    sorImpl.java:43) 
    at java.lang.reflect.Method.invoke(Method.java:601) 
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun 
    cher.java:290) 
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav 
    a:230) 
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La 
    uncher.java:409) 
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java: 
    352) 
    Caused by: org.apache.maven.project.DependencyResolutionException: Could not res 
    olve dependencies for project com.punit:punit:hpi:1.0-SNAPSHOT: The following ar 
    tifacts could not be resolved: org.jenkins-ci.main:jenkins-war:war:1.466, org.je 
    nkins-ci.main:jenkins-core:jar:1.466, org.jenkins-ci.main:jenkins-test-harness:j 
    ar:1.466, org.jenkins-ci.main:jenkins-war:jar:war-for-test:1.466: Could not tran 
    sfer artifact org.jenkins-ci.main:jenkins-war:war:1.466 from/to repo.jenkins-ci. 
    org (http://repo.jenkins-ci.org/public/): GET request of: org/jenkins-ci/main/je 
    nkins-war/1.466/jenkins-war-1.466.war from repo.jenkins-ci.org failed 
    at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(D 
    efaultProjectDependenciesResolver.java:189) 
    at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDe 
    pendencies(LifecycleDependencyResolver.java:185) 
    ... 22 more 
    Caused by: org.sonatype.aether.resolution.DependencyResolutionException: The fol 
    lowing artifacts could not be resolved: org.jenkins-ci.main:jenkins-war:war:1.46 
    6, org.jenkins-ci.main:jenkins-core:jar:1.466, org.jenkins-ci.main:jenkins-test- 
    harness:jar:1.466, org.jenkins-ci.main:jenkins-war:jar:war-for-test:1.466: Could 
    not transfer artifact org.jenkins-ci.main:jenkins-war:war:1.466 from/to repo.je 
    nkins-ci.org (http://repo.jenkins-ci.org/public/): GET request of: org/jenkins-c 
    i/main/jenkins-war/1.466/jenkins-war-1.466.war from repo.jenkins-ci.org failed 
    at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDepe 
    ndencies(DefaultRepositorySystem.java:375) 
    at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(D 
    efaultProjectDependenciesResolver.java:183) 
    ... 23 more 
    Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: The follo 
    wing artifacts could not be resolved: org.jenkins-ci.main:jenkins-war:war:1.466, 
    org.jenkins-ci.main:jenkins-core:jar:1.466, org.jenkins-ci.main:jenkins-test-ha 
    rness:jar:1.466, org.jenkins-ci.main:jenkins-war:jar:war-for-test:1.466: Could n 
    ot transfer artifact org.jenkins-ci.main:jenkins-war:war:1.466 from/to repo.jenk 
    ins-ci.org (http://repo.jenkins-ci.org/public/): GET request of: org/jenkins-ci/ 
    main/jenkins-war/1.466/jenkins-war-1.466.war from repo.jenkins-ci.org failed 
    at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(Def 
    aultArtifactResolver.java:538) 
    at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArti 
    facts(DefaultArtifactResolver.java:216) 
    at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDepe 
    ndencies(DefaultRepositorySystem.java:358) 
    ... 24 more 
    Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not tra 
    nsfer artifact org.jenkins-ci.main:jenkins-war:war:1.466 from/to repo.jenkins-ci 
    .org (http://repo.jenkins-ci.org/public/): GET request of: org/jenkins-ci/main/j 
    enkins-war/1.466/jenkins-war-1.466.war from repo.jenkins-ci.org failed 
    at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(W 
    agonRepositoryConnector.java:951) 
    at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(W 
    agonRepositoryConnector.java:941) 
    at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask. 
    run(WagonRepositoryConnector.java:669) 
    at org.sonatype.aether.util.concurrency.RunnableErrorForwarder$1.run(Run 
    nableErrorForwarder.java:60) 
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor
    java:1110) 
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor 
    .java:603) 
    at java.lang.Thread.run(Thread.java:722) 
    Caused by: org.apache.maven.wagon.TransferFailedException: GET request of: org/j 
    enkins-ci/main/jenkins-war/1.466/jenkins-war-1.466.war from repo.jenkins-ci.org 
    failed 
    at org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:3 
    49) 
    at org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:3 
    10) 
    at org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:2 
    87) 
    at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:97) 
    at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61) 
    at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask. 
    run(WagonRepositoryConnector.java:601) 
    ... 4 more 
    Caused by: java.net.SocketTimeoutException: Read timed out 
    at java.net.SocketInputStream.socketRead0(Native Method) 
    at java.net.SocketInputStream.read(SocketInputStream.java:150) 
    at java.net.SocketInputStream.read(SocketInputStream.java:121) 
    at org.apache.maven.wagon.providers.http.httpclient.impl.io.AbstractSess 
    ionInputBuffer.read(AbstractSessionInputBuffer.java:187) 
    at org.apache.maven.wagon.providers.http.httpclient.impl.io.ContentLengt 
    hInputStream.read(ContentLengthInputStream.java:176) 
    at org.apache.maven.wagon.providers.http.httpclient.conn.EofSensorInputS 
    tream.read(EofSensorInputStream.java:138) 
    at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:493) 

    at org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:3 
    39) 
    ... 9 more 
    [ERROR] 
    [ERROR] Re-run Maven using the -X switch to enable full debug logging. 
    [ERROR] 
    [ERROR] For more information about the errors and possible solutions, please rea 
    d the following articles: 
    [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyReso 
    lutionException 

  43. Mar 11, 2013

    Sean Soh says:

    Hi, I'm interested in learning how to write new plugins for Jenkins,however I am...

    Hi, I'm interested in learning how to write new plugins for Jenkins,however I am quite new with using Maven.

    I was following this tutorial, when I ran the command:  mvn -U org.jenkins-ci.tools:maven-hpi-plugin:create

    I got the following error messsage. Any ideas? Thanks:

    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) com.sun:tools:jar:1.5

      Try downloading the file manually from the project website.

      Then, install it using the command:
          mvn install:install-file -DgroupId=com.sun -DartifactId=tools -Dversion=1.5 -Dpackaging=jar -Dfile=/path/to/file

      Alternatively, if you host your own repository you can deploy the file there:
          mvn deploy:deploy-file -DgroupId=com.sun -DartifactId=tools -Dversion=1.5 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

      Path to dependency:
            1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.95
            2) org.kohsuke.stapler:maven-stapler-plugin:jar:1.16
            3) com.sun:tools:jar:1.5

    ----------
    1 required artifact is missing.

    for artifact:
      org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.95

    from the specified remote repositories:
      repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/),
      central (http://repo1.maven.org/maven2)

    1. Mar 11, 2013

      Sean Soh says:

      A bit of googling and I found the problem: I was using JRE instead of a JDK. The...

      A bit of googling and I found the problem: I was using JRE instead of a JDK. The same issue is also discussed here:

      http://jenkins.361315.n4.nabble.com/com-sun-tools-jar-1-5-is-missing-td390964.html

      The versions which I'm using now which works for me are:

      1) apache-maven-3.0.5

      2) jdk1.6.0_43

  44. Apr 11, 2013

    Sebastien ANTOINE says:

    Hi, I have a problem on Eclipse when I want to import a maven jenkins plugin th...

    Hi,

    I have a problem on Eclipse when I want to import a maven jenkins plugin that I created before with mvn cli. I have some errors in my pom.xml

    Have you got any ideas ?

  45. Apr 17, 2013

    Kenny Ayers says:

    This tutorial directs users to compile with Maven 2, however the feedback I got ...

    This tutorial directs users to compile with Maven 2, however the feedback I got on the Jenkins google group directed me to use Maven 3 to properly compile the subversion-plugin (https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-dev/ccolOycM1gI).  Compilation fails using Maven 2 and JDK 1.6.0_24, but works with Maven 3.0.5.  This could be worth noting in this write-up if it's not a corner-case.

    Thank you,

    Kenny

    1. Apr 25, 2013

      Jesse Glick says:

      Right, will do.

      Right, will do.

  46. Jul 07, 2013

    Dave Kelsey says:

    used the plugin generator http://plugin-generator.jenkins-ci.org to create ...

    used the plugin generator http://plugin-generator.jenkins-ci.org to create a starter plugin.

    setup nexus adding the jenkins-ci proxy as described.

    followed instructions on this page for packaging the project:

    mvn package
    [INFO] Scanning for projects...
    [INFO]
    [INFO] ------------------------------------------------------------------------
    [INFO] Building awesome 1.0-SNAPSHOT
    [INFO] ------------------------------------------------------------------------
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 12.026s
    [INFO] Finished at: Sun Jul 07 10:24:51 PDT 2013
    [INFO] Final Memory: 10M/81M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal on project awesome: Could not resolve dependencies for project org.jenkins-ci.plugins:awesome:hpi:1.0-SNAPSHOT: Failure to 
    find org.netbeans.modules:org-netbeans-insane:jar:RELEASE72 in http://localhost:8081/nexus/content/groups/public was cached in the local repository, 
    resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced -> [Help 1]
    [ERROR]
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR]
    [ERROR] For more information about the errors and possible solutions, please read the following articles:
    [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
    
    

    When I browse in nexus I do see the org-netbeans-insane release.

    I deleted the cached copy under ~/.m2/repository then re-running mvn and mvn still can not find the org-netbreans-insane release.

    this 'awesome' plugin is not awesome.

  47. Aug 06, 2013

    ramya m says:

    Hi,    I started setting up plugin environment, but when i tried to c...

    Hi,

       I started setting up plugin environment, but when i tried to compile am getting the following error. Can you please help me how to overcome it...

    [ERROR] COMPILATION ERROR :
    [INFO] -------------------------------------------------------------
    [ERROR] error: error reading C:\Documents and Settings\Administrator\.m2\repository\org\jenkin
    s-ci\main\jenkins-core\1.509.2\jenkins-core-1.509.2.jar; error in opening zip file
    [ERROR] error: error reading C:\Documents and Settings\Administrator\.m2\repository\org\jenkin
    s-ci\main\jenkins-core\1.509.2\jenkins-core-1.509.2.jar; error in opening zip file
    [INFO] 2 errors
    [INFO] -------------------------------------------------------------
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 8.110s
    [INFO] Finished at: Tue Aug 06 18:28:19 GMT+05:30 2013
    [INFO] Final Memory: 19M/46M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5:compile (def
    ault-compile) on project build: Compilation failure: Compilation failure:
    [ERROR] error: error reading C:\Documents and Settings\Administrator\.m2\repository\org\jenkin
    s-ci\main\jenkins-core\1.509.2\jenkins-core-1.509.2.jar; error in opening zip file
    [ERROR] error: error reading C:\Documents and Settings\Administrator\.m2\repository\org\jenkin
    s-ci\main\jenkins-core\1.509.2\jenkins-core-1.509.2.jar; error in opening zip file
    [ERROR] -> [Help 1]
    [ERROR]
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR]
    [ERROR] For more information about the errors and possible solutions, please read the followin
    g articles:
    [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException