Help coderanch get a
new server
by contributing to the fundraiser
  • 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Devaka Cooray
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Tim Moores
  • Carey Brown
  • Mikalai Zaikin
Bartenders:
  • Lou Hamers
  • Piet Souris
  • Frits Walraven

project.version folder is created in local maven repository

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
project.version folder is created in local maven repository - when the maven build is run in jenkin (in Windows 32) .

It works perfectly when manually done in console. (also it works fine with jenkin in Win 64)

The build error shown is :

Could not resolve dependencies for project x.y.z.ABC:jar:4.13-SNAPSHOT: The following artifacts could not be resolved: org.apache.httpcomponents:httpclient:jar:${project.version}, com.github.scribejava:scribejava-java8:jar:${project.version}: Could not find artifact org.apache.httpcomponents:httpclient:jar:${project.version} in central (https://repo.maven.apache.org/maven2) -> [Help 1]

PS: the pom file has explicit version mentioned for all jar libs. but above httpclient & scribejava-java8 are transitive dependencies

Yes of course : Could not find artifact org.apache.httpcomponents:httpclient:jar:${project.version}

because the maven generates above with hardcoding ${project.version} (interestingly it doesnt do such when run manually or when jenkin runs in other platforms)

Version Info : Apache Maven 3.8.4 , Java 17.0.1 , Windows 6.1 x86
 
Saloon Keeper
Posts: 15702
367
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Welcome to CodeRanch!

Please post your POM for us so we can try to reproduce the issue.
 
Saloon Keeper
Posts: 28054
198
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Welcome to the Ranch, Baru!

Why are you trying to run Jenkins on 32-bit Windows 7?  

Windows 7 is long past end-of-life. It gets no supports from Microsoft and more importantly, no security fixes. Actually, 32-bit OS support on almost any popular OS is pretty much dead these days.

If you're just trying to keep an older machine going, I'd recommend switching it from Windows to Linux. Linux can probably run 64-bit with Java 17 and Jenkins. The machine I do exactly that on is a no-name server built from cheap parts and I doubt it would run Windows 10, much less Windows 11. Since I don't run Windows at all, I don't care.

Not only would that sort of setup probably do you better than keeping an antique Windows alive, you don't have to pay for an OS license and paid support is optional. We provide lots of free support here on the CodeRanch, for example.
 
reply
    Bookmark Topic Watch Topic
  • New Topic