[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [dsdp-tm-dev] Re: RSE server (dstore) packaging
|
Hi Dave,
is there a chance factoring out the stuff that requires 1.4
into
a separate JAR, or is it too deeply
nested?
Would it help if Patrick ported the servers to 1.3 for his
own use,
submitted a patch, and we committed
his changes into a
"13_compatible" branch to start
with?
This could probably enable us to build a "13_compatible"
dstore
daemon regularly.
Cheers,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management Project
Lead, DSDP PMC Member
Hi,
Regarding downgrading the dstore server code to 1.3, if
you set the compiler compliance level to 1.3, the dstore.core, dstore,extra
and miners seem to compile fine.
There are a couple problems though:
1) The JDK didn't add their SSL support until 1.4 - so it
requires extra packages and the dstore code would have to change as a result.
2) The JDK didn't add their
regex support until 1.4 - so again there are extra packages
____________________________________
David McKnight
Phone: 905-413-3902 , T/L: 969-3902
Internet:
dmcknigh@xxxxxxxxxx
Mail:
D1/YFY/8200/TOR
____________________________________
Martin Oberhuber
<martin.oberhuber@xxxxxxxxxxxxx>
Sent by: dsdp-tm-dev-bounces@xxxxxxxxxxx
22/08/2008 06:51 AM
|
Please respond
to
Target Management developer discussions
<dsdp-tm-dev@xxxxxxxxxxx> |
|
|
To
| Patrick Tassé
<patrick.tasse@xxxxxxxxx>, Target Management developer
discussions <dsdp-tm-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| [dsdp-tm-dev] Re: RSE server
(dstore) packaging |
|
Hello Patrick,
these questions are dstore specific, others might
be more
knowledgeable here than I am, but here's the releng
related
answes:
* We build the rseserver-*.tar archives as part of
our
nightly releaese engineering process, see the
org.eclipse.rse.build project (shortly to be replaced
by
org.eclipse.tm.build)
* Right, the JARs are the same in all server
packages,
only the *.sh / *.pl / *.bat scripts differ
* I'd
think that "Create Jar" should work to replace
a pre-buildt jar by
something from your workspace,
but I can't say for sure --
forwarding to the Developer
Mailing list for comments
*
Downgrading to require only Java 1.3 on the server
seems a good idea
to me, but I do not know if it is
technically viable -
Dave?
Did you consider TCF or SSH on the server side? Why do
you
think you'd want dstore?
Cheers,
--
Martin Oberhuber, Senior
Member of Technical Staff, Wind River
Target Management Project Lead, DSDP
PMC Member
http://www.eclipse.org/dsdp/tm
Patrick Tassé
wrote:
> I'm working on a Eclipse Tracing prototype for Ericsson's CPP
platform
> and am evaluating the use of RSE for this task. I have a few
questions.
>
> 1) How are the rse-3.0-xxxxx.tar archives from the
DSDP-TM downloads
> page created? I saw that you can do Create JAR by
right-clicking on a
> .jardesc file in the project, is this how you do
it? But is there an
> automatic way to package all the .jar files and
scripts corresponding to
> the target platform in an archive, or is it
done manually (Export ->
> Archive File?) or with an external script
not part of the project files?
>
> 2) Is there any difference in
the contents of the .jar files or in build
> options depending on the
target platform? I'm assuming not since I saw
> for example all 5
implementations of UniversalXxxxxProcessHandler.class
> in the Linux
archive's jar files.
>
> 3) Some of our CPP nodes only have Java
1.3.1 installed. I saw that
> there is a hard requirement for Java 1.4
when launching the server, but
> by changing the Executing Environment
of the JRE System Library to
> J2SE-1.3 in the RSE server projects'
Java Build Path, I found that the
> only incompatibilities occur when
the DataStore is using SSL, and in the
> document/xml handling of the
SystemMessageFile. Do you think that an
> 'amputated' RSE server could
be viable without those two things, in case
> Java 1.3.1 in the server
side becomes a requirement for our prototype?
>
> Thank
you,
> Patrick
>
>
_______________________________________________
dsdp-tm-dev mailing
list
dsdp-tm-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev
