Quantcast
Channel: SCN : Discussion List - SAP NetWeaver Development Infrastructure (NWDI)
Viewing all articles
Browse latest Browse all 695

7.3 Components not building on NWDI 7.0

$
0
0

Hi All,

 

I am currently experiencing an issue with NWDI and am at a loss on how to proceed...

 

Environment:

 

CBS - Configured (to the best of our knowledge) to enable JDK1.6.0 builds but default to 1.4.2 builds

cbs.jpg

 

TRACK - The default build variant for our 7.3 track (new) is configured to use the JDK1.6 configured in the CBS settings:

Capture.PNG

 

As far as I can tell this configuration is correct. Our 7.0 tracks are still working albeit that the build plugin is now started with the JDK1.6.0 (as specified in BUILD_TOOL_JDK_HOME) but it forks a JDK1.4.2 compiler for the actual DC build (default key in JDK_HOME_PATHS).

 

For components in our 7.3 tracks however the builds are all failing. The request log looks fine but the build is failing stating 'compilation errors':

 

===== Processing =====  started at 2012-08-27 13:43:31.049 GMT

        BUILD DCs

            'customer.com/tools/crypto/list_providers/ep/comp' in variant 'default'

                .. FAILURE: The build failed due to compilation errors. See build log for details. [result code: 202]

    ===== Processing =====  finished at 2012-08-27 13:43:36.490 GMT and took 5 s 441 ms

 

The corresponding build log however do not show any errors but look like they just end prematurely. The last line is:

 

Start build plugin:

   using build plugin: sap.com/tc/bi/bp/portalapplication

   starting build plugin from : /usr/sap/DIP/JC23/j2ee/cluster/server0/temp/CBS/22/.B/11070/DCs/sap.com/tc/bi/bp/portalapplication/_comp/gen/default/public/def/

 

Normally I would expect a block of information about the build task/plugin after this line (plugin version, DC, SC, type, etc) but it EOF.

 

I cannot find any indication on the root cause of this in any other log file available to me. It is happening for all component types (lib,ep,web, etc).

 

Does anyone have any idea on how to approach this issue?

 

With kind regards,

Thijs Janssen


Viewing all articles
Browse latest Browse all 695

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>