Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-19449

p2.director install script is finding non-IU IUs to install

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 4.3.0.Alpha2
    • Fix Version/s: 4.3.0.Alpha2
    • Component/s: build
    • Labels:
      None
    • Sprint:
      Sprint #1 April 2015, Sprint #2 April 2015

      Description

      p2.director install script is finding non-IU IUs to install such as:

      eclipse.buildId
      java.version
      list.ius:
           [echo] Searching for IUs in http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Alpha2-SNAPSHOT/REPO/,http://download.jboss.org/jbosstools/mars/snapshots/builds/_composite_/core/master with -list 'Q:everything.select(y | everything.select(x | x.properties ~= filter("(org.eclipse.equinox.p2.bundle.localization='plugin')")).collect(x | x.requirements).flatten().exists(r | y ~= r))' ...
      
           [echo] Result: Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
           [echo] IU list written to /qa/hudson_workspace/workspace/jbosstools-composite-install_master/data/plugin.list.properties
      

      Full list here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_master/13118/console

      Reason: here's what's in the plugin.list.properties file:

      !SESSION 2015-03-13 18:06:15.934 -----------------------------------------------
      eclipse.buildId=4.5.0.I20150203-1300
      java.version=1.8.0_40
      java.vendor=Oracle Corporation
      BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
      
      !ENTRY org.eclipse.osgi 4 0 2015-03-13 18:06:17.233
      !MESSAGE The -clean (osgi.clean) option was not successful. Unable to clean the storage area: /qa/hudson_workspace/workspace/jbosstools-composite-install_master/eclipse/configuration/org.eclipse.osgi
      org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized.  Will retry after the state location is initialized.
      ch.qos.logback.classic=1.0.7.v20121108-1250
      ch.qos.logback.core=1.0.7.v20121108-1250
      ...
      tern.server.nodejs=0.9.0.201502141213
      ternjs=0.9.0.201502141213
      Operation completed in 183432 ms.
      

      So we need to filter out the header garbage.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  nickboldt Nick Boldt
                  Reporter:
                  nickboldt Nick Boldt
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: