From: <jbo...@li...> - 2006-05-18 00:32:53
|
Author: mic...@jb... Date: 2006-05-17 20:32:47 -0400 (Wed, 17 May 2006) New Revision: 4305 Modified: labs/jbossrules/trunk/documentation/manual/en/Chapter-Install/Section-Eclipse.xml Log: Modified: labs/jbossrules/trunk/documentation/manual/en/Chapter-Install/Section-Eclipse.xml =================================================================== --- labs/jbossrules/trunk/documentation/manual/en/Chapter-Install/Section-Eclipse.xml 2006-05-18 00:31:53 UTC (rev 4304) +++ labs/jbossrules/trunk/documentation/manual/en/Chapter-Install/Section-Eclipse.xml 2006-05-18 00:32:47 UTC (rev 4305) @@ -5,10 +5,11 @@ <section> <title>Generating Eclipse Projects</title> - <para> - The drools project has eclipse projects checked in for convenience. However, these are originally generated by maven 2. - If you have maven 2 installed, you can also regenerate the eclipse projects automatically, or even generate it for IntelliJ etc, see the instructions below for this (most people can ignore this section) - </para> + <para>The drools project has eclipse projects checked in for convenience. + However, these are originally generated by maven 2. If you have maven 2 + installed, you can also regenerate the eclipse projects automatically, or + even generate it for IntelliJ etc, see the instructions below for this + (most people can ignore this section)</para> <para><indexterm> <primary>maven</primary> @@ -239,6 +240,10 @@ /jbossrules/update instead of /trunk. They are plain vanilla eclipse feature and site projects.</para> + <para>PLEASE REMEMBER that the plug in in the downloads directory, as a + zip, should also be updated at the same time as the update site (as they + are alternative ways ot getting the same plug in).</para> + <para>Eclipse refreshing plugins in features and sites seems to not work, so what is best is to manually edit the site.xml project and the feature.xml. To do this, open the site.xml file in the drools-ide-update @@ -300,7 +305,8 @@ site.xml.</para> <para>Finally, drop the plugin jar into the /plugins jar directory of the - update site. Now you can upload the site as is, and it will show up as a - new version for Eclipse clients.</para> + update site (get the actual plug in from the exported plugin in the + previous step). Now you can upload the site as is, and it will show up as + a new version for Eclipse clients.</para> </section> </section> \ No newline at end of file |