You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by Kevin Meyer - KMZ <ke...@kmz.co.za> on 2010/11/20 18:42:04 UTC
Can we do something else with respect to the project documentation resources?
Guys,
With Dan's last use of svn:externals to replicate copies of the
documentation resources (images and the DTD files) means that an
"svn up ." takes more than 15 minutes on my system - each directory
query takes between 15 to 20 seconds, and there are 63 directories
queried..
Since each directory is just a copy of the same source directory, can't
we instead have a script (or some other copying tool) to just copy the
3 directories (docbkx/dtd-4.5, docbkx/style and docbkx/images) into
each destination?
Thus, I am requesting that only the main resource directory is fetched
from subversion (into, for example, trunk/src/docbkx/*), and some
other tool copy it from the local location into the required local
dependent project directories?
I would settle for a simple (shell/command) script, but I realize this
could become a maintenance nightmare - better if maven manages
the copying, is this possible?
Regards,
Kevin
Re: Can we do something else with respect to the project
documentation resources?
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Hi Dan...
But Kevin has a point here, why make the task of the SCM system we
have, SVN in our case, although it should be part of the build
process, that is copying whatever resources to whatever destination we
want ?
On Sat, Nov 20, 2010 at 6:50 PM, Dan Haywood
<da...@haywood-associates.co.uk> wrote:
> I've taken to using svn update --ignore-externals which does the trick for me.
>
> Good enough?
>
> Dan
>
> Sent from my iPhone
>
> On 20 Nov 2010, at 17:42, "Kevin Meyer - KMZ" <ke...@kmz.co.za> wrote:
>
>> Guys,
>>
>> With Dan's last use of svn:externals to replicate copies of the
>> documentation resources (images and the DTD files) means that an
>> "svn up ." takes more than 15 minutes on my system - each directory
>> query takes between 15 to 20 seconds, and there are 63 directories
>> queried..
>>
>> Since each directory is just a copy of the same source directory, can't
>> we instead have a script (or some other copying tool) to just copy the
>> 3 directories (docbkx/dtd-4.5, docbkx/style and docbkx/images) into
>> each destination?
>>
>> Thus, I am requesting that only the main resource directory is fetched
>> from subversion (into, for example, trunk/src/docbkx/*), and some
>> other tool copy it from the local location into the required local
>> dependent project directories?
>>
>> I would settle for a simple (shell/command) script, but I realize this
>> could become a maintenance nightmare - better if maven manages
>> the copying, is this possible?
>>
>>
>> Regards,
>> Kevin
>>
>
--
Thanks
- Mohammad Nour
Author of (WebSphere Application Server Community Edition 2.0 User Guide)
http://www.redbooks.ibm.com/abstracts/sg247585.html
- LinkedIn: http://www.linkedin.com/in/mnour
- Blog: http://tadabborat.blogspot.com
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
"Writing clean code is what you must do in order to call yourself a
professional. There is no reasonable excuse for doing anything less
than your best."
- Clean Code: A Handbook of Agile Software Craftsmanship
"Stay hungry, stay foolish."
- Steve Jobs
Re: Can we do something else with respect to the project documentation resources?
Posted by Kevin Meyer - KMZ <ke...@kmz.co.za>.
I'll give it a go.. yup it works! This is sufficient resolution for the
moment, pending a conclusion from Nour's comment...
Thanks for the suggestion, though.
I would express a +1 preference for the task of replicating the resource
to not rest with the SCM, if anyone knows how to make it part of the
build process instead.
On 20 Nov 2010 at 18:50, Dan Haywood wrote:
> I've taken to using svn update --ignore-externals which does the trick for me.
>
> Good enough?
>
> Dan
>
Re: Can we do something else with respect to the project documentation resources?
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
I've taken to using svn update --ignore-externals which does the trick for me.
Good enough?
Dan
Sent from my iPhone
On 20 Nov 2010, at 17:42, "Kevin Meyer - KMZ" <ke...@kmz.co.za> wrote:
> Guys,
>
> With Dan's last use of svn:externals to replicate copies of the
> documentation resources (images and the DTD files) means that an
> "svn up ." takes more than 15 minutes on my system - each directory
> query takes between 15 to 20 seconds, and there are 63 directories
> queried..
>
> Since each directory is just a copy of the same source directory, can't
> we instead have a script (or some other copying tool) to just copy the
> 3 directories (docbkx/dtd-4.5, docbkx/style and docbkx/images) into
> each destination?
>
> Thus, I am requesting that only the main resource directory is fetched
> from subversion (into, for example, trunk/src/docbkx/*), and some
> other tool copy it from the local location into the required local
> dependent project directories?
>
> I would settle for a simple (shell/command) script, but I realize this
> could become a maintenance nightmare - better if maven manages
> the copying, is this possible?
>
>
> Regards,
> Kevin
>
Re: Can we do something else with respect to the project documentation
resources?
Posted by Robert Matthews <rm...@nakedobjects.org>.
It's not come back to me yet, but I think it was at NOG, so I'll have a
look at how they are doing it and see if it's related.
Rob
On 22/11/10 10:20, dan haywood wrote:
> Primarily so that we can build docbook when offline. Also, for speed (for
> those of us on low bandwidth connections).
>
>
>
>
> On 22 November 2010 10:18, Robert Matthews<rm...@nakedobjects.org>wrote:
>
>
>> Can you remind me why we are referencing the DTD locally rather than
>> online? I Have vague memories about the XML documentation where this kind
>> of thing was a problem, but we managed to solve it locally (and simply).
>>
>> Regards
>> Rob
>>
>>
>> On 20/11/10 17:42, Kevin Meyer - KMZ wrote:
>>
>>
>>> Guys,
>>>
>>> With Dan's last use of svn:externals to replicate copies of the
>>> documentation resources (images and the DTD files) means that an
>>> "svn up ." takes more than 15 minutes on my system - each directory
>>> query takes between 15 to 20 seconds, and there are 63 directories
>>> queried..
>>>
>>> Since each directory is just a copy of the same source directory, can't
>>> we instead have a script (or some other copying tool) to just copy the
>>> 3 directories (docbkx/dtd-4.5, docbkx/style and docbkx/images) into
>>> each destination?
>>>
>>> Thus, I am requesting that only the main resource directory is fetched
>>> from subversion (into, for example, trunk/src/docbkx/*), and some
>>> other tool copy it from the local location into the required local
>>> dependent project directories?
>>>
>>> I would settle for a simple (shell/command) script, but I realize this
>>> could become a maintenance nightmare - better if maven manages
>>> the copying, is this possible?
>>>
>>>
>>> Regards,
>>> Kevin
>>>
>>>
>>>
>>>
>>
>>
>
Re: Can we do something else with respect to the project
documentation resources?
Posted by dan haywood <da...@haywood-associates.co.uk>.
Primarily so that we can build docbook when offline. Also, for speed (for
those of us on low bandwidth connections).
On 22 November 2010 10:18, Robert Matthews <rm...@nakedobjects.org>wrote:
> Can you remind me why we are referencing the DTD locally rather than
> online? I Have vague memories about the XML documentation where this kind
> of thing was a problem, but we managed to solve it locally (and simply).
>
> Regards
> Rob
>
>
> On 20/11/10 17:42, Kevin Meyer - KMZ wrote:
>
>> Guys,
>>
>> With Dan's last use of svn:externals to replicate copies of the
>> documentation resources (images and the DTD files) means that an
>> "svn up ." takes more than 15 minutes on my system - each directory
>> query takes between 15 to 20 seconds, and there are 63 directories
>> queried..
>>
>> Since each directory is just a copy of the same source directory, can't
>> we instead have a script (or some other copying tool) to just copy the
>> 3 directories (docbkx/dtd-4.5, docbkx/style and docbkx/images) into
>> each destination?
>>
>> Thus, I am requesting that only the main resource directory is fetched
>> from subversion (into, for example, trunk/src/docbkx/*), and some
>> other tool copy it from the local location into the required local
>> dependent project directories?
>>
>> I would settle for a simple (shell/command) script, but I realize this
>> could become a maintenance nightmare - better if maven manages
>> the copying, is this possible?
>>
>>
>> Regards,
>> Kevin
>>
>>
>>
>
>
Re: Can we do something else with respect to the project documentation
resources?
Posted by Robert Matthews <rm...@nakedobjects.org>.
Can you remind me why we are referencing the DTD locally rather than
online? I Have vague memories about the XML documentation where this
kind of thing was a problem, but we managed to solve it locally (and
simply).
Regards
Rob
On 20/11/10 17:42, Kevin Meyer - KMZ wrote:
> Guys,
>
> With Dan's last use of svn:externals to replicate copies of the
> documentation resources (images and the DTD files) means that an
> "svn up ." takes more than 15 minutes on my system - each directory
> query takes between 15 to 20 seconds, and there are 63 directories
> queried..
>
> Since each directory is just a copy of the same source directory, can't
> we instead have a script (or some other copying tool) to just copy the
> 3 directories (docbkx/dtd-4.5, docbkx/style and docbkx/images) into
> each destination?
>
> Thus, I am requesting that only the main resource directory is fetched
> from subversion (into, for example, trunk/src/docbkx/*), and some
> other tool copy it from the local location into the required local
> dependent project directories?
>
> I would settle for a simple (shell/command) script, but I realize this
> could become a maintenance nightmare - better if maven manages
> the copying, is this possible?
>
>
> Regards,
> Kevin
>
>