Return-Path: Delivered-To: apmail-incubator-ace-dev-archive@minotaur.apache.org Received: (qmail 89282 invoked from network); 11 Dec 2009 14:07:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Dec 2009 14:07:39 -0000 Received: (qmail 36086 invoked by uid 500); 11 Dec 2009 14:07:39 -0000 Delivered-To: apmail-incubator-ace-dev-archive@incubator.apache.org Received: (qmail 36051 invoked by uid 500); 11 Dec 2009 14:07:39 -0000 Mailing-List: contact ace-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ace-dev@incubator.apache.org Delivered-To: mailing list ace-dev@incubator.apache.org Received: (qmail 36041 invoked by uid 99); 11 Dec 2009 14:07:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Dec 2009 14:07:39 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tonit.com@googlemail.com designates 209.85.212.177 as permitted sender) Received: from [209.85.212.177] (HELO mail-vw0-f177.google.com) (209.85.212.177) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Dec 2009 14:07:37 +0000 Received: by vws7 with SMTP id 7so229370vws.22 for ; Fri, 11 Dec 2009 06:07:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=72PgHU4UKIP3QoLuQ8/ImNyPCtCpIDTv1LDPtaTjiCM=; b=sf+AfRcoA0hvDDOvBGQWv/8OJQRSAFZXeoNXf0rOvISG3K3XkG8pkTw+PTplzGR/38 2YL11gRGGpi3dcHFvIdqd+vTYHUsB60HqyVujTn+9qOmMtZSx0WehaSrevkxDHMT6pm4 pVk8UpVlNAgSL2slq8bXeFcRlT/R+u+ia3e8s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=r11tHKf5b6fzTqsdsS7b3jvUGGWII/li/efd4W7EeZ2E+lol6SrwopOmkgNb9tN9zU rdzOx1NDjUYkIjsBfMAaZf9VroUXFKtsqE6MJZc+ZhXhhv6XhJDJF1pQFb6UkR8IR1jk xF2peBPkDUFnXcQ/xyO/+PzihplzvDbduEUuY= MIME-Version: 1.0 Sender: tonit.com@googlemail.com Received: by 10.220.125.7 with SMTP id w7mr220235vcr.74.1260540435856; Fri, 11 Dec 2009 06:07:15 -0800 (PST) In-Reply-To: References: Date: Fri, 11 Dec 2009 15:07:15 +0100 X-Google-Sender-Auth: 72beee8a61090807 Message-ID: Subject: Re: Status Mavenization of ACE From: Toni Menzel To: ace-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=001636d34701e77d83047a7470db --001636d34701e77d83047a7470db Content-Type: text/plain; charset=ISO-8859-1 my fault. i did a renaming and.. well did not clean my own repo to try. thanks. willl fix asap. (..impl does not exist anymore) On Fri, Dec 11, 2009 at 3:01 PM, Marcel Offermans < marcel.offermans@luminis.nl> wrote: > Hi all, > > This morning I tried a "fresh" Maven build (mvn clean install) and I > encountered an issue: > > Downloading: > http://repository.apache.org/snapshots/org/apache/ace/ace-repository-impl/0.8.0-SNAPSHOT/ace-repository-impl-0.8.0-SNAPSHOT.jar > [INFO] Unable to find resource > 'org.apache.ace:ace-repository-impl:jar:0.8.0-SNAPSHOT' in repository > apache.snapshots (http://repository.apache.org/snapshots) > [INFO] snapshot org.apache.ace:ace-log-store:0.8.0-SNAPSHOT: checking for > updates from apache.snapshots > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Failed to resolve artifact. > > Missing: > ---------- > 1) org.apache.ace:ace-repository-impl:jar:0.8.0-SNAPSHOT > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.ace > -DartifactId=ace-repository-impl -Dversion=0.8.0-SNAPSHOT -Dpackaging=jar > -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.apache.ace > -DartifactId=ace-repository-impl -Dversion=0.8.0-SNAPSHOT -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > > Path to dependency: > 1) org.apache.ace:ace-client-repository-impl:bundle:0.8.0-SNAPSHOT > 2) org.apache.ace:ace-repository-impl:jar:0.8.0-SNAPSHOT > > ---------- > 1 required artifact is missing. > > for artifact: > org.apache.ace:ace-client-repository-impl:bundle:0.8.0-SNAPSHOT > > from the specified remote repositories: > apache.snapshots (http://repository.apache.org/snapshots), > central (http://repo1.maven.org/maven2) > > On Dec 10, 2009, at 21:43 , Toni Menzel wrote: > > > Today i managed try out some thoughts on how to do the ACE Target story > > (used & loved in the ant build version). > > Basically those target definitions are sets of ace bundles and some extra > > components (like dependencymanager & configadmin etc.) > > The idea behind these targets is that they are indeed preconfigured sets of > artifacts (in this case bundles + configuration) that can be easily run. > Having a collection of these available really helps people get started > (after building they should be able to run, with one single command, a > server, a target, etc.). > > Eventually, the definition of what goes to a target is something we want to > be able to import into ACE too, so we can self-host our own targets. Having > such a definition in a format that works for Maven, Pax Runner and ACE would > be great. > > > Because this is also a very good way to test our bundles (using pax > exam), i > > was looking for a way to > > - reuse the maven infrastructure > > - reuse this definition as much as possible for different scenarios > > Agreed, doing integration tests means defining such targets and running > tests against them. To optimize the speed of such tests, one can decide to > define custom targets with just the right artifacts to run those tests. Here > I see a lot of synergy between Pax Exam, running tests and ACE, provisioning > the right artifacts. Running tests in a framework that keeps running but > simply gets reconfigured test after test is an interesting direction to go > in. > > > With this, i think it is pretty easy to continue stacking together the > > target definition(s), running "tests" (currently it just checks if every > > bundle resolves+starts), interpreting the possible error log and fix BND > > settings as appropriate. > > > One more word on the ace-target-devgateway stufff: > > currently there is just the bundlelist (in pom), but i am playing with > > embedding & extracting the default settings (as before in those "conf" > > folders) in them as well. Not sure how this turns out, yet. > > One direction we could explore here is to start using Auto Configuration > for this. Part of this specification is the XML format in which > configuration data is supplied. I think I even might still have some code > lying around to convert normal property files into this XML format. > > Greetings, Marcel > > -- Toni Menzel Independent Software Developer Professional Profile: http://okidokiteam.com toni@okidokiteam.com http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. --001636d34701e77d83047a7470db--