Deprecated API
Contents
-
Deprecated InterfacesInterfaceDescriptionAvoid use of this type, if you need access to local repository use repository system classes instead.Avoid use of this type, if you need access to local repository use repository system session instead.use
META-INF/maven/extension.xmlto define artifacts exported by Maven core extensions.UseRuntimeInformationinstead.instead useSourcesince maven 4.0, this interface is not used anymore and is only here for compatibilityUse SLF4J directlyuseProjectBuilderinsteaduseProjectBuildingRequestinsteadAs of 3.2.2, and there is no direct replacement. This is an internal class which was not marked as such, but should have been.UseMavenRepositorySystemif needed, or maven-resolver directly, until maven 4.x api is outinstead useSourceuseToolchainsBuilderinstead
-
Deprecated ClassesClassDescriptionAvoid use of this type, if you need access to local repository use repository system session instead.Maven 3 compatability - please use
MetadataStaxReaderMaven 3 compatability - please useMetadataStaxWriterAs of 3.2.2, and there is no direct replacement. This is an internal class which was not marked as such, but should have been.instead useStringSourceinstead useUrlSourceUse MavenStaxReader insteadUse MavenStaxReader insteadUse MavenStaxWriter insteadUse MavenStaxWriter insteadsince maven 4.0, this class is now a no-op class and is only here for compatibilityUse SLF4J directlyAs of 3.0, use a specific implementation instead, e.g.NearestConflictResolverinstead useFileSourceinstead useStringSourceinstead useUrlSourceMaven 3 compatibility - please useorg.apache.maven.api.services.xml.SettingsXmlFactoryfrommaven-api-coreorSettingsStaxReaderMaven 3 compatibility - please useorg.apache.maven.api.services.xml.SettingsXmlFactoryfrommaven-api-coreorSettingsStaxWriteruseSettingsMergerinstead useDefaultToolchainsBuilderclients that do not require compatibility with Maven 3.2.3 and earlier should link toJavaToolchainImplinstead.
-
Deprecated Enum Classes
-
Deprecated Exception ClassesException ClassDescription
-
Deprecated FieldsFieldDescription
-
Deprecated MethodsMethodDescriptionWhere to send the notification to - eg email address.to be removed before 2.0 after the install/deploy plugins use the alternate methodwe want to use the artifact method only, and ensure artifact.file is set correctly.A value of
truedoes not mean that the dependency should be placed on the classpath. SeeJavaPathTypeinstead for better analysis.to be removed before 2.0 after the install/deploy plugins use the alternate methodwe want to use the artifact method only, and ensure artifact.file is set correctly.VersionRange is immutable, cloning is not useful and even more an issue against the cacheuseMETA-INF/maven/extension.xmlto define artifacts exported by Maven core and plugin extensions.useMETA-INF/maven/extension.xmlto define artifacts exported by Maven core and plugin extensions.UseFileSource.getPath()instead.UseClassRealmRequest.getParentImports()instead.If you use this method and your code is not in Maven Core, stop doing this.Since Maven 4: useMavenExecutionRequest.getProfileActivation().Since Maven 4: useMavenExecutionRequest.getProfileActivation().Since Maven 4: useMavenExecutionRequest.getProfileActivation().Since Maven 4: useMavenExecutionRequest.getProfileActivation().Since Maven 4: useMavenExecutionRequest.getProfileActivation().useMavenExecutionRequest.getTopDirectory()insteadSince Maven 4: useMavenExecutionRequest.getProjectActivation().Since Maven 4: useMavenExecutionRequest.getProfileActivation().useMavenExecutionRequest.getRootDirectory()insteadSince Maven 4: useMavenExecutionRequest.getProjectActivation().Since 3.9 there is no direct Maven2 interop offered at LRM level. See Resolver Configuration page optionaether.artifactResolver.simpleLrmInteropthat provides similar semantics. This method should be never invoked, and always returnsfalse.Since Maven 4: useMavenExecutionRequest.getProfileActivation().useMavenExecutionRequest.setTopDirectory(Path)insteadSince Maven 4: useMavenExecutionRequest.getProjectActivation().Since Maven 4: useMavenExecutionRequest.getProfileActivation().useMavenExecutionRequest.setRootDirectory(Path)insteadSince Maven 4: useMavenExecutionRequest.getProjectActivation().Since 3.9 there is no direct Maven2 interop offered at LRM level. See Resolver Configuration page optionaether.artifactResolver.simpleLrmInteropthat provides similar semantics. This method should be never invoked, and ignores parameter (value remains alwaysfalse).useMavenSession.getTopDirectory()()}since Maven 4since Maven 4since Maven 4since Maven 4since Maven 4since Maven 4since Maven 4since Maven 4since Maven 4since Maven 4since Maven 4since Maven 4since Maven 4since Maven 4since Maven 4since Maven 4since Maven 4since Maven 4org.apache.maven.model.building.DefaultModelBuilderFactory.setReportingConverter(ReportingConverter) instead useFileSource.getFile()UseModelBuilder.buildRawModel(Path, int, boolean)instead.UseModelBuildingRequest.getPomPath()instead.rawModel is never set, instead the fileModel is setUseModelBuildingRequest.setPomPath(Path)instead.setting the rawModel has no effect, instead the fileModel of phase one will be setUseModelReader.read(Path, Map)instead.UseModelLocator.locateExistingPom(Path)instead.UseModelLocator.locatePom(Path)instead.UsePathTranslator.alignToBaseDirectory(String, Path)instead.Use SLF4J directlyUse SLF4J directlyUse SLF4J directlyUse SLF4J directlyThis got added when implementing MNG-2199 and is no longer used. Commit 6cf9320942c34bc68205425ab696b1712ace9ba4 updated the way 'MavenProject' objects are initialized.This got added when implementing MNG-2199 and is no longer used. Commit 6cf9320942c34bc68205425ab696b1712ace9ba4 updated the way 'MavenProject' objects are initialized.org.apache.maven.project.interpolation.ModelInterpolator.interpolate(Model, Map<String, ?>, boolean) Please useMavenProjectHelperUse MavenProjectHelper.attachArtifact(..) instead.This method is unreliable because it does not consider other dependency properties. SeeJavaPathTypeinstead for better analysis.This method is unreliable because it does not consider other dependency properties. SeeJavaPathTypeinstead for better analysis.This method is unreliable because it does not consider other dependency properties. SeeJavaPathTypeinstead for better analysis.UseModelWriter.UseModelWriter.This got added when implementing MNG-2199 and is no longer used. Commit 6cf9320942c34bc68205425ab696b1712ace9ba4 updated the way 'MavenProject' objects are initialized.This got added when implementing MNG-2199 and is no longer used. Commit 6cf9320942c34bc68205425ab696b1712ace9ba4 updated the way 'MavenProject' objects are initialized.This method is here only for legacy uses (like UTs), nothing else should use it.org.apache.maven.repository.MetadataResolutionRequest.setRemoteRepostories(List<ArtifactRepository>) instead useFileSource.getFile()instead useStringSource.getContent()instead useUrlSource.getUrl()
-
Deprecated ConstructorsConstructorDescriptionThis ctor is present only for Plexus XML defined component compatibility, do not use it.Use
FileSource(Path)instead.the arguments are ignored. Use the no-args constructor.Rely onDefaultLifecycles(Lookup)insteadDo not use this ctor directly, inject this component instead.Should not be used in Java code.UseFileModelSource(Path)instead.UseModelBuildingException(ModelBuildingResult)instead.UseMavenBuildTimestamp(Date, Map)or extract the format and pass it toMavenBuildTimestamp(Date, String)instead.UseDebugConfigurationListener(Logger)instead.Left for binary compatibility.Left for binary compatibility.Left for binary compatibility.without passing in the system properties, the SystemPropertiesProfileActivator will not work correctly in embedded environments.useFileconstructor for pomLocationorg.apache.maven.project.InvalidProjectModelException(String, String, String, ModelValidationResult) useFileconstructor for pomLocation