Just thought I'd bring it up. I have to have this conversation periodically on the Commons mailing lists too. :)
On Tue, Jun 28, 2011 at 7:12 PM, Bruno Borges <bruno.bor...@gmail.com> wrote: > I understand that, but as this is a 1.5 release, I thought it shouldn't be a > problem as it is mostly used for new projects. > > I would take the risk. I prefer to have collision between 1.4 and 1.5 > wicketstuff artifacts, instead of pushing jasperreports-version.jar to a lib > folder instead of the actual (official) jasperreports-version.jar, if you > know what I mean. > > *Bruno Borges* > www.brunoborges.com.br > +55 21 76727099 > > > > On Tue, Jun 28, 2011 at 8:02 PM, James Carman > <ja...@carmanconsulting.com>wrote: > >> Sorry, hit send too soon. >> >> Are you changing artifact ids? If you are, then Maven will think that >> it's something different and will thus allow both the old and the new >> jars on the same classpath. If the class names don't change, then >> you've go the potential for a collision. Now, this might be an >> acceptable risk when you consider how many folks are actually using >> the wicketstuff code, but I thought I'd bring it up. We face this >> same stuff at Apache Commons. >> >> On Tue, Jun 28, 2011 at 6:48 PM, James Carman >> <ja...@carmanconsulting.com> wrote: >> > Are you changing artifact ids? >> > >> > On Tue, Jun 28, 2011 at 6:26 PM, Bruno Borges <bruno.bor...@gmail.com> >> wrote: >> >> How can that happen if the purpose of this change is exactly to avoid >> >> collisions ? >> >> >> >> >> >> *Bruno Borges* >> >> www.brunoborges.com.br >> >> +55 21 76727099 >> >> >> >> >> >> >> >> On Tue, Jun 28, 2011 at 6:59 PM, James Carman >> >> <jcar...@carmanconsulting.com>wrote: >> >> >> >>> This can cause classpath collisions >> >>> >> >>> Sent from my Android device. Please excuse typos and brevity. >> >>> On Jun 28, 2011 5:27 PM, "Bruno Borges" <bruno.bor...@gmail.com> >> wrote: >> >>> > I started to modify all JAR poms to have the wicketstuff- preffix. >> >>> > >> >>> > Is anybody against this? Why? >> >>> > >> >>> > :-) >> >>> > >> >>> > *Bruno Borges* >> >>> > www.brunoborges.com.br >> >>> > +55 21 76727099 >> >>> > >> >>> > >> >>> > >> >>> > On Sat, Mar 26, 2011 at 9:22 PM, Bruno Borges < >> bruno.bor...@gmail.com >> >>> >wrote: >> >>> > >> >>> >> We could simply rename the artifactId property of projects, >> prepending >> >>> with >> >>> >> wicketstuff-, like wicket does with their modules. >> >>> >> >> >>> >> Still, I agree that this is will take some time and effort. >> >>> >> >> >>> >> >> >>> >> Bruno Borges >> >>> >> www.brunoborges.com.br >> >>> >> +55 21 76727099 >> >>> >> >> >>> >> "The glory of great men should always be >> >>> >> measured by the means they have used to >> >>> >> acquire it." >> >>> >> - Francois de La Rochefoucauld >> >>> >> >> >>> >> >> >>> >> >> >>> >> On Sat, Mar 26, 2011 at 12:36 PM, Michael O'Cleirigh < >> >>> >> michael.ocleir...@rivulet.ca> wrote: >> >>> >> >> >>> >>> This is more complicated than I first thought. >> >>> >>> >> >>> >>> See this issue: http://jira.codehaus.org/browse/MDEPLOY-93 >> >>> >>> >> >>> >>> Essentially it seems that the deploy plugin does not honour the >> >>> >>> <finalName> option and uploads in the original format when >> deploying. >> >>> >>> >> >>> >>> I will investigate this further but it won't be part of the next >> point >> >>> >>> releases unfortunately. >> >>> >>> >> >>> >>> Mike >> >>> >>> >> >>> >>> >> >>> >>> I'm planning on doing point releases this weekend for 1.4.16.1 and >> >>> >>>> 1.5-rc2.1 and I'll make sure the artifacts generate using the >> longer >> >>> name. >> >>> >>>> >> >>> >>>> Thanks, >> >>> >>>> >> >>> >>>> Mike >> >>> >>>> >> >>> >>>> >> >>> >>>> In the most parent wicketstuff pom.xml: >> >>> >>>>> >> >>> >>>>> <build> >> >>> >>>>> >> >>> >> >>> >> <finalName>${project.groupId}-${project.artifactId}-${project.version}.jar</finalName> >> >>> >>>>> >> >>> >>>>> .... >> >>> >>>>> >> >>> >>>>> On Fri, Mar 25, 2011 at 9:31 AM, Wilhelmsen Tor Iver< >> >>> toriv...@arrive.no >> >>> >>>>> >wrote: >> >>> >>>>> >> >>> >>>>> - jasperreports-1.4.16.jar >> >>> >>>>>>> - jasperreports-3.7.2.jar >> >>> >>>>>>> The first one is from WicketStuff, but still, it is confusing >> to >> >>> see >> >>> >>>>>>> >> >>> >>>>>> this. >> >>> >>>>>> >> >>> >>>>>> This one of my biggest peeves with Maven: It has this concept of >> a >> >>> >>>>>> "groupId" to namespace artifacts in the repository, but this is >> of >> >>> no >> >>> >>>>>> consequence when the jar files appear in the classpath, since >> the >> >>> >>>>>> groupId >> >>> >>>>>> namespace is not part of the actual file name. >> >>> >>>>>> >> >>> >>>>>> A workaround could be to prefix the jar file name with the >> groupId >> >>> >>>>>> namespace somehow. >> >>> >>>>>> >> >>> >>>>>> - Tor Iver >> >>> >>>>>> >> >>> >>>>>> >> >>> >>>>> >> >>> >>>>> >> >>> >>>> >> >>> >>>> >> --------------------------------------------------------------------- >> >>> >>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> >>> >>>> For additional commands, e-mail: users-h...@wicket.apache.org >> >>> >>>> >> >>> >>>> >> >>> >>> >> >>> >>> >> --------------------------------------------------------------------- >> >>> >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> >>> >>> For additional commands, e-mail: users-h...@wicket.apache.org >> >>> >>> >> >>> >>> >> >>> >> >> >>> >> >> >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
