You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "kevin (JIRA)" <ji...@apache.org> on 2005/09/03 16:22:30 UTC
[jira] Created: (FOR-662) forrest seed using views broken index.source.xml
forrest seed using views broken index.source.xml
------------------------------------------------
Key: FOR-662
URL: http://issues.apache.org/jira/browse/FOR-662
Project: Forrest
Type: Bug
Components: Views
Versions: 0.8-dev
Environment: Any
Reporter: kevin
Priority: Minor
Tried howto example on views on fresh seed-basic site and got error:
X [0] index.source.xml BROKEN: /path/to/seed-basic/src/documentation/content/xdocs/index.source.xml (No such file or directory)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Created: (FOR-662) forrest seed using views broken index.source.xml
Posted by Kevin <ke...@kegcl.demon.co.uk>.
Tim Williams wrote:
> On 9/3/05, Kevin <fo...@kegcl.demon.co.uk> wrote:
>
>>On Sat, 2005-09-03 at 11:14 -0400, Tim Williams wrote:
>>
>>>I just did svn update; build clean; build; forrest seed-basic; and
>>>don't see this problem. Is your configuration unique? Have you "svn
>>>update/build clean/build" and are working with the trunk?
>>>--tim
>>
>>Yes default forrest and all updated.
>>
>>Then follow the howto example on views:
>>http://forrest.apache.org/docs_0_80/howto/howto-view-install.html
>>
>>i.e local-deploy latest views plugins and update forrest.properties
>>
>>It looks like source xml is required for a link. Testing on
>>forrest seed will give errors for all sources.
>
>
> Ok, you're talking about "forrest site" not "forrest run". I see it
> now. The site appears to really build fine other than the link to the
> source XML. I can look into it later this evening if someone else
> hasn't read this by then. I'm still learning views too though. In
> the mean time, assuming you don't need the XML Source link in the
> site, you could always go into the build directory of the plugins and
> copy the file "export-link-vt.xml" and paste it into your
> project-dir/src/resources/templates; then remove the line that looks
> like this:
> <forrest:contract name="content-source-xml-link"/>
>
> It should build fine after that, until someone has time to look into it.
Thanks Tim , I'll try that. I'm only starting to look at views and
trying out anything I can find in the docs. Sorry not to mention
forrest site in the jira.
Kevin
> [Note: I'm not sure that this hack would be endorsed by those folks
> that actually understand Views;) ]
> --tim
>
>
>>Kevin
>>
>>
>>>On 9/3/05, kevin (JIRA) <ji...@apache.org> wrote:
>>>
>>>>forrest seed using views broken index.source.xml
>>>>------------------------------------------------
>>>>
>>>> Key: FOR-662
>>>> URL: http://issues.apache.org/jira/browse/FOR-662
>>>> Project: Forrest
>>>> Type: Bug
>>>> Components: Views
>>>> Versions: 0.8-dev
>>>> Environment: Any
>>>> Reporter: kevin
>>>> Priority: Minor
>>>>
>>>>
>>>>Tried howto example on views on fresh seed-basic site and got error:
>>>>
>>>>X [0] index.source.xml BROKEN: /path/to/seed-basic/src/documentation/content/xdocs/index.source.xml (No such file or directory)
>>>>
>>>>
>>>>--
>>>>This message is automatically generated by JIRA.
>>>>-
>>>>If you think it was sent incorrectly contact one of the administrators:
>>>> http://issues.apache.org/jira/secure/Administrators.jspa
>>>>-
>>>>For more information on JIRA, see:
>>>> http://www.atlassian.com/software/jira
>>>>
>>>>
>>
>>
>>
>
Re: [jira] Created: (FOR-662) forrest seed using views broken
index.source.xml
Posted by Kevin <fo...@kegcl.demon.co.uk>.
On Sat, 2005-09-03 at 16:55 -0400, Tim Williams wrote:
> On 9/3/05, Kevin <fo...@kegcl.demon.co.uk> wrote:
> > On Sat, 2005-09-03 at 11:14 -0400, Tim Williams wrote:
> > > I just did svn update; build clean; build; forrest seed-basic; and
> > > don't see this problem. Is your configuration unique? Have you "svn
> > > update/build clean/build" and are working with the trunk?
> > > --tim
> >
> > Yes default forrest and all updated.
> >
> > Then follow the howto example on views:
> > http://forrest.apache.org/docs_0_80/howto/howto-view-install.html
> >
> > i.e local-deploy latest views plugins and update forrest.properties
> >
> > It looks like source xml is required for a link. Testing on
> > forrest seed will give errors for all sources.
>
> Ok, you're talking about "forrest site" not "forrest run". I see it
> now. The site appears to really build fine other than the link to the
> source XML. I can look into it later this evening if someone else
> hasn't read this by then. I'm still learning views too though. In
> the mean time, assuming you don't need the XML Source link in the
> site, you could always go into the build directory of the plugins and
> copy the file "export-link-vt.xml" and paste it into your
> project-dir/src/resources/templates; then remove the line that looks
> like this:
> <forrest:contract name="content-source-xml-link"/>
>
> It should build fine after that, until someone has time to look into it.
Thanks Tim, That worked fine.
Kevin
> [Note: I'm not sure that this hack would be endorsed by those folks
> that actually understand Views;) ]
> --tim
>
> > Kevin
> >
> > > On 9/3/05, kevin (JIRA) <ji...@apache.org> wrote:
> > > > forrest seed using views broken index.source.xml
> > > > ------------------------------------------------
> > > >
> > > > Key: FOR-662
> > > > URL: http://issues.apache.org/jira/browse/FOR-662
> > > > Project: Forrest
> > > > Type: Bug
> > > > Components: Views
> > > > Versions: 0.8-dev
> > > > Environment: Any
> > > > Reporter: kevin
> > > > Priority: Minor
> > > >
> > > >
> > > > Tried howto example on views on fresh seed-basic site and got error:
> > > >
> > > > X [0] index.source.xml BROKEN: /path/to/seed-basic/src/documentation/content/xdocs/index.source.xml (No such file or directory)
> > > >
> > > >
> > > > --
> > > > This message is automatically generated by JIRA.
> > > > -
> > > > If you think it was sent incorrectly contact one of the administrators:
> > > > http://issues.apache.org/jira/secure/Administrators.jspa
> > > > -
> > > > For more information on JIRA, see:
> > > > http://www.atlassian.com/software/jira
> > > >
> > > >
> >
> >
> >
Re: [jira] Created: (FOR-662) forrest seed using views broken index.source.xml
Posted by Tim Williams <wi...@gmail.com>.
On 9/3/05, Kevin <fo...@kegcl.demon.co.uk> wrote:
> On Sat, 2005-09-03 at 11:14 -0400, Tim Williams wrote:
> > I just did svn update; build clean; build; forrest seed-basic; and
> > don't see this problem. Is your configuration unique? Have you "svn
> > update/build clean/build" and are working with the trunk?
> > --tim
>
> Yes default forrest and all updated.
>
> Then follow the howto example on views:
> http://forrest.apache.org/docs_0_80/howto/howto-view-install.html
>
> i.e local-deploy latest views plugins and update forrest.properties
>
> It looks like source xml is required for a link. Testing on
> forrest seed will give errors for all sources.
Ok, you're talking about "forrest site" not "forrest run". I see it
now. The site appears to really build fine other than the link to the
source XML. I can look into it later this evening if someone else
hasn't read this by then. I'm still learning views too though. In
the mean time, assuming you don't need the XML Source link in the
site, you could always go into the build directory of the plugins and
copy the file "export-link-vt.xml" and paste it into your
project-dir/src/resources/templates; then remove the line that looks
like this:
<forrest:contract name="content-source-xml-link"/>
It should build fine after that, until someone has time to look into it.
[Note: I'm not sure that this hack would be endorsed by those folks
that actually understand Views;) ]
--tim
> Kevin
>
> > On 9/3/05, kevin (JIRA) <ji...@apache.org> wrote:
> > > forrest seed using views broken index.source.xml
> > > ------------------------------------------------
> > >
> > > Key: FOR-662
> > > URL: http://issues.apache.org/jira/browse/FOR-662
> > > Project: Forrest
> > > Type: Bug
> > > Components: Views
> > > Versions: 0.8-dev
> > > Environment: Any
> > > Reporter: kevin
> > > Priority: Minor
> > >
> > >
> > > Tried howto example on views on fresh seed-basic site and got error:
> > >
> > > X [0] index.source.xml BROKEN: /path/to/seed-basic/src/documentation/content/xdocs/index.source.xml (No such file or directory)
> > >
> > >
> > > --
> > > This message is automatically generated by JIRA.
> > > -
> > > If you think it was sent incorrectly contact one of the administrators:
> > > http://issues.apache.org/jira/secure/Administrators.jspa
> > > -
> > > For more information on JIRA, see:
> > > http://www.atlassian.com/software/jira
> > >
> > >
>
>
>
Re: [jira] Created: (FOR-662) forrest seed using views broken
index.source.xml
Posted by Kevin <fo...@kegcl.demon.co.uk>.
On Sat, 2005-09-03 at 11:14 -0400, Tim Williams wrote:
> I just did svn update; build clean; build; forrest seed-basic; and
> don't see this problem. Is your configuration unique? Have you "svn
> update/build clean/build" and are working with the trunk?
> --tim
Yes default forrest and all updated.
Then follow the howto example on views:
http://forrest.apache.org/docs_0_80/howto/howto-view-install.html
i.e local-deploy latest views plugins and update forrest.properties
It looks like source xml is required for a link. Testing on
forrest seed will give errors for all sources.
Kevin
> On 9/3/05, kevin (JIRA) <ji...@apache.org> wrote:
> > forrest seed using views broken index.source.xml
> > ------------------------------------------------
> >
> > Key: FOR-662
> > URL: http://issues.apache.org/jira/browse/FOR-662
> > Project: Forrest
> > Type: Bug
> > Components: Views
> > Versions: 0.8-dev
> > Environment: Any
> > Reporter: kevin
> > Priority: Minor
> >
> >
> > Tried howto example on views on fresh seed-basic site and got error:
> >
> > X [0] index.source.xml BROKEN: /path/to/seed-basic/src/documentation/content/xdocs/index.source.xml (No such file or directory)
> >
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > If you think it was sent incorrectly contact one of the administrators:
> > http://issues.apache.org/jira/secure/Administrators.jspa
> > -
> > For more information on JIRA, see:
> > http://www.atlassian.com/software/jira
> >
> >
Re: [jira] Created: (FOR-662) forrest seed using views broken index.source.xml
Posted by Tim Williams <wi...@gmail.com>.
I just did svn update; build clean; build; forrest seed-basic; and
don't see this problem. Is your configuration unique? Have you "svn
update/build clean/build" and are working with the trunk?
--tim
On 9/3/05, kevin (JIRA) <ji...@apache.org> wrote:
> forrest seed using views broken index.source.xml
> ------------------------------------------------
>
> Key: FOR-662
> URL: http://issues.apache.org/jira/browse/FOR-662
> Project: Forrest
> Type: Bug
> Components: Views
> Versions: 0.8-dev
> Environment: Any
> Reporter: kevin
> Priority: Minor
>
>
> Tried howto example on views on fresh seed-basic site and got error:
>
> X [0] index.source.xml BROKEN: /path/to/seed-basic/src/documentation/content/xdocs/index.source.xml (No such file or directory)
>
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
>
Re: [jira] Commented: (FOR-662) content-source-xml-link contract
breaks 'forrest site'
Posted by Ross Gardler <rg...@apache.org>.
Thorsten Scherler wrote:
> On Sun, 2005-09-04 at 04:51 +0200, Tim Williams (JIRA) wrote:
>
>> [ http://issues.apache.org/jira/browse/FOR-662?page=comments#action_12322601 ]
>>
>>Tim Williams commented on FOR-662:
>>----------------------------------
>>
>>A small portion of this remains unfortunately. The current solution doesn't work for the plugin docs. I think this source stuff needs some re-thinking unforunately.
>
>
> "The current solution doesn't work for the plugin docs."
>
> What do mean with that? Maybe the source should be resolved with the
> mounting capability of the lm?
+1
See my mail regarding the fact that all this docs stuff was a hack for
to get versioned docs up for the 0.7 release - at that time we didn't
have the locationmap, we need to leverage it.
[OT] I would like to make the refactoring of the sitemaps a goal for the
next Forrest Tuesday since this will make integration of forrest:views
easier as well (since it simplifies the sitemaps).
Ross
Re: Avoiding fixed uri spaces (Re: [jira] Commented: (FOR-662) content-source-xml-link
contract breaks 'forrest site')
Posted by Ross Gardler <rg...@apache.org>.
Tim Williams wrote:
> On 9/4/05, Ross Gardler <rg...@apache.org> wrote:
>
...
>>I believe the issue that arose because of the addition of the
>>*.source.xml matchers is a result of the fixing og the path part of the
>>URL, rather than a problem of the "extension" part.
>
>
> It's the implementation of the extension (adding a new matcher or
> ensuring that all matchers account for all the different "hints" that
> I thought needed re-thinking.
Yes, I thought so. This is caused by the fixing of the path part,
imagine that if there was no special matcher for the
"pluginDocs/index.xml" file in the sitemap. In this case there would be
no need for the new matcher for "pluginDocs/index.source.xml" since it
would have been matched by the catch-all "**.source.xml".
If we remove the need to fix the path (using the locationmap?) then the
problem does not exist and the hints in the URL are OK (at least I think
so).
> Anyway, don't worry, the status qou
> works.
For now...
>> > I still think there might be room for an
>> > enhanced Cocoon View in here - reacting to the "hint" in
>> > fname.hint.xml instead of the current request parameter. I don't know
>> > though...
>>
>>If you can make Cocoon views work without the request parameter then
>>this would work. Otherwise, it will be impossible to create a static
>>site beause request parameters add an '?' to the URL which is not legal
>>in a filename on disk. Unless you solve that problem you are on to a
>>loser (I've tried it). 'm not saying it won't work, I'm saying there is
>>a problem that needs to be addressed, I hope identifying the problem
>>will save you some time in experimentation ;-)
>
>
> I'm not constraining my thinking by the current Cocoon->View
> implementation. At the bottom of their own docs, they suggest that a
> future possible view accessor might be to react on a URI exstension --
> so why not our "hint" in fname.hint.xml?
I see. OK, we know what to consider if this raises its ugly head again.
> I don't have an itch to fix
> this at the moment and I suppose that the in vogue thing is not to
> have design debate on-list so I'll hush up until I have such an itch
> -- with the latest patch it's working fine.
:-))
I think we ought to focus on removing the fixed paths first, maybe that
itch will never arrive.
Ross
Re: Avoiding fixed uri spaces (Re: [jira] Commented: (FOR-662) content-source-xml-link contract breaks 'forrest site')
Posted by Tim Williams <wi...@gmail.com>.
On 9/4/05, Ross Gardler <rg...@apache.org> wrote:
> Tim Williams wrote:
> > On 9/4/05, Thorsten Scherler <th...@apache.org> wrote:
> >
> >>On Sun, 2005-09-04 at 04:51 +0200, Tim Williams (JIRA) wrote:
> >>
> >>> [
> http://issues.apache.org/jira/browse/FOR-662?page=comments#action_12322601 ]
> >>>
> >>>Tim Williams commented on FOR-662:
> >>>----------------------------------
> >>>
> >>>A small portion of this remains unfortunately. The current solution
> doesn't work for the plugin docs. I think this source stuff needs some
> re-thinking unforunately.
> >>
> >>"The current solution doesn't work for the plugin docs."
> >>
> >>What do mean with that? Maybe the source should be resolved with the
> >>mounting capability of the lm?
> >
> >
> > Actually, you had just closed the issue and I commented that it's not
> > totally resolved because our combined patches didn't work for
> > pluginDocs since there is a separate sitemap entry for them. I've
> > since patched that too. I don't immediately see how the locationmap
> > stuff will fit here, my comment about it needing some re-thinking is
> > that these requests have to be modified per match and don't "grow"
> > very well -- all unique matches need to account for these different
> > formats (e.g. pluginDocs).
>
> Which part are you saying needs rethinking, I'm confused. There are two
> parts of the URI that we are fixing, the first is the "extensions" the
> second is the path to the file.
>
> The extensions (i.e. *.source.xml) is in line with the proopsal we
> discussed a long time ago and recently resurfaced in
> http://marc.theaimsgroup.com/?l=forrest-dev&m=112550194621801&w=2 Do you
> see a problem with that proposal?
>
> The part about fixed paths in URI's (i.e. "pluginDocs/**") is a
> recognised problem that needs addressing.
>
> I believe the issue that arose because of the addition of the
> *.source.xml matchers is a result of the fixing og the path part of the
> URL, rather than a problem of the "extension" part.
It's the implementation of the extension (adding a new matcher or
ensuring that all matchers account for all the different "hints" that
I thought needed re-thinking. Anyway, don't worry, the status qou
works.
> > I still think there might be room for an
> > enhanced Cocoon View in here - reacting to the "hint" in
> > fname.hint.xml instead of the current request parameter. I don't know
> > though...
>
> If you can make Cocoon views work without the request parameter then
> this would work. Otherwise, it will be impossible to create a static
> site beause request parameters add an '?' to the URL which is not legal
> in a filename on disk. Unless you solve that problem you are on to a
> loser (I've tried it). 'm not saying it won't work, I'm saying there is
> a problem that needs to be addressed, I hope identifying the problem
> will save you some time in experimentation ;-)
I'm not constraining my thinking by the current Cocoon->View
implementation. At the bottom of their own docs, they suggest that a
future possible view accessor might be to react on a URI exstension --
so why not our "hint" in fname.hint.xml? I don't have an itch to fix
this at the moment and I suppose that the in vogue thing is not to
have design debate on-list so I'll hush up until I have such an itch
-- with the latest patch it's working fine.
--tim
Avoiding fixed uri spaces (Re: [jira] Commented: (FOR-662) content-source-xml-link
contract breaks 'forrest site')
Posted by Ross Gardler <rg...@apache.org>.
Tim Williams wrote:
> On 9/4/05, Thorsten Scherler <th...@apache.org> wrote:
>
>>On Sun, 2005-09-04 at 04:51 +0200, Tim Williams (JIRA) wrote:
>>
>>> [
http://issues.apache.org/jira/browse/FOR-662?page=comments#action_12322601 ]
>>>
>>>Tim Williams commented on FOR-662:
>>>----------------------------------
>>>
>>>A small portion of this remains unfortunately. The current solution
doesn't work for the plugin docs. I think this source stuff needs some
re-thinking unforunately.
>>
>>"The current solution doesn't work for the plugin docs."
>>
>>What do mean with that? Maybe the source should be resolved with the
>>mounting capability of the lm?
>
>
> Actually, you had just closed the issue and I commented that it's not
> totally resolved because our combined patches didn't work for
> pluginDocs since there is a separate sitemap entry for them. I've
> since patched that too. I don't immediately see how the locationmap
> stuff will fit here, my comment about it needing some re-thinking is
> that these requests have to be modified per match and don't "grow"
> very well -- all unique matches need to account for these different
> formats (e.g. pluginDocs).
Which part are you saying needs rethinking, I'm confused. There are two
parts of the URI that we are fixing, the first is the "extensions" the
second is the path to the file.
The extensions (i.e. *.source.xml) is in line with the proopsal we
discussed a long time ago and recently resurfaced in
http://marc.theaimsgroup.com/?l=forrest-dev&m=112550194621801&w=2 Do you
see a problem with that proposal?
The part about fixed paths in URI's (i.e. "pluginDocs/**") is a
recognised problem that needs addressing.
I believe the issue that arose because of the addition of the
*.source.xml matchers is a result of the fixing og the path part of the
URL, rather than a problem of the "extension" part.
> I still think there might be room for an
> enhanced Cocoon View in here - reacting to the "hint" in
> fname.hint.xml instead of the current request parameter. I don't know
> though...
If you can make Cocoon views work without the request parameter then
this would work. Otherwise, it will be impossible to create a static
site beause request parameters add an '?' to the URL which is not legal
in a filename on disk. Unless you solve that problem you are on to a
loser (I've tried it). 'm not saying it won't work, I'm saying there is
a problem that needs to be addressed, I hope identifying the problem
will save you some time in experimentation ;-)
Ross
Re: [jira] Commented: (FOR-662) content-source-xml-link contract breaks 'forrest site'
Posted by Tim Williams <wi...@gmail.com>.
On 9/4/05, Thorsten Scherler <th...@apache.org> wrote:
> On Sun, 2005-09-04 at 04:51 +0200, Tim Williams (JIRA) wrote:
> > [ http://issues.apache.org/jira/browse/FOR-662?page=comments#action_12322601 ]
> >
> > Tim Williams commented on FOR-662:
> > ----------------------------------
> >
> > A small portion of this remains unfortunately. The current solution doesn't work for the plugin docs. I think this source stuff needs some re-thinking unforunately.
>
> "The current solution doesn't work for the plugin docs."
>
> What do mean with that? Maybe the source should be resolved with the
> mounting capability of the lm?
Actually, you had just closed the issue and I commented that it's not
totally resolved because our combined patches didn't work for
pluginDocs since there is a separate sitemap entry for them. I've
since patched that too. I don't immediately see how the locationmap
stuff will fit here, my comment about it needing some re-thinking is
that these requests have to be modified per match and don't "grow"
very well -- all unique matches need to account for these different
formats (e.g. pluginDocs). I still think there might be room for an
enhanced Cocoon View in here - reacting to the "hint" in
fname.hint.xml instead of the current request parameter. I don't know
though...
--tim
Re: [jira] Commented: (FOR-662) content-source-xml-link contract
breaks 'forrest site'
Posted by Thorsten Scherler <th...@apache.org>.
On Sun, 2005-09-04 at 04:51 +0200, Tim Williams (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/FOR-662?page=comments#action_12322601 ]
>
> Tim Williams commented on FOR-662:
> ----------------------------------
>
> A small portion of this remains unfortunately. The current solution doesn't work for the plugin docs. I think this source stuff needs some re-thinking unforunately.
"The current solution doesn't work for the plugin docs."
What do mean with that? Maybe the source should be resolved with the
mounting capability of the lm?
Salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
[jira] Commented: (FOR-662) content-source-xml-link contract breaks 'forrest site'
Posted by "Tim Williams (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-662?page=comments#action_12322601 ]
Tim Williams commented on FOR-662:
----------------------------------
A small portion of this remains unfortunately. The current solution doesn't work for the plugin docs. I think this source stuff needs some re-thinking unforunately.
> content-source-xml-link contract breaks 'forrest site'
> ------------------------------------------------------
>
> Key: FOR-662
> URL: http://issues.apache.org/jira/browse/FOR-662
> Project: Forrest
> Type: Bug
> Components: Views
> Versions: 0.8-dev
> Environment: Any
> Reporter: kevin
> Priority: Minor
>
> Tried howto example on views on fresh seed-basic site and got error:
> X [0] index.source.xml BROKEN: /path/to/seed-basic/src/documentation/content/xdocs/index.source.xml (No such file or directory)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (FOR-662) content-source-xml-link contract breaks 'forrest site'
Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-662?page=all ]
Thorsten Scherler closed FOR-662:
---------------------------------
Resolution: Fixed
Team work fixed that bug :)
> content-source-xml-link contract breaks 'forrest site'
> ------------------------------------------------------
>
> Key: FOR-662
> URL: http://issues.apache.org/jira/browse/FOR-662
> Project: Forrest
> Type: Bug
> Components: Views
> Versions: 0.8-dev
> Environment: Any
> Reporter: kevin
> Priority: Minor
>
> Tried howto example on views on fresh seed-basic site and got error:
> X [0] index.source.xml BROKEN: /path/to/seed-basic/src/documentation/content/xdocs/index.source.xml (No such file or directory)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Reopened: (FOR-662) content-source-xml-link contract breaks 'forrest site'
Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-662?page=all ]
Thorsten Scherler reopened FOR-662:
-----------------------------------
I reopened this bug as example on how to analyse and resolve issues.
> content-source-xml-link contract breaks 'forrest site'
> ------------------------------------------------------
>
> Key: FOR-662
> URL: http://issues.apache.org/jira/browse/FOR-662
> Project: Forrest
> Type: Bug
> Components: Views
> Versions: 0.8-dev
> Environment: Any
> Reporter: kevin
> Priority: Minor
>
> Tried howto example on views on fresh seed-basic site and got error:
> X [0] index.source.xml BROKEN: /path/to/seed-basic/src/documentation/content/xdocs/index.source.xml (No such file or directory)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (FOR-662) content-source-xml-link contract breaks 'forrest site'
Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-662?page=all ]
Thorsten Scherler resolved FOR-662:
-----------------------------------
Resolution: Fixed
...but the issue is resolved. Sorry for the spam. :(
> content-source-xml-link contract breaks 'forrest site'
> ------------------------------------------------------
>
> Key: FOR-662
> URL: http://issues.apache.org/jira/browse/FOR-662
> Project: Forrest
> Type: Bug
> Components: Views
> Versions: 0.8-dev
> Environment: Any
> Reporter: kevin
> Priority: Minor
>
> Tried howto example on views on fresh seed-basic site and got error:
> X [0] index.source.xml BROKEN: /path/to/seed-basic/src/documentation/content/xdocs/index.source.xml (No such file or directory)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (FOR-662) content-source-xml-link contract breaks 'forrest site'
Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-662?page=all ]
Thorsten Scherler updated FOR-662:
----------------------------------
Summary: content-source-xml-link contract breaks 'forrest site' (was: forrest seed using views broken index.source.xml)
problem:
http://marc.theaimsgroup.com/?t=112578439100001&r=1&w=2
Issue history:
http://marc.theaimsgroup.com/?t=112575749800001&r=1&w=2
Workaround till contract is fixed:
http://svn.apache.org/viewcvs.cgi/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.output.viewHelper.xhtml/resources/templates/export-link.vt.xml?rev=267540&r1=264872&r2=267540&diff_format=h
> content-source-xml-link contract breaks 'forrest site'
> ------------------------------------------------------
>
> Key: FOR-662
> URL: http://issues.apache.org/jira/browse/FOR-662
> Project: Forrest
> Type: Bug
> Components: Views
> Versions: 0.8-dev
> Environment: Any
> Reporter: kevin
> Priority: Minor
>
> Tried howto example on views on fresh seed-basic site and got error:
> X [0] index.source.xml BROKEN: /path/to/seed-basic/src/documentation/content/xdocs/index.source.xml (No such file or directory)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira