[jira] [Commented] (SUREFIRE-826) maven-surefire-plugin does not add its own plugin dependencies to the classpath
[
https://issues.apache.org/jira/browse/SUREFIRE-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595434#comment-14595434
]
Sander Verhagen commented on SUREFIRE-826:
--
Hi, Tibor. Thanks for that. It would have taken me a while to circle back to
this and then to figure out where to go what to do. I'm sure that it was a
small thing for you, but it might be beneficial for people after me. Thanks!
> maven-surefire-plugin does not add its own plugin dependencies to the
> classpath
> ---
>
> Key: SUREFIRE-826
> URL: https://issues.apache.org/jira/browse/SUREFIRE-826
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading, Maven Surefire Plugin
>Affects Versions: 2.11
> Environment: Maven 3.0.3
> Java 6
>Reporter: René Zanner
>Assignee: Tibor Digana
> Fix For: 2.19
>
>
> Currently some JAR containing a RunListener for JUnit must be located in the
> project's classpath (and pollutes the classpath with most likely unwanted
> transitive dependencies).
> An alternative is to use the 'additionalClasspathElements' configuration
> element in the maven-surefire-plugin's configuration. Unfortunately this
> cannot be used to specify another maven artifact directly - only JARs or
> class folders in the file system.
> It would be consistent to enable the usage of plugin dependencies
> ({{}} element in the {{}} section of the POM) to load
> such classes:
> {code:xml}
>
> maven-surefire-plugin
>
>
>
> listener
> some.RunListener
>
>
>
>
>
>
> some.group.id
> some-artifact-id
> ${some.version}
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MNG-5819) Failure with maven-site-plugin:stage
[
https://issues.apache.org/jira/browse/MNG-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raju Bairishetti updated MNG-5819:
--
Comment: was deleted
(was: Hi [~khmarbaise],
The problem here is ubuntu maven package is the commons-lang dependency.
*Possible fixes:*
1) You can either unpack a stand-alone Maven archive or run the following
commands
cd /usr/share/maven/lib
sudo ln -s ../../java/commons-lang.jar .
commons-lang.jar present in /usr/shar/jar. Creating a symlink should solve the
problem.
2) Bump up the maven version to 3.2.3. )
> Failure with maven-site-plugin:stage
>
>
> Key: MNG-5819
> URL: https://issues.apache.org/jira/browse/MNG-5819
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.0.5
> Environment: Apache Maven 3.0.5
> (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100)
> Maven home: /usr/share/maven
> Java version: 1.7.0_21, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.8.5", arch: "x86_64", family: "mac"
>Reporter: Karl Heinz Marbaise
>Priority: Blocker
>
> If i try to stage the site of maven itself it fails with the following
> message:
> {code}Karl-Heinzs-MacBook-Pro:maven kama$ mvn site:stage
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache Maven
> [INFO] Maven Model
> [INFO] Maven Artifact
> [INFO] Maven Plugin API
> [INFO] Maven Builder Support
> [INFO] Maven Model Builder
> [INFO] Maven Settings
> [INFO] Maven Settings Builder
> [INFO] Maven Repository Metadata Model
> [INFO] Maven Aether Provider
> [INFO] Maven Core
> [INFO] Maven Compat
> [INFO] Maven Embedder
> [INFO] Apache Maven Distribution
> [INFO]
> [INFO]
>
> [INFO] Building Apache Maven 3.3.3
> [INFO]
>
> [INFO]
> [INFO] --- maven-site-plugin:3.4:stage (default-cli) @ maven ---
> [INFO] Using this base directory for staging:
> /Users/kama/ws-git/apache/maven/target/staging
> file:///Users/kama/ws-git/apache/maven/target/staging/ - Session: Opened
> [INFO] Pushing /Users/kama/ws-git/apache/maven/target/site
> [INFO]>>> to
> file:///Users/kama/ws-git/apache/maven/target/staging/../../../components/ref/3-LATEST
> file:///Users/kama/ws-git/apache/maven/target/staging/ - Session:
> Disconnecting
> file:///Users/kama/ws-git/apache/maven/target/staging/ - Session: Disconnected
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Maven .. FAILURE [0.967s]
> [INFO] Maven Model ... SKIPPED
> [INFO] Maven Artifact SKIPPED
> [INFO] Maven Plugin API .. SKIPPED
> [INFO] Maven Builder Support . SKIPPED
> [INFO] Maven Model Builder ... SKIPPED
> [INFO] Maven Settings SKIPPED
> [INFO] Maven Settings Builder SKIPPED
> [INFO] Maven Repository Metadata Model ... SKIPPED
> [INFO] Maven Aether Provider . SKIPPED
> [INFO] Maven Core SKIPPED
> [INFO] Maven Compat .. SKIPPED
> [INFO] Maven Embedder SKIPPED
> [INFO] Apache Maven Distribution . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.662s
> [INFO] Finished at: Sun May 03 16:51:13 CEST 2015
> [INFO] Final Memory: 14M/213M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4:stage (default-cli) on project
> maven: Execution default-cli of goal
> org.apache.maven.plugins:maven-site-plugin:3.4:stage failed: A required class
> was missing while executing
> org.apache.maven.plugins:maven-site-plugin:3.4:stage:
> org/apache/commons/lang/StringUtils
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.4
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/Users/kama/.m2/repository/org/apache/maven/plugi
[jira] [Commented] (MNG-5819) Failure with maven-site-plugin:stage
[
https://issues.apache.org/jira/browse/MNG-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595312#comment-14595312
]
Raju Bairishetti commented on MNG-5819:
---
Hi [~khmarbaise],
The problem here is ubuntu maven package is the commons-lang dependency.
*Possible fixes:*
1) You can either unpack a stand-alone Maven archive or run the following
commands
cd /usr/share/maven/lib
sudo ln -s ../../java/commons-lang.jar .
commons-lang.jar present in /usr/shar/jar. Creating a symlink should solve the
problem.
2) Bump up the maven version to 3.2.3.
> Failure with maven-site-plugin:stage
>
>
> Key: MNG-5819
> URL: https://issues.apache.org/jira/browse/MNG-5819
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.0.5
> Environment: Apache Maven 3.0.5
> (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100)
> Maven home: /usr/share/maven
> Java version: 1.7.0_21, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.8.5", arch: "x86_64", family: "mac"
>Reporter: Karl Heinz Marbaise
>Priority: Blocker
>
> If i try to stage the site of maven itself it fails with the following
> message:
> {code}Karl-Heinzs-MacBook-Pro:maven kama$ mvn site:stage
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache Maven
> [INFO] Maven Model
> [INFO] Maven Artifact
> [INFO] Maven Plugin API
> [INFO] Maven Builder Support
> [INFO] Maven Model Builder
> [INFO] Maven Settings
> [INFO] Maven Settings Builder
> [INFO] Maven Repository Metadata Model
> [INFO] Maven Aether Provider
> [INFO] Maven Core
> [INFO] Maven Compat
> [INFO] Maven Embedder
> [INFO] Apache Maven Distribution
> [INFO]
> [INFO]
>
> [INFO] Building Apache Maven 3.3.3
> [INFO]
>
> [INFO]
> [INFO] --- maven-site-plugin:3.4:stage (default-cli) @ maven ---
> [INFO] Using this base directory for staging:
> /Users/kama/ws-git/apache/maven/target/staging
> file:///Users/kama/ws-git/apache/maven/target/staging/ - Session: Opened
> [INFO] Pushing /Users/kama/ws-git/apache/maven/target/site
> [INFO]>>> to
> file:///Users/kama/ws-git/apache/maven/target/staging/../../../components/ref/3-LATEST
> file:///Users/kama/ws-git/apache/maven/target/staging/ - Session:
> Disconnecting
> file:///Users/kama/ws-git/apache/maven/target/staging/ - Session: Disconnected
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Maven .. FAILURE [0.967s]
> [INFO] Maven Model ... SKIPPED
> [INFO] Maven Artifact SKIPPED
> [INFO] Maven Plugin API .. SKIPPED
> [INFO] Maven Builder Support . SKIPPED
> [INFO] Maven Model Builder ... SKIPPED
> [INFO] Maven Settings SKIPPED
> [INFO] Maven Settings Builder SKIPPED
> [INFO] Maven Repository Metadata Model ... SKIPPED
> [INFO] Maven Aether Provider . SKIPPED
> [INFO] Maven Core SKIPPED
> [INFO] Maven Compat .. SKIPPED
> [INFO] Maven Embedder SKIPPED
> [INFO] Apache Maven Distribution . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.662s
> [INFO] Finished at: Sun May 03 16:51:13 CEST 2015
> [INFO] Final Memory: 14M/213M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4:stage (default-cli) on project
> maven: Execution default-cli of goal
> org.apache.maven.plugins:maven-site-plugin:3.4:stage failed: A required class
> was missing while executing
> org.apache.maven.plugins:maven-site-plugin:3.4:stage:
> org/apache/commons/lang/StringUtils
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.4
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/Users/kama/.m2/reposito
[jira] [Closed] (SUREFIRE-706) Global lock to serialize tests even if maven runs in parallel mode
[ https://issues.apache.org/jira/browse/SUREFIRE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-706. - Resolution: Won't Fix Surefire has no notion about other modules running in parallel. This is probably Maven core issue. > Global lock to serialize tests even if maven runs in parallel mode > -- > > Key: SUREFIRE-706 > URL: https://issues.apache.org/jira/browse/SUREFIRE-706 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin > Environment: all >Reporter: Frank Meilinger >Priority: Minor > > It would be nice to serialize unit tests globally in the surefire plugin, > even if maven 3 runs with parallel mode. I know that some test providers are > able to do parallel testing itself (e.g. Junit47 provider) without running > maven in parallel or not. These test provider parallel mode can be configured > with surefire plugin configuration. E.g. none can be > used to serialize unit tests even if using the JUnit47 provider. But when > running maven 3 with -T option, the tests are still running in parallel, > depending on the parallel decision of maven 3. For code which is not able to > run in parallel (while unit tests are running, this will happen), this is a > problem. In this case the provider option none won't > help. I think it would be great (and maybe easy to implement) to have a > global surefire plugin option to globally lock the surefire plugin's > execute() method to serialize all unit tests over all parallel maven builds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-505) Excludes Surefire reports for POM files with pom packaging
[
https://issues.apache.org/jira/browse/SUREFIRE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-505.
-
Resolution: Won't Fix
We accepted a bug fix where project with pom packaging is still qualified as
regular test project if specifying dependencies to scan.
Therefore please manage the skip options by this script without forcing us to
fix it in surefire:
org.apache.maven.plugins
maven-surefire-report-plugin
${isPomPackaging}
org.codehaus.mojo
build-helper-maven-plugin
bsh-property
isPomPackaging
> Excludes Surefire reports for POM files with pom packaging
> --
>
> Key: SUREFIRE-505
> URL: https://issues.apache.org/jira/browse/SUREFIRE-505
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Report Plugin
>Affects Versions: 2.4.3
>Reporter: Siveton Vincent
>
> need to implement canGenerateReport()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-893) Unsupported provider features should throw exception
[ https://issues.apache.org/jira/browse/SUREFIRE-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595238#comment-14595238 ] Tibor Digana commented on SUREFIRE-893: --- [~krosenvold] Which features need the treatment? > Unsupported provider features should throw exception > > > Key: SUREFIRE-893 > URL: https://issues.apache.org/jira/browse/SUREFIRE-893 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Kristian Rosenvold > > The feature matrix indicates that not all providers support all features, > but some providers do not throw exceptions if the feature is attempted used. > http://maven.apache.org/plugins/maven-surefire-plugin-2.12.1/plugins/maven-surefire-plugin/featurematrix.html > Add mechanism to throw exception when a provider does not support a feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-854) surefire causes "Forked Java VM exited abnormally"
[
https://issues.apache.org/jira/browse/SUREFIRE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595237#comment-14595237
]
Tibor Digana commented on SUREFIRE-854:
---
[~mjreged]
What can we do about this issue?
Still interested?
With the rules in Maven project this could be closed without providing test
project attachment after 3 months.
> surefire causes "Forked Java VM exited abnormally"
>
>
> Key: SUREFIRE-854
> URL: https://issues.apache.org/jira/browse/SUREFIRE-854
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
>Affects Versions: 2.12
> Environment: OS name: "windows 7", version: "6.1", arch: "amd64",
> family: "windows"
>Reporter: Martin Jozef
>
> The following argline will cause an error when the variable
> ${settings.localRepository} represents example C:\Users\Martin
> Jozef\.m2\repository\etc
> Tried escaping with quotes but it does not work. Moving the repository to a
> non-space location is not an option.
> -javaagent:"${settings.localRepository}/org/springframework/spring-agent/2.5.6.SEC03/spring-agent-2.5.6.SEC03.jar"
> -Xmx700m -Xms350m -XX:PermSize=80m -XX:MaxPermSize=180m
> Error:
> Error opening zip file or JAR manifest missing : C:\Users\Martin
> Error occurred during initialization of VM
> agent library failed to init: instrument
> Testsuite: com.bipt.tiva.persistence.risk.ho.HoRiskLoadTest
> Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
> Testcase: com.bipt.tiva.persistence.risk.ho.HoRiskLoadTest:null: Caused
> an ERROR
> Forked Java VM exited abnormally. Please note the time in the report does not
> reflect the time until the VM exit.
> junit.framework.AssertionFailedError: Forked Java VM exited abnormally.
> Please note the time in the report does not reflect the time until the VM
> exit.
> at
> org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:153)
> Test com.bipt.tiva.persistence.risk.ho.HoRiskLoadTest FAILED (crashed)
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-964) TEST-*.xml files generated by Surefire throw validation warnings in Eclipse for no grammer constraints (DTD or XML schema) referenced in the document
[
https://issues.apache.org/jira/browse/SUREFIRE-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595233#comment-14595233
]
Tibor Digana commented on SUREFIRE-964:
---
[~joshunger] Feel free to attach the XSD schema here in Jira issue and we will
distribute it.
> TEST-*.xml files generated by Surefire throw validation warnings in Eclipse
> for no grammer constraints (DTD or XML schema) referenced in the document
> -
>
> Key: SUREFIRE-964
> URL: https://issues.apache.org/jira/browse/SUREFIRE-964
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 2.13
> Environment: Any OS, Eclipse Juno with m2e and m2e-wtp.
>Reporter: Josh Unger
>Priority: Trivial
>
> 1. Create a Maven project in Eclipse.
> 2. Add a single class and a single test method decorated with @Test.
> {code}
> import org.junit.Test;
> public class ATest
> {
> @Test
> public void test()
> {
>
> }
> }
> {code}
> 3. Add the necessary information to the POM -
> {code}
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.13
>
>
>
>
>
> junit
> junit
> 4.7
> test
>
>
> {code}
> 4. Close Eclipse.
> 5. Edit your .project file to include the validator -
> {code}
>
> org.eclipse.wst.validation.validationbuilder
>
>
> {code}
> 6. Build from the command line -
> > mvn install
> 7. Open Eclipse.
> EXPECTING: no warnings appear out of the box. I understand workarounds, but
> for the benefit of anyone going forward and existing users, there should be
> no warnings.
> ACTUAL: warning appears -
> Description ResourcePathLocationType
> No grammar constraints (DTD or XML Schema) referenced in the document.
> TEST-ATest.xml /test/target/surefire-reports line 1 XML Problem
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1147) Unbounded memory usage when running MANY tests
[ https://issues.apache.org/jira/browse/SUREFIRE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1147: --- Fix Version/s: (was: 2.19) Backlog > Unbounded memory usage when running MANY tests > -- > > Key: SUREFIRE-1147 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1147 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.18.1 > Environment: win7, jdk 8u25, mvn 3.2.5 >Reporter: Laurent Claisse >Assignee: Tibor Digana > Fix For: Backlog > > Attachments: surefire-allocation-traces.png, surefire-leak.png, > surefire-leak2.png, surefire-leak3.png > > > I'm writing concurrency tests, checking that this thing is reproducible, that > other thing isn't, and so on. So i repeat tests MANY times like 100_000 (to > reproduce the leak, the test project is here: > https://github.com/vandekeiser/parallel-stream-fork-join-pool) > I see in VisualVM that the culprit is WrappedReportEntry, which indirectly > holds references to lots of byte[] and char[] (allocation traces and heap > dump pics are included in attachment) > I forked and patched maven-surefire-common, and that makes the leak go. I had > to replace WrappedReportEntry.original by a singleton fake ReportEntry. > Bebefore that i had replaced > Utf8RecodingDeferredFileOutputStream.deferredFileOutputStream by a > NullOutputStream and the leak was lesser but still here. > My fork of maven-surefire-common is there: > https://github.com/vandekeiser/maven-surefire/tree/master/maven-surefire-common. > It IS a patch so i checked the patch checkbox in the issue reporter, but it > is NOT intended to be distributed of course since it is very brutal and basic. > Also in my test project i explicitly deactivated reporting, but that doesn't > make the reporting leak go away at all: > true > false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-826) maven-surefire-plugin does not add its own plugin dependencies to the classpath
[
https://issues.apache.org/jira/browse/SUREFIRE-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-826.
-
Resolution: Fixed
Fixed in documentaion commitec31e6291a65b21772c693a70fa92603a1604ffb
http://maven.apache.org/surefire/maven-surefire-plugin/examples/junit.html
http://maven.apache.org/surefire/maven-surefire-plugin/examples/testng.html
http://maven.apache.org/surefire/maven-failsafe-plugin/examples/junit.html
http://maven.apache.org/surefire/maven-failsafe-plugin/examples/testng.html
> maven-surefire-plugin does not add its own plugin dependencies to the
> classpath
> ---
>
> Key: SUREFIRE-826
> URL: https://issues.apache.org/jira/browse/SUREFIRE-826
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading, Maven Surefire Plugin
>Affects Versions: 2.11
> Environment: Maven 3.0.3
> Java 6
>Reporter: René Zanner
>Assignee: Tibor Digana
> Fix For: 2.19
>
>
> Currently some JAR containing a RunListener for JUnit must be located in the
> project's classpath (and pollutes the classpath with most likely unwanted
> transitive dependencies).
> An alternative is to use the 'additionalClasspathElements' configuration
> element in the maven-surefire-plugin's configuration. Unfortunately this
> cannot be used to specify another maven artifact directly - only JARs or
> class folders in the file system.
> It would be consistent to enable the usage of plugin dependencies
> ({{}} element in the {{}} section of the POM) to load
> such classes:
> {code:xml}
>
> maven-surefire-plugin
>
>
>
> listener
> some.RunListener
>
>
>
>
>
>
> some.group.id
> some-artifact-id
> ${some.version}
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SUREFIRE-826) maven-surefire-plugin does not add its own plugin dependencies to the classpath
[
https://issues.apache.org/jira/browse/SUREFIRE-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-826:
--
Fix Version/s: 2.19
> maven-surefire-plugin does not add its own plugin dependencies to the
> classpath
> ---
>
> Key: SUREFIRE-826
> URL: https://issues.apache.org/jira/browse/SUREFIRE-826
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading, Maven Surefire Plugin
>Affects Versions: 2.11
> Environment: Maven 3.0.3
> Java 6
>Reporter: René Zanner
>Assignee: Tibor Digana
> Fix For: 2.19
>
>
> Currently some JAR containing a RunListener for JUnit must be located in the
> project's classpath (and pollutes the classpath with most likely unwanted
> transitive dependencies).
> An alternative is to use the 'additionalClasspathElements' configuration
> element in the maven-surefire-plugin's configuration. Unfortunately this
> cannot be used to specify another maven artifact directly - only JARs or
> class folders in the file system.
> It would be consistent to enable the usage of plugin dependencies
> ({{}} element in the {{}} section of the POM) to load
> such classes:
> {code:xml}
>
> maven-surefire-plugin
>
>
>
> listener
> some.RunListener
>
>
>
>
>
>
> some.group.id
> some-artifact-id
> ${some.version}
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MNG-5845) when in maven mojo, ClassNotFoundException slf4j-api `MessageFormatter` class
[
https://issues.apache.org/jira/browse/MNG-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
feilong updated MNG-5845:
-
Description:
*my code is*
{quote}
@Mojo(name = "hello",requiresProject = false)
public class HelloWorldMojo extends AbstractMojo{
@Override
public void execute() throws MojoExecutionException,MojoFailureException{
String[] argStrings = { "Hello world" };
FormattingTuple formattingTuple = MessageFormatter.arrayFormat("{}",
argStrings);
getLog().info(formattingTuple.getMessage());
}
}
{quote}
*when i run my plugins , show me result:*
{quote}
Caused by: java.lang.NoClassDefFoundError: org/slf4j/helpers/MessageFormatter
at com.feilong.core.log.Slf4jUtil.formatMessage(Slf4jUtil.java:77)
at
com.feilong.project.train.mojo.BaseFlowMojo.getFolderPath(BaseFlowMojo.java:72)
at
com.feilong.project.train.mojo.InvitationMojo.handleExecute(InvitationMojo.java:89)
at
com.feilong.project.train.mojo.BaseFlowMojo.execute(BaseFlowMojo.java:111)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more
Caused by: java.lang.ClassNotFoundException: org.slf4j.helpers.MessageFormatter
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
... 26 more
{quote}
*And from the log (run with -X), i see that :*
{quote}
Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
2015-04-22T19:57:37+08:00)
Maven home: D:\FeiLong Soft\Essential\Development\apache-maven-3.3.3\bin\..
Java version: 1.8.0_11, vendor: Oracle Corporation
Java home: D:\Program Files\Java\jdk1.8.0_11\jre
Default locale: zh_CN, platform encoding: GBK
OS name: "windows 7", version: "6.1", arch: "x86", family: "dos"
[DEBUG] Created new class realm maven.api
[DEBUG] Importing foreign packages into class realm maven.api
[DEBUG] Imported: javax.enterprise.inject.* < plexus.core
[DEBUG] Imported: javax.enterprise.util.* < plexus.core
[DEBUG] Imported: javax.inject.* < plexus.core
[DEBUG] Imported: org.apache.maven.* < plexus.core
[DEBUG] Imported: org.apache.maven.artifact < plexus.core
[DEBUG] Imported: org.apache.maven.classrealm < plexus.core
[DEBUG] Imported: org.apache.maven.cli < plexus.core
[DEBUG] Imported: org.apache.maven.configuration < plexus.core
[DEBUG] Imported: org.apache.maven.exception < plexus.core
[DEBUG] Imported: org.apache.maven.execution < plexus.core
[DEBUG] Imported: org.apache.maven.execution.scope < plexus.core
[DEBUG] Imported: org.apache.maven.lifecycle < plexus.core
[DEBUG] Imported: org.apache.maven.model < plexus.core
[DEBUG] Imported: org.apache.maven.monitor < plexus.core
[DEBUG] Imported: org.apache.maven.plugin < plexus.core
[DEBUG] Imported: org.apache.maven.profiles < plexus.core
[DEBUG] Imported: org.apache.maven.project < plexus.core
[DEBUG] Imported: org.apache.maven.reporting < plexus.core
[DEBUG] Imported: org.apache.maven.repository < plexus.core
[DEBUG] Imported: org.apache.maven.rtinfo < plexus.core
[DEBUG] Imported: org.apache.maven.settings < plexus.core
[DEBUG] Imported: org.apache.maven.toolchain < plexus.core
[DEBUG] Imported: org.apache.maven.usability < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.* < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.events < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core
[DEBUG] Imported: org.codehaus.classworlds < plexus.core
[DEBUG] Imported: org.codehaus.plexus.* < plexus.core
[DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core
[DEBUG] Imported: org.codehaus.plexus.component < plexus.core
[DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core
[DEBUG] Imported: org.codehaus.plexus.container < plexus.core
[DEBUG] Imported: org.codehaus.plexus.context < plexus.core
[DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core
[DEBUG] Imported: org.codehaus.plexus.logging < plexus.core
[DEBUG] Imported: org.codehaus.plexus.personality < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser <
plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.
[jira] [Updated] (MNG-5845) when in maven mojo, ClassNotFoundException slf4j-api `MessageFormatter` class
[
https://issues.apache.org/jira/browse/MNG-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
feilong updated MNG-5845:
-
Description:
*my code is *
{quote}
@Mojo(name = "hello",requiresProject = false)
public class HelloWorldMojo extends AbstractMojo{
@Override
public void execute() throws MojoExecutionException,MojoFailureException{
String[] argStrings = { "Hello world" };
FormattingTuple formattingTuple = MessageFormatter.arrayFormat("{}",
argStrings);
getLog().info(formattingTuple.getMessage());
}
}
{quote}
*when i run my plugins , show me result:*
{quote}
Caused by: java.lang.NoClassDefFoundError: org/slf4j/helpers/MessageFormatter
at com.feilong.core.log.Slf4jUtil.formatMessage(Slf4jUtil.java:77)
at
com.feilong.project.train.mojo.BaseFlowMojo.getFolderPath(BaseFlowMojo.java:72)
at
com.feilong.project.train.mojo.InvitationMojo.handleExecute(InvitationMojo.java:89)
at
com.feilong.project.train.mojo.BaseFlowMojo.execute(BaseFlowMojo.java:111)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more
Caused by: java.lang.ClassNotFoundException: org.slf4j.helpers.MessageFormatter
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
... 26 more
{quote}
*And from the log (run with -X), i see that :*
{quote}
Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
2015-04-22T19:57:37+08:00)
Maven home: D:\FeiLong Soft\Essential\Development\apache-maven-3.3.3\bin\..
Java version: 1.8.0_11, vendor: Oracle Corporation
Java home: D:\Program Files\Java\jdk1.8.0_11\jre
Default locale: zh_CN, platform encoding: GBK
OS name: "windows 7", version: "6.1", arch: "x86", family: "dos"
[DEBUG] Created new class realm maven.api
[DEBUG] Importing foreign packages into class realm maven.api
[DEBUG] Imported: javax.enterprise.inject.* < plexus.core
[DEBUG] Imported: javax.enterprise.util.* < plexus.core
[DEBUG] Imported: javax.inject.* < plexus.core
[DEBUG] Imported: org.apache.maven.* < plexus.core
[DEBUG] Imported: org.apache.maven.artifact < plexus.core
[DEBUG] Imported: org.apache.maven.classrealm < plexus.core
[DEBUG] Imported: org.apache.maven.cli < plexus.core
[DEBUG] Imported: org.apache.maven.configuration < plexus.core
[DEBUG] Imported: org.apache.maven.exception < plexus.core
[DEBUG] Imported: org.apache.maven.execution < plexus.core
[DEBUG] Imported: org.apache.maven.execution.scope < plexus.core
[DEBUG] Imported: org.apache.maven.lifecycle < plexus.core
[DEBUG] Imported: org.apache.maven.model < plexus.core
[DEBUG] Imported: org.apache.maven.monitor < plexus.core
[DEBUG] Imported: org.apache.maven.plugin < plexus.core
[DEBUG] Imported: org.apache.maven.profiles < plexus.core
[DEBUG] Imported: org.apache.maven.project < plexus.core
[DEBUG] Imported: org.apache.maven.reporting < plexus.core
[DEBUG] Imported: org.apache.maven.repository < plexus.core
[DEBUG] Imported: org.apache.maven.rtinfo < plexus.core
[DEBUG] Imported: org.apache.maven.settings < plexus.core
[DEBUG] Imported: org.apache.maven.toolchain < plexus.core
[DEBUG] Imported: org.apache.maven.usability < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.* < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.events < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core
[DEBUG] Imported: org.codehaus.classworlds < plexus.core
[DEBUG] Imported: org.codehaus.plexus.* < plexus.core
[DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core
[DEBUG] Imported: org.codehaus.plexus.component < plexus.core
[DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core
[DEBUG] Imported: org.codehaus.plexus.container < plexus.core
[DEBUG] Imported: org.codehaus.plexus.context < plexus.core
[DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core
[DEBUG] Imported: org.codehaus.plexus.logging < plexus.core
[DEBUG] Imported: org.codehaus.plexus.personality < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser <
plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.
[jira] [Updated] (MNG-5845) when in maven mojo, ClassNotFoundException slf4j-api `MessageFormatter` class
[
https://issues.apache.org/jira/browse/MNG-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
feilong updated MNG-5845:
-
Description:
my code is
@Mojo(name = "hello",requiresProject = false)
public class HelloWorldMojo extends AbstractMojo{
@Override
public void execute() throws MojoExecutionException,MojoFailureException{
String[] argStrings = { "Hello world" };
FormattingTuple formattingTuple = MessageFormatter.arrayFormat("{}",
argStrings);
getLog().info(formattingTuple.getMessage());
}
}
when i run my plugins , show me result:
Caused by: java.lang.NoClassDefFoundError: org/slf4j/helpers/MessageFormatter
at com.feilong.core.log.Slf4jUtil.formatMessage(Slf4jUtil.java:77)
at
com.feilong.project.train.mojo.BaseFlowMojo.getFolderPath(BaseFlowMojo.java:72)
at
com.feilong.project.train.mojo.InvitationMojo.handleExecute(InvitationMojo.java:89)
at
com.feilong.project.train.mojo.BaseFlowMojo.execute(BaseFlowMojo.java:111)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more
Caused by: java.lang.ClassNotFoundException: org.slf4j.helpers.MessageFormatter
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
... 26 more
And from the log (run with -X), i see that :
Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
2015-04-22T19:57:37+08:00)
Maven home: D:\FeiLong Soft\Essential\Development\apache-maven-3.3.3\bin\..
Java version: 1.8.0_11, vendor: Oracle Corporation
Java home: D:\Program Files\Java\jdk1.8.0_11\jre
Default locale: zh_CN, platform encoding: GBK
OS name: "windows 7", version: "6.1", arch: "x86", family: "dos"
[DEBUG] Created new class realm maven.api
[DEBUG] Importing foreign packages into class realm maven.api
[DEBUG] Imported: javax.enterprise.inject.* < plexus.core
[DEBUG] Imported: javax.enterprise.util.* < plexus.core
[DEBUG] Imported: javax.inject.* < plexus.core
[DEBUG] Imported: org.apache.maven.* < plexus.core
[DEBUG] Imported: org.apache.maven.artifact < plexus.core
[DEBUG] Imported: org.apache.maven.classrealm < plexus.core
[DEBUG] Imported: org.apache.maven.cli < plexus.core
[DEBUG] Imported: org.apache.maven.configuration < plexus.core
[DEBUG] Imported: org.apache.maven.exception < plexus.core
[DEBUG] Imported: org.apache.maven.execution < plexus.core
[DEBUG] Imported: org.apache.maven.execution.scope < plexus.core
[DEBUG] Imported: org.apache.maven.lifecycle < plexus.core
[DEBUG] Imported: org.apache.maven.model < plexus.core
[DEBUG] Imported: org.apache.maven.monitor < plexus.core
[DEBUG] Imported: org.apache.maven.plugin < plexus.core
[DEBUG] Imported: org.apache.maven.profiles < plexus.core
[DEBUG] Imported: org.apache.maven.project < plexus.core
[DEBUG] Imported: org.apache.maven.reporting < plexus.core
[DEBUG] Imported: org.apache.maven.repository < plexus.core
[DEBUG] Imported: org.apache.maven.rtinfo < plexus.core
[DEBUG] Imported: org.apache.maven.settings < plexus.core
[DEBUG] Imported: org.apache.maven.toolchain < plexus.core
[DEBUG] Imported: org.apache.maven.usability < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.* < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.events < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core
[DEBUG] Imported: org.codehaus.classworlds < plexus.core
[DEBUG] Imported: org.codehaus.plexus.* < plexus.core
[DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core
[DEBUG] Imported: org.codehaus.plexus.component < plexus.core
[DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core
[DEBUG] Imported: org.codehaus.plexus.container < plexus.core
[DEBUG] Imported: org.codehaus.plexus.context < plexus.core
[DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core
[DEBUG] Imported: org.codehaus.plexus.logging < plexus.core
[DEBUG] Imported: org.codehaus.plexus.personality < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser <
plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException <
plexus
[jira] [Updated] (MNG-5845) when in maven mojo, ClassNotFoundException slf4j-api `MessageFormatter` class
[ https://issues.apache.org/jira/browse/MNG-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] feilong updated MNG-5845: - Environment: window7; maven 3.3.3; my custom maven plugin dependencies org.apache.maven maven-core 3.3.3 org.apache.maven maven-plugin-api 3.3.3 org.apache.maven.plugin-tools maven-plugin-annotations 3.4 provided org.codehaus.plexus plexus-component-annotations 1.6 provided org.codehaus.plexus plexus-container-default 1.6 org.codehaus.plexus plexus-interactivity-api 1.0-alpha-6 plexus plexus-utils org.codehaus.plexus plexus-utils 3.0.22 org.apache.maven.plugin-testing maven-plugin-testing-harness 3.3.0 test org.slf4j slf4j-api 1.7.12 org.slf4j slf4j-log4j12 1.7.12 was: window7 maven 3.3.3 my custom maven plugin dependencies org.apache.maven maven-core 3.3.3 org.apache.maven maven-plugin-api 3.3.3 org.apache.maven.plugin-tools maven-plugin-annotations 3.4 provided org.codehaus.plexus plexus-component-annotations 1.6 provided org.codehaus.plexus plexus-container-default 1.6 org.codehaus.plexus plexus-interactivity-api 1.0-alpha-6 plexus plexus-utils org.codehaus.plexus plexus-utils 3.0.22 org.apache.maven.plugin-testing maven-plugin-testing-harness 3.3.0 test org.slf4j slf4j-api 1.7.12 org.slf4j slf4j-log4j12 1.7.12 > when in maven mojo, ClassNotFoundException slf4j-api `MessageFormatter` class > - > > Key: MNG-5845 > URL: https://issues.apache.org/jira/browse/MNG-5845 > Project: Maven > Issue Type: Bug > Components: Class Loading >Affects Versions: 3.3.3 > Environment: window7; > maven 3.3.3; > my custom maven plugin dependencies > > > > org.apache.maven > maven-core > 3.3.3 > > > org.apache.maven > maven-plugin-api > 3.3.3 > > > > org.apache.maven.plugin-tools > maven-plugin-annotations > 3.4 > provided > > > > org.codehaus.plexus > plexus-component-annotations > 1.6 >
[jira] [Created] (MNG-5845) when in maven mojo, ClassNotFoundException slf4j-api `MessageFormatter` class
feilong created MNG-5845:
Summary: when in maven mojo, ClassNotFoundException slf4j-api
`MessageFormatter` class
Key: MNG-5845
URL: https://issues.apache.org/jira/browse/MNG-5845
Project: Maven
Issue Type: Bug
Components: Class Loading
Affects Versions: 3.3.3
Environment: window7
maven 3.3.3
my custom maven plugin dependencies
org.apache.maven
maven-core
3.3.3
org.apache.maven
maven-plugin-api
3.3.3
org.apache.maven.plugin-tools
maven-plugin-annotations
3.4
provided
org.codehaus.plexus
plexus-component-annotations
1.6
provided
org.codehaus.plexus
plexus-container-default
1.6
org.codehaus.plexus
plexus-interactivity-api
1.0-alpha-6
plexus
plexus-utils
org.codehaus.plexus
plexus-utils
3.0.22
org.apache.maven.plugin-testing
maven-plugin-testing-harness
3.3.0
test
org.slf4j
slf4j-api
1.7.12
org.slf4j
slf4j-log4j12
1.7.12
Reporter: feilong
my code is
@Mojo(name = "hello",requiresProject = false)
public class HelloWorldMojo extends AbstractMojo{
@Override
public void execute() throws MojoExecutionException,MojoFailureException{
String[] argStrings = { "Hello world" };
FormattingTuple formattingTuple = MessageFormatter.arrayFormat("{}",
argStrings);
getLog().info(formattingTuple.getMessage());
}
}
when i run my plugins , show me result:
Caused by: java.lang.NoClassDefFoundError: org/slf4j/helpers/MessageFormatter
at com.feilong.core.log.Slf4jUtil.formatMessage(Slf4jUtil.java:77)
at
com.feilong.project.train.mojo.BaseFlowMojo.getFolderPath(BaseFlowMojo.java:72)
at
com.feilong.project.train.mojo.InvitationMojo.handleExecute(InvitationMojo.java:89)
at
com.feilong.project.train.mojo.BaseFlowMojo.execute(BaseFlowMojo.java:111)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more
Caused by: java.lang.ClassNotFoundException: org.slf4j.helpers.MessageFormatter
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
... 26 more
And from the log (run with -X), i see that :
Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
2015-04-22T19:57:37+08:00)
Maven home: D:\FeiLong Soft\Essential\Development\apache-maven-3.3.3\bin\..
Java version: 1.8.0_11, vendor: Oracle Corporation
Java home: D:\Program Files\Java\jdk1.8.0_11\jre
Default locale: zh_CN, platform encoding: GBK
OS name: "windows 7", version: "6.1", arch: "x86", family: "dos"
[DEBUG] Created new class realm maven.api
[DEBUG] Importing foreign packages into class realm maven.api
[DEBUG] Imported: javax.enterprise.inject.* < plexus.core
[DEBUG] Imported: javax.enterprise.util.* < plexus.core
[DEBUG] Imported: javax.inject.* < plexus.core
[DEBUG] Imported: org.apache.maven.* < plexus.core
[DEBUG] Imported: org.apache.maven.artifact < plexus.core
[DEBUG] Imported: org.apache.maven.classrealm < plexus.core
[DEBUG] Imported: org.apache.maven.cli < plexus.core
[DEBUG] Imported: org.apache.maven.configuration < plexus.core
[DEBUG] Imported: org.apache.maven.exception < plexus.core
[DEBUG] Imported: org.apache.maven.execution < plexus.core
[DEBUG] Imported: org.apache.maven.execution.scope < plexus.core
[DEBUG] Imported: org.apache.maven.lifecycle < plexus.core
[DEBUG] Imp
[jira] [Commented] (MEJB-82) Ability to add additional files to the META-INF directory
[ https://issues.apache.org/jira/browse/MEJB-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595131#comment-14595131 ] Alex Alvarez commented on MEJB-82: -- Doesn't work if you want to create different deployments with slighty different configurations. i.e. if you have multiple configurations, you will have to create a POM for each one, even if you just need slight configuration changes. projA/META-INF/ejb-jar.xml projA/META-INF/weblogic-ejb-jar.xml projB/META-INF/ejb-jar.xml projB/META-INF/weblogic-ejb-jar.xml projC/META-INF/ejb-jar.xml projC/META-INF/weblogic-ejb-jar.xml As most application servers require some sort of extension anyway the setting where you can specify a single a ejb-jar.xml only works for the most simple of cases. > Ability to add additional files to the META-INF directory > - > > Key: MEJB-82 > URL: https://issues.apache.org/jira/browse/MEJB-82 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Alexandre Alvarez >Assignee: Karl Heinz Marbaise > > Currently it is possible to specify the ejb-jar.xml to use via the ejbJar > property. However, some containers require additional configuration files > (i.e. weblogic-ejb-jar.xml), so it would be helpful to be able to specify a > META-INF folder (with filters) to package. > > projA/META-INF/ejb-jar.xml > projA/META-INF/weblogic-ejb-jar.xml > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MCLEAN-63) Make naming of properties consistent
[
https://issues.apache.org/jira/browse/MCLEAN-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MCLEAN-63:
--
Fix Version/s: 2.7
> Make naming of properties consistent
>
>
> Key: MCLEAN-63
> URL: https://issues.apache.org/jira/browse/MCLEAN-63
> Project: Maven Clean Plugin
> Issue Type: Improvement
>Affects Versions: 2.6.1
>Reporter: Karl Heinz Marbaise
> Fix For: 2.7
>
>
> The list of properties looks like this:
> {code}
> @Parameter( property = "clean.verbose" )
> @Parameter( property = "clean.followSymLinks", defaultValue = "false" )
> @Parameter( property = "clean.skip", defaultValue = "false" )
> @Parameter( property = "maven.clean.failOnError", defaultValue = "true" )
> @Parameter( property = "maven.clean.retryOnError", defaultValue = "true" )
> @Parameter( property = "clean.excludeDefaultDirectories", defaultValue =
> "false" )
> {code}
> The property names should follow the naming convention:
> {{maven.PLUGIN.WhatEver}} So {{clean.verbose}} should be changed into
> {{maven.clean.verbose}}, {{clean.followSymLinks}} should be changed into
> {{maven.clean.followSymLinks}}, {{clean.skip}} should be changed into
> {{maven.clean.skip}}, and {{clean.excludeDefaultDirectories}} should be
> changed into {{maven.clean.excludeDefaultDirectories}}.
> The old properties {{clean.*}} should be marked deprecated and a WARNING
> should be emitted. With version 3.X they can be replaced completely.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MCLEAN-63) Make naming of properties consistent
[
https://issues.apache.org/jira/browse/MCLEAN-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MCLEAN-63:
--
Description:
The list of properties looks like this:
{code}
@Parameter( property = "clean.verbose" )
@Parameter( property = "clean.followSymLinks", defaultValue = "false" )
@Parameter( property = "clean.skip", defaultValue = "false" )
@Parameter( property = "maven.clean.failOnError", defaultValue = "true" )
@Parameter( property = "maven.clean.retryOnError", defaultValue = "true" )
@Parameter( property = "clean.excludeDefaultDirectories", defaultValue =
"false" )
{code}
The property names should follow the naming convention:
{{maven.PLUGIN.WhatEver}} So {{clean.verbose}} should be changed into
{{maven.clean.verbose}}, {{clean.followSymLinks}} should be changed into
{{maven.clean.followSymLinks}}, {{clean.skip}} should be changed into
{{maven.clean.skip}}, and {{clean.excludeDefaultDirectories}} should be changed
into {{maven.clean.excludeDefaultDirectories}}.
The old properties {{clean.*}} should be marked deprecated and a WARNING should
be emitted. With version 3.X they can be replaced completely.
was:
The list of properties looks like this:
{code}
@Parameter( property = "clean.verbose" )
@Parameter( property = "clean.followSymLinks", defaultValue = "false" )
@Parameter( property = "clean.skip", defaultValue = "false" )
@Parameter( property = "maven.clean.failOnError", defaultValue = "true" )
@Parameter( property = "maven.clean.retryOnError", defaultValue = "true" )
@Parameter( property = "clean.excludeDefaultDirectories", defaultValue =
"false" )
{code}
The property names should follow the naming convention:
{{maven.PLUGIN.WhatEver}} So {{clean.verbose}} should be changed into
{{maven.clean.verbose}}, {{clean.followSymLinks}} should be changed into
{{maven.clean.followSymLinks}}, {{clean.skip}} should be changed into
{{maven.clean.skip}}, and {{clean.excludeDefaultDirectories}} should be changed
into {{maven.clean.excludeDefaultDirectories}}.
The old properties {{clean.*}} should be marked deprecated and a WARNING should
be emitted. With version 3.X they can be replaced completely.
> Make naming of properties consistent
>
>
> Key: MCLEAN-63
> URL: https://issues.apache.org/jira/browse/MCLEAN-63
> Project: Maven Clean Plugin
> Issue Type: Improvement
>Affects Versions: 2.6.1
>Reporter: Karl Heinz Marbaise
> Fix For: 2.7
>
>
> The list of properties looks like this:
> {code}
> @Parameter( property = "clean.verbose" )
> @Parameter( property = "clean.followSymLinks", defaultValue = "false" )
> @Parameter( property = "clean.skip", defaultValue = "false" )
> @Parameter( property = "maven.clean.failOnError", defaultValue = "true" )
> @Parameter( property = "maven.clean.retryOnError", defaultValue = "true" )
> @Parameter( property = "clean.excludeDefaultDirectories", defaultValue =
> "false" )
> {code}
> The property names should follow the naming convention:
> {{maven.PLUGIN.WhatEver}} So {{clean.verbose}} should be changed into
> {{maven.clean.verbose}}, {{clean.followSymLinks}} should be changed into
> {{maven.clean.followSymLinks}}, {{clean.skip}} should be changed into
> {{maven.clean.skip}}, and {{clean.excludeDefaultDirectories}} should be
> changed into {{maven.clean.excludeDefaultDirectories}}.
> The old properties {{clean.*}} should be marked deprecated and a WARNING
> should be emitted. With version 3.X they can be replaced completely.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MCLEAN-63) Make naming of properties consistent
Karl Heinz Marbaise created MCLEAN-63:
-
Summary: Make naming of properties consistent
Key: MCLEAN-63
URL: https://issues.apache.org/jira/browse/MCLEAN-63
Project: Maven Clean Plugin
Issue Type: Improvement
Affects Versions: 2.6.1
Reporter: Karl Heinz Marbaise
The list of properties looks like this:
{code}
@Parameter( property = "clean.verbose" )
@Parameter( property = "clean.followSymLinks", defaultValue = "false" )
@Parameter( property = "clean.skip", defaultValue = "false" )
@Parameter( property = "maven.clean.failOnError", defaultValue = "true" )
@Parameter( property = "maven.clean.retryOnError", defaultValue = "true" )
@Parameter( property = "clean.excludeDefaultDirectories", defaultValue =
"false" )
{code}
The property names should follow the naming convention:
{{maven.PLUGIN.WhatEver}} So {{clean.verbose}} should be changed into
{{maven.clean.verbose}}, {{clean.followSymLinks}} should be changed into
{{maven.clean.followSymLinks}}, {{clean.skip}} should be changed into
{{maven.clean.skip}}, and {{clean.excludeDefaultDirectories}} should be changed
into {{maven.clean.excludeDefaultDirectories}}.
The old properties {{clean.*}} should be marked deprecated and a WARNING should
be emitted. With version 3.X they can be replaced completely.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MWAR-350) Add Skip Parameter to Skip the process
[
https://issues.apache.org/jira/browse/MWAR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14594986#comment-14594986
]
Karl Heinz Marbaise commented on MWAR-350:
--
I have taken a look at the patch. First i would name the property not
{{maven.deploy.skip}} i would name it {{maven.war.skip}} otherwise users will
mistaken with other plugins apart from that maven-war-plugin does not really do
the deployment.
I would suggest to implement the skip like this:
{code:java}
if ( skip )
{
getLog().info( "WAR generation is skipped." );
return;
}
{code}
Furthermore it would be nice having an integration tests which shows the
intendant behaviour.
> Add Skip Parameter to Skip the process
> --
>
> Key: MWAR-350
> URL: https://issues.apache.org/jira/browse/MWAR-350
> Project: Maven WAR Plugin
> Issue Type: New Feature
>Affects Versions: 2.6
> Environment: Maven 3.3.3
> maven-war-plugin 2.6
>Reporter: Keshan De Silva
>Priority: Trivial
> Fix For: 2.7
>
> Attachments: Maven_War_Skip.patch
>
>
> * It will be usefull if maven-war plugin has a skip configuration as in most
> of the plugins have.
> {code:xml}
> org.apache.maven.plugins
> maven-war-plugin
> 2.6
>
> true
>
> {code}
> (I have attached a patch file)
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
