You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Bruno Borges <br...@gmail.com> on 2011/03/25 00:48:51 UTC
WicketStuff artifacts naming strategy
After 10 minutes I realized that having these two jars was not the problem
of some bug on my project...
- jasperreports-1.4.16.jar
- jasperreports-3.7.2.jar
The first one is from WicketStuff, but still, it is confusing to see this.
Should we configure the POM files to export the jar with a 'wicketstuff-'
preffix on all modules?
Cheers,
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
Re: WicketStuff artifacts naming strategy
Posted by Clint Checketts <ch...@gmail.com>.
You convinced me. ;)
On Tue, Jun 28, 2011 at 4:45 PM, Bruno Borges <br...@gmail.com>wrote:
> because the JAR file does not come with the groupId, and some projects have
> some very short names, like dojo, or yui.
>
> If I look at a JAR file named "wicket-dojo-1.5-RC5.1.jar", is that from
> wicketstuff or wicket ?
>
> *Bruno Borges*
> www.brunoborges.com.br
> +55 21 76727099
>
>
>
> On Tue, Jun 28, 2011 at 6:39 PM, Clint Checketts <checketts@gmail.com
> >wrote:
>
> > Why not just just use wicket- as the prefix? The groupId shows that it is
> > org.wicketstuff.
> >
> > -Clint
> >
> > On Tue, Jun 28, 2011 at 4:27 PM, Bruno Borges <bruno.borges@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.borges@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.ocleirigh@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<
> > > TorIverW@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-unsubscribe@wicket.apache.org
> > > >>> For additional commands, e-mail: users-help@wicket.apache.org
> > > >>>
> > > >>>
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > >> For additional commands, e-mail: users-help@wicket.apache.org
> > > >>
> > > >>
> > > >
> > >
> >
>
Re: WicketStuff artifacts naming strategy
Posted by Bruno Borges <br...@gmail.com>.
because the JAR file does not come with the groupId, and some projects have
some very short names, like dojo, or yui.
If I look at a JAR file named "wicket-dojo-1.5-RC5.1.jar", is that from
wicketstuff or wicket ?
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Tue, Jun 28, 2011 at 6:39 PM, Clint Checketts <ch...@gmail.com>wrote:
> Why not just just use wicket- as the prefix? The groupId shows that it is
> org.wicketstuff.
>
> -Clint
>
> On Tue, Jun 28, 2011 at 4:27 PM, Bruno Borges <bruno.borges@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.borges@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.ocleirigh@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<
> > TorIverW@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-unsubscribe@wicket.apache.org
> > >>> For additional commands, e-mail: users-help@wicket.apache.org
> > >>>
> > >>>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > >> For additional commands, e-mail: users-help@wicket.apache.org
> > >>
> > >>
> > >
> >
>
Re: WicketStuff artifacts naming strategy
Posted by Clint Checketts <ch...@gmail.com>.
Why not just just use wicket- as the prefix? The groupId shows that it is
org.wicketstuff.
-Clint
On Tue, Jun 28, 2011 at 4:27 PM, Bruno Borges <br...@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.borges@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.ocleirigh@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<
> TorIverW@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-unsubscribe@wicket.apache.org
> >>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
>
Re: WicketStuff artifacts naming strategy
Posted by Bruno Borges <br...@gmail.com>.
But is it necessary to rename the artifactId to OSGify a module?
I'm just asking. Not that I'm going back to rename all again. :-)
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Thu, Jun 30, 2011 at 12:20 PM, Martin Grigorov <mg...@apache.org>wrote:
> Harald said that "org.wicketstuff." convention is used by OSGi-ed projects.
>
> On Thu, Jun 30, 2011 at 6:09 PM, Bruno Borges <br...@gmail.com>
> wrote:
> > Yes, me neither. That's why I asked.
> >
> > The preffix I'm using is "wicketstuff-", but Harald mentioned
> > "org.wicketstuff."
> >
> > I don't want to use that, it's too verbose.
> >
> >
> > *Bruno Borges*
> > www.brunoborges.com.br
> > +55 21 76727099
> >
> >
> >
> > On Thu, Jun 30, 2011 at 12:06 PM, James Carman
> > <ja...@carmanconsulting.com>wrote:
> >
> >> I haven't seen that syntax before of having the group id in the
> >> artifact id, at least not with the longer group ids (reverse domain).
> >>
> >> On Thu, Jun 30, 2011 at 11:02 AM, Bruno Borges <br...@gmail.com>
> >> wrote:
> >> > The preffix is 'wicketstuff-', not 'org.wicketstuff.'
> >> >
> >> > Is this ok?
> >> >
> >> > *Bruno Borges*
> >> > www.brunoborges.com.br
> >> > +55 21 76727099
> >> >
> >> >
> >> >
> >> > On Wed, Jun 29, 2011 at 4:01 AM, Harald Wellmann <
> harald.wellmann@gmx.de
> >> >wrote:
> >> >
> >> >> For Maven OSGi bundle artifacts, there is a quasi-convention to have
> >> >> artifactId = Bundle-Symbolic name, so you would have
> >> >>
> >> >> groupId: org.wicketstuff
> >> >> artifactId: org.wicketstuff.foo.bar
> >> >> version: 1.5
> >> >>
> >> >> Bundle-Symbolic-Name: org.wicketstuff.foo.bar
> >> >> JAR name: org.wicketstuff.foo.bar-1.5.**jar
> >> >>
> >> >> Apache Servicemix and Apache Aries use this convention, while Apache
> >> >> Commons sticks with the old names.
> >> >>
> >> >> Having this naming scheme and the one Bruno suggested in parallel
> would
> >> >> help to distinguish OSGi bundles from plain old JARs.
> >> >>
> >> >> Then again, that would mean you'd have to rename artifacts, once you
> >> osgify
> >> >> them.
> >> >>
> >> >> Regards,
> >> >> Harald
> >> >>
> >> >>
> >> >>
> >> >>
> >>
> ------------------------------**------------------------------**---------
> >> >> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
> >> users-unsubscribe@wicket.apache.org>
> >> >> For additional commands, e-mail: users-help@wicket.apache.org
> >> >>
> >> >>
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: WicketStuff artifacts naming strategy
Posted by Martin Grigorov <mg...@apache.org>.
Harald said that "org.wicketstuff." convention is used by OSGi-ed projects.
On Thu, Jun 30, 2011 at 6:09 PM, Bruno Borges <br...@gmail.com> wrote:
> Yes, me neither. That's why I asked.
>
> The preffix I'm using is "wicketstuff-", but Harald mentioned
> "org.wicketstuff."
>
> I don't want to use that, it's too verbose.
>
>
> *Bruno Borges*
> www.brunoborges.com.br
> +55 21 76727099
>
>
>
> On Thu, Jun 30, 2011 at 12:06 PM, James Carman
> <ja...@carmanconsulting.com>wrote:
>
>> I haven't seen that syntax before of having the group id in the
>> artifact id, at least not with the longer group ids (reverse domain).
>>
>> On Thu, Jun 30, 2011 at 11:02 AM, Bruno Borges <br...@gmail.com>
>> wrote:
>> > The preffix is 'wicketstuff-', not 'org.wicketstuff.'
>> >
>> > Is this ok?
>> >
>> > *Bruno Borges*
>> > www.brunoborges.com.br
>> > +55 21 76727099
>> >
>> >
>> >
>> > On Wed, Jun 29, 2011 at 4:01 AM, Harald Wellmann <harald.wellmann@gmx.de
>> >wrote:
>> >
>> >> For Maven OSGi bundle artifacts, there is a quasi-convention to have
>> >> artifactId = Bundle-Symbolic name, so you would have
>> >>
>> >> groupId: org.wicketstuff
>> >> artifactId: org.wicketstuff.foo.bar
>> >> version: 1.5
>> >>
>> >> Bundle-Symbolic-Name: org.wicketstuff.foo.bar
>> >> JAR name: org.wicketstuff.foo.bar-1.5.**jar
>> >>
>> >> Apache Servicemix and Apache Aries use this convention, while Apache
>> >> Commons sticks with the old names.
>> >>
>> >> Having this naming scheme and the one Bruno suggested in parallel would
>> >> help to distinguish OSGi bundles from plain old JARs.
>> >>
>> >> Then again, that would mean you'd have to rename artifacts, once you
>> osgify
>> >> them.
>> >>
>> >> Regards,
>> >> Harald
>> >>
>> >>
>> >>
>> >>
>> ------------------------------**------------------------------**---------
>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
>> users-unsubscribe@wicket.apache.org>
>> >> For additional commands, e-mail: users-help@wicket.apache.org
>> >>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff artifacts naming strategy
Posted by Bruno Borges <br...@gmail.com>.
Correct, I don't think it would be nice to rename artifacts for 1.4 branch.
There's just too many people relying on old names.
What do others think?
On 2011 7 6 11:29, "Martin Grigorov" <mg...@apache.org> wrote:
> The improvement in the naming was done only for 1.5 branch of
> wicketstuff/core and will be available with the next release (RC6 ?!).
>
> On Wed, Jul 6, 2011 at 4:13 PM, gilbertoca <gi...@gmail.com> wrote:
>> Hi, Bruno!
>>
>> I'm with the same problem:
>>
>>
>>> gilberto@SUGEP-DMASI:~/dev/netbeans-config/snp$ ll
>>> target/snp-1.1-SNAPSHOT/WEB-INF/lib/|grep jasper
>>> -rw-r--r-- 1 gilberto users 23955 2011-07-04 11:31
>>> jasperreports-1.4.17.2.jar
>>> -rw-r--r-- 1 gilberto users 2525996 2011-07-04 11:12
>>> jasperreports-3.5.3.jar
>>>
>>>
>>
>> Other thing, the jasperreports(wicketstuff) is tied to jasperreports
3.5.3
>> as you see above - I can't use another version, even using the maven
>> exclusion tag.
>>
>> We are using:
>> wicket version 1.4.17
>> wicketstuff version 1.4.17.2
>>
>> Where can I get this artefact (wicketstuff-jasperreports) for 1.4
version?
>>
>> Regards,
>>
>> Gilberto Caetano de Andrade
>> Analista de Sistemas/DBA
>> www.secad.to.gov.br
>> blog.gilbertoca.com
>>
>>
>>
>> Bruno Borges wrote:
>>>
>>> Hell, it has been merged.
>>>
>>> pull request #42 merged to master.
>>>
>>> I've updated the wiki already asking for new JAR modules to follow this
>>> naming strategy.
>>>
>>> Thank you all for the support.
>>>
>>> *Bruno Borges*
>>> www.brunoborges.com.br
>>> +55 21 76727099
>>>
>>>
>>>
>>> On Thu, Jun 30, 2011 at 3:14 PM, Bruno Borges
>>> <bruno.borges@gmail.com>wrote:
>>>
>>>> The Pull request #42 is ready to be merged.
>>>>
>>>> Please review and vote.
>>>>
>>>> https://github.com/wicketstuff/core/pull/42
>>>>
>>>> There's one modification I made that is not related to the repository.
It
>>>> is here:
>>>> https://github.com/wicketstuff/core/pull/42/files#r55594
>>>>
>>>>
>>>>
>>>> *Bruno Borges*
>>>> www.brunoborges.com.br
>>>> +55 21 76727099
>>>>
>>>>
>>>>
>>>> On Thu, Jun 30, 2011 at 2:22 PM, Clint Checketts
>>>> <checketts@gmail.com>wrote:
>>>>
>>>>> I seem to recall the Maven guys recommending against periods in
>>>>> artifactIds.
>>>>> Can't find the link for the info though... maybe it was just soething
>>>>> they
>>>>> mentioned in the class.
>>>>>
>>>>> The purpose was to reduce confusion between artifactIds and groupIds.
>>>>>
>>>>> -Clint
>>>>>
>>>>> On Thu, Jun 30, 2011 at 11:14 AM, Igor Vaynberg
>>>>> <igor.vaynberg@gmail.com
>>> >> >wrote:
>>>>>
>>>>> > i think the groupid/artifactid do matter because some containers
have
>>>>> > bundle deployers that pull things from the maven repo...i think
>>>>> >
>>>>> > -igor
>>>>> >
>>>>> > On Thu, Jun 30, 2011 at 8:38 AM, Martin Grigorov
>>>>> <mgrigorov@apache.org>
>>>>> > wrote:
>>>>> > > The Maven artifact id is not important.
>>>>> > > The name of the produced .jar is what matters, right ?
>>>>> > >
>>>>> > > Harald just said that there is a convention in OSGi world to work
>>>>> with
>>>>> > > such named .jars (com.acme.blah)
>>>>> > >
>>>>> > > On Thu, Jun 30, 2011 at 6:31 PM, James Carman
>>>>> > > <jcarman@carmanconsulting.com> wrote:
>>>>> > >> And repetitive
>>>>> > >>
>>>>> > >> Sent from my Android device. Please excuse typos and brevity.
>>>>> > >> On Jun 30, 2011 11:12 AM, "Bruno Borges"
>>>>> <bruno.borges@gmail.com>
>>>>> > wrote:
>>>>> > >>> Yes, me neither. That's why I asked.
>>>>> > >>>
>>>>> > >>> The preffix I'm using is "wicketstuff-", but Harald mentioned
>>>>> > >>> "org.wicketstuff."
>>>>> > >>>
>>>>> > >>> I don't want to use that, it's too verbose.
>>>>> > >>>
>>>>> > >>>
>>>>> > >>> *Bruno Borges*
>>>>> > >>> www.brunoborges.com.br
>>>>> > >>> +55 21 76727099
>>>>> > >>>
>>>>> > >>>
>>>>> > >>>
>>>>> > >>> On Thu, Jun 30, 2011 at 12:06 PM, James Carman
>>>>> > >>> <james@carmanconsulting.com>wrote:
>>>>> > >>>
>>>>> > >>>> I haven't seen that syntax before of having the group id in the
>>>>> > >>>> artifact id, at least not with the longer group ids (reverse
>>>>> domain).
>>>>> > >>>>
>>>>> > >>>> On Thu, Jun 30, 2011 at 11:02 AM, Bruno Borges <
>>>>> > bruno.borges@gmail.com>
>>>>> > >>>> wrote:
>>>>> > >>>> > The preffix is 'wicketstuff-', not 'org.wicketstuff.'
>>>>> > >>>> >
>>>>> > >>>> > Is this ok?
>>>>> > >>>> >
>>>>> > >>>> > *Bruno Borges*
>>>>> > >>>> > www.brunoborges.com.br
>>>>> > >>>> > +55 21 76727099
>>>>> > >>>> >
>>>>> > >>>> >
>>>>> > >>>> >
>>>>> > >>>> > On Wed, Jun 29, 2011 at 4:01 AM, Harald Wellmann <
>>>>> > >> harald.wellmann@gmx.de
>>>>> > >>>> >wrote:
>>>>> > >>>> >
>>>>> > >>>> >> For Maven OSGi bundle artifacts, there is a quasi-convention
>>>>> to
>>>>> > have
>>>>> > >>>> >> artifactId = Bundle-Symbolic name, so you would have
>>>>> > >>>> >>
>>>>> > >>>> >> groupId: org.wicketstuff
>>>>> > >>>> >> artifactId: org.wicketstuff.foo.bar
>>>>> > >>>> >> version: 1.5
>>>>> > >>>> >>
>>>>> > >>>> >> Bundle-Symbolic-Name: org.wicketstuff.foo.bar
>>>>> > >>>> >> JAR name: org.wicketstuff.foo.bar-1.5.**jar
>>>>> > >>>> >>
>>>>> > >>>> >> Apache Servicemix and Apache Aries use this convention,
while
>>>>> > Apache
>>>>> > >>>> >> Commons sticks with the old names.
>>>>> > >>>> >>
>>>>> > >>>> >> Having this naming scheme and the one Bruno suggested in
>>>>> parallel
>>>>> > >> would
>>>>> > >>>> >> help to distinguish OSGi bundles from plain old JARs.
>>>>> > >>>> >>
>>>>> > >>>> >> Then again, that would mean you'd have to rename artifacts,
>>>>> once
>>>>> > you
>>>>> > >>>> osgify
>>>>> > >>>> >> them.
>>>>> > >>>> >>
>>>>> > >>>> >> Regards,
>>>>> > >>>> >> Harald
>>>>> > >>>> >>
>>>>> > >>>> >>
>>>>> > >>>> >>
>>>>> > >>>> >>
>>>>> > >>>>
>>>>> >
>>>>>
------------------------------**------------------------------**---------
>>>>> > >>>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.**
apache.org<
>>>>> > >>>> users-unsubscribe@wicket.apache.org>
>>>>> > >>>> >> For additional commands, e-mail:
users-help@wicket.apache.org
>>>>> > >>>> >>
>>>>> > >>>> >>
>>>>> > >>>> >
>>>>> > >>>>
>>>>> > >>>>
>>>>> ---------------------------------------------------------------------
>>>>> > >>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> > >>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>> > >>>>
>>>>> > >>>>
>>>>> > >>
>>>>> > >
>>>>> > >
>>>>> > >
>>>>> > > --
>>>>> > > Martin Grigorov
>>>>> > > jWeekend
>>>>> > > Training, Consulting, Development
>>>>> > > http://jWeekend.com
>>>>> > >
>>>>> > >
>>>>> ---------------------------------------------------------------------
>>>>> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> > > For additional commands, e-mail: users-help@wicket.apache.org
>>>>> > >
>>>>> > >
>>>>> >
>>>>> >
---------------------------------------------------------------------
>>>>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> > For additional commands, e-mail: users-help@wicket.apache.org
>>>>> >
>>>>> >
>>>>>
>>>>
>>>>
>>>
>>
>>
>> --
>> View this message in context:
http://apache-wicket.1842946.n4.nabble.com/WicketStuff-artifacts-naming-strategy-tp3404104p3648925.html
>> Sent from the Users forum mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
Re: WicketStuff artifacts naming strategy
Posted by Martin Grigorov <mg...@apache.org>.
The improvement in the naming was done only for 1.5 branch of
wicketstuff/core and will be available with the next release (RC6 ?!).
On Wed, Jul 6, 2011 at 4:13 PM, gilbertoca <gi...@gmail.com> wrote:
> Hi, Bruno!
>
> I'm with the same problem:
>
>
>> gilberto@SUGEP-DMASI:~/dev/netbeans-config/snp$ ll
>> target/snp-1.1-SNAPSHOT/WEB-INF/lib/|grep jasper
>> -rw-r--r-- 1 gilberto users 23955 2011-07-04 11:31
>> jasperreports-1.4.17.2.jar
>> -rw-r--r-- 1 gilberto users 2525996 2011-07-04 11:12
>> jasperreports-3.5.3.jar
>>
>>
>
> Other thing, the jasperreports(wicketstuff) is tied to jasperreports 3.5.3
> as you see above - I can't use another version, even using the maven
> exclusion tag.
>
> We are using:
> wicket version 1.4.17
> wicketstuff version 1.4.17.2
>
> Where can I get this artefact (wicketstuff-jasperreports) for 1.4 version?
>
> Regards,
>
> Gilberto Caetano de Andrade
> Analista de Sistemas/DBA
> www.secad.to.gov.br
> blog.gilbertoca.com
>
>
>
> Bruno Borges wrote:
>>
>> Hell, it has been merged.
>>
>> pull request #42 merged to master.
>>
>> I've updated the wiki already asking for new JAR modules to follow this
>> naming strategy.
>>
>> Thank you all for the support.
>>
>> *Bruno Borges*
>> www.brunoborges.com.br
>> +55 21 76727099
>>
>>
>>
>> On Thu, Jun 30, 2011 at 3:14 PM, Bruno Borges
>> <bruno.borges@gmail.com>wrote:
>>
>>> The Pull request #42 is ready to be merged.
>>>
>>> Please review and vote.
>>>
>>> https://github.com/wicketstuff/core/pull/42
>>>
>>> There's one modification I made that is not related to the repository. It
>>> is here:
>>> https://github.com/wicketstuff/core/pull/42/files#r55594
>>>
>>>
>>>
>>> *Bruno Borges*
>>> www.brunoborges.com.br
>>> +55 21 76727099
>>>
>>>
>>>
>>> On Thu, Jun 30, 2011 at 2:22 PM, Clint Checketts
>>> <checketts@gmail.com>wrote:
>>>
>>>> I seem to recall the Maven guys recommending against periods in
>>>> artifactIds.
>>>> Can't find the link for the info though... maybe it was just soething
>>>> they
>>>> mentioned in the class.
>>>>
>>>> The purpose was to reduce confusion between artifactIds and groupIds.
>>>>
>>>> -Clint
>>>>
>>>> On Thu, Jun 30, 2011 at 11:14 AM, Igor Vaynberg
>>>> <igor.vaynberg@gmail.com
>> >> >wrote:
>>>>
>>>> > i think the groupid/artifactid do matter because some containers have
>>>> > bundle deployers that pull things from the maven repo...i think
>>>> >
>>>> > -igor
>>>> >
>>>> > On Thu, Jun 30, 2011 at 8:38 AM, Martin Grigorov
>>>> <mgrigorov@apache.org>
>>>> > wrote:
>>>> > > The Maven artifact id is not important.
>>>> > > The name of the produced .jar is what matters, right ?
>>>> > >
>>>> > > Harald just said that there is a convention in OSGi world to work
>>>> with
>>>> > > such named .jars (com.acme.blah)
>>>> > >
>>>> > > On Thu, Jun 30, 2011 at 6:31 PM, James Carman
>>>> > > <jcarman@carmanconsulting.com> wrote:
>>>> > >> And repetitive
>>>> > >>
>>>> > >> Sent from my Android device. Please excuse typos and brevity.
>>>> > >> On Jun 30, 2011 11:12 AM, "Bruno Borges"
>>>> <bruno.borges@gmail.com>
>>>> > wrote:
>>>> > >>> Yes, me neither. That's why I asked.
>>>> > >>>
>>>> > >>> The preffix I'm using is "wicketstuff-", but Harald mentioned
>>>> > >>> "org.wicketstuff."
>>>> > >>>
>>>> > >>> I don't want to use that, it's too verbose.
>>>> > >>>
>>>> > >>>
>>>> > >>> *Bruno Borges*
>>>> > >>> www.brunoborges.com.br
>>>> > >>> +55 21 76727099
>>>> > >>>
>>>> > >>>
>>>> > >>>
>>>> > >>> On Thu, Jun 30, 2011 at 12:06 PM, James Carman
>>>> > >>> <james@carmanconsulting.com>wrote:
>>>> > >>>
>>>> > >>>> I haven't seen that syntax before of having the group id in the
>>>> > >>>> artifact id, at least not with the longer group ids (reverse
>>>> domain).
>>>> > >>>>
>>>> > >>>> On Thu, Jun 30, 2011 at 11:02 AM, Bruno Borges <
>>>> > bruno.borges@gmail.com>
>>>> > >>>> wrote:
>>>> > >>>> > The preffix is 'wicketstuff-', not 'org.wicketstuff.'
>>>> > >>>> >
>>>> > >>>> > Is this ok?
>>>> > >>>> >
>>>> > >>>> > *Bruno Borges*
>>>> > >>>> > www.brunoborges.com.br
>>>> > >>>> > +55 21 76727099
>>>> > >>>> >
>>>> > >>>> >
>>>> > >>>> >
>>>> > >>>> > On Wed, Jun 29, 2011 at 4:01 AM, Harald Wellmann <
>>>> > >> harald.wellmann@gmx.de
>>>> > >>>> >wrote:
>>>> > >>>> >
>>>> > >>>> >> For Maven OSGi bundle artifacts, there is a quasi-convention
>>>> to
>>>> > have
>>>> > >>>> >> artifactId = Bundle-Symbolic name, so you would have
>>>> > >>>> >>
>>>> > >>>> >> groupId: org.wicketstuff
>>>> > >>>> >> artifactId: org.wicketstuff.foo.bar
>>>> > >>>> >> version: 1.5
>>>> > >>>> >>
>>>> > >>>> >> Bundle-Symbolic-Name: org.wicketstuff.foo.bar
>>>> > >>>> >> JAR name: org.wicketstuff.foo.bar-1.5.**jar
>>>> > >>>> >>
>>>> > >>>> >> Apache Servicemix and Apache Aries use this convention, while
>>>> > Apache
>>>> > >>>> >> Commons sticks with the old names.
>>>> > >>>> >>
>>>> > >>>> >> Having this naming scheme and the one Bruno suggested in
>>>> parallel
>>>> > >> would
>>>> > >>>> >> help to distinguish OSGi bundles from plain old JARs.
>>>> > >>>> >>
>>>> > >>>> >> Then again, that would mean you'd have to rename artifacts,
>>>> once
>>>> > you
>>>> > >>>> osgify
>>>> > >>>> >> them.
>>>> > >>>> >>
>>>> > >>>> >> Regards,
>>>> > >>>> >> Harald
>>>> > >>>> >>
>>>> > >>>> >>
>>>> > >>>> >>
>>>> > >>>> >>
>>>> > >>>>
>>>> >
>>>> ------------------------------**------------------------------**---------
>>>> > >>>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
>>>> > >>>> users-unsubscribe@wicket.apache.org>
>>>> > >>>> >> For additional commands, e-mail: users-help@wicket.apache.org
>>>> > >>>> >>
>>>> > >>>> >>
>>>> > >>>> >
>>>> > >>>>
>>>> > >>>>
>>>> ---------------------------------------------------------------------
>>>> > >>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> > >>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>> > >>>>
>>>> > >>>>
>>>> > >>
>>>> > >
>>>> > >
>>>> > >
>>>> > > --
>>>> > > Martin Grigorov
>>>> > > jWeekend
>>>> > > Training, Consulting, Development
>>>> > > http://jWeekend.com
>>>> > >
>>>> > >
>>>> ---------------------------------------------------------------------
>>>> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> > > For additional commands, e-mail: users-help@wicket.apache.org
>>>> > >
>>>> > >
>>>> >
>>>> > ---------------------------------------------------------------------
>>>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> > For additional commands, e-mail: users-help@wicket.apache.org
>>>> >
>>>> >
>>>>
>>>
>>>
>>
>
>
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/WicketStuff-artifacts-naming-strategy-tp3404104p3648925.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff artifacts naming strategy
Posted by gilbertoca <gi...@gmail.com>.
Hi, Bruno!
I'm with the same problem:
> gilberto@SUGEP-DMASI:~/dev/netbeans-config/snp$ ll
> target/snp-1.1-SNAPSHOT/WEB-INF/lib/|grep jasper
> -rw-r--r-- 1 gilberto users 23955 2011-07-04 11:31
> jasperreports-1.4.17.2.jar
> -rw-r--r-- 1 gilberto users 2525996 2011-07-04 11:12
> jasperreports-3.5.3.jar
>
>
Other thing, the jasperreports(wicketstuff) is tied to jasperreports 3.5.3
as you see above - I can't use another version, even using the maven
exclusion tag.
We are using:
wicket version 1.4.17
wicketstuff version 1.4.17.2
Where can I get this artefact (wicketstuff-jasperreports) for 1.4 version?
Regards,
Gilberto Caetano de Andrade
Analista de Sistemas/DBA
www.secad.to.gov.br
blog.gilbertoca.com
Bruno Borges wrote:
>
> Hell, it has been merged.
>
> pull request #42 merged to master.
>
> I've updated the wiki already asking for new JAR modules to follow this
> naming strategy.
>
> Thank you all for the support.
>
> *Bruno Borges*
> www.brunoborges.com.br
> +55 21 76727099
>
>
>
> On Thu, Jun 30, 2011 at 3:14 PM, Bruno Borges
> <bruno.borges@gmail.com>wrote:
>
>> The Pull request #42 is ready to be merged.
>>
>> Please review and vote.
>>
>> https://github.com/wicketstuff/core/pull/42
>>
>> There's one modification I made that is not related to the repository. It
>> is here:
>> https://github.com/wicketstuff/core/pull/42/files#r55594
>>
>>
>>
>> *Bruno Borges*
>> www.brunoborges.com.br
>> +55 21 76727099
>>
>>
>>
>> On Thu, Jun 30, 2011 at 2:22 PM, Clint Checketts
>> <checketts@gmail.com>wrote:
>>
>>> I seem to recall the Maven guys recommending against periods in
>>> artifactIds.
>>> Can't find the link for the info though... maybe it was just soething
>>> they
>>> mentioned in the class.
>>>
>>> The purpose was to reduce confusion between artifactIds and groupIds.
>>>
>>> -Clint
>>>
>>> On Thu, Jun 30, 2011 at 11:14 AM, Igor Vaynberg
>>> <igor.vaynberg@gmail.com
> >> >wrote:
>>>
>>> > i think the groupid/artifactid do matter because some containers have
>>> > bundle deployers that pull things from the maven repo...i think
>>> >
>>> > -igor
>>> >
>>> > On Thu, Jun 30, 2011 at 8:38 AM, Martin Grigorov
>>> <mgrigorov@apache.org>
>>> > wrote:
>>> > > The Maven artifact id is not important.
>>> > > The name of the produced .jar is what matters, right ?
>>> > >
>>> > > Harald just said that there is a convention in OSGi world to work
>>> with
>>> > > such named .jars (com.acme.blah)
>>> > >
>>> > > On Thu, Jun 30, 2011 at 6:31 PM, James Carman
>>> > > <jcarman@carmanconsulting.com> wrote:
>>> > >> And repetitive
>>> > >>
>>> > >> Sent from my Android device. Please excuse typos and brevity.
>>> > >> On Jun 30, 2011 11:12 AM, "Bruno Borges"
>>> <bruno.borges@gmail.com>
>>> > wrote:
>>> > >>> Yes, me neither. That's why I asked.
>>> > >>>
>>> > >>> The preffix I'm using is "wicketstuff-", but Harald mentioned
>>> > >>> "org.wicketstuff."
>>> > >>>
>>> > >>> I don't want to use that, it's too verbose.
>>> > >>>
>>> > >>>
>>> > >>> *Bruno Borges*
>>> > >>> www.brunoborges.com.br
>>> > >>> +55 21 76727099
>>> > >>>
>>> > >>>
>>> > >>>
>>> > >>> On Thu, Jun 30, 2011 at 12:06 PM, James Carman
>>> > >>> <james@carmanconsulting.com>wrote:
>>> > >>>
>>> > >>>> I haven't seen that syntax before of having the group id in the
>>> > >>>> artifact id, at least not with the longer group ids (reverse
>>> domain).
>>> > >>>>
>>> > >>>> On Thu, Jun 30, 2011 at 11:02 AM, Bruno Borges <
>>> > bruno.borges@gmail.com>
>>> > >>>> wrote:
>>> > >>>> > The preffix is 'wicketstuff-', not 'org.wicketstuff.'
>>> > >>>> >
>>> > >>>> > Is this ok?
>>> > >>>> >
>>> > >>>> > *Bruno Borges*
>>> > >>>> > www.brunoborges.com.br
>>> > >>>> > +55 21 76727099
>>> > >>>> >
>>> > >>>> >
>>> > >>>> >
>>> > >>>> > On Wed, Jun 29, 2011 at 4:01 AM, Harald Wellmann <
>>> > >> harald.wellmann@gmx.de
>>> > >>>> >wrote:
>>> > >>>> >
>>> > >>>> >> For Maven OSGi bundle artifacts, there is a quasi-convention
>>> to
>>> > have
>>> > >>>> >> artifactId = Bundle-Symbolic name, so you would have
>>> > >>>> >>
>>> > >>>> >> groupId: org.wicketstuff
>>> > >>>> >> artifactId: org.wicketstuff.foo.bar
>>> > >>>> >> version: 1.5
>>> > >>>> >>
>>> > >>>> >> Bundle-Symbolic-Name: org.wicketstuff.foo.bar
>>> > >>>> >> JAR name: org.wicketstuff.foo.bar-1.5.**jar
>>> > >>>> >>
>>> > >>>> >> Apache Servicemix and Apache Aries use this convention, while
>>> > Apache
>>> > >>>> >> Commons sticks with the old names.
>>> > >>>> >>
>>> > >>>> >> Having this naming scheme and the one Bruno suggested in
>>> parallel
>>> > >> would
>>> > >>>> >> help to distinguish OSGi bundles from plain old JARs.
>>> > >>>> >>
>>> > >>>> >> Then again, that would mean you'd have to rename artifacts,
>>> once
>>> > you
>>> > >>>> osgify
>>> > >>>> >> them.
>>> > >>>> >>
>>> > >>>> >> Regards,
>>> > >>>> >> Harald
>>> > >>>> >>
>>> > >>>> >>
>>> > >>>> >>
>>> > >>>> >>
>>> > >>>>
>>> >
>>> ------------------------------**------------------------------**---------
>>> > >>>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
>>> > >>>> users-unsubscribe@wicket.apache.org>
>>> > >>>> >> For additional commands, e-mail: users-help@wicket.apache.org
>>> > >>>> >>
>>> > >>>> >>
>>> > >>>> >
>>> > >>>>
>>> > >>>>
>>> ---------------------------------------------------------------------
>>> > >>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> > >>>> For additional commands, e-mail: users-help@wicket.apache.org
>>> > >>>>
>>> > >>>>
>>> > >>
>>> > >
>>> > >
>>> > >
>>> > > --
>>> > > Martin Grigorov
>>> > > jWeekend
>>> > > Training, Consulting, Development
>>> > > http://jWeekend.com
>>> > >
>>> > >
>>> ---------------------------------------------------------------------
>>> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> > > For additional commands, e-mail: users-help@wicket.apache.org
>>> > >
>>> > >
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> > For additional commands, e-mail: users-help@wicket.apache.org
>>> >
>>> >
>>>
>>
>>
>
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/WicketStuff-artifacts-naming-strategy-tp3404104p3648925.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff artifacts naming strategy
Posted by Bruno Borges <br...@gmail.com>.
Hell, it has been merged.
pull request #42 merged to master.
I've updated the wiki already asking for new JAR modules to follow this
naming strategy.
Thank you all for the support.
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Thu, Jun 30, 2011 at 3:14 PM, Bruno Borges <br...@gmail.com>wrote:
> The Pull request #42 is ready to be merged.
>
> Please review and vote.
>
> https://github.com/wicketstuff/core/pull/42
>
> There's one modification I made that is not related to the repository. It
> is here:
> https://github.com/wicketstuff/core/pull/42/files#r55594
>
>
>
> *Bruno Borges*
> www.brunoborges.com.br
> +55 21 76727099
>
>
>
> On Thu, Jun 30, 2011 at 2:22 PM, Clint Checketts <ch...@gmail.com>wrote:
>
>> I seem to recall the Maven guys recommending against periods in
>> artifactIds.
>> Can't find the link for the info though... maybe it was just soething they
>> mentioned in the class.
>>
>> The purpose was to reduce confusion between artifactIds and groupIds.
>>
>> -Clint
>>
>> On Thu, Jun 30, 2011 at 11:14 AM, Igor Vaynberg <igor.vaynberg@gmail.com
>> >wrote:
>>
>> > i think the groupid/artifactid do matter because some containers have
>> > bundle deployers that pull things from the maven repo...i think
>> >
>> > -igor
>> >
>> > On Thu, Jun 30, 2011 at 8:38 AM, Martin Grigorov <mg...@apache.org>
>> > wrote:
>> > > The Maven artifact id is not important.
>> > > The name of the produced .jar is what matters, right ?
>> > >
>> > > Harald just said that there is a convention in OSGi world to work with
>> > > such named .jars (com.acme.blah)
>> > >
>> > > On Thu, Jun 30, 2011 at 6:31 PM, James Carman
>> > > <jc...@carmanconsulting.com> wrote:
>> > >> And repetitive
>> > >>
>> > >> Sent from my Android device. Please excuse typos and brevity.
>> > >> On Jun 30, 2011 11:12 AM, "Bruno Borges" <br...@gmail.com>
>> > wrote:
>> > >>> Yes, me neither. That's why I asked.
>> > >>>
>> > >>> The preffix I'm using is "wicketstuff-", but Harald mentioned
>> > >>> "org.wicketstuff."
>> > >>>
>> > >>> I don't want to use that, it's too verbose.
>> > >>>
>> > >>>
>> > >>> *Bruno Borges*
>> > >>> www.brunoborges.com.br
>> > >>> +55 21 76727099
>> > >>>
>> > >>>
>> > >>>
>> > >>> On Thu, Jun 30, 2011 at 12:06 PM, James Carman
>> > >>> <ja...@carmanconsulting.com>wrote:
>> > >>>
>> > >>>> I haven't seen that syntax before of having the group id in the
>> > >>>> artifact id, at least not with the longer group ids (reverse
>> domain).
>> > >>>>
>> > >>>> On Thu, Jun 30, 2011 at 11:02 AM, Bruno Borges <
>> > bruno.borges@gmail.com>
>> > >>>> wrote:
>> > >>>> > The preffix is 'wicketstuff-', not 'org.wicketstuff.'
>> > >>>> >
>> > >>>> > Is this ok?
>> > >>>> >
>> > >>>> > *Bruno Borges*
>> > >>>> > www.brunoborges.com.br
>> > >>>> > +55 21 76727099
>> > >>>> >
>> > >>>> >
>> > >>>> >
>> > >>>> > On Wed, Jun 29, 2011 at 4:01 AM, Harald Wellmann <
>> > >> harald.wellmann@gmx.de
>> > >>>> >wrote:
>> > >>>> >
>> > >>>> >> For Maven OSGi bundle artifacts, there is a quasi-convention to
>> > have
>> > >>>> >> artifactId = Bundle-Symbolic name, so you would have
>> > >>>> >>
>> > >>>> >> groupId: org.wicketstuff
>> > >>>> >> artifactId: org.wicketstuff.foo.bar
>> > >>>> >> version: 1.5
>> > >>>> >>
>> > >>>> >> Bundle-Symbolic-Name: org.wicketstuff.foo.bar
>> > >>>> >> JAR name: org.wicketstuff.foo.bar-1.5.**jar
>> > >>>> >>
>> > >>>> >> Apache Servicemix and Apache Aries use this convention, while
>> > Apache
>> > >>>> >> Commons sticks with the old names.
>> > >>>> >>
>> > >>>> >> Having this naming scheme and the one Bruno suggested in
>> parallel
>> > >> would
>> > >>>> >> help to distinguish OSGi bundles from plain old JARs.
>> > >>>> >>
>> > >>>> >> Then again, that would mean you'd have to rename artifacts, once
>> > you
>> > >>>> osgify
>> > >>>> >> them.
>> > >>>> >>
>> > >>>> >> Regards,
>> > >>>> >> Harald
>> > >>>> >>
>> > >>>> >>
>> > >>>> >>
>> > >>>> >>
>> > >>>>
>> >
>> ------------------------------**------------------------------**---------
>> > >>>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
>> > >>>> users-unsubscribe@wicket.apache.org>
>> > >>>> >> For additional commands, e-mail: users-help@wicket.apache.org
>> > >>>> >>
>> > >>>> >>
>> > >>>> >
>> > >>>>
>> > >>>>
>> ---------------------------------------------------------------------
>> > >>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> > >>>> For additional commands, e-mail: users-help@wicket.apache.org
>> > >>>>
>> > >>>>
>> > >>
>> > >
>> > >
>> > >
>> > > --
>> > > Martin Grigorov
>> > > jWeekend
>> > > Training, Consulting, Development
>> > > http://jWeekend.com
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> > > For additional commands, e-mail: users-help@wicket.apache.org
>> > >
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> > For additional commands, e-mail: users-help@wicket.apache.org
>> >
>> >
>>
>
>
Re: WicketStuff artifacts naming strategy
Posted by Bruno Borges <br...@gmail.com>.
The Pull request #42 is ready to be merged.
Please review and vote.
https://github.com/wicketstuff/core/pull/42
There's one modification I made that is not related to the repository. It is
here:
https://github.com/wicketstuff/core/pull/42/files#r55594
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Thu, Jun 30, 2011 at 2:22 PM, Clint Checketts <ch...@gmail.com>wrote:
> I seem to recall the Maven guys recommending against periods in
> artifactIds.
> Can't find the link for the info though... maybe it was just soething they
> mentioned in the class.
>
> The purpose was to reduce confusion between artifactIds and groupIds.
>
> -Clint
>
> On Thu, Jun 30, 2011 at 11:14 AM, Igor Vaynberg <igor.vaynberg@gmail.com
> >wrote:
>
> > i think the groupid/artifactid do matter because some containers have
> > bundle deployers that pull things from the maven repo...i think
> >
> > -igor
> >
> > On Thu, Jun 30, 2011 at 8:38 AM, Martin Grigorov <mg...@apache.org>
> > wrote:
> > > The Maven artifact id is not important.
> > > The name of the produced .jar is what matters, right ?
> > >
> > > Harald just said that there is a convention in OSGi world to work with
> > > such named .jars (com.acme.blah)
> > >
> > > On Thu, Jun 30, 2011 at 6:31 PM, James Carman
> > > <jc...@carmanconsulting.com> wrote:
> > >> And repetitive
> > >>
> > >> Sent from my Android device. Please excuse typos and brevity.
> > >> On Jun 30, 2011 11:12 AM, "Bruno Borges" <br...@gmail.com>
> > wrote:
> > >>> Yes, me neither. That's why I asked.
> > >>>
> > >>> The preffix I'm using is "wicketstuff-", but Harald mentioned
> > >>> "org.wicketstuff."
> > >>>
> > >>> I don't want to use that, it's too verbose.
> > >>>
> > >>>
> > >>> *Bruno Borges*
> > >>> www.brunoborges.com.br
> > >>> +55 21 76727099
> > >>>
> > >>>
> > >>>
> > >>> On Thu, Jun 30, 2011 at 12:06 PM, James Carman
> > >>> <ja...@carmanconsulting.com>wrote:
> > >>>
> > >>>> I haven't seen that syntax before of having the group id in the
> > >>>> artifact id, at least not with the longer group ids (reverse
> domain).
> > >>>>
> > >>>> On Thu, Jun 30, 2011 at 11:02 AM, Bruno Borges <
> > bruno.borges@gmail.com>
> > >>>> wrote:
> > >>>> > The preffix is 'wicketstuff-', not 'org.wicketstuff.'
> > >>>> >
> > >>>> > Is this ok?
> > >>>> >
> > >>>> > *Bruno Borges*
> > >>>> > www.brunoborges.com.br
> > >>>> > +55 21 76727099
> > >>>> >
> > >>>> >
> > >>>> >
> > >>>> > On Wed, Jun 29, 2011 at 4:01 AM, Harald Wellmann <
> > >> harald.wellmann@gmx.de
> > >>>> >wrote:
> > >>>> >
> > >>>> >> For Maven OSGi bundle artifacts, there is a quasi-convention to
> > have
> > >>>> >> artifactId = Bundle-Symbolic name, so you would have
> > >>>> >>
> > >>>> >> groupId: org.wicketstuff
> > >>>> >> artifactId: org.wicketstuff.foo.bar
> > >>>> >> version: 1.5
> > >>>> >>
> > >>>> >> Bundle-Symbolic-Name: org.wicketstuff.foo.bar
> > >>>> >> JAR name: org.wicketstuff.foo.bar-1.5.**jar
> > >>>> >>
> > >>>> >> Apache Servicemix and Apache Aries use this convention, while
> > Apache
> > >>>> >> Commons sticks with the old names.
> > >>>> >>
> > >>>> >> Having this naming scheme and the one Bruno suggested in parallel
> > >> would
> > >>>> >> help to distinguish OSGi bundles from plain old JARs.
> > >>>> >>
> > >>>> >> Then again, that would mean you'd have to rename artifacts, once
> > you
> > >>>> osgify
> > >>>> >> them.
> > >>>> >>
> > >>>> >> Regards,
> > >>>> >> Harald
> > >>>> >>
> > >>>> >>
> > >>>> >>
> > >>>> >>
> > >>>>
> > ------------------------------**------------------------------**---------
> > >>>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
> > >>>> users-unsubscribe@wicket.apache.org>
> > >>>> >> For additional commands, e-mail: users-help@wicket.apache.org
> > >>>> >>
> > >>>> >>
> > >>>> >
> > >>>>
> > >>>>
> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > >>>> For additional commands, e-mail: users-help@wicket.apache.org
> > >>>>
> > >>>>
> > >>
> > >
> > >
> > >
> > > --
> > > Martin Grigorov
> > > jWeekend
> > > Training, Consulting, Development
> > > http://jWeekend.com
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
Re: WicketStuff artifacts naming strategy
Posted by Clint Checketts <ch...@gmail.com>.
I seem to recall the Maven guys recommending against periods in artifactIds.
Can't find the link for the info though... maybe it was just soething they
mentioned in the class.
The purpose was to reduce confusion between artifactIds and groupIds.
-Clint
On Thu, Jun 30, 2011 at 11:14 AM, Igor Vaynberg <ig...@gmail.com>wrote:
> i think the groupid/artifactid do matter because some containers have
> bundle deployers that pull things from the maven repo...i think
>
> -igor
>
> On Thu, Jun 30, 2011 at 8:38 AM, Martin Grigorov <mg...@apache.org>
> wrote:
> > The Maven artifact id is not important.
> > The name of the produced .jar is what matters, right ?
> >
> > Harald just said that there is a convention in OSGi world to work with
> > such named .jars (com.acme.blah)
> >
> > On Thu, Jun 30, 2011 at 6:31 PM, James Carman
> > <jc...@carmanconsulting.com> wrote:
> >> And repetitive
> >>
> >> Sent from my Android device. Please excuse typos and brevity.
> >> On Jun 30, 2011 11:12 AM, "Bruno Borges" <br...@gmail.com>
> wrote:
> >>> Yes, me neither. That's why I asked.
> >>>
> >>> The preffix I'm using is "wicketstuff-", but Harald mentioned
> >>> "org.wicketstuff."
> >>>
> >>> I don't want to use that, it's too verbose.
> >>>
> >>>
> >>> *Bruno Borges*
> >>> www.brunoborges.com.br
> >>> +55 21 76727099
> >>>
> >>>
> >>>
> >>> On Thu, Jun 30, 2011 at 12:06 PM, James Carman
> >>> <ja...@carmanconsulting.com>wrote:
> >>>
> >>>> I haven't seen that syntax before of having the group id in the
> >>>> artifact id, at least not with the longer group ids (reverse domain).
> >>>>
> >>>> On Thu, Jun 30, 2011 at 11:02 AM, Bruno Borges <
> bruno.borges@gmail.com>
> >>>> wrote:
> >>>> > The preffix is 'wicketstuff-', not 'org.wicketstuff.'
> >>>> >
> >>>> > Is this ok?
> >>>> >
> >>>> > *Bruno Borges*
> >>>> > www.brunoborges.com.br
> >>>> > +55 21 76727099
> >>>> >
> >>>> >
> >>>> >
> >>>> > On Wed, Jun 29, 2011 at 4:01 AM, Harald Wellmann <
> >> harald.wellmann@gmx.de
> >>>> >wrote:
> >>>> >
> >>>> >> For Maven OSGi bundle artifacts, there is a quasi-convention to
> have
> >>>> >> artifactId = Bundle-Symbolic name, so you would have
> >>>> >>
> >>>> >> groupId: org.wicketstuff
> >>>> >> artifactId: org.wicketstuff.foo.bar
> >>>> >> version: 1.5
> >>>> >>
> >>>> >> Bundle-Symbolic-Name: org.wicketstuff.foo.bar
> >>>> >> JAR name: org.wicketstuff.foo.bar-1.5.**jar
> >>>> >>
> >>>> >> Apache Servicemix and Apache Aries use this convention, while
> Apache
> >>>> >> Commons sticks with the old names.
> >>>> >>
> >>>> >> Having this naming scheme and the one Bruno suggested in parallel
> >> would
> >>>> >> help to distinguish OSGi bundles from plain old JARs.
> >>>> >>
> >>>> >> Then again, that would mean you'd have to rename artifacts, once
> you
> >>>> osgify
> >>>> >> them.
> >>>> >>
> >>>> >> Regards,
> >>>> >> Harald
> >>>> >>
> >>>> >>
> >>>> >>
> >>>> >>
> >>>>
> ------------------------------**------------------------------**---------
> >>>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
> >>>> users-unsubscribe@wicket.apache.org>
> >>>> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>>> >>
> >>>> >>
> >>>> >
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >>>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>>
> >>>>
> >>
> >
> >
> >
> > --
> > Martin Grigorov
> > jWeekend
> > Training, Consulting, Development
> > http://jWeekend.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: WicketStuff artifacts naming strategy
Posted by Igor Vaynberg <ig...@gmail.com>.
i think the groupid/artifactid do matter because some containers have
bundle deployers that pull things from the maven repo...i think
-igor
On Thu, Jun 30, 2011 at 8:38 AM, Martin Grigorov <mg...@apache.org> wrote:
> The Maven artifact id is not important.
> The name of the produced .jar is what matters, right ?
>
> Harald just said that there is a convention in OSGi world to work with
> such named .jars (com.acme.blah)
>
> On Thu, Jun 30, 2011 at 6:31 PM, James Carman
> <jc...@carmanconsulting.com> wrote:
>> And repetitive
>>
>> Sent from my Android device. Please excuse typos and brevity.
>> On Jun 30, 2011 11:12 AM, "Bruno Borges" <br...@gmail.com> wrote:
>>> Yes, me neither. That's why I asked.
>>>
>>> The preffix I'm using is "wicketstuff-", but Harald mentioned
>>> "org.wicketstuff."
>>>
>>> I don't want to use that, it's too verbose.
>>>
>>>
>>> *Bruno Borges*
>>> www.brunoborges.com.br
>>> +55 21 76727099
>>>
>>>
>>>
>>> On Thu, Jun 30, 2011 at 12:06 PM, James Carman
>>> <ja...@carmanconsulting.com>wrote:
>>>
>>>> I haven't seen that syntax before of having the group id in the
>>>> artifact id, at least not with the longer group ids (reverse domain).
>>>>
>>>> On Thu, Jun 30, 2011 at 11:02 AM, Bruno Borges <br...@gmail.com>
>>>> wrote:
>>>> > The preffix is 'wicketstuff-', not 'org.wicketstuff.'
>>>> >
>>>> > Is this ok?
>>>> >
>>>> > *Bruno Borges*
>>>> > www.brunoborges.com.br
>>>> > +55 21 76727099
>>>> >
>>>> >
>>>> >
>>>> > On Wed, Jun 29, 2011 at 4:01 AM, Harald Wellmann <
>> harald.wellmann@gmx.de
>>>> >wrote:
>>>> >
>>>> >> For Maven OSGi bundle artifacts, there is a quasi-convention to have
>>>> >> artifactId = Bundle-Symbolic name, so you would have
>>>> >>
>>>> >> groupId: org.wicketstuff
>>>> >> artifactId: org.wicketstuff.foo.bar
>>>> >> version: 1.5
>>>> >>
>>>> >> Bundle-Symbolic-Name: org.wicketstuff.foo.bar
>>>> >> JAR name: org.wicketstuff.foo.bar-1.5.**jar
>>>> >>
>>>> >> Apache Servicemix and Apache Aries use this convention, while Apache
>>>> >> Commons sticks with the old names.
>>>> >>
>>>> >> Having this naming scheme and the one Bruno suggested in parallel
>> would
>>>> >> help to distinguish OSGi bundles from plain old JARs.
>>>> >>
>>>> >> Then again, that would mean you'd have to rename artifacts, once you
>>>> osgify
>>>> >> them.
>>>> >>
>>>> >> Regards,
>>>> >> Harald
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> ------------------------------**------------------------------**---------
>>>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
>>>> users-unsubscribe@wicket.apache.org>
>>>> >> For additional commands, e-mail: users-help@wicket.apache.org
>>>> >>
>>>> >>
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff artifacts naming strategy
Posted by Martin Grigorov <mg...@apache.org>.
The Maven artifact id is not important.
The name of the produced .jar is what matters, right ?
Harald just said that there is a convention in OSGi world to work with
such named .jars (com.acme.blah)
On Thu, Jun 30, 2011 at 6:31 PM, James Carman
<jc...@carmanconsulting.com> wrote:
> And repetitive
>
> Sent from my Android device. Please excuse typos and brevity.
> On Jun 30, 2011 11:12 AM, "Bruno Borges" <br...@gmail.com> wrote:
>> Yes, me neither. That's why I asked.
>>
>> The preffix I'm using is "wicketstuff-", but Harald mentioned
>> "org.wicketstuff."
>>
>> I don't want to use that, it's too verbose.
>>
>>
>> *Bruno Borges*
>> www.brunoborges.com.br
>> +55 21 76727099
>>
>>
>>
>> On Thu, Jun 30, 2011 at 12:06 PM, James Carman
>> <ja...@carmanconsulting.com>wrote:
>>
>>> I haven't seen that syntax before of having the group id in the
>>> artifact id, at least not with the longer group ids (reverse domain).
>>>
>>> On Thu, Jun 30, 2011 at 11:02 AM, Bruno Borges <br...@gmail.com>
>>> wrote:
>>> > The preffix is 'wicketstuff-', not 'org.wicketstuff.'
>>> >
>>> > Is this ok?
>>> >
>>> > *Bruno Borges*
>>> > www.brunoborges.com.br
>>> > +55 21 76727099
>>> >
>>> >
>>> >
>>> > On Wed, Jun 29, 2011 at 4:01 AM, Harald Wellmann <
> harald.wellmann@gmx.de
>>> >wrote:
>>> >
>>> >> For Maven OSGi bundle artifacts, there is a quasi-convention to have
>>> >> artifactId = Bundle-Symbolic name, so you would have
>>> >>
>>> >> groupId: org.wicketstuff
>>> >> artifactId: org.wicketstuff.foo.bar
>>> >> version: 1.5
>>> >>
>>> >> Bundle-Symbolic-Name: org.wicketstuff.foo.bar
>>> >> JAR name: org.wicketstuff.foo.bar-1.5.**jar
>>> >>
>>> >> Apache Servicemix and Apache Aries use this convention, while Apache
>>> >> Commons sticks with the old names.
>>> >>
>>> >> Having this naming scheme and the one Bruno suggested in parallel
> would
>>> >> help to distinguish OSGi bundles from plain old JARs.
>>> >>
>>> >> Then again, that would mean you'd have to rename artifacts, once you
>>> osgify
>>> >> them.
>>> >>
>>> >> Regards,
>>> >> Harald
>>> >>
>>> >>
>>> >>
>>> >>
>>> ------------------------------**------------------------------**---------
>>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
>>> users-unsubscribe@wicket.apache.org>
>>> >> For additional commands, e-mail: users-help@wicket.apache.org
>>> >>
>>> >>
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff artifacts naming strategy
Posted by James Carman <jc...@carmanconsulting.com>.
And repetitive
Sent from my Android device. Please excuse typos and brevity.
On Jun 30, 2011 11:12 AM, "Bruno Borges" <br...@gmail.com> wrote:
> Yes, me neither. That's why I asked.
>
> The preffix I'm using is "wicketstuff-", but Harald mentioned
> "org.wicketstuff."
>
> I don't want to use that, it's too verbose.
>
>
> *Bruno Borges*
> www.brunoborges.com.br
> +55 21 76727099
>
>
>
> On Thu, Jun 30, 2011 at 12:06 PM, James Carman
> <ja...@carmanconsulting.com>wrote:
>
>> I haven't seen that syntax before of having the group id in the
>> artifact id, at least not with the longer group ids (reverse domain).
>>
>> On Thu, Jun 30, 2011 at 11:02 AM, Bruno Borges <br...@gmail.com>
>> wrote:
>> > The preffix is 'wicketstuff-', not 'org.wicketstuff.'
>> >
>> > Is this ok?
>> >
>> > *Bruno Borges*
>> > www.brunoborges.com.br
>> > +55 21 76727099
>> >
>> >
>> >
>> > On Wed, Jun 29, 2011 at 4:01 AM, Harald Wellmann <
harald.wellmann@gmx.de
>> >wrote:
>> >
>> >> For Maven OSGi bundle artifacts, there is a quasi-convention to have
>> >> artifactId = Bundle-Symbolic name, so you would have
>> >>
>> >> groupId: org.wicketstuff
>> >> artifactId: org.wicketstuff.foo.bar
>> >> version: 1.5
>> >>
>> >> Bundle-Symbolic-Name: org.wicketstuff.foo.bar
>> >> JAR name: org.wicketstuff.foo.bar-1.5.**jar
>> >>
>> >> Apache Servicemix and Apache Aries use this convention, while Apache
>> >> Commons sticks with the old names.
>> >>
>> >> Having this naming scheme and the one Bruno suggested in parallel
would
>> >> help to distinguish OSGi bundles from plain old JARs.
>> >>
>> >> Then again, that would mean you'd have to rename artifacts, once you
>> osgify
>> >> them.
>> >>
>> >> Regards,
>> >> Harald
>> >>
>> >>
>> >>
>> >>
>> ------------------------------**------------------------------**---------
>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
>> users-unsubscribe@wicket.apache.org>
>> >> For additional commands, e-mail: users-help@wicket.apache.org
>> >>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
Re: WicketStuff artifacts naming strategy
Posted by Bruno Borges <br...@gmail.com>.
Yes, me neither. That's why I asked.
The preffix I'm using is "wicketstuff-", but Harald mentioned
"org.wicketstuff."
I don't want to use that, it's too verbose.
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Thu, Jun 30, 2011 at 12:06 PM, James Carman
<ja...@carmanconsulting.com>wrote:
> I haven't seen that syntax before of having the group id in the
> artifact id, at least not with the longer group ids (reverse domain).
>
> On Thu, Jun 30, 2011 at 11:02 AM, Bruno Borges <br...@gmail.com>
> wrote:
> > The preffix is 'wicketstuff-', not 'org.wicketstuff.'
> >
> > Is this ok?
> >
> > *Bruno Borges*
> > www.brunoborges.com.br
> > +55 21 76727099
> >
> >
> >
> > On Wed, Jun 29, 2011 at 4:01 AM, Harald Wellmann <harald.wellmann@gmx.de
> >wrote:
> >
> >> For Maven OSGi bundle artifacts, there is a quasi-convention to have
> >> artifactId = Bundle-Symbolic name, so you would have
> >>
> >> groupId: org.wicketstuff
> >> artifactId: org.wicketstuff.foo.bar
> >> version: 1.5
> >>
> >> Bundle-Symbolic-Name: org.wicketstuff.foo.bar
> >> JAR name: org.wicketstuff.foo.bar-1.5.**jar
> >>
> >> Apache Servicemix and Apache Aries use this convention, while Apache
> >> Commons sticks with the old names.
> >>
> >> Having this naming scheme and the one Bruno suggested in parallel would
> >> help to distinguish OSGi bundles from plain old JARs.
> >>
> >> Then again, that would mean you'd have to rename artifacts, once you
> osgify
> >> them.
> >>
> >> Regards,
> >> Harald
> >>
> >>
> >>
> >>
> ------------------------------**------------------------------**---------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
> users-unsubscribe@wicket.apache.org>
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: WicketStuff artifacts naming strategy
Posted by James Carman <ja...@carmanconsulting.com>.
I haven't seen that syntax before of having the group id in the
artifact id, at least not with the longer group ids (reverse domain).
On Thu, Jun 30, 2011 at 11:02 AM, Bruno Borges <br...@gmail.com> wrote:
> The preffix is 'wicketstuff-', not 'org.wicketstuff.'
>
> Is this ok?
>
> *Bruno Borges*
> www.brunoborges.com.br
> +55 21 76727099
>
>
>
> On Wed, Jun 29, 2011 at 4:01 AM, Harald Wellmann <ha...@gmx.de>wrote:
>
>> For Maven OSGi bundle artifacts, there is a quasi-convention to have
>> artifactId = Bundle-Symbolic name, so you would have
>>
>> groupId: org.wicketstuff
>> artifactId: org.wicketstuff.foo.bar
>> version: 1.5
>>
>> Bundle-Symbolic-Name: org.wicketstuff.foo.bar
>> JAR name: org.wicketstuff.foo.bar-1.5.**jar
>>
>> Apache Servicemix and Apache Aries use this convention, while Apache
>> Commons sticks with the old names.
>>
>> Having this naming scheme and the one Bruno suggested in parallel would
>> help to distinguish OSGi bundles from plain old JARs.
>>
>> Then again, that would mean you'd have to rename artifacts, once you osgify
>> them.
>>
>> Regards,
>> Harald
>>
>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<us...@wicket.apache.org>
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff artifacts naming strategy
Posted by Bruno Borges <br...@gmail.com>.
The preffix is 'wicketstuff-', not 'org.wicketstuff.'
Is this ok?
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Wed, Jun 29, 2011 at 4:01 AM, Harald Wellmann <ha...@gmx.de>wrote:
> For Maven OSGi bundle artifacts, there is a quasi-convention to have
> artifactId = Bundle-Symbolic name, so you would have
>
> groupId: org.wicketstuff
> artifactId: org.wicketstuff.foo.bar
> version: 1.5
>
> Bundle-Symbolic-Name: org.wicketstuff.foo.bar
> JAR name: org.wicketstuff.foo.bar-1.5.**jar
>
> Apache Servicemix and Apache Aries use this convention, while Apache
> Commons sticks with the old names.
>
> Having this naming scheme and the one Bruno suggested in parallel would
> help to distinguish OSGi bundles from plain old JARs.
>
> Then again, that would mean you'd have to rename artifacts, once you osgify
> them.
>
> Regards,
> Harald
>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<us...@wicket.apache.org>
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: WicketStuff artifacts naming strategy
Posted by Harald Wellmann <ha...@gmx.de>.
For Maven OSGi bundle artifacts, there is a quasi-convention to have
artifactId = Bundle-Symbolic name, so you would have
groupId: org.wicketstuff
artifactId: org.wicketstuff.foo.bar
version: 1.5
Bundle-Symbolic-Name: org.wicketstuff.foo.bar
JAR name: org.wicketstuff.foo.bar-1.5.jar
Apache Servicemix and Apache Aries use this convention, while Apache
Commons sticks with the old names.
Having this naming scheme and the one Bruno suggested in parallel would
help to distinguish OSGi bundles from plain old JARs.
Then again, that would mean you'd have to rename artifacts, once you
osgify them.
Regards,
Harald
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff artifacts naming strategy
Posted by James Carman <ja...@carmanconsulting.com>.
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 <br...@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 <br...@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
>> >> <jc...@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" <br...@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.borges@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.ocleirigh@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<
>> >>> TorIverW@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-unsubscribe@wicket.apache.org
>> >>> >>>> For additional commands, e-mail: users-help@wicket.apache.org
>> >>> >>>>
>> >>> >>>>
>> >>> >>>
>> >>> >>>
>> ---------------------------------------------------------------------
>> >>> >>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> >>> >>> For additional commands, e-mail: users-help@wicket.apache.org
>> >>> >>>
>> >>> >>>
>> >>> >>
>> >>>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff artifacts naming strategy
Posted by Bruno Borges <br...@gmail.com>.
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 <br...@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
> >> <jc...@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" <br...@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.borges@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.ocleirigh@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<
> >>> TorIverW@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-unsubscribe@wicket.apache.org
> >>> >>>> For additional commands, e-mail: users-help@wicket.apache.org
> >>> >>>>
> >>> >>>>
> >>> >>>
> >>> >>>
> ---------------------------------------------------------------------
> >>> >>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >>> >>> For additional commands, e-mail: users-help@wicket.apache.org
> >>> >>>
> >>> >>>
> >>> >>
> >>>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: WicketStuff artifacts naming strategy
Posted by James Carman <ja...@carmanconsulting.com>.
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 <br...@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
>> <jc...@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" <br...@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.borges@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.ocleirigh@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<
>>> TorIverW@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-unsubscribe@wicket.apache.org
>>> >>>> For additional commands, e-mail: users-help@wicket.apache.org
>>> >>>>
>>> >>>>
>>> >>>
>>> >>> ---------------------------------------------------------------------
>>> >>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> >>> For additional commands, e-mail: users-help@wicket.apache.org
>>> >>>
>>> >>>
>>> >>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff artifacts naming strategy
Posted by James Carman <ja...@carmanconsulting.com>.
Are you changing artifact ids?
On Tue, Jun 28, 2011 at 6:26 PM, Bruno Borges <br...@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
> <jc...@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" <br...@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.borges@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.ocleirigh@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<
>> TorIverW@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-unsubscribe@wicket.apache.org
>> >>>> For additional commands, e-mail: users-help@wicket.apache.org
>> >>>>
>> >>>>
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> >>> For additional commands, e-mail: users-help@wicket.apache.org
>> >>>
>> >>>
>> >>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff artifacts naming strategy
Posted by Bruno Borges <br...@gmail.com>.
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
<jc...@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" <br...@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.borges@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.ocleirigh@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<
> TorIverW@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-unsubscribe@wicket.apache.org
> >>>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>>
> >>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>
> >>>
> >>
>
Re: WicketStuff artifacts naming strategy
Posted by James Carman <jc...@carmanconsulting.com>.
This can cause classpath collisions
Sent from my Android device. Please excuse typos and brevity.
On Jun 28, 2011 5:27 PM, "Bruno Borges" <br...@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.borges@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.ocleirigh@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<
TorIverW@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-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
Re: WicketStuff artifacts naming strategy
Posted by Bruno Borges <br...@gmail.com>.
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 <br...@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.ocleirigh@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<TorIverW@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-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
Re: WicketStuff artifacts naming strategy
Posted by Bruno Borges <br...@gmail.com>.
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.ocleirigh@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<TorIverW@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-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: WicketStuff artifacts naming strategy
Posted by Michael O'Cleirigh <mi...@rivulet.ca>.
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<To...@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-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff artifacts naming strategy
Posted by Michael O'Cleirigh <mi...@rivulet.ca>.
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<To...@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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff artifacts naming strategy
Posted by Martin Grigorov <mg...@apache.org>.
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 <To...@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
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com <http://jweekend.com/>
RE: WicketStuff artifacts naming strategy
Posted by Wilhelmsen Tor Iver <To...@arrive.no>.
> - 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