Jerome Dochez wrote:
>
> On Apr 28, 2009, at 12:15 PM, Bill Shannon wrote:
>
>> I get all kinds of warnings when I build v3. Does anyone care about
>> these?
>>
>> [WARNING] Removing: jar from forked lifecycle, to prevent recursive
>> invocation.
>>
>> What the heck does that mean? And is there a way to get rid of it?
>>
>>
>> [WARNING] Warning in manifest for
>> org.glassfish:javax.xml.soap:jar:3.0-SNAPSHOT : Superfluous
>> export-package instructions: [javax.xml.soap.*]
>> [WARNING] Warning in manifest for
>> org.glassfish:javax.xml.soap:jar:3.0-SNAPSHOT : Did not find matching
>> referal for *
> I am guessing it's coming from BND when we have a package specified in
> the osgi.bundle file that is actually not part of the module. This
> could come when folks copied that file from another project but did
> not change the osgi.bundle file correctly
I think we get these WARNINGs from all the modules where we repackage
existing artifacts to add OSGi metadata. They are not going to affect
the outcome of the build, but we should be able to get rid of the WARNINGs.
>>
>> Lots of warnings similar to the above. Do these reflect bugs?
>> Laziness?
>>
> not a bug so it has to be the other explanation :)
>>
>> [WARNING] Ignoring project type pom - supportedProjectTypes =
>> [hk2-jar, bundle]
>>
>> Isn't that a bug in some pom file?
> that seems a bit more worrisome, I think Jane should look at that.
I know why this happening. We configure maven-bundle-plugin to be active
only for hk2-jar and bundle type of projects, so it reports an error
when the plugin is attempted to be executed by maven for other project
types like pom, distribution-fragment, zip, jar, etc. We should be able
to fix this by configuring the plugin's inheritance policy. Jane, one
more on your plate.
>>
>> [WARNING] Ignoring project type distribution-fragment -
>> supportedProjectTypes = [hk2-jar, bundle]
> looks like an left over from last integration from Snezana, We moved
> away from distribution fragments all together, it's probably not
> causing a bug, but we need to fix that.
Same as above.
>
>>
>> Ditto?
>>
>>
>> [WARNING] Warning in manifest for
>> org.glassfish.external:ldapbp-repackaged:jar:3.0-SNAPSHOT :
>> Superfluous export-package instructions: [*]
>> [WARNING] Warning in manifest for
>> org.glassfish.external:ldapbp-repackaged:jar:3.0-SNAPSHOT : Did not
>> find matching referal for !com.sun.jndi.ldap
>> [WARNING] Warning in manifest for
>> org.glassfish.external:ldapbp-repackaged:jar:3.0-SNAPSHOT : Did not
>> find matching referal for !com.sun.jndi.toolkit.corba
>> [WARNING] Warning in manifest for
>> org.glassfish.external:ldapbp-repackaged:jar:3.0-SNAPSHOT : Did not
>> find matching referal for !com.sun.security.sasl.preview
>> [WARNING] Warning in manifest for
>> org.glassfish.external:ldapbp-repackaged:jar:3.0-SNAPSHOT : Did not
>> find matching referal for !com.sun.security.sasl.util
>> [WARNING] Warning in manifest for
>> org.glassfish.external:ldapbp-repackaged:jar:3.0-SNAPSHOT : Did not
>> find matching referal for *
>>
>> Aren't these all bugs?
> same as (1), we probably have osgi.bundle referencing packages which
> are not part of the module.
These are not going to affect the outcome of the build, but we should be
able to configure maven-bundle-plugin in a better way. BTW, most of the
above warnings are caused by me.
I have filed issue #8057 and shall address them sometime in near future.
Thanks for reporting them,
Sahoo
>