On Mon, Aug 16, 2010 at 1:57 PM, Niall Pemberton
wrote:
> Apologies - for some reason I didn't read your reply properly.
The reason is much more likely to be my inability to express myself in english.
Jochen
--
I Am What I Am And That's All What I Yam (Popeye)
--
The problem is this: Commons libraries are more than likely to be used
by multiple dependencies. That's no problem for Maven, if they have
the same group and artifact Id. Maven eliminates the predecessor from
the dependency list. That won't work if the group Id has changes.
Jochen
2010/8/16 Rafa
On Mon, Aug 16, 2010 at 1:41 PM, Jochen Wiedmann
wrote:
> The idea is vice versa: Do not change the groupId, unless you are
> considering changes as serious as changing the package name.
I don't see why.
Domain based groupIds are standard now, they are easier to find in IDE
tools and I hear maven
On Mon, Aug 16, 2010 at 12:41 PM, Jochen Wiedmann
wrote:
> The idea is vice versa: Do not change the groupId, unless you are
> considering changes as serious as changing the package name.
Apologies - for some reason I didn't read your reply properly.
Niall
> On Mon, Aug 16, 2010 at 1:06 PM, Nia
The idea is vice versa: Do not change the groupId, unless you are
considering changes as serious as changing the package name.
On Mon, Aug 16, 2010 at 1:06 PM, Niall Pemberton
wrote:
> On Mon, Aug 16, 2010 at 11:43 AM, Jochen Wiedmann
> wrote:
>> Not that I have any ideas about Commons Net: But
On Mon, Aug 16, 2010 at 11:43 AM, Jochen Wiedmann
wrote:
> Not that I have any ideas about Commons Net: But to me the first
> requirement would be a change of the package structure like moving to
> o.a.c.net2, rather than o.a.c.net. Otherwise the groupId should
> preferrably be stable.
IMO the bu
Not that I have any ideas about Commons Net: But to me the first
requirement would be a change of the package structure like moving to
o.a.c.net2, rather than o.a.c.net. Otherwise the groupId should
preferrably be stable.
Jochen
On Mon, Aug 16, 2010 at 12:30 PM, sebb wrote:
> Net is still using
Net is still using the commons-net Maven groupId.
What needs to be done to move it to the o.a.c groupId?
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
