|Re: ws:project tag: How to specify a project type? [message #42676 is a reply to message #42615]
||Wed, 05 March 2008 15:57
| Paul Elder
Registered: July 2009
At the Eclispe Resource API level, there is no real concept of a project
type. The information you pass to the APIs gets reflected in the .project
file (which is an XML document). Some project 'types' - e.g. Java have
secondard files as well (e.g. .classpath).
Rather than try to know all of this things in the engine (a futile task), it
is assumed that you will simply generated all the files associated with the
type of project you want to produce:
<ws:file path=".project" template="projectXType.jet"/>
The best way to find out what files need to be created is to run the New
project wizard, and take a look. Removing explorer filters of . files is
"Steve Robenalt" <firstname.lastname@example.org> wrote in message
> Hi Paul,
> I have a large project built around JET2 that generates code for multiple
> platforms in C and Java, as well as XML and HTML artifacts. During the
> generation phase, a single source model (EMF-based model) leads to the
> creation of multiple projects, each of which contain the appropriate
> artifacts. These projects are created using the ws:project workspace tag.
> The problem is that ws:project creates an untyped project, so (for
> example) the Java-based artifacts don't compile, since the project doesn't
> have the Java nature assigned to them.
> I've been mulling over the idea of creating an addNature tag which would
> allow me to set the project type after creation. However, I'm wondering if
> there is either a current or planned enhancement to either the ws:project
> tag or a new tag that would achieve the same thing.
> Thanks for any help you can offer.
> Steve Robenalt
Powered by FUDForum
. Page generated in 0.12086 seconds