"artifact_id";"status_id";"status_name";"priority";"submitter_id";"submitter_name";"assigned_to_id";"assigned_to_name";"open_date";"close_date";"last_modified_date";"summary";"details";"_votes";"_voters";"_votage";"Component";"Product";"Operating System" 1265;1;"Open";5;910;"";100;"Nobody";"2011-01-26 09:34";"";"2011-01-26 09:34";"Modify Receiver ID in Feature.xml file";"The dll files get signed with a snk-file. Depending on this file, an id is generated and the dll is registered under this id. This id has to be put in the feature.xml file. Unfortunately wspbuilder does not change this id. As the wspbuilder-plugin already modifies the version-parameters in the file, it should change the receiver id as well. In a perfect world this id would get generated from a snk-file-parameter runtime but as a workaround it would also be possible to ask for the id as a required parameter.";0;0;0;"None";"None";"None" 1266;1;"Open";3;910;"";100;"Nobody";"2011-01-26 09:50";"";"2011-01-26 09:50";"dll version number: exchange last int with yymmdd-stamp";"The poms version number should get transferred from maven version to microsoft-version by the addin BEFORE compile. As a preparation. It should be a seperate goal and get fired in the lifecycle before any of the npanday plugins. We can change the last int value to a yymmdd timestamp in the dll as well as the feature.xml. Do not try to add more information than this as the integer has a maxvalue (65k). This will avoid future problems with how npanday handles maven version numbers too.";0;0;0;"None";"None";"None"