[xwiki-devs] m2eclipse and xwiki-commons
Hello devs, I just finished porting my XWiki development environment from Windows 7 to Ubuntu 12.04. I am now able to build all projects from the command line without errors. I'm working with the master branch from Git. I have Eclipse Juno installed with plugins that include m2eclipse (the version from the Eclipse update site) and AJDT. I am now trying to import the entire xwiki-commons Maven project into Eclipse. Just as happened under Windows (which I never asked about, since I was still trying to get command line builds to work), there are three Maven goals (plugins) in the xwiki-commons projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin, maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me some hints on how to resolve these mapping problems? Googling for answers about this hasn't yielded anything that I can understand :-) --Gary
Hi Gary, On Jul 26, 2012, at 3:26 AM, Gary Kopp wrote:
Hello devs,
I just finished porting my XWiki development environment from Windows 7 to Ubuntu 12.04. I am now able to build all projects from the command line without errors. I'm working with the master branch from Git. I have Eclipse Juno installed with plugins that include m2eclipse (the version from the Eclipse update site) and AJDT. I am now trying to import the entire xwiki-commons Maven project into Eclipse. Just as happened under Windows (which I never asked about, since I was still trying to get command line builds to work), there are three Maven goals (plugins) in the xwiki-commons projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin, maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me some hints on how to resolve these mapping problems? Googling for answers about this hasn't yielded anything that I can understand :-)
I'll let the Eclipse lovers answer your question… On my side I'm an IntelliJ IDEA fanboy ;) (and Maven works OOB on IntelliJ IDEA BTW) Thanks -Vincent
On Thu, Jul 26, 2012 at 4:26 AM, Gary Kopp <[email protected]> wrote:
Hello devs,
I just finished porting my XWiki development environment from Windows 7 to Ubuntu 12.04. I am now able to build all projects from the command line without errors. I'm working with the master branch from Git. I have Eclipse Juno installed with plugins that include m2eclipse (the version from the Eclipse update site) and AJDT. I am now trying to import the entire xwiki-commons Maven project into Eclipse. Just as happened under Windows (which I never asked about, since I was still trying to get command line builds to work), there are three Maven goals (plugins) in the xwiki-commons projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin, maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me some hints on how to resolve these mapping problems? Googling for answers about this hasn't yielded anything that I can understand :-)
I usually only open what I'm working on in Eclipse because otherwise with commons/rendering/platform it's a lot of projects and it's slowing down everything for things you probably don't care. As for the missing mapping between Maven plugins and m2e handlers: * aspectJ-maven-plugin: could not find any either, there used to be one but it does not work anymore on 4.x. There is no official version of AJDT for 4.x so that's probably why it's not yet fixed but it should be quickly fixed as soon as there is an official AJDT for 4.x. In that case it's not very hard to setup AJDT yourself properly for the project, basically it's just about enabling it for the project and adding the right folder in the list of source folders if I remember well. But aspectj is used only in some legacy projects to produce retro-compatibility APIs so you are probably not going to need it very often. * maven-antrun-plugin: used for a hack in one of the legacy projects so for now it should not be a big deal for you * maven-remote-resources-plugin: not sure why you have issue with this one, m2e ignore it by default and just indicate it in a warning
--Gary
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Thu, Jul 26, 2012 at 12:23 PM, Thomas Mortagne <[email protected]> wrote:
On Thu, Jul 26, 2012 at 4:26 AM, Gary Kopp <[email protected]> wrote:
Hello devs,
I just finished porting my XWiki development environment from Windows 7 to Ubuntu 12.04. I am now able to build all projects from the command line without errors. I'm working with the master branch from Git. I have Eclipse Juno installed with plugins that include m2eclipse (the version from the Eclipse update site) and AJDT. I am now trying to import the entire xwiki-commons Maven project into Eclipse. Just as happened under Windows (which I never asked about, since I was still trying to get command line builds to work), there are three Maven goals (plugins) in the xwiki-commons projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin, maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me some hints on how to resolve these mapping problems? Googling for answers about this hasn't yielded anything that I can understand :-)
I usually only open what I'm working on in Eclipse because otherwise with commons/rendering/platform it's a lot of projects and it's slowing down everything for things you probably don't care.
As for the missing mapping between Maven plugins and m2e handlers: * aspectJ-maven-plugin: could not find any either, there used to be one but it does not work anymore on 4.x. There is no official version of AJDT for 4.x so that's probably why it's not yet fixed but it
Actually there is one now since 4.2 (there was not not very long ago) so I guess (hope) the handler is probably going to be fixed in not too long.
should be quickly fixed as soon as there is an official AJDT for 4.x. In that case it's not very hard to setup AJDT yourself properly for the project, basically it's just about enabling it for the project and adding the right folder in the list of source folders if I remember well. But aspectj is used only in some legacy projects to produce retro-compatibility APIs so you are probably not going to need it very often. * maven-antrun-plugin: used for a hack in one of the legacy projects so for now it should not be a big deal for you * maven-remote-resources-plugin: not sure why you have issue with this one, m2e ignore it by default and just indicate it in a warning
--Gary
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
-- Thomas Mortagne
Thomas, On a minor note, I guess I could "solve" the aspect plugin problem by falling back to Indigo. And perhaps solve the other two problems by not importing the two projects that are involved -- xwiki-commons-component-legacy-default and xwiki-commons-tool-license-resources, although this might result in a non-buildable project tree in Eclipse anyway. On a more significant note, what I intended to do may be infeasible. And possibly never attempted. My goal is to study virtually every part of the code base. With Eclipse I could easily follow class and method references in as much depth as I wanted. And I could theoretically use container-based debugging to trace execution flow through the entire application. But all of that requires that I have the entire code base in one Eclipse workspace, and that's what I was starting out to build. Would that be hopeless/fruitless? I do have alternatives to Eclipse for at least part of my goal, but not for real-time debugging. --Gary -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Thomas Mortagne Sent: Thursday, July 26, 2012 3:25 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons On Thu, Jul 26, 2012 at 12:23 PM, Thomas Mortagne <[email protected]> wrote:
On Thu, Jul 26, 2012 at 4:26 AM, Gary Kopp <[email protected]> wrote:
Hello devs,
I just finished porting my XWiki development environment from Windows 7 to Ubuntu 12.04. I am now able to build all projects from the command line without errors. I'm working with the master branch from Git. I have Eclipse Juno installed with plugins that include m2eclipse (the version from the Eclipse update site) and AJDT. I am now trying to import the entire xwiki-commons Maven project into Eclipse. Just as happened under Windows (which I never asked about, since I was still trying to get command line builds to work), there are three Maven goals (plugins) in the xwiki-commons projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin, maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me some hints on how to resolve these mapping problems? Googling for answers about this hasn't yielded anything that I can understand :-)
I usually only open what I'm working on in Eclipse because otherwise with commons/rendering/platform it's a lot of projects and it's slowing down everything for things you probably don't care.
As for the missing mapping between Maven plugins and m2e handlers: * aspectJ-maven-plugin: could not find any either, there used to be one but it does not work anymore on 4.x. There is no official version of AJDT for 4.x so that's probably why it's not yet fixed but it
Actually there is one now since 4.2 (there was not not very long ago) so I guess (hope) the handler is probably going to be fixed in not too long.
should be quickly fixed as soon as there is an official AJDT for 4.x. In that case it's not very hard to setup AJDT yourself properly for the project, basically it's just about enabling it for the project and adding the right folder in the list of source folders if I remember well. But aspectj is used only in some legacy projects to produce retro-compatibility APIs so you are probably not going to need it very often. * maven-antrun-plugin: used for a hack in one of the legacy projects so for now it should not be a big deal for you * maven-remote-resources-plugin: not sure why you have issue with this one, m2e ignore it by default and just indicate it in a warning
--Gary
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 07/26/2012 07:08 AM, Gary Kopp wrote:
Thomas,
On a minor note, I guess I could "solve" the aspect plugin problem by falling back to Indigo. And perhaps solve the other two problems by not importing the two projects that are involved -- xwiki-commons-component-legacy-default and xwiki-commons-tool-license-resources, although this might result in a non-buildable project tree in Eclipse anyway.
On a more significant note, what I intended to do may be infeasible. And possibly never attempted. My goal is to study virtually every part of the code base. With Eclipse I could easily follow class and method references in as much depth as I wanted. And I could theoretically use container-based debugging to trace execution flow through the entire application. But all of that requires that I have the entire code base in one Eclipse workspace, and that's what I was starting out to build. Would that be hopeless/fruitless? I do have alternatives to Eclipse for at least part of my goal, but not for real-time debugging.
What works for me is to skip m2eclipse completely. I use Eclipse for browsing the code, and command line tools (git, mvn) for the rest. To prepare the eclipse projects, just use this line: mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true -Pci,integration-tests,legacy,hsqldb,jetty Then you can File->Import->Existing projects into workspace to get the projects built by maven into Eclipse. The problem is that whenever modules change, you'll have to regenerate/reimport the modules.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Thomas Mortagne Sent: Thursday, July 26, 2012 3:25 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons
On Thu, Jul 26, 2012 at 12:23 PM, Thomas Mortagne <[email protected]> wrote:
On Thu, Jul 26, 2012 at 4:26 AM, Gary Kopp <[email protected]> wrote:
Hello devs,
I just finished porting my XWiki development environment from Windows 7 to Ubuntu 12.04. I am now able to build all projects from the command line without errors. I'm working with the master branch from Git. I have Eclipse Juno installed with plugins that include m2eclipse (the version from the Eclipse update site) and AJDT. I am now trying to import the entire xwiki-commons Maven project into Eclipse. Just as happened under Windows (which I never asked about, since I was still trying to get command line builds to work), there are three Maven goals (plugins) in the xwiki-commons projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin, maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me some hints on how to resolve these mapping problems? Googling for answers about this hasn't yielded anything that I can understand :-)
I usually only open what I'm working on in Eclipse because otherwise with commons/rendering/platform it's a lot of projects and it's slowing down everything for things you probably don't care.
As for the missing mapping between Maven plugins and m2e handlers: * aspectJ-maven-plugin: could not find any either, there used to be one but it does not work anymore on 4.x. There is no official version of AJDT for 4.x so that's probably why it's not yet fixed but it
Actually there is one now since 4.2 (there was not not very long ago) so I guess (hope) the handler is probably going to be fixed in not too long.
should be quickly fixed as soon as there is an official AJDT for 4.x. In that case it's not very hard to setup AJDT yourself properly for the project, basically it's just about enabling it for the project and adding the right folder in the list of source folders if I remember well. But aspectj is used only in some legacy projects to produce retro-compatibility APIs so you are probably not going to need it very often. * maven-antrun-plugin: used for a hack in one of the legacy projects so for now it should not be a big deal for you * maven-remote-resources-plugin: not sure why you have issue with this one, m2e ignore it by default and just indicate it in a warning
-- Sergiu Dumitriu http://purl.org/net/sergiu/
Thanks for confirming one of my suspicions, Sergiu. I've used the eclipse goal on other Maven-based projects where I approached things in basically the way you describe. But since there is no mention of that approach in the XWiki docs I was hesitant to assume it would work with the XWiki projects. Can I run the Maven eclipse goal at the root of each project, like xwiki-commons, and it will walk down through all the projects in the tree? --Gary -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sergiu Dumitriu Sent: Thursday, July 26, 2012 5:19 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons On 07/26/2012 07:08 AM, Gary Kopp wrote:
Thomas,
On a minor note, I guess I could "solve" the aspect plugin problem by falling back to Indigo. And perhaps solve the other two problems by not importing the two projects that are involved -- xwiki-commons-component-legacy-default and xwiki-commons-tool-license-resources, although this might result in a non-buildable project tree in Eclipse anyway.
On a more significant note, what I intended to do may be infeasible. And possibly never attempted. My goal is to study virtually every part of the code base. With Eclipse I could easily follow class and method references in as much depth as I wanted. And I could theoretically use container-based debugging to trace execution flow through the entire application. But all of that requires that I have the entire code base in one Eclipse workspace, and that's what I was starting out to build. Would that be hopeless/fruitless? I do have alternatives to Eclipse for at least part of my goal, but not for real-time debugging.
What works for me is to skip m2eclipse completely. I use Eclipse for browsing the code, and command line tools (git, mvn) for the rest. To prepare the eclipse projects, just use this line: mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true -Pci,integration-tests,legacy,hsqldb,jetty Then you can File->Import->Existing projects into workspace to get the projects built by maven into Eclipse. The problem is that whenever modules change, you'll have to regenerate/reimport the modules.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Thomas Mortagne Sent: Thursday, July 26, 2012 3:25 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons
On Thu, Jul 26, 2012 at 12:23 PM, Thomas Mortagne <[email protected]> wrote:
On Thu, Jul 26, 2012 at 4:26 AM, Gary Kopp <[email protected]> wrote:
Hello devs,
I just finished porting my XWiki development environment from Windows 7 to Ubuntu 12.04. I am now able to build all projects from the command line without errors. I'm working with the master branch from Git. I have Eclipse Juno installed with plugins that include m2eclipse (the version from the Eclipse update site) and AJDT. I am now trying to import the entire xwiki-commons Maven project into Eclipse. Just as happened under Windows (which I never asked about, since I was still trying to get command line builds to work), there are three Maven goals (plugins) in the xwiki-commons projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin, maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me some hints on how to resolve these mapping problems? Googling for answers about this hasn't yielded anything that I can understand :-)
I usually only open what I'm working on in Eclipse because otherwise with commons/rendering/platform it's a lot of projects and it's slowing down everything for things you probably don't care.
As for the missing mapping between Maven plugins and m2e handlers: * aspectJ-maven-plugin: could not find any either, there used to be one but it does not work anymore on 4.x. There is no official version of AJDT for 4.x so that's probably why it's not yet fixed but it
Actually there is one now since 4.2 (there was not not very long ago) so I guess (hope) the handler is probably going to be fixed in not too long.
should be quickly fixed as soon as there is an official AJDT for 4.x. In that case it's not very hard to setup AJDT yourself properly for the project, basically it's just about enabling it for the project and adding the right folder in the list of source folders if I remember well. But aspectj is used only in some legacy projects to produce retro-compatibility APIs so you are probably not going to need it very often. * maven-antrun-plugin: used for a hack in one of the legacy projects so for now it should not be a big deal for you * maven-remote-resources-plugin: not sure why you have issue with this one, m2e ignore it by default and just indicate it in a warning
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
I do use m2e and it's working great for me. For me having to regenerate everytime you modify a pom is a pain. On Thu, Jul 26, 2012 at 2:28 PM, Gary Kopp <[email protected]> wrote:
Thanks for confirming one of my suspicions, Sergiu. I've used the eclipse goal on other Maven-based projects where I approached things in basically the way you describe. But since there is no mention of that approach in the XWiki docs I was hesitant to assume it would work with the XWiki projects.
Can I run the Maven eclipse goal at the root of each project, like xwiki-commons, and it will walk down through all the projects in the tree?
--Gary
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sergiu Dumitriu Sent: Thursday, July 26, 2012 5:19 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons
On 07/26/2012 07:08 AM, Gary Kopp wrote:
Thomas,
On a minor note, I guess I could "solve" the aspect plugin problem by falling back to Indigo. And perhaps solve the other two problems by not importing the two projects that are involved -- xwiki-commons-component-legacy-default and xwiki-commons-tool-license-resources, although this might result in a non-buildable project tree in Eclipse anyway.
On a more significant note, what I intended to do may be infeasible. And possibly never attempted. My goal is to study virtually every part of the code base. With Eclipse I could easily follow class and method references in as much depth as I wanted. And I could theoretically use container-based debugging to trace execution flow through the entire application. But all of that requires that I have the entire code base in one Eclipse workspace, and that's what I was starting out to build. Would that be hopeless/fruitless? I do have alternatives to Eclipse for at least part of my goal, but not for real-time debugging.
What works for me is to skip m2eclipse completely. I use Eclipse for browsing the code, and command line tools (git, mvn) for the rest.
To prepare the eclipse projects, just use this line:
mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true -Pci,integration-tests,legacy,hsqldb,jetty
Then you can File->Import->Existing projects into workspace to get the projects built by maven into Eclipse. The problem is that whenever modules change, you'll have to regenerate/reimport the modules.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Thomas Mortagne Sent: Thursday, July 26, 2012 3:25 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons
On Thu, Jul 26, 2012 at 12:23 PM, Thomas Mortagne <[email protected]> wrote:
On Thu, Jul 26, 2012 at 4:26 AM, Gary Kopp <[email protected]> wrote:
Hello devs,
I just finished porting my XWiki development environment from Windows 7 to Ubuntu 12.04. I am now able to build all projects from the command line without errors. I'm working with the master branch from Git. I have Eclipse Juno installed with plugins that include m2eclipse (the version from the Eclipse update site) and AJDT. I am now trying to import the entire xwiki-commons Maven project into Eclipse. Just as happened under Windows (which I never asked about, since I was still trying to get command line builds to work), there are three Maven goals (plugins) in the xwiki-commons projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin, maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me some hints on how to resolve these mapping problems? Googling for answers about this hasn't yielded anything that I can understand :-)
I usually only open what I'm working on in Eclipse because otherwise with commons/rendering/platform it's a lot of projects and it's slowing down everything for things you probably don't care.
As for the missing mapping between Maven plugins and m2e handlers: * aspectJ-maven-plugin: could not find any either, there used to be one but it does not work anymore on 4.x. There is no official version of AJDT for 4.x so that's probably why it's not yet fixed but it
Actually there is one now since 4.2 (there was not not very long ago) so I guess (hope) the handler is probably going to be fixed in not too long.
should be quickly fixed as soon as there is an official AJDT for 4.x. In that case it's not very hard to setup AJDT yourself properly for the project, basically it's just about enabling it for the project and adding the right folder in the list of source folders if I remember well. But aspectj is used only in some legacy projects to produce retro-compatibility APIs so you are probably not going to need it very often. * maven-antrun-plugin: used for a hack in one of the legacy projects so for now it should not be a big deal for you * maven-remote-resources-plugin: not sure why you have issue with this one, m2e ignore it by default and just indicate it in a warning
-- Sergiu Dumitriu http://purl.org/net/sergiu/
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
The important thing to keep in mind is that maven or m2e will always get what you need from the repository when you don't provide it yourself so you really don't have to be able to build everything. On Thu, Jul 26, 2012 at 3:35 PM, Thomas Mortagne <[email protected]> wrote:
I do use m2e and it's working great for me. For me having to regenerate everytime you modify a pom is a pain.
On Thu, Jul 26, 2012 at 2:28 PM, Gary Kopp <[email protected]> wrote:
Thanks for confirming one of my suspicions, Sergiu. I've used the eclipse goal on other Maven-based projects where I approached things in basically the way you describe. But since there is no mention of that approach in the XWiki docs I was hesitant to assume it would work with the XWiki projects.
Can I run the Maven eclipse goal at the root of each project, like xwiki-commons, and it will walk down through all the projects in the tree?
--Gary
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sergiu Dumitriu Sent: Thursday, July 26, 2012 5:19 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons
On 07/26/2012 07:08 AM, Gary Kopp wrote:
Thomas,
On a minor note, I guess I could "solve" the aspect plugin problem by falling back to Indigo. And perhaps solve the other two problems by not importing the two projects that are involved -- xwiki-commons-component-legacy-default and xwiki-commons-tool-license-resources, although this might result in a non-buildable project tree in Eclipse anyway.
On a more significant note, what I intended to do may be infeasible. And possibly never attempted. My goal is to study virtually every part of the code base. With Eclipse I could easily follow class and method references in as much depth as I wanted. And I could theoretically use container-based debugging to trace execution flow through the entire application. But all of that requires that I have the entire code base in one Eclipse workspace, and that's what I was starting out to build. Would that be hopeless/fruitless? I do have alternatives to Eclipse for at least part of my goal, but not for real-time debugging.
What works for me is to skip m2eclipse completely. I use Eclipse for browsing the code, and command line tools (git, mvn) for the rest.
To prepare the eclipse projects, just use this line:
mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true -Pci,integration-tests,legacy,hsqldb,jetty
Then you can File->Import->Existing projects into workspace to get the projects built by maven into Eclipse. The problem is that whenever modules change, you'll have to regenerate/reimport the modules.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Thomas Mortagne Sent: Thursday, July 26, 2012 3:25 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons
On Thu, Jul 26, 2012 at 12:23 PM, Thomas Mortagne <[email protected]> wrote:
On Thu, Jul 26, 2012 at 4:26 AM, Gary Kopp <[email protected]> wrote:
Hello devs,
I just finished porting my XWiki development environment from Windows 7 to Ubuntu 12.04. I am now able to build all projects from the command line without errors. I'm working with the master branch from Git. I have Eclipse Juno installed with plugins that include m2eclipse (the version from the Eclipse update site) and AJDT. I am now trying to import the entire xwiki-commons Maven project into Eclipse. Just as happened under Windows (which I never asked about, since I was still trying to get command line builds to work), there are three Maven goals (plugins) in the xwiki-commons projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin, maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me some hints on how to resolve these mapping problems? Googling for answers about this hasn't yielded anything that I can understand :-)
I usually only open what I'm working on in Eclipse because otherwise with commons/rendering/platform it's a lot of projects and it's slowing down everything for things you probably don't care.
As for the missing mapping between Maven plugins and m2e handlers: * aspectJ-maven-plugin: could not find any either, there used to be one but it does not work anymore on 4.x. There is no official version of AJDT for 4.x so that's probably why it's not yet fixed but it
Actually there is one now since 4.2 (there was not not very long ago) so I guess (hope) the handler is probably going to be fixed in not too long.
should be quickly fixed as soon as there is an official AJDT for 4.x. In that case it's not very hard to setup AJDT yourself properly for the project, basically it's just about enabling it for the project and adding the right folder in the list of source folders if I remember well. But aspectj is used only in some legacy projects to produce retro-compatibility APIs so you are probably not going to need it very often. * maven-antrun-plugin: used for a hack in one of the legacy projects so for now it should not be a big deal for you * maven-remote-resources-plugin: not sure why you have issue with this one, m2e ignore it by default and just indicate it in a warning
-- Sergiu Dumitriu http://purl.org/net/sergiu/
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
-- Thomas Mortagne
On Thu, Jul 26, 2012 at 2:08 PM, Gary Kopp <[email protected]> wrote:
Thomas,
On a minor note, I guess I could "solve" the aspect plugin problem by falling back to Indigo. And perhaps solve the other two problems by not importing the two projects that are involved -- xwiki-commons-component-legacy-default and xwiki-commons-tool-license-resources, although this might result in a non-buildable project tree in Eclipse anyway.
On a more significant note, what I intended to do may be infeasible. And possibly never attempted. My goal is to study virtually every part of the code base. With Eclipse I could easily follow class and method references in as much depth as I wanted. And I could theoretically use container-based debugging to trace execution flow through the entire application. But all of that requires that I have the entire code base in one Eclipse workspace, and that's what I was starting out to build. Would that be hopeless/fruitless? I do have alternatives to Eclipse for at least part of my goal, but not for real-time debugging.
You should not really expect to completely replace maven with m2e from my point of view, this is just useless. If you don't import some project m2e will trigger it from the maven repository as dependency which is why importing only what you are working on is useful, it's not everything or nothing. m2e give dynamic dependencies resolution, better integration with various Eclipse plugins and be able to run and debug stuff which is already great, if you need to actually build some jar you will never find easier than actually execute "mvn install" in a shell.
--Gary
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Thomas Mortagne Sent: Thursday, July 26, 2012 3:25 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons
On Thu, Jul 26, 2012 at 12:23 PM, Thomas Mortagne <[email protected]> wrote:
On Thu, Jul 26, 2012 at 4:26 AM, Gary Kopp <[email protected]> wrote:
Hello devs,
I just finished porting my XWiki development environment from Windows 7 to Ubuntu 12.04. I am now able to build all projects from the command line without errors. I'm working with the master branch from Git. I have Eclipse Juno installed with plugins that include m2eclipse (the version from the Eclipse update site) and AJDT. I am now trying to import the entire xwiki-commons Maven project into Eclipse. Just as happened under Windows (which I never asked about, since I was still trying to get command line builds to work), there are three Maven goals (plugins) in the xwiki-commons projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin, maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me some hints on how to resolve these mapping problems? Googling for answers about this hasn't yielded anything that I can understand :-)
I usually only open what I'm working on in Eclipse because otherwise with commons/rendering/platform it's a lot of projects and it's slowing down everything for things you probably don't care.
As for the missing mapping between Maven plugins and m2e handlers: * aspectJ-maven-plugin: could not find any either, there used to be one but it does not work anymore on 4.x. There is no official version of AJDT for 4.x so that's probably why it's not yet fixed but it
Actually there is one now since 4.2 (there was not not very long ago) so I guess (hope) the handler is probably going to be fixed in not too long.
should be quickly fixed as soon as there is an official AJDT for 4.x. In that case it's not very hard to setup AJDT yourself properly for the project, basically it's just about enabling it for the project and adding the right folder in the list of source folders if I remember well. But aspectj is used only in some legacy projects to produce retro-compatibility APIs so you are probably not going to need it very often. * maven-antrun-plugin: used for a hack in one of the legacy projects so for now it should not be a big deal for you * maven-remote-resources-plugin: not sure why you have issue with this one, m2e ignore it by default and just indicate it in a warning
--Gary
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
I personally use the great https://github.com/xwiki/xwiki-debug-eclipse done by Thomas. I import this project and (modulo some initial glitches) I am able to start a working instance of XWiki from within the Workbench. Then I import the modules I want to work on from xwiki-platform. M2Eclipse takes care of using the modules open in the workbench in the XWiki web application. So I don't need to do any jar copying or whatever. Sometimes hot code replacement is also applicable so you don't even have to restart the instance when you modify stuff. Debugging works out-of-the-box. I think that this is a very nice environment where you can manage building/deploying/running XWiki from a single environment, with M2Eclipse and Eclipse WTP taking care automatically of many details (almost everything actually). My 2 cents. -Fabio On Thu, Jul 26, 2012 at 3:26 AM, Gary Kopp <[email protected]> wrote:
Hello devs,
I just finished porting my XWiki development environment from Windows 7 to Ubuntu 12.04. I am now able to build all projects from the command line without errors. I'm working with the master branch from Git. I have Eclipse Juno installed with plugins that include m2eclipse (the version from the Eclipse update site) and AJDT. I am now trying to import the entire xwiki-commons Maven project into Eclipse. Just as happened under Windows (which I never asked about, since I was still trying to get command line builds to work), there are three Maven goals (plugins) in the xwiki-commons projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin, maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me some hints on how to resolve these mapping problems? Googling for answers about this hasn't yielded anything that I can understand :-)
--Gary
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Fabio, Thanks for adding your two cents. I had seen Thomas' doc on debugging under Eclipse and it attracted me. Now I'm thinking I need to combine your/Thomas approach, using m2eclipse, with Sergiu's approach of using Maven's eclipse:eclipse without m2eclipse. Then I can go in any direction -- browse the entire codebase following all references _or_ debug one or more specific modules. All I really have to do to make this practical is maintain two separate clones of the Git code base (since they will have different Eclipse project metadata created within them). --Gary -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Fabio Mancinelli Sent: Thursday, July 26, 2012 6:03 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons I personally use the great https://github.com/xwiki/xwiki-debug-eclipse done by Thomas. I import this project and (modulo some initial glitches) I am able to start a working instance of XWiki from within the Workbench. Then I import the modules I want to work on from xwiki-platform. M2Eclipse takes care of using the modules open in the workbench in the XWiki web application. So I don't need to do any jar copying or whatever. Sometimes hot code replacement is also applicable so you don't even have to restart the instance when you modify stuff. Debugging works out-of-the-box. I think that this is a very nice environment where you can manage building/deploying/running XWiki from a single environment, with M2Eclipse and Eclipse WTP taking care automatically of many details (almost everything actually). My 2 cents. -Fabio On Thu, Jul 26, 2012 at 3:26 AM, Gary Kopp <[email protected]> wrote:
Hello devs,
I just finished porting my XWiki development environment from Windows 7 to Ubuntu 12.04. I am now able to build all projects from the command line without errors. I'm working with the master branch from Git. I have Eclipse Juno installed with plugins that include m2eclipse (the version from the Eclipse update site) and AJDT. I am now trying to import the entire xwiki-commons Maven project into Eclipse. Just as happened under Windows (which I never asked about, since I was still trying to get command line builds to work), there are three Maven goals (plugins) in the xwiki-commons projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin, maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me some hints on how to resolve these mapping problems? Googling for answers about this hasn't yielded anything that I can understand :-)
--Gary
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hmmm. Frankly I see the two approaches as mutually exclusive. If you import projects using m2e and it works, it doesn't make sense to use the other approach because you will already have all that is provided by the other one (and even more) You are able to browse the the entire code base with both of the approaches (just import anything you need, and if you don't use snapshots m2e will download source code artifacts automatically and show you the code for the dependencies if you don't have it available) I still think that the M2E + wiki-debug-eclipse is a superior approach (when it works fine :)) -Fabio P.S.: Re another mail you sent, I usually deploy on tomcat with xwiki-debug-eclipse (and lately also on jetty). Works out-of-the-box, just define a profile and go. On Thu, Jul 26, 2012 at 2:21 PM, Gary Kopp <[email protected]> wrote:
Fabio,
Thanks for adding your two cents. I had seen Thomas' doc on debugging under Eclipse and it attracted me. Now I'm thinking I need to combine your/Thomas approach, using m2eclipse, with Sergiu's approach of using Maven's eclipse:eclipse without m2eclipse. Then I can go in any direction -- browse the entire codebase following all references _or_ debug one or more specific modules. All I really have to do to make this practical is maintain two separate clones of the Git code base (since they will have different Eclipse project metadata created within them).
--Gary
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Fabio Mancinelli Sent: Thursday, July 26, 2012 6:03 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons
I personally use the great https://github.com/xwiki/xwiki-debug-eclipse done by Thomas.
I import this project and (modulo some initial glitches) I am able to start a working instance of XWiki from within the Workbench.
Then I import the modules I want to work on from xwiki-platform. M2Eclipse takes care of using the modules open in the workbench in the XWiki web application. So I don't need to do any jar copying or whatever. Sometimes hot code replacement is also applicable so you don't even have to restart the instance when you modify stuff.
Debugging works out-of-the-box.
I think that this is a very nice environment where you can manage building/deploying/running XWiki from a single environment, with M2Eclipse and Eclipse WTP taking care automatically of many details (almost everything actually).
My 2 cents.
-Fabio
On Thu, Jul 26, 2012 at 3:26 AM, Gary Kopp <[email protected]> wrote:
Hello devs,
I just finished porting my XWiki development environment from Windows 7 to Ubuntu 12.04. I am now able to build all projects from the command line without errors. I'm working with the master branch from Git. I have Eclipse Juno installed with plugins that include m2eclipse (the version from the Eclipse update site) and AJDT. I am now trying to import the entire xwiki-commons Maven project into Eclipse. Just as happened under Windows (which I never asked about, since I was still trying to get command line builds to work), there are three Maven goals (plugins) in the xwiki-commons projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin, maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me some hints on how to resolve these mapping problems? Googling for answers about this hasn't yielded anything that I can understand :-)
--Gary
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Fabio, The potential problem with relying on m2eclipse exclusively is that I have found that some XWiki Maven projects won't import correctly. That's what started this thread. But, those errors would seem to be the exception rather than the rule and may be irrelevant for my purposes. So, I'll go with the m2e approach for now.
P.S.: Re another mail you sent, I usually deploy on tomcat with xwiki-debug-eclipse (and lately also on jetty). Works out-of-the-box, just define a profile and go.
Are you talking about a new Maven profile? Thanks for your help. --Gary -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Fabio Mancinelli Sent: Thursday, July 26, 2012 7:32 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons Hmmm. Frankly I see the two approaches as mutually exclusive. If you import projects using m2e and it works, it doesn't make sense to use the other approach because you will already have all that is provided by the other one (and even more) You are able to browse the the entire code base with both of the approaches (just import anything you need, and if you don't use snapshots m2e will download source code artifacts automatically and show you the code for the dependencies if you don't have it available) I still think that the M2E + wiki-debug-eclipse is a superior approach (when it works fine :)) -Fabio P.S.: Re another mail you sent, I usually deploy on tomcat with xwiki-debug-eclipse (and lately also on jetty). Works out-of-the-box, just define a profile and go. On Thu, Jul 26, 2012 at 2:21 PM, Gary Kopp <[email protected]> wrote:
Fabio,
Thanks for adding your two cents. I had seen Thomas' doc on debugging under Eclipse and it attracted me. Now I'm thinking I need to combine your/Thomas approach, using m2eclipse, with Sergiu's approach of using Maven's eclipse:eclipse without m2eclipse. Then I can go in any direction -- browse the entire codebase following all references _or_ debug one or more specific modules. All I really have to do to make this practical is maintain two separate clones of the Git code base (since they will have different Eclipse project metadata created within them).
--Gary
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Fabio Mancinelli Sent: Thursday, July 26, 2012 6:03 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons
I personally use the great https://github.com/xwiki/xwiki-debug-eclipse done by Thomas.
I import this project and (modulo some initial glitches) I am able to start a working instance of XWiki from within the Workbench.
Then I import the modules I want to work on from xwiki-platform. M2Eclipse takes care of using the modules open in the workbench in the XWiki web application. So I don't need to do any jar copying or whatever. Sometimes hot code replacement is also applicable so you don't even have to restart the instance when you modify stuff.
Debugging works out-of-the-box.
I think that this is a very nice environment where you can manage building/deploying/running XWiki from a single environment, with M2Eclipse and Eclipse WTP taking care automatically of many details (almost everything actually).
My 2 cents.
-Fabio
On Thu, Jul 26, 2012 at 3:26 AM, Gary Kopp <[email protected]> wrote:
Hello devs,
I just finished porting my XWiki development environment from Windows 7 to Ubuntu 12.04. I am now able to build all projects from the command line without errors. I'm working with the master branch from Git. I have Eclipse Juno installed with plugins that include m2eclipse (the version from the Eclipse update site) and AJDT. I am now trying to import the entire xwiki-commons Maven project into Eclipse. Just as happened under Windows (which I never asked about, since I was still trying to get command line builds to work), there are three Maven goals (plugins) in the xwiki-commons projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin, maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me some hints on how to resolve these mapping problems? Googling for answers about this hasn't yielded anything that I can understand :-)
--Gary
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Thu, Jul 26, 2012 at 3:49 PM, Gary Kopp <[email protected]> wrote:
Fabio,
The potential problem with relying on m2eclipse exclusively is that I have found that some XWiki Maven projects won't import correctly. That's what started this thread. But, those errors would seem to be the exception rather than the rule and may be irrelevant for my purposes. So, I'll go with the m2e approach for now.
Yep I know, that's why I said "if it works" in my previous message :)
P.S.: Re another mail you sent, I usually deploy on tomcat with xwiki-debug-eclipse (and lately also on jetty). Works out-of-the-box, just define a profile and go.
Are you talking about a new Maven profile?
No, WTP profile (File -> New -> Other -> Server) -Fabio
Thanks for your help.
--Gary
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Fabio Mancinelli Sent: Thursday, July 26, 2012 7:32 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons
Hmmm. Frankly I see the two approaches as mutually exclusive. If you import projects using m2e and it works, it doesn't make sense to use the other approach because you will already have all that is provided by the other one (and even more)
You are able to browse the the entire code base with both of the approaches (just import anything you need, and if you don't use snapshots m2e will download source code artifacts automatically and show you the code for the dependencies if you don't have it available)
I still think that the M2E + wiki-debug-eclipse is a superior approach (when it works fine :))
-Fabio
P.S.: Re another mail you sent, I usually deploy on tomcat with xwiki-debug-eclipse (and lately also on jetty). Works out-of-the-box, just define a profile and go.
On Thu, Jul 26, 2012 at 2:21 PM, Gary Kopp <[email protected]> wrote:
Fabio,
Thanks for adding your two cents. I had seen Thomas' doc on debugging under Eclipse and it attracted me. Now I'm thinking I need to combine your/Thomas approach, using m2eclipse, with Sergiu's approach of using Maven's eclipse:eclipse without m2eclipse. Then I can go in any direction -- browse the entire codebase following all references _or_ debug one or more specific modules. All I really have to do to make this practical is maintain two separate clones of the Git code base (since they will have different Eclipse project metadata created within them).
--Gary
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Fabio Mancinelli Sent: Thursday, July 26, 2012 6:03 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons
I personally use the great https://github.com/xwiki/xwiki-debug-eclipse done by Thomas.
I import this project and (modulo some initial glitches) I am able to start a working instance of XWiki from within the Workbench.
Then I import the modules I want to work on from xwiki-platform. M2Eclipse takes care of using the modules open in the workbench in the XWiki web application. So I don't need to do any jar copying or whatever. Sometimes hot code replacement is also applicable so you don't even have to restart the instance when you modify stuff.
Debugging works out-of-the-box.
I think that this is a very nice environment where you can manage building/deploying/running XWiki from a single environment, with M2Eclipse and Eclipse WTP taking care automatically of many details (almost everything actually).
My 2 cents.
-Fabio
On Thu, Jul 26, 2012 at 3:26 AM, Gary Kopp <[email protected]> wrote:
Hello devs,
I just finished porting my XWiki development environment from Windows 7 to Ubuntu 12.04. I am now able to build all projects from the command line without errors. I'm working with the master branch from Git. I have Eclipse Juno installed with plugins that include m2eclipse (the version from the Eclipse update site) and AJDT. I am now trying to import the entire xwiki-commons Maven project into Eclipse. Just as happened under Windows (which I never asked about, since I was still trying to get command line builds to work), there are three Maven goals (plugins) in the xwiki-commons projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin, maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me some hints on how to resolve these mapping problems? Googling for answers about this hasn't yielded anything that I can understand :-)
--Gary
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 07/26/2012 08:21 AM, Gary Kopp wrote:
Fabio,
Thanks for adding your two cents. I had seen Thomas' doc on debugging under Eclipse and it attracted me. Now I'm thinking I need to combine your/Thomas approach, using m2eclipse, with Sergiu's approach of using Maven's eclipse:eclipse without m2eclipse. Then I can go in any direction -- browse the entire codebase following all references _or_ debug one or more specific modules. All I really have to do to make this practical is maintain two separate clones of the Git code base (since they will have different Eclipse project metadata created within them).
You should never have to maintain two different clones. -- Sergiu Dumitriu http://purl.org/net/sergiu/
Sergiu, If you think I should never need to maintain two Git clones I might be missing something obvious. Let's say I want to use the m2e approach for selective debugging, and the import existing projects approach (non-m2e) for global code browsing. If I run mvn eclipse:eclipse it will create Eclipse metadata files in the Git projects, and this metadata is specific to the previously done Maven command line build. If I then use m2e to attempt to import Maven projects from the same clone the import will try to create its own Eclipse project metadata in the Git clone, which I would think is incompatible with the project metadata from mvn eclipse:eclipse. Or, I'm hopelessly confused and a lost cause :-) --Gary -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sergiu Dumitriu Sent: Thursday, July 26, 2012 7:53 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons On 07/26/2012 08:21 AM, Gary Kopp wrote:
Fabio,
Thanks for adding your two cents. I had seen Thomas' doc on debugging under Eclipse and it attracted me. Now I'm thinking I need to combine your/Thomas approach, using m2eclipse, with Sergiu's approach of using Maven's eclipse:eclipse without m2eclipse. Then I can go in any direction -- browse the entire codebase following all references _or_ debug one or more specific modules. All I really have to do to make this practical is maintain two separate clones of the Git code base (since they will have different Eclipse project metadata created within them).
You should never have to maintain two different clones. -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (5)
-
Fabio Mancinelli -
Gary Kopp -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol