[svn:fx-trunk] 10051: fix the build. xml that we include in the package in the frameworks directory.

Revision: 10051
Author:   [email protected]
Date:     2009-09-08 07:53:47 -0700 (Tue, 08 Sep 2009)
Log Message:
fix the build.xml that we include in the package in the frameworks directory.
-remove haloclassic
-add textlayout
-reorganize the targets
QE notes: no
Doc notes: no
Bugs: sdk-22441
Reviewer: n/a
Tests run: checkintests
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-22441
Modified Paths:
    flex/sdk/trunk/frameworks/build_framework.xml

Similar Messages

[svn] 3061: update the framework build. xml that gets included in the package

Revision: 3061
Author: [email protected]
Date: 2008-09-02 12:38:17 -0700 (Tue, 02 Sep 2008)
Log Message:
update the framework build.xml that gets included in the package
-use target-player = 10 for most frameworks
-updated utilities target to use FlexContentHolder.swc and framework.swc
Modified Paths:
flex/sdk/trunk/frameworks/build_framework.xml

The problem with re-using an existing WSUS is that ConfigMgr doesn't do anything with the existing approved and declenid updates. ConfigMgr will only use the metadata of the updates in WSUS. This could cause problems as the ConfigMgr client simply tells
the WUA agent to scan against WSUS for compliance and then uses the update groups to tell the client which updates should be installed. In case the WUA agent finds updates directly on WSUS that are approved then it will also start to install those updates...
That's why you should use one of them, as they will interfere with eachother..
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

[svn:bz-trunk] 21002: Clean up build. xml and remove unnecessary delete task in the jar target.

Revision: 21002
Revision: 21002
Author:   [email protected]
Date:     2011-03-31 09:47:04 -0700 (Thu, 31 Mar 2011)
Log Message:
Clean up build.xml and remove unnecessary delete task in the jar target.
Checkin tests passed.
Modified Paths:
    blazeds/trunk/modules/core/build.xml
    blazeds/trunk/modules/proxy/build.xml
    blazeds/trunk/modules/remoting/build.xml

Well obviously it is an Ant build.
It looks to just compile/build a web application into a war so you can deploy it where you want to.
You don't need to edit it every time you are making a new page. It should work for any generic struts web application laid out in the fashion it expects.
Cheers,
evnafets

[svn:fx-trunk] 5235: Fix asdoc build failure.

Revision: 5235
Author: [email protected]
Date: 2009-03-11 09:46:01 -0700 (Wed, 11 Mar 2009)
Log Message:
Fix asdoc build failure.
QE Notes: None
Doc Notes: None
Bugs: none
Reviewer: Gaurav
tests: ant doc
Modified Paths:
flex/sdk/trunk/frameworks/projects/airframework/build.xml

[svn:fx-trunk] 8708: Fix broken build

Revision: 8708
Author:   [email protected]
Date:     2009-07-21 07:46:45 -0700 (Tue, 21 Jul 2009)
Log Message:
Fix broken build
Modified Paths:
    flex/sdk/trunk/frameworks/projects/textLayout/build.xml

Welcome back everyone.
Hope you all had good holidays.
Cheers
glenn
tinylion development & design

[svn:fx-trunk] 5351: Fix for @ copy tag causing first method arg to appear as the last arg in the destination method

Revision: 5351
Author: [email protected]
Date: 2009-03-17 12:51:44 -0700 (Tue, 17 Mar 2009)
Log Message:
Fix for @copy tag causing first method arg to appear as the last arg in the destination method
QE Notes: Some baseline will require updates.
Doc Notes: None.
Bugs: SDK-19974
tests: checkintests, asdoc
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19974
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/AsDocUtil.java

Well, putting all that Java code into a JSP was a bad idea in the first place, just on general design principles. But you've done it in such a way that the result of compiling the JSP is malformed Java code. Frankly I would just throw it away and put the Java code into a servlet or some other Java class, where it belongs.
But if you're really working in a place where nobody has learned anything since 2003, and you're forced to support that old junk, then I would point out that the error occurs before the place which generates this line:
import java.util.*;You only need to look at two of the thousand lines of code you posted.

[svn:bz-trunk] 17057: Fix jboss-classloading.xml.

Revision: 17057
Revision: 17057
Author:   [email protected]
Date:     2010-07-26 07:39:50 -0700 (Mon, 26 Jul 2010)
Log Message:
Fix jboss-classloading.xml.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/WEB-INF/jboss-classloading.xml

[svn:fx-trunk] 12994: * Fixes for two issues that were showing up in FB.

Revision: 12994
Revision: 12994
Author:   [email protected]
Date:     2009-12-16 06:44:45 -0800 (Wed, 16 Dec 2009)
Log Message:
Fixes for two issues that were showing up in FB.
QE notes:
Doc notes:
Bugs: SDK-24669, SDK-24686
Reviewer: Corey
Cycloner: George
Tests run: checkintests
Is noteworthy for integration: yes, fixes two FB issues.
Code-level description of changes:
modules/compiler/src/java/flex2/tools/PreLink.java
    Modified postRun() to swap in the root CompilationUnit's Logger
    when validating it's StyleContainer. This allows the warnings
    from StylesContainer.validate() to be persisted across incremental
    compilations. This fixes SDK-24686.
modules/compiler/src/java/flex2/compiler/Source.java
    Made getLogger() public, so it could be called from PreLink.
modules/compiler/src/java/flex2/compiler/CompilerAPI.java
    Modified compile() to check forcedToStop() after each PreLink
    batch. This fixes SDK-24669.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24669
    http://bugs.adobe.com/jira/browse/SDK-24686
    http://bugs.adobe.com/jira/browse/SDK-24686
    http://bugs.adobe.com/jira/browse/SDK-24669
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/Source.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/linker/CULinkable.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/PreLink.java

[svn:fx-trunk] 7891: Fixed bug in effects that was fallout from renaming offsets property to postLayoutTransformOffsets .

Revision: 7891
Author:   [email protected]
Date:     2009-06-16 13:38:37 -0700 (Tue, 16 Jun 2009)
Log Message:
Fixed bug in effects that was fallout from renaming offsets property to postLayoutTransformOffsets.
QE Notes: none
Doc Notes: None
Bugs: SDK-21839
Reviewer: Evtim
Tests: checkintests
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21839
Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/AnimateTransfor mInstance.as

Lots to be excited about. BUT...Just updated to 8.1 on one of my computers to test it out...
Sadly, the following issue is NOT fixed for me. Is it with new projects only? I haven't started a new project on 8.1 I've only opened an old project but the issue that I'm referring to which involves also a delay/freeze of anywhere from a few seconds to a MINUTE while the render bar goes from yellow to red and then back to yellow is still there. Boo.
On the list above...
Switching between sequences can turn the render bar red.
This issue is incredibly easy to replicate. I really do hope it gets fixed. Here are the steps:
1) Create two sequences with multiple short clips (the more clips the better)
2) Make sure GPU acceleration is enabled.
3) Add warp stabilizer to the clips in both sequences. Again, the more clips the longer the delay/freeze will be as the render bar goes from YELLOW to RED and then eventually back to YELLOW again.
4) Hit SAVE.
5) Now, toggle between sequences. You'll hit a short delay with a few clips stabilized and a LONG delay with lots stabilized. In my case this delay is around a full minute. The render bar will go from YELLOW to RED and then back to yellow...eventually.
6) Toggle back to the original sequence and the delay occurs again.
7) Once you've toggled between sequences and have gone through this delay, that's it, there is no longer a delay...UNTIL...(and here's the big kicker)...until the project is SAVED again. After that the issue returns when you toggle between sequences. Both saving manually and AUTOSAVING cause this issue. No way around it except not editing with GPU acceleration.
Not sure what the issue is...caching issue when saving maybe? Either way, it stinks and it's still there in 8.1. Big bummer.
Again, lots to be excited about with this release but I really was hopefully this specific issue was resolved.
Sigh.

[svn:fx-trunk] 11541: Fix the textLayout build number that is set in the main build. xml to match what will be set when the build machine does NOT do the build

Revision: 11541
Author:   [email protected]
Date:     2009-11-06 14:29:41 -0800 (Fri, 06 Nov 2009)
Log Message:
Fix the textLayout build number that is set in the main build.xml to match what will be set when the build machine does NOT do the build
QE notes: no
Doc notes: no
Bugs: no
Reviewer:
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/frameworks/air-config.xml
    flex/sdk/trunk/frameworks/flex-config.xml

Thats good news.

[svn:bz-trunk] 19327: Fix some typo in the build.xml.

Revision: 19327
Revision: 19327
Author:   [email protected]
Date:     2010-12-13 12:43:25 -0800 (Mon, 13 Dec 2010)
Log Message:
Fix some typo in the build.xml.
Modified Paths:
    blazeds/trunk/build.xml

[svn:fx-4.0.0] 13615: fix airframework/build. xml so the en_US _rb does not become corrupt when the other. locales target is run.

Revision: 13615
Revision: 13615
Author:   [email protected]
Date:     2010-01-18 20:59:14 -0800 (Mon, 18 Jan 2010)
Log Message:
fix airframework/build.xml so the en_US _rb does not become corrupt when the other.locales target is run.
-removed the redundant en_US call in the other.locales target
-added a clean for locales that will only remove the locale being built before rebuild - not all of the locales
-add updated dita that does not contain spark references
QE notes:
Doc notes:
Bugs: no but Pete and I discussed briefly
Reviewer:
Tests run: doc and other.locales
Is noteworthy for integration:
Modified Paths:
    flex/sdk/branches/4.0.0/frameworks/projects/airframework/build.xml
    flex/sdk/branches/4.0.0/frameworks/projects/airframework/bundles/de_DE/docs/packages.dita
    flex/sdk/branches/4.0.0/frameworks/projects/airframework/bundles/fr_FR/docs/packages.dita
    flex/sdk/branches/4.0.0/frameworks/projects/airframework/bundles/ru_RU/docs/packages.dita
    flex/sdk/branches/4.0.0/frameworks/projects/airframework/bundles/zh_CN/docs/packages.dita

What kind of projects are they (Struts/JSF/Hibernate)? Does the working project differ in any way with other two apps?
What exactly is not working? Are they recognized by workshop as Struts/JSF/Hibernate app?
Please send the .log to [email protected]

[svn:fx-trunk] 17790: fix the samples.

Revision: 17790
Revision: 17790
Author:   [email protected]
Date:     2010-09-21 12:52:57 -0700 (Tue, 21 Sep 2010)
Log Message:
fix the samples. Have them refer to 10.1 playerglobal
QE notes: no
Doc notes: no
Bugs: no
Reviewer:no
Tests run: no
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/samples/themes/arcade/build.xml
    flex/sdk/trunk/samples/themes/cobalt/build.xml
    flex/sdk/trunk/samples/themes/graphite/build.xml
    flex/sdk/trunk/samples/themes/zen/build.xml

[svn] 746: creating flex-sdk-description. xml is no longer a build machine only function, it will happen in the build .xml.

Revision: 746
Author: [email protected]
Date: 2008-03-05 10:49:48 -0800 (Wed, 05 Mar 2008)
Log Message:
creating flex-sdk-description.xml is no longer a build machine only function, it will happen in the build.xml. There are 3 tokens in the flex-sdk-description.xml file in collateral/en_US/. The release and version vars are set in the build.properties file. build.number can be manually set in the properties in build.xml or can be passed in when building the SDK by using -Dbuild.number= , the default is "workspace"
Modified Paths:
flex/sdk/trunk/build.properties
flex/sdk/trunk/build.xml
Added Paths:
flex/sdk/trunk/collateral/en_US/flex-sdk-description.xml

I'll add that when I run devenv.exe with the flag /TFSLink, VS opens a Team Explorer window that contains the following text:
An exception was encountered while constructing the content of this frame. This information is also logged in "C:\Users\<username>\AppData\Roaming\Microsoft\VisualStudio\11.0\ActivityLog.xml".Exception details:System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.VisualStudio.Shell.Interop.IVsShell5.LoadPackageWithContext(Guid& packageGuid, Int32 reason, Guid& context) at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.GetPackage() at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.ConstructContent()

[svn:bz-3.x] 15191: Minor update to the build. xml and only make files write protected with chmod.

Revision: 15191
Revision: 15191
Author:   [email protected]
Date:     2010-04-01 07:06:21 -0700 (Thu, 01 Apr 2010)
Log Message:
Minor update to the build.xml and only make files write protected with chmod.
Modified Paths:
    blazeds/branches/3.x/modules/sdk/build.xml

DyNamic I agree that is sounds like you may be facing a network configuration issue. Please let your network people know that you need access to the following servers and ports to download Adobe applications through the Adobe Application Manager:
ccmdls.adobe.com:443
ims-na1.adobelogin.com:443
na1r.services.adobe.com:443
prod-rel-ffc-ccm.oobesaas.adobe.com:443
lm.licenses.adobe.com:443
In addition for updates to download properly you will also need access to the following servers:
http://www.adobe.com/:80
htttp:///swupmf.adobe.com/:80
http://swupdl.adobe.com/:80
http://crl.adobe.com/:80

[svn:fx-trunk] 10051: fix the build. xml that we include in the package in the frameworks directory.

Similar Messages

Maybe you are looking for