;
>>>>> > >>>> > On Wed, Jun 29, 2011 at 4:01 AM, Harald Wellmann <
>>>>> > >> harald.wellm...@gmx.de
>>>>> > >>>> >wrote:
>>>>> > >>>> >
>>>>> &g
gt;>> > >>>> >>
>>>> > >>>> >> groupId: org.wicketstuff
>>>> > >>>> >> artifactId: org.wicketstuff.foo.bar
>>>> > >>>> >> version: 1.5
>>>> > >>>> >&
>>>> >> version: 1.5
>>> > >>>> >>
>>> > >>>> >> Bundle-Symbolic-Name: org.wicketstuff.foo.bar
>>> > >>>> >> JAR name: org.wicketstuff.foo.bar-1.5.**jar
>>> > >>>> >
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 wrote:
> T
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
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 Vayn
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 wrote:
> The Maven artifact id is not important.
> The name of the produced .jar is what matters, right ?
>
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
wrote:
> And repetitive
>
> Sent from my Android de
And repetitive
Sent from my Android device. Please excuse typos and brevity.
On Jun 30, 2011 11:12 AM, "Bruno Borges" 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 verbos
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 wrote:
> Harald said that "org.wicketstuff." convention is
Harald said that "org.wicketstuff." convention is used by OSGi-ed projects.
On Thu, Jun 30, 2011 at 6:09 PM, Bruno Borges 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 ver
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
wrote:
> I haven't seen that
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 wrote:
> The preffix is 'wicketstuff-', not 'org.wicketstuff.'
>
> Is this ok?
>
> *Bruno Borges*
> www.brunoborges.
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 wrote:
> For Maven OSGi bundle artifacts, there is a quasi-convention to have
> artifactId = Bundle-Symbolic name, so you wo
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 Ser
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 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 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 actua
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
Are you changing artifact ids?
On Tue, Jun 28, 2011 at 6:26 PM, Bruno Borges 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
> 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
wrote:
> This can cause classpath collisions
>
> Sent from my Android device. Please excuse typos and brevity
This can cause classpath collisions
Sent from my Android device. Please excuse typos and brevity.
On Jun 28, 2011 5:27 PM, "Bruno Borges" wrote:
> I started to modify all JAR poms to have the wicketstuff- preffix.
>
> Is anybody against this? Why?
>
> :-)
>
> *Bruno Borges*
> www.brunoborges.com
You convinced me. ;)
On Tue, Jun 28, 2011 at 4:45 PM, Bruno Borges 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 ?
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:
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 wrote:
> I started to modify all JAR poms to have the wicketstuff- preffix.
>
> Is anybody against this? Why?
>
> :-)
>
> *Bruno Borges*
> www.brunoborg
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 wrote:
> We could simply rename the artifactId property of projects, prepending with
> wick
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
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
option and uploads in the original format when deploying.
I will investigate this further but it won't be part of the next
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:
${project.groupId}-${project.artifactId}-${project.version}.jar
On Fri, Mar 25, 2011 at 9
In the most parent wicketstuff pom.xml:
${project.groupId}-${project.artifactId}-${project.version}.jar
On Fri, Mar 25, 2011 at 9:31 AM, Wilhelmsen Tor Iver wrote:
> > - jasperreports-1.4.16.jar
> > - jasperreports-3.7.2.jar
>
> > The first one is from WicketStuff, but still, it is confusi
> - 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
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 'wick
31 matches
Mail list logo
