Hi,
I will take care of it next week.
Please help to review / close / merge existing PR.
wt., 7 lut 2023 o 09:22 napisał(a):
> Hi!
>
>
> The latest release of Maven Wrapper was in May 2022. There has been some
> fixes and features since then (see:
>
Hi,
The following command can deploy and then increment verion number,
but how toincrement verion number and then deploy?
mvn build-helper:parse-version versions:update-versions
Oh right, I thought he was going to fix something in surefire
There's also https://maven.apache.org/guides/mini/guide-attached-tests.html
-
- org.apache.maven.plugins
- maven-surefire-plugin
- ${surefire.version}
-
-
-
I agree that the current syntax for adding to stuff to test runtime is
clunky and I wouldn't personally use it unless I needed to.
On Thu, Feb 16, 2023 at 1:07 PM Alexander Kriegisch
wrote:
>
> Which is exactly why I was asking. I want to learn about real-world use
> cases which would require
Which is exactly why I was asking. I want to learn about real-world use
cases which would require such a thing, not be just nice to have.
Over-engineering POMs does not make them more readable or maintainable.
Alexander Kriegisch
https://scrum-master.de
Mikael Åsberg schrieb am 16.02.2023 um
I use runtime scope a lot, but personally can't recall having needed
the equivalent of a test-runtime scope myself (or, more likely, I
could get away with test compile scope even though the dependency was
only needed at test runtime). But just because I haven't needed it
doesn't mean there are no
For a test, does it really matter to make the dependency test-scoped?
Mikael Åsberg schrieb am 16.02.2023 um 12:35:
> Because there exists runtime, but no test only runtime scope
>
> On Thu, Feb 16, 2023 at 12:22 PM Alexander Kriegisch
> wrote:
>>
>> I would be more interested first in why this
Because there exists runtime, but no test only runtime scope
On Thu, Feb 16, 2023 at 12:22 PM Alexander Kriegisch
wrote:
>
> I would be more interested first in why this should be necessary at all.
> What is the use case that would not be covered by declaring a regular
> test-scoped dependency
I would be more interested first in why this should be necessary at all.
What is the use case that would not be covered by declaring a regular
test-scoped dependency in the module?
--
Alexander Kriegisch
https://scrum-master.de
Olivier Lamy schrieb am 16.02.2023 um 11:58:
> On Thu, 16 Feb 2023
On Thu, 16 Feb 2023 at 20:52, Olivier Lamy wrote:
>
> On Thu, 16 Feb 2023 at 20:07, Delany wrote:
> >
> > Hi Stephane,
> >
> > You can do like this
> >
> >
> > maven-surefire-plugin
> > 3.0.0-M9
> >
> >
> > org.apache.commons
> >
On Thu, 16 Feb 2023 at 20:07, Delany wrote:
>
> Hi Stephane,
>
> You can do like this
>
>
> maven-surefire-plugin
> 3.0.0-M9
>
>
> org.apache.commons
> commons-email
> 1.5
>
>
>
Hi Stephane,
You can do like this
maven-surefire-plugin
3.0.0-M9
org.apache.commons
commons-email
1.5
On Thu, 16 Feb 2023 at 11:25, Stephane Passignat
wrote:
>
Hello,
Is it possible to add a maven artifact as an additionalClasspathElement ?
I tried this syntax, inspired by the exclusion mechanism, but it's not
working.
org.apache.maven.plugins
maven-surefire-plugin
3.0.0-M9
13 matches
Mail list logo