Le mercredi 14 mars 2018, 01:37:38 CET Laird Nelson a écrit :
> On Tue, Mar 13, 2018 at 5:34 PM Hervé BOUTEMY wrote:
> > I don't see any issues with content provided:
> > org.springframework.boot:spring-
> > boot-dependencies has a "pom" packaging, then would be deployed directly
> > as
> > build
Le mardi 13 mars 2018, 19:57:01 CET Robert Scholte a écrit :
> Does it make sense to move some of the archetypes to their matching
> project?
>
> For example, Why not move maven-archetype-plugin to the maven-plugin
> project.
> This should make it easier to maintain to to keep it up to date.
maven
Le mardi 13 mars 2018, 22:47:50 CET Michael Osipov a écrit :
> Am 2018-03-13 um 18:23 schrieb Robert Scholte:
> > On Tue, 13 Mar 2018 00:13:59 +0100, Hervé BOUTEMY
> >
> > wrote:
> >> Hi Charles,
> >>
> >> Thanks for the feedback
> >>
> >> Le lundi 12 mars 2018, 01:49:26 CET Charles Honton a éc
On Tue, Mar 13, 2018 at 5:34 PM Hervé BOUTEMY wrote:
> I don't see any issues with content provided:
> org.springframework.boot:spring-
> boot-dependencies has a "pom" packaging, then would be deployed directly as
> build POM, containing dependencyManagement
>
I'm not sure, but I think the quest
Le mardi 13 mars 2018, 21:59:56 CET Andreas Sewe a écrit :
> Hi,
>
> as a user of Maven and a researcher analyzing what's in Maven central, I
> would prefer to see
>
>
>
> in the "kept by choice" category as well. While may be
> more useful for end-user facing tools, in this day and age of b
I don't see any issues with content provided: org.springframework.boot:spring-
boot-dependencies has a "pom" packaging, then would be deployed directly as
build POM, containing dependencyManagement
Regards,
Hervé
Le mardi 13 mars 2018, 12:25:21 CET Arnaud Héritier a écrit :
> Spring Boot (but
Am 2018-03-13 um 18:23 schrieb Robert Scholte:
On Tue, 13 Mar 2018 00:13:59 +0100, Hervé BOUTEMY
wrote:
Hi Charles,
Thanks for the feedback
Le lundi 12 mars 2018, 01:49:26 CET Charles Honton a écrit :
Hervé,
Great work!
Thank you: it took a lot of time and discussion :)
Some possible a
Hi,
as a user of Maven and a researcher analyzing what's in Maven central, I
would prefer to see
in the "kept by choice" category as well. While may be
more useful for end-user facing tools, in this day and age of badges
pointing to CI servers on Github, I can still see this as useful for
co
Hi,
> Naming Conventions
> consumer pom must continue to be named pom.xml
> build pom shall be called build.xml
Please don't re-use a name already occupied by another build tool (in
this case, Ant). Many IDEs associate editors based on file name and this
would confuse them. Eclipse, for example,
Does it make sense to move some of the archetypes to their matching
project?
For example, Why not move maven-archetype-plugin to the maven-plugin
project.
This should make it easier to maintain to to keep it up to date.
thanks,
Robert
On Tue, 13 Mar 2018 07:52:18 +0100, Hervé BOUTEMY
wr
Hi to all,
I want to know if we have more enhancements etc.
I would like to merge this as soon as possible to master...
On 19/02/18 19:59, Karl Heinz Marbaise wrote:
Hi,
I would like to integrate the issue MNG-6362 which contains only
enhancements for the README.md, CONTRIBUTION.md and a
On Tue, 13 Mar 2018 00:13:59 +0100, Hervé BOUTEMY
wrote:
Hi Charles,
Thanks for the feedback
Le lundi 12 mars 2018, 01:49:26 CET Charles Honton a écrit :
Hervé,
Great work!
Thank you: it took a lot of time and discussion :)
Some possible additions for the wiki page:
Naming Conventions
Spring Boot (but others are doing too) is using a lot the dependencies with
~empty jar artifacts (
http://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-web/2.0.0.RELEASE/
)
You declare something like :
org.springframework.boot
spring-boot-dependenc
13 matches
Mail list logo
