You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Costin Leau (JIRA)" <ji...@apache.org> on 2007/05/15 19:14:16 UTC
[jira] Created: (FELIX-288) autodetermined import versions cannot
be changed
autodetermined import versions cannot be changed
------------------------------------------------
Key: FELIX-288
URL: https://issues.apache.org/jira/browse/FELIX-288
Project: Felix
Issue Type: Bug
Components: Maven Bundle Plugin
Reporter: Costin Leau
>From the mailing list
> Import versions
>
> The import versions are determined automatically and can't be
> overridden. For example inside Spring/OSGi, we import spring 2.0.5 and
> the resulting imports have version 2.0.
> We want to be more specific such as 2.0.5 or [2.0.5, 2.1) but whatever I
> specify as import package is completely ignored.
>
I think this is a BND issue again, will raise it with Peter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-288) autodetermined import versions cannot
be changed
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall resolved FELIX-288.
-----------------------------------
Resolution: Fixed
Assignee: Richard S. Hall
I updated BND to 140, so please close this if it is fixed. Thanks.
> autodetermined import versions cannot be changed
> ------------------------------------------------
>
> Key: FELIX-288
> URL: https://issues.apache.org/jira/browse/FELIX-288
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Reporter: Costin Leau
> Assigned To: Richard S. Hall
>
> From the mailing list
> > Import versions
> >
> > The import versions are determined automatically and can't be
> > overridden. For example inside Spring/OSGi, we import spring 2.0.5 and
> > the resulting imports have version 2.0.
> > We want to be more specific such as 2.0.5 or [2.0.5, 2.1) but whatever I
> > specify as import package is completely ignored.
> >
> I think this is a BND issue again, will raise it with Peter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-288) autodetermined import versions cannot
be changed
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496476 ]
Stuart McCulloch commented on FELIX-288:
----------------------------------------
Once the BND library has been fixed, we'll just need to update the version in the pom file to pick it up.
> autodetermined import versions cannot be changed
> ------------------------------------------------
>
> Key: FELIX-288
> URL: https://issues.apache.org/jira/browse/FELIX-288
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Reporter: Costin Leau
>
> From the mailing list
> > Import versions
> >
> > The import versions are determined automatically and can't be
> > overridden. For example inside Spring/OSGi, we import spring 2.0.5 and
> > the resulting imports have version 2.0.
> > We want to be more specific such as 2.0.5 or [2.0.5, 2.1) but whatever I
> > specify as import package is completely ignored.
> >
> I think this is a BND issue again, will raise it with Peter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-288) autodetermined import versions cannot be
changed
Posted by "Costin Leau (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Costin Leau closed FELIX-288.
-----------------------------
> autodetermined import versions cannot be changed
> ------------------------------------------------
>
> Key: FELIX-288
> URL: https://issues.apache.org/jira/browse/FELIX-288
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Reporter: Costin Leau
> Assignee: Richard S. Hall
>
> From the mailing list
> > Import versions
> >
> > The import versions are determined automatically and can't be
> > overridden. For example inside Spring/OSGi, we import spring 2.0.5 and
> > the resulting imports have version 2.0.
> > We want to be more specific such as 2.0.5 or [2.0.5, 2.1) but whatever I
> > specify as import package is completely ignored.
> >
> I think this is a BND issue again, will raise it with Peter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-288) autodetermined import versions cannot
be changed
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch updated FELIX-288:
-----------------------------------
Priority: Major
Looks like this is fixed in bndlib version 0.0.140
> autodetermined import versions cannot be changed
> ------------------------------------------------
>
> Key: FELIX-288
> URL: https://issues.apache.org/jira/browse/FELIX-288
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Reporter: Costin Leau
>
> From the mailing list
> > Import versions
> >
> > The import versions are determined automatically and can't be
> > overridden. For example inside Spring/OSGi, we import spring 2.0.5 and
> > the resulting imports have version 2.0.
> > We want to be more specific such as 2.0.5 or [2.0.5, 2.1) but whatever I
> > specify as import package is completely ignored.
> >
> I think this is a BND issue again, will raise it with Peter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-288) autodetermined import versions cannot
be changed
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch updated FELIX-288:
-----------------------------------
can this issue be closed?
> autodetermined import versions cannot be changed
> ------------------------------------------------
>
> Key: FELIX-288
> URL: https://issues.apache.org/jira/browse/FELIX-288
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Reporter: Costin Leau
> Assignee: Richard S. Hall
>
> From the mailing list
> > Import versions
> >
> > The import versions are determined automatically and can't be
> > overridden. For example inside Spring/OSGi, we import spring 2.0.5 and
> > the resulting imports have version 2.0.
> > We want to be more specific such as 2.0.5 or [2.0.5, 2.1) but whatever I
> > specify as import package is completely ignored.
> >
> I think this is a BND issue again, will raise it with Peter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-288) autodetermined import versions cannot
be changed
Posted by "Costin Leau (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537241 ]
Costin Leau commented on FELIX-288:
-----------------------------------
yes, just closed it
> autodetermined import versions cannot be changed
> ------------------------------------------------
>
> Key: FELIX-288
> URL: https://issues.apache.org/jira/browse/FELIX-288
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Reporter: Costin Leau
> Assignee: Richard S. Hall
>
> From the mailing list
> > Import versions
> >
> > The import versions are determined automatically and can't be
> > overridden. For example inside Spring/OSGi, we import spring 2.0.5 and
> > the resulting imports have version 2.0.
> > We want to be more specific such as 2.0.5 or [2.0.5, 2.1) but whatever I
> > specify as import package is completely ignored.
> >
> I think this is a BND issue again, will raise it with Peter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.