I think the easiest way forward for this release will be to remove the
problem element from the m1 POM and re-sign it in-place. For future
releases let's sync the groupId to org.apache.jcs.
Thanks a whole bunch Thomas for taking on the relatively thankless role
of Release Manager for JCS. I am sure your efforts are appreciated by
many. Let's also say a big thanks to Aaron too - clearly JCS is almost
entirely the result of his labour.
Scott
Thomas Vandahl wrote:
Hi folks,
I asked for the whereabouts of the jcs-1.3.jar in the maven1 repository
and got the following response. How would we proceed? I tend to fix the
pom but changing the groupID would have the advantage of a unified
deploy for the next release. Please suggest.
Bye, Thomas.
-------- Original Message --------
Subject: Re: JCS 1.3 not in m1-repo
Date: Mon, 11 Jun 2007 12:33:27 -0700
From: Carlos Sanchez <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>
The source POM was invalid: Unrecognised tag:
'aspectSourceDirectories' (position: START_TAG seen
...</unitTestSourceDirectory>\n\t\t<aspect
SourceDirectories>... @315:28) .
Now, do you want to fix it or point people to org.apache.jcs ?
The report is here
http://repo1.maven.org/maven2-converted-from-maven1/.reports/health-report.xml
On 6/11/07, Thomas Vandahl <[EMAIL PROTECTED]> wrote:
Hi folks,
I wrote this to [EMAIL PROTECTED] a couple of days before without
being subscribed but the mail probably got stuck somewhere. So here we
go again:
I found that the newly released jcs-1.3.jar is not accessible in the
maven1 repository. It obviously contains a redirect to the maven2-repo
where it did not arrive. Everything on our side looks ok to me. Could
you please check what happened?
TIA
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
