Explanation for bundleshade of org.sonatype.sisu ?
Hi,
I am currently in the process of packaging Maven 3 and all its
dependencies for Fedora. I encountered few things in org.sonatype.sisu
pom.xml that I don't entirely understand.
This is the main directory structure:
.
├── guice-bean
│ ├── guice-bean-binders
│ ├── guice-bean-containers
│ ├── guice-bean-converters
│ ├── guice-bean-inject
│ ├── guice-bean-locators
│ ├── guice-bean-reflect
│ ├── guice-bean-scanners
│ └── sisu-inject-bean
└── guice-plexus
├── guice-plexus-binders
├── guice-plexus-converters
├── guice-plexus-locators
├── guice-plexus-metadata
├── guice-plexus-scanners
├── guice-plexus-shim
└── sisu-inject-plexus
sisu-inject-bean and sisu-inject plexus seem to be bundling and shading
rest of their group respectively (plus few other libraries such as
objectweb-asm, javax.inject and some plexus parts).
What I don't understand is why was this approach used instead of
standard dependency resolution of maven (addding libraries into
dependency section or similar). For the reference I am adding part of
sisu-inject-plexus pom.xml containing settings for bundle and shade
plugin. I am guessing it might have something to do with the way bundle
plugin is used, but I'd rather know for sure.
-
build
plugins
plugin
groupIdorg.apache.felix/groupId
artifactIdmaven-bundle-plugin/artifactId
extensionstrue/extensions
configuration
excludeDependencies
!-- fragment host and external dependencies --
sisu-inject-bean,*;groupId=org.codehaus.plexus
/excludeDependencies
instructions
Bundle-SymbolicName
org.sonatype.inject.plexus
/Bundle-SymbolicName
Fragment-Host
org.sonatype.inject
/Fragment-Host
Export-Package
org.codehaus.plexus.*;-noimport:=true;-split-package:=merge-first
/Export-Package
Private-Package
META-INF.plexus,org.sonatype.guice.*,org.objectweb.asm
/Private-Package
/instructions
/configuration
/plugin
plugin
artifactIdmaven-shade-plugin/artifactId
executions
execution
phasepackage/phase
goals
goalshade/goal
/goals
configuration
artifactSet
includes
include${project.groupId}:${project.artifactId}/include
/includes
/artifactSet
relocations
relocation
patternorg.objectweb/pattern
shadedPatternorg.sonatype.guice/shadedPattern
/relocation
/relocations
filters
filter
artifact*:*/artifact
includes
includeMETA-INF/**/include
includeorg/codehaus/plexus/**/include
includeorg/sonatype/guice/plexus/**/include
includeorg/objectweb/asm/*Writer*/include
/includes
/filter
/filters
/configuration
/execution
/executions
/plugin
/plugins
/build
--
Stanislav Ochotnicky sochotni...@redhat.com
Associate Software Engineer - Base Operating Systems Brno
PGP: 71A1677C
Red Hat Inc. http://cz.redhat.com
signature.asc
Description: OpenPGP digital signature
Re: Explanation for bundleshade of org.sonatype.sisu ?
On 11 October 2010 09:15, Stanislav Ochotnicky sochotni...@redhat.comwrote:
Hi,
I am currently in the process of packaging Maven 3 and all its
dependencies for Fedora. I encountered few things in org.sonatype.sisu
pom.xml that I don't entirely understand.
you already asked this question:
http://maven.40175.n5.nabble.com/Explanation-for-bundle-shade-of-org-sonatype-sisu-td3204579.html
and received an answer:
http://maven.40175.n5.nabble.com/Re-Explanation-for-bundle-shade-of-org-sonatype-sisu-td3204596.html
it's basically an assembly of the smaller component jars into a cohesive
bundle
This is the main directory structure:
.
├── guice-bean
│ ├── guice-bean-binders
│ ├── guice-bean-containers
│ ├── guice-bean-converters
│ ├── guice-bean-inject
│ ├── guice-bean-locators
│ ├── guice-bean-reflect
│ ├── guice-bean-scanners
│ └── sisu-inject-bean
└── guice-plexus
├── guice-plexus-binders
├── guice-plexus-converters
├── guice-plexus-locators
├── guice-plexus-metadata
├── guice-plexus-scanners
├── guice-plexus-shim
└── sisu-inject-plexus
sisu-inject-bean and sisu-inject plexus seem to be bundling and shading
rest of their group respectively (plus few other libraries such as
objectweb-asm, javax.inject and some plexus parts).
What I don't understand is why was this approach used instead of
standard dependency resolution of maven (addding libraries into
dependency section or similar). For the reference I am adding part of
sisu-inject-plexus pom.xml containing settings for bundle and shade
plugin. I am guessing it might have something to do with the way bundle
plugin is used, but I'd rather know for sure.
-
build
plugins
plugin
groupIdorg.apache.felix/groupId
artifactIdmaven-bundle-plugin/artifactId
extensionstrue/extensions
configuration
excludeDependencies
!-- fragment host and external dependencies --
sisu-inject-bean,*;groupId=org.codehaus.plexus
/excludeDependencies
instructions
Bundle-SymbolicName
org.sonatype.inject.plexus
/Bundle-SymbolicName
Fragment-Host
org.sonatype.inject
/Fragment-Host
Export-Package
org.codehaus.plexus.*;-noimport:=true;-split-package:=merge-first
/Export-Package
Private-Package
META-INF.plexus,org.sonatype.guice.*,org.objectweb.asm
/Private-Package
/instructions
/configuration
/plugin
plugin
artifactIdmaven-shade-plugin/artifactId
executions
execution
phasepackage/phase
goals
goalshade/goal
/goals
configuration
artifactSet
includes
include${project.groupId}:${project.artifactId}/include
/includes
/artifactSet
relocations
relocation
patternorg.objectweb/pattern
shadedPatternorg.sonatype.guice/shadedPattern
/relocation
/relocations
filters
filter
artifact*:*/artifact
includes
includeMETA-INF/**/include
includeorg/codehaus/plexus/**/include
includeorg/sonatype/guice/plexus/**/include
includeorg/objectweb/asm/*Writer*/include
/includes
/filter
/filters
/configuration
/execution
/executions
/plugin
/plugins
/build
--
Stanislav Ochotnicky sochotni...@redhat.com
Associate Software Engineer - Base Operating Systems Brno
PGP: 71A1677C
Red Hat Inc. http://cz.redhat.com
--
Cheers, Stuart
Re: [VOTE] Release Maven Antrun plugin version 1.6
On 10/09/2010 11:05 AM, Benjamin Bentmann wrote: Paul Gier wrote: Staging site: http://maven.apache.org/plugins/maven-antrun-plugin-1.6/ Hm, both this staged site and the one from the 1.5 release are missing the menu Project Documentation in the left nav bar of the index page. This menu is visible on other pages though and I couldn't reproduce this locally, strange. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks for catching this. I have fixed the staged site. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Maven Antrun plugin version 1.6
Hi, The vote has passed with the following result: +1 (binding): Paul Gier, Vincent Siveton, Olivier Lamy, Benjamin Bentmann, Hervé Boutemy I will promote the artifacts to the central repository and continue with the release. On 10/07/2010 03:32 PM, Paul Gier wrote: Hi, We solved 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125version=16742 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11125status=1 Staging repo: https://repository.apache.org/content/repositories/maven-006/ Staging site: http://maven.apache.org/plugins/maven-antrun-plugin-1.6/ SCM Tag: http://svn.apache.org/repos/asf/maven/plugins/tags/maven-antrun-plugin-1.6/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] [x3] Release Maven Assembly Plugin version 2.2
Hi, The vote has passed with the following result: +1 (binding): John Casey, Olivier Lamy, Benjamin Bentmann, Lukas Theussl, Herve Boutemy I'll promote the artifacts. On 10/7/10 4:57 PM, John Casey wrote: Hi, NOTE: This is the third attempt to release version 2.2. The bugfix that triggered this respin is: http://jira.codehaus.org/browse/MASSEMBLY-509 We solved 93 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126version=12617 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+MASSEMBLY+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-003/ Staging site: http://maven.apache.org/plugins/maven-assembly-plugin-2.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Again, here's my +1. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.johnofalltrades.name/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Antrun Plugin 1.6 Released
The Maven team is pleased to announce the release of the Maven Antrun Plugin, version 1.6 This plugin provides the ability to run Ant tasks in a Maven build. See the plugin's site for more details: http://maven.apache.org/plugins/maven-antrun-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-antrun-plugin/artifactId version1.6/version /plugin Enjoy, -The Maven team Release Notes - Maven 2.x Antrun Plugin - Version 1.6 ** Bug * [MANTRUN-152] - Embedded task attachartifact does not work without classifier * [MANTRUN-154] - Antrun double decodes xml escapes * [MANTRUN-155] - Encoding issue with created build-main.xml ** Improvement * [MANTRUN-150] - Update site docs to reflect change to target instead of tasks - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
