You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by jerome lacoste <je...@gmail.com> on 2006/07/01 06:09:08 UTC

Re: Best practise: handling xdoclet generated sources

On 6/30/06, Graham Leggett <mi...@sharp.fm> wrote:
> Hi all,
>
> I am trying to figure out the proper maven based layout for some existing
> ant code that uses xdoclet for code generation (standard EJB stuff).
>
> From what I have seen to date, the way so far is for maven to ask xdoclet
> to generate the code in the temporary target/generated-src directory.
>
> The trouble is that the static code in the project code references the
> generated code, and so won't build in an IDE like eclipse, as the
> generated-src directory doesn't exist initially, or after an mvn clean.
>
> I can set the project up so that target/generated-src is in
> src/main/generated-src (for example), which solves the Eclipse problem,
> but then the code is not regenerated on a clean.
>
> Can anyone suggest a best practise that is capable of keeping Eclipse
> happy, and mvn clean working, both at the same time?

With IDEA, I manually add the source directories so that idea is
capable of building my project. You might need to do the same thing
with eclipse.

Jerome

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org