-Original Message-
From: Martin Poeschl [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 06, 2003 9:44 PM
To: Jakarta General List
Subject: Re: [Fwd: Maven as a top-level apache project]
Steve Downey wrote:
From: [EMAIL PROTECTED]
To: Jakarta General List [EMAIL PROTECTED
-Original Message-
From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Dan Diephouse
Sent: Thursday, February 06, 2003 9:52 PM
To: [EMAIL PROTECTED]
Subject: Re: [Fwd: Maven as a top-level apache project]
It is your responsibility to enforce that policy. Not maven
Steve Downey wrote:
-Original Message-
From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Dan Diephouse
Sent: Thursday, February 06, 2003 9:52 PM
To: [EMAIL PROTECTED]
Subject: Re: [Fwd: Maven as a top-level apache project]
It is your responsibility to enforce that policy
Costin Manolache wrote:
Nick Chalko wrote:
Agree, centipede has the same problem. Easy to download a jar without
knowing it's liscense.
Sending a license file with a jar is something that the new Jakarta
Ruper project should handle.
And why not: DISPLAY the damn license and require
Nick Chalko wrote:
And why not: DISPLAY the damn license and require the user to type
I do understand the terms of this licence and click somewhere
( that may also cover the requirements of some of the packages ).
Or even better, if it's a GPL license Ruper should require the user
to type I
On 9/2/03 2:05 Costin Manolache [EMAIL PROTECTED] wrote:
And why not: DISPLAY the damn license and require the user to type
I do understand the terms of this licence and click somewhere
( that may also cover the requirements of some of the packages ).
Click-through is something we always
2. Can ASF Projects use GPL/LGPL Projects?
Yes. But, they cannot distribute them.
ASF projects can use GPL/LGPL code during the build process so long as
there is no runtime dependency in the code produced. Programs like
checkstyle are OK. Imports of classes covered by GPL/LGPL are not.
As far as L/GPL jars go that's not something Maven controls. Projects
state their own dependencies and if an Apache project is violating
Apache policies how is that Maven's problem? If it was an Ant build that
used the get/ task to link in an L/GPL jar is that Ant's problem?
Obviously not.
The second I feel that the environment here at Apache has eroded to the
point where this is not possible I will not hesitate to propose movement
of the code to an environment conducive to the production of outstanding
software. I believe the environment here has the potential of becoming
Andrew C. Oliver wrote:
2. Can ASF Projects use GPL/LGPL Projects?
Yes. But, they cannot distribute them.
ASF projects can use GPL/LGPL code during the build process so long as
there is no runtime dependency in the code produced. Programs like
checkstyle are OK. Imports of classes
Jason van Zyl wrote:
and can't or won't comply with Apache
policies,
I started removing the Sun violations and I just sent you another
message asking you to take on a maven repository admin role. Feel free
to find the violations and remove them with a notification on the
maven-user list. You
On Fri, 2003-02-07 at 10:18, Sam Ruby wrote:
Jason van Zyl wrote:
and can't or won't comply with Apache
policies,
I started removing the Sun violations and I just sent you another
message asking you to take on a maven repository admin role. Feel free
to find the violations and
On Fri, 2003-02-07 at 10:40, Jason van Zyl wrote:
On Fri, 2003-02-07 at 10:18, Sam Ruby wrote:
Jason van Zyl wrote:
and can't or won't comply with Apache
policies,
I started removing the Sun violations and I just sent you another
message asking you to take on a maven
Jason van Zyl wrote:
On Fri, 2003-02-07 at 10:18, Sam Ruby wrote:
Jason van Zyl wrote:
and can't or won't comply with Apache
policies,
I started removing the Sun violations and I just sent you another
message asking you to take on a maven repository admin role. Feel free
to find the
Jason van Zyl wrote:
The second I feel that the environment here at Apache has eroded to
the point where this is not possible I will not hesitate to propose
movement of the code to an environment conducive to the production of
outstanding software. I believe the environment here has the
Sam Ruby wrote:
I am willing to take on the maven repository admin role on one condition
- every other admin is removed. In short, I am willing to take on
responsibility for removing piss from the pool if and only if the
sources of this contamination are eliminated first.
i realise you
On Fri, 2003-02-07 at 12:50, Rodent of Unusual Size wrote:
Jason van Zyl wrote:
The second I feel that the environment here at Apache has eroded to
the point where this is not possible I will not hesitate to propose
movement of the code to an environment conducive to the production of
Jason van Zyl wrote:
thanks for the detailed answer, jason. i have personal opinions
on the items you listed, but it's unclear to me that having
another country heard from would help the weather -- so i won't
weigh in with my thoughts unless someone asks me. the short form
is that i agree on
Rodent of Unusual Size wrote:
Sam Ruby wrote:
I am willing to take on the maven repository admin role on one condition
- every other admin is removed. In short, I am willing to take on
responsibility for removing piss from the pool if and only if the
sources of this contamination are
Jason van Zyl wrote:
i'd like to make sure that the term 'philosophical
visions' isn't being mistakenly applied to things motivated by
legally-required oversight.
What I'm referring to by philosophical vision is Sam's notion of opening
up everything to everybody and trying to create one big
At 07:53 PM 2/6/2003, Sam Ruby wrote:
Dan Diephouse wrote:
2. Can ASF Projects use GPL/LGPL Projects?
Yes. But, they cannot distribute them.
ASF projects can use GPL/LGPL code during the build process so long as
there is no runtime dependency in the code produced. Programs like
From: Costin Manolache [EMAIL PROTECTED]
Maven is a nice tool - and I wish it good luck wherever it goes.
But if Maven charter will include the creation of a maven-only
repository -
I hope at least some board members will vote -1.
I don't see that ever happening. Already the Maven repository
Jason van Zyl wrote:
BTW, for the record, was the creation of the jakarta-turbine-maven
resources (CVS and lists) approved by this PMC?
Yes, they were. The creation of the lists didn't get by Sam. It was
Costin who argued that each project should be allowed to do what it
likes.
Ack. For
Jason van Zyl wrote:
Gump _never_ used an object model, never. Gump was targeted at overall
control by a small set of people (and it's still that way, no one
outside of Jakarta/XML barely knows what it is) to build sources against
CVS. That's not what Maven was ever targeted at, ever. Maven
Costin,
what's a 'maven-only' repository?
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
news [EMAIL PROTECTED] wrote on 07/02/2003 04:53:05 AM:
Sam Ruby wrote:
Those that care to participate, please
news [EMAIL PROTECTED] wrote on 07/02/2003 06:00:32 AM:
I am talking about this in the context of the other discussions on
having an apache repository ( and use the apache mirroring system, etc).
Also in the context of having a common policy on how releases will
be distributed and structured
repository.
The 'apache repository' and the ones maven can use (note that maven can
have multiple repositories) are not necessarily one and the same thing. We
have a 'repository' at a customer site I work on, as well as one at the
office. Apache hosting its own (of whatever format is agreed)
From: [EMAIL PROTECTED]
To: Jakarta General List [EMAIL PROTECTED]
Sent: Thursday, February 06, 2003 8:07 PM
Subject: Re: [Fwd: Maven as a top-level apache project]
BTW, given the license discussions it seems unlikely a solution that
includes all the jars in the same place will work. So
Steve Downey wrote:
From: [EMAIL PROTECTED]
To: Jakarta General List [EMAIL PROTECTED]
Sent: Thursday, February 06, 2003 8:07 PM
Subject: Re: [Fwd: Maven as a top-level apache project]
BTW, given the license discussions it seems unlikely a solution that
includes all the jars in the same
Steve Downey wrote:
From: [EMAIL PROTECTED]
To: Jakarta General List [EMAIL PROTECTED]
Sent: Thursday, February 06, 2003 8:07 PM
Subject: Re: [Fwd: Maven as a top-level apache project]
BTW, given the license discussions it seems unlikely a solution that
includes all the jars in the same place
[EMAIL PROTECTED] wrote:
Costin,
what's a 'maven-only' repository?
There are at least 3 build tools in apache: ant is one of them,
gump and maven ( there are more actually ). There are many
projects whose releases will be in such a repositroy. The policy
and the format of the descriptors
Dan Diephouse wrote:
Steve Downey wrote:
From: [EMAIL PROTECTED]
To: Jakarta General List [EMAIL PROTECTED]
Sent: Thursday, February 06, 2003 8:07 PM
Subject: Re: [Fwd: Maven as a top-level apache project]
BTW, given the license discussions it seems unlikely a solution that
includes all
Steve Downey [EMAIL PROTECTED] wrote on 07/02/2003
01:13:24 PM:
One thing that has annoyed me is that Maven will download jars from the
ibiblio repository with no regard to the license of them. It's an easy
way
for jars to come into a build without formal review and acceptance of
the
[EMAIL PROTECTED] wrote:
Sure, but let's not lose focus of what this is for. Distribution?
Building? A company/individual can set up their own repository of jars (we
all do) that they've accepted licenses for. The 'tools' should be able to
work with that set up, similar to how Maven does
Sam Ruby wrote:
It is your responsibility to enforce that policy. Not maven and not
the ASF's. When you integrate JAR or any resource into your project
you are doing so delibrately. You should know where that jar
originally comes from. If you don't, ask on the developers or user's
list.
Dan Diephouse wrote:
People should have a resonable expectation that building an ASF
project should not involve the download of materials in violation of
their licenses or the incurring of any additional obligations.
Enforcement of this policy via Maven or simply by peer review of POMs
are
On Fri, 7 Feb 2003, Dan Diephouse wrote:
4. Can ASF Projects use Sun BCL licensed products?
Yes, but ASF can't distribute them.
Each product you download from Sun's java.sun.com web site has a license
that you have to agree to in order to download that JAR. In the case of
several
On Thu, 2003-02-06 at 16:45, Sam Ruby wrote:
Jason, now let me ask you a direct question:
if you don't want to work
with the Apache infrastructure
I am first concerned with setting up the infrastructure that Maven
requires in order to satisfy the needs of people building projects.
L/GPL
On Thu, 2003-02-06 at 22:06, Sam Ruby wrote:
It is your responsibility to enforce that policy. Not maven and not the
ASF's. When you integrate JAR or any resource into your project you are
doing so delibrately. You should know where that jar originally comes
from. If you don't,
39 matches
Mail list logo
