Community
Participate
Working Groups
I'm trying to implement a classpath container that will represent an externally managed project (it could be anything, starting from Netbeans or IDEA projects to Ant's file). My code is pulling out all information about project and trying to add sources and libraries into the classpath container. I managed to create libraries, but source folders cause problems. I can see these source folders within my container/library in Package Explorer but java builder is complaining about build path issues (saying that my container is invalid or there is a circular dependencies. Another issue is that "Open Type" dialog can see classes from those source folders, but then I trying to jump into the code it is saying that can't map resource showing a correct path to the .java file. I'm running this on Eclipse 3.1RC2
I wonder if it is possible to address this issue in 3.1 stream or maybe in 3.2?
Wouldn't it be possible for you to construct a true project for the externally managed project ? This would allow you to express more settings etc... on it. The change you are asking is quite involving, unclear we will have the resource to do it for 3.2.
(In reply to comment #2) > Wouldn't it be possible for you to construct a true project for the externally > managed project ? This would allow you to express more settings etc... on it. In this case it will be necessary to synchronize between external project and this current one all the time, which I'm trying to avoid. One of the most interesting applications for this is to use Maven's project descriptor to manage all dependencies and source folders (it can be quite advanced, when nested projects are used), so it would be quite difficult to keep it in sync because it will be necessary to implement bidirectional synchonization (changes in a .classpath should be propagated back to Maven projects, but it is not 0ne-to-one mapping because .classpath is flat, but Maven is working with hierarchical project structure and sub-project descriptors). > The change you are asking is quite involving, unclear we will have the resource > to do it for 3.2. If you think about this feature, it can actually make import from 3rd party projects much easier and more dynamic (in a way that it will be picking up all the changes after import). So, I believe it is quite important feature.
I come across another use case for this feature. There are number of plugins that may generate source code that need to be compiled (preferrable by Eclipse compiler). The list includes XDocled (used by WTP), some of the ORM data binding tools and even APT tool in Java5. Usually target folders where these sources are generated are not comitted to version control, so the only way to find out if there are additional sources is to look into configuration of the external tool and explicitly add these folders into the project. That leads into the situation when the same path specified in two places (if not more) and it would be really great to avoid this. I believe WTP project will benefit from this feature too.
Any chance this could be resolved for 3.2?
Any chance this can be supported in Eclipse 3.3?
