[
https://issues.jboss.org/browse/JGRP-1866?page=com.atlassian.jira.plugin....
]
Lukas Vlcek commented on JGRP-1866:
-----------------------------------
I have just reindexed project info data from Magnolina into DCP but it does not seem to do
any change to JGroups data. You can check directly the source data \[1\] that is being
indexed into DCP it still contains:
{code}
{
...
"sys_content_id" : "jgroups",
"sys_title" : "JGroups",
...
"committerGitLink" : "git@github.com:belaban/JGroups.git", //
<= is this the problematic data?
"committerLink" : "git@github.com:belaban/JGroups.git", // <=
is this the problematic data?
...
}
{code}
So either this needs to be updated in {{project.properties}} file (which is crawled by
Magnolia once a day automatically) or in Magnolia itself if the project does not use
{{project.properties}} file. Once this update is done, please let us know that we shall
reindex this data into DCP again.
\[1\]
http://www.jboss.org/rest/projectData
Broken Links on
JBoss.org
-------------------------
Key: JGRP-1866
URL:
https://issues.jboss.org/browse/JGRP-1866
Project: JGroups
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Daniel Coughlin
Assignee: Bela Ban
Fix For: 3.5
The following broken link is currently listed against this project on
www.jboss.org/projects.
git@github.com:belaban/JGroups.git - Committer Git
If you maintain a project.properties file that you have told the
jboss.org team about,
then you just need to fix it in there and the change will be reflected on the site.
Otherwise, you need to update the data on this project's Magnolia page.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)