I note that all 3 of these project fall under the "creadur" moniker. Are
they intended to work together?
I note that Rat has the capability of examining archives and that a quick
reading of tentacles indicates that it does the same.
Any guidance concerning how these tools are to be used
Currently the RAT tool allows you to insert a license and optional
copyright into files that do not have them. Should we explore taking this
functionality out of the core rat and making it a secondary tool?
Positives:
- This would simplify the RAT core and ensure that the core does not
I would like to see RAT progress to the point where it can scan a project,
detect any files that have licenses that are not compatible with ASF and
include in that scans of any libraries/jars.
In addition, I think that it should be simple for users to modify the
licenses / accepted license list /
s and have the ReportConfiguration collect them. Then the reporters
can be plugged in and new reporters can be developed as needed.
On Sat, Nov 4, 2023 at 9:48 PM P. Ottlinger wrote:
> Hi Claude,
>
> Am 03.11.23 um 08:36 schrieb Claude Warren:
> > Negatives:
> >
> > - It will
Greetings,
I have been working on RAT-321 [1] and in the process have had to rework
the configuration aspect of the RAT report. (Don't Panic) I moved all the
configuration information into o.a.r.ReportConfiguration and moved the
actual execution of the report into a class called "Reporter". I
While working on the configuration file definition of Licenses it became
apparent that a "NOT" IHeaderMatcher was required that would reverse the
state of an other IHeaderMatcher.
Specifically the problem arises when looking at the Apache 2.0 matcher and
the Applied Apache 2.0 matcher. The
I notice that there is an API module that has very few classes in it. What
is the purpose of this module?
I also recall seeing a ticket/branch that was working on separating the CLI
from the base code. is that still desirable? If so how was that supposed
to look?
Right now with the change to
Greetings,
I have been working on moving the license definitions into a configuration
file. The current working code is at [1]. It passes the core tests.
I have not removed any of the redundant code yet, and some of the
extensions (ant and maven) are not working yet. However, I wanted to see
Is there any interest in reviewing this before I go much further or should
I just assume that it is OK and I should proceed?
On Fri, Aug 18, 2023 at 12:38 PM Claude Warren wrote:
> Greetings,
>
> I have been working on moving the license definitions into a configuration
> file.
Does RAT support files that list multiple licenses? SPDX tags do but I
didn't see any way to specify that a file has multiple licenses and weather
those multiple licenses were "a AND b" or "a OR b".
Is there such a concept in RAT currently and, if not, do we want to
support it?
Claude
I looks like the snapshots in the repository contain very old code.
I looked in
https://repository.apache.org/content/repositories/snapshots/org/apache/rat/apache-rat/0.16-SNAPSHOT/
and downloaded the apache-rat-0.16-20230724-065051-299.jar and it contains
files with a date of 30 November 1979.
Phillipp, indicated that there should be an entry in the changelog for
RAT-251. However, I can not find any file by that name in the codebase.
Where/how does one update this file?
Claude
just confusing.
On Mon, Jul 24, 2023, 16:22 P. Ottlinger wrote:
> Hi,
>
> Am 24.07.23 um 09:22 schrieb Claude Warren:
> > I looks like the snapshots in the repository contain very old code.
> >
> > I looked in
> >
> https://repository.apache.org/content/r
t
> > Issue Type: Improvement
> > Components: engine
> >Affects Versions: 0.15
> >Reporter: Claude Warren
> >Priority: Minor
> >
> > The concept here is to rework the license matching definitions so that
> the SimplePatternBased
What I really want to do is create a configuration file to define all the
simple text licenses.
I don't have the code in front of me, but adding the tags is trivial, but
we have to figure out which family category and name they belong to.
SPDX is a camel's nose in that it can bring in many more
I am happy to move forward in whatever way makes life easier for most of
us.
If we have a BACKLOG.md then anyone who wanted to would be able to add to
it and would be able to select any ticket from the list to work on. Is
that correct? If someone adds to the BACKLOG I would like to discuss it
My proposed list is not sorted by priority and I am fairly certain there
are cross issue dependencies that need to be sorted out to git a true order
of implementation.
I think we should add the following components in Jira:
Build
Client - command line
Client - Maven
Client - Ant
Configuration
Core
Documentation
What I listed as "Helper Files" in the original documentation should be
filed under "Build" or "Configuration"
--
LinkedIn:
I spent a good part of FOSDEM listening to SPDX talks. SPDX is an open
project (standard?) that has spent a lot of time figuring out how to parse
licenses and understand if they conflict or not.
I think we should:
1. Look at being able to take SPDX license files [1] and creating our
I proposed this list awhile back, does anyone have any comments? Do we
have a way to make an Epic to track all of these as a release target?
On Tue, Jan 23, 2024 at 11:01 AM Claude Warren wrote:
> I walked through the list of Jira tickets and picked out the ones I think
> should be i
The reasons it did not rise linearly with more SPDX checks is that the SPDX
check works differently from most of the other matchers. Because the same
regex call is used by all SPDX matchers the system only runs the match
once and every SPDX matcher then looks to see if they were matched. So
Can you show me the output for the specific file in the run?Does the
output indicate that it has detected it as an MIT license?
On Thu, Jan 11, 2024 at 11:33 AM Maxim Solodovnik (Jira)
wrote:
>
> [
>
I have created a list of tickets and placed them under some general
headings. I think we should look through these and see if
a) I got them segregated correctly
b) if any can be closed (I think so)
c) if any should be combined into epics (It think so)
And then determine how we want to move
+1 (binding)
Tested Maven on different repo
Validated source folders contain proper licenses and have proper structure.
On Thu, Jan 25, 2024 at 2:46 PM Jochen Wiedmann
wrote:
> +1 (Binding)
>
> Thanks for all the work on this important bug fix release.
>
> Jochen
>
> On Wed, Jan 24, 2024 at
James,
The in general processing for matching licenses strips out all non
essential text (e.g. '/' and '*') so the current implementation can not
determine if the license text is within a javadoc block or not. Some
matchers (e.g. Copyright, SPDX, and regex) do use the unmodified text but
they
I walked through the list of Jira tickets and picked out the ones I think
should be in 0.17 (it is most of them). I further broke them into
sections. I tried to note where items reached across the sections. Let's
discuss this and see if there are things that should not be included or
things
This is an error. The Licenses is listed as Deprecated when it is not.
The note in the code says the type should be changed from an array of
Object to an array of License.
On Mon, Mar 4, 2024 at 5:24 AM Maxim Solodovnik
wrote:
> Thanks for the quick answer Phil :)
>
> On Mon, 4 Mar 2024 at
RAT-364 has been opened to address this issue.
https://issues.apache.org/jira/browse/RAT-364
On Fri, Mar 8, 2024 at 11:32 AM Claude Warren wrote:
> This is an error. The Licenses is listed as Deprecated when it is not.
> The note in the code says the type should be changed from an
We deprecated some things after 0.15 and put them back in 0.16.1 to make
the migration easier. Should we remove them in 0.17. This has an impact
on the solution to RAT-364 as well as the complexity of the code base.
Also should we move to supporting Maven 4.x in 0.17 or do we need a
solution
at 9:24 PM P. Ottlinger wrote:
> Hi Claude,
>
> thanks for raising the issue
>
> Am 18.03.24 um 14:03 schrieb Claude Warren:
> > We deprecated some things after 0.15 and put them back in 0.16.1 to make
> > the migration easier. Should we remove them i
/
On Thu, Mar 28, 2024 at 10:01 AM P. Ottlinger wrote:
> Hi,
>
> Am 28.03.24 um 09:41 schrieb Claude Warren:
> > I got back to looking at 366 and discovered a problem that I think has
> been
> > lurking in the system for some time. Basically, if a file has the
> > signat
RAT-355 started as a way to dump the running configuration so users could
verify what they have configured. This led to the necessity of being able
to dump the license definitions. This is the second iteration of the code
and uses an annotation to describe the components (Licenses and Matchers).
I got back to looking at 366 and discovered a problem that I think has been
lurking in the system for some time. Basically, if a file has the
signatures for more than one license only one will be reported, and the
selection of which one is (I think) random.
The CI build for RAT-366 shows a test
license
*
On Fri, Mar 29, 2024 at 3:50 PM Claude Warren wrote:
> I have a proposed change. See
> https://github.com/Claudenw/creadur-rat/pull/6/files
> Note that this pull request is the difference between multiple targets and
>
I have created a pull request with both changes included. I think this is
smaller than the combined pull requests done individually and since they
overlapped and resulted in a bunch of merge conflicts I figured I would
bite the bullet and get them out of the way all at once.
- The issue with
.txt
? Unknown license
*
I think this solves the problem.
Claude
On Thu, Mar 28, 2024 at 10:17 AM Claude Warren wrote:
> SPDX[1] has an interesting format where they can report 2 (or more?)
> licenses in one.
>
> There are a couple of things h
Currently Rat does nothing with binary files except note that they are
binary. However, the Tika library gives us a view into the interiors of
some binary files. The ones that come to mind are image files.
Using Tika we can extract the metadata from binary files, for image files
(and some
Currently Rat does no inspection of archives. This means that a jar that
does not meet the licensing of a project could be included and would not be
detected.
Currently the DefaultAnalyser simply marks the archives and archives and
does nothing more with them. Under the proposed Tika change
Currently we do not do anything with what we think are notices. Notices
are detected as text files that have specific names. I think that we
should run them through the standard processing to see if they have text
for other licenses in them. This is important for ASF Notice files where
we are
I have a pull request to switch to the Tika parser [1] one of changes that
this imposes is that Tika correctly determines that json files are
plain/text type. So they get processed for licenses and the change will
end up listing all json files as having unknown licenses. This is a
radical
Is there a way to execute a Java application, capture the output, and
insert it into an index.apt.vm file? If so I would like to generate the
help for the CLI and insert it during the build process.
:
> Cool, good to know that everything works automatically!
>
> Phil
>
> Am 03.05.24 um 12:59 schrieb Claude Warren:
> > If the XML looks like:
> >
> > "
> >
> >
> >
> >
> > The output as defined in the default.xslt woul
ommands (e.g. --help-i for --help-input, or --input-f for
--input-file). This is/was supported by the commons-cli library and should
be a simple switch to activate.
Claude
On Sat, May 11, 2024 at 8:31 AM Claude Warren wrote:
> Revisiting the list:
>
> Config
>
> [X] 322 Hidden di
Revisiting the list:
Config
[X] 322 Hidden dir processing
[X] 335 .gitignore not processed correctly
313 Add EUPL license
[X] 110 Ability to define target license(s)
146 list of directories to exclude by default.
2 reports should be able to skip certain file types or contents.
130 support new
and Ant. But that takes some harmonization.
Claude
On Sat, May 11, 2024 at 9:00 PM P. Ottlinger wrote:
> Hi Claude,
>
> Am 11.05.24 um 09:45 schrieb Claude Warren:
> > Create a repository for license files separate from the main tool.
> Perhaps
> > in the tools section, p
logical groupings. However, that is a discussion for later. This
change is about how we present the configuration options in the UIs,
specifically the command line version.
On Tue, May 14, 2024 at 6:38 PM Claude Warren wrote:
> The base configuration is currently stored in the Config class. S
Greetings,
Gary Gregory has put forth an argument that Builders are logically an
instance of Suppliers and should implement Supplier. At first I disagreed
with this stand but on reviewing gang of four documents and several
examples of implementing the Builder pattern in Java I find that there is
the configuration is common across all UIs.
On Mon 13 May 2024, 14:15 Jochen Wiedmann,
wrote:
> On Sat, May 11, 2024 at 9:45 AM Claude Warren wrote:
> >
> > I think that we should do the following:
>
> ...
>
> > create a licenses section in the configuratio
Greetings,
The code base has the ability to read archive files. It is only used to
create a "walker" to read archives passed in on the command line. I
propose that we modify the processing of ARCHIVE type files to scan them
for licences.
*Proposal:*
What I propose is that we extract each file
I would like to see us try to develop DOAP maintenance software. Once we
identify sources for the values in the DOAP it should be doable. Possibly
under a differen Creadur project.
On Sat, May 4, 2024 at 5:10 PM Claude Warren (Jira) wrote:
>
> [
> https://issues.apache.org/jira/b
0 schrieb Claude Warren:
> > Is there a way to execute a Java application, capture the output, and
> > insert it into an index.apt.vm file? If so I would like to generate the
> > help for the CLI and insert it during the build process.
>
> As there are so many XML/TXT/maven-si
*Current state*
We attempt to provide a default configuration that is ASF requirements
based.
We currently categorize documents into one of six categories: Generated,
Unknown, Archive, Notice, Binary, Standard.
- Standard documents get scanned for the presence or absence of license
at 8:53 AM P. Ottlinger wrote:
> Hi Claude,
>
> Am 03.05.24 um 07:26 schrieb Claude Warren:
> >
> > "
> >
> > This proposal would, in cases where licenses are discovered, add the
> > license entries as with STANDARD resource types. For example:
java
On Sun, May 5, 2024 at 4:02 PM P. Ottlinger wrote:
> Hi,
>
> Am 05.05.24 um 08:52 schrieb Claude Warren:
> > *Current state*
> >
> > We attempt to provide a default configuration that is ASF requirements
> > based.
> >
> > We currently categ
, those are my thoughts on the situation.
Claude
On Sat, May 11, 2024 at 9:43 PM P. Ottlinger wrote:
> Hi Claude,
>
> thanks for the thorough explanations
>
> Am 11.05.24 um 09:45 schrieb Claude Warren:
> > We need to support RAT-7 but to do so I think will requi
[
https://issues.apache.org/jira/browse/RAT-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781683#comment-17781683
]
Claude Warren commented on RAT-325:
---
That is what I would expect. If you edit the configuration file
[
https://issues.apache.org/jira/browse/RAT-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781683#comment-17781683
]
Claude Warren edited comment on RAT-325 at 11/1/23 9:52 AM:
That is what I would
Claude Warren created RAT-324:
-
Summary: Add tests to validate that UI options update the
ReportConfiguration as expected
Key: RAT-324
URL: https://issues.apache.org/jira/browse/RAT-324
Project: Apache
[
https://issues.apache.org/jira/browse/RAT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Warren updated RAT-323:
--
Description:
The UIs (CLI, ANT and Maven) were all developed separately and have different
options
[
https://issues.apache.org/jira/browse/RAT-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781890#comment-17781890
]
Claude Warren commented on RAT-325:
---
I have created a branch on my repository that changes to block
Claude Warren created RAT-328:
-
Summary: Output process can attempt to close output multiple times.
Key: RAT-328
URL: https://issues.apache.org/jira/browse/RAT-328
Project: Apache Rat
Issue Type
Claude Warren created RAT-334:
-
Summary: Create an option to verify NOTICE file
Key: RAT-334
URL: https://issues.apache.org/jira/browse/RAT-334
Project: Apache Rat
Issue Type: Improvement
Claude Warren created RAT-329:
-
Summary: Add "md" as a recognized extension for processing
Key: RAT-329
URL: https://issues.apache.org/jira/browse/RAT-329
Project: Apache Rat
Issue
[
https://issues.apache.org/jira/browse/RAT-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782513#comment-17782513
]
Claude Warren commented on RAT-330:
---
File types may also have to contain information about indenting each
Claude Warren created RAT-330:
-
Summary: Simplify the definition of file types.
Key: RAT-330
URL: https://issues.apache.org/jira/browse/RAT-330
Project: Apache Rat
Issue Type: Improvement
Claude Warren created RAT-332:
-
Summary: --force can cause system error
Key: RAT-332
URL: https://issues.apache.org/jira/browse/RAT-332
Project: Apache Rat
Issue Type: Improvement
Affects
Claude Warren created RAT-331:
-
Summary: Explore using license text files to build text matchers
for license insertion
Key: RAT-331
URL: https://issues.apache.org/jira/browse/RAT-331
Project: Apache Rat
Claude Warren created RAT-333:
-
Summary: --force will change the file permissions
Key: RAT-333
URL: https://issues.apache.org/jira/browse/RAT-333
Project: Apache Rat
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/RAT-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Warren updated RAT-329:
--
Summary: Add "md" and yaml as a recognized extension for processing (was:
Add "md&q
Claude Warren created RAT-327:
-
Summary: Add definitions for all ASF approved licenses
Key: RAT-327
URL: https://issues.apache.org/jira/browse/RAT-327
Project: Apache Rat
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/RAT-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Warren updated RAT-324:
--
Parent: RAT-323
Issue Type: Sub-task (was: Improvement)
> Add tests to validate that UI opti
[
https://issues.apache.org/jira/browse/RAT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781262#comment-17781262
]
Claude Warren commented on RAT-323:
---
My design here is that all UIs will require two things:
1) the UI
[
https://issues.apache.org/jira/browse/RAT-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781268#comment-17781268
]
Claude Warren commented on RAT-325:
---
I would doubt the SPDX feature because that was fixed in an earlier
[
https://issues.apache.org/jira/browse/RAT-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781272#comment-17781272
]
Claude Warren commented on RAT-325:
---
Can you add tests so that we can catch performance degradation
Claude Warren created RAT-323:
-
Summary: Harmonize UIs
Key: RAT-323
URL: https://issues.apache.org/jira/browse/RAT-323
Project: Apache Rat
Issue Type: Improvement
Components: cli
Claude Warren created RAT-326:
-
Summary: Fix javadoc errors
Key: RAT-326
URL: https://issues.apache.org/jira/browse/RAT-326
Project: Apache Rat
Issue Type: Bug
Components: site
[
https://issues.apache.org/jira/browse/RAT-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17772816#comment-17772816
]
Claude Warren commented on RAT-321:
---
The initial code for this idea is complete.
What is needed
[
https://issues.apache.org/jira/browse/RAT-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778344#comment-17778344
]
Claude Warren commented on RAT-321:
---
This issue is fixed in https://github.com/apache/creadur-rat/pull/158
[
https://issues.apache.org/jira/browse/RAT-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778299#comment-17778299
]
Claude Warren commented on RAT-321:
---
I found a misplaced line in the DefaultPolicy class.
> Al
[
https://issues.apache.org/jira/browse/RAT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744636#comment-17744636
]
Claude Warren commented on RAT-251:
---
I propose adding the SPDX header tags to the pattern matching
[
https://issues.apache.org/jira/browse/RAT-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744628#comment-17744628
]
Claude Warren commented on RAT-264:
---
This is a duplicate of RAT-251
> Use SPDX license identifi
Claude Warren created RAT-320:
-
Summary: Add a command line option to output to a file.
Key: RAT-320
URL: https://issues.apache.org/jira/browse/RAT-320
Project: Apache Rat
Issue Type
[
https://issues.apache.org/jira/browse/RAT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744919#comment-17744919
]
Claude Warren commented on RAT-251:
---
After futher review of the code, I have changed my stance. I think
[
https://issues.apache.org/jira/browse/RAT-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745051#comment-17745051
]
Claude Warren commented on RAT-319:
---
There is an option to use a custom XSLT to transform the output
[
https://issues.apache.org/jira/browse/RAT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747313#comment-17747313
]
Claude Warren commented on RAT-251:
---
I think this issue can be closed but I don't have access rights to do
[
https://issues.apache.org/jira/browse/RAT-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753469#comment-17753469
]
Claude Warren commented on RAT-321:
---
My thought is to remove as much of the hard coding as possible
[
https://issues.apache.org/jira/browse/RAT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751757#comment-17751757
]
Claude Warren commented on RAT-251:
---
[~janc] can you pull and compile run the speedup_SPDX branch on my
[
https://issues.apache.org/jira/browse/RAT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751983#comment-17751983
]
Claude Warren commented on RAT-251:
---
I will open a pull request this evening when I get home from work
Claude Warren created RAT-321:
-
Summary: Allow configuration to define SimplePatternBasedLicense
instances
Key: RAT-321
URL: https://issues.apache.org/jira/browse/RAT-321
Project: Apache Rat
[
https://issues.apache.org/jira/browse/RAT-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808961#comment-17808961
]
Claude Warren commented on RAT-325:
---
[~cdutz] I ran a test. If you add 0.16.1-SNAPSHOT to your
apache
Claude Warren created RAT-358:
-
Summary: Update documentation to match configuration options and
files
Key: RAT-358
URL: https://issues.apache.org/jira/browse/RAT-358
Project: Apache Rat
Issue
[
https://issues.apache.org/jira/browse/RAT-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809115#comment-17809115
]
Claude Warren commented on RAT-358:
---
Documentation should explain the following items in the configuration
Claude Warren created RAT-340:
-
Summary: Make processing multi-threaded.
Key: RAT-340
URL: https://issues.apache.org/jira/browse/RAT-340
Project: Apache Rat
Issue Type: New Feature
Affects
[
https://issues.apache.org/jira/browse/RAT-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805012#comment-17805012
]
Claude Warren commented on RAT-325:
---
I think the SPDX is slow because is it does a regex on every line
[
https://issues.apache.org/jira/browse/RAT-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805014#comment-17805014
]
Claude Warren commented on RAT-343:
---
I think I have 2 solutions. Both of which should be implemented
[
https://issues.apache.org/jira/browse/RAT-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805225#comment-17805225
]
Claude Warren commented on RAT-343:
---
There is an extensive change to how licenses are defined. It is now
[
https://issues.apache.org/jira/browse/RAT-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805225#comment-17805225
]
Claude Warren edited comment on RAT-343 at 1/11/24 8:39 AM
[
https://issues.apache.org/jira/browse/RAT-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805478#comment-17805478
]
Claude Warren commented on RAT-343:
---
[~romain.manni-bucau] I did not. I stuck with the vanilla Maven code
Claude Warren created RAT-350:
-
Summary: Fix javadoc errors/warnings
Key: RAT-350
URL: https://issues.apache.org/jira/browse/RAT-350
Project: Apache Rat
Issue Type: Improvement
Claude Warren created RAT-346:
-
Summary: WARN in case user defined License family has the same
name as existing one
Key: RAT-346
URL: https://issues.apache.org/jira/browse/RAT-346
Project: Apache Rat
1 - 100 of 227 matches
Mail list logo
