Home › Forums › Jspresso core project › Jspresso users

Initial problem with trying the CRUD 5 minute demo on new installation..

11 posts / 0 new
Login or register to post comments
Last post
Wed, 12/07/2011 - 04:07
#1
Rick
Offline
Joined: 12/07/2011
Initial problem with trying the CRUD 5 minute demo on new installation..

So, I'm trying out Jspresso and ran into a snag on my OSX-Lion machine.. I've got a fresh installation of Eclipse Indigo and installed all of the items in that tutorial page OK but when I put the new Maven remote catalog in place and press the verify button, it says there are 0 items in the catalog.  Later when creating the project from the empty catalog, I'm stuck.. I did have it working once but had other issues so I blew away my Eclipse installation and started over and it's been a problem since.. Any ideas on how to proceed?  I'll probably see about starting over again this evening and see if I can get past this but I tried it 2-3 times last night with no luck..

-- Rick

 

Top
Tags:
Wed, 12/07/2011 - 08:33
#2
Rick
Offline
Joined: 12/07/2011
Ok.. Got past that hurdle.. I

Ok.. Got past that hurdle.. I had to blow away ALL eclipse fragments everywhere and then it behaved.. Unfortunately I'm now getting a build failure when doing the "mvn package" and get the following errors :

 

 

[INFO] ------------------------------------------------------------------------

[INFO] Building Example Application - Webapp 0.0.1-SNAPSHOT

[INFO] ------------------------------------------------------------------------

[WARNING] The POM for com.adobe.blazeds:blazeds-common:jar:4.0.0.14931 is missing, no dependency information available

[WARNING] The POM for com.adobe.blazeds:blazeds-core:jar:4.0.0.14931 is missing, no dependency information available

[WARNING] The POM for com.adobe.blazeds:blazeds-remoting:jar:4.0.0.14931 is missing, no dependency information available

[WARNING] The POM for com.adobe.blazeds:blazeds-proxy:jar:4.0.0.14931 is missing, no dependency information available

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Example Application ............................... SUCCESS [0.014s]

[INFO] Example Application - Core ........................ SUCCESS [16.459s]

[INFO] Example Application - Startup ..................... SUCCESS [0.000s]

[INFO] Example Application - Startup - Swing ............. SUCCESS [11.255s]

[INFO] Example Application - Startup - Remote ............ SUCCESS [0.699s]

[INFO] Example Application - Startup - Flex .............. SUCCESS [0.001s]

[INFO] Example Application - Startup - Flex - Config ..... SUCCESS [0.107s]

[INFO] Example Application - Startup - Flex - Client ..... SUCCESS [26.879s]

[INFO] Example Application - Startup - Qooxdoo ........... SUCCESS [0.000s]

[INFO] Example Application - Startup - Qooxdoo - Client .. SUCCESS [19.550s]

[INFO] Example Application - Startup - Qooxdoo - Server .. SUCCESS [0.906s]

[INFO] Example Application - Webapp ...................... FAILURE [0.108s]

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 1:19.519s

[INFO] Finished at: Tue Dec 06 22:27:08 PST 2011

[INFO] Final Memory: 38M/123M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal on project helloworld-webapp: Could not resolve dependencies for project com.example.helloworld:helloworld-webapp:war:0.0.1-SNAPSHOT: The following artifacts could not be resolved: com.adobe.blazeds:blazeds-common:jar:4.0.0.14931, com.adobe.blazeds:blazeds-core:jar:4.0.0.14931, com.adobe.blazeds:blazeds-remoting:jar:4.0.0.14931, com.adobe.blazeds:blazeds-proxy:jar:4.0.0.14931: Failure to find com.adobe.blazeds:blazeds-common:jar:4.0.0.14931 in http://repository.jspresso.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of jspresso-repository has elapsed or updates are forced -> [Help 1]

[ERROR] 

Any ideas?  This is under MacOSX Lion if it matters..

 

Top
Wed, 12/07/2011 - 09:50
#3
vvandens
Offline
Joined: 05/29/2008
blazeds repo

Hi Rick,

Welcome to Jspresso !

The blazeds 4 artifacts are only available in the springframework maven 2 repository which is hosted on amazon. This repo is correctly defined on the Jspresso root pom so Maven should be able to download them. Maybe did you have some network failure when building ? In that case, you can force an update with "mvn -U clean package".

as a reference here is the s3 browsing URL for the Springframework repo (and the BlazeDS 4 artifacts) :

http://s3browse.springsource.com/browse/maven.springframework.org/extern...

 

Best,

Vincent

Top
Wed, 12/07/2011 - 17:43
#4
Rick
Offline
Joined: 12/07/2011
Hmm.. I tried the 'clean' and

Hmm.. I tried the 'clean' and package as indicated above and still get the same results.. Should I blow-away my project and try again?  Perhaps I'll try the 10 minute demo using only the command line this time and see if that makes a difference -- the project in this case (in eclipse) was setup in Eclipse..

Top
Wed, 12/07/2011 - 18:10
#5
vvandens
Offline
Joined: 05/29/2008
Amazon S3

It might be linked to the reposirtory being hosted on Amazon s3. I know that, for instance, you cannot directly access the repo using a browser.

I don't think it has anything to do with your project, so don't blow away anything. Trying the command line on your existing project is a good idea. If it works better, then I will perhaps mirro these blazeds artifacts on te Jspresso repo which is a more "classic" one.

Top
Wed, 12/07/2011 - 18:21
#6
Rick
Offline
Joined: 12/07/2011
Is there a way to tell if

Is there a way to tell if Maven can't access the Amazon S3 files?  I was going to paste the entire log but it's rather lengthy.. Unfortunately, I'm at work right now so I do not have access to the machine but I might see if I can setup the same scenario here at work but it's on an XP Pro machine which may require extra steps possibly.. Otherwise I'll have to wait until tonight..

Top
Wed, 12/07/2011 - 20:37
#7
vvandens
Offline
Joined: 05/29/2008
If there is a problem, it is

If there is a problem, it is from M2E but I strongly doubt. The best way to tell is to launch "mvn -U package" and see if it fails the same way.

However, I've never heard of such problems before, but who knows...

Top
Wed, 12/07/2011 - 20:55
#8
vvandens
Offline
Joined: 05/29/2008
springframework repo is down

Well, I've just tried to remove the blazeDS 4 artifacts from my local repo and build the sample project again and... it's failing on the same error. The Spring external repo seems to be down actually; the magic of relying on the cloud ;-)

I will upload the Blazeds artifacts on the Jspresso maven repo tonight so that they should be downloadable again. Thanks for reporting the problem !

Cheers,

Vincent

Top
Wed, 12/07/2011 - 21:06
#9
vvandens
Offline
Joined: 05/29/2008
Done

Your project should build correctly again.

 

Vincent

Top
Wed, 12/07/2011 - 21:57
#10
Rick
Offline
Joined: 12/07/2011
Thanks for looking into it

Thanks for looking into it and fixing the problem.. I'll give it a shot tonight!  Thanks again for the quick responses!

Top
Thu, 12/08/2011 - 06:10
#11
Rick
Offline
Joined: 12/07/2011
Cool beans!  It's working

Cool beans!  It's working now!!  

Top
‹ Previous topic: Using FusionCharts -- paid version.. Next topic: [Problem] with bidirectional 1-N relationship ›