You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "David C. Hicks" <dh...@i-hicks.org> on 2008/09/19 23:17:40 UTC
Maven/Eclipse - Keeping them in sync?
I'm beginning a new, fairly large, project. Eclipse will be our
development platform, but I've already set up the starting point in
Maven. Simple enough. Now, my question is, how can I keep them in
sync, easily? I realize that it's best to re-run "mvn eclipse:eclipse"
after adding dependencies, but what about source folders? I need to add
new source folders, but Maven doesn't know anything about that, so the
next time I re-generate the .project/.classpath files, it'll revert back
to those folders not being "source" folders.
Any help how to make this behave?
Thanks,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Eclipse - Keeping them in sync?
Posted by "David C. Hicks" <dh...@i-hicks.org>.
Good points, Eugene. I'll take a closer look at what we're trying to
accomplish. Maybe it does make more sense to put integration tests in a
different module. This is a very new project, so we're still figuring
out a lot of the details. It's just so easy to add source folders under
Eclipse, that it's easy to think about it that way.
Thanks for the input.
Dave
Eugene Kuleshov wrote:
> David C. Hicks wrote:
>
>> Thanks again. I'll check out the build-helper plugin.
>>
>> As for larger projects, that's exactly how I've done them in the past.
>> It requires a little massaging of the pom.xml files, but I haven't found
>> a cleaner way to handle it. Maybe one day between Eclipse and Maven
>> this won't be such a mind twister.
>>
>> The primary reason I'm adding extra source folders is for test code. I
>> really don't want to mix functional tests with my unit tests. It made
>> sense, to me, to put them in a different tree, but it didn't seem like a
>> good fit for a sub-module.
>>
>> Thanks for all the suggestions!
>>
>>
>
> The m2eclipse uses pom.xml as a source of information for configuring
> projects in Eclipse. The reason for that is to keep build in Eclipse and in
> the command line in sync. The command line build won't run for your
> additional test folders if they are not in the pom.xml. After all it might
> be a good idea to keep integration tests in a separate module and that would
> closely follow standard Maven conventions.
>
> On the other hand, if you have command line build that works, but there is
> some issues in the IDE for the very same build, please submit a bug report
> for m2eclipse and provide test project that would allow us to reproduce it.
>
> Thanks
>
> Eugene
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Eclipse - Keeping them in sync?
Posted by Eugene Kuleshov <eu...@md.pp.ru>.
David C. Hicks wrote:
>
> Thanks again. I'll check out the build-helper plugin.
>
> As for larger projects, that's exactly how I've done them in the past.
> It requires a little massaging of the pom.xml files, but I haven't found
> a cleaner way to handle it. Maybe one day between Eclipse and Maven
> this won't be such a mind twister.
>
> The primary reason I'm adding extra source folders is for test code. I
> really don't want to mix functional tests with my unit tests. It made
> sense, to me, to put them in a different tree, but it didn't seem like a
> good fit for a sub-module.
>
> Thanks for all the suggestions!
>
The m2eclipse uses pom.xml as a source of information for configuring
projects in Eclipse. The reason for that is to keep build in Eclipse and in
the command line in sync. The command line build won't run for your
additional test folders if they are not in the pom.xml. After all it might
be a good idea to keep integration tests in a separate module and that would
closely follow standard Maven conventions.
On the other hand, if you have command line build that works, but there is
some issues in the IDE for the very same build, please submit a bug report
for m2eclipse and provide test project that would allow us to reproduce it.
Thanks
Eugene
--
View this message in context: http://www.nabble.com/Maven-Eclipse---Keeping-them-in-sync--tp19579618p19588102.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Eclipse - Keeping them in sync?
Posted by "David C. Hicks" <dh...@i-hicks.org>.
No sweat. The build-helper plugin solved my problem for me.
I appreciate the input!
Thor wrote:
> Ok. Got it. the last mail was out of context...
>
> My regards...
>
>
> On Mon, Sep 22, 2008 at 9:05 AM, David C. Hicks <dh...@i-hicks.org> wrote:
>
>
>> Yes. I don't want functional test code mixed with unit test code.
>>
>>
>> Thor wrote:
>>
>>
>>> Ok David.
>>> Is there any reason why you are not using the maven standard layout for
>>> your
>>> project?
>>>
>>> You just put all of your test code into the /src/test/java/ and maven adds
>>> it to the eclipse path...
>>>
>>>
>>> On Sat, Sep 20, 2008 at 8:48 AM, David C. Hicks <dh...@i-hicks.org>
>>> wrote:
>>>
>>>
>>>
>>>
>>>> Thanks again. I'll check out the build-helper plugin.
>>>>
>>>> As for larger projects, that's exactly how I've done them in the past.
>>>> It
>>>> requires a little massaging of the pom.xml files, but I haven't found a
>>>> cleaner way to handle it. Maybe one day between Eclipse and Maven this
>>>> won't be such a mind twister.
>>>>
>>>> The primary reason I'm adding extra source folders is for test code. I
>>>> really don't want to mix functional tests with my unit tests. It made
>>>> sense, to me, to put them in a different tree, but it didn't seem like a
>>>> good fit for a sub-module.
>>>>
>>>> Thanks for all the suggestions!
>>>> Dave
>>>>
>>>>
>>>> Stefan Hübner wrote:
>>>>
>>>>
>>>>
>>>>
>>>>> David,
>>>>>
>>>>> 2008/9/19 David C. Hicks <dh...@i-hicks.org>:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> I'm beginning a new, fairly large, project. Eclipse will be our
>>>>>> development
>>>>>> platform, but I've already set up the starting point in Maven. Simple
>>>>>> enough. Now, my question is, how can I keep them in sync, easily? I
>>>>>> realize that it's best to re-run "mvn eclipse:eclipse" after adding
>>>>>> dependencies, but what about source folders? I need to add new source
>>>>>> folders, but Maven doesn't know anything about that, so the next time I
>>>>>> re-generate the .project/.classpath files, it'll revert back to those
>>>>>> folders not being "source" folders.
>>>>>>
>>>>>> Any help how to make this behave?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> You need to add additional source folders by using the
>>>>> build-helper-maven-plugin
>>>>> (http://mojo.codehaus.org/build-helper-maven-plugin/). Then the
>>>>> maven-eclipse-plugin happily add all your source folders to eclipse's
>>>>> project configuration.
>>>>>
>>>>> Also another hint on handling larger project setup with many
>>>>> submodules and maybe independent project side by side. In my last
>>>>> project to keep all my projects and submodules (40+) synced with
>>>>> eclipse I put all projects and multiprojects in the same subversion
>>>>> trunk and thus the same working folder in parallel subfolders. in the
>>>>> working folder's root I established a "bootstapper"-pom which included
>>>>> all projects as submodules. the project's parent pom resided in a
>>>>> parallel subfolder next to the projects as well. Also this parent-pom
>>>>> was included as a submodule by the bootstrapper-pom. With this setup
>>>>> we were able to invoke any maven commands on all projects at once.
>>>>>
>>>>> -Stefan
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Eclipse - Keeping them in sync?
Posted by Thor <me...@gmail.com>.
Ok. Got it. the last mail was out of context...
My regards...
On Mon, Sep 22, 2008 at 9:05 AM, David C. Hicks <dh...@i-hicks.org> wrote:
> Yes. I don't want functional test code mixed with unit test code.
>
>
> Thor wrote:
>
>> Ok David.
>> Is there any reason why you are not using the maven standard layout for
>> your
>> project?
>>
>> You just put all of your test code into the /src/test/java/ and maven adds
>> it to the eclipse path...
>>
>>
>> On Sat, Sep 20, 2008 at 8:48 AM, David C. Hicks <dh...@i-hicks.org>
>> wrote:
>>
>>
>>
>>> Thanks again. I'll check out the build-helper plugin.
>>>
>>> As for larger projects, that's exactly how I've done them in the past.
>>> It
>>> requires a little massaging of the pom.xml files, but I haven't found a
>>> cleaner way to handle it. Maybe one day between Eclipse and Maven this
>>> won't be such a mind twister.
>>>
>>> The primary reason I'm adding extra source folders is for test code. I
>>> really don't want to mix functional tests with my unit tests. It made
>>> sense, to me, to put them in a different tree, but it didn't seem like a
>>> good fit for a sub-module.
>>>
>>> Thanks for all the suggestions!
>>> Dave
>>>
>>>
>>> Stefan Hübner wrote:
>>>
>>>
>>>
>>>> David,
>>>>
>>>> 2008/9/19 David C. Hicks <dh...@i-hicks.org>:
>>>>
>>>>
>>>>
>>>>
>>>>> I'm beginning a new, fairly large, project. Eclipse will be our
>>>>> development
>>>>> platform, but I've already set up the starting point in Maven. Simple
>>>>> enough. Now, my question is, how can I keep them in sync, easily? I
>>>>> realize that it's best to re-run "mvn eclipse:eclipse" after adding
>>>>> dependencies, but what about source folders? I need to add new source
>>>>> folders, but Maven doesn't know anything about that, so the next time I
>>>>> re-generate the .project/.classpath files, it'll revert back to those
>>>>> folders not being "source" folders.
>>>>>
>>>>> Any help how to make this behave?
>>>>>
>>>>>
>>>>>
>>>>>
>>>> You need to add additional source folders by using the
>>>> build-helper-maven-plugin
>>>> (http://mojo.codehaus.org/build-helper-maven-plugin/). Then the
>>>> maven-eclipse-plugin happily add all your source folders to eclipse's
>>>> project configuration.
>>>>
>>>> Also another hint on handling larger project setup with many
>>>> submodules and maybe independent project side by side. In my last
>>>> project to keep all my projects and submodules (40+) synced with
>>>> eclipse I put all projects and multiprojects in the same subversion
>>>> trunk and thus the same working folder in parallel subfolders. in the
>>>> working folder's root I established a "bootstapper"-pom which included
>>>> all projects as submodules. the project's parent pom resided in a
>>>> parallel subfolder next to the projects as well. Also this parent-pom
>>>> was included as a submodule by the bootstrapper-pom. With this setup
>>>> we were able to invoke any maven commands on all projects at once.
>>>>
>>>> -Stefan
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
(o_ \*
/ / ) |
/ \ /
| O |
v v ....
Re: Maven/Eclipse - Keeping them in sync?
Posted by "David C. Hicks" <dh...@i-hicks.org>.
Yes. I don't want functional test code mixed with unit test code.
Thor wrote:
> Ok David.
> Is there any reason why you are not using the maven standard layout for your
> project?
>
> You just put all of your test code into the /src/test/java/ and maven adds
> it to the eclipse path...
>
>
> On Sat, Sep 20, 2008 at 8:48 AM, David C. Hicks <dh...@i-hicks.org> wrote:
>
>
>> Thanks again. I'll check out the build-helper plugin.
>>
>> As for larger projects, that's exactly how I've done them in the past. It
>> requires a little massaging of the pom.xml files, but I haven't found a
>> cleaner way to handle it. Maybe one day between Eclipse and Maven this
>> won't be such a mind twister.
>>
>> The primary reason I'm adding extra source folders is for test code. I
>> really don't want to mix functional tests with my unit tests. It made
>> sense, to me, to put them in a different tree, but it didn't seem like a
>> good fit for a sub-module.
>>
>> Thanks for all the suggestions!
>> Dave
>>
>>
>> Stefan Hübner wrote:
>>
>>
>>> David,
>>>
>>> 2008/9/19 David C. Hicks <dh...@i-hicks.org>:
>>>
>>>
>>>
>>>> I'm beginning a new, fairly large, project. Eclipse will be our
>>>> development
>>>> platform, but I've already set up the starting point in Maven. Simple
>>>> enough. Now, my question is, how can I keep them in sync, easily? I
>>>> realize that it's best to re-run "mvn eclipse:eclipse" after adding
>>>> dependencies, but what about source folders? I need to add new source
>>>> folders, but Maven doesn't know anything about that, so the next time I
>>>> re-generate the .project/.classpath files, it'll revert back to those
>>>> folders not being "source" folders.
>>>>
>>>> Any help how to make this behave?
>>>>
>>>>
>>>>
>>> You need to add additional source folders by using the
>>> build-helper-maven-plugin
>>> (http://mojo.codehaus.org/build-helper-maven-plugin/). Then the
>>> maven-eclipse-plugin happily add all your source folders to eclipse's
>>> project configuration.
>>>
>>> Also another hint on handling larger project setup with many
>>> submodules and maybe independent project side by side. In my last
>>> project to keep all my projects and submodules (40+) synced with
>>> eclipse I put all projects and multiprojects in the same subversion
>>> trunk and thus the same working folder in parallel subfolders. in the
>>> working folder's root I established a "bootstapper"-pom which included
>>> all projects as submodules. the project's parent pom resided in a
>>> parallel subfolder next to the projects as well. Also this parent-pom
>>> was included as a submodule by the bootstrapper-pom. With this setup
>>> we were able to invoke any maven commands on all projects at once.
>>>
>>> -Stefan
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Eclipse - Keeping them in sync?
Posted by Thor <me...@gmail.com>.
Ok David.
Is there any reason why you are not using the maven standard layout for your
project?
You just put all of your test code into the /src/test/java/ and maven adds
it to the eclipse path...
On Sat, Sep 20, 2008 at 8:48 AM, David C. Hicks <dh...@i-hicks.org> wrote:
> Thanks again. I'll check out the build-helper plugin.
>
> As for larger projects, that's exactly how I've done them in the past. It
> requires a little massaging of the pom.xml files, but I haven't found a
> cleaner way to handle it. Maybe one day between Eclipse and Maven this
> won't be such a mind twister.
>
> The primary reason I'm adding extra source folders is for test code. I
> really don't want to mix functional tests with my unit tests. It made
> sense, to me, to put them in a different tree, but it didn't seem like a
> good fit for a sub-module.
>
> Thanks for all the suggestions!
> Dave
>
>
> Stefan Hübner wrote:
>
>> David,
>>
>> 2008/9/19 David C. Hicks <dh...@i-hicks.org>:
>>
>>
>>> I'm beginning a new, fairly large, project. Eclipse will be our
>>> development
>>> platform, but I've already set up the starting point in Maven. Simple
>>> enough. Now, my question is, how can I keep them in sync, easily? I
>>> realize that it's best to re-run "mvn eclipse:eclipse" after adding
>>> dependencies, but what about source folders? I need to add new source
>>> folders, but Maven doesn't know anything about that, so the next time I
>>> re-generate the .project/.classpath files, it'll revert back to those
>>> folders not being "source" folders.
>>>
>>> Any help how to make this behave?
>>>
>>>
>>
>> You need to add additional source folders by using the
>> build-helper-maven-plugin
>> (http://mojo.codehaus.org/build-helper-maven-plugin/). Then the
>> maven-eclipse-plugin happily add all your source folders to eclipse's
>> project configuration.
>>
>> Also another hint on handling larger project setup with many
>> submodules and maybe independent project side by side. In my last
>> project to keep all my projects and submodules (40+) synced with
>> eclipse I put all projects and multiprojects in the same subversion
>> trunk and thus the same working folder in parallel subfolders. in the
>> working folder's root I established a "bootstapper"-pom which included
>> all projects as submodules. the project's parent pom resided in a
>> parallel subfolder next to the projects as well. Also this parent-pom
>> was included as a submodule by the bootstrapper-pom. With this setup
>> we were able to invoke any maven commands on all projects at once.
>>
>> -Stefan
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
(o_ \*
/ / ) |
/ \ /
| O |
v v ....
Re: Maven/Eclipse - Keeping them in sync?
Posted by "David C. Hicks" <dh...@i-hicks.org>.
Thanks again. I'll check out the build-helper plugin.
As for larger projects, that's exactly how I've done them in the past.
It requires a little massaging of the pom.xml files, but I haven't found
a cleaner way to handle it. Maybe one day between Eclipse and Maven
this won't be such a mind twister.
The primary reason I'm adding extra source folders is for test code. I
really don't want to mix functional tests with my unit tests. It made
sense, to me, to put them in a different tree, but it didn't seem like a
good fit for a sub-module.
Thanks for all the suggestions!
Dave
Stefan Hübner wrote:
> David,
>
> 2008/9/19 David C. Hicks <dh...@i-hicks.org>:
>
>> I'm beginning a new, fairly large, project. Eclipse will be our development
>> platform, but I've already set up the starting point in Maven. Simple
>> enough. Now, my question is, how can I keep them in sync, easily? I
>> realize that it's best to re-run "mvn eclipse:eclipse" after adding
>> dependencies, but what about source folders? I need to add new source
>> folders, but Maven doesn't know anything about that, so the next time I
>> re-generate the .project/.classpath files, it'll revert back to those
>> folders not being "source" folders.
>>
>> Any help how to make this behave?
>>
>
> You need to add additional source folders by using the
> build-helper-maven-plugin
> (http://mojo.codehaus.org/build-helper-maven-plugin/). Then the
> maven-eclipse-plugin happily add all your source folders to eclipse's
> project configuration.
>
> Also another hint on handling larger project setup with many
> submodules and maybe independent project side by side. In my last
> project to keep all my projects and submodules (40+) synced with
> eclipse I put all projects and multiprojects in the same subversion
> trunk and thus the same working folder in parallel subfolders. in the
> working folder's root I established a "bootstapper"-pom which included
> all projects as submodules. the project's parent pom resided in a
> parallel subfolder next to the projects as well. Also this parent-pom
> was included as a submodule by the bootstrapper-pom. With this setup
> we were able to invoke any maven commands on all projects at once.
>
> -Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Eclipse - Keeping them in sync?
Posted by Stefan Hübner <st...@googlemail.com>.
David,
2008/9/19 David C. Hicks <dh...@i-hicks.org>:
> I'm beginning a new, fairly large, project. Eclipse will be our development
> platform, but I've already set up the starting point in Maven. Simple
> enough. Now, my question is, how can I keep them in sync, easily? I
> realize that it's best to re-run "mvn eclipse:eclipse" after adding
> dependencies, but what about source folders? I need to add new source
> folders, but Maven doesn't know anything about that, so the next time I
> re-generate the .project/.classpath files, it'll revert back to those
> folders not being "source" folders.
>
> Any help how to make this behave?
You need to add additional source folders by using the
build-helper-maven-plugin
(http://mojo.codehaus.org/build-helper-maven-plugin/). Then the
maven-eclipse-plugin happily add all your source folders to eclipse's
project configuration.
Also another hint on handling larger project setup with many
submodules and maybe independent project side by side. In my last
project to keep all my projects and submodules (40+) synced with
eclipse I put all projects and multiprojects in the same subversion
trunk and thus the same working folder in parallel subfolders. in the
working folder's root I established a "bootstapper"-pom which included
all projects as submodules. the project's parent pom resided in a
parallel subfolder next to the projects as well. Also this parent-pom
was included as a submodule by the bootstrapper-pom. With this setup
we were able to invoke any maven commands on all projects at once.
-Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Eclipse - Keeping them in sync?
Posted by Eugene Kuleshov <eu...@md.pp.ru>.
megathor wrote:
>
> You also could give it a try to q4E: http://code.google.com/p/q4e/
> It has a lot of very nice features...
> M2Eclipse and q4E have both very nice features
>
Here is side by side comparison
http://docs.codehaus.org/display/MAVENUSER/Eclipse+Integration
megathor wrote:
>
> And both have their projects at Eclipse:
> http://www.eclipse.org/proposals/m2e/
> http://www.eclipse.org/proposals/iam/
>
> I wonder why the Eclipse Foundation guys didn't merge both projects...
>
Eclipse Foundation does not interfere with project development, it only
provides infrastructure, legal support and general coordination. Basically
it is up to project developers to decide to join forces, but there is a lot
of code in both m2eclipse and q4e projects and it is unclear how one would
merge those different codebases.
regards,
Eugene
--
View this message in context: http://www.nabble.com/Maven-Eclipse---Keeping-them-in-sync--tp19579618p19581094.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Eclipse - Keeping them in sync?
Posted by Thor <me...@gmail.com>.
You also could give it a try to q4E: http://code.google.com/p/q4e/
It has a lot of very nice features...
M2Eclipse and q4E have both very nice features...
And both have their projects at Eclipse:
http://www.eclipse.org/proposals/m2e/
http://www.eclipse.org/proposals/iam/
And they both have approved projects
http://www.eclipse.org/m2e/
http://www.eclipse.org/iam/
I wonder why the Eclipse Foundation guys didn't merge both projects...
On Fri, Sep 19, 2008 at 4:00 PM, David C. Hicks <dh...@i-hicks.org> wrote:
> Thanks for the tips, guys. I had forgotten about the m2eclipse plugin. It's
> been too long since I was in a real project. :-)
> I guess m2eclipse has come a little further since I last looked at it -
> probably 2 years?
> Thanks again,
> Dave
>
>
>
> Stevo Slavic' wrote:
>
>> Hello David,
>>
>> Just as Klaus said, use m2eclipse plugin. After installing it, I'd first
>> manually create a folder in eclipse workspace, named as your root maven
>> project artifactId, then copy root POM and rest of the project structure
>> you've created into that new folder. Finally, with m2eclipse plugin you
>> could just "File-->Import...-->General-->Maven Projects" and select/browse
>> to newly created folder, leaving m2eclipse do the rest.
>>
>> Regards,
>> Stevo.
>>
>> On Fri, Sep 19, 2008 at 11:24 PM, Klaus <kd...@googlemail.com> wrote:
>>
>>
>>
>>> Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin
>>> that
>>> updates the project settings according to the setting in the pom.xml. No
>>> (re)generate of eclipse-project files, no problem with new source
>>> folders..
>>>
>>> klaus
>>>
>>> On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks <dh...@i-hicks.org>
>>> wrote:
>>>
>>>
>>>
>>>> I'm beginning a new, fairly large, project. Eclipse will be our
>>>> development platform, but I've already set up the starting point in
>>>>
>>>>
>>> Maven.
>>>
>>>
>>>> Simple enough. Now, my question is, how can I keep them in sync,
>>>>
>>>>
>>> easily?
>>>
>>>
>>>> I realize that it's best to re-run "mvn eclipse:eclipse" after adding
>>>> dependencies, but what about source folders? I need to add new source
>>>> folders, but Maven doesn't know anything about that, so the next time I
>>>> re-generate the .project/.classpath files, it'll revert back to those
>>>> folders not being "source" folders.
>>>>
>>>> Any help how to make this behave?
>>>> Thanks,
>>>> Dave
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
(o_ \*
/ / ) |
/ \ /
| O |
v v ....
Re: Maven/Eclipse - Keeping them in sync?
Posted by "David C. Hicks" <dh...@i-hicks.org>.
Thanks for the tips, guys. I had forgotten about the m2eclipse plugin.
It's been too long since I was in a real project. :-)
I guess m2eclipse has come a little further since I last looked at it -
probably 2 years?
Thanks again,
Dave
Stevo Slavic' wrote:
> Hello David,
>
> Just as Klaus said, use m2eclipse plugin. After installing it, I'd first
> manually create a folder in eclipse workspace, named as your root maven
> project artifactId, then copy root POM and rest of the project structure
> you've created into that new folder. Finally, with m2eclipse plugin you
> could just "File-->Import...-->General-->Maven Projects" and select/browse
> to newly created folder, leaving m2eclipse do the rest.
>
> Regards,
> Stevo.
>
> On Fri, Sep 19, 2008 at 11:24 PM, Klaus <kd...@googlemail.com> wrote:
>
>
>> Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin that
>> updates the project settings according to the setting in the pom.xml. No
>> (re)generate of eclipse-project files, no problem with new source folders..
>>
>> klaus
>>
>> On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks <dh...@i-hicks.org>
>> wrote:
>>
>>
>>> I'm beginning a new, fairly large, project. Eclipse will be our
>>> development platform, but I've already set up the starting point in
>>>
>> Maven.
>>
>>> Simple enough. Now, my question is, how can I keep them in sync,
>>>
>> easily?
>>
>>> I realize that it's best to re-run "mvn eclipse:eclipse" after adding
>>> dependencies, but what about source folders? I need to add new source
>>> folders, but Maven doesn't know anything about that, so the next time I
>>> re-generate the .project/.classpath files, it'll revert back to those
>>> folders not being "source" folders.
>>>
>>> Any help how to make this behave?
>>> Thanks,
>>> Dave
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Eclipse - Keeping them in sync?
Posted by Klaus <kd...@googlemail.com>.
So you want to add another folder as container for source files?
(additionally to /src/main/java and /target/generated-sources). Good
question..
>From what google points me to i would recommend you to have a look at
http://mojo.codehaus.org/build-helper-maven-plugin/index.html . I do not
know, if any of the eclipse plugins does take this into account (possibly
not). But this should not be a big issue as you could do so manually..
Or you use Intellij (did i say that loud??) It seem as they have solved the
problem already.. http://intellij.net/forums/thread.jspa?threadID=273917
klaus
On Sat, Sep 20, 2008 at 7:25 AM, David C. Hicks <dh...@i-hicks.org> wrote:
> No, that doesn't work. It just resets the source folders to what the Maven
> pom.xml thinks it should be. I had tried that before, but I just
> double-checked before I replied to make certain I wasn't misremembering.
>
> Thanks for the suggestion, though.
>
>
>
> stug23 wrote:
>
>> To bring project up to date when adding source directories, try selecting
>> the
>> following menu item from the contextual menu (right-click on your project
>> in
>> the Package Explorer):
>>
>> Maven => Update Project Configuration
>>
>> This will synch up the source folders with the Eclipse classpath.
>>
>>
>>
>> David C. Hicks wrote:
>>
>>
>>> OK, I installed m2eclipse and it seems happy with my project. I was able
>>> to go through the POM editor and update a lot of information that previously
>>> wasn't there. Very cool.
>>>
>>> Problem: I still don't see it picking up new source folders. If I add a
>>> source folder in Eclipse, how does that end up in the pom.xml to somehow be
>>> included in a production and/or test build? I see a spot to enter source
>>> folders in the POM editor, but it is unclear how to actually enter them.
>>>
>>> Am I missing something?
>>>
>>> Thanks again!
>>> Dave
>>>
>>> PS - for those who recommended Q4E, I'm looking at it, too, but from what
>>> I can tell it seems that m2eclipse is way ahead in terms of fit and finish.
>>> That's just a first impression, though.
>>>
>>>
>>> Stevo Slavic' wrote:
>>>
>>>
>>>> Hello David,
>>>>
>>>> Just as Klaus said, use m2eclipse plugin. After installing it, I'd first
>>>> manually create a folder in eclipse workspace, named as your root maven
>>>> project artifactId, then copy root POM and rest of the project structure
>>>> you've created into that new folder. Finally, with m2eclipse plugin you
>>>> could just "File-->Import...-->General-->Maven Projects" and
>>>> select/browse
>>>> to newly created folder, leaving m2eclipse do the rest.
>>>>
>>>> Regards,
>>>> Stevo.
>>>>
>>>> On Fri, Sep 19, 2008 at 11:24 PM, Klaus <kd...@googlemail.com> wrote:
>>>>
>>>>
>>>>
>>>>> Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin
>>>>> that
>>>>> updates the project settings according to the setting in the pom.xml.
>>>>> No
>>>>> (re)generate of eclipse-project files, no problem with new source
>>>>> folders..
>>>>>
>>>>> klaus
>>>>>
>>>>> On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks <dh...@i-hicks.org>
>>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> I'm beginning a new, fairly large, project. Eclipse will be our
>>>>>> development platform, but I've already set up the starting point in
>>>>>>
>>>>>>
>>>>> Maven.
>>>>>
>>>>>
>>>>>> Simple enough. Now, my question is, how can I keep them in sync,
>>>>>>
>>>>>>
>>>>> easily?
>>>>>
>>>>>
>>>>>> I realize that it's best to re-run "mvn eclipse:eclipse" after adding
>>>>>> dependencies, but what about source folders? I need to add new source
>>>>>> folders, but Maven doesn't know anything about that, so the next time
>>>>>> I
>>>>>> re-generate the .project/.classpath files, it'll revert back to those
>>>>>> folders not being "source" folders.
>>>>>>
>>>>>> Any help how to make this behave?
>>>>>> Thanks,
>>>>>> Dave
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Maven/Eclipse - Keeping them in sync?
Posted by "David C. Hicks" <dh...@i-hicks.org>.
No, that doesn't work. It just resets the source folders to what the
Maven pom.xml thinks it should be. I had tried that before, but I just
double-checked before I replied to make certain I wasn't misremembering.
Thanks for the suggestion, though.
stug23 wrote:
> To bring project up to date when adding source directories, try selecting the
> following menu item from the contextual menu (right-click on your project in
> the Package Explorer):
>
> Maven => Update Project Configuration
>
> This will synch up the source folders with the Eclipse classpath.
>
>
>
> David C. Hicks wrote:
>
>> OK, I installed m2eclipse and it seems happy with my project. I was able
>> to go through the POM editor and update a lot of information that
>> previously wasn't there. Very cool.
>>
>> Problem: I still don't see it picking up new source folders. If I add a
>> source folder in Eclipse, how does that end up in the pom.xml to somehow
>> be included in a production and/or test build? I see a spot to enter
>> source folders in the POM editor, but it is unclear how to actually
>> enter them.
>>
>> Am I missing something?
>>
>> Thanks again!
>> Dave
>>
>> PS - for those who recommended Q4E, I'm looking at it, too, but from
>> what I can tell it seems that m2eclipse is way ahead in terms of fit and
>> finish. That's just a first impression, though.
>>
>>
>> Stevo Slavic' wrote:
>>
>>> Hello David,
>>>
>>> Just as Klaus said, use m2eclipse plugin. After installing it, I'd first
>>> manually create a folder in eclipse workspace, named as your root maven
>>> project artifactId, then copy root POM and rest of the project structure
>>> you've created into that new folder. Finally, with m2eclipse plugin you
>>> could just "File-->Import...-->General-->Maven Projects" and
>>> select/browse
>>> to newly created folder, leaving m2eclipse do the rest.
>>>
>>> Regards,
>>> Stevo.
>>>
>>> On Fri, Sep 19, 2008 at 11:24 PM, Klaus <kd...@googlemail.com> wrote:
>>>
>>>
>>>
>>>> Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin
>>>> that
>>>> updates the project settings according to the setting in the pom.xml. No
>>>> (re)generate of eclipse-project files, no problem with new source
>>>> folders..
>>>>
>>>> klaus
>>>>
>>>> On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks <dh...@i-hicks.org>
>>>> wrote:
>>>>
>>>>
>>>>
>>>>> I'm beginning a new, fairly large, project. Eclipse will be our
>>>>> development platform, but I've already set up the starting point in
>>>>>
>>>>>
>>>> Maven.
>>>>
>>>>
>>>>> Simple enough. Now, my question is, how can I keep them in sync,
>>>>>
>>>>>
>>>> easily?
>>>>
>>>>
>>>>> I realize that it's best to re-run "mvn eclipse:eclipse" after adding
>>>>> dependencies, but what about source folders? I need to add new source
>>>>> folders, but Maven doesn't know anything about that, so the next time I
>>>>> re-generate the .project/.classpath files, it'll revert back to those
>>>>> folders not being "source" folders.
>>>>>
>>>>> Any help how to make this behave?
>>>>> Thanks,
>>>>> Dave
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Eclipse - Keeping them in sync?
Posted by stug23 <pa...@gmail.com>.
To bring project up to date when adding source directories, try selecting the
following menu item from the contextual menu (right-click on your project in
the Package Explorer):
Maven => Update Project Configuration
This will synch up the source folders with the Eclipse classpath.
David C. Hicks wrote:
>
> OK, I installed m2eclipse and it seems happy with my project. I was able
> to go through the POM editor and update a lot of information that
> previously wasn't there. Very cool.
>
> Problem: I still don't see it picking up new source folders. If I add a
> source folder in Eclipse, how does that end up in the pom.xml to somehow
> be included in a production and/or test build? I see a spot to enter
> source folders in the POM editor, but it is unclear how to actually
> enter them.
>
> Am I missing something?
>
> Thanks again!
> Dave
>
> PS - for those who recommended Q4E, I'm looking at it, too, but from
> what I can tell it seems that m2eclipse is way ahead in terms of fit and
> finish. That's just a first impression, though.
>
>
> Stevo Slavic' wrote:
>> Hello David,
>>
>> Just as Klaus said, use m2eclipse plugin. After installing it, I'd first
>> manually create a folder in eclipse workspace, named as your root maven
>> project artifactId, then copy root POM and rest of the project structure
>> you've created into that new folder. Finally, with m2eclipse plugin you
>> could just "File-->Import...-->General-->Maven Projects" and
>> select/browse
>> to newly created folder, leaving m2eclipse do the rest.
>>
>> Regards,
>> Stevo.
>>
>> On Fri, Sep 19, 2008 at 11:24 PM, Klaus <kd...@googlemail.com> wrote:
>>
>>
>>> Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin
>>> that
>>> updates the project settings according to the setting in the pom.xml. No
>>> (re)generate of eclipse-project files, no problem with new source
>>> folders..
>>>
>>> klaus
>>>
>>> On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks <dh...@i-hicks.org>
>>> wrote:
>>>
>>>
>>>> I'm beginning a new, fairly large, project. Eclipse will be our
>>>> development platform, but I've already set up the starting point in
>>>>
>>> Maven.
>>>
>>>> Simple enough. Now, my question is, how can I keep them in sync,
>>>>
>>> easily?
>>>
>>>> I realize that it's best to re-run "mvn eclipse:eclipse" after adding
>>>> dependencies, but what about source folders? I need to add new source
>>>> folders, but Maven doesn't know anything about that, so the next time I
>>>> re-generate the .project/.classpath files, it'll revert back to those
>>>> folders not being "source" folders.
>>>>
>>>> Any help how to make this behave?
>>>> Thanks,
>>>> Dave
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Maven-Eclipse---Keeping-them-in-sync--tp19579618p19582428.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Eclipse - Keeping them in sync?
Posted by "David C. Hicks" <dh...@i-hicks.org>.
OK, I installed m2eclipse and it seems happy with my project. I was able
to go through the POM editor and update a lot of information that
previously wasn't there. Very cool.
Problem: I still don't see it picking up new source folders. If I add a
source folder in Eclipse, how does that end up in the pom.xml to somehow
be included in a production and/or test build? I see a spot to enter
source folders in the POM editor, but it is unclear how to actually
enter them.
Am I missing something?
Thanks again!
Dave
PS - for those who recommended Q4E, I'm looking at it, too, but from
what I can tell it seems that m2eclipse is way ahead in terms of fit and
finish. That's just a first impression, though.
Stevo Slavic' wrote:
> Hello David,
>
> Just as Klaus said, use m2eclipse plugin. After installing it, I'd first
> manually create a folder in eclipse workspace, named as your root maven
> project artifactId, then copy root POM and rest of the project structure
> you've created into that new folder. Finally, with m2eclipse plugin you
> could just "File-->Import...-->General-->Maven Projects" and select/browse
> to newly created folder, leaving m2eclipse do the rest.
>
> Regards,
> Stevo.
>
> On Fri, Sep 19, 2008 at 11:24 PM, Klaus <kd...@googlemail.com> wrote:
>
>
>> Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin that
>> updates the project settings according to the setting in the pom.xml. No
>> (re)generate of eclipse-project files, no problem with new source folders..
>>
>> klaus
>>
>> On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks <dh...@i-hicks.org>
>> wrote:
>>
>>
>>> I'm beginning a new, fairly large, project. Eclipse will be our
>>> development platform, but I've already set up the starting point in
>>>
>> Maven.
>>
>>> Simple enough. Now, my question is, how can I keep them in sync,
>>>
>> easily?
>>
>>> I realize that it's best to re-run "mvn eclipse:eclipse" after adding
>>> dependencies, but what about source folders? I need to add new source
>>> folders, but Maven doesn't know anything about that, so the next time I
>>> re-generate the .project/.classpath files, it'll revert back to those
>>> folders not being "source" folders.
>>>
>>> Any help how to make this behave?
>>> Thanks,
>>> Dave
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Eclipse - Keeping them in sync?
Posted by Rusty Wright <ru...@gmail.com>.
What about doing a right click in the Project Explorer, select New ->
Other ... -> Maven -> Maven Project ?
Then in the New Maven Project window only check Use default Workspace
location, click Next, then you get that glorious list of Archetypes to
choose from.
Stevo Slavi? wrote:
> Hello David,
>
> Just as Klaus said, use m2eclipse plugin. After installing it, I'd first
> manually create a folder in eclipse workspace, named as your root maven
> project artifactId, then copy root POM and rest of the project structure
> you've created into that new folder. Finally, with m2eclipse plugin you
> could just "File-->Import...-->General-->Maven Projects" and select/browse
> to newly created folder, leaving m2eclipse do the rest.
>
> Regards,
> Stevo.
>
> On Fri, Sep 19, 2008 at 11:24 PM, Klaus <kd...@googlemail.com> wrote:
>
>> Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin that
>> updates the project settings according to the setting in the pom.xml. No
>> (re)generate of eclipse-project files, no problem with new source folders..
>>
>> klaus
>>
>> On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks <dh...@i-hicks.org>
>> wrote:
>>
>>> I'm beginning a new, fairly large, project. Eclipse will be our
>>> development platform, but I've already set up the starting point in
>> Maven.
>>> Simple enough. Now, my question is, how can I keep them in sync,
>> easily?
>>> I realize that it's best to re-run "mvn eclipse:eclipse" after adding
>>> dependencies, but what about source folders? I need to add new source
>>> folders, but Maven doesn't know anything about that, so the next time I
>>> re-generate the .project/.classpath files, it'll revert back to those
>>> folders not being "source" folders.
>>>
>>> Any help how to make this behave?
>>> Thanks,
>>> Dave
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven/Eclipse - Keeping them in sync?
Posted by Stevo Slavić <ss...@gmail.com>.
Hello David,
Just as Klaus said, use m2eclipse plugin. After installing it, I'd first
manually create a folder in eclipse workspace, named as your root maven
project artifactId, then copy root POM and rest of the project structure
you've created into that new folder. Finally, with m2eclipse plugin you
could just "File-->Import...-->General-->Maven Projects" and select/browse
to newly created folder, leaving m2eclipse do the rest.
Regards,
Stevo.
On Fri, Sep 19, 2008 at 11:24 PM, Klaus <kd...@googlemail.com> wrote:
> Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin that
> updates the project settings according to the setting in the pom.xml. No
> (re)generate of eclipse-project files, no problem with new source folders..
>
> klaus
>
> On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks <dh...@i-hicks.org>
> wrote:
>
> > I'm beginning a new, fairly large, project. Eclipse will be our
> > development platform, but I've already set up the starting point in
> Maven.
> > Simple enough. Now, my question is, how can I keep them in sync,
> easily?
> > I realize that it's best to re-run "mvn eclipse:eclipse" after adding
> > dependencies, but what about source folders? I need to add new source
> > folders, but Maven doesn't know anything about that, so the next time I
> > re-generate the .project/.classpath files, it'll revert back to those
> > folders not being "source" folders.
> >
> > Any help how to make this behave?
> > Thanks,
> > Dave
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
Re: Maven/Eclipse - Keeping them in sync?
Posted by Klaus <kd...@googlemail.com>.
Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin that
updates the project settings according to the setting in the pom.xml. No
(re)generate of eclipse-project files, no problem with new source folders..
klaus
On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks <dh...@i-hicks.org> wrote:
> I'm beginning a new, fairly large, project. Eclipse will be our
> development platform, but I've already set up the starting point in Maven.
> Simple enough. Now, my question is, how can I keep them in sync, easily?
> I realize that it's best to re-run "mvn eclipse:eclipse" after adding
> dependencies, but what about source folders? I need to add new source
> folders, but Maven doesn't know anything about that, so the next time I
> re-generate the .project/.classpath files, it'll revert back to those
> folders not being "source" folders.
>
> Any help how to make this behave?
> Thanks,
> Dave
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>