Arnaud, I saw on the branch merge vote that you mentioned applying
some patches to trunk. Please do, if you have time. I'm still
interested in an 0.9-alpha-2 build with the fixes you and Nicolas have
discussed.
If it's going to cause trouble with the branch, then let's create a
new 0.9 branch a
On 4/12/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
only the jpox plugin should be 1.1.6, jpox must be 1.1.7
Thank you. That was the last snapshot, and "mvn release:prepare
-DdryRun=true" now completes successfully.
It looks like there are some models which have version 1.0.0. Do you
th
Wendy Smoak a écrit :
On 4/11/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
[INFO] Can't release project due to non released dependencies :
org.codehaus.mojo:jpox-maven-plugin:maven-plugin:1.1.7-SNAPSHOT:runtime
in project 'Archiva Standard Reports'
(org.apache.maven.archiva:archiva-report
On 4/11/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
OK, I bugged Jesse on irc about the maven-app-* releases that need to
be promoted from staging. Those are the last remaining snapshots in
the build. Then we'll see how easy it is... some time this weekend,
probably.
Thanks to Jesse for synci
I have my archiva deployed and running, so I can wait for a merge for any
further enhancements. I allready had to adapt MRM153 patch for the "/proxy"
to "/repository" URI changes. I'll follow changes made on trunk to update my
snapshot, and propose patches when required.
Just for my info, as I mi
I took a look at archiva/trunk, and the only remaining snapshot
dependencies I see are from maven-app-configuration. That vote has
passed and is just waiting for the staged binaries to be copied over
to the synced repo.
Once that's done, I'd like to tag and release archiva/trunk. It
works, it a
