facebook
  1. MyEclipse IDE
    2.  > 
  2. Maven for MyEclipse (Maven4MyEclipse)

Local Archetypes not working on MyEclipse Blue 10.6+

  1. MyEclipse IDE
    2.  > 
  2. Maven for MyEclipse (Maven4MyEclipse)
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • December 18, 2012 at 1:22 pm #333486 Reply

    jelebl1
    Member

    In MyEclipse 10.0, we used to be able to:

    1. Create a Maven Archetype from any project:

    mvn archetype:create-from-project

    2. Install the Archetype locally:

    cd target/generated-sources/archetype/
    mvn install

    3. And then try to create a new project in MyEclipse 10 using the archetype.

    New –> Maven Project –> Next –> Choose “Default Local” Catalog and pick newly created archetype. –> Next –> Finish

    In MyEclipse 10.6+, we always get this error message:

    Can’t rename C:\usr\local\worspace_archetype\MyProject

    We tried on several desktop that have MyEclipse 10.6+, and error can be reproduced everytime. I can provide an archetype exemple, if needed.

    Attachments:
    You must be logged in to view attached files.
    December 19, 2012 at 5:04 am #333498 Reply

    support-swapna
    Moderator

    jelebl1,

    Sorry that you are seeing this issue.

    1. Can you please update to version 10.7 and see if the issue exists ?
    2. Can you please provide us with the archetype example to help us replicate the issue at our end ?
    3. Attach the entire contents of the .log file which is located at <workspace dir>/.metadata/.log to help us investigate further.

    December 19, 2012 at 7:28 am #333505 Reply

    jelebl1
    Member

    1. I tested with 10.7 and the issue still exists
    2. I put it in attachment. Unzip it and and run mvn clean install in root folder to publish it in your local catalog.
    3. Here’s the content of the log file:

    !ENTRY org.eclipse.m2e.core 4 -1 2012-12-19 08:21:43.522
!MESSAGE Can't rename C:\usr\local\workspace_archetype\MyHelloWorld.

!ENTRY org.eclipse.m2e.logback.appender 2 0 2012-12-19 08:21:45.585
!MESSAGE AsyncHttpClient.close() hasn't been invoked, which may produce file descriptor leaks

    Please tell me if you need anything else.

    Attachments:
    You must be logged in to view attached files.
    December 20, 2012 at 5:02 am #333553 Reply

    support-swapna
    Moderator

    jelebl1,

    Thank you for the details. I have escalated it to the dev team to investigate further.
    Sorry for inconvenience caused.

    December 20, 2012 at 1:38 pm #333568 Reply

    support-piotr
    Participant

    jelebl1,

    When I used Maven shipped with MyEclipse, I was able to install archetype and use it from within MyEclipse. However, when I used Maven installed in my system, to create and install the archetype, I’ve got some problems with using the archetype in MyEclipse. Unfortunately the pom.xml does contain specific to your company repository and I am missing parent pom.xml, which is not available in the default Maven repository. I have simply removed it, but I cannot be sure for 100% of the solution is such a case.

    MyEclipse is shipped with Maven 3.0.2, the version of Maven available under my system is 3.0.4. It would be best if you use the same version of Maven if working outside of MyEclipse. If you want to change version of Maven used within MyEclipse, please open Window->Preferences and navigate to MyEclipse/Maven4MyEclipse/Installation and add another installation. Note that the embedded one will be still used in some cases.

    Let us know how that works for you!

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)
Reply To: Local Archetypes not working on MyEclipse Blue 10.6+

You must be logged in to post in the forum log in