Download JAR files tagged by goals with all dependencies

Maven plugin for creating NetBeans modules. It defines a custom lifecycle called "nbm". During packaging, the module JAR is enhanced with NetBeans-specific manifest entries and, along with other required files, packed into a *.nbm file, ready for distribution. Additionally the plugin provides aggregator goals to create an update site or cluster for your module projects.

The Jadex GPMN (goal oriented process modeling notation) kernel provides a goal-oriented workflow kernel. The idea is that a workflow is specified as declarative goal hierarchy, which describes what has to be achieved to fulfill the workflow. At runtime goals are pursued by executing plans represented by standard BPMN workflows. The execution of goal-based workflows is achieved by conversion to BDI agents.

This is the parent module for all components of the Djenni framework - a test data generation framework that sets out to introduce better practices in test data management and generation. The core goals are: - to reduce the amount of time developers and testers spend manually crafting data - to make tests clearer by only focusing on the key data elements - to make tests even more complete by fuzzing data elements that are not deemed key to the test - to better support later test phases by helping developers to provide data generators suitable for large scale data generation in a thread safe / multi-threadable manner.

配置监控信息，在web.xml中添加 <filter> <description>拦截获取js与css过滤</description> <filter-name>MergeFilter</filter-name> <filter-class>com.njzxw.filter.MergeFilter</filter-class> <init-param> <!-- js合并输出路径 --> <param-name>jsDir</param-name> <param-value>${js.path}</param-value> </init-param> <init-param> <!-- css合并输出路径 --> <param-name>cssDir</param-name> <param-value>${css.path}</param-value> </init-param> </filter> 同时添加一个合并js\css对应一个merge.xml，最好放置在同级，如： <merge> <group name="sss" > <js path="js/common/common.js" /> <js path="js/common/index.js" /> <css path="css/common/animate.css" /> <css path="css/common/normalize.css" /> </group> </merge> 访问项目：xxx/sss.js xxx/sss.css 同时配合maven插件： compress-maven-plugin结合使用： <plugin> <groupId>com.github.eliayng</groupId> <artifactId>compress-maven-plugin</artifactId> <version>1.0.0</version> <executions> <execution> <phase>compile</phase> <goals> <goal>compress</goal> </goals> </execution> </executions> <configuration> <skip>${skipCompress}</skip> <poolNum>50</poolNum> <jsOutDir>${jsOutDir}</jsOutDir> <cssOutDir>${cssOutDir}</cssOutDir> <!--是否监控编译class文件--> <isCompressClass>true</isCompressClass> <!-- 是否复制资源文件 --> <isResourcesCopy>true</isResourcesCopy> </configuration> </plugin>

This plugin provides integration between Spring and Maven. Plugin goals support loading a Spring context XML file as part of the Maven build lifecycle. The XML file can be on the local file system or be accessible via any URL Spring's resource loading mechanism can understand. Spring's "classpath:context.xml" style notation is supported. Annotated Java classes can also be used to load a Spring context. Maven properties are injected into the Spring context (both XML and annotation style) as a java.util.Properties bean named "mavenProperties". Maven properties are also registered as a top level PropertySource so that Spring's placeholder resolution framework automatically considers them. See Project Reports -> Plugin Documentation for details on plugin goals. By default, the profile "maven" is set as an active Spring profile along with any other active Maven profiles.

Geronimo integration testsuite. This contains 2 profiles, default and child. The default profile is used by the top level suites directly under this. The child profile is used by the test poms under the suites. This pom defines the basic dependencies needed by most suites. The start-selenium, start-server, invoke, and stop-server goals are globally configured here in the pluginManagement sections. They just need to be bound in the suites where needed and appropriate. The test poms under the suites should have this pom as their parent and set their relativePath appropriately The test poms under the suites inherit an empty 'child' profile from here. But any other build executions within the test poms should all be inside a 'child' profile.