The following comment has been added to this issue:
Author: Jason Chaffee
Created: Sun, 7 Sep 2003 7:25 PM
Body:
Yes, the current implementation has the classpath hard coded to use oracle and hsqldb.
However, that can be easily changed to allow the project to specify witch jars to use
by using a custom property in the dependency, such as sql.classpath.
In other words, the implementation of how the classpath is being built can be changed
with one or two lines of script to make it more generic.
The point of this feature request is to request that there be a sql plugin that ships
by default with maven. I merely supplied an example that I have written for my
purposes, with about two lines of changes there will be no hard coded classpath for
oracle and hsqldb.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-796
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-796
Summary: How about adding the the sql plugin to maven
Type: Improvement
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Assignee:
Reporter: Jason Chaffee
Created: Sun, 7 Sep 2003 2:52 PM
Updated: Sun, 7 Sep 2003 2:53 PM
Description:
How about adding the the sql plugin I have created to maven? I have attached a zip
file containing all necessary files.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
