Yes, please, upload your code.
I will try to update them for 1.1.
Thanks,
Guillaume Nodet
anita kulshreshtha wrote:
Comments inline..
--- Guillaume Nodet <[EMAIL PROTECTED]> wrote:
Plugins are quite independant of the build afaik (even if they are
used
by the main build).
They could be written for G 1.1 and updated for G 1.x and have their
lifecycle decorrelated from Geronimo.
Usually they are and will be in the future... The change from HEAD
to 1.1 is so drastic that there was no point in continuing the
development of packaging and other plugins in the HEAD.
As they will be very useful for people creating plugins, I think it
could be interesting to write them for 1.1 before of the m2 switch.
Is there any beginning of implementation available somewhere ?
I have some code for packaging plugin for 1.1 that compiles but you
would need M2 geronimo-* jars for that. There is no point using the
HEAD for anything now. Please let me know if you want me upload a patch
to the jira.
Thanks
Anita
Cheers,
Guillaume Nodet
anita kulshreshtha wrote:
All work related to M2 was halted until the trunk was merged. M2
packaging plugin would require transferring all M2 work to 1.1. I do
not think there are any plans to do it before the merge or at least
the
1.1. release. I think using Maven1 will be best at this time. Let's
hear from Jacek..
Thanks
Anita
--- Guillaume Nodet <[EMAIL PROTECTED]> wrote:
I haven't seen any geronimo plugin for m2 in head.
That whould be very usefull, especially because Geronimo plugins
have
to
be in a m2 layout, but the only tools to create a car is a m1
plugin.
Any idea ?
Cheers,
Guillaume Nodet
Aaron Mulder wrote:
I'd rather handle the ApacheDS integration separately from the 1.1
release. Fortunately, the plugins work with the Maven 2
repository,
so that issue should be easier.
The main question is how to do the build and packaging. If the
API
is
unchanged, we can build our integration module using our Maven 1
packaging plugin against ADS 0.9.2 and just have it apply the
1.0.x
JARs at installation time. If the API is different, it may make
the
most sense to try to split out our directory integration and do
the
build and packaging under Maven 2 (I'm assuming that Geronimo HEAD
has
a Maven 2 packaging plugin, but if not, I guess we can work on
one).
Thanks,
Aaron
On 5/10/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote:
ApacheDS 0.9.2 to 1.0-RC2 ?
I have a patch to port the Geronimo part to 1.0-RC2. However,
currently ADS 1.0 jars propagated to maven2 repo only.
2006/5/9, Matt Hogstrom <[EMAIL PROTECTED]>:
Consolidated list so far is:
Axis from 1.4-356167 to 1.4
commons-fileupload 1.1-dev to 1.1
jasper from 5.5.9 to 5.5.15
Jetty from 5.1.9 to 5.1.10
stax from 1.1.1-dev to 1.1.2
Tomcat 5.5.9 to 5.5.15
tranql from 1.2.1 to 1.3-SNAPSHOT
tranql-connector from 1.1 to 1.2-SNAPSHOT
Keep 'em coming.
Matt
Aaron Mulder wrote:
That issue has a great list.
We definitely need to try updating commons-fileupload (from
1.1-dev to
1.1). I think there may even be a separate Jira for that.
But the
old one occasionally hangs, so it's definitely worth trying
the new
one.
Thanks,
Aaron
On 5/9/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
Here are the packages I'm recommending for 1.1. If I missed
one
please chime in.
Axis from 1.4-356167 to 1.4
jasper from 5.5.9 to 5.5.15
Jetty from 5.1.9 to 5.1.10
stax from 1.1.1-dev to 1.1.2
tranql from 1.2.1 to 1.3-SNAPSHOT
tranql-connector from 1.1 to 1.2-SNAPSHOT
This is the list so far...I've updated
http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking
with this information.
Was mentioned on the list:
Howl - Researching this
--
Alexei Zakharov,
Intel Middleware Product Division
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
