You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Gerodolle (JIRA)" <ji...@apache.org> on 2008/05/13 15:14:55 UTC
[jira] Created: (FELIX-554) allow removing a bundle from a remote
OBR
allow removing a bundle from a remote OBR
-----------------------------------------
Key: FELIX-554
URL: https://issues.apache.org/jira/browse/FELIX-554
Project: Felix
Issue Type: New Feature
Components: Maven Bundle Plugin
Affects Versions: maven-bundle-plugin-1.4.1, maven-bundle-plugin-1.4.0
Environment: any
Reporter: Gerodolle
Priority: Minor
With version 1.4.1 of maven-bundle-plugin , it is possible to incrementally build a remote obr repository, by adding new bundles using "mvn deploy -DremoteOBR", but the removal of obsolete bundles from the repository remains manual, thus error prone.
it would be nice to have a way to automatically remove a bundle from a remote OBR, e.g. to replace a version of a bundle with a new version .
Removing a bundle would mean suppress the reference to this bundle from the repository.xml file .
Optionaly, we could also "undeploy" the artifact itself, but then we have to suppress the folder and edit the maven metadata.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-554) allow removing a bundle from a remote
OBR
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch reassigned FELIX-554:
--------------------------------------
Assignee: Stuart McCulloch
> allow removing a bundle from a remote OBR
> -----------------------------------------
>
> Key: FELIX-554
> URL: https://issues.apache.org/jira/browse/FELIX-554
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.0, maven-bundle-plugin-1.4.1
> Environment: any
> Reporter: Gerodolle
> Assignee: Stuart McCulloch
> Priority: Minor
> Fix For: maven-bundle-plugin-1.4.3
>
>
> With version 1.4.1 of maven-bundle-plugin , it is possible to incrementally build a remote obr repository, by adding new bundles using "mvn deploy -DremoteOBR", but the removal of obsolete bundles from the repository remains manual, thus error prone.
> it would be nice to have a way to automatically remove a bundle from a remote OBR, e.g. to replace a version of a bundle with a new version .
> Removing a bundle would mean suppress the reference to this bundle from the repository.xml file .
> Optionaly, we could also "undeploy" the artifact itself, but then we have to suppress the folder and edit the maven metadata.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-554) allow removing a bundle from a remote
OBR
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch resolved FELIX-554.
------------------------------------
Resolution: Fixed
Fix Version/s: maven-bundle-plugin-1.4.3
Clement contributed a remote-clean goal that went into maven-bundle-plugin 1.4.3:
http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
It supports cleaning of the remote repository file (similar to the bundle:clean goal)
Note: removal of the deployed bundle artifact is outside of the scope of this plugin.
> allow removing a bundle from a remote OBR
> -----------------------------------------
>
> Key: FELIX-554
> URL: https://issues.apache.org/jira/browse/FELIX-554
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.0, maven-bundle-plugin-1.4.1
> Environment: any
> Reporter: Gerodolle
> Priority: Minor
> Fix For: maven-bundle-plugin-1.4.3
>
>
> With version 1.4.1 of maven-bundle-plugin , it is possible to incrementally build a remote obr repository, by adding new bundles using "mvn deploy -DremoteOBR", but the removal of obsolete bundles from the repository remains manual, thus error prone.
> it would be nice to have a way to automatically remove a bundle from a remote OBR, e.g. to replace a version of a bundle with a new version .
> Removing a bundle would mean suppress the reference to this bundle from the repository.xml file .
> Optionaly, we could also "undeploy" the artifact itself, but then we have to suppress the folder and edit the maven metadata.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-554) allow removing a bundle from a remote
OBR
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch reassigned FELIX-554:
--------------------------------------
Assignee: (was: Stuart McCulloch)
Unassigning myself from this issue, because I'll be away for the next few weeks on vacation.
> allow removing a bundle from a remote OBR
> -----------------------------------------
>
> Key: FELIX-554
> URL: https://issues.apache.org/jira/browse/FELIX-554
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.0, maven-bundle-plugin-1.4.1
> Environment: any
> Reporter: Gerodolle
> Priority: Minor
>
> With version 1.4.1 of maven-bundle-plugin , it is possible to incrementally build a remote obr repository, by adding new bundles using "mvn deploy -DremoteOBR", but the removal of obsolete bundles from the repository remains manual, thus error prone.
> it would be nice to have a way to automatically remove a bundle from a remote OBR, e.g. to replace a version of a bundle with a new version .
> Removing a bundle would mean suppress the reference to this bundle from the repository.xml file .
> Optionaly, we could also "undeploy" the artifact itself, but then we have to suppress the folder and edit the maven metadata.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-554) allow removing a bundle from a remote
OBR
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch updated FELIX-554:
-----------------------------------
Fix Version/s: maven-bundle-plugin-1.4.2
> allow removing a bundle from a remote OBR
> -----------------------------------------
>
> Key: FELIX-554
> URL: https://issues.apache.org/jira/browse/FELIX-554
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.0, maven-bundle-plugin-1.4.1
> Environment: any
> Reporter: Gerodolle
> Assignee: Stuart McCulloch
> Priority: Minor
> Fix For: maven-bundle-plugin-1.4.2
>
>
> With version 1.4.1 of maven-bundle-plugin , it is possible to incrementally build a remote obr repository, by adding new bundles using "mvn deploy -DremoteOBR", but the removal of obsolete bundles from the repository remains manual, thus error prone.
> it would be nice to have a way to automatically remove a bundle from a remote OBR, e.g. to replace a version of a bundle with a new version .
> Removing a bundle would mean suppress the reference to this bundle from the repository.xml file .
> Optionaly, we could also "undeploy" the artifact itself, but then we have to suppress the folder and edit the maven metadata.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-554) allow removing a bundle from a remote
OBR
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch updated FELIX-554:
-----------------------------------
Fix Version/s: (was: maven-bundle-plugin-1.4.2)
Unfortunately I don't have time to get this into 1.4.2, so will reschedule to a later release.
> allow removing a bundle from a remote OBR
> -----------------------------------------
>
> Key: FELIX-554
> URL: https://issues.apache.org/jira/browse/FELIX-554
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.0, maven-bundle-plugin-1.4.1
> Environment: any
> Reporter: Gerodolle
> Assignee: Stuart McCulloch
> Priority: Minor
>
> With version 1.4.1 of maven-bundle-plugin , it is possible to incrementally build a remote obr repository, by adding new bundles using "mvn deploy -DremoteOBR", but the removal of obsolete bundles from the repository remains manual, thus error prone.
> it would be nice to have a way to automatically remove a bundle from a remote OBR, e.g. to replace a version of a bundle with a new version .
> Removing a bundle would mean suppress the reference to this bundle from the repository.xml file .
> Optionaly, we could also "undeploy" the artifact itself, but then we have to suppress the folder and edit the maven metadata.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-554) allow removing a bundle from a remote
OBR
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch reassigned FELIX-554:
--------------------------------------
Assignee: Stuart McCulloch
> allow removing a bundle from a remote OBR
> -----------------------------------------
>
> Key: FELIX-554
> URL: https://issues.apache.org/jira/browse/FELIX-554
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.0, maven-bundle-plugin-1.4.1
> Environment: any
> Reporter: Gerodolle
> Assignee: Stuart McCulloch
> Priority: Minor
> Fix For: maven-bundle-plugin-1.4.2
>
>
> With version 1.4.1 of maven-bundle-plugin , it is possible to incrementally build a remote obr repository, by adding new bundles using "mvn deploy -DremoteOBR", but the removal of obsolete bundles from the repository remains manual, thus error prone.
> it would be nice to have a way to automatically remove a bundle from a remote OBR, e.g. to replace a version of a bundle with a new version .
> Removing a bundle would mean suppress the reference to this bundle from the repository.xml file .
> Optionaly, we could also "undeploy" the artifact itself, but then we have to suppress the folder and edit the maven metadata.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-554) allow removing a bundle from a remote
OBR
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch closed FELIX-554.
----------------------------------
Closing as the bundle:remote-clean goal is available in both 1.4.3 and 2.0.0
> allow removing a bundle from a remote OBR
> -----------------------------------------
>
> Key: FELIX-554
> URL: https://issues.apache.org/jira/browse/FELIX-554
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.0, maven-bundle-plugin-1.4.1
> Environment: any
> Reporter: Gerodolle
> Assignee: Stuart McCulloch
> Priority: Minor
> Fix For: maven-bundle-plugin-1.4.3
>
>
> With version 1.4.1 of maven-bundle-plugin , it is possible to incrementally build a remote obr repository, by adding new bundles using "mvn deploy -DremoteOBR", but the removal of obsolete bundles from the repository remains manual, thus error prone.
> it would be nice to have a way to automatically remove a bundle from a remote OBR, e.g. to replace a version of a bundle with a new version .
> Removing a bundle would mean suppress the reference to this bundle from the repository.xml file .
> Optionaly, we could also "undeploy" the artifact itself, but then we have to suppress the folder and edit the maven metadata.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.