Community
Participate
Working Groups
Jie Chen 08/10/2005 03:40:49 PM: > * For the PDE build, is there a way to split English and NL feature > packaging? The current PDE process seems always have the NL feature > packaged within the English feature (it probably because the English > feature includes the NL feature in the feature.xml file). Is there a > plan to make it happen in the future?
The packager just follows the inclusions clause of features. If the feature you are packaging includes the NL feature then obviously it will be included. Am I missing something? Can you provide an example?
Comment #1 From Pascal Rapicault 2005-08-10 23:19 >> Can you provide an example? Turns out this is an instance of a more general problem. Example from R*D: Peter Manahan 08/10/2005 09:31:34 PM: > From the install point of view the packages generated by a PDE are > fairly useless and currently they are opened up and ripped apart and > repackaged. The primary problem is that during the install we need > to provide the ability to select slices of function. For example NL. > The 6.0 RAD builds took features as input and spit out separate zip > files with the feature, the common plugins , the os specific > plugins/fragments, and the NL fragments/features. > So for a feature say com.ibm.web.tools which had nl and both win32, > linux fragments we got files like. > com.ibm.web.tools.feature.zip > com.ibm.web.tools.common.zip > com.ibm.web.tools.linux.zip > com.ibm.web.tools.windows.zip > com.ibm.web.tools.common.nl.zip > com.ibm.web.tools.linux.nl.zip
To be clear: attach to THIS bug report a simplified case of the problem you are seeing.
Closing as remind. Requested data not provided.