Hello Tibor,
Tibor Digana schrieb am Sa., 27. Aug. 2016 um
22:48 Uhr:
> The JUnit5 team create junit5-provider which might be nice to have a
> look inside. I don't know if this provider has all features Surefire
> provided through surefire-junit47-provider, I know for certain that
> junit5-provi
Am 08/24/16 um 09:22 schrieb Stephen Connolly:
> I think we probably need to rethink version ranges. What I'd like is to let
> the consumer Pom treat version ranges more as guidance rather than hard
> requirements. It's a pain if you depend transitiveky on Foo:[1.0] but need
> Foo:[1.0.1,1.1) for t
Last week, I communicated my thoughts on why POM model 4.1.0 should not be
introduced in the 3.x series. I said that I believed that forcing two
separate lines of development would best be beneficial to the overall code
base (which is big!!!). The benefit, so I think, is that 3.x would focus on
gra
Am 08/24/16 um 08:15 schrieb Hervé BOUTEMY:
> Le mercredi 24 août 2016 00:45:28 Christian Schulte a écrit :
>> Am 08/24/16 um 00:40 schrieb Christian Schulte:
>>> Am 08/23/16 um 22:33 schrieb Hervé BOUTEMY:
yes, people providing libraries have this big choice to do: when to
upgrade
m
feedback consolidated in http://svn.apache.org/r1758149
Here is the plan now:
http://maven.apache.org/aether-archives/aether.html
Any more changes before I implement it?
Regards,
Hervé
Le vendredi 26 août 2016 20:45:53 Igor Fedorenko a écrit :
> On Fri, Aug 26, 2016, at 12:51 AM, Michael Osip
We should probably add repository info too.
Right now dependencies are searched in every repository if it is not
found. Not very efficient if you now where it should look.
I still like this related
article:"http://blog.sonatype.com/2012/02/public-service-announcement-your-build-is-leaking-and-
yes, we'll need to find clear terms for each concept: I now understand what
you meant by consumer pom, which is not what I meant :)
there are 2 ideas:
- publishing classical Maven pom without build information (pom generated by
flatten plugin or alike), to be able to add new build features in
+1
Le dimanche 28 août 2016 12:57:52 Robert Scholte a écrit :
> Hi Tibor,
>
> There's no need to hurry to for Maven-4.0.0 just because of the
> modelVersion. Maven2 was already using it, we may assume that users
> already know about this.
> I'd really prefer to stay on 3.x and go to 5.x once we'v
Hi Tibor,
There's no need to hurry to for Maven-4.0.0 just because of the
modelVersion. Maven2 was already using it, we may assume that users
already know about this.
I'd really prefer to stay on 3.x and go to 5.x once we've extended the
model to version 5.0.0. (I don't mind skipping 4.x if
The Apache Maven team is pleased to announce the release of the
Apache Maven WAR Plugin, version 3.0.0.
The WAR Plugin is responsible for collecting all artifact dependencies, classes
and resources of the web application and packaging them into a web application
archive.
http://maven.apache.org/
@Jason
@all
Can you tell me why we want to release Maven 3.4.0 and not Maven 4.0.0?
I guess Maven 4.0.x may finalize Model Version 4.0.0 era.
Do you have other plans with Maven 4.x?
Back to modelVersion and consumer POM. The consumer pom is a subset of
normal POM. Keep using consumer POM with curr
Hi,
here is my +1.
Kind regards
On 24/08/16 21:11, Karl Heinz Marbaise wrote:
Hi,
We solved 33 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121&version=12331760
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=projec
Hi,
The vote has passed with the following result:
+1 : Tibor Digana, Hervé Boutemy, Olivier Lamy, Karl Heinz Marbaise
PMC quorum: reached
I will promote the artifacts to the central repo.
Kind regards
Karl Heinz Marbaise
-
Hi Robert, as I am reading your comments, I see the situation is not
be so tragic :)
What about to let m-deploy-p and m-release-p to decide on modelVersion
of consumer project as the minimum version. If for instance a new
scope value is available in of your project POM, then
the plugin would decid
Mikael, your patch should appear in
https://github.com/apache/maven-plugins/pulls
Many people do this.
Please read tutorial on GitHub to push a new pull request.
On 8/28/16, Mikael Petterson [via Maven]
wrote:
>
>
> Hi,
>
> We are trying to use 2.12 of this plugin.
>
> I notice that the filter th
15 matches
Mail list logo
