Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Component/s: jenkins-test-harness
-
Labels:None
-
Similar Issues:
Description
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. Jesse Glick 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.
Attachments
Issue Links
- relates to
-
JENKINS-24064 war-for-test makes for excessively large artifacts of Jenkins core
-
- Resolved
-
-
INFRA-1342 Deploy war-for-test artifacts for cores 2.64 through 2.79
-
- Closed
-
- links to
(4 links to)
Code changed in jenkins
User: Jesse Glick
Path:
src/main/java/org/jvnet/hudson/test/WarExploder.java
http://jenkins-ci.org/commit/jenkins-test-harness/b45ae9bb02999e82d14dd16f95c1b8fd2b277343
Log:
Merge pull request #73 from jglick/IDEA-is-broken-
JENKINS-45245JENKINS-45245Work around failure of IDEA to add jenkins-war.war to the test CPCompare: https://github.com/jenkinsci/jenkins-test-harness/compare/2a12efb35ad1...b45ae9bb0299