On May 2, 2014, at 12:27 PM, Fred Opims wrote:
> After that, i've tried to to have the same configuration you've set in the
> Wolips Pane.
> I had to copy some frameworks in some specific location.
Those are just the defaults. You can actually put them anywhere you want, as
long as the wolip.
ere.
> Then i copy the wolips.properties (from /Library/Application
> Support/WOLips/ ) and i past it in my project folder at the same level
> than my build.properties file. The previous message (The properties
> 'wo.system.frameworks' and 'wo.local.frameworks'
tem.frameworks' and 'wo.local.frameworks') disappear and the first
> one came back (The framework name 'ERJars' does not exist.)
> Should i have wolips.properties file somewhere else (in addition to the one
> located in ~/Library/Application Support/WOLips/)?
he wolips.properties (from /Library/Application Support/WOLips/ )
and i past it in my project folder at the same level than my
build.properties file. The previous message (The properties
'wo.system.frameworks' and 'wo.local.frameworks') disappear and the
first one came back (Th
ings in your
>>>> wolips.properties file, your build.properties file needs a property that
>>>> points to the wolips.properties file. Otherwise Ant doesn’t know anything
>>>> about it.
>>>>
>>>> wolips.properties=/path/to/wolips.propertie
se the settings in your
>>> wolips.properties file, your build.properties file needs a property that
>>> points to the wolips.properties file. Otherwise Ant doesn’t know anything
>>> about it.
>>>
>>> wolips.properties=/path/to/wolips.
f you want to use the settings in your
>>> wolips.properties file, your build.properties file needs a property that
>>> points to the wolips.properties file. Otherwise Ant doesn’t know anything
>>> about it.
>>>
>>> wolips.properties=/path/to/wolips.properties
&g
ttle known fact: If you want to use the settings in your
>>> wolips.properties file, your build.properties file needs a property that
>>> points to the wolips.properties file. Otherwise Ant doesn’t know anything
>>> about it.
>>>
>>> wolips.properties=/path
>> Little known fact: If you want to use the settings in your
>>> wolips.properties file, your build.properties file needs a property that
>>> points to the wolips.properties file. Otherwise Ant doesn’t know anything
>>> about it.
>>>
>>> wolips.
nything about it.
>>
>> wolips.properties=/path/to/wolips.properties
>>
>> Dave
>>
>>
>> On May 1, 2014, at 7:28 AM, Fred Opims wrote:
>>
>>> Hi All!
>>> I’m trying to make an install of my webObject app, but i’ve a go
properties=/path/to/wolips.properties
>
> Dave
>
>
> On May 1, 2014, at 7:28 AM, Fred Opims wrote:
>
> Hi All!
> I’m trying to make an install of my webObject app, but i’ve a got the
> following error: ...build.xml:206: The framework name 'ERJars' does not
>
ll!
>> I’m trying to make an install of my webObject app, but i’ve a got the
>> following error: ...build.xml:206: The framework name 'ERJars' does not
>> exist.
>> I’ve seen some thread talking about the same issue.
>> The value of wo.local.frameworks in
, Fred Opims wrote:
> Hi All!
> I’m trying to make an install of my webObject app, but i’ve a got the
> following error: ...build.xml:206: The framework name 'ERJars' does not exist.
> I’ve seen some thread talking about the same issue.
> The value of wo.local.framework
Hi All!
I’m trying to make an install of my webObject app, but i’ve a got the
following error: ...build.xml:206: The framework name 'ERJars' does not
exist.
I’ve seen some thread talking about the same issue.
The value of wo.local.frameworks in my wolips.properties didn’t have wonder
fra
Hi Miguel,
You can use NSBundle.bundleForClass(some class in that bundle).name()
Chuck
On 2013-01-22, at 11:59 AM, Miguel Torres wrote:
> Hi List,
>
> We need to get the framework name to get some resource. We have made this
> before just calling the method frameworkName()
Thanks Mike,
We'll test it.
On 22/01/2013, at 17:47, Mike Schrag wrote:
>>> Hi Miguel,
>>>
>>> You can use NSBundle.bundleForClass(some class in that bundle).name()
> You should test this with embedded frameworks in deployment … I seem to
> recall a bug at one point where the embedded jars i
>> Hi Miguel,
>>
>> You can use NSBundle.bundleForClass(some class in that bundle).name()
You should test this with embedded frameworks in deployment … I seem to recall
a bug at one point where the embedded jars inside of frameworks tricked
NSBundle into thinking they were app-level jars. that m
Thanks everyone I will try it.
On 22/01/2013, at 14:20, Chuck Hill wrote:
> Hi Miguel,
>
> You can use NSBundle.bundleForClass(some class in that bundle).name()
>
>
> Chuck
>
>
> On 2013-01-22, at 11:59 AM, Miguel Torres wrote:
>
>> Hi List,
>>
Hi Miguel. You should be able to use:
NSBundle.bundleForClass( My.class ).name()
Cheers,
- hugi
// Hugi Thordarson
// http://www.godurkodi.is/
On 22.1.2013, at 19:59, Miguel Torres wrote:
> Hi List,
>
> We need to get the framework name to get some resource. We have made this
gt; We need to get the framework name to get some resource. We have made this
> before just calling the method frameworkName() from a java class that extends
> from a ERXComponent o WOComponent.
>
> Now we need to get the framework's name from a class that do not extends from
>
Hi List,
We need to get the framework name to get some resource. We have made this
before just calling the method frameworkName() from a java class that extends
from a ERXComponent o WOComponent.
Now we need to get the framework's name from a class that do not extends from
WOComponent, i
Hi Thomas. You should be able to use:
NSBundle.bundleForClass( My.class ).name()
Cheers,
- hugi
// Hugi Thordarson
// http://www.godurkodi.is/
On 8.1.2013, at 13:53, Thomas Grass
(01SoftwareSolutions) wrote:
> Hello WO-Developers,
> within a component, i need to get the name of the framewo
Hello WO-Developers,
within a component, i need to get the name of the framework for this function:
public String logoPath() {
return
application().resourceManager().pathURLForResourceNamed("dataHeaderInvoice.png",
this.frameworkName(), null).getPath();
}
Usually i did this by t
e
>> [property] Loading
>> /Users/jtayler/Desktop/VAT/Planaby-Server/WOMan/build.properties
>> [property] Loading /Users/jtayler/Library/Application
>> Support/WOLips/wolips.properties
>> Override ignored for property "wolips.properties"
>>
&g
; [property] Loading /Users/jtayler/Library/Application
> Support/WOLips/wolips.properties
> Override ignored for property "wolips.properties"
>
> init.build:
>
> compile:
>[mkdir] Skipping /Users/jtayler/Desktop/VAT/Planaby-Server/WOMan/bin
&g
ignored for property "wolips.properties"
init.build:
compile:
[mkdir] Skipping /Users/jtayler/Desktop/VAT/Planaby-Server/WOMan/bin
because it already exists.
BUILD FAILED
/Users/jtayler/Desktop/VAT/Planaby-Server/WOMan/build.xml:206: The framework
name 'ERPro
sults I expect - but when I went
to make an install build, I started getting this failure and haven't been able
to figure?
BUILD FAILED
/Users/jtayler/Desktop/VAT/Planaby-Server/WOMan/build.xml:206: The framework
name 'WOOgnl' does not exist.
I'd guess WOOgnl is really ju
27 matches
Mail list logo
