Re: Does maven-artifact-transfer really need to use reflection ?

2015-06-14 Thread Robert Scholte
For eclipse-aether you must, because the signature of some method calls of ProjectBuildingRequest have changed. You won't be able to compile the code. Trying to do something like this won't work: Object repoSession = buildingRequest.getRepositorySession() if (isMaven31()) { // cast to eclip

Does maven-artifact-transfer really need to use reflection ?

2015-06-14 Thread Kristian Rosenvold
As long as each class is either sonatype-aether or eclipse-aether, it does not really need reflection ? K

Re: svn commit: r1685226 - in /maven/plugins/trunk/maven-assembly-plugin/src: main/java/org/apache/maven/plugin/assembly/artifact/ test/java/org/apache/maven/plugin/assembly/archive/phase/ test/java/o

2015-06-14 Thread Robert Scholte
Assumptions... http://mvnrepository.org/artifact/org.apache.maven.shared/maven-dependency-tree says enough usage. although I can't tell if it uses the (removed) tree package or the current graph package. Anyhow, since we're pushing this to 3.0 as well, I need to change the methods of org