incubator-empire-db-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Döbele <>
Subject questions regarding rc3 and building the assembly
Date Sat, 24 Apr 2010 21:30:39 GMT
Hi Francis

again, I have a couple of questions / problems and I am probably just to stupid again to get
it right.

First when I get the latest sources and I try to build the assembly using "mvn clean install
-Papache-release" I get the following:
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] [enforcer:enforce {execution: enforce-versions}]
[INFO] [source:jar {execution: attach-sources}]
[INFO] [javadoc:jar {execution: attach-javadocs}]
[INFO] Not executing Javadoc as the project is not a Java classpath-capable pack
[INFO] [gpg:sign {execution: default}]
GPG Passphrase: *

Do you know what GPG Passphrase it is asking for?

Also you say that we should add the stating repository to our Maven settings. I know I could
possibly Google that, but can you tell me how to add the staging repository to my settings.xml
(In know where the file is, I just need to know what exactly to add).

Finally I noticed, that in our previous release we had the apidocs in the root folder.
In rc3 they are not supplied any more.
Is it your intention not to supply the apidocs this way?


Francis De Brabandere wrote:
> re: [VOTE] Release Apache Empire-db 2.0.6-incubating (rc3)
> Hi,
> We have just prepared the third 2.0.6-incubating release candidate
> and we are now looking for approval of the PMC to publish the release.
> Once the community approves the release we will have a second binding
> release round for IPMC members.
> These are the major change from our previous 2.0.5-incubating release:
> - Code-Generator allows generation of Data Model code files for
> existing databases
> - Maven plugin for DB-Code-Generator
> - New example to demonstrate interoperability between Empire-db and
> Spring
> - Provided jars are now OSGi compatible
> These are the changes since previous rc1:
> - Fixed progress data type issue (EMPIREDB-76)
> - Fixed codegen app + added tests
> - Fixed missing commons-logging dependency making war's unusable
> These are the changes since previous rc2:
> - Correct distribution module version
> - Decoupled the codegen example as we have the chicken-egg problem
> there
> Changelog:
> 2.0.6-incubating-rc3/CHANGELOG.txt?view=co
> Subversion tag:
> empire-db-2.0.6-incubating-rc3
> Maven staging repository:
> 005/
> Distribution files are located here
> Rat report for the tag is available here:
> Vote open for 72 hours.
> [ ] +1
> [ ] +0
> [ ] -1
> --
> Microsoft gives you windows, Linux gives you the whole house.

View raw message