[JBoss JIRA] Created: (ARQ-585) Support for adding a beans.xml without discarding the original beans.xml with .mergeAsResource()
11:21 a.m.
Support for adding a beans.xml without discarding the original beans.xml with
.mergeAsResource()
------------------------------------------------------------------------------------------------
Key: ARQ-585
URL: https://issues.jboss.org/browse/ARQ-585
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
Presume these 2 beans.xml files:
Production code: beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
</beans>
{code}
Test addition: test-beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
Now, for non-test runs (such as in the IDE or in production), only the beans.xml is
activated through weld and the test-only alternative should not be activated.
For test runs, the test-only alternative should be activated, yet the rest of the content
from beans.xml should be in there too.
So it should be merged to something like this:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
It would be nice if we do something like mergeAsResource(), shown in this example:
{code}
public static WebArchive createDeployment() {
WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class,
"guvnor-webapp-5.3.0-SNAPSHOT.war")
.importDirectory(new
File("target/guvnor-webapp-5.3.0-SNAPSHOT/"))
.as(WebArchive.class)
.mergeAsResource(new
File("target/test-classes/META-INF/test-beans.xml"),
"META-INF/beans.xml")
.addAsResource(new File("target/test-classes/"),
ArchivePaths.create(""))
.addAsLibraries(
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.resolveAsFiles(new ScopeFilter("test")));
return webArchive;
}
{code}
Because of maintenance, copying everything from beans.xml to test-beans.xml on every
change to beans.xml is NOT an option.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:41 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-585) Support for adding a beans.xml without discarding the original beans.xml with .mergeAsResource()
[
https://issues.jboss.org/browse/ARQ-585?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet commented on ARQ-585:
--------------------------------------
Another option would be that arquillian or weld automatically recognizes
"test-beans.xml" (just like beans.xml and seam-beans.xml).
Support for adding a beans.xml without discarding the original
beans.xml with .mergeAsResource()
------------------------------------------------------------------------------------------------
Key: ARQ-585
URL: https://issues.jboss.org/browse/ARQ-585
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
Presume these 2 beans.xml files:
Production code: beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
</beans>
{code}
Test addition: test-beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
Now, for non-test runs (such as in the IDE or in production), only the beans.xml is
activated through weld and the test-only alternative should not be activated.
For test runs, the test-only alternative should be activated, yet the rest of the content
from beans.xml should be in there too.
So it should be merged to something like this:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
It would be nice if we do something like mergeAsResource(), shown in this example:
{code}
public static WebArchive createDeployment() {
WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class,
"guvnor-webapp-5.3.0-SNAPSHOT.war")
.importDirectory(new
File("target/guvnor-webapp-5.3.0-SNAPSHOT/"))
.as(WebArchive.class)
.mergeAsResource(new
File("target/test-classes/META-INF/test-beans.xml"),
"META-INF/beans.xml")
.addAsResource(new File("target/test-classes/"),
ArchivePaths.create(""))
.addAsLibraries(
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.resolveAsFiles(new ScopeFilter("test")));
return webArchive;
}
{code}
Because of maintenance, copying everything from beans.xml to test-beans.xml on every
change to beans.xml is NOT an option.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:02 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-585) Support for adding a test-beans.xml without discarding the original beans.xml or seam-beans.xml
[
https://issues.jboss.org/browse/ARQ-585?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet updated ARQ-585:
---------------------------------
Summary: Support for adding a test-beans.xml without discarding the original beans.xml
or seam-beans.xml (was: Support for adding a beans.xml without discarding the original
beans.xml with .mergeAsResource())
Support for adding a test-beans.xml without discarding the original
beans.xml or seam-beans.xml
-----------------------------------------------------------------------------------------------
Key: ARQ-585
URL: https://issues.jboss.org/browse/ARQ-585
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
Presume these 2 beans.xml files:
Production code: beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
</beans>
{code}
Test addition: test-beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
Now, for non-test runs (such as in the IDE or in production), only the beans.xml is
activated through weld and the test-only alternative should not be activated.
For test runs, the test-only alternative should be activated, yet the rest of the content
from beans.xml should be in there too.
So it should be merged to something like this:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
It would be nice if we do something like mergeAsResource(), shown in this example:
{code}
public static WebArchive createDeployment() {
WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class,
"guvnor-webapp-5.3.0-SNAPSHOT.war")
.importDirectory(new
File("target/guvnor-webapp-5.3.0-SNAPSHOT/"))
.as(WebArchive.class)
.mergeAsResource(new
File("target/test-classes/META-INF/test-beans.xml"),
"META-INF/beans.xml")
.addAsResource(new File("target/test-classes/"),
ArchivePaths.create(""))
.addAsLibraries(
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.resolveAsFiles(new ScopeFilter("test")));
return webArchive;
}
{code}
Because of maintenance, copying everything from beans.xml to test-beans.xml on every
change to beans.xml is NOT an option.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:01 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-585) Support for adding a test-beans.xml without discarding the original beans.xml or seam-beans.xml
[
https://issues.jboss.org/browse/ARQ-585?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen commented on ARQ-585:
-----------------------------------
If anything, this could be a feature of ShrinkWrap Descirptors.
Support for adding a test-beans.xml without discarding the original
beans.xml or seam-beans.xml
-----------------------------------------------------------------------------------------------
Key: ARQ-585
URL: https://issues.jboss.org/browse/ARQ-585
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
Presume these 2 beans.xml files:
Production code: beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
</beans>
{code}
Test addition: test-beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
Now, for non-test runs (such as in the IDE or in production), only the beans.xml is
activated through weld and the test-only alternative should not be activated.
For test runs, the test-only alternative should be activated, yet the rest of the content
from beans.xml should be in there too.
So it should be merged to something like this:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
It would be nice if we do something like mergeAsResource(), shown in this example:
{code}
public static WebArchive createDeployment() {
WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class,
"guvnor-webapp-5.3.0-SNAPSHOT.war")
.importDirectory(new
File("target/guvnor-webapp-5.3.0-SNAPSHOT/"))
.as(WebArchive.class)
.mergeAsResource(new
File("target/test-classes/META-INF/test-beans.xml"),
"META-INF/beans.xml")
.addAsResource(new File("target/test-classes/"),
ArchivePaths.create(""))
.addAsLibraries(
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.resolveAsFiles(new ScopeFilter("test")));
return webArchive;
}
{code}
Because of maintenance, copying everything from beans.xml to test-beans.xml on every
change to beans.xml is NOT an option.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:57 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-585) Support for adding a test-beans.xml without discarding the original beans.xml or seam-beans.xml
[
https://issues.jboss.org/browse/ARQ-585?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet commented on ARQ-585:
--------------------------------------
Workaround: move everything from seam-beans.xml into beans.xml and use seam-beans.xml in
your test classpath.
Support for adding a test-beans.xml without discarding the original
beans.xml or seam-beans.xml
-----------------------------------------------------------------------------------------------
Key: ARQ-585
URL: https://issues.jboss.org/browse/ARQ-585
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
Presume these 2 beans.xml files:
Production code: beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
</beans>
{code}
Test addition: test-beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
Now, for non-test runs (such as in the IDE or in production), only the beans.xml is
activated through weld and the test-only alternative should not be activated.
For test runs, the test-only alternative should be activated, yet the rest of the content
from beans.xml should be in there too.
So it should be merged to something like this:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
It would be nice if we do something like mergeAsResource(), shown in this example:
{code}
public static WebArchive createDeployment() {
WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class,
"guvnor-webapp-5.3.0-SNAPSHOT.war")
.importDirectory(new
File("target/guvnor-webapp-5.3.0-SNAPSHOT/"))
.as(WebArchive.class)
.mergeAsResource(new
File("target/test-classes/META-INF/test-beans.xml"),
"META-INF/beans.xml")
.addAsResource(new File("target/test-classes/"),
ArchivePaths.create(""))
.addAsLibraries(
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.resolveAsFiles(new ScopeFilter("test")));
return webArchive;
}
{code}
Because of maintenance, copying everything from beans.xml to test-beans.xml on every
change to beans.xml is NOT an option.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:05 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-585) Support for adding a test-beans.xml without discarding the original beans.xml or seam-beans.xml
[
https://issues.jboss.org/browse/ARQ-585?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet edited comment on ARQ-585 at 9/30/11 3:04 AM:
---------------------------------------------------------------
Failing workaround: move everything from seam-beans.xml into beans.xml and use
seam-beans.xml in your test classpath.
Doesn't work because <alternatives> must be declared in beans.xml, not
seam-beans.xml.
was (Author: ge0ffrey):
Workaround: move everything from seam-beans.xml into beans.xml and use seam-beans.xml
in your test classpath.
Support for adding a test-beans.xml without discarding the original
beans.xml or seam-beans.xml
-----------------------------------------------------------------------------------------------
Key: ARQ-585
URL: https://issues.jboss.org/browse/ARQ-585
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
Presume these 2 beans.xml files:
Production code: beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
</beans>
{code}
Test addition: test-beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
Now, for non-test runs (such as in the IDE or in production), only the beans.xml is
activated through weld and the test-only alternative should not be activated.
For test runs, the test-only alternative should be activated, yet the rest of the content
from beans.xml should be in there too.
So it should be merged to something like this:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
It would be nice if we do something like mergeAsResource(), shown in this example:
{code}
public static WebArchive createDeployment() {
WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class,
"guvnor-webapp-5.3.0-SNAPSHOT.war")
.importDirectory(new
File("target/guvnor-webapp-5.3.0-SNAPSHOT/"))
.as(WebArchive.class)
.mergeAsResource(new
File("target/test-classes/META-INF/test-beans.xml"),
"META-INF/beans.xml")
.addAsResource(new File("target/test-classes/"),
ArchivePaths.create(""))
.addAsLibraries(
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.resolveAsFiles(new ScopeFilter("test")));
return webArchive;
}
{code}
Because of maintenance, copying everything from beans.xml to test-beans.xml on every
change to beans.xml is NOT an option.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:18 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-585) Support for adding a test-beans.xml without discarding the original beans.xml or seam-beans.xml
[
https://issues.jboss.org/browse/ARQ-585?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet commented on ARQ-585:
--------------------------------------
Working workaround:
Put the real beans.xml in
src/main/resources/META-INF/beans.xml
Make sure there is no src/main/webapp/WEB-INF/beans.xml
put the test beans.xml somewhere, for example
src/test/resources/META-INF/beans.xml
then add this to @Deployment:
.addAsWebInfResource(new File("target/test-classes/META-INF/beans.xml"),
ArchivePaths.create("beans.xml"))
Note: if you have this problem too and this workaround works for you, then still vote for
this issue anyway.
Support for adding a test-beans.xml without discarding the original
beans.xml or seam-beans.xml
-----------------------------------------------------------------------------------------------
Key: ARQ-585
URL: https://issues.jboss.org/browse/ARQ-585
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
Presume these 2 beans.xml files:
Production code: beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
</beans>
{code}
Test addition: test-beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
Now, for non-test runs (such as in the IDE or in production), only the beans.xml is
activated through weld and the test-only alternative should not be activated.
For test runs, the test-only alternative should be activated, yet the rest of the content
from beans.xml should be in there too.
So it should be merged to something like this:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
It would be nice if we do something like mergeAsResource(), shown in this example:
{code}
public static WebArchive createDeployment() {
WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class,
"guvnor-webapp-5.3.0-SNAPSHOT.war")
.importDirectory(new
File("target/guvnor-webapp-5.3.0-SNAPSHOT/"))
.as(WebArchive.class)
.mergeAsResource(new
File("target/test-classes/META-INF/test-beans.xml"),
"META-INF/beans.xml")
.addAsResource(new File("target/test-classes/"),
ArchivePaths.create(""))
.addAsLibraries(
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.resolveAsFiles(new ScopeFilter("test")));
return webArchive;
}
{code}
Because of maintenance, copying everything from beans.xml to test-beans.xml on every
change to beans.xml is NOT an option.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:20 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-585) Support for adding a test-beans.xml without discarding the original beans.xml or seam-beans.xml
[
https://issues.jboss.org/browse/ARQ-585?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet edited comment on ARQ-585 at 9/30/11 3:18 AM:
---------------------------------------------------------------
Working workaround (hack actually):
Put the real beans.xml in
src/main/resources/META-INF/beans.xml
Make sure there is no src/main/webapp/WEB-INF/beans.xml
put the test beans.xml somewhere, for example
src/test/resources/META-INF/beans.xml
then add this to @Deployment:
.addAsWebInfResource(new File("target/test-classes/META-INF/beans.xml"),
ArchivePaths.create("beans.xml"))
Note: if you have this problem too and this workaround works for you, then still vote for
this issue anyway.
was (Author: ge0ffrey):
Working workaround:
Put the real beans.xml in
src/main/resources/META-INF/beans.xml
Make sure there is no src/main/webapp/WEB-INF/beans.xml
put the test beans.xml somewhere, for example
src/test/resources/META-INF/beans.xml
then add this to @Deployment:
.addAsWebInfResource(new File("target/test-classes/META-INF/beans.xml"),
ArchivePaths.create("beans.xml"))
Note: if you have this problem too and this workaround works for you, then still vote for
this issue anyway.
Support for adding a test-beans.xml without discarding the original
beans.xml or seam-beans.xml
-----------------------------------------------------------------------------------------------
Key: ARQ-585
URL: https://issues.jboss.org/browse/ARQ-585
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
Presume these 2 beans.xml files:
Production code: beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
</beans>
{code}
Test addition: test-beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
Now, for non-test runs (such as in the IDE or in production), only the beans.xml is
activated through weld and the test-only alternative should not be activated.
For test runs, the test-only alternative should be activated, yet the rest of the content
from beans.xml should be in there too.
So it should be merged to something like this:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
It would be nice if we do something like mergeAsResource(), shown in this example:
{code}
public static WebArchive createDeployment() {
WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class,
"guvnor-webapp-5.3.0-SNAPSHOT.war")
.importDirectory(new
File("target/guvnor-webapp-5.3.0-SNAPSHOT/"))
.as(WebArchive.class)
.mergeAsResource(new
File("target/test-classes/META-INF/test-beans.xml"),
"META-INF/beans.xml")
.addAsResource(new File("target/test-classes/"),
ArchivePaths.create(""))
.addAsLibraries(
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.resolveAsFiles(new ScopeFilter("test")));
return webArchive;
}
{code}
Because of maintenance, copying everything from beans.xml to test-beans.xml on every
change to beans.xml is NOT an option.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:43 p.m.
New subject: [JBoss JIRA] (ARQ-585) Support for adding a test-beans.xml without discarding the original beans.xml or seam-beans.xml
[
https://issues.jboss.org/browse/ARQ-585?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet commented on ARQ-585:
--------------------------------------
Note workaround doesn't work on JBoss AS 7 because the location for the beans.xml is
WEB-INF/beans.xml there (and anything else fails). See WELD-953 and SOLDER-220.
Support for adding a test-beans.xml without discarding the original
beans.xml or seam-beans.xml
-----------------------------------------------------------------------------------------------
Key: ARQ-585
URL: https://issues.jboss.org/browse/ARQ-585
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
Presume these 2 beans.xml files:
Production code: beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
</beans>
{code}
Test addition: test-beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
Now, for non-test runs (such as in the IDE or in production), only the beans.xml is
activated through weld and the test-only alternative should not be activated.
For test runs, the test-only alternative should be activated, yet the rest of the content
from beans.xml should be in there too.
So it should be merged to something like this:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
It would be nice if we do something like mergeAsResource(), shown in this example:
{code}
public static WebArchive createDeployment() {
WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class,
"guvnor-webapp-5.3.0-SNAPSHOT.war")
.importDirectory(new
File("target/guvnor-webapp-5.3.0-SNAPSHOT/"))
.as(WebArchive.class)
.mergeAsResource(new
File("target/test-classes/META-INF/test-beans.xml"),
"META-INF/beans.xml")
.addAsResource(new File("target/test-classes/"),
ArchivePaths.create(""))
.addAsLibraries(
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.resolveAsFiles(new ScopeFilter("test")));
return webArchive;
}
{code}
Because of maintenance, copying everything from beans.xml to test-beans.xml on every
change to beans.xml is NOT an option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:16 p.m.
New subject: [JBoss JIRA] (ARQ-585) Support for adding a beans-test.xml without discarding the original beans.xml or seam-beans.xml
[
https://issues.jboss.org/browse/ARQ-585?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet updated ARQ-585:
---------------------------------
Summary: Support for adding a beans-test.xml without discarding the original beans.xml
or seam-beans.xml (was: Support for adding a test-beans.xml without discarding the
original beans.xml or seam-beans.xml)
Support for adding a beans-test.xml without discarding the original
beans.xml or seam-beans.xml
-----------------------------------------------------------------------------------------------
Key: ARQ-585
URL: https://issues.jboss.org/browse/ARQ-585
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
Presume these 2 beans.xml files:
Production code: beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
</beans>
{code}
Test addition: test-beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
Now, for non-test runs (such as in the IDE or in production), only the beans.xml is
activated through weld and the test-only alternative should not be activated.
For test runs, the test-only alternative should be activated, yet the rest of the content
from beans.xml should be in there too.
So it should be merged to something like this:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
It would be nice if we do something like mergeAsResource(), shown in this example:
{code}
public static WebArchive createDeployment() {
WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class,
"guvnor-webapp-5.3.0-SNAPSHOT.war")
.importDirectory(new
File("target/guvnor-webapp-5.3.0-SNAPSHOT/"))
.as(WebArchive.class)
.mergeAsResource(new
File("target/test-classes/META-INF/test-beans.xml"),
"META-INF/beans.xml")
.addAsResource(new File("target/test-classes/"),
ArchivePaths.create(""))
.addAsLibraries(
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.resolveAsFiles(new ScopeFilter("test")));
return webArchive;
}
{code}
Because of maintenance, copying everything from beans.xml to test-beans.xml on every
change to beans.xml is NOT an option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:56 a.m.
New subject: [JBoss JIRA] (ARQ-585) Support for adding a beans-test.xml without discarding the original beans.xml or seam-beans.xml
[
https://issues.jboss.org/browse/ARQ-585?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet commented on ARQ-585:
--------------------------------------
Good workaround:
There's a better way of making @Alternative usable for testing:
Don't use @Alternative, but use @Specializes. Just put the @Specializes bean only in
your test classpath and it will automatically replace the real bean. No need to mess
around with beans.xml.
Resolving this issue as "Won't fix" because SHRINKDESC-6 will fix the
@Alternative case mostly. Reopen if you don't agree.
Support for adding a beans-test.xml without discarding the original
beans.xml or seam-beans.xml
-----------------------------------------------------------------------------------------------
Key: ARQ-585
URL: https://issues.jboss.org/browse/ARQ-585
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
Presume these 2 beans.xml files:
Production code: beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
</beans>
{code}
Test addition: test-beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
Now, for non-test runs (such as in the IDE or in production), only the beans.xml is
activated through weld and the test-only alternative should not be activated.
For test runs, the test-only alternative should be activated, yet the rest of the content
from beans.xml should be in there too.
So it should be merged to something like this:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
It would be nice if we do something like mergeAsResource(), shown in this example:
{code}
public static WebArchive createDeployment() {
WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class,
"guvnor-webapp-5.3.0-SNAPSHOT.war")
.importDirectory(new
File("target/guvnor-webapp-5.3.0-SNAPSHOT/"))
.as(WebArchive.class)
.mergeAsResource(new
File("target/test-classes/META-INF/test-beans.xml"),
"META-INF/beans.xml")
.addAsResource(new File("target/test-classes/"),
ArchivePaths.create(""))
.addAsLibraries(
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.resolveAsFiles(new ScopeFilter("test")));
return webArchive;
}
{code}
Because of maintenance, copying everything from beans.xml to test-beans.xml on every
change to beans.xml is NOT an option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:56 a.m.
New subject: [JBoss JIRA] (ARQ-585) Support for adding a beans-test.xml without discarding the original beans.xml or seam-beans.xml
[
https://issues.jboss.org/browse/ARQ-585?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet resolved ARQ-585.
----------------------------------
Resolution: Deferred
Support for adding a beans-test.xml without discarding the original
beans.xml or seam-beans.xml
-----------------------------------------------------------------------------------------------
Key: ARQ-585
URL: https://issues.jboss.org/browse/ARQ-585
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
Presume these 2 beans.xml files:
Production code: beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
</beans>
{code}
Test addition: test-beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
Now, for non-test runs (such as in the IDE or in production), only the beans.xml is
activated through weld and the test-only alternative should not be activated.
For test runs, the test-only alternative should be activated, yet the rest of the content
from beans.xml should be in there too.
So it should be merged to something like this:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
It would be nice if we do something like mergeAsResource(), shown in this example:
{code}
public static WebArchive createDeployment() {
WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class,
"guvnor-webapp-5.3.0-SNAPSHOT.war")
.importDirectory(new
File("target/guvnor-webapp-5.3.0-SNAPSHOT/"))
.as(WebArchive.class)
.mergeAsResource(new
File("target/test-classes/META-INF/test-beans.xml"),
"META-INF/beans.xml")
.addAsResource(new File("target/test-classes/"),
ArchivePaths.create(""))
.addAsLibraries(
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.resolveAsFiles(new ScopeFilter("test")));
return webArchive;
}
{code}
Because of maintenance, copying everything from beans.xml to test-beans.xml on every
change to beans.xml is NOT an option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:56 a.m.
New subject: [JBoss JIRA] (ARQ-585) Support for adding a beans-test.xml without discarding the original beans.xml or seam-beans.xml
[
https://issues.jboss.org/browse/ARQ-585?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet edited comment on ARQ-585 at 1/9/12 4:55 AM:
--------------------------------------------------------------
Good workaround:
There's a better way of making @Alternative usable for testing:
Don't use @Alternative, but use @Specializes. Just put the @Specializes bean only in
your test classpath and it will automatically replace the real bean. No need to mess
around with beans.xml.
Resolving this issue as "Deferred" because SHRINKDESC-6 will fix the
@Alternative case mostly. Reopen if you don't agree.
was (Author: ge0ffrey):
Good workaround:
There's a better way of making @Alternative usable for testing:
Don't use @Alternative, but use @Specializes. Just put the @Specializes bean only in
your test classpath and it will automatically replace the real bean. No need to mess
around with beans.xml.
Resolving this issue as "Won't fix" because SHRINKDESC-6 will fix the
@Alternative case mostly. Reopen if you don't agree.
Support for adding a beans-test.xml without discarding the original
beans.xml or seam-beans.xml
-----------------------------------------------------------------------------------------------
Key: ARQ-585
URL: https://issues.jboss.org/browse/ARQ-585
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
Presume these 2 beans.xml files:
Production code: beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
</beans>
{code}
Test addition: test-beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
Now, for non-test runs (such as in the IDE or in production), only the beans.xml is
activated through weld and the test-only alternative should not be activated.
For test runs, the test-only alternative should be activated, yet the rest of the content
from beans.xml should be in there too.
So it should be merged to something like this:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
It would be nice if we do something like mergeAsResource(), shown in this example:
{code}
public static WebArchive createDeployment() {
WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class,
"guvnor-webapp-5.3.0-SNAPSHOT.war")
.importDirectory(new
File("target/guvnor-webapp-5.3.0-SNAPSHOT/"))
.as(WebArchive.class)
.mergeAsResource(new
File("target/test-classes/META-INF/test-beans.xml"),
"META-INF/beans.xml")
.addAsResource(new File("target/test-classes/"),
ArchivePaths.create(""))
.addAsLibraries(
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.resolveAsFiles(new ScopeFilter("test")));
return webArchive;
}
{code}
Because of maintenance, copying everything from beans.xml to test-beans.xml on every
change to beans.xml is NOT an option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:58 a.m.
New subject: [JBoss JIRA] (ARQ-585) Support for adding a beans-test.xml without discarding the original beans.xml or seam-beans.xml
[
https://issues.jboss.org/browse/ARQ-585?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet edited comment on ARQ-585 at 1/9/12 4:56 AM:
--------------------------------------------------------------
Good workaround:
There's a better way of making @Alternative usable for testing:
Don't use @Alternative, but use @Specializes. Just put the @Specializes bean only in
your test classpath and it will automatically replace the real bean. No need to mess
around with beans.xml. Note: the weld manual could be clearer about @Alternative vs
@Specializes.
Resolving this issue as "Deferred" because SHRINKDESC-6 will fix the
@Alternative case mostly. Reopen if you don't agree.
was (Author: ge0ffrey):
Good workaround:
There's a better way of making @Alternative usable for testing:
Don't use @Alternative, but use @Specializes. Just put the @Specializes bean only in
your test classpath and it will automatically replace the real bean. No need to mess
around with beans.xml.
Resolving this issue as "Deferred" because SHRINKDESC-6 will fix the
@Alternative case mostly. Reopen if you don't agree.
Support for adding a beans-test.xml without discarding the original
beans.xml or seam-beans.xml
-----------------------------------------------------------------------------------------------
Key: ARQ-585
URL: https://issues.jboss.org/browse/ARQ-585
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
Presume these 2 beans.xml files:
Production code: beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
</beans>
{code}
Test addition: test-beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
Now, for non-test runs (such as in the IDE or in production), only the beans.xml is
activated through weld and the test-only alternative should not be activated.
For test runs, the test-only alternative should be activated, yet the rest of the content
from beans.xml should be in there too.
So it should be merged to something like this:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
It would be nice if we do something like mergeAsResource(), shown in this example:
{code}
public static WebArchive createDeployment() {
WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class,
"guvnor-webapp-5.3.0-SNAPSHOT.war")
.importDirectory(new
File("target/guvnor-webapp-5.3.0-SNAPSHOT/"))
.as(WebArchive.class)
.mergeAsResource(new
File("target/test-classes/META-INF/test-beans.xml"),
"META-INF/beans.xml")
.addAsResource(new File("target/test-classes/"),
ArchivePaths.create(""))
.addAsLibraries(
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.resolveAsFiles(new ScopeFilter("test")));
return webArchive;
}
{code}
Because of maintenance, copying everything from beans.xml to test-beans.xml on every
change to beans.xml is NOT an option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:25 p.m.
New subject: [JBoss JIRA] (ARQ-585) Support for adding a beans-test.xml without discarding the original beans.xml or seam-beans.xml
[
https://issues.jboss.org/browse/ARQ-585?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen closed ARQ-585.
-----------------------------
deferred
Support for adding a beans-test.xml without discarding the original
beans.xml or seam-beans.xml
-----------------------------------------------------------------------------------------------
Key: ARQ-585
URL: https://issues.jboss.org/browse/ARQ-585
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
Presume these 2 beans.xml files:
Production code: beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
</beans>
{code}
Test addition: test-beans.xml:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
Now, for non-test runs (such as in the IDE or in production), only the beans.xml is
activated through weld and the test-only alternative should not be activated.
For test runs, the test-only alternative should be activated, yet the rest of the content
from beans.xml should be in there too.
So it should be merged to something like this:
{code}
<beans xmlns="http://java.sun.com/xml/ns/javaee" ...>
<!-- 100 lines that change regularly during development -->
<alternatives>
<class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class>
</alternatives>
</beans>
{code}
It would be nice if we do something like mergeAsResource(), shown in this example:
{code}
public static WebArchive createDeployment() {
WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class,
"guvnor-webapp-5.3.0-SNAPSHOT.war")
.importDirectory(new
File("target/guvnor-webapp-5.3.0-SNAPSHOT/"))
.as(WebArchive.class)
.mergeAsResource(new
File("target/test-classes/META-INF/test-beans.xml"),
"META-INF/beans.xml")
.addAsResource(new File("target/test-classes/"),
ArchivePaths.create(""))
.addAsLibraries(
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.resolveAsFiles(new ScopeFilter("test")));
return webArchive;
}
{code}
Because of maintenance, copying everything from beans.xml to test-beans.xml on every
change to beans.xml is NOT an option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4439
days inactive
4675
days old
arquillian-issues@lists.jboss.org
14 comments
6 participants
participants (6)
-
Aslak Knutsen (JIRA) -
Geoffrey De Smet (Commented) (JIRA)
-
Geoffrey De Smet (Issue Comment Edited) (JIRA)
-
Geoffrey De Smet (JIRA)
-
Geoffrey De Smet (Resolved) (JIRA)
-
Geoffrey De Smet (Updated) (JIRA)