Grokbase Groups Maven dev August 2006
FAQ
http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins

I've written up my notes on what I have done to patch maven plugins
that describes how to build the trunk of a plugin, apply patches, and
deploy the plugin to an internal company repository.

I could not find anything like this in the documentation sets and I
needed it because I need to ensure my build process is working without
waiting for a plugin release. Hopefully it will be of use to other
people that need a stop gap solution.

I'd appreciate any feedback or alternative solutions people have.
My first attempt was to use the SNAPSHOT repositories but as soon as a
new SNAPSHOT was released I lost all my patches! Oops. I believe that
the way I am doing it now will mean I only need to check released
versions of the plugin and to re-apply the process only if my patches
are not in that release.

Thanks
Bae

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Search Discussions

  • Brett Porter at Aug 21, 2006 at 7:49 am
    Looks good!
    On 16/8/06 12:30 PM, Barrie Treloar wrote:
    http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins

    I've written up my notes on what I have done to patch maven plugins
    that describes how to build the trunk of a plugin, apply patches, and
    deploy the plugin to an internal company repository.

    I could not find anything like this in the documentation sets and I
    needed it because I need to ensure my build process is working without
    waiting for a plugin release. Hopefully it will be of use to other
    people that need a stop gap solution.

    I'd appreciate any feedback or alternative solutions people have.
    My first attempt was to use the SNAPSHOT repositories but as soon as a
    new SNAPSHOT was released I lost all my patches! Oops. I believe that
    the way I am doing it now will mean I only need to check released
    versions of the plugin and to re-apply the process only if my patches
    are not in that release.

    Thanks
    Bae

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
    For additional commands, e-mail: dev-help@maven.apache.org

    --
    Apache Maven - http://maven.apache.org/
    Better Builds with Maven - http://library.mergere.com/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
    For additional commands, e-mail: dev-help@maven.apache.org
  • Nathan Beyer at Aug 22, 2006 at 2:39 am
    One thing I noticed was the repository configurations. In particular the
    "releases" disabled and "snapshots" enabled. Like this:

    <repository>
    <id>apache.snapshots</id>
    <name>Maven Snapshots</name>
    <url>http://people.apache.org/maven-snapshot-repository</url>
    <releases>
    <enabled>false</enabled>
    </releases>
    <snapshots>
    <enabled>true</enabled>
    </snapshots>
    </repository>


    Have you tested this out? I've found that when 'releases' is disabled, the
    repository seems to be completely ignored if you're not using explicit
    dependency versions. For example, the dependency downloads if the version is
    "2-SNAPSHOT", but it doesn't if the version is "[1,3)". I'm still trying to
    track down exactly what's causing this for me, but I thought I'd check. I
    suspect it has something to do with ArtifactRepositoryMetadata's [1]
    isSnapshot()method being hardcoded to return false, but I'm still trying to
    narrow it down farther.

    [1]
    http://svn.apache.org/viewvc/maven/components/trunk/maven-artifact-manager/s
    rc/main/java/org/apache/maven/artifact/repository/metadata/ArtifactRepositor
    yMetadata.java?view=markup

    -Nathan
    -----Original Message-----
    From: Brett Porter
    Sent: Monday, August 21, 2006 2:44 AM
    To: Maven Developers List
    Subject: Re: Request for review of wiki notes on patching maven plugins

    Looks good!
    On 16/8/06 12:30 PM, Barrie Treloar wrote:
    http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins

    I've written up my notes on what I have done to patch maven plugins
    that describes how to build the trunk of a plugin, apply patches, and
    deploy the plugin to an internal company repository.

    I could not find anything like this in the documentation sets and I
    needed it because I need to ensure my build process is working without
    waiting for a plugin release. Hopefully it will be of use to other
    people that need a stop gap solution.

    I'd appreciate any feedback or alternative solutions people have.
    My first attempt was to use the SNAPSHOT repositories but as soon as a
    new SNAPSHOT was released I lost all my patches! Oops. I believe that
    the way I am doing it now will mean I only need to check released
    versions of the plugin and to re-apply the process only if my patches
    are not in that release.

    Thanks
    Bae

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
    For additional commands, e-mail: dev-help@maven.apache.org
  • Barrie Treloar at Aug 22, 2006 at 3:57 am

    On 8/22/06, Nathan Beyer wrote:
    One thing I noticed was the repository configurations. In particular the
    "releases" disabled and "snapshots" enabled. Like this: [del]

    Have you tested this out? I've found that when 'releases' is disabled, the
    repository seems to be completely ignored if you're not using explicit
    dependency versions. For example, the dependency downloads if the version is
    "2-SNAPSHOT", but it doesn't if the version is "[1,3)". I'm still trying to
    track down exactly what's causing this for me, but I thought I'd check. I
    suspect it has something to do with ArtifactRepositoryMetadata's [1]
    isSnapshot()method being hardcoded to return false, but I'm still trying to
    narrow it down farther.
    The purpose of this wiki page is to document how you would build the
    latest snapshot version of plugins. And since these plugins have yet
    to be released they are likely to depend upon snapshot versions.

    In the repository at
    <url>http://people.apache.org/maven-snapshot-repository</url> there
    should be no released versions. Al released versions would be
    available from central.

    Please start another thread and explain what you are trying to do as
    what you have written above would indicate that this post has no value
    to you and you should ignore it.

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
    For additional commands, e-mail: dev-help@maven.apache.org

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupdev @
categoriesmaven
postedAug 16, '06 at 2:31a
activeAug 22, '06 at 3:57a
posts4
users3
websitemaven.apache.org
irc#maven

People

Translate

site design / logo © 2021 Grokbase