Re: Next Generation Integration Testing for Plugins/Core

[Tibor Digana]

am, programming language is our toy ;-)
everybody has some preferences, so i respect them and i understand that
even the Lambda would be a big jump for us nevertheless the Groovy or
Kotlin.
i saw the parameterized tests, re-runs in Groovy, log result of assertion
statements, and I spoke with Benedikt and we agreed that Spock is very
special and we like it.
i do not want to push Karl. Maybe one advice is to think about the
programming approach where these annotations and code would be easily used
in another languages too.
that's basically all from my side.

Enjoy!


On Thu, Oct 31, 2019 at 11:56 PM Vladimir Sitnikov <
sitnikov.vladi...@gmail.com> wrote:

> Karl>on the language features but since JDK8 I don't see any advantage
>
> What about Kotlin?
>
> There are nice things there: the language is statically compiled, great
> Java interop, there are extension functions, multiline strings, helpful
> standard library, default parameters.
> Kotlin is great for creating DSLs.
>
> It can be used with JUnit or other frameworks (e.g.
> https://github.com/kotlintest/kotlintest )
>
> Vladimir
>

Re: Next Generation Integration Testing for Plugins/Core

[Vladimir Sitnikov]

Karl>on the language features but since JDK8 I don't see any advantage

What about Kotlin?

There are nice things there: the language is statically compiled, great
Java interop, there are extension functions, multiline strings, helpful
standard library, default parameters.
Kotlin is great for creating DSLs.

It can be used with JUnit or other frameworks (e.g.
https://github.com/kotlintest/kotlintest )

Vladimir

Re: [VOTE] Release Apache Maven Source Plugin version 3.2.0

[Sylwester Lachiewicz]

+1

czw., 31 paź 2019, 18:43 użytkownik Karl Heinz Marbaise 
napisał:

> Hi Hervé,
>
> tested and +1 from me
>
> Kind regards
> Karl Heinz Marbaise
>
> On 29.10.19 22:44, Hervé BOUTEMY wrote:
> > Hi,
> >
> > We solved 2 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924&=12345522=Text
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1532/
> >
> https://repository.apache.org/content/repositories/maven-1532/org/apache/maven/plugins/maven-source-plugin/3.2.0/maven-source-plugin-3.2.0-source-release.zip
> >
> > Source release checksum(s):
> > maven-source-plugin-3.2.0-source-release.zip sha512:
> 2321599d28affd25b2821a14182383a1a3a31bb33344fae395805d3173e9cdcfd2b1c09608e73a160f054f9086ad56f2b11f4fe56117fddb34356d1b8e935780
> >
> > Staging site:
> > https://maven.apache.org/plugins-archives/maven-source-plugin-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for at least 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven Source Plugin version 3.2.0

[Karl Heinz Marbaise]

Hi Hervé,

tested and +1 from me

Kind regards
Karl Heinz Marbaise

On 29.10.19 22:44, Hervé BOUTEMY wrote:

Hi,

We solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924&=12345522=Text

Staging repo:
https://repository.apache.org/content/repositories/maven-1532/
https://repository.apache.org/content/repositories/maven-1532/org/apache/maven/plugins/maven-source-plugin/3.2.0/maven-source-plugin-3.2.0-source-release.zip

Source release checksum(s):
maven-source-plugin-3.2.0-source-release.zip sha512: 
2321599d28affd25b2821a14182383a1a3a31bb33344fae395805d3173e9cdcfd2b1c09608e73a160f054f9086ad56f2b11f4fe56117fddb34356d1b8e935780

Staging site:
https://maven.apache.org/plugins-archives/maven-source-plugin-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven JAR Plugin version Y.Z

[Karl Heinz Marbaise]

Hi Hervé,

tested with serveral maven versions etc.

Just fine.

So +1 from me.

Kind regards
Karl Heinz Marbaise
On 29.10.19 22:55, Hervé BOUTEMY wrote:

Hi,

We solved 1 issue:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12345503=Text

Staging repo:
https://repository.apache.org/content/repositories/maven-1533/
https://repository.apache.org/content/repositories/maven-1533/org/apache/maven/plugins/maven-jar-plugin/3.2.0/maven-jar-plugin-3.2.0-source-release.zip

Source release checksum(s):
maven-jar-plugin-3.2.0-source-release.zip sha512: 
b84da749dd6ca3a58173ad060a7406bee48ea02d78bc638fcc404c1c31c7c466d5d33890ab549a4edd99efcfebb8926a7955d647a398968c2b1c44393a3bef43

Staging site:
https://maven.apache.org/plugins-archives/maven-jar-plugin-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: last review of Reproducible Builds proposal

[Christofer Dutz]

Hi all,

as I can see you're voting on releasing the reproducible build extended plugin 
versions.
Is there any documentation on how to use this new feature? 

I had a look at the confluence page, but that seemed like a brainstorming 
session.

I would love to add this to the PLC4X build asap. 
So I would like to test the release-candidates and vote too.

Chris



Am 16.10.19, 14:42 schrieb "Hervé BOUTEMY" :

Le mercredi 16 octobre 2019, 13:40:48 CEST Andreas Sewe a écrit :
> Emmanuel Bourg wrote:
> > Le 16/10/2019 à 08:35, Hervé BOUTEMY a écrit :
> >> last question: now that we seem to fully understand each other, does it
> >> mean that you don't need any more "seconds since the epoch" format
> >> support for the property?
> > 
> > If Maven supports the SOURCE_DATE_EPOCH environment variable I don't
> > think that's necessary, otherwise it would be nice to be able to invoke
> > 
> > Maven with:
> >mvn package -Dproject.build.outputTimestamp=$SOURCE_DATE_EPOCH
> > 
> > and this means supporting a timestamp formatted as seconds since the
> > epoch.
> 
> +1
> 
> The above would be a nice, simple way of bridging the gap between
> SOURCE_DATE_EPOCH and project.build.outputTimestamp.
told like that, ok, why not

> 
> If it is not too much trouble to implement the "\d+ -> seconds since
> epoch" heuristic, them I would love to see it included.
ok, I'll do and prepare the release

Regards,

Hervé

> 
> Best wishes,
> 
> Andreas





-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Docker image with initialized local cache saves 50 seconds in startup

[Tibor Digana]

Thx Herve for the hint. The size of the local cahe is 40 MB.

All core plugins [1] and Packaging (ear, ejb, jar, rar and war) are
included in the range [3.0, 4.0).
Two plugins (verifier:2.0+ and rar:1.0+) do not have this range.

[1] https://maven.apache.org/plugins/


On Wed, Oct 30, 2019 at 10:47 PM Hervé Boutemy  wrote:

> Le mercredi 30 octobre 2019 14:55:46 CET, vous avez écrit :
> > Agree we should publish with an asf account and make it part of the
> release
> > process.
> > That said I still fail to see how you can add a relevant cache. Maybe
> take
> > the time to review plugin version in a few asf projects (let say
> > maven-surefire, geronimo-openapi and spark) and check out if it works to
> > cache anything.
> if we choose one precise version of each plugin, we will never get the
> version
> used by a project: IMHO, we need to choose a range for each plugin
> https://maven.apache.org/plugins/
> Something like dependency:resolve-plugins should be able to do the job.
>
> With a range per plugin, I'd love to see the size of the initial local
> repository
> At least, using such an image would require minimal efforts from users,
> particularly on CI servers
>
> Regards,
>
> Hervé
>
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Old Blog
> >  | Github <
> https://github.com/rmannibucau>
> > | LinkedIn  | Book
> > <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > >
> >
> >
> > Le mer. 30 oct. 2019 à 14:31, Tibor Digana  a
> >
> > écrit :
> > > Stephen, yeah something like you do in your scrip but it must not be a
> > > personal owner. Even Carloss is person who makes this deployment to
> > > DockerHub but his images are used by the entire world and we should
> decide
> > > whether we would agree with him to have such images under his
> > > responsibility or our responsibility as the Apache group. Then the
> script
> > > would be official and we can cut the release of Maven and the Docker
> image
> > > will be ready for the downloads together with the Maven distribution.
> So
> > > the users will always know that it is consistent deployment and they
> > > wouldn't expect that the image is missing for the new version.
> > >
> > > So here we should decide on who will be the deployer of these images
> with
> > > the cache. And the technical solution is smaller problem I would say.
> > >
> > > On Wed, Oct 30, 2019 at 10:28 AM Stephen Connolly <
> > >
> > > stephen.alan.conno...@gmail.com> wrote:
> > > > On Wed 30 Oct 2019 at 08:21, Tibor Digana 
> > >
> > > wrote:
> > > > > It's the situation when you have maven plugins in repo and it means
> > >
> > > that
> > >
> > > > > all custom plugins/deps can be still downloaded as before.
> > > > > Nothing exists like this in the world and we are talking about the
> > > > > approaches.
> > > >
> > > > Cough cough cough
> > >
> > >
> https://github.com/stephenc/docker-git-java8-maven-vim/blob/168b9968deae41
> > > 8ca3fd63c63038e896255c6fe8/Dockerfile#L50>
> > > > There are issues, but it does shave a bit of time... though we end up
> > > > adding our common dependencies into the seed pom so that it is an
> > >
> > > effective
> > >
> > > > speed up
> > > >
> > > > > I added Karl, Herve and Stephen in CC because we talked about this
> > >
> > > issue
> > >
> > > > > in ASF CON and Twitter.
> > > > >
> > > > > On Wed, Oct 30, 2019 at 6:36 AM Romain Manni-Bucau <
> > > >
> > > > rmannibu...@gmail.com>
> > > >
> > > > > wrote:
> > > > >> Hi Tibor,
> > > > >>
> > > > >> It has two issues:
> > > > >>
> > > > >> 1. It will not be the right plugin versions in 90% of the cases
> > >
> > > (except
> > >
> > > > >> demo ;))
> > > > >> 2. It will miss all custom plugins
> > > > >>
> > > > >> Now question is: what happens if you mount your local repo when
> > >
> > > running
> > >
> > > > >> docker? It works as expected. Means we could use a custom
> entrypoint
> > > > >> printing a warning banner if it is not done probably instead of
> > > >
> > > > incrasing
> > > >
> > > > >> the image size without being sure to reach the original goal.
> > > > >>
> > > > >> Wdyt?
> > > > >>
> > > > >> Romain
> > > > >>
> > > > >> Le mer. 30 oct. 2019 à 02:03, Tibor Digana <
> tibordig...@apache.org> a
> > > > >>
> > > > >> écrit :
> > > > >> > If you use Docker images with Maven with no mapping of cache to
> the
> > > > >> > volumes, you may notice that Maven downloads the plugins for the
> > >
> > > build
> > >
> > > > >> > lifecycle.
> > > > >> >
> > > > >> > This slows down the build because a lot of artifacts and plugins
> > > > >> > are
> > > > >> > initially downloaded.
> > > > >> > This takes 50 seconds which might be even longer than the
> > > > >> > productive
> > > > >>
> > > > >> build
> > > > >>
> > > > >> > itself (compiler, package, ...).
> > > > >> >
> > > > >> > We discussed this topic 

Re: [VOTE] Release Apache Maven JAR Plugin version Y.Z

[Olivier Lamy]

+1

On Wed, 30 Oct 2019 at 08:06, Hervé BOUTEMY  wrote:

> Hi,
>
> We solved 1 issue:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12345503=Text
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1533/
>
> https://repository.apache.org/content/repositories/maven-1533/org/apache/maven/plugins/maven-jar-plugin/3.2.0/maven-jar-plugin-3.2.0-source-release.zip
>
> Source release checksum(s):
> maven-jar-plugin-3.2.0-source-release.zip sha512:
> b84da749dd6ca3a58173ad060a7406bee48ea02d78bc638fcc404c1c31c7c466d5d33890ab549a4edd99efcfebb8926a7955d647a398968c2b1c44393a3bef43
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-jar-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy