Hi All: I previously thought using an project-scoped preference eclipse preference node would properly store the data in your project so that the preference is a per-project setting and so that also these preferences can be shared. This is not the case, as from this article: * /Project scope/. This scope stores values that are specific to a single project in your workspace, such as code formatter and compiler settings. Note that this scope is provided by the org.eclipse.core.resources plug-in, which is not included in the Eclipse Rich Client Platform. This scope will not exist in applications that don’t explicitly include the resources plug-in. Settings saved in the following method, while on a project-scope, are still saved in the workspace, which means they're not persisted to cvs / svn / etc. IScopeContext context = new ProjectScope(project); IEclipsePreferences node = context.getNode(qualifier); if (node != null) node.putDouble(IJBossESBFacetDataModelProperties.ESB_PROJECT_VERSION, 2.0); Does anyone know how to actually put some settings inside the .settings folder of a project the way JDT and WTP do? Thanks. _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

that is also my understanding. Rob, could you show the *exact* code you have done which doesn't store it ?

/max Alexey Kazakov wrote: > We use exactly the same method, which you mentioned, to store Seam > project settings in .setting folder. > See > org.jboss.tools.seam.ui.preferences.SeamSettingsPreferencePage.storeSettings() > > Rob Stryker wrote: > >> Hi All: >> >> I previously thought using an project-scoped preference eclipse >> preference node would properly store the data in your project so that >> the preference is a per-project setting and so that also these >> preferences can be shared. >> >> This is not the case, as from this article: >> >> * /Project scope/. This scope stores values that are specific to a >> single project in your workspace, such as code formatter and >> compiler settings. Note that this scope is provided by the >> org.eclipse.core.resources plug-in, which is not included in the >> Eclipse Rich Client Platform. This scope will not exist in >> applications that don� explicitly include the resources plug-in. >> >> Settings saved in the following method, while on a project-scope, are >> still saved in the workspace, which means they're not persisted to cvs / >> svn / etc. >> >> IScopeContext context = new ProjectScope(project); >> IEclipsePreferences node = context.getNode(qualifier); >> if (node != null) >> node.putDouble(IJBossESBFacetDataModelProperties.ESB_PROJECT_VERSION, 2.0); >> >> >> Does anyone know how to actually put some settings inside the .settings >> folder of a project the way JDT and WTP do? Thanks. >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > ------------------------------------------------------------------------ _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

Don't forget to node.flush(); Denny Xu wrote: > Max Rydahl Andersen wrote: > >> that is also my understanding. >> >> Rob, could you show the *exact* code you have done which doesn't store >> it ? >> > Rob seems to be sleeping ;) > here is this code: > String qualifier = > ESBProjectCorePlugin.getDefault().getDescriptor().getUniqueIdentifier(); > IScopeContext context = new ProjectScope(project); > IEclipsePreferences node = context.getNode(qualifier); > if (node != null) > node.putDouble(IJBossESBFacetDataModelProperties.ESB_PROJECT_VERSION, 2.0); > > when retrieve the value: > IProject p = getProject(); > String qualifier = > ESBProjectCorePlugin.getDefault().getDescriptor().getUniqueIdentifier(); > IScopeContext context = new ProjectScope(p); > IEclipsePreferences node = context.getNode(qualifier); > if (node != null) { > double d = > node.getDouble(IJBossESBFacetDataModelProperties.ESB_PROJECT_VERSION, 1.0); > > Denny > > >> /max >> >> Alexey Kazakov wrote: >> >>> We use exactly the same method, which you mentioned, to store Seam >>> project settings in .setting folder. >>> See >>> org.jboss.tools.seam.ui.preferences.SeamSettingsPreferencePage.storeSettings() >>> >>> Rob Stryker wrote: >>> >>> >>>> Hi All: >>>> >>>> I previously thought using an project-scoped preference eclipse >>>> preference node would properly store the data in your project so that >>>> the preference is a per-project setting and so that also these >>>> preferences can be shared. >>>> >>>> This is not the case, as from this article: >>>> >>>> * /Project scope/. This scope stores values that are specific to a >>>> single project in your workspace, such as code formatter and >>>> compiler settings. Note that this scope is provided by the >>>> org.eclipse.core.resources plug-in, which is not included in the >>>> Eclipse Rich Client Platform. This scope will not exist in >>>> applications that don� explicitly include the resources plug-in. >>>> >>>> Settings saved in the following method, while on a project-scope, are >>>> still saved in the workspace, which means they're not persisted to cvs / >>>> svn / etc. >>>> >>>> IScopeContext context = new ProjectScope(project); >>>> IEclipsePreferences node = context.getNode(qualifier); >>>> if (node != null) >>>> node.putDouble(IJBossESBFacetDataModelProperties.ESB_PROJECT_VERSION, 2.0); >>>> >>>> >>>> Does anyone know how to actually put some settings inside the .settings >>>> folder of a project the way JDT and WTP do? Thanks. >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>> >>>> >>>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> > > ------------------------------------------------------------------------ _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

Max Rydahl Andersen wrote: > that is also my understanding. > > Rob, could you show the *exact* code you have done which doesn't store > it ? > Rob seems to be sleeping ;) here is this code: String qualifier = ESBProjectCorePlugin.getDefault().getDescriptor().getUniqueIdentifier(); IScopeContext context = new ProjectScope(project); IEclipsePreferences node = context.getNode(qualifier); if (node != null) node.putDouble(IJBossESBFacetDataModelProperties.ESB_PROJECT_VERSION, 2.0); when retrieve the value: IProject p = getProject(); String qualifier = ESBProjectCorePlugin.getDefault().getDescriptor().getUniqueIdentifier(); IScopeContext context = new ProjectScope(p); IEclipsePreferences node = context.getNode(qualifier); if (node != null) { double d = node.getDouble(IJBossESBFacetDataModelProperties.ESB_PROJECT_VERSION, 1.0); Denny > /max > > Alexey Kazakov wrote: > >> We use exactly the same method, which you mentioned, to store Seam >> project settings in .setting folder. >> See >> org.jboss.tools.seam.ui.preferences.SeamSettingsPreferencePage.storeSettings() >> >> Rob Stryker wrote: >> >> >>> Hi All: >>> >>> I previously thought using an project-scoped preference eclipse >>> preference node would properly store the data in your project so that >>> the preference is a per-project setting and so that also these >>> preferences can be shared. >>> >>> This is not the case, as from this article: >>> >>> * /Project scope/. This scope stores values that are specific to a >>> single project in your workspace, such as code formatter and >>> compiler settings. Note that this scope is provided by the >>> org.eclipse.core.resources plug-in, which is not included in the >>> Eclipse Rich Client Platform. This scope will not exist in >>> applications that don� explicitly include the resources plug-in. >>> >>> Settings saved in the following method, while on a project-scope, are >>> still saved in the workspace, which means they're not persisted to cvs / >>> svn / etc. >>> >>> IScopeContext context = new ProjectScope(project); >>> IEclipsePreferences node = context.getNode(qualifier); >>> if (node != null) >>> node.putDouble(IJBossESBFacetDataModelProperties.ESB_PROJECT_VERSION, 2.0); >>> >>> >>> Does anyone know how to actually put some settings inside the .settings >>> folder of a project the way JDT and WTP do? Thanks. >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> >>> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> > ------------------------------------------------------------------------ > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev >