Yes , Mike's right . That command would help you copy your UI changes to the 
server and then you just need to refresh your browser for your changes to 
reflect on the CloudStack UI .

The active destination where the code gets copied is  - cloudstack/ 
client/target/cloud-client-Snapshot-4.2.0 /scripts/

Within the scripts folder , you'll see all the javascripts files which are 
loaded by the browser .

Hope this helps.

Thanks,
Pranav

-----Original Message-----
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Wednesday, July 03, 2013 3:34 AM
To: dev@cloudstack.apache.org
Subject: Re: ACS plugins

I wonder if this would work for you to reload (I've only used it when making 
changes to existing JavaScript files, though)?

mvn -P developer -pl :cloud-client-ui -DskipTests=true


On Tue, Jul 2, 2013 at 3:59 PM, CK <cloudw...@gmail.com> wrote:

> Thanks Brian, the UI plugins work on the master branch.
>
> However, after registering a plugin the Wiki says "Reload the UI - 
> rerun the build UI portion of the mvn build, if not in the active 
> Tomcat/jetty folder, and then refresh the browser. You should see your 
> new plugin in the side navigation bar!"
>
> What is the actual command to rerun the build UI portion of the mvn build?
>
> What is the active Tomcat/jetty folder? - /opt/cloudstack?
>
>
> On 2 July 2013 19:11, Brian Federle <brian.fede...@citrix.com> wrote:
>
> > Hello,
> >
> > >> I have DevCloud2 running with ACS 4.1 pulled in via git.
> >
> > You'll want to make sure you are on either the master or 4.2 branch 
> > for
> UI
> > plugins to work, since they didn't exist on 4.1 or earlier.
> >
> > -Brian
> >
> > -----Original Message-----
> > From: CK [mailto:cloudw...@gmail.com]
> > Sent: Tuesday, July 02, 2013 11:04 AM
> > To: dev@cloudstack.apache.org
> > Subject: Re: ACS plugins
> >
> > Hi Pranav,
> >
> > To keep things simple, I have exactly followed the wiki:
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+Plugin+Tutor
> ialbutit did not work :-(
> >
> > I have DevCloud2 running with ACS 4.1 pulled in via git. The 
> > /ui/plugins folder did not exist so I created it and followed the 
> > wiki creating the directory structure and creating 
> > /ui/plugins/plugins.js
> >
> > In the Wiki when it says "...rerun the build UI portion of the mvn 
> > build..." which of the mvn commands do I need to run from the 
> > /opt/cloudstack directory:
> >
> > 1) mvn -P developer,systemvm clean install
> >
> > 2) mvn -P developer -pl developer,tools/devcloud -Ddeploydb
> >
> > 3) mvn -pl :cloud-client-ui jetty:run
> >
> > Thanks
> >
> >
> > On 2 July 2013 18:26, Pranav Saxena <pranav.sax...@citrix.com> wrote:
> >
> > > Please see my comments inline  and shoot any queries you may have 
> > > with UI plugins -
> > >
> > > Thanks,
> > > Pranav
> > > -----Original Message-----
> > > From: CK [mailto:cloudw...@gmail.com]
> > > Sent: Tuesday, July 02, 2013 9:36 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: ACS plugins
> > >
> > > Hi,
> > >
> > > Are UI plugins implemented/deployed differently to other types 
> > > such as API, Storage or Networking plugins (reside under 
> > > /cloudstack/plugins) [Pranav] - Yes , UI plugins are implemented in their 
> > > own unique way .
> > > The wiki page elaborates on the pattern/structure you need to 
> > > follow to develop a UI plugin.
> > >
> > > I am looking at writing a UI plugin, browsing the wiki I have come 
> > > across this page:
> > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+Plugin+T
> > > utor
> > > ial
> > >
> > > It mentions plugins reside in the /ui/plugins/(pluginID)folder and 
> > > are registered in: /ui/plugins/plugins.js
> > >
> > > Is the UI plugin wiki correct and the one I should follow as 
> > > opposed to the API plugins?
> > > [Pranav] - This is the perfect wiki page . Please follow it .
> > >
> > > Thanks
> > >
> >
>



--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*

Reply via email to