- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 11 for mayBe (0.03 sec)
-
maven-core/src/main/java/org/apache/maven/lifecycle/internal/ProjectSegment.java
* into TaskSegments. This class represents the execution context of one such task segment. * </p> * <p> * Wise voices have suggested that maybe aggregators shouldn't be bound to the ordinary * lifecycle at all, in which case we wouldn't be needing this class at all ( and * ProjectBuildList.getByTaskSegments). Or maybe they should be introduced in the calculation * of the execution plan instead, which seems much nicer. * </p> * <p>
Registered: Wed Jun 12 09:55:16 UTC 2024 - Last Modified: Wed Sep 06 08:39:32 UTC 2023 - 3.5K bytes - Viewed (0) -
maven-core/src/test/java/org/apache/maven/lifecycle/internal/LifecycleExecutionPlanCalculatorTest.java
session1, ProjectDependencyGraphStub.A, taskSegment2.getTasks()); assertEquals(3, executionPlan2.size()); } // Maybe also make one with LifeCycleTasks public static LifecycleExecutionPlanCalculator createExecutionPlaceCalculator( MojoDescriptorCreator mojoDescriptorCreator) throws ComponentLookupException {
Registered: Wed Jun 12 09:55:16 UTC 2024 - Last Modified: Wed Sep 06 08:39:32 UTC 2023 - 3.9K bytes - Viewed (0) -
maven-compat/src/main/java/org/apache/maven/artifact/repository/metadata/AbstractRepositoryMetadata.java
// TODO not sure that it should assume this, maybe the calls to addMetadata should pre-merge, then artifact // replaces? AbstractRepositoryMetadata repoMetadata = (AbstractRepositoryMetadata) metadata; this.metadata.merge(repoMetadata.getMetadata()); } public void merge(ArtifactMetadata metadata) { // TODO not sure that it should assume this, maybe the calls to addMetadata should pre-merge, then artifact
Registered: Wed Jun 12 09:55:16 UTC 2024 - Last Modified: Fri Apr 12 10:50:18 UTC 2024 - 7K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/lifecycle/internal/builder/Builder.java
* </p> * <strong>Note:</strong> This interface is part of work in progress and can be changed or removed without notice. */ public interface Builder { // // Be nice to whittle this down to Session, maybe add task segments to the session. The session really is // the place to store reactor related information. // void build( MavenSession session, ReactorContext reactorContext,
Registered: Wed Jun 12 09:55:16 UTC 2024 - Last Modified: Mon Mar 18 00:24:53 UTC 2024 - 2K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/lifecycle/internal/ProjectBuildList.java
private final List<ProjectSegment> items; public ProjectBuildList(List<ProjectSegment> items) { this.items = Collections.unmodifiableList(items); } // TODO Optimize; or maybe just rewrite the whole way aggregating mojos are being run. /** * Returns aProjectBuildList that contains only items for the specified taskSegment * @param taskSegment the requested task segment
Registered: Wed Jun 12 09:55:16 UTC 2024 - Last Modified: Wed Jan 10 12:55:54 UTC 2024 - 4.1K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/exception/DefaultExceptionHandler.java
project - nice little sample projects that could be run in the core as well as integration tests All Possible Errors - invalid lifecycle phase (maybe same as bad CLI param, though you were talking about embedder too) - <module> specified is not found - malformed settings - malformed POM - local repository not writable - remote repositories not available
Registered: Wed Jun 12 09:55:16 UTC 2024 - Last Modified: Thu Jun 06 10:31:03 UTC 2024 - 10.7K bytes - Viewed (0) -
maven-core/src/test/java/org/apache/maven/lifecycle/internal/stub/LifecycleExecutionPlanCalculatorStub.java
LifecyclePhaseNotFoundException, LifecycleNotFoundException, PluginVersionResolutionException { // Maybe do something ? } public MavenExecutionPlan calculateExecutionPlan( MavenSession session, MavenProject project, List<Task> tasks, boolean setup)
Registered: Wed Jun 12 09:55:16 UTC 2024 - Last Modified: Tue Jan 09 20:57:17 UTC 2024 - 12.4K bytes - Viewed (0) -
analysis/analysis-api-standalone/analysis-api-fir-standalone-base/src/org/jetbrains/kotlin/analysis/api/standalone/base/services/LLStandaloneFirElementByPsiElementChooser.kt
@Suppress("DEPRECATION_ERROR") private fun KtTypeReference.toKotlinTypeReference(): FirTypeRef { // Maybe resolve all types here to not to work with FirTypeRef directly return PsiRawFirBuilder( createEmptySession(), DummyScopeProvider, bodyBuildingMode = BodyBuildingMode.NORMAL
Registered: Wed Jun 12 09:53:16 UTC 2024 - Last Modified: Wed May 15 11:34:07 UTC 2024 - 14.2K bytes - Viewed (0) -
maven-compat/src/main/java/org/apache/maven/repository/legacy/resolver/DefaultLegacyArtifactCollector.java
} if (artifact.getVersion() == null) { // set the recommended version // TODO maybe its better to just pass the range through to retrieval and use a // transformation? ArtifactVersion version;
Registered: Wed Jun 12 09:55:16 UTC 2024 - Last Modified: Wed Sep 06 11:28:54 UTC 2023 - 36.7K bytes - Viewed (0) -
analysis/analysis-api-fir/src/org/jetbrains/kotlin/analysis/api/fir/components/KaFirResolver.kt
// TODO: Ideally, we should get the substitutor from the candidate. But it seems there is no way to get the substitutor from the // candidate, `Candidate.substitutor` is not complete. maybe we can carry over the final substitutor if it's available from // body resolve phase? val substitutor = when (fir) {
Registered: Wed Jun 12 09:53:16 UTC 2024 - Last Modified: Tue Jun 11 15:45:42 UTC 2024 - 73K bytes - Viewed (0)