Thanks Wayne, really useful explanations. I already had googled a bit
about this but, as always, one cannot expect to find good examples or
practices out there and I have a high respect for this list opinions,
specially about "the maven way" which I see now again and again ends up
always with l
Hi folks,
using 3.0.3.
I'm in the process of creating a test module for my multi-module web
project, to perform integration tests.
I have a fairly standard setup, a WAR-type module depending on several
other modules. I have some classes I want to test residing on the WAR
and some in other m
You could deploy in place or unpacked or something similar, there is
more than one way to deploy or test your webapp without it having to be
packed into the WAR, which is what takes most of the build time for us too.
Em 13-05-2011 01:42, Ron Wheeler escreveu:
On 12/05/2011 12:53 PM, javadaisy
Em 12-05-2011 12:02, Tim Pizey escreveu:
On 12 May 2011 11:50, Alex Lopez wrote:
Em 12-05-2011 01:22, Andrew Robinson escreveu:
I have been using maven 2.2.1 for a while at my company and we just
switched
to maven 3. I have rebuilt my computer (ubuntu maverick 10.04 32-bit ==>
ubu
circumstances wouldn't end mvn process, instead forcing it to
continue?
Em 12-05-2011 11:50, Alex Lopez escreveu:
Em 12-05-2011 01:22, Andrew Robinson escreveu:
I have been using maven 2.2.1 for a while at my company and we just
switched
to maven 3. I have rebuilt my computer (ubuntu maverick
Em 12-05-2011 01:22, Andrew Robinson escreveu:
I have been using maven 2.2.1 for a while at my company and we just switched
to maven 3. I have rebuilt my computer (ubuntu maverick 10.04 32-bit ==>
ubuntu natty 11.04 64-bit) and installed maven 3.
In maven 3.0.3, (I have not seen it with maven 2
never a good idea to commit the target dir IMO...
Em 09-05-2011 15:42, Refr Bruhl escreveu:
Team
I've an issue with the m2 plugin using maven in conjunction with subversion.
Since this crosses three platforms I thought I would try both the subversion and
maven list to see if anyone has run acr
You could check out the books freely available in sonatype website
(books section), maven reference and maven by example, these really
helped me a lot to understand whan a multi-module/reactor project is and
how to arrange a good structure for it (ie separate inheritance from
modularity etc)
Have you tried with maven-site-plugin 3.0-beta-3 ?
Also I don't remember why exaclty, I've got
attach-descriptor
might
be plenty of ways ;)
Em 13-04-2011 15:44, Fernando Wermus escreveu:
Alex,
I understand your proposal. Do I need to create two proyects for this
situation or could I avoid this?
2011/4/13 Alex Lopez
Make the classes into different jars (java 1.4 and 1.6) and add one ore the
oth
Make the classes into different jars (java 1.4 and 1.6) and add one ore
the other as dependencies under different profiles.
Em 13-04-2011 15:01, Fernando Wermus escreveu:
Hi all,
We have a proyect which we need to compile under java 1.4 for some
companies and 1.6 for other companies. The p
BTW the "mvn install" or "mvn deploy" is done in our case on the top
directory, the reactor one, and it gets propagated to the others in
appropriate order by the reactor module.
Em 07-04-2011 11:16, Alex Lopez escreveu:
I don't think I can post the full thing, bu
This is an example multi-module project with separate war, reactor and
parent poms
Em 07-04-2011 11:16, Alex Lopez escreveu:
I don't think I can post the full thing, but I'll post some cut down
version so you can make an idea.
BTW, I got the idea from the documentation on sonatype
27;d
really like to see a working example of this in action.
Cheers,
Adam
On 7 April 2011 09:51, Alex Lopez wrote:
Here we have a similar setup, we manage to build everything into a WAR
including dependent jars using reactor/assembly project:
BTW, we use separate poms for parent (inheritance)
Here we have a similar setup, we manage to build everything into a WAR
including dependent jars using reactor/assembly project:
BTW, we use separate poms for parent (inheritance) and reactor
(multi-module), which I think makes sense as all sub-modules have the
parent as parent but not one sub-
Jaina,
if maven works in another machine it might be some configuration either in:
- Your settings.xml file ~/.m2/settings.xml
- Maven's global settings.xml under maven's install dir {$M2_HOME}/conf
- Other files under Maven installation dir
- M2Eclipse configuration (Preferences->Maven)
Alex
16 matches
Mail list logo