Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 68418 invoked from network); 18 Mar 2011 14:18:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Mar 2011 14:18:45 -0000 Received: (qmail 93455 invoked by uid 500); 18 Mar 2011 14:18:45 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 93409 invoked by uid 500); 18 Mar 2011 14:18:45 -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 93402 invoked by uid 99); 18 Mar 2011 14:18:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Mar 2011 14:18:45 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of pajbam@gmail.com designates 74.125.82.178 as permitted sender) Received: from [74.125.82.178] (HELO mail-wy0-f178.google.com) (74.125.82.178) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Mar 2011 14:18:37 +0000 Received: by wyj26 with SMTP id 26so4424369wyj.37 for ; Fri, 18 Mar 2011 07:18:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:from:mime-version:content-type:subject :date:in-reply-to:to:references:message-id:x-mailer; bh=V305U9n96LmLgOasCxpijsosFLh2QScxaNonixUEl7w=; b=DQDxdp5fuI5uKQcb852h2/QaWHBK90ILp8/ORAug/YzErG2SdiaIkgS/IREwH0oM8e Y/OSRmigbZu/fQV9UYANO9MYT3JpypGQtC3NSGI1Y6VpMywQxiQ0PYy16tXjMGBgVY8E uEJjYzW/I4+C9sE6bFBGHZy6CfkWlLivLa/7k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer; b=MLzstT8woGJECy0ojKxCJbQLoXx8KTiUguiK4Z+B7mDD4U0ydMhpkFVrarptRrR+62 IvaBqmEtOuQKMZcRPVHPt42U5xpBPKjuMVG5MbiagBwaFJRVHTtLHua+Q59SeFzac3wx VU87pOvzbIuYZZFw7WMPeSQHic2cV1pz1clmI= Received: by 10.227.147.20 with SMTP id j20mr1284593wbv.159.1300457897081; Fri, 18 Mar 2011 07:18:17 -0700 (PDT) Received: from [192.168.0.52] (lon92-10-78-226-4-211.fbx.proxad.net [78.226.4.211]) by mx.google.com with ESMTPS id o6sm1390111wbo.20.2011.03.18.07.18.15 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Mar 2011 07:18:16 -0700 (PDT) Sender: Pierre-Arnaud Marcelot From: Pierre-Arnaud Marcelot Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: multipart/alternative; boundary=Apple-Mail-4-28146948 Subject: Re: Pb with mvn eclipse:eclipse and -Dintegration Date: Fri, 18 Mar 2011 15:18:13 +0100 In-Reply-To: <4D83660D.5000405@gmail.com> To: "Apache Directory Developers List" References: <4D83660D.5000405@gmail.com> Message-Id: <40F87FF7-4AB0-4D3C-B747-DEDBFE514B44@marcelot.net> X-Mailer: Apple Mail (2.1082) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-4-28146948 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Emmanuel, On 18 mars 2011, at 15:02, Emmanuel Lecharny wrote: > Hi guys, >=20 > I'm facing some painful problem with the last modifications made on = the build system : as the shared-integ is now depending on the = -Dintegration profile to be present to be executed, if you forget to = provide this profile when doing a mvn eclipse:eclipse, the .classpath is = not generated correctly. >=20 > So now, to get all the module correctly imported in eclipse, you have = to do : > mvn eclipse:eclipse -Dintegration >=20 > Although I understand that it was mandatory to add this profile to get = the site generated and the release to be done, I think there are two = problems with this approach : > - first, no one has been informed about this modification This has been discussed in this thread on the ML [1]. You probably = didn't see it. > - second, fixing an issue by creating a new one is not a solution. I don't think it created an issue, it's just something you need to know = before generating Eclipse files. Now, I understand it can become a problem when you're used to doing = something else for a long time, and having to specify to specify a = specific profile can also be counter-intuitive. > I'm not blaming anyone here, I just think that when someone is facing = such an issue, creating a JIRA is necessary to get everyone informed = about the problem, and giving someone an opportunity to track the = problem and eventually fix it. I think we can rollback on the specific profile creation and go back = with old system where everything was generated without the need to add a = specific profile. We'd then have to try to find another fix for the site generation issue = which will block further releases. > I'll create the JIRA now. >=20 > Thanks ! >=20 Regards, Pierre-Arnaud [1] - http://directory.markmail.org/thread/6m66jithffwj7kja= --Apple-Mail-4-28146948 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi = Emmanuel,

On 18 mars 2011, at 15:02, Emmanuel Lecharny = wrote:

Hi guys,

I'm facing some painful problem with = the last modifications made on the build system : as the shared-integ is = now depending on the -Dintegration profile to be present to be executed, = if you forget to provide this profile when doing a mvn eclipse:eclipse, = the .classpath is not generated correctly.

So now, to get all the = module correctly imported in eclipse, you have to do :
mvn = eclipse:eclipse -Dintegration

Although I understand that it was = mandatory to add this profile to get the site generated and the release = to be done, I think there are two problems with this approach :
- = first, no one has been informed about this = modification

This has been = discussed in this thread on the ML [1]. You probably didn't see = it.

- second, fixing an issue by = creating a new one is not a = solution.

I don't think it = created an issue, it's just something you need to know before generating = Eclipse files.
Now, I understand it can become a problem when = you're used to doing something else for a long time, and having to = specify to specify a specific profile can also be = counter-intuitive.

I'm not = blaming anyone here, I just think that when someone is facing such an = issue, creating a JIRA is necessary to get everyone informed about the = problem, and giving someone an opportunity to track the problem and = eventually fix it.

I = think we can rollback on the specific profile creation and go back with = old system where everything was generated without the need to add a = specific profile.
We'd then have to try to find another fix = for the site generation issue which will block further = releases.

I'll create the = JIRA now.

Thanks = !


Regards,
Pierre-= Arnaud

= --Apple-Mail-4-28146948--