Skip to main content
aboutsummaryrefslogtreecommitdiffstats
path: root/org.eclipse.m2e.cliresolver30
AgeCommit message (Collapse)AuthorFilesLines
2011-07-31removed stale/redundant eclipse metadata filesIgor Fedorenko6-321/+0
Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
2011-06-08new version 1.0.100-SNAPSHOTIgor Fedorenko1-1/+1
Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
2011-04-01Rolled back incorrect version changevladt1-1/+1
2011-03-21new version 0.14.0-SNAPSHOTvladt1-1/+1
2011-02-24338149 fixed workspace dependency resolution in some casesIgor Fedorenko2-1/+277
Dependency resolution was broken when project packaging type was different from file extension of project's primary artifact, like it is the case for maven-plugin projects that have file extension jar. The solution was to change workspace state file format to use artifact extension instead of project packaging type and update maven 2.x and maven 3.0-beta-2 workspace resolvers to use artifact file extension to match workspace projects with artifacts. Aether-based workspace resolver was already using file extension. Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
2011-02-23335701 discover required m2e extensions during project importIgor Fedorenko2-3/+1
Introduced ability to see project lifecycle mapping configuration as part of import wizard and to check m2e marketplace for extensions that provide support for non-covered mojo executions and unsupported packaging types. This is a proof-of-concept implemenation. UI is completely throw-away code. Backend requires significact work as well. Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
2011-02-11utf-8Igor Fedorenko1-2/+2
Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
2011-02-10335972, 335722 new maven.runtime dependenciesIgor Fedorenko1-2/+2
maven 3.0.2 aether 1.10.1 async-http-client 1.6.0 netty 3.2.4.Final Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
2011-02-10Cosmetics/cleanupvladt1-0/+3
2011-02-08Cleanupvladt1-5/+0
2011-02-02335719: error marker when project configuration update is requiredIgor Fedorenko1-3/+0
Separated project effective lifecycle mapping metadata and made it persistent member of MavenProjectFacade. LifecycleMapping instances do not have any project specific state as a result of this change. Added (partially implemented) logic to perform effective lifecycle mapping metadata comparison during whenever project pom.xml change is detected. Error marker is added to project if mapping has change and/or interesting mojo execution configuration has changed. Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
2011-01-21.settings fileIgor Fedorenko1-0/+3
Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
2011-01-21switched to org.eclipse.m2e for selfhostingIgor Fedorenko2-10/+2
Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
2011-01-21MNGECLIPSE-2746 - Moved setting marker attributes into ↵Matthew Piggott1-3/+0
LifecycleMappingProblemInfo
2010-12-22MNGECLIPSE-2676 workspace resolution does not work for external maven 3.0 ↵Igor Fedorenko1-3/+3
runtimes Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
2010-12-21Cleanupvladt1-0/+8
2010-12-21use proper groupId and artifactIdIgor Fedorenko1-6/+6
Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
2010-12-21moved cliresolver from githubIgor Fedorenko10-0/+296
Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>

    Back to the top