Michal, I have committed a quick patch for EJB dependency handling so that extensions for the EJB type artifacts is ".jar" and not ".ejb".
I hope I haven't broken anything. I have tested it successfully on my current project. Thanks -Vincent > -----Original Message----- > From: Michal Maczka [mailto:[EMAIL PROTECTED] > Sent: 18 June 2003 22:52 > To: Maven Developers List > Subject: RE: Problems of EJB plugin and Dependencies download > > > I see 2 solutions: > > > > 1/ Add a property called <classpath>false</classpath> and if found the > > said dependency is not added to the Classpath? > > > > or > > > > 2/ Define a list of well known artifact types. That would server 2 > > purposes: > > a- to know if the said dependency type should be added to the classpath > > b- to know what extension this type has > > > > I prefer 2. > > > > -Vincent > > Jason was saying that it will be possible to reuse some components of > maven-new. > > If we are not going to make I can also propose two other options: > > 1) Add all artifacts to class path. I don't think people are using too > many > non "jar like" artifacts. Too many things in classspath makes no harm. > > > Regarding your propositions: > ad 1) -1 : I think that option with marking deps in POM..is bad. -1 > ad 2) +1 I did it already with XML based configuration files sometimes > ago. But think XML or even java properties are too heavy there. > Why just not put it to Java code? > > Michal > > P.S. > > I would not rush with those changes for rc1. > > > > > > --------------------------------------------------------------------- > 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]
