You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2011/04/04 13:51:05 UTC

[jira] [Commented] (QPID-3181) Auto-generate Eclipse .project and .classpath files for Qpid Java components

    [ https://issues.apache.org/jira/browse/QPID-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015367#comment-13015367 ] 

Robbie Gemmell commented on QPID-3181:
--------------------------------------

Looks good :)

One tiny niggle; I realise it's just a comment for possible future extension, but it would be good to get rid of the hard coded path within the in the 'eclipse-project' target if possible?

> Auto-generate Eclipse .project and .classpath files for Qpid Java components
> ----------------------------------------------------------------------------
>
>                 Key: QPID-3181
>                 URL: https://issues.apache.org/jira/browse/QPID-3181
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Ant Build System
>            Reporter: Keith Wall
>            Assignee: Robbie Gemmell
>            Priority: Minor
>              Labels: eclipse
>         Attachments: 0001-QPID-3181-Addition-of-new-task-eclipse-to-Java-build.patch
>
>
> For those who use Eclipse and prefer to have the Qpid Java components in separate Eclipse projects know that there is much manual effort required to import the projects, set up source paths, class-paths, and establish dependencies between projects.   This has been discussed on the dev-list. I know I can spend up to half an hour getting the manual setup done.
> I've written an extension to the build system that uses http://ant-eclipse.sourceforge.net/ to create the Eclipse .project and .classpath files automatically for each of the Java components (broker, common, client etc).  The new targets make use of the existing properties used by the Ant build process: source folders come from ${module.src} etc, classpaths from ${module.libs} etc and the project dependencies are computed from automatically ${module.depends} so there is no new configuration to maintain.
> There is still a single *manual step* required within Eclipse (to create a linked source from broker, common, client and broker-plugins-access-control projects to their auto-generated code source folder beneath build/scratch) as Ant Eclipse does not yet support the creation of linked-sources, but after this is done you have a fully imported Qpid with zero errors :).  
> I will put together a Wiki page to provide instructions.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org