-
Bug
-
Resolution: Fixed
-
Critical
-
None
Specifically seems to be maven-hpi-plugin 2.0 that's causing this, with the JENKINS-24064 fix. Now we get an error like
java.lang.AssertionError: jenkins.war is not in the classpath. If you are running this from the core workspace, run 'mvn install' to create the war image in war/target/jenkins
whenever trying to run tests. jglick says this is due to Intellij not honoring https://github.com/jenkinsci/maven-hpi-plugin/blob/137e435d0770f78edbbd2ed54d91809b7e7be5aa/src/main/resources/META-INF/plexus/components.xml#L134, so we need to figure out how to, like, get it to honor that.
- relates to
-
JENKINS-24064 war-for-test makes for excessively large artifacts of Jenkins core
-
- Resolved
-
- links to
(3 links to)
[JENKINS-45245] Cannot run tests in IntelliJ IDEA with plugin parent POM 2.30
Link |
New:
This issue relates to |
Component/s | New: jenkins-test-harness [ 21462 ] | |
Component/s | Original: core [ 15593 ] |
Remote Link | New: This issue links to "jenkins-test-harness PR 65 (Web Link)" [ 17194 ] |
Summary | Original: Cannot run tests in Intellij with plugin parent POM 2.31+ | New: Cannot run tests in IntelliJ IDEA with plugin parent POM 2.30 |
Assignee | New: Kohsuke Kawaguchi [ ci_jenkinsci_org ] |
Moving it to jenkins-test-harness since that is the immediate source of the error, though the changed behavior is actually in maven-hpi-plugin + plugin-pom and the fix probably needs to be in https://github.com/stapler/idea-stapler-plugin for which we have no apparent bug tracker.