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 2012/04/13 04:37:53 UTC
[DISCUSSION] 1.0.0 library change
Responding in a second email (wanted to keep the original data clean).
> A asm-3.2.jar
This is one of the libraries we intentionally repackage (xbean-asm) in order to avoid library conflicts with other popular libs (like hibernate).
I'll have a look to see what is pulling in asm and see if it can be removed.
> A gson-2.1.jar
Do we still need this? If so we'll need it listed in all of our NOTICE files for the tomee wars, tomee zips, and openejb standalone zips.
> apache-tomee 1.0.0 plus
>
> A aether-api-1.13.1.jar
> A aether-connector-wagon-1.13.1.jar
> A aether-impl-1.13.1.jar
> A aether-spi-1.13.1.jar
> A aether-util-1.13.1.jar
> A google-collections-1.0.jar
> A httpclient-4.1.2.jar
> A httpcore-4.1.2.jar
> A jline-0.9.94.jar
> A jsoup-1.6.1.jar
> A maven-aether-provider-3.0.4.jar
> A maven-model-3.0.4.jar
> A maven-model-builder-3.0.4.jar
> A maven-repository-metadata-3.0.4.jar
> A mina-core-2.0.2.jar
> A openejb-common-cli-4.0.0.jar
> A openejb-provisionning-4.0.0.jar
> A openejb-ssh-4.0.0.jar
> A ops4j-base-lang-1.2.3.jar
> A ops4j-base-util-collections-1.2.3.jar
> A ops4j-base-util-property-1.2.3.jar
> A ops4j-base-util-xml-1.2.3.jar
> A pax-url-maven-commons-1.3.5.jar
> A plexus-classworlds-2.4.jar
> A plexus-component-annotations-1.5.5.jar
> A plexus-container-default-1.5.5.jar
> A plexus-interpolation-1.14.jar
> A plexus-utils-2.0.6.jar
> A sisu-guice-3.0.3-no_aop.jar
> A sisu-inject-bean-2.2.3.jar
> A sisu-inject-plexus-2.2.3.jar
> A slf4j-jdk14-1.6.4.jar
> A sshd-core-0.6.0.jar
> A wagon-file-2.2.jar
> A wagon-http-2.2.jar
> A wagon-http-shared4-2.2.jar
> A wagon-provider-api-2.2.jar
This is really where we need the most discussion. There are some challenges:
- 37 new libraries is a lot to legally screen (each will need NOTICE file additions and possibly a couple LICENSE additions). This will take a week or more as everyone on the PMC is legally required to review this information for accuracy before they can vote.
- 37 new libraries is a lot to add prior to a final with no previous beta exposure.
- 1.0 final is maybe not the best term for functionality that is really an alpha or beta.
- Could apply to all distros: no easy way to add this functionality to TomEE WebProfile or OpenEJB Standalone.
I see two basic solutions, more are possible, but here goes:
1. Leave things the way they are and hold 1.0 till all can be legally screened. This would be a 1.0 final feature of TomEE+ only.
2. Hold this functionality till it can be legally screened. Release it as an alpha or beta, possibly in the form of a zip that can be extracted into a TomEE, TomEE+, or OpenEJB install.
3. Other (insert proposal here :)
Thoughts?
-David
Re: [DISCUSSION] 1.0.0 library change
Posted by Romain Manni-Bucau <rm...@gmail.com>.
it downloads the zip and install it for next starts (like the
provisionning.properties). That's just a simpler way to do so
- Romain
2012/4/13 Mohammad Nour El-Din <no...@gmail.com>
> Sorry then I missed the point here, so if the zip is already there, so what
> does the downloader do :) ?
>
> On Fri, Apr 13, 2012 at 12:12 PM, Romain Manni-Bucau
> <rm...@gmail.com>wrote:
>
> > in my idea it was what we do today: in our build we create zip then the
> > downloader simply download the zip but the zip is built from maven
> >
> > - Romain
> >
> >
> > 2012/4/13 Mohammad Nour El-Din <no...@gmail.com>
> >
> > > Great idea
> > >
> > > One comment though, can we do this by means of maven, like having a pom
> > > from which we refer to all required released Jars, and it does all
> > > assembling magic out of the box, so we just direct users to that pom
> they
> > > get it build it and voila :) ?
> > >
> > > On Fri, Apr 13, 2012 at 11:42 AM, Jean-Louis MONTEIRO <
> > jeanouii@gmail.com
> > > >wrote:
> > >
> > > > +1, that seems great to me.
> > > >
> > > > JLouis
> > > >
> > > > Le 13 avril 2012 11:25, Romain Manni-Bucau <rm...@gmail.com> a
> > > > écrit :
> > > >
> > > > > yep that's probably the best compromise between simplicity,
> features,
> > > > > weight and work for the release.
> > > > >
> > > > > - Romain
> > > > >
> > > > >
> > > > > 2012/4/13 David Blevins <da...@gmail.com>
> > > > >
> > > > > > Had a quick chat with Romain on IRC. I proposed some kind of
> > > > > > mini-downloader for the future zip that will contain all the
> > > > provisioning
> > > > > > libs. The downloader would pull down the zip and install the
> libs.
> > > > > > There'd be some sort of button/cli for doing the install.
> > > > > >
> > > > > > This means:
> > > > > >
> > > > > > 1) we can get TomEE final out quicker
> > > > > > 2) we can get this in all 3 of the servers (not just TomEE+)
> > > > > > 3) it can clearly be marked as beta allowing us to incorporate
> > > > feedback
> > > > > > (we wouldn't have to treat it as stable)
> > > > > >
> > > > > > More thoughts welcome of course.
> > > > > >
> > > > > >
> > > > > > -David
> > > > > >
> > > > > > On Apr 12, 2012, at 11:35 PM, Romain Manni-Bucau wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > -100 for 2): IMHO it is a great feature which should be part of
> > > > tomee+
> > > > > > > bundle
> > > > > > > -1 to do another beta which simply means for a lot of people
> dont
> > > use
> > > > > me
> > > > > > > +1 to keep the way it is and simply fix potential dependencies
> > > issues
> > > > > > (asm
> > > > > > > for instance)
> > > > > > >
> > > > > > > gson is used for common cli module to output data but we
> probably
> > > can
> > > > > do
> > > > > > > something simpler, i think Thiago uses it too for the GUI for
> > next
> > > > > > releases
> > > > > > > (but same note, just the info we need to keep something to do
> > json)
> > > > > > >
> > > > > > > - Romain
> > > > > > >
> > > > > > >
> > > > > > > 2012/4/13 David Blevins <da...@gmail.com>
> > > > > > >
> > > > > > >> Responding in a second email (wanted to keep the original data
> > > > clean).
> > > > > > >>
> > > > > > >>> A asm-3.2.jar
> > > > > > >>
> > > > > > >> This is one of the libraries we intentionally repackage
> > > (xbean-asm)
> > > > in
> > > > > > >> order to avoid library conflicts with other popular libs (like
> > > > > > hibernate).
> > > > > > >>
> > > > > > >> I'll have a look to see what is pulling in asm and see if it
> can
> > > be
> > > > > > >> removed.
> > > > > > >>
> > > > > > >>> A gson-2.1.jar
> > > > > > >>
> > > > > > >> Do we still need this? If so we'll need it listed in all of
> our
> > > > > NOTICE
> > > > > > >> files for the tomee wars, tomee zips, and openejb standalone
> > zips.
> > > > > > >>
> > > > > > >>> apache-tomee 1.0.0 plus
> > > > > > >>>
> > > > > > >>> A aether-api-1.13.1.jar
> > > > > > >>> A aether-connector-wagon-1.13.1.jar
> > > > > > >>> A aether-impl-1.13.1.jar
> > > > > > >>> A aether-spi-1.13.1.jar
> > > > > > >>> A aether-util-1.13.1.jar
> > > > > > >>> A google-collections-1.0.jar
> > > > > > >>> A httpclient-4.1.2.jar
> > > > > > >>> A httpcore-4.1.2.jar
> > > > > > >>> A jline-0.9.94.jar
> > > > > > >>> A jsoup-1.6.1.jar
> > > > > > >>> A maven-aether-provider-3.0.4.jar
> > > > > > >>> A maven-model-3.0.4.jar
> > > > > > >>> A maven-model-builder-3.0.4.jar
> > > > > > >>> A maven-repository-metadata-3.0.4.jar
> > > > > > >>> A mina-core-2.0.2.jar
> > > > > > >>> A openejb-common-cli-4.0.0.jar
> > > > > > >>> A openejb-provisionning-4.0.0.jar
> > > > > > >>> A openejb-ssh-4.0.0.jar
> > > > > > >>> A ops4j-base-lang-1.2.3.jar
> > > > > > >>> A ops4j-base-util-collections-1.2.3.jar
> > > > > > >>> A ops4j-base-util-property-1.2.3.jar
> > > > > > >>> A ops4j-base-util-xml-1.2.3.jar
> > > > > > >>> A pax-url-maven-commons-1.3.5.jar
> > > > > > >>> A plexus-classworlds-2.4.jar
> > > > > > >>> A plexus-component-annotations-1.5.5.jar
> > > > > > >>> A plexus-container-default-1.5.5.jar
> > > > > > >>> A plexus-interpolation-1.14.jar
> > > > > > >>> A plexus-utils-2.0.6.jar
> > > > > > >>> A sisu-guice-3.0.3-no_aop.jar
> > > > > > >>> A sisu-inject-bean-2.2.3.jar
> > > > > > >>> A sisu-inject-plexus-2.2.3.jar
> > > > > > >>> A slf4j-jdk14-1.6.4.jar
> > > > > > >>> A sshd-core-0.6.0.jar
> > > > > > >>> A wagon-file-2.2.jar
> > > > > > >>> A wagon-http-2.2.jar
> > > > > > >>> A wagon-http-shared4-2.2.jar
> > > > > > >>> A wagon-provider-api-2.2.jar
> > > > > > >>
> > > > > > >> This is really where we need the most discussion. There are
> > some
> > > > > > >> challenges:
> > > > > > >>
> > > > > > >> - 37 new libraries is a lot to legally screen (each will need
> > > NOTICE
> > > > > > file
> > > > > > >> additions and possibly a couple LICENSE additions). This will
> > > take
> > > > a
> > > > > > week
> > > > > > >> or more as everyone on the PMC is legally required to review
> > this
> > > > > > >> information for accuracy before they can vote.
> > > > > > >> - 37 new libraries is a lot to add prior to a final with no
> > > previous
> > > > > > beta
> > > > > > >> exposure.
> > > > > > >> - 1.0 final is maybe not the best term for functionality that
> is
> > > > > really
> > > > > > >> an alpha or beta.
> > > > > > >> - Could apply to all distros: no easy way to add this
> > > functionality
> > > > to
> > > > > > >> TomEE WebProfile or OpenEJB Standalone.
> > > > > > >>
> > > > > > >> I see two basic solutions, more are possible, but here goes:
> > > > > > >>
> > > > > > >> 1. Leave things the way they are and hold 1.0 till all can be
> > > > legally
> > > > > > >> screened. This would be a 1.0 final feature of TomEE+ only.
> > > > > > >> 2. Hold this functionality till it can be legally screened.
> > > > Release
> > > > > it
> > > > > > >> as an alpha or beta, possibly in the form of a zip that can be
> > > > > extracted
> > > > > > >> into a TomEE, TomEE+, or OpenEJB install.
> > > > > > >> 3. Other (insert proposal here :)
> > > > > > >>
> > > > > > >>
> > > > > > >> Thoughts?
> > > > > > >>
> > > > > > >>
> > > > > > >> -David
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Thanks
> > > - Mohammad Nour
> > > ----
> > > "Life is like riding a bicycle. To keep your balance you must keep
> > moving"
> > > - Albert Einstein
> > >
> >
>
>
>
> --
> Thanks
> - Mohammad Nour
> ----
> "Life is like riding a bicycle. To keep your balance you must keep moving"
> - Albert Einstein
>
Re: [DISCUSSION] 1.0.0 library change
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Sorry then I missed the point here, so if the zip is already there, so what
does the downloader do :) ?
On Fri, Apr 13, 2012 at 12:12 PM, Romain Manni-Bucau
<rm...@gmail.com>wrote:
> in my idea it was what we do today: in our build we create zip then the
> downloader simply download the zip but the zip is built from maven
>
> - Romain
>
>
> 2012/4/13 Mohammad Nour El-Din <no...@gmail.com>
>
> > Great idea
> >
> > One comment though, can we do this by means of maven, like having a pom
> > from which we refer to all required released Jars, and it does all
> > assembling magic out of the box, so we just direct users to that pom they
> > get it build it and voila :) ?
> >
> > On Fri, Apr 13, 2012 at 11:42 AM, Jean-Louis MONTEIRO <
> jeanouii@gmail.com
> > >wrote:
> >
> > > +1, that seems great to me.
> > >
> > > JLouis
> > >
> > > Le 13 avril 2012 11:25, Romain Manni-Bucau <rm...@gmail.com> a
> > > écrit :
> > >
> > > > yep that's probably the best compromise between simplicity, features,
> > > > weight and work for the release.
> > > >
> > > > - Romain
> > > >
> > > >
> > > > 2012/4/13 David Blevins <da...@gmail.com>
> > > >
> > > > > Had a quick chat with Romain on IRC. I proposed some kind of
> > > > > mini-downloader for the future zip that will contain all the
> > > provisioning
> > > > > libs. The downloader would pull down the zip and install the libs.
> > > > > There'd be some sort of button/cli for doing the install.
> > > > >
> > > > > This means:
> > > > >
> > > > > 1) we can get TomEE final out quicker
> > > > > 2) we can get this in all 3 of the servers (not just TomEE+)
> > > > > 3) it can clearly be marked as beta allowing us to incorporate
> > > feedback
> > > > > (we wouldn't have to treat it as stable)
> > > > >
> > > > > More thoughts welcome of course.
> > > > >
> > > > >
> > > > > -David
> > > > >
> > > > > On Apr 12, 2012, at 11:35 PM, Romain Manni-Bucau wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > -100 for 2): IMHO it is a great feature which should be part of
> > > tomee+
> > > > > > bundle
> > > > > > -1 to do another beta which simply means for a lot of people dont
> > use
> > > > me
> > > > > > +1 to keep the way it is and simply fix potential dependencies
> > issues
> > > > > (asm
> > > > > > for instance)
> > > > > >
> > > > > > gson is used for common cli module to output data but we probably
> > can
> > > > do
> > > > > > something simpler, i think Thiago uses it too for the GUI for
> next
> > > > > releases
> > > > > > (but same note, just the info we need to keep something to do
> json)
> > > > > >
> > > > > > - Romain
> > > > > >
> > > > > >
> > > > > > 2012/4/13 David Blevins <da...@gmail.com>
> > > > > >
> > > > > >> Responding in a second email (wanted to keep the original data
> > > clean).
> > > > > >>
> > > > > >>> A asm-3.2.jar
> > > > > >>
> > > > > >> This is one of the libraries we intentionally repackage
> > (xbean-asm)
> > > in
> > > > > >> order to avoid library conflicts with other popular libs (like
> > > > > hibernate).
> > > > > >>
> > > > > >> I'll have a look to see what is pulling in asm and see if it can
> > be
> > > > > >> removed.
> > > > > >>
> > > > > >>> A gson-2.1.jar
> > > > > >>
> > > > > >> Do we still need this? If so we'll need it listed in all of our
> > > > NOTICE
> > > > > >> files for the tomee wars, tomee zips, and openejb standalone
> zips.
> > > > > >>
> > > > > >>> apache-tomee 1.0.0 plus
> > > > > >>>
> > > > > >>> A aether-api-1.13.1.jar
> > > > > >>> A aether-connector-wagon-1.13.1.jar
> > > > > >>> A aether-impl-1.13.1.jar
> > > > > >>> A aether-spi-1.13.1.jar
> > > > > >>> A aether-util-1.13.1.jar
> > > > > >>> A google-collections-1.0.jar
> > > > > >>> A httpclient-4.1.2.jar
> > > > > >>> A httpcore-4.1.2.jar
> > > > > >>> A jline-0.9.94.jar
> > > > > >>> A jsoup-1.6.1.jar
> > > > > >>> A maven-aether-provider-3.0.4.jar
> > > > > >>> A maven-model-3.0.4.jar
> > > > > >>> A maven-model-builder-3.0.4.jar
> > > > > >>> A maven-repository-metadata-3.0.4.jar
> > > > > >>> A mina-core-2.0.2.jar
> > > > > >>> A openejb-common-cli-4.0.0.jar
> > > > > >>> A openejb-provisionning-4.0.0.jar
> > > > > >>> A openejb-ssh-4.0.0.jar
> > > > > >>> A ops4j-base-lang-1.2.3.jar
> > > > > >>> A ops4j-base-util-collections-1.2.3.jar
> > > > > >>> A ops4j-base-util-property-1.2.3.jar
> > > > > >>> A ops4j-base-util-xml-1.2.3.jar
> > > > > >>> A pax-url-maven-commons-1.3.5.jar
> > > > > >>> A plexus-classworlds-2.4.jar
> > > > > >>> A plexus-component-annotations-1.5.5.jar
> > > > > >>> A plexus-container-default-1.5.5.jar
> > > > > >>> A plexus-interpolation-1.14.jar
> > > > > >>> A plexus-utils-2.0.6.jar
> > > > > >>> A sisu-guice-3.0.3-no_aop.jar
> > > > > >>> A sisu-inject-bean-2.2.3.jar
> > > > > >>> A sisu-inject-plexus-2.2.3.jar
> > > > > >>> A slf4j-jdk14-1.6.4.jar
> > > > > >>> A sshd-core-0.6.0.jar
> > > > > >>> A wagon-file-2.2.jar
> > > > > >>> A wagon-http-2.2.jar
> > > > > >>> A wagon-http-shared4-2.2.jar
> > > > > >>> A wagon-provider-api-2.2.jar
> > > > > >>
> > > > > >> This is really where we need the most discussion. There are
> some
> > > > > >> challenges:
> > > > > >>
> > > > > >> - 37 new libraries is a lot to legally screen (each will need
> > NOTICE
> > > > > file
> > > > > >> additions and possibly a couple LICENSE additions). This will
> > take
> > > a
> > > > > week
> > > > > >> or more as everyone on the PMC is legally required to review
> this
> > > > > >> information for accuracy before they can vote.
> > > > > >> - 37 new libraries is a lot to add prior to a final with no
> > previous
> > > > > beta
> > > > > >> exposure.
> > > > > >> - 1.0 final is maybe not the best term for functionality that is
> > > > really
> > > > > >> an alpha or beta.
> > > > > >> - Could apply to all distros: no easy way to add this
> > functionality
> > > to
> > > > > >> TomEE WebProfile or OpenEJB Standalone.
> > > > > >>
> > > > > >> I see two basic solutions, more are possible, but here goes:
> > > > > >>
> > > > > >> 1. Leave things the way they are and hold 1.0 till all can be
> > > legally
> > > > > >> screened. This would be a 1.0 final feature of TomEE+ only.
> > > > > >> 2. Hold this functionality till it can be legally screened.
> > > Release
> > > > it
> > > > > >> as an alpha or beta, possibly in the form of a zip that can be
> > > > extracted
> > > > > >> into a TomEE, TomEE+, or OpenEJB install.
> > > > > >> 3. Other (insert proposal here :)
> > > > > >>
> > > > > >>
> > > > > >> Thoughts?
> > > > > >>
> > > > > >>
> > > > > >> -David
> > > > > >>
> > > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Thanks
> > - Mohammad Nour
> > ----
> > "Life is like riding a bicycle. To keep your balance you must keep
> moving"
> > - Albert Einstein
> >
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
Re: [DISCUSSION] 1.0.0 library change
Posted by Romain Manni-Bucau <rm...@gmail.com>.
in my idea it was what we do today: in our build we create zip then the
downloader simply download the zip but the zip is built from maven
- Romain
2012/4/13 Mohammad Nour El-Din <no...@gmail.com>
> Great idea
>
> One comment though, can we do this by means of maven, like having a pom
> from which we refer to all required released Jars, and it does all
> assembling magic out of the box, so we just direct users to that pom they
> get it build it and voila :) ?
>
> On Fri, Apr 13, 2012 at 11:42 AM, Jean-Louis MONTEIRO <jeanouii@gmail.com
> >wrote:
>
> > +1, that seems great to me.
> >
> > JLouis
> >
> > Le 13 avril 2012 11:25, Romain Manni-Bucau <rm...@gmail.com> a
> > écrit :
> >
> > > yep that's probably the best compromise between simplicity, features,
> > > weight and work for the release.
> > >
> > > - Romain
> > >
> > >
> > > 2012/4/13 David Blevins <da...@gmail.com>
> > >
> > > > Had a quick chat with Romain on IRC. I proposed some kind of
> > > > mini-downloader for the future zip that will contain all the
> > provisioning
> > > > libs. The downloader would pull down the zip and install the libs.
> > > > There'd be some sort of button/cli for doing the install.
> > > >
> > > > This means:
> > > >
> > > > 1) we can get TomEE final out quicker
> > > > 2) we can get this in all 3 of the servers (not just TomEE+)
> > > > 3) it can clearly be marked as beta allowing us to incorporate
> > feedback
> > > > (we wouldn't have to treat it as stable)
> > > >
> > > > More thoughts welcome of course.
> > > >
> > > >
> > > > -David
> > > >
> > > > On Apr 12, 2012, at 11:35 PM, Romain Manni-Bucau wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > -100 for 2): IMHO it is a great feature which should be part of
> > tomee+
> > > > > bundle
> > > > > -1 to do another beta which simply means for a lot of people dont
> use
> > > me
> > > > > +1 to keep the way it is and simply fix potential dependencies
> issues
> > > > (asm
> > > > > for instance)
> > > > >
> > > > > gson is used for common cli module to output data but we probably
> can
> > > do
> > > > > something simpler, i think Thiago uses it too for the GUI for next
> > > > releases
> > > > > (but same note, just the info we need to keep something to do json)
> > > > >
> > > > > - Romain
> > > > >
> > > > >
> > > > > 2012/4/13 David Blevins <da...@gmail.com>
> > > > >
> > > > >> Responding in a second email (wanted to keep the original data
> > clean).
> > > > >>
> > > > >>> A asm-3.2.jar
> > > > >>
> > > > >> This is one of the libraries we intentionally repackage
> (xbean-asm)
> > in
> > > > >> order to avoid library conflicts with other popular libs (like
> > > > hibernate).
> > > > >>
> > > > >> I'll have a look to see what is pulling in asm and see if it can
> be
> > > > >> removed.
> > > > >>
> > > > >>> A gson-2.1.jar
> > > > >>
> > > > >> Do we still need this? If so we'll need it listed in all of our
> > > NOTICE
> > > > >> files for the tomee wars, tomee zips, and openejb standalone zips.
> > > > >>
> > > > >>> apache-tomee 1.0.0 plus
> > > > >>>
> > > > >>> A aether-api-1.13.1.jar
> > > > >>> A aether-connector-wagon-1.13.1.jar
> > > > >>> A aether-impl-1.13.1.jar
> > > > >>> A aether-spi-1.13.1.jar
> > > > >>> A aether-util-1.13.1.jar
> > > > >>> A google-collections-1.0.jar
> > > > >>> A httpclient-4.1.2.jar
> > > > >>> A httpcore-4.1.2.jar
> > > > >>> A jline-0.9.94.jar
> > > > >>> A jsoup-1.6.1.jar
> > > > >>> A maven-aether-provider-3.0.4.jar
> > > > >>> A maven-model-3.0.4.jar
> > > > >>> A maven-model-builder-3.0.4.jar
> > > > >>> A maven-repository-metadata-3.0.4.jar
> > > > >>> A mina-core-2.0.2.jar
> > > > >>> A openejb-common-cli-4.0.0.jar
> > > > >>> A openejb-provisionning-4.0.0.jar
> > > > >>> A openejb-ssh-4.0.0.jar
> > > > >>> A ops4j-base-lang-1.2.3.jar
> > > > >>> A ops4j-base-util-collections-1.2.3.jar
> > > > >>> A ops4j-base-util-property-1.2.3.jar
> > > > >>> A ops4j-base-util-xml-1.2.3.jar
> > > > >>> A pax-url-maven-commons-1.3.5.jar
> > > > >>> A plexus-classworlds-2.4.jar
> > > > >>> A plexus-component-annotations-1.5.5.jar
> > > > >>> A plexus-container-default-1.5.5.jar
> > > > >>> A plexus-interpolation-1.14.jar
> > > > >>> A plexus-utils-2.0.6.jar
> > > > >>> A sisu-guice-3.0.3-no_aop.jar
> > > > >>> A sisu-inject-bean-2.2.3.jar
> > > > >>> A sisu-inject-plexus-2.2.3.jar
> > > > >>> A slf4j-jdk14-1.6.4.jar
> > > > >>> A sshd-core-0.6.0.jar
> > > > >>> A wagon-file-2.2.jar
> > > > >>> A wagon-http-2.2.jar
> > > > >>> A wagon-http-shared4-2.2.jar
> > > > >>> A wagon-provider-api-2.2.jar
> > > > >>
> > > > >> This is really where we need the most discussion. There are some
> > > > >> challenges:
> > > > >>
> > > > >> - 37 new libraries is a lot to legally screen (each will need
> NOTICE
> > > > file
> > > > >> additions and possibly a couple LICENSE additions). This will
> take
> > a
> > > > week
> > > > >> or more as everyone on the PMC is legally required to review this
> > > > >> information for accuracy before they can vote.
> > > > >> - 37 new libraries is a lot to add prior to a final with no
> previous
> > > > beta
> > > > >> exposure.
> > > > >> - 1.0 final is maybe not the best term for functionality that is
> > > really
> > > > >> an alpha or beta.
> > > > >> - Could apply to all distros: no easy way to add this
> functionality
> > to
> > > > >> TomEE WebProfile or OpenEJB Standalone.
> > > > >>
> > > > >> I see two basic solutions, more are possible, but here goes:
> > > > >>
> > > > >> 1. Leave things the way they are and hold 1.0 till all can be
> > legally
> > > > >> screened. This would be a 1.0 final feature of TomEE+ only.
> > > > >> 2. Hold this functionality till it can be legally screened.
> > Release
> > > it
> > > > >> as an alpha or beta, possibly in the form of a zip that can be
> > > extracted
> > > > >> into a TomEE, TomEE+, or OpenEJB install.
> > > > >> 3. Other (insert proposal here :)
> > > > >>
> > > > >>
> > > > >> Thoughts?
> > > > >>
> > > > >>
> > > > >> -David
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
>
>
>
> --
> Thanks
> - Mohammad Nour
> ----
> "Life is like riding a bicycle. To keep your balance you must keep moving"
> - Albert Einstein
>
Re: [DISCUSSION] 1.0.0 library change
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Great idea
One comment though, can we do this by means of maven, like having a pom
from which we refer to all required released Jars, and it does all
assembling magic out of the box, so we just direct users to that pom they
get it build it and voila :) ?
On Fri, Apr 13, 2012 at 11:42 AM, Jean-Louis MONTEIRO <je...@gmail.com>wrote:
> +1, that seems great to me.
>
> JLouis
>
> Le 13 avril 2012 11:25, Romain Manni-Bucau <rm...@gmail.com> a
> écrit :
>
> > yep that's probably the best compromise between simplicity, features,
> > weight and work for the release.
> >
> > - Romain
> >
> >
> > 2012/4/13 David Blevins <da...@gmail.com>
> >
> > > Had a quick chat with Romain on IRC. I proposed some kind of
> > > mini-downloader for the future zip that will contain all the
> provisioning
> > > libs. The downloader would pull down the zip and install the libs.
> > > There'd be some sort of button/cli for doing the install.
> > >
> > > This means:
> > >
> > > 1) we can get TomEE final out quicker
> > > 2) we can get this in all 3 of the servers (not just TomEE+)
> > > 3) it can clearly be marked as beta allowing us to incorporate
> feedback
> > > (we wouldn't have to treat it as stable)
> > >
> > > More thoughts welcome of course.
> > >
> > >
> > > -David
> > >
> > > On Apr 12, 2012, at 11:35 PM, Romain Manni-Bucau wrote:
> > >
> > > > Hi,
> > > >
> > > > -100 for 2): IMHO it is a great feature which should be part of
> tomee+
> > > > bundle
> > > > -1 to do another beta which simply means for a lot of people dont use
> > me
> > > > +1 to keep the way it is and simply fix potential dependencies issues
> > > (asm
> > > > for instance)
> > > >
> > > > gson is used for common cli module to output data but we probably can
> > do
> > > > something simpler, i think Thiago uses it too for the GUI for next
> > > releases
> > > > (but same note, just the info we need to keep something to do json)
> > > >
> > > > - Romain
> > > >
> > > >
> > > > 2012/4/13 David Blevins <da...@gmail.com>
> > > >
> > > >> Responding in a second email (wanted to keep the original data
> clean).
> > > >>
> > > >>> A asm-3.2.jar
> > > >>
> > > >> This is one of the libraries we intentionally repackage (xbean-asm)
> in
> > > >> order to avoid library conflicts with other popular libs (like
> > > hibernate).
> > > >>
> > > >> I'll have a look to see what is pulling in asm and see if it can be
> > > >> removed.
> > > >>
> > > >>> A gson-2.1.jar
> > > >>
> > > >> Do we still need this? If so we'll need it listed in all of our
> > NOTICE
> > > >> files for the tomee wars, tomee zips, and openejb standalone zips.
> > > >>
> > > >>> apache-tomee 1.0.0 plus
> > > >>>
> > > >>> A aether-api-1.13.1.jar
> > > >>> A aether-connector-wagon-1.13.1.jar
> > > >>> A aether-impl-1.13.1.jar
> > > >>> A aether-spi-1.13.1.jar
> > > >>> A aether-util-1.13.1.jar
> > > >>> A google-collections-1.0.jar
> > > >>> A httpclient-4.1.2.jar
> > > >>> A httpcore-4.1.2.jar
> > > >>> A jline-0.9.94.jar
> > > >>> A jsoup-1.6.1.jar
> > > >>> A maven-aether-provider-3.0.4.jar
> > > >>> A maven-model-3.0.4.jar
> > > >>> A maven-model-builder-3.0.4.jar
> > > >>> A maven-repository-metadata-3.0.4.jar
> > > >>> A mina-core-2.0.2.jar
> > > >>> A openejb-common-cli-4.0.0.jar
> > > >>> A openejb-provisionning-4.0.0.jar
> > > >>> A openejb-ssh-4.0.0.jar
> > > >>> A ops4j-base-lang-1.2.3.jar
> > > >>> A ops4j-base-util-collections-1.2.3.jar
> > > >>> A ops4j-base-util-property-1.2.3.jar
> > > >>> A ops4j-base-util-xml-1.2.3.jar
> > > >>> A pax-url-maven-commons-1.3.5.jar
> > > >>> A plexus-classworlds-2.4.jar
> > > >>> A plexus-component-annotations-1.5.5.jar
> > > >>> A plexus-container-default-1.5.5.jar
> > > >>> A plexus-interpolation-1.14.jar
> > > >>> A plexus-utils-2.0.6.jar
> > > >>> A sisu-guice-3.0.3-no_aop.jar
> > > >>> A sisu-inject-bean-2.2.3.jar
> > > >>> A sisu-inject-plexus-2.2.3.jar
> > > >>> A slf4j-jdk14-1.6.4.jar
> > > >>> A sshd-core-0.6.0.jar
> > > >>> A wagon-file-2.2.jar
> > > >>> A wagon-http-2.2.jar
> > > >>> A wagon-http-shared4-2.2.jar
> > > >>> A wagon-provider-api-2.2.jar
> > > >>
> > > >> This is really where we need the most discussion. There are some
> > > >> challenges:
> > > >>
> > > >> - 37 new libraries is a lot to legally screen (each will need NOTICE
> > > file
> > > >> additions and possibly a couple LICENSE additions). This will take
> a
> > > week
> > > >> or more as everyone on the PMC is legally required to review this
> > > >> information for accuracy before they can vote.
> > > >> - 37 new libraries is a lot to add prior to a final with no previous
> > > beta
> > > >> exposure.
> > > >> - 1.0 final is maybe not the best term for functionality that is
> > really
> > > >> an alpha or beta.
> > > >> - Could apply to all distros: no easy way to add this functionality
> to
> > > >> TomEE WebProfile or OpenEJB Standalone.
> > > >>
> > > >> I see two basic solutions, more are possible, but here goes:
> > > >>
> > > >> 1. Leave things the way they are and hold 1.0 till all can be
> legally
> > > >> screened. This would be a 1.0 final feature of TomEE+ only.
> > > >> 2. Hold this functionality till it can be legally screened.
> Release
> > it
> > > >> as an alpha or beta, possibly in the form of a zip that can be
> > extracted
> > > >> into a TomEE, TomEE+, or OpenEJB install.
> > > >> 3. Other (insert proposal here :)
> > > >>
> > > >>
> > > >> Thoughts?
> > > >>
> > > >>
> > > >> -David
> > > >>
> > > >>
> > >
> > >
> >
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
Re: [DISCUSSION] 1.0.0 library change
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
+1, that seems great to me.
JLouis
Le 13 avril 2012 11:25, Romain Manni-Bucau <rm...@gmail.com> a écrit :
> yep that's probably the best compromise between simplicity, features,
> weight and work for the release.
>
> - Romain
>
>
> 2012/4/13 David Blevins <da...@gmail.com>
>
> > Had a quick chat with Romain on IRC. I proposed some kind of
> > mini-downloader for the future zip that will contain all the provisioning
> > libs. The downloader would pull down the zip and install the libs.
> > There'd be some sort of button/cli for doing the install.
> >
> > This means:
> >
> > 1) we can get TomEE final out quicker
> > 2) we can get this in all 3 of the servers (not just TomEE+)
> > 3) it can clearly be marked as beta allowing us to incorporate feedback
> > (we wouldn't have to treat it as stable)
> >
> > More thoughts welcome of course.
> >
> >
> > -David
> >
> > On Apr 12, 2012, at 11:35 PM, Romain Manni-Bucau wrote:
> >
> > > Hi,
> > >
> > > -100 for 2): IMHO it is a great feature which should be part of tomee+
> > > bundle
> > > -1 to do another beta which simply means for a lot of people dont use
> me
> > > +1 to keep the way it is and simply fix potential dependencies issues
> > (asm
> > > for instance)
> > >
> > > gson is used for common cli module to output data but we probably can
> do
> > > something simpler, i think Thiago uses it too for the GUI for next
> > releases
> > > (but same note, just the info we need to keep something to do json)
> > >
> > > - Romain
> > >
> > >
> > > 2012/4/13 David Blevins <da...@gmail.com>
> > >
> > >> Responding in a second email (wanted to keep the original data clean).
> > >>
> > >>> A asm-3.2.jar
> > >>
> > >> This is one of the libraries we intentionally repackage (xbean-asm) in
> > >> order to avoid library conflicts with other popular libs (like
> > hibernate).
> > >>
> > >> I'll have a look to see what is pulling in asm and see if it can be
> > >> removed.
> > >>
> > >>> A gson-2.1.jar
> > >>
> > >> Do we still need this? If so we'll need it listed in all of our
> NOTICE
> > >> files for the tomee wars, tomee zips, and openejb standalone zips.
> > >>
> > >>> apache-tomee 1.0.0 plus
> > >>>
> > >>> A aether-api-1.13.1.jar
> > >>> A aether-connector-wagon-1.13.1.jar
> > >>> A aether-impl-1.13.1.jar
> > >>> A aether-spi-1.13.1.jar
> > >>> A aether-util-1.13.1.jar
> > >>> A google-collections-1.0.jar
> > >>> A httpclient-4.1.2.jar
> > >>> A httpcore-4.1.2.jar
> > >>> A jline-0.9.94.jar
> > >>> A jsoup-1.6.1.jar
> > >>> A maven-aether-provider-3.0.4.jar
> > >>> A maven-model-3.0.4.jar
> > >>> A maven-model-builder-3.0.4.jar
> > >>> A maven-repository-metadata-3.0.4.jar
> > >>> A mina-core-2.0.2.jar
> > >>> A openejb-common-cli-4.0.0.jar
> > >>> A openejb-provisionning-4.0.0.jar
> > >>> A openejb-ssh-4.0.0.jar
> > >>> A ops4j-base-lang-1.2.3.jar
> > >>> A ops4j-base-util-collections-1.2.3.jar
> > >>> A ops4j-base-util-property-1.2.3.jar
> > >>> A ops4j-base-util-xml-1.2.3.jar
> > >>> A pax-url-maven-commons-1.3.5.jar
> > >>> A plexus-classworlds-2.4.jar
> > >>> A plexus-component-annotations-1.5.5.jar
> > >>> A plexus-container-default-1.5.5.jar
> > >>> A plexus-interpolation-1.14.jar
> > >>> A plexus-utils-2.0.6.jar
> > >>> A sisu-guice-3.0.3-no_aop.jar
> > >>> A sisu-inject-bean-2.2.3.jar
> > >>> A sisu-inject-plexus-2.2.3.jar
> > >>> A slf4j-jdk14-1.6.4.jar
> > >>> A sshd-core-0.6.0.jar
> > >>> A wagon-file-2.2.jar
> > >>> A wagon-http-2.2.jar
> > >>> A wagon-http-shared4-2.2.jar
> > >>> A wagon-provider-api-2.2.jar
> > >>
> > >> This is really where we need the most discussion. There are some
> > >> challenges:
> > >>
> > >> - 37 new libraries is a lot to legally screen (each will need NOTICE
> > file
> > >> additions and possibly a couple LICENSE additions). This will take a
> > week
> > >> or more as everyone on the PMC is legally required to review this
> > >> information for accuracy before they can vote.
> > >> - 37 new libraries is a lot to add prior to a final with no previous
> > beta
> > >> exposure.
> > >> - 1.0 final is maybe not the best term for functionality that is
> really
> > >> an alpha or beta.
> > >> - Could apply to all distros: no easy way to add this functionality to
> > >> TomEE WebProfile or OpenEJB Standalone.
> > >>
> > >> I see two basic solutions, more are possible, but here goes:
> > >>
> > >> 1. Leave things the way they are and hold 1.0 till all can be legally
> > >> screened. This would be a 1.0 final feature of TomEE+ only.
> > >> 2. Hold this functionality till it can be legally screened. Release
> it
> > >> as an alpha or beta, possibly in the form of a zip that can be
> extracted
> > >> into a TomEE, TomEE+, or OpenEJB install.
> > >> 3. Other (insert proposal here :)
> > >>
> > >>
> > >> Thoughts?
> > >>
> > >>
> > >> -David
> > >>
> > >>
> >
> >
>
Re: [DISCUSSION] 1.0.0 library change
Posted by Romain Manni-Bucau <rm...@gmail.com>.
yep that's probably the best compromise between simplicity, features,
weight and work for the release.
- Romain
2012/4/13 David Blevins <da...@gmail.com>
> Had a quick chat with Romain on IRC. I proposed some kind of
> mini-downloader for the future zip that will contain all the provisioning
> libs. The downloader would pull down the zip and install the libs.
> There'd be some sort of button/cli for doing the install.
>
> This means:
>
> 1) we can get TomEE final out quicker
> 2) we can get this in all 3 of the servers (not just TomEE+)
> 3) it can clearly be marked as beta allowing us to incorporate feedback
> (we wouldn't have to treat it as stable)
>
> More thoughts welcome of course.
>
>
> -David
>
> On Apr 12, 2012, at 11:35 PM, Romain Manni-Bucau wrote:
>
> > Hi,
> >
> > -100 for 2): IMHO it is a great feature which should be part of tomee+
> > bundle
> > -1 to do another beta which simply means for a lot of people dont use me
> > +1 to keep the way it is and simply fix potential dependencies issues
> (asm
> > for instance)
> >
> > gson is used for common cli module to output data but we probably can do
> > something simpler, i think Thiago uses it too for the GUI for next
> releases
> > (but same note, just the info we need to keep something to do json)
> >
> > - Romain
> >
> >
> > 2012/4/13 David Blevins <da...@gmail.com>
> >
> >> Responding in a second email (wanted to keep the original data clean).
> >>
> >>> A asm-3.2.jar
> >>
> >> This is one of the libraries we intentionally repackage (xbean-asm) in
> >> order to avoid library conflicts with other popular libs (like
> hibernate).
> >>
> >> I'll have a look to see what is pulling in asm and see if it can be
> >> removed.
> >>
> >>> A gson-2.1.jar
> >>
> >> Do we still need this? If so we'll need it listed in all of our NOTICE
> >> files for the tomee wars, tomee zips, and openejb standalone zips.
> >>
> >>> apache-tomee 1.0.0 plus
> >>>
> >>> A aether-api-1.13.1.jar
> >>> A aether-connector-wagon-1.13.1.jar
> >>> A aether-impl-1.13.1.jar
> >>> A aether-spi-1.13.1.jar
> >>> A aether-util-1.13.1.jar
> >>> A google-collections-1.0.jar
> >>> A httpclient-4.1.2.jar
> >>> A httpcore-4.1.2.jar
> >>> A jline-0.9.94.jar
> >>> A jsoup-1.6.1.jar
> >>> A maven-aether-provider-3.0.4.jar
> >>> A maven-model-3.0.4.jar
> >>> A maven-model-builder-3.0.4.jar
> >>> A maven-repository-metadata-3.0.4.jar
> >>> A mina-core-2.0.2.jar
> >>> A openejb-common-cli-4.0.0.jar
> >>> A openejb-provisionning-4.0.0.jar
> >>> A openejb-ssh-4.0.0.jar
> >>> A ops4j-base-lang-1.2.3.jar
> >>> A ops4j-base-util-collections-1.2.3.jar
> >>> A ops4j-base-util-property-1.2.3.jar
> >>> A ops4j-base-util-xml-1.2.3.jar
> >>> A pax-url-maven-commons-1.3.5.jar
> >>> A plexus-classworlds-2.4.jar
> >>> A plexus-component-annotations-1.5.5.jar
> >>> A plexus-container-default-1.5.5.jar
> >>> A plexus-interpolation-1.14.jar
> >>> A plexus-utils-2.0.6.jar
> >>> A sisu-guice-3.0.3-no_aop.jar
> >>> A sisu-inject-bean-2.2.3.jar
> >>> A sisu-inject-plexus-2.2.3.jar
> >>> A slf4j-jdk14-1.6.4.jar
> >>> A sshd-core-0.6.0.jar
> >>> A wagon-file-2.2.jar
> >>> A wagon-http-2.2.jar
> >>> A wagon-http-shared4-2.2.jar
> >>> A wagon-provider-api-2.2.jar
> >>
> >> This is really where we need the most discussion. There are some
> >> challenges:
> >>
> >> - 37 new libraries is a lot to legally screen (each will need NOTICE
> file
> >> additions and possibly a couple LICENSE additions). This will take a
> week
> >> or more as everyone on the PMC is legally required to review this
> >> information for accuracy before they can vote.
> >> - 37 new libraries is a lot to add prior to a final with no previous
> beta
> >> exposure.
> >> - 1.0 final is maybe not the best term for functionality that is really
> >> an alpha or beta.
> >> - Could apply to all distros: no easy way to add this functionality to
> >> TomEE WebProfile or OpenEJB Standalone.
> >>
> >> I see two basic solutions, more are possible, but here goes:
> >>
> >> 1. Leave things the way they are and hold 1.0 till all can be legally
> >> screened. This would be a 1.0 final feature of TomEE+ only.
> >> 2. Hold this functionality till it can be legally screened. Release it
> >> as an alpha or beta, possibly in the form of a zip that can be extracted
> >> into a TomEE, TomEE+, or OpenEJB install.
> >> 3. Other (insert proposal here :)
> >>
> >>
> >> Thoughts?
> >>
> >>
> >> -David
> >>
> >>
>
>
Re: [DISCUSSION] 1.0.0 library change
Posted by David Blevins <da...@gmail.com>.
Had a quick chat with Romain on IRC. I proposed some kind of mini-downloader for the future zip that will contain all the provisioning libs. The downloader would pull down the zip and install the libs. There'd be some sort of button/cli for doing the install.
This means:
1) we can get TomEE final out quicker
2) we can get this in all 3 of the servers (not just TomEE+)
3) it can clearly be marked as beta allowing us to incorporate feedback (we wouldn't have to treat it as stable)
More thoughts welcome of course.
-David
On Apr 12, 2012, at 11:35 PM, Romain Manni-Bucau wrote:
> Hi,
>
> -100 for 2): IMHO it is a great feature which should be part of tomee+
> bundle
> -1 to do another beta which simply means for a lot of people dont use me
> +1 to keep the way it is and simply fix potential dependencies issues (asm
> for instance)
>
> gson is used for common cli module to output data but we probably can do
> something simpler, i think Thiago uses it too for the GUI for next releases
> (but same note, just the info we need to keep something to do json)
>
> - Romain
>
>
> 2012/4/13 David Blevins <da...@gmail.com>
>
>> Responding in a second email (wanted to keep the original data clean).
>>
>>> A asm-3.2.jar
>>
>> This is one of the libraries we intentionally repackage (xbean-asm) in
>> order to avoid library conflicts with other popular libs (like hibernate).
>>
>> I'll have a look to see what is pulling in asm and see if it can be
>> removed.
>>
>>> A gson-2.1.jar
>>
>> Do we still need this? If so we'll need it listed in all of our NOTICE
>> files for the tomee wars, tomee zips, and openejb standalone zips.
>>
>>> apache-tomee 1.0.0 plus
>>>
>>> A aether-api-1.13.1.jar
>>> A aether-connector-wagon-1.13.1.jar
>>> A aether-impl-1.13.1.jar
>>> A aether-spi-1.13.1.jar
>>> A aether-util-1.13.1.jar
>>> A google-collections-1.0.jar
>>> A httpclient-4.1.2.jar
>>> A httpcore-4.1.2.jar
>>> A jline-0.9.94.jar
>>> A jsoup-1.6.1.jar
>>> A maven-aether-provider-3.0.4.jar
>>> A maven-model-3.0.4.jar
>>> A maven-model-builder-3.0.4.jar
>>> A maven-repository-metadata-3.0.4.jar
>>> A mina-core-2.0.2.jar
>>> A openejb-common-cli-4.0.0.jar
>>> A openejb-provisionning-4.0.0.jar
>>> A openejb-ssh-4.0.0.jar
>>> A ops4j-base-lang-1.2.3.jar
>>> A ops4j-base-util-collections-1.2.3.jar
>>> A ops4j-base-util-property-1.2.3.jar
>>> A ops4j-base-util-xml-1.2.3.jar
>>> A pax-url-maven-commons-1.3.5.jar
>>> A plexus-classworlds-2.4.jar
>>> A plexus-component-annotations-1.5.5.jar
>>> A plexus-container-default-1.5.5.jar
>>> A plexus-interpolation-1.14.jar
>>> A plexus-utils-2.0.6.jar
>>> A sisu-guice-3.0.3-no_aop.jar
>>> A sisu-inject-bean-2.2.3.jar
>>> A sisu-inject-plexus-2.2.3.jar
>>> A slf4j-jdk14-1.6.4.jar
>>> A sshd-core-0.6.0.jar
>>> A wagon-file-2.2.jar
>>> A wagon-http-2.2.jar
>>> A wagon-http-shared4-2.2.jar
>>> A wagon-provider-api-2.2.jar
>>
>> This is really where we need the most discussion. There are some
>> challenges:
>>
>> - 37 new libraries is a lot to legally screen (each will need NOTICE file
>> additions and possibly a couple LICENSE additions). This will take a week
>> or more as everyone on the PMC is legally required to review this
>> information for accuracy before they can vote.
>> - 37 new libraries is a lot to add prior to a final with no previous beta
>> exposure.
>> - 1.0 final is maybe not the best term for functionality that is really
>> an alpha or beta.
>> - Could apply to all distros: no easy way to add this functionality to
>> TomEE WebProfile or OpenEJB Standalone.
>>
>> I see two basic solutions, more are possible, but here goes:
>>
>> 1. Leave things the way they are and hold 1.0 till all can be legally
>> screened. This would be a 1.0 final feature of TomEE+ only.
>> 2. Hold this functionality till it can be legally screened. Release it
>> as an alpha or beta, possibly in the form of a zip that can be extracted
>> into a TomEE, TomEE+, or OpenEJB install.
>> 3. Other (insert proposal here :)
>>
>>
>> Thoughts?
>>
>>
>> -David
>>
>>
Re: [DISCUSSION] 1.0.0 library change
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi,
-100 for 2): IMHO it is a great feature which should be part of tomee+
bundle
-1 to do another beta which simply means for a lot of people dont use me
+1 to keep the way it is and simply fix potential dependencies issues (asm
for instance)
gson is used for common cli module to output data but we probably can do
something simpler, i think Thiago uses it too for the GUI for next releases
(but same note, just the info we need to keep something to do json)
- Romain
2012/4/13 David Blevins <da...@gmail.com>
> Responding in a second email (wanted to keep the original data clean).
>
> > A asm-3.2.jar
>
> This is one of the libraries we intentionally repackage (xbean-asm) in
> order to avoid library conflicts with other popular libs (like hibernate).
>
> I'll have a look to see what is pulling in asm and see if it can be
> removed.
>
> > A gson-2.1.jar
>
> Do we still need this? If so we'll need it listed in all of our NOTICE
> files for the tomee wars, tomee zips, and openejb standalone zips.
>
> > apache-tomee 1.0.0 plus
> >
> > A aether-api-1.13.1.jar
> > A aether-connector-wagon-1.13.1.jar
> > A aether-impl-1.13.1.jar
> > A aether-spi-1.13.1.jar
> > A aether-util-1.13.1.jar
> > A google-collections-1.0.jar
> > A httpclient-4.1.2.jar
> > A httpcore-4.1.2.jar
> > A jline-0.9.94.jar
> > A jsoup-1.6.1.jar
> > A maven-aether-provider-3.0.4.jar
> > A maven-model-3.0.4.jar
> > A maven-model-builder-3.0.4.jar
> > A maven-repository-metadata-3.0.4.jar
> > A mina-core-2.0.2.jar
> > A openejb-common-cli-4.0.0.jar
> > A openejb-provisionning-4.0.0.jar
> > A openejb-ssh-4.0.0.jar
> > A ops4j-base-lang-1.2.3.jar
> > A ops4j-base-util-collections-1.2.3.jar
> > A ops4j-base-util-property-1.2.3.jar
> > A ops4j-base-util-xml-1.2.3.jar
> > A pax-url-maven-commons-1.3.5.jar
> > A plexus-classworlds-2.4.jar
> > A plexus-component-annotations-1.5.5.jar
> > A plexus-container-default-1.5.5.jar
> > A plexus-interpolation-1.14.jar
> > A plexus-utils-2.0.6.jar
> > A sisu-guice-3.0.3-no_aop.jar
> > A sisu-inject-bean-2.2.3.jar
> > A sisu-inject-plexus-2.2.3.jar
> > A slf4j-jdk14-1.6.4.jar
> > A sshd-core-0.6.0.jar
> > A wagon-file-2.2.jar
> > A wagon-http-2.2.jar
> > A wagon-http-shared4-2.2.jar
> > A wagon-provider-api-2.2.jar
>
> This is really where we need the most discussion. There are some
> challenges:
>
> - 37 new libraries is a lot to legally screen (each will need NOTICE file
> additions and possibly a couple LICENSE additions). This will take a week
> or more as everyone on the PMC is legally required to review this
> information for accuracy before they can vote.
> - 37 new libraries is a lot to add prior to a final with no previous beta
> exposure.
> - 1.0 final is maybe not the best term for functionality that is really
> an alpha or beta.
> - Could apply to all distros: no easy way to add this functionality to
> TomEE WebProfile or OpenEJB Standalone.
>
> I see two basic solutions, more are possible, but here goes:
>
> 1. Leave things the way they are and hold 1.0 till all can be legally
> screened. This would be a 1.0 final feature of TomEE+ only.
> 2. Hold this functionality till it can be legally screened. Release it
> as an alpha or beta, possibly in the form of a zip that can be extracted
> into a TomEE, TomEE+, or OpenEJB install.
> 3. Other (insert proposal here :)
>
>
> Thoughts?
>
>
> -David
>
>