Try and you will see what happens.
I do not use it because I am the old school using IDEA and command line. I
need to see the code in IDE because this Diff in GitHub does not show me
the changes as good as IDEA does.
On Wed, Dec 19, 2018 at 6:01 PM Enrico Olivelli wrote:
> self anwsered:
> just
:24 AM Dejan Stojadinovic
wrote:
> Thanx Tibor, I left short comments on JIRA issues (just to mark them).
> I hope I will squeeze first github PR in a few days.
>
> Regards,
> Dejan
>
> On 2019/03/24 23:19:08, Tibor Digana wrote:
> > Hi Dejan,
> >
> > G
would appreciate to have additionally
the previous developers on the board as well and grow the team, i.e.
Andreas and Kristian.
Cheers
Tibor
On Mon, Mar 25, 2019 at 5:11 PM Stephane Nicoll
wrote:
> Thanks for having a look Tibor!
>
> On Mon, Mar 25, 2019 at 4:37 PM Tibor Digana
> wro
oll
wrote:
> On Tue, Mar 26, 2019 at 12:26 PM Tibor Digana
> wrote:
>
> > Stephane,
> >
> > >> I wanted to make sure that the JUnit5 story was functional
> >
> > I really don't like politics.
>
>
> What's that supposed to mean? If you want to quot
s.apache.org/slack-invite
> #maven <https://s.apache.org/slack-invite#maven> channel
>
>
> Enrico
>
> Il giorno mer 27 mar 2019 alle ore 15:45 Tibor Digana
> ha scritto:
> >
> > Stephane, What exists in our agreement are two issues (SUREFIRE-1546 and
> &
Enrico wants to integrate GitHub with Gitter.
He did not mean Slack for this purpose and therefore I mentioned to
propagate Gitter.
On Sun, Mar 24, 2019 at 12:07 PM Olivier Lamy wrote:
> agree with what Romain said.
>
> On Sun, 24 Mar 2019 at 21:06, Romain Manni-Bucau
> wrote:
>
> > Hi,
> >
>
ack and github
> https://get.slack.help/hc/en-us/articles/232289568-GitHub-for-Slack
> but please if we can avoid having in the maven or surefire it's just too
> verbose... (better having dedicated channel such maven-github etc..)
>
>
> On Sun, 24 Mar 2019 at 21:16, Tibor Digana wrot
contributed few (easy) maven commits:
> https://github.com/apache/maven/commits?author=dejan2609
>
> Regards,
> Dejan Stojadinović
>
> On 2019/03/23 21:47:04, Tibor Digana wrote:
> > It's going to be very pedant work for someone who want to help us in
> > Surefire.
&
2.22.2-SNAPSHOT works for our purpose so I was wondering if more
> > fixes could be backported and/or if someone would like to review those
> > changes.
> >
> > Thanks,
> > S.
> >
> >
> > [1] https://github.com/snicoll/maven-surefire/tree/2.22.x
> >
>
Hi,
All the issues for maven-compiler-plugin:3.8.1 is fixed.
https://issues.apache.org/jira/projects/MCOMPILER/versions/12343484
Can we agree on cutting the release version?
Do you see any reason to wait?
I am very happy to see a new incremental compiler, see
f more
> > fixes could be backported and/or if someone would like to review those
> > changes.
> >
> > Thanks,
> > S.
> >
> >
> > [1] https://github.com/snicoll/maven-surefire/tree/2.22.x
> >
> > On Wed, Feb 27, 2019 at 1:46 PM Tibor Diga
I want to observe a list of config parameters (names) in MOJO plugin
without injecting @Param for each.
If the customer still uses old parameter, the MOJO wouldn't know it.
Therefore I want to read the list of paramaters. And if he stil uses the
old name, the plugin would fail with a hint saying
Karl, why the release notes on Jira are for the old version 3.6.0 and not
the 3.6.1?
On Thu, Apr 4, 2019 at 9:55 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We have solved 42 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12338966
>
> There are issues left in
Hey Karl. feel free to start the release process. No objections from my
side.
@Robert is there some more you want to add in the version 3.8.1?
T
On Sat, Mar 23, 2019 at 12:20 PM Tibor Digana
wrote:
> Hi,
>
> All the issues for maven-compiler-plugin:3.8.1 is fixed.
> https://issue
It's going to be very pedant work for someone who want to help us in
Surefire.
I am looking for some volunteer who will remove the deprecated config param
`forkMode` in favor of `forkCount`. All our ITs should use `forkCount`
since then.
Additionally, the volunteer should deprecate
Hi Stephane,
We are talking only about these two commits [1]?
Notice that 001e807 modifies file names to the verbose one which breaks
backwards compatibility and this should not forcibly (by default) happen in
your version/branch.
Try to fork the project, make a local branch and then reset HEAD
+1
On Sun, Feb 24, 2019 at 9:34 PM Karl Heinz Marbaise
wrote:
> Hi to all,
>
> We solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12344643
>
> There are still a couple of issues left in JIRA:
>
>
+1
On Fri, Mar 1, 2019 at 2:57 PM Robert Scholte wrote:
> Hi,
>
> We solved 46(!) issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12343313=Text
>
> There are still a couple of issues left in JIRA:
>
>
Stephane, the problem is with Spring upgrade policy as I have understood.
What about releasing RC4 for you?
Do you really need to have SUREFIRE-1546 done? We do not want to enable it
implicitly as it is done in master right now, and therefore M4 needs to
take more time to enable this feature via
welcome compromises on our side in ASF and now your steps in
Spring should be to make compromise in your internal policies.
Cheers
Tibor
On Mon, Feb 25, 2019 at 11:44 AM Stephane Nicoll
wrote:
> Thanks for the reply. See my feedback below
>
> On Mon, Feb 25, 2019 at 11:20 AM Tibor Digana
Hi Karl,
How you want to continue with this? The release plugin made commits to the
Git history. Do you want to complete it with deployment?
On Sun, Feb 24, 2019 at 9:34 PM Karl Heinz Marbaise
wrote:
> Hi to all,
>
> We solved 3 issues:
>
>
Stephane,
I have been quite busy with other JUnit5 work - SUREFIRE-1585.
Can you join us in the chat on Slack "the-asf.slack.com"?
You will find the Channel named "surefire".
Ping us as soon as you are ready and we will find some way.
I am glad!
Cheers
Tibor
On Mon, Feb 25, 2019 at 8:54 AM
Is it so a big problem to keep both versions? This is our internal Nexus
server anyway.
On Wed, Feb 13, 2019 at 1:27 PM Benedikt Ritter wrote:
> Hello,
>
> Am Di., 12. Feb. 2019 um 08:39 Uhr schrieb Benedikt Ritter <
> brit...@apache.org>:
>
> > Hello,
> >
> > Am Mo., 11. Feb. 2019 um 18:39 Uhr
>
> > Am Mi., 13. Feb. 2019 um 17:48 Uhr schrieb Tibor Digana <
> > tibordig...@apache.org>:
> >
> > > Is it so a big problem to keep both versions? This is our internal
> Nexus
> > > server anyway.
> > >
> >
> > From my PoV th
Benedikt, it does not mean that something with public IP is for public use.
We made only a compromise for some users to verify some functionality.
On Thu, Feb 14, 2019 at 11:42 AM Benedikt Ritter wrote:
> Am Mi., 13. Feb. 2019 um 17:48 Uhr schrieb Tibor Digana <
> tibordig...@a
+1
On Tue, Feb 5, 2019 at 12:15 AM Michael Osipov wrote:
> Hi,
>
> We solved 12 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12344885
>
> There are still a couple of issues left in JIRA:
>
>
+1 used 3.6.1 in project with build success
On Thu, Apr 4, 2019 at 9:55 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We have solved 42 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12338966
>
> There are issues left in JIRA for Maven core:
>
>
On Tue, Mar 26, 2019 at 9:24 AM Dejan Stojadinovic
wrote:
> Thanx Tibor, I left short comments on JIRA issues (just to mark them).
> I hope I will squeeze first github PR in a few days.
>
> Regards,
> Dejan
>
> On 2019/03/24 23:19:08, Tibor Digana wrote:
> > Hi
e correct one, cause I
> mistaken the link I have copied...
>
> Please advise that the solved issue URL (JIRA Release notes) for 3.6.1 is:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344378=12316922
>
>
> Kind regards
> Karl Heinz Marbaise
&g
Hi,
In *apache/maven-site* [1], I have updated checkstyle for IntelliJ IDEA
because the new IDEA 14+ is not able to understand the old format.
[1]: https://github.com/apache/maven-site/pull/78
Cheers
Tibor
As I have understood junit5 users, XML should have an additional
information (an attribute) describing Display Name for the XML attribute
"testcase.classname", "testcase.name" and "testsuite.name".
On Sat, Apr 13, 2019 at 2:43 PM Christian Stein wrote:
> Hi Maven devs, especially Maven Surefire
Definitely it should be java7.html
On Mon, Apr 15, 2019 at 8:03 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> On 15.04.19 18:44, Elliotte Rusty Harold wrote:
> > Is this page still accurate or should it be deleted?
> >
> > https://maven.apache.org/developers/java6.html
>
> this should be changed to
o and use Maven)
> > >> Maven 3.6.0
> > >> Java 8 update 202
> > >>
> > >> The build log says:
> > >> [INFO] There are 2 errors reported by Checkstyle 8.19 with
> > sun_checks.xml
> > >> ruleset.
&
I will fix it when I have time, but not today
>
>
> Thank you very much for reporting
> Enrico
>
>
>
> Il giorno mar 14 mag 2019 alle ore 16:24 Enrico Olivelli
> eolive...@gmail.com> ha scritto:
>
> >
> >
> > Il giorno mar 14 mag 2019 alle or
; Maven 3.6.0
> > >> Java 8 update 202
> > >>
> > >> The build log says:
> > >> [INFO] There are 2 errors reported by Checkstyle 8.19 with
> > sun_checks.xml
> > >> ruleset.
> > >> [ERROR]
> > >>
&g
+1
On Wed, May 15, 2019 at 10:33 PM Robert Scholte
wrote:
> Hi,
>
> The Apache Maven project consist of about 100 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to make real progress on all these projects, including
>
Hi Enrico,
My browser has also loaded
https://maven.apache.org/plugins/maven-checkstyle-plugin/
This is the version and release date I see on the top right corner of the
page:
Version: 3.1.0 | Last Published: 2019-05-12
Is it right information?
Cheers
Tibor
On Sat, May 25, 2019 at 5:24 PM
issue with m2e-core and opened a
> PR
> > (as mentioned above), then logged an issue with maven-archetype and
> opened
> > a PR (which is essentially what we are discussing here).
> >
> > Tony
> >
> > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=5
There is Jira issue reported
https://issues.apache.org/jira/browse/SUREFIRE-1664
Every volunteer is welcome!
On Sun, Jun 2, 2019 at 11:23 PM James Gough wrote:
> Hi,
>
> I've just started looking into
> https://issues.apache.org/jira/browse/MTOOLCHAINS-21, which is a bug
> report
> about
What stops us developing on Java 8?
Maven project stops us.
We wanted to use Java 7 and not higher. Therefore reworking the little code
with removed dom4j keeps javac still on java7 and we would not have a
problem when dom4j moves to java9+ because of non-applicable CVEs. We can
use Java XML Api
First of all, this PR was create because of vulnerability CVE-2018-1000632.
Vulner or non-vulnerability, the version of javac for dom4j:1.6.1 is not an
argument for me.
If some code was broken in that version, it would be an argument. But it is
not an argument to infinitely grow versions only
but is not a blocking
> requirement (especially since this plugin is not a lifecycle plugin).
>
> Robert
> On 4-6-2019 22:05:33, Tibor Digana wrote:
> What stops us developing on Java 8?
> Maven project stops us.
> We wanted to use Java 7 and not higher. Therefore reworking the little code
+1
On Tue, May 28, 2019 at 8:55 PM Robert Scholte wrote:
> Hi,
>
> The Apache Maven project consist of about 100 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to make real progress on all these projects, including
>
Not sure there is a real limitation to do it.
We can at least see new candidates for committers from the group of
contributors.
The contributors like it of course, and why not, their work is valuable!
On Tue, May 28, 2019 at 10:24 PM Enrico Olivelli
wrote:
> Hi,
> Is there any rule to add a
We should ask the contributor because some German companies do not allow
you to work in OSS unless you have got an internal confirmation from
commercial management.
My last company had this rule; does not matter if the prodution area is the
same with OSS or not.
In my case we were in totally
+1, successful build, sha512 ok
On Thu, May 30, 2019 at 5:26 PM Michael Osipov wrote:
> Hi,
>
> We solved 22 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317230=12342342
>
> There are still a couple of issues left in JIRA:
>
>
+1
On Fri, Jun 7, 2019 at 3:32 PM Robert Scholte wrote:
> Hi,
>
> The Apache Maven project consist of about 90 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to make real progress on all these projects, including
> our
+1
sha512 ok
build passed
Failed unit tests in Surefire need to be fixed.
On Fri, Jun 7, 2019 at 2:57 PM Michael Osipov wrote:
> Hi,
>
> We solved 16 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12343094
>
> There are still a couple of issues left in
+1
On Fri, Jun 7, 2019 at 4:19 PM Robert Scholte wrote:
> Hi,
>
> We solved 9 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318020=12335855=Text
>
> There are ZERO issues left in JIRA:
>
>
Why you use Eclipse. Use InteliJ IDEA. It is professional tool. Every
company has money to buy enterprise IDEA, the company wouln'd say no
because it is price you pay once and you can upgrade to major version
within whole year. You can use it forever without paying more after the
support period of
ter and oss
>
> Le sam. 8 juin 2019 à 10:29, Tibor Digana a
> écrit :
>
> > Why you use Eclipse. Use InteliJ IDEA. It is professional tool. Every
> > company has money to buy enterprise IDEA, the company wouln'd say no
> > because it is price you pay once and you can up
If polyglot was included directly in Maven dist, we could run the build
with something like this:
$ mvn -f pom.kts install
Any thoughts?
On Sat, Jun 8, 2019 at 1:55 AM Manfred Moser
wrote:
> Shipped 0.4.1 of polyglot-maven with more kotlin goodness ;-)
>
>
>
@Mickael Istria
@Eric Lilja
@Elliotte Rusty Harold
We are the maintainers.
But there is one thing I do not understand why such upgrade is so important
for the users even if overriding the dependency in user's POM is so simple.
Do you inherit from this project and you need dom4j as transitive
+1 for deleting 9 1nd 10.
yes, there's a statement by Robert "all non-EOL versions and the first EA".
Now that includes 7 and 8 .
On Sun, Jun 2, 2019 at 10:42 AM Enrico Olivelli wrote:
> Hi,
> To me it is not clear if we should keep tests against java 9 and java 10.
>
> I think it is mostly a
Enrico, I sent you a message regarding this question on GitHub, pls see it
here
https://github.com/apache/maven-archetype/pull/28#issuecomment-498030811
On Sun, Jun 2, 2019 at 12:44 PM Enrico Olivelli wrote:
> Hi,
> I am not able to understand why integration tests of Maven Archetype plugin
>
+1
On Thu, Jun 13, 2019 at 5:18 PM Tibor Digana wrote:
> Hi,
>
> We solved 1 issue:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122=12345450
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/i#issues
+1, sha512 ok, and build passed successfully on jdk 1.8 and 12
On Wed, Jun 12, 2019 at 5:29 PM Enrico Olivelli wrote:
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342845=Text=12319223
>
> There are still a couple of issues left in JIRA:
>
>
.. but this java 1.7 project and not 1.8 you you have guessed.
On Sat, Jun 15, 2019 at 3:07 PM Behrang Saeedzadeh
wrote:
> Enabled generating Java 9+ projects as well as using JUnit 5.x
>
> I have kept the plugin backwards compatible -- if javaCompilerVersion and
> junitVersion properties are
+1 ... sha 512 .. ok, Maven build .. ok.
On Sun, Jun 9, 2019 at 3:22 PM Michael Osipov wrote:
> Hi,
>
> We solved 7 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12345229
>
> There are still a couple of issues left in JIRA:
>
>
Hi James,
Added to dev mailing list.
Perhaps nice but it does not help, due to you wont find any critical issues
since at least the PMD is running in our project builds.
I would appreciate if you participate at GitHub in Maven because this is
the physical help and fix these issues in
Hi,
The vote has passed with the following result:
Karl Heinz Marbaise, Jesper Udby, Tibor Digaňa, Michael Osipov, Sylwester
Lachiewicz, Enrico Olivelli
PMC quorum: reached
I will promote the artifacts to the central repo.
Cheers
Tibor17
The Apache Maven team is pleased to announce the release of the Apache
Maven Archetype Plugin, version 3.1.1.
The Archetype Plugin allows the user to create a Maven project from an
existing template called an archetype. It also allows the user to create an
archetype from an existing project.
The Apache Maven team is pleased to announce the release of the Apache
Maven Archetype Plugin, version 3.1.1.
The Archetype Plugin allows the user to create a Maven project from an
existing template called an archetype. It also allows the user to create an
archetype from an existing project.
Hi,
We solved 1 issue:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122=12345450
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/i#issues/?jql=project+%3D+ARCHETYPE+AND+status+%3D+Open+ORDER+BY+priority+DESC
Staging repo:
sorry my typo.
Thx
On Thu, Jun 13, 2019 at 9:18 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> This is not for Maven Archiver ..it is for Maven Archetype ...
>
> Apart from that
>
> +1 from me
>
> Kind regards
> Karl Heinz Marbaise
>
> On 13.06.19 17:18, Tibor Digan
Hi Michael,
The latest build failed [1]. Have you analysed the root cause with these
failed tests?
[1]:
https://builds.apache.org/job/maven-box/job/maven-wagon/job/master/16/#showFailuresLink
T
On Thu, Jun 13, 2019 at 3:46 PM Michael Osipov wrote:
> Hi,
>
> We solved 6 issues:
>
>
..
yes, incremental reports to fixes
yes, minor reports to features
I have checked those two, and really they are not features - improvement in
logger etc.
So 3.6.2 is alright, 3.7.0 too.
Worse is timing, because both improvements in 3.6.2 are open.
2 Improvements:
In this case trigger the CI build manually. There might be erronous tests
blocking a port, as you say, if they use same ports.
Thx
On Thu, Jun 13, 2019 at 6:57 PM Michael Osipov wrote:
> Am 2019-06-13 um 18:45 schrieb Tibor Digana:
> > Hi Michael,
> >
> > The latest build
Who can rework the Jenkins plugin we use, so that the build won't be
triggered after Groovy libs have changed?
Somebody changes [1] and [2] and then all 100 Maven projects run all bunch
of branches.
The queue is huge in Jenkins, and this is the blocker for the entire
organization and not only for
+1
sha ok, build passed
On Wed, Jun 19, 2019 at 11:00 PM Michael Osipov wrote:
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12345669
>
> There are still a couple of issues left in JIRA:
>
>
Hey StephenC,
I was looking for Anders' answer in Eclipse issue. Important is that the
issue was isolated to https://github.com/tesla/m2eclipse-mavenarchiver and
to Maven.
Issues are everywhere, in every tool, that's the life. Maybe some did not
reach such ratings to fix them nor contributor who
Hi Cristiano,
I guess your architect who designed your company parent POM made everying
honestly right.
But we can prove or avoid the error on the tool if we simply add something,
then make a comparison test and we exclude added things which could not
change the outcome.
Open the project in
mpany policy that is aggressive
> about CVEs.
> Please let me know if there is anything I can do to help with this.
>
> [1] https://issues.apache.org/jira/browse/ARCHETYPE-568
>
> Thanks!
> Tony Homer
>
> On 6/5/19 , 5:52 AM, "Tibor Digana" wrote
+1
On Wed, May 8, 2019 at 8:25 PM Robert Scholte wrote:
> Hi,
>
> The Apache Maven project consist of about 100 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to make real progress on all these projects, including
>
+1
Karl, perhaps "plexus-archiver:4.1.0" can speedup maven-war-plugin too.
WDYT?
On Wed, May 8, 2019 at 10:22 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12344629
>
> There are still a couple of issues
gt; > Tibor
> > It is strage all its are passing on CI.
> > Are you sure you have correcly unpacked the package?
> >
> >
> > Il lun 13 mag 2019, 21:23 Tibor Digana ha
> > scritto:
> >
> >> checked the sha512 of src zip, ok
> >> checked the b
checked the sha512 of src zip, ok
checked the build, failed (mvn verify -P run-its,quality-checks)
[INFO] Building: MCHECKSTYLE-54\pom.xml
[INFO] MCHECKSTYLE-54\pom.xml ... FAILED
(5.3 s)
*Mcheckstyle54.java:[1] (misc) NewlineAtEndOfFile: File does not end with
gt;
> Il lun 13 mag 2019, 21:23 Tibor Digana ha
> scritto:
>
> > checked the sha512 of src zip, ok
> > checked the build, failed (mvn verify -P run-its,quality-checks)
> >
>
> What is 'quality-checks' profile? I have never heard about it
>
> Enrico
>
+1
On Thu, May 23, 2019 at 7:56 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12343424
>
> There are still a couple of issues left in JIRA:
>
>
+1
Thx Enrico for your work!
On Mon, May 13, 2019 at 11:52 AM Enrico Olivelli
wrote:
> Hi,
>
> We solved 13 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342397=Text=12317223
>
> Please note that this version now only supports CheckStyle 8+ and Java 8
> (as
Thx for your effort.
Good job with everything you have done in Maven.
On Fri, May 10, 2019 at 2:23 PM Enrico Olivelli wrote:
> Hi all,
> I am going to cut a release of Maven Checkstyle Plugin during this weekend.
>
> There are major changes, I will release 3.1.0 version:
> - drop support for
Is it what Marc Philipp was asking me on the chat?
The purpose looked like a top secret ;-) but it was not because Mark needed
it for testing of some internal report.
Now it looks like Junit5 wants to remove the Surefire report out been dead
and move these features into Junit5.
The RunListener
it's better if users still consider it as a blackbox and use
native listener which normally appear on classpath of tests.
On Thu, May 16, 2019 at 12:51 PM Benedikt Ritter wrote:
> Hello,
>
> Am Do., 16. Mai 2019 um 12:36 Uhr schrieb Tibor Digana <
> tibordig...@apache.org>:
>
>>
> > >> The build log says:
> > >> [INFO] There are 2 errors reported by Checkstyle 8.19 with
> > sun_checks.xml
> > >> ruleset.
> > >> [ERROR]
> > >>
> >
> src\main\java\org\apache\maven\plugins\checkstyle\m
> > >>
> > >> The build log says:
> > >> [INFO] There are 2 errors reported by Checkstyle 8.19 with
> > sun_checks.xml
> > >> ruleset.
> > >> [ERROR]
> > >>
> >
> src\main\java\org\apache\maven\plugins\ch
+1
All checks passed.
On Sat, Apr 27, 2019 at 6:04 PM Enrico Olivelli wrote:
> Hi,
>
> We solved 1 issue:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345433=Text=12317927=Create_token=A5KQ-2QAV-T4JA-FDED%7C568123541489d632001256d1b9872c5af17721f9%7Clout
>
> There are
+1
On Sat, Apr 20, 2019 at 8:01 PM Robert Scholte wrote:
> Hi,
>
> We solved 13 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122=12340346=Text
>
> There are still a couple of issues left in JIRA:
>
>
+1
All checks passed.
On Sun, Apr 28, 2019 at 3:08 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225=12343484
>
> There are still a couple of issues left in JIRA:
>
>
ote:
> Tibor,
> I suggest ou to take a look to some of the great talk from Mark R, Java
> cheif architect
>
> https://youtu.be/eOWsEHibxbU
>
>
> Enrico
>
>
> Il ven 19 apr 2019, 22:21 Tibor Digana ha
> scritto:
>
> > Sorry guys but again, what di
Sorry guys but again, what did you change in the language?
Some Japaneese java.time support, some deprecations, ...
Why the language architect does not bring something new? You wanted to
improve Generics. C# has features like s/getter, and Java has not.
But this is weaker release than Java 1.6
Sorry, wrong link, this is correct
[1]
https://issues.apache.org/jira/browse/SUREFIRE-1652?focusedCommentId=16822409=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16822409
On Sat, Apr 20, 2019 at 1:26 PM Tibor Digana wrote:
> Bernd, why here? See [1], I am tot
e
> latest Java releases but in respect for this mailing list I refrain from
> discussing it.
>
> Gruss
> Bernd
>
>
>
>
> --
> http://bernd.eckenfels.net
>
>
> Von: Tibor Digana
> Gesendet: Freitag, April 19, 2019 11:04 PM
>
a look to some of the great talk from Mark R, Java
> > cheif architect
> >
> > https://youtu.be/eOWsEHibxbU
> >
> >
> > Enrico
> >
> >
> > Il ven 19 apr 2019, 22:21 Tibor Digana ha
> > scritto:
> >
> > > Sorry guys but aga
I also would prefer using Java 8 in plugins but we have made an agreement
to use Java 7 and migrate plugins to API 3.0.
This means the ant-maven-plugin should be released with version 3.0.0.
Enrico, do we loose some rules of Checkstyle if using the old version of
the plugin at Java 7 here in
> late).
>
> On 2019/04/07 01:19:13, Tibor Digana wrote:
> > Hi Dejan,
> >
> > I almost forgot your email.
> > Pls create a PR on GitHub with a little work even if still incomplete but
> > at least we would not forget it.
> > As you can see in [1
you have to publish it other way, because this is a big project.
I will post to you Enrico in private on Slack because you have to use out
Unix machine which is fast upload then.
On Fri, Apr 26, 2019 at 7:10 PM Enrico Olivelli wrote:
> I am trying to stage the website
> I get this error
pls do not override the production page. Users can always find the list of
artifact in mavenrepo.
On Thu, Apr 25, 2019 at 7:08 PM Enrico Olivelli wrote:
> Hi,
> I am staging a release for Surefire 2.22.2, I am not cuting it from
> master branchm which is 3.x.
>
> I think I should not update the
ers
Tibor17
On Thu, Jul 4, 2019 at 1:48 PM Graham Leggett wrote:
> On 04 Jul 2019, at 13:12, Tibor Digana wrote:
>
> Did you read the Jira and the commit in Git?
> It was written in the way to push Java 8 without any strong reason, sorry
> for that but it's truth.
>
>
&
Suddenly we have one common problem on Jenkins builds in master branches.
It looks random and some files produced by ITs do not exist in "target".
Do you understand the root cause?
This is the error log in maven-archetype:
I downloaded the sources but the build failed with one error.
The error looks reasonable to me. You guys did not see this issue?
As it seems, this test should create *mjavadoc338-direct-1.0-sources.jar*
but I do not see that one in target/.
[INFO] Building: MJAVADOC-338_downloadSources\pom.xml
901 - 1000 of 1362 matches
Mail list logo
