maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ziga GREGORIC <>
Subject Re: Stop offline mode artifact version renumbering
Date Sun, 28 Jul 2013 19:59:57 GMT
Hi Eric,

Not sure if I got you either, but see if this can help you out.

Where is the jetty with 'unwanted' version coming from? Use mvn
dependency:tree, but don't completely rely on results, as it is broken
(there's an issue on this in jira) and you might find the artifact, that
adds the wrong jetty as transitive dependency. For this artifact, add jetty
to excludes (in your pom - don't manipulate jetty poms). In case something
from jetty is now missing, add it in dependecies explicitly.

Another approach, which is easier but might not always work is to define
add dependencyManagement section and specify there all jetty versions you
want to use.

Forcing maven into taking what you have in the local repo by manipulating
local repo xml's scares me off. I'd trust pom.xml's of my project,
fine-tune it, test with -o on another box.


On Sat, Jul 27, 2013 at 3:48 AM, Ron Wheeler <
> wrote:

> I am not sure that I understand the problem but will version ranges in
> dependency specifications help?
> Ron
> On 26/07/2013 12:01 PM, Bahmer, Eric V wrote:
>> I've searched through a few years archives of the mailing list and can't
>> seem to find an answer to an issue that's been bugging me for a while now.
>> We've been using a highly customized third-party application for a while
>> now and are looking to upgrade to a newer version.
>> The new version uses maven for part of it's build process.
>> I work in an environment that for SECURITY reasons I must run my build in
>> OFFLINE mode.
>> I have already rebuilt over 600 rpms to have all the necessary
>> dependencies available locally.
>> The problem I'm having is this:
>> The project uses jetty, it calls for version 7.5.3 to be used, I have a
>> patched 8.1.0 installed.
>> Maven will resolve jetty correctly, however one of the jetty jars will
>> end up with it's version number altered in the distribution.
>> jetty-server-8.1.0.v20120127.**jar
>> jetty-servlet-8.1.0.v20120127.**jar
>> jetty-start-7.5.3.v20111011.**jar
>> This will not work as jetty-start reads it's own filename string and
>> attempts to load other jetty jars with the same version string.
>> I can get around the problem by replacing the jetty version number
>> <version.jetty> tag in the parent pom, which will make jetty-start have the
>> same 8.1.0 version number.
>> However, jetty isn't the only jar that this is happening to.
>> The overall project which isn't entirely java has a few sub-projects
>> built separately exhibiting this same behavior and I would rather avoid
>> replacing every version number in every pom or adding them if they don't
>> have them just so that all related packages like jetty, spring, or resteasy
>> have matching version numbers.
>> I also don't want several copies of the same jar with different filenames
>> because the version number is different for the sub-projects.
>> Otherwise I have to put a bunch of ugly loops in my rpm spec file to
>> clean up both before the build and after.
>> Is there a way to force resolution of my locally installed version
>> numbers and NOT rename the jar files to an incorrect version number? I've
>> already tried the versions plugin, the dependency plugin, -U,
>> -Dmaven.ignore.versions as well as combinations of them all.
>> I repeat that I have all necessary dependencies locally installed for
>> offline build. I know my versions work. I want maven to ignore what the
>> poms say about version and take the version number from what I have
>> installed.
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email:
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@maven.**<>
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message