You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tom Huybrechts (JIRA)" <ji...@codehaus.org> on 2006/12/01 10:57:41 UTC
[jira] Created: (MECLIPSE-201) add support for Import-Package in
MakeArtifactsMojo
add support for Import-Package in MakeArtifactsMojo
---------------------------------------------------
Key: MECLIPSE-201
URL: http://jira.codehaus.org/browse/MECLIPSE-201
Project: Maven 2.x Eclipse Plugin
Issue Type: New Feature
Components: PDE support
Reporter: Tom Huybrechts
When generating POMs, the plugin translates OSGi Require-Bundle dependencies into Maven dependencies.
It does not take Import-Package dependencies into account.
If there is interest in this feature, I will write a patch to add it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-201) add support for Import-Package in
MakeArtifactsMojo
Posted by "Tom Huybrechts (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-201?page=comments#action_82613 ]
Tom Huybrechts commented on MECLIPSE-201:
-----------------------------------------
When you do make-artifacts, you should have a complete Eclipse install in which each bundle's dependencies are resolved. You can examine the package wirings and map the Maven dependencies accordingly. Off course this is just a snapshot in time, but it is enough for compilation.
> add support for Import-Package in MakeArtifactsMojo
> ---------------------------------------------------
>
> Key: MECLIPSE-201
> URL: http://jira.codehaus.org/browse/MECLIPSE-201
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: PDE support
> Reporter: Tom Huybrechts
>
> When generating POMs, the plugin translates OSGi Require-Bundle dependencies into Maven dependencies.
> It does not take Import-Package dependencies into account.
> If there is interest in this feature, I will write a patch to add it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-201) add support for Import-Package in
MakeArtifactsMojo
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez updated MECLIPSE-201:
------------------------------------
Component/s: (was: PDE support)
OSGi
> add support for Import-Package in MakeArtifactsMojo
> ---------------------------------------------------
>
> Key: MECLIPSE-201
> URL: http://jira.codehaus.org/browse/MECLIPSE-201
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: OSGi
> Reporter: Tom Huybrechts
>
> When generating POMs, the plugin translates OSGi Require-Bundle dependencies into Maven dependencies.
> It does not take Import-Package dependencies into account.
> If there is interest in this feature, I will write a patch to add it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-201) add support for Import-Package in
MakeArtifactsMojo
Posted by "Tom Huybrechts (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-201?page=comments#action_82403 ]
Tom Huybrechts commented on MECLIPSE-201:
-----------------------------------------
As an example of a POM that is incorrect because of this, look at org.eclipse.equinox.registry. Its manifest has Import-Package dependencies on various OSGi packages but these are not declared as a dependency in the POM.
> add support for Import-Package in MakeArtifactsMojo
> ---------------------------------------------------
>
> Key: MECLIPSE-201
> URL: http://jira.codehaus.org/browse/MECLIPSE-201
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: PDE support
> Reporter: Tom Huybrechts
>
> When generating POMs, the plugin translates OSGi Require-Bundle dependencies into Maven dependencies.
> It does not take Import-Package dependencies into account.
> If there is interest in this feature, I will write a patch to add it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-201) add support for Import-Package in
MakeArtifactsMojo
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-201?page=comments#action_82405 ]
fabrizio giustina commented on MECLIPSE-201:
--------------------------------------------
> If there is interest in this feature, I will write a patch to add it.
how could you do that? Maven dependency model doesn't support package-level dependencies like osgi do. The only thing that could be done is scanning the whole repository to find out which jars contains such packages and guess a version.
I would be happy to support that, but at the moment I don't think it can be done, what was your idea?
> add support for Import-Package in MakeArtifactsMojo
> ---------------------------------------------------
>
> Key: MECLIPSE-201
> URL: http://jira.codehaus.org/browse/MECLIPSE-201
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: PDE support
> Reporter: Tom Huybrechts
>
> When generating POMs, the plugin translates OSGi Require-Bundle dependencies into Maven dependencies.
> It does not take Import-Package dependencies into account.
> If there is interest in this feature, I will write a patch to add it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira