Renaming package names

[Ceki Gülcü <ce...@qos.ch>]

I recently received the following from a developer who wishes to remain 
anonymous.

<whistle-blowing>
Hi Ceki,

In one of my current projects I have come across some 3rd-party
commercial product, which includes as part of their software-product
Log4J. Nothing against it, however I found, that they have renamed the
package-structure
(from org.apache.log4j to com.COMPANY.org.apache.log4j) - just wanted to
know if this does not violate the Apache Software license?

I find it quite an unethnical practice to hide acknowledgement where
it is really due and wanted to know, if this is something the ASF
would be concerned about.

Let me know your thoughts.

Kind regards,
</whistle-blowing>

It appears that the product in question includes a copy of the Apache
license in their documentation. Does this give them the right to
rename packages an appropriate the software?

My understanding is that the Apache license allows this.

Your comments would be appreciated.


-- 
Ceki Gülcü

      For log4j documentation consider "The complete log4j manual"
      ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp  



---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org

Re: Renaming package names

[Erik Abele <er...@codefaktor.de>]

On 11.03.2004, at 15:36, Ceki Gülcü wrote:

> It appears that the product in question includes a copy of the Apache
> license in their documentation. Does this give them the right to
> rename packages an appropriate the software?
>
> My understanding is that the Apache license allows this.

Yes, together with other changes to the code, this would be called a 
'Derivative Work' (definition see license) and it is perfectly fine and 
allowed by the AL as long as the product in question also conforms to 
section 4b of AL2.0:

"You must cause any modified files to carry prominent notices stating 
that You changed the files..."

Hope this helps...

Cheers,
Erik

> Your comments would be appreciated.
>
>
> -- 
> Ceki Gülcü
>
>      For log4j documentation consider "The complete log4j manual"
>      ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp

Re: Renaming package names

[Stefano Mazzocchi <st...@apache.org>]

Nick Chalko wrote:

> Ceki Gülcü wrote:
> 
>>
>> In one of my current projects I have come across some 3rd-party
>> commercial product, that they have renamed the
>> package-structure
>> (from org.apache.log4j to com.COMPANY.org.apache.log4j) - just wanted to
>> know if this does not violate the Apache Software license?
>>
>>
> I think bea, does this. It is one way of ensuring that bea will use 
> exactly the version of log4j they want without naming/classpath 
> confilts. I think it is fine as long as the NOTICE with attribution to 
> the ASF is left.

java (unlike c#) does not have a versioning concept for classes so many 
people are resulting in changing package names to do exactly that and 
make sure that you don't trigger class cast exceptions during classloading.

[cocoon is currently voting about doing the same on the other side, 
changing the name of the rhino packages to avoid collision with rhino 
shipped with weblogic and websphere]

also, keep in mind that there is nothing in the license that stops 
people from changing package names.

You could think that the use of the name "apache" and "log4j" in the 
package name would be considered abusive, but this would result in them 
changing the name entirely and this would not solve any issue.

In short: if they give credits, they are in good faith, if not, no 
matter what they do with the software, they are abusive... but package 
name change should not be considered abusive as such, but rather a 
necessity that arised out of java internal limitations.

-- 
Stefano.

Re: Renaming package names

[Nick Chalko <ni...@chalko.com>]

Ceki Gülcü wrote:

>
> In one of my current projects I have come across some 3rd-party
> commercial product, that they have renamed the
> package-structure
> (from org.apache.log4j to com.COMPANY.org.apache.log4j) - just wanted to
> know if this does not violate the Apache Software license?
>
>
I think bea, does this. 
It is one way of ensuring that bea will use exactly the version of log4j 
they want without naming/classpath confilts. 
I think it is fine as long as the NOTICE with attribution to the ASF is 
left.

R,
Nick



---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org