when i do mvn install from that branch root i get:

http://papernapkin.org/pastebin/view/4946

-igor



On 3/8/07, Alastair Maw <[EMAIL PROTECTED]> wrote:

Martijn Dashorst wrote:
> On 3/8/07, Al Maw <[EMAIL PROTECTED]> wrote:
>> We can automate the scp stuff as part of the -DperformRelease=true.
>>
>> We should surely also be copying doing a proper deploy, not an install,
>> so that we copy the JARs for the projects to apache's Maven repo, so
>> they can be synced up with repo1.maven.org?
>
> Incubator jars are barred from being released to the central repo. And
> the release should be voted on before we put it into the wild. Maven
> does have something like a staging thing, not sure how that works.

Hmmm. We still need the Maven 2 poms and things in a repo somewhere so
people can actually use them. If we're not allowed to publish things to
repo1.maven.org while incubating that's pretty serious and seems rather
misguided. :-(

>> I'm still in favour of using the release plug-in if we can, as it scps
>> the site to the right place, doesn't let you tag if there are test
>> failures, and all the rest of it.
>
> We will not deploy the site as it currently is: no more examples and
> just the default maven reports. But having the javadoc and the
> dependencies up on the site is something worthwile. The WICKETxSITE
> will function as our site portal, wicket-1.3.0 will have the release
> details.

Well, I was going to tweak the output of site:site somewhat to make it
more useful as part of this process.

>> > We also need to sign the release using gpg, as I understand there is
a
>> > maven plugin for that as well.
>>
>> OK, I'll see if I can look into this at some point.
>
> I just got gpg installed on my mac, so I'll be able to generate a key
> and sign the releases.

Hokay.

What I'm interested in at this point is whether people would be happy to
move the 1.3 modules/build structure to something that resembles this
branch. I'm reluctant to do much more work on this proof-of-concept
branch as there seems little point doing it all twice. I'll call a vote
on this shortly on dev@ if no one objects.

I'd also like to rename the "wicket-1.x" branch to "wicket-1.3.x" while
I'm about it.

Al

Reply via email to