ok
get that

one more question
to align xmlcode contents better I try the following:
1) add
white-space: pre;
font-family: monospace;
display: block;
unicode-bidi: embed;
to css definition of xmlcode class to enforce this class act like <pre> tag
(it works, but all current xml files need to be corrected - too much
changes)

2) use &nbsp; - but it didn't compile, could you please help me to find dtd
or xsd to add nbsp entity to it? I can escape it with &amp; but code will
be to heavy in this case

Or maybe there is a better solution?

ps Take a look at
http://incubator.apache.org/openmeetings/BuildInstructions.html at "To
compile the client you can also use ant:" section to see what I'm trying to
fix


On Sat, Dec 17, 2011 at 21:48, [email protected]
<[email protected]>wrote:

> Yes and no...
>
> The Apache infra structure works like that:
> The server people.apache.org acts as 'staging' instance and a regulär job
> does copy those files to the actual web-server(s)
>
> Once we have our trunk in the new infra structure we also get a integrated
> on their bild cycle but I don't think that it will be possible to grab the
> bild artefacts using a cron job.
> The Apache infra actually expects every project to have a compiled version
> of the website in the SVN.
>
> Sebastian
> Am 17.12.2011 15:35 schrieb "Maxim Solodovnik" <[email protected]>:
>
> Am I right thinking we store both xml sources and compiled html in the SVN?
>> Maybe it is OK to store XML only in OM SVN, and build apache site from it
>> using cron on daily basis?
>>
>> It seems like to complicated to store same thing 2 times
>>
>> On Sat, Dec 17, 2011 at 17:16, Maxim Solodovnik <[email protected]>wrote:
>>
>>> OK
>>> will commit documentation changes to all these places
>>>
>>>
>>> On Sat, Dec 17, 2011 at 16:42, [email protected] <
>>> [email protected]> wrote:
>>>
>>>> ++ I guess Daniel from the Apache Infra-Team will soon copy the svn
>>>> snapshot he imported to our repository,
>>>> see: https://issues.apache.org/jira/browse/INFRA-4184
>>>>
>>>> 2011/12/17 [email protected] <[email protected]>
>>>>
>>>> .Hi Maxim,
>>>>>
>>>>> no I accidently pushed the send button without content :D
>>>>>
>>>>> What I wanted to say: Make sure the new docs have those changes too ^^
>>>>>
>>>>> See:
>>>>> http://incubator.apache.org/openmeetings/BuildInstructions.html
>>>>>
>>>>> I have moved almost all content to the new docs.
>>>>> The docs are now in the SVN for example for the BuildInstructions.xml:
>>>>>
>>>>> http://code.google.com/p/openmeetings/source/browse/trunk/singlewebapp/xdocs/BuildInstructions.xml
>>>>>
>>>>> You can compile the .html files / docs using this command:
>>>>> ant build.only.webservice.doc
>>>>>
>>>>> That will create also the WebService-API HTML pages like those ones:
>>>>> http://incubator.apache.org/openmeetings/UserService.html
>>>>>
>>>>> You find the resulting docs / website in the folder "docs" after each
>>>>> build:
>>>>>
>>>>> http://code.google.com/p/openmeetings/source/browse/trunk/singlewebapp/#singlewebapp%2Fdocs
>>>>> And it will be also copied into
>>>>> /dist/red5-xyz/webapps/openmeetings/docs
>>>>> => So you have now a documentation that ships with every build :)
>>>>>
>>>>> To update the incubator.apache.org/openmeetings website, you
>>>>> currently need to commit those generated docs also to:
>>>>> http://svn.apache.org/repos/asf/incubator/openmeetings/site/docs/
>>>>> Then login to people.apache.org with you ssh user/pass
>>>>> cd /www/incubator.apache.org/openmeetings
>>>>> and now you need to get the content from the SVN to the server ... I
>>>>> made three tiny Shell-Script's that you can use:
>>>>> ./sync_script.sh
>>>>> cd images/ ./sync_script.sh
>>>>> cd ../css ./sync_script.sh
>>>>>
>>>>> Sync-Scripts:
>>>>>
>>>>> http://svn.apache.org/repos/asf/incubator/openmeetings/site/docs/sync_script.sh
>>>>>
>>>>> http://svn.apache.org/repos/asf/incubator/openmeetings/site/docs/images/sync_script.sh
>>>>>
>>>>> http://svn.apache.org/repos/asf/incubator/openmeetings/site/docs/css/sync_script.sh
>>>>>
>>>>> Sebastian
>>>>>
>>>>>
>>>>>
>>>>> ---------- Forwarded message ----------
>>>>> From: [email protected] <[email protected]>
>>>>> Date: 2011/12/17
>>>>> Subject: Fwd: [openmeetings-dev] [openmeetings] r4731 committed -
>>>>> Edited wiki page BuildSourceNew through web user interface.
>>>>> To: Maxim Solodovnik <[email protected]>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ---------- Forwarded message ----------
>>>>> From: <[email protected]>
>>>>> Date: 2011/12/17
>>>>> Subject: [openmeetings-dev] [openmeetings] r4731 committed - Edited
>>>>> wiki page BuildSourceNew through web user interface.
>>>>> To: [email protected]
>>>>>
>>>>>
>>>>> Revision: 4731
>>>>> Author:   [email protected]
>>>>> Date:     Sat Dec 17 00:43:59 2011
>>>>> Log:      Edited wiki page BuildSourceNew through web user interface.
>>>>> http://code.google.com/p/**openmeetings/source/detail?r=**4731<http://code.google.com/p/openmeetings/source/detail?r=4731>
>>>>>
>>>>> Modified:
>>>>>  /wiki/BuildSourceNew.wiki
>>>>>
>>>>> ==============================**=========
>>>>> --- /wiki/BuildSourceNew.wiki   Sat Nov 12 09:48:40 2011
>>>>> +++ /wiki/BuildSourceNew.wiki   Sat Dec 17 00:43:59 2011
>>>>> @@ -26,11 +26,12 @@
>>>>>  ant                           # compiles a complete package into the
>>>>> folder dist
>>>>>  ant compile.laszlo.main       # compiles the client into main.swf8.swf
>>>>>  ant compile.laszlo.main.debug # compiles the debug-client into
>>>>> maindebug.swf8.swf
>>>>> +ant -Ddb=<name of DB>         # will copy <name of
>>>>> DB>_persistense.xml to persistense.xml (for ex. ant -Ddb=mysql will set
>>>>> mysql as default DB)
>>>>>  }}}
>>>>>
>>>>>  To compile just the openmeetings JAR file:
>>>>>  {{{
>>>>> -ant -f build_openmeetings_jar.xml
>>>>> +ant jar.only
>>>>>  }}}
>>>>>
>>>>>  To run Junit tests using ANT see [JUnitTestings]
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "OpenMeetings developers" group.
>>>>> To post to this group, send email to openmeetings-dev@googlegroups.**
>>>>> com <[email protected]>.
>>>>> To unsubscribe from this group, send email to
>>>>> openmeetings-dev+unsubscribe@**googlegroups.com<openmeetings-dev%[email protected]>
>>>>> .
>>>>> For more options, visit this group at http://groups.google.com/**
>>>>> group/openmeetings-dev?hl=en<http://groups.google.com/group/openmeetings-dev?hl=en>
>>>>> .
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sebastian Wagner
>>>>> http://www.openmeetings.de
>>>>> http://incubator.apache.org/openmeetings/
>>>>> http://www.webbase-design.de
>>>>> http://www.wagner-sebastian.com
>>>>> [email protected]
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sebastian Wagner
>>>>> http://www.openmeetings.de
>>>>> http://incubator.apache.org/openmeetings/
>>>>> http://www.webbase-design.de
>>>>> http://www.wagner-sebastian.com
>>>>> [email protected]
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Sebastian Wagner
>>>> http://www.openmeetings.de
>>>> http://incubator.apache.org/openmeetings/
>>>> http://www.webbase-design.de
>>>> http://www.wagner-sebastian.com
>>>> [email protected]
>>>>
>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>


-- 
WBR
Maxim aka solomax

Reply via email to