Community
Participate
Working Groups
if you run the metadata generator in -inplace mode and set -publishArtifacts then all the artifacts in the repo are vaporized. As in the files on disk are deleted. Austensibly this is caused by the repo thinking it was out of sync (the index says there isnt such an artifact but the disk has one) so we toast the "old" one and then go to copy the new one in. Of course, the new one is the old one and well, not happy. the obvious answer is to say well, if the source and the destingation are the same, don't delete anything and call it a day. We are so good at information hiding and separating concerns however that we do not have the source and destination addresses available together anywhere that I can see.
I saw the same vaporization when using the metadata generator with this args: -source ${LOCATION} \ -metadataRepository file:${LOCATION} -metadataRepositoryName "${NAME} Updates" \ -artifactRepository file:${LOCATION} -artifactRepositoryName "${NAME} Artifacts" \ -site file:${LOCATION}/site.xml Generator reported: Generation completed with success [0 seconds]. After this "success" directories features/ and plugins/ are empty. This could also be related to bug 233240? But I'm not signing any artifacts nor do I see a sign of an OOME. FYI: the whole content of ${LOCATION} was freshly generated from the IDE using an update site project. After performing "Build All" the generated content.xml lacked any trace of the categories I had defined in the site.xml editor. That's why I launched the metadata generator outside the IDE. Now I need to export all features and plugins again, after which I will find that the categories are missing from content.xml so I will want to run the metadata generator again, which will be happy to eat my artifacts, after which I will have to ...
Created attachment 107008 [details] patch
Patch was reviewed with John and is now released to 3.4.1 and HEAD
