"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "openmeetings-server/src/site/xdoc/BuildInstructions.xml" between
apache-openmeetings-6.1.0-src.tar.gz and apache-openmeetings-6.2.0-src.tar.gz

About: OpenMeetings is a browser-based software that allows you to set up instantly a conference in the Web. You can use your microphone or webcam, share documents on a white board, share your screen or record meetings. Source code.

BuildInstructions.xml  (apache-openmeetings-6.1.0-src)	:	BuildInstructions.xml  (apache-openmeetings-6.2.0-src)
skipping to change at line 95		skipping to change at line 95
<source>		<source>
<![CDATA[		<![CDATA[
mvn install -P allModules,quick,mysql -pl openmeetings-util,openmeetings-db,open meetings-core,openmeetings-install,openmeetings-service,openmeetings-web,openmee tings-server,openmeetings-webservice -Dwicket.configuration=DEVELOPMENT		mvn install -P allModules,quick,mysql -pl openmeetings-util,openmeetings-db,open meetings-core,openmeetings-install,openmeetings-service,openmeetings-web,openmee tings-server,openmeetings-webservice -Dwicket.configuration=DEVELOPMENT
]]>		]]>
</source>		</source>
</section>		</section>
<section name="Update JavaScript and CSS at runtime">		<section name="Update JavaScript and CSS at runtime">
<div>		<div>
<p>You can update Javascript and CSS files and th en copy them at runtime. No need to re-run the entire Server build and restart. This can greatly save time when developing:</p>		<p>You can update Javascript and CSS files and th en copy them at runtime. No need to re-run the entire Server build and restart. This can greatly save time when developing:</p>
<source>mvn minify:minify@room-js minify:minify@i		<source>
nterview-wb-js minify:minify@wb-js minify:minify@fileinput-js minify:minify@sett		<![CDATA[
ings-js minify:minify@nettest-js minify:minify@chat-js minify:minify@theme-minif		cd openmeetings-web
y</source>		# Run NPM install on each of the packages (only required once unless you change
<p>You can further trim down the compile time to		dependency):
just selected Javascript sections:</p>		mvn frontend:npm@main-install frontend:npm@chat-install frontend:npm@settings-in
<source>mvn minify:minify@room-js minify:minify@i		stall frontend:npm@room-install frontend:npm@wb-install
nterview-wb-js</source>		# Run NPM
<p>And then copy them into the relevant folder, f		mvn frontend:npm@main frontend:npm@chat frontend:npm@settings frontend:npm@room
or example if your run the Embedded Jetty:</p>		frontend:npm@wb
<source>cp -R target/generated-sources/js/org/apa		# Minify CSS
che/openmeetings/* target/openmeetings-web-6.0.0-SNAPSHOT/WEB-INF/classes/org/ap		mvn minify:minify@theme-minify minify:minify@nettest-js
ache/openmeetings/</source>		# Copy to destination, in this case running OpenMeetings using the embedded Jett
		y, see above
		export CURRENT_DIR=$(pwd)
		rsync -a $CURRENT_DIR/target/generated-sources/js/ $CURRENT_DIR/target/openmeeti
		ngs-web-7.0.0-SNAPSHOT/WEB-INF/classes/
		]]>
		</source>
		<p>You can also copy paste above into a handy she
		ll script and just run that on demand.</p>
		<p>This also allows you to use another editor lik
		e WebStorm or IntelliJ for editing the OpenMeetings node npm projects!</p>
</div>		</div>
</section>		</section>
<section name="Fix Proxy settings">		<section name="Fix Proxy settings">
<div>		<div>
<b>Working behind a proxy:</b>		<b>Working behind a proxy:</b>
If you are sitting behind a proxy you should add some proxy settings before starting the build process.		If you are sitting behind a proxy you should add some proxy settings before starting the build process.
<br />		<br />
<source>git config --global http.proxy http://pro xyuser:proxypwd@proxy.server.com:8080</source>		<source>git config --global http.proxy http://pro xyuser:proxypwd@proxy.server.com:8080</source>
<ul>		<ul>
<li>change <tt>proxyuser</tt> to your pro xy user</li>		<li>change <tt>proxyuser</tt> to your pro xy user</li>
End of changes. 1 change blocks.
13 lines changed or deleted		23 lines changed or added

---