Let's suppose I have main GUI program with lots of dependencies and some
unit tests. Maven will run my unit tests just fine. But suppose I want
to run the main program and try my GUI out -- maybe run a manual test of
the GUI.
How do I do this with maven?
I've seen it done in the sample code
Might this do the trick?
http://mojo.codehaus.org/exec-maven-plugin/java-mojo.html
On Apr 10, 2011 2:32 PM, siegfr...@heintze.com wrote:
Let's suppose I have main GUI program with lots of dependencies and some
unit tests. Maven will run my unit tests just fine. But suppose I want
to run the
On Sat, Apr 9, 2011 at 7:54 PM, Jörg Schaible joerg.schai...@gmx.de wrote:
Ludwig Magnusson wrote:
Hello!
I know that the maven-eclipse-plugin somehow can figure out that a
dependency actually exists as a project in workspace and therefore add
that project to the build path instead of
Howdy,
I want to be able to check that the MDB's created actually execute and
behave as expected.
For reference, the EE5 tutorial (
http://download.oracle.com/javaee/5/tutorial/doc/bnbpq.html) covers two
equivalent tests :
- *Building, Deploying, and Running the simplemessage Application
Hi!
I wrote a little about integration testing an EJB a while ago. It
doesn't test an MDB, but it builds a Stateless ejb, deploys it on a
JBoss and tests it. It could perhaps be used as a hint for you and how
to solve your problem.
But when I do mvn install on the multiprojet then I will get a
JAR but when doing mvn site on the multiproject I get
target/classes.
That seems to be the opposite to what you have described?
/Lucas
On 04/08/2011 07:52 PM, Brian Fox
Only some jars contains API meant to be used by customers. No
point in having Javadoc for internal code, that will be confusing
for the customer.
For our internal use we are using Eclipse and having "projects
dependencies" in the .classpath file instead
