Community
Participate
Working Groups
When enabling/disabling package artifacts, and in other situations as well, it is possible ot get a mixture of package icons of both the Tigerstripe and "built-in versions. Its not yet been possible to spot a pattern, but its very frequent.
*** Bug 246856 has been marked as a duplicate of this bug. ***
Case 1: Packages are in the profile, and then disabled - any EMPTY packages do not get updated with the internal TS icon.
Actually case 1 should have said they don't get the eclipse icon Case 2: The opposite - if there is an empty package, then the icon doesn't get changed to the TS one.
Trying to build a summary of example cases: 1. Empty packages will not be treated a "package artifacts" because the list of packages is built up from existing "real" artifacts. 1.a This also means that you can't "Open in Package Artifact Editor", an empty package (that wasn't created with the Artifact Wizard or API). 1.b These empty packages might arise because of the project not having package artifacts when it was created.
Duncan, can you see if yo can work out WHEN this happens... not necessary for you to fix it (yet :-)) RC
I seem to get the Package icon all the time irrespective of the Profile setting for Package on the artifacts tab of the Profile. Other strange behaviour is that if Package is not checked on the artifacts tab of the Profile I still get the Package artifact form to edit when I create the Package (which I should not). And can open it for edit at any time. In summary it seems as if the Profile is ignored and Package artifacts are enabled all the time.
There was an earlier defect fixed, which resolved the package icon issue. I tried reproducing this problem with no luck. Please reopen if you're still able to reproduce it.