Win a copy of 97 Things Every Java Programmer Should Know this week in the Java in General forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • salvin francis
  • fred rosenberger

Package doesn’t exist

 
Greenhorn
Posts: 10
Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Enterprise Project; Project Built on Pipeline;

Build Env: Maven , Java and Nexus

I am using dependency management to refer a particular package in Nexus. It’s a multi-module project. Dependencies are referred in dependeny management of Parent POM. The packages are available on Nexus. When I build the project on the pipeline, I am getting error: Package doesn’t exist.

For other projects built on the pipeline, I am not getting this error.

If I do a local build, I am getting the same error as well. I deleted the entire m2 repo for local build but it’s able to download the other dependencies from Nexus and not this one.


But if my team-mate downloads the code from github and does a local build, his build is successfull.

What might be the issue?

Note: I cannot post POM as I have restricted access to Internet.
 
Marshal
Posts: 69426
276
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What's the name of the package? Are you allowed to show us the line of code where the error occurs?
 
David Shawn
Greenhorn
Posts: 10
Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the reply. I am getting error on the library that's internally developed. I can't post the code/pom here as I have only restricted access to the internet.

There are 4 libraries in the package. All these 4 libraries of the package are available on Nexus. All these libraries are jar files. I am refering all the 4 libraries and of which, 3 libraries, I am not getting error. For the fourth one, I am getting error, "Package "package name" doesn't exist.

These libraries are used by many projects and for the other project, with the same reference, I am not getting error. In my team mate system, the build is successful. I am getting this error both on the local build as well as on the pipeline as well.
 
Saloon Keeper
Posts: 12012
257
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
To avoid confusion, please use 'package' to refer to a namespace for Java classes and resources, and 'artifact' to refer to the result of building a project.

We can't help you if you don't show us more. If you can't use internet at the office, crib down the relevant parts of the different POMs (at least 3 of them: the project that's giving you problems, the parent, and one of the projects that uses the same dependency and doesn't have issues), and also the complete and exact error message. We need to at least look at the <modules>, <parent>, <dependencyManagement> and <dependencies> of the POMs. It's fine if you use fake group and artifact names.
 
And then we all jump out and yell "surprise! we got you this tiny ad!"
Devious Experiments for a Truly Passive Greenhouse!
https://www.kickstarter.com/projects/paulwheaton/greenhouse-1
    Bookmark Topic Watch Topic
  • New Topic