[ http://jira.jboss.com/jira/browse/JBREM-70?page=history ]
karan malhi resolved JBREM-70:
------------------------------
Resolution: Done
> Clean up build.xml. Fix .classpath and .project for eclipse
> -----------------------------------------------------------
>
> Key: JBREM-70
> URL: http://jira.jboss.com/jira/browse/JBREM-70
> Project: JBoss Remoting
> Type: Task
> Components: general
> Versions: 1.0.1 final
> Environment: Debian Sarge
> Eclipse Version: 3.0.1
> Reporter: karan malhi
> Assignee: karan malhi
> Priority: Trivial
> Fix For: 1.2.0 beta
> Attachments: .classpath, .project, Eclipse-HowTo.txt
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> build.xml contains dependencies on j2ee, jaxrpc and transaction projects
> which are not used by remoting. remove those entries.
> For eclipse usage, the .classpath has to be fixed to use a variable name
> instead of the relative path. This fix would assume that the user checked out
> Remoting as part of the jboss head. When JBREM 20 and JBREM 11 are finished,
> this classpath setting would change.
> .project doesnt need to have projects listed in there. Eclipse should just
> depend on jars instead of making seperate projects and adding dependencies to
> those projects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
