Hi Jacques,
I have removed some redundant cast warming but if you set all the warning on
eclipse to warning where they are ignore you will get many others.
So we have to decide if we would like to remove all the warning or simply the
ones intercepted by the build.
In your patch was missing
https://blogs.apache.org/conferences/entry/call_for_participation_apachecon_north
Jacopo
From: Jacques Le Roux jacques.le.r...@les7arts.com
BTW there are some interseting things, like wrong libs names:
[javac16] warning: [path] bad path element D:\workspace\ofbizDev\framework\base\lib\commons-io-1.3.1.jar: no such file or
directory
[javac16] warning: [path] bad path element
Yes, it's strange also to me, it's necessary to dig it something more.
Anyone having some suggestion on it ?
Thanks
Marco
Il giorno 13/mar/2011, alle ore 11.17, Jacques Le Roux ha scritto:
From: Jacques Le Roux jacques.le.r...@les7arts.com
BTW there are some interseting things, like wrong
Hi Marco,
My idea is to use compilerarg value=-Xlint/ (thanks for the miss), so I'd say I don't care about Eclipse, if some want to fix
them, perfect, else simply forget about those warnings
I will wait to commit that we remove most, if not all, of the warning messages
in order to not
+1
Thanks
Marco
Il giorno 13/mar/2011, alle ore 11.31, Jacques Le Roux ha scritto:
Hi Marco,
My idea is to use compilerarg value=-Xlint/ (thanks for the miss), so
I'd say I don't care about Eclipse, if some want to fix them, perfect, else
simply forget about those warnings
I will
Add compilerarg value=-Xlint/ to all build targets
--
Key: OFBIZ-4213
URL: https://issues.apache.org/jira/browse/OFBIZ-4213
Project: OFBiz
Issue Type: Improvement
Components: ALL
[
https://issues.apache.org/jira/browse/OFBIZ-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-4213:
---
Description:
THe idea is to use compilerarg value=-Xlint/ and to not care about
Eclipse,
[
https://issues.apache.org/jira/browse/OFBIZ-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-4213:
---
Attachment: OFBIZ-4213_Add compilerarg value=-Xlint.patch
Add compilerarg value=-Xlint/ to
[
https://issues.apache.org/jira/browse/OFBIZ-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13006177#comment-13006177
]
Jacques Le Roux commented on OFBIZ-2761:
Hi Aswath,
Did you get a chance to look
[
https://issues.apache.org/jira/browse/OFBIZ-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13006191#comment-13006191
]
Jacques Le Roux commented on OFBIZ-4213:
Thanks to Marco's continued hard work, at
[
https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13006193#comment-13006193
]
Jacques Le Roux commented on OFBIZ-4014:
Hi Sascha,
I did not test yet, but why
[
https://issues.apache.org/jira/browse/OFBIZ-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13006203#comment-13006203
]
Marco Risaliti commented on OFBIZ-4213:
---
Hi Jacques,
I have seen that it's due to
[
https://issues.apache.org/jira/browse/OFBIZ-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-4213:
---
Attachment: OFBIZ-4213_Add compilerarg value=-Xlint.patch
Actually we need to use
[
https://issues.apache.org/jira/browse/OFBIZ-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-4213.
--
Resolution: Fixed
Fix Version/s: SVN trunk
ok -Xlint:-path was the solution, committed
[
https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13006219#comment-13006219
]
Jacques Le Roux commented on OFBIZ-4014:
Sascha,
Could you update your patch
Hi Hans,
Is there an issue to do this?
Thanks
Jacques
Scott Gray wrote:
Hi Hans
Would you please consider moving the inline css out to the relevant theme
stylesheets?
Many thanks
Scott
HotWax Media
http://www.hotwaxmedia.com
On 26/01/2011, at 8:53 PM, hans...@apache.org wrote:
Author:
I have not looked into details, this has been committed by Adam
http://markmail.org/message/wnioayvhpqoo6p6u
Could you please enlighten us Adam?
Thanks
Jacques
René Scheibe wrote:
Some time ago the Ant if task implementation was replaced by another
one using a Javascript version.
I was
From the Rev 894330 commit log:
[OFBIZ-3274] - Using decorator sections to control the left-bar
The leftbar content is now defined using the left-column
ApplicationDecorator section instead of setting the variables
leftbarScreenName, leftbarScreenLocation and MainColumnStyle. The
logic that
[
https://issues.apache.org/jira/browse/OFBIZ-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric de Maulde updated OFBIZ-4212:
--
Attachment: ScaleImage.patch
Here is a new patch to scale main image product content and
https://issues.apache.org/jira/browse/OFBIZ-4213
From: risali...@gmail.com
+1
Thanks
Marco
Il giorno 13/mar/2011, alle ore 11.31, Jacques Le Roux ha scritto:
Hi Marco,
My idea is to use compilerarg value=-Xlint/ (thanks for the miss), so I'd say I don't care about Eclipse, if some want to
Hi,
I've notice several missed features from the new image magenement.
I haven't seen :
_ original image saving (where a functionality able to automatically
resize all images if the webmaster decide by eg. to modify the large
size)
_ non-automatic resizing into configured
[
https://issues.apache.org/jira/browse/OFBIZ-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Risaliti resolved OFBIZ-4102.
---
Resolution: Fixed
Thanks to Jacques has completed this work with issue OFBIZ-4213.
So now
[
https://issues.apache.org/jira/browse/OFBIZ-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Risaliti closed OFBIZ-4102.
-
Remove most of the java compilation warning (generics markup, unused
code/import)
Hi Adrian,
when I did this change I supposed that left-column where only something
related to applications.
The global decorator only had visibility of a pre-body and a body section.
The main purpose of the change was to get rid of the several variables and
use the decorator feature.
But I agree
Ideally, the multi-column layout would be handled by the applications
needing it - not by the decorator. But it has been that way for too long
to change it now.
A framework-only deployment can have applications too - the Example and
Web Tools components are examples.
Would you be willing to
26 matches
Mail list logo
