Dima Berastau wrote: > 1. generating/updating project.xml from .classpath and .project would > already be useful.
Not sure about .project, but .classpath file should IMO be generated from the POM, never the other way around simply because POM has more information in it. The plugin could watch the POM (and possibly it's ancestors) for changes and ask the user to update the affected .classpath files automatically. > 2. running maven's goals from eclipse runtime Building atop of Eclipse Ant plugin would be probably the best choice here. > 3. as would the effort to keep the 2 in sync automatically, Not sure what you mean here, sorry > 4. an editor with outline for project.xml/project.properties would also be > very handy. I envision it as wizard-like tabbed editor like the one provided for plugin descriptors by Eclipse PDE. > I have nothing against JSRs as long as they are useful (= were designed as a > result of experience based on people using technology) and flexible (= it > shouldn't take 1 year to change a standard). > Personally, I think that it would be a lot faster to write a plugin and > start making use of it (if it turns out to be useful people with a lot of > free time can standardize it later). That would also be my preferable choice. :-) Let's make something that works, then extract the important bits later to make a stnadard, and finally implement the thing the right way and scrap the prototype. R. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
