- Sort Score
- Result 10 results
- Languages All
Results 1 - 6 of 6 for qmove (0.16 sec)
-
maven-core/src/test/java/org/apache/maven/internal/impl/TestApi.java
assertTrue(paths.containsAll(classes)); assertTrue(paths.containsAll(modules)); // If caller wants only a classpath, JUnit shall move there. dispatched = session.resolveDependencies(coord, PathScope.TEST_COMPILE, Arrays.asList(JavaPathType.CLASSES)); classes = dispatched.get(JavaPathType.CLASSES);
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Thu Apr 25 14:13:36 GMT 2024 - 9.9K bytes - Viewed (2) -
api/maven-api-model/src/main/mdo/maven.mdo
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Apr 23 13:29:46 GMT 2024 - 115.1K bytes - Viewed (0) -
maven-artifact/src/main/java/org/apache/maven/artifact/versioning/VersionRange.java
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Wed Feb 28 07:40:37 GMT 2024 - 18.9K bytes - Viewed (0) -
maven-core/src/site/apt/offline-mode.apt
filesystem. It is not possible to determine whether a file-based location will be available except on a case-by-case basis (or a root-url by root-url basis). We may want to move the offline sensitivity entirely to Maven-Artifact, below, so we can be smarter about testing filesystem-based repositories, etc. * If not otherwise specified, all other wagons are assumed to be
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-core/src/test/resources/projects/past-model-version-pom.xml
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <project> <!-- once we move past supporting modelVersion 4.0.0 we should update this version --> <modelVersion>3.9.9</modelVersion> <groupId>tests.project</groupId> <artifactId>past-model-version</artifactId> <version>1</version>
XML - Registered: Sun Mar 31 03:35:09 GMT 2024 - Last Modified: Mon Jun 03 20:33:44 GMT 2019 - 1K bytes - Viewed (0) -
maven-core/src/site/apt/getting-to-container-configured-mojos.apt
of most plexus components has been to avoid instance state like the plague. With the current parameter passing model of mojos, this will not be possible, particularly when we move mojos to a singleton instantiation model, and then run a reactorized project...the successive calls may leave behind configuration artifacts from invocation to invocation. Maven Modifications * DefaultPluginManager
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jan 30 15:20:35 GMT 2023 - 4.1K bytes - Viewed (0)