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).
