2012/8/31 Rohit Yadav :
> Hi Darren and everyone,
>
> What are the differences between Maven2 and Maven3?
Some performance improvement
Better handling handling of reactor
With the tomcat maven plugin, you can run tomcat7:run from the top
and all modules classes will be added to the tomcat classpath
> CS because the home page will come up even if the system is
>>completely
>> >> broken. One thing for CS is the context path must be /client, so you
>> >> can add /client but you'll see it still doesn't work (ie
>> >> login fails, and I'm not
Hi Darren and everyone,
What are the differences between Maven2 and Maven3?
And why we'll be using Maven2 other than the fact that it's widely popular,
understood and used?
I've put a wiki page that everyone can update/edit as we shift to maven:
https://cwiki.apache.org/confluence/display/CLOUDS
g for CS is the context path must be /client, so you
> >> can add /client but you'll see it still doesn't work (ie
> >> login fails, and I'm not sure where the logs are going to but from the
> >> browser you can see /client/api doesn't respond).
;>>
>>> BTW this need a mysql started locally
>>> I just wonder if you have think about running that with an embeded db
>>> (derby or hsql etc)
>>> Same for unit tests.
>>> ?
>>>
>>>>> 2) "mvn -Dnonoss -am -pl client jetty:run&q
27;t respond).
>
>Darren
>
>
>
>> ---- Original Message ----
>> Subject: Re: maven: latest patches and how to setup Eclipse/M2E/Jetty
>> From: Olivier Lamy
>> Date: Wed, August 29, 2012 9:59 am
>> To: cloudstack-dev@incubator.apache.org
>>
>>
>&g
lugin).
But you mean /client is mandatory ? (no use of contextPath ? )
I can't really test as I don't any mysql running :-)
>
> Darren
>
>
>
>> ---- Original Message
>> Subject: Re: maven: latest patches and how to setup Eclipse/M2E/Jetty
>> Fro
ogin fails, and I'm not sure where the logs are going to but from the
browser you can see /client/api doesn't respond).
Darren
> Original Message ----
> Subject: Re: maven: latest patches and how to setup Eclipse/M2E/Jetty
> From: Olivier Lamy
> Date: Wed, Aug
plugin to work right with multi-modules, I
>> always seem to need to run it as a standalone build.
>
> Maybe but tomcat7:run works great with multi modules :-)
>
>
>>
>>
>> Darren
>>
>>
>>
>>
>>> Original Message ---
Hugo,
I created https://reviews.apache.org/r/6829/ for this. Can you download
the patch and try it out?
Darren
> Original Message
> Subject: RE: maven: latest patches and how to setup Eclipse/M2E/Jetty
> From: "Darren Shepherd"
> Date: Wed, August
a dev setup is for the version to be random so
that it always copies the scripts and what not over.
Darren
> Original Message ----
> Subject: RE: maven: latest patches and how to setup Eclipse/M2E/Jetty
> From: Hugo Trippaers
> Date: Wed, August 29, 2012 8:48 am
33 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: maven: latest patches and how to setup Eclipse/M2E/Jetty
2012/8/29 Darren Shepherd :
> Olivier,
>
> You added the client module to the main pom.xml, but that break the
> profiles for the build. I created that pom mainly for the
On Wed, Aug 29, 2012 at 05:24:04AM -0400, Olivier Lamy wrote:
> 2012/8/29 Prasanna Santhanam :
> >> 4. Go to File->Import and then Import Existing *Maven* Project. Select
> >> the root of the git repo and it will find a bunch of projects. Import
> >> and then let maven download the internet and c
2012/8/29 Prasanna Santhanam :
>> 4. Go to File->Import and then Import Existing *Maven* Project. Select
>> the root of the git repo and it will find a bunch of projects. Import
>> and then let maven download the internet and compile everything. First
>> run will be very slow, but then fast ther
> 4. Go to File->Import and then Import Existing *Maven* Project. Select
> the root of the git repo and it will find a bunch of projects. Import
> and then let maven download the internet and compile everything. First
> run will be very slow, but then fast thereafter.
>
> You should now have al
& mvn jetty:run" for some reason.
> I've never gotten the jetty plugin to work right with multi-modules, I
> always seem to need to run it as a standalone build.
Maybe but tomcat7:run works great with multi modules :-)
>
>
> Darren
>
>
>
>
>>
to run it as a standalone build.
Darren
> -------- Original Message --------
> Subject: Re: maven: latest patches and how to setup Eclipse/M2E/Jetty
> From: Olivier Lamy
> Date: Tue, August 28, 2012 3:10 pm
> To: cloudstack-dev@incubator.apache.org
>
>
> merged.
>
merged.
Added configuration for using tomcat maven plugin too.
from README.md:
to run webapp client:
mvn org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1:run -pl
:cloud-client-ui -am
then hit: http://localhost:8080/cloud-client-ui/
or add in your ~/.m2/settings.xml
org.apache.tomcat.
Hi,
I will take care of that.
2012/8/28 Darren Shepherd :
>
> For whatever reason, my patches on review board never seem to work. I
> just do "git format-patch --stdout origin/master" but then review board
> just throws an error when I upload the patch. Regardless, can a
> committer pull the bra
For whatever reason, my patches on review board never seem to work. I
just do "git format-patch --stdout origin/master" but then review board
just throws an error when I upload the patch. Regardless, can a
committer pull the branch "maven-final" from
https://github.com/ibuildthecloud/incubator-c
20 matches
Mail list logo
