+1. We do this all the time at Apache. Fwiw, maven.apache.org isn't
any official repo. it's repository.apache.org (for snapshots) and
repo1.maven.org for releases.

On Tue, Oct 20, 2009 at 9:31 AM, Jason van Zyl <[email protected]> wrote:
> On 2009-10-20, at 5:16 AM, Svante Schubert wrote:
>
>> Hi,
>>
>> I am a Maven fan and stumbled over a this:
>>
>> http://sourceforge.net/mailarchive/forum.php?thread_name=B4EA6C26949B4127960EE2A00780F643%40Sealion&forum_name=saxon-help
>>
>> Is this true? In any case, thought you might want to know...
>>
>
> That post is FUD as far as I'm concerned. The problem is easily solved by
> including any necessary license files or notices by including them in the
> JAR. Then amazingly when the user gets the JAR they get the required
> additions. There is inventional called a JAR file. It's pretty useful for
> packaging things up and delivering them.
>
> The guy who posted this also appears to be from the company responsible for
> producing Saxon, so unless they plan on suing people who use JARs coming
> from Maven then there is no legal problem. They have to enforce it. Would be
> easy enough to take the JARs they produce and put the notice files in the
> JARs if their build is deficient in doing this.
>
> Maven is completely able to deliver copyright notices. You package them up
> in the releases you create which is what we do at Apache.
>
>> Keep up the good work!
>> Svante
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ----------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to