Mark project as deprecated

[virmundi]

I recently had some difficulty with a deploy. I ended up deploying the same project under 3 different groupIds. While I did not knowingly promote two of them, they show up in the public search. I fear this will confuse people looking for the correct version.

I spoke with technomancy this evening. His advice was to re-deploy the two project "with 'ignore me' in the description". While this will work, it does lack a certain ease of use. An icon indicating that the project is deprecated or abandon on the search page would help out a lot. Projects could be deprecated via the profile/dashboard back-end.

Thanks,
JPD

[tobias]

I'm reluctant to add a deprecation button to the UI, but would be open to possibly excluding projects that have the exact text "DEPRECATED:" in the description from the search index. In your case, you also want to link to the correct project. I don't want to allow html in the description, but it wouldn't be difficult to parse dependency descriptors ([foo/bar "1.2.3"]) in the description, and link them to the correct project.

How does that sound?

[tobias]

@awb99 - I'm moving your discussion from #616 (comment) to here since this issue is a more appropriate place for it.

Is it possible to exclude DEPRECIATED artefacts from search? Or at least show them AFTER the non depreciated artefacts. We have reorganized our artefact system, and want to make sure that users do not get confused and by mistake use old versions. It is not very helpful, if the first couple of pages only show depreciated projects.

We have a few search related issues that I'd like to look at soon. If I'm able, I will include this as well.