6:16 a.m.
Allow @Deployment to be optional
--------------------------------
Key: ARQ-272
URL: https://jira.jboss.org/browse/ARQ-272
Project: Arquillian
Issue Type: Feature Request
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 1.0.0.Alpha4
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains the test class,
which would reduce the noise in ARQ OSGi tests considerably.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:16 a.m.
New subject: [JBoss JIRA] Work started: (ARQ-272) Allow @Deployment to be optional
[
https://jira.jboss.org/browse/ARQ-272?page=com.atlassian.jira.plugin.syst...
]
Work on ARQ-272 started by Thomas Diesler.
Allow @Deployment to be optional
--------------------------------
Key: ARQ-272
URL: https://jira.jboss.org/browse/ARQ-272
Project: Arquillian
Issue Type: Feature Request
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 1.0.0.Alpha4
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains the test class,
which would reduce the noise in ARQ OSGi tests considerably.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:20 a.m.
New subject: [JBoss JIRA] Updated: (ARQ-272) Allow @Deployment to be optional
[
https://jira.jboss.org/browse/ARQ-272?page=com.atlassian.jira.plugin.syst...
]
Thomas Diesler updated ARQ-272:
-------------------------------
Description:
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains just the test
class, which would reduce the noise in ARQ OSGi tests considerably.
Currently this code is required in every OSGi test case that does not operate on a single
bundle deployment.
@Deployment
public static Archive<?> createDeployment()
{
return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
}
was:
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains the test class,
which would reduce the noise in ARQ OSGi tests considerably.
Allow @Deployment to be optional
--------------------------------
Key: ARQ-272
URL: https://jira.jboss.org/browse/ARQ-272
Project: Arquillian
Issue Type: Feature Request
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 1.0.0.Alpha4
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains just the test
class, which would reduce the noise in ARQ OSGi tests considerably.
Currently this code is required in every OSGi test case that does not operate on a single
bundle deployment.
@Deployment
public static Archive<?> createDeployment()
{
return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:28 a.m.
New subject: [JBoss JIRA] Resolved: (ARQ-272) Allow @Deployment to be optional
[
https://jira.jboss.org/browse/ARQ-272?page=com.atlassian.jira.plugin.syst...
]
Thomas Diesler resolved ARQ-272.
--------------------------------
Resolution: Done
Done.
Running org.jboss.arquillian.container.osgi.arq272.ARQ272TestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.445 sec
Please pull from http://github.com/jbosgi/arquillian/tree/arq272
Allow @Deployment to be optional
--------------------------------
Key: ARQ-272
URL: https://jira.jboss.org/browse/ARQ-272
Project: Arquillian
Issue Type: Feature Request
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 1.0.0.Alpha4
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains just the test
class, which would reduce the noise in ARQ OSGi tests considerably.
Currently this code is required in every OSGi test case that does not operate on a single
bundle deployment.
@Deployment
public static Archive<?> createDeployment()
{
return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:30 a.m.
New subject: [JBoss JIRA] Reopened: (ARQ-272) Allow @Deployment to be optional
[
https://jira.jboss.org/browse/ARQ-272?page=com.atlassian.jira.plugin.syst...
]
Thomas Diesler reopened ARQ-272:
--------------------------------
Assignee: Aslak Knutsen (was: Thomas Diesler)
Allow @Deployment to be optional
--------------------------------
Key: ARQ-272
URL: https://jira.jboss.org/browse/ARQ-272
Project: Arquillian
Issue Type: Feature Request
Reporter: Thomas Diesler
Assignee: Aslak Knutsen
Fix For: 1.0.0.Alpha4
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains just the test
class, which would reduce the noise in ARQ OSGi tests considerably.
Currently this code is required in every OSGi test case that does not operate on a single
bundle deployment.
@Deployment
public static Archive<?> createDeployment()
{
return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:21 a.m.
New subject: [JBoss JIRA] Updated: (ARQ-272) Allow @Deployment to be optional
[
https://jira.jboss.org/browse/ARQ-272?page=com.atlassian.jira.plugin.syst...
]
Thomas Diesler updated ARQ-272:
-------------------------------
Assignee: Thomas Diesler (was: Aslak Knutsen)
Waiting on
[ARQ-273] Verify that all jbosgi in-container tests can be migrated to ARQ
Allow @Deployment to be optional
--------------------------------
Key: ARQ-272
URL: https://jira.jboss.org/browse/ARQ-272
Project: Arquillian
Issue Type: Feature Request
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 1.0.0.Alpha4
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains just the test
class, which would reduce the noise in ARQ OSGi tests considerably.
Currently this code is required in every OSGi test case that does not operate on a single
bundle deployment.
@Deployment
public static Archive<?> createDeployment()
{
return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:59 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-272) Allow @Deployment to be optional
[
https://jira.jboss.org/browse/ARQ-272?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen updated ARQ-272:
------------------------------
Fix Version/s: 1.0.0.Beta1
(was: 1.0.0.Alpha4)
Allow @Deployment to be optional
--------------------------------
Key: ARQ-272
URL: https://jira.jboss.org/browse/ARQ-272
Project: Arquillian
Issue Type: Feature Request
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 1.0.0.Beta1
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains just the test
class, which would reduce the noise in ARQ OSGi tests considerably.
Currently this code is required in every OSGi test case that does not operate on a single
bundle deployment.
@Deployment
public static Archive<?> createDeployment()
{
return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:53 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-272) Allow @Deployment to be optional
[
https://jira.jboss.org/browse/ARQ-272?page=com.atlassian.jira.plugin.syst...
]
Thomas Diesler updated ARQ-272:
-------------------------------
Assignee: Aslak Knutsen (was: Thomas Diesler)
We are good to go please pull
http://github.com/jbosgi/arquillian/tree/jbosgi
Allow @Deployment to be optional
--------------------------------
Key: ARQ-272
URL: https://jira.jboss.org/browse/ARQ-272
Project: Arquillian
Issue Type: Feature Request
Reporter: Thomas Diesler
Assignee: Aslak Knutsen
Fix For: 1.0.0.Beta1
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains just the test
class, which would reduce the noise in ARQ OSGi tests considerably.
Currently this code is required in every OSGi test case that does not operate on a single
bundle deployment.
@Deployment
public static Archive<?> createDeployment()
{
return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:07 a.m.
New subject: [JBoss JIRA] Assigned: (ARQ-272) Allow @Deployment to be optional
[
https://issues.jboss.org/browse/ARQ-272?page=com.atlassian.jira.plugin.sy...
]
Thomas Diesler reassigned ARQ-272:
----------------------------------
Assignee: Thomas Diesler (was: Aslak Knutsen)
Allow @Deployment to be optional
--------------------------------
Key: ARQ-272
URL: https://issues.jboss.org/browse/ARQ-272
Project: Arquillian
Issue Type: Feature Request
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 1.0.0.Beta1
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains just the test
class, which would reduce the noise in ARQ OSGi tests considerably.
Currently this code is required in every OSGi test case that does not operate on a single
bundle deployment.
@Deployment
public static Archive<?> createDeployment()
{
return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:07 a.m.
New subject: [JBoss JIRA] Work started: (ARQ-272) Allow @Deployment to be optional
[
https://issues.jboss.org/browse/ARQ-272?page=com.atlassian.jira.plugin.sy...
]
Work on ARQ-272 started by Thomas Diesler.
Allow @Deployment to be optional
--------------------------------
Key: ARQ-272
URL: https://issues.jboss.org/browse/ARQ-272
Project: Arquillian
Issue Type: Feature Request
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 1.0.0.Beta1
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains just the test
class, which would reduce the noise in ARQ OSGi tests considerably.
Currently this code is required in every OSGi test case that does not operate on a single
bundle deployment.
@Deployment
public static Archive<?> createDeployment()
{
return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:48 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-272) Allow @Deployment to be optional
[
https://issues.jboss.org/browse/ARQ-272?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen commented on ARQ-272:
-----------------------------------
Keep in mind that this is not a feature the will go into Arquillian Core. A non defined
@Deployment has another meaning in Arq Core. This can be implemented as a
DeploymentScenarioGenerator specially for the OSGi Container test Suite.
Allow @Deployment to be optional
--------------------------------
Key: ARQ-272
URL: https://issues.jboss.org/browse/ARQ-272
Project: Arquillian
Issue Type: Feature Request
Components: OSGi Containers
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 1.0.0.Beta1
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains just the test
class, which would reduce the noise in ARQ OSGi tests considerably.
Currently this code is required in every OSGi test case that does not operate on a single
bundle deployment.
@Deployment
public static Archive<?> createDeployment()
{
return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:48 a.m.
New subject: [JBoss JIRA] Updated: (ARQ-272) Allow @Deployment to be optional
[
https://issues.jboss.org/browse/ARQ-272?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-272:
------------------------------
Component/s: OSGi Containers
Allow @Deployment to be optional
--------------------------------
Key: ARQ-272
URL: https://issues.jboss.org/browse/ARQ-272
Project: Arquillian
Issue Type: Feature Request
Components: OSGi Containers
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 1.0.0.Beta1
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains just the test
class, which would reduce the noise in ARQ OSGi tests considerably.
Currently this code is required in every OSGi test case that does not operate on a single
bundle deployment.
@Deployment
public static Archive<?> createDeployment()
{
return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:19 a.m.
New subject: [JBoss JIRA] Resolved: (ARQ-272) Allow @Deployment to be optional
[
https://issues.jboss.org/browse/ARQ-272?page=com.atlassian.jira.plugin.sy...
]
Thomas Diesler resolved ARQ-272.
--------------------------------
Fix Version/s: (was: 1.0.0.Beta1)
Resolution: Won't Fix
Won't Fix
Allow @Deployment to be optional
--------------------------------
Key: ARQ-272
URL: https://issues.jboss.org/browse/ARQ-272
Project: Arquillian
Issue Type: Feature Request
Components: OSGi Containers
Reporter: Thomas Diesler
Assignee: Thomas Diesler
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains just the test
class, which would reduce the noise in ARQ OSGi tests considerably.
Currently this code is required in every OSGi test case that does not operate on a single
bundle deployment.
@Deployment
public static Archive<?> createDeployment()
{
return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:21 a.m.
New subject: [JBoss JIRA] Updated: (ARQ-272) Allow @Deployment to be optional
[
https://issues.jboss.org/browse/ARQ-272?page=com.atlassian.jira.plugin.sy...
]
Thomas Diesler updated ARQ-272:
-------------------------------
Git Pull Request: https://github.com/arquillian/arquillian-container-osgi/pull/2
Allow @Deployment to be optional
--------------------------------
Key: ARQ-272
URL: https://issues.jboss.org/browse/ARQ-272
Project: Arquillian
Issue Type: Feature Request
Components: OSGi Containers
Reporter: Thomas Diesler
Assignee: Thomas Diesler
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains just the test
class, which would reduce the noise in ARQ OSGi tests considerably.
Currently this code is required in every OSGi test case that does not operate on a single
bundle deployment.
@Deployment
public static Archive<?> createDeployment()
{
return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:39 a.m.
New subject: [JBoss JIRA] Closed: (ARQ-272) Allow @Deployment to be optional
[
https://issues.jboss.org/browse/ARQ-272?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen closed ARQ-272.
-----------------------------
pushed testcase removal upstream
Allow @Deployment to be optional
--------------------------------
Key: ARQ-272
URL: https://issues.jboss.org/browse/ARQ-272
Project: Arquillian
Issue Type: Feature Request
Components: OSGi Containers
Reporter: Thomas Diesler
Assignee: Thomas Diesler
OSGi test cases frequently generate non-trivial bundle deployments as part of their test
methods.
The bundle that contains the test case is automatically generated by ARQ. To be precise,
the test class is always added to the @Deployment. The bundle manifest is generated or
extended by the required Import/Export-Package statements.
If @Deployment was missing, ARQ could generate an Archive that contains just the test
class, which would reduce the noise in ARQ OSGi tests considerably.
Currently this code is required in every OSGi test case that does not operate on a single
bundle deployment.
@Deployment
public static Archive<?> createDeployment()
{
return ShrinkWrap.create(JavaArchive.class, "empty-bundle");
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4800
days inactive
5035
days old
arquillian-issues@lists.jboss.org
14 comments
2 participants
participants (2)
-
Aslak Knutsen (JIRA) -
Thomas Diesler (JIRA)