On Wed, Jun 18, 2008 at 1:34 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
> Robert Burrell Donkin ha scritto:
>>
>> On Mon, Jun 16, 2008 at 9:38 PM, Rick McGuire <[EMAIL PROTECTED]> wrote:
>>>
>>> Stefano Bagnara wrote:
We also depend on com.sun.mail.util.CRLFOutputStream but we should
On Wed, Jun 18, 2008 at 7:56 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
> Stefano Bagnara ha scritto:
>>
>> David Jencks ha scritto:
>>>
>>> 2. each artifact distributed from apache must include a LICENSE and
>>> NOTICE file applying to the contents of that artifact.
>>> [...]
>>
>> Are we sur
On Wed, Jun 18, 2008 at 7:13 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
> In most Licenses for product I use I read a lot of boilerplate that does not
> apply to the specific product I use, but the licensor simply use the same
> license for each product. Some term is clearly out of scope, bu
Stefano Bagnara ha scritto:
David Jencks ha scritto:
2. each artifact distributed from apache must include a LICENSE and
NOTICE file applying to the contents of that artifact.
[...]
Are we sure that if I include the bigger LICENSE&NOTICE from the one
aboves in ALL of our packages I'm breaki
David Jencks ha scritto:
On Jun 18, 2008, at 9:55 AM, Stefano Bagnara wrote:
David Jencks ha scritto:
Thinking about the situation a little more
the normal maven generated artifacts (jar, source, javadoc jars) can
get the m-r-r-p generated legal files as they include what maven
expects
On Jun 18, 2008, at 9:55 AM, Stefano Bagnara wrote:
David Jencks ha scritto:
Thinking about the situation a little more
the normal maven generated artifacts (jar, source, javadoc jars)
can get the m-r-r-p generated legal files as they include what
maven expects from these artifacts
On
David Jencks ha scritto:
Thinking about the situation a little more
the normal maven generated artifacts (jar, source, javadoc jars) can
get the m-r-r-p generated legal files as they include what maven
expects from these artifacts
On the other hand, you need to have hardcoded LICENSE and
On Jun 18, 2008, at 1:25 AM, Stefano Bagnara wrote:
David Jencks ha scritto:
On Jun 17, 2008, at 4:18 PM, Stefano Bagnara wrote:
David Jencks ha scritto:
The source and binary jars do not include junit so their LICENSE
and NOTICE files must not include them. The distro assemblies do
incl
In a discussion about LICENSE/NOTICE generation from maven remote
resources plugin the result was a blocking issue in the pom content:
there is no way to specify the copyright owner for a given artifact, it
only allow us to specify the licenses.
I just wanted to share with you this issue, so m
Jukka Zitting ha scritto:
Hi,
On Wed, Jun 18, 2008 at 4:31 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
I'm simply saying that I agree with David that each package should have its
own specific NOTICE/LICENSE but IMHO at the moment it doesn't worth the
effort until maven will give us a better
Hi,
On Wed, Jun 18, 2008 at 4:31 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
> I'm simply saying that I agree with David that each package should have its
> own specific NOTICE/LICENSE but IMHO at the moment it doesn't worth the
> effort until maven will give us a better solution.
Fair enough.
Trying again to pass the antispam filter.
I and Rick had some off-list conversation about failures in our
testsuite when using geronimo javamail.
He already fixed the first NPEs I found, now I opened a few more issue
on the basic use of MimeMessage and our MimeMessageWrapper object:
GERONIM
Jukka Zitting ha scritto:
Hi,
On Wed, Jun 18, 2008 at 3:15 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
I would simply need maven to generate the NOTICE/LICENSE for dependencies
I'm including with the "assembly" plugin and its dependencySets feature!
With this plugin maven is really aware of
Stefano Bagnara ha scritto:
Jukka Zitting ha scritto:
The collection and
maintenance of proper license and copyright information is a project
issue not a tool issue, so I wouldn't put blame on Maven about this.
assembly and the remote resources plugin should collaborate in order to
create NOT
Hi,
On Wed, Jun 18, 2008 at 3:15 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
> I would simply need maven to generate the NOTICE/LICENSE for dependencies
> I'm including with the "assembly" plugin and its dependencySets feature!
> With this plugin maven is really aware of what dependencies I am
Jukka Zitting ha scritto:
Hi,
On Wed, Jun 18, 2008 at 11:25 AM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
I would like maven to address this issue someway: are we the only maven
based project creating the jar, source-jar, javadoc-jar,
bin-zip-with-runtime-dependencies, src-zip-with-all-depende
Hi,
On Wed, Jun 18, 2008 at 11:25 AM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
> I would like maven to address this issue someway: are we the only maven
> based project creating the jar, source-jar, javadoc-jar,
> bin-zip-with-runtime-dependencies, src-zip-with-all-dependencies ? I don't
> this
Robert Burrell Donkin ha scritto:
On Mon, Jun 16, 2008 at 9:38 PM, Rick McGuire <[EMAIL PROTECTED]> wrote:
Stefano Bagnara wrote:
We also depend on com.sun.mail.util.CRLFOutputStream but we should
definitely replace this with some james class (maybe copied from geronimo?)
Not sure what this cl
David Jencks ha scritto:
On Jun 17, 2008, at 4:18 PM, Stefano Bagnara wrote:
David Jencks ha scritto:
The source and binary jars do not include junit so their LICENSE and
NOTICE files must not include them. The distro assemblies do include
them so require a different LICENSE/NOTICE file. So
An automated nightly build of JAMES has been posted to
http://people.apache.org/builds/james/nightly/
Any unit test errors from the build should be reported below:
-
20 matches
Mail list logo
