[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[News.eclipse.technology.packaging] Re: Welcome to eclipse.technology.packaging

I was glad to see this project proposal, but have a few questions that don't appear to be in scope based on the proposal. Are there guidelines or standards on how workspaces can be packaged/shared? My usecase is that I have a set of features/plugins to roll out to some new users. I'd like to get them started as soon as possible with a configuration that is tuned to a new user. Examples of some things included; other s/w distributions like the JDK and Tomcat, a sample project so people can kick the tires on the plugins, and some customizations like having some snippets prepoulated. Is there something better than workspaces to manage this?

We fixed the location and included the workspace, but this isn't very flexible. We didn't want to force the users through steps like updating the preferences to point to the proper location for the Tomcat installation and change the project properties to set JSF library references. How is this handled elsewhere? Installing the workspace and then making changes for a new install location appeared to be messy. Importing the projects didn't do the trick because the users would still have a decent amount of configuration to take care of on their own.

Any comments would be appreciated.

Thanks,
John