- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for example (0.27 sec)
-
maven-core/src/test/resources/consumer/simple/pom.xml
XML - Registered: Sun Apr 14 03:35:08 GMT 2024 - Last Modified: Tue Nov 28 17:17:10 GMT 2023 - 1.4K bytes - Viewed (0) -
.idea/encodings.xml
<file url="file://$PROJECT_DIR$/libraries/examples/browser-example/src/main/resources" charset="UTF-8" /> <file url="file://$PROJECT_DIR$/libraries/examples/js-example" charset="UTF-8" /> <file url="file://$PROJECT_DIR$/libraries/examples/js-example/src/main/kotlin" charset="UTF-8" />
XML - Registered: Fri May 03 08:18:13 GMT 2024 - Last Modified: Mon Aug 22 14:23:18 GMT 2022 - 5.9K bytes - Viewed (0) -
dbflute.xml
<property name="target.dir" value="${basedir}/target" /> <property name="branch.name" value="fess-14.13" /> <property name="mydbflute.url" value="https://github.com/lastaflute/lastaflute-example-waterfront/archive/${branch.name}.zip" /> <target name="mydbflute.check"> <condition property="mydbflute.exists"> <available file="${mydbflute.dir}" type="dir" /> </condition> </target>
XML - Registered: Mon May 06 08:04:11 GMT 2024 - Last Modified: Thu Apr 04 02:03:51 GMT 2024 - 1000 bytes - Viewed (0) -
api/maven-api-toolchain/src/main/mdo/toolchains.mdo
and match them against the toolchain requirements of the project (as configured in {@code pom.xml}): if match is found, the toolchain instance is made available to other Maven plugins.</p> <p>With {@code jdk} toolchain, for example, instead of being stuck with the JDK used to run Maven, all plugins can use the same other JDK instance without hardcoding absolute paths into the {@code pom.xml}
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)