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.
I added Karl, Herve and Stephen in CC because we talked about this issue in
ASF CON
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
On Tue, 29 Oct 2019 at 22:16, Romain Manni-Bucau
wrote:
> Le mar. 29 oct. 2019 à 22:58, Karl Heinz Marbaise a
> écrit :
>
> > Hi Romain,
> >
> > On 29.10.19 22:40, Romain Manni-Bucau wrote:
> > > Hi Karl
> > >
> > > Not sure id do a MavenIT annotation - test is enough probably - but i
> > >
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
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
well, you have use different JVMs if you expect different env vars.
On Wed, Oct 30, 2019 at 3:23 PM Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> On Tue, 29 Oct 2019 at 22:16, Romain Manni-Bucau
> wrote:
>
> > Le mar. 29 oct. 2019 à 22:58, Karl Heinz Marbaise a
> > écrit :
> >
>
I don't want your dependencies of course because it is user specific issue.
I only want to trigger "mvn clean install" or deploy and this will fetch
the plugins, not the dependencies from a dummy empty pom. (don't mean
user's pom). Finally, the user will have plugins in the image which come
from
My script is for my cases. I'm just saying it's not rocket science, others
are doing it already
On Wed, 30 Oct 2019 at 13:31, Tibor Digana wrote:
> 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
>
Good point so guess it can be combined with a config (more a system
properties) to run in memory or forked and therefore the fs can be either
in mem or just populated from the spec (annotations).
Was looking to get something more fluent on the full setup than matching
multiple resources which is -
Karl, where you define CLI command in each test?
Regarding the f/w you have selected. If I had to decide between JUnit5 or
Groovy/Spock, I would decide for Spock.
On Tue, Oct 29, 2019 at 9:47 PM Karl Heinz Marbaise
wrote:
> Hi to all,
>
> I've invested some time to get a thing working in a
+1
Kind regards
Gabriel
El mar., 29 de octubre de 2019 17:11, Karl Heinz Marbaise
escribió:
> Hi to all,
>
> based on the discusion this is the formal VOTE to lift the minimum of
> Maven Core with version 3.7.0 to JDK 8 minimum.
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
Hi Mike,
But I definitely need to re-do the documentation.
http://plc4x.apache.org/developers/code-gen/protocol/mspec.html
I had started writing it before I did a big extension and refactoring …
I really hope I finally will get the chance to work on this again very soon.
Chris
Von: "Beckerle,
Not sure I understand it well Tibor, do you encourage to multiply the
number of potential solutions to request more time to contributor to see
how to do things?
Don't think it is good, a single simple solution sounds more promising -
once again from my past experience.
Once again Tibor, all I'm
Romain, I am glad that you are with me.
Attracting the contributors!
I hope we all voted for Java 8 sources in Maven Core.
And Spock is the same story.
Java is the like C++ old style.
Lambda makes this language more moderns a bit.
Regarding issues with Java 14, all can be fixed, just give the
Romain, the Java has not made any significant progress in language after
Java 9. Yes, some JVM features in J13 were really great but not in language.
All fixes about switch-case in several versions, strings, preliminary
feature. Nothing very progressive for developers! And I think the frequent
Hi,
On 30.10.19 15:23, Stephen Connolly wrote:
On Tue, 29 Oct 2019 at 22:16, Romain Manni-Bucau
wrote:
Le mar. 29 oct. 2019 à 22:58, Karl Heinz Marbaise a
écrit :
Hi Romain,
On 29.10.19 22:40, Romain Manni-Bucau wrote:
Hi Karl
Not sure id do a MavenIT annotation - test is enough
@Tibor: do you agree we write the tests with chai (js)? It is the same to
use groovy for a java dev today since java caught up its lateness. Not
stacking layers and avoiding useless abstractions is the best way to enable
people to contribute from my experience. As soon as you add a layer which
has
+1
On Wed, Oct 30, 2019 at 6:10 PM Gabriel Belingueres
wrote:
> +1
>
> Kind regards
> Gabriel
>
> El mar., 29 de octubre de 2019 17:11, Karl Heinz Marbaise <
> khmarba...@gmx.de>
> escribió:
>
> > Hi to all,
> >
> > based on the discusion this is the formal VOTE to lift the minimum of
> > Maven
@Tibor: one goal we should focus on on any new feature is to enable us to
attract more new contributors, spock has the disadvantage to not be
mainstream at all + to be on groovy which has some issues to support recent
java version so it will not help it to be more adopted, therefore I guess
+1
/Anders (mobile)
Den tis 29 okt. 2019 20:11Karl Heinz Marbaise skrev:
> Hi to all,
>
> based on the discusion this is the formal VOTE to lift the minimum of
> Maven Core with version 3.7.0 to JDK 8 minimum.
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
> Kind regards
Stephen, this is clear to me but we need to move ahead a bit.
Should I start the vote that we will have new project (
github.com/apache/maven-docker) for these purposes?
Or should we talk to Carloss and ask him if he would be fine with deploying
these images in DockerHub?
On Wed, Oct 30, 2019 at
Integration test choices include the excellent Spock as mentioned. I've
used it and it's very solid. Two more choices include:
Another choice is Cuppa - https://github.com/cuppa-framework/cuppa
I've used this too, and it's great - no right-click-run-this-one in
Intellij though. I wish it had more
Oops. Blog entry linking to video of 16s build -
https://paulhammant.com/2017/02/05/a-16-second-java-webapp-build-including-webdriver-tests/
Le samedi 26 octobre 2019, 23:56:37 CET Enrico Olivelli a écrit :
> Hello,
> as Vladimir reported in [1] we have problems of our binary distributions.
>
> Short version of the story:
> - we are missing some entries in LICENSE, in my opinion we should cite
> every other ASLv2 licenced project that
What is the usage of this first group outside demos (it is trivial to build
a dedicated image for demos so i drop it from any asf work for now)?
Le mer. 30 oct. 2019 à 23:18, Tibor Digana a
écrit :
> Romain, of course we know this but there are two groups of users.
> First those who use the
+1!!!
Dan
> On Oct 29, 2019, at 4:11 PM, Karl Heinz Marbaise wrote:
>
> Hi to all,
>
> based on the discusion this is the formal VOTE to lift the minimum of
> Maven Core with version 3.7.0 to JDK 8 minimum.
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
> Kind
Karl
(Sorry for top posting)
Thank you very much for moving this forward.
In my personal experience one real blocker in contributions to Maven,
expecially plugins, is to write integration tests.
So having a nice way to create tests is very welcome.
Having a way to run tests as simple unit tests
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
>
sure :)
Le mardi 29 octobre 2019, 23:16:05 CET Karl Heinz Marbaise a écrit :
> Hi Hervé,
>
> I think you meant: "[VOTE] Release Apache Maven Source Plugin Version
> 3.2.0" didn't you ?
>
> Kind regards
> Karl Heinz Marbaise
>
> On 29.10.19 22:55, Hervé BOUTEMY wrote:
> > Hi,
> >
> > We
Romain, of course we know this but there are two groups of users.
First those who use the Maven in docker without CI.
And second of those who integrate the docker container with the CI and they
use the volumes.
The first group of people may freely use the image we are discussing here
because this
Hi,
let me conclude some of the things together:
The decision which I have made against Spock was based on several
reasons:
* People often tend to write Java code (which is valid), cause
they don't know Groovy or don't want to learn a new language
just to write tests.
This means in
Ci servers have all cache so it is useless to make the docker pull slow
with useless versions to then download or not plugins IMHO.
Le mer. 30 oct. 2019 à 22:47, Hervé Boutemy a écrit :
> Le mercredi 30 octobre 2019 14:55:46 CET, vous avez écrit :
> > Agree we should publish with an asf account
+1
On Wed, 30 Oct 2019 at 7:44 am, 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/
>
>
+1 (non binding)
Le jeu. 31 oct. 2019 à 05:05, Olivier Lamy a écrit :
> +1
>
> On Wed, 30 Oct 2019 at 7:44 am, Hervé BOUTEMY
> wrote:
>
> > Hi,
> >
> > We solved 2 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924&=12345522=Text
> >
> > Staging repo:
>
34 matches
Mail list logo
