Add an attachment proposed patch, testcase, etc. None edit Description John Himpel Problem Occurred 'Retrieving archetypes: An internal error occurred during: Always Steps to Reproduce: Comment 1 Roland Grunberg ArchetypeCatalog cannot be found by org.
Comment 3 Roland Grunberg Comment 4 Mikolaj Izdebski Earlier I did the same. No exeptions show up, but the list of archetypes is empty.
Besides that I don't know how this should properly be fixed other than hacking manifests. Comment 5 John Himpel Once I increased the size of that partition I had listing of archetypes. Although yes, that would probably be the approach to add an archetype from a catalog that isn't present.
Comment 7 John Himpel I looked in Koji and didn't see anything that looked like it included these changes, but I'm certainly not an expert at interpreting Change Logs. Comment 8 Gerard Ryan Unfortunately I haven't been much help, since I was away on holidays for a while, and came back to a dead laptop.
I'll hopefully have a usable machine sometime soon. Comment 9 Gerard Ryan At this point, the F20 branch will diverge from Rawhide. There's already a 1. Is it ok for there to be a 1. I feel like maybe F20 should go to 1. Does that make sense? If so, I'll submit an update after work tomorrow or if anyone else would like to do it before then, feel free. Comment 10 Gerard Ryan I'm not so good at thinking of these things late at night!
I'll do that later and submit an update. Comment 11 Mikolaj Izdebski Youn could bump release in F20 branch in one of the following ways: In either case upgrade path from F20 to F21 is retained. That works too, until the difference becomes too big to effectively maintain both versions using conditionals. Comment 12 Gerard Ryan Good point, although there wouldn't necessarily be too many now, that number could grow a lot if we went down that path, and may not get cleaned up much.
I've gone with your first solution: Comment 13 Fedora Update System Please go to the following url: Comment 15 Mikolaj Izdebski I can see the list of archetypes and I can select one, but creating project fails see attached log. Comment 16 Gerard Ryan Yeah, I'm seeing that too.
I'll try to have a look at it this weekend. I think it's probably due to the hacks I did to get this to build with maven 3. I might be able to backport some stuff from m2e-core Comment 17 Fedora Update System If problems still persist, please make note of it in this bug report.
Comment 18 John Himpel I select "Use default Workspace location" and click "Next". An error message appears at the top of the next dialog box saying "No archetypes currently available. The archetype list will refresh when the indexes finish updating. Then both drop to normal idle usage levels. The error message remains and nothing appears in the list of archetypes. Perhaps there's a maven rpm that I'm missing? I assumed that eclipse-m2e-core would install everything I needed, but maybe that's not the case.
Comment 19 Roland Grunberg I don't see eclipse-m2e-core You could do something like: Comment 20 Andreas Bierfert Comment 21 John Himpel I've run eclipse from the command line with all the debug options that I could find and nothing unusual appears. Hopefully, now the devCon has just finished, some of the Java guys can look into this.
My symptoms are now somewhat different that the symptoms described originally. A small red circle with a white "x" inside No archetypes currently available. In the Windows version, Eclipse fetches the various catalogs and presents a list of archetypes. In Fedora, nothing happens. Comment 22 Whistler Comment 23 John Himpel If anyone still needs this on F22, feel free to propose a patch!
Comment 26 Fedora Update System