On 2015-05-15 16:26 Colm O hEigeartaigh wrote:
Ok thanks! Maybe there is something in my build environment that is
causing
it...
For the sake of for try: please be sure to remove any "target" directory
before switching from 1_2_X to master and vice-versa.
The idea is that, since "target" directories are not under git control -
and thus are not removed when switching - and since on master some
directories exist with same name but different packaging when compared
to 1_2_X equivalent (think of "core", "client" or "common"), the
resulting directory content might cause troubles to RAT.
Summarizing:
1. find . -name "target" -exec rm -rf {} \; (to clean up any messy
situation)
2. git checkout master
3. ... (work with mvn)
4. mvn clean
5. git checkout 1_2_X
4. ... (work with mvn)
5. mvn clean
and so on.
Could you please try and let me know if this changes anything WRT RAT
hanging?
Regards.
On Fri, May 15, 2015 at 3:16 PM, Francesco Chicchiriccò
<[email protected]> wrote:
On 15/05/2015 15:50, Colm O hEigeartaigh wrote:
Hi all,
The Apache Rat plugin is hanging for me on 1.2.x. It's fine on
master. The
output just looks like:
[INFO] Exclude: **/deb/control/conffiles
[INFO] Exclude: **/deb/control/control
[INFO] Exclude: **/*.lst
[INFO] 3745 resources included (use -debug for more details)
Java 1.7.0_80 + Maven 3.3.1. Any ideas?
Hi,
something similar used to happen occasionally to me as well (not
currently, however): a while ago I found that this was related to
RAT-158 /
DOXIA-526, but if so it should have stopped after upgrading the parent
POM
to 17 (see MPOM-69).
The only way to workaround I've found was to skip rat checks.
It seems that neither Jenkins nor Travis is suffering from this
trouble,
anyway.
Regards.
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/
