| Deployment, Artifacts, and shared TPTP projects. [message #79659] |
Wed, 02 August 2006 22:37  |
 Bertrand Quenin
Messages: 70
Registered: July 2009 |
Member |
|
|
Ok,
Thanks again for this marvelous tool =)
I'm facing the following problem.
- An artifact can reference files that i call "test material" via the
CLASSPATH property of the artifact's default property group. (It's the
general properties tab in the UI).
- As "Deployment ground rules" states:
Absolute Paths
All paths must be absolute. For example, on Windows, "C:\myRootDir" is
appropriate and on Linux "/home/user/myRootDir" is appropriate - all paths
must be absolute and not relative.
Fine, we must use absolute paths.
- let's imagine a basic use case:
Me, Mr. A, create a TPTP java project that includes all necessary assets
for testing including an artifact. As my test requires some "test
material" that is specific for a test suite, i use the CLASSPATH attribute
to reference files to be deployed. As paths must be absolute, i get a
"platform specific" file name in my artifact.
I decide to check in this project in my favorite source manager.
Mr. B, checks Mr A's project out and get all the project stuff. Mr B
tries to launch a test using the artifact that Mr. A creates. Dang ! No
files are deployed since all paths (absolute, sic) are meaningless in Mr B
environment.
What's the solution ? How make Mr. B happy again ?
PS: Of course you can use the project classpath to create pseudo "platform
independant" test material (by adding a class folder for example in the
project buildpath). But the problem is that this material is a global one
and can't be using for a particular test suite ...
Help !
Regards
BQ.
|
|
|
| Re: Deployment, Artifacts, and shared TPTP projects. [message #79689 is a reply to message #79659] |
Wed, 02 August 2006 23:01  |
Bertrand Quenin
Messages: 70
Registered: July 2009 |
Member |
|
|
In fact,
The following things would be great:
Replace this "ugly!!" artifact general properties tab with a sexy UI
editor extension, especially for "test material" (understand files to be
deployed) by adding a basic File/FolderSelectionDialog that will
reinterpret the output in CLASSPATH properties.
Another thing that would be really handy is to have the possibility to
use symbolic variables in a classpath entry value (like everywhere in
eclipse) and not only these "annoying" absolute paths.
I have already develop such an UI plugin (at least for FileDialog , not
for symbolic variables): The only reason i'm asking is because it's
possible to extend the TPTP UI (with editor, editor extension, etc.) and
making a sexy UI that enters ugly paths is posible. But, introducing
symbolic variables in artifact CLASSPATH properties need a processing
before test execution (in order to replace the symbolic variable with its
effective value and giving the framework its damn absolute path =) ). It
seems that there's no extension point giving this possibility (process
artifact classpath entries before test execution).
There are 2 solutions for me:
- Perhaps i missed the extension point that match my needs, then i can
implement this functionality on y own.
- if it's not the case, i have to directly change the TPTP source code
and i don't want to (i want to develop an extension, not a modification)
so i have to propose and vote for this FIR in order to make you implement
it =)
Regards
BQ.
|
|
|
| Re: Deployment, Artifacts, and shared TPTP projects. [message #103745 is a reply to message #79689] |
Mon, 09 July 2007 15:45 |
Paul Slauenwhite
Messages: 975
Registered: July 2009 |
Senior Member |
|
|
Hi Bertrand,
Agreed that absolute paths in the general properties of all test
artifacts is not potable. I have opened defect
https://bugs.eclipse.org/bugs/show_bug.cgi?id=195846 to address this issue
in TPTP. I would assume workspace-relative paths (e.g. using Eclipse
symbolic variables) is one viable solution. Unfortunately, there is no
extension point for providing your own custom preprocessor for general
properties.
Paul
"Bertrand Quenin" <bquenin@axway.com> wrote in message
news:70929e5e14a2f8e87708c9cd98754adc$1@www.eclipse.org...
> In fact,
>
> The following things would be great:
>
> Replace this "ugly!!" artifact general properties tab with a sexy UI
> editor extension, especially for "test material" (understand files to be
> deployed) by adding a basic File/FolderSelectionDialog that will
> reinterpret the output in CLASSPATH properties.
> Another thing that would be really handy is to have the possibility to
> use symbolic variables in a classpath entry value (like everywhere in
> eclipse) and not only these "annoying" absolute paths.
>
> I have already develop such an UI plugin (at least for FileDialog , not
> for symbolic variables): The only reason i'm asking is because it's
> possible to extend the TPTP UI (with editor, editor extension, etc.) and
> making a sexy UI that enters ugly paths is posible. But, introducing
> symbolic variables in artifact CLASSPATH properties need a processing
> before test execution (in order to replace the symbolic variable with its
> effective value and giving the framework its damn absolute path =) ). It
> seems that there's no extension point giving this possibility (process
> artifact classpath entries before test execution).
> There are 2 solutions for me:
> - Perhaps i missed the extension point that match my needs, then i can
> implement this functionality on y own.
> - if it's not the case, i have to directly change the TPTP source code and
> i don't want to (i want to develop an extension, not a modification) so i
> have to propose and vote for this FIR in order to make you implement it =)
>
> Regards
> BQ.
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03276 seconds
] 
Search
Help
Register
Login
Home
