[Cosmo-dev] Problem with cosmo.account.settings

Antonio Muñiz amunizmartin.cosmo at gmail.com
Thu Oct 25 01:38:33 PDT 2007


Hi Travis.

I checkout the 0.7.5 branch, but the problem persist.
Initialy /src/main/webapp/js/lib do not exist, only
/src/main/webapp/js/cosmo exists. I modify settings.js and I do mvn package
in cosmo directory. This generates /src/main/webapp/js/lib content (with
dojo.js included) but my changes don´t take effect.

I do:
1. Modify settings.js
2. cd cosmo
3. mvn package --> generates js/lib directory
4. cd ../snarf
5. mvn package --> generates server bundle.

When I try "mvn package" in cosmo directory it throws an error: the lib dojo
0.4.1-075-SNAPSHOT is required but it don´t find it.
I change the pom:
              <artifactItem>
                                    <groupId>org.osaf.cosmo</groupId>
                                    <artifactId>dojo</artifactId>
                                    <version>0.4.1-075-SNAPSHOT</version>
                                    <type>jar</type>
               </artifactItem>

and I put
               <artifactItem>
                                    <groupId>org.osaf.cosmo</groupId>
                                    <artifactId>dojo</artifactId>
                                    <version>0.4.1-072</version>
                                    <type>jar</type>
                </artifactItem>

I don´t know if dojo version is important.
I hope your reply.

Antonio.

2007/10/24, Travis Vachon <travis at osafoundation.org>:
>
> Hi Antonio
> I suspect the problem is that you grabbed the 0.7.2 tag which is set up to
> always pull the "javascript distribution" from our servers. This
> distribution comes with settings.js packed into
> cosmo/src/main/webapp/js/lib/dojo.js so your modified version isn't being
> grabbed.
>
> You have a couple options for fixing this:
>
> 1) Grab the 0.7 branch instead. This will give you the code that has
> become the 0.7.5 tag. Building this will pull down the development version
> of the javascript distribution which does not come with settings.js built
> into dojo.js.
>
> 2) From the "project root" (where you started your commands as well):
> cd dojo
> mvn package install # you'll need ant for this step, "apt-get install ant
> ant-optional" in ubuntu
> cd ../cosmo
> mvn -U package
> # continue with the steps you mentioned
>
> This will build a developer version of the javascript distribution and
> install it to your local maven repository. Building cosmo after this should
> use this version of the javascript.
>
>
>
> All that said, devs generally run from an exploded WAR by editing
> snarf/<pathtodistribution>/tomcat/conf/server.xml and changing  the docBase
> attribute of the <Context> element whose path attribute is "/chandler" to
> the absolute path of cosmo/src/main/webapp so this is the environment that
> I'm confident will give you the results you're looking for.
>
> It occurs to me that we haven't taken a look at the "Hack some code"
> section as it relates to Javascript development in a while, so I'll make
> sure that's up to date today as well.
>
> Let me know whether this works for you or not!
>
> Also, feel free to pop into #cosmo on irc.freenode.net for help, the core
> devs are pretty much always there during the day (9-7 or so Pacific Standard
> Time) and someone knowledgeable is usually at least lurking 24/7.
>
> -Travis
>
>
> On Oct 24, 2007, at 8:50 AM, Antonio Muñiz wrote:
>
> Hi, Jared.
>
> I downloaded cosmo 0.7.2 from svn repository.
> My modification is:
> When a user will do click on the Settings link, it will do nothing (not
> show the settings form). Simple.
> This is the first step.
>
> For this I have to modify the file menu.js (delete
> cosmo.account.settings.showDialog() line)
>
> ...
> { id: 'settingsMenuItem',
>         displayText: _('Main.Settings'),
>         onclickFunc: function () { cosmo.account.settings.showDialog(); },
>         displayMode: cosmo.ui.menu.displayModes.AUTH,
>         requiredRoles: [cosmo.ui.menu.requiredRoles.USER]
>         },
> ...
>
> I modify the file and I do:
> cd cosmo
> mvn package
> cd ..
> cd snarf
> mvn package
>
> This generate a tar.gz file which contains the bundle server. I launch the
> server but the changes has no effect.
>
>
> Thanks for reply.
>
> Antonio.
>
>
> 2007/10/24, Jared Rhine <jared at wordzoo.com>:
> >
> > Antonio Muñiz wrote:
> > > I try to modify the code in /js/cosmo/account/settings.js but the
> > > changes don´t take effect. Why?
> >
> > Hello, Antonio.  Are you working from a downloaded tarball?  If so, some
> > of our Javascript code is wrapped up into a single "built" file.  If you
> >
> > change one of the source files, you would then need to recompile.
> >
> > If you're doing development on Cosmo, you would normally "build from
> > source", using the instructions here:
> >
> >    http://chandlerproject.org/Developers/ChandlerServerSource
> >
> > There's a "Hack some code" section on that page, for instance.
> >
> > Does this help?  You may be having other problems, in which case we'll
> > need more information about your set up and what you are trying to do.
> >
> > -- Jared
> >
> >
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
>
>
>
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/cosmo-dev/attachments/20071025/c306062a/attachment.htm


More information about the cosmo-dev mailing list