[jira] (MANTRUN-188) MavenProject/MavenSession Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MANTRUN-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MANTRUN-188.
---
Resolution: Fixed
Assignee: Karl-Heinz Marbaise
Fixed in [r1616893|http://svn.apache.org/r1616893].
> MavenProject/MavenSession Injection as a paremeter instead as a component.
> --
>
> Key: MANTRUN-188
> URL: https://jira.codehaus.org/browse/MANTRUN-188
> Project: Maven Antrun Plugin
> Issue Type: Task
>Affects Versions: 1.7
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 1.8
>
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
> The following:
> {code:java}
> @Component
> protected MavenSession session;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${session}", readonly = true, required = true )
> protected MavenSession session;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MANTRUN-188) MavenProject/MavenSession Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MANTRUN-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MANTRUN-188:
Fix Version/s: 1.8
> MavenProject/MavenSession Injection as a paremeter instead as a component.
> --
>
> Key: MANTRUN-188
> URL: https://jira.codehaus.org/browse/MANTRUN-188
> Project: Maven Antrun Plugin
> Issue Type: Task
>Affects Versions: 1.7
>Reporter: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 1.8
>
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
> The following:
> {code:java}
> @Component
> protected MavenSession session;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${session}", readonly = true, required = true )
> protected MavenSession session;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MANTRUN-188) MavenProject/MavenSession Injection as a paremeter instead as a component.
Karl-Heinz Marbaise created MANTRUN-188:
---
Summary: MavenProject/MavenSession Injection as a paremeter
instead as a component.
Key: MANTRUN-188
URL: https://jira.codehaus.org/browse/MANTRUN-188
Project: Maven Antrun Plugin
Issue Type: Task
Affects Versions: 1.7
Reporter: Karl-Heinz Marbaise
Priority: Minor
The following:
{code:java}
@Component
protected MavenProject project;
{code}
has to be replaced by the following:
{code:java}
@Parameter( defaultValue = "${project}", readonly = true, required = true )
protected MavenProject project;
{code}
The following:
{code:java}
@Component
protected MavenSession session;
{code}
has to be replaced by the following:
{code:java}
@Parameter( defaultValue = "${session}", readonly = true, required = true )
protected MavenSession session;
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MANTRUN-187) Make Plugin only 2.2.1 compatible - get rid of Maven 2.0
[ https://jira.codehaus.org/browse/MANTRUN-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MANTRUN-187. --- Resolution: Fixed Fixed in [r1616888|http://svn.apache.org/r1616888]. > Make Plugin only 2.2.1 compatible - get rid of Maven 2.0 > > > Key: MANTRUN-187 > URL: https://jira.codehaus.org/browse/MANTRUN-187 > Project: Maven Antrun Plugin > Issue Type: Task >Affects Versions: 1.8 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.8 > > > No more Maven 2.0.X -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MANTRUN-187) Make Plugin only 2.2.1 compatible - get rid of Maven 2.0
[ https://jira.codehaus.org/browse/MANTRUN-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise reassigned MANTRUN-187: --- Assignee: Karl-Heinz Marbaise > Make Plugin only 2.2.1 compatible - get rid of Maven 2.0 > > > Key: MANTRUN-187 > URL: https://jira.codehaus.org/browse/MANTRUN-187 > Project: Maven Antrun Plugin > Issue Type: Task >Affects Versions: 1.8 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.8 > > > No more Maven 2.0.X -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MANTRUN-187) Make Plugin only 2.2.1 compatible - get rid of Maven 2.0
[ https://jira.codehaus.org/browse/MANTRUN-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MANTRUN-187: Fix Version/s: 1.8 > Make Plugin only 2.2.1 compatible - get rid of Maven 2.0 > > > Key: MANTRUN-187 > URL: https://jira.codehaus.org/browse/MANTRUN-187 > Project: Maven Antrun Plugin > Issue Type: Task >Affects Versions: 1.8 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.8 > > > No more Maven 2.0.X -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MANTRUN-187) Make Plugin only 2.2.1 compatible - get rid of Maven 2.0
Karl-Heinz Marbaise created MANTRUN-187: --- Summary: Make Plugin only 2.2.1 compatible - get rid of Maven 2.0 Key: MANTRUN-187 URL: https://jira.codehaus.org/browse/MANTRUN-187 Project: Maven Antrun Plugin Issue Type: Task Affects Versions: 1.8 Reporter: Karl-Heinz Marbaise Priority: Minor No more Maven 2.0.X -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MANT-76) MavenProject/MavenSession Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MANT-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MANT-76.
---
Resolution: Fixed
Fixed in [r1616885|http://svn.apache.org/r1616885].
> MavenProject/MavenSession Injection as a paremeter instead as a component.
> --
>
> Key: MANT-76
> URL: https://jira.codehaus.org/browse/MANT-76
> Project: Maven Ant Plugin
> Issue Type: Task
>Affects Versions: 2.3
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.4
>
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
> The following:
> {code:java}
> @Component
> protected MavenSession session;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${session}", readonly = true, required = true )
> protected MavenSession session;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MANT-76) MavenProject/MavenSession Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MANT-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise reassigned MANT-76:
---
Assignee: Karl-Heinz Marbaise
> MavenProject/MavenSession Injection as a paremeter instead as a component.
> --
>
> Key: MANT-76
> URL: https://jira.codehaus.org/browse/MANT-76
> Project: Maven Ant Plugin
> Issue Type: Task
>Affects Versions: 2.3
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.4
>
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
> The following:
> {code:java}
> @Component
> protected MavenSession session;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${session}", readonly = true, required = true )
> protected MavenSession session;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MANT-76) MavenProject/MavenSession Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MANT-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MANT-76:
Fix Version/s: 2.4
> MavenProject/MavenSession Injection as a paremeter instead as a component.
> --
>
> Key: MANT-76
> URL: https://jira.codehaus.org/browse/MANT-76
> Project: Maven Ant Plugin
> Issue Type: Task
>Affects Versions: 2.3
>Reporter: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.4
>
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
> The following:
> {code:java}
> @Component
> protected MavenSession session;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${session}", readonly = true, required = true )
> protected MavenSession session;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MANT-76) MavenProject/MavenSession Injection as a paremeter instead as a component.
Karl-Heinz Marbaise created MANT-76:
---
Summary: MavenProject/MavenSession Injection as a paremeter
instead as a component.
Key: MANT-76
URL: https://jira.codehaus.org/browse/MANT-76
Project: Maven Ant Plugin
Issue Type: Task
Affects Versions: 2.3
Reporter: Karl-Heinz Marbaise
Priority: Minor
The following:
{code:java}
@Component
protected MavenProject project;
{code}
has to be replaced by the following:
{code:java}
@Parameter( defaultValue = "${project}", readonly = true, required = true )
protected MavenProject project;
{code}
The following:
{code:java}
@Component
protected MavenSession session;
{code}
has to be replaced by the following:
{code:java}
@Parameter( defaultValue = "${session}", readonly = true, required = true )
protected MavenSession session;
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MENFORCER-199) allow the file based rules to use wildcards on resources
[ https://jira.codehaus.org/browse/MENFORCER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351213#comment-351213 ] Karl-Heinz Marbaise commented on MENFORCER-199: --- I have to take a deeper look into it this could be a job for http://maven.apache.org/shared/file-management/examples/mojo.html I have to check that. > allow the file based rules to use wildcards on resources > > > Key: MENFORCER-199 > URL: https://jira.codehaus.org/browse/MENFORCER-199 > Project: Maven Enforcer Plugin > Issue Type: Wish >Reporter: Bjoern Koos > > To check e.g. a maximum file size on multiple resources it would be helpful > to use wildcards. Either in the specified files entries or maybe by using a > fileSet-like semantics. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-10) Upgrade maven-filtering to 1.2
[ https://jira.codehaus.org/browse/MACR-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise resolved MACR-10. - Resolution: Fixed Fixed [r1616880|http://svn.apache.org/r1616880]. > Upgrade maven-filtering to 1.2 > -- > > Key: MACR-10 > URL: https://jira.codehaus.org/browse/MACR-10 > Project: Maven ACR Plugin > Issue Type: Task >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-10) Upgrade maven-filtering to 1.2
[ https://jira.codehaus.org/browse/MACR-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise reassigned MACR-10: --- Assignee: Karl-Heinz Marbaise > Upgrade maven-filtering to 1.2 > -- > > Key: MACR-10 > URL: https://jira.codehaus.org/browse/MACR-10 > Project: Maven ACR Plugin > Issue Type: Task >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-10) Upgrade maven-filtering to 1.2
[ https://jira.codehaus.org/browse/MACR-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MACR-10: Fix Version/s: 1.1 > Upgrade maven-filtering to 1.2 > -- > > Key: MACR-10 > URL: https://jira.codehaus.org/browse/MACR-10 > Project: Maven ACR Plugin > Issue Type: Task >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-10) Upgrade maven-filtering to 1.2
Karl-Heinz Marbaise created MACR-10: --- Summary: Upgrade maven-filtering to 1.2 Key: MACR-10 URL: https://jira.codehaus.org/browse/MACR-10 Project: Maven ACR Plugin Issue Type: Task Reporter: Karl-Heinz Marbaise Priority: Minor -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-9) Upgrade plexus-archiver to 2.4.4
[ https://jira.codehaus.org/browse/MACR-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MACR-9. -- Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1616875|http://svn.apache.org/r1616875]. > Upgrade plexus-archiver to 2.4.4 > > > Key: MACR-9 > URL: https://jira.codehaus.org/browse/MACR-9 > Project: Maven ACR Plugin > Issue Type: Task >Affects Versions: 1.0 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.1 > > > Upgrade plexus-archiver from 2.4.3 to 2.4.4 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-9) Upgrade plexus-archiver to 2.4.4
[ https://jira.codehaus.org/browse/MACR-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MACR-9: --- Fix Version/s: 1.1 > Upgrade plexus-archiver to 2.4.4 > > > Key: MACR-9 > URL: https://jira.codehaus.org/browse/MACR-9 > Project: Maven ACR Plugin > Issue Type: Task >Affects Versions: 1.0 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.1 > > > Upgrade plexus-archiver from 2.4.3 to 2.4.4 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-9) Upgrade plexus-archiver to 2.4.4
Karl-Heinz Marbaise created MACR-9: -- Summary: Upgrade plexus-archiver to 2.4.4 Key: MACR-9 URL: https://jira.codehaus.org/browse/MACR-9 Project: Maven ACR Plugin Issue Type: Task Affects Versions: 1.0 Reporter: Karl-Heinz Marbaise Priority: Minor Upgrade plexus-archiver from 2.4.3 to 2.4.4 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MENFORCER-202) Get rid of [WARNING] during build
[
https://jira.codehaus.org/browse/MENFORCER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MENFORCER-202.
-
Resolution: Fixed
Assignee: Karl-Heinz Marbaise
Fixed in [r1616874|http://svn.apache.org/r1616874].
> Get rid of [WARNING] during build
> -
>
> Key: MENFORCER-202
> URL: https://jira.codehaus.org/browse/MENFORCER-202
> Project: Maven Enforcer Plugin
> Issue Type: Task
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Critical
> Fix For: 1.4
>
>
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.enforcer:enforcer-api:jar:2.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.enforcer:enforcer:2.0-SNAPSHOT,
> /Users/kama/ws-git/apache/maven-enforcer/pom.xml, line 267, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.enforcer:enforcer-rules:jar:2.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.enforcer:enforcer:2.0-SNAPSHOT,
> /Users/kama/ws-git/apache/maven-enforcer/pom.xml, line 267, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.plugins:maven-enforcer-plugin:maven-plugin:2.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.enforcer:enforcer:2.0-SNAPSHOT,
> /Users/kama/ws-git/apache/maven-enforcer/pom.xml, line 267, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.enforcer:enforcer:pom:2.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @ line 267, column
> 15
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MENFORCER-202) Get rid of [WARNING] during build
[
https://jira.codehaus.org/browse/MENFORCER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MENFORCER-202:
--
Fix Version/s: 1.4
> Get rid of [WARNING] during build
> -
>
> Key: MENFORCER-202
> URL: https://jira.codehaus.org/browse/MENFORCER-202
> Project: Maven Enforcer Plugin
> Issue Type: Task
>Reporter: Karl-Heinz Marbaise
>Priority: Critical
> Fix For: 1.4
>
>
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.enforcer:enforcer-api:jar:2.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.enforcer:enforcer:2.0-SNAPSHOT,
> /Users/kama/ws-git/apache/maven-enforcer/pom.xml, line 267, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.enforcer:enforcer-rules:jar:2.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.enforcer:enforcer:2.0-SNAPSHOT,
> /Users/kama/ws-git/apache/maven-enforcer/pom.xml, line 267, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.plugins:maven-enforcer-plugin:maven-plugin:2.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.enforcer:enforcer:2.0-SNAPSHOT,
> /Users/kama/ws-git/apache/maven-enforcer/pom.xml, line 267, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.enforcer:enforcer:pom:2.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @ line 267, column
> 15
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MENFORCER-202) Get rid of [WARNING] during build
Karl-Heinz Marbaise created MENFORCER-202:
-
Summary: Get rid of [WARNING] during build
Key: MENFORCER-202
URL: https://jira.codehaus.org/browse/MENFORCER-202
Project: Maven Enforcer Plugin
Issue Type: Task
Reporter: Karl-Heinz Marbaise
Priority: Critical
{code}
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.maven.enforcer:enforcer-api:jar:2.0-SNAPSHOT
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-javadoc-plugin is missing. @
org.apache.maven.enforcer:enforcer:2.0-SNAPSHOT,
/Users/kama/ws-git/apache/maven-enforcer/pom.xml, line 267, column 15
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.maven.enforcer:enforcer-rules:jar:2.0-SNAPSHOT
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-javadoc-plugin is missing. @
org.apache.maven.enforcer:enforcer:2.0-SNAPSHOT,
/Users/kama/ws-git/apache/maven-enforcer/pom.xml, line 267, column 15
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.maven.plugins:maven-enforcer-plugin:maven-plugin:2.0-SNAPSHOT
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-javadoc-plugin is missing. @
org.apache.maven.enforcer:enforcer:2.0-SNAPSHOT,
/Users/kama/ws-git/apache/maven-enforcer/pom.xml, line 267, column 15
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.maven.enforcer:enforcer:pom:2.0-SNAPSHOT
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-javadoc-plugin is missing. @ line 267, column 15
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-706) MavenProject/MavenSession Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MASSEMBLY-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MASSEMBLY-706.
-
Resolution: Fixed
Fixed in [r1616873|http://svn.apache.org/r1616873].
> MavenProject/MavenSession Injection as a paremeter instead as a component.
> --
>
> Key: MASSEMBLY-706
> URL: https://jira.codehaus.org/browse/MASSEMBLY-706
> Project: Maven Assembly Plugin
> Issue Type: Improvement
>Affects Versions: 2.4.1
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.5
>
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
> The following:
> {code:java}
> @Component
> protected MavenSession session;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${session}", readonly = true, required = true )
> protected MavenSession session;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-706) MavenProject/MavenSession Injection as a paremeter instead as a component.
Karl-Heinz Marbaise created MASSEMBLY-706:
-
Summary: MavenProject/MavenSession Injection as a paremeter
instead as a component.
Key: MASSEMBLY-706
URL: https://jira.codehaus.org/browse/MASSEMBLY-706
Project: Maven Assembly Plugin
Issue Type: Improvement
Affects Versions: 2.4.1
Reporter: Karl-Heinz Marbaise
Priority: Minor
The following:
{code:java}
@Component
protected MavenProject project;
{code}
has to be replaced by the following:
{code:java}
@Parameter( defaultValue = "${project}", readonly = true, required = true )
protected MavenProject project;
{code}
The following:
{code:java}
@Component
protected MavenSession session;
{code}
has to be replaced by the following:
{code:java}
@Parameter( defaultValue = "${session}", readonly = true, required = true )
protected MavenSession session;
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-706) MavenProject/MavenSession Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MASSEMBLY-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MASSEMBLY-706:
--
Fix Version/s: 2.5
> MavenProject/MavenSession Injection as a paremeter instead as a component.
> --
>
> Key: MASSEMBLY-706
> URL: https://jira.codehaus.org/browse/MASSEMBLY-706
> Project: Maven Assembly Plugin
> Issue Type: Improvement
>Affects Versions: 2.4.1
>Reporter: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.5
>
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
> The following:
> {code:java}
> @Component
> protected MavenSession session;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${session}", readonly = true, required = true )
> protected MavenSession session;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-706) MavenProject/MavenSession Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MASSEMBLY-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise reassigned MASSEMBLY-706:
-
Assignee: Karl-Heinz Marbaise
> MavenProject/MavenSession Injection as a paremeter instead as a component.
> --
>
> Key: MASSEMBLY-706
> URL: https://jira.codehaus.org/browse/MASSEMBLY-706
> Project: Maven Assembly Plugin
> Issue Type: Improvement
>Affects Versions: 2.4.1
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.5
>
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
> The following:
> {code:java}
> @Component
> protected MavenSession session;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${session}", readonly = true, required = true )
> protected MavenSession session;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MEJB-69) MavenProject/MavenSession Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MEJB-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MEJB-69.
---
Resolution: Duplicate
Assignee: Karl-Heinz Marbaise
Duplicate of MEJB-68
> MavenProject/MavenSession Injection as a paremeter instead as a component.
> --
>
> Key: MEJB-69
> URL: https://jira.codehaus.org/browse/MEJB-69
> Project: Maven EJB Plugin
> Issue Type: Improvement
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
> The following:
> {code:java}
> @Component
> protected MavenSession session;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${session}", readonly = true, required = true )
> protected MavenSession session;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MEJB-69) MavenProject/MavenSession Injection as a paremeter instead as a component.
Karl-Heinz Marbaise created MEJB-69:
---
Summary: MavenProject/MavenSession Injection as a paremeter
instead as a component.
Key: MEJB-69
URL: https://jira.codehaus.org/browse/MEJB-69
Project: Maven EJB Plugin
Issue Type: Improvement
Reporter: Karl-Heinz Marbaise
Priority: Minor
The following:
{code:java}
@Component
protected MavenProject project;
{code}
has to be replaced by the following:
{code:java}
@Parameter( defaultValue = "${project}", readonly = true, required = true )
protected MavenProject project;
{code}
The following:
{code:java}
@Component
protected MavenSession session;
{code}
has to be replaced by the following:
{code:java}
@Parameter( defaultValue = "${session}", readonly = true, required = true )
protected MavenSession session;
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MEJB-68) MavenProject/MavenSession Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MEJB-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MEJB-68.
---
Resolution: Fixed
Fixed in [r1616870|http://svn.apache.org/r1616870]
> MavenProject/MavenSession Injection as a paremeter instead as a component.
> --
>
> Key: MEJB-68
> URL: https://jira.codehaus.org/browse/MEJB-68
> Project: Maven EJB Plugin
> Issue Type: Improvement
>Affects Versions: 2.3
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.4
>
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
> The following:
> {code:java}
> @Component
> protected MavenSession session;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${session}", readonly = true, required = true )
> protected MavenSession session;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MEJB-68) MavenProject/MavenSession Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MEJB-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MEJB-68:
Fix Version/s: 2.4
> MavenProject/MavenSession Injection as a paremeter instead as a component.
> --
>
> Key: MEJB-68
> URL: https://jira.codehaus.org/browse/MEJB-68
> Project: Maven EJB Plugin
> Issue Type: Improvement
>Affects Versions: 2.3
>Reporter: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.4
>
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
> The following:
> {code:java}
> @Component
> protected MavenSession session;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${session}", readonly = true, required = true )
> protected MavenSession session;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MEJB-68) MavenProject/MavenSession Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MEJB-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise reassigned MEJB-68:
---
Assignee: Karl-Heinz Marbaise
> MavenProject/MavenSession Injection as a paremeter instead as a component.
> --
>
> Key: MEJB-68
> URL: https://jira.codehaus.org/browse/MEJB-68
> Project: Maven EJB Plugin
> Issue Type: Improvement
>Affects Versions: 2.3
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.4
>
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
> The following:
> {code:java}
> @Component
> protected MavenSession session;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${session}", readonly = true, required = true )
> protected MavenSession session;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MEJB-68) MavenProject/MavenSession Injection as a paremeter instead as a component.
Karl-Heinz Marbaise created MEJB-68:
---
Summary: MavenProject/MavenSession Injection as a paremeter
instead as a component.
Key: MEJB-68
URL: https://jira.codehaus.org/browse/MEJB-68
Project: Maven EJB Plugin
Issue Type: Improvement
Affects Versions: 2.3
Reporter: Karl-Heinz Marbaise
Priority: Minor
The following:
{code:java}
@Component
protected MavenProject project;
{code}
has to be replaced by the following:
{code:java}
@Parameter( defaultValue = "${project}", readonly = true, required = true )
protected MavenProject project;
{code}
The following:
{code:java}
@Component
protected MavenSession session;
{code}
has to be replaced by the following:
{code:java}
@Parameter( defaultValue = "${session}", readonly = true, required = true )
protected MavenSession session;
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MENFORCER-176) Throws NoSuchMethodError with Maven 2.0.x
[
https://jira.codehaus.org/browse/MENFORCER-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MENFORCER-176.
-
Resolution: Won't Fix
Assignee: Karl-Heinz Marbaise
Based on MENFORCER-200 i will close this issue.
> Throws NoSuchMethodError with Maven 2.0.x
> -
>
> Key: MENFORCER-176
> URL: https://jira.codehaus.org/browse/MENFORCER-176
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin, Standard Rules
>Affects Versions: 1.3.1
> Environment: Mac OS, JDK 1.7.0
>Reporter: Anders Hammar
>Assignee: Karl-Heinz Marbaise
>
> Building a Mojo project with Maven 2.0.x using enforcer and some rules I get
> this stacktrace:
> {quote}
> java.lang.NoSuchMethodError:
> org.apache.maven.project.MavenProject.getProjectBuilderConfiguration()Lorg/apache/maven/project/ProjectBuilderConfiguration;
> at
> org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:139)
> at
> org.apache.maven.shared.dependency.graph.internal.Maven2DependencyGraphBuilder.buildDependencyGraph(Maven2DependencyGraphBuilder.java:55)
> at
> org.apache.maven.plugins.enforcer.AbstractBanDependencies.getDependenciesToCheck(AbstractBanDependencies.java:126)
> at
> org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute(AbstractBanDependencies.java:90)
> at
> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:177)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:454)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:345)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:132)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:290)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MENFORCER-176) Throws NoSuchMethodError with Maven 2.0.x
[
https://jira.codehaus.org/browse/MENFORCER-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MENFORCER-176:
--
Fix Version/s: (was: more-investigation)
> Throws NoSuchMethodError with Maven 2.0.x
> -
>
> Key: MENFORCER-176
> URL: https://jira.codehaus.org/browse/MENFORCER-176
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin, Standard Rules
>Affects Versions: 1.3.1
> Environment: Mac OS, JDK 1.7.0
>Reporter: Anders Hammar
>
> Building a Mojo project with Maven 2.0.x using enforcer and some rules I get
> this stacktrace:
> {quote}
> java.lang.NoSuchMethodError:
> org.apache.maven.project.MavenProject.getProjectBuilderConfiguration()Lorg/apache/maven/project/ProjectBuilderConfiguration;
> at
> org.apache.maven.shared.dependency.tree.DefaultDependencyTreeBuilder.buildDependencyTree(DefaultDependencyTreeBuilder.java:139)
> at
> org.apache.maven.shared.dependency.graph.internal.Maven2DependencyGraphBuilder.buildDependencyGraph(Maven2DependencyGraphBuilder.java:55)
> at
> org.apache.maven.plugins.enforcer.AbstractBanDependencies.getDependenciesToCheck(AbstractBanDependencies.java:126)
> at
> org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute(AbstractBanDependencies.java:90)
> at
> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:177)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:454)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:345)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:132)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:290)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MENFORCER-201) MavenProject Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MENFORCER-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MENFORCER-201.
-
Resolution: Fixed
Fixed in [r1616867|http://svn.apache.org/r1616867].
> MavenProject Injection as a paremeter instead as a component.
> -
>
> Key: MENFORCER-201
> URL: https://jira.codehaus.org/browse/MENFORCER-201
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
>Affects Versions: 1.4
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 1.4
>
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
> The following:
> {code:java}
> @Component
> protected MavenSession session;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${session}", readonly = true, required = true )
> protected MavenSession session;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MENFORCER-201) MavenProject Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MENFORCER-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MENFORCER-201:
--
Description:
The following:
{code:java}
@Component
protected MavenProject project;
{code}
has to be replaced by the following:
{code:java}
@Parameter( defaultValue = "${project}", readonly = true, required = true )
protected MavenProject project;
{code}
The following:
{code:java}
@Component
protected MavenSession session;
{code}
has to be replaced by the following:
{code:java}
@Parameter( defaultValue = "${session}", readonly = true, required = true )
protected MavenSession session;
{code}
was:
The following:
{code:java}
@Component
protected MavenProject project;
{code}
has to be replaced by the following:
{code:java}
@Parameter( defaultValue = "${project}", readonly = true, required = true )
protected MavenProject project;
{code}
> MavenProject Injection as a paremeter instead as a component.
> -
>
> Key: MENFORCER-201
> URL: https://jira.codehaus.org/browse/MENFORCER-201
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
>Affects Versions: 1.4
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 1.4
>
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
> The following:
> {code:java}
> @Component
> protected MavenSession session;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${session}", readonly = true, required = true )
> protected MavenSession session;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MENFORCER-201) MavenProject Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MENFORCER-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise reassigned MENFORCER-201:
-
Assignee: Karl-Heinz Marbaise
> MavenProject Injection as a paremeter instead as a component.
> -
>
> Key: MENFORCER-201
> URL: https://jira.codehaus.org/browse/MENFORCER-201
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
>Affects Versions: 1.4
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 1.4
>
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MENFORCER-201) MavenProject Injection as a paremeter instead as a component.
[
https://jira.codehaus.org/browse/MENFORCER-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MENFORCER-201:
--
Fix Version/s: 1.4
> MavenProject Injection as a paremeter instead as a component.
> -
>
> Key: MENFORCER-201
> URL: https://jira.codehaus.org/browse/MENFORCER-201
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
>Affects Versions: 1.4
>Reporter: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 1.4
>
>
> The following:
> {code:java}
> @Component
> protected MavenProject project;
> {code}
> has to be replaced by the following:
> {code:java}
> @Parameter( defaultValue = "${project}", readonly = true, required = true )
> protected MavenProject project;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MENFORCER-201) MavenProject Injection as a paremeter instead as a component.
Karl-Heinz Marbaise created MENFORCER-201:
-
Summary: MavenProject Injection as a paremeter instead as a
component.
Key: MENFORCER-201
URL: https://jira.codehaus.org/browse/MENFORCER-201
Project: Maven Enforcer Plugin
Issue Type: Improvement
Affects Versions: 1.4
Reporter: Karl-Heinz Marbaise
Priority: Minor
The following:
{code:java}
@Component
protected MavenProject project;
{code}
has to be replaced by the following:
{code:java}
@Parameter( defaultValue = "${project}", readonly = true, required = true )
protected MavenProject project;
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCLEAN-55) maven clean seems to use old java.io API to clean the target directory
[ https://jira.codehaus.org/browse/MCLEAN-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351204#comment-351204 ] Karl-Heinz Marbaise commented on MCLEAN-55: --- In this case we need to take care of Java 1.5 as well, cause this plugin has been uplifted to at least Maven 2.2.1 which is JDK 1.5. Of course the path you described Kristian is a better solution and more flexible. > maven clean seems to use old java.io API to clean the target directory > -- > > Key: MCLEAN-55 > URL: https://jira.codehaus.org/browse/MCLEAN-55 > Project: Maven Clean Plugin > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Mark > Fix For: 3.0 > > > Problem: the old java.io API cannot handle filenames that have a bad > encoding, ie. iso-8859-1 encoded umlauts when running with LC_ALL=*.UTF-8. > To reproduce the problem do: > git clone https://github.com/jjYBdx4IL/filenameenc.git > cd filenameenc > mvn test > mvn clean # <- produces an error when trying to remove target/ > The example itself demonstrates the problem and shows a solution by using > java.nio.Files.newDirectoryStream(). -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-57) Qualifier in EJB execution doesn't filter per-execution
[ https://jira.codehaus.org/browse/MEJB-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MEJB-57: Fix Version/s: 2.4 > Qualifier in EJB execution doesn't filter per-execution > --- > > Key: MEJB-57 > URL: https://jira.codehaus.org/browse/MEJB-57 > Project: Maven EJB Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: Any >Reporter: Mykel Alvis > Fix For: 2.4 > > Attachments: classified-ejb.test.zip > > > When performing multiple (filtered) executions of the ejb:ejb goal, only the > first filtered version of the deployment descriptor is used. > In the attached case, there are two executions of ejb:ejb with different > filters (dev and prod). The deployment descriptor is set to be filtered with > different values, and yet both resultant ejb jars have precisely the same > ejb-jar.xml > Note: If I'm just doing this incorrectly, please smack me down immediately. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-67) Upgrade plexus-utils to 3.0.17
[ https://jira.codehaus.org/browse/MEJB-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351203#comment-351203 ] Karl-Heinz Marbaise commented on MEJB-67: - Unfortunately we can't upgrade, cause 3.0.17 requires Java 1.6 which would break 2.2.1 compatiblity. This should be done for 3.0 where we have at least Java 1.6. At this time it should be checked carefully. > Upgrade plexus-utils to 3.0.17 > -- > > Key: MEJB-67 > URL: https://jira.codehaus.org/browse/MEJB-67 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 3.0 > > > Upgrade plexus-utils from 3.0.15 to 3.0.17. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-67) Upgrade plexus-utils to 3.0.17
[ https://jira.codehaus.org/browse/MEJB-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MEJB-67: Fix Version/s: (was: 2.4) 3.0 > Upgrade plexus-utils to 3.0.17 > -- > > Key: MEJB-67 > URL: https://jira.codehaus.org/browse/MEJB-67 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 3.0 > > > Upgrade plexus-utils from 3.0.15 to 3.0.17. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-66) Upgrade plexus-archiver to 2.4.4
[ https://jira.codehaus.org/browse/MEJB-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MEJB-66. --- Resolution: Fixed Fixed in [r1616863|http://svn.apache.org/r1616863]. > Upgrade plexus-archiver to 2.4.4 > > > Key: MEJB-66 > URL: https://jira.codehaus.org/browse/MEJB-66 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > Upgrade of plexus-archiver from 2.4.3 to 2.4.4 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-67) Upgrade plexus-utils to 3.0.17
Karl-Heinz Marbaise created MEJB-67: --- Summary: Upgrade plexus-utils to 3.0.17 Key: MEJB-67 URL: https://jira.codehaus.org/browse/MEJB-67 Project: Maven EJB Plugin Issue Type: Improvement Affects Versions: 2.4 Reporter: Karl-Heinz Marbaise Priority: Minor Upgrade plexus-utils from 3.0.15 to 3.0.17. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-66) Upgrade plexus-archiver to 2.4.4
Karl-Heinz Marbaise created MEJB-66: --- Summary: Upgrade plexus-archiver to 2.4.4 Key: MEJB-66 URL: https://jira.codehaus.org/browse/MEJB-66 Project: Maven EJB Plugin Issue Type: Improvement Affects Versions: 2.4 Reporter: Karl-Heinz Marbaise Priority: Minor Upgrade of plexus-archiver from 2.4.3 to 2.4.4 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-67) Upgrade plexus-utils to 3.0.17
[ https://jira.codehaus.org/browse/MEJB-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MEJB-67: Fix Version/s: 2.4 > Upgrade plexus-utils to 3.0.17 > -- > > Key: MEJB-67 > URL: https://jira.codehaus.org/browse/MEJB-67 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > Upgrade plexus-utils from 3.0.15 to 3.0.17. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-66) Upgrade plexus-archiver to 2.4.4
[ https://jira.codehaus.org/browse/MEJB-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise reassigned MEJB-66: --- Assignee: Karl-Heinz Marbaise > Upgrade plexus-archiver to 2.4.4 > > > Key: MEJB-66 > URL: https://jira.codehaus.org/browse/MEJB-66 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > Upgrade of plexus-archiver from 2.4.3 to 2.4.4 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-66) Upgrade plexus-archiver to 2.4.4
[ https://jira.codehaus.org/browse/MEJB-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MEJB-66: Fix Version/s: 2.4 > Upgrade plexus-archiver to 2.4.4 > > > Key: MEJB-66 > URL: https://jira.codehaus.org/browse/MEJB-66 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > Upgrade of plexus-archiver from 2.4.3 to 2.4.4 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-688) Use maven-invoker-plugin 1.9
[ https://jira.codehaus.org/browse/MASSEMBLY-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MASSEMBLY-688: Assignee: Robert Scholte (was: Karl-Heinz Marbaise) > Use maven-invoker-plugin 1.9 > > > Key: MASSEMBLY-688 > URL: https://jira.codehaus.org/browse/MASSEMBLY-688 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Assignee: Robert Scholte >Priority: Minor > Fix For: 2.5 > > > We should update maven-invoker-plugin to 1.9 and improve setup structure for > integration tests. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MENFORCER-200) Make Plugin only 2.2.1 compatible - get rid of Maven 2.0
[ https://jira.codehaus.org/browse/MENFORCER-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MENFORCER-200. - Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1616853|http://svn.apache.org/r1616853] > Make Plugin only 2.2.1 compatible - get rid of Maven 2.0 > > > Key: MENFORCER-200 > URL: https://jira.codehaus.org/browse/MENFORCER-200 > Project: Maven Enforcer Plugin > Issue Type: Improvement >Affects Versions: 1.4 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.4 > > > Upgrade to 2.2.1 dependency instead of 2.0.X -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MENFORCER-200) Make Plugin only 2.2.1 compatible - get rid of Maven 2.0
Karl-Heinz Marbaise created MENFORCER-200: - Summary: Make Plugin only 2.2.1 compatible - get rid of Maven 2.0 Key: MENFORCER-200 URL: https://jira.codehaus.org/browse/MENFORCER-200 Project: Maven Enforcer Plugin Issue Type: Improvement Affects Versions: 1.4 Reporter: Karl-Heinz Marbaise Priority: Minor Upgrade to 2.2.1 dependency instead of 2.0.X -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MENFORCER-200) Make Plugin only 2.2.1 compatible - get rid of Maven 2.0
[ https://jira.codehaus.org/browse/MENFORCER-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MENFORCER-200: -- Fix Version/s: 1.4 > Make Plugin only 2.2.1 compatible - get rid of Maven 2.0 > > > Key: MENFORCER-200 > URL: https://jira.codehaus.org/browse/MENFORCER-200 > Project: Maven Enforcer Plugin > Issue Type: Improvement >Affects Versions: 1.4 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.4 > > > Upgrade to 2.2.1 dependency instead of 2.0.X -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-688) Use maven-invoker-plugin 1.9
[ https://jira.codehaus.org/browse/MASSEMBLY-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MASSEMBLY-688. - Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed [r1616836|http://svn.apache.org/r1616836] done by Robert Scholte. > Use maven-invoker-plugin 1.9 > > > Key: MASSEMBLY-688 > URL: https://jira.codehaus.org/browse/MASSEMBLY-688 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.5 > > > We should update maven-invoker-plugin to 1.9 and improve setup structure for > integration tests. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-453) Change Maven prerequisite to 2.2.1
[ https://jira.codehaus.org/browse/MDEP-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MDEP-453. --- Resolution: Fixed Fix Version/s: 2.9 Assignee: Robert Scholte Fixed in [r1616850|http://svn.apache.org/r1616850] > Change Maven prerequisite to 2.2.1 > -- > > Key: MDEP-453 > URL: https://jira.codehaus.org/browse/MDEP-453 > Project: Maven Dependency Plugin > Issue Type: Task >Affects Versions: 2.8 >Reporter: Robert Scholte >Assignee: Robert Scholte > Fix For: 2.9 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-688) Use maven-invoker-plugin 1.9
[ https://jira.codehaus.org/browse/MASSEMBLY-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MASSEMBLY-688: -- Fix Version/s: 2.5 > Use maven-invoker-plugin 1.9 > > > Key: MASSEMBLY-688 > URL: https://jira.codehaus.org/browse/MASSEMBLY-688 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.5 > > > We should update maven-invoker-plugin to 1.9 and improve setup structure for > integration tests. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-688) Use maven-invoker-plugin 1.9
[ https://jira.codehaus.org/browse/MASSEMBLY-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MASSEMBLY-688: -- Description: We should update maven-invoker-plugin to 1.9 and improve setup structure for integration tests. (was: We should update maven-invoker-plugin to 1.8 and improve setup structure for integration tests.) > Use maven-invoker-plugin 1.9 > > > Key: MASSEMBLY-688 > URL: https://jira.codehaus.org/browse/MASSEMBLY-688 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.5 > > > We should update maven-invoker-plugin to 1.9 and improve setup structure for > integration tests. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-688) Use maven-invoker-plugin 1.9
[ https://jira.codehaus.org/browse/MASSEMBLY-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MASSEMBLY-688: -- Summary: Use maven-invoker-plugin 1.9 (was: Use maven-invoker-plugin 1.8) > Use maven-invoker-plugin 1.9 > > > Key: MASSEMBLY-688 > URL: https://jira.codehaus.org/browse/MASSEMBLY-688 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Priority: Minor > > We should update maven-invoker-plugin to 1.8 and improve setup structure for > integration tests. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-453) Change Maven prerequisite to 2.2.1
Robert Scholte created MDEP-453: --- Summary: Change Maven prerequisite to 2.2.1 Key: MDEP-453 URL: https://jira.codehaus.org/browse/MDEP-453 Project: Maven Dependency Plugin Issue Type: Task Affects Versions: 2.8 Reporter: Robert Scholte -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5677) Fine-grained cache management
[ https://jira.codehaus.org/browse/MNG-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko closed MNG-5677. --- Resolution: Fixed Fix Version/s: 3.2.3 Refined caches API to allow fine-grained removal of entries. https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=693f8f6604f24792b4dadbacf2fbc0eb79285915 > Fine-grained cache management > - > > Key: MNG-5677 > URL: https://jira.codehaus.org/browse/MNG-5677 > Project: Maven > Issue Type: Bug > Components: Embedding >Reporter: Igor Fedorenko >Assignee: Igor Fedorenko > Fix For: 3.2.3 > > > Maven maintains a number of caches to improve performance and memory > utilization when multiple projects reference the same resource (artifact > metadata, class realms, etc). m2e needs a way to flush these caches on > per-project basis. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5677) Fine-grained cache management
[ https://jira.codehaus.org/browse/MNG-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko reassigned MNG-5677: --- Assignee: Igor Fedorenko > Fine-grained cache management > - > > Key: MNG-5677 > URL: https://jira.codehaus.org/browse/MNG-5677 > Project: Maven > Issue Type: Bug > Components: Embedding >Reporter: Igor Fedorenko >Assignee: Igor Fedorenko > > Maven maintains a number of caches to improve performance and memory > utilization when multiple projects reference the same resource (artifact > metadata, class realms, etc). m2e needs a way to flush these caches on > per-project basis. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5677) Fine-grained cache management
Igor Fedorenko created MNG-5677: --- Summary: Fine-grained cache management Key: MNG-5677 URL: https://jira.codehaus.org/browse/MNG-5677 Project: Maven Issue Type: Bug Components: Embedding Reporter: Igor Fedorenko Maven maintains a number of caches to improve performance and memory utilization when multiple projects reference the same resource (artifact metadata, class realms, etc). m2e needs a way to flush these caches on per-project basis. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-28) outputDirectory is not created before packaging
[
https://jira.codehaus.org/browse/MEJB-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MEJB-28.
---
Resolution: Fixed
Fix Version/s: 2.4
Assignee: Karl-Heinz Marbaise
This is fixed in relationship with EJB-50.
> outputDirectory is not created before packaging
> ---
>
> Key: MEJB-28
> URL: https://jira.codehaus.org/browse/MEJB-28
> Project: Maven EJB Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Ron Piterman
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.4
>
>
> When using the jar plugin, outputDirectory is being cerated prior to creating
> the jar.
> The ejb plugin however fails if specifying an outputDirectory which does not
> exist -
> So, specifying something like ${project.build.directory}/jar will always fail
> after a clean.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MEJB-28) outputDirectory is not created before packaging
[
https://jira.codehaus.org/browse/MEJB-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351181#comment-351181
]
Karl-Heinz Marbaise edited comment on MEJB-28 at 8/8/14 10:36 AM:
--
This is fixed in relationship with MEJB-50.
was (Author: khmarbaise):
This is fixed in relationship with EJB-50.
> outputDirectory is not created before packaging
> ---
>
> Key: MEJB-28
> URL: https://jira.codehaus.org/browse/MEJB-28
> Project: Maven EJB Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Ron Piterman
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.4
>
>
> When using the jar plugin, outputDirectory is being cerated prior to creating
> the jar.
> The ejb plugin however fails if specifying an outputDirectory which does not
> exist -
> So, specifying something like ${project.build.directory}/jar will always fail
> after a clean.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MEJB-58) Documentation fails to mention where and how the plugin gets ejb-jar.xml from
[ https://jira.codehaus.org/browse/MEJB-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MEJB-58. --- Resolution: Fixed Fixed in [r1616804|http://svn.apache.org/r1616804]. Created a parameter to influence the location of ejb-jar.xml file with an appropriate default value. > Documentation fails to mention where and how the plugin gets ejb-jar.xml from > - > > Key: MEJB-58 > URL: https://jira.codehaus.org/browse/MEJB-58 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.3 > Environment: na >Reporter: paul hinds >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > I have a build failing since the ejb plugin can not find ejb-jar.xml and the > documentation conspicuously fails to mention where it needs to be. > http://maven.apache.org/plugins/maven-ejb-plugin/index.html > All this plugin does is make a jar with some predefined resources so it is > important that the docs explain what it is doing. Maven3 hardcodes various > locations of files and if they are not documented it is not possible to use > the system. > Previous maven versions let you defined where ejb-jar.xml comes from, now it > has to be somewhere specific but where it needs to be is only specified in > the source code. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-58) Documentation fails to mention where and how the plugin gets ejb-jar.xml from
[ https://jira.codehaus.org/browse/MEJB-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MEJB-58: Fix Version/s: (was: more-investigation) 2.4 > Documentation fails to mention where and how the plugin gets ejb-jar.xml from > - > > Key: MEJB-58 > URL: https://jira.codehaus.org/browse/MEJB-58 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.3 > Environment: na >Reporter: paul hinds >Priority: Minor > Fix For: 2.4 > > > I have a build failing since the ejb plugin can not find ejb-jar.xml and the > documentation conspicuously fails to mention where it needs to be. > http://maven.apache.org/plugins/maven-ejb-plugin/index.html > All this plugin does is make a jar with some predefined resources so it is > important that the docs explain what it is doing. Maven3 hardcodes various > locations of files and if they are not documented it is not possible to use > the system. > Previous maven versions let you defined where ejb-jar.xml comes from, now it > has to be somewhere specific but where it needs to be is only specified in > the source code. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-58) Documentation fails to mention where and how the plugin gets ejb-jar.xml from
[ https://jira.codehaus.org/browse/MEJB-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise reassigned MEJB-58: --- Assignee: Karl-Heinz Marbaise > Documentation fails to mention where and how the plugin gets ejb-jar.xml from > - > > Key: MEJB-58 > URL: https://jira.codehaus.org/browse/MEJB-58 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.3 > Environment: na >Reporter: paul hinds >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > I have a build failing since the ejb plugin can not find ejb-jar.xml and the > documentation conspicuously fails to mention where it needs to be. > http://maven.apache.org/plugins/maven-ejb-plugin/index.html > All this plugin does is make a jar with some predefined resources so it is > important that the docs explain what it is doing. Maven3 hardcodes various > locations of files and if they are not documented it is not possible to use > the system. > Previous maven versions let you defined where ejb-jar.xml comes from, now it > has to be somewhere specific but where it needs to be is only specified in > the source code. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-63) outputDirectory is treated differently to ear, war plugins
[
https://jira.codehaus.org/browse/MEJB-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351174#comment-351174
]
Karl-Heinz Marbaise commented on MEJB-63:
-
Currently the EJB plugin uses the following:
{code:java}
@Parameter( property = "outputDirectory", defaultValue =
"${project.build.outputDirectory}" )
private File outputDirectory;
{code}
which should be changed into (From maven-jar-plugin):
{code:java}
@Parameter( defaultValue = "${project.build.directory}", required = true )
private File outputDirectory;
{code}
This would make the behaviour more consistent.
> outputDirectory is treated differently to ear, war plugins
> --
>
> Key: MEJB-63
> URL: https://jira.codehaus.org/browse/MEJB-63
> Project: Maven EJB Plugin
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Honza Brázdil
> Fix For: 3.0
>
>
> Property outputDirectory is treated differently then in ear and war plugin.
> In ear and war plugin it's place where the resulting package is stored, in
> ejb plugin it is place where the plugin takes files to package.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MEJB-63) outputDirectory is treated differently to ear, war plugins
[ https://jira.codehaus.org/browse/MEJB-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MEJB-63: Fix Version/s: (was: more-investigation) 3.0 > outputDirectory is treated differently to ear, war plugins > -- > > Key: MEJB-63 > URL: https://jira.codehaus.org/browse/MEJB-63 > Project: Maven EJB Plugin > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Honza Brázdil > Fix For: 3.0 > > > Property outputDirectory is treated differently then in ear and war plugin. > In ear and war plugin it's place where the resulting package is stored, in > ejb plugin it is place where the plugin takes files to package. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-50) Empty src/main/java causes ejb plugin to fail
[
https://jira.codehaus.org/browse/MEJB-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MEJB-50.
---
Resolution: Fixed
Assignee: Karl-Heinz Marbaise
Fixed in [r1616786|http://svn.apache.org/r1616786].
> Empty src/main/java causes ejb plugin to fail
> -
>
> Key: MEJB-50
> URL: https://jira.codehaus.org/browse/MEJB-50
> Project: Maven EJB Plugin
> Issue Type: Bug
>Affects Versions: 2.2.1
> Environment: Apache Maven 2.2.1 (rdebian-1)
> Java version: 1.6.0_22
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux" version: "2.6.32-24-generic" arch: "i386" Family: "unix"
> (Ubuntu 10.04)
>Reporter: Joe Littlejohn
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.4
>
>
> I have a created a simple project that includes a module with a packaging
> type of ejb. This module does not yet contain any Java classes. When I run
> {{mvn clean package}} I get the following error:
> {{There was a problem creating the EJB archive:
> /home/jlittlej/workspace/todo/trunk/ToDo-Core/target/classes isn't a
> directory.}}
> If the packaging type is jar, this error does not occur - a normal jar that
> doesn't contain any classes is built. If the packaging type is ejb, the build
> fails.
> Full trace:
> {noformat}
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: There was a problem
> creating the EJB archive:
> /home/jlittlej/workspace/todo/trunk/ToDo-Core/target/classes isn't a
> directory.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: There was a
> problem creating the EJB archive:
> /home/jlittlej/workspace/todo/trunk/ToDo-Core/target/classes isn't a
> directory.
> at org.apache.maven.plugin.ejb.EjbMojo.execute(EjbMojo.java:256)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> ... 17 more
> Caused by: org.codehaus.plexus.archiver.ArchiverException:
> /home/jlittlej/workspace/todo/trunk/ToDo-Core/target/classes isn't a
> directory.
> at
> org.codehaus.plexus.archiver.AbstractArchiver.addFileSet(AbstractArchiver.java:208)
> at
> org.codehaus.plexus.archiver.AbstractArchiver.addDirectory(AbstractArchiver.java:194)
> at
> org.codehaus.plexus.archiver.AbstractArchiver.addDirectory(AbstractArchiver.java:182)
> at org.apache.maven.plugin.ejb.EjbMojo.execute(EjbMojo.java:244)
> ... 19 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MEJB-50) Empty src/main/java causes ejb plugin to fail
[
https://jira.codehaus.org/browse/MEJB-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MEJB-50:
Fix Version/s: (was: more-investigation)
2.4
> Empty src/main/java causes ejb plugin to fail
> -
>
> Key: MEJB-50
> URL: https://jira.codehaus.org/browse/MEJB-50
> Project: Maven EJB Plugin
> Issue Type: Bug
>Affects Versions: 2.2.1
> Environment: Apache Maven 2.2.1 (rdebian-1)
> Java version: 1.6.0_22
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux" version: "2.6.32-24-generic" arch: "i386" Family: "unix"
> (Ubuntu 10.04)
>Reporter: Joe Littlejohn
>Priority: Minor
> Fix For: 2.4
>
>
> I have a created a simple project that includes a module with a packaging
> type of ejb. This module does not yet contain any Java classes. When I run
> {{mvn clean package}} I get the following error:
> {{There was a problem creating the EJB archive:
> /home/jlittlej/workspace/todo/trunk/ToDo-Core/target/classes isn't a
> directory.}}
> If the packaging type is jar, this error does not occur - a normal jar that
> doesn't contain any classes is built. If the packaging type is ejb, the build
> fails.
> Full trace:
> {noformat}
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: There was a problem
> creating the EJB archive:
> /home/jlittlej/workspace/todo/trunk/ToDo-Core/target/classes isn't a
> directory.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: There was a
> problem creating the EJB archive:
> /home/jlittlej/workspace/todo/trunk/ToDo-Core/target/classes isn't a
> directory.
> at org.apache.maven.plugin.ejb.EjbMojo.execute(EjbMojo.java:256)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> ... 17 more
> Caused by: org.codehaus.plexus.archiver.ArchiverException:
> /home/jlittlej/workspace/todo/trunk/ToDo-Core/target/classes isn't a
> directory.
> at
> org.codehaus.plexus.archiver.AbstractArchiver.addFileSet(AbstractArchiver.java:208)
> at
> org.codehaus.plexus.archiver.AbstractArchiver.addDirectory(AbstractArchiver.java:194)
> at
> org.codehaus.plexus.archiver.AbstractArchiver.addDirectory(AbstractArchiver.java:182)
> at org.apache.maven.plugin.ejb.EjbMojo.execute(EjbMojo.java:244)
> ... 19 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MEJB-64) Upgrade to Maven 2.2.1 compatiblity
[ https://jira.codehaus.org/browse/MEJB-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351164#comment-351164 ] Karl-Heinz Marbaise commented on MEJB-64: - Fixed in [r1616765|http://svn.apache.org/r1616765]. > Upgrade to Maven 2.2.1 compatiblity > --- > > Key: MEJB-64 > URL: https://jira.codehaus.org/browse/MEJB-64 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > Upgrading to at least Maven 2.2.1 and leave 2.0 behind. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-65) Upgrade maven-filtering to 1.2
[ https://jira.codehaus.org/browse/MEJB-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MEJB-65: Fix Version/s: 2.4 > Upgrade maven-filtering to 1.2 > -- > > Key: MEJB-65 > URL: https://jira.codehaus.org/browse/MEJB-65 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Karl-Heinz Marbaise > Fix For: 2.4 > > > Currently maven-ejb uses maven-filtering 1.0 we should upgrade to newer > version. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-65) Upgrade maven-filtering to 1.2
[ https://jira.codehaus.org/browse/MEJB-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MEJB-65. --- Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1616768|http://svn.apache.org/r1616768]. > Upgrade maven-filtering to 1.2 > -- > > Key: MEJB-65 > URL: https://jira.codehaus.org/browse/MEJB-65 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise > Fix For: 2.4 > > > Currently maven-ejb uses maven-filtering 1.0 we should upgrade to newer > version. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-65) Upgrade maven-filtering to 1.2
Karl-Heinz Marbaise created MEJB-65: --- Summary: Upgrade maven-filtering to 1.2 Key: MEJB-65 URL: https://jira.codehaus.org/browse/MEJB-65 Project: Maven EJB Plugin Issue Type: Improvement Affects Versions: 2.3 Reporter: Karl-Heinz Marbaise Currently maven-ejb uses maven-filtering 1.0 we should upgrade to newer version. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-52) need to update dependency of maven-archiver to 2.5
[ https://jira.codehaus.org/browse/MEJB-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MEJB-52. --- Resolution: Fixed Assignee: Karl-Heinz Marbaise The current code of maven-ejb-plugin uses maven-archiver:2.5. So this issue is fixed. > need to update dependency of maven-archiver to 2.5 > -- > > Key: MEJB-52 > URL: https://jira.codehaus.org/browse/MEJB-52 > Project: Maven EJB Plugin > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Peter Butkovic >Assignee: Karl-Heinz Marbaise > Fix For: 2.4 > > > due to: http://jira.codehaus.org/browse/MSHARED-131 > there is a need up update dependencies to to maven-archiver-2.5 > otherwise incorrect META-INF/MANIFEST.MF files are generated, currently I'm > forced to use old 2.1 version of maven-ejb-plugin as a workaround. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-52) need to update dependency of maven-archiver to 2.5
[ https://jira.codehaus.org/browse/MEJB-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MEJB-52: Fix Version/s: 2.4 > need to update dependency of maven-archiver to 2.5 > -- > > Key: MEJB-52 > URL: https://jira.codehaus.org/browse/MEJB-52 > Project: Maven EJB Plugin > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Peter Butkovic > Fix For: 2.4 > > > due to: http://jira.codehaus.org/browse/MSHARED-131 > there is a need up update dependencies to to maven-archiver-2.5 > otherwise incorrect META-INF/MANIFEST.MF files are generated, currently I'm > forced to use old 2.1 version of maven-ejb-plugin as a workaround. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-64) Upgrade to Maven 2.2.1 compatiblity
[ https://jira.codehaus.org/browse/MEJB-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MEJB-64. --- Resolution: Fixed Fixed in [r1616754|http://svn.apache.org/r1616754]. > Upgrade to Maven 2.2.1 compatiblity > --- > > Key: MEJB-64 > URL: https://jira.codehaus.org/browse/MEJB-64 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > Upgrading to at least Maven 2.2.1 and leave 2.0 behind. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-64) Upgrade to Maven 2.2.1 compatiblity
Karl-Heinz Marbaise created MEJB-64: --- Summary: Upgrade to Maven 2.2.1 compatiblity Key: MEJB-64 URL: https://jira.codehaus.org/browse/MEJB-64 Project: Maven EJB Plugin Issue Type: Improvement Affects Versions: 2.3 Reporter: Karl-Heinz Marbaise Priority: Minor Upgrading to at least Maven 2.2.1 and leave 2.0 behind. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-64) Upgrade to Maven 2.2.1 compatiblity
[ https://jira.codehaus.org/browse/MEJB-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MEJB-64: Fix Version/s: 2.4 > Upgrade to Maven 2.2.1 compatiblity > --- > > Key: MEJB-64 > URL: https://jira.codehaus.org/browse/MEJB-64 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > Upgrading to at least Maven 2.2.1 and leave 2.0 behind. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-64) Upgrade to Maven 2.2.1 compatiblity
[ https://jira.codehaus.org/browse/MEJB-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise reassigned MEJB-64: --- Assignee: Karl-Heinz Marbaise > Upgrade to Maven 2.2.1 compatiblity > --- > > Key: MEJB-64 > URL: https://jira.codehaus.org/browse/MEJB-64 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > Upgrading to at least Maven 2.2.1 and leave 2.0 behind. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRELEASE-882) [regression] Perform fails because usage of site plugin with wrong version
[
https://jira.codehaus.org/browse/MRELEASE-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Schaible closed MRELEASE-882.
--
Resolution: Not A Bug
Actually it was a very unfortunate sequence of failures. I wanted to release
our master POM in new version 274, but I typed version 247, with the effect
that the tag got nested in subversion "../tags/v_247/v_247". The checkout then
provided the real version 247 and there were the versions declared I've seen.
Even worse, I did not recognize the real culprit, so I downgraded the release
plugin, dropped the tag in subversion (../tags/v_247) and did the release
again. Since release:prepare could now create the tag at the correct position,
performing the release worked ... unfortunately. I try to clean up currently
the mess I've created ;-)
> [regression] Perform fails because usage of site plugin with wrong version
> --
>
> Key: MRELEASE-882
> URL: https://jira.codehaus.org/browse/MRELEASE-882
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.5
>Reporter: Jörg Schaible
>
> We use M322 and define the version 3.4 for the site plugin in our POM using a
> version property. The output of help:effective-pom verifies that the
> site-plugin is declared using version 3.4. However, release:perform fails
> with (snippet):
> {noformat}
> [INFO] --- maven-release-plugin:2.5:perform (default-cli) @ master ---
> [INFO] Checking out the project to perform the release ...
> ...
> [INFO] [INFO] --- maven-site-plugin:3.0-beta-3:site (default-site) @ master
> ---
> [INFO] [WARNING] Error injecting:
> org.apache.maven.plugins.site.DefaultMavenReportExecutor
> [INFO] java.lang.NoClassDefFoundError:
> org/sonatype/aether/graph/DependencyFilter
> [INFO] at java.lang.Class.getDeclaredConstructors0(Native Method)
> [INFO] at java.lang.Class.privateGetDeclaredConstructors(Class.java:2532)
> {noformat}
> Obviously the release:perform goal of the release plugin in version 2.5 uses
> now version 3.0-beta-3 of the site plugin with is incompatible.
> When we go back to version 2.4.2 of the release plugin, it uses the correct
> (declared) version of the site plugin and the release is performed
> successfully.
> Comparing the used plugin versions during release:perform, it is not only the
> version of the site plugin that is wrong. It seems that any declared plugin
> version is simply ignored with release plugin version 2.5.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MRELEASE-882) [regression] Perform fails because usage of site plugin with wrong version
[
https://jira.codehaus.org/browse/MRELEASE-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351156#comment-351156
]
Robert Scholte commented on MRELEASE-882:
-
There are 2 things really weird:
- none of the [fixed issues of
2.5|https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144&version=19017]
seems to be related to this.
- The release perform is very straightforward: checkout the code by tag into
the {{target/checkout}}-directory and from this directory run {{mvn deploy
site-deploy}}. You could try to do the latter part by hand and it will give you
the same result. Try to figure out what has happened with the pom.
> [regression] Perform fails because usage of site plugin with wrong version
> --
>
> Key: MRELEASE-882
> URL: https://jira.codehaus.org/browse/MRELEASE-882
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.5
>Reporter: Jörg Schaible
>
> We use M322 and define the version 3.4 for the site plugin in our POM using a
> version property. The output of help:effective-pom verifies that the
> site-plugin is declared using version 3.4. However, release:perform fails
> with (snippet):
> {noformat}
> [INFO] --- maven-release-plugin:2.5:perform (default-cli) @ master ---
> [INFO] Checking out the project to perform the release ...
> ...
> [INFO] [INFO] --- maven-site-plugin:3.0-beta-3:site (default-site) @ master
> ---
> [INFO] [WARNING] Error injecting:
> org.apache.maven.plugins.site.DefaultMavenReportExecutor
> [INFO] java.lang.NoClassDefFoundError:
> org/sonatype/aether/graph/DependencyFilter
> [INFO] at java.lang.Class.getDeclaredConstructors0(Native Method)
> [INFO] at java.lang.Class.privateGetDeclaredConstructors(Class.java:2532)
> {noformat}
> Obviously the release:perform goal of the release plugin in version 2.5 uses
> now version 3.0-beta-3 of the site plugin with is incompatible.
> When we go back to version 2.4.2 of the release plugin, it uses the correct
> (declared) version of the site plugin and the release is performed
> successfully.
> Comparing the used plugin versions during release:perform, it is not only the
> version of the site plugin that is wrong. It seems that any declared plugin
> version is simply ignored with release plugin version 2.5.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MRELEASE-882) [regression] Perform fails because usage of site plugin with wrong version
Jörg Schaible created MRELEASE-882:
--
Summary: [regression] Perform fails because usage of site plugin
with wrong version
Key: MRELEASE-882
URL: https://jira.codehaus.org/browse/MRELEASE-882
Project: Maven Release Plugin
Issue Type: Bug
Components: perform
Affects Versions: 2.5
Reporter: Jörg Schaible
We use M322 and define the version 3.4 for the site plugin in our POM using a
version property. The output of help:effective-pom verifies that the
site-plugin is declared using version 3.4. However, release:perform fails with
(snippet):
{noformat}
[INFO] --- maven-release-plugin:2.5:perform (default-cli) @ master ---
[INFO] Checking out the project to perform the release ...
...
[INFO] [INFO] --- maven-site-plugin:3.0-beta-3:site (default-site) @ master ---
[INFO] [WARNING] Error injecting:
org.apache.maven.plugins.site.DefaultMavenReportExecutor
[INFO] java.lang.NoClassDefFoundError:
org/sonatype/aether/graph/DependencyFilter
[INFO] at java.lang.Class.getDeclaredConstructors0(Native Method)
[INFO] at java.lang.Class.privateGetDeclaredConstructors(Class.java:2532)
{noformat}
Obviously the release:perform goal of the release plugin in version 2.5 uses
now version 3.0-beta-3 of the site plugin with is incompatible.
When we go back to version 2.4.2 of the release plugin, it uses the correct
(declared) version of the site plugin and the release is performed successfully.
Comparing the used plugin versions during release:perform, it is not only the
version of the site plugin that is wrong. It seems that any declared plugin
version is simply ignored with release plugin version 2.5.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
