bundle.xml revision ada1678a4262b208a7b87391f520a7767d25287c
<?xml version="1.0" encoding="UTF-8"?>
<!--
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
The contents of this file are subject to the terms of either the GNU
General Public License Version 2 only ("GPL") or the Common Development
and Distribution License("CDDL") (collectively, the "License"). You
may not use this file except in compliance with the License. You can
obtain a copy of the License at
or packager/legal/LICENSE.txt. See the License for the specific
language governing permissions and limitations under the License.
When distributing the software, include this License Header Notice in each
file and include the License file at packager/legal/LICENSE.txt.
GPL Classpath Exception:
Oracle designates this particular file as subject to the "Classpath"
exception as provided by Oracle in the GPL Version 2 section of the License
file that accompanied this code.
Modifications:
If applicable, add the following below the License Header, with the fields
enclosed by brackets [] replaced by your own identifying information:
"Portions Copyright [year] [name of copyright owner]"
Contributor(s):
If you wish your version of this file to be governed by only the CDDL or
only the GPL Version 2, indicate your decision by adding "[Contributor]
elects to include this software in this distribution under the [CDDL or GPL
Version 2] license." If you don't indicate a single choice of license, a
recipient has the option to distribute your version of this file under
either the CDDL, the GPL Version 2 or to extend the choice of license to
its licensees as provided above. However, if you add GPL Version 2 code
and therefore, elected the GPL Version 2 license, then the option applies
only if the new code is made subject to such option by the copyright
holder.
-->
<!--
Describes how to create the zip file for the non-OSGi ACC bundle.
Because of the way some other modules are organized, the ACC module's
transitive closure of dependencies includes modules that it will never
use at runtime. This is the case, for example, because the published
security API for programmatic login implements both the server-side and
the client-side login methods in the same class. That means that the ACC's
dependence on the security module which defines the API would seem to
create a further dependency on other, server-side-only modules. This
descriptor excludes such modules from the bundle.
-->
<assembly>
<id>bundle</id>
<formats>
<format>zip</format>
</formats>
<dependencySets useProjectArtifact="true">
<dependencySet>
<!--
N O T E
The next mapping works for the current version of the assembly
plug-in. Future versions are described as using
${artifact.artifactId} and ${artifact.extension}.
See the outputFileNameMapping topic right after this URL:
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_dependencySet
-->
<outputFileNameMapping>
${artifactId}.${extension}
</outputFileNameMapping>
<excludes>
</excludes>
</dependencySet>
</dependencySets>
<fileSets>
<fileSet>
<includes>
</includes>
</fileSet>
</fileSets>
</assembly>