You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Scott Semyan (JIRA)" <be...@incubator.apache.org> on 2005/05/09 22:28:08 UTC
[jira] Created: (BEEHIVE-628) derby.jar varible inconsistent in petstoreweb application
derby.jar varible inconsistent in petstoreweb application
---------------------------------------------------------
Key: BEEHIVE-628
URL: http://issues.apache.org/jira/browse/BEEHIVE-628
Project: Beehive
Type: Bug
Components: Samples
Versions: V1
Reporter: Scott Semyan
Priority: Minor
The derby.jar variable in build.properties for PetstoreWeb is inconsistent with the httpunit.dir variable. One points to a jar file and the other points to the install directory. The comment for derby.jar is misleading:
derby.jar=/path/to/derby
We should either make them consistent (have a derby.dir variable pointing to the Derby install location), or we should add a comment to the build.properties file indicating that derby.jar should point to the full path to the derby.jar like so:
# Set this variable to point to the derby jar file
derby.jar=/path/to/derby/jar
I prefer the former to keep things consistent.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (BEEHIVE-628) derby.jar varible inconsistent in petstoreweb application
Posted by "Eddie O'Neil (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-628?page=all ]
Eddie O'Neil resolved BEEHIVE-628:
----------------------------------
Resolution: Fixed
Fixed in SVN 169407. Applies most of these fixes from Scott.
> derby.jar varible inconsistent in petstoreweb application
> ---------------------------------------------------------
>
> Key: BEEHIVE-628
> URL: http://issues.apache.org/jira/browse/BEEHIVE-628
> Project: Beehive
> Type: Bug
> Components: Samples
> Versions: V1
> Reporter: Scott Semyan
> Assignee: Eddie O'Neil
> Priority: Minor
> Fix For: V1
>
> The derby.jar variable in build.properties for PetstoreWeb is inconsistent with the httpunit.dir variable. One points to a jar file and the other points to the install directory. The comment for derby.jar is misleading:
> derby.jar=/path/to/derby
> We should either make them consistent (have a derby.dir variable pointing to the Derby install location), or we should add a comment to the build.properties file indicating that derby.jar should point to the full path to the derby.jar like so:
> # Set this variable to point to the derby jar file
> derby.jar=/path/to/derby/jar
> I prefer the former to keep things consistent.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (BEEHIVE-628) derby.jar varible inconsistent in petstoreweb application
Posted by "Eddie O'Neil (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-628?page=all ]
Eddie O'Neil closed BEEHIVE-628:
--------------------------------
Closing. Any other comments welcome if there's petstoreWeb feedback...
> derby.jar varible inconsistent in petstoreweb application
> ---------------------------------------------------------
>
> Key: BEEHIVE-628
> URL: http://issues.apache.org/jira/browse/BEEHIVE-628
> Project: Beehive
> Type: Bug
> Components: Samples
> Versions: V1
> Reporter: Scott Semyan
> Assignee: Eddie O'Neil
> Priority: Minor
> Fix For: V1
>
> The derby.jar variable in build.properties for PetstoreWeb is inconsistent with the httpunit.dir variable. One points to a jar file and the other points to the install directory. The comment for derby.jar is misleading:
> derby.jar=/path/to/derby
> We should either make them consistent (have a derby.dir variable pointing to the Derby install location), or we should add a comment to the build.properties file indicating that derby.jar should point to the full path to the derby.jar like so:
> # Set this variable to point to the derby jar file
> derby.jar=/path/to/derby/jar
> I prefer the former to keep things consistent.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-628) derby.jar varible inconsistent in petstoreweb application
Posted by "Eddie O'Neil (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-628?page=all ]
Eddie O'Neil updated BEEHIVE-628:
---------------------------------
Assign To: Eddie O'Neil
Fix Version: V1
Yeah, derby.jar and the HTTPUnit JARs have different purposes in my mind. derby.jar needs to be *in* the webapp in order for things to work -- that means we need to move it and is thus why I prefer explicitly describing the path to it rather than to the Derby distribution. If it's in the distribution, great, but I'd rather copy something that is referenced explicitly.
On HTTPUnit, we only need to reference those JARs which is why the httpunit.dir property exists. Also, there are many HTTPUnit JARs, so having to reference each individually would be a pain.
In the end, the build file is just a sample, and it is easy to change in another environment.
I agree that the derby.jar path would be easier to understand if it was "/path/to/derby.jar".
> derby.jar varible inconsistent in petstoreweb application
> ---------------------------------------------------------
>
> Key: BEEHIVE-628
> URL: http://issues.apache.org/jira/browse/BEEHIVE-628
> Project: Beehive
> Type: Bug
> Components: Samples
> Versions: V1
> Reporter: Scott Semyan
> Assignee: Eddie O'Neil
> Priority: Minor
> Fix For: V1
>
> The derby.jar variable in build.properties for PetstoreWeb is inconsistent with the httpunit.dir variable. One points to a jar file and the other points to the install directory. The comment for derby.jar is misleading:
> derby.jar=/path/to/derby
> We should either make them consistent (have a derby.dir variable pointing to the Derby install location), or we should add a comment to the build.properties file indicating that derby.jar should point to the full path to the derby.jar like so:
> # Set this variable to point to the derby jar file
> derby.jar=/path/to/derby/jar
> I prefer the former to keep things consistent.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira