You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Bryan Duxbury (JIRA)" <ji...@apache.org> on 2008/12/03 19:31:44 UTC
[jira] Created: (THRIFT-221) Make java build classpath more dynamic
and configurable
Make java build classpath more dynamic and configurable
-------------------------------------------------------
Key: THRIFT-221
URL: https://issues.apache.org/jira/browse/THRIFT-221
Project: Thrift
Issue Type: Improvement
Components: Library (Java), Test Suite
Reporter: Bryan Duxbury
Assignee: Bryan Duxbury
Priority: Trivial
The way that the current Java library and test builds are set up, they rely on an external jar that's assumed to be at some specific path. This isn't where the jar resides on my machine, so every time I want to do some building, I have to hand edit the file, and then when I want to generate a diff for posting on jira, I have to revert the changes.
We should make it so the class path is configurable in a way that doesn't require checkins. There are a couple different ways to do this, but a properties file with the classpath is probably one of the easiest.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (THRIFT-221) Make java build classpath more
dynamic and configurable
Posted by "Bryan Duxbury (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Duxbury resolved THRIFT-221.
----------------------------------
Resolution: Fixed
Committed as part of THRIFT-166.
> Make java build classpath more dynamic and configurable
> -------------------------------------------------------
>
> Key: THRIFT-221
> URL: https://issues.apache.org/jira/browse/THRIFT-221
> Project: Thrift
> Issue Type: Improvement
> Components: Library (Java), Test Suite
> Reporter: Bryan Duxbury
> Assignee: Bryan Duxbury
> Priority: Trivial
>
> The way that the current Java library and test builds are set up, they rely on an external jar that's assumed to be at some specific path. This isn't where the jar resides on my machine, so every time I want to do some building, I have to hand edit the file, and then when I want to generate a diff for posting on jira, I have to revert the changes.
> We should make it so the class path is configurable in a way that doesn't require checkins. There are a couple different ways to do this, but a properties file with the classpath is probably one of the easiest.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.