james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Bagnara <apa...@bago.org>
Subject Re: 0.6 source code
Date Tue, 10 Mar 2009 10:24:09 GMT
Wim Jongman ha scritto:
> Yes, well, I am sorry to hear that. I want to make an OSGi bundle out of
> mime4j to possibly propose it for the eclipse Orbit project. To be able to
> do that, having all sources available to accompany the binaries would make
> this task much easier. I am not at all interested in building the
> application again. In fact, I want to take it as "pure" as possible, direct
> from the source.

"pure" sources are the one without generated stuff.

maven make it simple to invoke javacc automatically while building the
project. If you want you can study the pom and run javacc manually.

I can't believe that to propose a new bundle you have to produce
generated sources. Generated sources are interim artifacts that shuold
not be used anywhere except, maybe, debugging.

BTW, the file we publish in the maven repository:
Should include also generated sources (because the purpose of that file
is to be used in IDE for debugging).


> On Mon, Mar 9, 2009 at 11:52 PM, Bernd Fondermann <bf_jak@brainlounge.de>wrote:
>> Wim Jongman wrote:
>>> Might i suggest that (for the future) the generated files are also bundled
>>> in the source drop? Some people (me for one) do not have maven on their
>>> desktops.
>>> Thanks and best regards,
>>> Wim
>> Well, when dealing with the source dist you should be prepared to have the
>> primary build tool available - which in case of mime4j is maven2.
>> I understand your position, but in this case the generated source files are
>> build artefacts which don't belong in a source distribution.
>>  Bernd

View raw message