[jira] [Updated] (MCOMPILER-318) Groovy files not been compiled when used with java9 spring boot

2017-12-12 Thread Yugant H Shah (JIRA)

 [ 
https://issues.apache.org/jira/browse/MCOMPILER-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yugant H Shah updated MCOMPILER-318:

Priority: Critical  (was: Major)

> Groovy files not been compiled when used with java9 spring boot
> ---
>
> Key: MCOMPILER-318
> URL: https://issues.apache.org/jira/browse/MCOMPILER-318
> Project: Maven Compiler Plugin
>  Issue Type: Bug
>Affects Versions: 3.6.2, 3.7.0
>Reporter: Yugant H Shah
>Priority: Critical
> Attachments: JigsawTest.zip
>
>
> Compiling java9+ groovy + maven code base does not compile groovy files.
> Attached is the sample project
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile 
> (default-compile) on project api: Compilation failure: Compilation failure:
> [ERROR] lombok/dummy/ForceNewRound0.java:[1,1] file should be on source path, 
> or on patch path for module
> [ERROR] 
> /Users/yushah/home/git/JigsawTest/com.allstate.jigsaw.api/src/main/java/com/allstate/jigsaw/ServiceA.java:[24,32]
>  cannot find symbol
> [ERROR] symbol:   class GroovyService
> [ERROR] location: package com.allstate.jigsaw
> [ERROR] -> [Help 1]
> [ERROR] 



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


[jira] [Commented] (DOXIASITETOOLS-182) create DocumentContent interface to model SiteRendererSink output

2017-12-12 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/DOXIASITETOOLS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288703#comment-16288703
 ] 

Hudson commented on DOXIASITETOOLS-182:
---

Build succeeded in Jenkins: Maven TLP » maven-doxia-sitetools » master #5

See 
https://builds.apache.org/job/maven-box/job/maven-doxia-sitetools/job/master/5/

> create DocumentContent interface to model SiteRendererSink output
> -
>
> Key: DOXIASITETOOLS-182
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-182
> Project: Maven Doxia Sitetools
>  Issue Type: Improvement
>  Components: Site renderer
>Affects Versions: 1.7.5
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
> Fix For: 1.8
>
>
> when merging document content into template, the fact that the document 
> content has been created with a Doxia Sink has no meaning: what is important 
> is that the useful output fields are available (title, date, authors, head, 
> body, doc rendering context)
> creating an interface for this output will ease understanding of the 
> mechanics (and avoid noise about the specific Sink)



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


[GitHub] maven-surefire issue #166: Support filtering of tests from Base Class (TestN...

2017-12-12 Thread Tibor17
Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/166
  
@krmahadevan 
There is one failing integration test:
[unix] Failed tests:   shouldNotRunExcludedClassesAndMethods[0]
(org.apache.maven.surefire.its.TestMultipleMethodPatternsTestNGIT): wrong 
number of tests expected:<11> but was:<12>

What is wrong?
Why it failed?



---


[jira] [Commented] (SUREFIRE-1452) Support filtering of tests from Base Class (TestNG)

2017-12-12 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288491#comment-16288491
 ] 

ASF GitHub Bot commented on SUREFIRE-1452:
--

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/166
  
@krmahadevan 
I have created a branch `SUREFIRE-1452`, changed your commit [1] according 
to our needs and now the build is running [2].
[1]: 
https://git1-us-west.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=946bf1eb8d5b56dcd10ec44c463d2f6014d01a95
[2]: 
https://builds.apache.org/view/M-R/view/Maven/job/maven-surefire-pipeline/job/SUREFIRE-1452/



> Support filtering of tests from Base Class (TestNG)
> ---
>
> Key: SUREFIRE-1452
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1452
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
> support
>Reporter: Tibor Digana
>Assignee: Tibor Digana
> Fix For: 2.21.0.Jigsaw
>
>
> User has two test classes.
> An abstract base class called {{BaseTest}} which contains an {{@Test}} method 
> called {{testMethodFromBase}}. A child class called {{ChildTest}} which 
> extends {{BaseTest}}.
> User attempts at running the TestNG test via 
> {{-Dtest=ChildTest#testMethodFromBase}}.
> This PR basically addresses only the TestNG portion of the bug 
> https://github.com/cbeust/testng/issues/1563



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


[GitHub] maven-surefire issue #166: Support filtering of tests from Base Class (TestN...

2017-12-12 Thread Tibor17
Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/166
  
@krmahadevan 
I have created a branch `SUREFIRE-1452`, changed your commit [1] according 
to our needs and now the build is running [2].
[1]: 
https://git1-us-west.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=946bf1eb8d5b56dcd10ec44c463d2f6014d01a95
[2]: 
https://builds.apache.org/view/M-R/view/Maven/job/maven-surefire-pipeline/job/SUREFIRE-1452/



---


[jira] [Created] (MJMOD-8) NPE on create

2017-12-12 Thread Victor Romero (JIRA)
Victor Romero created MJMOD-8:
-

 Summary: NPE on create
 Key: MJMOD-8
 URL: https://issues.apache.org/jira/browse/MJMOD-8
 Project: Maven JMod Plugin
  Issue Type: Bug
Affects Versions: 3.0.0-alpha-2
 Environment: Apache Maven 3.5.0
Maven home: /usr/share/maven
Java version: 9-Ubuntu, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-9-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.13.0-19-generic", arch: "amd64", family: "unix"

Reporter: Victor Romero


Trying to compile with latest snapshot version (as I saw another NPE issue for 
the latest released version here) gets a NPE.

Steps to reproduce:

git clone https://github.com/vromero/npe-on-alpha-2.git
cd npe-on-alpha-2
mvn clean install -X

will return :


{code:java}
INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 2.144 s
[INFO] Finished at: 2017-12-12T15:45:10-08:00
[INFO] Final Memory: 17M/58M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-jmod-plugin:3.0.0-alpha-2-SNAPSHOT:create 
(default-create) on project about-cli-distribution-jmod: Execution 
default-create of goal 
org.apache.maven.plugins:maven-jmod-plugin:3.0.0-alpha-2-SNAPSHOT:create 
failed.: NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-jmod-plugin:3.0.0-alpha-2-SNAPSHOT:create 
(default-create) on project about-cli-distribution-jmod: Execution 
default-create of goal 
org.apache.maven.plugins:maven-jmod-plugin:3.0.0-alpha-2-SNAPSHOT:create failed.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:993)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:345)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:191)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:564)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:356)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
default-create of goal 
org.apache.maven.plugins:maven-jmod-plugin:3.0.0-alpha-2-SNAPSHOT:create failed.
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:145)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:993)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:345)
at 

[jira] [Created] (SUREFIRE-1452) Support filtering of tests from Base Class (TestNG)

2017-12-12 Thread Tibor Digana (JIRA)
Tibor Digana created SUREFIRE-1452:
--

 Summary: Support filtering of tests from Base Class (TestNG)
 Key: SUREFIRE-1452
 URL: https://issues.apache.org/jira/browse/SUREFIRE-1452
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
support
Reporter: Tibor Digana
Assignee: Tibor Digana
 Fix For: 2.21.0.Jigsaw


User has two test classes.

An abstract base class called {{BaseTest}} which contains an {{@Test}} method 
called {{testMethodFromBase}}. A child class called {{ChildTest}} which extends 
{{BaseTest}}.

User attempts at running the TestNG test via 
{{-Dtest=ChildTest#testMethodFromBase}}.

This PR basically addresses only the TestNG portion of the bug 
https://github.com/cbeust/testng/issues/1563



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


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

2017-12-12 Thread Robert Scholte (JIRA)

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

Robert Scholte commented on MNG-6308:
-

Yes, I think that's the best option. Without version it is compact, better 
readable. And it is the value that will never change (the version is variable, 
will change with every release).

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



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


[jira] [Commented] (WAGON-492) Using Wagon component with Spring

2017-12-12 Thread JIRA

[ 
https://issues.apache.org/jira/browse/WAGON-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287732#comment-16287732
 ] 

Laurent Granié commented on WAGON-492:
--

If I use this DownloaderBean with SpringBoot 1.5.9-RELEASE it's ok.
So finally, it's not really a wagon bug.
It's maybe more a dependency problem due to JBoss 6.4 modules/sub-system 
dependencies.

> Using Wagon component with Spring
> -
>
> Key: WAGON-492
> URL: https://issues.apache.org/jira/browse/WAGON-492
> Project: Maven Wagon
>  Issue Type: Bug
>  Components: wagon-provider-api
>Affects Versions: 2.12
>Reporter: Laurent Granié
> Attachments: DownloaderBean.java, bniapi-wagon.zip
>
>
> I'm using Wagon with Spring.
> With version 2.10 it's ok. But since version 2.12 I can not load component 
> into Spring.
> You can find my DownloaderServiceBean attached.
> The error is like :
> Unsatisfied dependency expressed through field 'downloader': Error
> creating bean with name 'downloaderBean': Invocation of init method
> failed; nested exception is java.lang.NoSuchMethodError:
> org.codehaus.plexus.configuration.PlexusConfiguration.setName(Ljava/lang/String;)V;
> nested exception is
> org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'downloaderBean': Invocation of init method
> failed; nested exception is java.lang.NoSuchMethodError:
> org.codehaus.plexus.configuration.PlexusConfiguration.setName(Ljava/lang/String;)V



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


[jira] [Commented] (WAGON-492) Using Wagon component with Spring

2017-12-12 Thread JIRA

[ 
https://issues.apache.org/jira/browse/WAGON-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287731#comment-16287731
 ] 

Laurent Granié commented on WAGON-492:
--

I attached a project.
When I execute test, I've got no problem.
But when I use it in JBoss 6.4, here what is :
Caused by: org.springframework.beans.factory.BeanCreationException: Error 
creating bean with name 'downloaderBean': Invocation of init method failed; 
nested exception is java.lang.NoSuchMethodError: 
org.codehaus.plexus.configuration.PlexusConfiguration.setName(Ljava/lang/String;)V
at 
org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:136)
 [spring-beans-4.3.1.RELEASE.jar:4.3.1.RELEASE]
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:408)
 [spring-beans-4.3.1.RELEASE.jar:4.3.1.RELEASE]
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1570)
 [spring-beans-4.3.1.RELEASE.jar:4.3.1.RELEASE]
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545)
 [spring-beans-4.3.1.RELEASE.jar:4.3.1.RELEASE]
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
 [spring-beans-4.3.1.RELEASE.jar:4.3.1.RELEASE]
at 
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
 [spring-beans-4.3.1.RELEASE.jar:4.3.1.RELEASE]
at 
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
 [spring-beans-4.3.1.RELEASE.jar:4.3.1.RELEASE]
at 
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
 [spring-beans-4.3.1.RELEASE.jar:4.3.1.RELEASE]
at 
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
 [spring-beans-4.3.1.RELEASE.jar:4.3.1.RELEASE]
at 
org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:187)
 [spring-beans-4.3.1.RELEASE.jar:4.3.1.RELEASE]
at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.findAutowireCandidates(DefaultListableBeanFactory.java:1213)
 [spring-beans-4.3.1.RELEASE.jar:4.3.1.RELEASE]
at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1053)
 [spring-beans-4.3.1.RELEASE.jar:4.3.1.RELEASE]
at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1018)
 [spring-beans-4.3.1.RELEASE.jar:4.3.1.RELEASE]
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:566)
 [spring-beans-4.3.1.RELEASE.jar:4.3.1.RELEASE]
... 112 more
Caused by: java.lang.NoSuchMethodError: 
org.codehaus.plexus.configuration.PlexusConfiguration.setName(Ljava/lang/String;)V
at 
org.codehaus.plexus.configuration.DefaultPlexusConfiguration.addChild(DefaultPlexusConfiguration.java:222)
 [plexus-container-default-1.7.1.jar:]
at 
org.codehaus.plexus.configuration.DefaultPlexusConfiguration.getChild(DefaultPlexusConfiguration.java:165)
 [plexus-container-default-1.7.1.jar:]
at 
org.codehaus.plexus.configuration.DefaultPlexusConfiguration.getChild(DefaultPlexusConfiguration.java:149)
 [plexus-container-default-1.7.1.jar:]
at 
org.codehaus.plexus.container.initialization.InitializeComponentRegistryPhase.getComponentRepository(InitializeComponentRegistryPhase.java:65)
 [plexus-container-default-1.7.1.jar:]
at 
org.codehaus.plexus.container.initialization.InitializeComponentRegistryPhase.execute(InitializeComponentRegistryPhase.java:40)
 [plexus-container-default-1.7.1.jar:]
at 
org.codehaus.plexus.DefaultPlexusContainer.initializePhases(DefaultPlexusContainer.java:644)
 [plexus-container-default-1.7.1.jar:]
at 
org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusContainer.java:556)
 [plexus-container-default-1.7.1.jar:]
at 
org.codehaus.plexus.DefaultPlexusContainer.construct(DefaultPlexusContainer.java:281)
 [plexus-container-default-1.7.1.jar:]
at 
org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:172)
 [plexus-container-default-1.7.1.jar:]
at com.rtd.bni.wagon.DownloaderBean.initialize(DownloaderBean.java:92) 
[bniapi-wagon-1.0-SNAPSHOT.jar:]
at 

[jira] [Updated] (WAGON-492) Using Wagon component with Spring

2017-12-12 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/WAGON-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Laurent Granié updated WAGON-492:
-
Attachment: bniapi-wagon.zip

Exemple project

> Using Wagon component with Spring
> -
>
> Key: WAGON-492
> URL: https://issues.apache.org/jira/browse/WAGON-492
> Project: Maven Wagon
>  Issue Type: Bug
>  Components: wagon-provider-api
>Affects Versions: 2.12
>Reporter: Laurent Granié
> Attachments: DownloaderBean.java, bniapi-wagon.zip
>
>
> I'm using Wagon with Spring.
> With version 2.10 it's ok. But since version 2.12 I can not load component 
> into Spring.
> You can find my DownloaderServiceBean attached.
> The error is like :
> Unsatisfied dependency expressed through field 'downloader': Error
> creating bean with name 'downloaderBean': Invocation of init method
> failed; nested exception is java.lang.NoSuchMethodError:
> org.codehaus.plexus.configuration.PlexusConfiguration.setName(Ljava/lang/String;)V;
> nested exception is
> org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'downloaderBean': Invocation of init method
> failed; nested exception is java.lang.NoSuchMethodError:
> org.codehaus.plexus.configuration.PlexusConfiguration.setName(Ljava/lang/String;)V



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


[jira] [Created] (INFRATEST3-2) test me

2017-12-12 Thread Gavin (JIRATEST)
Gavin created INFRATEST3-2:
--

 Summary: test me
 Key: INFRATEST3-2
 URL: https://issues-test.apache.org/jira/browse/INFRATEST3-2
 Project: Infra Test 3
  Issue Type: Bug
Reporter: Gavin






--
This message was sent by Atlassian JIRA
(v7.6.0#76001)


[jira] [Closed] (INFRATEST3-1) test issue

2017-12-12 Thread Gavin (JIRATEST)

 [ 
https://issues-test.apache.org/jira/browse/INFRATEST3-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gavin closed INFRATEST3-1.
--
Resolution: Fixed

All good here

> test issue
> --
>
> Key: INFRATEST3-1
> URL: https://issues-test.apache.org/jira/browse/INFRATEST3-1
> Project: Infra Test 3
>  Issue Type: Bug
>Reporter: Gavin
>Assignee: Gavin
>Priority: Major
>
> needs a description



--
This message was sent by Atlassian JIRA
(v7.6.0#76001)


[jira] [Commented] (INFRATEST3-1) test issue

2017-12-12 Thread Gavin (JIRATEST)

[ 
https://issues-test.apache.org/jira/browse/INFRATEST3-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265584#comment-16265584
 ] 

Gavin commented on INFRATEST3-1:


testing HipChat integration

> test issue
> --
>
> Key: INFRATEST3-1
> URL: https://issues-test.apache.org/jira/browse/INFRATEST3-1
> Project: Infra Test 3
>  Issue Type: Bug
>Reporter: Gavin
>Assignee: Gavin
>Priority: Major
>
> needs a description



--
This message was sent by Atlassian JIRA
(v7.6.0#76001)


[jira] [Commented] (INFRATEST3-1) test issue

2017-12-12 Thread Gavin (JIRATEST)

[ 
https://issues-test.apache.org/jira/browse/INFRATEST3-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265582#comment-16265582
 ] 

Gavin commented on INFRATEST3-1:


this is a comment

> test issue
> --
>
> Key: INFRATEST3-1
> URL: https://issues-test.apache.org/jira/browse/INFRATEST3-1
> Project: Infra Test 3
>  Issue Type: Bug
>Reporter: Gavin
>Assignee: Gavin
>Priority: Major
>
> needs a description



--
This message was sent by Atlassian JIRA
(v7.6.0#76001)


[jira] [Assigned] (INFRATEST3-1) test issue

2017-12-12 Thread Gavin (JIRATEST)

 [ 
https://issues-test.apache.org/jira/browse/INFRATEST3-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gavin reassigned INFRATEST3-1:
--

Assignee: Gavin

> test issue
> --
>
> Key: INFRATEST3-1
> URL: https://issues-test.apache.org/jira/browse/INFRATEST3-1
> Project: Infra Test 3
>  Issue Type: Bug
>Reporter: Gavin
>Assignee: Gavin
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.0#76001)


[jira] [Updated] (INFRATEST3-1) test issue

2017-12-12 Thread Gavin (JIRATEST)

 [ 
https://issues-test.apache.org/jira/browse/INFRATEST3-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gavin updated INFRATEST3-1:
---
Description: needs a description

> test issue
> --
>
> Key: INFRATEST3-1
> URL: https://issues-test.apache.org/jira/browse/INFRATEST3-1
> Project: Infra Test 3
>  Issue Type: Bug
>Reporter: Gavin
>Assignee: Gavin
>Priority: Major
>
> needs a description



--
This message was sent by Atlassian JIRA
(v7.6.0#76001)


[jira] [Created] (INFRATEST3-1) test issue

2017-12-12 Thread Gavin (JIRATEST)
Gavin created INFRATEST3-1:
--

 Summary: test issue
 Key: INFRATEST3-1
 URL: https://issues-test.apache.org/jira/browse/INFRATEST3-1
 Project: Infra Test 3
  Issue Type: Bug
Reporter: Gavin






--
This message was sent by Atlassian JIRA
(v7.6.0#76001)


[jira] [Commented] (MPLUGIN-328) ArrayIndexOutOfBoundsException: 48188

2017-12-12 Thread zosrothko (JIRA)

[ 
https://issues.apache.org/jira/browse/MPLUGIN-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287342#comment-16287342
 ] 

zosrothko commented on MPLUGIN-328:
---

Sample project provided in plugin.zip as well as its parent project as pom.xml

> ArrayIndexOutOfBoundsException: 48188 
> --
>
> Key: MPLUGIN-328
> URL: https://issues.apache.org/jira/browse/MPLUGIN-328
> Project: Maven Plugin Tools
>  Issue Type: Bug
>  Components: Plugin Plugin
>Affects Versions: 3.5
> Environment: 
> :\Users\fandre\Documents\MXW\MI\MI-4.1.1\Installer>C:\ASF\apache-maven-3.5.0\bin\mvn
>  -version
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
> 2017-04-03T21:39:06+02:00)
> Maven home: C:\ASF\apache-maven-3.5.0\bin\..
> Java version: 1.8.0_141, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_141\jre
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: zosrothko
> Attachments: plugin.zip, pom.xml
>
>
> Hi
> Got a ArrayIndexOutOfBoundsException on the maven-plugin-plugin:3.5 with an 
> empty execution element
> {code:java}
> maven-plugin-plugin
> 3.5
>  
>   
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor 
> (default-descriptor) on project scortes-maven-plugin: Execution 
> default-descriptor of goal 
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188 -> 
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor 
> (default-descriptor) on project scortes-maven-plugin: Execution 
> default-descriptor of goal 
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-descriptor of goal 
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 48188
> at org.objectweb.asm.ClassReader.readClass(Unknown Source)
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> at 
> org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.analyzeClassStream(DefaultMojoAnnotationsScanner.java:215)
> at 
> org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.scanArchive(DefaultMojoAnnotationsScanner.java:145)
> at 
> 

[jira] [Updated] (MPLUGIN-328) ArrayIndexOutOfBoundsException: 48188

2017-12-12 Thread zosrothko (JIRA)

 [ 
https://issues.apache.org/jira/browse/MPLUGIN-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

zosrothko updated MPLUGIN-328:
--
 Docs Text: 
plugin.zip contains the maven artifact 
com.scort.es.plugins:scortes-maven-plugin:1.0.5 where this issue appears. 
pom.xml is the parent project referenced by this later.
  
com.scort
rd
2017.1
  

Attachment: plugin.zip
pom.xml

> ArrayIndexOutOfBoundsException: 48188 
> --
>
> Key: MPLUGIN-328
> URL: https://issues.apache.org/jira/browse/MPLUGIN-328
> Project: Maven Plugin Tools
>  Issue Type: Bug
>  Components: Plugin Plugin
>Affects Versions: 3.5
> Environment: 
> :\Users\fandre\Documents\MXW\MI\MI-4.1.1\Installer>C:\ASF\apache-maven-3.5.0\bin\mvn
>  -version
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
> 2017-04-03T21:39:06+02:00)
> Maven home: C:\ASF\apache-maven-3.5.0\bin\..
> Java version: 1.8.0_141, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_141\jre
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: zosrothko
> Attachments: plugin.zip, pom.xml
>
>
> Hi
> Got a ArrayIndexOutOfBoundsException on the maven-plugin-plugin:3.5 with an 
> empty execution element
> {code:java}
> maven-plugin-plugin
> 3.5
>  
>   
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor 
> (default-descriptor) on project scortes-maven-plugin: Execution 
> default-descriptor of goal 
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188 -> 
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor 
> (default-descriptor) on project scortes-maven-plugin: Execution 
> default-descriptor of goal 
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-descriptor of goal 
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 48188
> at org.objectweb.asm.ClassReader.readClass(Unknown Source)
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> at 
> org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.analyzeClassStream(DefaultMojoAnnotationsScanner.java:215)
> at 
>