On 31/12/2010 4:27 PM, Steve Cohen wrote:
No. Sorry. But thanks.
I thought I'd struck gold with that appassembler thing and by the time
I figured out that I hadn't I had forgotten all about your sample.
Now that I look at it, it seems that what you are doing and what I am
doing are not tha
On Sat, Jan 1, 2011 at 12:22 AM, Steve Cohen wrote:
> Well, all I can say is that I was doing approximately as you have described
> and it didn't really work.
>
> I was using assembly:assembly (single for some reason failed to bring in
> everything needed - perhaps the mistake was mine), I also us
No. Sorry. But thanks.
I thought I'd struck gold with that appassembler thing and by the time I
figured out that I hadn't I had forgotten all about your sample.
Now that I look at it, it seems that what you are doing and what I am
doing are not that different. And your example shows the us
Did you try the POM and assembly that I sent you?
It is pretty straightforward.
Ron
On 31/12/2010 2:47 PM, Steve Cohen wrote:
Yes, you are basically right. You can't get away from the need of the
aggregator project. And the dual testing was caused by specifying too
many phases on the command
Yes, you are basically right. You can't get away from the need of the
aggregator project. And the dual testing was caused by specifying too
many phases on the command line.
I was overly exuberant in my earlier praise of appassembler. It
appeared to do what I want, but the way I had it set u
http://blog.artifact-software.com/tech/?p=58
This may help with the discussion about how to deal with the separation
of deployment from development which is the key to solving a good chunk
of your problem.
Ron
On 31/12/2010 10:39 AM, Mr Rocks wrote:
I have a Maven project organized like
Never do anything interesting in a aggregate project (what I think
you're calling an uber-project). Make a separate leaf project, listed
last in the list of modules, to run assembly:single.
On Fri, Dec 31, 2010 at 8:52 AM, Steve Cohen wrote:
> Well, all I can say is that I was doing approximate
> My other thought is that I should simply use the assembly plugin to create a
> compressed file of all the configurations and then have the application server
> use the appropriate subset of those configuration files by adding it to the
> class path at runtime. This is desirable because I would o
I have a Maven project organized like this:
parentProj
supportingJar
first-web-app-war
second-web-app-war
second-web-app-packaged-as-ear
third-web-app
The 3 web applications are all deployed on different application servers and
machines (2 Tomcat as war, 1 WebSphere as ear).
Install implies package.
If you run
mvn clean install package
Yoyr tests will run twicr because you asked maven to run them twice
Also you should be binding assembly: single to tgen lifecycle, not invoking
directly
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random
Well, all I can say is that I was doing approximately as you have
described and it didn't really work.
I was using assembly:assembly (single for some reason failed to bring in
everything needed - perhaps the mistake was mine), I also used a
separate uber-project to do nothing but the assembly.
11 matches
Mail list logo
