It really depends on whether you are looking to use the 1.1.9
enhnacement features, or the 1.1.9 runtime features. I think the bug
it was addressing was in the runtime - so to upgrade would be nice but
non essential.
As for the conversion, I'm not really sure...
- Brett
On 30/01/2008, at 11:57 PM, nicolas de loof wrote:
I also notice archiva-model is using jpox 1.1.6 plugin from Mojo
Is there a reason not to use jpox-one :
http://www.jpox.org/downloads/maven2/jpox/jpox-maven-plugin/
Nico.
2008/1/30, nicolas de loof <[EMAIL PROTECTED]>:
MVNII-14 was closed as "Won't fix"
The central POM is a converted from m1 POM, jPox also has a valid
POM in
SVN
That also shows that the m1 -> m2 pom conversion doesn't work well
and
produces invalid POMs.
Maybe this process should be enhance to validate the converted POM
before
deployment, and maybe slip it if non convertible.
Nico.
2008/1/30, Wendy Smoak <[EMAIL PROTECTED]>:
On Jan 30, 2008 8:18 AM, nicolas de loof <[EMAIL PROTECTED]> wrote:
Is there a good reason to declare jpox-repository in archiva main
pom
?
The jpox pom.xml is a maven1 pom, and the requested artifact is
available in
central.
I think it was added while we waited for jpox 1.1.9 to be uploaded
[1]
and it can be removed now.
[1] http://jira.codehaus.org/browse/MEV-566
--
Wendy
