Should be simple enough, I guess.
Behavior unclear however for suite component module projects. If copy is not
listed in suite module list, then should the copy still be a suite component
module? Or perhaps the copy should just be a standalone module in this case,
with the same platform as the suite had? (You could, I guess, then readd it to
the same suite or some other suite if you wanted to.)
Copying a suite project would I think need to copy all the suite component
module projects too. So maybe not so simple. :-) But can draw some inspiration
from J2EE impls.
High priority feature for the next release.
> ....for suite component module projects. If copy is not listed in suite
> module list, then should the copy still be a suite component module?
I don't understand. Suite component is always listed in some suite. Or do you
mean target directory in your context? I would just make a copy and make it
suite component. User can than remove it from its suite or move it to another
Copying suite is really a question. I'll have to setup J2EE, hopefully not
Aha, I see. You probably mean "If copy *is* listed in suite module list, then
should the copy still be a suite component module?"
Since than there would be a clash in the same CNBs. So we would have to either
make it standalone or somehow tweak CNB of a new one - e.g. original.cnb_copy or
original.cnb_1. But since it is not easy to change CNB it is odd to append some
Ideal would be if it is possible to tell what should be done. But again we would
need to enhance Project API.
I meant, if the original is a suite component module, do you add the copy to the
suite. For now I think no - make it standalone. Too hard to do right.
Ok, I'll do the basic version into 5.0u1.
Fixed for modules (not suite yet).
ui/ModuleActions.java; 1.19 -> 1.20;
ui/ModuleOperations.java; 1.4 -> 1.5;
I believe that usefulness for suite-copying is not so high. Very few usecases
probably. Will be implemented in the future. Filing a separate issue for it -