[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
These should all be pointing to the control ID. Please fix.
Thanks,
Greg
On Mar 25, 2011, at 1:54 PM, Albert L. Rossi wrote:
> Roland,
>
> this looks like a mixup from a recent refactoring that was done. I see inconsistent ids for:
>
> org.eclipse.ptp.rm.mpi.mpich2.resourceManager
> org.eclipse.ptp.rm.slurm.resourceManager
> org.eclipse.ptp.rm.ibm.ll.LLServiceProvider
> org.eclipse.ptp.rm.ibm.pe.resourceManager
>
> I don't know what Greg wants to do with legacy RMs; control should only really apply to the JAXB implementation.
>
> Al
>
> ----- Roland Schulz <roland@xxxxxxx> wrote:
>> Hi,
>>
>> for the CVS version of the PBS RM, I noticed it is not possible to
>> create a new RM because getRMConfigurationWizardPageFactory(controlId)
>> returns null. This seems to be because the
>> org.eclipse.ptp.ui.rmConfigurationWizards extension point id is
>> org.eclipse.ptp.rm.pbs.resourceManager while the correct controlId is
>> org.eclipse.ptp.rm.pbs.control.
>>
>> Can I go ahead and fix the extension point ID or is the correct
>> approach to change something else?
>>
>> Roland
>>
>> --
>> ORNL/UT Center for Molecular Biophysics cmb.ornl.gov
>> 865-241-1537, ORNL PO BOX 2008 MS6309
>> _______________________________________________
>> ptp-dev mailing list
>> ptp-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>
>
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev