Community
Participate
Working Groups
Build Identifier: The feature is new since 3.6 but I think it should be improved significantly. I think we should only export the selected plugins (also only for the selected platform). Think about putting a exported target platform to version control... I only makes sense if only the selected files (plug-ins features) are added. and nothing more... to export the complete content (all plug-ins and features) does not make sense. I mean, the user defined the target platform with lots of work and then suddenly we copy just all the files ? please see my comments on http://aniszczyk.org/2010/04/09/pdes-export-target-wizard/ Reproducible: Always
What do you mean by selected plug-ins and features? The target export wizard should do exactly that, export all content from your current target.
have also a look at bug 304062 which needs the functionality
(In reply to comment #1) > What do you mean by selected plug-ins and features? The target export wizard > should do exactly that, export all content from your current target. In the target platform I can select _which_ plugins are necessary. (not all). The export wizard should only export the selected and necessary plugins not all content.
I think you mean a scenario were you add some features (whatever) and then on the Content page of the editor, deselect certain bundles. Right? I agree that the export should follow what is selected on the Content page
(In reply to comment #4) > I think you mean a scenario were you add some features (whatever) and then on > the Content page of the editor, deselect certain bundles. Right? I agree that > the export should follow what is selected on the Content page ok, thanks Jeff. I hopefully find the time to write a patch for this.
another usefull feature when _composing_ a target platform would be: - start with an empty target platform - I have a bunch of my plugins which require other plugins (for the target platform) - i would be useful if the target platform could be automatically derived from the manifest files from the above mentioned "bunch of my plugins) and add the necessary other plugins I think this would make sense. maybe I should open an own bug id for this ?
(In reply to comment #6) > I think this would make sense. maybe I should open an own bug id for this ? Feels like a different topic. FWIW, on the original topic, I should have a patch for this and the related bug 321870 later today.
(In reply to comment #7) > (In reply to comment #6) > > I think this would make sense. maybe I should open an own bug id for this ? > > Feels like a different topic. bug 329271 now covers this > > FWIW, on the original topic, I should have a patch for this and the related bug > 321870 later today. this is great news !
I've attached a patch to bug 321870 that should address the issue raised here as well as some other things.
Was this bug fixed by Jeffs patch? Should it be closed?
(In reply to comment #10) > Was this bug fixed by Jeffs patch? Should it be closed? Yes, Jeff's patch fixes the export so only the plug-ins selected on the content page are included. Closing as a duplicate. *** This bug has been marked as a duplicate of bug 321870 ***
