RE: [m2] exception while creating skeleton project
it sounds like having to create a dummy pom and blank jar is a bit of a hack isn't there a cleaner way to support jars that can't be released? simon -Original Message- From: Trygve Laugstøl [mailto:[EMAIL PROTECTED] Sent: 29 April 2005 13:55 To: Maven Users List Subject: Re: [m2] exception while creating skeleton project ... jdbc.jar is a jar file from Sun that we're not allowed to distribute to you will have to make a stub pom[1] for it. For this particular jar the classes will be in your JDK if you use a recent JDK version (IIRC JDBC 2 was included in 1.2) so you can just make a empty file in your repo called: jdbc/jdbc/2.0/jdbc-2.0.jar [1]: project modelVersion4.0.0/modelVersion groupIdjdbc/groupId artifactIdjdbc/artifactId version2.0/version /project -- Trygve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] exception while creating skeleton project
On 5/3/05, Simon Matic Langford [EMAIL PROTECTED] wrote: it sounds like having to create a dummy pom and blank jar is a bit of a hack isn't there a cleaner way to support jars that can't be released? yes, working on it for alpha-2. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] exception while creating skeleton project
On Fri, 2005-04-29 at 13:23 +0100, Thomas Riley wrote: Hi, I've downloaded the Maven 2 technology preview, installed and set up MAVEN_HOME but when I run: m2 archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app ... maven gets some way through the process but the fails (fetching jdbc-2.0.pom?) - output below. Something I've missed? Maven will only try to resolve these dependencies if there is a pom.xml in the current directory, so I think that this might be cause. As for the jdbc artifact it's beeing sucked in because it's listed in the Velocity pom. jdbc.jar is a jar file from Sun that we're not allowed to distribute to you will have to make a stub pom[1] for it. For this particular jar the classes will be in your JDK if you use a recent JDK version (IIRC JDBC 2 was included in 1.2) so you can just make a empty file in your repo called: jdbc/jdbc/2.0/jdbc-2.0.jar [1]: project modelVersion4.0.0/modelVersion groupIdjdbc/groupId artifactIdjdbc/artifactId version2.0/version /project -- Trygve Tom [snip] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] exception while creating skeleton project
I've corrected the velocity pom, since jdbc is optional. Sorry for the inconvenience. - Brett On 4/29/05, Trygve Laugstøl [EMAIL PROTECTED] wrote: On Fri, 2005-04-29 at 13:23 +0100, Thomas Riley wrote: Hi, I've downloaded the Maven 2 technology preview, installed and set up MAVEN_HOME but when I run: m2 archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app ... maven gets some way through the process but the fails (fetching jdbc-2.0.pom?) - output below. Something I've missed? Maven will only try to resolve these dependencies if there is a pom.xml in the current directory, so I think that this might be cause. As for the jdbc artifact it's beeing sucked in because it's listed in the Velocity pom. jdbc.jar is a jar file from Sun that we're not allowed to distribute to you will have to make a stub pom[1] for it. For this particular jar the classes will be in your JDK if you use a recent JDK version (IIRC JDBC 2 was included in 1.2) so you can just make a empty file in your repo called: jdbc/jdbc/2.0/jdbc-2.0.jar [1]: project modelVersion4.0.0/modelVersion groupIdjdbc/groupId artifactIdjdbc/artifactId version2.0/version /project -- Trygve Tom [snip] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
