How to create SCA-Files without sources?

[raphael_ostermann-goletz]

Hello,

even if we use the Build-Options "include_source = false" and "package type = Archive" (in effect there is no SOURCEARCHIVES-Folder in the sca-file) we found sources in our exported sca-file in the folder BUILDARCHIVES as zip-file "src.zip".

Because of copyright reasons we don't want to deliver source code, so the sca-file should be created without containing any .java-files.

Is there any option or function or method in NWDI (7.31) that prevents NWDI to put the src.zip into the sca-file?

Or do we have to delete e.g. the complete BUILDARCHIVES-Folder (as the simplest manual solution)?

Thanks for helping!

Greetings

Raphael Ostermann-Goletz

[junwu]

how u get ur sca?

[raphael_ostermann-goletz]

Yes, we assemble with the same options as presented in your picture.

The result is with src.zip in BUILDARCHIVES.

I've checked older sca-files (assembled with NWDI 7.30), and there the sources are missing in one track, but in an other track the sources are included.So there are differences between tracks and it seems as there is somewhere an option for this functionality?

[junwu]

"include source pointer in archive" can you try that one?

[ErvinSzolke]

Hi,

yes, normally that would be a solution. What you have to know is that source pointer means that instead of storing the sources in the SCA it only has links to the DTR where the sources are located.

This is useful because the size of the SCA will be smaller but the SCA will work only in that network this case where the DTR is accessible.

Cheers,

Ervin

[former_member193379]

Hi,

This selects source code that has been modified since the last assembly and only exports the delta to SCA. This significantly reduces import times if you have already imported predecessor and also significantly reduces assembly runtimes.

Thanks,

Hamendra

[raphael_ostermann-goletz]

Hello,

thank you for your comments! - I tested the option "include source pointer in archive" now several times an I can confirm Hamendra's restriction to delta sources. That means, even if the option is used, there is still source code in the sca (src.zip). Because we developed a full release, nearly the whole sources are included...

I tried another way by using another NWDI-Tool ("http://<domain:port>/SCD/SCDownload" - a tipp from our administrator, but he mentioned, that this is a tool just for testing, not for regular assembly and delivery). In that tool you can use the Option "without buildarchives" which eliminates this path totally from the sca and in effect there is no src.zip anymore. Is that option "without buildarchives" perhaps available in the regular assembly-process (e.g. as customizing in the depth of NWDI-tracks or environment)? Takes a missing BUILDARCHIVES an effect to the result of the deploy-process? (We just need the "executables" in the deploy system and no build Information.)

Best regards

Raphael

[junwu]

Package Types - Setting Up the Development Landscape: Landscape Configurator - SAP Library

[raphael_ostermann-goletz]

The track was still configured with package type "Archive" - and in fact the SOURCEARCHIVES is omitted, but the included BUILDARCHIVES contains the src.zip-file with the java-coding .

We use also the build variant "include_source = false", but that doesn't matter:

[junwu]

currently where you download the sca?

[raphael_ostermann-goletz]

We use the normal way over the NWDI. In the "final assembly" (FA) track we first import the components in the development (coming from another track over track connection), then consolidation, next assembly and export the sca finally. The FA-track is configured like mentioned above, so the SOURCEARCHIVES are standardly eliminated.
See picture for the FA-track: