You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@creadur.apache.org by "Jochen Wiedmann (JIRA)" <ji...@apache.org> on 2016/09/11 08:54:20 UTC
[jira] [Resolved] (RAT-219) RAT project uses groupId:
org.apache.rat instead of org.apache.creadur.rat
[ https://issues.apache.org/jira/browse/RAT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Wiedmann resolved RAT-219.
---------------------------------
Resolution: Won't Fix
Assignee: Jochen Wiedmann
As far as I am concerned, not changing the groupId has been an intentional, although informal decision, when Rat went TLP, in order to avoid compatibility issues.
OTOH, Rat is basically a build time tool. I am unaware of any users, that use it at runtime. In fact, nowadays, I am even unaware of any users of the Ant tasks, or the CLI. So, I wouldn't block any change, if you'd do it in Git. Nevertheless, I am resolving this issue, so that it is out of scope.
> RAT project uses groupId: org.apache.rat instead of org.apache.creadur.rat
> --------------------------------------------------------------------------
>
> Key: RAT-219
> URL: https://issues.apache.org/jira/browse/RAT-219
> Project: Apache Rat
> Issue Type: Improvement
> Affects Versions: 0.12
> Reporter: Karl Heinz Marbaise
> Assignee: Jochen Wiedmann
> Priority: Critical
> Fix For: 0.13
>
>
> This should be done before 1.0.0 to make it consistent with the other projects (Whiskers/Tentacles).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [jira] [Resolved] (RAT-219) RAT project uses groupId:
org.apache.rat instead of org.apache.creadur.rat
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Jochen,
On 11/09/16 14:15, Jochen Wiedmann wrote:
> On Sun, Sep 11, 2016 at 2:09 PM, Karl Heinz Marbaise <kh...@gmx.de> wrote:
>
>> first if it is an informal decision why not making a formal decision of
>> it...to make a clear line where RAT belongs to?
>>
>> And why just setting it to Won't Fix to get it out of scope? We can create a
>> milestone 1.0.0 to assign it to it and may be we should change it earlier...
>
>
> As I wrote: You are committers, feel free to go on. I won't object.
> (No guarantees, that others feel different.)
> OTOH, I don't see any
> problem for users here,
> so I don't see any need for a Jira issue.
I find it very important to document things via JIRA for at least two
reasons.
First a users which takes a look can see what we have in
mind/ideas/improvements/bugs otherwise where should it be documentented
and second a potential contributor can take a look into the list of
issues and decide to work on some of them...
Furthermore you can use the JIRA as a good based for release notes to
create them automatically...
Just my thoughts about that...
Kind regards
Karl Heinz Marbaise
Re: [jira] [Resolved] (RAT-219) RAT project uses groupId:
org.apache.rat instead of org.apache.creadur.rat
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Sun, Sep 11, 2016 at 2:09 PM, Karl Heinz Marbaise <kh...@gmx.de> wrote:
> first if it is an informal decision why not making a formal decision of
> it...to make a clear line where RAT belongs to?
>
> And why just setting it to Won't Fix to get it out of scope? We can create a
> milestone 1.0.0 to assign it to it and may be we should change it earlier...
As I wrote: You are committers, feel free to go on. I won't object.
(No guarantees, that others feel different.) OTOH, I don't see any
problem for users here, so I don't see any need for a Jira issue.
Jochen
--
The next time you hear: "Don't reinvent the wheel!"
http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
Re: [jira] [Resolved] (RAT-219) RAT project uses groupId:
org.apache.rat instead of org.apache.creadur.rat
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Jochen,
first if it is an informal decision why not making a formal decision of
it...to make a clear line where RAT belongs to?
And why just setting it to Won't Fix to get it out of scope? We can
create a milestone 1.0.0 to assign it to it and may be we should change
it earlier...
Why not changing that...RAT has not reached 1.0.0 ? So it can be
changed...That's the reason why I have added the information to do that
before 1.0.0 ...
Kind regards
Karl Heinz Marbaise
On 11/09/16 10:54, Jochen Wiedmann (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/RAT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Jochen Wiedmann resolved RAT-219.
> ---------------------------------
> Resolution: Won't Fix
> Assignee: Jochen Wiedmann
>
> As far as I am concerned, not changing the groupId has been an intentional, although informal decision, when Rat went TLP, in order to avoid compatibility issues.
>
> OTOH, Rat is basically a build time tool. I am unaware of any users, that use it at runtime. In fact, nowadays, I am even unaware of any users of the Ant tasks, or the CLI.
> So, I wouldn't block any change, if you'd do it in Git.
> Nevertheless, I am resolving this issue, so that it is out of scope.
>
>
>> RAT project uses groupId: org.apache.rat instead of org.apache.creadur.rat
>> --------------------------------------------------------------------------
>>
>> Key: RAT-219
>> URL: https://issues.apache.org/jira/browse/RAT-219
>> Project: Apache Rat
>> Issue Type: Improvement
>> Affects Versions: 0.12
>> Reporter: Karl Heinz Marbaise
>> Assignee: Jochen Wiedmann
>> Priority: Critical
>> Fix For: 0.13
>>
>>
>> This should be done before 1.0.0 to make it consistent with the other projects (Whiskers/Tentacles).
>
>
>