[jira] [Updated] (MDEP-609) Dependency analyzer gets confused if the same package is defined in 2 different artifacts

2018-05-22 Thread Ahmed Hammad (JIRA)

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

Ahmed Hammad updated MDEP-609:
--
Description: 
The issue might be related to MNG-6415

If a certain package is defined in 2 different artifacts, and a a maven module 
declares a dependency on these 2 artifacts (once through a transitive 
dependency and once using a declared dependency), dependency analyzer reports 
the dependency as "Used Undeclared", while declared dependencies should always 
take precedence (even if they appear later in the POM)

For example:

Project 1 pom:
{code:java}

http://maven.apache.org/POM/4.0.0;
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
   test
project1
1.0.0-SNAPSHOT
   
  
 test
 project2
 1.0.0-SNAPSHOT
  
  
 org.hamcrest
 hamcrest-all
 1.1
  
   

{code}
Project 2 pom:
{code:java}

http://maven.apache.org/POM/4.0.0;
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
   4.0.0
test
project2
1.0.0-SNAPSHOT


org.hamcrest
hamcrest-core
1.3



{code}
And Project 1 uses a package which can be found in both hamcrest-core and 
hamcrest-all:
{code:java}
import org.hamcrest.core.IsEqual;

class Test {
IsEqual isEqual;
}
{code}
When doing a dependency analysis for Project 1, no "Used undeclared" are 
expected to be seen, because Project 1 declares a dependency on hamcrest-all.

However, I get:

[INFO] — maven-dependency-plugin:2.8:analyze (default-cli) @ project1 —
 [WARNING] Used undeclared dependencies found:
 [WARNING] org.hamcrest:hamcrest-core:jar:1.3:compile

  was:
If a certain package is defined in 2 different artifacts, and a a maven module 
declares a dependency on these 2 artifacts (once through a transitive 
dependency and once using a declared dependency), dependency analyzer reports 
the dependency as "Used Undeclared", while declared dependencies should always 
take precedence (even if they appear later in the POM)

For example:

Project 1 pom:
{code:java}

http://maven.apache.org/POM/4.0.0;
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
   test
project1
1.0.0-SNAPSHOT
   
  
 test
 project2
 1.0.0-SNAPSHOT
  
  
 org.hamcrest
 hamcrest-all
 1.1
  
   

{code}
Project 2 pom:
{code:java}

http://maven.apache.org/POM/4.0.0;
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
   4.0.0
test
project2
1.0.0-SNAPSHOT


org.hamcrest
hamcrest-core
1.3



{code}
And Project 1 uses a package which can be found in both hamcrest-core and 
hamcrest-all:
{code:java}
import org.hamcrest.core.IsEqual;

class Test {
IsEqual isEqual;
}
{code}
When doing a dependency analysis for Project 1, no "Used undeclared" are 
expected to be seen, because Project 1 declares a dependency on hamcrest-all.

However, I get:

[INFO] — maven-dependency-plugin:2.8:analyze (default-cli) @ project1 —
 [WARNING] Used undeclared dependencies found:
 [WARNING] org.hamcrest:hamcrest-core:jar:1.3:compile


> Dependency analyzer gets confused if the same package is defined in 2 
> different artifacts
> -
>
> Key: MDEP-609
> URL: https://issues.apache.org/jira/browse/MDEP-609
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: analyze
>Affects Versions: 3.1.0
>Reporter: Ahmed Hammad
>Priority: Major
>
> The issue might be related to MNG-6415
> If a certain package is defined in 2 different artifacts, and a a maven 
> module declares a dependency on these 2 artifacts (once through a transitive 
> dependency and once using a declared dependency), dependency analyzer reports 
> the dependency as "Used Undeclared", while declared dependencies should 
> always take precedence (even if they appear later in the POM)
> For example:
> Project 1 pom:
> {code:java}
> 
> http://maven.apache.org/POM/4.0.0;
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
>test
> project1
> 1.0.0-SNAPSHOT
>
>   
>  test
>  

[jira] [Updated] (MDEP-609) Dependency analyzer gets confused if the same package is defined in 2 different artifacts

2018-04-26 Thread Ahmed Hammad (JIRA)

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

Ahmed Hammad updated MDEP-609:
--
Description: 
If a certain package is defined in 2 different artifacts, and a a maven module 
declares a dependency on these 2 artifacts (once through a transitive 
dependency and once using a declared dependency), dependency analyzer reports 
the dependency as "Used Undeclared", while declared dependencies should always 
take precedence (even if they appear later in the POM)

For example:

Project 1 pom:
{code:java}

http://maven.apache.org/POM/4.0.0;
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
   test
project1
1.0.0-SNAPSHOT
   
  
 test
 project2
 1.0.0-SNAPSHOT
  
  
 org.hamcrest
 hamcrest-all
 1.1
  
   

{code}
Project 2 pom:
{code:java}

http://maven.apache.org/POM/4.0.0;
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
   4.0.0
test
project2
1.0.0-SNAPSHOT


org.hamcrest
hamcrest-core
1.3



{code}
And Project 1 uses a package which can be found in both hamcrest-core and 
hamcrest-all:
{code:java}
import org.hamcrest.core.IsEqual;

class Test {
IsEqual isEqual;
}
{code}
When doing a dependency analysis for Project 1, no "Used undeclared" are 
expected to be seen, because Project 1 declares a dependency on hamcrest-all.

However, I get:

[INFO] — maven-dependency-plugin:2.8:analyze (default-cli) @ project1 —
 [WARNING] Used undeclared dependencies found:
 [WARNING] org.hamcrest:hamcrest-core:jar:1.3:compile

  was:
If a certain package is defined in 2 different artifacts, and a a maven module 
declares a dependency on these 2 artifacts (once through a transitive 
dependency and once using a declared dependency), dependency analyzer reports 
the transitive dependency as "Used Undeclared", while declared dependencies 
should always take precedence (even if they appear later in the POM)

For example:

Project 1 pom:
{code:java}

http://maven.apache.org/POM/4.0.0;
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
   test
project1
1.0.0-SNAPSHOT
   
  
 test
 project2
 1.0.0-SNAPSHOT
  
  
 org.hamcrest
 hamcrest-all
 1.1
  
   

{code}
Project 2 pom:
{code:java}

http://maven.apache.org/POM/4.0.0;
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
   4.0.0
test
project2
1.0.0-SNAPSHOT


org.hamcrest
hamcrest-core
1.3



{code}
And Project 1 uses a package which can be found in both hamcrest-core and 
hamcrest-all:
{code:java}
import org.hamcrest.core.IsEqual;

class Test {
IsEqual isEqual;
}
{code}
When doing a dependency analysis for Project 1, no "Used undeclared" are 
expected to be seen, because Project 1 declares a dependency on hamcrest-all.

However, I get:

[INFO] --- maven-dependency-plugin:2.8:analyze (default-cli) @ project1 ---
[WARNING] Used undeclared dependencies found:
[WARNING] org.hamcrest:hamcrest-core:jar:1.3:compile


> Dependency analyzer gets confused if the same package is defined in 2 
> different artifacts
> -
>
> Key: MDEP-609
> URL: https://issues.apache.org/jira/browse/MDEP-609
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: analyze
>Affects Versions: 3.1.0
>Reporter: Ahmed Hammad
>Priority: Major
>
> If a certain package is defined in 2 different artifacts, and a a maven 
> module declares a dependency on these 2 artifacts (once through a transitive 
> dependency and once using a declared dependency), dependency analyzer reports 
> the dependency as "Used Undeclared", while declared dependencies should 
> always take precedence (even if they appear later in the POM)
> For example:
> Project 1 pom:
> {code:java}
> 
> http://maven.apache.org/POM/4.0.0;
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
>test
> project1
> 1.0.0-SNAPSHOT
>
>   
>  test
>  project2
>  1.0.0-SNAPSHOT
>   
>   
>  

[jira] [Created] (MDEP-609) Dependency analyzer gets confused if the same package is defined in 2 different artifacts

2018-04-26 Thread Ahmed Hammad (JIRA)
Ahmed Hammad created MDEP-609:
-

 Summary: Dependency analyzer gets confused if the same package is 
defined in 2 different artifacts
 Key: MDEP-609
 URL: https://issues.apache.org/jira/browse/MDEP-609
 Project: Maven Dependency Plugin
  Issue Type: Bug
  Components: analyze
Affects Versions: 3.1.0
Reporter: Ahmed Hammad


If a certain package is defined in 2 different artifacts, and a a maven module 
declares a dependency on these 2 artifacts (once through a transitive 
dependency and once using a declared dependency), dependency analyzer reports 
the transitive dependency as "Used Undeclared", while declared dependencies 
should always take precedence (even if they appear later in the POM)

For example:

Project 1 pom:
{code:java}

http://maven.apache.org/POM/4.0.0;
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
   test
project1
1.0.0-SNAPSHOT
   
  
 test
 project2
 1.0.0-SNAPSHOT
  
  
 org.hamcrest
 hamcrest-all
 1.1
  
   

{code}
Project 2 pom:
{code:java}

http://maven.apache.org/POM/4.0.0;
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
   4.0.0
test
project2
1.0.0-SNAPSHOT


org.hamcrest
hamcrest-core
1.3



{code}
And Project 1 uses a package which can be found in both hamcrest-core and 
hamcrest-all:
{code:java}
import org.hamcrest.core.IsEqual;

class Test {
IsEqual isEqual;
}
{code}
When doing a dependency analysis for Project 1, no "Used undeclared" are 
expected to be seen, because Project 1 declares a dependency on hamcrest-all.

However, I get:

[INFO] --- maven-dependency-plugin:2.8:analyze (default-cli) @ project1 ---
[WARNING] Used undeclared dependencies found:
[WARNING] org.hamcrest:hamcrest-core:jar:1.3:compile



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SUREFIRE-1450) TestNG Listener aren't working from Property Tag in POM.xml With JDK9

2018-01-16 Thread Hammad (JIRA)

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

Hammad commented on SUREFIRE-1450:
--

Yes I think we can, with help from [~eolivelli], I also verified that problem 
isn't reproducing with 2.21.0-SNAPSHOT .

> TestNG Listener aren't working from Property Tag in POM.xml With JDK9
> -
>
> Key: SUREFIRE-1450
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1450
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
> support
>Affects Versions: 2.20.1
> Environment: macOS + Ubuntu, JDK9
>Reporter: Hammad
>Assignee: Tibor Digana
>Priority: Major
>  Labels: newbie
> Fix For: 2.21.0.Jigsaw
>
>
> TestNG Listener are not working when using:
> Maven = Apache Maven 3.5.2
> JDK9
> Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
> I executed it with jdk8 in same environment listener did work, but they 
> aren't working with JDK9
> FYI: 
> https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (SUREFIRE-1450) TestNG Listener aren't working from Property Tag in POM.xml With JDK9

2018-01-02 Thread Hammad (JIRA)

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

Hammad edited comment on SUREFIRE-1450 at 1/2/18 10:15 AM:
---

[~krmahadevan] Yes this summarise the problem.

!https://i.stack.imgur.com/2oJpa.png!


was (Author: hammadhost):
[~krmahadevan] Yes this summarise the problem.

> TestNG Listener aren't working from Property Tag in POM.xml With JDK9
> -
>
> Key: SUREFIRE-1450
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1450
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
> support
>Affects Versions: 2.20.1
> Environment: macOS + Ubuntu, JDK9
>Reporter: Hammad
>Assignee: Tibor Digana
>  Labels: newbie
>
> TestNG Listener are not working when using:
> Maven = Apache Maven 3.5.2
> JDK9
> Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
> I executed it with jdk8 in same environment listener did work, but they 
> aren't working with JDK9
> FYI: 
> https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag



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


[jira] [Commented] (SUREFIRE-1450) TestNG Listener aren't working from Property Tag in POM.xml With JDK9

2018-01-02 Thread Hammad (JIRA)

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

Hammad commented on SUREFIRE-1450:
--

[~krmahadevan] Yes this summarise the problem.

> TestNG Listener aren't working from Property Tag in POM.xml With JDK9
> -
>
> Key: SUREFIRE-1450
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1450
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
> support
>Affects Versions: 2.20.1
> Environment: macOS + Ubuntu, JDK9
>Reporter: Hammad
>Assignee: Tibor Digana
>  Labels: newbie
>
> TestNG Listener are not working when using:
> Maven = Apache Maven 3.5.2
> JDK9
> Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
> I executed it with jdk8 in same environment listener did work, but they 
> aren't working with JDK9
> FYI: 
> https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag



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


[jira] [Comment Edited] (SUREFIRE-1450) TestNG Listener aren't working from Property Tag in POM.xml With JDK9

2018-01-02 Thread Hammad (JIRA)

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

Hammad edited comment on SUREFIRE-1450 at 1/2/18 8:48 AM:
--

as per [~krmahadevan] instructions, passed listener from command line argument 
instead of testng.xml tag, and its working as expected.
!https://i.stack.imgur.com/Uvy1Q.png!


was (Author: hammadhost):
as per [~krmahadevan] instructions
!https://i.stack.imgur.com/Uvy1Q.png!

> TestNG Listener aren't working from Property Tag in POM.xml With JDK9
> -
>
> Key: SUREFIRE-1450
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1450
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
> support
>Affects Versions: 2.20.1
> Environment: macOS + Ubuntu, JDK9
>Reporter: Hammad
>Assignee: Tibor Digana
>  Labels: newbie
>
> TestNG Listener are not working when using:
> Maven = Apache Maven 3.5.2
> JDK9
> Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
> I executed it with jdk8 in same environment listener did work, but they 
> aren't working with JDK9
> FYI: 
> https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag



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


[jira] [Commented] (SUREFIRE-1450) TestNG Listener aren't working from Property Tag in POM.xml With JDK9

2018-01-02 Thread Hammad (JIRA)

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

Hammad commented on SUREFIRE-1450:
--

as per [~krmahadevan]
!https://i.stack.imgur.com/Uvy1Q.png!

> TestNG Listener aren't working from Property Tag in POM.xml With JDK9
> -
>
> Key: SUREFIRE-1450
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1450
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
> support
>Affects Versions: 2.20.1
> Environment: macOS + Ubuntu, JDK9
>Reporter: Hammad
>Assignee: Tibor Digana
>  Labels: newbie
>
> TestNG Listener are not working when using:
> Maven = Apache Maven 3.5.2
> JDK9
> Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
> I executed it with jdk8 in same environment listener did work, but they 
> aren't working with JDK9
> FYI: 
> https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag



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


[jira] [Comment Edited] (SUREFIRE-1450) TestNG Listener aren't working from Property Tag in POM.xml With JDK9

2018-01-02 Thread Hammad (JIRA)

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

Hammad edited comment on SUREFIRE-1450 at 1/2/18 8:46 AM:
--

as per [~krmahadevan] instructions
!https://i.stack.imgur.com/Uvy1Q.png!


was (Author: hammadhost):
as per [~krmahadevan]
!https://i.stack.imgur.com/Uvy1Q.png!

> TestNG Listener aren't working from Property Tag in POM.xml With JDK9
> -
>
> Key: SUREFIRE-1450
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1450
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
> support
>Affects Versions: 2.20.1
> Environment: macOS + Ubuntu, JDK9
>Reporter: Hammad
>Assignee: Tibor Digana
>  Labels: newbie
>
> TestNG Listener are not working when using:
> Maven = Apache Maven 3.5.2
> JDK9
> Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
> I executed it with jdk8 in same environment listener did work, but they 
> aren't working with JDK9
> FYI: 
> https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag



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


[jira] [Commented] (SUREFIRE-1450) TestNG Listener aren't working from Property Tag in POM.xml With JDK9

2018-01-01 Thread Hammad (JIRA)

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

Hammad commented on SUREFIRE-1450:
--

I have already shared the same result with [~krmahadevan] waiting for his 
answer lets see what he has to say about it.

> TestNG Listener aren't working from Property Tag in POM.xml With JDK9
> -
>
> Key: SUREFIRE-1450
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1450
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
> support
>Affects Versions: 2.20.1
> Environment: macOS + Ubuntu, JDK9
>Reporter: Hammad
>Assignee: Tibor Digana
>  Labels: newbie
>
> TestNG Listener are not working when using:
> Maven = Apache Maven 3.5.2
> JDK9
> Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
> I executed it with jdk8 in same environment listener did work, but they 
> aren't working with JDK9
> FYI: 
> https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag



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


[jira] [Updated] (SUREFIRE-1450) TestNG Listener aren't working from Property Tag in POM.xml With JDK9

2018-01-01 Thread Hammad (JIRA)

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

Hammad updated SUREFIRE-1450:
-
Description: 
TestNG Listener are not working when using:
Maven = Apache Maven 3.5.2
JDK9
Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
I executed it with jdk8 in same environment listener did work, but they aren't 
working with JDK9
FYI: 
https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag

  was:
TestNG Listener are not working when using:
Maven = Apache Maven 3.5.2
JDK9 on either platform (sierra+ubuntu)
Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
I executed it with jdk8 in same environment listener did work, but they aren't 
working with JDK9
FYI: 
https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag


> TestNG Listener aren't working from Property Tag in POM.xml With JDK9
> -
>
> Key: SUREFIRE-1450
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1450
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
> support
>Affects Versions: 2.20.1
> Environment: macOS + Ubuntu, JDK9
>Reporter: Hammad
>Assignee: Tibor Digana
>  Labels: newbie
>
> TestNG Listener are not working when using:
> Maven = Apache Maven 3.5.2
> JDK9
> Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
> I executed it with jdk8 in same environment listener did work, but they 
> aren't working with JDK9
> FYI: 
> https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag



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


[jira] [Comment Edited] (SUREFIRE-1450) TestNG Listener aren't working from Property Tag in POM.xml With JDK9

2018-01-01 Thread Hammad (JIRA)

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

Hammad edited comment on SUREFIRE-1450 at 1/1/18 1:08 PM:
--

!https://i.stack.imgur.com/ESBPi.png!

>From command line testng listeners are working fine JDK9. So I assume its 
>sure-fire issue.
And by not working I mean when I execute listener with property tag from pom, I 
don't see any output in jdk9 case.

!https://i.stack.imgur.com/gBglc.png!


listener
poc.config.MyCustomListener

This is the POM part.


was (Author: hammadhost):
!https://i.stack.imgur.com/ESBPi.png!

>From command line testng listeners are working fine JDK9. So I assume its 
>sure-fire issue.
And by not working I mean when I execute listener with property tag from pom, I 
don't see any output in jdk9 case.

!https://i.stack.imgur.com/gBglc.png!

> TestNG Listener aren't working from Property Tag in POM.xml With JDK9
> -
>
> Key: SUREFIRE-1450
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1450
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
> support
>Affects Versions: 2.20.1
> Environment: macOS + Ubuntu, JDK9
>Reporter: Hammad
>Assignee: Tibor Digana
>  Labels: newbie
>
> TestNG Listener are not working when using:
> Maven = Apache Maven 3.5.2
> JDK9 on either platform (sierra+ubuntu)
> Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
> I executed it with jdk8 in same environment listener did work, but they 
> aren't working with JDK9
> FYI: 
> https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag



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


[jira] [Comment Edited] (SUREFIRE-1450) TestNG Listener aren't working from Property Tag in POM.xml With JDK9

2018-01-01 Thread Hammad (JIRA)

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

Hammad edited comment on SUREFIRE-1450 at 1/1/18 1:07 PM:
--

!https://i.stack.imgur.com/ESBPi.png!

>From command line testng listeners are working fine JDK9. So I assume its 
>sure-fire issue.
And by not working I mean when I execute listener with property tag from pom, I 
don't see any output in jdk9 case.

!https://i.stack.imgur.com/gBglc.png!


was (Author: hammadhost):
!https://i.stack.imgur.com/ESBPi.png!

>From command line testng listeners are working fine JDK9. So I assume its 
>sure-fire issue.
And by not working I mean when I execute listener with property tag from pom, I 
don't see any output in jdk9 case.

> TestNG Listener aren't working from Property Tag in POM.xml With JDK9
> -
>
> Key: SUREFIRE-1450
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1450
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
> support
>Affects Versions: 2.20.1
> Environment: macOS + Ubuntu, JDK9
>Reporter: Hammad
>Assignee: Tibor Digana
>  Labels: newbie
>
> TestNG Listener are not working when using:
> Maven = Apache Maven 3.5.2
> JDK9 on either platform (sierra+ubuntu)
> Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
> I executed it with jdk8 in same environment listener did work, but they 
> aren't working with JDK9
> FYI: 
> https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag



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


[jira] [Commented] (SUREFIRE-1450) TestNG Listener aren't working from Property Tag in POM.xml With JDK9

2018-01-01 Thread Hammad (JIRA)

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

Hammad commented on SUREFIRE-1450:
--

!https://i.stack.imgur.com/ESBPi.png!

>From command line testng listeners are working fine JDK9. So I assume its 
>sure-fire issue.
And by not working I mean when I execute listener with property tag from pom, I 
don't see any output in jdk9 case.

> TestNG Listener aren't working from Property Tag in POM.xml With JDK9
> -
>
> Key: SUREFIRE-1450
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1450
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
> support
>Affects Versions: 2.20.1
> Environment: macOS + Ubuntu, JDK9
>Reporter: Hammad
>Assignee: Tibor Digana
>  Labels: newbie
>
> TestNG Listener are not working when using:
> Maven = Apache Maven 3.5.2
> JDK9 on either platform (sierra+ubuntu)
> Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
> I executed it with jdk8 in same environment listener did work, but they 
> aren't working with JDK9
> FYI: 
> https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag



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


[jira] [Updated] (SUREFIRE-1450) TestNG Listener aren't working from Property Tag in POM With JDK9

2017-12-05 Thread Hammad (JIRA)

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

Hammad updated SUREFIRE-1450:
-
Summary: TestNG Listener aren't working from Property Tag in POM With JDK9  
(was: TestNG Listener aren't working With JDK9)

> TestNG Listener aren't working from Property Tag in POM With JDK9
> -
>
> Key: SUREFIRE-1450
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1450
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
> support
>Affects Versions: 2.20.1
> Environment: macOS + Ubuntu, JDK9
>Reporter: Hammad
>  Labels: newbie
>
> TestNG Listener are not working when using:
> Maven = Apache Maven 3.5.2
> JDK9 on either platform (sierra+ubuntu)
> Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
> I executed it with jdk8 in same environment listener did work, but they 
> aren't working with JDK9
> FYI: 
> https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag



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


[jira] [Updated] (SUREFIRE-1450) TestNG Listener aren't working from Property Tag in POM.xml With JDK9

2017-12-05 Thread Hammad (JIRA)

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

Hammad updated SUREFIRE-1450:
-
Summary: TestNG Listener aren't working from Property Tag in POM.xml With 
JDK9  (was: TestNG Listener aren't working from Property Tag in POM With JDK9)

> TestNG Listener aren't working from Property Tag in POM.xml With JDK9
> -
>
> Key: SUREFIRE-1450
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1450
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
> support
>Affects Versions: 2.20.1
> Environment: macOS + Ubuntu, JDK9
>Reporter: Hammad
>  Labels: newbie
>
> TestNG Listener are not working when using:
> Maven = Apache Maven 3.5.2
> JDK9 on either platform (sierra+ubuntu)
> Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
> I executed it with jdk8 in same environment listener did work, but they 
> aren't working with JDK9
> FYI: 
> https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag



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


[jira] [Created] (SUREFIRE-1450) TestNG Listener aren't working With JDK9

2017-12-05 Thread Hammad (JIRA)
Hammad created SUREFIRE-1450:


 Summary: TestNG Listener aren't working With JDK9
 Key: SUREFIRE-1450
 URL: https://issues.apache.org/jira/browse/SUREFIRE-1450
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG 
support
Affects Versions: 2.20.1
 Environment: macOS + Ubuntu, JDK9
Reporter: Hammad


TestNG Listener are not working when using:
Maven = Apache Maven 3.5.2
JDK9 on either platform (sierra+ubuntu)
Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire
I executed it with jdk8 in same environment listener did work, but they aren't 
working with JDK9
FYI: 
https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag



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