You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by manyofh <ma...@googlemail.com> on 2014/01/11 08:41:56 UTC

Question regarding log4j2 development with Eclipse and Maven

Hi guys,

does anyone have experiences with log4j2 development in combination with
Eclipse and Maven?
I guess I could need some support there.

What I want to do is to check out the code (using Eclipse with
Subversive) and importing them into Eclipse.
At the end I would like to have the "trunk" (parent pom) as a project in
my workspace and handle it as one with all the build path (right click
on the project -> build path -> e.g. configure build path) functionality
that I have with a normal java project in Eclipse. This project should
contain as well all the other projects (module poms).

Something like this:
--- log4j2 (trunk, parent pom)
 |---log4j-core
 |---log4j-api
.
.
.
.

With this constellation I would be able to use all the eclipse features
e. g. JUnit integration and so on and as well and in addition to it I
can sync the whole trunk over one project instead of checking every
project/module.

I tried a few things but nothing works really fine.

Any thoughts?

Cheers,
Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: Question regarding log4j2 development with Eclipse and Maven

Posted by manyofh <ma...@googlemail.com>.
Hi Remko,

thanks a lot for your help. It worked :)

Regards,
Andreas

On 11.01.2014 10:30, Remko Popma wrote:
> About syncing all modules via one project:
>  In my Eclipse workspace I have the log4j trunk checked out as a
> non-java project. I then followed the procedure I described to create
> java projects for the modules I want to work on. The modules are
> separate java projects but point to subdirectories of the log4j project.
> 
> The nice thing is that the projects are linked because they point to the
> same physical files/directories: if I modify a file in the log4j-core
> project, that same file in the log4j project also shows the "modified"
> svn decorator icon.
> If I right-click the log4j project and select Team > Update from the
> popup menu, all module projects are also updated.
> 
> Hope this helps,
> Remko
> 
> 
> On Sat, Jan 11, 2014 at 5:31 PM, Remko Popma <remko.popma@gmail.com
> <ma...@gmail.com>> wrote:
> 
>     After checkout, run this command:
>     mvn build eclipse:eclipse
> 
>     This will generate eclipse .project and .classpath files in each
>     module in the log4j project.
>     Now use the Eclipse new java project wizard to create an Eclipse
>     project for each module (like log4j-api, log4j-core, ...).
>     When you do this, make sure to specify the location where the module
>     is actually located, and Eclipse will find the .project and
>     .classpath files that Maven generated.
> 
> 
>     On Sat, Jan 11, 2014 at 4:41 PM, manyofh <manyofh@googlemail.com
>     <ma...@googlemail.com>> wrote:
> 
>         Hi guys,
> 
>         does anyone have experiences with log4j2 development in
>         combination with
>         Eclipse and Maven?
>         I guess I could need some support there.
> 
>         What I want to do is to check out the code (using Eclipse with
>         Subversive) and importing them into Eclipse.
>         At the end I would like to have the "trunk" (parent pom) as a
>         project in
>         my workspace and handle it as one with all the build path (right
>         click
>         on the project -> build path -> e.g. configure build path)
>         functionality
>         that I have with a normal java project in Eclipse. This project
>         should
>         contain as well all the other projects (module poms).
> 
>         Something like this:
>         --- log4j2 (trunk, parent pom)
>          |---log4j-core
>          |---log4j-api
>         .
>         .
>         .
>         .
> 
>         With this constellation I would be able to use all the eclipse
>         features
>         e. g. JUnit integration and so on and as well and in addition to
>         it I
>         can sync the whole trunk over one project instead of checking every
>         project/module.
> 
>         I tried a few things but nothing works really fine.
> 
>         Any thoughts?
> 
>         Cheers,
>         Andreas
> 
>         ---------------------------------------------------------------------
>         To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>         <ma...@logging.apache.org>
>         For additional commands, e-mail:
>         log4j-dev-help@logging.apache.org
>         <ma...@logging.apache.org>
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: Question regarding log4j2 development with Eclipse and Maven

Posted by Remko Popma <re...@gmail.com>.
About syncing all modules via one project:
 In my Eclipse workspace I have the log4j trunk checked out as a non-java
project. I then followed the procedure I described to create java projects
for the modules I want to work on. The modules are separate java projects
but point to subdirectories of the log4j project.

The nice thing is that the projects are linked because they point to the
same physical files/directories: if I modify a file in the log4j-core
project, that same file in the log4j project also shows the "modified" svn
decorator icon.
If I right-click the log4j project and select Team > Update from the popup
menu, all module projects are also updated.

Hope this helps,
Remko


On Sat, Jan 11, 2014 at 5:31 PM, Remko Popma <re...@gmail.com> wrote:

> After checkout, run this command:
> mvn build eclipse:eclipse
>
> This will generate eclipse .project and .classpath files in each module in
> the log4j project.
> Now use the Eclipse new java project wizard to create an Eclipse project
> for each module (like log4j-api, log4j-core, ...).
> When you do this, make sure to specify the location where the module is
> actually located, and Eclipse will find the .project and .classpath files
> that Maven generated.
>
>
> On Sat, Jan 11, 2014 at 4:41 PM, manyofh <ma...@googlemail.com> wrote:
>
>> Hi guys,
>>
>> does anyone have experiences with log4j2 development in combination with
>> Eclipse and Maven?
>> I guess I could need some support there.
>>
>> What I want to do is to check out the code (using Eclipse with
>> Subversive) and importing them into Eclipse.
>> At the end I would like to have the "trunk" (parent pom) as a project in
>> my workspace and handle it as one with all the build path (right click
>> on the project -> build path -> e.g. configure build path) functionality
>> that I have with a normal java project in Eclipse. This project should
>> contain as well all the other projects (module poms).
>>
>> Something like this:
>> --- log4j2 (trunk, parent pom)
>>  |---log4j-core
>>  |---log4j-api
>> .
>> .
>> .
>> .
>>
>> With this constellation I would be able to use all the eclipse features
>> e. g. JUnit integration and so on and as well and in addition to it I
>> can sync the whole trunk over one project instead of checking every
>> project/module.
>>
>> I tried a few things but nothing works really fine.
>>
>> Any thoughts?
>>
>> Cheers,
>> Andreas
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>>
>

Re: Question regarding log4j2 development with Eclipse and Maven

Posted by Remko Popma <re...@gmail.com>.
After checkout, run this command:
mvn build eclipse:eclipse

This will generate eclipse .project and .classpath files in each module in
the log4j project.
Now use the Eclipse new java project wizard to create an Eclipse project
for each module (like log4j-api, log4j-core, ...).
When you do this, make sure to specify the location where the module is
actually located, and Eclipse will find the .project and .classpath files
that Maven generated.


On Sat, Jan 11, 2014 at 4:41 PM, manyofh <ma...@googlemail.com> wrote:

> Hi guys,
>
> does anyone have experiences with log4j2 development in combination with
> Eclipse and Maven?
> I guess I could need some support there.
>
> What I want to do is to check out the code (using Eclipse with
> Subversive) and importing them into Eclipse.
> At the end I would like to have the "trunk" (parent pom) as a project in
> my workspace and handle it as one with all the build path (right click
> on the project -> build path -> e.g. configure build path) functionality
> that I have with a normal java project in Eclipse. This project should
> contain as well all the other projects (module poms).
>
> Something like this:
> --- log4j2 (trunk, parent pom)
>  |---log4j-core
>  |---log4j-api
> .
> .
> .
> .
>
> With this constellation I would be able to use all the eclipse features
> e. g. JUnit integration and so on and as well and in addition to it I
> can sync the whole trunk over one project instead of checking every
> project/module.
>
> I tried a few things but nothing works really fine.
>
> Any thoughts?
>
> Cheers,
> Andreas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>