search

jenkins-x / jx

Jenkins X provides automated CI+CD for Kubernetes with Preview Environments on Pull Requests using Cloud Native pipelines from Tekton
https://jenkins-x.io/
Apache License 2.0
4.57k stars 787 forks source link

Could not find a pack for Java. Trying to find the next likely language match... #2580

Closed MastanaGuru closed 5 years ago

MastanaGuru commented 5 years ago

Summary

Newbie to jenkins-x. Getting pack errors trying to run jx import for a Java Rest Service project

Steps to reproduce the behavior

jx import --url GitUrl performing pack detection in folder /Users/u740885/jxProjects/PMFSvc/ProviderMFSvc --> Draft detected Java (94.126469%) --> Could not find a pack for Java. Trying to find the next likely language match... --> Draft detected XML (3.107456%) --> Could not find a pack for XML. Trying to find the next likely language match... --> Draft detected RPM Spec (1.295966%) --> Could not find a pack for RPM Spec. Trying to find the next likely language match... --> Draft detected Eagle (0.858386%) --> Could not find a pack for Eagle. Trying to find the next likely language match... --> Draft detected Coq (0.433633%) --> Could not find a pack for Coq. Trying to find the next likely language match... --> Draft detected Java Server Pages (0.178090%) --> Could not find a pack for Java Server Pages. Trying to find the next likely language match... error: there was an error detecting the language using packs from /Users/u740885/jx/draft/packs/github.com/jenkins-x-buildpacks/jenkins-x-kubernetes/packs

Jx version

The output of jx version is:

NAME VERSION jx 1.3.688 jenkins x platform 0.0.3125 Kubernetes cluster v1.11.0+d4cacc0 kubectl v1.13.1 helm client v2.12.1+g02a47c7 helm server v2.12.1+g02a47c7 git git version 2.20.0 Operating System Mac OS X 10.14.2 build 18C54

Kubernetes cluster

minishift v1.28.0+48e89ed

Operating system / Environment

Expected behavior

Actual behavior

michaelneale commented 5 years ago

@jstrachan what should default for java be - does such a thing make sense or it needs to know what kind of java app?

jstrachan commented 5 years ago

we only have packs for common java build tools like maven, gradle, sbt.

I guess we could create a java pack which adds a dummy pom.xml so at least things can work when importing projects that don't have gradle or pom.xml files? We'd also need to try detect the src/main/java and src/test/java directories in case folk are importing a folder with arbitrary java files I guess

MastanaGuru commented 5 years ago

Sorry my bad. For the POC, I had created a new repo and missed copying the pom.xml. After copying it, the build works. The issue can be closed. Thanks.

michaelneale commented 5 years ago

yeah that makes sense - there is no generic way to "build java" in any case - there is no prescribed structure (other than the package paths, but that doesn't say where the root is, or what dependencies are) so not surprising. If anything if it sees no dependency thing like maven or gradle, but knows it is java, it probably needs to error out ideally.