[jira] [Comment Edited] (MNG-6308) display packaging when building a module

2017-12-10 Thread JIRA

[ 
https://issues.apache.org/jira/browse/MNG-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285311#comment-16285311
 ] 

Hervé Boutemy edited comment on MNG-6308 at 12/10/17 4:44 PM:
--

sure, one can avoid defining $\{project.packaging} then put just pom to not 
benefit from default plugin bindings to lifecycle

but in general, if we defined default plugin bindings based on 
$\{project.packaging} value, it's because in general this defines the expected 
default build: explicitely adding some plugins is just some little additional 
build customization

notice: probably we should have put this element in build, then have 
$\{project.build.packaging}, but now the habit is to have this build info near 
groupId/artifactId/version


was (Author: hboutemy):
sure, one can avoid defining $\{project.packaging} then put just pom to not 
benefit from default plugin bindings to lifecycle

but in general, if we defined default plugin bindings based on 
$\{project.packaging} value, it's because in general this defines the expected 
default build: explicitely adding some plugins is just some little additional 
build customization

> display packaging when building a module
> 
>
> Key: MNG-6308
> URL: https://issues.apache.org/jira/browse/MNG-6308
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.5.2
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>
> Packaging is a key information, since it defines what bindings will be: it is 
> short and should be visible in the build log
> proposal:
> {code}[INFO] 
> 
> [INFO] Building Apache Maven Distribution 3.5.3-SNAPSHOT
> [15/15]
> [INFO] ---  pom  
> --{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Comment Edited] (MNG-6308) display packaging when building a module

2017-12-10 Thread JIRA

[ 
https://issues.apache.org/jira/browse/MNG-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285311#comment-16285311
 ] 

Hervé Boutemy edited comment on MNG-6308 at 12/10/17 4:42 PM:
--

sure, one can avoid defining $\{project.packaging} then put just pom to not 
benefit from default plugin bindings to lifecycle

but in general, if we defined default plugin bindings based on 
$\{project.packaging} value, it's because in general this defines the expected 
default build: explicitely adding some plugins is just some little additional 
build customization


was (Author: hboutemy):
sure, one can avoid defining ${project.packaging} then put just pom to not 
benefit from default plugin bindings to lifecycle

but in general, if we defined default plugin bindings based on 
${project.packaging} value, it's because in general this defines the expected 
default build: explicitely adding some plugins is just some little additional 
build customization

> display packaging when building a module
> 
>
> Key: MNG-6308
> URL: https://issues.apache.org/jira/browse/MNG-6308
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.5.2
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>
> Packaging is a key information, since it defines what bindings will be: it is 
> short and should be visible in the build log
> proposal:
> {code}[INFO] 
> 
> [INFO] Building Apache Maven Distribution 3.5.3-SNAPSHOT
> [15/15]
> [INFO] ---  pom  
> --{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Comment Edited] (MNG-6308) display packaging when building a module

2017-12-10 Thread JIRA

[ 
https://issues.apache.org/jira/browse/MNG-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285144#comment-16285144
 ] 

Hervé Boutemy edited comment on MNG-6308 at 12/10/17 8:52 AM:
--

re-reading once more 
http://maven.apache.org/ref/3.5.2/maven-core/artifact-handlers.html
I don't think having a packaging attribute on artifact handlers has really a 
meaning: javadoc packaging does not exist, not java-source
I really feel that there is a misconception here (and I suppose that this 
getPackaging() method isn't used anywhere since it does not really have any 
meaning)

and when we read the documentation for type in pom's dependency 
http://maven.apache.org/ref/3.5.2/maven-model/maven.html#class_dependency , 
this misconception is apparent by the vague explanations


was (Author: hboutemy):
re-reading once more 
http://maven.apache.org/ref/3.5.2/maven-core/artifact-handlers.html
I don't think having a packaging attribute on artifact handlers has really a 
meaning: javadoc packaging does not exist, not java-source
I really feel that there is a misconception here (and I suppose that this 
getPackaging() method isn't used anywhere since it does not really have any 
meaning)

> display packaging when building a module
> 
>
> Key: MNG-6308
> URL: https://issues.apache.org/jira/browse/MNG-6308
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.5.2
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>
> Packaging is a key information, since it defines what bindings will be: it is 
> short and should be visible in the build log
> proposal:
> {code}[INFO] 
> 
> [INFO] Building Apache Maven Distribution 3.5.3-SNAPSHOT
> [15/15]
> [INFO] ---  pom  
> --{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Comment Edited] (MNG-6308) display packaging when building a module

2017-12-09 Thread JIRA

[ 
https://issues.apache.org/jira/browse/MNG-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16258643#comment-16258643
 ] 

Hervé Boutemy edited comment on MNG-6308 at 12/10/17 7:12 AM:
--

bq. Are we interested in the packaging or the type (i.e. the file extension)?
the fact that you ask shows that it's a key info we should have made more 
visible for years...
we're at build time, what is important to me is packaging since it drives 
build: see bindings associated to each packaging 
http://maven.apache.org/ref/3.5.2/maven-core/default-bindings.html

we can also write
{code}[INFO] 

[INFO] Building Apache Maven Distribution 3.5.3-SNAPSHOT[15/15]
[INFO] 
---[pom]{code}



was (Author: hboutemy):
bq. Are we interested in the packaging or the type (i.e. the file extension)?
the fact that you ask shows that it's a key info we should have made more 
visible for years...
we're at build time, what is important to me is packaging since it drives 
build:http://maven.apache.org/ref/3.5.2/maven-core/default-bindings.html

we can also write
{code}[INFO] 

[INFO] Building Apache Maven Distribution 3.5.3-SNAPSHOT[15/15]
[INFO] 
---[pom]{code}


> display packaging when building a module
> 
>
> Key: MNG-6308
> URL: https://issues.apache.org/jira/browse/MNG-6308
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.5.2
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>
> Packaging is a key information, since it defines what bindings will be: it is 
> short and should be visible in the build log
> proposal:
> {code}[INFO] 
> 
> [INFO] Building Apache Maven Distribution 3.5.3-SNAPSHOT
> [15/15]
> [INFO] ---  pom  
> --{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Comment Edited] (MNG-6308) display packaging when building a module

2017-11-19 Thread JIRA

[ 
https://issues.apache.org/jira/browse/MNG-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16258643#comment-16258643
 ] 

Hervé Boutemy edited comment on MNG-6308 at 11/19/17 10:14 PM:
---

bq. Are we interested in the packaging or the type (i.e. the file extension)?
the fact that you ask shows that it's a key info we should have made more 
visible for years...
we're at build time, what is important to me is packaging since it drives 
build:http://maven.apache.org/ref/3.5.2/maven-core/default-bindings.html

we can also write
{code}[INFO] 

[INFO] Building Apache Maven Distribution 3.5.3-SNAPSHOT[15/15]
[INFO] 
---[pom]{code}



was (Author: hboutemy):
bq. Are we interested in the packaging or the type (i.e. the file extension)?
the fact that you ask shows that it's a key info we should have made more 
visible for years...
we're at build time, what is important to me is packaging since it drives 
build:http://maven.apache.org/ref/3.5.2/maven-core/default-bindings.html

{code}[INFO] 

[INFO] Building Apache Maven Distribution 3.5.3-SNAPSHOT[15/15]
[INFO] 
---[pom]{code}


> display packaging when building a module
> 
>
> Key: MNG-6308
> URL: https://issues.apache.org/jira/browse/MNG-6308
> Project: Maven
>  Issue Type: Improvement
>Affects Versions: 3.5.2
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>
> Packaging is a key information, since it defines what bindings will be: it is 
> short and should be visible in the build log
> proposal:
> {code}[INFO] 
> 
> [INFO] Building Apache Maven Distribution 3.5.3-SNAPSHOT
> [15/15]
> [INFO] ---  pom  
> --{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)