Am 02.12.2012 13:51, schrieb Robert Burrell Donkin:
Should we push ahead with Apache Rat 0.9...?
+1
Although I'm currently not really available as a member of creadur :-(
Cheers
Phil
Am 02.03.2013 11:20, schrieb Robert Burrell Donkin:
The maven scm publish process seems much smoother now (though still
slow). Perhaps we should roll this out to the rest of the suite (Whisker
and Tentacles). Opinions? Objections?
+1
Rollout.
Thanks for all your efforts
Phil
Hi,
Am 11.03.2013 12:51, schrieb Robert Burrell Donkin:
Opinions?
+1
Go for it.
Should we raise the version of Java as well?
Cheers
Philipp
Hi,
thanks for your ideas.
Am 23.03.2013 16:10, schrieb Robert Burrell Donkin:
Opinions? Objections? Improvements?
+1
Very nice plan!
Cheers
Philipp
Hi,
Am 25.03.2013 21:19, schrieb sebb:
However if the nested class is very small, leave it - it's clearer.
I'd prefer to avoid nested classes (except for enumerations). They
prevent easy testing ...
Just my 2ct.
Cheers
Philipp
Am 29.03.2013 10:06, schrieb Robert Burrell Donkin:
I've been wondering whether Tentacles might be a good GSOC project for a
student who's interested more in solving human problems than hard core
technical coding. Perhaps run as a Agile project, weekly sprints going
back to people in the
Am 31.03.2013 14:59, schrieb Robert Burrell Donkin:
[ ] +0 In favour of release but have not checked release
+0
Happy easter and thanks for all your efforts!
Phil
Hi,
Am 01.04.2013 10:02, schrieb Robert Burrell Donkin:
For application code, I think that it more obvious to model an interface
with an interface. When in this mode, I lean towards prefixing with 'I'
(rather than suffixing or prefixing implementations with Impl or Default).
I'd definitely
Hi,
thanks for your work.
Am 09.05.2013 22:09, schrieb Robert Burrell Donkin:
Some other projects make the documentation for their releases available
online. I like this idea, and we could do this by generating the 0.9
documentation and committing it to the website CMS.
+1
I'm astonished
Am 27.06.2013 13:25, schrieb sebb:
Unless I hear otherwise, I propose to standardise the location (and
fix the pom).
+1
Thanks
Phil
Dear *,
Am 08.07.2013 21:46, schrieb Robert Burrell Donkin:
I wonder whether it would be simpler and more conventional to factor out
three phases:
1. scan the source, building a strongly-typed, immutable domain model
+1
Scanning could be done multithreadedly with a status output on console
Am 11.08.2013 21:54, schrieb Robert Burrell Donkin:
--8--
[ ] +1 Release orgapachecreadur-059 as Apache Whisker 0.1
[ ] +0
[ ] -0
[ ] -1 Do not release orgapachecreadur-058 as Apache Whisker 0.1
Hi,
Am 20.08.2013 22:32, schrieb Robert Burrell Donkin:
The download page http://creadur.apache.org/rat/download_rat.cgi should
now be pointed at Apache Rat 0.10 and Apache Rat 0.9 should now be
archived. (If anyone has a few spare cycles, please take a quick look)
Unless I've forgotten
Hi,
Am 01.09.2013 21:53, schrieb Robert Burrell Donkin:
http://svn.apache.org/repos/asf/creadur/rat/branches/apache-rat-project-0.10-website/
(unless anyone jumps in with a better name)
I'd propose 0.10-cms to make it clearer that it's just a cms-thing but
not a 'general' webpage?
But I'm
Hi all,
I'm just working on
https://issues.apache.org/jira/browse/RAT-164
and added a proposed patch.
Since it's one of my first commits I'm not sure where to update any
CLI/help documentations.
Can someone please provide assistance or guide me in what to do or where
to add the new environment
Hi Dennis, hi *,
thanks for the hint; Jenkins made sure that the checkins didn't break
anything.
Am 27.07.2014 um 15:12 schrieb Dennis Lundberg:
There is a job for Rat in the ASF Jenkins instance at:
https://builds.apache.org/view/All/job/rat-jdk-1.5-maven-2/
JENKINS SITE:SITE
Wouldn't it be
Hi Sebb,
thanks for your input.
Am 28.07.2014 um 11:59 schrieb sebb:
JENKINS SITE:SITE
Wouldn't it be useful to have a Jenkins job for site:site running daily
to check whether something goes wrong during site generation? One
shouldn't be flooded with warnings upon releasing RAT.
What do
Hi,
buildbot (http://ci.apache.org/builders/rat_trunk) does not seem to be
able to build rat and fails with a timeout, e.g.
http://ci.apache.org/builders/rat_trunk/builds/3/steps/svn/logs/stdio
Is this problem somehow related to the buildslave? Is there a cancelled
job blocking some files that
Hi guys,
due to my addition of commons-lang3 I ran into the versioning chaos of
creadur's compiler level.
Are there any hard reasons to keep with 1.5 in Jenkins?
Since these ancient Java versions are not officially supported and no
security updates for the varous security issues are
Hi Sebb,
SITE BUILD
Am 29.07.2014 um 00:02 schrieb sebb:
https://builds.apache.org/job/Creadur-Rat-site/
It needs some work ...
Since I lack the privileges ... could you configure the job to run
daily?! I don't have enough rights to even trigger it if logged in.
RAT BUILD
Furthermore it
Hi guys,
Robert merged the GSOC stuff into a separate branch - in case there are
no objections I'd start to merge the branch back to trunk.
Since all tests hopefully run on the branch I assume no functionality
broken, but will check carefully upon merge/commit.
Any objections?
Thanks,
Phil
Hi Sebb,
JENKINS
thanks for your work - could you clone the site and install jobs for
Whisker and tentacles as well?
So that we have:
https://builds.apache.org/job/Creadur-Tentacles-site/
https://builds.apache.org/job/Creadur-Tentacles/
working on
Hi,
Am 02.08.2014 um 19:38 schrieb Dennis Lundberg:
We should really release Rat 0.11 before we merge the branch into trunk. It
has been on my todo list fora while, but I have some time in the coming
week, and will try to push a release out.
Alright - sounds like a plan.
I'd just want to
Hi,
thanks for integrating everything into Jenkins.
Am 03.08.2014 um 20:03 schrieb Dennis Lundberg:
So we agree to stay on Java 5 for now. I've changed the config for the
Jenkins build job to reflect that. The build will fail until the commit for
RAT-136 is reverted. Can you fix that Phil?
Hi,
On 2014-08-08 10:22, Dennis Lundberg wrote:
That's an interesting question. I talked to Phil off list, about his
changes and one thing that emerged from those talks was the need to
establish standards for Creadur. A topic we decided to discuss on the
list
once we get Rat 0.11 out. Let us
Hi,
thanks for your efforts!
On 2014-08-08 14:31, Dennis Lundberg wrote:
Tag:
http://svn.apache.org/repos/asf/creadur/rat/tags/apache-rat-project-0.11/
https://svn.apache.org/repos/asf/creadur/rat/tags/apache-rat-project-0.11/ant-task-examples.xml
contains version 0.9-SNAPSHOT ?!
Since I
Hi,
could anyone with enough Jenkins-kharma change all of the RAT jobs, to
perform a clean install deploy instead of a plain clean install ...
thus we shouldn't get these build errors upon version change and there's
always a SNAPSHOT deployed.
Hi Sebb,
Am 10.08.2014 um 21:22 schrieb sebb:
-1
I'm seeing an NPE when running mvn apache-rat: rat
-Dcommons.rat.version=0.11 against commons-csv and commons-compress.
Other times I have seen messages such as
Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property
Hi *,
Am 11.08.2014 um 00:53 schrieb sebb:
Fails with NPE - likely because getProject() is null - same issue as
I'd already discovered.
That's rather strange I've replaced the injection of project in
AbstractRatMojo:
//@Parameter(name = project, readonly = true)
@Component
Hi Sebb,
On 2014-08-11 12:09, sebb wrote:
AFAICT the test does not detect the error.
yes, that's why I was asking for proposals on how to test it ;-)
I think the problem is that the tests are run in a different
environment.
There probably needs to be an IT instead to run the code
Hi *,
Am 16.08.2014 um 20:42 schrieb Dennis Lundberg:
Guide for testing releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Everyone is encouraged to vote, express their opinions and jump in if
they find anything wrong with the release. Only PMC votes are
Hi,
Am 19.08.2014 um 01:37 schrieb sebb:
Reverting patch since there is a NPE during rat:rat on 0.11-RC2.
Can you provide a sample project on which it fails?
It works OK for me with Commons NET and with the current IT.
I've just deleted my local repository and checked out:
hg clone
Hi *,
sorry for the confusion:
+1
I've had caching issues with 0.11 ...
RAT-170
In 0.12 we should generate our own reports during build and site
(https://issues.apache.org/jira/browse/RAT-170)
RAT-158
I'd propose to add the JDK-related compiler warnings to the release
notes as known but not
Hi,
yesterday I've realized that the next ASF board meeting will take place
tomorrow.
How can we file a report or does Robert have to do this?
Since we are working hard on getting 0.11 out, we should propagate this
to the board.
Thanks for your feedback,
Phil
Hi folks,
I'm sorry for spamming all of us with those Jenkins mails - it seems
that the JenkinsCI is even more instable than the buildbot stuff.
I'm trying to get in touch with INFRA/BUILD to solve things in our
favour. Luckily I'm able to see errors in Jenkins, while buildbot still
remains
Hi again,
Am 20.08.2014 um 12:47 schrieb P. Ottlinger:
I'm sorry for spamming all of us with those Jenkins mails - it seems
that the JenkinsCI is even more instable than the buildbot stuff.
I've reconfigured the mail notifications - hopefully (after people from
infra helped to fix the build
Hi,
Am 21.08.2014 um 16:55 schrieb Dennis Lundberg:
I will promote the artifacts to the central repo, and copy the
relevant files to the dist area.
superb - please do not forget about the announcement mail ...
to further promote 0.11.
Cheers,
Phil
signature.asc
Description: OpenPGP digital
Hi *,
currently Whisker makes heavy use of commons-lang3, thus is not a valid
JDK5 maven plugin.
Should we change the compiler level to jdk1.6 or start a mahor
refactoring?
My personal opinion is to upgrade to at least JDK6.
What do you think?
Thanks,
Phil
Hi,
can anyone point me to the cause of RAT's build error ...
Sometimes there are cycles detected
I don't see these warnings locally.
Thanks for your opinions,
Phil
Hi Dennis,
thanks for your offer.
On 2014-08-22 15:18, Dennis Lundberg wrote:
If that is the case we might need to require Maven 3 to *build* Rat,
but you will still be able to *use* Rat with Maven 2.
+1 with me.
Cheers,
Phil
Hi Dennis,
Am 22.08.2014 um 15:18 schrieb Dennis Lundberg:
I will take a look at these later on. My gut feeling is that this is a
Maven version dilemma. It probably works with Maven 3 but fails with
Maven 2.
Would you mind having a look at whisker as well?
It runs well locally but fails on
Hi *,
would you mind having our 3 projects in SonarQube?
Cheers,
Phil
signature.asc
Description: OpenPGP digital signature
Hi,
On 2014-08-28 14:15, Dennis Lundberg wrote:
That said, doing the invitation in the announcement mail is a good
idea. I will try to do that.
I'd still prefer to have a separate list since the dev@ is used for
internal discussions /or my stupid questions :-)/. I think that's not
Hi guys,
does anyone of you see the use case of blocking the reports?
On 2014-09-10 23:11, Chris Burroughs (JIRA) wrote:
Chris Burroughs created RAT-173:
---
Summary: skip property does not skip report
Key: RAT-173
Hi,
On 2014-09-16 11:30, sebb wrote:
This should surely say ... unless you set addDefaultLicenseMatchers
to false.
Agreed?
+1
Most probably more documentation is needed in case projects are not
using Apache-licenses only.
Phil
Hi everyone,
I'm not really sure how the build can be fixed.
I've introduced a pluginManagement section to prevent a javadoc-plugin
error that complained about the HelpMojo's empty @version/author ...
but I don't really get where the
org.apache.maven.plugins:maven-plugin-plugin:jar:2.17
Hi *, hi dennis,
Am 15.10.2014 um 21:21 schrieb Dennis Lundberg:
Just looking at the log output, it sounds like someone has configured the
wrong version for maven plugin plugin. There is no 2.17 version for that
plugin.
thanks for your patch - I don't really get why there's is
Hi,
Am 04.11.2014 um 20:15 schrieb Jochen Wiedmann (JIRA):
[
https://issues.apache.org/jira/browse/RAT-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann closed RAT-103.
---
Proposal: automatic code formatting based on an
Hi,
Am 04.11.2014 um 23:14 schrieb Dennis Lundberg:
I've changed our Jenkins jobs for Rat, so that they now use Java 6.
That made our builds succeed again.
I thought there were strong arguments for staying with Java5 and
ensuring that RAT builds with Java5 ?!
Are these objections gone now?
Hi *,
after finalizing the analysis on
https://issues.apache.org/jira/browse/RAT-190
it seems that RAT is not explicit enough when it comes to encoding.
CAUSE/BUG BACKGROUND
If mvn is configured to run with a non UTF-8 encoding there will be
problems when matching UTF-8 content with licenses.
Hi Karl Heinz,
thanks for your interest and inquiries.
Am 27.03.2015 um 19:58 schrieb Karl Heinz Marbaise:
Furthermore is it possible to get the line numbers where to expect the
license to start ?
This would solve my problem to start integration of m2e for Eclipse into
apache-rat maven
Fellow devs,
I've created RAT-195 as a task to perform commits on.
Am 31.07.2014 um 22:18 schrieb P. Ottlinger:
Since all tests hopefully run on the branch I assume no functionality
broken, but will check carefully upon merge/commit.
OVERVIEW
I browsed the rather old branch and do not really
Hi Jochen,
thanks for your input -
Am 24.02.2015 um 15:48 schrieb Jochen Wiedmann:
What we should have, of course, is a Maven parameter
encoding=${rat.encoding}
which might be used to overwrite the Maven default.
I played around with the test project (attached to RAT-190) a bit.
If I
Hi *,
Am 24.02.2015 um 00:53 schrieb sebb:
The only change, that I'd be in favour of would be to enforce an
explicit encoding. Or, in other words, throw an exception, if an
encoding (aka charset) isn't explicitly choosen.
What do you think of adding two more configuration options in the
Hi *,
Am 24.02.2015 um 18:07 schrieb sebb:
+/** @see LicenseFamily#getName() */
+private final String name;
+/** @see LicenseFamily#getCategory() */
+private final String category;
+/** @see LicenseFamily#getNotes() */
+private final String notes;
+/**
Hi Maxim,
if I'm not too mistaken you are talking about this one:
https://issues.apache.org/jira/browse/RAT-179
Am 20.04.2015 um 20:56 schrieb Maxim Solodovnik:
could you please check if issue described here:
http://rat.markmail.org/thread/3qdpynxpejujbzm7 is fixed?
It seems it's not touched
Hi,
any opinions?
Am 15.04.2015 um 22:47 schrieb P. Ottlinger:
does anyone miss features we must add before we can release RAT 0.12.
I assume that merging in the GSOC stuff takes longer, thus I'd be fine
with doing a release before.
Since I don't know how to do the release-dance I cannot
Hi Maxim,
I'm not sure whether I understand your problem correctly
you do define new licenses and they are not taken into account?
Do you have an example project that shows the behaviour you see/expect?
org.apache.rat.mp.AbstractRatMojo#getLicenseMatchers() line 217ff. takes
the defined
Hi,
just to avoid confusion - I took Rober from these tasks to not give the
impression he's working on it.
In moste cases I don't know what theses cases mean or where their
motivation comes from.
Cheers,
Phil
Am 18.05.2015 um 16:33 schrieb Jochen Wiedmann (JIRA):
[
Hi guys,
does anyone miss features we must add before we can release RAT 0.12.
I assume that merging in the GSOC stuff takes longer, thus I'd be fine
with doing a release before.
Thanks for your opinions,
Phil
signature.asc
Description: OpenPGP digital signature
Hi,
APACHE-RAT-TASKS - FAILURES
I'm beginning to use IntelliJ more and more and just wondered if I'm the
onliest person with problems to run the tests in apache-rat-tasks:
*ReportTest::testAddLicenseHeaders* fails with
Hi,
Am 12.11.2015 um 16:39 schrieb Sebb (JIRA):
> Sebb created RAT-209:
>
> A license header is not usually required for short files that have no
> creative content.
I do not really think that this feature is that useful since it adds
some unclear "guessing" to the
Hi *,
Am 28.09.2015 um 13:16 schrieb sebb:
> However I wonder why we bundle the Ant plugin build in with Maven.
> Ant and Maven are independent build systems.
> An Ant-only shop is forced to use Maven to build RAT.
>
> We should probably split the project into a standalone core (CLI) and
> then
Hi *,
Jochen, thanks for your interest and proposal!
Am 29.09.2015 um 15:46 schrieb Jochen Wiedmann:
> with regard to RAT-163, and RAT-208, I'd like to push out a release of
> Rat 0.12 (Note: Minus Gradle Plugin!) and propose myself as the RM. Is
> anyone fine with that?
+1
We need to get 0.12
Am 27.09.2015 um 17:03 schrieb Apache Jenkins Server:
> Changes:
>
> [jochen] PR: RAT-208
>
> Added includesFile, excludesFile, includesFileCharacterset, and
> excludesFileCharacterset parameters,
> and support thereof.
The build fails because
org.apache.maven
maven-model
-
Hi all,
please let me rephrase my concerns
there are people that wait for a new RAT release and would like to use
the newly contributed gradle plugin.
Since we rely on a source code compatibility of JDK1.5 the build fails ...
thus we may not just upgrade our builds to use >=Java7, but need
Hi all,
happy new year to you all as time passes I wonder what kind of
problems we had when 0.12 was supposed to be released.
Can anyone help out? I don't know how to perform a release:
* what to build from where?
* how to sign?
* whom to notiy?
...
any help would be appreciated.
Cheers,
Hi Jochen,
Am 12.06.2016 um 20:17 schrieb joc...@apache.org:
> Log:
> Publidh site for Rat-0.12.
could you enlighten us which steps were needed to publish the page?
Thanks
Phil
Am 10.06.2016 um 12:27 schrieb sebb:
> What's that doing here?
>
> The ASF mirror site is not intended as an Eclipse workspace item...
+1
My impression is that the current site (to be released for 0.12) is
broken, too.
Is there a way to rework the site without affecting the release binaries?
Hi Jochen,
thanks for your efforts, but the mail contains some typos/wrong versions
and does not really announce the new features that were added.
At least that reflects the currently poor status of the project :-(
Cheers,
Phil
Am 13.06.2016 um 19:02 schrieb Jochen Wiedmann:
> Hi,
>
> The
Hi,
Am 14.06.2016 um 08:49 schrieb Jochen Wiedmann:
> So, I'd like us to pick up the offer of a simple directory, which we
> can use to upload or commit
> via SVN. At least, I know how to handle that.
+1
I'd even make it more simple - move to git and use gh-pages-branch to
generate the pages.
Hi everyone,
would it be good to just delete the existing 0.12-branch and perform a
fresh release?
This would allow to take the UI changes I introduced via RAT-210 to the
upcoming release.
I think we should not release with the old ASF logo.
Cheers,
Phil
signature.asc
Description: OpenPGP
Am 11.03.2016 um 09:36 schrieb Jochen Wiedmann:
> Philipp, it would have been nice to drop a few words on why we should
> upgrade. Just the higher version number is a bit weak.
Jochen, thanks for the hint -
I thought you were able to read the contents of the PR.
But I've added the description
Hi Karanjeet,
thanks for your interest in RAT :-)
Am 23.05.2016 um 20:33 schrieb Karanjeet Singh:
> (a) Does RAT check for License file in the top-level directory or it
> assumes that each file should have a license header?
The basic assumption is that each file needs to have a valid license
Hi,
Am 23.05.2016 um 22:24 schrieb Karanjeet Singh:
> Can you point me to some documentation which explains how can I configure
> my own licenses?
feel free to have a look on my example pages:
https://github.com/ottlinger/creadur-rat-examples
I do hope it's what you are looking for.
Phil
Am 22.05.2016 um 22:02 schrieb Dennis Lundberg:
> I suggest that we first roll back to a previous (for us working)
> version of the ASF parent and do the 0.12 release, requiring Java 5.
I only did that locally - nothing is committed yet
Thanks for your opinion!
Phil
Hi,
Am 22.05.2016 um 10:45 schrieb Karl Heinz Marbaise:
> exact svn location ?
nothing special - I've modified the parent-pom reference on trunk:
* https://svn.apache.org/repos/asf/creadur/rat/trunk
* https://svn.apache.org/repos/asf/creadur/whisker/trunk
*
Hi,
Am 21.05.2016 um 20:44 schrieb P. Ottlinger:
> I tried updating to the latest apache-parent-pom 18, but local builds
> fail with problems related to maven-enforcer, that is our being tied to
> JDK5.
Whisker and tentacles encounter the same exception having JDK6 it
seems to b
Hi,
Am 22.05.2016 um 10:05 schrieb Karl Heinz Marbaise:
>
> can you give a hint what exactly you have tried to build and using which
> parameters and Maven version? Java version you have used?
clean install works fine, but
site:site fails with the given exception.
$ mvn --version
Apache Maven
Hi Jochen,
Am 10.05.2016 um 13:35 schrieb Jochen Wiedmann:
> I was running "mvn release:prepare" in the release branch for Rat
> 0.12. However, the created tag contains SNAPSHOT versions [1]. Are you
> aware of anything that I might have done wrong?
did you follow
Hi,
Am 11.05.2016 um 07:39 schrieb Jochen Wiedmann:
> yes I did run release:prepare in the parent project (except, that I
> did it in the release branch, and not in the trunk).
Maybe maven was unable to properly create the branch -
is it possible to remove the branch and try again?
Did you run
Hi,
thanks for your input.
Am 17.07.2016 um 04:55 schrieb Javen O'Neal:
> It probably makes sense to start a discussion with the Apache
> Licensing/Legal team to see if they would approve this 1-character
> modification to their license statement and start promoting the https
> version.
I think
Am 22.06.2016 um 12:12 schrieb Stian Soiland-Reyes:
> Using pure Maven and svn2pub or git2pub should be sufficient, and
> allowing GitHub-contributions to editing the website lowers the
> barriers for outsiders.
+1
The simpler the better.
I do even prefer the github based approach that a
Hi,
Am 30.01.2017 um 15:18 schrieb Karl Heinz Marbaise:
> based on the number of fixed issues in RAT 0.13 i would like to start
> making a new release of Apache RAT to get forward.
+1
No problem with releasing - just be careful with the homepage since it's
the manually crafted version (which
Hi Jochen,
thanks for verifying that the problems I tried to report in May
(subject: update to newest apache-parent pom yields problems with maven
enforcer, from: 2016-05-21 ) are still there.
My comment (in the task) was there to avoid additional nodes why I did
not update the ASF parent.
Feel
Hi,
Am 04.09.2016 um 00:10 schrieb Karl Heinz Marbaise:
>Transfer content of target/staging
>(manually done to gh-pages branch for above example which works).
thanks for your help!
I've regenerated the site under
https://ottlinger.github.io/creadur-rat-examples/index.html
In case
Hi,
Am 05.09.2016 um 08:59 schrieb Karl Heinz Marbaise:
>
> Why waiting so long? Do you have no time at the moment?
I thought waiting longer yields a bigger chanhce for feedback, but maybe
you are right.
> If you so I can try to publish the site?
Go ahead - can you add more details on what
Hi all,
Am 15.08.2016 um 09:29 schrieb P. Ottlinger:
> The problem is that not many people know how to trigger and perform
> website updates - apart from that the 0.12 webpage is broken
I'm trying to fix the webpage and generated the current HEAD to
https://ottlinger.github.io/cread
Hi,
Am 30.08.2016 um 23:45 schrieb Karl Heinz Marbaise:
> I'm just curious why the staging site[1].
> is more up-to-date ((Release 0.12 is on this page)
> than the main site[2] and why the site build [3] is not working ?
as I mentioned yesterday: the site from the 0.12-branch is buggy (it
Hi!
I tried bringing up this issue more than once, thus I was very happy
that somebody else feels the same.
In 0.12 we had a contribution that added a Gradle plugin. It failed due
to insufficient dependencies with JDK5.
Thus there's a need to update if we want to stay relevant.
If we are
Hi,
Am 11.09.2016 um 20:53 schrieb Jochen Wiedmann:
> There is no reason, to retreat the plugin, as long as it becomes a
> standalone module.
To follow your argumentation: Ant and Maven-module should be standalone
as well.
I think that's rather hard and makes things even more complicated as
Hi Karlheinz,
sorry to hear that.
Am 09.09.2016 um 17:20 schrieb Karl Heinz Marbaise:
> I have filed in the information into the issue[1]
After reading your comments in the ticket I've decided to request a new
repo:
https://git-wip-us.apache.org/repos/asf/creadur-site.git
with github
Am 09.09.2016 um 22:21 schrieb P. Ottlinger:
> After reading your comments in the ticket I've decided to request a new
> repo:
> https://git-wip-us.apache.org/repos/asf/creadur-site.git
> with github integration.
I've pushed the current RAT site to the main branch of above repo.
Ho
Am 10.09.2016 um 00:08 schrieb Karl Heinz Marbaise:
>
> shouldn't that be put on a branch called asf-site ? Or do i mistaken
> something?
DONE.
Not sure what is happening/needs to happen yet.
Thanks
Phil
Am 10.09.2016 um 01:54 schrieb Karl Heinz Marbaise:
>
> I have made a small change on the site to see how long it takes..very
> short time...the larger the change the longer it takes..
great news! Thanks.
I tried changing the subdirectory rat, but the stuff does not seem to be
autopublished as
Am 09.09.2016 um 22:48 schrieb Karl Heinz Marbaise:
> You can define a language level in a parent pom and overwrite it in a
> child ...so no problem...
fine with me - just create a ticket and go ahead :-)
The builds will verify that stuff is working fine.
Phil
Hi,
Am 09.09.2016 um 22:33 schrieb Karl Heinz Marbaise:
> after taking a deeper look (pom's in particular) into the different
> parts whiskers, tentacles and rat...
>
> I'm the opinion there must be done something to generalize the pom's of
> the different parts / projects to prevent pom
Hi,
Am 23.09.2016 um 16:38 schrieb Karl Heinz Marbaise:
> And yes this should be fixed on the site...
how would we want to fix this?
The cgi-script looks rather generic.
I wouldn't mind if we had
* a 0.13-SNAPSHOT site, but could only download 0.12 or
* enhance the download.cgi to allow
Hi,
Am 18.08.2016 um 14:41 schrieb Jochen Wiedmann (JIRA):
>
> [
> https://issues.apache.org/jira/browse/RAT-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426364#comment-15426364
> ]
>
> Jochen Wiedmann commented on RAT-216:
>
Hi,
Am 25.08.2016 um 10:56 schrieb Jochen Wiedmann:
> Can anyone explain to me, what's wrong here?
I tried upgrading some stuff - since the enforcer-rules are still in
beta upgrading to 1.0-beta-5 fixed the problem.
Thanks for bringing up the issue; no need to upgrade our language level
from
1 - 100 of 249 matches
Mail list logo
