Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 66548 invoked from network); 3 Oct 2008 13:06:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Oct 2008 13:06:48 -0000 Received: (qmail 21882 invoked by uid 500); 3 Oct 2008 13:06:46 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 21843 invoked by uid 500); 3 Oct 2008 13:06:46 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 21832 invoked by uid 99); 3 Oct 2008 13:06:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Oct 2008 06:06:46 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pajbam@gmail.com designates 209.85.200.173 as permitted sender) Received: from [209.85.200.173] (HELO wf-out-1314.google.com) (209.85.200.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Oct 2008 13:05:44 +0000 Received: by wf-out-1314.google.com with SMTP id 27so1669764wfd.31 for ; Fri, 03 Oct 2008 06:06:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=UW1/NGQia5TpHKcdwGOq4ixrE/dPoQ5poOcCjrPbNb8=; b=eGDFvRencvLXU+1EBIEfeLrVvUOwW1Ne333yJT1WjKJJciMrwTeaia2jmYF7jJ/muq IBO6rhnDYCWcXcEV+YtU9qdmqih9A4jaiUEKXmsVsTinWrOcK5+MmgD7j1l6+7pt1lWp cSiRjgnsMYICYlEWmsPkYJ7Mn99Mjj0TThQRA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=mPCkDrzusbZptGyXAkuFFy2Ra6Lxh0nSuOIBZfBnDx67v63esmoZEetGWnBvDaAdxz eeG2Vzc/gbhZt660macP6FiSFESN5imbgM9DEytal58uQgzWyD+b36pjlc4z67ZMWf/L WdQSduOcYIxTUqmHcGKfx6dxuFhKHIW98plZ0= Received: by 10.142.230.11 with SMTP id c11mr359806wfh.302.1223039179040; Fri, 03 Oct 2008 06:06:19 -0700 (PDT) Received: by 10.143.6.6 with HTTP; Fri, 3 Oct 2008 06:06:18 -0700 (PDT) Message-ID: <98d8c0860810030606n53d53a3dxa40bd2ded7260c73@mail.gmail.com> Date: Fri, 3 Oct 2008 15:06:18 +0200 From: "Pierre-Arnaud Marcelot" Sender: pajbam@gmail.com To: "Apache Directory Developers List" Subject: Re: [Studio] Using the Maven Release Plugin In-Reply-To: <98d8c0860810030302v4cf0622fq3e6866b85a5ad049@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_28599_11477645.1223039179038" References: <98d8c0860809190454q4a3356d1q9b45e6b9e735f197@mail.gmail.com> <98d8c0860809230515m336efc7dhf9f4bbe2b4843b93@mail.gmail.com> <98d8c0860809300307i2f218264r353155658ff0b4f3@mail.gmail.com> <48E293C9.7020003@apache.org> <98d8c0860810010102g1e75838fg262131967eec5d7e@mail.gmail.com> <48E3B129.2080401@apache.org> <98d8c0860810020449j7e3cb8dm2346bfd53c1cf03c@mail.gmail.com> <98d8c0860810020458h2ba75587kf0e07a34eae4c6f7@mail.gmail.com> <48E4BB01.8030708@apache.org> <98d8c0860810030302v4cf0622fq3e6866b85a5ad049@mail.gmail.com> X-Google-Sender-Auth: 51aa72944862be2c X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_28599_11477645.1223039179038 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi again, Looks like Apache DS already had the same problem before [1]. I'm going to look for any "wrote: > Hi, > > I'm trying to use the 'release:perform' task on Studio. > I've released internally in my personal Maven repository the TLP pom > version 14 and I've updated Studio's root pom to use this version. > I've setup my settings.xml file with the release profile (I'm releasing > into a specific folder instead of apache's maven repo of course) and used it > to run the release. > > It worked for a few projects that got successfully deploy to my repo but it > then failed on the LDAP Browser Core project. > Looks like it failed when generating the Javadoc... :( > > The build log is attached to this mail. > > Does anyone know who I can fix this? > > Thanks, > Pierre-Arnaud > > > On Thu, Oct 2, 2008 at 2:13 PM, Felix Knecht wrote: > >> Pierre-Arnaud Marcelot schrieb: >> > Guys, >> > >> > The "release:prepare" goal is working! ;) At last... >> > >> > Here are the few modifications I had to do to make it work: >> > >> > * Exclude the 'test-integration-core' and 'test-integration-ui' >> > projects from the build (so they don't get released). >> > * Change the version of the studio-maven-plugin to a released one >> > (ie. 1.0.1). >> > * Change the '' in the configuration of the >> > release plugin to "clean studio:eclipse >> > install". >> > >> > I tested the generated jars and distribution and they are working very >> > well. >> > >> > If everyone if ok with these modification, I'd like to apply them on >> > trunk. >> >> +1 >> >> > WDYT ? >> > >> > Unfortunately, I was not able to test the deployment using the >> > "release:perform" goal because Studio's pom refers to TLP pom version >> > 13 which does not allow us to change the remote repository. >> > Maybe, we can release the TLP pom version 14, so I can try this. >> >> +1 >> >> Felix >> > WDYT ? >> > >> > Thanks, >> > Pierre-Arnaud >> > >> > On Thu, Oct 2, 2008 at 1:49 PM, Pierre-Arnaud Marcelot >> > > wrote: >> > >> > On Wed, Oct 1, 2008 at 7:19 PM, Stefan Seelmann >> > > wrote: >> > >> > We already have such profiles, they are called >> > integration-core and >> > integration-ui :-) >> > >> > >> > Yeah, it's true, but I'm talking about a profile in the root pom >> > that will include the 'test-integration-core' and >> > 'test-integration-ui' projects. >> > >> > By default, these 2 projects will be excluded from the build, and >> > they will be included only if you add this profile. >> > >> > Regards, >> > Pierre-Arnaud >> > >> > >> >> > ------=_Part_28599_11477645.1223039179038 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Hi again,

Looks like Apache DS already had the same problem before [1].

I'm going to look for any "<a" string in the javadoc and replace it by "&lt;a" to fix the issue.

Regards,
Pierre-Arnaud

[1] - http://issues.apache.org/jira/browse/DIRSERVER-748


On Fri, Oct 3, 2008 at 12:02 PM, Pierre-Arnaud Marcelot <pa@marcelot.net> wrote:
Hi,

I'm trying to use the 'release:perform' task on Studio.
I've released internally in my personal Maven repository the TLP pom version 14 and I've updated Studio's root pom to use this version.
I've setup my settings.xml file with the release profile (I'm releasing into a specific folder instead of apache's maven repo of course) and used it to run the release.

It worked for a few projects that got successfully deploy to my repo but it then failed on the LDAP Browser Core project.
Looks like it failed when generating the Javadoc... :(

The build log is attached to this mail.

Does anyone know who I can fix this?

Thanks,
Pierre-Arnaud


On Thu, Oct 2, 2008 at 2:13 PM, Felix Knecht <felixk@apache.org> wrote:
Pierre-Arnaud Marcelot schrieb:
> Guys,
>
> The "release:prepare" goal is working! ;) At last...
>
> Here are the few modifications I had to do to make it work:
>
>     * Exclude the 'test-integration-core' and 'test-integration-ui'
>       projects from the build (so they don't get released).
>     * Change the version of the studio-maven-plugin to a released one
>       (ie. 1.0.1).
>     * Change the '<preparationGoals>' in the configuration of the
>       release plugin to "<preparationGoals>clean studio:eclipse
>       install</preparationGoals>".
>
> I tested the generated jars and distribution and they are working very
> well.
>
> If everyone if ok with these modification, I'd like to apply them on
> trunk.

+1

> WDYT ?
>
> Unfortunately, I was not able to test the deployment using the
> "release:perform" goal because Studio's pom refers to TLP pom version
> 13 which does not allow us to change the remote repository.
> Maybe, we can release the TLP pom version 14, so I can try this.

+1

Felix
> WDYT ?
>
> Thanks,
> Pierre-Arnaud
>
> On Thu, Oct 2, 2008 at 1:49 PM, Pierre-Arnaud Marcelot
> <pa@marcelot.net <mailto:pa@marcelot.net>> wrote:
>
>     On Wed, Oct 1, 2008 at 7:19 PM, Stefan Seelmann
>     <seelmann@apache.org <mailto:seelmann@apache.org>> wrote:
>
>         We already have such profiles, they are called
>         integration-core and
>         integration-ui :-)
>
>
>     Yeah, it's true, but I'm talking about a profile in the root pom
>     that will include the 'test-integration-core' and
>     'test-integration-ui' projects.
>
>     By default, these 2 projects will be excluded from the build, and
>     they will be included only if you add this profile.
>
>     Regards,
>     Pierre-Arnaud
>
>



------=_Part_28599_11477645.1223039179038--