Re: Change of Chair

[Martin Gainty]

Congratulations Karl

Viel Gluck !
Martin-

From: Robert Scholte 
Sent: Thursday, April 21, 2022 10:57 AM
To: Maven Developers List 
Cc: Maven Project Management Committee List 
Subject: Change of Chair

Hi all,

as of now, Karl Heinz is the new chairman of the Apache Maven project.
I've done it for quite some time with a lot of pleasure.
I will also reduce my activities on this project, but will still be
involved as PMC member.

thanks,
Robert


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

RE: Maven Dependency Plugin - Log4j vulnerabilities

[Martin Gainty]

I *thought* log4j 1.2.15 had the patch to mitigate the JNDI Security 
Vulnerabity?
Is this not the case?
Thanks John
M.



Sent from my Verizon, Samsung Galaxy smartphone



 Original message 
From: John Patrick 
Date: 3/3/22 4:07 AM (GMT-05:00)
To: Maven Developers List 
Cc: David Milet , iss...@maven.apache.org, 
VZ-Product-OneTalk , Danylo Volokh 

Subject: Re: Maven Dependency Plugin - Log4j vulnerabilities

Sorry I thought you where talking about log4j v2, not v1. I can see it
downloads the metadata about the project but non or the jars;
local-repo/log4j
local-repo/log4j/log4j
local-repo/log4j/log4j/1.2.12/log4j-1.2.12.pom
local-repo/log4j/log4j/1.2.12/log4j-1.2.12.pom.sha1
local-repo/log4j
local-repo/log4j/log4j
local-repo/log4j/log4j/1.2.12
local-repo/log4j/log4j/1.2.12/log4j-1.2.12.pom
local-repo/log4j/log4j/1.2.12/log4j-1.2.12.pom.sha1
local-repo/log4j/log4j/1.2.12/_remote.repositories

So I would still say false positive, as the jar is not actually used.

But looking at the dependency tree it would need the apache commons to
update commons-logging:commons-logging, then
ommons-digester:commons-digester then org.apache.velocity:velocity-tools,
then it gets to the 1st dependency within the maven ecosystem.
So 5 ish patches to 5 separate projects to upgrade, test and release, each
before then next pr can progress.

John


On Thu, 3 Mar 2022 at 07:53, Thomas Matthijs  wrote:

> That was just to demonstrate how i got the dependency chain, that file
> was there, but if you're going to be this hostile, i'm not interested
> anymore, muting thread
>
> On Thu, 3 Mar 2022 at 08:48, Piotr Żygieło 
> wrote:
> >
> > On Thu, 3 Mar 2022 at 08:37, Thomas Matthijs  wrote:
> > >
> > > Can confirm this project downloads log4j 1.12.12 for me
> >
> > As I see it - you confirm something else.
> >
> > > Failed to read artifact descriptor for log4j:log4j:jar:1.2.12:
> >
> > Failed to read artifact descriptor for log4j:log4j:jar:1.2.12:
> > _artifact descriptor_
> >
> > --
> > Piotrek
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Welcome Guillaume Nodet as new Maven Committer

[Martin Gainty]

Bonjour Guillame!

martin

From: Karl Heinz Marbaise 
Sent: Friday, May 28, 2021 6:43 AM
To: Maven Developers List ; Robert Scholte 

Subject: Re: Welcome Guillaume Nodet as new Maven Committer

Hi Guillaume,

welcome.

Kind regards
Karl Heinz Marbaise


On 25.05.21 19:19, Robert Scholte wrote:
> Hi,
>
> On behalf of the Apache Maven PMC I am pleased to announce that
> Guillaume Nodet has been voted in as new Apache Maven committer
> and he has accepted this invitation.
>
> Welcome on board and have a lot of fun!
>
> Thanks,
> Robert Scholte
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Help Wanted

[Martin Gainty]

/maven-dependency-plugin/src/test/java/org/apache/maven/plugins/dependency/fromDependencies/TestUnpackDependenciesMojo.java:[544,65]
 incompatible types: java.lang.Object cannot be converted to 
org.apache.maven.artifact.Artifact

[ERROR] 
/workspace/maven-dependency-plugin/src/test/java/org/apache/maven/plugins/dependency/fromDependencies/TestUnpackDependenciesMojo.java:[554,65]
 incompatible types: java.lang.Object cannot be converted to 
org.apache.maven.artifact.Artifact



I stronlgy assume the POM you sent me is not the latest one you actually used 
to solve the issue?



Any more ideas? Thanks a lot! :-)



-Markus





Von: Martin Gainty [mailto:mgai...@hotmail.com]
Gesendet: Donnerstag, 10. Dezember 2020 11:44
An: Maven Developers List
Betreff: Re: Help Wanted



Hi Markus

i was able to get tests to pass for maven-dependency-plugin

[INFO]  T E S T S

[INFO] ---

SystemPropertyManager::writePropertiesFile LINE 106 throws ClassCastException 
message=java.lang.Object cannot be cast to java.lang.String

[DEBUG] boot classpath:  
\Users\MGainty\.m2\repository\org\apache\maven\surefire\surefire-booter\2.22.1\surefire-booter-2.22.1.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\surefire\surefire-api\2.22.1\surefire-api-2.22.1.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\surefire\surefire-logger-api\2.22.1\surefire-logger-api-2.22.1.jar
  
\Maven-plugin\maven-dependency-plugin\maven-dependency-plugin-markus\target\test-classes
  
\Maven-plugin\maven-dependency-plugin\maven-dependency-plugin-markus\target\classes
  
\Users\MGainty\.m2\repository\org\apache\maven\surefire\surefire-api\2.9\surefire-api-2.9.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\surefire\maven-surefire-common\2.22.1\maven-surefire-common-2.22.1.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\maven-plugin-descriptor\2.2.1\maven-plugin-descriptor-2.2.1.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\maven-project\2.2.1\maven-project-2.2.1.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\maven-profile\2.2.1\maven-profile-2.2.1.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\maven-artifact-manager\2.2.1\maven-artifact-manager-2.2.1.jar
  
\Users\MGainty\.m2\repository\backport-util-concurrent\backport-util-concurrent\3.1\backport-util-concurrent-3.1.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\maven-plugin-registry\2.2.1\maven-plugin-registry-2.2.1.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\maven-toolchain\2.2.1\maven-toolchain-2.2.1.jar
  
\Users\MGainty\.m2\repository\org\codehaus\plexus\plexus-java\0.9.10\plexus-java-0.9.10.jar
  
\Users\MGainty\.m2\repository\com\thoughtworks\qdox\qdox\2.0-M8\qdox-2.0-M8.jar 
 
\Users\MGainty\.m2\repository\org\apache\maven\shared\maven-common-artifact-filters\3.0.1\maven-common-artifact-filters-3.0.1.jar
  
\Users\MGainty\.m2\repository\org\sonatype\sisu\sisu-inject-plexus\1.4.2\sisu-inject-plexus-1.4.2.jar
  
\Users\MGainty\.m2\repository\org\sonatype\sisu\sisu-inject-bean\1.4.2\sisu-inject-bean-1.4.2.jar
  
\Users\MGainty\.m2\repository\org\sonatype\sisu\sisu-guice\2.1.7\sisu-guice-2.1.7-noaop.jar
  
\Users\MGainty\.m2\repository\org\eclipse\aether\aether-api\1.1.0-SNAPSHOT\aether-api-1.1.0-SNAPSHOT.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\maven-artifact\3.1.1\maven-artifact-3.1.1.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\maven-plugin-api\3.1.1\maven-plugin-api-3.1.1.jar
  
\Users\MGainty\.m2\repository\org\eclipse\sisu\org.eclipse.sisu.plexus\0.1.0\org.eclipse.sisu.plexus-0.1.0.jar
 \Users\MGainty\.m2\repository\javax\enterprise\cdi-api\1.0\cdi-api-1.0.jar  
\Users\MGainty\.m2\repository\javax\annotation\jsr250-api\1.0\jsr250-api-1.0.jar
  \Users\MGainty\.m2\repository\javax\inject\javax.inject\1\javax.inject-1.jar  
\Users\MGainty\.m2\repository\org\eclipse\sisu\org.eclipse.sisu.inject\0.1.0\org.eclipse.sisu.inject-0.1.0.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\maven-model\3.1.1\maven-model-3.1.1.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\maven-core\3.1.1\maven-core-3.1.1.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\maven-settings\3.1.1\maven-settings-3.1.1.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\maven-settings-builder\3.1.1\maven-settings-builder-3.1.1.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\maven-model-builder\3.1.1\maven-model-builder-3.1.1.jar
  
\Users\MGainty\.m2\repository\org\apache\maven\maven-aether-provider\3.1.1\maven-aether-provider-3.1.1.jar
  
\Users\MGainty\.m2\repository\org\eclipse\aether\aether-impl\0.9.0.M2\aether-impl-0.9.0.M2.jar
  
\Users\MGainty\.m2\repository\org\eclipse\aether\aether-util\0.9.0.M2\aether-util-0.9.0.M2.jar
  
\Users\MGainty\.m2\repository\org\codehaus\plexus\plexus-classworlds\2.5.1\plexus-classworlds-2.5.1.jar
  
\Users\MGainty\.m2\repository\org\codehaus\plexus\plexus-component-annotations\2.0.0\plexus-component-annotations-2.0.0.jar
  
\Users\MGain

Re: Help Wanted

[Martin Gainty]

r
 
C:\Maven-plugin\maven-dependency-plugin\maven-dependency-plugin-markus\surefire 
2020-12-09T18-42-51_647-jvmRun1 surefire6735082700204536096tmp 
surefire_06519399515511647335tmp"
[WARNING] Corrupted stdin stream in forked JVM 1. See the dump file 
\Maven-plugin\maven-dependency-plugin\maven-dependency-plugin-markus\target\surefire-reports\2020-12-09T18-42-51_647-jvmRun1.dumpstream
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 25.633 s
[INFO] Finished at: 2020-12-09T18:43:01-05:00
[INFO] 

please see attached pom.xml

~gruss~
martin
____
From: Martin Gainty 
Sent: Monday, December 7, 2020 4:58 PM
To: Maven Developers List 
Subject: Re: Help Wanted

sorry.. got distracted watching a 1941 dogfight of messerschmitt vs spitfire 
re-creation over englisch channel
Watch Pearl Harbor Online | Free Full Movie | 123Movies 
(123moviesgoto.com)<https://123moviesgoto.com/pearl-harbor>
for all whose fathers fought in the "Big War" I would say this flick seems like 
worthwhile viewing

I took a copy of https://github.com/apache/maven-dependency-plugin/pull/109

>mvn compile

ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/fromDependencies/TestUnpackDependenciesMojo.java:[544,65]
incompatible types: java.lang.Object cannot be converted to 
org.apache.maven.artifact.Artifact
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/fromDependencies/TestUnpackDependenciesMojo.java:[554,65]
 incompatible types: java.lang.Object cannot be converted to 
org.apache.maven.artifact.Artifact
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[210,17]
 name clash: 
setRemoteArtifactRepositories(java.util.List)
 in org.apache.maven.plugins.dependency.testUtils.stubs.DependencyProjectStub 
and setRemoteArtifactRepositories(java.util.List) in 
org.apache.maven.project.MavenProject have the same erasure, yet neither 
overrides the other
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[240,17]
 name clash: setDependencies(java.util.List) 
in org.apache.maven.plugins.dependency.testUtils.stubs.DependencyProjectStub 
and setDependencies(java.util.List) in org.apache.maven.project.MavenProject 
have the same erasure, yet neither overrides the other
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[389,17]
 name clash: 
setAttachedArtifacts(java.util.List) in 
org.apache.maven.plugins.dependency.testUtils.stubs.DependencyProjectStub and 
setAttachedArtifacts(java.util.List) in org.apache.maven.project.MavenProject 
have the same erasure, yet neither overrides the other
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[394,17]
 name clash: setCompileSourceRoots(java.util.List) in 
org.apache.maven.plugins.dependency.testUtils.stubs.DependencyProjectStub and 
setCompileSourceRoots(java.util.List) in org.apache.maven.project.MavenProject 
have the same erasure, yet neither overrides the other
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[399,17]
 name clash: setTestCompileSourceRoots(java.util.List) in 
org.apache.maven.plugins.dependency.testUtils.stubs.DependencyProjectStub and 
setTestCompileSourceRoots(java.util.List) in 
org.apache.maven.project.MavenProject have the same erasure, yet neither 
overrides the other
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[404,17]
 name clash: setScriptSourceRoots(java.util.List) in 
org.apache.maven.plugins.dependency.testUtils.stubs.DependencyProjectStub and 
setScriptSourceRoots(java.util.List) in org.apache.maven.project.MavenProject 
have the same erasure, yet neither overrides the other
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[615,17]

Re: Help Wanted

[Martin Gainty]

sorry.. got distracted watching a 1941 dogfight of messerschmitt vs spitfire 
re-creation over englisch channel
Watch Pearl Harbor Online | Free Full Movie | 123Movies 
(123moviesgoto.com)
for all whose fathers fought in the "Big War" I would say this flick seems like 
worthwhile viewing

I took a copy of https://github.com/apache/maven-dependency-plugin/pull/109

>mvn compile

ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/fromDependencies/TestUnpackDependenciesMojo.java:[544,65]
incompatible types: java.lang.Object cannot be converted to 
org.apache.maven.artifact.Artifact
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/fromDependencies/TestUnpackDependenciesMojo.java:[554,65]
 incompatible types: java.lang.Object cannot be converted to 
org.apache.maven.artifact.Artifact
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[210,17]
 name clash: 
setRemoteArtifactRepositories(java.util.List)
 in org.apache.maven.plugins.dependency.testUtils.stubs.DependencyProjectStub 
and setRemoteArtifactRepositories(java.util.List) in 
org.apache.maven.project.MavenProject have the same erasure, yet neither 
overrides the other
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[240,17]
 name clash: setDependencies(java.util.List) 
in org.apache.maven.plugins.dependency.testUtils.stubs.DependencyProjectStub 
and setDependencies(java.util.List) in org.apache.maven.project.MavenProject 
have the same erasure, yet neither overrides the other
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[389,17]
 name clash: 
setAttachedArtifacts(java.util.List) in 
org.apache.maven.plugins.dependency.testUtils.stubs.DependencyProjectStub and 
setAttachedArtifacts(java.util.List) in org.apache.maven.project.MavenProject 
have the same erasure, yet neither overrides the other
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[394,17]
 name clash: setCompileSourceRoots(java.util.List) in 
org.apache.maven.plugins.dependency.testUtils.stubs.DependencyProjectStub and 
setCompileSourceRoots(java.util.List) in org.apache.maven.project.MavenProject 
have the same erasure, yet neither overrides the other
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[399,17]
 name clash: setTestCompileSourceRoots(java.util.List) in 
org.apache.maven.plugins.dependency.testUtils.stubs.DependencyProjectStub and 
setTestCompileSourceRoots(java.util.List) in 
org.apache.maven.project.MavenProject have the same erasure, yet neither 
overrides the other
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[404,17]
 name clash: setScriptSourceRoots(java.util.List) in 
org.apache.maven.plugins.dependency.testUtils.stubs.DependencyProjectStub and 
setScriptSourceRoots(java.util.List) in org.apache.maven.project.MavenProject 
have the same erasure, yet neither overrides the other
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[615,17]
 name clash: 
setMailingLists(java.util.List) in 
org.apache.maven.plugins.dependency.testUtils.stubs.DependencyProjectStub and 
setMailingLists(java.util.List) in org.apache.maven.project.MavenProject have 
the same erasure, yet neither overrides the other
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[614,5]
 method does not override or implement a method from a supertype
[ERROR] 
/Maven-plugin/maven-dependency-plugin/maven-dependency-plugin-markus/src/test/java/org/apache/maven/plugins/dependency/testUtils/stubs/DependencyProjectStub.java:[631,17]
 name clash: setDevelopers(java.util.List) in 
org.apache.maven.plugins.dependency.testUtils.stubs.DependencyProjectStub and 
setDevelopers(java.util.List) in org.apache.maven.project.MavenProject have the 
same erasure, yet neither overrides the other
[ERROR] 

Re: Assumption fail treated as unexcepted exception?!

[Martin Gainty]

MG>below


From: Markus KARG 
Sent: Tuesday, August 18, 2020 8:28 AM
To: 'Maven Developers List' 
Subject: AW: Assumption fail treated as unexcepted exception?!

Martin,

sorry was busy otherwise, had no time to check with JUnit 4. Will try ASAP and 
report here.

In fact I do not understand what you want me to ask the JUnit authors. I do not 
want to use JUnit 3 at all (I did not actively decide for any version), so if 
there is something to ask them, please tell me *what*?
MG>we need to understand if the statement if Junit AssumptionViolatedException 
is thrown
MG>the intended behaviour is to NOT fail the testcase that wraps 
AssumptionViolatedException 
MG>AssumptionViolatedException source is displayed below

package org.junit;

import org.hamcrest.Matcher;

/**
 * An exception class used to implement assumptions (state in which a 
given test
 * is meaningful and should or should not be executed). A test for which an 
assumption
 * fails should not generate a test case failure.
 *
 * @see org.junit.Assume
 * @since 4.12
 */
@SuppressWarnings("deprecation")
public class AssumptionViolatedException extends 
org.junit.internal.AssumptionViolatedException {
private static final long serialVersionUID = 1L;

/**
 * An assumption exception with the given actual value and a 
matcher describing
 * the expectation that failed.
 */
public  AssumptionViolatedException(T actual, Matcher matcher) {
super(actual, matcher);
}

/**
 * An assumption exception with a message with the given actual 
value and a
 * matcher describing the expectation that failed.
 */
public  AssumptionViolatedException(String message, T expected, 
Matcher matcher) {
super(message, expected, matcher);
}

/**
 * An assumption exception with the given message only.
 */
public AssumptionViolatedException(String message) {
super(message);
}

/**
 * An assumption exception with the given message and a cause.
 */
public AssumptionViolatedException(String assumption, Throwable t) {
super(assumption, t);
}
}

MG>if the above junit statement is true then when you throw 
AssumptionViolatedException
MG>the testcase that wraps AssumptionViolatedException  should 
NOT FAIL the testcase
MG>If true I will admit this junit behaviour seems counter-intuitive
MG>thanks
MG>martin

thanks
-Markus


-----Ursprüngliche Nachricht-
Von: Martin Gainty [mailto:mgai...@hotmail.com]
Gesendet: Dienstag, 18. August 2020 11:28
An: Maven Developers List
Betreff: Re: Assumption fail treated as unexcepted exception?!

have you tried with junit4?

if you need to stick with older junit then you can implement your 
AssumptionViolatedException to extend BuildFailureException

any feedback from junit author on this behaviour?

gruss
~martin~



From: Markus KARG 
Sent: Monday, August 17, 2020 1:53 PM
To: 'Maven Developers List' 
Subject: AW: Assumption fail treated as unexcepted exception?!

That doesn't make it any better, and it is no excuse that we do not simply 
catch that particular exception inside the Surefire plugin.
So did we simply forget to implement this is the Surefire plugin (so I can add 
it), did we not implement it deliberately (so I shall not add it), or is it 
broken (so I shall fix it)?
-Markus

-Ursprüngliche Nachricht-
Von: Tibor Digana [mailto:tibordig...@apache.org]
Gesendet: Montag, 17. August 2020 18:37
An: Maven Developers List
Betreff: Re: Assumption fail treated as unexcepted exception?!

This is the outcome in IDEA:

"Tests failed: 1, passed: 0"

So the behavior is the same with Maven.

On Mon, Aug 17, 2020 at 6:35 PM Tibor Digana  wrote:

> Hi Markus,
>
> It is a specific problem related to the JUnit library because the test
> fails in IntelliJ IDEA and in Maven as well.
>
> The JUnit4 assumptions fail with yellow markers in IDEA but here the
> JUnit3' TestCase fails in red as a typical error or failure.
> And Maven fails this test as follows but i think this behavior starts in
> the junit library itself.
>
> [INFO] Running test.TestAssumptions
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 0.028 s <<< FAILURE! - in test.TestAssumptions
> [ERROR] test.TestAssumptions.testABC  Time elapsed: 0.01 s  <<< ERROR!
> org.junit.AssumptionViolatedException: got: , expected: is 
> at test/test.TestAssumptions.testABC(TestAssumptions.java:9)
>
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR]   TestAssumptions.testABC:9 » AssumptionViolated got: ,
> expected: is  [INFO]
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> [INFO]
> [INFO]
> 
> [INFO] BUILD FAILURE
>
> On Mon, Aug 17, 

Re: Assumption fail treated as unexcepted exception?!

[Martin Gainty]

have you tried with junit4?

if you need to stick with older junit then you can implement your 
AssumptionViolatedException to extend BuildFailureException

any feedback from junit author on this behaviour?

gruss
~martin~



From: Markus KARG 
Sent: Monday, August 17, 2020 1:53 PM
To: 'Maven Developers List' 
Subject: AW: Assumption fail treated as unexcepted exception?!

That doesn't make it any better, and it is no excuse that we do not simply 
catch that particular exception inside the Surefire plugin.
So did we simply forget to implement this is the Surefire plugin (so I can add 
it), did we not implement it deliberately (so I shall not add it), or is it 
broken (so I shall fix it)?
-Markus

-Ursprüngliche Nachricht-
Von: Tibor Digana [mailto:tibordig...@apache.org]
Gesendet: Montag, 17. August 2020 18:37
An: Maven Developers List
Betreff: Re: Assumption fail treated as unexcepted exception?!

This is the outcome in IDEA:

"Tests failed: 1, passed: 0"

So the behavior is the same with Maven.

On Mon, Aug 17, 2020 at 6:35 PM Tibor Digana  wrote:

> Hi Markus,
>
> It is a specific problem related to the JUnit library because the test
> fails in IntelliJ IDEA and in Maven as well.
>
> The JUnit4 assumptions fail with yellow markers in IDEA but here the
> JUnit3' TestCase fails in red as a typical error or failure.
> And Maven fails this test as follows but i think this behavior starts in
> the junit library itself.
>
> [INFO] Running test.TestAssumptions
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 0.028 s <<< FAILURE! - in test.TestAssumptions
> [ERROR] test.TestAssumptions.testABC  Time elapsed: 0.01 s  <<< ERROR!
> org.junit.AssumptionViolatedException: got: , expected: is 
> at test/test.TestAssumptions.testABC(TestAssumptions.java:9)
>
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR]   TestAssumptions.testABC:9 » AssumptionViolated got: ,
> expected: is  [INFO]
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> [INFO]
> [INFO]
> 
> [INFO] BUILD FAILURE
>
> On Mon, Aug 17, 2020 at 3:07 PM Markus KARG 
> wrote:
>
>> Martin,
>>
>> I don't understand your question.
>>
>> You posted the Javadocs, and they tell it clearly: "A test for which an
>> assumption fails should NOT generate a test case failure.".
>>
>> Also Assume's Javadocs
>> (https://junit.org/junit4/javadoc/4.12/org/junit/Assume.html) are pretty
>> clear about it: "... A failed assumption does NOT mean the code is broken,
>> but that the test provides no useful information. Assume basically means
>> "don't RUN this test if these conditions don't apply". The default JUnit
>> runner SKIPS tests with failing assumptions..."
>>
>> So do you really want me to ask the JUnit people whether they really MEAN
>> what they clearly wrote...?
>>
>> -Markus
>>
>> -Ursprüngliche Nachricht-
>> Von: Martin Gainty [mailto:mgai...@hotmail.com]
>> Gesendet: Montag, 17. August 2020 12:27
>> An: Maven Developers List
>> Betreff: Re: Assumption fail treated as unexcepted exception?!
>>
>>
>>/**
>>  * Call to assume that actual satisfies the condition
>> specified by matcher.
>>  * If not, the test halts and is ignored.
>>  * Example:
>>  * :
>>  *   assumeThat(1, is(1)); // passes
>>  *   foo(); // will execute
>>  *   assumeThat(0, is(1)); // assumption failure! test halts
>>  *   int x = 1 / 0; // will never execute
>>  * 
>>  *
>>  * @param  the static type accepted by the matcher (this can flag
>> obvious compile-time problems such as {@code assumeThat(1, is("a"))}
>>  * @param actual the computed value being compared
>>  * @param matcher an expression, built of {@link Matcher}s, specifying
>> allowed values
>>  * @see org.hamcrest.CoreMatchers
>>  * @see org.junit.matchers.JUnitMatchers
>>  */
>> public static  void assumeThat(T actual, Matcher matcher) {
>> if (!matcher.matches(actual)) {
>> throw new AssumptionViolatedException(actual, matcher);
>> }
>> }
>>
>> //does AssumptionViolatedException ever produce test case failure?
>>
>> /**
>>  * An exception class used to implement assumptions (state in
>> which a
>> given test
>>  * is meaningful and should or should not be executed). A test for which
>> an
>> assumption
>>  * fails should not generat

Re: Assumption fail treated as unexcepted exception?!

[Martin Gainty]

initCause(e);
}

@Override
public String getMessage() {
return StringDescription.asString(this);
}

public void describeTo(Description description) {
if (fAssumption != null) {
description.appendText(fAssumption);
}

if (fValueMatcher) {
// a value was passed in when this instance was constructed; print 
it
if (fAssumption != null) {
description.appendText(": ");
}

description.appendText("got: ");
description.appendValue(fValue);

if (fMatcher != null) {
description.appendText(", expected: ");
description.appendDescriptionOf(fMatcher);
}
}
}
}

//at least with junit 4.12 if AssumptionViolatedException will not FAIL the 
test-case
//AssumptionViolatedException falls between the exception-handlers to produce 
ERROR

can you verify with junit author(s) AssumptionViolatedException  does not FAIL 
test-case is intended behaviour?
martin







From: Markus KARG 
Sent: Sunday, August 16, 2020 1:39 PM
To: 'Maven Developers List' 
Subject: AW: Assumption fail treated as unexcepted exception?!

The debug output is quite huge, so I won't put it here. What in particular
shall I lookup inside of that? The environment is:

Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
2019-04-04T21:00:29+02:00)
Maven home: C:\Program Files\apache-maven-3.6.1
Java version: 1.8.0_212, vendor: Azul Systems, Inc., runtime: C:\Program
Files\zulu8.38.0.13-ca-jdk8.0.212-win_x64\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"
...
[DEBUG] Goal:
org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test)
[DEBUG] Style: Regular
[DEBUG] Configuration: 


${maven.test.additionalClasspath}
  -Xmx384m
  
  ${childDelegation}
  

${maven.test.dependency.excludes}
  ${maven.surefire.debug}
  ${dependenciesToScan}
  ${disableXmlReport}
  ${enableAssertions}
  ${surefire.encoding}
  
true
  
  ${excludedGroups}
  ${surefire.excludesFile}

${surefire.failIfNoSpecifiedTests}
  ${failIfNoTests}
  ${forkCount}
  ${forkMode}
  ${surefire.exitTimeout}

${surefire.timeout}
  ${groups}
  ${surefire.includesFile}
  ${junitArtifactName}
  ${junitPlatformArti
factName}
  ${jvm}
  
  ${objectFactory}
  ${parallel}
  
  ${parallelOptimized}

${surefire.parallel.forcedTimeout}

${surefire.parallel.timeout}
  ${perCoreThreadCount}
  ${plugin.artifactMap}
  
  ${surefire.printSummary}
  ${project.artifactMap}
  
  ${maven.test.redirectTestOutputToFile}
  
  ${surefire.reportFormat}
  ${surefire.reportNameSuffix}
  
  ${surefire.rerunFailingTestsCount}
  ${reuseForks}
  ${surefire.runOrder}
  ${surefire.shutdown}
  ${maven.test.skip}
  ${surefire.skipAfterFailureCount}
  ${maven.test.skip.exec}
  ${skipTests}
  ${surefire.suiteXmlFiles}
  
C:\Program Files\apache-maven-3.6.1
  
  ${tempDir}
  ${test}
  
  ${maven.test.failure.ignore}
  ${testNGArtifactName}
  
  ${threadCount}
  ${threadCountClasses}
  ${threadCountMethods}
  ${threadCountSuites}
  ${trimStackTrace}
  ${surefire.useFile}
  ${surefire.useManifestOnlyJar}
  ${surefire.useSystemClassLoader}
  ${useUnlimitedThreads}
  ${basedir}
  
  

...
[ERROR]
testProofClaim(org.apache.maven.plugins.dependency.fromConfiguration.TestCop
yMojo)  Time elapsed: 0.146 s  <<< ERROR!
org.junit.AssumptionViolatedException: always skip
at
org.apache.maven.plugins.dependency.fromConfiguration.TestCopyMojo.testProof
Claim(TestCopyMojo.java:76)
...

IIUC, Maven debug doesn't contain any really specific information besides
what I aready assumed: Surefire treats org.junit.AssumptionViolatedException
as an error but not as a request to skip the test.

This can be reproduced with this really simple test case:
https://github.com/mkarg/maven-dependency-plugin/commit/af257d7987fc41ac4377
4d2dca60b201979d11a2 - as you can see, I just ask JUnit 4.13 to fail the
assumptions, and JUnit CORRECTLY throws AssumptionViolatedException - but
Maven seems to not specifically deal with it.

-Markus


-Ursprüngliche Nachricht-
Von: Martin Gainty [mailto:mgai...@hotmail.com]
Gesendet: Sonntag, 16. August 2020 14:24
An: Maven Developers List
Betreff: Re: Assumption fail treated as unexcepted exception?!

MG>below


From: Markus KARG 
Sent: Sunday, August 16, 2020 7:40 AM
To: dev@maven.apache.org 
Subject: Assumption fail treated as unexcepted exception?!

Guys,



I'm stuck with working on a new feature due to this, so I hope you can help
me quickly:



JUnit knows assumptions, assertions and exceptions. Failing assertions will
FAIL tests (hence will fail maven builds). Failing assumptions will SKIP
tests (hence will pass maven builds). Exceptions will ERROR tests (hen

Re: Assumption fail treated as unexcepted exception?!

[Martin Gainty]

MG>below


From: Markus KARG 
Sent: Sunday, August 16, 2020 7:40 AM
To: dev@maven.apache.org 
Subject: Assumption fail treated as unexcepted exception?!

Guys,



I'm stuck with working on a new feature due to this, so I hope you can help
me quickly:



JUnit knows assumptions, assertions and exceptions. Failing assertions will
FAIL tests (hence will fail maven builds). Failing assumptions will SKIP
tests (hence will pass maven builds). Exceptions will ERROR tests (hence
will break maven builds). Unfortunately today I noticed that assumptions
actually ERROR test (hence fail builds) in Maven!



(I simply added another test to maven dependency plugin which contains an
always-failing assumption to proof the claim)



[INFO] Results:

[INFO]

[ERROR] Errors:

[ERROR]   TestCopyMojo.proofClaim:274 ┐ AssumptionViolated always skip

MG>get maven environment and debug information
MG>mvn -e -X
MG>also I know Junit 5.4.2 needs Hamcrest to be on classpath
MG>can you tell us which version of Junit you are using?

-Markus Karg
~gruss~
~martin~

Re: Welcome the new Maven committers: Maarten Mulders en Martin Kanters

[Martin Gainty]

welkom martin!

martin


From: Karl Heinz Marbaise 
Sent: Friday, July 10, 2020 6:04 PM
To: Maven Developers List 
Subject: Re: Welcome the new Maven committers: Maarten Mulders en Martin Kanters

Hi,

On 10.07.20 21:12, Robert Scholte wrote:
> Hi,
>
> On behalf of the Apache Maven PMC I am pleased to announce that
> Maarten Mulders en Martin Kanters has been voted in as new Apache Maven 
> committers
> and they've both accepted this invitation.
>
> Welcome on board and have a lot of fun!

Welcome on board to both of you.

Welcome Maarten Mulders.
Welcome Martin Kanters.


Kind regards
Karl Heinz Marbaise

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: migrating Apache Resource Bundles from svn to Git

[Martin Gainty]

Karl helps everyone who has questions He will always answer any questions I ask 
no matter how trivial Viel Gluck!

--
Sent from my Alcatel GO FLIP V

On Jun 25, 2020 2:57 AM, Robert Scholte  wrote:
I don't mind joining as committer. I actually was surprised Karl Heinz is 
already PMC.

Robert
On 25-6-2020 08:37:55, Hervé BOUTEMY  wrote:
yes, Creadur could be a good home both for these bundles and the Apache parent
POM, to manage Apache project conventions for Maven separately from Maven code
itself
And if some of us want to continue work on it (given we produce plugins that
are to be updated in Apache parent POM), they could join Creadur
https://creadur.apache.org/

Regards,

Hervé

Le mercredi 24 juin 2020, 21:40:41 CEST Robert Scholte a écrit :
> I've been thinking about asking if project Creadur wants this code, since
> they also maintain the rat maven plugin. Looks quite related to me.
>
> Robert
>
> On 24-6-2020 00:00:09, Hervé BOUTEMY wrote:
> the little discussion now gave me an opinion:
> if nobody objects, I'll migrate the bundles to one unique Git repository:
> - name: maven-apache-resource-bundles.git
> - version will be 1.5-SNAPSHOT
> - containing 3
> org.apache.apache.resources:apache-(jar|jar-txt|incubator-disclaimer)-resou
> rce-bundle for maven-remote-resources-plugin and
> apache-source-release-assembly-descriptor for maven-assembly-plugin
>
> Regards,
>
> Hervé
>
> Le mardi 23 juin 2020, 00:11:41 CEST Hervé BOUTEMY a écrit :
> > it seems there is a misunderstanding: it's not 4 parent POMs
> > it's resource bundles, that are used with maven-assembly-plugin or maven-
> > remote-resources-plugin in Apache parent POM [1]
> >
> > see https://maven.apache.org/apache-resource-bundles/index.html for some
> > description
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://github.com/apache/maven-apache-parent/blob/master/pom.xml
> >
> > Le lundi 22 juin 2020, 20:31:16 CEST Robert Scholte a écrit :
> > > On 22-6-2020 00:25:39, Hervé BOUTEMY wrote:
> > > > I agree: independent release cycles means independent repositories.
> > >
> > > in the past, we had 4 independent Maven parent POMs [1] under one unique
> > > svn trunk, with 4 separate release cycles, many votes/hard maintenance
> > > (having a new parent POM release for plugins, for example) and hard to
> > > use (version of parent for plugins was not the same as shared parent, or
> > > pure maven parent). When switching to Git, we switched to one Git
> > > repository and one unique release cycle: a vote for a release remains
> > > not
> > > so easy (because getting votes is not easy), but at least there is only
> > > one for every parent POM. Robert Scholte: I think there's a small
> > > difference, these poms all inherit from the apache-parent. If there's a
> > > new parent, it makes sense to release them all at once.
> > >
> > >
> > >
> > > We have the same initial situation with resource bundles: the
> > > independence
> > > of the release cycles inside the unique trunk are not written in stone,
> > > we
> > > can simplify and hope that it will ease maintenance in addition to ease
> > > migration. Or we can make efforts to split: for plugins or shared
> > > components, splitting was the only reasonable option.
> > >
> > > > I wonder if they should be part of the Maven group, looks more like a
> > > > they
> > > > are maintained by us by coincidence. Is there some ASF resources group
> > > > to
> > > > maintain this (or worth introducing)?
> > >
> > > exactly like the ASF parent POM
> > > If you find someone who want to maintain, don't hesitate
> > > Robert Scholte:
> > > Let me see if I can get them out of the Maven project.
> > > I don't mind maintaining these parents, but I'd prefer have a clear
> > > separation on which parts are clearly Maven and which actually ASF
> > >
> > > thanks,
> > > Robert
> > >
> > >
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1] https://maven.apache.org/pom/index.html
> > >
> > > Le dimanche 21 juin 2020, 21:36:37 CEST Robert Scholte a écrit :
> > > > I agree: independent release cycles means independent repositories.
> > > > I wonder if they should be part of the Maven group, looks more like a
> > > > they
> > > > are maintained by us by coincidence. Is there some ASF resources group
> > > > to
> > > > maintain this (or worth introducing)?
> > > >
> > > > thanks,
> > > > Robert
> > > >
> > > > On 21-6-2020 19:14:47, Michael Osipov wrote:
> > > >
> > > > Am 2020-06-20 um 00:31 schrieb Hervé BOUTEMY:
> > > > > one of the last part not yet done, because there is a choice to do:
> > > > > - migrate to one multi-module Git repository?
> > > > > - or split each bundle into a separate Git repo?
> > > >
> > > > These two question can be answered when we know whether these modules
> > > > are loosely coupled of strongly interrelated like our POM parents.
> > > > If the former, separate repos, if the latter one repo.
> > > >
> > > >
> > > > 

Re: Running mojo unit test in the debugger

[Martin Gainty]

seem to recall plexus container implementor will need to configure plexus 
container at  
META-INF/plexus/plexus.xml

https://codehaus-plexus.github.io/plexus-containers/plexus-container-default/

I havent used plexus since sisu and google-guice were released

does this answer your question?
m.


From: Benson Margulies 
Sent: Friday, May 8, 2020 5:16 PM
To: Maven Developers List 
Cc: volf...@google.com 
Subject: Running mojo unit test in the debugger

I am trying to recall how to debug a Junit test that uses
AbstractMojoTestCase. Simply asking an IDE to debug the test fails with
plexus container errors. I cannot recall if these can be debugged as
ordinary unit tests somehow, or whether we need to set remote debugging
options to the surefire plugin and attach the debugger.

Re: Running mojo unit test in the debugger

[Martin Gainty]

From: Benson Margulies 
Sent: Friday, May 8, 2020 5:16 PM
To: Maven Developers List 
Cc: volf...@google.com 
Subject: Running mojo unit test in the debugger

I am trying to recall how to debug a Junit test that uses
AbstractMojoTestCase. Simply asking an IDE to debug the test fails with
plexus container errors. I cannot recall if these can be debugged as
ordinary unit tests somehow, or whether we need to set remote debugging
options to the surefire plugin and attach the debugger.

Re: New Commiter: Elliotte Rusty Harold

[Martin Gainty]

welcome Elliotte!

martin


From: Karl Heinz Marbaise 
Sent: Friday, December 13, 2019 11:29 AM
To: dev@maven.apache.org ; elh...@ibiblio.org 

Subject: New Commiter: Elliotte Rusty Harold

Hi Elliotte,

the Project Management Committee (PMC) for Apache Maven
has invited you Elliotte to become a committer and
we are pleased to announce that you have accepted the invitation.

Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.

Elliotte, welcome and enjoy!

Kind regards
Karl Heinz Marbaise

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Surefire CNFE

[Martin Gainty]

CNFE when running surefire means
Isolated (TEST) Classloader cannot load the dependency containing that class
In your case that dependency is junit

if it was up to me i would discontinue use of Isolated Classloader in favour of 
using system classloader
the only reason Isolated cl was used was the path limitation for System 
ClassLoader (initially 4k)
now all paths including CLASSPATH can be 32k so restricted classpath length 
should not be an issue

ymmv
martin-

Re: Maven Security, @Component and MNG-4384

[Martin Gainty]

  
  server001
  my_login
  my_password
  ${user.home}/.ssh/id_dsa
  some_passphrase
  664
  775
  


from ${MAVEN_HOME}/conf/settings.xml

https://maven.apache.org/ref/3.3.9/maven-settings-builder/apidocs/org/apache/maven/settings/crypto/SettingsDecryptionRequest.html#setServers(java.util.List)

so your org.apache.maven.settings.crypto.SettingsDecryptionRequest.setServers 
needs to gather up
the list of server ids from {MAVEN_HOME}/conf/settings.xml

not so clear as javadoc is missing from maven-settings-builder site..romain can 
you post this info on
http://maven.apache.org/ref/3.6.1/maven-settings-builder/

?
thanks


From: Romain Manni-Bucau 
Sent: Monday, June 24, 2019 1:11 AM
To: Maven Developers List
Subject: Re: Maven Security, @Component and MNG-4384

Hi

Did you have a look to org.apache.maven.settings.crypto.SettingsDecrypter?

It can be injected as a component then you can call decrypt on it passing a
request to the method. You get a new null server if it is not encrypted or
the new server with everything in clear.

Would that work better for you?

Romain

Le lun. 24 juin 2019 à 03:31, Chris Graham  a écrit :

> Hi everyone,
>
> I need to add the ability to load users, passwords etc in a 3rd party
> plugin.
>
> It currently requires a userid and password in the  section
> of the pom (ugh), ideally, I'd like to look them up from the 
> section of settings.xml, and even better yet, make use of being able to
> decrypt passwords.
>
> So I did what we all do, and go and look to see what has been done before,
> and I came across this:
>
>
> /maven-scm/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/AbstractScmMojo.java:
>
> /**
>  * When this plugin requires Maven 3.0 as minimum, this component can
> be removed and o.a.m.s.c.SettingsDecrypter be
>  * used instead.
>  */
> @Component( hint = "mng-4384" )
> private SecDispatcher secDispatcher;
>
> and:
>
>
> /maven-scm/maven-scm-plugin/src/main/resources/META-INF/plexus/components.xml:
>
> 
>   
> 
>
> org.sonatype.plexus.components.sec.dispatcher.SecDispatcher
>   mng-4384
>
>
> org.sonatype.plexus.components.sec.dispatcher.DefaultSecDispatcher
>   
> 
>   org.sonatype.plexus.components.cipher.PlexusCipher
>   mng-4384
>   _cipher
> 
>   
>   
>
> <_configuration-file>~/.m2/settings-security.xml
>   
> 
> 
>   org.sonatype.plexus.components.cipher.PlexusCipher
>   mng-4384
>
>
> org.sonatype.plexus.components.cipher.DefaultPlexusCipher
> 
>   
> 
>
> So, I'm left with the question, what is the current, correct way of
> accessing userids, passwords (encrypted or not)?
>
> I could simply, copy the same approach, but I'd prefer not too, as it's a
> good opportunity 'to do it right'.
>
> Any suggestions?
>
> Would we then consider updating the existing maven plugins to support this?
>
> @Stephen, sounds like a good idea for a blog entry? ;)
>

Re: New committer: Enrico Olivelli

[Martin Gainty]

benvenuto enrico!

From: Stephen Connolly 
Sent: Friday, December 14, 2018 5:04 PM
To: Maven Developers List
Subject: Re: New committer: Enrico Olivelli

Welcome!

On Fri 14 Dec 2018 at 21:07, Robert Scholte  wrote:

> The Project Management Committee (PMC) for Apache Maven
> has invited Enrico Olivelli to become a committer and
> we are pleased to announce that he has accepted.
>
> Being a committer enables easier contribution to the
> project since there is no need to go via the patch
> submission process. This should enable better productivity.
>
> Enrico, welcome and enjoy!
>
> thanks,
> Robert
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Sent from my phone

Re: Is compile classpath deterministic?

[Martin Gainty]

i  am curious as to your ${packaging.type} from both pom.xml resolve to?

https://javaee.groups.io/g/jersey/topic/jersey_2_26_and_jax_rs_2_1/6052416?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,6052416

?

From: Dagang Wei 
Sent: Saturday, October 20, 2018 6:23 PM
To: dev@maven.apache.org
Subject: Is compile classpath deterministic?

Hi folks,

I ran into an issue of compile dependency conflict caused by same class
name (javax.ws.rs.core.Response) with different method signatures in
different artifacts (jsr311-api and javax.ws.rs-api). On one machine, it
compiles because it compiles against  javax.ws.rs-api; on another machine,
it doesn't, because it compiles against jsr311-api.

So, I am wondering if the compile classpath deterministic? If not, can we
make it deterministic so that it is easier to discover and debug dependency
issues?

Thanks!
Dagang

Re: Welcome Sylwester Lachiewicz to the Apache Maven Team

[Martin Gainty]

wilkommen sylwester

i look forward to reading your jira reports

martin

From: Karl Heinz Marbaise 
Sent: Wednesday, September 5, 2018 1:27 PM
To: Maven Developers List; Sylwester Lachiewicz
Subject: Re: Welcome Sylwester Lachiewicz to the Apache Maven Team

Hi Sylwester,

On 05/09/18 19:20, Sylwester Lachiewicz wrote:
> Hi Everyone,
>
> thank you for so warm welcome - my adventure with helping Maven Project
> began not so long ago, and the more I am more than willing to join you.

Great to hear this...


> We have some work in Jira and a PRs to review - I'm going to verify it.

Yeah we much JIRA's 

 >
And
> I hope The Maven Team in the future with commits.

That was the idea ;-)...


Kind regards
Karl Heinz Marbaise
>
> Best regards
> Sylwester
>
> pon., 3 wrz 2018 o 19:21 użytkownik Tibor Digana 
> napisał:
>
>>   Welcome Sylwester!
>>
>> On Sun, Sep 2, 2018 at 12:58 PM Karl Heinz Marbaise 
>> wrote:
>>
>>> Hi to all,
>>>
>>> On behalf of the Apache Maven PMC I am pleased to announce that
>>> Sylwester Lachiewicz has been voted in as a new Apache Maven committer.
>>>
>>> Sylwester, welcome on board and have a lot of fun!
>>>
>>> Thanks.
>>>
>>> Kind regards
>>> Karl Heinz Marbaise
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>>
>


Mit freundlichem Gruß
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz MarbaiseUSt.IdNr: DE191347579
Hauptstrasse 177
52146 Würselen   http://www.soebes.de

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Welcome Christian Stein to the Apache Maven Team

[Martin Gainty]

Willkommen Christian!


martin
__



From: Robert Scholte 
Sent: Monday, May 7, 2018 4:01 PM
To: dev@maven.apache.org; Apache Maven Users
Subject: Welcome Christian Stein to the Apache Maven Team

Hi,

On behalf of the Apache Maven PMC I am pleased to announce that Christian
Stein (sor) has been voted in as a new Apache Maven committer.

Christian, welcome on board and have a lot of fun!

thanks,
Robert

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [MNG-6169] Lifecycle/binding plugin version updates

[Martin Gainty]

Good Morning Michael


any timeline on pom.xml creation for tomcat source distros?

i d/l 8.5.4

https://archive.apache.org/dist/tomcat/tomcat-8/v8.5.4/src/

and i see only 1 pom.xml for jdbc-pool


but I see 3 build.xml

find . name build.xml

./modules/jdbc-pool/build.xml
./res/deployer/build.xml
./webapps/ROOT/build.xml


for each attempt to track down a TC problem i am forced to create pom.xml from 
scratch

so I can build, package and deploy the war to locate the problem


I of course will help you *behind the scenes* for any assistance you may require


thanks,

Martin
__

"why do you help the british?..in 1812 they burned your capitol"..The Great 
Escape



From: Michael Osipov 
Sent: Friday, May 12, 2017 6:58 PM
To: Maven Developers List
Subject: Re: [MNG-6169] Lifecycle/binding plugin version updates

Am 2017-05-13 um 00:30 schrieb Hervé BOUTEMY:
> Le vendredi 12 mai 2017, 13:50:37 CEST Michael Osipov a écrit :
>> Am 2017-05-12 um 08:25 schrieb Hervé BOUTEMY:
>>> Jenkins build is not flaky: it is strict on dependency resolution from
>>> cache, which is an intent, not a bug
>>
>> This pretty much explains why a lot of ITs fail here at work with a
>> empty repo. I will to work this through.
> beware to not make the ITs fail with previous Maven versions

All I did is this:
https://github.com/apache/maven-integration-testing/commit/5c01864e44c7c96cac95545e8568acd044b6d7dc
[https://avatars3.githubusercontent.com/u/573017?v=3=200]

[MNG-6169] Lifecycle/binding plugin version updates · 
apache/maven-integration-testing@5c01864
github.com
MNG-5895 and MNG-6090 with ArtifactResolutionException. Add dependencies Maven 
Resources Plugin 3.0.2 and Maven Surefire 2.2.0 to bootstrap's group 7.





>>
>>> that's why I don't like changing default plugins versions:
>>>
>>> 1. depending on default plugins versions is a bad practice: IMHO, having
>>> old plugins helps people know that they should not rely on it
>>
>> This basically means that people would need to provide versions
>> explicitly in the POMs starting with Maven 4.
> ??? Why are you talking about Maven 4?

If you are saying that depending on default version is a bad practice it
actually means to me that this should change in the new major. Shouldn't it?

>> Looks like a lot of
>> hassle, doesn't it? I'd better see this in the Super POM rather embedded
>> in a JAR.
> ??? "embedded in a JAR"? what did I say that lead to something like this?

I assumed that your idea is rather nothing this up to the Super POM:
./maven-model-builder/src/main/resources/org/apache/maven/model/pom-4.0.0.xml

>>> 2. people who do a "dependency:go-offline" with a previous Maven version
>>> but run offline with updated Maven version will see their build fail and
>>> report about dependency:go-offline not being reliable, which is
>>> technically not true, but is sensitive to Maven version (something that
>>> is hard to explain)
>>
>> Pretty good point. We should actually ad this information to the goal
>> doc. This will also fail if your change your POM.
>>
>>> On the first objection, it's a question of choice on how to promote the
>>> good practice about explicitely choosing your plugins versions
>>>
>>> On the second objection, I had an idea of Maven core improvement that
>>> would fix the go-offline dependency on Maven version used: what if Maven
>>> core distribution did contain a (read-only) local repo with default
>>> plugins already resolved?
>>>
>>> With such a feature, go-offline would not be dependant on Maven version
>>> used (starting from the Maven version that has this pre-built repo). And
>>> user would better see the default dependencies by looking at this
>>> pre-builot repo = something I'm sure they will do (but they don't have a
>>> look at lifecycle definition files, which are opaque for them)
>>>
>>> I didn't have time to work on implementing this idea, I suppose this would
>>> just require a new default repository with file://${maven.home}/default-
>>> plugins/ url, and to fill this repo at build time with appropriate
>>> go-offline
>> Sounds like a good idea but would produce a lot of bloat, wouldn't it?
> what do you call "bloat"? and what do you call "a lot"? Is it better to
> download plugin artifacts from network instead?
>
>> All plugin dependency trees. This should be configurable in settings.xml
>> and MDEP should provide a goal to populate such a repo.
>> I am afraid that no one will pick this up anytime soon.
>>
>> Do you know completely reject the issue to be merged?
> I'd like to have us understand each other:
> - what do you expect to win?
> - what do we loose?
> I know doing this update is easy to do and corresponds to a lot of good
> intentions on 

Re: Taking Security Seriously

[Martin Gainty]

From: Bernd Eckenfels 
Sent: Monday, December 5, 2016 5:10 PM
To: Maven Developers List
Subject: Re: Taking Security Seriously

Having artifact checksums (hashes not signatures) in POM dependency 
declarations would be cool, but that is not what .md5 or .asc is used for.

Gruss
Bernd
--
http://bernd.eckenfels.net




On Mon, Dec 5, 2016 at 10:45 PM +0100, "Alexander Kjäll" 
 wrote:










Maybe we are talking about different attack scenarios?

The vector I would like to protect against is that someone is able to
inject false binaries in a caching nexus server (or over the network
if https is not used).

The way I envision the trust to be established is:

The developer goes either to maven central or the projects homepage
and copies the  block needed to add the dependency to
pom.xml. The dependency block includes information that can be used to
cryptographically guarantee that the binary that ends up in the build
is the same one that the original developer published.

I think it would be possible to simplify the verification of gpg
signatures and make it be possible to automate it in a resonable
manner.

MG>Sign project artifact, the POM, and attached artifacts with GnuPG for 
deployment is implemented via maven-gpg-plugin:sign (where default binding for 
maven-gpg-plugin is verify phase)

http://maven.apache.org/plugins/maven-gpg-plugin/sign-mojo.html
Apache Maven GPG Plugin – 
gpg:sign
maven.apache.org
gpg:sign. Full name: org.apache.maven.plugins:maven-gpg-plugin:1.6:sign. 
Description:



best regards
Alexander Kjäll


2016-12-05 18:29 GMT+01:00 Hervé BOUTEMY :
> I fear the proposed change would not improve security but lower it:
> if the pom contains the reference to a key "to be used to sign the artifact",
> anybody wanting to change the content will just change the key reference to a
> value it owns
>
> yes, knowing which keys you should trust to sign which artifact is not easy,
> but I fear there is no automagic way to automate trust
>
> What I'd want to do is to improve the dependencies report to show the key used
> to sign the artifact: that would improve people knowledge of who they are
> trusting: but that would not mean that they can trust them...
>
> Regards,
>
> Hervé
>
> Le lundi 5 décembre 2016, 09:31:20 CET Alexander Kjäll a écrit :
>> Regarding verifying the gpg signature, as a contributor to the gpg
>> verify plugin here:
>>
>> http://www.simplify4u.org/pgpverify-maven-plugin/index.html
>>
>> I have some thoughts on why the current infrastructure doesn't really
>> help us to verify the signatures in practice:
>>
>> 1) Very hard to know what key are the correct one, as it's not specified
>> anywhere in the pom, you need to contact the developer of the jar that
>> you want to verify and ask them to publish what key they used to sign
>> the project with. It would be nice to have a  tag in the pom
>> in order to resolve this.
>>
>> 2) Verifying the signature can't really be done with a maven plugin, as
>> those are downloaded over the same channels that the jar's are
>> downloaded over, and there is no method for maven to verify that it
>> downloaded the correct plugin.
>>
>> I opened a bug about this problem a couple of years ago, but since it's
>> not really possible to fix this without changing the structure of the
>> pom i didn't even bother to write a patch for it.
>>
>> If there is a chance that a fix for this problem would be included, then
>> I would be happy to try to write a patch for it.
>>
>> best regards
>> Alexander Kjäll
>>
>> On 05. des. 2016 08:23, Hervé BOUTEMY wrote:
>> > AFAIK, checksums are there only to avoid stupid download/upload
>> > distorsion.
>> > What gives real security is *signature* done by developers, ie .asc files,
>> > that use other hash algorithms than these little .md5 and .sha1 files.
>> > That's why we recommend to verify *the signature* [1].
>> >
>> > Another topic: https://www.apache.org/dev/release-signing.html is not
Signing Releases - Apache Software 
Foundation
www.apache.org
Abstract¶ This document gives a basic primer on the wide subject of release 
signing. See under Further reading for links to authoritative sources of deeper 
information.



>> > about
>> > Maven repository but is about Apache releases that are distributed as part
>> > of Apache official (source) releases, distributed by Apache mirrors [2]
>> >
>> > AFAIK, security is taken seriously: checksums are just not really part of
>> > that security, they are only checksums.
>> >
>> > Regards,
>> >
>> > Hervé
>> >
>> > [1] http://maven.apache.org/download.cgi
Apache Download Mirrors - Apache Maven
maven.apache.org
We suggest the following mirror site for your download: 
http://apache.mirrors.lucidnetworks.net/ Other mirror sites are suggested 

Re: Logging for 3.0.x and >=3.1.0

[Martin Gainty]

From: Jason Pyeron 
Sent: Wednesday, November 23, 2016 2:59 PM
To: dev@maven.apache.org
Subject: Logging for 3.0.x and >=3.1.0

Working on a plugin right now and it needs to work in 3.0 as well as 3.3.

Scratching my head on can we use slf4j in 3.0 or is there a backwards 
compatibility logic to put in.

MG>AFAIK SLF4J 1.5.6 changed StaticLoggerBinder.SINGLETON from public static to 
private

IllegalAccessError exceptions when using SLF4J. Why is that?

Here are the exception details.

Exception in thread "main" java.lang.IllegalAccessError: tried to access field
org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory
   at org.slf4j.LoggerFactory.(LoggerFactory.java:60)

This error is caused by the static initializer of the LoggerFactory class 
attempting to directly access the SINGLETON field of 
org.slf4j.impl.StaticLoggerBinder. While this was allowed in SLF4J 1.5.5 and 
earlier, in 1.5.6 and later the SINGLETON field has been marked as private 
access.

If you get the exception shown above, then you are using an older version of 
slf4j-api, e.g. 1.4.3, with a new version of a slf4j binding, e.g. 1.5.6. 
Typically, this occurs when your Maven pom.ml file incorporates hibernate 3.3.0 
which declares a dependency on slf4j-api version 1.4.2. If your pom.xml 
declares a dependency on an slf4j binding, say slf4j-log4j12 version 1.5.6, 
then you will get illegal access errors.

To see which version of slf4j-api is pulled in by Maven, use the maven 
dependency plugin as follows.

mvn dependency:tree

http://slf4j.org/faq.html
SLF4J FAQ
slf4j.org
Binding Requirements; slf4j-nop: JDK 1.5: slf4j-simple: JDK 1.5: slf4j-log4j12: 
JDK 1.5, plus any other library dependencies required by the log4j appenders in 
use



MG>does this help?

-Jason
MG>enjoy your holiday

--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-   -
- Jason Pyeron  PD Inc. http://www.pdinc.us -
PD Inc.
www.pdinc.us
PD Inc is a business solutions provider with expert solutions tailored to 
consulting projects on an enterprise-wide scale. We have been able to leverage 
our vast ...



- Principal Consultant  10 West 24th Street #100-
- +1 (443) 269-1555 x333Baltimore, Maryland 21218   -
-   -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

RE: upgrade maven plugin to run with asm 6?

[Martin Gainty]

i find throwing everything in the kitchen sink and hoping all the dishes get 
cleaned doesnt workpick one variable such as maven-plugin-plugin and introduce 
each new version by a point release3.0 causes exception3.1 causes 
exception...3.5 works with asm6 and JDK 1.9
eventually you'll determine which version works with your specific environment 
configuration

ToDo: can someone update README for 3.5 that 3.5 works with JDK1.9 and ASM6?
thanks romainMartin
__ 



> From: rmannibu...@gmail.com
> Date: Mon, 10 Oct 2016 21:04:50 +0200
> Subject: RE: upgrade maven plugin to run with asm 6?
> To: dev@maven.apache.org
> 
> Oh tested 3.4 but missed 3.5. 3.5 solved the issue!
> 
> Thanks!
> 
> Le 10 oct. 2016 20:31, "Martin Gainty" <mgai...@hotmail.com> a écrit :
> >
> >
> >
> >
> > > From: rmannibu...@gmail.com
> > > Date: Mon, 10 Oct 2016 17:07:54 +0200
> > > Subject: Re: upgrade maven plugin to run with asm 6?
> > > To: dev@maven.apache.org
> > >
> > > 2016-10-10 16:54 GMT+02:00 Martin Gainty <mgai...@hotmail.com>:
> > >
> > > >
> > > >
> > > >
> > > > > From: rmannibu...@gmail.com
> > > > > Date: Mon, 10 Oct 2016 15:10:33 +0200
> > > > > Subject: upgrade maven plugin to run with asm 6?
> > > > > To: dev@maven.apache.org
> > > > >
> > > > > Hi guys,
> > > > >
> > > > > is there some plans to upgrade maven plugin to asm6 (thinking
> > > > > to maven-plugin-tools-annotations and maven-plugin-plugin and more
> > > > > concretely to DefaultMojoAnnotationsScanner used to generate the
> help
> > > > mojo)?
> > > > >
> > > > > I know there is only the alpha our ATM but I think it would enable
> users
> > > > to
> > > > > start building using asm 6 instead of preventing them to run their
> build
> > > > > and the later upgrade would be smooth.
> > > > MG>craft a q test-harness
> > > > MG>switch JAVA to JDK 1.8
> > > > MG>in test-harness substitute in asm-6 into dependency-management of
> > > > parent pom
> > > > MG>mvn package and observe:
> > > > MG>ANY TEST ERRORS ?
> > > > MG>ANY TEST FAILURES?
> > > > MG>is JDKProxy being implemented to implement Interfaces?
> > > > MG>is asm-6 being called to extend subclasses?
> > > > MG>http://stackoverflow.com/questions/10664182/what-is-
> > > > the-difference-between-jdk-dynamic-proxy-and-cglib
> > > > MG>if all of these scenarios pass I think you will have a *convincing
> > > > case* to upgrade asm to 6 in all plugins
> > > > MG>I have a few spare cycles today so let me know if you need any
> > > > assistance
> > > >
> > > >
> > > so concretely I wanted to upgrade
> > > https://github.com/tomitribe/crest/tree/master/crest-maven-plugin to
> asm6
> > > to support java 9 (not sure why you spoke of java 8, typo?) but the side
> > > effect of upgrading it as a dependency of my project was to break the
> > > maven-plugin-plugin. I'm not sure why isolation was broken but I'm very
> > > concerned cause soon we'll upgrade the whole tomee stack to asm 6
> (xbean,
> > > openjpa, cxf, openwebbeans, batchee, tomee itself and probably a few I
> > > forget) and most of them have maven plugins and would break.
> > >
> > > It fails with a NPE in Type.getProxyClass IIRC so maven annotation
> scanner
> > > doesn't work on java 9.
> > MG>JDK 1.9 annotation processor has been "tweaked"
> > MG>http://openjdk.java.net/jeps/217
> > MG>which is the reason why I suggested using the older annotation scanner
> > MG>do we know if error originates from ASM6 upgrade, maven-plugin or
> JDK1.9 that said can you post a bug in JIRA?
> > MG>https://maven.apache.org/issue-tracking.html
> > >
> > > Will be a bit short to help in the ~2 coming weeks but if nothing moved
> > > next month I'll try to hack something up for sure!
> > >
> > >
> > > >
> > > > >
> > > > > Romain Manni-Bucau
> > > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > > > rmannibucau> |
> > > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > > > <http://www.tomitribe.com> | JavaEE Factory
> > > > > <https://javaeefactory-rmannibucau.rhcloud.com>
> > > >
> >
  

RE: upgrade maven plugin to run with asm 6?

[Martin Gainty]

> From: rmannibu...@gmail.com
> Date: Mon, 10 Oct 2016 17:07:54 +0200
> Subject: Re: upgrade maven plugin to run with asm 6?
> To: dev@maven.apache.org
> 
> 2016-10-10 16:54 GMT+02:00 Martin Gainty <mgai...@hotmail.com>:
> 
> >
> >
> >
> > > From: rmannibu...@gmail.com
> > > Date: Mon, 10 Oct 2016 15:10:33 +0200
> > > Subject: upgrade maven plugin to run with asm 6?
> > > To: dev@maven.apache.org
> > >
> > > Hi guys,
> > >
> > > is there some plans to upgrade maven plugin to asm6 (thinking
> > > to maven-plugin-tools-annotations and maven-plugin-plugin and more
> > > concretely to DefaultMojoAnnotationsScanner used to generate the help
> > mojo)?
> > >
> > > I know there is only the alpha our ATM but I think it would enable users
> > to
> > > start building using asm 6 instead of preventing them to run their build
> > > and the later upgrade would be smooth.
> > MG>craft a q test-harness
> > MG>switch JAVA to JDK 1.8
> > MG>in test-harness substitute in asm-6 into dependency-management of
> > parent pom
> > MG>mvn package and observe:
> > MG>ANY TEST ERRORS ?
> > MG>ANY TEST FAILURES?
> > MG>is JDKProxy being implemented to implement Interfaces?
> > MG>is asm-6 being called to extend subclasses?
> > MG>http://stackoverflow.com/questions/10664182/what-is-
> > the-difference-between-jdk-dynamic-proxy-and-cglib
> > MG>if all of these scenarios pass I think you will have a *convincing
> > case* to upgrade asm to 6 in all plugins
> > MG>I have a few spare cycles today so let me know if you need any
> > assistance
> >
> >
> so concretely I wanted to upgrade
> https://github.com/tomitribe/crest/tree/master/crest-maven-plugin to asm6
> to support java 9 (not sure why you spoke of java 8, typo?) but the side
> effect of upgrading it as a dependency of my project was to break the
> maven-plugin-plugin. I'm not sure why isolation was broken but I'm very
> concerned cause soon we'll upgrade the whole tomee stack to asm 6 (xbean,
> openjpa, cxf, openwebbeans, batchee, tomee itself and probably a few I
> forget) and most of them have maven plugins and would break.
> 
> It fails with a NPE in Type.getProxyClass IIRC so maven annotation scanner
> doesn't work on java 9.
MG>JDK 1.9 annotation processor has been "tweaked" 
MG>http://openjdk.java.net/jeps/217
MG>which is the reason why I suggested using the older annotation scanner
MG>do we know if error originates from ASM6 upgrade, maven-plugin or JDK1.9 
that said can you post a bug in JIRA?
MG>https://maven.apache.org/issue-tracking.html
> 
> Will be a bit short to help in the ~2 coming weeks but if nothing moved
> next month I'll try to hack something up for sure!
> 
> 
> >
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > <http://www.tomitribe.com> | JavaEE Factory
> > > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
  

RE: upgrade maven plugin to run with asm 6?

[Martin Gainty]

> From: rmannibu...@gmail.com
> Date: Mon, 10 Oct 2016 15:10:33 +0200
> Subject: upgrade maven plugin to run with asm 6?
> To: dev@maven.apache.org
> 
> Hi guys,
> 
> is there some plans to upgrade maven plugin to asm6 (thinking
> to maven-plugin-tools-annotations and maven-plugin-plugin and more
> concretely to DefaultMojoAnnotationsScanner used to generate the help mojo)?
> 
> I know there is only the alpha our ATM but I think it would enable users to
> start building using asm 6 instead of preventing them to run their build
> and the later upgrade would be smooth.
MG>craft a q test-harness
MG>switch JAVA to JDK 1.8
MG>in test-harness substitute in asm-6 into dependency-management of parent pom
MG>mvn package and observe:
MG>ANY TEST ERRORS ?
MG>ANY TEST FAILURES?
MG>is JDKProxy being implemented to implement Interfaces?
MG>is asm-6 being called to extend subclasses?
MG>http://stackoverflow.com/questions/10664182/what-is-the-difference-between-jdk-dynamic-proxy-and-cglib
MG>if all of these scenarios pass I think you will have a *convincing case* to 
upgrade asm to 6 in all plugins
MG>I have a few spare cycles today so let me know if you need any assistance


> 
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Wordpress Blog
>  | Github  |
> LinkedIn  | Tomitriber
>  | JavaEE Factory
> 
  

RE: Figure out compilerId

[Martin Gainty]

if I understand correctly compilerId attribute would *drive* compiler selection 
and exec parser/compiler for compilerId?
eclipse?
javac?

csharp?
Martin 
__ 



> Subject: Re: Figure out compilerId
> From: manf...@simpligility.com
> To: dev@maven.apache.org
> Date: Fri, 30 Sep 2016 18:18:26 +0200
> 
> Another way I thought of is to have a standard property that is used in the 
> compiler plugin config and the Android Maven Plugin just reads it as well in 
> the mojo. If its defined as a user property I think we wont even have to 
> write any code to read it.
> 
> Would that work? 
> 
> Manfred
> 
> 
> 
> Manfred Moser wrote on 2016-09-30 09:08:
> 
> > Hi,
> > 
> > We have some ongoing work on the Android Maven Plugin that will introduce a 
> > new
> > compiler (https://source.android.com/source/jack.html).
> > The compiler is set in the compilerId of the Maven Compiler Plugin. 
> > 
> > Now we would like the Android Maven Plugin to automatically know if this is 
> > set
> > and hence use its related mojo as well. Is there a standard way to access 
> > the
> > compilerId configuration of the current project? 
> > 
> > Or do we basically have to write the code to create the effective pom, 
> > access
> > the compiler plugin config and check for the compilerId being set to "jack" 
> > or
> > whatever. 
> > 
> > Any hints appreciated..
> > 
> > Manfred
> > 
> > References:
> > 
> > https://github.com/simpligility/android-maven-plugin/issues/536
> > https://issues.jboss.org/browse/FH-2743
> > 
> > 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> > 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
  

RE: slf4j runtime dependency for plugin

[Martin Gainty]

Fred:he is missing slf4j-nop as a runtime dependency specifically:
org.slf4j
slf4j-nop  
1.7.2runtime  

Martin--
__ 


> From: fred.co...@gmail.com
> Date: Mon, 15 Aug 2016 22:13:45 +1200
> Subject: Re: slf4j runtime dependency for plugin
> To: dev@maven.apache.org
> 
> Clearly it's going to matter to him if Maven fails to provide and it
> doesn't work. Some sort of dependency isolation not right somewhere?
> Something seems to be going on. You're right, but he's seeing behaviour
> that indicates something is amiss.
> 
> On Mon, Aug 15, 2016 at 6:37 PM, Michael Osipov  wrote:
> 
> > Am 2016-08-14 um 23:21 schrieb Christopher:
> >
> >> On Sun, Aug 14, 2016 at 4:31 PM Michael Osipov 
> >> wrote:
> >>
> >> Am 2016-08-12 um 23:48 schrieb Christopher:
> >>>
>  Hi,
> 
>  I use a plugin which has a runtime dependency on an slf4j
>  implementation,
>  but the plugin itself is built without declaring one in its pom. (
>  https://github.com/koraktor/mavanagaiata/issues/43)
> 
>  In some versions of Maven, I get a warning about slf4j not finding an
>  implementation. In other versions, it is silent.
> 
>  Was an slf4j implementation provided in newer versions to the execution
> 
> >>> of
> >>>
>  plugins?
> 
>  Will there be a multiple-binding conflict if the plugin itself provides
> 
> >>> one
> >>>
>  of its own to get rid of the warning on certain versions of maven which
>  result in that warning (I didn't see one when I tried)?
> 
>  If there is a risk of a conflict, which implementation would be
>  preferred
>  in order to converge on one provided by Maven?
> 
>  Is there another solution the plugin should seek?
> 
>  In general, what dependencies are plugins expected to provide, and what
>  dependencies are expected to be provided by Maven, and how are conflicts
>  resolved in the architecture?
> 
>  Feel free to comment on the GitHub issue directly, or here. I'll be
>  watching both.
> 
> >>>
> >>> I will cite what I have written on Stack Overflow
> >>> (http://stackoverflow.com/a/7107934/696632) five years ago and it still
> >>> holds true:
> >>>
> >>> You *never* provide a log implementation. The client application has to
> >>> do so. Otherwhise this would be a violation of separation of concerns.
> >>> Don't do any assumptions about an unknown client.
> >>>
> >>>
> >>> I agree with that sentiment...generally. But this is a maven plugin, so
> >> I'm
> >> trying to figure out what Maven is going to provide it when it executes.
> >> If
> >> it's not going to provide an implementation, then the plugin has to. If
> >> you
> >> have answers to the specific questions I asked above, I think it might
> >> help.
> >>
> >
> > It should not matter to you what Maven provides. It will always provide
> > some backend. Otherwise Maven won't be able to log itself.  Even if Maven
> > would not provide anything. It is not your task to force some
> > implementation. It is a several failure of the client to do so.
> >
> > Michael
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
  

RE: Profile Activation

[Martin Gainty]

MG>quick comment
> To: dev@maven.apache.org
> From: khmarba...@gmx.de
> Subject: Profile Activation
> Date: Fri, 12 Aug 2016 17:45:21 +0200
> 
> Hi to all,
> 
> I have the following profile:
> 
> 
>
>profile-not-value-true
>
>  
>profilea
>!true
>  
>
>
>  
>
>  com.soebes.maven.plugins
>  echo-maven-plugin
>  
>
>  initialize
>  
>echo
>  
>
>  
>  
>
>  profile not value true
>
>  
>
>  
>
>  
> 
> So the question is: What would you expect you need to do to activate 
> this profile?
> 
> Currently this profile is activated cause if I don't define the property 
> "profilea" at all it seemed to that Maven is assuming this means "not 
> value 'true'" ?
> 
> I have assumed it should be activated if the property exists which means 
> giving it on command line like this:
> 
> mvn -DprofileaMG>assumes the property *must* exist as documented at

MG>http://maven.apache.org/guides/introduction/introduction-to-profiles.html
MG>if ok for system property to not exist or system property to *not* be 
defined then either:
MG>fix code to detect system property must exist to conform to doc
MG>ORMG>change doc to say : The following profile will be activated when the 
system property "debug" is defined with a value which is not "true" -OR- when 
system property "debug" does not exist or when system property "debug" was 
never defined
> 
MG>*Methinks you found a bug Karl*
> 
> WDYT ?
> 
> Kind regards
> Karl Heinz Marbaise
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
  

RE: Build failed in Jenkins: core-it-maven-3-win #1233

[Martin Gainty]

MG>quick question below


> Subject: Re: Build failed in Jenkins: core-it-maven-3-win #1233
> To: dev@maven.apache.org
> From: c...@schulte.it
> Date: Thu, 28 Jul 2016 17:30:34 +0200
> 
> Can someone take a look, please?
> 
> Error: JAVA_HOME is set to an invalid directory.
> JAVA_HOME = "f:\jenkins\tools\java\latest-1.7-64"
> Please set the JAVA_HOME variable in your environment to match the
> location of your Java installation.
> 
> 
> Am 07/28/16 um 17:27 schrieb Apache Jenkins Server:
> > See 
> > 
> > Changes:
> > 
> > [schulte] [MNG-5670] guard against ConcurrentModificationException 
> > [MNG-6053]
> > 
> > --
> > Started by an SCM change
> > [EnvInject] - Loading node environment variables.
> > Building remotely on windows-2012-1 (Windows) in workspace 
> > 
> >  > git rev-parse --is-inside-work-tree # timeout=10
> > Fetching changes from the remote Git repository
> >  > git config remote.origin.url 
> > https://git-wip-us.apache.org/repos/asf/maven.git # timeout=10
> > Fetching upstream changes from 
> > https://git-wip-us.apache.org/repos/asf/maven.git
> >  > git --version # timeout=10
> >  > git -c core.askpass=true fetch --tags --progress 
> > https://git-wip-us.apache.org/repos/asf/maven.git 
> > +refs/heads/*:refs/remotes/origin/*
> >  > git rev-parse "origin/master^{commit}" # timeout=10
> > Checking out Revision 53077505a7e9408565ec30a43ad243c41189a94e 
> > (origin/master)
> >  > git config core.sparsecheckout # timeout=10
> >  > git checkout -f 53077505a7e9408565ec30a43ad243c41189a94e
> >  > git rev-list 32ce34921cc3d71c4216781de4a574037fad532f # timeout=10
> >  > git rev-parse --is-inside-work-tree # timeout=10
> > Fetching changes from the remote Git repository
> >  > git config remote.origin.url 
> > https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git # 
> > timeout=10
> > Pruning obsolete local branches
> > Fetching upstream changes from 
> > https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
> >  > git --version # timeout=10
> >  > git -c core.askpass=true fetch --tags --progress 
> > https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git 
> > +refs/heads/*:refs/remotes/origin/* --prune
> >  > git rev-parse "origin/master^{commit}" # timeout=10
> > Checking out Revision 31780e49d00ad5be0dd80ee5b37483f624bbf394 
> > (origin/master)
> >  > git config core.sparsecheckout # timeout=10
> >  > git checkout -f 31780e49d00ad5be0dd80ee5b37483f624bbf394
> >  > git rev-list 31780e49d00ad5be0dd80ee5b37483f624bbf394 # timeout=10
> >  > git branch -a # timeout=10
> >  > git rev-parse "remotes/origin/MNG-2477^{commit}" # timeout=10
> >  > git rev-parse "remotes/origin/MNG-3205^{commit}" # timeout=10
> >  > git rev-parse "remotes/origin/embedder^{commit}" # timeout=10
> >  > git rev-parse "remotes/origin/master^{commit}" # timeout=10
> > [m3-its] $ cmd /c call C:\Windows\TEMP\hudson3181989308987956124.bat
> > 
> > rmdir> /S /Q 
> >  
> > The system cannot find the file specified.
> > 
> > rmdir> /S /Q 
> > 
> >  
> > The system cannot find the file specified.
> > 
> > exit> 0 
> > [m3-its] $ cmd.exe /C 
> > '"f:\jenkins\jenkins-slave\tools\hudson.tasks.Maven_MavenInstallation\maven-3.3.1\bin\mvn.cmd
> >  -f maven-3-trunk/pom.xml -DskipTests=true 
> > -Dmaven.home.exists.continue=true 
> > -DdistributionTargetFolder=
> >  
> > -Dmaven.repo.local=
> >  clean package -B -U -V && exit %%ERRORLEVEL%%"'

MG>can you insert -e -X on mvn.cmd so we can see which plugin is being executed 
and which env variables are available e.g.cmd.exe /C 
'"f:\jenkins\jenkins-slave\tools\hudson.tasks.Maven_MavenInstallation\maven-3.3.1\bin\mvn.cmd
 -e -X -f maven-3-trunk/pom.xml -DskipTests=true 
-Dmaven.home.exists.continue=true 
-DdistributionTargetFolder=
 
-Dmaven.repo.local=
 clean package -B -U -V && exit %%ERRORLEVEL%%"'MG>re-rerun with -e -X params 
and post results here> > Error: JAVA_HOME is set to an invalid directory. 
> > JAVA_HOME = "f:\jenkins\tools\java\latest-1.7-64" 
> > Please set the JAVA_HOME variable in your environment to match the 
> > location of your Java installation. 
> > 
> > Build step 'Invoke top-level Maven targets' marked build as failure
> > Recording test results
> > ERROR: Step ‘Publish JUnit 

RE: Anyone care to advise?

[Martin Gainty]

MG>quick inline comment prefixed with MG
> Date: Sat, 5 Mar 2016 09:30:36 +0100
> Subject: Re: Anyone care to advise?
> From: mfriedenha...@gmail.com
> To: dev@maven.apache.org
> 
> Hello Stephen,
> 
> sounds a bit like Jenkins' Maven2 job type ;-)
> 
> Regards
> Mirko
> -- 
> Sent from my mobile
> Am 03.03.2016 13:12 schrieb "Stephen Connolly" <
> stephen.alan.conno...@gmail.com>:
> 
> > I had an evil idea...
> >
> > https://github.com/stephenc/reactor-snapshot-maven-plugin
> >
> > So the idea is to let you do things and resume quicker while doing things
> > that need the reactor artifacts when you don't want to invoke the full
> > lifecycle
> >
> > e.g.
> >
> > mvn package
> > com.github.stephenc.maven:reactor-snapshot-maven-plugin:1.0-SNAPSHOT:take
> >
> > mvn
> >
> > com.github.stephenc.maven:reactor-snapshot-maven-plugin:1.0-SNAPSHOT:restore
> > javadoc:jar
> > com.github.stephenc.maven:reactor-snapshot-maven-plugin:1.0-SNAPSHOT:take
> >
> > mvn
> >
> > com.github.stephenc.maven:reactor-snapshot-maven-plugin:1.0-SNAPSHOT:restore
> > source:jar
> > com.github.stephenc.maven:reactor-snapshot-maven-plugin:1.0-SNAPSHOT:take
> >
> > mvn
> >
> > com.github.stephenc.maven:reactor-snapshot-maven-plugin:1.0-SNAPSHOT:restore
> > install:install deploy:deploy
> >
> > mvn
> >
> > com.github.stephenc.maven:reactor-snapshot-maven-plugin:1.0-SNAPSHOT:restore
> > site
> >
> > Now this might ultimately need an extension helper so that things like -rf
> > will work better... but I wanted to try it out first.
MG>thinking custom-lifecycle might work but i dont know your full scope design
MG>if you could provide an example where custom-lifecycle wont work but this 
will
MG>with a working example i am all for it
> >
> >
> > The issue I have is persisting and looking up the artifact handlers... the
> > current way is hacky in the extreme and relies on the sisu injection
> > picking the same order (which may not always be valid due to the lifecycle
> > goals you might specify)
MG>playing the "which classloader is current phase implementing" has bitten me 
a few times
> >
> >
> > So, anyone care to tell me the "right" way to hack this!
> >
> >
> > -Stephen
> >
  

RE: Julia Antonova is out of office.

[Martin Gainty]

a happy St Vladimir Day to Julia..enjoy your national Holiday
I did not realize Vladimir is Putin's Patron 
saint?http://www.pravdareport.com/history/25-07-2013/125264-vladimir_putin_saint_prince-0/
?
Martin--
__ 

  


> Date: Mon, 22 Feb 2016 21:14:36 +0100
> Subject: Re: Julia Antonova is out of office.
> From: aherit...@gmail.com
> To: dev@maven.apache.org
> 
> I cannot bilieve it. Happy holidays Julia !
> 
> Le lundi 22 février 2016, Stephen Connolly 
> a écrit :
> 
> > w00t... I missed finding out about her holidays and had assumed she had
> > unsubscribed... I am happy again
> >
> > On 22 February 2016 at 18:59, Jesse McConnell  > >
> > wrote:
> >
> > > So where did the wiki page for this end up getting migrated after
> > codehaus
> > > shutdown?
> > >
> > > --
> > > jesse mcconnell
> > > jesse.mcconn...@gmail.com 
> > >
> > > On Mon, Feb 22, 2016 at 12:57 PM, Julia Antonova  > >
> > > wrote:
> > >
> > > > I will be out of the office starting  20.02.2016 and will not return
> > > until
> > > > 24.02.2016.
> > > >
> > > > I have no access to my mailbox, I will answer your message upon return.
> > > > Thank you!
> > > >
> > >
> >
> 
> 
> -- 
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
  

RE: How the Lucene PMC manages releases

[Martin Gainty]

in lucene/testframework:renamed CheapBastard codec to Lucene54 to see if the 
SPILoader would pick it up ..it didnteven when i replaced CheapBastard entry in 
resources/META-INF/services/org.apache.lucene.codecs.Codeca quick refactor 
NamedSPILoader.lookup(String name)  to read 
resources/META-INF/services/org.apache.lucene.codecs.Codec (and replace 
CheapBastard to Lucene54 in TestRuleSetupAndRestoreClassEnv)and now Lucene54 
codec is picked up by NamedSPILoader lookup method

Maven Specific:
refactored the 10 year old ivy script reactor workflow which is difficult to 
follow.. so I created pom.xml from original ivy build.xml
attaching test-framework pom.xml for review
(mentioned this to McCandless BTW..but havent heard back)
Merci!
Martin 
__ 



> Date: Sun, 15 Nov 2015 21:10:58 +
> Subject: Re: How the Lucene PMC manages releases
> From: stephen.alan.conno...@gmail.com
> To: dev@maven.apache.org
> 
> To my thinking this is a case of special circumstances. I wrote a test case
> but didn't understand how to integrate the test case correctly into the
> suite and as such a regression crept in when fixing some regressions in
> other (non-covered) areas of the version inheritance code. I attribute at
> least 3 of the version numbers to the various regressions in this area of
> the code base. Thankfully we now have better tests in this area and they
> are now integrated.
> 
> Let's see how many numbers we end up burning next time around before we
> rush to change how we do things.
> 
> On 15 November 2015 at 20:48, Paul Benedict  wrote:
> 
> > Whether you're incrementing the last number by one or labeling it RC, you
> > end up with a new release regardless. I don't have an issue with burning
> > numbers at all; it's out there for people to consume immediately no matter
> > what you call it. IMO, if anyone is concerned with the quality, either vote
> > it down or the RM should ask for Alpha/Beta/GA qualities in the voting
> > thread.
> >
> >
> >
> >
> > Cheers,
> > Paul
> >
> > On Sun, Nov 15, 2015 at 2:13 PM, Benson Margulies 
> > wrote:
> >
> > > On Sun, Nov 15, 2015 at 2:35 PM, Paul Benedict 
> > > wrote:
> > > > That's how it use to work, but that requires a double voting process:
> > > vote
> > > > once on the RC and then again if the RC is ready for production. It's
> > > > easier to just burn the numbers; if it fails, move to the next;
> > otherwise
> > > > you release what you have.
> > >
> > > There's an advantage that I think you might be missing. When you vote
> > > an RC, it becomes a formal release, and you can advertise it to the
> > > user community for testing, which might get you more testers than you
> > > get on the dev@ list.
> > >
> > >
> > > >
> > > >
> > > > Cheers,
> > > > Paul
> > > >
> > > > On Sun, Nov 15, 2015 at 11:48 AM, Anders Hammar 
> > > wrote:
> > > >
> > > >> That's how Maven core releases were done in the early v3.0.x days.
> > > >> Personally I think it worked very good.
> > > >>
> > > >> /Anders (mobile)
> > > >> On Nov 15, 2015 15:40, "Benson Margulies" 
> > > wrote:
> > > >>
> > > >> > Given the number of 'burned' releases recently, I thought people
> > might
> > > >> > be interested in hearing about an alternative approach.
> > > >> >
> > > >> > When a Lucene dev has a sudden urge to make a release, he or she set
> > > >> > up a release with a version of x.y.z-RC1. This is a real release. It
> > > >> > goes up for a vote.
> > > >> >
> > > >> > If there's something grossly wrong with it, the RM burns it and
> > tries
> > > >> > again with RC2, etc.
> > > >> >
> > > >> > If it passes the vote, the user community (not just the dev
> > community)
> > > >> > is invited/exhorted to test it for a bit. Problems are repaired. If
> > > >> > the fixes are significant, then the the next step is another RC.
> > When
> > > >> > an RC is clean, or manifests only tiny problems, the RM goes ahead
> > and
> > > >> > puts up x.y.z for a vote.
> > > >> >
> > > >> > The result of this is that a non-RC release hardly every gets
> > burned.
> > > >> >
> > > >> >
> > -
> > > >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > >> > For additional commands, e-mail: dev-h...@maven.apache.org
> > > >> >
> > > >> >
> > > >>
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > >
> >
  

pom.xml
Description: XML document

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

RE: Maven Plugin ITs with M2 disabled

[Martin Gainty]

> Date: Sat, 26 Sep 2015 10:53:44 +0200
> To: dev@maven.apache.org
> Subject: Maven Plugin ITs with M2 disabled
> From: rfscho...@apache.org
> 
> Hi,
> 
> FYI, I've disabled these jobs [1][2] on our buildserver. They gave some  
> odd M2-specific errors I don't want to spent time on. Time to move forward.
> 
> thanks,
> Robert
> 
> [1] https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m2/
> [2]  
> https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m2-with-maven-plugin/

MG>verified maven-eclipse-plugin 2.10 trunk is unaffected 
MG>repository location:
MG>https://maven.apache.org/plugins/maven-eclipse-plugin/source-repository.html
MG>clean build
MG>clean package
MG>mvn org.apache.maven.plugins:maven-eclipse-plugin:2.10:eclipse creates 
.project .classpath and .settings 

MG>resolve-workspace-dependencies goal has no output

[DEBUG] Configuring mojo org.apache.maven.plugins:maven-eclipse-plugin:2.10:reso
lve-workspace-dependencies from plugin realm ClassRealm[plugin>org.apache.maven.
plugins:maven-eclipse-plugin:2.10, parent: sun.misc.Launcher$AppClassLoader@4e25
154f]
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-eclipse-plugin:2.10:res
olve-workspace-dependencies' with basic configurator -->
[DEBUG]   (f) localRepository =   id: local
  url: file:///C:/Users/mgainty/.m2/repository/
   layout: default
snapshots: [enabled => true, update => always]
 releases: [enabled => true, update => always]
[DEBUG]   (f) remoteArtifactRepositories = [  id: central
  url: https://repo.maven.apache.org/maven2
   layout: default
snapshots: [enabled => false, update => daily]
 releases: [enabled => true, update => daily]
]
[DEBUG] -- end configuration --
[DEBUG] Detected workspace at C:\Maven-plugin\maven-eclipse-plugin\2.10\target\t
mp-workspace0\eclipse\dynamicWorkspace\workspace\.
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
MG>but no output even when project-A and project-Z live in workspace folder
MG>possible bug here?

MG>would reverting maven-eclipse-plugin pom.xml to 2.10 solve 
cyclic reference: Edge between 
'Vertex{label='org.apache.maven.plugins:maven-invoker-plugin'}' and 
'Vertex{label='org.apache.maven.plugins:maven-site-plugin'}' introduces to 
cycle in the graph org.apache.maven.plugins:maven-site-plugin --> 
org.apache.maven.plugins:maven-invoker-plugin --> 
org.apache.maven.plugins:maven-site-plugin
MG>?

> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
  

RE: Account on issues.apache.org/jira

[Martin Gainty]

Norbert

what is a *non-standard problem*

?
Martin 


 From: norbertw...@gmail.com
 Date: Wed, 26 Aug 2015 19:02:39 +0200
 Subject: Account on issues.apache.org/jira
 To: dev@maven.apache.org
 
 Hi,
 What is the email address to report (non standard) problems with the JIRA
 account?
 
 Regards,
 NW
  

RE: Using ${revision} as a version

[Martin Gainty]

 Date: Sun, 23 Aug 2015 17:16:07 +0200
 From: khmarba...@gmx.de
 To: dev@maven.apache.org
 Subject: Using ${revision} as a version
 
 Hi,
 
 I have test project where i defined the pom like this:
 
 ...
modelVersion4.0.0/modelVersion
 
groupIdcom.soebes.examples.j2ee/groupId
artifactIdparent/artifactId
version${revision}/version
packagingpom/packaging
 
 If i define the revision on command line like this.
 
 mvn -Drevision=1.0-SNAPSHOT clean package
 
 everything fine...
MGso launcher ingests revision property from System.getProperties()
MG  package org.codehaus.plexus.classworlds.launcher;
   public class Configurator  implements ConfigurationHandler
 {
public void configure( InputStream is )
throws IOException, ConfigurationException, DuplicateRealmException, 
NoSuchRealmException
{
if ( world == null )
{
world = new ClassWorld();
}
curRealm = null;
foreignClassLoader = null;
if ( this.launcher != null )
{
foreignClassLoader = this.launcher.getSystemClassLoader();
}
ConfigurationParser parser = new ConfigurationParser( this, 
System.getProperties() );
MGCLI seems to be obtaining properties properly..so far so good... but look 
below:

 But now i want to make the usage a bit more convenient so i added the 
 following to my pom:
 
 
properties
  project.build.sourceEncodingUTF-8/project.build.sourceEncoding
  revision1.0-SNAPSHOT/revision
/properties
 
 to have a default for revision which works fine now...
 
 But if i would like to overwrite the property from command line like this:
 
 mvn -Drevision=1.0 clean package
 
 the build failes in the following location:
 
 [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (assemblies) 
 on project assembly: Failed to create assembly: Unable to resolve 
 dependencies for assembly 'archive': Failed to resolve dependencies for 
 assembly: Unable to get dependency information for 
 com.soebes.examples.j2ee:service-client:jar:1.0-SNAPSHOT: Failed to 
 process POM for 
 com.soebes.examples.j2ee:service-client:jar:1.0-SNAPSHOT: Non-resolvable 
 parent POM for 
 com.soebes.examples.j2ee:service-client:[unknown-version]: Failure to 
 find com.soebes.examples.j2ee:parent:pom:${revision} in 
 http://localhost:8081/nexus/content/groups/public was cached in the 
 local repository, resolution will not be reattempted until the update 
 interval of nexus has elapsed or updates are forced
 [ERROR] com.soebes.examples.j2ee:service-client:jar:1.0-SNAPSHOT
 
 The project is available on github 
 (https://github.com/khmarbaise/javaee/tree/mvn321)
 
 So the question which is coming up...is this based on Maven core or is 
 this based on maven-assembly-plugin ?

MGbut in Maven-core:
MGorg.apache.maven.plugin
MGpublic class PluginParameterExpressionEvaluatorimplements 
TypeAwareExpressionEvaluator
MG@Override
MGpublic Object evaluate( String expr, Class? type ) throws 
ExpressionEvaluationException
MG
MGif ( value == null )
{
// The CLI should win for defining properties
if ( properties != null )
{
// We will attempt to get nab a system property as a way to 
specify a
// parameter to a plugins. My particular case here is allowing 
the surefire
// plugin to run a single test so I want to specify that class 
on the cli
// as a parameter.
value = properties.getProperty( expression );
}
if ( ( value == null )  ( ( project != null )  ( 
project.getProperties() != null ) ) )
{
value = project.getProperties().getProperty( expression );
}
}
MGso it appears CLI is supposed to win over any properties defined within 
project pom.xml
MGbut CLI implementation becomes inconsistent when project properties has 
version already defined in project pom.xml
MGbehaviour resulting from object graph produced by the reactor from CLI 
properties appears to be undefined and ultimately causes Exception
MGI think you found a Bug Karl
 
 Kind regards
 Karl Heinz Marbaise
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 

  

RE: maven-remote-resources-plugin downloads from disabled repositories

[Martin Gainty]

Barrie

https://maven.apache.org/guides/development/guide-testing-development-plugins.html

suggests setting up profile in settings.xml to enable or disable snapshots then 
invoke mvn profile
mvn -pProfileWithoutSnapshot

did you try configuring profile in settings.xml?
Martin 
__ 

   


 Date: Fri, 21 Aug 2015 11:09:24 +0930
 Subject: maven-remote-resources-plugin downloads from disabled repositories
 From: baerr...@gmail.com
 To: dev@maven.apache.org
 
 I'm tinkering with maven-scm and when I build it locally via
  ../maven-scm/maven-scm-plugin mvn -X clean install -Drat.skip
 
 Maven attempts to download the snapshot metadata for it's the already
 installed snapshot files. (This is probably because I'm running inside a
 module and not at the top level)
 
 I've attempted to disable apache.snapshots in settings.xml as I dont want
 any snapshot I haven't built myself.
 
 The configuration debugs indicate that the repositories are are disabled -
 but Maven still attempts to get the metadata. It looks like
 maven-remote-resources-plugin is the culprit.
 
 Does anyone else see this?
 
 I've only recently re-setup my Mac to cut code, so its possible I've not
 got something configured correctly.
 
  mvn -v
 Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
 2014-12-15T03:59:23+10:30)
 Maven home: /usr/local/Cellar/maven/3.2.5/libexec
 Java version: 1.6.0_65, vendor: Apple Inc.
 Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
 Default locale: en_US, platform encoding: MacRoman
 OS name: mac os x, version: 10.9.5, arch: x86_64, family: mac
 
 The debug output:
 
 [DEBUG] Configuring mojo
 'org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process' with
 basic configurator --
 [DEBUG]   (f) appendedResourcesDirectory =
 /Users/barrie/ide/maven/maven-scm/maven-scm-plugin/src/main/appended-resources
 [DEBUG]   (f) attachToMain = true
 [DEBUG]   (f) attachToTest = true
 [DEBUG]   (f) attached = true
 [DEBUG]   (f) basedir = /Users/barrie/ide/maven/maven-scm/maven-scm-plugin
 [DEBUG]   (f) encoding = UTF-8
 [DEBUG]   (f) excludeTransitive = false
 [DEBUG]   (f) includeProjectProperties = false
 [DEBUG]   (f) includeScope = runtime
 [DEBUG]   (f) localRepository =   id: local
   url: file:///Users/barrie/.m2/repository/
layout: default
 snapshots: [enabled = true, update = always]
  releases: [enabled = true, update = always]
 
 [DEBUG]   (f) outputDirectory =
 /Users/barrie/ide/maven/maven-scm/maven-scm-plugin/target/maven-shared-archive-resources
 [DEBUG]   (f) remoteArtifactRepositories = [  id: central
   url: https://repo.maven.apache.org/maven2
layout: default
 snapshots: [enabled = false, update = never]
  releases: [enabled = true, update = daily]
 ,   id: apache.snapshots
   url: https://repository.apache.org/content/groups/snapshots-group
layout: default
 snapshots: [enabled = false, update = never]
  releases: [enabled = false, update = never]
 ]
 [DEBUG]   (f) resourceBundles = [org.apache:apache-jar-resource-bundle:1.4]
 [DEBUG]   (f) resources = [Resource {targetPath: null, filtering: false,
 FileSet {directory:
 /Users/barrie/ide/maven/maven-scm/maven-scm-plugin/src/main/resources,
 PatternSet [includes: {}, excludes: {}]}}]
 [DEBUG]   (f) runOnlyAtExecutionRoot = false
 [DEBUG]   (f) skip = false
 [DEBUG]   (f) useDefaultFilterDelimiters = true
 [DEBUG]   (f) mavenSession = org.apache.maven.execution.MavenSession@569c6f2
 [DEBUG]   (f) project = MavenProject:
 org.apache.maven.plugins:maven-scm-plugin:1.9.5-SNAPSHOT @
 /Users/barrie/ide/maven/maven-scm/maven-scm-plugin/pom.xml
 [DEBUG] -- end configuration --
 
 ...
 
 [DEBUG]
 org.apache.maven.scm:maven-scm-provider-svntest:jar:1.9.5-SNAPSHOT:test
 (selected for test)
 [DEBUG] org.apache.maven.scm:maven-scm-test:jar:1.9.5-SNAPSHOT:test
 (selected for test)
 [DEBUG] Building project for
 org.apache.maven.scm:maven-scm-manager-plexus:jar:1.9.5-SNAPSHOT:compile
 [DEBUG] Using transporter WagonTransporter with priority -1.0 for
 https://repository.apache.org/content/groups/snapshots-group/
 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for
 https://repository.apache.org/content/groups/snapshots-group/
 Downloading:
 https://repository.apache.org/content/groups/snapshots-group/org/apache/maven/scm/maven-scm-managers/1.9.5-SNAPSHOT/maven-metadata.xml
 [DEBUG] Writing tracking file
 /Users/barrie/.m2/repository/org/apache/maven/scm/maven-scm-managers/1.9.5-SNAPSHOT/resolver-status.properties
 [WARNING] Could not transfer metadata
 org.apache.maven.scm:maven-scm-managers:1.9.5-SNAPSHOT/maven-metadata.xml
 from/to apache.snapshots (
 https://repository.apache.org/content/groups/snapshots-group/):
 java.lang.RuntimeException: Could not generate DH keypair
 org.eclipse.aether.transfer.MetadataTransferException: 

RE: [VOTE] Add Manfred Moser as committer

[Martin Gainty]

+1

Martin


 Date: Wed, 13 May 2015 09:16:19 +0100
 Subject: Re: [VOTE] Add Manfred Moser as committer
 From: stephen.alan.conno...@gmail.com
 To: dev@maven.apache.org
 
 +1
 
 On 13 May 2015 at 08:36, Kristian Rosenvold kristian.rosenv...@zenior.no
 wrote:
 
  +1
  13. mai 2015 8.55 a.m. skrev Hervé BOUTEMY herve.bout...@free.fr:
 
   Hi,
  
   I'd like to introduce Manfred Moser as committer for the Apache  Maven
   project.
  
   He's working on Android Maven plugin for years, has great discussions
  both
   on
   users and dev MLs, has a great attitude.
   And he's just told he wants to improve the site and work on Maven: having
   him
   make pull requests is just a waste of energy for both Manfred and whoever
   will
   accept the PRs: I'm confident that he'll know when to do changes by
   himself and
   when some discussion is necessary before doing the job.
  
   Vote open for 72H
  
   [+1]
   [0]
   [-1]
  
   And here's my +1.
  
   Hervé
  
   -
   To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
   For additional commands, e-mail: dev-h...@maven.apache.org
  
  
 
  

RE: Codehaus EOL and MAVENUSER Confluence Wiki

[Martin Gainty]

 From: herve.bout...@free.fr
 To: dev@maven.apache.org
 Subject: Codehaus EOL and MAVENUSER Confluence Wiki
 Date: Wed, 4 Mar 2015 02:20:09 +0100
 
 Hi,
 
 I got a report from someone about links from Jira to old Codehaus MAVEN 
 Confluence Wiki [1]: I explained that we already copied the content to ASF 
 MAVENOLD [2] as read-only and copied useful content to ASF MAVEN [3]
 
 Then ok for Codehaus MAVEN Confluence Wiki.
 
 But what about Codehaus MAVENUSER Confluence Wiki [4]?
 Is the whole content useful? Should we have the same strategy than MAVEN? Who 
 could do that?

MGhttp://docs.codehaus.org/display/MAVENUSER/Home;jsessionid=A686FD6E6C1DA1A824E695ABEB288143
MGCodehaus content is useful..but will require resource who can understand and 
write legible cyrilic..
MGCan Igor port the pages with cyrilic to ASF MAVEN[3]?
 
 Or should we only copy relevant pages to MAVEN? How to do that (I didn't find 
 any way to export even a simple page to later reimport)
 
 Any thoughts?
 
 Regards,
 
 Hervé
 
 
 [1] http://docs.codehaus.org/display/MAVEN/
 
 [2] https://cwiki.apache.org/confluence/display/MAVENOLD/
 
 [3] https://cwiki.apache.org/confluence/display/MAVEN/
 
 [4] http://docs.codehaus.org/display/MAVENUSER/
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Slave windows2 machine crashed

[Martin Gainty]

500+ testcases in Lucene 4.10.2 cause OOM and PermGen errors ..this 
configuration cured OOM and PermGen errors

  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.18.1/version
configuration
   argLine-Xms2048M -Xmx3192M -XX:PermSize=3192M 
-XX:MaxPermSize=6144m/argLine
  parallelmethods/parallel
  useUnlimitedThreadstrue/useUnlimitedThreads
  forkCount${surefire.forkNumber}/forkCount
  reuseForksfalse/reuseForks
/configuration
/plugin

http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html

YMMV,
Martin 
___


 Date: Sat, 7 Feb 2015 12:11:46 -0700
 From: tibordig...@apache.org
 To: dev@maven.apache.org
 Subject: Re: Slave windows2 machine crashed
 
 Failed again with OOM. I guess the machine self restarted before this run
 https://builds.apache.org/job/maven-surefire-windows/773/org.apache.maven.surefire$surefire-integration-tests/testReport/org.apache.maven.surefire.its/XmlReporterRunTimeIT/testForkModeAlways/
 
 
 
 --
 View this message in context: 
 http://maven.40175.n5.nabble.com/Slave-windows2-machine-crashed-tp5826082p5826085.html
 Sent from the Maven Developers mailing list archive at Nabble.com.
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: incremental compiler questions

[Martin Gainty]

 in time seems to be a key to understanding 
what collection requires re-compilation
MGcan Kristians work be refactored to be able to produce graph snapshots?
MGas far as implementation I would suggest CLI first, CI (Jenkins?) second and 
IDE third..refactoring an IDE plugin that works in Eclipse, Idea and Netbeans 
from my experience is a very time consuming exercise.
MGThanks for thinking this through Jason Mark and Igor
MGThoughts?

 
  
  LieGrue,
  strub
  
  
  
  
  
  On Saturday, 10 January 2015, 2:04, Martin Gainty mgai...@hotmail.com 
  wrote:
  G ood Evening Igor-
  
  Instead of implementing eclipe jdt for incremental java compilation is 
  there:
  
  1)any ability to refactor/reconfigure javac to read Last Modified Date of 
  source 
  file to enable incremental compilation?
  2)any concerns over generated class files..are they the same?
  any deltas ..if so ...what are they?
  3)can we implement a static settings.xml or other static configuration 
  file that 
  manfred suggested for eclipse jdt?
  4)any ability to switch compiler from javac to jdt as an attribute in 
  maven-compiler-plugin?
  
  Thanks for a great presentation on Maven Dev hangout
  Martin 
  __ 
  
  
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
  
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder,  Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 believe nothing, no matter where you read it,
 or who has said it,
 not even if i have said it,
 unless it agrees with your own reason
 and your own common sense.
 
  -- Buddha
 
 
 
 
 
 
 
 
 
  

incremental compiler questions

[Martin Gainty]

Good Evening Igor-

Instead of implementing eclipe jdt for incremental java compilation is there:

1)any ability to refactor/reconfigure javac to read Last Modified Date of 
source file to enable incremental compilation?
2)any concerns over generated class files..are they the same?
any deltas ..if so ...what are they?
3)can we implement a static settings.xml or other static configuration file 
that manfred suggested for eclipse jdt?
4)any ability to switch compiler from javac to jdt as an attribute in 
maven-compiler-plugin?

Thanks for a great presentation on Maven Dev hangout
Martin 
__ 


  

RE: prepare for the Anschluss

[Martin Gainty]

  Martin,
 
I think there is a misunderstanding here. 
ART as well as Dalvik both are runtimes on the devices. 
You error message comes from the build when dex is processing 
the Java jar files with Java bytecode to produce Android bytecode with dex. 
The issue is probably some specific old jar that uses pre Java 5  
if you find the specific dependency you will be able to check it out in more 
details. 
Maybe try by managing the asm dependency to a newer version than what is your 
resolved 
dependency or at least check out what that version is .. 

MGI have a ton of spring stuff that used asm byte-code generator from 10 years 
back..
MGI'll focus on getting asm up to date in my repo..
MGthis will at least get those classes in the right format for the dex step

MGIn the meanwhile how would android-plugin accommodate ART instead of dalvik?
 
manfred 
MGMany Thanks for the suggestion Manfred
MGMartin
 Subject: Re: prepare for the Anschluss
 From: manf...@mosabuam.com
 To: dev@maven.apache.org
 Date: Mon, 29 Dec 2014 20:49:45 +0100
 
 Martin,
 
 I think there is a misunderstanding here. ART as well as Dalvik both are 
 runtimes on the devices. You error message comes from the build when dex is 
 processing the Java jar files with Java bytecode to produce Android bytecode 
 with dex. The issue is probably some specific old jar that uses pre Java 5 
  if you find the specific dependency you will be able to check it out in 
 more details. Maybe try by managing the asm dependency to a newer version 
 than what is your resolved dependency or at least check out what that version 
 is .. 
 
 manfred 
 
 
 
 Martin Gainty wrote on 24.12.2014 05:13:
 
  the line from Sound of Music that seems applicable for this situtation
  
  when I run the dx Utility from maven-android-plugin as:
  java -Xmx5120M -jar $ANDROID_HOME/lib/dx.jar --dex
  --output=$ANDROID_HOME/target/classes.dex 
  ${user.home}/.m2/repository/org/apache/maven/maven-plugin-descriptor/2.0.5/maven-plugin-descriptor-2.0.5.jar
   
  ${user.home}/.m2/repository/com/android/tools/lint/lint-api/22.4.2/lint-api-22.4.2.jar
  ...space delimited list of 1000 assorted jars to be converted to DEX
  fubars with the following friendly message:
  UNEXPECTED TOP-LEVEL EXCEPTION:
  java.lang.IllegalArgumentException: already added:
  Lorg/objectweb/asm/tree/AbstractInsnNode;
 at 
  com.android.dx.dex.file.ClassDefsSection.add(ClassDefsSection.java:122)
 at com.android.dx.dex.file.DexFile.add(DexFile.java:161)
 at com.android.dx.command.dexer.Main.processClass(Main.java:685)
 at com.android.dx.command.dexer.Main.processFileBytes(Main.java:634)
 at com.android.dx.command.dexer.Main.access$600(Main.java:78)
 at com.android.dx.command.dexer.Main$1.processFileBytes(Main.java:572)
 at
 
  com.android.dx.cf.direct.ClassPathOpener.processArchive(ClassPathOpener.java:284)
 at
 
  com.android.dx.cf.direct.ClassPathOpener.processOne(ClassPathOpener.java:166)
 at
 
  com.android.dx.cf.direct.ClassPathOpener.process(ClassPathOpener.java:144)
 at com.android.dx.command.dexer.Main.processOne(Main.java:596)
 at com.android.dx.command.dexer.Main.processAllFiles(Main.java:498)
 at com.android.dx.command.dexer.Main.runMonoDex(Main.java:264)
 at com.android.dx.command.dexer.Main.run(Main.java:230)
 at com.android.dx.command.dexer.Main.main(Main.java:199)
 at com.android.dx.command.Main.main(Main.java:103)
  1149 errors; aborting
  warning: Ignoring InnerClasses attribute for an anonymous inner class
  (org.apache.commons.jxpath.JXPathBasicBeanInfo$1) that doesn't come with an
  associated EnclosingMethod attribute. This class was probably produced by a
  compiler that did not target the modern .class file format. The recommended
  solution is to recompile the class from source, using an up-to-date compiler
  and without specifying any -target type options. The consequence of 
  ignoring
  this warning is that reflective operations on this class will incorrectly
  indicate that it is *not* an inner class.
  
  Apparently Androids com.android.dx.cf.direct.ClassPathOpener is expecting a
  specific format of Class  for reflection magic so apparently I would need to
  recompile ALL of  the maven jars in my local repo to at least 1.7.0_45 
  before
  attempting ..i have 1000 at last count and this effort would be too time
  consuming so I am seeking advice on how to mitigate
  
  Google has decided to shy away from Androids Dalvik VM to create Googles 
  own VM
  for Android Lollipop called ART here are some conversion pointers..The long
  winded explanation for this paradigm shift involves lawsuits in US Courts
  
  Moving from DALVIK to ART
  
  Enabling ART in Android Build
  
  Device Runtime(s)
  Two runtimes are now available, the existing Dalvik runtime (libdvm.so) and 
  the
  ART runtime (libart.so).
  A device

prepare for the Anschluss

[Martin Gainty]

the line from Sound of Music that seems applicable for this situtation

when I run the dx Utility from maven-android-plugin as:
java -Xmx5120M -jar $ANDROID_HOME/lib/dx.jar --dex 
--output=$ANDROID_HOME/target/classes.dex  
${user.home}/.m2/repository/org/apache/maven/maven-plugin-descriptor/2.0.5/maven-plugin-descriptor-2.0.5.jar
  
${user.home}/.m2/repository/com/android/tools/lint/lint-api/22.4.2/lint-api-22.4.2.jar
 ...space delimited list of 1000 assorted jars to be converted to DEX
fubars with the following friendly message:
UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.IllegalArgumentException: already added: 
Lorg/objectweb/asm/tree/AbstractInsnNode;
at com.android.dx.dex.file.ClassDefsSection.add(ClassDefsSection.java:122)
at com.android.dx.dex.file.DexFile.add(DexFile.java:161)
at com.android.dx.command.dexer.Main.processClass(Main.java:685)
at com.android.dx.command.dexer.Main.processFileBytes(Main.java:634)
at com.android.dx.command.dexer.Main.access$600(Main.java:78)
at com.android.dx.command.dexer.Main$1.processFileBytes(Main.java:572)
at 
com.android.dx.cf.direct.ClassPathOpener.processArchive(ClassPathOpener.java:284)
at 
com.android.dx.cf.direct.ClassPathOpener.processOne(ClassPathOpener.java:166)
at 
com.android.dx.cf.direct.ClassPathOpener.process(ClassPathOpener.java:144)
at com.android.dx.command.dexer.Main.processOne(Main.java:596)
at com.android.dx.command.dexer.Main.processAllFiles(Main.java:498)
at com.android.dx.command.dexer.Main.runMonoDex(Main.java:264)
at com.android.dx.command.dexer.Main.run(Main.java:230)
at com.android.dx.command.dexer.Main.main(Main.java:199)
at com.android.dx.command.Main.main(Main.java:103)
1149 errors; aborting
warning: Ignoring InnerClasses attribute for an anonymous inner class 
(org.apache.commons.jxpath.JXPathBasicBeanInfo$1) that doesn't come with an 
associated EnclosingMethod attribute. This class was probably produced by a 
compiler that did not target the modern .class file format. The recommended 
solution is to recompile the class from source, using an up-to-date compiler 
and without specifying any -target type options. The consequence of ignoring 
this warning is that reflective operations on this class will incorrectly 
indicate that it is *not* an inner class.

Apparently Androids com.android.dx.cf.direct.ClassPathOpener is expecting a 
specific format of Class  for reflection magic so apparently I would need to 
recompile ALL of  the maven jars in my local repo to at least 1.7.0_45 before 
attempting ..i have 1000 at last count and this effort would be too time 
consuming so I am seeking advice on how to mitigate

Google has decided to shy away from Androids Dalvik VM to create Googles own VM 
for Android Lollipop called ART here are some conversion pointers..The long 
winded explanation for this paradigm shift involves lawsuits in US Courts

Moving from DALVIK to ART

Enabling ART in Android Build

Device Runtime(s)
Two runtimes are now available, the existing Dalvik runtime (libdvm.so) and the 
ART runtime (libart.so).
A device can be built using either or both runtimes. (You can dual boot from 
Developer options if both runtimes are installed.) 
See runtime_common.mk. That is included from 
build/target/product/runtime_libdvm.mk or 
build/target/product/runtime_libdvm.mk or both.

To maintain backward compatibility, ART uses the same input bytecode as Dalvik, 
supplied through standard .dex files as part of APK files,

DEX to ART ELF Conversion:
Once an application is compiled by using ART's on-device dex2oat utility, it is 
run solely from the compiled ELF executable
the Dalvik .odex files are replaced with Executable and Linkable Format (ELF) 
executables output from dex2oat

These helpful hints should be sanitised and posted somewhere but I dont know 
where this should go?

Looks like we have some interesting work to look forward to 2015

Happy Channukah/Merry Christmas
Martin 
__ 


  

RE: Need Jira account

[Martin Gainty]

what is the failure you are experiencing?
which maven plugin are you submitting a patch for?
what is the maven version, OS and JDK your patch is targetting?

Martin 
__ 

   


 From: raghavendra.vai...@gmail.com
 Subject: Need Jira account
 Date: Thu, 25 Dec 2014 08:10:05 +0530
 To: dev@maven.apache.org
 
 Can some one tell me how do I get a Jira account for creating and submitting 
 patches ? the website says contact your Jira administrators …. I am not sure 
 who is the Jira administrator.
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: maven-eclipe-plugin build failing due to Could not generate DH keypair

[Martin Gainty]

at the bank the Sun Provider would occasionaly fubar our security installation
we mitigated by switching the provider to bouncycastle
Kristian...where is the testcase?
Martin-
Nota Bene: in  maven-elcipse-plugin someone *should* correct multymodule to 
multimodule 

 Date: Sun, 7 Dec 2014 13:07:05 +0100
 Subject: Re: maven-eclipe-plugin build failing due to Could not generate DH 
 keypair
 From: kristian.rosenv...@gmail.com
 To: dev@maven.apache.org
 
 I removed the testcase in r1643665. If anyone wants to work on the
 failing test feel free to revert my commit and fix it.
 
 The implications of having all the builds red for any length of time
 is usually more fallout.
 
 Kristian
 
 
 2014-12-07 8:30 GMT+01:00 Anders Hammar and...@hammar.net:
  I think we should retire it. There hasn't been a release for almost three
  years and there has just been very little code activity since then.
  Retiring it would give the community a clear (and honest) indication that
  we will not fix any issues in it.
 
  /Anders
 
  On Sun, Dec 7, 2014 at 1:05 AM, Barrie Treloar baerr...@gmail.com wrote:
 
  On 7 December 2014 at 10:24, Jörg Schaible joerg.schai...@gmx.de wrote:
 
   Benson Margulies wrote:
  
Well, the only users would be either people using old versions of
   Eclipse,
or very stubborn people trying to use it in the teeth of m2e.
  
   Or users that explicitly remove m2e from their Eclipse installation
  because
   even without it current Eclipse is quite unstable and extremely resource
   hungry.
  
 
  There was a call a while ago to retire it, but there were enough people
  stuck in the past and had no choice, or preferred its use that it stayed.
 
  Perhaps it's time for a new home instead?
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: How to setup SVN for HTML content of published site?

[Martin Gainty]

 Date: Mon, 24 Nov 2014 08:32:46 -0700
 From: tibo...@lycos.com
 To: dev@maven.apache.org
 Subject: How to setup SVN for HTML content of published site?
 
 I want to deploy the site to SVN repo. 
 How to configure the SVN server so that the path in particular repository
 would be provided like a web content?

MGI do not know of a SVN server which serves web-content per-se..perhaps the 
other devs can suggest?
MGnexus installs an instance of Eclipse-Jetty web-server which you can monitor 
at localhost:8081
MGhttps://github.com/sonatype/nexus-book/blob/master/chapter-installation.asciidoc

 We are using CollabNet SubversionEdge.
 
 
 
 -
 BR, tibor17
 --
 View this message in context: 
 http://maven.40175.n5.nabble.com/How-to-setup-SVN-for-HTML-content-of-published-site-tp5815564.html
 Sent from the Maven Developers mailing list archive at Nabble.com.
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Raven, take 2

[Martin Gainty]

 Date: Sat, 22 Nov 2014 08:42:24 -0500
 Subject: Re: Raven, take 2
 From: bimargul...@gmail.com
 To: dev@maven.apache.org
 
 On Sat, Nov 22, 2014 at 8:34 AM, Stephen Connolly 
 stephen.alan.conno...@gmail.com wrote:
 
  I will point out that there is a consulting company with Maven in their
  name using a raven already.
MGyep
MGhttp://www.mavenraven.org/
MGPersonally I like the owl.. the hole in the owls' stomach begs explanation
 
 
 I don't know if that's an insurmountable trademark problem or not.
 
 Of course, we don't have to have a mascot at all. Some sort of graphic
 design embodiment of a chain of plugins, for example ...
 
 
 
 
  On Saturday, November 22, 2014, Benson Margulies bimargul...@gmail.com
  wrote:
 
   http://beautyofbirds.com/images/birds/ravens/AustralianRaven.jpg
  
   I'm not very clever with gimp, but let's see what can be done.
  
 
 
  --
  Sent from my phone
 
  

RE: Trying to port Neo4j on AIX

[Martin Gainty]

  

 Date: Fri, 29 Aug 2014 13:42:26 +1000
 Subject: Re: Trying to port Neo4j on AIX
 From: chrisgw...@gmail.com
 To: dev@maven.apache.org
 
 And the failing error is?
 Should this not be posted on the users list?
 
 -Chris
 
 
 On Thu, Aug 28, 2014 at 1:36 AM, Siah Lyimo sly...@us.ibm.com wrote:
 
 
 
 
  Hi,
  I'm  working on porting Neo4j on AIX and I was wondering if there is anyone
  who has previously made an attempt to port to AIX.
  I'm currently having the following ERRORS while running mvn clean install
 
  Tests in error:
DumpProcessInformationTest.shouldDumpProcessInformation:60 » IO Cannot
  run pro...
 
  Tests run: 2087, Failures: 10, Errors: 1, Skipped: 25
 
  [INFO]
  
  [INFO] Reactor Summary:
  [INFO]
  [INFO] Neo4j .. SUCCESS
  [  2.391 s]
  [INFO] Licensing configuration  SUCCESS
  [  1.814 s]
  [INFO] Neo4j - Primitive Collections .. SUCCESS
  [  9.302 s]
  [INFO] Neo4j - IO . SUCCESS
  [ 18.431 s]
  [INFO] Neo4j - Graph Database Kernel .. FAILURE [05:48
  min]
  [INFO] Neo4j - JMX support  SKIPPED
  [INFO] Neo4j - Usage Data Collection .. SKIPPED
  [INFO] Neo4j - Monitor Logging  SKIPPED
  [INFO] Neo4j - Graphviz generation  SKIPPED
  [INFO] Neo4j - Lucene Index ... SKIPPED
  [INFO] Neo4j - Graph Algorithms ... SKIPPED
  [INFO] Neo4j - Graph Matching . SKIPPED
  [INFO] Neo4j Community Cypher Build ... SKIPPED
  [INFO] Neo4j - Cypher Commons . SKIPPED
  [INFO] Neo4j - Cypher Compiler 2.2  SKIPPED
  [INFO] Neo4j - Cypher . SKIPPED
  [INFO] Neo4j - Consistency Checker  SKIPPED
  [INFO] Neo4j Community  SKIPPED
  [INFO] Neo4j GraphGist  SKIPPED
  [INFO] Neo4j - Cypher Documentation ... SKIPPED
  [INFO] Neo4j Cypher Reference Card Tests .. SKIPPED
  [INFO] Neo4j Community  SKIPPED
  [INFO] Neo4j - Generic shell .. SKIPPED
  [INFO] Neo4j Examples . SKIPPED
  [INFO] Neo4j Server API ... SKIPPED
  [INFO] Neo4j Browser .. SKIPPED
  [INFO] Neo4j Server ... SKIPPED
  [INFO] Neo4j - Server Plugin Tests  SKIPPED
  [INFO] Neo4j Server Examples .. SKIPPED
  [INFO] Neo4j - UDC Integration  SKIPPED
  [INFO] Neo4j Community Build .. SKIPPED
  [INFO] Neo4j - Graph DB Monitoring and Management tools ... SKIPPED
  [INFO] Neo4j Advanced . SKIPPED
  [INFO] Neo4j Advanced Server .. SKIPPED
  [INFO] Neo4j Advanced Build ... SKIPPED
  [INFO] Neo4j - Communication Package .. SKIPPED
  [INFO] Neo4j - Clustering Infrastructure .. SKIPPED
  [INFO] Neo4j - Backup Tool  SKIPPED
  [INFO] Neo4j - High Availability .. SKIPPED
  [INFO] Neo4j Enterprise ... SKIPPED
  [INFO] Neo4j Enterprise Server  SKIPPED
  [INFO] Neo4j - Enterprise Performance Tests ... SKIPPED
  [INFO] Neo4j Enterprise Build . SKIPPED
  [INFO] Neo4j Integration Tests  SKIPPED
  [INFO]
  
  [INFO] BUILD FAILURE
  [INFO]
  
  [INFO] Total time: 06:24 min
  [INFO] Finished at: 2014-08-27T10:03:41-05:00
  [INFO] Final Memory: 75M/253M
  [INFO]
  
  [ERROR] Failed to execute goal
  org.apache.maven.plugins:maven-surefire-plugin:2.15:test (default-test) on
  project neo4j-kernel: There are test failures.

MGcwd /target/surefire-reports
MGls --sort=size -l
MGgrab the biggest TEST-*.XML and post contents here

  [ERROR]
  [ERROR] Please refer
  to /home/neo4j/community/kernel/target/surefire-reports for the individual
  test results.
 
  Thank you in advance.
 
  Regards,
 
  Siah Lyimo.
  Software Engineering intern
  

RE: Welcome our new VP of Apache Maven, Hervé Boutemy

[Martin Gainty]

This is wonderful news

Félicitations Herve!
Martin Gainty 
__


 Date: Sun, 20 Jul 2014 11:42:19 +0200
 From: khmarba...@gmx.de
 To: dev@maven.apache.org
 Subject: Re: Welcome our new VP of Apache Maven, Hervé Boutemy
 
 Hi Hervé,
 
 congratulations to being VP .the  unlucky victim
 
 
 Kind regards
 Karl-Heinz Marbaise
 
 On 7/19/14 11:42 PM, Stephen Connolly wrote:
  The role of VP of maven is more a technical and legal responsibility in
  that the ASF board requires an officer of the foundation to delegate the
  powers vested in the PMC to.
 
  A few years back, John Casey suggested that we should try rotating this
  burden amongst the PMC on a yearly-ish basis.
 
  I have been PMC chair for the last year, and it has been fun times, but
  when I took the unlucky victim role I said it would be for one year only.
 
  True to my word, I asked the PMC to nominate a replacement. Hervé was
  selected and at the most recent board meeting I was released from these
  responsibilities with board approving Hervé as our new VP
 
  Everyone please congratulate Hervé on being our next unlucky victim!
 
  Please also remember that it is the community that determines the direction
  of this project. The PMC is there to ensure the project plays by the rules,
  the PMC chair is here to serve the project, board and PMC.
 
  I wish Hervé all the best for his stint... And I won't fear taking the
  baton up again next time ;-)
 
  - Stephen
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Hangout summary?

[Martin Gainty]

anytime before 11pm CEST would work best for me

Manfred PST is California.. who is from California?

*gruss*
Martin 
__


 Subject: Re: Hangout summary?
 From: manf...@mosabuam.com
 To: dev@maven.apache.org
 Date: Fri, 11 Jul 2014 00:45:36 +0200
 
 PST 
 
 Igor Fedorenko wrote on 08.07.2014 23:21:
 
  I will be in GMT+4 timezone until the end of the summer, then go back to
  my normal GMT-4.
  
  --
  Regards,
  Igor
  
  
  On 2014-07-04, 1:33, Robert Scholte wrote:
  Hi,
 
  Just to give Olivier a chance to join, let's collect the local times of
  the current joiners and try to find a timeslot when it's not midnight:
 
  If I'm correct, following have joined at least 2 times or are Maven PMC
  22:00-23:00 (CEST) Robert Scholte, Hervé Boutemy, Karl-Heinz Marbaise,
  Mark Struberg
  21:00-22:00 (IST) Stephen Connolly
 
  unknown, please complete
  Jason van Zyl
  Igor Fedorenko
  Manfred Moser
  Mark Derricutt
  Emily Blades
 
  thanks,
  Robert
 
 
  Op Fri, 27 Jun 2014 23:48:13 +0200 schreef Olivier Lamy ol...@apache.org:
 
  Hi
  Hangout time is a pain for me and I probably don't have time to
  participate.
  But I'm interested to read a summary ( mail or wiki page ) on what
  happend.
 
  Is there any?
 
  Cheers
  --
  Olivier
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
  
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
  
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Maven Developer Hangout

[Martin Gainty]

IfIAmNotLocalNexusAdminlocal-repositories are always the first repositories to 
be searched
IfIAmLocalNexusAdminthen promote to local nexus and search local nexus..local 
nexus repo will be the first searched repo
then central
then the plethora of maven mirrors

I like the idea of package affinity identified in repositories in pom.xml:
package org.fubar has affinity to fubar repository (presumably at 
http://www.fubar.org)
package org.apache.struts2 has affinity to main apache repository (presumably 
at repo http://www.eu.apache.org/dist)
package org.apache.maven has affinity to codehaus repository (presumably at 
repo http://dist.codehaus.org)

  repositoriesrepository  idcodehaus/id  nameCodehaus 
Release Repo/name  urlhttp://dist.codehaus.org//url
  package-affinityorg.apache.maven.*/package-affinity/repository?
Martin-



 Date: Mon, 7 Jul 2014 09:35:31 -0500
 Subject: Re: Maven Developer Hangout
 From: pbened...@apache.org
 To: dev@maven.apache.org
 
 I agree with anyone/everyone who says we should get rid of the idea of a
 local repository. It should just be looked at as a local remote repo with
 some default intermediary repository manager built-in to Maven. Jason, is
 that what you're referring to?
 
 
 Cheers,
 Paul
 
 
 On Mon, Jul 7, 2014 at 9:31 AM, Jason van Zyl ja...@takari.io wrote:
 
  Yup, this is essentially what routing rules are in Nexus. Would likely
  make sense to move this logic into Maven to speed up lookups.
 
  I also think trying to have each dependency mark where it comes from as
  cumbersome.
 
  On Jul 7, 2014, at 9:45 AM, Daniel Kulp dk...@apache.org wrote:
 
  
   Personally, I’ve always wondered if the repository entries should have
  an includes and excludes tags to say this repository should only be
  searched for these artifacts (like org.apache.*:*).  Should help speed the
  builds by not looking at every repository for every artifact when we know
  they are in central.
  
   Dan
  
  
  
   On Jul 4, 2014, at 12:56 PM, Robert Scholte rfscho...@apache.org
  wrote:
  
   In addition to our hangout session: isn't it weird that for a
  dependency Maven can go over all the repositories, even though when an
  extra repository is added to the pom.xml, the developer knows exactly which
  dependencies should make use of that repository.
  
   To me it would make sense if you could add a reference to the
  repository per dependency, like
  
   dependency
   groupIdcom.acme/groupId
   artifactIdspecialtool/artifactId
   version1.0-alpha-1/version
   repositoryIdacme-store/repositoryId !-- only look in this repo, I
  know it's not in Central --
   /dependency
  
   Robert
  
   Op Thu, 03 Jul 2014 00:37:17 +0200 schreef Mark Derricutt 
  m...@talios.com:
  
   On 3 Jul 2014, at 6:25, Robert Scholte wrote:
  
   This is probably more than enough for tomorrow.
  
   A discussion on a merits and flaws of repositories (when combined
  with mirrors) is also warranted after some previous discussion on the list.
  
   Mark
  
   -
   To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
   For additional commands, e-mail: dev-h...@maven.apache.org
  
   -
   To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
   For additional commands, e-mail: dev-h...@maven.apache.org
  
  
   --
   Daniel Kulp
   dk...@apache.org - http://dankulp.com/blog
   Talend Community Coder - http://coders.talend.com
  
  
   -
   To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
   For additional commands, e-mail: dev-h...@maven.apache.org
  
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder,  Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  The modern conservative is engaged in one of man's oldest exercises in
  moral philosophy; that is,
  the search for a superior moral justification for selfishness.
 
   -- John Kenneth Galbraith
 
 
 
 
 
 
 
 
 
 
  

RE: Maven Developer Hangout

[Martin Gainty]

Many is the time I wonder where did that dependency come from?
I see the addition of a repositoryId attribute as an essential feature for 
aufgeregt sein auditing goal by maven-audit-plugin

Good Idea Robert!
+1

Martin 
_


 To: dev@maven.apache.org
 Subject: Re: Maven Developer Hangout
 Date: Fri, 4 Jul 2014 18:56:58 +0200
 From: rfscho...@apache.org
 
 In addition to our hangout session: isn't it weird that for a dependency  
 Maven can go over all the repositories, even though when an extra  
 repository is added to the pom.xml, the developer knows exactly which  
 dependencies should make use of that repository.
 
 To me it would make sense if you could add a reference to the repository  
 per dependency, like
 
 dependency
groupIdcom.acme/groupId
artifactIdspecialtool/artifactId
version1.0-alpha-1/version
repositoryIdacme-store/repositoryId !-- only look in this repo, I  
 know it's not in Central --
 /dependency
 
 Robert
 
 Op Thu, 03 Jul 2014 00:37:17 +0200 schreef Mark Derricutt  
 m...@talios.com:
 
  On 3 Jul 2014, at 6:25, Robert Scholte wrote:
 
  This is probably more than enough for tomorrow.
 
  A discussion on a merits and flaws of repositories (when combined with  
  mirrors) is also warranted after some previous discussion on the list.
 
  Mark
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Maven Developer Hangout

[Martin Gainty]

 Date: Fri, 4 Jul 2014 18:31:35 -0500
 Subject: Re: Maven Developer Hangout
 From: pbened...@apache.org
 To: dev@maven.apache.org
 
 The use of repositories even with a symbolic id assumes there's only one
 canonical location for the artifact. I don't think that's true and would
 never want to be the end-user who has to manage those symbolic ids. I still
 advocate removing this tag. I think it's the job of the intermediary (like
 Nexus) to write some metadata on where it last found the artifact and then
 only searching others upon failure retrieving a different version / update.

MGPaul..Where would the discovered repository metadata be 
written?..distributionManagement?

MGTamas ...is this possible?
 
 
 Cheers,
 Paul
 
 
 On Fri, Jul 4, 2014 at 2:52 PM, Robert Scholte rfscho...@apache.org wrote:
 
  I fully agree on the SHA1 check and the repo manager protocol, but as long
  as we need the repositories/ in the pom.xml, the repositoryId can help to
  optimize the searchpath for the artifacts.
 
  That would make the pom responsible for mapping dependency to the original
  repositoryUrl and the repository manager for mapping the original
  repositoryUrl to the ultimate repositoryUrl.
 
  Or don't do it to encourage projects to push their artifacts to Maven
  Central.
 
  thanks,
  Robert
 
  Op Fri, 04 Jul 2014 19:08:16 +0200 schreef Jason van Zyl ja...@takari.io
  :
 
   If you consider the identity of the artifact to be its SHA1,
  theoretically it doesn't matter where it comes from. This is not to say
  that's optimal to go looking everywhere for an artifact. How this is
  constrained in Nexus is through routing rules where Nexus knows only to
  look for given groupIds in a particular repository and this great optimizes
  lookup times. One might argue this type of logic can be moved back into
  Maven itself.
 
  As we discussed in the hangout, and I agree with Igor, that mirrors were
  an error and likely something we should eliminate in Maven 4.0.0 and work
  on a repository manager protocol like we discussed.
 
  On Jul 4, 2014, at 12:56 PM, Robert Scholte rfscho...@apache.org wrote:
 
   In addition to our hangout session: isn't it weird that for a dependency
  Maven can go over all the repositories, even though when an extra
  repository is added to the pom.xml, the developer knows exactly which
  dependencies should make use of that repository.
 
  To me it would make sense if you could add a reference to the repository
  per dependency, like
 
  dependency
   groupIdcom.acme/groupId
   artifactIdspecialtool/artifactId
   version1.0-alpha-1/version
   repositoryIdacme-store/repositoryId !-- only look in this repo, I
  know it's not in Central --
  /dependency
 
  Robert
 
  Op Thu, 03 Jul 2014 00:37:17 +0200 schreef Mark Derricutt 
  m...@talios.com:
 
   On 3 Jul 2014, at 6:25, Robert Scholte wrote:
 
   This is probably more than enough for tomorrow.
 
 
  A discussion on a merits and flaws of repositories (when combined
  with mirrors) is also warranted after some previous discussion on the 
  list.
 
  Mark
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder,  Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  Our achievements speak for themselves. What we have to keep track
  of are our failures, discouragements and doubts. We tend to forget
  the past difficulties, the many false starts, and the painful
  groping. We see our past achievements as the end result of a
  clean forward thrust, and our present difficulties as
  signs of decline and decay.
 
   -- Eric Hoffer, Reflections on the Human Condition
 
 
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
  

RE: Maven Developer Hangout

[Martin Gainty]

 Date: Thu, 3 Jul 2014 09:45:22 +0100
 Subject: Re: Maven Developer Hangout
 From: stephen.alan.conno...@gmail.com
 To: dev@maven.apache.org
 
 On 2 July 2014 19:25, Robert Scholte rfscho...@apache.org wrote:
 
  Sure, I can fill some time with my proposal.[1]
  Another thing that comes to my mind is Stephens proposal on supplies
  concept[2]
 
 
 I don't think I can make today's hangout... There is a limit to the amount
 of after 5pm IT related activities permitted by my wife and I used up
 this weeks allocation yesterday!
MGunderstood stephen..hopefully we can catch up next week
MGHope you and your wife have a great weekend!
MGMartin
 
 
  And an interesting talk would be about the proposal Removing ability for
  plugins to dynamically inject dependencies[3]. For most cases I can think
  of a solution, however what to do with pom-less goals dependency:get?
 
  This is probably more than enough for tomorrow.
 
  Robert
 
  [1] http://markmail.org/message/cmia5vylzh2lzp3t
  [2] http://markmail.org/message/sx4slb2dwbvth7u6
  [3] http://markmail.org/message/7f55pruyc6pt2hlw
 
  Op Wed, 02 Jul 2014 16:34:46 +0200 schreef Jason van Zyl ja...@takari.io
  :
 
 
   The hangout is the same time as last week:
 
  https://plus.google.com/u/0/events/c5dc2fimb4mau0anec7i1nde500
 
  I figure we'll just always schedule it even if few or no one shows up.
  Just a standing meeting to discuss anything.
 
  Robert, maybe you would like to talk about your lifecycle proposal? We
  can also discuss anything else, the floor is open.
 
  With holidays in Canada this week I haven't finished writing up the POM
  Evolved proposal.
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder,  Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  First, the taking in of scattered particulars under one Idea,
  so that everyone understands what is being talked about ... Second,
  the separation of the Idea into parts, by dividing it at the joints,
  as nature directs, not breaking any limb in half as a bad carver might.
 
-- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
 
 
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
  

RE: [RFC] [MENFORCER-174]

[Martin Gainty]

If I understand what you are attempting here:
you wish to place additional restrictions on which artifacts are being exposed 
to distribution-management
via a maven-enforcer-plugin rule implementor ?

from a conceptual point of view Repo Managers (nexus specifically) can 
grant or deny access to repos, packages within those repos and artifacts within 
the packages
 From there the permissions matrix of that folder can be implemented by 
imposing .htaccess on the folder
in this way devs do not have access to any of the RELEASE repositories
Operators do not have insert/update capability to SNAPSHOTs 

 if this your intent here?

Martin 
__


 Date: Mon, 30 Jun 2014 08:08:10 +0200
 From: khmarba...@gmx.de
 To: dev@maven.apache.org
 Subject: [RFC] [MENFORCER-174]
 
 Hi,
 
 according to comments about the naming of the rule 
 (BanDistributionManagement my original name) and the suggestions made by 
 Robert Scholte which of course are true in particular about the 
 confusions about the intention of the rule.
 
 I would like to know if someone of the devs has a good/better idea...
 
 My idea is: FilterDistributionManagement
 
 The idea of the rule is to limit the usage of distributionManagement in 
 particular areas of pom may be only within a company pom etc.
 
 What about LimitDistributionManagementUsage
 
 Many thanks in advance...
 
 Kind regards
 Karl-Heinz Marbaise
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: maven-enforcer-plugin

[Martin Gainty]

Afternoon Karl!
dreading going out in the hot sun without SPF 1000 so Im dallying on the puter 
for as long as I can 

some situations I found for doxia (that you pointed out yesterday):

1)Tests wont compile clean e.g. Cast to (LinkItem) was never completed on 
return from parent.getBody().getBreadcrumbs().get(0);
 parentHref = scp://parent.com/index.html;
linkItem =(LinkItem)parent.getBody().getBreadcrumbs().get(0);
linkItem.setHref( parentHref );

2)some of the testcases seem to hang?
Running 
org.apache.maven.doxia.site.decoration.inheritance.DecorationModelInheritenceAssemblerTest
DecorationModelInheritenceAssemblerTest seems to hang for about an hour?

3)doxias maven-enforcer-plugin was set to MaxJdkVersion of 5 here are the 
rules for maxJdkVersion
 plugin
  artifactIdmaven-enforcer-plugin/artifactId
  executions
execution
  idenforce-bytecode-version/id
  goals
goalenforce/goal
  /goals
  configuration
rules
  enforceBytecodeVersion
maxJdkVersion1.5/maxJdkVersion
I have not used Java5 in about 5 years so Im wondering why is doxia hardgated 
to Java 1.5 ?

Thanks
Martin-
Mexico vs Netherlands 12:00 PM (on Telly) ..in south america ..Estádio 
Castelão, Fortaleza Brasil

 Date: Sun, 29 Jun 2014 14:11:13 +0200
 From: khmarba...@gmx.de
 To: dev@maven.apache.org
 Subject: maven-enforcer-plugin
 
 Hi,
 
 i wan't to go with a release (presumably 1.4) within the next two weeks...
 
 Is there something which you would like to integrate that release...so 
 please raise your hand...
 
 Kind regards
 Karl-Heinz Marbaise
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: [VOTE] Release Apache Maven Changelog Plugin version 2.3

[Martin Gainty]

I dont know enough to make an intelligent comment on any of the deltas that may 
have been fixed  in changelog

Deprecating:
As far as deprecating ..be mindful that Maven is used by over 100,000 shops for 
production builds
Before anything gets trashed we need to keep release managers implementing 
previous maven installations satisfied.

*congratulations on your win today*
Martin

 Date: Thu, 26 Jun 2014 22:49:21 +0200
 From: khmarba...@gmx.de
 To: dev@maven.apache.org
 Subject: Re: [VOTE] Release Apache Maven Changelog Plugin version 2.3
 
 Hi,
 
 anyone else?
 
 
   On 6/26/14 1:38 AM, Olivier Lamy wrote:
  +1
 
  On 25 June 2014 05:43, Karl Heinz Marbaise khmarba...@gmx.de wrote:
  Hi,
 
  We solved 13 issues:
  http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11211version=16516
 
  There are still a couple of issues left in JIRA:
  http://jira.codehaus.org/issues/?jql=project%20%3D%20MCHANGELOG%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
 
  Staging repo:
  https://repository.apache.org/content/repositories/maven-1027
 
  http://repository.apache.org/content/repositories/maven-1027/org/apache/maven/plugins/maven-changelog-plugin/2.3/maven-changelog-plugin-2.3-source-release.zip
 
  Source release checksum(s):
  maven-changelog-plugin-2.3-source-release.zip sha1:
  66bf25b213e3af3cbe4de850e06ddd2bfc1414f7
 
  Staging site:
  http://maven.apache.org/plugins-archives/maven-changelog-plugin-LATEST/
 
  Guide to testing staged releases:
  http://maven.apache.org/guides/development/guide-testing-releases.html
 
  Vote open for 72 hours.
 
  [ ] +1
  [ ] +0
  [ ] -1
 
  Kind regards
  Karl-Heinz Marbaise
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 
 
 
 
 Mit freundlichem Gruß
 Karl-Heinz Marbaise
 -- 
 SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
 Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029
 Hauptstrasse 177 USt.IdNr: DE191347579
 52146 Würselen   http://www.soebes.de
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Topics for Maven Development Hangout

[Martin Gainty]

I wondered  why Hangout was setup for 1400pm Brasil time instead of CEST?

I like the idea of flattened poms but I'm hesitant to advocate their usage 
without knowing the pros/cons for FP.

I would also like to see more on full software development 
lifecycle..Occassionaly i see plugins that dont have positive testcases
reason being is that they most probably would'nt work..one that actually 
stopped my most recent deployment in its tracks..

I would love to see how other languages populate Template Types that guice 
implements..e.g. populate this using Ruby T ?

I think Stephen, Kristian and Benson have a lot of good ideas and i would 
welcome their participation if they have the time.
Thanks,
Martin 


 Date: Thu, 19 Jun 2014 20:05:10 +0200
 From: khmarba...@gmx.de
 To: dev@maven.apache.org
 Subject: Re: Topics for Maven Development Hangout
 
 Hi,
   22:00-23:00 CEST was fine for me. And Thursday shouldn't be a problem
  for me.
 
 vote for that too...here in europe...
 
 Kind regards
 Karl-Heinz
 
 
  Robert
 
  Op Thu, 19 Jun 2014 18:41:18 +0200 schreef Jason van Zyl ja...@takari.io:
 
  Sure, how about Thursday? We were also thinking of trying to make it
  earlier in the day for Europeans. It was a scheduling error on my part
  making it late at night in Europe.
 
  On Jun 19, 2014, at 12:08 PM, Stephen Connolly
  stephen.alan.conno...@gmail.com wrote:
 
  Can we move it to a day of the week other than Wed? as I'd really
  like to
  join
 
 
  On 19 June 2014 16:51, Tamás Cservenák ta...@cservenak.net wrote:
 
  I did not make it for the first one, but watched the recording.
 
  One topic I'd like to propose is about thing mentioned at very last
  minutes
  of the recording: repository tags in POM, smarter protocol between
  Maven
  and MRM, etc
 
  Should we have some wiki with topic proposals maybe?
 
 
  Thanks,
  ~t~
 
 
  Thanks,
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Resolving the dependencies for an Artifact

[Martin Gainty]

 Date: Fri, 20 Jun 2014 08:29:10 +1000
 Subject: Re: Resolving the dependencies for an Artifact
 From: william.fergu...@xandar.com.au
 To: dev@maven.apache.org
 
 Hi Robert,
 
 Use case is within the android-maven-plugin we need to generate artefacts
 for AAR (Android archive) dependencies when building a project.
 
 When doing so we need to provide the dependencies of the AAR (not the
 project) into the generation tool. We can readily retrieve the deps for the
 AAR by looking through the dependency graph of the project until we find
 the AAR that then collect deps from there on.
 
 This works fine for project (A) that has a dependency on B and C.
 But if A has dep on B  C and B also has a dep on C then it breaks because
 Maven's dependency resolution (for A, ie the project) will ignore the B-C
 dep because A-C is more direct. So when we look for the deps of B we never
 see C.
 
 NB maven-dependency-plugin uses maven-dependency-tree for its resolution,
 which is where I've taken most of my lead so far.
 
 It gets down to the context in which the resolution is being done. I need
 the context to be B instead of A and in order to do that I need to get the
 MavenProject for B. And this is where I am stuck.
MGIf I understand a prioritised dependency shortcut of A-B then B-C (instead 
of A-C)?
MGput this on the Jason's wishlist for Maven 4.x!
MGdoes anyone know if Maven has ability to reorder the dependency graph?
 
 William
 
 
 On Fri, Jun 20, 2014 at 4:44 AM, Robert Scholte rfscho...@apache.org
 wrote:
 
  Hi William,
 
  most of the time it's not necessary to find a specific file like this, so
  I'm wondering what the usecase is.
 
  If you're hitting an issue, think of a plugin which might have the same
  issue and have a look at its code.
  In this case I'm thinking of the maven-dependency-plugin, especially the
  code for dependency:tree.
  Or use the org.apache.maven.project.ProjectBuilder
 
  thanks,
  Robert
 
  Op Thu, 19 Jun 2014 00:01:52 +0200 schreef William Ferguson 
  william.fergu...@xandar.com.au:
 
   I asked on maven-users but didn't get any viable responses. So I'm hoping
  someone here can help.
 
  --
  I have a Mojo that needs to work with Maven 3.0.* and 3.1+
 
  In the Mojo I have an Artifact and I need to resolve it's dependencies.
  How
  can/should I do it?
 
  If I can resolve the Artifact to a MavenProject then I can use
  DependencyGraphBuilder (from maven-dependency-tree) to construct a graph
  of
  the deps. But I'm struggling to make the Artifact to MavenProject
  conversion happen.
 
  I thought that If I could get a URL to the Artifact's POM file then I
  could
  use DefaultMavenRuntime (maven-runtime) to resolve the URL into a
  MavenProject. But
 
 1. I can't work out how to get a URL to the artifact's POM file (it
 
 needs to handle both reactor artifacts and repo artifacts)
 2. Even with a URL to the POM file, MavenRuntime#getProject) is
 
 returning null.
 
  Can someone please point me in the right direction?
  Am I even on the right path or is there a much more straight forward way
  of
  getting the dependencies for the Artifact?
  --
 
  William
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
  

RE: A thought on local-SNAPSHOTs

[Martin Gainty]

 To: dev@maven.apache.org
 Subject: Re: A thought on local-SNAPSHOTs
 Date: Sun, 15 Jun 2014 13:08:17 +0200
 From: rfscho...@apache.org
 
 Op Sun, 15 Jun 2014 11:07:33 +0200 schreef Stephen Connolly  
 stephen.alan.conno...@gmail.com:
 
  The real issue I see is people not defining their snapshot policy (and I
  mean that in a wider sense)
 
  Personally speaking I favour *never* deploying snapshots. Only using them
  for local speed up where a large reactor required to wire everything up
  using either the `package` or `verify` phase (with or without tests
  skipped) would just take too long.
 
 exactly my thoughts as well. I see a lot of users still doing 'install'  
 for the wrong reasons:
 - coworkers said so / internet said so.
 
  So for me, with my pattern of creating local aggregator projects and not
  really installing let alone deploying snapshots, there is no problem...
 
  When working on projects however that use a CI system to deploy snapshots
  after every build... Well I tend to curse them (or turn off snapshot  
  update
  checking)... Worse is where this was done because building a specific
  artifact requires a toolchain I do not have access to on my machine...  
  So I
  am forced to turn on snapshot checking for every build while working on
  that module.
 
  What you usually find is people have not realised the cause and effect.
 
  I favour the CI server deploying snapshots with every build *but* into a
  repo only for use by the CI server.
 
  I favour never deploying smapshots to developer repositories... Any time
  you think you need to... Well you probably just need to cut a release...
  Can't cut a release because tests are failing? Wtf are you giving me that
  broken shit for... Timestamped snapshots are just a crutch...
 
  My €0.02
 
 
 I like to improve the lifecycle even a bit. If you do a deploy, the  
 install should be skipped. This way all co-workers will pull the same  
 instance. If the deploy fails, your local repo is still clean.
 My current thought is to introduce the ability to split the lifecycle.
 
  :
  :
verify
/\
 installdeploy
 
 This would improve the reliability of Maven, make it a bit faster and in  
 the end both 'mvn install' and 'mvn deploy' will keep the same behavior.
 
 thanks,
 Robert
 
  On Sunday, 15 June 2014, Mark Derricutt m...@talios.com wrote:
 
  Hey all,
 
  A recent discussion on one of the github PR's led to a discussion on
  SNAPSHOT resolution, which is a long standing issue in maven range  
  support
  with several long standing open tickets lingering.
 
  A thought I just had, which relates to some things I've been playing  
  with
  in my C.I. builds, could quite simply resolve this.  Maybe
 
  I know a few people who say they just don't allow/use SNAPSHOTs but
  whenever you do an `mvm install` you end up with a -SNAPSHOT in your
  ~/.m2/repository - and that then affects resolution.
 
  My thought was  why is the local _repository_ treated differently to
  normal repositories - in that it's as tho  
  `snapshotsenabledtrue/enabled/snapshots`
  is defined for them - and maybe it is? Why not simply _disable_  
  that.
 
  But further than that, what if maven tracked TWO local repositories:
 
~/.m2/repository
~/.m2/snapshots
 
  Much like `distributionManagement ` has two a `repository` and
  `snapshotRepository` section, what if we have an  
  `installationManagement`
  section ( probably limited only to `settings.xml` for install wide
  settings? ) that did the same, but for the local repository? -SNAPSHOTs
  installed via `mvn install` or downloaded via dependencies would go in  
  here.
 
  This way - there's a clear separation of snapshots and releases, if you
  don't want snapshot resolution - disable that local repository
 
  Thoughts?
 
  Mark
 
 
MGSNAPSHOTs are Murphy on your back Not only maven but eclipse distros going 
into local p2 repo
MGSpent most of the weekend trying to get eclipse buildnumber to sub in 
reasonable version on SNAPS
MG24 hours later i called nojoy and mv  SNAPs and success deployed eclipse 
distros into local p2 repo
MGI agree with Stephen ..if a SNAP is'nt validated for public use dont put in 
any repo
MGBTW: nexus repositories have 3 categories of distros SNAPs, STAGED and 
RELEASEs
MGHappy Fathers Day

 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Not able to download artifact java-ee-apis from com.ibm.websphere

[Martin Gainty]

 answered on axis developers list

You can find it in the WAS installation directory under 
plugins/com.ibm.ws.runtime.jar.

Br
Martin

  


 Date: Mon, 28 Apr 2014 01:22:23 -0700
 From: suhaslonar...@gmail.com
 To: dev@maven.apache.org
 Subject: Not able to download artifact java-ee-apis from com.ibm.websphere
 
 Hi Team,
 
 I am having trouble to download artifact java-ee-apis from from
 com.ibm.websphere.
 
 Current dependency I have added
 dependency
 groupIdcom.ibm.websphere/groupId
 artifactIdjava-ee-apis/artifactId
 /dependency
 
 Then to resolve this issue I have added below dependency.
 dependency
 groupIdjavax/groupId
 artifactIdjavaee-api/artifactId
 version6.0/version
 /dependency
 
 After adding above dependencies build was successfully created and EAR also
 but its my feeling that like I have replaced com.ibm.websphere dependency
 with javax ...will it make difference in prod? will it conflict?
 
 What is recommended fix for this ?
 
 Please help me on this :)
 
 
 
 --
 View this message in context: 
 http://maven.40175.n5.nabble.com/Not-able-to-download-artifact-java-ee-apis-from-com-ibm-websphere-tp5792082.html
 Sent from the Maven Developers mailing list archive at Nabble.com.
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Maven Build Systems

[Martin Gainty]

  


 Date: Sun, 30 Mar 2014 12:57:29 +0200
 From: khmarba...@gmx.de
 To: dev@maven.apache.org
 Subject: Maven Build Systems
 
 Hi,
 
 just wan't to know if i'm right...
 Currently i got messages from the Apache build system like this:
 
 The project org.apache.maven.plugins:maven-plugins:26-SNAPSHOT 
 (/x1/jenkins/jenkins-slave/workspace/maven-plugins-ITs-m3/maven-plugins/pom.xml)
  
 has 1 error
 [ERROR] Non-resolvable parent POM: Could not find artifact 
 org.apache.maven:maven-parent:pom:24 in central 
 (http://repo.maven.apache.org/maven2) and 'parent.relativePath' points 
 at wrong local POM @ line 23, column 11 - [Help 2]
MGrelativePath doesnt point to parent pom but points to thin air..commenting 
out fixes
MG
MGSwitching topics to maven-site-plugin the way I got it to work was
MGclean folder run plugin maven-project-info-reports-plugin e.g. 
MGplugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-project-info-reports-plugin/artifactId
  version2.7/version
  configuration
   maven.site.deploy.skipfalse/maven.site.deploy.skip
dependencyDetailsEnabledfalse/dependencyDetailsEnabled
dependencyLocationsEnabledfalse/dependencyLocationsEnabled
   /configuration
  /plugin
MGa valid site.xml *should* be located in /src/site
MGall applicable *.html *should* be located in /target/site in target/apidocs 
or target/xref or target/examples
MGimages should be stored in /target/images folder
MGcss files should be stored in /target/css folder
MGVelocity Macros *should* be stored in base folder where they are used e.g. 
/examples/selective-project-info-reports.apt.vm
MGAlmost Plain Text should be stored in /src/site/apt folder e.g.
/src/site/apt/index.apt
MGFWIK these are all the files that maven-site-plugin will deploy no change in 
files, layout or structure
MGsite generation to the best of my knowledge is now complete so you *should* 
be able to deploy with
MGmvn site:deploy
 MGIF you want a more capable deployer I would look at Puppet Enterprise
MGDoes this answer your questions/concerns on mvn-site-plugin?
MGMartin
 
 Kind regards
 Karl-Heinz Marbaise
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Maven Build Systems

[Martin Gainty]

Im answering my emails from this am i hope.. by tonite I can read all my emails


BTW if you need a maven skin have a look at maven-default-skin
http://maven.apache.org/skins/maven-default-skin/sample/

 

Does anyone know what  pixware.fr  is about?


Merci Karl!

  



 Date: Sun, 30 Mar 2014 20:48:27 +0200
 From: khmarba...@gmx.de
 To: dev@maven.apache.org
 Subject: Re: Maven Build Systems
 
 Hi Martin,
 
 
 MGrelativePath doesnt point to parent pom but points to thin 
 air..commenting out fixes...
 
 Have you read the answer of Hervéa few hours before ...?
 
 Kind regards
 Karl-Heinz Marbaise
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Welcome Mirko Friedenhagen to the Apache Maven Team

[Martin Gainty]

Willkommen  Mirko!

Martin --

  


 Date: Mon, 17 Mar 2014 21:06:17 +0100
 From: khmarba...@gmx.de
 To: dev@maven.apache.org
 Subject: Re: Welcome Mirko Friedenhagen to the Apache Maven Team
 
 Hi Mirko,
 
  On behalf of the Apache Maven PMC I am pleased to announce that Mirko
  Friedenhagen (mfriedenhagen) has been voted in as a new Apache Maven
  committer.
 
 Cool...welcome on board...
 
 Happy hacking...
 Kind regards
 Karl-Heinz Marbaise
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Using Maven Project (JAR) as library for non-Maven Android project

[Martin Gainty]

I would suggest implementing your Android Application with maven-android-plugin
https://code.google.com/p/maven-android-plugin/

 

Obrigado!
Martín 
__ 


  



 Date: Thu, 13 Mar 2014 20:31:10 -0300
 Subject: Using Maven Project (JAR) as library for non-Maven Android project
 From: agapito.an...@gmail.com
 To: dev@maven.apache.org
 
 Hello,
 I'm developing an Android Application (Non-Maven) and I'd like to use a
 Maven Project as library. Is this possible? How to import a Maven jar file
 as library to a Non-Maven project?
 
 original-MavenOBD-0.0.1-SNAPSHOT.jar
 
 Thanks,
 BR
 
 
 
 
 *André Camargo AgapitoCel: 55 (11) 90309-1221São
 Paulo/spagapito.an...@gmail.com agapito.an...@gmail.com*
  

RE: Maven-release-plugin and scm site publication: need help

[Martin Gainty]

MGso in your instance why does'nt maven-scm-publish to ~/maven-sites ??

  


 Date: Sun, 23 Feb 2014 09:52:12 -0500
 Subject: Re: Maven-release-plugin and scm site publication: need help
 From: bimargul...@gmail.com
 To: dev@maven.apache.org
 
 Never mind, I found the shell script left behind by the last person
 who did this. I
 
 On Sun, Feb 23, 2014 at 7:38 AM, Benson Margulies bimargul...@gmail.com 
 wrote:
  I've staged 2.5 of the maven-release component. However, the
  documentation staging process is failing.
 
  mvn -Preporting site site:stage
 
  does not write into the ~/maven-sites directory where the scm plugin 
  expects it.
 
  Could some kind soul either checkout the tag and patch this up and
  stage it, or commit a fix, or give me a hint? I get on an airplane in
  7 hours.
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

Sonatype plugin question?

[Martin Gainty]

I *think* the sonatype folk went home for weekend so I'll ask maven gurus


Close to getting a plugin working but when i start wrapper.exe the wrapper.log 
displays this error:

The following plugins were processed:
jvm 1| ... 
org.sonatype.nexus.plugins:stagingrules-nexus-plugin:1.0-SNAPSHOT :: 
action=ACTIVATE result=BROKEN
jvm 1|Reason: Plugin artifact 
com.sonatype.nexus:nexus-core:2.7.0::jar not found!


Ideas on where com.sonatype.nexus:nexus-core:2.7.0::jar should be located?

local repo?
some undisclosed maven repo?

classpath?

 

HELP!
Martin 


  



  

RE: Sonatype plugin question?

[Martin Gainty]

I wrote and installed a quick and dirty sonatype plugin
My Nexus OpenSource distro that Im testing against is 2.8.0-SNAPSHOT
my plugin examples came from 2.7.0
If Monday am comes and Im calling no joy... i'll revert nexus back to 2.7.0 and 
test on that

I guess Sonatype folk are is in Russia or watching the Olympics

Thanks Igor!
Martin-

  



 Date: Sat, 22 Feb 2014 19:23:08 -0500
 From: i...@ifedorenko.com
 To: dev@maven.apache.org
 Subject: Re: Sonatype plugin question?
 
 I think this message comes from a Nexus server, and the plugin refers
 to Nexus plugin running on the server. Almost looks like a broken Nexus
 installation, but it's been some time since I last looked at Nexus.
 
 --
 Regards,
 Igor
 
 
 On 2/22/2014, 19:08, Martin Gainty wrote:
  I *think* the sonatype folk went home for weekend so I'll ask maven gurus
 
 
  Close to getting a plugin working but when i start wrapper.exe the 
  wrapper.log displays this error:
 
  The following plugins were processed:
  jvm 1 | ... 
  org.sonatype.nexus.plugins:stagingrules-nexus-plugin:1.0-SNAPSHOT :: 
  action=ACTIVATE result=BROKEN
  jvm 1 | Reason: Plugin artifact com.sonatype.nexus:nexus-core:2.7.0::jar 
  not found!
 
 
  Ideas on where com.sonatype.nexus:nexus-core:2.7.0::jar should be located?
 
  local repo?
  some undisclosed maven repo?
 
  classpath?
 
 
 
  HELP!
  Martin
 
 
 
 
 
 
  
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Sonatype plugin question?

[Martin Gainty]

wondering where nexus is looking to resolve dependencies?
I'll try scopeprovided/scope for nexus-core

 

(re)posted to nexus-...@sonatype.org‏

Thanks Stewart
Martin

  



 Subject: Re: Sonatype plugin question?
 From: mccu...@gmail.com
 Date: Sun, 23 Feb 2014 00:37:17 +
 To: dev@maven.apache.org
 
 On 23 Feb 2014, at 00:08, Martin Gainty mgai...@hotmail.com wrote:
  I *think* the sonatype folk went home for weekend so I'll ask maven gurus
 
 Odd assumption, why didn’t you at least try asking this question on 
 nexus-user or nexus-dev?
 
  Close to getting a plugin working but when i start wrapper.exe the 
  wrapper.log displays this error:
  
  The following plugins were processed:
  jvm 1 | ... 
  org.sonatype.nexus.plugins:stagingrules-nexus-plugin:1.0-SNAPSHOT :: 
  action=ACTIVATE result=BROKEN
 
 Is this your own plugin? You should ideally choose a groupId that matches 
 your organization/company
 
  jvm 1 | Reason: Plugin artifact com.sonatype.nexus:nexus-core:2.7.0::jar 
  not found!
 
 Looks like your pom.xml has a bad dependency - nexus-core has a groupId of 
 org.sonatype.nexus and should be a provided dependency
 
 In fact you should really just depend on nexus-plugin-api as explained in 
 http://books.sonatype.com/nexus-book/reference/plugdev.html
 
  Ideas on where com.sonatype.nexus:nexus-core:2.7.0::jar should be located?
  
  local repo?
  some undisclosed maven repo?
  
  classpath?
  
  HELP!
 
 Best way to get help is to ask this on either of the nexus mailing lists 
 (http://www.sonatype.org/nexus/participate) - paste a copy of your plugin 
 pom.xml
 
  Martin 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: ftps

[Martin Gainty]

Hi Jeff


Is this what you're referring to:


wagon-providers/wagon-file/target/surefire-reports/TEST-org.apache.maven.wagon.providers.file.FileWagonTest.xml


  testcase name=testWagonGetIfNewerToStreamIsNewer 
classname=org.apache.maven.wagon.providers.file.FileWagonTest time=0.15
error 
type=java.lang.NullPointerException:java.lang.NullPointerException: null
 at org.apache.maven.wagon.WagonTestCase.getWagon(WagonTestCase.java:214)
 at org.apache.maven.wagon.WagonTestCase.putFile(WagonTestCase.java:866)
 at org.apache.maven.wagon.WagonTestCase.putFile(WagonTestCase.java:922)
 at 
org.apache.maven.wagon.StreamingWagonTestCase.testWagonGetIfNewerToStreamIsNewer(StreamingWagonTestCase.java:106)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
 at junit.framework.TestCase.runTest(TestCase.java:168)
 at junit.framework.TestCase.runBare(TestCase.java:134)
 at junit.framework.TestResult$1.protect(TestResult.java:110)
 at junit.framework.TestResult.runProtected(TestResult.java:128)
 at junit.framework.TestResult.run(TestResult.java:113)
 at junit.framework.TestCase.run(TestCase.java:124)
 at junit.framework.TestSuite.runTest(TestSuite.java:243)
 at junit.framework.TestSuite.run(TestSuite.java:238)
 at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
 at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
 at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
 at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
/error


bashls -al file-list

 

drwxr-xr-x2 mgainty  Administ0 Jan 14 15:19 
testWagonGetIfNewerIsSame.file-repository.1389730775510
drwxr-xr-x1 mgainty  Administ0 Jan 14 14:56 
testWagonGetIfNewerToStreamIsNewer.file-repository.1389729415483
drwxr-xr-x1 mgainty  Administ0 Jan 14 15:17 
testWagonGetIfNewerToStreamIsNewer.file-repository.1389730620309
drwxr-xr-x2 mgainty  Administ0 Jan 14 15:19 
testWagonGetIfNewerToStreamIsNewer.file-repository.1389730775263
drwxr-xr-x2 mgainty  Administ0 Jan 14 14:56 
testWagonGetIfNewerToStreamIsOlder.file-repository.1389729415589
drwxr-xr-x1 mgainty  Administ0 Jan 14 15:17 
testWagonGetIfNewerToStreamIsOlder.file-repository.1389730620412
drwxr-xr-x1 mgainty  Administ0 Jan 14 15:19 
testWagonGetIfNewerToStreamIsOlder.file-repository.1389730775411
drwxr-xr-x2 mgainty  Administ0 Jan 14 14:56 
testWagonGetIfNewerToStreamIsSame.file-repository.1389729415614
drwxr-xr-x2 mgainty  Administ0 Jan 14 15:17 
testWagonGetIfNewerToStreamIsSame.file-repository.1389730620428
drwxr-xr-x1 mgainty  Administ0 Jan 14 15:19 
testWagonGetIfNewerToStreamIsSame.file-repository.1389730775420
drwxr-xr-x1 mgainty  Administ0 Jan 14 14:56 
testWagonPutDirectory.file-repository.1389729415700
drwxr-xr-x2 mgainty  Administ0 Jan 14 15:17 
testWagonPutDirectory.file-repository.1389730620528
drwxr-xr-x2 mgainty  Administ0 Jan 14 15:19 
testWagonPutDirectory.file-repository.1389730775529
drwxr-xr-x1 mgainty  Administ0 Jan 14 14:56 
testWagonPutDirectoryDeepDestination.file

repository.1389729415772
drwxr-xr-x1 mgainty  Administ0 Jan 14 15:17 
testWagonPutDirectoryDeepDestination.file-repository.1389730620468
drwxr-xr-x2 mgainty  Administ0 Jan 14 15:19 
testWagonPutDirectoryDeepDestination.file-repository.1389730775492
drwxr-xr-x2 mgainty  Administ0 Jan 14 14:56 
testWagonPutDirectoryForDot.file-repository.1389729415706
drwxr-xr-x1 mgainty  Administ0 Jan 14 15:17 
testWagonPutDirectoryForDot.file-repository.1389730620537
drwxr-xr-x1 mgainty  Administ0 Jan 14 15:19 
testWagonPutDirectoryForDot.file-repository.1389730775537
drwxr-xr-x1 mgainty  Administ0 Jan 14 14:56 
testWagonPutDirectoryWhenDirectoryAlreadyExists.file-repository.1389729415664
drwxr-xr-x1 mgainty  Administ0 Jan 14 15:17 
testWagonPutDirectoryWhenDirectoryAlreadyExists.file-repository.1389730620488
drwxr-xr-x1 mgainty  Administ0 Jan 14 15:19 
testWagonPutDirectoryWhenDirectoryAlreadyExists.filerepository.1389730775477
drwxr-xr-x1 mgainty  Administ0 Jan 14 14:56 
testWagonResourceExists.file-repository.1389729415743
drwxr-xr-x2 mgainty  Administ0 Jan 14 15:17 
testWagonResourceExists.file-repository.1389730620555
drwxr-xr-x2 mgainty  Administ0 Jan 

RE: ftps

[Martin Gainty]

  


 Date: Tue, 14 Jan 2014 11:22:55 -0500
 Subject: ftps
 From: shawj...@gmail.com
 To: dev@maven.apache.org
 
 Would anyone like to work on an FTPS maven-wagon provider? I have one
 started at https://github.com/shawjef3/maven-wagon/tree/wagon-ftps . So far
 it's mostly a copy-paste of the FTP provider, but of course there are some
 changes. It compiles, but testing fails when a thread fails to start. The
 debug log isn't helping me much, but I might just not know where to look.
 
 Jeff
MGso if we can find test-resource.pom, test-resource b.txt, 
more-resources.dat  files and put them in 'file-list' folder
MGwe can at least get over the testcase failure
MGWDYT?  

RE: Welcome Karl Heinz Marbaise as a Maven Committer

[Martin Gainty]

Willkommen Karl!

Martin

 To: dev@maven.apache.org; us...@maven.apache.org
 Date: Fri, 3 Jan 2014 20:38:41 +0100
 Subject: Welcome Karl Heinz Marbaise as a Maven Committer
 From: rfscho...@apache.org
 
 Hi Maven folks!
 
 The Apache Maven PMC is glad to welcome Karl Heinz Marbaise as new Apache  
 Maven Committer!
 Most of us already know Karl Heinz from his work on several Maven plugins  
 as member of the Codehaus Mojo team and his activities on other Maven  
 related projects.
 
 Karl Heinz, congrats and welcome on board!
 
 Robert
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Plugin phase awareness...

[Martin Gainty]

-SNAPSHOT\maven-metadata-local.xml
[DEBUG] Installing test:lifecycle-phase-plugin-test/maven-metadata.xml to 
C:\Users\mgainty\.m2\repository\test\lifecycle-phase-plugin-test\maven-metadata-local.xml
[INFO] 
[INFO] --- lifecycle-phases-plugin:1.0:phase-name (install-phase) @ 
lifecycle-phase-plugin-test ---
[DEBUG] Configuring mojo test:lifecycle-phases-plugin:1.0:phase-name from 
plugin realm ClassRealm[plugintest:lifecycle-phases-plugin:1.0, parent: 
sun.misc.Launcher$AppClassLoader@68ffab0a]
[DEBUG] Configuring mojo 'test:lifecycle-phases-plugin:1.0:phase-name' with 
basic configurator --
[DEBUG]   (f) execution = test:lifecycle-phases-plugin:1.0:phase-name 
{execution: install-phase}
[DEBUG]   (f) phase = install
[DEBUG] -- end configuration --
[INFO] [phase-name] Maven lifecycle phase is install
MG(correct)


so compiling and running with JDK/JVM/JRE 1.7.0_45 does correct the bug
I will update JIRA that this only fails with 1.7.0_25 JDK/JVM/JRE (and does not 
fail with JDK/JVM/JRE 1.7.0_45)

https://jira.codehaus.org/browse/MNG-

 

I am puzzled why this bug is manifested when compiling and executing with 
1.7.0_25 
I would appreciate hearing about bug-fixes from the JVM team that were 
corrected in 1.7.0_25 (in the 1.7.0_45 release)

 

Much appreciated Mr Patrick!
Happy New Year

Martin Gainty 
__ 
Porfavor..no altere ni interrumpir esta communicacion..Gracias
Please ..do not alter or interrupt this communicaction..Thank You

  



 Date: Mon, 30 Dec 2013 15:02:05 -0800
 From: robert.patr...@oracle.com
 To: mgai...@hotmail.com; dev@maven.apache.org
 Subject: RE: Plugin phase awareness...
 
 I don't have Maven 3.02 or Java 7u25 handy but as you can see from my example 
 execution below, Maven 3.0.5 and Java 7u45 works fine-that is, multiple 
 executions of the plugin in the different lifecycle phases that I have 
 executions declared in my project POM for all return the same value as the 
 lifecycle phase).
 
  
 
 C:\rpatrick\work\src\maven\lifecycle-phase\test-projectmvn  -version
 
 Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 
 07:51:
 
 28-0600)
 
 Maven home: c:\wls1213\oracle_common\modules\org.apache.maven_3.0.5
 
 Java version: 1.7.0_45, vendor: Oracle Corporation
 
 Java home: c:\java\jdk1.7.0\jre
 
 Default locale: en_US, platform encoding: Cp1252
 
 OS name: windows 7, version: 6.1, arch: amd64, family: windows
 
  
 
 C:\rpatrick\work\src\maven\lifecycle-phase\test-projectmvn install
 
 [INFO] Scanning for projects...
 
 [INFO]
 
 [INFO] 
 
 
 [INFO] Building lifecycle-phase-plugin-test 1.0-SNAPSHOT
 
 [INFO] 
 
 
 [INFO]
 
 [INFO] --- lifecycle-phases-plugin:1.0:phase-name (validate-phase) @ 
 lifecycle-p
 
 hase-plugin-test ---
 
 [INFO] [phase-name] Maven lifecycle phase is validate
 
 [INFO]
 
 [INFO] --- lifecycle-phases-plugin:1.0:phase-name (compile-phase) @ 
 lifecycle-ph
 
 ase-plugin-test ---
 
 [INFO] [phase-name] Maven lifecycle phase is compile
 
 [INFO]
 
 [INFO] --- lifecycle-phases-plugin:1.0:phase-name (process-classes-phase) @ 
 life
 
 cycle-phase-plugin-test ---
 
 [INFO] [phase-name] Maven lifecycle phase is process-classes
 
 [INFO]
 
 [INFO] --- lifecycle-phases-plugin:1.0:phase-name (package-phase) @ 
 lifecycle-ph
 
 ase-plugin-test ---
 
 [INFO] [phase-name] Maven lifecycle phase is package
 
 [INFO]
 
 [INFO] --- lifecycle-phases-plugin:1.0:phase-name 
 (pre-integration-test-phase) @
 
 lifecycle-phase-plugin-test ---
 
 [INFO] [phase-name] Maven lifecycle phase is pre-integration-test
 
 [INFO]
 
 [INFO] --- lifecycle-phases-plugin:1.0:phase-name 
 (post-integration-test-phase)
 
 @ lifecycle-phase-plugin-test ---
 
 [INFO] [phase-name] Maven lifecycle phase is post-integration-test
 
 [INFO]
 
 [INFO] --- lifecycle-phases-plugin:1.0:phase-name (verify-phase) @ 
 lifecycle-pha
 
 se-plugin-test ---
 
 [INFO] [phase-name] Maven lifecycle phase is verify
 
 [INFO]
 
 [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
 lifecycle-phas
 
 e-plugin-test ---
 
 [INFO] Installing 
 C:\rpatrick\work\src\maven\lifecycle-phase\test-project\pom.xm
 
 l to 
 C:\Users\rpatrick\.m2\repository\test\lifecycle-phase-plugin-test\1.0-SNAPS
 
 HOT\lifecycle-phase-plugin-test-1.0-SNAPSHOT.pom
 
 [INFO]
 
 [INFO] --- lifecycle-phases-plugin:1.0:phase-name (install-phase) @ 
 lifecycle-ph
 
 ase-plugin-test ---
 
 [INFO] [phase-name] Maven lifecycle phase is install
 
 [INFO] 
 
 
 [INFO] BUILD SUCCESS
 
 [INFO] 
 
 
 [INFO] Total time: 0.880s
 
 [INFO] Finished at: Mon Dec 30 16:55:29 CST 2013
 
 [INFO] Final Memory: 14M/490M
 
 [INFO

RE: Plugin phase awareness...

[Martin Gainty]

 
Good Morning Patrick

could you upload plugin and test-harness somewhere (and let me have access).. I 
would really like to get this working
(and close out this bug)

Many Thanks for your help (and support)!
Martin Gainty 
__ 

Inte förändra och störa denna överföring tack


  


Date: Mon, 30 Dec 2013 07:46:49 -0800
From: robert.patr...@oracle.com
To: dev@maven.apache.org
Subject: RE: Plugin phase awareness...

Seems to work properly with Maven 3.0.5 anyway.  See attached plugin and test 
project.
 
 
--
Robert Patrick robert.patr...@oracle.com
VP, FMW Platform Architecture
Oracle Corporation  Office: +1.940.725.0011
1148 Triple Crown Court Fax: +1.940.725.0012
Bartonville, TX 76226, USA  Mobile: +1.469.556.9450
 
Professional Oracle WebLogic Server
by Robert Patrick, Gregory Nyberg, and Philip Aston
with Josh Bregman and Paul Done
Book Home Page: http://www.wrox.com/
Kindle Version: http://www.amazon.com/
 
 
-Original Message-
From: Martin Gainty [mailto:mgai...@hotmail.com] 
Sent: Sunday, December 29, 2013 7:25 PM
To: Maven Developers List
Subject: RE: Plugin phase awareness...
 
 
  
 
 
 From: mgai...@hotmail.com
 To: dev@maven.apache.org
 Subject: RE: Plugin phase awareness...
 Date: Sun, 29 Dec 2013 17:46:29 -0500
 
 
 
 
 
 
  Date: Sun, 29 Dec 2013 15:13:12 +
  Subject: Re: Plugin phase awareness...
  From: stephen.alan.conno...@gmail.com
  To: dev@maven.apache.org
  
  Are you running the mojo directly in your testing by any chance?
  
  Eg
  
  mvn short-name:goal
 MGCorrect I was testing in this fashion
 
  As opposed to
  
  mvn phase
 MGThanks Stephen I will try this out
MG_12_29_2013
 /**
  * @parameter expression=${mojoExecution}
  */
 @Parameter(defaultValue = ${mojoExecution})  private 
org.apache.maven.plugin.MojoExecution execution; //supposedly mojoExecution 
injected here  public org.apache.maven.plugin.MojoExecution getExecution() { 
return execution; } //accessor for execution
 /**
  * @parameter expression=${mojoExecution.lifecyclePhase}
  */
@Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
private String lifecyclePhase; //supposedly lifecyclePhase is injected here
public org.apache.maven.model.Plugin plugin=new 
org.apache.maven.model.Plugin();
public String getLifecyclePhase() { //accessor for lifecyclePhase
   if(lifecyclePhase==null) {
plugin.setGroupId(org.apache.maven.plugins);
plugin.setArtifactId(maven-compiler-plugin);
plugin.setVersion(3.1);
String goal=compile;
String executionId=executionId;
System.out.println(CompilerMojoTestCase::getLifecyclePhase 
goal=+goal+ executionId=+executionId);
org.apache.maven.plugin.MojoExecution mojo=new 
org.apache.maven.plugin.MojoExecution((org.apache.maven.model.Plugin)plugin, 
goal, executionId );
lifecyclePhase= mojo.getLifecyclePhase();
   }
  return lifecyclePhase;
 }
 
MG_12_29_2013public void testCompilerBasic() throws Exception {
  System.out.println(CompilerMojoTestCase::testCompilerBasic LINE 143 
getLifeyclePhase()= +getLifecyclePhase());
 
MG_12_29_2013mvn -e -X -o process-test-classes 1 errors.lst 
MG_12_29_2013CompilerMojoTestCase::getLifecyclePhase goal=compile 
executionId=executionId
MG_12_29_2013CompilerMojoTestCase::testCompilerBasic LINE 143 
getLifeyclePhase()= null
 
MG_12_29_2013My thinking is that lifecyclePhase is somehow not being injected..
MG_12_29_2013Ideas?
 
  Because if the former, then the phase is null as the execution was 
  not bound to a phase.
  
  I have not used this specific property before, so cannot speak to 
  whether it works when bound to a phase, but if your test plugin 
  execution is not bound to a phase then you would not expect to see a 
  non null value
  
  On Sunday, 29 December 2013, Martin Gainty wrote:
  
   Morning All-
  
  
  
   Even after downloading maven-core 3.1.1 source and re-compiling to 
   new maven-core-3.1.1.jar distro and forcing maven-core-3.1.1 
   dependency into maven-surefire-plugin
  
  
   I could not get ${mojoExecution.lifecyclePhase} to display 
   anything other than null
  
  
   https://jira.codehaus.org/browse/MNG-
  
  
  
   Ideas?
  
   Martin --
   __
  
  
   Inte förändra och störa denna överföring
  
  
  
  
  
  
  
   From: mgai...@hotmail.com javascript:;
   To: dev@maven.apache.org javascript:;
   Subject: RE: Plugin phase awareness...
   Date: Wed, 25 Dec 2013 22:40:07 -0500
  
  
  
  
   Wasted an enormous amount of time chasing the exact location of 
   .git file.. i guess its a good thing it was Christmas
  
   Thanks Jason!
   Martin Gainty
   __
  
  
  
  
  
From: jpye...@pdinc.us
To: dev@maven.apache.org
Subject: RE: Plugin phase awareness...
Date: Wed, 25 Dec 2013 10:52:34 -0500
   
 -Original Message

RE: Plugin phase awareness...

[Martin Gainty]

operational with JDK-1.6 but compiling and running with Oracle Java 
version=1.7.0.25 reproduces the bug


JDK: 1.6

mvn -version=3.0.2

maven-core:3.0

maven-plugin-annotations:3.2

test-projectmvn -e -X -o compile

[INFO] [phase-name]  Maven lifecycle phase is compile (correct)


JDK: 1.6

mvn -version =3.0.5
maven-core:3.0

maven-plugin-annotations:3.2

test-projectmvn -e -X -o compile

[INFO] [phase-name] Maven lifecycle phase is compile (correct)

 

JDK: 1.6

mvn -version=3.1.1

maven-core:3.0

maven-plugin-annotations:3.2

test-projectmvn -e -X -o compile

[INFO] [phase-name] Maven lifecycle phase is compile (correct)

 

--JDK-1.7.0.25--
BASHmvn -version
Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500)
Java version: 1.7.0_25, vendor: Oracle Corporation
Java home: jdk1.7.0_25/jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family: windows


mvn -version=3.0.2

maven-core:3.0

maven-plugin-annotations:3.2

 

test-projectmvn -e -X -o compile

[INFO] [phase-name] Maven lifecycle phase is validate

 

i wonder if Mr Gosling could possibly shed some light on this ?

Thanks Robert,

Martin-

  



 Date: Mon, 30 Dec 2013 08:07:46 -0800
 From: robert.patr...@oracle.com
 To: dev@maven.apache.org
 Subject: RE: Plugin phase awareness...
 
 I had attached it to the last email but you can grab it here: 
 https://dl.dropboxusercontent.com/u/78116035/maven/lifecycle-phase.zip 
 
 Hope this helps,
 Robert
 
 --
 Robert Patrick robert.patr...@oracle.com
 VP, FMW Platform Architecture
 Oracle Corporation Office: +1.940.725.0011
 1148 Triple Crown Court Fax: +1.940.725.0012
 Bartonville, TX 76226, USA Mobile: +1.469.556.9450
 
 Professional Oracle WebLogic Server
 by Robert Patrick, Gregory Nyberg, and Philip Aston
 with Josh Bregman and Paul Done
 Book Home Page: http://www.wrox.com/
 Kindle Version: http://www.amazon.com/
 
 
 -Original Message-
 From: Martin Gainty [mailto:mgai...@hotmail.com] 
 Sent: Monday, December 30, 2013 10:02 AM
 To: Maven Developers List
 Subject: RE: Plugin phase awareness...
 
 
 Good Morning Patrick
 
 could you upload plugin and test-harness somewhere (and let me have access).. 
 I would really like to get this working (and close out this bug)
 
 Many Thanks for your help (and support)!
 Martin Gainty
 __ 
 
 Inte förändra och störa denna överföring tack
 
 
 
 
 
 Date: Mon, 30 Dec 2013 07:46:49 -0800
 From: robert.patr...@oracle.com
 To: dev@maven.apache.org
 Subject: RE: Plugin phase awareness...
 
 Seems to work properly with Maven 3.0.5 anyway. See attached plugin and test 
 project.
 
 
 --
 Robert Patrick robert.patr...@oracle.com VP, FMW Platform Architecture
 Oracle Corporation Office: +1.940.725.0011
 1148 Triple Crown Court Fax: +1.940.725.0012
 Bartonville, TX 76226, USA Mobile: +1.469.556.9450
 
 Professional Oracle WebLogic Server
 by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and 
 Paul Done Book Home Page: http://www.wrox.com/ Kindle Version: 
 http://www.amazon.com/
 
 
 -Original Message-
 From: Martin Gainty [mailto:mgai...@hotmail.com]
 Sent: Sunday, December 29, 2013 7:25 PM
 To: Maven Developers List
 Subject: RE: Plugin phase awareness...
 
 
 
 
 
  From: mgai...@hotmail.com
  To: dev@maven.apache.org
  Subject: RE: Plugin phase awareness...
  Date: Sun, 29 Dec 2013 17:46:29 -0500
  
  
  
  
  
  
   Date: Sun, 29 Dec 2013 15:13:12 +
   Subject: Re: Plugin phase awareness...
   From: stephen.alan.conno...@gmail.com
   To: dev@maven.apache.org
   
   Are you running the mojo directly in your testing by any chance?
   
   Eg
   
   mvn short-name:goal
  MGCorrect I was testing in this fashion
  
   As opposed to
   
   mvn phase
  MGThanks Stephen I will try this out
 MG_12_29_2013
 /**
 * @parameter expression=${mojoExecution}
 */
 @Parameter(defaultValue = ${mojoExecution}) private 
 org.apache.maven.plugin.MojoExecution execution; //supposedly mojoExecution 
 injected here public org.apache.maven.plugin.MojoExecution getExecution() { 
 return execution; } //accessor for execution
 /**
 * @parameter expression=${mojoExecution.lifecyclePhase}
 */
 @Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
 private String lifecyclePhase; //supposedly lifecyclePhase is injected here
 public org.apache.maven.model.Plugin plugin=new 
 org.apache.maven.model.Plugin();
 public String getLifecyclePhase() { //accessor for lifecyclePhase
 if(lifecyclePhase==null) {
 plugin.setGroupId(org.apache.maven.plugins);
 plugin.setArtifactId(maven-compiler-plugin);
 plugin.setVersion(3.1);
 String goal=compile;
 String executionId=executionId;
 System.out.println(CompilerMojoTestCase::getLifecyclePhase goal=+goal+ 
 executionId=+executionId);
 org.apache.maven.plugin.MojoExecution mojo=new 
 org.apache.maven.plugin.MojoExecution((org.apache.maven.model.Plugin)plugin, 
 goal

RE: Plugin phase awareness...

[Martin Gainty]

Morning All-

 

Even after downloading maven-core 3.1.1 source and re-compiling to new 
maven-core-3.1.1.jar distro
and forcing maven-core-3.1.1 dependency into maven-surefire-plugin

 
I could not get ${mojoExecution.lifecyclePhase} to display anything other than 
null


https://jira.codehaus.org/browse/MNG-

 

Ideas?

Martin --
__ 


Inte förändra och störa denna överföring

  





From: mgai...@hotmail.com
To: dev@maven.apache.org
Subject: RE: Plugin phase awareness...
Date: Wed, 25 Dec 2013 22:40:07 -0500




Wasted an enormous amount of time chasing the exact location of .git file.. i 
guess its a good thing it was Christmas

Thanks Jason!
Martin Gainty 
__ 


  


 From: jpye...@pdinc.us
 To: dev@maven.apache.org
 Subject: RE: Plugin phase awareness...
 Date: Wed, 25 Dec 2013 10:52:34 -0500
 
  -Original Message-
  From: Martin Gainty 
  Sent: Wednesday, December 25, 2013 10:40
  
  bashgit clone 
  bashhttps://github.com/apache/maven/blob/maven-3.1.1/maven-core src
  Cloning into 'src'...
  fatal: repository 
  'https://github.com/apache/maven/blob/maven-3.1.1/maven-core/'
  not found
 
 It is not like subversion, git clone https://github.com/apache/maven.git
 
 The git operation will have to happen from the root of the repository, and git
 hub does not auto redirect git clones to the proper url from the repo browser
 urls.
 
  
  
  
  
   Date: Tue, 24 Dec 2013 18:51:59 -0500
   From: i...@ifedorenko.com
   To: dev@maven.apache.org
   Subject: Re: Plugin phase awareness...
   
   
  https://github.com/apache/maven/blob/maven-3.1.1/maven-core/src/main/j
   ava/org/apache/maven/plugin/MojoExecution.java#L160
   
   
   ... and, like I said, the example I pasted elsewhere in this thread 
   does work in maven 3.0.5 and 3.1.1.
   
   --
   Regards,
   Igor
   
   On 12/24/2013, 18:01, Martin Gainty wrote:
not found in 3.1.1
   
   
   
${user.home}\org\apache\maven\maven-core\3.1.1\jarjavap .\or 
g\apache\maven\plugin\MojoExecution | grep lifecyclePhase
   
   
Warning: Binary file .\org\apache\maven\plugin\MojoExecution 
contains org.apache.maven.plugin.MojoExecution
   
   
I have 3.1.1 fully operational but I cannt locate the 
  lifecyclePhase 
in MojoExecution
   
I *thought* 3.1.1 was latest...does anyone know where the 
  lifecyclePhase attribute is located?
   
   
   
Thanks!
Martin
   
__
God jul till alla och
   
   
   
   
   
   
   
From: mgai...@hotmail.com
To: dev@maven.apache.org
Subject: RE: Plugin phase awareness...
Date: Tue, 24 Dec 2013 08:01:01 -0500
   
mvn version 3.0.2
   
   
   
public class CompilerMojo extends AbstractCompilerMojo
   
{
   
/**
* @parameter expression=${mojoExecution}
*/
@Parameter(defaultValue = ${mojoExecution}) private 
org.apache.maven.plugin.MojoExecution execution; public 
org.apache.maven.plugin.MojoExecution getExecution() { return 
execution; }
   
   
   
/**
* @parameter expression=${mojoExecution.lifecyclePhase}
*/
@Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
private String executionPhase;
public String getExecutionPhase() { return executionPhase; }
   
   
public void execute() throws MojoExecutionException, 
CompilationFailureException { 
  getLog().info(CompilerMojo::execute 
LINE 135 Current Execution is +getExecution()); 
getLog().info(CompilerMojo::execute LINE 136 Current Execution 
phase is +getExecutionPhase()); ...
   
}
   
..
   
}
   
[info] CompilerMojo::execute LINE 135 Current Execution is null 
[info] CompilerMojo::execute LINE 136 Current Execution phase is 
null
   
   
i cant seem to get this to work in 3.0.2...let me try 3.11
   
   
   
thanks,
Martin
   
   
   
   
   
Date: Tue, 24 Dec 2013 02:53:06 +0100
Subject: Re: Plugin phase awareness...
From: lennart.jore...@gmail.com
To: dev@maven.apache.org
   
Try just injecting the mojoExecution object.
Then invoke the getLifecyclePhase() method in it.
   
   
2013/12/24 Martin Gainty mgai...@hotmail.com
   
Igor/Tamas
a quick test
   
package org.apache.maven.plugin;
public class CompilerMojo extends AbstractCompilerMojo { 
@Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
private String executionPhase;
public String getExecutionPhase() { return executionPhase; }
   
   
public void execute() throws MojoExecutionException, 
CompilationFailureException { 
getLog().info(CompilerMojo::execute LINE 136 Current phase is 
+getExecutionPhase()); 
   
}
   
}
[info] CompilerMojo::execute LINE 136 Current phase is null
   
   
   
does this work in all versions of maven...if not which 
  versions 
can i implement

RE: Plugin phase awareness...

[Martin Gainty]

  


 Date: Sun, 29 Dec 2013 15:13:12 +
 Subject: Re: Plugin phase awareness...
 From: stephen.alan.conno...@gmail.com
 To: dev@maven.apache.org
 
 Are you running the mojo directly in your testing by any chance?
 
 Eg
 
 mvn short-name:goal
MGCorrect I was testing in this fashion
 
 As opposed to
 
 mvn phase
MGThanks Stephen I will try this out
 
 Because if the former, then the phase is null as the execution was not
 bound to a phase.
 
 I have not used this specific property before, so cannot speak to whether
 it works when bound to a phase, but if your test plugin execution is not
 bound to a phase then you would not expect to see a non null value
 
 On Sunday, 29 December 2013, Martin Gainty wrote:
 
  Morning All-
 
 
 
  Even after downloading maven-core 3.1.1 source and re-compiling to new
  maven-core-3.1.1.jar distro
  and forcing maven-core-3.1.1 dependency into maven-surefire-plugin
 
 
  I could not get ${mojoExecution.lifecyclePhase} to display anything other
  than null
 
 
  https://jira.codehaus.org/browse/MNG-
 
 
 
  Ideas?
 
  Martin --
  __
 
 
  Inte förändra och störa denna överföring
 
 
 
 
 
 
 
  From: mgai...@hotmail.com javascript:;
  To: dev@maven.apache.org javascript:;
  Subject: RE: Plugin phase awareness...
  Date: Wed, 25 Dec 2013 22:40:07 -0500
 
 
 
 
  Wasted an enormous amount of time chasing the exact location of .git
  file.. i guess its a good thing it was Christmas
 
  Thanks Jason!
  Martin Gainty
  __
 
 
 
 
 
   From: jpye...@pdinc.us
   To: dev@maven.apache.org
   Subject: RE: Plugin phase awareness...
   Date: Wed, 25 Dec 2013 10:52:34 -0500
  
-Original Message-
From: Martin Gainty
Sent: Wednesday, December 25, 2013 10:40
   
bashgit clone
bashhttps://github.com/apache/maven/blob/maven-3.1.1/maven-core src
Cloning into 'src'...
fatal: repository
'https://github.com/apache/maven/blob/maven-3.1.1/maven-core/'
not found
  
   It is not like subversion, git clone https://github.com/apache/maven.git
  
   The git operation will have to happen from the root of the repository,
  and git
   hub does not auto redirect git clones to the proper url from the repo
  browser
   urls.
  
   
   
   
   
 Date: Tue, 24 Dec 2013 18:51:59 -0500
 From: i...@ifedorenko.com
 To: dev@maven.apache.org
 Subject: Re: Plugin phase awareness...


https://github.com/apache/maven/blob/maven-3.1.1/maven-core/src/main/j
 ava/org/apache/maven/plugin/MojoExecution.java#L160


 ... and, like I said, the example I pasted elsewhere in this thread
 does work in maven 3.0.5 and 3.1.1.

 --
 Regards,
 Igor

 On 12/24/2013, 18:01, Martin Gainty wrote:
  not found in 3.1.1
 
 
 
  ${user.home}\org\apache\maven\maven-core\3.1.1\jarjavap .\or
  g\apache\maven\plugin\MojoExecution | grep lifecyclePhase
 
 
  Warning: Binary file .\org\apache\maven\plugin\MojoExecution
  contains org.apache.maven.plugin.MojoExecution
 
 
  I have 3.1.1 fully operational but I cannt locate the
lifecyclePhase
  in MojoExecution
 
  I *thought* 3.1.1 was latest...does anyone know where the
lifecyclePhase attribute is located?
 
 
 
  Thanks!
  Martin
 
  __
  God jul till alla och
 
 
 
 
 
 
 
  From: mgai...@hotmail.com
  To: dev@maven.apache.org
  Subject: RE: Plugin phase awareness...
  Date: Tue, 24 Dec 2013 08:01:01 -0500
 
  mvn version 3.0.2
 
 
 
  public class CompilerMojo extends AbstractCompilerMojo
 
  {
 
  /**
  * @parameter expression=${mojoExecution}
  */
  @Pa
 
 
 
 -- 
 Sent from my phone
  

RE: Plugin phase awareness...

[Martin Gainty]

  


 From: mgai...@hotmail.com
 To: dev@maven.apache.org
 Subject: RE: Plugin phase awareness...
 Date: Sun, 29 Dec 2013 17:46:29 -0500
 
 
 
 
 
 
  Date: Sun, 29 Dec 2013 15:13:12 +
  Subject: Re: Plugin phase awareness...
  From: stephen.alan.conno...@gmail.com
  To: dev@maven.apache.org
  
  Are you running the mojo directly in your testing by any chance?
  
  Eg
  
  mvn short-name:goal
 MGCorrect I was testing in this fashion
 
  As opposed to
  
  mvn phase
 MGThanks Stephen I will try this out
MG_12_29_2013
 /**
  * @parameter expression=${mojoExecution}
  */
 @Parameter(defaultValue = ${mojoExecution})
 private org.apache.maven.plugin.MojoExecution execution; //supposedly 
mojoExecution injected here
 public org.apache.maven.plugin.MojoExecution getExecution() { return 
execution; } //accessor for execution
 /**
  * @parameter expression=${mojoExecution.lifecyclePhase}
  */
@Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
private String lifecyclePhase; //supposedly lifecyclePhase is injected here
public org.apache.maven.model.Plugin plugin=new 
org.apache.maven.model.Plugin();
public String getLifecyclePhase() { //accessor for lifecyclePhase
   if(lifecyclePhase==null) {
plugin.setGroupId(org.apache.maven.plugins);
plugin.setArtifactId(maven-compiler-plugin);
plugin.setVersion(3.1);
String goal=compile;
String executionId=executionId;
System.out.println(CompilerMojoTestCase::getLifecyclePhase 
goal=+goal+ executionId=+executionId);
org.apache.maven.plugin.MojoExecution mojo=new 
org.apache.maven.plugin.MojoExecution((org.apache.maven.model.Plugin)plugin, 
goal, executionId );
lifecyclePhase= mojo.getLifecyclePhase();
   }
  return lifecyclePhase;
 }

MG_12_29_2013public void testCompilerBasic() throws Exception {
  System.out.println(CompilerMojoTestCase::testCompilerBasic LINE 143 
getLifeyclePhase()= +getLifecyclePhase());

MG_12_29_2013mvn -e -X -o process-test-classes 1 errors.lst
MG_12_29_2013CompilerMojoTestCase::getLifecyclePhase goal=compile 
executionId=executionId
MG_12_29_2013CompilerMojoTestCase::testCompilerBasic LINE 143 
getLifeyclePhase()= null

MG_12_29_2013My thinking is that lifecyclePhase is somehow not being injected..
MG_12_29_2013Ideas?
 
  Because if the former, then the phase is null as the execution was not
  bound to a phase.
  
  I have not used this specific property before, so cannot speak to whether
  it works when bound to a phase, but if your test plugin execution is not
  bound to a phase then you would not expect to see a non null value
  
  On Sunday, 29 December 2013, Martin Gainty wrote:
  
   Morning All-
  
  
  
   Even after downloading maven-core 3.1.1 source and re-compiling to new
   maven-core-3.1.1.jar distro
   and forcing maven-core-3.1.1 dependency into maven-surefire-plugin
  
  
   I could not get ${mojoExecution.lifecyclePhase} to display anything other
   than null
  
  
   https://jira.codehaus.org/browse/MNG-
  
  
  
   Ideas?
  
   Martin --
   __
  
  
   Inte förändra och störa denna överföring
  
  
  
  
  
  
  
   From: mgai...@hotmail.com javascript:;
   To: dev@maven.apache.org javascript:;
   Subject: RE: Plugin phase awareness...
   Date: Wed, 25 Dec 2013 22:40:07 -0500
  
  
  
  
   Wasted an enormous amount of time chasing the exact location of .git
   file.. i guess its a good thing it was Christmas
  
   Thanks Jason!
   Martin Gainty
   __
  
  
  
  
  
From: jpye...@pdinc.us
To: dev@maven.apache.org
Subject: RE: Plugin phase awareness...
Date: Wed, 25 Dec 2013 10:52:34 -0500
   
 -Original Message-
 From: Martin Gainty
 Sent: Wednesday, December 25, 2013 10:40

 bashgit clone
 bashhttps://github.com/apache/maven/blob/maven-3.1.1/maven-core src
 Cloning into 'src'...
 fatal: repository
 'https://github.com/apache/maven/blob/maven-3.1.1/maven-core/'
 not found
   
It is not like subversion, git clone https://github.com/apache/maven.git
   
The git operation will have to happen from the root of the repository,
   and git
hub does not auto redirect git clones to the proper url from the repo
   browser
urls.
   




  Date: Tue, 24 Dec 2013 18:51:59 -0500
  From: i...@ifedorenko.com
  To: dev@maven.apache.org
  Subject: Re: Plugin phase awareness...
 
 
 https://github.com/apache/maven/blob/maven-3.1.1/maven-core/src/main/j
  ava/org/apache/maven/plugin/MojoExecution.java#L160
 
 
  ... and, like I said, the example I pasted elsewhere in this thread
  does work in maven 3.0.5 and 3.1.1.
 
  --
  Regards,
  Igor
 
  On 12/24/2013, 18:01, Martin Gainty wrote:
   not found in 3.1.1
  
  
  
   ${user.home}\org\apache\maven\maven-core\3.1.1\jarjavap

RE: Plugin phase awareness...

[Martin Gainty]

bashgit clone https://github.com/apache/maven/blob/maven-3.1.1/maven-core src
Cloning into 'src'...
fatal: repository 'https://github.com/apache/maven/blob/maven-3.1.1/maven-core/'
 not found

 

?

Martin



Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.

  


 Date: Tue, 24 Dec 2013 18:51:59 -0500
 From: i...@ifedorenko.com
 To: dev@maven.apache.org
 Subject: Re: Plugin phase awareness...
 
 https://github.com/apache/maven/blob/maven-3.1.1/maven-core/src/main/java/org/apache/maven/plugin/MojoExecution.java#L160
 
 
 ... and, like I said, the example I pasted elsewhere in this thread does
 work in maven 3.0.5 and 3.1.1.
 
 --
 Regards,
 Igor
 
 On 12/24/2013, 18:01, Martin Gainty wrote:
  not found in 3.1.1
 
 
 
  ${user.home}\org\apache\maven\maven-core\3.1.1\jarjavap .\or
  g\apache\maven\plugin\MojoExecution | grep lifecyclePhase
 
 
  Warning: Binary file .\org\apache\maven\plugin\MojoExecution contains 
  org.apache.maven.plugin.MojoExecution
 
 
  I have 3.1.1 fully operational but I cannt locate the lifecyclePhase in 
  MojoExecution
 
  I *thought* 3.1.1 was latest...does anyone know where the lifecyclePhase 
  attribute is located?
 
 
 
  Thanks!
  Martin
 
  __
  God jul till alla och
 
 
 
 
 
 
 
  From: mgai...@hotmail.com
  To: dev@maven.apache.org
  Subject: RE: Plugin phase awareness...
  Date: Tue, 24 Dec 2013 08:01:01 -0500
 
  mvn version 3.0.2
 
 
 
  public class CompilerMojo extends AbstractCompilerMojo
 
  {
 
  /**
  * @parameter expression=${mojoExecution}
  */
  @Parameter(defaultValue = ${mojoExecution})
  private org.apache.maven.plugin.MojoExecution execution;
  public org.apache.maven.plugin.MojoExecution getExecution() { return 
  execution; }
 
 
 
  /**
  * @parameter expression=${mojoExecution.lifecyclePhase}
  */
  @Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
  private String executionPhase;
  public String getExecutionPhase() { return executionPhase; }
 
 
  public void execute() throws MojoExecutionException, 
  CompilationFailureException
  {
  getLog().info(CompilerMojo::execute LINE 135 Current Execution is 
  +getExecution());
  getLog().info(CompilerMojo::execute LINE 136 Current Execution phase is 
  +getExecutionPhase());
  ...
 
  }
 
  ..
 
  }
 
  [info] CompilerMojo::execute LINE 135 Current Execution is null
  [info] CompilerMojo::execute LINE 136 Current Execution phase is null
 
 
  i cant seem to get this to work in 3.0.2...let me try 3.11
 
 
 
  thanks,
  Martin
 
 
 
 
 
  Date: Tue, 24 Dec 2013 02:53:06 +0100
  Subject: Re: Plugin phase awareness...
  From: lennart.jore...@gmail.com
  To: dev@maven.apache.org
 
  Try just injecting the mojoExecution object.
  Then invoke the getLifecyclePhase() method in it.
 
 
  2013/12/24 Martin Gainty mgai...@hotmail.com
 
  Igor/Tamas
  a quick test
 
  package org.apache.maven.plugin;
  public class CompilerMojo extends AbstractCompilerMojo
  {
  @Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
  private String executionPhase;
  public String getExecutionPhase() { return executionPhase; }
 
 
  public void execute() throws MojoExecutionException,
  CompilationFailureException
  {
  getLog().info(CompilerMojo::execute LINE 136 Current phase is
  +getExecutionPhase());
  
 
  }
 
  }
  [info] CompilerMojo::execute LINE 136 Current phase is null
 
 
 
  does this work in all versions of maven...if not which versions can i
  implement mojoExecution.lifecyclePhase
 
  ?
  Martin
  __
  Jogi és Bizalmassági kinyilatkoztatás
 
 
  Ez az üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor kérjük,
  hogy jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának
  készítése nem megengedett. Ez az üzenet csak ismeret cserét szolgál és
  semmiféle jogi alkalmazhatósága sincs. Mivel az electronikus üzenetek
  könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet 
  ezen
  üzenet tartalma miatt.
 
 
 
 
 
  From: ta...@cservenak.net
  Date: Mon, 23 Dec 2013 11:04:58 +0100
  Subject: Re: Plugin phase awareness...
  To: dev@maven.apache.org
 
  Here is an example, same as proposed by Igor
 
  https://github.com/sonatype/nexus-maven-plugins/blob/master/staging/maven-plugin/src/main/java/org/sonatype/nexus/maven/staging/AbstractStagingMojo.java#L72
 
  Still, you need to be careful if you want maven 2.x, maven 3.0.x and
  maven
  3.1.x compatibility, as some methods did change around here.
  Just skim the javadoc comments.
 
 
  HTH,
  ~t~
 
 
  On Sat, Dec 21, 2013 at 3:27 PM, Igor Fedorenko i

RE: Plugin phase awareness...

[Martin Gainty]

Wasted an enormous amount of time chasing the exact location of .git file.. i 
guess its a good thing it was Christmas

Thanks Jason!
Martin Gainty 
__ 


  


 From: jpye...@pdinc.us
 To: dev@maven.apache.org
 Subject: RE: Plugin phase awareness...
 Date: Wed, 25 Dec 2013 10:52:34 -0500
 
  -Original Message-
  From: Martin Gainty 
  Sent: Wednesday, December 25, 2013 10:40
  
  bashgit clone 
  bashhttps://github.com/apache/maven/blob/maven-3.1.1/maven-core src
  Cloning into 'src'...
  fatal: repository 
  'https://github.com/apache/maven/blob/maven-3.1.1/maven-core/'
  not found
 
 It is not like subversion, git clone https://github.com/apache/maven.git
 
 The git operation will have to happen from the root of the repository, and git
 hub does not auto redirect git clones to the proper url from the repo browser
 urls.
 
  
  
  
  
   Date: Tue, 24 Dec 2013 18:51:59 -0500
   From: i...@ifedorenko.com
   To: dev@maven.apache.org
   Subject: Re: Plugin phase awareness...
   
   
  https://github.com/apache/maven/blob/maven-3.1.1/maven-core/src/main/j
   ava/org/apache/maven/plugin/MojoExecution.java#L160
   
   
   ... and, like I said, the example I pasted elsewhere in this thread 
   does work in maven 3.0.5 and 3.1.1.
   
   --
   Regards,
   Igor
   
   On 12/24/2013, 18:01, Martin Gainty wrote:
not found in 3.1.1
   
   
   
${user.home}\org\apache\maven\maven-core\3.1.1\jarjavap .\or 
g\apache\maven\plugin\MojoExecution | grep lifecyclePhase
   
   
Warning: Binary file .\org\apache\maven\plugin\MojoExecution 
contains org.apache.maven.plugin.MojoExecution
   
   
I have 3.1.1 fully operational but I cannt locate the 
  lifecyclePhase 
in MojoExecution
   
I *thought* 3.1.1 was latest...does anyone know where the 
  lifecyclePhase attribute is located?
   
   
   
Thanks!
Martin
   
__
God jul till alla och
   
   
   
   
   
   
   
From: mgai...@hotmail.com
To: dev@maven.apache.org
Subject: RE: Plugin phase awareness...
Date: Tue, 24 Dec 2013 08:01:01 -0500
   
mvn version 3.0.2
   
   
   
public class CompilerMojo extends AbstractCompilerMojo
   
{
   
/**
* @parameter expression=${mojoExecution}
*/
@Parameter(defaultValue = ${mojoExecution}) private 
org.apache.maven.plugin.MojoExecution execution; public 
org.apache.maven.plugin.MojoExecution getExecution() { return 
execution; }
   
   
   
/**
* @parameter expression=${mojoExecution.lifecyclePhase}
*/
@Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
private String executionPhase;
public String getExecutionPhase() { return executionPhase; }
   
   
public void execute() throws MojoExecutionException, 
CompilationFailureException { 
  getLog().info(CompilerMojo::execute 
LINE 135 Current Execution is +getExecution()); 
getLog().info(CompilerMojo::execute LINE 136 Current Execution 
phase is +getExecutionPhase()); ...
   
}
   
..
   
}
   
[info] CompilerMojo::execute LINE 135 Current Execution is null 
[info] CompilerMojo::execute LINE 136 Current Execution phase is 
null
   
   
i cant seem to get this to work in 3.0.2...let me try 3.11
   
   
   
thanks,
Martin
   
   
   
   
   
Date: Tue, 24 Dec 2013 02:53:06 +0100
Subject: Re: Plugin phase awareness...
From: lennart.jore...@gmail.com
To: dev@maven.apache.org
   
Try just injecting the mojoExecution object.
Then invoke the getLifecyclePhase() method in it.
   
   
2013/12/24 Martin Gainty mgai...@hotmail.com
   
Igor/Tamas
a quick test
   
package org.apache.maven.plugin;
public class CompilerMojo extends AbstractCompilerMojo { 
@Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
private String executionPhase;
public String getExecutionPhase() { return executionPhase; }
   
   
public void execute() throws MojoExecutionException, 
CompilationFailureException { 
getLog().info(CompilerMojo::execute LINE 136 Current phase is 
+getExecutionPhase()); 
   
}
   
}
[info] CompilerMojo::execute LINE 136 Current phase is null
   
   
   
does this work in all versions of maven...if not which 
  versions 
can i implement mojoExecution.lifecyclePhase
   
?
Martin
__
Jogi és Bizalmassági kinyilatkoztatás
   
   
Ez az üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor 
kérjük, hogy jelentse azt nekünk vissza. Semmiféle továbbítása 
vagy másolatának készítése nem megengedett. Ez az üzenet csak 
ismeret cserét szolgál és semmiféle jogi 
  alkalmazhatósága sincs. 
Mivel az electronikus üzenetek könnyen 
  megváltoztathatóak, ezért 
minket semmi felelöség nem terhelhet ezen üzenet 
  tartalma miatt

RE: Plugin phase awareness...

[Martin Gainty]

mvn version 3.0.2

 

public class CompilerMojo extends AbstractCompilerMojo

{

 /**
  * @parameter expression=${mojoExecution}
  */
  @Parameter(defaultValue = ${mojoExecution})
  private org.apache.maven.plugin.MojoExecution execution;
  public org.apache.maven.plugin.MojoExecution getExecution() { return 
execution; }

 

 /**
  * @parameter expression=${mojoExecution.lifecyclePhase}
  */
@Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
private String executionPhase;
public String getExecutionPhase() { return executionPhase; }


public void execute() throws MojoExecutionException, 
CompilationFailureException
{
  getLog().info(CompilerMojo::execute LINE 135 Current Execution is 
+getExecution());
  getLog().info(CompilerMojo::execute LINE 136 Current Execution phase is 
+getExecutionPhase());
...

   }

..

}

[info] CompilerMojo::execute LINE 135 Current Execution is null
[info] CompilerMojo::execute LINE 136 Current Execution phase is null


i cant seem to get this to work in 3.0.2...let me try 3.11

 

thanks,
Martin 

  



 Date: Tue, 24 Dec 2013 02:53:06 +0100
 Subject: Re: Plugin phase awareness...
 From: lennart.jore...@gmail.com
 To: dev@maven.apache.org
 
 Try just injecting the mojoExecution object.
 Then invoke the getLifecyclePhase() method in it.
 
 
 2013/12/24 Martin Gainty mgai...@hotmail.com
 
  Igor/Tamas
  a quick test
 
  package org.apache.maven.plugin;
  public class CompilerMojo extends AbstractCompilerMojo
  {
  @Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
  private String executionPhase;
  public String getExecutionPhase() { return executionPhase; }
 
 
  public void execute() throws MojoExecutionException,
  CompilationFailureException
  {
  getLog().info(CompilerMojo::execute LINE 136 Current phase is
  +getExecutionPhase());
  
 
  }
 
  }
  [info] CompilerMojo::execute LINE 136 Current phase is null
 
 
 
  does this work in all versions of maven...if not which versions can i
  implement mojoExecution.lifecyclePhase
 
  ?
  Martin
  __
  Jogi és Bizalmassági kinyilatkoztatás
 
 
  Ez az üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor kérjük,
  hogy jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának
  készítése nem megengedett. Ez az üzenet csak ismeret cserét szolgál és
  semmiféle jogi alkalmazhatósága sincs. Mivel az electronikus üzenetek
  könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet ezen
  üzenet tartalma miatt.
 
 
 
 
 
   From: ta...@cservenak.net
   Date: Mon, 23 Dec 2013 11:04:58 +0100
   Subject: Re: Plugin phase awareness...
   To: dev@maven.apache.org
  
   Here is an example, same as proposed by Igor
  
  https://github.com/sonatype/nexus-maven-plugins/blob/master/staging/maven-plugin/src/main/java/org/sonatype/nexus/maven/staging/AbstractStagingMojo.java#L72
  
   Still, you need to be careful if you want maven 2.x, maven 3.0.x and
  maven
   3.1.x compatibility, as some methods did change around here.
   Just skim the javadoc comments.
  
  
   HTH,
   ~t~
  
  
   On Sat, Dec 21, 2013 at 3:27 PM, Igor Fedorenko i...@ifedorenko.com
  wrote:
  
Something like this should do the trick
   
@Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
private String executionPhase;
   
other magic properties available to mojos are documented in [1]
   
[1] http://maven.apache.org/ref/3.1.1/maven-core/apidocs/org/
apache/maven/plugin/PluginParameterExpressionEvaluator.html
   
--
Regards,
Igor
   
   
   
On 12/21/2013, 3:52, Lennart Jörelid wrote:
   
Hello all,
   
How can a running Mojo query the Maven API (or some other API) to
  find out
which Maven Phase it has been invoked in? Something like ...
   
String currentPhase = getSomeMavenApiHelper().getCurrentPhase();
   
--
+==+
| Bästa hälsningar,
| [sw. Best regards]
|
| Lennart Jörelid
| EAI Architect  Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: l...@jguru.se
| URL: www.jguru.se
| Phone
| (skype): jgurueurope
| (intl): +46 708 507 603
| (domestic): 0708 - 507 603
+==+
   
   
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
   
   
 
 
 
 
 
 -- 
 
 --
 +==+
 | Bästa hälsningar,
 | [sw. Best regards]
 |
 | Lennart Jörelid
 | EAI Architect  Integrator
 |
 | jGuru Europe AB
 | Mölnlycke - Kista
 |
 | Email: l...@jguru.se
 | URL: www.jguru.se
 | Phone
 | (skype): jgurueurope
 | (intl): +46 708 507 603
 | (domestic): 0708 - 507 603
 +==+
  

RE: Plugin phase awareness...

[Martin Gainty]

not found in 3.1.1

 

${user.home}\org\apache\maven\maven-core\3.1.1\jarjavap .\or
g\apache\maven\plugin\MojoExecution | grep lifecyclePhase


Warning: Binary file .\org\apache\maven\plugin\MojoExecution contains 
org.apache.maven.plugin.MojoExecution


I have 3.1.1 fully operational but I cannt locate the lifecyclePhase in 
MojoExecution

I *thought* 3.1.1 was latest...does anyone know where the lifecyclePhase 
attribute is located?

 

Thanks!
Martin

__ 
God jul till alla och



  



 From: mgai...@hotmail.com
 To: dev@maven.apache.org
 Subject: RE: Plugin phase awareness...
 Date: Tue, 24 Dec 2013 08:01:01 -0500
 
 mvn version 3.0.2
 
 
 
 public class CompilerMojo extends AbstractCompilerMojo
 
 {
 
 /**
 * @parameter expression=${mojoExecution}
 */
 @Parameter(defaultValue = ${mojoExecution})
 private org.apache.maven.plugin.MojoExecution execution;
 public org.apache.maven.plugin.MojoExecution getExecution() { return 
 execution; }
 
 
 
 /**
 * @parameter expression=${mojoExecution.lifecyclePhase}
 */
 @Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
 private String executionPhase;
 public String getExecutionPhase() { return executionPhase; }
 
 
 public void execute() throws MojoExecutionException, 
 CompilationFailureException
 {
 getLog().info(CompilerMojo::execute LINE 135 Current Execution is 
 +getExecution());
 getLog().info(CompilerMojo::execute LINE 136 Current Execution phase is 
 +getExecutionPhase());
 ...
 
 }
 
 ..
 
 }
 
 [info] CompilerMojo::execute LINE 135 Current Execution is null
 [info] CompilerMojo::execute LINE 136 Current Execution phase is null
 
 
 i cant seem to get this to work in 3.0.2...let me try 3.11
 
 
 
 thanks,
 Martin 
 
 
 
 
 
  Date: Tue, 24 Dec 2013 02:53:06 +0100
  Subject: Re: Plugin phase awareness...
  From: lennart.jore...@gmail.com
  To: dev@maven.apache.org
  
  Try just injecting the mojoExecution object.
  Then invoke the getLifecyclePhase() method in it.
  
  
  2013/12/24 Martin Gainty mgai...@hotmail.com
  
   Igor/Tamas
   a quick test
  
   package org.apache.maven.plugin;
   public class CompilerMojo extends AbstractCompilerMojo
   {
   @Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
   private String executionPhase;
   public String getExecutionPhase() { return executionPhase; }
  
  
   public void execute() throws MojoExecutionException,
   CompilationFailureException
   {
   getLog().info(CompilerMojo::execute LINE 136 Current phase is
   +getExecutionPhase());
   
  
   }
  
   }
   [info] CompilerMojo::execute LINE 136 Current phase is null
  
  
  
   does this work in all versions of maven...if not which versions can i
   implement mojoExecution.lifecyclePhase
  
   ?
   Martin
   __
   Jogi és Bizalmassági kinyilatkoztatás
  
  
   Ez az üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor kérjük,
   hogy jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának
   készítése nem megengedett. Ez az üzenet csak ismeret cserét szolgál és
   semmiféle jogi alkalmazhatósága sincs. Mivel az electronikus üzenetek
   könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet 
   ezen
   üzenet tartalma miatt.
  
  
  
  
  
From: ta...@cservenak.net
Date: Mon, 23 Dec 2013 11:04:58 +0100
Subject: Re: Plugin phase awareness...
To: dev@maven.apache.org
   
Here is an example, same as proposed by Igor
   
   https://github.com/sonatype/nexus-maven-plugins/blob/master/staging/maven-plugin/src/main/java/org/sonatype/nexus/maven/staging/AbstractStagingMojo.java#L72
   
Still, you need to be careful if you want maven 2.x, maven 3.0.x and
   maven
3.1.x compatibility, as some methods did change around here.
Just skim the javadoc comments.
   
   
HTH,
~t~
   
   
On Sat, Dec 21, 2013 at 3:27 PM, Igor Fedorenko i...@ifedorenko.com
   wrote:
   
 Something like this should do the trick

 @Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
 private String executionPhase;

 other magic properties available to mojos are documented in [1]

 [1] http://maven.apache.org/ref/3.1.1/maven-core/apidocs/org/
 apache/maven/plugin/PluginParameterExpressionEvaluator.html

 --
 Regards,
 Igor



 On 12/21/2013, 3:52, Lennart Jörelid wrote:

 Hello all,

 How can a running Mojo query the Maven API (or some other API) to
   find out
 which Maven Phase it has been invoked in? Something like ...

 String currentPhase = getSomeMavenApiHelper().getCurrentPhase();

 --
 +==+
 | Bästa hälsningar,
 | [sw. Best regards]
 |
 | Lennart Jörelid
 | EAI Architect  Integrator
 |
 | jGuru Europe AB
 | Mölnlycke - Kista
 |
 | Email: l...@jguru.se
 | URL: www.jguru.se
 | Phone
 | (skype): jgurueurope

RE: Plugin phase awareness...

[Martin Gainty]

Igor/Tamas
a quick test
 
package org.apache.maven.plugin;
public class CompilerMojo extends AbstractCompilerMojo 
{
@Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
private String executionPhase;
public String getExecutionPhase() { return executionPhase; }


public void execute() throws MojoExecutionException, 
CompilationFailureException
{
  getLog().info(CompilerMojo::execute LINE 136 Current phase is 
+getExecutionPhase());


  }

}
[info] CompilerMojo::execute LINE 136 Current phase is null

 

does this work in all versions of maven...if not which versions can i implement 
mojoExecution.lifecyclePhase

?
Martin 
__ 
Jogi és Bizalmassági kinyilatkoztatás

 
Ez az üzenet bizalmas.  Ha nem ön az akinek szánva volt, akkor kérjük, hogy 
jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának készítése 
nem megengedett.  Ez az üzenet csak ismeret cserét szolgál és semmiféle jogi 
alkalmazhatósága sincs.  Mivel az electronikus üzenetek könnyen 
megváltoztathatóak, ezért minket semmi felelöség nem terhelhet ezen üzenet 
tartalma miatt.


  


 From: ta...@cservenak.net
 Date: Mon, 23 Dec 2013 11:04:58 +0100
 Subject: Re: Plugin phase awareness...
 To: dev@maven.apache.org
 
 Here is an example, same as proposed by Igor
 https://github.com/sonatype/nexus-maven-plugins/blob/master/staging/maven-plugin/src/main/java/org/sonatype/nexus/maven/staging/AbstractStagingMojo.java#L72
 
 Still, you need to be careful if you want maven 2.x, maven 3.0.x and maven
 3.1.x compatibility, as some methods did change around here.
 Just skim the javadoc comments.
 
 
 HTH,
 ~t~
 
 
 On Sat, Dec 21, 2013 at 3:27 PM, Igor Fedorenko i...@ifedorenko.com wrote:
 
  Something like this should do the trick
 
  @Parameter(defaultValue = ${mojoExecution.lifecyclePhase})
  private String executionPhase;
 
  other magic properties available to mojos are documented in [1]
 
  [1] http://maven.apache.org/ref/3.1.1/maven-core/apidocs/org/
  apache/maven/plugin/PluginParameterExpressionEvaluator.html
 
  --
  Regards,
  Igor
 
 
 
  On 12/21/2013, 3:52, Lennart Jörelid wrote:
 
  Hello all,
 
  How can a running Mojo query the Maven API (or some other API) to find out
  which Maven Phase it has been invoked in? Something like ...
 
  String currentPhase = getSomeMavenApiHelper().getCurrentPhase();
 
  --
  +==+
  | Bästa hälsningar,
  | [sw. Best regards]
  |
  | Lennart Jörelid
  | EAI Architect  Integrator
  |
  | jGuru Europe AB
  | Mölnlycke - Kista
  |
  | Email: l...@jguru.se
  | URL: www.jguru.se
  | Phone
  | (skype): jgurueurope
  | (intl): +46 708 507 603
  | (domestic): 0708 - 507 603
  +==+
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
  

RE: Plugin phase awareness...

[Martin Gainty]

bashmvn help:effective-pom | grep phase
phasesite-deploy/phase
phasepackage/phase
phasegenerate-resources/phase
phasesite/phase
phasesite-deploy/phase
phasetest/phase
phasetest-compile/phase
phasecompile/phase
phaseclean/phase
phaseinstall/phase
phaseprocess-resources/phase
phaseprocess-test-resources/phase
phasepackage/phase
phasedeploy/phase


?
Martin 
__ 


Inte förändra och störa detta meddelande


  



 Date: Sat, 21 Dec 2013 09:52:56 +0100
 Subject: Plugin phase awareness...
 From: lennart.jore...@gmail.com
 To: dev@maven.apache.org
 
 Hello all,
 
 How can a running Mojo query the Maven API (or some other API) to find out
 which Maven Phase it has been invoked in? Something like ...
 
 String currentPhase = getSomeMavenApiHelper().getCurrentPhase();
 
 --
 +==+
 | Bästa hälsningar,
 | [sw. Best regards]
 |
 | Lennart Jörelid
 | EAI Architect  Integrator
 |
 | jGuru Europe AB
 | Mölnlycke - Kista
 |
 | Email: l...@jguru.se
 | URL: www.jguru.se
 | Phone
 | (skype): jgurueurope
 | (intl): +46 708 507 603
 | (domestic): 0708 - 507 603
 +==+
  

RE: New logo?

[Martin Gainty]

   Date: Fri, 20 Dec 2013 13:01:54 -0500
 Subject: Re: New logo?
 From: manf...@simpligility.com
 To: dev@maven.apache.org
 CC: manf...@simpligility.com
 
 I would move the Raven closer to the word Maven but otherwise this looks
 good imho. Of course I am not sure if everyone would recognize it as a
 raven ..
MGFWIK:  produced jpg appears to be a recreation of Totem Pole Raven
MGHere is an example of a Totem Pole Raven
http://www.google.com/imgres?imgurl=http://store.thewolfden.ca/html/images/items/02401.jpgimgrefurl=http://store.thewolfden.ca/cgi/thewolfden/02401.htmlh=371w=324sz=48tbnid=Dbwv1S537dXgyM:tbnh=92tbnw=80zoom=1usg=__enxcgZ3IHP1U98lPSkU9h_C_4m8=docid=Gcv-5rS4I5NxBMsa=Xei=INq0UoCrM5LlsASQ94HQCgved=0CDQQ9QEwAw
MG

 manfred
MGBecause 'Apache' is a Native American Tribe ..it would make sense
MGto ensure the icon/jpg/bmp reflect Native American Theme
 
  http://people.apache.org/~stephenc/maven-logo-contest/maven-6.png
 
  http://people.apache.org/~stephenc/maven-logo-contest/maven-7.png
 
  http://people.apache.org/~stephenc/maven-logo-contest/maven-7a.png
 
  http://people.apache.org/~stephenc/maven-logo-contest/maven-7b.png
 
  All based on this:
  http://people.apache.org/~stephenc/maven-logo-contest/maven-7b-big.pngwhich
  I traced from one of the raven totems
 
  The -7 set all echo the gradient used in the Apache feather, though I
  think
  the solid colour might have more strength.
 
  I'll see if I can find another one to try tracing
 
 
  On 19 December 2013 20:35, Manfred Moser manf...@simpligility.com wrote:
 
  Thats what I had in mind. Just a stylized version that is simplified and
  with not too many details. Even maybe just a head or upper body of the
  Maven Raven ... I just had to write that.. I like it ;-)
 
  manfred
 
   Likely that would be overly complex at small resolutions, but a
  monochrome
   all black stencil version might work for small versions with the full
   colour at 200px+
  
   On Thursday, 19 December 2013, Paul Benedict wrote:
  
   I like the Raven idea -- especially if you can color the bird with
  the
   Apache feathers look.
  
  
   On Thu, Dec 19, 2013 at 12:13 PM, Manfred Moser
   manf...@simpligility.comjavascript:;
   wrote:
  
What a splendid idea! This is by far my favourite. Trailed by the
   Moose
maybe.
   
We could use a symbolized interpretation of a Raven along the lines
  of
   
   
   
  
  https://www.google.ca/search?q=raven+pacific+northwest+artespv=210es_sm=119tbm=ischtbo=usource=univsa=Xei=ATezUofzI4jyoASBnIAoved=0CC4QsAQbiw=1229bih=1083
   
   
Manfred
   
 It seems that a Raven would be better. It even rhymes with Maven,
  in
 English. They have a lot of significance to many different
  cultures,
 with themes ranging from wisdom, to good luck, to even blood
  thirsty
 birds of battle preferred by warriors. And given this cultural
 history, there exists a large corpus of artistic material to
  inspire
 or choose.

 https://www.google.com/search?tbm=ischq=raven
 http://en.wikipedia.org/wiki/Cultural_depictions_of_ravens


 On Thu, Dec 19, 2013 at 5:36 AM, Stephen Connolly
 stephen.alan.conno...@gmail.com javascript:; wrote:
 the wise owl?

 http://people.apache.org/~stephenc/maven-logo-contest/maven-5.png


  -
 To unsubscribe, e-mail:
   dev-unsubscr...@maven.apache.orgjavascript:;
 For additional commands, e-mail:
   dev-h...@maven.apache.orgjavascript:;

   
   
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
   javascript:;
For additional commands, e-mail:
   dev-h...@maven.apache.orgjavascript:;
   
   
  
  
   --
   Cheers,
   Paul
  
  
  
   --
   Sent from my phone
  
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: New logo?

[Martin Gainty]

Apache?

Totems?


When my ancestors arrived at Ellis they were reminded ..there are 
native-americans


http://indianspictures.blogspot.com/2012/01/american-native-american-photos-of.html


Worth a gander?
Martin 
__ 


  



 Date: Thu, 19 Dec 2013 23:44:00 +
 Subject: Re: New logo?
 From: stephen.alan.conno...@gmail.com
 To: dev@maven.apache.org; manf...@simpligility.com
 
 http://people.apache.org/~stephenc/maven-logo-contest/maven-6.png
 
 http://people.apache.org/~stephenc/maven-logo-contest/maven-7.png
 
 http://people.apache.org/~stephenc/maven-logo-contest/maven-7a.png
 
 http://people.apache.org/~stephenc/maven-logo-contest/maven-7b.png
 
 All based on this:
 http://people.apache.org/~stephenc/maven-logo-contest/maven-7b-big.pngwhich
 I traced from one of the raven totems
 
 The -7 set all echo the gradient used in the Apache feather, though I think
 the solid colour might have more strength.
 
 I'll see if I can find another one to try tracing
 
 
 On 19 December 2013 20:35, Manfred Moser manf...@simpligility.com wrote:
 
  Thats what I had in mind. Just a stylized version that is simplified and
  with not too many details. Even maybe just a head or upper body of the
  Maven Raven ... I just had to write that.. I like it ;-)
 
  manfred
 
   Likely that would be overly complex at small resolutions, but a
  monochrome
   all black stencil version might work for small versions with the full
   colour at 200px+
  
   On Thursday, 19 December 2013, Paul Benedict wrote:
  
   I like the Raven idea -- especially if you can color the bird with the
   Apache feathers look.
  
  
   On Thu, Dec 19, 2013 at 12:13 PM, Manfred Moser
   manf...@simpligility.comjavascript:;
   wrote:
  
What a splendid idea! This is by far my favourite. Trailed by the
   Moose
maybe.
   
We could use a symbolized interpretation of a Raven along the lines of
   
   
   
  
  https://www.google.ca/search?q=raven+pacific+northwest+artespv=210es_sm=119tbm=ischtbo=usource=univsa=Xei=ATezUofzI4jyoASBnIAoved=0CC4QsAQbiw=1229bih=1083
   
   
Manfred
   
 It seems that a Raven would be better. It even rhymes with Maven, in
 English. They have a lot of significance to many different cultures,
 with themes ranging from wisdom, to good luck, to even blood thirsty
 birds of battle preferred by warriors. And given this cultural
 history, there exists a large corpus of artistic material to inspire
 or choose.

 https://www.google.com/search?tbm=ischq=raven
 http://en.wikipedia.org/wiki/Cultural_depictions_of_ravens


 On Thu, Dec 19, 2013 at 5:36 AM, Stephen Connolly
 stephen.alan.conno...@gmail.com javascript:; wrote:
 the wise owl?

 http://people.apache.org/~stephenc/maven-logo-contest/maven-5.png


  -
 To unsubscribe, e-mail:
   dev-unsubscr...@maven.apache.orgjavascript:;
 For additional commands, e-mail:
   dev-h...@maven.apache.orgjavascript:;

   
   
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
   javascript:;
For additional commands, e-mail:
   dev-h...@maven.apache.orgjavascript:;
   
   
  
  
   --
   Cheers,
   Paul
  
  
  
   --
   Sent from my phone
  
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
  

RE: More hard problems...

[Martin Gainty]

  


 To: dev@maven.apache.org
 Subject: Re: More hard problems...
 Date: Tue, 26 Nov 2013 22:57:45 +0100
 From: e...@zusammenkunft.net
 
 Am 26.11.2013, 22:02 Uhr, schrieb Robert Scholte rfscho...@apache.org:
  In addition to this story: There's an open issue called MDEPLOY-118 
  which describes a related issue: how to release the same version for 
  different platforms?
 
 Related there is also the need for features. Larger projects typically 
 have a lot of optional dependencies but dont help to requesat a specific 
 subset. For example a Scheduler like Quartz offers a core engine but also 

MGHere are the Quartz configuration properties i have
org.quartz.scheduler.instanceName = JBossQuartzScheduler
org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 10
org.quartz.threadPool.threadPriority = 5
org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread = 
true

MGwould you know of a plugin that will update my quartz.properties
MGin org\jboss\resource\adapter\quartz\inflow
 
 EJB APIs or a Servlet manager implementation. In an ideal world the 
 project would be split into multiple artifacts, but even then there can be 
 a complexity explosion. Depending on the core scheduler feature of 
 quartz would then skip all optional dependencies (like servlet and EJB 
 API).

MGHow best to configure quartz core scheduler feature?
MGWhat would this look like?
 
 (This is similiar to the testing scope, which could be implemented as a 
 well known feature). And this also goes in line with 
 platforms/implementations: the jdk1.4 feature can depend on a 
 concurrent-backport wherees the java7 does not.
 
 Gruss
 Bernd
MGBeste Grüße
MGMartin 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Model Version 5.0.0

[Martin Gainty]

Date: Sat, 23 Nov 2013 23:47:55 -0500
 From: i...@ifedorenko.com
 To: dev@maven.apache.org
 Subject: Re: Model Version 5.0.0
 
 
 
 On 11/23/2013, 23:08, Jason van Zyl wrote:
 
  On Nov 23, 2013, at 5:44 PM, Stephen Connolly
  stephen.alan.conno...@gmail.com wrote:
 
  Before I forget, here are some of my thoughts on moving towards
  Model Version 5.0.0
 
  The pom that we build with need not be the pom that gets
  deployed... thus the pom that is built with need not be the same
  format as the pom that gets deployed.
 
 
  Can you explain why you think this is useful? To me all the
 information that is carried with the POM after deployment is
  primarily for the consumption of tools, and there are a lot of tools
  that expect more than the dependency information. Removing all other
  elements in the POM is equivalent to being massively backward
  incompatible for an API. And if the subsequent consumption after
  deployment is primarily by programs, then why does it matter what
  gets deployed. I don't really see much benefit, but will create all
  sorts of technical problems where we need multiple readers and all
  that entails and the massive number of problems this will cause
  people who have created tooling, especially IDE integration. 

MGgood point!..which reader is default? and which version of reader to use?

MGthe permutations of every reader for both format types produce daunting 
numbers

MGIgor ..can i assume your fallback  Model would be 4.0.0?
 
 The way I see it, what is deployed describes how the artifact needs to
 be consumed. This is artifact's public API, if you will, it will be
 consumed by wide range of tools that resolve dependencies from Maven
 repositories and descriptor format should be very stable. Mostly likely
 we have no choice but use (a subset of) the current 4.0.0 model version.
MGIgor..so you agree with previous paragraph?


 How the artifact is produced, on the other hand, is artifact's
 implementation detail. It is perfectly reasonable for a project to
 require minimal version of Maven, for example. Or use completely
 different format, not related to pom at all.
MGHow would new format be described?
MGHow would new format be described in archetypes?

 By separating consumption and production metadata formats, we'll be
MGHow would op migrate from 'consumption metadata format' to 'production 
metadata format'?

MGSans namespace identification (pointing to XSDs) as suggested by Paul
MGHow would the plugin know which format to implement (consumption vs 
production?)


 able to evolve production format more aggressively. For example, it
 would be nice to have Tycho-specific configuration markup inside build
 section. This is not currently possible because all poms must be
 compatible with the same model.

MGTycho is latest eclipse but dont forget Europa, Ganymede, Helios, Indigo and 
Juno..once your are done refactoring Eclipse

http://wiki.eclipse.org/Older_Versions_Of_Eclipse
MGwhat about MyEclipse which is based on Helios?
http://www.myeclipseide.com/module-htmlpages-display-pid-342.html
MGOnce Eclipse (and MyEclipse) refactorings are completed what about the 
thousand of users who use Idea or Netbeans?
MGUnless every IDE and every IDE variants are accomodated you could be 
spending 40 hours a week for months
MGat a time to refactor plugin changes to every version of every IDE...are you 
volunteering to be that refactoring resource?
 --
 Regards,
 Igor

MGRegards, Martin
 
 
 
  Only with packagingpom/packaging do we actually need things like the
  plugins section in the deployed pom, because it is a reality that for
  noo-pom packaging we just want the transitive dependencies.
 
  Now there is the extensions issue where you might be registering a
  different file type that has different rules with respect to the
  classpath... but I am unsure if we actually consider those when evaluating
  the dependency tree... and in any case, once we accept that the deployed
  pom is not the same as the pom used to build (for non-pom packaging at
  least) we can transform that dependency tree using the exact rules that
  have to be known at build time thus closing the extensions issue.
 
  For projects with packagingpom/packaging in fact we are only deploying
  smal files so perhaps we can deploy two pom files... the one that exposes
  the standard dependency stuff and then a second one that is used for build
  inheritance.
 
  My vision is thus that we deploy between 2 and three pom files for every
  project.
 
  For jar/war/ear/... we deploy:
  * a modelVersion 4.0.0 pom as .pom (only lists dependencies)
  * a modelVersion 5.0.0 pom as -v5.pom (only lists dependencies but allows
  for new scopes)
 
  For pom we deploy
  * a modelVersion 4.0.0 pom as .pom (only lists dependencies)
  * a modelVersion 5.0.0 pom as -v5.pom (only lists dependencies but allows
  for new scopes)
  * the pom itself
 
  When building a pom, your parent pom must be of a modelVersion = your
  

RE: Boy have we got a broken webpage

[Martin Gainty]

LF Standard Nix line-ending

LFCR windows line-end

unix2dos usually cures

are you're thinking of a filter to catch \n Line-endings  by maven-site

?
MG
  



 Date: Sun, 17 Nov 2013 08:20:15 -0500
 Subject: Re: Boy have we got a broken webpage
 From: bimargul...@gmail.com
 To: dev@maven.apache.org
 
 Oh! That's really clever. I wonder, though, who, when, why?
 
 On Sun, Nov 17, 2013 at 5:50 AM, sebb seb...@gmail.com wrote:
  On 16 November 2013 21:02, Hervé BOUTEMY herve.bout...@free.fr wrote:
  ouch, strange: 'r' were replaced by 'n'
 
  Perhaps a botched attempt at changing line endings from (CR) to (LF) ?
 
  I just had a look at archive content, and it does not have the problem
 
  so I just copied archive content into actual plugin documentation location:
  another reason why a svn copy on staged documentation (which was voted on) 
  is
  better than regenerating a new documentation
 
  Regards,
 
  Hervé
 
  Le samedi 16 novembre 2013 14:32:00 Benson Margulies a écrit :
  http://maven.apache.org/plugins/maven-scm-publish-plugin/examples/one-module
  -configuration.html
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Stupid Question about plugin annotations

[Martin Gainty]

looks like we need to hire you to check our code..(provided you work for free)
 
package org.apache.maven.plugins.annotations;
 
import java.lang.annotation.RetentionPolicy;
 
@Documented
@Retention( RetentionPolicy.CLASS )
@Target( { ElementType.FIELD } )
@Inherited
public @interface Parameter
 
RetentionPolicy parameters:
CLASS
Annotations are to be recorded in the class file by the compiler
 but need NOT be retained by the VM at run time.



RUNTIME
Annotations are to be recorded in the class file by the compiler and
 RETAINED by the VM at run time, so they may be read reflectively.



SOURCE
Annotations are to be discarded by the compiler. 
https://jira.codehaus.org/browse/MNG-5520
 
thanks Robert!
Martin 
__ 

 

 Date: Fri, 20 Sep 2013 00:42:59 -0700
 From: robert.patr...@oracle.com
 To: dev@maven.apache.org
 Subject: RE: Stupid Question about plugin annotations
 
 Thanks.  http://jira.codehaus.org/browse/MNG-5518 submitted with test case.
 
 
 --
 Robert Patrick robert.patr...@oracle.com
 VP, FMW Architects Team: The A-Team   
 Oracle CorporationOffice: +1.940.725.0011
 1148 Triple Crown Court   Fax: +1.940.725.0012
 Bartonville, TX 76226, USAMobile: +1.469.556.9450
 
 A-Team Chronicles Blog: http://www.ateam-oracle.com/  
 
 Professional Oracle WebLogic Server
 by Robert Patrick, Gregory Nyberg, and Philip Aston
 with Josh Bregman and Paul Done
 Book Home Page: http://www.wrox.com/
 Kindle Version: http://www.amazon.com/
 
 
 -Original Message-
 From: Anders Hammar [mailto:and...@hammar.net] 
 Sent: Friday, September 20, 2013 2:20 AM
 To: Maven Developers List
 Subject: Re: Stupid Question about plugin annotations
 
 Actually, he needs to sign up on Codehaus Xircles.
 
 /Anders
 
 
 On Fri, Sep 20, 2013 at 9:06 AM, Lennart Jörelid
 lennart.jore...@gmail.comwrote:
 
  You can sign up for a JIRA account on the JIRA welcome page.
 
  You can find the respective JIRAs on
  http://maven.apache.org/issue-tracking.html
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Lost in space with Subversion...

[Martin Gainty]

  


 Date: Sun, 15 Sep 2013 00:50:17 +0200
 Subject: Lost in space with Subversion...
 From: denn...@apache.org
 To: dev@maven.apache.org
 
 Hi,
 
 When working on improving our license header compliance I ran into a
 problem I've not encountered before: spaces in the path of a directory
 that is checked into Subversion.
 
 I am unable to update files that reside inside a directory that has
 spaces in it. I've tried from Windows and Ubuntu using both a Java
 desktop app and standard svn command line client. The error message
 complains about the spaces, which in the URL have been converted to
 %20.
 
 Has anyone ever encountered this?
 
 Here are the files in question, that needs license headers. I've
 currently excluded them from RAT in the POM, so if someone succeeds in
 checking in updated versions of them with license headers, please
 remember to remove the excludes in the POM.
 
 maven-jarsigner-plugin
 src/it/spacy path/src/main/java/Main.java
MGif its windows i would try 8.3 name for the part of the folder with spaces 
e.g.
MGsrc/it/SPACY~1/src/main/java/Main.java

 src/it/spacy path/verify.bsh
MG8.3 substitution *should* work here
MGsrc/it/SPACY~1/verify.bsh
MGnix techs remember the LF toCRLF when converting to dos 
MGunix2dos verify.bsh 
 maven-patch-plugin
 src/it/path with spaces/invoker.properties
MGsame here
MGsrc/it/SPACY~1/invoker.properties
 -- 
 Dennis Lundberg
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Plugin testing release for 3.1.1

[Martin Gainty]

Manfred

 

if there is a problem is on the Apache side you should be able to make the 
change

wheres the hangup

 

?
Martin  
__ 

  



 Date: Fri, 13 Sep 2013 00:05:23 -0400
 Subject: Plugin testing release for 3.1.1
 From: manf...@simpligility.com
 To: dev@maven.apache.org
 
 Hi!
 
 With the 3.1.1 release of Maven coming up hopefully soon I would like to
 move forward with the plugin testing harness using it as well. Jason fixed
 it to work with 3.0 and requested the repo to be moved from svn to git so
 he can release 2.2 over a month ago.
 
 It seems like nothing happen on the infra side of things. Can somebody
 take this up and get it done asap. Or could I get some sort of access
 (maybe through the committer school) to do it myself at Apache?
 
 Worst case I could of course just temporarily fork it into my namespace
 and use it in the android maven plugin but I would rather not waste my
 time on that.
 
 manfred
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: [DISCUSS] Should the Maven PMC be an example of how we want the Maven Community to behave (was Re: svn commit: r1506778 - /maven/site/trunk/content/markdown/project-roles.md)

[Martin Gainty]

 


 
 Date: Sat, 27 Jul 2013 10:53:09 +0200
 Subject: Re: [DISCUSS] Should the Maven PMC be an example of how we want the 
 Maven Community to behave (was Re: svn commit: r1506778 - 
 /maven/site/trunk/content/markdown/project-roles.md)
 From: fred.co...@gmail.com
 To: dev@maven.apache.org
 
 I have a bunch of IRL stuff to deal with at the moment, and can't even work
 on my own FOSS or proprietary code, so don't expect a fork soon.
 
 When I say broken, don't be offended, few codebases aren't broken in some
 way :-)
 
 One example of broken is my SCM url being munged from this:
 
 scm:git:git:${project.groupId}/${project.artifactId}.git
 
 To this:
 
 scm:git:git:${project.groupId}/${project.artifactId}.git/${project.artifactId}
MGset up a link#!/bin/sh
if test ${SCM}x = x; then
SCM=LN -s 
scm:git:git:${project.groupId}/${project.artifactId}.git/${project.artifactId} 
scm:git:git:${project.groupId}/${project.artifactId}.git
if test -x ${SCM}; then
 export SCM
else
  echo Error:  Set the SCM environment variable.
exit
   fi
fiifndef SCM
 SCM=${SCM}
endif

MGthen reference SCM in your maven pom.xml
 
 And all I have to say to that, other than the pain it caused me, is LOL!
 :-p OK, I can add one more thing: F*** SVN. OK, now I'm done. :-)
 
 Then there's the issue where my .ssh/config file was totally ignored unless
 I used the external provider, and so on and so forth.MGexport SSH=ssh -s -F 
 /home/fcooke/.ssh/config $1
 
 Reality check: It's a lot easier and quicker to hack in a fix for me that
 breaks everyone else, than it is to agree on and implement a solution that
 works for everyone in a backward compatible way. Hence fork. Make what I
 need happen now and not sit around waiting for agreement on how to progress
 properly.
 
 Other than a fork of my very own, I'd be VERY hesitant to trust anyone
 else's forks. For example, I don't trust Debian Maven nor Fedora Maven out
 of unjustified and paranoid fear that their patches to just use what the
 distro has for deps might be active when they shouldn't be, etc. Forks
 rarely gain traction, unless the base project is severely lacking in some
 way.
MGspecific examples?
 Fred.MGMartin
 
 On Sat, Jul 27, 2013 at 9:56 AM, Hervé BOUTEMY herve.bout...@free.frwrote:
 
  Le vendredi 26 juillet 2013 01:05:44 Fred Cooke a écrit :
   About the fork, though, I'm interested. I'm interested in why it's
   maintained and how it differs. I'm interested because I intend to fork it
   myself to fix things which would break others which I know won't change
   upstream (site and release stuff). Perhaps someone already fixed what I
   consider broken and others, perhaps, do not consider broken. Email me
   privately if need be.
  
   If the fork is just a branch (or set thereof), and not promoted as a fork
   (in a social sense), then is there really any harm? Is it being viewed
  as a
   loss of potential work done? Open source is open for a reason.
  +1
 
  in your case for example:
 
  if you make a fork to site plugin to fix it in a personal way, please don't
  hide it but show us where you fork/branch and explain how you change the
  code
  (in a Jira issue?): I'm interested to see your work and understand what
  you're
  doing, since I definitely don't understand how you find the plugin broken
  (and
  to be honest, every time I read this broken sentence, I feel aggressed).
 
  IMHO, a personal branch can be an excellent way of working with the
  community:
  I'm really interested to see you fix what I can't do because I really don't
  understand what is broken.
 
  Of course, if the difference between your branch and trunk gets big, it'll
  be
  harder to find how to converge later: but we'll see. Explaned with the
  community from start, and used to interact with the community to show how
  it
  can evolve, we can understand and define with consensus that this can be a
  real
  friendly fork = a different choice on some fundamental point. Or perhaps it
  will be the start og m-site-p 4: who knows?
 
  Regards,
 
  Hervé
 
  
   Fred.
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
  

RE: Passing information between goals

[Martin Gainty]

can anyone reach the URL?

Baptiste is it possible to repost comments for build-helper to pastebin?

http://pastebin.com/



 
 Date: Wed, 24 Jul 2013 15:20:33 +0200
 Subject: Re: Passing information between goals
 From: m...@batmat.net
 To: dev@maven.apache.org
 
 Hi,
 
 I remember doing that for build-helper. It was for many executions of the
 same mojo though, not sure how it behaves with different mojos.
 See
 http://mojo.10943.n7.nabble.com/build-helper-m-p-thread-safety-issue-td39561.htmland
 the ReserveListenerPortMojo
 
 My 2 cents.
 
 Cheers
 Le 24 juil. 2013 14:17, Stephen Connolly stephen.alan.conno...@gmail.com
 a écrit :
 
  This is generally a tad tricky.
 
  1. Because of class unloading it may not be possible to use the Hack-type
  solution of stashing the data in a Class level static field. Though that
  solution will work as long as the field uses a collection type that allows
  for GC when the MavenProject that it is caching a value for has been
  collected by GC (think of the users of Maven Embedder who's Maven process
  may be long lived and reused multiple times)
 
  2. Easiest way may just be to serialize the value into a string form and
  set a project property with a non-maven resolvable name to the string
  value. For example I do not think it is possible to have a Maven property
  start with the null character.
 
  You code will need to be defensive, and if the property (or cache value if
  you go route 1) is missing it will have to calculate the value from scratch
 
 
  On 24 July 2013 12:57, Francesco Mari mari.france...@gmail.com wrote:
 
   Hi,
  
   I wrote some MOJOs which use common data. This data depends on the
   structure of the project and can't be changed at runtime.
  
   I would like to compute this information at the beginiing of the build
   process, and re-use it in each related goal. Ideally, the first goal
  should
   compute the data, and the following ones will just use it.
  
   Which is the best option? Are there any plugins already implementing
  such a
   strategy, so I can take a look at their source code?
  
 
  

RE: Java version usage survey

[Martin Gainty]

Folks

In the states..government sector (specifically State Agencies) lag at least 5 
years behind available current releases
the specific example I provide is the app I was working on was based on JVM 1.5
the Portal was based on JVM 1.4
the end result was:
Annotations: NOPE
Generics: NOPE
EfficientGC: NOPE

The agency managers are listening to the hogwash from offshore consultants who 
say :
too expensive to upgrade to 1.7
this type of thinking is costing every taxpayer beaucoups bucks as each and 
every single tweak to the 1.4 JVM
(patches already rolled into 1.6 and improved for 1.7 and tested) take a week 
or so (to test) on 1.4

Login to ANY State agency website ..attempt to upgrade your Browser's JVM 
plugin to 1.6 or 1.7 and 
watch the fireworks!

In other words: SNAFU
Martin 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.


 Date: Tue, 16 Jul 2013 12:35:06 +0100
 Subject: Re: Java version usage survey
 From: stephen.alan.conno...@gmail.com
 To: dev@maven.apache.org
 
 Speaking as a Maven Developer...
 
 My primary development machine is OS-X.
 
 On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25
 
 I have a personal linode running 1.6.0_22, and my famous Acer Aspire One
 that has some Java 1.5 and 1.6 versions on it... but I have not turned it
 on more than twice since March 2011... most likely I will wipe it and
 reinstall some more recent linux on it which will remove the older JDK
 versions leaving it with likely a 1.6 and a 1.7.
 
 I also have a windows box sitting beside me... powered off (the Sun Ultra
 T-20's are noisy don't you know) I only turn it on when I *need* windows
 and a virtual machine will not suffice (i.e. firmware updates on Samsung
 Galaxy S... which is now only used as a game console by my son) That has
 Java 1.4-1.7 on it but it is far from current in terms of AV and patches,
 so not something I would turn on for a quick test of a release.
 
 Effectively the lowest I can test releases is Java 1.6.
 
 It would be interesting to hear what the rest of the committers have as
 their testing capability. If very few committers have access to Java 1.5
 across operating systems then I think the answer is clear... namely we
 would not be in a position to stand over a release that claims to work on
 Java 1.5, and hence moving to Java 1.6 as a baseline would seem a good idea.
 
 Tools like animal-sniffer are great to help developers who cannot set up
 the older JVMs on their development environment... but in my experience
 they are no substitute for running on the older JVM.
 
 If our test capability is basically the Windows/Java 1.5 slave and the
 *nix/Java 1.5 slave on the Apache Jenkins build server *and* we cannot keep
 that integration test suite passing *then* Java 1.5 is dead for Maven IMHO
 
 -Stephen
 
 
 On 16 July 2013 11:58, Robert Patrick robert.patr...@oracle.com wrote:
 
  Oracle Java 5 and 6 are EOLed but Oracle continues to support customers
  using commercial products that require them that themselves are not EOLed.
   Given that current versions of Maven support Java 5 and 6, the real
  question is how important is it for older applications that cannot support
  Java 7 to be able to use future versions of Maven?
 
  As far as I know, there is nothing from preventing Maven developers from
  using the existing versions of JDK 5/6 to build and test Maven.
 
  --
  Robert Patrick robert.patr...@oracle.com
  VP, FMW Architects Team: The A-Team
  Oracle Corporation  Office: +1.940.725.0011
  1148 Triple Crown Court Fax: +1.940.725.0012
  Bartonville, TX 76226, USA  Mobile: +1.469.556.9450
 
  Professional Oracle WebLogic Server
  by Robert Patrick, Gregory Nyberg, and Philip Aston
  with Josh Bregman and Paul Done
  Book Home Page: http://www.wrox.com/
  Kindle Version: http://www.amazon.com/
 
 
 
  -Original Message-
  From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
  Sent: Tuesday, July 16, 2013 3:47 AM
  

RE: How Maven works - definitions

[Martin Gainty]

If you want to discover how a house was built you need to talk to an Architect

The Architecture of maven is a loose Framework which constitute One of 3 
default Maven lifecycles
http://maven.apache.org/ref/3.0.5/maven-core/lifecycles.html
 
Each Maven lifecycle in turn consists of one or more phases which will allow 
multiple Modello architected plugins (spec v 4.0.0 of Modello) to be bound to 
that phase in order to execute the plugins goal for their Mojo class
http://www.maestrodev.com/better-builds-with-maven/creating-applications-with-maven/utilizing-the-build-life-cycle/
 
In order for use to  provide further clarification we would need to know which 
tasks you wish to run

HTH
Martin Gainty 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.

 
 Date: Mon, 8 Jul 2013 07:01:18 +0930
 Subject: Re: How Maven works - definitions
 From: baerr...@gmail.com
 To: dev@maven.apache.org
 
 On 8 July 2013 04:01, Mirko Friedenhagen mfriedenha...@gmail.com wrote:
  Hello,
 
  first of all, thanks for your replies. I think it would help very much
  if an introductory would be at the plugin development page[1] to get
  the big picture. Or even be repeated at the the run[2] page.
 
  Running Maven is trivial until you encounter problems or wish to
  extend stuff. I deal a lot with supporting our department (roughly 200
  developers, 150 of whom are using Maven) and I am always reiterating
  explaining the basic glossary (phase, lifecycle, goal).
 
  While the Complete reference by Sonatype is great once you know the
  basics, it is quite extensive and not every application developer
  wants or needs to delve throught it :-)
 
 I will agree the documentation could be improved.
 
 I've also said in the past that one of Maven's problems is that it
 just works for most people.
 
 Compare that to Ant where before you can build a project you must read
 the README, configure your project settings file and then try to
 build, often trouble shooting by looking at the Ant website.  This
 means the average user of Ant has picked up more stuff because they
 are forced to.
 
 In Maven only the person who is modifying the poms generally acquires
 more in depth knowledge of Maven - including terminology.
 
 Which means when someone does need to work out what went wrong there
 is a steep learning curve because it was not amortized over time.
 
 Ideas on how to fix that are welcome.
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
  

RE: Solaris package creation

[Martin Gainty]

I would suggest a plugin designed to handle OS-flavoured debian, SystemV or 
Redhat specific distros
http://mojo.codehaus.org/unix/

Ciao,
Martin 
__ 

Per favore non alterare o perturbare questa trasmissione...Grazie 

 
 From: carmella.y.carr...@ericsson.com
 To: dev@maven.apache.org
 Subject: Solaris package creation 
 Date: Fri, 21 Jun 2013 08:59:39 +
 
 
 Hi All
 
 Can you recommend the best plugin or method to use to create a Solaris .pkg 
 through maven ?
 I see there are a few methods mentioned on the web, for example using 
 unix-maven-plugin, maven -assembly-plugin with the solaris-maven-plugin or 
 using -exec, using antrun.  However none are that well documented.
 Is there a best approach in practice ?
 
 Thanks a million
 Carmella
 
  

RE: Run maven commands from Java code

[Martin Gainty]

MGElmar MGIf you believe maven-embedder lacks documentation on generating 
archetypes
MGperhaps you can gain insight into how archetypes are generated by want 
reading these URLS
MGhttp://maven.apache.org/ref/3.0.2/maven-embedder/team-list.htmlMGhttp://maven.apache.org/archetype/maven-archetype-plugin/generate-mojo.html
MGto get started on generating archetypes
MGTake a Look at how to generate the parameters using in 
maven-archetype-plugin archetypeArtifactIdString-The archetype's artifactId. 
archetypeCatalogString-The archetype catalogs to use to build a list and let 
the user choose from. It is a comma separated list of catalogs. Catalogs use 
following schemes: •'file://...' witharchetype-catalog.xml automatically 
appended when pointing to a directory
•'http://...' or 'https://...' with archetype-catalog.xml appended
•'local' which is the shortcut for 'file://~/.m2/archetype-catalog.xml'
•'remote' which is the shortcut for Maven Central repository, ie 
'http://repo1.maven.org/maven2'
•'internal' which is an internal catalog
Since 2.0-alpha-5, default value is no longerinternal,local but remote,local. 
If Maven Central repository catalog file is empty, internalcatalog is used 
instead.
Default value is: remote,local. 
archetypeGroupIdString-The archetype's groupId. 
archetypeRepositoryString-The archetype's repository. 
archetypeVersionString-The archetype's version. 
basedirFile-(no description) 
filterString2.1Applying some filter on displayed archetypes list: format 
isartifactId or groupId:artifactId. •org.apache: - displays all archetypes 
which contain org.apache in groupId
•:jee or jee - displays all archetypes which contain jee in artifactId
•org.apache:jee - displays all archetypes which contain org.apache in groupId 
AND jee in artifactId 
goalsString-Additional goals to immediately run on the project created from the 
archetype.
 
MGIf you want your user to have a user-selectable list specify catalog
MGfilter would be used to filter the presented archetypes , (jee or jdk come 
to mind)
MGgoals are another important aspect as each mojo can contain multiple actions 
(mojo)
MGinteractive would be a good idea to gain feedback from your client (but not 
if its called by embedder)I am attaching a sample archetype-catalog.xml for 
your perusal
 
MGThis sounds like quite an interesting project you are working on
MGPlease feel free to ping back for questions\comments and or advice Bedankt,
Martin
__ 
Gelieve niet veranderen of verstoren deze transmissie
  From: elm...@infosupport.com
 To: dev@maven.apache.org
 CC: jor...@infosupport.com
 Subject: Run maven commands from Java code
 Date: Mon, 13 May 2013 13:03:12 +
 
 Dear sir/madame,
 
 I'm Elmar Maan and I'm studying software engineering in Holland.
 
 I'm developing a desktop application, that can easily generate maven modules, 
 inside a Maven project.
 This will be a JavaFX application, so I need to call Maven commands from Java 
 code.
 
 This is what I've tried:
 First I tried to use the Maven library, which I found in the Maven central 
 repository. (org.apache.maven.archetype: archetype-common 2.2)
 I wanted to use the DefaultArchetypeManager the generate a project from an 
 archetype (generateProjectFromArchetype(ArchtypeRequest, request)
 
 This gave me a lot of nullpointer exceptions, because almost all the classes 
 that it uses are interfaces, which are never initialized.
 
 So after three days of struggling with the library, I had no results.
 Then I found the maven-embedder library.
 This library lets me run the maven command-line commands, like mvn 
 archetype:generate, and works just fine, but I think it's deprecated, because 
 there is no more information on the maven site.
 
 Also the library I used earlier has less or zero documentation or examples.
 
 My question is, What's the best way to call the maven archetype:generate 
 command, so I can generate archetypes from remote catalogs etc.
 Is there another library, or am i developing something that is not even 
 possible?
 
 Yours sincerely,
 
 Elmar Maan
 student
 
 e-mail: mailto:elm...@infosupport.com
 mobiel: +31 (0)652 290 928
 
 Info Support
 Kruisboog 42
 3905 TG Veenendaal
 tel: +31 (0)318 55 20 20
 fax: + 31 (0)318 55 23 55
 www.infosupport.comhttp://www.infosupport.com/
 
 
 Op dit e-mailbericht is de disclaimer van Info Support van toepassing, zie 
 http://www.infosupport.com/disclaimer