9:10 p.m.
create an essential build profile to make build more approachable
-----------------------------------------------------------------
Key: ARQ-297
URL: https://jira.jboss.org/browse/ARQ-297
Project: Arquillian
Issue Type: Feature Request
Components: Build Infrastructure
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Newcomers are struggling to build Arquillian for the first time because the default
profile steps into all the container modules. This results in massive downloads (JBoss AS
embedded, GlassFish embedded, etc), slow build processes and frequent failures. A newcomer
to Arquillian shouldn't have to go through this whole parade. They really just want to
build the essential bits of Arquillian, then hand pick the container module they want to
study or hack.
To cut down on the default build, we should introduce a new profile in the aggregator pom
that is activated by default. (Hudson can be set to run with -Pall)
<profile>
<id>essential</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>build</module>
<module>api</module>
<module>spi</module>
<module>impl-base</module>
<module>junit</module>
<module>testng</module>
<module>testenrichers</module>
<module>protocols</module>
</modules>
</profile>
(I should note that Thomas already did a similar thing to isolate the Arquillian
essentials to work on OSGi, but that build profile could be replaced with this one, give
or take a module or two).
--
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:10 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-297) add an essential build profile to make build more approachable
[
https://jira.jboss.org/browse/ARQ-297?page=com.atlassian.jira.plugin.syst...
]
Dan Allen updated ARQ-297:
--------------------------
Summary: add an essential build profile to make build more approachable (was: create
an essential build profile to make build more approachable)
add an essential build profile to make build more approachable
--------------------------------------------------------------
Key: ARQ-297
URL: https://jira.jboss.org/browse/ARQ-297
Project: Arquillian
Issue Type: Feature Request
Components: Build Infrastructure
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Newcomers are struggling to build Arquillian for the first time because the default
profile steps into all the container modules. This results in massive downloads (JBoss AS
embedded, GlassFish embedded, etc), slow build processes and frequent failures. A newcomer
to Arquillian shouldn't have to go through this whole parade. They really just want to
build the essential bits of Arquillian, then hand pick the container module they want to
study or hack.
To cut down on the default build, we should introduce a new profile in the aggregator pom
that is activated by default. (Hudson can be set to run with -Pall)
<profile>
<id>essential</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>build</module>
<module>api</module>
<module>spi</module>
<module>impl-base</module>
<module>junit</module>
<module>testng</module>
<module>testenrichers</module>
<module>protocols</module>
</modules>
</profile>
(I should note that Thomas already did a similar thing to isolate the Arquillian
essentials to work on OSGi, but that build profile could be replaced with this one, give
or take a module or two).
--
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:28 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-297) add an essential build profile to make build more approachable
[
https://jira.jboss.org/browse/ARQ-297?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen commented on ARQ-297:
-----------------------------------
What Thomas did could be replaced with:
mvn clean install -pl container/osgi-embedded/,containers/osgi-remote -am
The same goes for the ppl that are interested in only one container:
mvn clean install -pl containers/jbossas-remote-6,junit -am
add an essential build profile to make build more approachable
--------------------------------------------------------------
Key: ARQ-297
URL: https://jira.jboss.org/browse/ARQ-297
Project: Arquillian
Issue Type: Feature Request
Components: Build Infrastructure
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Newcomers are struggling to build Arquillian for the first time because the default
profile steps into all the container modules. This results in massive downloads (JBoss AS
embedded, GlassFish embedded, etc), slow build processes and frequent failures. A newcomer
to Arquillian shouldn't have to go through this whole parade. They really just want to
build the essential bits of Arquillian, then hand pick the container module they want to
study or hack.
To cut down on the default build, we should introduce a new profile in the aggregator pom
that is activated by default. (Hudson can be set to run with -Pall)
<profile>
<id>essential</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>build</module>
<module>api</module>
<module>spi</module>
<module>impl-base</module>
<module>junit</module>
<module>testng</module>
<module>testenrichers</module>
<module>protocols</module>
</modules>
</profile>
(I should note that Thomas already did a similar thing to isolate the Arquillian
essentials to work on OSGi, but that build profile could be replaced with this one, give
or take a module or two).
--
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:30 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-297) add an essential build profile to make build more approachable
[
https://jira.jboss.org/browse/ARQ-297?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen commented on ARQ-297:
-----------------------------------
Not that I'm against a container free build, just saying.. :)
add an essential build profile to make build more approachable
--------------------------------------------------------------
Key: ARQ-297
URL: https://jira.jboss.org/browse/ARQ-297
Project: Arquillian
Issue Type: Feature Request
Components: Build Infrastructure
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Newcomers are struggling to build Arquillian for the first time because the default
profile steps into all the container modules. This results in massive downloads (JBoss AS
embedded, GlassFish embedded, etc), slow build processes and frequent failures. A newcomer
to Arquillian shouldn't have to go through this whole parade. They really just want to
build the essential bits of Arquillian, then hand pick the container module they want to
study or hack.
To cut down on the default build, we should introduce a new profile in the aggregator pom
that is activated by default. (Hudson can be set to run with -Pall)
<profile>
<id>essential</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>build</module>
<module>api</module>
<module>spi</module>
<module>impl-base</module>
<module>junit</module>
<module>testng</module>
<module>testenrichers</module>
<module>protocols</module>
</modules>
</profile>
(I should note that Thomas already did a similar thing to isolate the Arquillian
essentials to work on OSGi, but that build profile could be replaced with this one, give
or take a module or two).
--
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
11:54 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-297) add an essential build profile to make build more approachable
[
https://jira.jboss.org/browse/ARQ-297?page=com.atlassian.jira.plugin.syst...
]
Pete Muir commented on ARQ-297:
-------------------------------
I would advise against removing tests from the default build - sounds like a recipe for
people forgetting to run tests! Why not just add a few profiles to make it easier to
select what you do/don't want e.g.
mvn install # builds everything
mvn install -P!containers # builds everything except containers
mvn install -P!containers,jboss-containers # builds everything except non-jboss
containers
add an essential build profile to make build more approachable
--------------------------------------------------------------
Key: ARQ-297
URL: https://jira.jboss.org/browse/ARQ-297
Project: Arquillian
Issue Type: Feature Request
Components: Build Infrastructure
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Newcomers are struggling to build Arquillian for the first time because the default
profile steps into all the container modules. This results in massive downloads (JBoss AS
embedded, GlassFish embedded, etc), slow build processes and frequent failures. A newcomer
to Arquillian shouldn't have to go through this whole parade. They really just want to
build the essential bits of Arquillian, then hand pick the container module they want to
study or hack.
To cut down on the default build, we should introduce a new profile in the aggregator pom
that is activated by default. (Hudson can be set to run with -Pall)
<profile>
<id>essential</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>build</module>
<module>api</module>
<module>spi</module>
<module>impl-base</module>
<module>junit</module>
<module>testng</module>
<module>testenrichers</module>
<module>protocols</module>
</modules>
</profile>
(I should note that Thomas already did a similar thing to isolate the Arquillian
essentials to work on OSGi, but that build profile could be replaced with this one, give
or take a module or two).
--
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:11 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-297) add an essential build profile to make build more approachable
[
https://jira.jboss.org/browse/ARQ-297?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen commented on ARQ-297:
-----------------------------------
instead of making profiles that are special to our build that needs documentation to be
used anyway, why not just 'teach' the user/devs about the features that are in the
build system we use, e.g. -pl -am.
the containers will be moved out of the Arquillian build in time..
add an essential build profile to make build more approachable
--------------------------------------------------------------
Key: ARQ-297
URL: https://jira.jboss.org/browse/ARQ-297
Project: Arquillian
Issue Type: Feature Request
Components: Build Infrastructure
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Newcomers are struggling to build Arquillian for the first time because the default
profile steps into all the container modules. This results in massive downloads (JBoss AS
embedded, GlassFish embedded, etc), slow build processes and frequent failures. A newcomer
to Arquillian shouldn't have to go through this whole parade. They really just want to
build the essential bits of Arquillian, then hand pick the container module they want to
study or hack.
To cut down on the default build, we should introduce a new profile in the aggregator pom
that is activated by default. (Hudson can be set to run with -Pall)
<profile>
<id>essential</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>build</module>
<module>api</module>
<module>spi</module>
<module>impl-base</module>
<module>junit</module>
<module>testng</module>
<module>testenrichers</module>
<module>protocols</module>
</modules>
</profile>
(I should note that Thomas already did a similar thing to isolate the Arquillian
essentials to work on OSGi, but that build profile could be replaced with this one, give
or take a module or two).
--
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:11 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-297) add an essential build profile to make build more approachable
[
https://jira.jboss.org/browse/ARQ-297?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen edited comment on ARQ-297 at 9/16/10 7:11 AM:
------------------------------------------------------------
instead of making profiles that are special to our build that needs documentation to be
used anyway, why not just 'teach' the user/devs about the features that are in the
build system we use, e.g. -pl -am.
the containers will be moved out of the Arquillian build at some point..
was (Author: aslak):
instead of making profiles that are special to our build that needs documentation to
be used anyway, why not just 'teach' the user/devs about the features that are in
the build system we use, e.g. -pl -am.
the containers will be moved out of the Arquillian build in time..
add an essential build profile to make build more approachable
--------------------------------------------------------------
Key: ARQ-297
URL: https://jira.jboss.org/browse/ARQ-297
Project: Arquillian
Issue Type: Feature Request
Components: Build Infrastructure
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Newcomers are struggling to build Arquillian for the first time because the default
profile steps into all the container modules. This results in massive downloads (JBoss AS
embedded, GlassFish embedded, etc), slow build processes and frequent failures. A newcomer
to Arquillian shouldn't have to go through this whole parade. They really just want to
build the essential bits of Arquillian, then hand pick the container module they want to
study or hack.
To cut down on the default build, we should introduce a new profile in the aggregator pom
that is activated by default. (Hudson can be set to run with -Pall)
<profile>
<id>essential</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>build</module>
<module>api</module>
<module>spi</module>
<module>impl-base</module>
<module>junit</module>
<module>testng</module>
<module>testenrichers</module>
<module>protocols</module>
</modules>
</profile>
(I should note that Thomas already did a similar thing to isolate the Arquillian
essentials to work on OSGi, but that build profile could be replaced with this one, give
or take a module or two).
--
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:24 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-297) add an essential build profile to make build more approachable
[
https://jira.jboss.org/browse/ARQ-297?page=com.atlassian.jira.plugin.syst...
]
Pete Muir commented on ARQ-297:
-------------------------------
I would certainly prefer that, than disabling them by default.
add an essential build profile to make build more approachable
--------------------------------------------------------------
Key: ARQ-297
URL: https://jira.jboss.org/browse/ARQ-297
Project: Arquillian
Issue Type: Feature Request
Components: Build Infrastructure
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Newcomers are struggling to build Arquillian for the first time because the default
profile steps into all the container modules. This results in massive downloads (JBoss AS
embedded, GlassFish embedded, etc), slow build processes and frequent failures. A newcomer
to Arquillian shouldn't have to go through this whole parade. They really just want to
build the essential bits of Arquillian, then hand pick the container module they want to
study or hack.
To cut down on the default build, we should introduce a new profile in the aggregator pom
that is activated by default. (Hudson can be set to run with -Pall)
<profile>
<id>essential</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>build</module>
<module>api</module>
<module>spi</module>
<module>impl-base</module>
<module>junit</module>
<module>testng</module>
<module>testenrichers</module>
<module>protocols</module>
</modules>
</profile>
(I should note that Thomas already did a similar thing to isolate the Arquillian
essentials to work on OSGi, but that build profile could be replaced with this one, give
or take a module or two).
--
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
7:26 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-297) add an essential build profile to make build more approachable
[
https://jira.jboss.org/browse/ARQ-297?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-297:
-------------------------------
Great, if we can provide a command that is just as concise as one that would activate a
specialized profile, then I'm all for it. This is just a matter of communication then.
I see newcomers struggle to build the containers every week and I just don't want that
to be their first memory of Arquillian.
Teaching the developer about the features in the build system is something that's more
of a long-term goal. What we need for newcomers is a simple instruction in the form of a
command, as Pete suggested:
mvn install -P!containers # builds everything except containers
I need to update the build docs anyway, so I'll link this issue to that one.
add an essential build profile to make build more approachable
--------------------------------------------------------------
Key: ARQ-297
URL: https://jira.jboss.org/browse/ARQ-297
Project: Arquillian
Issue Type: Feature Request
Components: Build Infrastructure
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Newcomers are struggling to build Arquillian for the first time because the default
profile steps into all the container modules. This results in massive downloads (JBoss AS
embedded, GlassFish embedded, etc), slow build processes and frequent failures. A newcomer
to Arquillian shouldn't have to go through this whole parade. They really just want to
build the essential bits of Arquillian, then hand pick the container module they want to
study or hack.
To cut down on the default build, we should introduce a new profile in the aggregator pom
that is activated by default. (Hudson can be set to run with -Pall)
<profile>
<id>essential</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>build</module>
<module>api</module>
<module>spi</module>
<module>impl-base</module>
<module>junit</module>
<module>testng</module>
<module>testenrichers</module>
<module>protocols</module>
</modules>
</profile>
(I should note that Thomas already did a similar thing to isolate the Arquillian
essentials to work on OSGi, but that build profile could be replaced with this one, give
or take a module or two).
--
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
11:16 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-297) add an essential build profile to make build more approachable
[
https://jira.jboss.org/browse/ARQ-297?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen commented on ARQ-297:
-----------------------------------
To build a specific container, the test framework and all their deps in one go:
mvn install -pl containers/jbossas-remote-6,junit -am
mvn install -pl containers/jbossas-remote-6,testng -am
mvn install -pl containers/weld-se-embedded-1,junit -am
etc etc
Build Arquillian core:
mvn install -pl impl-base/ -am
Build a TestFramework integration pluss Core.
mvn install -pl junit -am
mvn install -pl testng -am
add an essential build profile to make build more approachable
--------------------------------------------------------------
Key: ARQ-297
URL: https://jira.jboss.org/browse/ARQ-297
Project: Arquillian
Issue Type: Feature Request
Components: Build Infrastructure
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Newcomers are struggling to build Arquillian for the first time because the default
profile steps into all the container modules. This results in massive downloads (JBoss AS
embedded, GlassFish embedded, etc), slow build processes and frequent failures. A newcomer
to Arquillian shouldn't have to go through this whole parade. They really just want to
build the essential bits of Arquillian, then hand pick the container module they want to
study or hack.
To cut down on the default build, we should introduce a new profile in the aggregator pom
that is activated by default. (Hudson can be set to run with -Pall)
<profile>
<id>essential</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>build</module>
<module>api</module>
<module>spi</module>
<module>impl-base</module>
<module>junit</module>
<module>testng</module>
<module>testenrichers</module>
<module>protocols</module>
</modules>
</profile>
(I should note that Thomas already did a similar thing to isolate the Arquillian
essentials to work on OSGi, but that build profile could be replaced with this one, give
or take a module or two).
--
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
11:30 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-297) add an essential build profile to make build more approachable
[
https://jira.jboss.org/browse/ARQ-297?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-297:
-------------------------------
I've updated the build page accordingly:
https://www.jboss.org/arquillian/build.html
We may need a docs update too (I can't remember if we have build instructions there).
Should we still move forward with creating some basic profiles? Do we want to get rid of
the OSGi profile?
add an essential build profile to make build more approachable
--------------------------------------------------------------
Key: ARQ-297
URL: https://jira.jboss.org/browse/ARQ-297
Project: Arquillian
Issue Type: Feature Request
Components: Build Infrastructure
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Newcomers are struggling to build Arquillian for the first time because the default
profile steps into all the container modules. This results in massive downloads (JBoss AS
embedded, GlassFish embedded, etc), slow build processes and frequent failures. A newcomer
to Arquillian shouldn't have to go through this whole parade. They really just want to
build the essential bits of Arquillian, then hand pick the container module they want to
study or hack.
To cut down on the default build, we should introduce a new profile in the aggregator pom
that is activated by default. (Hudson can be set to run with -Pall)
<profile>
<id>essential</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>build</module>
<module>api</module>
<module>spi</module>
<module>impl-base</module>
<module>junit</module>
<module>testng</module>
<module>testenrichers</module>
<module>protocols</module>
</modules>
</profile>
(I should note that Thomas already did a similar thing to isolate the Arquillian
essentials to work on OSGi, but that build profile could be replaced with this one, give
or take a module or two).
--
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
8:01 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-297) add an essential build profile to make build more approachable
[
https://jira.jboss.org/browse/ARQ-297?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen commented on ARQ-297:
-----------------------------------
personally i would say no compile profiles, and remove the OSGi one.
add an essential build profile to make build more approachable
--------------------------------------------------------------
Key: ARQ-297
URL: https://jira.jboss.org/browse/ARQ-297
Project: Arquillian
Issue Type: Feature Request
Components: Build Infrastructure
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Fix For: 1.0.0.Beta1
Newcomers are struggling to build Arquillian for the first time because the default
profile steps into all the container modules. This results in massive downloads (JBoss AS
embedded, GlassFish embedded, etc), slow build processes and frequent failures. A newcomer
to Arquillian shouldn't have to go through this whole parade. They really just want to
build the essential bits of Arquillian, then hand pick the container module they want to
study or hack.
To cut down on the default build, we should introduce a new profile in the aggregator pom
that is activated by default. (Hudson can be set to run with -Pall)
<profile>
<id>essential</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>build</module>
<module>api</module>
<module>spi</module>
<module>impl-base</module>
<module>junit</module>
<module>testng</module>
<module>testenrichers</module>
<module>protocols</module>
</modules>
</profile>
(I should note that Thomas already did a similar thing to isolate the Arquillian
essentials to work on OSGi, but that build profile could be replaced with this one, give
or take a module or two).
--
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:15 p.m.
New subject: [JBoss JIRA] Closed: (ARQ-297) add an essential build profile to make build more approachable
[
https://issues.jboss.org/browse/ARQ-297?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen closed ARQ-297.
-----------------------------
Assignee: Aslak Knutsen
Resolution: Won't Fix
Fixed by ARQ-361
add an essential build profile to make build more approachable
--------------------------------------------------------------
Key: ARQ-297
URL: https://issues.jboss.org/browse/ARQ-297
Project: Arquillian
Issue Type: Feature Request
Components: Build Infrastructure
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Beta1
Newcomers are struggling to build Arquillian for the first time because the default
profile steps into all the container modules. This results in massive downloads (JBoss AS
embedded, GlassFish embedded, etc), slow build processes and frequent failures. A newcomer
to Arquillian shouldn't have to go through this whole parade. They really just want to
build the essential bits of Arquillian, then hand pick the container module they want to
study or hack.
To cut down on the default build, we should introduce a new profile in the aggregator pom
that is activated by default. (Hudson can be set to run with -Pall)
<profile>
<id>essential</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>build</module>
<module>api</module>
<module>spi</module>
<module>impl-base</module>
<module>junit</module>
<module>testng</module>
<module>testenrichers</module>
<module>protocols</module>
</modules>
</profile>
(I should note that Thomas already did a similar thing to isolate the Arquillian
essentials to work on OSGi, but that build profile could be replaced with this one, give
or take a module or two).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4811
days inactive
5035
days old
arquillian-issues@lists.jboss.org
12 comments
3 participants
participants (3)
-
Aslak Knutsen (JIRA) -
Dan Allen (JIRA)
-
Pete Muir (JIRA)