Oh Ok thanks for the explanation I think the internal repository idea is more what I had in mind. What can Mahven do in terms of this feature and is there any documentation for it?
-- Thanks, Mike ---------------------------------------------- "Gareth Western" <[EMAIL PROTECTED]> 03/31/2006 09:34 AM Please respond to "Maven Users List" <[email protected]> To "Maven Users List" <[email protected]> cc Subject Re: Quick explanation requested Hi, You would only have an app stored on ibiblio if you were willing to distribute your application (along with the source), and as long as your application's licensing is compatible with this. AFAIK there are no "safeguards" on ibiblio. It's a publicly-browsable repository which people can use to retrieve code on which their own application relies. I would guess that you don't need to upload your application to ibiblio anyway. Perhaps you're confusing ibiblio with creating your own internal repository, the latter of which you COULD upload your own applications for internal downloads, etc.? Cheers, Gareth On 3/31/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: > > I'd appreciate if someone can shed some light on 2 points. > > 1) Why is it a good idea to have a complete app stored on ibiblio > including source? Is there any safeguards as to who can download these > projects (i.e. what security is in place, for example if someone knows or > guesses your artifactId)? > > 2) Why would we initate the following command below, if we get all the > plugin components initally when we download any goal the first time? > mvn install:install-file -DgroupId=javax.activation > -DartifactId=activation -Dversion=1.0.2 > -Dpackaging=jar -Dfile=/ > > Thanks. > ---------------------------------------------- > Miike Tedesco > ---------------------------------------------- >
