[jira] [Resolved] (GERONIMO-6441) remove unused genesis modules
[ https://issues.apache.org/jira/browse/GERONIMO-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved GERONIMO-6441. - Resolution: Fixed > remove unused genesis modules > - > > Key: GERONIMO-6441 > URL: https://issues.apache.org/jira/browse/GERONIMO-6441 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: buildsystem >Reporter: Mark Struberg >Assignee: Mark Struberg > > geronimo genesis contains a few modules which are not enabled since a long > time. We shall remove them from our SCM as they just cause confusion... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6441) remove unused genesis modules
[ https://issues.apache.org/jira/browse/GERONIMO-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596920#comment-13596920 ] Mark Struberg commented on GERONIMO-6441: - I now removed * genesis-skin * genesis-maven-plugin They were not contained in the last few releases it seems and were not even enabled in the section thus not available for snapshots neither. > remove unused genesis modules > - > > Key: GERONIMO-6441 > URL: https://issues.apache.org/jira/browse/GERONIMO-6441 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: buildsystem >Reporter: Mark Struberg >Assignee: Mark Struberg > > geronimo genesis contains a few modules which are not enabled since a long > time. We shall remove them from our SCM as they just cause confusion... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6441) remove unused genesis modules
Mark Struberg created GERONIMO-6441: --- Summary: remove unused genesis modules Key: GERONIMO-6441 URL: https://issues.apache.org/jira/browse/GERONIMO-6441 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: buildsystem Reporter: Mark Struberg Assignee: Mark Struberg geronimo genesis contains a few modules which are not enabled since a long time. We shall remove them from our SCM as they just cause confusion... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] [CANCELLED] Release genesis-2.1 and xbean-3.13
Txs for catching this! I gonna reroll after this has been fixed. It seems the 2 genesis modules you mentioned are not even in the section since quite some time. Thus I gonna delete them from SVN if noone objects. Btw, the whole genesis project seems to be in a very bad shape. It e.g. references a geronimo-genesis-skin in the site which does not exist! Gonna just drop it for now... LieGrue, strub > > From: Jarek Gawor >To: dev ; Mark Struberg >Sent: Friday, March 8, 2013 6:09 AM >Subject: Re: [VOTE] Release genesis-2.1 and xbean-3.13 > >Thank you for putting this all together! However, I did find a few problems: > >-1 for genesis. 1) geronimo-maven-plugin and geronimo-skip have >SNAPHOST parents. If these are no longer needed then we should drop >them from svn and not release them. 2) There is pluginRepository >defined which points to >http://people.apache.org/repo/m2-snapshot-repository which is no >longer in use. I think that can be removed all together or at least >changed to the nexus snapshot repository. > >-1 for xbean. In xbean I put in temporary repository/plugRepositry >entries for apache snapshots repository so that genesis snapshots >could be picked up (in the room pom.xml). Now that we are releasing >genesis, those two repository entires are not needed anymore. > >Thanks again, > >Jarek > >On Thu, Mar 7, 2013 at 3:53 PM, Mark Struberg wrote: >> Hi! >> >> I'd like to call a VOTE on genesis-2.1 and xbean-3.13. >> >> The Maven Staging Repo which contains both releases (xbean needs genesis): >> https://repository.apache.org/content/repositories/orgapachegeronimo-001/ >> >> >> SVN source tag for genesis: >> https://svn.apache.org/repos/asf/geronimo/genesis/tags/genesis-2.1/ >> >> SVN source tag for xbean: >> https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.13/ >> >> Source releases (plus hashes) are available under: >> https://repository.apache.org/content/repositories/orgapachegeronimo-001/org/apache/geronimo/genesis/genesis/2.1/ >> https://repository.apache.org/content/repositories/orgapachegeronimo-001/org/apache/xbean/xbean/3.13/ >> >> My PGP release key 2FDB81B1 is available at >> https://svn.apache.org/repos/asf/geronimo/KEYS >> >> Kevan is so kind and will collect the JIRA bits (I have absolutely no >> oversight about how to gather all the needed infos there). >> >> The VOTE will be open for 72 hours. >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 veto (and reason why) >> >> >> There is a small (and old) guide for testing staged releases: >> http://maven.apache.org/guides/development/guide-testing-releases.html >> >> In practice it's as easy as adding a profile to your ~/.m2/settings.xml >> which contains the with the URL pointing to the staging repo as >> posted above. >> >> >> txs and LieGrue, >> strub > > >
Re: [VOTE] Release genesis-2.1 and xbean-3.13
Thank you for putting this all together! However, I did find a few problems: -1 for genesis. 1) geronimo-maven-plugin and geronimo-skip have SNAPHOST parents. If these are no longer needed then we should drop them from svn and not release them. 2) There is pluginRepository defined which points to http://people.apache.org/repo/m2-snapshot-repository which is no longer in use. I think that can be removed all together or at least changed to the nexus snapshot repository. -1 for xbean. In xbean I put in temporary repository/plugRepositry entries for apache snapshots repository so that genesis snapshots could be picked up (in the room pom.xml). Now that we are releasing genesis, those two repository entires are not needed anymore. Thanks again, Jarek On Thu, Mar 7, 2013 at 3:53 PM, Mark Struberg wrote: > Hi! > > I'd like to call a VOTE on genesis-2.1 and xbean-3.13. > > The Maven Staging Repo which contains both releases (xbean needs genesis): > https://repository.apache.org/content/repositories/orgapachegeronimo-001/ > > > SVN source tag for genesis: > https://svn.apache.org/repos/asf/geronimo/genesis/tags/genesis-2.1/ > > SVN source tag for xbean: > https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.13/ > > Source releases (plus hashes) are available under: > https://repository.apache.org/content/repositories/orgapachegeronimo-001/org/apache/geronimo/genesis/genesis/2.1/ > https://repository.apache.org/content/repositories/orgapachegeronimo-001/org/apache/xbean/xbean/3.13/ > > My PGP release key 2FDB81B1 is available at > https://svn.apache.org/repos/asf/geronimo/KEYS > > Kevan is so kind and will collect the JIRA bits (I have absolutely no > oversight about how to gather all the needed infos there). > > The VOTE will be open for 72 hours. > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 veto (and reason why) > > > There is a small (and old) guide for testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > In practice it's as easy as adding a profile to your ~/.m2/settings.xml > which contains the with the URL pointing to the staging repo as > posted above. > > > txs and LieGrue, > strub
Re: [VOTE] Release genesis-2.1 and xbean-3.13
Thx Mark 2013/3/7 Mark Struberg > Hi! > > I'd like to call a VOTE on genesis-2.1 and xbean-3.13. > > The Maven Staging Repo which contains both releases (xbean needs genesis): > https://repository.apache.org/content/repositories/orgapachegeronimo-001/ > > > SVN source tag for genesis: > https://svn.apache.org/repos/asf/geronimo/genesis/tags/genesis-2.1/ > > SVN source tag for xbean: > https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.13/ > > Source releases (plus hashes) are available under: > > https://repository.apache.org/content/repositories/orgapachegeronimo-001/org/apache/geronimo/genesis/genesis/2.1/ > > https://repository.apache.org/content/repositories/orgapachegeronimo-001/org/apache/xbean/xbean/3.13/ > > My PGP release key 2FDB81B1 is available at > https://svn.apache.org/repos/asf/geronimo/KEYS > > Kevan is so kind and will collect the JIRA bits (I have absolutely no > oversight about how to gather all the needed infos there). > > The *VOTE* will be open for 72 hours. > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 veto (and reason why) > > > There is a small (and old) guide for testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > In practice it's as easy as adding a profile to your ~/.m2/settings.xml > which contains the with the URL pointing to the staging repo > as posted above. > > > txs and LieGrue, > strub > -- Jean-Louis
[VOTE] Release genesis-2.1 and xbean-3.13
Hi! I'd like to call a VOTE on genesis-2.1 and xbean-3.13. The Maven Staging Repo which contains both releases (xbean needs genesis): https://repository.apache.org/content/repositories/orgapachegeronimo-001/ SVN source tag for genesis: https://svn.apache.org/repos/asf/geronimo/genesis/tags/genesis-2.1/ SVN source tag for xbean: https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.13/ Source releases (plus hashes) are available under: https://repository.apache.org/content/repositories/orgapachegeronimo-001/org/apache/geronimo/genesis/genesis/2.1/ https://repository.apache.org/content/repositories/orgapachegeronimo-001/org/apache/xbean/xbean/3.13/ My PGP release key 2FDB81B1 is available at https://svn.apache.org/repos/asf/geronimo/KEYS Kevan is so kind and will collect the JIRA bits (I have absolutely no oversight about how to gather all the needed infos there). The VOTE will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 veto (and reason why) There is a small (and old) guide for testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html In practice it's as easy as adding a profile to your ~/.m2/settings.xml which contains the with the URL pointing to the staging repo as posted above. txs and LieGrue, strub
xbean trunk temporarily defunct
Hi folks! Due to releasing genesis (where the cleanup was long time overdue) and xbean in one go, I had to upgrade the parent pom of xbean to genesis-2.1 which is contained in the same staging repo. As this is not yet released, the CI for xbean is currently defunct until the release gets pushed. If you like to build it locally, then please add the staging repo [1] of the VOTE I gonna send out in a few minutes. LieGrue, strub [1] https://repository.apache.org/content/repositories/orgapachegeronimo-001/
Re: genesis + xbean release train
On Mar 7, 2013, at 1:56 PM, Mark Struberg wrote: > Hi folks! > > If noone objects, then I gonna roll a genesis + xbean release tonight into a > single staging area. Sounds good to me. --kevan
genesis + xbean release train
Hi folks! If noone objects, then I gonna roll a genesis + xbean release tonight into a single staging area. LieGrue, strub
interceptors-1.2 specification
Hi folks! Has there been some work done already on the interceptors-1.2 specification? We gonna need this for EJB-3.2 and CDI-1.1. Marina posted a PFD. I did a quick scan through and it looks fine. Not sure when I can find a bit time for it, but I'm interested in helping with it. LieGrue, strub
