On Jan 31, 2008 3:26 PM, Magnus Grimsell <[EMAIL PROTECTED]> wrote:
> > Well, the version of Cargo integrated is: 0.9
>
> Ok, I've done some fixes for Cactus to work with Cargo 1.0-SNAPSHOT.
> Once cargo releases 1.0 I'll be able to commit them.
>
> > One other quick question. My PGP key is signed only by Roy
> > Fielding(I missed
> > the
> > key-signing party in Atlanta :-)) so will I be able to make a release?
>
> I have never been involved in releasing Cactus. Maybe someone else can share 
> some light on this?

AFAIK you can (I've done several ASF releases and my key is signed by
nobody) - its nice to have but not required and the release signing
FAQ doesn't say its required:
http://www.apache.org/dev/release-signing.html#web-of-trust

Niall

> >
> > Cheers, Petar.
> >
> > On Jan 31, 2008 4:41 PM, Petar Tahchiev
> > <[EMAIL PROTECTED]> wrote:
> >
> > > OK,
> > >
> > > so far:
> > >
> > > 1) I removed all of the .cvsignore files.
> > > 2) Improved lots of the documentation.
> > > 3) Removed the samples module from the initial build.
> > > If you just run mvn install then the samples modules will
> > not be build.
> > > When specifying a with-samples profile, like:
> > >
> > > mvn clean install -P with-samples
> > >
> > > then the same build will pass + the samples modules. Now
> > for the samples
> > > to be executed correctly you will need a servlet
> > container/ejb container.
> > > Hopefully Cargo gives us the opportunity to get the containers from
> > > internet.
> > > This will, however, slow down the build process, but as far
> > as you have
> > > patience, it's OK. :-)
> > >
> > > Any other comments?
> > >
> > >
> > >
> > > On Jan 30, 2008 7:44 PM, sebb <[EMAIL PROTECTED]> wrote:
> > >
> > > > Trying "mvn site:site" complains that it cannot find:
> > > >
> > > > org.apache.cactus:cactus.maven.skin:jar:2.0.0
> > > >
> > > > "mvn install" fails because it cannot find:
> > > >
> > > > [C:/apache/tomcat/apache-tomcat-6.0.14]
> > > >
> > > >
> > > > On 30/01/2008, sebb <[EMAIL PROTECTED]> wrote:
> > > > > A brief look shows that:
> > > > >
> > > > > The README file has the line:
> > > > >
> > > > > To build Cactus from CVS, please refer to the following tuturial
> > > > > which should probably be
> > > > > To build Cactus from SVN, please refer to the following tutorial
> > > > >
> > > > > There need to be LICENSE and NOTICE files.
> > > > >
> > > > > The .cvsignore files should be deleted.
> > > > >
> > > > > ===
> > > > >
> > > > > Not everyone will want to build the code and
> > documentation just in
> > > > > order to review the proposed release, so may I suggest
> > that you create
> > > > > the distribution artefacts and web-site from the branch
> > and upload
> > > > > them to your personal directory on people.apache.org?
> > > > >
> > > > > Once any issues are sorted, a formal vote can be started.
> > > > >
> > > > > Sebastian
> > > > > On 30/01/2008, Petar Tahchiev
> > <[EMAIL PROTECTED]> wrote:
> > > > > > Hi guys,
> > > > > >
> > > > > > my name is Petar Tahchiev, and I see I am currently
> > the only active
> > > > > > committer for the Cactus project.
> > > > > > For the last year I have been working in a separate
> > branch here:
> > > > > >
> > > > > >
> > > >
> > http://svn.apache.org/repos/asf/jakarta/cactus/branches/CACTUS
> > _TRUNK_MAMOUTH/
> > > > > >
> > > > > > and I think that I am ready to try and make a release
> > candidate
> > > > (RC).
> > > > > > Because of the status of Cactus
> > > > > > I guess I will have to initiate a vote for this
> > release to be done,
> > > > and also
> > > > > > to fix if you find something to be broken.
> > > > > >
> > > > > > The current changes include:
> > > > > > 1) new Maven2 based build system
> > > > > > 2) integration between Cargo & Cactus
> > > > > > 3) new Ant tasks (see the sample projects).
> > > > > > 4) the New Cactus web-site (look in cactus-site and
> > execute mvn
> > > > site:site)
> > > > > > 5) Cactus-eclipse plugin refactored to support Eclipse 3.2
> > > > > >
> > > > > > Well, currently the only thing that is left is to describe
> > > > everything in a
> > > > > > nice documentation,
> > > > > > but I prefer to do this once I see that you guys say
> > everything is
> > > > OK.
> > > > > >
> > > > > > So that's what I do now. I hope that you guys
> > checkout the project
> > > > from the
> > > > > > repository and give it a try.
> > > > > >
> > > > > > Waiting for your comments.
> > > > > >
> > > > > > Cheers, Petar.
> > > > > >
> > > > > > --
> > > > > > Regards, Petar!
> > > > > > Karlovo, Bulgaria.
> > > > > >
> > > > > > EOOXML objections
> > > > > > http://www.grokdoc.net/index.php/EOOXML_objections
> > > > > >
> > > > > > Public PGP Key at:
> > > > > >
> > > >
> > http://keyserver.linux.it/pks/lookup?op=get&search=0x1A15B53B761500F9
> > > > > > Key Fingerprint: AA16 8004 AADD 9C76 EF5B  4210 1A15
> > B53B 7615 00F9
> > > > > >
> > > > >
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Regards, Petar!
> > > Karlovo, Bulgaria.
> > >
> > > EOOXML objections
> > > http://www.grokdoc.net/index.php/EOOXML_objections
> > >
> > > Public PGP Key at:
> > >
> > http://keyserver.linux.it/pks/lookup?op=get&search=0x1A15B53B761500F9
> > > Key Fingerprint: AA16 8004 AADD 9C76 EF5B  4210 1A15 B53B 7615 00F9
> > >
> >
> >
> >
> > --
> > Regards, Petar!
> > Karlovo, Bulgaria.
> >
> > EOOXML objections
> > http://www.grokdoc.net/index.php/EOOXML_objections
> >
> > Public PGP Key at:
> > http://keyserver.linux.it/pks/lookup?op=get&search=0x1A15B53B761500F9
> > Key Fingerprint: AA16 8004 AADD 9C76 EF5B  4210 1A15 B53B 7615 00F9
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to