Hi Arno,
I used Java 1.8.
Cheers
Tibor
On Fri, Jul 5, 2019 at 11:40 PM Arnaud Héritier wrote:
> Which java version are you using ?
> I will test again this weekend
>
> Le ven. 5 juil. 2019 à 22:20, Tibor Digana a
> écrit :
>
> > I downloaded the sources but the bui
't be
downloaded. Why Jenkins passed.
On Fri, Jul 5, 2019 at 11:40 PM Arnaud Héritier wrote:
> Which java version are you using ?
> I will test again this weekend
>
> Le ven. 5 juil. 2019 à 22:20, Tibor Digana a
> écrit :
>
> > I downloaded the sources but the build fa
Hello Olivier,
After seen the repo, it was obvious that Jetty was developed in three code
lines namely 9.2.x, 9.3.x and 9.4.x.
The next fact is that the Maven team agreed to use Java compiler 1.7. The
user can use JDK 1.8 or higher with security patches.
These two facts mean that we can stick to t
Hi Clemens,
I think you are right, I also have to add -Dhttps.protocols=TLSv1.2 in to
CLI when using J7.
The Jenkinsfile does it [1] already but we should investigate the ITs and
add TLS in CLI of the ITs as well unless it's in there.
[1]:
https://gitbox.apache.org/repos/asf?p=maven-jenkins-lib.gi
/\Q[DEBUG] Additional arguments:
> \E(?:-Dhttps.protocols=TLSv1.2 )?-P(.+)\Q-DperformRelease=true -f
> pom.xml\E/
>
> ...
>
> But: where does this additonal arg come from in the first place? Should
> the match be re-written?
>
> Cheers,
>
> Clemens
>
> Am 14.07.20
this
> noise in the dev-mail-group? Where could I have read about this system
> property? Is it documented somewhere?
>
> Cheers, Clemens
> [1]
>
> https://stackoverflow.com/questions/39157422/how-to-enable-tls-1-2-in-java-7
>
> Am 14.07.2019 um 18:58 schrieb Tibor D
Hi Lenant,
The plugin looks like this in POM:
... implements="pkg.ResolverImpl"...
~~~ plugin dependencies ~~~
groupId,artifactId,version ~~~ for ~~~ artifact ~~~ having ~~~
pkg.ResolverImpl.class ~~~
So " implements" is already the extention style.
The class Resolver
Hello devs,
You may have noticed that Maven build fails over one month.
We cann't cut a new release version of Maven.
Additionally, another Maven builds still fail too.
Not speaking too long, I want to inform you that I want to revert the
commit of MRESOLVER-7 in Maven Core and make the build pas
Heads up!,
I am investigating the build errors on Maven Core.
So I created three branches moved the HEAD backwards (i.e. git reset --hard
HEAD~12) and observed the outcome.
I have investigated 29 commits. Not sure how far to go...
`maven-resolver-1.3.3-reset-head-12` crashed with Linux + JDK 7,
For these purpose of build stability, see Jira issue
https://issues.apache.org/jira/browse/MNG-6712
"Revert maven-resolver:1.4.0 to 1.3.3"
On Tue, Jul 16, 2019 at 12:48 PM Tibor Digana
wrote:
> Hello devs,
>
> You may have noticed that Maven build fails over one month.
&g
Clemens, why the issues cannot use Jira ID only?
If somebody wants to know more, she/he can still open Jira and see.
Another position is when you develop a new feature and then human readable
name should be used.
This way we know that we have more ITs for bug than originally TDD
features, or oposit
, I started by doing a lot of cleanup on old merged
> branches: it
> would be nice if everybody did its own cleanup when merging
>
> Regards,
>
> Hervé
>
>
> [1]
> https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven/job/
> master/
> <https://builds.
gards,
>
> Hervé
>
> [2]
> https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven/job/master/242/testReport/
>
> Le samedi 20 juillet 2019, 12:48:27 CEST Tibor Digana a écrit :
> > I wrote in our chat that Maven Core fails randomly on random JDK versions
>
t; > >> 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]
> > >>
>
Hi Clemens,
Does JDK 7u80 work for you on fresh empty local repo?
It does not for me on Surefire project! The Maven fails downloading the
artifacts from Maven Central this month. Before the build was okay.
So I issued the ticket https://issues.apache.org/jira/browse/INFRA-18775
and I hope that o
+1
On Wed, Jul 24, 2019 at 9:59 PM Michael Osipov wrote:
> Hi,
>
> We solved 13 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923&version=12343145
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D
I think a good compromise would be to introduce default value "TLS1.2" for
"https.protocols" in the POM section "properties" which can be overridden
in command line.
TLS1.2
On Wed, Jul 24, 2019 at 11:37 PM Clemens Quoss wrote:
> Hi Robert,
> well it is already handled in the POM only for
typo: TLSv1.2
On Thu, Jul 25, 2019 at 12:14 AM Tibor Digana
wrote:
> I think a good compromise would be to introduce default value "TLS1.2" for
> "https.protocols" in the POM section "properties" which can be overridden
> in command line.
>
>
>
Just one remark from me:
I have got successful build with Surefire but it is strange because I
cannot explain why my change did it successful ;-) - pls help to explain it:
https://builds.apache.org/job/maven-box/job/maven-surefire/job/TLS1.2/
Before I did this in the configuration of "maven-invoke
Hi Robert,
Thx for hint. Perhaps you saw my branch.
That branch is only playground where I am testing our Jenkins.
Of course I will finish it as you have proposed with the configuration via
Jenkinsfile and system properties.
Additionally, the ITs have to use this system property too in their CLI
w
s to pass those properties,
> which are isolated.
>
> Robert
>
> On Thu, 25 Jul 2019 14:20:53 +0200, Tibor Digana
>
> wrote:
>
> > Just one remark from me:
> > I have got successful build with Surefire but it is strange because I
> > cannot explain why my change did
, ensure it starts with mvn -V to see
> the version output.
>
> thanks,
> Robert
>
>
> On Fri, 26 Jul 2019 16:41:58 +0200, Tibor Digana
>
> wrote:
>
> > Hi Robert,
> >
> > I have very similar issue in apache/maven-resolver on my PC.
> > I don't k
Hi devs,
Now we can archive any directories in plugin builds.
This feature was enabled in Jenkins library maven-jenkins-lib.
For instance, this is the Jenkinsfile script from apache/maven-archetype.
Here you can see how to archive the build result of all ITs from failed
builds for further analysi
env vars is strange because of JAVA_HOME, there are at least two.
One in CLI and second in env vars.
I think we should use latest `maven-shared-utils` and check the code in
shared utils. Maybe to fix shared utils and meanwhile use snapshot version,
maybe.
On Tue, Jul 16, 2019 at 11:22 PM
8u152 is very old. Why Infra team did not install 8u212, did they?
On Mon, Jul 29, 2019 at 4:31 PM Enrico Olivelli wrote:
> FYI from bui...@apache.org
>
> -- Forwarded message -
> Da: Chris Thistlethwaite
> Date: lun 29 lug 2019 alle ore 16:21
> Subject: JDK installations on Jen
+1
build success
On Sun, Jul 28, 2019 at 10:17 PM Michael Osipov wrote:
> Hi,
>
> We solved 14 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926&version=12342389
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jq
This debugging session has been hard, but I'm happy to say that it is now
> under control: no more wild guesses about strange root causes, but pure
> simple logic.
>
> Regards,
>
> Hervé
>
> Le dimanche 28 juillet 2019, 16:20:59 CEST Tibor Digana a écrit :
> > W
nt problem.
For more information see the Jira [2].
[1]: https://builds.apache.org/job/maven-box/job/maven/job/master/
[2]: https://issues.apache.org/jira/browse/MNG-6725
On Tue, Jul 30, 2019 at 9:40 AM Tibor Digana wrote:
> Essentially you want to say that global environment variable over
t, and this thread
> is
> not about it: I don't know why you're mixing everything and make simple
> things
> complex
>
> Regards,
>
> Hervé
>
> Le mardi 30 juillet 2019, 09:40:43 CEST Tibor Digana a écrit :
> > Essentially you want to say that global envir
Now the build is fully working.
The problem was with serializating "currentBuild" in the statement "def
changes = currentBuild?.changeSets".
On Fri, Aug 2, 2019 at 10:59 PM Robert Scholte wrote:
> Nope, it is not
>
> [Pipeline] echo
> WARNING: Could not determine JIRA issues:
> hudson.plugins.gi
Hi devs,
I hope you have spent a nice weekend ;-)
Integrated new Surefire feature [1] in the core-its branch [2] which fixed
the first issue (see point 1.) and the build is successful [3].
After making an analysis, with a help of the logs, we can see that there
are 3 known issues at least:
1. S
Hi all,
I have noticed several technical issues in core-its:
1. some tests are not listed in the IntegrationTestSuite.java.
I have already added two (MavenITmng5175WagonHttpTest,
MavenIT0146InstallerSnapshotNaming).
Some tests are broken, excluded from the execution and they are listed
in
+1
On Wed, Aug 7, 2019 at 9:13 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
t is actually the surefire
> project. To me it is insane to see 20 different builds that take between
> about 1h and 1.5h on a shared infrastructure, whereas ITs of Maven take
> less than 0.5h. So the biggest gain is not on Maven ITs.
>
> thanks,
> Robert
>
>
> On Sun, 11
where can can improve buildtime, and that is actually the surefire
> project. To me it is insane to see 20 different builds that take between
> about 1h and 1.5h on a shared infrastructure, whereas ITs of Maven take
> less than 0.5h. So the biggest gain is not on Maven ITs.
>
> thanks,
As Michael mentioned pending issue MNG-6716, I would like to mention
another Jira issues which are in my memory.
These (MRESOLVER-92, MNG-6731) are fixed and waiting for an approval.
Then I would like to cut a new release for the version 1.4.1 of MRESOLVER.
We made one step back from the version 1.
Hi,
We solved 1 issue:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12345950
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/i#issues/?jql=project+%3D+MRESOLVER+AND+status+%3D+Open+ORDER+BY+priority+DESC
Staging repo:
https://r
Here is mine +1.
On Thu, Aug 15, 2019 at 1:53 PM Tibor Digana wrote:
> Hi,
>
> We solved 1 issue:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12345950
>
> There are still a couple of issues left in JIRA:
>
> https://issue
The builds on a Jenkins node should be isolated. The paths of local
repository should be distinct. Therefore we used the trick with
EXECUTOR_NUMBER:
https://gitbox.apache.org/repos/asf?p=maven-jenkins-lib.git;a=blob;f=vars/asfMavenTlpPlgnBuild.groovy;h=e4576ac12e9dec73aee0540fa9aab37fd507d614;hb=H
Thx, the Vote has passed successfully.
On Sun, Aug 18, 2019 at 1:27 AM Olivier Lamy wrote:
> +1
>
> On Thu, 15 Aug 2019 at 21:53, Tibor Digana wrote:
>
> > Hi,
> >
> > We solved 1 issue:
> >
> >
> https://issues.apache.org/jira/secure/Release
Hi,
The vote has passed with the following result:
+1 : Tamás Cservenák, Tibor Digana, Michael Osipov, Sylwester Lachiewicz,
Olivier Lamy
0 : none
-1 : none.
PMC quorum: accomplished.
I will promote the artifacts to the central repo.
Kind regards
Tibor17
The Apache Maven team is pleased to announce the release of the Maven
Resolver 1.4.1.
https://maven.apache.org/resolver/
Release Notes - Maven Resolver - Version 1.4.1
** Task
* [MRESOLVER-92] - Revert MRESOLVER-7
Enjoy,
-The Apache Maven team
Hi,
There's a new branch MNG-6738 with new Resolver 1.4.1.
If you have no objections, I will push it to master.
https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=88b632cf3d727c7d003a8a36f1b39bffb2f790f3
The build is running
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6738/
Hi,
Just an announcement.
Today I would like to release Archetype 3.1.2.
https://issues.apache.org/jira/projects/ARCHETYPE/versions/12345957
Cheers
Tibor17
Hi,
We solved 9 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122&version=12345957
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARCHETYPE%20AND%20status%20%3D%20Open%20AND%20resolution%20%3D%20Unresolve
+1
On Mon, Aug 19, 2019 at 10:49 PM Tibor Digana
wrote:
> Hi,
>
> We solved 9 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122&version=12345957
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org
Hi,
Want to announce you about a new issue in the Resolver.
@Herve @Sylwester I found you in the history. Can you comment author's
changes?
https://github.com/apache/maven-resolver/pull/39
https://issues.apache.org/jira/browse/MRESOLVER-93
On Wed, Aug 14, 2019 at 5:23 PM Tibor Digana
ael Istria wrote:
> On Tue, Aug 20, 2019 at 9:01 PM Tibor Digana
> wrote:
>
> > Want to announce you about a new issue in the Resolver.
> > @Herve @Sylwester I found you in the history. Can you comment author's
> > changes?
>
>
> Is it a regression compar
You are providing us with really minimum information.
So what are you debugging, what version or snapshot?
How you debug it and what's your command or test you run and what platform,
etc.
It happens only while debugging?
Ideal issues would report a bug in Jira.
On Wed, Aug 21, 2019 at 4:45 AM 星光 <
s few weeks off the
> grid
> > > due to traveling). Let me try to push something soon (if it is not too
> > > late).
> > >
> > > On 2019/04/07 01:19:13, Tibor Digana wrote:
> > > > Hi Dejan,
> > > >
> > > > I almost fo
This Vote was initiated upon users requirement of bug fix.
Feel free to vote.
On Mon, Aug 19, 2019 at 10:49 PM Tibor Digana
wrote:
> Hi,
>
> We solved 9 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122&version=12345957
>
> There are
21, 2019 at 12:38 PM Dejan Stojadinovic
wrote:
> @Tibor please review https://github.com/apache/maven-surefire/pull/233
>
> On 2019/05/06 13:37:02, Tibor Digana wrote:
> > Hello Dejan, I am glad that you are back again.
> > yes, feel free. Github is yours.
> > T
> >
Thx Tamas and Olivier but I will keep the Vote open because we are still
only 3.
On Thu, Aug 22, 2019 at 4:39 PM Tamás Cservenák wrote:
> +1
>
> On Mon, Aug 19, 2019, 22:50 Tibor Digana wrote:
>
> > Hi,
> >
> > We solved 9 issues:
> >
> &g
Hi,
The vote has passed with the following result:
+1 : Tibor Digaňa, Olivier Lamy, Tamás Cservenák, Romain Manni-Bucau,
Sylwester Lachiewicz
0 : none
-1 : none.
PMC quorum: accomplished.
I will promote the artifacts to the central repo.
Cheers
Tibor17
Thx to all. The Vote is finished.
On Thu, Aug 22, 2019 at 9:17 PM Sylwester Lachiewicz
wrote:
> Looks and works well for me
> +1
>
> Sylwester
>
> czw., 22 sie 2019 o 20:32 Romain Manni-Bucau
> napisał(a):
>
> > +1 (non binding)
> >
> > Le jeu. 22 ao
The Apache Maven team is pleased to announce the release of the Apache
Maven Archetype Plugin, version 3.1.2.
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.
http
I don't know what Jira issue you are refferring to.
The ICL is used due to user's filtering and the multiple fork VMs.
On Fri, Aug 23, 2019 at 12:40 AM Martin Gainty wrote:
> CNFE when running surefire means
> Isolated (TEST) Classloader cannot load the dependency containing that
> class
> In yo
previous Tibor's
> answer.
>
> @Tibor: topic was changed do your mailbox didnt see the trick but thread is
> available at
> https://mail-archives.apache.org/mod_mbox/maven-dev/201908.mbox/browser
>
>
> Le ven. 23 août 2019 à 00:45, Tibor Digana a
> écrit :
>
>
Yeah Enrico, go for it. ;-)
Good luck!
T
On Fri, Aug 23, 2019 at 7:18 AM Enrico Olivelli wrote:
> Il gio 22 ago 2019, 23:42 Hervé BOUTEMY ha
> scritto:
>
> > We have 49 issues closed and nothing remaining open [1]
> >
> > Any objection to launch the release now?
> >
> > Any volunteer?
> >
>
>
There's very good BND plugin org.apache.felix:maven-bundle-plugin.
+1 to retire and delete old https://maven.apache.org/shared/maven-osgi/
Cheers
Tibor17
On Fri, Aug 23, 2019 at 3:17 PM Robert Scholte wrote:
> Hi,
>
> The Apache Maven project consist of about 90 (sub)projects. Due to the
> small
Hi Dirk,
This project is not worth a plugin, it is a pure converter of single class.
In this case it is legal to adopt this code according to the license.
Anyway the Maven is not the OSGi. The OSGi is not our key API we deliver to
our customers.
We have to save our energy on what makes Maven The M
build passed ok, sha512 matched
+1
On Fri, Aug 23, 2019 at 9:33 PM Michael Osipov wrote:
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821&version=12344828
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org
org.apache.maven.it
> .MavenITmng6386BaseUriPropertyTest.testitMNG6386UnicodeChars(MavenITmng6386BaseUriPropertyTest.java:90)
> >
> >
> >
> > Enrico
> >
> > Il giorno ven 23 ago 2019 alle ore 09:49 Tibor Digana <
> > tibordig...@apache.org> ha scri
that's bad. We were too fast :-)
Although my build passed but in this case as I saw the commit I have to
give my -1, sorry!
On Sat, Aug 24, 2019 at 9:41 PM Gabriel Belingueres
wrote:
> Hi:
>
> Regarding MPIR-375, I noted that the merge of the PR into master branch
> was done *before* I made chan
gt;
>
>
>
>
> *BUT* if I configure the plugin in BOTH the pluginManagement and reporting
> section, then it fails again.
> Sounds to me like some plugin resolution condition that causes the
> pluginManagementExcludes list parameter to not be set
The build is currently running and the 'deploy' is performed at the end.
https://builds.apache.org/job/maven-box/job/maven-surefire/job/master/53/
We have to wait few hours because the Jenkins queue is full.
On Sun, Aug 25, 2019 at 9:03 AM Dan Tran wrote:
> @Tibor Digana I
Michael, this is true but the second problem is a missed commit? Where is
the commit? It is not in the PR.
Gabriel, the log file was not attached.
And the third problem is an exception which we could not see because the
log is not in the attachements.
On Sun, Aug 25, 2019 at 5:14 PM Michael Osipov
I was waiting this this issue. Now it is clear for me too.
So we are missing this commit, right? It's worth to complete the PR#7 and
restart the vote.
Gabriel, why the exception with plugin version 3.0.1 appears on your box?
T
On Mon, Aug 26, 2019 at 2:49 PM Gabriel Belingueres
wrote:
> Created
I am currently preparing Surefire PR#240 (SUREFIRE-1658) for Enrico because
he comes back from vacations on Wednesday and he will perform review.
In your PR, Tomo, I planned to "play" with your code in my own IDE on my
PC. But I am not glad when I ask my ASF colleagues and they do not reply
except
+1, sha512 ok, build ok, found error - see the extra email.
On Wed, Aug 28, 2019 at 9:18 PM Enrico Olivelli wrote:
> Hi,
>
> We have solved 52 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12345234
>
> There are issues left in JIRA for Maven core:
I used Maven 3.6.2 in the IntelliJ IDEA 2019.2.1 and I found these errors
in the log file:
~/.IntelliJIdea2019.2/system/log/idea.log
2019-08-28 21:31:32,072 [255937677] ERROR - #org.jetbrains.idea.maven
- com.google.inject.CreationException: Unable to create injector, see the
following error
6852351&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16852351
>
> I reported to Jetbrains https://youtrack.jetbrains.com/issue/IDEA-215315 <
> https://youtrack.jetbrains.com/issue/IDEA-215315> and is supposed to be
> fixed in 2019.3
>
> > On
PM Enrico Olivelli
> wrote:
>
>> It may be due to any change regarding jsr 330 like
>> https://issues.apache.org/jira/plugins/servlet/mobile#issue/MNG-6686
>>
>>
>> I think it is an issue for Idea and not for us.
>> It would be good to have some developer
into
>> this.
>> > Is there any new way to replace maven components?
>> >
>> > On Wed, Aug 28, 2019 at 11:57 PM Enrico Olivelli
>> > wrote:
>> >
>> > > It may be due to any change regarding jsr 330 like
>> > > htt
dn't dig well into
>> this.
>> > Is there any new way to replace maven components?
>> >
>> > On Wed, Aug 28, 2019 at 11:57 PM Enrico Olivelli
>> > wrote:
>> >
>> > > It may be due to any change regarding jsr 330 l
We should use authors of the issue/PR/idea.
After the release we can ask WHY (practical goals) he wanted the feature
more than how. The question for "HOW" has to be placed very early during
the review, but too late after the PR has been merged.
I expect that the reviewer developer has checked all t
ppreciate their help on this release.
>
> Robert
>
>
> On Sat, 31 Aug 2019 08:33:15 +0200, Tibor Digana
>
> wrote:
>
> > We should use authors of the issue/PR/idea.
> > After the release we can ask WHY (practical goals) he wanted the feature
> > more than ho
sure at 100% it is something that should stay
> forever on the website, maybe it can be in the announcement email.
>
> I have used the release notes of 3.6.1 as template, to me it is not a
> problem to shrink the list making some sort of select
> 'distict(reportername)',
ck of text needs to add value and it
> > should be compact, though easy to read/overview. Compressing reporters
> > and
> > contributors to a list (or comma separated line) makes sense to me.
> >
> > Robert
> >
> > >
> > > I have to close th
In theory, the incremental compiler would make it faster.
But this can be told only if you present a demo project with has trivial
tests taking much less time to complete than the compiler.
In reality the tests in huge projects take significantly longer time than
the compiler.
Some developers say
t to replace default logic
> (surefire is a good example where it must be refined and it can save hours
> there ;))
> 4. Let's try to impl it as a mvn extension first then if it works well on
> multiple big project get it to core?
>
> Romain
>
>
>
> Le ven. 13 sep
rst then if it works well on
> > multiple big project get it to core?
>
> Did anyone Google for "maven extension build cache"? There are already
> commercial solutions for it.
> Even though I would like to see improvements in this area, the old
> architecture of Maven make
cau
wrote:
> Tibor, maven is the only one with the logic to give any cache the data it
> needs. Jenkins alone can't since it does not own the reactor nor plugin I/O
> values.
>
> Le sam. 14 sept. 2019 à 12:45, Tibor Digana a
> écrit :
>
> > But I do not understand w
compared to
> Maven. For their build cache extension they had to analyze the plugin
> descriptors, marking all parameters as either input or output. And that
> boosts the builds with their extension.
>
> thanks,
> Robert
>
>
> On Sat, 14 Sep 2019 13:37:40 +0200, Tibor Digana
>
Alexander,
Enrico is really right. Today it is Microservices and there every
microservice is in a separate SCM repo.
It was just only an example with Microservices but in my experiences you
can always find the lower bound modules in the hierary which do not change
so much and segragate them in ano
e SCM we will need to hire a team of release
> managers and build engineers to coordinate and support this.
>
> Again, we are don’t selling our approach. We implemented the missing for
> us feature.
>
> PS. Just thing why commercial products like Gradle Maven Extensions
> app
the topic we are interested in.
>
> Thank you
> Aleks
>
> On 2019/09/14 20:37:03, Tibor Digana wrote:
> > Hello Maximilian,
> >
> > So now the next step is to break the traditional dependencies in Maven
> and
> > isolate the services via web-services, e.g.
I was the person who talked with Robert and Herve about incremental build
in ASF Conference Budapest in 2015.
I had an idea with a Java agent and optimize the test-set in Surefire but
we all understood that a generic solution is not possible with full
guarantees for all users which may finally brea
Hello guys,
For the user community these two issues are important:
https://issues.apache.org/jira/browse/MNG-6169
https://issues.apache.org/jira/browse/MNG-6548
The Tycho project is the user as well.
The J8 is internal code improvement/change => lower priority than the
user's priority => release o
Can somebody explain a realistic USE CASE when you trigger two consequent
builds (with no changes in sources) and that you expect identical MD5 of
the build artifacts (JAR)?
This can be achieved only when the "timeStamp" in properties is fixed
unmodified in POM.
Does it make sense to call it timeSt
yes Hunter, exactly this was one possibility.
The names of the property can be just like in the HTTP Headers:
Last-Modified
If-Modified-Since -> maybe here can be also the commit hash, not only time
in millis/UTC
ETag
and every module may have different value ;-) then. and then the SCM... has
to r
ed 3.7.0 candidates.
>
> As said, the Java 8 update is not just about internal code improvements
> or
> changes. Maven will expose new APIs/SPIs that contain Java 8 Functions,
> so
> it must be seen as a requirement to implement the experimental
> buildconsumer feature.
>
ven-plugin
1.8.0
modernizer
verify
modernizer
1.8
org.gaul
modernizer-maven-annotations
1.8.0
On Mon, Sep 30, 2019 at 9:04 PM Enrico Olivelli wrote:
> Tibor
>
> Il lun 30 set 2019, 20:30 Tibor Digana ha
> scritto:
>
> > Robert, yo
This is not very serious discussion since we saw users on our mailing list
who said that he is using Java 1.6 compiler and JDK7 in Maven.
Serious discussion would uncover pros/cons and impact analysis.
I would have a problem with Java 1.8 in target and source code but I have
problem that we exclud
Sorry my important typo " I would have a problem with Java 1.8 ".
Correction " I would NOT have a problem with Java 1.8 "
On Thu, Oct 3, 2019 at 5:03 PM Tibor Digana wrote:
> This is not very serious discussion since we saw users on our mailing list
> who said that he
Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> On Thu, 3 Oct 2019 at 16:49, Karl Heinz Marbaise
> wrote:
>
> > Hi,
> >
> > On 03.10.19 17:03, Tibor Digana wrote:
> > > This is not very serious discussion since we saw users on our mailing
>
i-Bucau
wrote:
> Le jeu. 3 oct. 2019 à 20:22, Tibor Digana a
> écrit :
>
> > The topic related to TLS is only related to runtime, means JDK, which is
> > under the control of the particular user or CI.
> > I guess the user can easily find the answer:
> >
> >
&
It would be worth to add a new goal called "release" to the
maven-release-plugin which merges "prepare" and "perform".
We developers in companies use both goals prepare and perform immediately
together because for us two goals do not make sense.
Two goals make sense for those who can wait days to s
| Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
>
t; run both at once typically) but I disagree with last parts "skip the
> > test"
> > > - maven is also there to enforce tests as a good practise, if you don't
> > > automatically test it you can configure maven to skip tests for the
> > release
> >
201 - 300 of 1362 matches
Mail list logo
