openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-1816) openjpa-2.0.1.jar does not import package 'serp.util'
Date Wed, 13 Oct 2010 20:23:32 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920749#action_12920749
] 

Donald Woods commented on OPENJPA-1816:
---------------------------------------

Are you sure you're comparing openjpa-2.0.0.jar and openjpa-2.0.1.jar?  The MANIFEST.MF files
are almost identical, except for the version changes from 2.0.0 -> 2.0.1 and the updated
JPA spec version....

Both builds set serp.*;resolution:=optional in the Import-Package.

What is your OSGi scenario?  How are you using OpenJPA in OSGi?  Are you using Apache Aries
JPA to provide the integration?  I want to understand how you are using OpenJPA with OSGi
and why you are not manually including Serp like the other optional depends....



> openjpa-2.0.1.jar does not import package 'serp.util'
> -----------------------------------------------------
>
>                 Key: OPENJPA-1816
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1816
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: osgi
>    Affects Versions: 2.0.1
>            Reporter: alex hutter
>            Assignee: Donald Woods
>
> openjpa-2.0.1.jar's MANIFEST.MF does not import the package 'serp.util'.  This makes
it unusable in an OSGi env.
> This is a regression from openjpa-2.0.0.jar.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message