Author: nickboldt Date: 2012-01-22 23:45:00 -0500 (Sun, 22 Jan 2012) New Revision: 38024 Added: trunk/central/README.Central.localhost.testing.txt trunk/central/README.Central.milestone.testing.txt Removed: trunk/central/README.localhost.testing.txt trunk/central/README.milestone.testing.txt Log: rename and tweak READMEs to match JBDS versions (JBDS-1959) Added: trunk/central/README.Central.localhost.testing.txt =================================================================== --- trunk/central/README.Central.localhost.testing.txt (rev 0) +++ trunk/central/README.Central.localhost.testing.txt 2012-01-23 04:45:00 UTC (rev 38024) @@ -0,0 +1,47 @@ +To build/test locally: + +0. Run a web server locally, so you can access central/site/target/site/jbosstools-directory.xml via an http:// URL. You have many options for this. Here's one: + + su + cd /tmp; wget -nc http://elonen.iki.fi/code/nanohttpd/NanoHTTPD.java + javac NanoHTTPD.java; java NanoHTTPD -d /path/to/parent/folder/for/central/ + +1. If you need to iterate through changes to the product/plugins/com.jboss.jbds.central plugin, you can do so, rebuild it, and reinstall it into a running JBDS instance. + + Help > Install new > file:///path/to/product/site/target/site/ + +For example, you might want to edit central/plugins/org.jboss.tools.central/src/org/jboss/tools/central/configurators/DefaultJBossCentralConfigurator.java to set a new path for JBOSS_DISCOVERY_DIRECTORY_3_3_0_XML: + + private static final String JBOSS_DISCOVERY_DIRECTORY_3_3_0_XML = "http://localhost/central/site/target/site/jbosstools-directory.xml"; // for testing on localhost + +2. Rebuild: + + cd /path/to/central; mvn clean install + +3. Verify the directory.xml file is generated, and http-accessible: + + firefox http://localhost/central/site/target/site/jbosstools-directory.xml + +4. Verify central/site/target/site/jbosstools-directory.xml points at the updated version of the o.j.t.central plugin in /path/to/central/site/target/site/plugins/ + + Note: if built locally, there should be no Jenkins/Hudson buildID Hxxx number in the version suffix, eg., + 1.0.0.v20120120-1459-Beta1 + instead of + 1.0.0.v20120120-1459-H123-Beta1 + +5. Launch JBDS like this: + + ./eclipse -vmargs -Djboss.discovery.directory.url=file:///path/to/central/site/target/site/jbosstools-directory.xml + or + ./eclipse -vmargs -Djboss.discovery.directory.url=http://localhost/central/site/target/site/jbosstools-directory.xml + +6. Select 'Help > Jboss Central' (if not already loaded). Check the 'Software/Updates' tab to review contents of the discovery site (as per org.jboss.tools.central.discovery/plugin.xml). Hit the refresh icon if necessary to see changes. + +-- + +To iterate through local changes: + +7. Change product/plugins/org.jboss.tools.central.discovery/plugin.xml. + +8. Repeat steps 2-6. If you rebuild the central plugin, you must reinstall it; the discovery plugin can simply be rebuilt and refreshed w/o needing to install anything new. + Copied: trunk/central/README.Central.milestone.testing.txt (from rev 38023, trunk/central/README.milestone.testing.txt) =================================================================== --- trunk/central/README.Central.milestone.testing.txt (rev 0) +++ trunk/central/README.Central.milestone.testing.txt 2012-01-23 04:45:00 UTC (rev 38024) @@ -0,0 +1,20 @@ +JBoss Central has a "software/update" page which gets its content from a hardcoded URL, set in the org.jboss.tools.central plugin. + +The published (current) milestone release URL is + + http://download.jboss.org/jbosstools/updates/development/indigo/jbosstool... + +The stable branch (upcoming milestone) URL is + + http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/jbos... + +The unstable trunk URL is + + http://download.jboss.org/jbosstools/updates/nightly/core/trunk/jbosstool... + +The same as used for all milestone releases of JBoss Tools; should you want to pull the list of available updates from a NEWER directory file (eg., during a QE cycle when there's a milestone candidate available, but the published milestone site still contains the PREVIOUS milestone), you can do so using a commmandline flag. + +Thus, when running Eclipse, simply pass in an alternate URL like this: + + ./eclipse -vmargs -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/jbosstools-directory.xml + Deleted: trunk/central/README.localhost.testing.txt =================================================================== --- trunk/central/README.localhost.testing.txt 2012-01-23 04:44:50 UTC (rev 38023) +++ trunk/central/README.localhost.testing.txt 2012-01-23 04:45:00 UTC (rev 38024) @@ -1,27 +0,0 @@ -To build/test/iterate locally: - -0. Run a web server locally, so you can access central/site/target/site/jbosstools-directory.xml via an http:// URL. You have many options for this. Here's one: - - su - cd /tmp; wget -nc http://elonen.iki.fi/code/nanohttpd/NanoHTTPD.java - javac NanoHTTPD.java; java NanoHTTPD -d /path/to/parent/folder/for/central/ - -1. edit central/plugins/org.jboss.tools.central/src/org/jboss/tools/central/configurators/DefaultJBossCentralConfigurator.java to set a new path for JBOSS_DISCOVERY_DIRECTORY_3_3_0_XML: - - private static final String JBOSS_DISCOVERY_DIRECTORY_3_3_0_XML = "http://localhost/central/site/target/site/jbosstools-directory.xml"; // for testing on localhost - -2. build central/ folder: - - cd /path/to/central; mvn clean install - -3. verify the directory.xml file is generated, and http-accessible: - - firefox http://localhost/central/site/target/site/jbosstools-directory.xml - -4. verify central/site/target/site/jbosstools-directory.xml points at the updated version of the o.j.t.central plugin in /path/to/central/site/target/site/plugins/ - -5. install updated o.j.t.central plugin into new Eclipse instance from http://localhost/central/site/target/site/ (or local file:// path if you prefer). Restart when prompted. - -6. Change central/plugins/org.jboss.tools.central/plugin.xml, then repeat steps 2-5. - - Deleted: trunk/central/README.milestone.testing.txt =================================================================== --- trunk/central/README.milestone.testing.txt 2012-01-23 04:44:50 UTC (rev 38023) +++ trunk/central/README.milestone.testing.txt 2012-01-23 04:45:00 UTC (rev 38024) @@ -1,21 +0,0 @@ -JBoss Central has a "software/update" page which gets its content from a hardcoded URL, set in the org.jboss.tools.central plugin. - -The published (current) milestone release URL is - - http://download.jboss.org/jbosstools/updates/development/indigo/jbosstool... - -The stable branch (upcoming milestone) URL is - - http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/jbos... - -The unstable trunk URL is - - http://download.jboss.org/jbosstools/updates/nightly/core/trunk/jbosstool... - -The same as used for all milestone releases of JBoss Tools; should you want to pull the list of available updates from a NEWER directory file (eg., during a QE cycle when there's a milestone candidate available, but the published milestone site still contains the PREVIOUS milestone), you can do so using a commmandline flag. - -Thus, when running Eclipse or JBDS, simply pass in an alternate URL like this: - -./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/jbosstools-directory.xml -./eclipse -vmargs -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/jbosstools-directory.xml -