Petals Studio

Provide an integration with m2eclipse

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 1.1.1
  • Fix Version/s: 1.3.4
  • Component/s: Studio Product
  • Security Level: Public
  • Description:
    Hide

    m2eclipse is an Eclipse toolset to work with Maven from Eclipse.
    It was already tested in the very first versions of Petals Studio but it was removed due to several constraints. However, it has now gained in usability and stability. Instead of writting code to execute Maven commands (in a shell) from Eclipse, the studio should use m2eclipse.

    The integration with m2eclipse will have to provide the following artifacts:

    • Register the Petals Maven artifacts as a Maven catalog in m2eclipse (currently not working for local catalogs).
    • Configure projects with dependencies if necessary (MavenProjectConfigurator).
    • Make sure the Petals packaging types (service-unit, service-assembly...) appear in the tooling and are correctly used.
    • Replace the current solution to create Petals components and shared libraries. This may need to make some code API in m2eclipse and thus require to propose pacthes in the project.

    m2eclipse moved in the Eclipse Foundation few months ago.
    Several things have changed. Therefore, this integration should wait for the Indigo release.

    Show
    m2eclipse is an Eclipse toolset to work with Maven from Eclipse. It was already tested in the very first versions of Petals Studio but it was removed due to several constraints. However, it has now gained in usability and stability. Instead of writting code to execute Maven commands (in a shell) from Eclipse, the studio should use m2eclipse. The integration with m2eclipse will have to provide the following artifacts:
    • Register the Petals Maven artifacts as a Maven catalog in m2eclipse (currently not working for local catalogs).
    • Configure projects with dependencies if necessary (MavenProjectConfigurator).
    • Make sure the Petals packaging types (service-unit, service-assembly...) appear in the tooling and are correctly used.
    • Replace the current solution to create Petals components and shared libraries. This may need to make some code API in m2eclipse and thus require to propose pacthes in the project.
    m2eclipse moved in the Eclipse Foundation few months ago. Several things have changed. Therefore, this integration should wait for the Indigo release.
  • Environment:
    All

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Zurczak added a comment - Mon, 30 May 2011 - 12:41:50 +0200

Commits # 1974 to # 1976: initial contribution

Show
Vincent Zurczak added a comment - Mon, 30 May 2011 - 12:41:50 +0200 Commits # 1974 to # 1976: initial contribution
Hide
Permalink
Vincent Zurczak added a comment - Thu, 13 Dec 2012 - 19:25:57 +0100

There are still issues with m2eclipse.
It sometimes remains heavy to use. People should be able to install it if they want. But it should not be part of the initial package.

Show
Vincent Zurczak added a comment - Thu, 13 Dec 2012 - 19:25:57 +0100 There are still issues with m2eclipse. It sometimes remains heavy to use. People should be able to install it if they want. But it should not be part of the initial package.

People

Dates

  • Created:
    Mon, 30 May 2011 - 12:33:42 +0200
    Updated:
    Tue, 2 Jul 2013 - 12:13:54 +0200
    Resolved:
    Thu, 13 Dec 2012 - 19:25:57 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.