| Home » Archived » Maven Integration (M2E) » Importing legacy artifacts Into M2 Repository from Eclipse
 Goto Forum:| 
| Importing legacy artifacts Into M2 Repository from Eclipse [message #1271] | Fri, 18 April 2008 02:52  |  | 
| Eclipse User  |  |  |  |  | Originally posted by: cl.houze.etat.ge.ch 
 Hi M2E team,
 
 first of all, thanks to all Maven and M2E contributors for the great job
 you've done. Here in our organization (Computer dept for Geneva State,
 Switzerland) we've packaged a software dev infarstructure based on Maven,
 Eclipse Europa(J2ee), M2Eclipse, Jonas, Cargo, and some others plugins
 plus a set of in-house parents POMs, archetypes, and tools enforcing our
 standards, for a load of new and existing applications(this including
 critical applications such as taxation processing). We plan to provide
 continuous integration this summer for our dev teams, and migrate to Maven
 as many projects as possible for better build quality.
 
 This is why we're more than happy about the M2Eclipse project proposal.
 
 One of the in-house tool we've done is an "artifact importer": in fact,
 it's a gui layer above "mvn install:install / deploy:deploy" that allows
 to easily import legacy artifacts and associated sources, because you may
 want to use (many) artifacts from projects that wont be converted to
 Maven. I think I've seen this kind of need somewhere in Maven mailing
 list. We're currently including this utility as an Eclipse plugin. Maybe
 m2e could include such utility, or the community could be interested by
 this, but I dont know what is the process for submitting code, so let me
 know if giving this makes sense.
 
 Now, to get back to M2E current version 0.9.2, it looks great, and we're
 going to upgrade soon. As it's very promising, for future versions we'd
 like to get real seamless integration between any WTP project type and
 Maven project structure.
 
 Anyway, wishing success to this initiative !
 
 Christian-Luc
 |  |  |  |  | 
| Re: Importing legacy artifacts Into M2 Repository from Eclipse [message #3114 is a reply to message #1271] | Fri, 18 April 2008 11:24   |  | 
| Eclipse User  |  |  |  |  | Originally posted by: igorfie.yahoo.com 
 Chrisrtian-Luc Houze wrote:
 > Hi M2E team,
 >
 > first of all, thanks to all Maven and M2E contributors for the great job
 > you've done. Here in our organization (Computer dept for Geneva State,
 > Switzerland) we've packaged a software dev infarstructure based on
 > Maven, Eclipse Europa(J2ee), M2Eclipse, Jonas, Cargo, and some others
 > plugins plus a set of in-house parents POMs, archetypes, and tools
 > enforcing our standards, for a load of new and existing
 > applications(this including critical applications such as taxation
 > processing). We plan to provide continuous integration this summer for
 > our dev teams, and migrate to Maven as many projects as possible for
 > better build quality.
 >
 > This is why we're more than happy about the M2Eclipse project proposal.
 >
 > One of the in-house tool we've done is an "artifact importer": in fact,
 > it's a gui layer above "mvn install:install / deploy:deploy" that allows
 > to easily import legacy artifacts and associated sources, because you
 > may want to use (many) artifacts from projects that wont be converted to
 > Maven. I think I've seen this kind of need somewhere in Maven mailing
 > list. We're currently including this utility as an Eclipse plugin. Maybe
 > m2e could include such utility, or the community could be interested by
 > this, but I dont know what is the process for submitting code, so let me
 > know if giving this makes sense.
 
 The best way to start is to create an enhancement request in M2E JIRA
 (http://jira.codehaus.org/browse/MNGECLIPSE) and attach proposed patch
 there.
 
 > Now, to get back to M2E current version 0.9.2, it looks great, and we're
 > going to upgrade soon. As it's very promising, for future versions we'd
 > like to get real seamless integration between any WTP project type and
 > Maven project structure.
 
 There is a number of bug/enhancement requests about M2E/WTP integration
 in M2E JIRA already. To help us prioritize work better, it would be
 great if you could file enhancement requests and/or vote for existing
 JIRAs. Also, have a look at current M2E/WTP integration proposal
 http://archive.m2eclipse.codehaus.org/dev/47FEEAA8.2040406%4 0md.pp.ru
 and you're more than welcome to join the discussion.
 
 --
 Regards,
 Igor Fedorenko
 |  |  |  |  | 
| Re: Importing legacy artifacts Into M2 Repository from Eclipse [message #3146 is a reply to message #1271] | Fri, 18 April 2008 16:01  |  | 
| Eclipse User  |  |  |  |  | Chrisrtian-Luc Houze wrote: > One of the in-house tool we've done is an "artifact importer": in
 > fact, it's a gui layer above "mvn install:install / deploy:deploy"
 > that allows to easily import legacy artifacts and associated sources,
 > because you may want to use (many) artifacts from projects that wont
 > be converted to Maven.
 I am somewhat confused, because those goals only work for Maven
 projects that have existing poms. Though there is install:install-file
 and deploy:deploy-file goals that allow to deploy arbitrary jars.
 > I think I've seen this kind of need somewhere in Maven mailing list.
 > We're currently including this utility as an Eclipse plugin. Maybe m2e
 > could include such utility, or the community could be interested by
 > this, but I dont know what is the process for submitting code, so let
 > me know if giving this makes sense.
 Right. I think that could be a good tool (perhaps it would be useful
 to package it as a standalone RCP app). We had something simple
 contributed at some point, but it didn't make into the code (totally my
 fault). http://jira.codehaus.org/browse/MNGECLIPSE-335
 
 One thing that might be interesting to cover is how to generate proper
 maven metadata. For example, assign parent poms with all project
 details, analyze and populate dependencies in generated poms and so on.
 So, it isn't small task if you want to go whole nine yards. Though all
 pieces are already there and just need to be assembled together with
 nice UI frontend.
 
 More over, if we deal with Eclipse/osgi artifacts, things get bit more
 complicated because of mapping from osgi naming conventions to Maven.
 There are some Maven plugins to handle that, and we also have this
 covered in Tycho plugins that we are using for building Eclipse plugins
 and RCP applications.
 > Now, to get back to M2E current version 0.9.2, it looks great, and
 > we're going to upgrade soon. As it's very promising, for future
 > versions we'd like to get real seamless integration between any WTP
 > project type and Maven project structure.
 WTP integration is certainly in our plans. There is some experimental
 work in progress already happening, but we could use additional help
 with that. You can watch the following wiki page for that and/or add
 your use cases and ideas there.
 http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+ WTP
 
 regards,
 Eugene
 |  |  |  | 
 
 
 Current Time: Thu Oct 30 13:07:48 EDT 2025 
 Powered by FUDForum . Page generated in 0.03853 seconds |