- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 18 for We (0.12 sec)
-
maven-core/src/main/java/org/apache/maven/ReactorReader.java
// There is no need to check if the build has created any outputs, see MNG-2222. boolean projectCompiledDuringThisSession = project.hasLifecyclePhase("compile") && COMPILE_PHASE_TYPES.contains(type); // Check if the project is part of the session (not filtered by -pl, -rf, etc). If so, we check
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Thu May 02 16:33:18 GMT 2024 - 21.3K bytes - Viewed (0) -
maven-core/src/site/apt/offline-mode.apt
currently wrong for execution. <<NOTE:>> Do we want to fail when we cannot bind a mojo to the lifecycle because of offline/online status? That would probably indicate that the user was trying to do something they cannot succeed at for now...so we probably
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Mar 18 00:24:53 GMT 2024 - 10.6K bytes - Viewed (0) -
maven-api-impl/src/main/java/org/apache/maven/internal/impl/model/DefaultModelInterpolator.java
// MNG-1927, MNG-2124, MNG-3355: // If the build section is present and the project directory is non-null, we should make // sure interpolation of the directories below uses translated paths. // Afterward, we'll double back and translate any paths that weren't covered during interpolation via the // code below... translatedPrefixes.add("build.directory");
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 20K bytes - Viewed (0) -
maven-compat/src/main/java/org/apache/maven/artifact/resolver/DefaultArtifactResolver.java
// The root artifact may, or may not be resolved so we need to check before we attempt to resolve. // This is often an artifact like a POM that is taken from disk and we already have hold of the // file reference. But this may be a Maven Plugin that we need to resolve from a remote repository // as well as its dependencies.
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Thu Apr 25 05:46:50 GMT 2024 - 24.8K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/execution/MavenSession.java
/** * Adapt a {@link MavenExecutionRequest} to a {@link Settings} object for use in the Maven core. * We want to make sure that what is ask for in the execution request overrides what is in the settings. * The CLI feeds into an execution request so if a particular value is present in the execution request * then we will take that over the value coming from the user settings. */
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Mar 25 10:50:01 GMT 2024 - 16.6K bytes - Viewed (0) -
maven-core/src/test/java/org/apache/maven/AbstractCoreMavenComponentTestCase.java
} return request; } // layer the creation of a project builder configuration with a request, but this will need to be // a Maven subclass because we don't want to couple maven to the project builder which we need to // separate. protected MavenSession createMavenSession(File pom) throws Exception { return createMavenSession(pom, new Properties()); }
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 11.7K bytes - Viewed (1) -
maven-core/src/main/java/org/apache/maven/DefaultMaven.java
try { validateLocalRepository(request); } catch (IOException e) { return addExceptionToResult(result, e); } // // We enter the session scope right after the MavenSession creation and before any of the // AbstractLifecycleParticipant lookups // so that @SessionScoped components can be @Injected into AbstractLifecycleParticipants.
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 27.5K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultMavenPluginManager.java
logger.debug("Loading mojo " + mojoDescriptor.getId() + " from plugin realm " + pluginRealm); } // We are forcing the use of the plugin realm for all lookups that might occur during // the lifecycle that is part of the lookup. Here we are specifically trying to keep // lookups that occur in contextualize calls in line with the right realm.
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Thu Apr 25 14:13:36 GMT 2024 - 42.5K bytes - Viewed (0) -
maven-compat/src/test/java/org/apache/maven/repository/legacy/resolver/DefaultArtifactCollectorTest.java
@BeforeEach void setUp() throws Exception { source = new Source(); projectArtifact = createArtifactSpec("project", "1.0", null); } @Test @Disabled("works, but we don't fail on cycles presently") void testCircularDependencyNotIncludingCurrentProject() throws ArtifactResolutionException, InvalidVersionSpecificationException {
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Thu Apr 25 05:46:50 GMT 2024 - 42.5K bytes - Viewed (0) -
maven-api-impl/src/main/java/org/apache/maven/internal/impl/DefaultSettingsBuilder.java
Settings effective = settingsMerger.merge(user, settingsMerger.merge(project, global, false, null), false, null); // If no repository is defined in the user/global settings, // it means that we have "old" settings (as those are new in 4.0) // so add central to the computed settings for backward compatibility. if (effective.getRepositories().isEmpty()
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 12K bytes - Viewed (0)