If you're just using project archives standard, and not mixing use of project archives with the server's view, then you should be 100% fine. This ID is the module id for each archive. This is so when you deploy a module, it can remember which module you're deploying.
Admittedly using an id like projectName:outputPath could have worked, but then any time hte package was changed, I'd have to refactor the id, or if the project was renamed, I'd have to refactor the id, and all of these things would lead to problems, specifically that if you had already deployed a project archives via the server's view, the OLD module would no longer be found (since hte module factory only has the new id) and, well, this is what we have now
So if you're mixing use with the server's view to deploy your project archives, you should definitely have different id's for each archive
Thanks Rob, that was a good explanation!
I'm indeed mixing Project Archives with the Server View and sometimes I do experience "problems" when undeploying an artifact.
When I remove any Project Archive artifact from any server I usually have to manually undeploy the artifact (by accessing the folder and deleting it), so that was not a bug, it was actually a "work-as-expected".
I'll spend some time to code some clever shell script to re-randomize all my ModuleIDPropertyKey.
Again, thanks a lot!
Rob, haven't we fixed this yet ?
The id should just be set to be the workspace path of the .archive file location if the ID is not specifically set (to work with existing ones).
WTP servers seem to handles renames of modules fine, why cant we ?