You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@empire-db.apache.org by Rainer Döbele <do...@esteam.de> on 2010/04/24 23:30:39 UTC
questions regarding rc3 and building the assembly
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
age
[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?
Regards
Rainer
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:
> http://svn.apache.org/viewvc/incubator/empire-db/tags/apache-empire-db-
> 2.0.6-incubating-rc3/CHANGELOG.txt?view=co
>
> Subversion tag:
> https://svn.apache.org/repos/asf/incubator/empire-db/tags/apache-
> empire-db-2.0.6-incubating-rc3
>
> Maven staging repository:
> https://repository.apache.org/content/repositories/orgapacheempire-db-
> 005/
>
> Distribution files are located here
> http://people.apache.org/~francisdb/empire-db/
>
> Rat report for the tag is available here:
> http://people.apache.org/~francisdb/empire-db/rat.txt
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
> --
> http://www.somatik.be
> Microsoft gives you windows, Linux gives you the whole house.
Re: questions regarding rc3 and building the assembly
Posted by Francis De Brabandere <fr...@gmail.com>.
The thing here is that if we release an other rc version maven will
not update your local repository. So after testing you should remove
~/.m2/repository/org/apache/empire-db
On Sat, Apr 24, 2010 at 11:40 PM, Benjamin Venditti
<be...@arcor.de> wrote:
> hi rainer,
>
> here is a snippet from the <profiles> tag from my settings.xml
>
> -------------SNIP-------------
>
> <profile>
> <id>empire-staging</id>
> <repositories>
> <repository>
> <id>empire-staging</id>
> <name>empire-DB staging repository</name>
>
> <url>https://repository.apache.org/content/repositories/orgapacheempire-db-005/</url>
> </repository>
> </repositories>
>
> <pluginRepositories>
> <pluginRepository>
> <id>empire-staging</id>
> <name>empire-DB staging repository</name>
>
> <url>https://repository.apache.org/content/repositories/orgapacheempire-db-005/</url>
> </pluginRepository>
> </pluginRepositories>
>
> </profile>
>
> -----------SNAP---------
>
>
> Am 24.04.2010 23:30, schrieb Rainer Döbele:
>>
>> 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
>> age
>> [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?
>>
>> Regards
>> Rainer
>>
>>
>> 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:
>>> http://svn.apache.org/viewvc/incubator/empire-db/tags/apache-empire-db-
>>> 2.0.6-incubating-rc3/CHANGELOG.txt?view=co
>>>
>>> Subversion tag:
>>> https://svn.apache.org/repos/asf/incubator/empire-db/tags/apache-
>>> empire-db-2.0.6-incubating-rc3
>>>
>>> Maven staging repository:
>>> https://repository.apache.org/content/repositories/orgapacheempire-db-
>>> 005/
>>>
>>> Distribution files are located here
>>> http://people.apache.org/~francisdb/empire-db/
>>>
>>> Rat report for the tag is available here:
>>> http://people.apache.org/~francisdb/empire-db/rat.txt
>>>
>>> Vote open for 72 hours.
>>>
>>> [ ] +1
>>> [ ] +0
>>> [ ] -1
>>>
>>>
>>> --
>>> http://www.somatik.be
>>> Microsoft gives you windows, Linux gives you the whole house.
>
>
--
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.
re: questions regarding rc3 and building the assembly
Posted by Rainer Döbele <do...@esteam.de>.
Thanks Benjamin,
that was a quick answer - although I did switch off my computer afterwards and I wasn't online Sunday.
Regards
Rainer
Benjamin Venditti wrote:
> Re: questions regarding rc3 and building the assembly
>
> hi rainer,
>
> here is a snippet from the <profiles> tag from my settings.xml
>
> -------------SNIP-------------
>
> <profile>
> <id>empire-staging</id>
> <repositories>
> <repository>
> <id>empire-staging</id>
> <name>empire-DB staging repository</name>
>
> <url>https://repository.apache.org/content/repositories/orgapacheempire-
> db-005/</url>
> </repository>
> </repositories>
>
> <pluginRepositories>
> <pluginRepository>
> <id>empire-staging</id>
> <name>empire-DB staging repository</name>
>
> <url>https://repository.apache.org/content/repositories/orgapacheempire-
> db-005/</url>
> </pluginRepository>
> </pluginRepositories>
>
> </profile>
>
> -----------SNAP---------
>
>
> Am 24.04.2010 23:30, schrieb Rainer Döbele:
> > 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
> > age
> > [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?
> >
> > Regards
> > Rainer
> >
> >
> > 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:
> >> http://svn.apache.org/viewvc/incubator/empire-db/tags/apache-empire-
> db-
> >> 2.0.6-incubating-rc3/CHANGELOG.txt?view=co
> >>
> >> Subversion tag:
> >> https://svn.apache.org/repos/asf/incubator/empire-db/tags/apache-
> >> empire-db-2.0.6-incubating-rc3
> >>
> >> Maven staging repository:
> >> https://repository.apache.org/content/repositories/orgapacheempire-
> db-
> >> 005/
> >>
> >> Distribution files are located here
> >> http://people.apache.org/~francisdb/empire-db/
> >>
> >> Rat report for the tag is available here:
> >> http://people.apache.org/~francisdb/empire-db/rat.txt
> >>
> >> Vote open for 72 hours.
> >>
> >> [ ] +1
> >> [ ] +0
> >> [ ] -1
> >>
> >>
> >> --
> >> http://www.somatik.be
> >> Microsoft gives you windows, Linux gives you the whole house.
Re: questions regarding rc3 and building the assembly
Posted by Benjamin Venditti <be...@arcor.de>.
hi rainer,
here is a snippet from the <profiles> tag from my settings.xml
-------------SNIP-------------
<profile>
<id>empire-staging</id>
<repositories>
<repository>
<id>empire-staging</id>
<name>empire-DB staging repository</name>
<url>https://repository.apache.org/content/repositories/orgapacheempire-db-005/</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>empire-staging</id>
<name>empire-DB staging repository</name>
<url>https://repository.apache.org/content/repositories/orgapacheempire-db-005/</url>
</pluginRepository>
</pluginRepositories>
</profile>
-----------SNAP---------
Am 24.04.2010 23:30, schrieb Rainer Döbele:
> 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
> age
> [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?
>
> Regards
> Rainer
>
>
> 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:
>> http://svn.apache.org/viewvc/incubator/empire-db/tags/apache-empire-db-
>> 2.0.6-incubating-rc3/CHANGELOG.txt?view=co
>>
>> Subversion tag:
>> https://svn.apache.org/repos/asf/incubator/empire-db/tags/apache-
>> empire-db-2.0.6-incubating-rc3
>>
>> Maven staging repository:
>> https://repository.apache.org/content/repositories/orgapacheempire-db-
>> 005/
>>
>> Distribution files are located here
>> http://people.apache.org/~francisdb/empire-db/
>>
>> Rat report for the tag is available here:
>> http://people.apache.org/~francisdb/empire-db/rat.txt
>>
>> Vote open for 72 hours.
>>
>> [ ] +1
>> [ ] +0
>> [ ] -1
>>
>>
>> --
>> http://www.somatik.be
>> Microsoft gives you windows, Linux gives you the whole house.
Re: questions regarding rc3 and building the assembly
Posted by Francis De Brabandere <fr...@gmail.com>.
On Mon, Apr 26, 2010 at 8:58 AM, Rainer Döbele <do...@esteam.de> wrote:
> Hi Francis,
>
> that's fine with me.
> Sorry that I had to bother you with that - and that I did not notice before.
> But rather now than later on the incubator PMC.
Totally agree, I'd rather have some rc release cycles here as they are
shorter...
Should have the time this evening to cut rc4
>
> Regards
> Rainer
>
>
> Francis De Brabandere wrote:
>> Re: questions regarding rc3 and building the assembly
>>
>> >> 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?
>> >
>> > This is unintentional, I'll have a look at it.
>>
>> I added both javadoc jars for empire-db and empire-db-struts2. Try a
>> "mvn clean install" on the dist module.
>>
>> This how the new distribution should look like:
>>
>> /bin/empire-db-2.0.6-incubating.jar
>> /bin/empire-db-struts2-2.0.6-incubating.jar
>> /doc/empire-db-2.0.6-incubating-javadoc.jar
>> /doc/empire-db-struts2-2.0.6-incubating-javadoc.jar
>> /src/...
>> *notes files
>>
>> Let me know if this is ok then I cut a new release... hopefully the last
>> one.
>>
>> Cheers,
>> Francis
>>
>> >
>> >>
>> >> Regards
>> >> Rainer
>> >>
>> >>
>> >> 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:
>> >>> http://svn.apache.org/viewvc/incubator/empire-db/tags/apache-empire-
>> db-
>> >>> 2.0.6-incubating-rc3/CHANGELOG.txt?view=co
>> >>>
>> >>> Subversion tag:
>> >>> https://svn.apache.org/repos/asf/incubator/empire-db/tags/apache-
>> >>> empire-db-2.0.6-incubating-rc3
>> >>>
>> >>> Maven staging repository:
>> >>> https://repository.apache.org/content/repositories/orgapacheempire-
>> db-
>> >>> 005/
>> >>>
>> >>> Distribution files are located here
>> >>> http://people.apache.org/~francisdb/empire-db/
>> >>>
>> >>> Rat report for the tag is available here:
>> >>> http://people.apache.org/~francisdb/empire-db/rat.txt
>> >>>
>> >>> Vote open for 72 hours.
>> >>>
>> >>> [ ] +1
>> >>> [ ] +0
>> >>> [ ] -1
>> >>>
>> >>>
>> >>> --
>> >>> http://www.somatik.be
>> >>> Microsoft gives you windows, Linux gives you the whole house.
>> >>
>> >
>> >
>> >
>> > --
>> > http://www.somatik.be
>> > Microsoft gives you windows, Linux gives you the whole house.
>> >
>>
>>
>>
>> --
>> http://www.somatik.be
>> Microsoft gives you windows, Linux gives you the whole house.
>
--
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.
re: questions regarding rc3 and building the assembly
Posted by Rainer Döbele <do...@esteam.de>.
Hi Francis,
that's fine with me.
Sorry that I had to bother you with that - and that I did not notice before.
But rather now than later on the incubator PMC.
Regards
Rainer
Francis De Brabandere wrote:
> Re: questions regarding rc3 and building the assembly
>
> >> 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?
> >
> > This is unintentional, I'll have a look at it.
>
> I added both javadoc jars for empire-db and empire-db-struts2. Try a
> "mvn clean install" on the dist module.
>
> This how the new distribution should look like:
>
> /bin/empire-db-2.0.6-incubating.jar
> /bin/empire-db-struts2-2.0.6-incubating.jar
> /doc/empire-db-2.0.6-incubating-javadoc.jar
> /doc/empire-db-struts2-2.0.6-incubating-javadoc.jar
> /src/...
> *notes files
>
> Let me know if this is ok then I cut a new release... hopefully the last
> one.
>
> Cheers,
> Francis
>
> >
> >>
> >> Regards
> >> Rainer
> >>
> >>
> >> 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:
> >>> http://svn.apache.org/viewvc/incubator/empire-db/tags/apache-empire-
> db-
> >>> 2.0.6-incubating-rc3/CHANGELOG.txt?view=co
> >>>
> >>> Subversion tag:
> >>> https://svn.apache.org/repos/asf/incubator/empire-db/tags/apache-
> >>> empire-db-2.0.6-incubating-rc3
> >>>
> >>> Maven staging repository:
> >>> https://repository.apache.org/content/repositories/orgapacheempire-
> db-
> >>> 005/
> >>>
> >>> Distribution files are located here
> >>> http://people.apache.org/~francisdb/empire-db/
> >>>
> >>> Rat report for the tag is available here:
> >>> http://people.apache.org/~francisdb/empire-db/rat.txt
> >>>
> >>> Vote open for 72 hours.
> >>>
> >>> [ ] +1
> >>> [ ] +0
> >>> [ ] -1
> >>>
> >>>
> >>> --
> >>> http://www.somatik.be
> >>> Microsoft gives you windows, Linux gives you the whole house.
> >>
> >
> >
> >
> > --
> > http://www.somatik.be
> > Microsoft gives you windows, Linux gives you the whole house.
> >
>
>
>
> --
> http://www.somatik.be
> Microsoft gives you windows, Linux gives you the whole house.
Re: questions regarding rc3 and building the assembly
Posted by Francis De Brabandere <fr...@gmail.com>.
>> 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?
>
> This is unintentional, I'll have a look at it.
I added both javadoc jars for empire-db and empire-db-struts2. Try a
"mvn clean install" on the dist module.
This how the new distribution should look like:
/bin/empire-db-2.0.6-incubating.jar
/bin/empire-db-struts2-2.0.6-incubating.jar
/doc/empire-db-2.0.6-incubating-javadoc.jar
/doc/empire-db-struts2-2.0.6-incubating-javadoc.jar
/src/...
*notes files
Let me know if this is ok then I cut a new release... hopefully the last one.
Cheers,
Francis
>
>>
>> Regards
>> Rainer
>>
>>
>> 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:
>>> http://svn.apache.org/viewvc/incubator/empire-db/tags/apache-empire-db-
>>> 2.0.6-incubating-rc3/CHANGELOG.txt?view=co
>>>
>>> Subversion tag:
>>> https://svn.apache.org/repos/asf/incubator/empire-db/tags/apache-
>>> empire-db-2.0.6-incubating-rc3
>>>
>>> Maven staging repository:
>>> https://repository.apache.org/content/repositories/orgapacheempire-db-
>>> 005/
>>>
>>> Distribution files are located here
>>> http://people.apache.org/~francisdb/empire-db/
>>>
>>> Rat report for the tag is available here:
>>> http://people.apache.org/~francisdb/empire-db/rat.txt
>>>
>>> Vote open for 72 hours.
>>>
>>> [ ] +1
>>> [ ] +0
>>> [ ] -1
>>>
>>>
>>> --
>>> http://www.somatik.be
>>> Microsoft gives you windows, Linux gives you the whole house.
>>
>
>
>
> --
> http://www.somatik.be
> Microsoft gives you windows, Linux gives you the whole house.
>
--
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.
Re: questions regarding rc3 and building the assembly
Posted by Francis De Brabandere <fr...@gmail.com>.
On Sat, Apr 24, 2010 at 11:30 PM, Rainer Döbele <do...@esteam.de> wrote:
> 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
> age
> [INFO] [gpg:sign {execution: default}]
> GPG Passphrase: *
>
> Do you know what GPG Passphrase it is asking for?
This is for signing the release, but I don't think you need the
apache-release profile for building the distribution. There's a link
on the the 'release process' wiki page that shows you how to set this
up.
>
> 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?
This is unintentional, I'll have a look at it.
>
> Regards
> Rainer
>
>
> 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:
>> http://svn.apache.org/viewvc/incubator/empire-db/tags/apache-empire-db-
>> 2.0.6-incubating-rc3/CHANGELOG.txt?view=co
>>
>> Subversion tag:
>> https://svn.apache.org/repos/asf/incubator/empire-db/tags/apache-
>> empire-db-2.0.6-incubating-rc3
>>
>> Maven staging repository:
>> https://repository.apache.org/content/repositories/orgapacheempire-db-
>> 005/
>>
>> Distribution files are located here
>> http://people.apache.org/~francisdb/empire-db/
>>
>> Rat report for the tag is available here:
>> http://people.apache.org/~francisdb/empire-db/rat.txt
>>
>> Vote open for 72 hours.
>>
>> [ ] +1
>> [ ] +0
>> [ ] -1
>>
>>
>> --
>> http://www.somatik.be
>> Microsoft gives you windows, Linux gives you the whole house.
>
--
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.