[jira] [Updated] (ARCHETYPE-506) archetype:generate if pom.xml packaging value is pom,Chinese XML comments will change to ???
[
https://issues.apache.org/jira/browse/ARCHETYPE-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
feilong updated ARCHETYPE-506:
--
Description:
{{archetype:generate}} if pom.xml {{packaging}} value is pom,Chinese XML
comments will change to {{???}}
here is
{code:xml}
true
org.apache.maven.plugins
maven-surefire-plugin
${v.maven-surefire-plugin}
true
{code}
if {{pom}}
when i call mvn {{archetype:generate}}
result is
{code:xml}
true
org.apache.maven.plugins
maven-surefire-plugin
${v.maven-surefire-plugin}
true
{code}
but when {{war}}, result is ok
And in
http://maven.apache.org/archetype/maven-archetype-plugin/generate-mojo.html,
I can't find any {{encode}} or {{charset}} param to set
was:
{{archetype:generate}} if pom.xml {{packaging}} value is pom,Chinese XML
comments will change to {{???}}
here is
{code:xml}
true
org.apache.maven.plugins
maven-surefire-plugin
${v.maven-surefire-plugin}
true
{code}
if {{pom}}
when i call mvn {{archetype:generate}}
result is
{code:xml}
true
org.apache.maven.plugins
maven-surefire-plugin
${v.maven-surefire-plugin}
true
{code}
but when {{war}}, result is ok
And in
http://maven.apache.org/archetype/maven-archetype-plugin/generate-mojo.html#archetypeArtifactId,
I can't find any {{encode}} or {{charset}} param to set
> archetype:generate if pom.xml packaging value is pom,Chinese XML comments
> will change to ???
> --
>
> Key: ARCHETYPE-506
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-506
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: feilong
>
> {{archetype:generate}} if pom.xml {{packaging}} value is pom,Chinese XML
> comments will change to {{???}}
> here is
> {code:xml}
>
>
> true
> org.apache.maven.plugins
> maven-surefire-plugin
> ${v.maven-surefire-plugin}
>
>
> true
>
>
> {code}
> if {{pom}}
> when i call mvn {{archetype:generate}}
> result is
> {code:xml}
>
>
> true
> org.apache.maven.plugins
> maven-surefire-plugin
> ${v.maven-surefire-plugin}
>
>
> true
>
>
> {code}
> but when {{war}}, result is ok
> And in
> http://maven.apache.org/archetype/maven-archetype-plugin/generate-mojo.html,
> I can't find any {{encode}} or {{charset}} param to set
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ARCHETYPE-506) archetype:generate if pom.xml packaging value is pom,Chinese XML comments will change to ???
[
https://issues.apache.org/jira/browse/ARCHETYPE-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
feilong updated ARCHETYPE-506:
--
Description:
{{archetype:generate}} if pom.xml {{packaging}} value is pom,Chinese XML
comments will change to {{???}}
here is
{code:xml}
true
org.apache.maven.plugins
maven-surefire-plugin
${v.maven-surefire-plugin}
true
{code}
if {{pom}}
when i call mvn {{archetype:generate}}
result is
{code:xml}
true
org.apache.maven.plugins
maven-surefire-plugin
${v.maven-surefire-plugin}
true
{code}
but when {{war}}, result is ok
And in
http://maven.apache.org/archetype/maven-archetype-plugin/generate-mojo.html#archetypeArtifactId,
I can't find any {{encode}} or {{charset}} param to set
was:
{{archetype:generate}} if pom.xml {{packaging}} value is pom,Chinese XML
comments will change to {{???}}
here is
{code:xml}
true
org.apache.maven.plugins
maven-surefire-plugin
${v.maven-surefire-plugin}
true
{code}
if {{pom}}
when i call mvn {{archetype:generate}}
result is
{code:xml}
true
org.apache.maven.plugins
maven-surefire-plugin
${v.maven-surefire-plugin}
true
{code}
but when {{war}}, result is ok
> archetype:generate if pom.xml packaging value is pom,Chinese XML comments
> will change to ???
> --
>
> Key: ARCHETYPE-506
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-506
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: feilong
>
> {{archetype:generate}} if pom.xml {{packaging}} value is pom,Chinese XML
> comments will change to {{???}}
> here is
> {code:xml}
>
>
> true
> org.apache.maven.plugins
> maven-surefire-plugin
> ${v.maven-surefire-plugin}
>
>
> true
>
>
> {code}
> if {{pom}}
> when i call mvn {{archetype:generate}}
> result is
> {code:xml}
>
>
> true
> org.apache.maven.plugins
> maven-surefire-plugin
> ${v.maven-surefire-plugin}
>
>
> true
>
>
> {code}
> but when {{war}}, result is ok
> And in
> http://maven.apache.org/archetype/maven-archetype-plugin/generate-mojo.html#archetypeArtifactId,
> I can't find any {{encode}} or {{charset}} param to set
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ARCHETYPE-506) archetype:generate if pom.xml packaging value is pom,Chinese XML comments will change to ???
[
https://issues.apache.org/jira/browse/ARCHETYPE-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
feilong updated ARCHETYPE-506:
--
Description:
{{archetype:generate}} if pom.xml {{packaging}} value is pom,Chinese XML
comments will change to {{???}}
here is
{code:xml}
true
org.apache.maven.plugins
maven-surefire-plugin
${v.maven-surefire-plugin}
true
{code}
if {{pom}}
when i call mvn {{archetype:generate}}
result is
{code:xml}
true
org.apache.maven.plugins
maven-surefire-plugin
${v.maven-surefire-plugin}
true
{code}
but when {{war}}, result is ok
was:
archetype:generate if pom.xml packaging value is pom,Chinese XML comments will
change to ???
here is
{code:xml}
true
org.apache.maven.plugins
maven-surefire-plugin
${v.maven-surefire-plugin}
true
{code}
if pom
when i call mvn archetype:generate
result is
{code:xml}
true
org.apache.maven.plugins
maven-surefire-plugin
${v.maven-surefire-plugin}
true
{code}
> archetype:generate if pom.xml packaging value is pom,Chinese XML comments
> will change to ???
> --
>
> Key: ARCHETYPE-506
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-506
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: feilong
>
> {{archetype:generate}} if pom.xml {{packaging}} value is pom,Chinese XML
> comments will change to {{???}}
> here is
> {code:xml}
>
>
> true
> org.apache.maven.plugins
> maven-surefire-plugin
> ${v.maven-surefire-plugin}
>
>
> true
>
>
> {code}
> if {{pom}}
> when i call mvn {{archetype:generate}}
> result is
> {code:xml}
>
>
> true
> org.apache.maven.plugins
> maven-surefire-plugin
> ${v.maven-surefire-plugin}
>
>
> true
>
>
> {code}
> but when {{war}}, result is ok
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ARCHETYPE-506) archetype:generate if pom.xml packaging value is pom,Chinese XML comments will change to ???
[
https://issues.apache.org/jira/browse/ARCHETYPE-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
feilong updated ARCHETYPE-506:
--
Description:
archetype:generate if pom.xml packaging value is pom,Chinese XML comments will
change to ???
here is
{code:xml}
true
org.apache.maven.plugins
maven-surefire-plugin
${v.maven-surefire-plugin}
true
{code}
if pom
when i call mvn archetype:generate
result is
{code:xml}
true
org.apache.maven.plugins
maven-surefire-plugin
${v.maven-surefire-plugin}
true
{code}
was:archetype:generate if pom.xml packaging value is pom,Chinese XML comments
will change to ???
> archetype:generate if pom.xml packaging value is pom,Chinese XML comments
> will change to ???
> --
>
> Key: ARCHETYPE-506
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-506
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: feilong
>
> archetype:generate if pom.xml packaging value is pom,Chinese XML comments
> will change to ???
> here is
> {code:xml}
>
>
> true
> org.apache.maven.plugins
> maven-surefire-plugin
> ${v.maven-surefire-plugin}
>
>
> true
>
>
> {code}
> if pom
> when i call mvn archetype:generate
> result is
> {code:xml}
>
>
> true
> org.apache.maven.plugins
> maven-surefire-plugin
> ${v.maven-surefire-plugin}
>
>
> true
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ARCHETYPE-506) archetype:generate if pom.xml packaging value is pom,Chinese XML comments will change to ???
feilong created ARCHETYPE-506: - Summary: archetype:generate if pom.xml packaging value is pom,Chinese XML comments will change to ??? Key: ARCHETYPE-506 URL: https://issues.apache.org/jira/browse/ARCHETYPE-506 Project: Maven Archetype Issue Type: Bug Affects Versions: 2.4 Reporter: feilong archetype:generate if pom.xml packaging value is pom,Chinese XML comments will change to ??? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5652) "supplies"/"provides"/"proffers" concept proposal
[
https://issues.apache.org/jira/browse/MNG-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401285#comment-15401285
]
Robert Scholte commented on MNG-5652:
-
http://cr.openjdk.java.net/~mr/jigsaw/spec/lang-vm.html Jigsaw/Java9 recognizes
this as well, they introduce {{provides X.Y with Z1.Z2;}}, but they can do it
on a TypeName level.
> "supplies"/"provides"/"proffers" concept proposal
> -
>
> Key: MNG-5652
> URL: https://issues.apache.org/jira/browse/MNG-5652
> Project: Maven
> Issue Type: New Feature
> Components: FDPFC
>Reporter: Stephen Connolly
>
> The exact name is still undecided. Some candidate names are: "supplies",
> "provides", and "proffers"
> h2. "supplies" concept proposal
> ===
> h3. Introduction
>
> The following is a proposal for Maven in a post-modelVersion-4.0.0 era. The
> aim of this proposal is to simplify the management of dependency trees in the
> decentralised era of artifact production that we find ourselves in.
> The core issue is that different organisations can produce artifacts that may
> overlap. The easiest example is the servlet-api. If we restrict ourselves to
> version 2.5 of the servlet specification there are quite a few artifacts that
> all deliver the exact same content:
> * {{jetty:servlet-api:2.5-6.0.2}}
> * {{org.daisy.libs:servlet-api:2.5.0}}
> * {{org.mortbay.jetty:servlet-api-2.5:6.1.14}}
> * {{org.jboss.spec.javax.servlet:jboss-servlet-api_2.5_spec:1.0.1.Final}}
> * etc
> **Note:** this is a generic problem that is not restricted to the
> servlet-api, the servlet-api just provides the example that will be most
> familiar to everyone.
> So where these multiple artifacts supplying the equivalent content becomes a
> problem is when the dependency tree is being calculated. If you have two
> dependencies each declaring transitive dependencies on different artifacts
> that supply equivalent content, then you end up with two copies of the same
> JAR file in your classpath.
> In the case of the servlet-api, the hack most people use is to declare the
> servlet-api with scope `provided` thus preventing it from being transitive.
> This is, however, a hack. In a more ideal world it would be better to let the
> servlet-api be transitive and only when we get to the WAR module would we
> declare that a specific servlet-api is to be provided in the containers that
> the WAR is targets for deployment into.
> We can take a second example that does not have the luxury of a *de facto*
> hack.
> * {{javax.faces:jsf-api:2.1}}
> * {{org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec:2.1.28.Final}}
> * {{org.apache.myfaces.core:myfaces-api:2.1.13}}
> Now in the case of the JSF API, you are supposed to bundle the JSF API in
> your WAR file. So if I use three JSF component libraries, I could very well
> end up with three different but equivalent JSF API jars in my WAR file.
> Ideally what we want is some way of telling Maven that these artifacts are
> equivalent.
> Proposal
>
> Introduce the concept of "supplies" to the project model. The concept needs
> three changes to the project model:
> 1. An explicit top level construct for a project to explicitly declare
> up-front artifacts that it knows - at the time the project is being authored
> - to contain equivalent content to at least a subset of the project's
> content. Declarations could include a claim from: `subset`, `superset`,
> `disjoint` and `equivalent` with the default being `disjoint`.
> 2. An explicit sub-element of the `dependency` construct to allow consumers
> to *post-facto* declare a specific dependency as supplying equivalent content
> for other dependencies
> 3. An extension to the `dependency/excludes/exclude` construct to allow
> consumers to remove claims a dependency makes with respect to supplying
> equivalent content
> By way of illustration, here are some examples of these constructs mapped to
> a Model Version 4.0.0 like XML schema. As the post-modelVersion-4.0.0 schema
> is not yet known, this represents the best way to illustrate how the concept
> will work, but note that this proposal does not suggest a schema for this
> concept.
> h3. Example 1
> This illustrates how we would want, say, the `myfaces-api` project model to
> look.
> {code:xml}
>
> org.apache.myfaces.core
> myfaces-api
> 2.1.3
> ...
>
>
> javax.faces
> jsf-api
> [2.1,2.2)
> superset
>
>
> org.jboss.spec.javax.faces
> jboss-jsf-api_2.1_spec
> equivalent
>
>
> ...
>
> {code}
> This indicates that the {{myfaces-api}} artifact is intended to be useable as
> a drop-in replacement for either the {{javax.faces:jsf-api}} artifact within
> a bounded range or for any version of the
>
[jira] [Commented] (MNG-6074) Maven should produce an error if no model version has been set in a POM file used to build an effective model.
[
https://issues.apache.org/jira/browse/MNG-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401245#comment-15401245
]
Hudson commented on MNG-6074:
-
UNSTABLE: Integrated in maven-3.x #1352 (See
[https://builds.apache.org/job/maven-3.x/1352/])
[MNG-6074] Maven should produce an error if no model version has been (schulte:
rev 744b98e8cf9f2fbe4f73b07927a2c697e8cc6fc2)
*
maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
> Maven should produce an error if no model version has been set in a POM file
> used to build an effective model.
> --
>
> Key: MNG-6074
> URL: https://issues.apache.org/jira/browse/MNG-6074
> Project: Maven
> Issue Type: Improvement
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Maven currently only validates the model version to equal {{4.0.0}} when set.
> The XML element is optional. Starting with Maven 3.4.0 a warning message
> should be printed whenever no model version has been set so that it becomes
> possible to use that version to decide about Maven behaviour. For example: In
> Maven 3.5 we could add support for a new model version {{4.1.0}} which may be
> used to decide about how Maven 3.5 should behave. Behaviour for model version
> {{4.0.0}} will be the same as in Maven 3.4. Behaviour for model version
> {{4.1.0}} could be different. For this the model version needs to be set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MNG-6074) Maven should produce an error if no model version has been set in a POM file used to build an effective model.
[
https://issues.apache.org/jira/browse/MNG-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte updated MNG-6074:
---
Summary: Maven should produce an error if no model version has been set in
a POM file used to build an effective model. (was: Maven should print a
warning if no model version has been set in a POM file.)
> Maven should produce an error if no model version has been set in a POM file
> used to build an effective model.
> --
>
> Key: MNG-6074
> URL: https://issues.apache.org/jira/browse/MNG-6074
> Project: Maven
> Issue Type: Improvement
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Maven currently only validates the model version to equal {{4.0.0}} when set.
> The XML element is optional. Starting with Maven 3.4.0 a warning message
> should be printed whenever no model version has been set so that it becomes
> possible to use that version to decide about Maven behaviour. For example: In
> Maven 3.5 we could add support for a new model version {{4.1.0}} which may be
> used to decide about how Maven 3.5 should behave. Behaviour for model version
> {{4.0.0}} will be the same as in Maven 3.4. Behaviour for model version
> {{4.1.0}} could be different. For this the model version needs to be set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-6075) Increase the model validation level to the next minor level version.
[ https://issues.apache.org/jira/browse/MNG-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401215#comment-15401215 ] Hudson commented on MNG-6075: - UNSTABLE: Integrated in maven-3.x #1350 (See [https://builds.apache.org/job/maven-3.x/1350/]) [MNG-6075] Increase the model validation level to the next minor level (schulte: rev 3681fd8489cd59d0c5bc49ef38725b655d524301) * maven-model-builder/src/main/java/org/apache/maven/model/building/ModelBuildingRequest.java > Increase the model validation level to the next minor level version. > > > Key: MNG-6075 > URL: https://issues.apache.org/jira/browse/MNG-6075 > Project: Maven > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Critical > Fix For: 3.4.0 > > > Maven 3 has warned about various model related issues clearly stating that > not reacting to those warnings may break with a future Maven version. > Starting with Maven 3.4, the model validation level has been increased to the > next minor version so that such warnings will become errors as of 3.4. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6073) Addition of a core extension point to the model builder supporting model finalization.
[ https://issues.apache.org/jira/browse/MNG-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401214#comment-15401214 ] Hudson commented on MNG-6073: - UNSTABLE: Integrated in maven-3.x #1350 (See [https://builds.apache.org/job/maven-3.x/1350/]) [MNG-6073] Addition of a core extension point to the model builder (schulte: rev 3628e9665a6d1340da4e9b5bd6d1d05e6f9adfc2) * maven-model-builder/src/main/java/org/apache/maven/model/finalization/DependencyManagementModelFinalizer.java > Addition of a core extension point to the model builder supporting model > finalization. > -- > > Key: MNG-6073 > URL: https://issues.apache.org/jira/browse/MNG-6073 > Project: Maven > Issue Type: New Feature >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: 3.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNG-6075) Increase the model validation level to the next minor level version.
[ https://issues.apache.org/jira/browse/MNG-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MNG-6075. -- Resolution: Fixed > Increase the model validation level to the next minor level version. > > > Key: MNG-6075 > URL: https://issues.apache.org/jira/browse/MNG-6075 > Project: Maven > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Critical > Fix For: 3.4.0 > > > Maven 3 has warned about various model related issues clearly stating that > not reacting to those warnings may break with a future Maven version. > Starting with Maven 3.4, the model validation level has been increased to the > next minor version so that such warnings will become errors as of 3.4. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MNG-6075) Increase the model validation level to the next minor level version.
Christian Schulte created MNG-6075: -- Summary: Increase the model validation level to the next minor level version. Key: MNG-6075 URL: https://issues.apache.org/jira/browse/MNG-6075 Project: Maven Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Critical Fix For: 3.4.0 Maven 3 has warned about various model related issues clearly stating that not reacting to those warnings may break with a future Maven version. Starting with Maven 3.4, the model validation level has been increased to the next minor version so that such warnings will become errors as of 3.4. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
