Daniel Rall <[EMAIL PROTECTED]> writes:

>On Sat, 24 Sep 2005, Henning P. Schmiedehausen wrote:

>> "Will Glass-Husain" <[EMAIL PROTECTED]> writes:
>> 
>> >I'd like to keep the javacc output in the source tree.
>> 
>> That's perfectly fine with me. Another idea: Don't keep it in src/java
>> but e.g. in src/javacc-generated and then merge the two trees at build
>> time.

>I personally rather like this idea, since it provides a clear separation,
>but doesn't it make it slightly more difficult on people using IDEs?

With Eclipse, you can define multiple source locations, so this is no
problem. That should be possible with other IDEs, too. Only slight
annoying thing would be maven but there is a defined workaround in the
FAQ and as we are not generating the source code on the fly (like with
did with the Torque peer in Turbine which turned out to be One Big
Mistake (TM)) and there is no overlap between the tree in
src/<javacc-generated> and src/java, this should be no big deal.

I want to do some test with this, once I got the ant build worked out
as discussed and reduced the ~190 Findbugs issues that the current
code base has.

        Best regards
                Henning


-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
[EMAIL PROTECTED]        +49 9131 50 654 0   http://www.intermeta.de/

RedHat Certified Engineer -- Jakarta Turbine Development  -- hero for hire
   Linux, Java, perl, Solaris -- Consulting, Training, Development

                      4 - 8 - 15 - 16 - 23 - 42

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to