- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 47 for light (0.16 sec)
-
maven-core/src/test/resources/apiv4-repo/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3-javadoc.jar
*/ body { background-color: #FFFFFF; color:#000000 } /* Headings */ h1 { font-size: 145% } /* Table colors */ .TableHeadingColor { background: #CCCCFF; color:#000000 } /* Dark mauve */ .TableSubHeadingColor { background: #EEEEFF; color:#000000 } /* Light mauve */ .TableRowColor { background: #FFFFFF; color:#000000 } /* White */ /* Font used in left-hand frame lists */ .FrameTitleFont { font-size: 100%; font-family: Helvetica, Arial, sans-serif; color:#000000 } .FrameHeadingFont { font-size: 90%; font-family:...
Archive - Registered: Sun Apr 14 03:35:08 GMT 2024 - Last Modified: Sun Oct 02 08:41:25 GMT 2022 - 236.8K bytes - Viewed (0) -
maven-core/plugin-manager.txt
* Extension points that plugins might expose h3. The plugin manager may have to deal with particular actions when a plugin is * installation * activation * update * deactivation * un-installation When a plugin is installed we may want to check the license and make users agree. We may also want to unpack the given plugin in a particular location.
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jul 18 22:45:13 GMT 2022 - 12.9K bytes - Viewed (0) -
maven-artifact/src/test/java/org/apache/maven/artifact/versioning/DefaultArtifactVersionTest.java
} private void assertVersionOlder(String left, String right) { assertTrue( newArtifactVersion(left).compareTo(newArtifactVersion(right)) < 0, left + " should be older than " + right); assertTrue( newArtifactVersion(right).compareTo(newArtifactVersion(left)) > 0, right + " should be newer than " + left); }
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Wed Sep 06 08:39:32 GMT 2023 - 9.5K bytes - Viewed (0) -
maven-core/src/main/resources/META-INF/maven/extension.xml
<exportedPackage>jakarta.inject.*</exportedPackage> <exportedPackage>jakarta.annotation.*</exportedPackage> <!-- | We may potentially want to export these, but right now I'm not sure that anything Guice specific needs | to be made available to plugin authors. If we find people are getting fancy and want to take advantage of
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jan 08 10:37:09 GMT 2024 - 12.2K bytes - Viewed (0) -
maven-bom/src/site/site.xml
<options> <disableCookies/> <trackPageView/> <enableLinkTracking/> </options> </matomo> </custom> <publishDate position="right" /> <version position="right" /> <body> <breadcrumbs> <item name="Apache" href="https://www.apache.org/" /> <item name="Maven" href="https://maven.apache.org/index.html" /> <item name="Ref" href="../" />
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 24 21:16:47 GMT 2024 - 2.4K bytes - Viewed (0) -
maven-builder-support/src/test/java/org/apache/maven/building/DefaultProblemTest.java
problem = new DefaultProblem(null, null, null, Integer.MAX_VALUE, -1, null); assertEquals(Integer.MAX_VALUE, problem.getLineNumber()); // this case is not specified, might also return -1 problem = new DefaultProblem(null, null, null, Integer.MIN_VALUE, -1, null); assertEquals(Integer.MIN_VALUE, problem.getLineNumber()); } @Test void testGetColumnNumber() {
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sat Apr 15 17:24:20 GMT 2023 - 4.9K bytes - Viewed (0) -
apache-maven/src/assembly/maven/conf/settings.xml
| relies on the detection of a property, either matching a particular value for the property, | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'. | Finally, the list of active profiles can be specified directly from the command line. |
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jun 19 15:06:01 GMT 2023 - 11K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/resolver/MavenChainedWorkspaceReader.java
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 5.6K bytes - Viewed (0) -
maven-core/src/site/apt/getting-to-container-configured-mojos.apt
implementation under a different roleHint, or else replace the BasicComponentConfigurator. * Other We may need to define a new lifecycle/phase to contextualize a mojo right before it's used, and reset it's state afterward. Up to now, the approach 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,
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) -
maven-core/src/site/apt/configuration-management.apt
${maven.home} | +--- maven.properties +-----+ * Group configuration As far as properties go for an entire build the maven.properties could be placed at the top of the group but I'm not really sure how this might work. There could probably also be a directory for plugins.xml and maven.properties. * Project configuration At the project level all configuration is achieved by tweaking the POM. One of the differences between
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)