Bug 478855 - Referenced resources cannot be found - plugin.xml
Summary: Referenced resources cannot be found - plugin.xml
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: 2.6   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 2.7   Edit
Assignee: Frank Becker CLA
QA Contact:
URL:
Whiteboard:
Keywords: Documentation
Depends on:
Blocks:
 
Reported: 2015-10-01 17:11 EDT by Amr Dawood CLA
Modified: 2015-11-18 01:32 EST (History)
4 users (show)

See Also:


Attachments
Two missing files in Mylyn (116.86 KB, image/jpeg)
2015-10-01 17:11 EDT, Amr Dawood CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Amr Dawood CLA 2015-10-01 17:11:55 EDT
Created attachment 256985 [details]
Two missing files in Mylyn

Two files are missing:
"help/Mylyn WikiText User Guide-toc.xml"
&
"help/devguide/WikiText Developer Guide-toc.xml". 

Two errors whose messages say: "Referenced resource 'help/Mylyn WikiText User Guide-toc.xml' in attribute 'file' cannot be found" and "Referenced resource 'help/devguide/WikiText Developer Guide-toc.xml' in attribute 'file' cannot be found" appear in eclipse.
Comment 1 Jeremie Bresson CLA 2015-10-16 02:02:08 EDT
I have discussed this point on the mailing list [1]. It is my point (3).

In a fresh Mylyn Docs workspace you have 2 errors marker:

> Referenced resource 'help/Mylyn WikiText User Guide-toc.xml' in attribute 'file' cannot be found (Line 15)
> Referenced resource 'help/devguide/WikiText Developer Guide-toc.xml' in attribute 'file' cannot be found (Line 16)

The files are really missing because they will be created during the build (based on the corresponding "*.textile" files in the "org.eclipse.mylyn.wikitext.help.ui/help" folder).

You can:
a/ ignore those errors (you can delete them from the problem view).
b/ create the missing files manually (an empty file is enough).
c/ run a maven build ("mvn verify" at the root of the mylyn docs repository). The missing files will be generated by the build.

I see no other solutions for that. 
The "*-toc.xml" files are ignored from the git repository and this is correct. If we start to add them (or a placeholder file) it means that we will have pending git changes for those files and we do not want something like that for derived ressources.

For me this bug can be closed as RESOLVED WONTFIX or something similar.

[1] https://dev.eclipse.org/mhonarc/lists/mylyn-docs-dev/msg00236.html
Comment 2 Amr Dawood CLA 2015-10-16 12:14:07 EDT
OPTION "c/" worked for me. Thanks Jeremie. Closing as RESOLVED WONTFIX.
Comment 3 Jeremie Bresson CLA 2015-11-04 12:08:54 EST
I would like to reopen this bug to implement the solution "b/" in the "Mylyn.setup" task (for the Eclipse Oomph installer)

I will propose a patch that generates the two placeholder files at startup time.

In my eyes, it is important to have a bug free setup for people setting up their workspace with Mylyn. There are other problems at the moment, see the discussion on the Mailing list [1].

With my patch I will solve the two issues described in comment #0.

Can someone please REOPEN this bug?

[1] http://dev.eclipse.org/mhonarc/lists/mylyn-docs-dev/msg00258.html
Comment 4 Amr Dawood CLA 2015-11-04 12:13:20 EST
I see your point, Jeremie, and I agree with you. Reopening the bug.
Comment 5 Eclipse Genie CLA 2015-11-04 12:19:14 EST
New Gerrit change created: https://git.eclipse.org/r/59682
Comment 6 Jeremie Bresson CLA 2015-11-15 04:31:24 EST
@Steffen Pingel & Frank Becker:
You seem to be the 2 authors of the Mylyn Oomph setup file, I took the liberty to add you CC on this bug.

Can you help me, with Change 59682?
https://git.eclipse.org/r/59682

If this changed is merged, we will have an error-free Mylyn Docs workspace set up with Oomph.

As I wrote on Gerrit line 593, there are a lot of changes... But at the end, only the 2 additional "setup:ResourceCreationTask" are new.
Should I push a hand-written patch with only theses XML modifications? Maybe the Oomph Editor added unintentional XML changes in the setup document.

PS: feel free to move this bug to another project (Mylyn Releng or something similar) if it better suit your workflow.
Comment 8 Sam Davis CLA 2015-11-17 17:57:52 EST
Frank, should we close this?
Comment 9 Jeremie Bresson CLA 2015-11-18 01:32:54 EST
(In reply to Sam Davis from comment #8)
> Frank, should we close this?

This was reopen with comment #4 to fix the Oomph setup.
I have verified this change, and got a error free Workspace for Mylyn Docs.

Thank you for your help.

Marking this bug as RESOLVED FIXED.