[
https://issues.apache.org/jira/browse/PLUTO-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622080#action_12622080
]
Craig Doremus commented on PLUTO-495:
-------------------------------------
We have not been keeping any of the configuration files for Eclipse (or any
other IDE) in our source code repository. The m2eclipse plugin has improved
greatly lately and should be used instead of manually updating the Java build
path. Just make sure you configure the plugin to enable nested modules.
We would greatly appreciate any help from the Pluto community. Find an issue is
Jira you would like to work on and attach your patch file to the issue. If you
use a Subversion plugin (I used Subclipse), creating a patch file is easy. If
you don't have any preferences, I'd suggest PLUTO-443, which is to add a
resource serving test to the JSR-286 testsuite.
> Eclipse autobuilld/compile/debug project
> ----------------------------------------
>
> Key: PLUTO-495
> URL: https://issues.apache.org/jira/browse/PLUTO-495
> Project: Pluto
> Issue Type: Improvement
> Components: build system
> Affects Versions: 2.0.0
> Environment: Ubuntu/Eclipse Java 1.5 x86
> Reporter: Gonzalo Aguilar
> Priority: Minor
> Fix For: 2.0.0
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> Hello all!
> I wanted to checkout the project and contribute to it with some fixes and
> updates. But I found maven difficult to use/maintain and does not add
> anything to pure developement for beginners. This is only my opinion...
> So I decided to create a project overlayed into the main maven project so
> anyone can develop/debug with minimal effort with Eclipse. I'm trying not to
> break anything inside the tree so you can use the project without
> modifications.
> Maybe someone will want to use this overlay. The problem is that I don't know
> the right way to contribute with this. Should I do a patch? Do you think
> it's useful?
> Do you want me to prepare this for common use?
> Anyway, if you don't like it or don't want it, I will try to submit some
> patches to the project to try address several issues:
> 1.- Functional bugs/improvements to the version 2.0 (trunk)
> 2.- Configuration improvement (mostly logging and exception handling) to let
> developers what's going on in initialization.
> More on this later.
> Now what I'm doing is to track down whole initialization to check everything
> runs ok and learning how everything works...
> Thank you very much!
> Best regards,
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
