public void PermissionModeUtils(); public static String getUserMaskFor(String); } org/apache/maven/wagon/WagonConstants.class package org.apache.maven.wagon; public final synchronized class WagonConstants { public static final int UNKNOWN_PORT = -1; public static final int UNKNOWN_LENGTH = -1; public void WagonConstants(); } org/apache/maven/wagon/PathUtils.class package org.apache.maven.wagon; public synchronized class PathUtils { public void PathUtils(); public static String dirname(String); public static...

descendants, need a mechanism to find out what type has been used as a parameter * for the concrete matcher. Unfortunately, this type is lost during type erasure so we need to use reflection * to get it back, by picking out the type of a known parameter to a known method. * The catch is that, with bridging methods, this type is only visible in the class that actually implements * the expected method, so the ReflectiveTypeFinder needs to be applied to that class or a subtype. * * For example, the abstract...

class and nested interface has its own separate page. Each of these pages has three sections consisting of a class/interface description, summary tables, and detailed member descriptions: Class inheritance diagram Direct Subclasses All Known Subinterfaces All Known Implementing Classes Class/interface declaration Class/interface description Nested Class Summary Field Summary Constructor Summary Method Summary Field Detail Constructor Detail Method Detail Each summary entry contains the first sentence...