Thanks Stephen for explaining! Makes lots of sense!!!
Sonia Stephen Connolly-2 wrote: > > you are working for ericsson... so com.ericsson.what.ever.you.want > > Or if you are working on a project hosted on dev.java.net you'd use > net.java.dev.projectname > > It's just like package names in java... there are no hard and fast > rules... but if you ever want to interact with the public > repositories, you'd want to ensure that the group Id you are using is > not used by anyone else... > > For example, if you publish to your internal repo using com.sun... and > then sun publish to repo1 an artifact with the same groupId and > artifactId but a newer version, it may interfere with your build as > that newer version will bee seen in version ranges.... > > If they deploy something with the same version, and your developers > accidentally get that one on their machein first you'll have all sorts > of trouble. > > So the recommendation is to use a group ID that you control (in this > case by you, we mean your employers) > > -Stephen > > 2008/10/2 solo1970 <[EMAIL PROTECTED]>: >> >> What does that mean exactly??? >> >> >> Stephen Connolly-2 wrote: >>> >>> yes, but it's best to use a group Id that you control >>> >>> Sent from my iPod >>> >>> On 2 Oct 2008, at 19:48, solo1970 <[EMAIL PROTECTED]> >>> wrote: >>> >>>> >>>> Ok, so if understand this correctly I can give it any groupId >>>> ArtifctId that >>>> I choose regardless of the file name. Once deployed with those >>>> coordinates, then that's what I use to declare the dependencies..... >>>> >>>> Sonia >>>> >>>> >>>> >>>> Stephen Connolly-2 wrote: >>>>> >>>>> If they already exist in a maven repo... you could use that >>>>> (provided it >>>>> is >>>>> not a short groupId... so if it was www.somecompany.org that you >>>>> got the >>>>> files you could use the groupId of "com.somecompany") >>>>> >>>>> If you are unsure in any way... you could use your groupId to >>>>> ensure that >>>>> it >>>>> is these exact jars that are used... i.e. "com.ericsson.ncl" >>>>> >>>>> If you are bored you could crack-open the jar files and see what the >>>>> common >>>>> package root is and use that >>>>> >>>>> -Stephen >>>>> >>>>> 2008/10/2 solo1970 <[EMAIL PROTECTED]> >>>>> >>>>>> >>>>>> Hello, >>>>>> >>>>>> I am fairly new to Maven and Archiva and would like some help on two >>>>>> issues >>>>>> both related to the same problem. >>>>>> >>>>>> We have to use 2 jar files: nclmsg.public.jar and nclutil.public.jar >>>>>> provided to us by A third party (we need for compile and packaging >>>>>> (war)) >>>>>> >>>>>> 1. In order to use them, I want to do a mvn deploy:deploy-file to >>>>>> our >>>>>> repository, which is Archiva >>>>>> >>>>>> 2. How do we figure out the groupId, artifactId and version of those >>>>>> jars... >>>>>> I searched the different repositories on the net, but didn't find >>>>>> anything, >>>>>> probably because they were provided to us. >>>>>> >>>>>> mvn deploy:deploy-file -Dfile=nclmsg.public.jar -DgroupId=??? >>>>>> -DartifactId=??? -Dversion=???? -Dpackaging=jar -DgeneratePom=true >>>>>> -DcreateChecksum=true -DrepositoryId=3pp_cache >>>>>> -Durl=dav:http://maven.xxxx.se:8888/repository/3pp_cache >>>>>> >>>>>> Can anyone help clarify this for me??? >>>>>> >>>>>> Sonia >>>>>> -- >>>>>> View this message in context: >>>>>> http://www.nabble.com/Determining-jar-groupId-ArtifactId-for-deploy-file-tp19781489p19781489.html >>>>>> Sent from the Maven - Users mailing list archive at Nabble.com. >>>>>> >>>>>> >>>>>> --- >>>>>> ------------------------------------------------------------------ >>>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/Determining-jar-groupId-ArtifactId-for-deploy-file-tp19781489p19785329.html >>>> Sent from the Maven - Users mailing list archive at Nabble.com. >>>> >>>> >>>> --------------------------------------------------------------------- >>>> 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] >>> >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/Determining-jar-groupId-ArtifactId-for-deploy-file-tp19781489p19786021.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> 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] > > > -- View this message in context: http://www.nabble.com/Determining-jar-groupId-ArtifactId-for-deploy-file-tp19781489p19798148.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
