You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by David Blevins <da...@gmail.com> on 2013/01/14 21:27:58 UTC
SVN Reorg
With the SVN changes regarding openejb->tomee renaming, I wondered if we wanted to take the opportunity to move to a more standard SVN layout.
Right now we have a "trunk" module with a ton of things in it:
$ svn list http://svn.apache.org/repos/asf/tomee/trunk/
.gitignore
STATUS.txt
camel/
colossus/
graduation-resolution.txt
javaee-api/
openejb/
openejb-eclipse/
openejb-eclipse-plugin/
patched-libraries/
presentations/
sandbox/
Having "sandbox" and "presentations" things like that under trunk is very odd. We've sort of lived with it and it's not a big deal, but we developers know the actual trunk is the "openejb" module.
Do we want to start moving to a more standard layout? Something like:
For TomEE/OpenEJB (i.e. what is currently at asf/tomee/trunk/openejb/):
- http://svn.apache.org/repos/asf/tomee/tomee/trunk/
- http://svn.apache.org/repos/asf/tomee/tomee/tags/
- http://svn.apache.org/repos/asf/tomee/tomee/branches/
For javaee-api:
- http://svn.apache.org/repos/asf/tomee/javaee-api/trunk/
- http://svn.apache.org/repos/asf/tomee/javaee-api/tags/
- http://svn.apache.org/repos/asf/tomee/javaee-api/branches/
For Website (this already exists, just showing to see the consistency):
- http://svn.apache.org/repos/asf/tomee/site/trunk/
- http://svn.apache.org/repos/asf/tomee/site/branches/
Eclipse plugins:
- http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/trunk/
- http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/tags/
- http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/branches/
Everything that doesn't fit could likely go into sandbox possibly (no "trunk"):
- http://svn.apache.org/repos/asf/tomee/sandbox/
- http://svn.apache.org/repos/asf/tomee/sandbox/camel
- http://svn.apache.org/repos/asf/tomee/sandbox/colossus
- http://svn.apache.org/repos/asf/tomee/sandbox/release-tools
- ...
The 'presentations' folder could probably just get moved into the site:
- http://svn.apache.org/repos/asf/tomee/site/trunk/content/presentations/
Thoughts?
-David
Re: SVN Reorg
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
No special opinion on KarafEE.
But agree with a restructured repo.
David's proposal is a good starting point. We can still adapt small things
in the future.
Let's go for it if nobody is against.
Jean-Louis
2013/1/15 Romain Manni-Bucau <rm...@gmail.com>
> i'm ok moving it elsewhere but ok to remove it too
>
> it sounds useful but nobody is here to maintain it so i think we have to
> choose
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/1/15 Jonathan Gallimore <jo...@gmail.com>
>
> > I think the restructure as David suggests sounds good. I quite like the
> > idea of moving the presentations to the website instead.
> >
> > I agree that keeping the Maven plugin with the rest of the build makes
> > sense.
> >
> > KarafEE - are you thinking of splitting it out into its own build or
> losing
> > it altogether? I haven't used it but it sounds like its useful.
> >
> > Jon
> >
> > On Mon, Jan 14, 2013 at 8:33 PM, Romain Manni-Bucau
> > <rm...@gmail.com>wrote:
> >
> > > i'd move presentations at same level as trunk is.
> > >
> > > other wise it sounds fine
> > >
> > > another point is current trunk: do we keep it as this?
> > >
> > > personally i wonder if we should keep karafee or not
> > >
> > > we spoke about mvn plugin, tomee and openejb but currently lifecycles
> are
> > > too linked to be split IMO
> > >
> > > *Romain Manni-Bucau*
> > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > > *Blog: **http://rmannibucau.wordpress.com/*<
> > > http://rmannibucau.wordpress.com/>
> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > > *Github: https://github.com/rmannibucau*
> > >
> > >
> > >
> > > 2013/1/14 David Blevins <da...@gmail.com>
> > >
> > > > With the SVN changes regarding openejb->tomee renaming, I wondered if
> > we
> > > > wanted to take the opportunity to move to a more standard SVN layout.
> > > >
> > > > Right now we have a "trunk" module with a ton of things in it:
> > > >
> > > > $ svn list http://svn.apache.org/repos/asf/tomee/trunk/
> > > > .gitignore
> > > > STATUS.txt
> > > > camel/
> > > > colossus/
> > > > graduation-resolution.txt
> > > > javaee-api/
> > > > openejb/
> > > > openejb-eclipse/
> > > > openejb-eclipse-plugin/
> > > > patched-libraries/
> > > > presentations/
> > > > sandbox/
> > > >
> > > > Having "sandbox" and "presentations" things like that under trunk is
> > very
> > > > odd. We've sort of lived with it and it's not a big deal, but we
> > > > developers know the actual trunk is the "openejb" module.
> > > >
> > > > Do we want to start moving to a more standard layout? Something
> like:
> > > >
> > > >
> > > > For TomEE/OpenEJB (i.e. what is currently at
> asf/tomee/trunk/openejb/):
> > > >
> > > > - http://svn.apache.org/repos/asf/tomee/tomee/trunk/
> > > > - http://svn.apache.org/repos/asf/tomee/tomee/tags/
> > > > - http://svn.apache.org/repos/asf/tomee/tomee/branches/
> > > >
> > > > For javaee-api:
> > > >
> > > > - http://svn.apache.org/repos/asf/tomee/javaee-api/trunk/
> > > > - http://svn.apache.org/repos/asf/tomee/javaee-api/tags/
> > > > - http://svn.apache.org/repos/asf/tomee/javaee-api/branches/
> > > >
> > > > For Website (this already exists, just showing to see the
> consistency):
> > > >
> > > > - http://svn.apache.org/repos/asf/tomee/site/trunk/
> > > > - http://svn.apache.org/repos/asf/tomee/site/branches/
> > > >
> > > > Eclipse plugins:
> > > >
> > > > -
> http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/trunk/
> > > > -
> http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/tags/
> > > > -
> > > http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/branches/
> > > >
> > > >
> > > > Everything that doesn't fit could likely go into sandbox possibly (no
> > > > "trunk"):
> > > >
> > > > - http://svn.apache.org/repos/asf/tomee/sandbox/
> > > > - http://svn.apache.org/repos/asf/tomee/sandbox/camel
> > > > - http://svn.apache.org/repos/asf/tomee/sandbox/colossus
> > > > - http://svn.apache.org/repos/asf/tomee/sandbox/release-tools
> > > > - ...
> > > >
> > > > The 'presentations' folder could probably just get moved into the
> site:
> > > >
> > > > -
> > >
> http://svn.apache.org/repos/asf/tomee/site/trunk/content/presentations/
> > > >
> > > >
> > > > Thoughts?
> > > >
> > > >
> > > > -David
> > > >
> > > >
> > >
> >
>
--
Jean-Louis
Re: SVN Reorg
Posted by Romain Manni-Bucau <rm...@gmail.com>.
i'm ok moving it elsewhere but ok to remove it too
it sounds useful but nobody is here to maintain it so i think we have to
choose
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/1/15 Jonathan Gallimore <jo...@gmail.com>
> I think the restructure as David suggests sounds good. I quite like the
> idea of moving the presentations to the website instead.
>
> I agree that keeping the Maven plugin with the rest of the build makes
> sense.
>
> KarafEE - are you thinking of splitting it out into its own build or losing
> it altogether? I haven't used it but it sounds like its useful.
>
> Jon
>
> On Mon, Jan 14, 2013 at 8:33 PM, Romain Manni-Bucau
> <rm...@gmail.com>wrote:
>
> > i'd move presentations at same level as trunk is.
> >
> > other wise it sounds fine
> >
> > another point is current trunk: do we keep it as this?
> >
> > personally i wonder if we should keep karafee or not
> >
> > we spoke about mvn plugin, tomee and openejb but currently lifecycles are
> > too linked to be split IMO
> >
> > *Romain Manni-Bucau*
> > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > *Blog: **http://rmannibucau.wordpress.com/*<
> > http://rmannibucau.wordpress.com/>
> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > *Github: https://github.com/rmannibucau*
> >
> >
> >
> > 2013/1/14 David Blevins <da...@gmail.com>
> >
> > > With the SVN changes regarding openejb->tomee renaming, I wondered if
> we
> > > wanted to take the opportunity to move to a more standard SVN layout.
> > >
> > > Right now we have a "trunk" module with a ton of things in it:
> > >
> > > $ svn list http://svn.apache.org/repos/asf/tomee/trunk/
> > > .gitignore
> > > STATUS.txt
> > > camel/
> > > colossus/
> > > graduation-resolution.txt
> > > javaee-api/
> > > openejb/
> > > openejb-eclipse/
> > > openejb-eclipse-plugin/
> > > patched-libraries/
> > > presentations/
> > > sandbox/
> > >
> > > Having "sandbox" and "presentations" things like that under trunk is
> very
> > > odd. We've sort of lived with it and it's not a big deal, but we
> > > developers know the actual trunk is the "openejb" module.
> > >
> > > Do we want to start moving to a more standard layout? Something like:
> > >
> > >
> > > For TomEE/OpenEJB (i.e. what is currently at asf/tomee/trunk/openejb/):
> > >
> > > - http://svn.apache.org/repos/asf/tomee/tomee/trunk/
> > > - http://svn.apache.org/repos/asf/tomee/tomee/tags/
> > > - http://svn.apache.org/repos/asf/tomee/tomee/branches/
> > >
> > > For javaee-api:
> > >
> > > - http://svn.apache.org/repos/asf/tomee/javaee-api/trunk/
> > > - http://svn.apache.org/repos/asf/tomee/javaee-api/tags/
> > > - http://svn.apache.org/repos/asf/tomee/javaee-api/branches/
> > >
> > > For Website (this already exists, just showing to see the consistency):
> > >
> > > - http://svn.apache.org/repos/asf/tomee/site/trunk/
> > > - http://svn.apache.org/repos/asf/tomee/site/branches/
> > >
> > > Eclipse plugins:
> > >
> > > - http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/trunk/
> > > - http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/tags/
> > > -
> > http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/branches/
> > >
> > >
> > > Everything that doesn't fit could likely go into sandbox possibly (no
> > > "trunk"):
> > >
> > > - http://svn.apache.org/repos/asf/tomee/sandbox/
> > > - http://svn.apache.org/repos/asf/tomee/sandbox/camel
> > > - http://svn.apache.org/repos/asf/tomee/sandbox/colossus
> > > - http://svn.apache.org/repos/asf/tomee/sandbox/release-tools
> > > - ...
> > >
> > > The 'presentations' folder could probably just get moved into the site:
> > >
> > > -
> > http://svn.apache.org/repos/asf/tomee/site/trunk/content/presentations/
> > >
> > >
> > > Thoughts?
> > >
> > >
> > > -David
> > >
> > >
> >
>
Re: SVN Reorg
Posted by Jonathan Gallimore <jo...@gmail.com>.
I think the restructure as David suggests sounds good. I quite like the
idea of moving the presentations to the website instead.
I agree that keeping the Maven plugin with the rest of the build makes
sense.
KarafEE - are you thinking of splitting it out into its own build or losing
it altogether? I haven't used it but it sounds like its useful.
Jon
On Mon, Jan 14, 2013 at 8:33 PM, Romain Manni-Bucau
<rm...@gmail.com>wrote:
> i'd move presentations at same level as trunk is.
>
> other wise it sounds fine
>
> another point is current trunk: do we keep it as this?
>
> personally i wonder if we should keep karafee or not
>
> we spoke about mvn plugin, tomee and openejb but currently lifecycles are
> too linked to be split IMO
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/1/14 David Blevins <da...@gmail.com>
>
> > With the SVN changes regarding openejb->tomee renaming, I wondered if we
> > wanted to take the opportunity to move to a more standard SVN layout.
> >
> > Right now we have a "trunk" module with a ton of things in it:
> >
> > $ svn list http://svn.apache.org/repos/asf/tomee/trunk/
> > .gitignore
> > STATUS.txt
> > camel/
> > colossus/
> > graduation-resolution.txt
> > javaee-api/
> > openejb/
> > openejb-eclipse/
> > openejb-eclipse-plugin/
> > patched-libraries/
> > presentations/
> > sandbox/
> >
> > Having "sandbox" and "presentations" things like that under trunk is very
> > odd. We've sort of lived with it and it's not a big deal, but we
> > developers know the actual trunk is the "openejb" module.
> >
> > Do we want to start moving to a more standard layout? Something like:
> >
> >
> > For TomEE/OpenEJB (i.e. what is currently at asf/tomee/trunk/openejb/):
> >
> > - http://svn.apache.org/repos/asf/tomee/tomee/trunk/
> > - http://svn.apache.org/repos/asf/tomee/tomee/tags/
> > - http://svn.apache.org/repos/asf/tomee/tomee/branches/
> >
> > For javaee-api:
> >
> > - http://svn.apache.org/repos/asf/tomee/javaee-api/trunk/
> > - http://svn.apache.org/repos/asf/tomee/javaee-api/tags/
> > - http://svn.apache.org/repos/asf/tomee/javaee-api/branches/
> >
> > For Website (this already exists, just showing to see the consistency):
> >
> > - http://svn.apache.org/repos/asf/tomee/site/trunk/
> > - http://svn.apache.org/repos/asf/tomee/site/branches/
> >
> > Eclipse plugins:
> >
> > - http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/trunk/
> > - http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/tags/
> > -
> http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/branches/
> >
> >
> > Everything that doesn't fit could likely go into sandbox possibly (no
> > "trunk"):
> >
> > - http://svn.apache.org/repos/asf/tomee/sandbox/
> > - http://svn.apache.org/repos/asf/tomee/sandbox/camel
> > - http://svn.apache.org/repos/asf/tomee/sandbox/colossus
> > - http://svn.apache.org/repos/asf/tomee/sandbox/release-tools
> > - ...
> >
> > The 'presentations' folder could probably just get moved into the site:
> >
> > -
> http://svn.apache.org/repos/asf/tomee/site/trunk/content/presentations/
> >
> >
> > Thoughts?
> >
> >
> > -David
> >
> >
>
Re: SVN Reorg
Posted by Romain Manni-Bucau <rm...@gmail.com>.
i'd move presentations at same level as trunk is.
other wise it sounds fine
another point is current trunk: do we keep it as this?
personally i wonder if we should keep karafee or not
we spoke about mvn plugin, tomee and openejb but currently lifecycles are
too linked to be split IMO
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/1/14 David Blevins <da...@gmail.com>
> With the SVN changes regarding openejb->tomee renaming, I wondered if we
> wanted to take the opportunity to move to a more standard SVN layout.
>
> Right now we have a "trunk" module with a ton of things in it:
>
> $ svn list http://svn.apache.org/repos/asf/tomee/trunk/
> .gitignore
> STATUS.txt
> camel/
> colossus/
> graduation-resolution.txt
> javaee-api/
> openejb/
> openejb-eclipse/
> openejb-eclipse-plugin/
> patched-libraries/
> presentations/
> sandbox/
>
> Having "sandbox" and "presentations" things like that under trunk is very
> odd. We've sort of lived with it and it's not a big deal, but we
> developers know the actual trunk is the "openejb" module.
>
> Do we want to start moving to a more standard layout? Something like:
>
>
> For TomEE/OpenEJB (i.e. what is currently at asf/tomee/trunk/openejb/):
>
> - http://svn.apache.org/repos/asf/tomee/tomee/trunk/
> - http://svn.apache.org/repos/asf/tomee/tomee/tags/
> - http://svn.apache.org/repos/asf/tomee/tomee/branches/
>
> For javaee-api:
>
> - http://svn.apache.org/repos/asf/tomee/javaee-api/trunk/
> - http://svn.apache.org/repos/asf/tomee/javaee-api/tags/
> - http://svn.apache.org/repos/asf/tomee/javaee-api/branches/
>
> For Website (this already exists, just showing to see the consistency):
>
> - http://svn.apache.org/repos/asf/tomee/site/trunk/
> - http://svn.apache.org/repos/asf/tomee/site/branches/
>
> Eclipse plugins:
>
> - http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/trunk/
> - http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/tags/
> - http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/branches/
>
>
> Everything that doesn't fit could likely go into sandbox possibly (no
> "trunk"):
>
> - http://svn.apache.org/repos/asf/tomee/sandbox/
> - http://svn.apache.org/repos/asf/tomee/sandbox/camel
> - http://svn.apache.org/repos/asf/tomee/sandbox/colossus
> - http://svn.apache.org/repos/asf/tomee/sandbox/release-tools
> - ...
>
> The 'presentations' folder could probably just get moved into the site:
>
> - http://svn.apache.org/repos/asf/tomee/site/trunk/content/presentations/
>
>
> Thoughts?
>
>
> -David
>
>
Re: SVN Reorg
Posted by Romain Manni-Bucau <rm...@gmail.com>.
ok moved in tomee/karafee/trunk
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/1/30 David Blevins <da...@gmail.com>
> Another trunk is good. If it sits there for too long, then off to the
> sandbox.
>
> -David
>
> On Jan 30, 2013, at 1:26 AM, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
> > if nobody shouts before next week i'll move karafee over sandbox or
> another
> > trunk
> >
> > any objection?
> >
> > *Romain Manni-Bucau*
> > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > *Github: https://github.com/rmannibucau*
> >
> >
> >
> > 2013/1/22 AndyG <an...@orprovision.com>
> >
> >> I think there may be a chmod/chown issue on the buildbot repo being
> caused
> >> by
> >> our build. Infra deleted the repo several times but it becomes
> unreadable
> >> specifically during the tomee builds.
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >> http://openejb.979440.n4.nabble.com/SVN-Reorg-tp4660262p4660344.html
> >> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
> >>
>
>
Re: SVN Reorg
Posted by David Blevins <da...@gmail.com>.
Another trunk is good. If it sits there for too long, then off to the sandbox.
-David
On Jan 30, 2013, at 1:26 AM, Romain Manni-Bucau <rm...@gmail.com> wrote:
> if nobody shouts before next week i'll move karafee over sandbox or another
> trunk
>
> any objection?
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/1/22 AndyG <an...@orprovision.com>
>
>> I think there may be a chmod/chown issue on the buildbot repo being caused
>> by
>> our build. Infra deleted the repo several times but it becomes unreadable
>> specifically during the tomee builds.
>>
>>
>>
>> --
>> View this message in context:
>> http://openejb.979440.n4.nabble.com/SVN-Reorg-tp4660262p4660344.html
>> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
>>
Re: SVN Reorg
Posted by Romain Manni-Bucau <rm...@gmail.com>.
if nobody shouts before next week i'll move karafee over sandbox or another
trunk
any objection?
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/1/22 AndyG <an...@orprovision.com>
> I think there may be a chmod/chown issue on the buildbot repo being caused
> by
> our build. Infra deleted the repo several times but it becomes unreadable
> specifically during the tomee builds.
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/SVN-Reorg-tp4660262p4660344.html
> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
>
Re: SVN Reorg
Posted by AndyG <an...@orprovision.com>.
I think there may be a chmod/chown issue on the buildbot repo being caused by
our build. Infra deleted the repo several times but it becomes unreadable
specifically during the tomee builds.
--
View this message in context: http://openejb.979440.n4.nabble.com/SVN-Reorg-tp4660262p4660344.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: SVN Reorg
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Great!
Always thought the way we did was the infra way.
Nice update!
Le 18 janv. 2013 04:51, "David Blevins" <da...@gmail.com> a écrit :
> Ok. Hopefully have completely fixed our buildbot setup. Now we have the
> following builders:
>
> [19:23] <tomee-bot> openejb-branch31: idle, last build 1622h15m45s ago:
> failed compile
> [19:23] <tomee-bot> openejb-branch32: idle, last build 11132h41m42s ago:
> failed test
> [19:23] <tomee-bot> tomee-javaee-api: idle, last build 9m00s ago: failed
> deploy
> [19:23] <tomee-bot> tomee-patches: idle, last build 8m16s ago: build
> successful
> [19:23] <tomee-bot> tomee-release-branch: idle
> [19:23] <tomee-bot> tomee-trunk-deploy: idle
> [19:23] <tomee-bot> tomee-trunk-empty-repo: idle
> [19:23] <tomee-bot> tomee-trunk-itests: idle, last build 3m22s ago:
> failed cdi-tomee-webapp-deployer
> [19:23] <tomee-bot> tomee-trunk-osx: offline
> [19:23] <tomee-bot> tomee-trunk-ubuntu: building(compiling)
> [19:23] <tomee-bot> tomee-trunk-win-ibmjdk6: idle
> [19:23] <tomee-bot> tomee-trunk-win-sunsdk: building(updating)
>
>
> Maintaining our buildbot config has been an incredible pain, so finally I
> learned some Python and rewrote it. Those of us who have had to deal with
> it in the past should find it a breath of fresh air. There were soooo many
> fixed strings not updated, paths that pointed nowhere, and builder names
> that didn't match the build definition, commenting out a builder or adding
> a builder was a pain. Some of the build definitions didn't even have
> schedules anymore and were not used. In general, a pain.
>
> Should be much easier now.
>
> Before:
>
> -
> https://svn.apache.org/repos/infra/!svn/bc/847059/infrastructure/buildbot/aegis/buildmaster/master1/projects/tomee.conf
>
> After:
>
> -
> https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/tomee.conf
>
> We also have a builder we could potentially use for each release:
>
> [19:23] <tomee-bot> tomee-release-branch: idle
>
> This `tomee-release-branch` builder is setup to watch the following path:
>
> - http://svn.apache.org/repos/asf/tomee/tomee/branches/release
>
> So if we put our release branch there when we make one, we won't have to
> setup a buildbot builder each time we do a release.
>
>
> -David
>
>
Re: SVN Reorg
Posted by David Blevins <da...@gmail.com>.
Ok. Hopefully have completely fixed our buildbot setup. Now we have the following builders:
[19:23] <tomee-bot> openejb-branch31: idle, last build 1622h15m45s ago: failed compile
[19:23] <tomee-bot> openejb-branch32: idle, last build 11132h41m42s ago: failed test
[19:23] <tomee-bot> tomee-javaee-api: idle, last build 9m00s ago: failed deploy
[19:23] <tomee-bot> tomee-patches: idle, last build 8m16s ago: build successful
[19:23] <tomee-bot> tomee-release-branch: idle
[19:23] <tomee-bot> tomee-trunk-deploy: idle
[19:23] <tomee-bot> tomee-trunk-empty-repo: idle
[19:23] <tomee-bot> tomee-trunk-itests: idle, last build 3m22s ago: failed cdi-tomee-webapp-deployer
[19:23] <tomee-bot> tomee-trunk-osx: offline
[19:23] <tomee-bot> tomee-trunk-ubuntu: building(compiling)
[19:23] <tomee-bot> tomee-trunk-win-ibmjdk6: idle
[19:23] <tomee-bot> tomee-trunk-win-sunsdk: building(updating)
Maintaining our buildbot config has been an incredible pain, so finally I learned some Python and rewrote it. Those of us who have had to deal with it in the past should find it a breath of fresh air. There were soooo many fixed strings not updated, paths that pointed nowhere, and builder names that didn't match the build definition, commenting out a builder or adding a builder was a pain. Some of the build definitions didn't even have schedules anymore and were not used. In general, a pain.
Should be much easier now.
Before:
- https://svn.apache.org/repos/infra/!svn/bc/847059/infrastructure/buildbot/aegis/buildmaster/master1/projects/tomee.conf
After:
- https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/tomee.conf
We also have a builder we could potentially use for each release:
[19:23] <tomee-bot> tomee-release-branch: idle
This `tomee-release-branch` builder is setup to watch the following path:
- http://svn.apache.org/repos/asf/tomee/tomee/branches/release
So if we put our release branch there when we make one, we won't have to setup a buildbot builder each time we do a release.
-David
Re: SVN Reorg
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Do we move osgi to sthg else (sandbox or tomee/osgi)?
Le 17 janv. 2013 19:49, "David Blevins" <da...@gmail.com> a écrit :
> Ok, took a quick stab at the reorg.
>
> svn switch https://svn.apache.org/repos/asf/tomee/tomee/trunk
>
> Also trying to get our buildbot config fixed with paths and hooks.
>
>
> -David
>
> On Jan 14, 2013, at 12:27 PM, David Blevins <da...@gmail.com>
> wrote:
>
> > With the SVN changes regarding openejb->tomee renaming, I wondered if we
> wanted to take the opportunity to move to a more standard SVN layout.
> >
> > Right now we have a "trunk" module with a ton of things in it:
> >
> > $ svn list http://svn.apache.org/repos/asf/tomee/trunk/
> > .gitignore
> > STATUS.txt
> > camel/
> > colossus/
> > graduation-resolution.txt
> > javaee-api/
> > openejb/
> > openejb-eclipse/
> > openejb-eclipse-plugin/
> > patched-libraries/
> > presentations/
> > sandbox/
> >
> > Having "sandbox" and "presentations" things like that under trunk is
> very odd. We've sort of lived with it and it's not a big deal, but we
> developers know the actual trunk is the "openejb" module.
> >
> > Do we want to start moving to a more standard layout? Something like:
> >
> >
> > For TomEE/OpenEJB (i.e. what is currently at asf/tomee/trunk/openejb/):
> >
> > - http://svn.apache.org/repos/asf/tomee/tomee/trunk/
> > - http://svn.apache.org/repos/asf/tomee/tomee/tags/
> > - http://svn.apache.org/repos/asf/tomee/tomee/branches/
> >
> > For javaee-api:
> >
> > - http://svn.apache.org/repos/asf/tomee/javaee-api/trunk/
> > - http://svn.apache.org/repos/asf/tomee/javaee-api/tags/
> > - http://svn.apache.org/repos/asf/tomee/javaee-api/branches/
> >
> > For Website (this already exists, just showing to see the consistency):
> >
> > - http://svn.apache.org/repos/asf/tomee/site/trunk/
> > - http://svn.apache.org/repos/asf/tomee/site/branches/
> >
> > Eclipse plugins:
> >
> > - http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/trunk/
> > - http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/tags/
> > - http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/branches/
> >
> >
> > Everything that doesn't fit could likely go into sandbox possibly (no
> "trunk"):
> >
> > - http://svn.apache.org/repos/asf/tomee/sandbox/
> > - http://svn.apache.org/repos/asf/tomee/sandbox/camel
> > - http://svn.apache.org/repos/asf/tomee/sandbox/colossus
> > - http://svn.apache.org/repos/asf/tomee/sandbox/release-tools
> > - ...
> >
> > The 'presentations' folder could probably just get moved into the site:
> >
> > -
> http://svn.apache.org/repos/asf/tomee/site/trunk/content/presentations/
> >
> >
> > Thoughts?
> >
> >
> > -David
> >
>
>
Re: SVN Reorg
Posted by David Blevins <da...@gmail.com>.
Ok, took a quick stab at the reorg.
svn switch https://svn.apache.org/repos/asf/tomee/tomee/trunk
Also trying to get our buildbot config fixed with paths and hooks.
-David
On Jan 14, 2013, at 12:27 PM, David Blevins <da...@gmail.com> wrote:
> With the SVN changes regarding openejb->tomee renaming, I wondered if we wanted to take the opportunity to move to a more standard SVN layout.
>
> Right now we have a "trunk" module with a ton of things in it:
>
> $ svn list http://svn.apache.org/repos/asf/tomee/trunk/
> .gitignore
> STATUS.txt
> camel/
> colossus/
> graduation-resolution.txt
> javaee-api/
> openejb/
> openejb-eclipse/
> openejb-eclipse-plugin/
> patched-libraries/
> presentations/
> sandbox/
>
> Having "sandbox" and "presentations" things like that under trunk is very odd. We've sort of lived with it and it's not a big deal, but we developers know the actual trunk is the "openejb" module.
>
> Do we want to start moving to a more standard layout? Something like:
>
>
> For TomEE/OpenEJB (i.e. what is currently at asf/tomee/trunk/openejb/):
>
> - http://svn.apache.org/repos/asf/tomee/tomee/trunk/
> - http://svn.apache.org/repos/asf/tomee/tomee/tags/
> - http://svn.apache.org/repos/asf/tomee/tomee/branches/
>
> For javaee-api:
>
> - http://svn.apache.org/repos/asf/tomee/javaee-api/trunk/
> - http://svn.apache.org/repos/asf/tomee/javaee-api/tags/
> - http://svn.apache.org/repos/asf/tomee/javaee-api/branches/
>
> For Website (this already exists, just showing to see the consistency):
>
> - http://svn.apache.org/repos/asf/tomee/site/trunk/
> - http://svn.apache.org/repos/asf/tomee/site/branches/
>
> Eclipse plugins:
>
> - http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/trunk/
> - http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/tags/
> - http://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/branches/
>
>
> Everything that doesn't fit could likely go into sandbox possibly (no "trunk"):
>
> - http://svn.apache.org/repos/asf/tomee/sandbox/
> - http://svn.apache.org/repos/asf/tomee/sandbox/camel
> - http://svn.apache.org/repos/asf/tomee/sandbox/colossus
> - http://svn.apache.org/repos/asf/tomee/sandbox/release-tools
> - ...
>
> The 'presentations' folder could probably just get moved into the site:
>
> - http://svn.apache.org/repos/asf/tomee/site/trunk/content/presentations/
>
>
> Thoughts?
>
>
> -David
>