We made some progress. Doing a complete rebuild of the LCDS project
from SVN fixed some of the problems. (Does this mean that to install
Flex 3 you need to recreate all your previous projects rather than
just import them into the new workspace?)
Then we kept getting these errors in our log:
!ENTRY com.adobe.flexbuilder.project 4 43 2007-12-11 14:58:53.516
!MESSAGE Uncaught exception in compiler
!STACK 0
java.lang.NullPointerException
at
flex2.compiler.as3.managed.ManagedFirstPassEvaluator.evaluate
(ManagedFirstPassEvaluator.java:153)
If you are getting this, take a look at this blog post:
http://blog.riait.co.uk/2007/10/09/managed-sucks/
Is [Managed] no longer valid? We took those out and the build seems
to work without errors.
Lastly, our html wrapper is not working and thus no Flex being
displayed in the browser unless we navigate directly to the swf file.
We are getting close, but I will say this 'upgrade' process is not
easy and were we not on Subversion it could be even worse. It has
taken us almost all day to get our project to this point, and we
still are not completely working. (I guess that's why it's still
BETA.) Anyway, if we can help smooth out this process, we are happy
to help so that other's do not have to go through this.
- Kevin
On Dec 11, 2007, at 1:30 PM, Kevin wrote:
We made the decision to give Flex 3 Beta 2 a try with a current
project since we need some of the enhancements to Flex 3.. However,
we seem to not be able to get past the initial installation phase.
All our projects are LCDS project so I am wondering if that is a
problem. We would greatly appreciate any help in resolving these
issues since we would rather help isolate these problems than revert
to Flex 2 (Everything is backed up so we can go back easily.)
Here is what we did and the problems we had:
We deleted our Flex 2 plugin folder
We removed the flex 2 plugin files from the Eclipse plugin folder
We deleted our old workspace and created a new blank workspace (NOTE:
We only did this after having problems as finding this bug note:
https://bugs.adobe.com/jira/browse/FB-994)
We then installed the Flex 3 plugin from the installer. This install
appeared to work fine.
Next we tried to Import a small Flex project from our old workspace.
When the project tries to build we get the errors saying it can't
find certain directories in our workspace. However, these
directories are there. Any thoughts? Right now we are going to try
to build the project from scratch from our SVN server. If that works
then I am assuming there is a backwards compatibility problem.
Thanks for the help, we really want to try to get Flex 3 to work.
- Kevin
!MESSAGE Resource /OurApp/assets/icons does not exist.
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Resource /
dBocl Login/assets/icons does not exist.
!MESSAGE Resource /OurApp/assets/icons does not exist.
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Resource /
dBocl Login/assets/icons does not exist.
!MESSAGE Resource /OurApp/assets/icons does not exist.
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Resource /
dBocl Login/assets/icons does not exist.
