Skip to content
Commits on May 6, 2013
  1. Update plexus-utils to 3.0

    committed May 6, 2013
  2. Update maven-archiver to 2.5

    committed May 6, 2013
Commits on May 2, 2013
  1. @jglick

    Use current LTS: 1.509.1.

    jglick committed May 2, 2013
Commits on Feb 28, 2013
  1. @kohsuke
  2. @kohsuke
  3. @kohsuke

    The default dependency resolution scope should be "test".

    This only needs to be "compile" for those plugins that are bundled with the core.
    The "test" scope brings in some of the useful development-time plugins, such as ui-samples.
    It also allows the plugin developers to add plugins that are convenient when interactively testing the plugin.
    kohsuke committed Feb 28, 2013
  4. @kohsuke

    Fixed the discrepancy between the hpl file and plugins staged.

    Talking to Max wrt Jenkow plugin revealed this problem.
    
    As the code was written, the "compile" scope was used to place plugins
    to work/plugins, while the "test" scope was used to generate a list of
    dependencies in the generated .hpl file for the current plugin.
    
    With this, we end up producing more in the "Dependencies" field of the
    hpl file than what's available in work/plugins, so at the start-up the
    plugin currently developed will fail to load, citing missing
    dependencies.
    
    The hpl generation code needs to use the same dependency scope as
    the RunMojo to avoid this.
    kohsuke committed Feb 28, 2013
Commits on Feb 22, 2013
  1. @kohsuke
  2. @kohsuke
  3. @kohsuke

    restored parity between hpi:run and packaging.

    The Libraries path should contain the exact same thing, which in turn allows us to use <pluginFirstLoader> correctly to mask some classes.
    kohsuke committed Feb 22, 2013
Commits on Feb 21, 2013
  1. @jglick
Commits on Jan 7, 2013
  1. @jglick
Commits on Jan 4, 2013
  1. @kohsuke
  2. @kohsuke
  3. @kohsuke

    Restricting what classes the web application sees.

    Previously, we were using the classloader of this Maven plugin as the parent of the web application classloader. We were blacklisting some classes that are causing conflicts with Jenkins, but this is a catch-up game that you can never win.
    
    A better way to do this is by white-listing. We'll only let the web application see the servlet classes (and other JCP APIs if there's any, such as JSP and JSTL related ones.), then delegate straight to JavaSE. Note that for this to work, those exposed APIs must not have any visible dependencies to other non-exported classes. I believe APIs do satisfy that constraints.
    
    The immediate motivation of this was the Jenkow plugin, which required Xalan 2.7.5-ish, whereas this plugin was exposing Xalan 2.6.0
    kohsuke committed Jan 3, 2013
Commits on Dec 20, 2012
  1. @kohsuke
  2. @kohsuke
  3. @kohsuke

    added support for Global-Mask-Classes. See ClassicPluginStrategy in J…

    …enkins 1.496 for how the core uses this.
    kohsuke committed Dec 19, 2012
Commits on Nov 24, 2012
  1. @kohsuke
Commits on Sep 19, 2012
  1. @kohsuke
  2. @kohsuke
  3. @kohsuke
Commits on Aug 30, 2012
  1. @kohsuke
  2. @kohsuke
  3. @kohsuke
  4. @kohsuke

    encourage default groupID

    kohsuke committed Aug 29, 2012
Commits on Aug 28, 2012
  1. @kohsuke
  2. @kohsuke
Commits on Aug 27, 2012
  1. @imod
  2. @imod
  3. @imod
  4. @imod
Commits on Aug 25, 2012
  1. @imod
  2. @imod
Commits on Aug 22, 2012
  1. @jglick

    Should also pass over SCOPE_TEST dependencies.

    Otherwise during hpi:run (or hudson-dev:run) is muddied with things like org.jvnet.hudson.test.SleepBuilder.DescriptorImpl.
    (Worse, in cases like SleepBuilder, there is no *.jelly so attempting to add the builder results in an exception when you submit.)
    This is because the.hpl (for example of ui-samples-plugin) includes jenkins-test-harness.jar.
    Simplifying to use getRuntimeClasspathElements, which is what is actually wanted here.
    jglick committed Aug 22, 2012
Something went wrong with that request. Please try again.