On Jul 21, 2005, at 7:00 PM, Aaron Mulder wrote:
Where in maven would this appear? I wonder if we should create a
"geronimo-dependencies" virtual project or something, as opposed to
putting something like this side by side with the proper geronimo
artifacts. What do others think?
geronimo/jars (our output)
geronimo/wars (our demo apps)
geronimo-spec/jars (our spec output)
geronimo-dependencies/jars/ (put pluto thing here)
I think that this is confusing, because things like openejb, mx4j,
tomcat... are dependencies too.
can we just put the things we create in geronimo/jars?
geir
Aaron
On Thu, 21 Jul 2005, Dave Colasurdo wrote:
The JIRA entry for the console (GERONIMO-762) has been updated
with the
instructions for creating pluto-portal.jar (actually the JIRA
contains
the jar as well).
Is the required fix as simple as:
1) Rename pluto-portal-1.0.1-rc2.jar to geronimo-pluto-portal.jar
2) Publish the new jar to the Apache maven repository
3) Change the console dependency references to use the new name
Any issues with this approach?
Are special privileges required to publish to the Apache maven
repository (http://cvs.apache.org/repository/)?
Thanks
-Dave-
Aaron Mulder wrote:
So it seems that the Pluto problem is pretty serious. We're
actually dependent on an artifact that Pluto does not produce.
There is
no "pluto-portal" output from the Pluto build. I think that
means we
shouldn't be calling it "pluto-portal", but instead
"geronimo-package-of-pluto-portal-code" or something along those
lines
(but perhaps shorter).
No wonder the Pluto fellow is not putting it in Maven! :)
Aaron
--
Geir Magnusson Jr +1-203-665-6437
[EMAIL PROTECTED]
