Samuel Le Berrigaud wrote:
> Alternatively you might consider moving all components to the new
> groupId "org.apache.commons" and using maven's relocation
> (http://maven.apache.org/guides/mini/guide-relocation.html) to ensure
> backward compatibility.
See old discussions ...
- Jörg
--
Alternatively you might consider moving all components to the new
groupId "org.apache.commons" and using maven's relocation
(http://maven.apache.org/guides/mini/guide-relocation.html) to ensure
backward compatibility.
SaM
On Tue, Jun 16, 2009 at 8:58 AM, sebb wrote:
> On 15/06/2009, Jörg Schaible
On 15/06/2009, Jörg Schaible wrote:
> Emmanuel Bourg wrote:
>
> > sebb a écrit :
> >> Which is the correct style for Maven2 releases?
> >>
> >> org.apache.commons
> >> commons-component
> >>
> >> or
> >>
> >> commons-component
> >> commons-component
> >>
> >> There are recent examples
Emmanuel Bourg wrote:
> sebb a écrit :
>> Which is the correct style for Maven2 releases?
>>
>> org.apache.commons
>> commons-component
>>
>> or
>>
>> commons-component
>> commons-component
>>
>> There are recent examples of both.
>
> I would say:
>
> - new components use "org.apache.commons
sebb a écrit :
Which is the correct style for Maven2 releases?
org.apache.commons
commons-component
or
commons-component
commons-component
There are recent examples of both.
I would say:
- new components use "org.apache.commons"
- already released components keep the same groupId. If the
On Mon, Jun 15, 2009 at 3:03 PM, sebb wrote:
> Which is the correct style for Maven2 releases?
>
> org.apache.commons
> commons-component
>
> or
>
> commons-component
> commons-component
>
Depends.
We started off with "commons-component". No one has taken on
relocating old components -- there is
Which is the correct style for Maven2 releases?
org.apache.commons
commons-component
or
commons-component
commons-component
There are recent examples of both.
Also, I've noticed that some pom.xml files (e.g. compress, proxy)
don't include a for the current component; presumably that
is an ove
