Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: Hugo Trippaers <HTrippaers@schubergphilis.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Subject: RE: maven: latest patches and how to setup Eclipse/M2E/Jetty
Thread-Topic: maven: latest patches and how to setup Eclipse/M2E/Jetty
Thread-Index: AQHNhXeWj1CMWZ+/1EKZ9+2haXoNLZdwIyaAgADMUEA=
Date: Wed, 29 Aug 2012 15:48:30 +0000
Message-ID: <6DE00C9FDF08A34683DF71786C70EBF029B03F57@SBPOMB402.sbp.lan>
References: 
 <20120828164813.d3d18d9a633cb81ed61112bf108fc615.7b05be1cad.wbe@email00.secureserver.net>
 <CAPoyBqSR8g4AVxeJCzOhN5_erEhZXwcdqaN+LhGy3HdvaQyULQ@mail.gmail.com>
In-Reply-To: 
 <CAPoyBqSR8g4AVxeJCzOhN5_erEhZXwcdqaN+LhGy3HdvaQyULQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Heya,

I'm running into some problems with the jetty:run directly from eclipse. Ev=
erything starts fine, except that the code depends on 'getImplementationVer=
sion()' at various points. (See CitrixResourceBase:5452 for example )

When running with jetty this returns null and that will subsequently cause =
the initialization of a Xen hypervisor to fail as the version field for the=
 HostVO can't be null in the database.

Any way to work around this?

Cheers,

Hugo

-----Original Message-----
From: Olivier Lamy [mailto:olamy@apache.org]=20
Sent: Wednesday, August 29, 2012 7: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 <darren@godaddy.com>:
> Olivier,
>
> You added the client module to the main pom.xml, but that break the=20
> profiles for the build.  I created that pom mainly for the jetty:run,=20
> but it depends on all the non-oss stuff and doesn't respect the=20
> profiles to not depend on them when the profiles aren't activated. =20
> While it would be great to have the client pom switch its deps based=20
> on the profiles, it doesn't matter because at runtime because the=20
> components.xml for CS refers to all the non-oss stuff.
>
> So I purposely left the client module out of the main build for two=20
> reasons.
>
> 1) It doesn't respect the profiles
Good reason. I will check that.
> 2) "mvn -Dnonoss -am -pl client jetty:run" doesn't seem to work.  You=20
> have to do
>   "mvn -Dnonoss install && cd client && mvn jetty:run" for some reason.
> I've never gotten the jetty plugin to work right with multi-modules, I=20
> always seem to need to run it as a standalone build.

Maybe but tomcat7:run works great with multi modules :-)


>
>
> Darren
>
>
>
>
>> -------- Original Message --------
>> Subject: Re: maven: latest patches and how to setup Eclipse/M2E/Jetty
>> From: Olivier Lamy <olamy@apache.org>
>> Date: Tue, August 28, 2012 3:10 pm
>> To: cloudstack-dev@incubator.apache.org
>>
>>
>> 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=20
>> :cloud-client-ui -am then hit: http://localhost:8080/cloud-client-ui/
>> or add in your ~/.m2/settings.xml
>>   <pluginGroups>
>>     <pluginGroup>org.apache.tomcat.maven</pluginGroup>
>>   </pluginGroups>
>> and save your fingers with mvn tomcat7:run -pl :cloud-client-ui -am
>>
>>
>> 2012/8/28 Olivier Lamy <olamy@apache.org>:
>> > Hi,
>> > I will take care of that.
>> >
>> > 2012/8/28 Darren Shepherd <darren@godaddy.com>:
>> >>
>> >> For whatever reason, my patches on review board never seem to=20
>> >> work.  I just do "git format-patch --stdout origin/master" but=20
>> >> then review board just throws an error when I upload the patch. =20
>> >> Regardless, can a committer pull the branch "maven-final" from=20
>> >> https://github.com/ibuildthecloud/incubator-cloudstack.git and=20
>> >> merge to master?
>> >>
>> >> Included in the branch is the following:
>> >>
>> >>
>> >> * Add resources to jars - There was a bunch of random files like=20
>> >> keystores and such that were missing from the maven built jars
>> >>
>> >> * Added profiles for non-oss stuff - The following maven profiles=20
>> >> are available to build the non-oss stuff: kvm, f5, netscaler, srx,=20
>> >> netapp, vmware.  To include those components in the build just put=20
>> >> "-Pvmware,kvm" or whatever component you want.  You can also do=20
>> >> "mvn -Dnonoss=3Dtrue" to include all of them.
>> >>
>> >> * Added deps/install-non-oss.sh - This script will install the=20
>> >> nonoss jars into your local repo so that you don't have to use my=20
>> >> private repo anymore
>> >>
>> >> * jetty:run support and a corresponding Eclipse launch config -=20
>> >> This feature is really, really convenient for development.  Refer=20
>> >> to below for more info.
>> >>
>> >>
>> >> If you want to setup your development environment to be based on=20
>> >> Eclipse and Maven and not the ant stuff then do the following=20
>> >> (after you have pulled my changes):
>> >>
>> >> 1. If you have existing Eclipse projects, delete them all.
>> >> 2. Delete all .classpath, .project, and .settings files (ie "find .
>> >> -name .classpath -o -name .project -o -name .settings -exec rm -rf=20
>> >> {} \; -print" ) 3. Install M2E Eclipse.  If your running Indigo or=20
>> >> Juno M2E is an official Eclipse foundation project.  If your=20
>> >> running Helios or older its a separate plugin that google knows=20
>> >> the location of (but honestly just upgrade to Indigo.  Not Juno,=20
>> >> I've found it to be really slow).  So in Indigo/Juno just go to=20
>> >> Help->Install New Software and put m2e in the filter and you'll=20
>> >> find it.
>> >> 4. Go to File->Import and then Import Existing *Maven* Project. =20
>> >> Select the root of the git repo and it will find a bunch of=20
>> >> projects.  Import and then let maven download the internet and=20
>> >> compile everything.  First run will be very slow, but then fast there=
after.
>> >>
>> >> You should now have all your compiling cloudstack projects.  If=20
>> >> you get issues regarding compiling the vmware, f5, then run=20
>> >> deps/install-non-oss.sh to install the non-oss stuff.  Now the=20
>> >> awesome part (assuming the previous steps worked).
>> >>
>> >> 5. Go back to File->Import, Import Existing *Maven* Project and=20
>> >> select the {git.root}/client folder and import.
>> >> 6. Go to Run->Debug Configurations... on the left you should see=20
>> >> Maven
>> >> Build-> cloudstack-ui.  Click that and magic will ensue.  That=20
>> >> Build-> will run
>> >> cloudstack in a jetty instance which should be accessible at=20
>> >> http://localhost:8080/client.  So now you can just edit code and=20
>> >> click run and it will launch it in Eclipse with debugging and all=20
>> >> the hotswapping magic the JVM provides.  It assumes your DB is at loc=
alhost.
>> >>  If your DB is elsewhere, then edit=20
>> >> ${git.root}/build/replace.properties
>> >> appropriately.
>> >>
>> >> Adios,
>> >> Darren
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > Olivier Lamy
>> > Talend: http://coders.talend.com
>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy


--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy