Hey Ashish,

You were right, here is one : could we not use the work done in 
https://issues.apache.org/jira/browse/OFBIZ-1700 ?

I think, Tim is the man who can answer...

Thanks

Jacques

From: "Jacques Le Roux" <[EMAIL PROTECTED]>
We may hope, yes.

Jacques

From: "Ashish Vijaywargiya" <[EMAIL PROTECTED]>
Inline

On Wed, Jun 18, 2008 at 1:41 PM, Jacques Le Roux <
[EMAIL PROTECTED]> wrote:

Thanks Tim,

I have updated the wiki accordingly. We should not get anymore any
complaints  :p


I am sure instead getting complaints we will get suggestions :-)
Correct Jacques ?

--
Ashish





Jacques

From: "Tim Ruppert" <[EMAIL PROTECTED]>

Everything's up there except the new filename with the SVN version  number
in it - which will happen sometime later today.

Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595


On Jun 18, 2008, at 11:13 AM, Jacques Le Roux wrote:

 From: "Tim Ruppert" <[EMAIL PROTECTED]>

-- Did you have something else in mind?


Something very simple (harcoded) as in footer.ftl files in  release4.0


The only problem is that since this isn't based upon SVN keywords  or
 anything, that we'll have an updated footer.ftl with incorrect
information going forward - which in my opinion is a bad idea.    Thoughts?


Yes you are right indeed, this would one more worry when launching a  new
release (I could note it somewhere but we can't rely on such a  way of doing
things, I agree)... OK forget it, except if someone has  a better idea ?

Jacques



TIA

Jacques

 4. Text
-- Fixed per Jacques instructions

Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595


On Jun 18, 2008, at 6:36 AM, Jacques Le Roux wrote:

 I prefer the 1st if it's easy to set :o)
I tested (only launched and opened front and back on Windows),   not
 surprinsgly they work well both (release and trunk)
BTW I see that we do an svn co instead of an svn export Jacopo
 suggested (pro : less files and space from 117MB to 95 for  trunk  for
 instance, cons : have to redo an svn co after if  willing to  pursuie  with
OFBiz). What to you think about it  folks ?

I propose to add something like  "Apache OFBiz trunk version"   like
 we did for release. Even without the real svn version  number  we will
 have at least this information (maybe at this  stage on  the build  server
it's possible to add the svn  version ?)

Jacques

From: "Ashish Vijaywargiya" <[EMAIL PROTECTED]>

I will like the second option i.e "if we should simply add it  to
 the
"Nightly Builds, What Do I Get?" ".

--
Ashish

On Wed, Jun 18, 2008 at 7:43 AM, Tim Ruppert <
[EMAIL PROTECTED]
>
wrote:

 We can do whatever you like - if you just want it to show the
size  of each
of the files, we can do that - or if we should simply add it  to
the "Nightly
Builds, What Do I Get?" section.  Let me know the preference   and
 I"ll get it
in there.

Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595


On Jun 18, 2008, at 3:01 AM, Ashish Vijaywargiya wrote:

Jacques ,


(just telling people that's both are about 100MB to donwload)


 Adding the details about the external jar files will be  good
 to  put

altogether.
The size of both are about 100MB (External jars size  included  in
 the
project
is around 40MB or 50MB whatever it is)

Let's see what other has to say .... its my own wish :-).

--
Ashish



On Wed, Jun 18, 2008 at 4:53 AM, Jacques Le Roux <
[EMAIL PROTECTED]> wrote:

Tim,


That's great. Could it be possible to have some words about   the
 size
(just
telling people that's both are about 100MB to donwload) ?

I will try to test them both today and will update wiki
 accordingly.

Thanks

Jacques

From: "Tim Ruppert" <[EMAIL PROTECTED]>

Just so that everyone knows, the build area is ready now and  is

accessible from the ofbiz.apache.org home page.  I will  post
another
email out to everyone whenever everyone's had a chance to   test
 out the
results.

Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595















Reply via email to