Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6662557
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T02:24:08+00:00 2026-05-26T02:24:08+00:00

We are using Maven 2.2.1 version . I have an existing POM.xml file ,

  • 0

We are using Maven 2.2.1 version .

I have an existing POM.xml file , in that i have observed a lot of jars
were mentioned with the version 99.1 , look this below :

<dependency>

            <dependency>
                <groupId>org.apache.geronimo.specs</groupId>
                <artifactId>geronimo-jaxws_2.1_spec</artifactId>
                <version>99.1</version>
                <scope>provided</scope>
            </dependency>

            <dependency>
                <groupId>org.apache.geronimo.specs</groupId>
                <artifactId>geronimo-ws-metadata_2.0_spec</artifactId>
                <version>99.1</version>
                <scope>provided</scope>
            </dependency>

Later i have chnaged the versions from 99.1 to exact version (For example in case of
geronimo-jaxws_2.1_spec jar i mentioned version as 1.7.1 )

Now this looks like this

<dependency>
                <groupId>org.apache.geronimo.specs</groupId>
                <artifactId>geronimo-jaxws_2.1_spec</artifactId>
                <version>1.7.1</version>
                <scope>provided</scope>
            </dependency>

The application got compiled , and its BUILD SUCCESSFUL .

But i dont know , chnaging like this will impact anything ??

And also i observed that for some of the jars on to dependency tag there is no version tag ?? Is this acceptable ??

Please tell me , Thank you very much .

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T02:24:08+00:00Added an answer on May 26, 2026 at 2:24 am

    If everything works and you know that 1.7.1 is correct version than you have no problem. Unfortunately there are all kind of version naming schemes that make it hard sometimes to figure what is what. So it’s not clear what version 99.1 corresponds to. I seen this kind of situations with other products as well.

    And also i observed that for some of the jars on to dependency tag there is no version tag > ?? Is this acceptable ??

    Versions are probably defined in the parent pom in dependencyManagement section. In this case children poms will not need explicit version specified.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have this lines under our pom.xml file <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>2.3.2</version> <configuration> <jdkLevel>1.6</jdkLevel>
We're using maven 2.1.0. I have multiple modules that are completely separate, but still
I have to build an application using Maven for PHP that has multiple modules.
I've recently started using Gradle and replacing my existing Maven-based projects. I have had
We are using Maven(3.0.3) as build tool and we need to have different version
I have the following dependency in my pom.xml <dependency> <groupId>aGroup</groupId> <artifactId>anArtifact</artifactId> <version>aVersion</version> </dependency> I
We are using Maven 3.0.3. We have deployed a JAR file to an internal
We are using Maven for a large build process (> 100 modules). We have
I'm using Maven in the context of another build-tool (leiningen for Clojure, but this
I'm using a maven plugin that defines a custom packaging type and lifecycle for

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.