I guess I'm missing something. I thought the point was to have the source for dependent projects that are snapshots in the jars. That makes sense to me. In that case I'm not sure how having a build property helps since the source would need to be in the jar that is part of the Cocoon download.
If this discussion is about putting Cocoon source in jars, I'm not sure what the point of that is since you have to download the source to build. Ralph Sylvain Wallez said: >>>> >>> "exclude.archive-sources" is fine if you think it better fits the >>> build property naming scheme. Or better "exclude.source-in-jars" >>> which is a noun instead of a verb? >> >> >> Used include.sources-in-jars. I don't like the exclude syntax so much >> and there are already other include.* properties (see below that added >> one). Sometimes I will change all excludes in includes as it was >> already done for the blocks. > > > Agree. "include" is more understable than "exclude" which is a negation. > > Sylvain
