You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@empire-db.apache.org by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org> on 2009/02/25 11:17:01 UTC
[jira] Created: (EMPIREDB-35) make sure our jar's are osgi
compatible
make sure our jar's are osgi compatible
---------------------------------------
Key: EMPIREDB-35
URL: https://issues.apache.org/jira/browse/EMPIREDB-35
Project: Empire-DB
Issue Type: Task
Components: Core
Reporter: Francis De Brabandere
add the needed info in the pom.xml's (see wicket)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (EMPIREDB-35) make sure our jar's are osgi
compatible
Posted by "Greg Reiser (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851531#action_12851531 ]
Greg Reiser commented on EMPIREDB-35:
-------------------------------------
I use empire-db extensively in an OSGi environment. In order to do so, I compile from source. By changing the packaging in the pom.xml to bundle and adding the following:
<build>
<plugins>
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<extensions>true</extensions>
<configuration>
<instructions>
<Export-Package>org.apache.empire.*</Export-Package>
<Private-Package></Private-Package>
<Bundle-Activator></Bundle-Activator>
</instructions>
</configuration>
</plugin>
</plugins>
</build>
Of course, to please everyone, a separate OSGi pom might be necessary or perhaps maven profiles?
> make sure our jar's are osgi compatible
> ---------------------------------------
>
> Key: EMPIREDB-35
> URL: https://issues.apache.org/jira/browse/EMPIREDB-35
> Project: Empire-DB
> Issue Type: Task
> Components: Core
> Affects Versions: empire-db-2.0.5-incubating
> Reporter: Francis De Brabandere
> Assignee: Francis De Brabandere
> Priority: Minor
>
> add the needed info in the pom.xml's (see wicket)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (EMPIREDB-35) make sure our jar's are osgi
compatible
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere updated EMPIREDB-35:
------------------------------------------
Priority: Minor (was: Major)
Affects Version/s: empire-db-2.0.5-incubating
> make sure our jar's are osgi compatible
> ---------------------------------------
>
> Key: EMPIREDB-35
> URL: https://issues.apache.org/jira/browse/EMPIREDB-35
> Project: Empire-DB
> Issue Type: Task
> Components: Core
> Affects Versions: empire-db-2.0.5-incubating
> Reporter: Francis De Brabandere
> Priority: Minor
>
> add the needed info in the pom.xml's (see wicket)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (EMPIREDB-35) make sure our jar's are osgi
compatible
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere reassigned EMPIREDB-35:
---------------------------------------------
Assignee: Francis De Brabandere
> make sure our jar's are osgi compatible
> ---------------------------------------
>
> Key: EMPIREDB-35
> URL: https://issues.apache.org/jira/browse/EMPIREDB-35
> Project: Empire-DB
> Issue Type: Task
> Components: Core
> Affects Versions: empire-db-2.0.5-incubating
> Reporter: Francis De Brabandere
> Assignee: Francis De Brabandere
> Priority: Minor
>
> add the needed info in the pom.xml's (see wicket)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (EMPIREDB-35) make sure our jar's are osgi
compatible
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere updated EMPIREDB-35:
------------------------------------------
Fix Version/s: empire-db-2.0.6-incubating
> make sure our jar's are osgi compatible
> ---------------------------------------
>
> Key: EMPIREDB-35
> URL: https://issues.apache.org/jira/browse/EMPIREDB-35
> Project: Empire-DB
> Issue Type: Task
> Components: Core
> Affects Versions: empire-db-2.0.5-incubating
> Reporter: Francis De Brabandere
> Assignee: Francis De Brabandere
> Priority: Minor
> Fix For: empire-db-2.0.6-incubating
>
>
> add the needed info in the pom.xml's (see wicket)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (EMPIREDB-35) make sure our jar's are osgi
compatible
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851610#action_12851610 ]
Francis De Brabandere commented on EMPIREDB-35:
-----------------------------------------------
Just changed the parent pom to add osgi manifest info to all jars. I actually looked at how apache wicket does this and I did not have to change the packaging to bundle for now. See "Adding OSGi metadata to existing projects without changing the packaging type" at http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
Greg could you please test the produced jars and make sure they work in your project? Do you actually need the bundle packaging? As that is more for real osgi based projects, we for now only want to support osgi.
> make sure our jar's are osgi compatible
> ---------------------------------------
>
> Key: EMPIREDB-35
> URL: https://issues.apache.org/jira/browse/EMPIREDB-35
> Project: Empire-DB
> Issue Type: Task
> Components: Core
> Affects Versions: empire-db-2.0.5-incubating
> Reporter: Francis De Brabandere
> Assignee: Francis De Brabandere
> Priority: Minor
>
> add the needed info in the pom.xml's (see wicket)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EMPIREDB-35) make sure our jar's are osgi
compatible
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere resolved EMPIREDB-35.
-------------------------------------------
Resolution: Fixed
I'm marking this as fixed, it can be reopened if needed
> make sure our jar's are osgi compatible
> ---------------------------------------
>
> Key: EMPIREDB-35
> URL: https://issues.apache.org/jira/browse/EMPIREDB-35
> Project: Empire-DB
> Issue Type: Task
> Components: Core
> Affects Versions: empire-db-2.0.5-incubating
> Reporter: Francis De Brabandere
> Assignee: Francis De Brabandere
> Priority: Minor
> Fix For: empire-db-2.0.6-incubating
>
>
> add the needed info in the pom.xml's (see wicket)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.