Thomas Diesler created JBOSGI-655:
-------------------------------------
Summary: Cannot access jboss-osgi API docs
Key: JBOSGI-655
URL: https://issues.jboss.org/browse/JBOSGI-655
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Distribution
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 2.0.1
http://docs.jboss.org/osgi/apidocs
403 Forbidden
You don't have permission to access /osgi/apidocs on this server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/JBOSGI-650?page=com.atlassian.jira.plugin... ]
Thomas Diesler resolved JBOSGI-650.
-----------------------------------
Resolution: Done
Done
> Update WildFly dependency to 8.0.0.Alpha2
> -----------------------------------------
>
> Key: JBOSGI-650
> URL: https://issues.jboss.org/browse/JBOSGI-650
> Project: JBoss OSGi
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Distribution
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: JBossOSGi 2.0.0
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/JBOSGI-650?page=com.atlassian.jira.plugin... ]
Work on JBOSGI-650 started by Thomas Diesler.
> Update WildFly dependency to 8.0.0.Alpha2
> -----------------------------------------
>
> Key: JBOSGI-650
> URL: https://issues.jboss.org/browse/JBOSGI-650
> Project: JBoss OSGi
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Distribution
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: JBossOSGi 2.0.0
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Thomas Diesler created JBOSGI-654:
-------------------------------------
Summary: CLONE - Add ability to provision adapted modules
Key: JBOSGI-654
URL: https://issues.jboss.org/browse/JBOSGI-654
Project: JBoss OSGi
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Provisioner
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 2.0.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Thomas Diesler created JBOSGI-653:
-------------------------------------
Summary: Add ability to provision adapted modules
Key: JBOSGI-653
URL: https://issues.jboss.org/browse/JBOSGI-653
Project: JBoss OSGi
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Provisioner
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 2.0.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/JBOSGI-652?page=com.atlassian.jira.plugin... ]
Thomas Diesler resolved JBOSGI-652.
-----------------------------------
Fix Version/s: JBossOSGi 2.0.0
Resolution: Done
Done in jbosgi-provision-1.0.1.Final
> Add ability to provision adapted modules
> ----------------------------------------
>
> Key: JBOSGI-652
> URL: https://issues.jboss.org/browse/JBOSGI-652
> Project: JBoss OSGi
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Provisioner
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: JBossOSGi 2.0.0
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/JBOSGI-652?page=com.atlassian.jira.plugin... ]
Thomas Diesler updated JBOSGI-652:
----------------------------------
Component/s: Provisioner
(was: Repository)
> Add ability to provision adapted modules
> ----------------------------------------
>
> Key: JBOSGI-652
> URL: https://issues.jboss.org/browse/JBOSGI-652
> Project: JBoss OSGi
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Provisioner
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Thomas Diesler created JBOSGI-652:
-------------------------------------
Summary: Add ability to provision adapted modules
Key: JBOSGI-652
URL: https://issues.jboss.org/browse/JBOSGI-652
Project: JBoss OSGi
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Repository
Reporter: Thomas Diesler
Assignee: Thomas Diesler
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/JBOSGI-649?page=com.atlassian.jira.plugin... ]
Thomas Diesler edited comment on JBOSGI-649 at 6/21/13 1:39 AM:
----------------------------------------------------------------
Done in jbosgi-framework-3.0.1.Final
was (Author: thomas.diesler):
Done
> Install adapted Module through BundleManager
> --------------------------------------------
>
> Key: JBOSGI-649
> URL: https://issues.jboss.org/browse/JBOSGI-649
> Project: JBoss OSGi
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Core Framework
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: JBossOSGi 2.0.0
>
>
> There are currently multiple places where WildFly installs an adapted module directly into the environment. These should be consolidated and go through the BundleManager
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/JBOSGI-651?page=com.atlassian.jira.plugin... ]
Thomas Diesler resolved JBOSGI-651.
-----------------------------------
Resolution: Done
Done in jbosgi-repository-3.0.1.Final
> Add ability to specify a target resource type with the maven repository
> -----------------------------------------------------------------------
>
> Key: JBOSGI-651
> URL: https://issues.jboss.org/browse/JBOSGI-651
> Project: JBoss OSGi
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Repository
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: JBossOSGi 2.0.0
>
>
> An abstract resource can delegate to the Module/MavenIdentityRepository. The target resource can either be module or bundle. It should be possible to specify the target type with the requirement.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira