You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by "Gaasch, Derek" <dg...@montana.edu> on 2003/10/09 22:52:57 UTC
more maven build trouble
I decided that since my problem posted earlier (see below) hasn't gotten any
response, this would be a good time to get involved with the turbine source
code. Yikes. I got maven, got the source tree.... and now? I'm using the RC1
maven code & on "maven" I get a ton of errors that look like "$basePrefix"
errors. I found some archived mail about these kinds of problems --
specifically that since b9 you need to put some torque stuff into a
properties file:
torque.addGetByNameMethod = true
torque.addIntakeRetrievable = false
torque.addSaveMethod = true
torque.addTimeStamp = true
torque.basePrefix = Base
torque.complexObjectModel = true
torque.useManagers = false
torque.useClasspath = true
torque.saveException = Exception
However, no matter what properties file I try, I cant get it to fix the
problem. Any suggestions? I've tried:
{PROJECT_PATH}/project.properties
{PROJECT_PATH}/build.properties
as well as
{MAVEN_PLUGIN_DIR}/project.properties
...
-d
-----Original Message-----
From: Gaasch, Derek [mailto:dgaasch@montana.edu]
Sent: Tuesday, October 07, 2003 6:29 PM
To: 'Turbine Users List'
Subject: BUG: argument type mismatch: intake on 2.2->2.3 upgrade
Spent a while testing this out & it looks like this is a problem with
multivalue fields of primitives. When the group is created on init, intake
looks for a method that accepts (for example) an int[] as a parameter. But
then when reflection is doing its thing, it's working with a value array of
Integer objects... therein lies the argument type mismatch. Pretty much
stops my conversion to 2.3 dead in its tracks.
-d
-----Original Message-----
From: Gaasch, Derek [mailto:dgaasch@montana.edu]
Sent: Monday, October 06, 2003 3:55 PM
To: 'Turbine Users List'
Subject: intake on 2.2->2.3 upgrade
I'm switching from 2.2 over to 2.3 and I'm having an intake issue,
specifically with groups that have multivalue integer fields. I keep getting
"argument type mismatch" exceptions. Any clues of what's going on / what has
changed in Intake that might be the cause of this?
Thanks,
derek
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
RE: fulcrum-localization test fail in non-US locale
Posted by Eric Pugh <ep...@upstate.com>.
Any patches submitted would be great.. Maybe you can look up the current
system property and change it to us? Or, although it seems like heck, maybe
add more versions and and add some docs about why the unit test fails?
Things that depend on external resources (like the country code) are hard to
test... Any patches are happily accepted! Possibly you could also add a
section to the xdocs highlighting that it may fail on non us platforms,
since I expect localization to be built by non US folks a lot!
Eric
> -----Original Message-----
> From: Angelo Turetta [mailto:at-turbine@commit.it]
> Sent: Saturday, October 18, 2003 5:58 PM
> To: Turbine Developers List
> Subject: fulcrum-localization test fail in non-US locale
>
>
> Trying to build fulcrum-localization, I get the following
> error during test:
>
> ----------------
> Testsuite: org.apache.fulcrum.localization.LocalizationTest
> Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 1,532 sec
>
> Testcase: testInitialization took 0,691 sec
> Testcase: testLocalization took 0,831 sec
> Caused an ERROR
> Can't find bundle for base name
> org.apache.fulcrum.localization.BarBundle,
> locale it_IT
> java.util.MissingResourceException: Can't find bundle for base name
> org.apache.fulcrum.localization.BarBundle, locale it_IT
> at
> org.apache.fulcrum.localization.DefaultLocalizationService.cac
> heBundle(Defau
> ltLocalizationService.java:381)
> at
> org.apache.fulcrum.localization.DefaultLocalizationService.get
> Bundle(Default
> LocalizationService.java:345)
> at
> org.apache.fulcrum.localization.DefaultLocalizationService.get
> String(Default
> LocalizationService.java:531)
> at
> org.apache.fulcrum.localization.LocalizationTest.testLocalizat
> ion(Localizati
> onTest.java:104)
> at ........ (unimportant stack trace removed)
> ---------------
>
> After looking at the code, I found that setting
>
> MAVEN_OPTS=-Duser.language=en -Duser.region=US
>
> before running maven let me pass the tests. Not bad for a localization
> service, its testing classes presume to be run only in a U.S.
> environment
> :-)
>
> Ciao
> Angelo Turetta
> Modena - Italy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
fulcrum-localization test fail in non-US locale
Posted by Angelo Turetta <at...@commit.it>.
Trying to build fulcrum-localization, I get the following error during test:
----------------
Testsuite: org.apache.fulcrum.localization.LocalizationTest
Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 1,532 sec
Testcase: testInitialization took 0,691 sec
Testcase: testLocalization took 0,831 sec
Caused an ERROR
Can't find bundle for base name org.apache.fulcrum.localization.BarBundle,
locale it_IT
java.util.MissingResourceException: Can't find bundle for base name
org.apache.fulcrum.localization.BarBundle, locale it_IT
at
org.apache.fulcrum.localization.DefaultLocalizationService.cacheBundle(Defau
ltLocalizationService.java:381)
at
org.apache.fulcrum.localization.DefaultLocalizationService.getBundle(Default
LocalizationService.java:345)
at
org.apache.fulcrum.localization.DefaultLocalizationService.getString(Default
LocalizationService.java:531)
at
org.apache.fulcrum.localization.LocalizationTest.testLocalization(Localizati
onTest.java:104)
at ........ (unimportant stack trace removed)
---------------
After looking at the code, I found that setting
MAVEN_OPTS=-Duser.language=en -Duser.region=US
before running maven let me pass the tests. Not bad for a localization
service, its testing classes presume to be run only in a U.S. environment
:-)
Ciao
Angelo Turetta
Modena - Italy
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
RE: more maven build trouble
Posted by Eric Pugh <ep...@upstate.com>.
Welcome to the only part about Maven that sucks.. Building Turbine! Derek,
you are using RC1? Did you build it yourself or download from the web..?
You should be able to put the properties in your turbine root directory..
{PROJECT_PATH}/project.properties is correct...
Also, try doing a maven clean, and then maven jar.. It should work, if not
I can send you the correct version of the torque plugin offline..
Eric
> -----Original Message-----
> From: Gaasch, Derek [mailto:dgaasch@montana.edu]
> Sent: Thursday, October 09, 2003 10:53 PM
> To: 'Turbine Users List'
> Cc: 'turbine-dev@jakarta.apache.org'
> Subject: more maven build trouble
>
>
>
> I decided that since my problem posted earlier (see below)
> hasn't gotten any
> response, this would be a good time to get involved with the
> turbine source
> code. Yikes. I got maven, got the source tree.... and now?
> I'm using the RC1
> maven code & on "maven" I get a ton of errors that look like
> "$basePrefix"
> errors. I found some archived mail about these kinds of problems --
> specifically that since b9 you need to put some torque stuff into a
> properties file:
>
> torque.addGetByNameMethod = true
> torque.addIntakeRetrievable = false
> torque.addSaveMethod = true
> torque.addTimeStamp = true
> torque.basePrefix = Base
> torque.complexObjectModel = true
> torque.useManagers = false
> torque.useClasspath = true
> torque.saveException = Exception
>
> However, no matter what properties file I try, I cant get it
> to fix the
> problem. Any suggestions? I've tried:
>
> {PROJECT_PATH}/project.properties
> {PROJECT_PATH}/build.properties
> as well as
> {MAVEN_PLUGIN_DIR}/project.properties
> ...
>
> -d
>
>
>
>
> -----Original Message-----
> From: Gaasch, Derek [mailto:dgaasch@montana.edu]
> Sent: Tuesday, October 07, 2003 6:29 PM
> To: 'Turbine Users List'
> Subject: BUG: argument type mismatch: intake on 2.2->2.3 upgrade
>
>
> Spent a while testing this out & it looks like this is a problem with
> multivalue fields of primitives. When the group is created on
> init, intake
> looks for a method that accepts (for example) an int[] as a
> parameter. But
> then when reflection is doing its thing, it's working with a
> value array of
> Integer objects... therein lies the argument type mismatch.
> Pretty much
> stops my conversion to 2.3 dead in its tracks.
>
> -d
>
> -----Original Message-----
> From: Gaasch, Derek [mailto:dgaasch@montana.edu]
> Sent: Monday, October 06, 2003 3:55 PM
> To: 'Turbine Users List'
> Subject: intake on 2.2->2.3 upgrade
>
>
> I'm switching from 2.2 over to 2.3 and I'm having an intake issue,
> specifically with groups that have multivalue integer fields.
> I keep getting
> "argument type mismatch" exceptions. Any clues of what's
> going on / what has
> changed in Intake that might be the cause of this?
>
> Thanks,
>
> derek
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org