Bryan Kowal 1117e40536 Issue #18 - jvm argument names are no longer used when re-configuring setup.env; renamed variables that referenced jettyPort. ... Former-commit-id: 94b327d00f [formerly 94b327d00f [formerly 1c18ec39ea8a1bf1867ee96d6a33a9c595951d1f]] Former-commit-id: 2386dd5890 Former-commit-id: 5395b66d6e		2012-04-09 13:15:50 -05:00
..
build.wes2bridge.utility	Issue #18 - rename jetty.port to web.port; the default for web.port is now 8080. The wes2bridge utilities are now built from source.	2012-04-09 09:32:45 -05:00
com.raytheon.wes2bridge.common	Issue #18 - jvm argument names are no longer used when re-configuring setup.env; renamed variables that referenced jettyPort.	2012-04-09 13:15:50 -05:00
com.raytheon.wes2bridge.configuration	Issue #18 - jvm argument names are no longer used when re-configuring setup.env; renamed variables that referenced jettyPort.	2012-04-09 13:15:50 -05:00
com.raytheon.wes2bridge.datalink	Issue #18 - rename jetty.port to web.port; the default for web.port is now 8080. The wes2bridge utilities are now built from source.	2012-04-09 09:32:45 -05:00
com.raytheon.wes2bridge.manager	Issue #18 - jvm argument names are no longer used when re-configuring setup.env; renamed variables that referenced jettyPort.	2012-04-09 13:15:50 -05:00
com.raytheon.wes2bridge.utility.feature	Issue #18 - rename jetty.port to web.port; the default for web.port is now 8080. The wes2bridge utilities are now built from source.	2012-04-09 09:32:45 -05:00
com.raytheon.wes2bridge.utility.product	Issue #18 - rename jetty.port to web.port; the default for web.port is now 8080. The wes2bridge utilities are now built from source.	2012-04-09 09:32:45 -05:00