Community
Participate
Working Groups
org.eclipse.ptp.rdt.server.dstore needs a way to build within the workspace to be able to test changes. Similar to the build.sh of jproxy. Also it needs to be added to project_sets. (of course easy but filing because we can't commit - so that it is not forgotten)
Before this could be done, you'd need to work out a way to build the rdt server locally. Currently the only way to do this is to obtain a copy of the RSE dstore server from the RSE downloads site, unpack the server, manually create each of the jar's from the *.jardesc files in the org.eclipe.ptp.rdt.core.remotejars plugin, copy these jars to the dstore server, manually create a jar-in-jar manifest, and jar up the server. Most of this is done by the build.xml in org.eclipse.ptp.rdt.remotejars, but it doesn't work from the command line, only as part of the PTP build. It may be possible to modify the build.xml to work from the command line also (or be driven from a shell script that handles any additional actions).
Why don't we just take the JAR files from ${eclipse.home}/plugins and only add the compiled classes from the workspace which are part of PTP?
Because thats not how the headless build works.
(In reply to comment #3) > Because thats not how the headless build works. Of course it would be nicer to have the same method for headless and workspace, but I meant my suggestion primarily/only for the workspace built.
CDT is changing to Maven/Tycho. Would this solve this problem if we changed too? I don't know what is involved and whether it is a good idea. I'm just asking because I think it would be nice to solve this for Juno.
I don't think this is an issue any more. PBS support has moved to the JAXB RM which no longer requires a server.
Sorry, brain dead. Ignore last comment.
Assuming this will not be fixed.