- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 17 for structure (0.21 sec)
-
maven-compat/src/main/java/org/apache/maven/repository/MetadataGraph.java
import java.util.ArrayList; import java.util.Collection; /** * This is the main graph data structure used by the RepositorySystem to present tree and graph objects. * * */ @Deprecated public class MetadataGraph { /** all graph nodes */ Collection<MetadataGraphNode> nodes; /** entry point for tree-like structures */ MetadataGraphNode entry; public MetadataGraph(MetadataGraphNode entry) {
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Wed Sep 06 11:28:54 GMT 2023 - 2K bytes - Viewed (0) -
api/maven-api-toolchain/src/main/mdo/toolchains.mdo
<type>DOM</type> <!-- DOM for Maven 2.0.9/2.3.3 --> <description> Toolchain identification information, which will be matched against project requirements. <p>Actual content structure is completely open: each toolchain type will define its own format and semantics. <p>This is generally a properties format: {@code <name>value</name>} with predefined
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Wed Feb 07 21:28:01 GMT 2024 - 8.5K bytes - Viewed (0) -
maven-core/src/site/apt/inheritance.apt
<parent> <groupId></groupId> <artifactId></artifactId> <version></version> </parent> </project> +-----+ Extending the POM in the future In order to anticipate changes in the structure of the POM as new releases of maven occur, the maven inheritance model must be pinned against a particular modelVersion. This is required so that a change from modelVersion 4.0.0 to
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jul 18 17:22:19 GMT 2022 - 3.5K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/lifecycle/MavenExecutionPlan.java
pre-calculated execution plan that stays the same during the execution. If deciding to add mutable state to this class, it should be at least considered to separate this into a separate mutable structure. */ private final List<ExecutionPlanItem> planItem; private final Map<String, ExecutionPlanItem> lastMojoExecutionForAllPhases; final List<String> phasesInExecutionPlan;
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Wed Jan 10 12:55:54 GMT 2024 - 6.2K bytes - Viewed (0) -
maven-core/src/test/java/org/apache/maven/lifecycle/internal/stub/AboutTheStubs.html
identify which stub creates that specific piece of data. The most important stubs are: LifecycleExecutionPlanCalculatorStub ProjectDependencyGraphStub Since they define the primary structure of the project/build. The stubs define three top-level targets that are defined in LifecycleTaskSegmentCalculatorStub; clean, aggr and install. "aggr" is an aggregating task while clean and install are lifecyclephases.
HTML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Jul 02 16:47:10 GMT 2021 - 2.3K bytes - Viewed (0) -
apache-maven/src/assembly/shared/init
if [ ! -x "$JAVACMD" ] ; then echo "The java(1) command does not exist in PATH nor is JAVA_HOME set, so Apache Maven cannot be started." >&2 exit 1 fi fi # traverses directory structure from process work directory to filesystem root # first directory with .mvn subdirectory is considered project base directory find_maven_basedir() { ( basedir=`find_file_argument_basedir "$@"` wdir="$basedir"
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sat Mar 05 22:52:54 GMT 2022 - 2.3K bytes - Viewed (0) -
maven-core/src/site/apt/configuration-management.apt
<name>theme</name> <value>classic</value> </parameter> </parameters> </plugin> </plugins> +-----+ Unified source directory Unified source directory structure that is analogous to the repository itself. This way locations of intermediary artifacts of a build would be in a known location. This would also help with developer setup i.e. getting
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Mar 18 00:24:53 GMT 2024 - 5.8K bytes - Viewed (0) -
maven-compat/src/test/java/org/apache/maven/artifact/resolver/ArtifactResolverTest.java
// I want to set up a local/remote repositories for testing but I don't want to have // to change them when I change the layout of the repositories. So I want to generate // the structure I want to test by using the artifact handler manager which dictates // the layout used for a particular artifact type. /** */ @Deprecated class ArtifactResolverTest extends AbstractArtifactComponentTestCase {
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Thu Apr 25 05:46:50 GMT 2024 - 10.1K bytes - Viewed (0) -
maven-core/src/test/java/org/apache/maven/graph/DefaultProjectDependencyGraphTest.java
assertEquals(depender1, sortedProjects.get(1)); } @Test void testVerifyExpectedParentStructure() throws CycleDetectedException, DuplicateProjectException { // This test verifies the baseline structure used in subsequent tests. If this fails, the rest will fail. ProjectDependencyGraph graph = threeProjectsDependingOnASingle(); final List<MavenProject> sortedProjects = graph.getSortedProjects();
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Sep 22 06:02:04 GMT 2023 - 7.2K bytes - Viewed (0) -
maven-core/src/test/java/org/apache/maven/graph/DefaultGraphBuilderTest.java
import static org.mockito.ArgumentMatchers.anyList; import static org.mockito.Mockito.mock; import static org.mockito.Mockito.when; class DefaultGraphBuilderTest { /* The multi-module structure in this project is displayed as follows: module-parent └─── module-independent (without parent declaration) module-a module-b (depends on module-a) module-c
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Dec 05 09:23:26 GMT 2023 - 27.8K bytes - Viewed (0)