Created a -Puser profile.
Revision 498337
Cheers
Prasad
On 1/20/07, Prasad Kashyap [EMAIL PROTECTED] wrote:
Alright.. I can put that in a profile. But a user should be able to
have a way to build and install it all in one go. If that's a profile
invocation, then so be it.
Cheers
Prasad
On
On 1/19/07, Jason Dillon [EMAIL PROTECTED] wrote:
Aight... well, be careful. This looks like that start of an
unmaintainable build configuration.
And... It still does not build:
This should fix it.
Modified: Apache\geronimo\samples\pom.xml
Sending Content: C:\Apache\geronimo\samples\pom.xml
On 1/19/07, Jason Dillon [EMAIL PROTECTED] wrote:
Aight... well, be careful. This looks like that start of an
unmaintainable build configuration.
Moved reporting up to top level.
The individual sample's parent will aggregate the javadoc and xref.
Child modules will have css and images dir.
I don't believe that the default build of samples should attempt to
start Geronimo or deploy anything, which it appears that it currently
does.
The default build, should compile/package/install and should not be
attempting to start or deploy anything.
--jason
On Jan 20, 2007, at 6:21
On 1/20/07, Jason Dillon [EMAIL PROTECTED] wrote:
I don't believe that the default build of samples should attempt to
start Geronimo or deploy anything, which it appears that it currently
does.
The default build, should compile/package/install and should not be
attempting to start or deploy
Alright.. I can put that in a profile. But a user should be able to
have a way to build and install it all in one go. If that's a profile
invocation, then so be it.
Cheers
Prasad
On 1/20/07, Jason Dillon [EMAIL PROTECTED] wrote:
I don't believe that the default build of samples should attempt
Very nice...I like the idea of standalone samples. Without getting
into the specs debate yet again ... but most likely will ... I like
the samples released with the version of the server so people can
pick up one version and know what its for. I think the organization
for now is great as
Why are there reporting elements in the architype (and also in the
first sample), which are not at the top-level, but are in calculator-
stateless-pojo?
Why does this project not inherit from genesis project-config?
Why is the geronimo-maven-plugin configured here?
And why on earth are
Spec versioning with the server would have been nice to help keep
artifacts in sync with the version of the server they are meant to go
with.
The new samples stuff is actually depending on versions of specs
which are not the versions used by the server. Everytime we update a
version of
On Jan 19, 2007, at 5:24 PM, Jason Dillon wrote:
Why are there reporting elements in the architype (and also in the
first sample), which are not at the top-level, but are in
calculator-stateless-pojo?
Why does this project not inherit from genesis project-config?
Why is the
On 1/19/07, Jason Dillon [EMAIL PROTECTED] wrote:
Why are there reporting elements in the architype (and also in the
first sample), which are not at the top-level, but are in calculator-
stateless-pojo?
The requirement is for only 2 reporting elements, javadoc and jxr.
A user should be able to
Aight... well, be careful. This looks like that start of an
unmaintainable build configuration.
And... It still does not build:
snip
Bliss:~/ws/geronimo/samples jason$ mvn
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Geronimo Samples
[INFO] Geronimo Maven2 Plugins
12 matches
Mail list logo
