"Kyle Adams" <[EMAIL PROTECTED]> wrote on 29/10/2003 02:00:56 AM:
> > Rather than using the version numbered jar, can you deploy an > > unversioned one instead? > > Very likely, but then (if I understand correctly) wouldn't I lose > the ability to grab the JAR from a repository? Not that I can tell. You'd copy the versioned one to an unversioned name and then deploy it, right? > Most of what I've seen up till now has involved using the repository > for "plain vanilla" JARs. I'm trying to figure out if the > repository can be adapted for J2EE packages. I'd love to be able to We use it for J2EE packages at work. > say that MyEJB-A.jar has a dependency on MyEJB-B.jar, version 1.0.1. > The build system should then be able to retrieve MyEJB-B-ejb- > client-1.0.1.jar from the repository and include it in the classpath > when building MyEJB-A.jar. But we explicitly specify the dependencies. > Fortunately all of the above can be scripted via various Ant tasks. Or via maven.xml. > Regardless, I've gotten some good ideas on how to handle versioned > JAR file names in J2EE out of this discussion - thanks! Cool. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
