Re: [hyades-dev] dynamic classpath option missing on the M7 driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [hyades-dev] dynamic classpath option missing on the M7 driver

From: Suzanne Dirkers <dirkers@xxxxxxxxxx>
Date: Wed, 18 Feb 2004 14:09:54 -0500
Delivered-to: hyades-dev@xxxxxxxxxxx
List-archive: <http://dev.eclipse.org/pipermail/hyades-dev/>
List-help: <mailto:hyades-dev-request@eclipse.org?subject=help>
List-subscribe: <http://dev.eclipse.org/mailman/listinfo/hyades-dev>, <mailto:hyades-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <http://dev.eclipse.org/mailman/listinfo/hyades-dev>, <mailto:hyades-dev-request@eclipse.org?subject=unsubscribe>

Thanks but I couldn't get that to work at all. I had to go to an earlier verson to be able to build successfully, one that actually had that classpath dependency option in there.

Suzanne

Valentina Popescu <popescu@xxxxxxxxxx>
Sent by: hyades-dev-admin@xxxxxxxxxxx

02/18/2004 01:44 PM

Please respond to
hyades-dev

To	hyades-dev@xxxxxxxxxxx
cc
Subject	[hyades-dev] dynamic classpath option missing on the M7 driver

Suzanne, the classpath option has been completely removed from the latest M7 driver.
They made this a default option so you don't have to do anything special to use dynamic classpath for dependant plugins

There have been some problems on the Hyades HEAD related to the logging.core plugin but they should all be solved by now. I am looking at our local build on hoplite 4 ( build this morning ) and I don't see any problems

Thank you,
Valentina Popescu
IBM Toronto Labs, popescu@xxxxxxxxxx
(905)413-2412 (tie-line 969)
fax: (905) 413-4920

hyades-dev-request@xxxxxxxxxxx
Sent by: hyades-dev-admin@xxxxxxxxxxx

02/18/2004 12:00 PM

Please respond to
hyades-dev

To	hyades-dev@xxxxxxxxxxx
cc
Subject	hyades-dev digest, Vol 1 #157 - 3 msgs

Send hyades-dev mailing list submissions to hyades-dev@xxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit http://dev.eclipse.org/mailman/listinfo/hyades-dev or, via email, send a message with subject or body 'help' to hyades-dev-request@xxxxxxxxxxx You can reach the person managing the list at hyades-dev-admin@xxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of hyades-dev digest..." Today's Topics: 1. org.eclipse.hyades.test.tests CVS module created on 1.3 and 3.0 streams (Valentina Popescu) 2. Re: org.eclipse.hyades.test.tests CVS module created on 1.3 and 3.0 streams (Suzanne Dirkers) --__--__-- Message: 1 To: hyades-dev@xxxxxxxxxxx Cc: RND-ADTC-CAN@xxxxxxxxxx From: Valentina Popescu <popescu@xxxxxxxxxx> Date: Tue, 17 Feb 2004 15:19:59 -0500 Subject: [hyades-dev] org.eclipse.hyades.test.tests CVS module created on 1.3 and 3.0 streams Reply-To: hyades-dev@xxxxxxxxxxx This is a multipart message in MIME format. --=_alternative 006FDF3E85256E3D_= Content-Type: text/plain; charset="US-ASCII" The plugin used to store Hyades Test tool junit testcases is now in CVS, on the Hyades_v1_3_0 branch and HEAD stream. The plugin name is org.eclipse.hyades.test.tests and will contain all junit testcases required for the Hyades Test components. I will notify you when the CVS module used to check in trace and log testcases will be created. Please follow these steps when checking in code into org.eclipse.hyades.test.tests plugin 1. Make sure your workspace is set to use dynamic classpath for dependent plugins. By default, the option is unset. Go to the Window > Preferences > Plug-In Development > Java Build Path Control and check 'Use dynamic classpath for dependent plugins' 2. Every group contributing to the Hyades Test tool may want to have a separate source directory where the testcases and any other non java files will be stored. How to create a separate source directory : Assuming that HttpTests will be the folder containing http testcases : - create a new folder under the org.eclipse.hyades.test.tests named HttpTests - open the build.properties file and update the source location with this new folder : source.tests.jar = HyadesExtensions/,\ HttpTests/ ( to test the change, you will have export the plugin, delete the plugin from the workspace then reimport the plugin; the HttpTests folder should be seen as a source folder in Java Perspective ) 3. Add your testscases to the source folder, together with any other files you will need to run the scenarios. As usual, contact Qiyan Li/Toronto/IBM if you have any CVS related problems Thank you, Valentina Popescu IBM Toronto Labs, popescu@xxxxxxxxxx (905)413-2412 (tie-line 969) fax: (905) 413-4920 --=_alternative 006FDF3E85256E3D_= Content-Type: text/html; charset="US-ASCII" The plugin used to store Hyades Test tool junit testcases is now in CVS, on the Hyades_v1_3_0 branch and HEAD stream. The plugin name is org.eclipse.hyades.test.tests and will contain all junit testcases required for the Hyades Test components. I will notify you when the CVS module used to check in trace and log testcases will be created. Please follow these steps when checking in code into org.eclipse.hyades.test.tests plugin 1. Make sure your workspace is set to use dynamic classpath for dependent plugins. By default, the option is unset. Go to the Window > Preferences > Plug-In Development > Java Build Path Control and check 'Use dynamic classpath for dependent plugins' 2. Every group contributing to the Hyades Test tool may want to have a separate source directory where the testcases and any other non java files will be stored. How to create a separate source directory : Assuming that HttpTests will be the folder containing http testcases : - create a new folder under the org.eclipse.hyades.test.tests named HttpTests - open the build.properties file and update the source location with this new folder : source.tests.jar = HyadesExtensions/,\                    HttpTests/ ( to test the change, you will have export the plugin, delete the plugin from the workspace then reimport the plugin; the HttpTests folder should be seen as a source folder in Java Perspective ) 3. Add your testscases to the source folder, together with any other files you will need to run the scenarios. As usual, contact Qiyan Li/Toronto/IBM if you have any CVS related problems Thank you, Valentina Popescu IBM Toronto Labs,   popescu@xxxxxxxxxx (905)413-2412         (tie-line  969) fax: (905) 413-4920 --=_alternative 006FDF3E85256E3D_=-- --__--__-- Message: 2 To: hyades-dev@xxxxxxxxxxx Subject: Re: [hyades-dev] org.eclipse.hyades.test.tests CVS module created on 1.3 and 3.0 streams From: Suzanne Dirkers <dirkers@xxxxxxxxxx> Date: Wed, 18 Feb 2004 10:13:51 -0500 Reply-To: hyades-dev@xxxxxxxxxxx This is a multipart message in MIME format. --=_alternative 00546CD785256E3E_= Content-Type: text/plain; charset="US-ASCII" Where did the checkbox for 'use dynamic classpath for dependent plugins' go in Eclipse 3? It's not where you describe below. And I cannot get hyades to build at 3.0 off the HEAD stream. Thanks, Suzanne Valentina Popescu <popescu@xxxxxxxxxx> Sent by: hyades-dev-admin@xxxxxxxxxxx 02/17/2004 03:19 PM Please respond to hyades-dev To hyades-dev@xxxxxxxxxxx cc RND-ADTC-CAN@xxxxxxxxxx Subject [hyades-dev] org.eclipse.hyades.test.tests CVS module created on 1.3 and 3.0 streams The plugin used to store Hyades Test tool junit testcases is now in CVS, on the Hyades_v1_3_0 branch and HEAD stream. The plugin name is org.eclipse.hyades.test.tests and will contain all junit testcases required for the Hyades Test components. I will notify you when the CVS module used to check in trace and log testcases will be created. Please follow these steps when checking in code into org.eclipse.hyades.test.tests plugin 1. Make sure your workspace is set to use dynamic classpath for dependent plugins. By default, the option is unset. Go to the Window > Preferences > Plug-In Development > Java Build Path Control and check 'Use dynamic classpath for dependent plugins' 2. Every group contributing to the Hyades Test tool may want to have a separate source directory where the testcases and any other non java files will be stored. How to create a separate source directory : Assuming that HttpTests will be the folder containing http testcases : - create a new folder under the org.eclipse.hyades.test.tests named HttpTests - open the build.properties file and update the source location with this new folder : source.tests.jar = HyadesExtensions/,\ HttpTests/ ( to test the change, you will have export the plugin, delete the plugin from the workspace then reimport the plugin; the HttpTests folder should be seen as a source folder in Java Perspective ) 3. Add your testscases to the source folder, together with any other files you will need to run the scenarios. As usual, contact Qiyan Li/Toronto/IBM if you have any CVS related problems Thank you, Valentina Popescu IBM Toronto Labs, popescu@xxxxxxxxxx (905)413-2412 (tie-line 969) fax: (905) 413-4920 --=_alternative 00546CD785256E3E_= Content-Type: text/html; charset="US-ASCII" Where did the checkbox for 'use dynamic classpath for dependent plugins' go in Eclipse 3? It's not where you describe below. And I cannot get hyades to build at 3.0 off the HEAD stream. Thanks, Suzanne <table width=100%> <tr valign=top> <td width=40%>Valentina Popescu <popescu@xxxxxxxxxx> Sent by: hyades-dev-admin@xxxxxxxxxxx 02/17/2004 03:19 PM <table border> <tr valign=top> <td bgcolor=white> <div align=center>Please respond to hyades-dev</div></table> <td width=59%> <table width=100%> <tr> <td> <div align=right>To</div> <td valign=top>hyades-dev@xxxxxxxxxxx <tr> <td> <div align=right>cc</div> <td valign=top>RND-ADTC-CAN@xxxxxxxxxx <tr> <td> <div align=right>Subject</div> <td valign=top>[hyades-dev] org.eclipse.hyades.test.tests CVS module created on 1.3 and 3.0 streams</table> <table> <tr valign=top> <td> <td></table> </table> The plugin used to store Hyades Test tool junit testcases is now in CVS, on the Hyades_v1_3_0 branch and HEAD stream. The plugin name is org.eclipse.hyades.test.tests and will contain all junit testcases required for the Hyades Test components. I will notify you when the CVS module used to check in trace and log testcases will be created. Please follow these steps when checking in code into org.eclipse.hyades.test.tests plugin 1. Make sure your workspace is set to use dynamic classpath for dependent plugins. By default, the option is unset. Go to the Window > Preferences > Plug-In Development > Java Build Path Control and check 'Use dynamic classpath for dependent plugins' 2. Every group contributing to the Hyades Test tool may want to have a separate source directory where the testcases and any other non java files will be stored. How to create a separate source directory : Assuming that HttpTests will be the folder containing http testcases : - create a new folder under the org.eclipse.hyades.test.tests named HttpTests - open the build.properties file and update the source location with this new folder : source.tests.jar = HyadesExtensions/,\                   HttpTests/ ( to test the change, you will have export the plugin, delete the plugin from the workspace then reimport the plugin; the HttpTests folder should be seen as a source folder in Java Perspective ) 3. Add your testscases to the source folder, together with any other files you will need to run the scenarios. As usual, contact Qiyan Li/Toronto/IBM if you have any CVS related problems Thank you, Valentina Popescu IBM Toronto Labs,   popescu@xxxxxxxxxx (905)413-2412         (tie-line  969) fax: (905) 413-4920 --=_alternative 00546CD785256E3E_=-- --__--__-- _______________________________________________ hyades-dev mailing list hyades-dev@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/hyades-dev End of hyades-dev Digest

References:
- [hyades-dev] dynamic classpath option missing on the M7 driver
  - From: Valentina Popescu

Prev by Date: [hyades-dev] dynamic classpath option missing on the M7 driver
Next by Date: Re: [hyades-dev] dynamic classpath option missing on the M7 driver
Previous by thread: [hyades-dev] dynamic classpath option missing on the M7 driver
Next by thread: Re: [hyades-dev] dynamic classpath option missing on the M7 driver
Index(es):
- Date
- Thread

Breadcrumbs