Re: How to build custom inhouse maven release?

> Change all the 2.0.9's you find in there...there is also a property in
>  the root pom that has 2.0.9.
>
>
>
>  -----Original Message-----
>  From: Luke Patterson [mailto:lukewpatterson@...]
>  Sent: Wednesday, April 30, 2008 10:20 AM
>  To: Maven Developers List
>  Subject: Re: How to build custom inhouse maven release?
>
>  I'd like to know too.  I'm also using a custom version.
>
>  I am waiting on:
>
>  http://jira.codehaus.org/browse/MNG-3380
>
>
>  On 4/30/08, Joshua ChaitinPollak <jpollak@...> wrote:
>  >
>  > Hello,
>  >
>  > I just submitted a patch for this bug:
>  >
>  > http://jira.codehaus.org/browse/MNG-3559
>  >
>  > I don't know if it is the 'correct' fix, but it does the job for my
>  issue.
>  >
>  > Unfortunately, I can't want for a new Maven release, so I need to
>  build an
>  > in-house version with this patch to deploy to my development team. I'm
>  > building off the maven 2.0.9 tag, and tried tweaking the top level
>  pom's
>  > version to be 2.0.9.1 and that didn't seem to work (mvn package still
>  > built 2.0.9).
>  >
>  > How would I change the Maven version number?
>  >
>  > Is there a best practice for naming an in house version? I was
>  thinking of
>  > something like 2.0.9-kiva-1.
>  >
>  > Last question: Is there any way I can ease deployment of this version
>  via
>  > our shared in-house repository? If it was a plugin I would just upload
>  it
>  > into the repo and change our project's dependency, but in this case
>  its
>  > Maven it self. I think I need everyone to download the tar.bz or zip
>  and
>  > install it, right?
>  >
>  > Thanks,
>  >
>  > Josh
>  >
>  > --
>  > Joshua ChaitinPollak | Software Engineer
>  > Kiva Systems, Inc., 225 Wildwood Ave, Woburn, MA 01970
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: dev-unsubscribe@...
>  For additional commands, e-mail: dev-help@...
>
>