Joe Bohn wrote:
Joe Bohn wrote:
Joe Bohn wrote:
Jarek Gawor wrote:
On Tue, Mar 11, 2008 at 1:20 PM, Joe Bohn [EMAIL PROTECTED]
wrote:
5) Should we make all samples plugins? At the moment the
jsp-examples,
servlet-examples, and ldap-sample-app are plugins. The other 12
samples
are not.
Joe Bohn wrote:
Jarek Gawor wrote:
On Tue, Mar 11, 2008 at 1:20 PM, Joe Bohn [EMAIL PROTECTED] wrote:
5) Should we make all samples plugins? At the moment the jsp-examples,
servlet-examples, and ldap-sample-app are plugins. The other 12
samples
are not. I'd be in favor of creating a
Joe Bohn wrote:
Joe Bohn wrote:
Jarek Gawor wrote:
On Tue, Mar 11, 2008 at 1:20 PM, Joe Bohn [EMAIL PROTECTED]
wrote:
5) Should we make all samples plugins? At the moment the
jsp-examples,
servlet-examples, and ldap-sample-app are plugins. The other 12
samples
are not. I'd be in favor
Jarek Gawor wrote:
On Tue, Mar 11, 2008 at 1:20 PM, Joe Bohn [EMAIL PROTECTED] wrote:
5) Should we make all samples plugins? At the moment the jsp-examples,
servlet-examples, and ldap-sample-app are plugins. The other 12 samples
are not. I'd be in favor of creating a plugin for each and
One alternative we could use for the samples requiring a database is to
standardize a sample database and use the same one for all the sample
applications.
If we go this way maybe we could have a separate plugin to just create and load
a sample DB and make such plugin a dependency on the other
On Tue, Mar 11, 2008 at 1:20 PM, Joe Bohn [EMAIL PROTECTED] wrote:
5) Should we make all samples plugins? At the moment the jsp-examples,
servlet-examples, and ldap-sample-app are plugins. The other 12 samples
are not. I'd be in favor of creating a plugin for each and will work on
doing
On Thu, Mar 13, 2008 at 4:15 PM, Joe Bohn [EMAIL PROTECTED] wrote:
Donald Woods wrote:
User wouldn't have to build anything if each sample was a plug-in
That would be true if the value in a sample just in running it.
However, I think most users want to dig into the source, make minor
Many of the sample wiki entries include *.zip files in addition to
references to the svn repo. These *.zip files include some snapshot of
the source as well as the javadocs, xrefs, ears/wars, and in some cases
even wiki html (I think including the wiki content in a zip is a bad
idea ... it
The archetype needs to be documented in the wiki for 2.1+ if we intend
to encourage its use. I assume that is still the case (please speak-up
otherwise). BTW, I'm not sure what it would mean to release the
archetype. It produces a jar but I'm not sure what it would be used
for. Anybody
We have the following branches in samples:
- geronimo/samples/branches/1.0
Newly added for the migration samples. We'll see what happens with
this branch. We don't have the other 1.0 samples (were there any?)
checked in.
- geronimo/samples/branches/2.0
This includes the samples for
Joe Bohn wrote:
We have the following branches in samples:
- geronimo/samples/branches/1.0
Newly added for the migration samples. We'll see what happens with
this branch. We don't have the other 1.0 samples (were there any?)
checked in.
- geronimo/samples/branches/2.0
This includes
On Mar 13, 2008, at 11:17 AM, Joe Bohn wrote:
The archetype needs to be documented in the wiki for 2.1+ if we
intend to encourage its use. I assume that is still the case
(please speak-up otherwise). BTW, I'm not sure what it would mean
to release the archetype. It produces a jar
David Jencks wrote:
On Mar 13, 2008, at 11:17 AM, Joe Bohn wrote:
The archetype needs to be documented in the wiki for 2.1+ if we intend
to encourage its use. I assume that is still the case (please
speak-up otherwise). BTW, I'm not sure what it would mean to release
the archetype. It
On Mar 13, 2008, at 11:41 AM, Joe Bohn wrote:
David Jencks wrote:
On Mar 13, 2008, at 11:17 AM, Joe Bohn wrote:
The archetype needs to be documented in the wiki for 2.1+ if we
intend to encourage its use. I assume that is still the case
(please speak-up otherwise). BTW, I'm not sure
Joe Bohn wrote:
David Jencks wrote:
On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
Donald Woods wrote:
Joe Bohn wrote:
2) When to release the samples? I think we should make an effort
to release the samples concurrent with each Geronimo release. This
is important because the jsp
We have never yet released artifacts for samples apart from those that
were released as part of a server release via plugins in 2.0.x
(jsp-examples, servlet-examples, and ldap-sample-app). Since these
samples weren't included in the server svn they were not released as
part of the 2.1
On Mar 13, 2008, at 11:47 AM, Joe Bohn wrote:
Joe Bohn wrote:
David Jencks wrote:
On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
Donald Woods wrote:
Joe Bohn wrote:
2) When to release the samples? I think we should make an
effort to release the samples concurrent with each Geronimo
I'd like to see us keep a branches/2.0 and branches/2.1 around, so
people can continue to add and enhance the samples if they wish
-Donald
Joe Bohn wrote:
We have the following branches in samples:
- geronimo/samples/branches/1.0
Newly added for the migration samples. We'll see what
Joe Bohn wrote:
Many of the sample wiki entries include *.zip files in addition to
references to the svn repo. These *.zip files include some snapshot of
the source as well as the javadocs, xrefs, ears/wars, and in some cases
even wiki html (I think including the wiki content in a zip is a
Joe Bohn wrote:
We have the following branches in samples:
- geronimo/samples/branches/1.0
Newly added for the migration samples. We'll see what happens with
this branch. We don't have the other 1.0 samples (were there any?)
checked in.
There were some samples apps for 1.0 scattered all
On Thu, Mar 13, 2008 at 1:47 PM, Joe Bohn [EMAIL PROTECTED] wrote:
Joe Bohn wrote:
David Jencks wrote:
On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
Donald Woods wrote:
Joe Bohn wrote:
2) When to release the samples? I think we should make an effort
to release the samples
I wasn't sure which thread to put this in, so I'll throw it in here. So
far, it seems that when we've been discussing samples, we're lumping the
sample applications and the migration samples in together. Is this
something we want to do? In my mind, they aren't really the same and
shouldn't
Migration samples should definitively not go into svn because the source
environment, the start point for those apps is intended to be a different
platform, not Geronimo. There would be no point in keeping them into svn and
adding them as a part of the release process.
However there are a
User wouldn't have to build anything if each sample was a plug-in
Other thought, why not create a samples assembly which would create a
zip/tar of the binaries that could be downloaded and extracted by a user
to their location of choice. A similar source and repo zipfile could be
created
On Thu, Mar 13, 2008 at 3:44 PM, Hernan Cunico [EMAIL PROTECTED] wrote:
Migration samples should definitively not go into svn because the source
environment, the start point for those apps is intended to be a different
platform, not Geronimo. There would be no point in keeping them into svn
On Thu, Mar 13, 2008 at 2:44 PM, Hernan Cunico [EMAIL PROTECTED] wrote:
Migration samples should definitively not go into svn because the source
environment, the start point for those apps is intended to be a different
platform, not Geronimo. There would be no point in keeping them into svn
Well, from the wiki - Geronimo documentation, there are 3main sets of samples,
well actually 3 now.
1- Migration samples
2- Sample applicaitons
3- Tutorials
1- Migration samples. These should not be in svn unless we plan to maintain and
test sample applications that are intended for JBoss,
On Thu, Mar 13, 2008 at 4:01 PM, Hernan Cunico [EMAIL PROTECTED] wrote:
Well, from the wiki - Geronimo documentation, there are 3main sets of
samples, well actually 3 now.
1- Migration samples
2- Sample applicaitons
3- Tutorials
1- Migration samples. These should not be in svn unless we
Donald Woods wrote:
User wouldn't have to build anything if each sample was a plug-in
That would be true if the value in a sample just in running it.
However, I think most users want to dig into the source, make minor
changes and tweak it as a way to jump start their own development.
Erik B. Craig wrote:
On Thu, Mar 13, 2008 at 2:44 PM, Hernan Cunico [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Migration samples should definitively not go into svn because the
source environment, the start point for those apps is intended to be
a different platform, not
On Thu, Mar 13, 2008 at 3:08 PM, Jason Warner [EMAIL PROTECTED] wrote:
On Thu, Mar 13, 2008 at 4:01 PM, Hernan Cunico [EMAIL PROTECTED] wrote:
Well, from the wiki - Geronimo documentation, there are 3main sets of
samples, well actually 3 now.
1- Migration samples
2- Sample
Joe Bohn wrote:
Donald Woods wrote:
User wouldn't have to build anything if each sample was a plug-in
That would be true if the value in a sample just in running it. However,
I think most users want to dig into the source, make minor changes and
tweak it as a way to jump start their
Erik B. Craig wrote:
On Thu, Mar 13, 2008 at 3:08 PM, Jason Warner [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
On Thu, Mar 13, 2008 at 4:01 PM, Hernan Cunico [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Well, from the wiki - Geronimo documentation, there are
On Thu, Mar 13, 2008 at 3:32 PM, Hernan Cunico [EMAIL PROTECTED] wrote:
Erik B. Craig wrote:
On Thu, Mar 13, 2008 at 3:08 PM, Jason Warner [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
On Thu, Mar 13, 2008 at 4:01 PM, Hernan Cunico [EMAIL PROTECTED]
mailto:[EMAIL
David Jencks wrote:
On Mar 13, 2008, at 11:47 AM, Joe Bohn wrote:
Joe Bohn wrote:
David Jencks wrote:
On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
Donald Woods wrote:
Joe Bohn wrote:
2) When to release the samples? I think we should make an effort
to release the samples concurrent
Donald Woods wrote:
Joe Bohn wrote:
2) When to release the samples? I think we should make an effort to
release the samples concurrent with each Geronimo release. This is
important because the jsp servlet examples are referenced from
within the welcome page on Geronimo. I suppose we
No objection, it should be easier to maintain and as Donald mentioned, we could
get some extra juice out of them as testsuite tests.
My question is where would we put them now. Would they go into server/branches/2.1 so we make them available for 2.1.1?
Cheers!
Hernan
Joe Bohn wrote:
Donald
On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
Donald Woods wrote:
Joe Bohn wrote:
2) When to release the samples? I think we should make an effort
to release the samples concurrent with each Geronimo release.
This is important because the jsp servlet examples are
referenced from
David Jencks wrote:
On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
Donald Woods wrote:
Joe Bohn wrote:
2) When to release the samples? I think we should make an effort to
release the samples concurrent with each Geronimo release. This is
important because the jsp servlet examples are
I agree with David. There is no need to cram everything into
server/trunk. Samples are now hooked up with the automatic Geronimo
builds so I think that should be enough (as long as people will
actaully pay attention if they fail to build ok).
Jarek
On Wed, Mar 12, 2008 at 11:16 AM, David Jencks
I also am in agreement with David on this,
I think it would be a far better approach to not include them within
trunk. While it may be a bit more work to release them separately from
the actual server release, it would seem to be a big step backwards with
what we have been working on.
Perhaps
A bit of unfinished business from 2.1 is the release of samples. I
think we need to get these fixed and available fairly soon for 2.1.
Here are some questions for discussion around that and how we should
manage the samples in general.
1) Do we release all the samples collectively or
On Tue, Mar 11, 2008 at 1:20 PM, Joe Bohn [EMAIL PROTECTED] wrote:
A bit of unfinished business from 2.1 is the release of samples. I
think we need to get these fixed and available fairly soon for 2.1.
Here are some questions for discussion around that and how we should
manage the
Joe,
1. I agree on releasing samples collectively
2. My opinion on when to release is that they should be at the very
least concurrent with each release, if not slightly before. I believe
functional, relevant samples can help reduce barrier to entry.
3. As far as where to keep the source
On Tue, Mar 11, 2008 at 1:34 PM, Erik B. Craig [EMAIL PROTECTED] wrote:
Joe,
1. I agree on releasing samples collectively
2. My opinion on when to release is that they should be at the very
least concurrent with each release, if not slightly before. I believe
functional, relevant samples
On Tue, Mar 11, 2008 at 3:08 PM, Joe Bohn [EMAIL PROTECTED] wrote:
Joe Bohn wrote:
3) Managing sample source. IMO the only place we should maintain source
for the samples is in svn. I think Jarek managed to update all of the
sample doc with references to the svn repo for each sample
That's pretty much it. We should definitively keep them on svn but we should
also make them available as a zip/tar pretty much the same way we do with the
server src. We'd also make those zip files available from the same apache
mirrors we use for the server.
Back to your top 5 list
1) My
Joe Bohn wrote:
Joe Bohn wrote:
One option would be to create a zip per sample in the maven build and
release them as additional artifacts along with the sample plugins,
jars, ears, wars, etc... We could then reference the mirror locations
of these zip files in the wiki pages.
This is a
Viet Nguyen wrote:
snip
These docs are generated through maven, so inclusion or exclusion of
them it easy.
IIUC you are saying that the maven generation of the docs, etc.. into a
zip is already in place (one possible solution I mentioned earlier to
the zip file dilemma). It looks like
+1 to removing zips from the Wiki. Users can use a svn client or browse
the repo to see the source. Lets reduce our release overhead here
-Donald
Joe Bohn wrote:
Joe Bohn wrote:
3) Managing sample source. IMO the only place we should maintain
source for the samples is in svn. I
Joe Bohn wrote:
A bit of unfinished business from 2.1 is the release of samples. I
think we need to get these fixed and available fairly soon for 2.1. Here
are some questions for discussion around that and how we should manage
the samples in general.
1) Do we release all the samples
51 matches
Mail list logo
