[svn] 688: asc: adding a barebones build. properties so we get line numbers on stack traces

Revision: 688
Author: [email protected]
Date: 2008-02-28 14:17:43 -0800 (Thu, 28 Feb 2008)
Log Message:
asc: adding a barebones build.properties so we get line numbers on stack traces
Added Paths:
flex/sdk/trunk/modules/asc/build/java/build.properties

Similar Messages

Problems with line numbers (building via ant).

We use ant for our builds and are having a problem with getting line numbers into call stacks. When running on linux we do not get the lines for our projects (not all projects have debug option), just (Unknown Source), however we do see line numbers for the tib jars. Eclipse is fine, we can see all line numbers as appropriate.
I have tried "lines", "lines,source" and "lines,var,source" - all build a different sized jar which suggest something is getting added. However as we see line nums for tib it suggests it's some strange java runtime option. We're using sunjdk 1.5.10 and also jrockit.
Any ideas/answers most appreciated.
Many thanks, Declan
Ant task
<target name="compile" depends="init">
     <javac target="1.5" destdir="${classes}" debug="on" debuglevel="lines,source">
          <src path="${src}"/>
          <classpath refid="default.classpath"/>
     </javac>
     <javac target="1.5" destdir="${classes-test}" debug="on" debuglevel="lines,source">
          <src path="${testsrc}"/>
          <classpath refid="default.classpath"/>
          <classpath location="${classes}"/>
     </javac>
</target>
Example output
java.lang.IllegalArgumentException: Field data is null
at com.tibco.tibrv.TibrvMsg._addImpl(TibrvMsg.java:1503)
at com.tibco.tibrv.TibrvMsg.add(TibrvMsg.java:1020)
at com.lehman.fid.jdt.channel.tibrv.TibrvMessage.putObject(Unknown Source)
at com.lehman.cmd.etrading.orderbook.dp.DefaultDepthPublisher.buildSubMessage(Unknown Source)
at com.lehman.cmd.etrading.orderbook.dp.DefaultDepthPublisher.buildSubMessage(Unknown Source)
at com.lehman.cmd.etrading.orderbook.dp.DefaultDepthPublisher.publishDepth(Unknown Source)
Cmd line
VM_OPTS="-Dlogfile=../../log/CmdOrderBook.log"
VM_OPTS="${VM_OPTS} -Dcom.sun.management.jmxremote"
VM_OPTS="${VM_OPTS} -Dcom.sun.management.jmxremote.authenticate=false"
VM_OPTS="${VM_OPTS} -Dcom.sun.management.jmxremote.password=false"
VM_OPTS="${VM_OPTS} -Dcom.sun.management.jmxremote.ssl=false"
PARAMS="-springcfg orderbook-context.xml -instancename CmdOrderBook"
exec ${JAVA_HOME}/bin/java -DappInstance=CmdOrderBook -server -Xmx500M -Xms250M -Xincgc ${VM_OPTS} com.lehman.cmd.etrading.orderbook.CommoditiesOrderBook ${PARAMS} >> ../../log/Cm
dOrderBook.out 2>&1

We use ant for our builds and are having a problem with getting line numbers into call stacks. When running on linux we do not get the lines for our projects (not all projects have debug option), just (Unknown Source), however we do see line numbers for the tib jars. Eclipse is fine, we can see all line numbers as appropriate.
I have tried "lines", "lines,source" and "lines,var,source" - all build a different sized jar which suggest something is getting added. However as we see line nums for tib it suggests it's some strange java runtime option. We're using sunjdk 1.5.10 and also jrockit.
Any ideas/answers most appreciated.
Many thanks, Declan
Ant task
<target name="compile" depends="init">
     <javac target="1.5" destdir="${classes}" debug="on" debuglevel="lines,source">
          <src path="${src}"/>
          <classpath refid="default.classpath"/>
     </javac>
     <javac target="1.5" destdir="${classes-test}" debug="on" debuglevel="lines,source">
          <src path="${testsrc}"/>
          <classpath refid="default.classpath"/>
          <classpath location="${classes}"/>
     </javac>
</target>
Example output
java.lang.IllegalArgumentException: Field data is null
at com.tibco.tibrv.TibrvMsg._addImpl(TibrvMsg.java:1503)
at com.tibco.tibrv.TibrvMsg.add(TibrvMsg.java:1020)
at com.lehman.fid.jdt.channel.tibrv.TibrvMessage.putObject(Unknown Source)
at com.lehman.cmd.etrading.orderbook.dp.DefaultDepthPublisher.buildSubMessage(Unknown Source)
at com.lehman.cmd.etrading.orderbook.dp.DefaultDepthPublisher.buildSubMessage(Unknown Source)
at com.lehman.cmd.etrading.orderbook.dp.DefaultDepthPublisher.publishDepth(Unknown Source)
Cmd line
VM_OPTS="-Dlogfile=../../log/CmdOrderBook.log"
VM_OPTS="${VM_OPTS} -Dcom.sun.management.jmxremote"
VM_OPTS="${VM_OPTS} -Dcom.sun.management.jmxremote.authenticate=false"
VM_OPTS="${VM_OPTS} -Dcom.sun.management.jmxremote.password=false"
VM_OPTS="${VM_OPTS} -Dcom.sun.management.jmxremote.ssl=false"
PARAMS="-springcfg orderbook-context.xml -instancename CmdOrderBook"
exec ${JAVA_HOME}/bin/java -DappInstance=CmdOrderBook -server -Xmx500M -Xms250M -Xincgc ${VM_OPTS} com.lehman.cmd.etrading.orderbook.CommoditiesOrderBook ${PARAMS} >> ../../log/Cm
dOrderBook.out 2>&1

[svn:fx-trunk] 11314: add the empty properties file to svn to fix the build .properties

Revision: 11314
Author:   [email protected]
Date:     2009-10-30 10:38:34 -0700 (Fri, 30 Oct 2009)
Log Message:
add the empty properties file to svn to fix the build.properties
QE notes:
Doc notes:
Bugs: fix the build
Reviewer: Pete
Tests run: checkintests
Is noteworthy for integration: no
Added Paths:
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/de_DE/empty.properties
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/fr_FR/empty.properties
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/ja_JP/empty.properties
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/ru_RU/empty.properties
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/zh_CN/empty.properties

Thats good news.

[svn] 762: -update the 3.0 branch to use build. properties to create the flex-sdk-description.xml

Revision: 762
Author: [email protected]
Date: 2008-03-10 07:44:49 -0700 (Mon, 10 Mar 2008)
Log Message:
-update the 3.0 branch to use build.properties to create the flex-sdk-description.xml
Modified Paths:
flex/sdk/branches/3.0.x/build.properties
flex/sdk/branches/3.0.x/build.xml
Added Paths:
flex/sdk/branches/3.0.x/collateral/en_US/flex-sdk-description.xml

By the way, simply adding the quotes around the lexical names in the sql statement doesn't work. That causes the lexical references to be ignored as simple string values:
SELECT
   '&FLEX_GL_BALANCING_APROMPT' alias_gl_balancing_aprompt
,'&FLEX_GL_ACCOUNT_LPROMPT'   alias_gl_account_lprompt
,'&ACCT_BAL_LPROMPT'          alias_acct_bal_lprompt
FROM dualI turned on statement-level debugging via xdodebug.cfg and saw how it compiled the lexicals. By replicating the call to apps.fnd_flex_xml_publisher_apis.kff_segments_metadata that I found there, I was able to hack together a workaround for this issue.
Please point me to a better way of doing this if possible, as I had to GRANT EXECUTE on this apps package to my custom code schema. Is there a better lexical/flexfields reference than the XML Publisher documentation?
Here is the call I made in my before-report trigger:
--set ACCT_BAL_LPROMPT flexfield segment metadata lexical
begin
apps.fnd_flex_xml_publisher_apis.kff_segments_metadata(
'FLEX_ACCT_BAL_LPROMPT',
'SQLGL',
'GL#',
101,
'GL_BALANCING',
'Y',
'LEFT_PROMPT',
c_FLEX_ACCT_BAL_LPROMPT
end;

[svn:bz-trunk] 23200: Update the common-code jar name in the qa/build. properties.

Revision: 23200
Revision: 23200
Author:   [email protected]
Date:     2011-11-08 07:32:08 -0800 (Tue, 08 Nov 2011)
Log Message:
Update the common-code jar name in the qa/build.properties. Also include all commons-*.jar in the flex.test.classpath property.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/build.xml
    blazeds/trunk/qa/build.properties

hi,
You must have recoverd from the prob faced. Could you please help us out? we are facing the following error
Created connection to registry
[java] Got registry servicequery manager, and life cycle manager
[java] Feb 6, 2007 12:46:05 PM com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection post
[java] SEVERE: SAAJ0009: Message send failed
[java] javax.xml.registry.JAXRException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed

[svn] 2203: update build.properties to 3.0.3

Revision: 2203
Author: [email protected]
Date: 2008-06-24 07:52:56 -0700 (Tue, 24 Jun 2008)
Log Message:
update build.properties to 3.0.3
Modified Paths:
flex/sdk/branches/3.0.x/build.properties

As long as you aren't in Canada. Canadian law does not allow an iTunes card to be used to purchase the new software.

[svn:fx-trunk] 5811: Adding a Flex Builder Flash-Integration and Utilities project to make these files easier for people to work on .

Revision: 5811
Author: [email protected]
Date: 2009-03-31 11:20:19 -0700 (Tue, 31 Mar 2009)
Log Message:
Adding a Flex Builder Flash-Integration and Utilities project to make these files easier for people to work on. Flash-Integration is really an intermediate swc that Utilities uses. I've also modified the existing Flex Builder project for flex4tests to build against this new utilities project directly.
Also change the way FlashIntegration is built--we no longer have a manifest file and just include-classes FlashIntegrationClasses.as.
QE Notes: -
Doc Notes: -
Bugs: -
Reviewer: Evtim
tests: -
Modified Paths:
flex/sdk/trunk/development/eclipse/flex/flex4test/.actionScriptProperties
flex/sdk/trunk/frameworks/projects/flash-integration/build.xml
Added Paths:
flex/sdk/trunk/development/eclipse/flex/flash-integration/
flex/sdk/trunk/development/eclipse/flex/flash-integration/.actionScriptProperties
flex/sdk/trunk/development/eclipse/flex/flash-integration/.flexLibProperties
flex/sdk/trunk/development/eclipse/flex/flash-integration/.project
flex/sdk/trunk/development/eclipse/flex/utilities/
flex/sdk/trunk/development/eclipse/flex/utilities/.actionScriptProperties
flex/sdk/trunk/development/eclipse/flex/utilities/.flexLibProperties
flex/sdk/trunk/development/eclipse/flex/utilities/.project
flex/sdk/trunk/frameworks/projects/flash-integration/src/FlashIntegrationClasses.as
Removed Paths:
flex/sdk/trunk/frameworks/projects/flash-integration/manifest.xml

Thats good news.

[svn:fx-trunk] 20696: update build. properties values that are used for flex-sdk-description.xml.

Revision: 20696
Revision: 20696
Author:   [email protected]
Date:     2011-03-08 14:09:49 -0800 (Tue, 08 Mar 2011)
Log Message:
update build.properties values that are used for flex-sdk-description.xml. release.version = 4.5.1 release = Superhero
QE notes: no
Doc notes: no
Bugs: no
Reviewer: lauren
Tests run: no
Is noteworthy for integration: most likely FB will have to be aware of this
Modified Paths:
    flex/sdk/trunk/build.properties

Thats good news.

[svn:fx-trunk] 12946: Fixed capitalization and added newline to components. properties

Revision: 12946
Revision: 12946
Author:   [email protected]
Date:     2009-12-14 22:00:07 -0800 (Mon, 14 Dec 2009)
Log Message:
Fixed capitalization and added newline to components.properties
QE notes: none
Doc notes: none
Bugs: n/a
Reviewer: Gordon
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/bundles/en_US/components.properties
    flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/SpinnerAccImpl.as

Thats good news.

Adding a CI Build with powershell

Hi,
Adding a CI Build (class: System.Build) with powershell to Service Manager 2012 R2 results in an error, but the Build is added with the correct properties. Here is the error message:
New-SCSMObject : Item has already been added. Key in dictionary: 'Notes' Key being added: 'Notes'
At line:1 char:15
+ new-SCSMObject <<<< (get-scsmclass System.Build) -propertyhashtable ($build)
+ CategoryInfo : InvalidOperation: (Notes:ManagementPackProperty) [New-SCSMObject], ArgumentException
+ FullyQualifiedErrorId : property 'Notes' has already been added to collection,SMLets.NewSMObjectCommand
here is what I do:
$build=@{Displayname = "Test 1"}$build+=@{AssetStatus = "Deployed"}$build+=@{ObjectStatus = "Active"}$build+=@{Category = "Software"}$build+=@{Title = "Test"}$build+=@{Version = "1"}new-SCSMObject (get-scsmclass System.Build) -propertyhashtable ($build)
If I querry this Object with
get-scsmobject (get-scsmclass System.Build$) -Filter "Displayname -eq 'Test 1'"
I get the warning:
WARNING: The property 'Notes' already exists, skipping.
Exception: The member "Notes" is already present.
In my Build Form there are also two "notes" fields.
So my questions:
a) does this occur on other installations?
b) If not: any idea, where this comes from or how I could find out.
b) If yes: how do you deal with it?
tia
Patrick Wahlmüller

Hi Roman,
Thanks for your response.
Here are some findings: Smlets are not exact enough, because in the System.build Object there are 2 Notes Fields. One from the System.ConfigItem class and one from the System.Build class. I do not understand the reason for two notes fields, but the smlets
have a problem with it and the result is a warning. You can suppress this by
get-scsmobject (get-scsmclass
System.Build$)
-Filter "Displayname -eq 'Test 1'" -WarningAction silentlycontinue
(thanks to
Jason)
When I use native cmdlets:
Get-SCSMClassInstance -class $buclass -Filter 'Displayname -eq "Test 1"'
Results in two notes fields:
Notes
System.ConfigItem_Notes
But, I'll give it a try with native cmdlets, since the are part of the product.
But one question remains: Why are there two notes fields?
Patrick Wahlmüller

Error in build.properties, how to set j2ee.home?

Hi,
I'm newbie for J2EE platform. I downloaded J2EE tutorial from sun site. I try to compile a app which ConvertApp using the asant build comannd.
I get this error.
build
Buildfile: build.xml
j2ee-home-test:
BUILD FAILED
D:\Projects\j2ee-1_4-doc-tutorial_7\j2eetutorial14\examples\common\targets.xml:1
0: The j2ee.home property is not properly set in <INSTALL>/j2eetutorial14/exampl
es/common/build.properties.
Set the j2ee.home property to the location of your Application Server installati
on.
On Windows, you must escape any backslashes in the j2ee.home property with anoth
er backslash or use forward slashes as a path separator. So, if your Application
Server installation is C:\Sun\AppServer, you must set j2ee.home as follows:
    j2ee.home = C:\\Sun\\AppServer
    or
    j2ee.home=C:/Sun/AppServer
j2ee.home is currently set to:
Total time: 0 secondsIn which line i should add the j2ee.home value?
my build.properties look like this :
# general
build=build
sql.script=create.sql
delete.sql.script=delete.sql
# database
conpool.name=DerbyPool
jdbc.resource.name=jdbc/ejbTutorialDB
# mail
mailhost=mail_server_ip
mailuser=user_id
fromaddress=email_address
mailjndi=mail/MySession
# cmp
pm.resource.name=jdo/cmp-roster
pm.factory.class=com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl
db.schema=APPPlease enlighten me on this.
Thanks in advance

Hi,
Updated "j2ee.home" and "j2ee.tutorial.home" properties in "build.properties" file which is stored in
\j2eetutorial14\examples\common
use forward slash as path seprator.
e.g
j2ee.home=D:/ProgramFiles/Sun/AppServ8.1UR2
j2ee.tutorial.home=E:/Ishtiaque/eBooks/Sun/2EE/j2eetutorial14
Regards,
Ishtiaque

Jwsdp_1.2 - build.properties not accessible

Hello,
since I've updated my jwsdp-version (to jwsdp_1.2), I cannot use ant to install my services, because the manager.username and manager.password in build.xml aren't accessible for ant, although a build.properties files exists in my home directory (OS: Win XP).
Therefore I do have to set the values for manager.username and manager.password explicitly in my build.xml
Can anyone give me some advice, what to do or is it a bug
Best regards, Macar

if you would like build.xml to access build.properties in your home dir, please ensure build.xmls reference to build.properties does point to the appropiate location.

[svn] 4463: Use svn: ignore to suppress some new build output from appearing in 'svn status'.

Revision: 4463
Author: [email protected]
Date: 2009-01-08 18:33:41 -0800 (Thu, 08 Jan 2009)
Log Message:
Use svn:ignore to suppress some new build output from appearing in 'svn status'.
AIR SDK Readme.txt
frameworks/projects/air
lib/fxgutils.jar
modules/fxgutils/classes
QE Notes: None
Doc Notes: None
Bugs: None
Reviewer: None
Property Changed:
flex/sdk/trunk/
flex/sdk/trunk/frameworks/projects/
flex/sdk/trunk/lib/
flex/sdk/trunk/modules/fxgutils/

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

An Error Occurs When I Go To "Build Properties-- Icon" -- Custom Icon Build Fails

LV 2011
Mac OS X 10.6.8
1. Create a new Build Specification using the Application Builder.
2. Click on the "Icon" tab.
The following error occurs:
Three possible outcomes from here:
1. Usually LV2011 hangs when changing this option. (i.e. "time to Force-Quit LabView" and recover the project) It hangs after I uncheck the "Use default LabView icon" box, and then select my own custom icon from the file browser that appears.
If it doesn't hang:
2. I build using the default LabView icon. That build succeeds.
3. I build using my own icon (which has worked before in LabView app builds). That build fails, near the end, with the following error:
Please tell me how I can help get this working.

Good questions.
1. This happens with all projects. As I mentioned, I get an error box as soon as I select the "Icon" tab in the Build Properties dialog. After that, it either hangs or fails to build. This happens with any new or existing project.
2. I have not built an application with a custom icon with LabView 2011. Remember I am Mac OSX so I install Application Builder separately from a .dmg file.
3. I was able to successfully build an application with a custom icon in LabView 2010.
So, it would seem to me that we should rule out that it's a global bug with LV2011 on Mac OSX (10.6.8). If you install and make a new project, and attempt to add a custom icon, I would bet you can reproduce this exactly. The error dialog pops regardless, and everytime.

Where is a build.properties?

Looking in forum i found a lot of mentions of build.properties file.
Its looks important, but i cant find it.
Where is it places?
(I use JDeveloper 11.1.1.4.0 under win7)

in what context do they mention build.properties
when you're using ant to build/create resources you can define properties in this file.
for example when you build or try to deploy bpel processes, the buid.xml file will include this build.properties file to retrieve properties from.
for example the host-url or the port , all the kind of settings

[svn] 688: asc: adding a barebones build. properties so we get line numbers on stack traces

Similar Messages

Maybe you are looking for