Bug 415942 - Set 'code.ignoredWarnings' for test bundles in order to use global build settings
Summary: Set 'code.ignoredWarnings' for test bundles in order to use global build sett...
Status: VERIFIED FIXED
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.10.0 Luna   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: Luna M2   Edit
Assignee: John Arthorne CLA
QA Contact:
URL:
Whiteboard:
Keywords: test
Depends on:
Blocks: 401776
  Show dependency tree
 
Reported: 2013-08-27 06:57 EDT by Dani Megert CLA
Modified: 2013-09-05 03:45 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2013-08-27 06:57:52 EDT
Set 'code.ignoredWarnings' for test bundles in order to use the global build settings and reduce the discouraged access warnings in the official build.

The easiest way to do this is:

1. in the repository root add a folder 'tests-pom'
2. into the new folder add the following pom.xml:
     http://git.eclipse.org/c/pde/eclipse.pde.ui.git/plain/tests-pom/pom.xml
3. adjust the parent group and artifact id in that file
4. in each test bundle modify the pom.xml as follows:
   a) replace the parent artifact id with "tests-pom"
   b) add this to the parent declaration:
      <relativePath>../../tests-pom/</relativePath>

As a template you can use e.g. http://git.eclipse.org/c/pde/eclipse.pde.ui.git/
Comment 1 John Arthorne CLA 2013-09-04 14:11:11 EDT
I have added a test parent pom, but not yet linked it from the test bundles. I'm no pom expert so could use a second set of eyes on it. There is a slight difference from Dani's instructions: p2 already has a releng folder for additional pom.xml files so I put the "test parent" in there. I made the parent of the "test parent" to be the "p2 parent" that is the common parent of all p2 pom.xml files.
Comment 3 David Williams CLA 2013-09-04 19:08:28 EDT
FWIW, a test build at least completed. Not sure if it "worked" as you wanted, but these build results are here: 

http://build.eclipse.org/eclipse/builds/4I/siteDir/eclipse/downloads/drops4/I20130904-1455/testResults.php

(And these "test builds" don't have unit tests ran ... just confirming you didn't "break the build" :)
Comment 4 Dani Megert CLA 2013-09-05 03:45:38 EDT
Verified in I20130904-2000.