[jira] [Updated] (MINSTALL-160) generatePom=true with 3.0.0-M1 does not generate minimal POM but copies existing one
[
https://issues.apache.org/jira/browse/MINSTALL-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MINSTALL-160:
-
Affects Version/s: (was: 3.0.0-M2)
> generatePom=true with 3.0.0-M1 does not generate minimal POM but copies
> existing one
>
>
> Key: MINSTALL-160
> URL: https://issues.apache.org/jira/browse/MINSTALL-160
> Project: Maven Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 3.0.0-M1, 3.0.0
>Reporter: Václav Haisman
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.0.1
>
>
> I am using install:install-file with generatePom=true to install JAR with
> minimal POM file. This has stopped working with 3.0.0-M1. With 3.0.0-M1, it
> copeis existing project pom.xml instead of generating a minimal one.
>
> This is easily reproducible with minimal project:
> {code:java}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> maven.install.plugin.issue
> maven.install.plugin.issue
> 1.0-SNAPSHOT
> jar
> maven.install.plugin.issue
>
> 1.6
> 1.6
>
>
>
>
>
> maven-install-plugin
>
> 3.0.0-M1
>
>
>
>
>
>
> maven-install-plugin
>
>
> default-install
> none
> install
>
>
> custom-install
> install
>
> install-file
>
>
>
> ${project.build.directory}/${project.artifactId}-${project.version}.${project.packaging}
> true
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MINSTALL-160) generatePom=true with 3.0.0-M1 does not generate minimal POM but copies existing one
[
https://issues.apache.org/jira/browse/MINSTALL-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamás Cservenák updated MINSTALL-160:
-
Affects Version/s: 3.0.0
3.0.0-M2
> generatePom=true with 3.0.0-M1 does not generate minimal POM but copies
> existing one
>
>
> Key: MINSTALL-160
> URL: https://issues.apache.org/jira/browse/MINSTALL-160
> Project: Maven Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 3.0.0-M1, 3.0.0, 3.0.0-M2
>Reporter: Václav Haisman
>Priority: Major
> Fix For: 3.0.1
>
>
> I am using install:install-file with generatePom=true to install JAR with
> minimal POM file. This has stopped working with 3.0.0-M1. With 3.0.0-M1, it
> copeis existing project pom.xml instead of generating a minimal one.
>
> This is easily reproducible with minimal project:
> {code:java}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> maven.install.plugin.issue
> maven.install.plugin.issue
> 1.0-SNAPSHOT
> jar
> maven.install.plugin.issue
>
> 1.6
> 1.6
>
>
>
>
>
> maven-install-plugin
>
> 3.0.0-M1
>
>
>
>
>
>
> maven-install-plugin
>
>
> default-install
> none
> install
>
>
> custom-install
> install
>
> install-file
>
>
>
> ${project.build.directory}/${project.artifactId}-${project.version}.${project.packaging}
> true
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MINSTALL-160) generatePom=true with 3.0.0-M1 does not generate minimal POM but copies existing one
[
https://issues.apache.org/jira/browse/MINSTALL-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamás Cservenák updated MINSTALL-160:
-
Fix Version/s: 3.0.1
> generatePom=true with 3.0.0-M1 does not generate minimal POM but copies
> existing one
>
>
> Key: MINSTALL-160
> URL: https://issues.apache.org/jira/browse/MINSTALL-160
> Project: Maven Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 3.0.0-M1
>Reporter: Václav Haisman
>Priority: Major
> Fix For: 3.0.1
>
>
> I am using install:install-file with generatePom=true to install JAR with
> minimal POM file. This has stopped working with 3.0.0-M1. With 3.0.0-M1, it
> copeis existing project pom.xml instead of generating a minimal one.
>
> This is easily reproducible with minimal project:
> {code:java}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> maven.install.plugin.issue
> maven.install.plugin.issue
> 1.0-SNAPSHOT
> jar
> maven.install.plugin.issue
>
> 1.6
> 1.6
>
>
>
>
>
> maven-install-plugin
>
> 3.0.0-M1
>
>
>
>
>
>
> maven-install-plugin
>
>
> default-install
> none
> install
>
>
> custom-install
> install
>
> install-file
>
>
>
> ${project.build.directory}/${project.artifactId}-${project.version}.${project.packaging}
> true
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MINSTALL-160) generatePom=true with 3.0.0-M1 does not generate minimal POM but copies existing one
[
https://issues.apache.org/jira/browse/MINSTALL-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Václav Haisman updated MINSTALL-160:
Issue Type: Bug (was: Wish)
> generatePom=true with 3.0.0-M1 does not generate minimal POM but copies
> existing one
>
>
> Key: MINSTALL-160
> URL: https://issues.apache.org/jira/browse/MINSTALL-160
> Project: Maven Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 3.0.0-M1
>Reporter: Václav Haisman
>Priority: Major
>
> I am using install:install-file with generatePom=true to install JAR with
> minimal POM file. This has stopped working with 3.0.0-M1. With 3.0.0-M1, it
> copeis existing project pom.xml instead of generating a minimal one.
>
> This is easily reproducible with minimal project:
> {code:java}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> maven.install.plugin.issue
> maven.install.plugin.issue
> 1.0-SNAPSHOT
> jar
> maven.install.plugin.issue
>
> 1.6
> 1.6
>
>
>
>
>
> maven-install-plugin
>
> 3.0.0-M1
>
>
>
>
>
>
> maven-install-plugin
>
>
> default-install
> none
> install
>
>
> custom-install
> install
>
> install-file
>
>
>
> ${project.build.directory}/${project.artifactId}-${project.version}.${project.packaging}
> true
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (MINSTALL-160) generatePom=true with 3.0.0-M1 does not generate minimal POM but copies existing one
[
https://issues.apache.org/jira/browse/MINSTALL-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Václav Haisman updated MINSTALL-160:
Description:
I am using install:install-file with generatePom=true to install JAR with
minimal POM file. This has stopped working with 3.0.0-M1. With 3.0.0-M1, it
copeis existing project pom.xml instead of generating a minimal one.
This is easily reproducible with minimal project:
{code:java}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
maven.install.plugin.issue
maven.install.plugin.issue
1.0-SNAPSHOT
jar
maven.install.plugin.issue
1.6
1.6
maven-install-plugin
3.0.0-M1
maven-install-plugin
default-install
none
install
custom-install
install
install-file
${project.build.directory}/${project.artifactId}-${project.version}.${project.packaging}
true
{code}
was:
I am using install:install-file with generatePom=true to install JAR with
minimal POM file. This has stopped working with 3.0.0-M1. This is easily
reproducible with minimal project:
{code}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
maven.install.plugin.issue
maven.install.plugin.issue
1.0-SNAPSHOT
jar
maven.install.plugin.issue
1.6
1.6
maven-install-plugin
3.0.0-M1
maven-install-plugin
default-install
none
install
custom-install
install
install-file
${project.build.directory}/${project.artifactId}-${project.version}.${project.packaging}
true
{code}
> generatePom=true with 3.0.0-M1 does not generate minimal POM but copies
> existing one
>
>
> Key: MINSTALL-160
> URL: https://issues.apache.org/jira/browse/MINSTALL-160
> Project: Maven Install Plugin
> Issue Type: Wish
> Components: install:install-file
>Affects Versions: 3.0.0-M1
>Reporter: Václav Haisman
>Priority: Major
>
> I am using install:install-file with generatePom=true to install JAR with
> minimal POM file. This has stopped working with 3.0.0-M1. With 3.0.0-M1, it
> copeis existing project pom.xml instead of generating a minimal one.
>
> This is easily reproducible with minimal project:
> {code:java}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> maven.install.plugin.issue
> maven.install.plugin.issue
> 1.0-SNAPSHOT
> jar
> maven.install.plugin.issue
>
> 1.6
> 1.6
>
>
>
>
>
> maven-install-plugin
>
> 3.0.0-M1
>
>
>
>
>
>
> maven-install-plugin
>
>
> default-install
> none
> install
>
>
> custom-install
> install
>
> install-file
>
>
>
> ${project.build.directory}/${project.artifactId}-${project.version}.${project.packaging}
> true
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
