jbi_framework
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>net.open-esb.core</groupId>
<artifactId>jbi_framework</artifactId>
<version>2.4.3</version>
</dependency><?xml version="1.0" encoding="UTF-8"?>
<!--
# BEGIN_HEADER - DO NOT EDIT
#
# The contents of this file are subject to the terms
# of the Common Development and Distribution License
# (the "License"). You may not use this file except
# in compliance with the License.
#
# You can obtain a copy of the license at
# https://open-esb.dev.java.net/public/CDDLv1.0.html.
# See the License for the specific language governing
# permissions and limitations under the License.
#
# When distributing Covered Code, include this CDDL
# HEADER in each file and include the License file at
# https://open-esb.dev.java.net/public/CDDLv1.0.html.
# If applicable add the following below this CDDL HEADER,
# with the fields enclosed by brackets "[]" replaced with
# your own identifying information: Portions Copyright
# [year] [name of copyright owner]
-->
<!--
# @(#)pom.xml
# Copyright 2004-2007 Sun Microsystems, Inc. All Rights Reserved.
#
# END_HEADER - DO NOT EDIT
-->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<parent>
<groupId>net.open-esb.core</groupId>
<artifactId>esb-packages</artifactId>
<version>2.4.3</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<groupId>net.open-esb.core</groupId>
<artifactId>jbi_framework</artifactId>
<name>jbi_framework</name>
<description>
In order to get around the JBI Lifecycle Classpath limitation in the
application server, a new JBI jar file is being created called
esb_jbi_framework.jar. This jar file will contain a MANIFEST.MF file that contains
Class-Path: entries that point towards the jbi_rt.jar (JBI Runtime) and
jbi_tests.jar (Scaffolding Registry et al) . This way we dont have to
combine the throwaway jbi_tests.jar with the main jbi_rt.jar later. We would
simply have to dereference it from jbi_framework.jar.
Likewise adding a new JAR to the same classpath would simply mean adding a new
entry to the ClassPath: header field.
</description>
<build>
<plugins>
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<id>${project.artifactId}-classpath-jar</id>
<phase>package</phase>
<goals><goal>run</goal></goals>
<configuration>
<tasks>
<jar destfile="${project.build.directory}/${project.artifactId}-${project.version}.jar">
<manifest>
<!--
<attribute name="Build-info" value="${buildinfo}" />
<attribute name="Notice" value="${copyright}" />
-->
<attribute name="Class-Path" value="jbi_rt.jar jbi_rt_l10n.jar xbean.jar" />
</manifest>
</jar>
</tasks>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>
Open source consumption has exploded, with estimates placing this year’s downloads at over 6.6 trillion. This reliance on open source components, now making up to 90% of the modern software application, has ushered in both unprecedented innovation and complex challenges for software supply chains.
View the Report