The note I saw on our Jira said that commons-fileupload 1.1 requires
commons-io 1.1 -- do you have a separate indication that commons-io
1.2 is needed?
http://issues.apache.org/jira/browse/GERONIMO-1756
http://jakarta.apache.org/commons/fileupload/changes-report.html
Thanks,
Aaron
On
Kevan Miller wrote:
On May 9, 2006, at 12:42 PM, Matt Hogstrom wrote:
Consolidated list so far is:
Axis from 1.4-356167 to 1.4
commons-fileupload1.1-devto1.1
jasper from 5.5.9 to 5.5.15
Jetty from 5.1.9
Gianny,
TranQL 1.3 has several performance and feature fixes (thanks to you) that we've been planning on for
1.1. I didn't realize the changes to OpenEJB however. I'd like to get this release wrapped up the
week after Java One if possible (end of the month). Can you guesstimate the
Let's address Directory in 1.2. Since its not core to CTS I think it would be pushing 1.1 out. It
would be awesome to get this updated in 1.2 when we finally ship 1.1. Looking at the packages out
there we are ut of date on several so one of the first things I'd like to do is get current on
Since the M2 conversion is independent of 1.1 what does the community think about starting that
merge into 1.1 now? I think it would allow us to become more productive on 1.2 since the work would
already be in place. For those working on the M2 conversion what do you think about starting that
--- Matt Hogstrom [EMAIL PROTECTED] wrote:
Since the M2 conversion is independent of 1.1 what does the community
think about starting that
merge into 1.1 now? I think it would allow us to become more
productive on 1.2 since the work would
already be in place. For those working on the
Hi Matt,
Moving the M2 conversion work from the trunk to 1.1 should not be
disruptive. It would have the following changes
1) add pom.xmls in all modules
2) add a few ant files in some modules
3) change *Test.java files in quite a few modules.
I have no strong objections to it except that I'm
What are the ant files used for ?
And why changing the test class names ? Surefire can be configured
specifically if needed ... So this change could be delayed.
Cheers,
Guillaume Nodet
Prasad Kashyap wrote:
Hi Matt,
Moving the M2 conversion work from the trunk to 1.1 should not be
Ant files are used to do some custom things that jelly did in Maven 1.
Eg: modules\installer-support\setup.xml
The Test class names didn't change. Minor modifications to the code in
the *Test.java were done. Sorry for the confusion.
Cheers
Prasad
On 5/11/06, Guillaume Nodet [EMAIL PROTECTED]
Someone hit me in the head about priorities (I think it was Prasad). If someone isn't working on
1.1 and has time this is excellent. Please don't let me distract you from 1.1 though :)
Prasad Kashyap wrote:
Hi Matt,
Moving the M2 conversion work from the trunk to 1.1 should not be
On 5/10/06, anita kulshreshtha [EMAIL PROTECTED] 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
ApacheDS0.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
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
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
FYI: ADS API has changed significantly since 0.9.2.
2006/5/10, Aaron Mulder [EMAIL PROTECTED]:
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
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..
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.
As they will be very useful for people creating plugins, I think it
could be interesting to
So my understanding of things is that we have the full set of G 1.1
plugins for Maven 1, and it would be nice to also have at least a G
1.1 packaging plugin for Maven 2 (though we'll need them all in due
course).
For the Maven 1 plugin, it looks like we have some Jelly code and a
Java
Comments inline...
--- Aaron Mulder [EMAIL PROTECTED] wrote:
So my understanding of things is that we have the full set of G 1.1
plugins for Maven 1, and it would be nice to also have at least a G
1.1 packaging plugin for Maven 2 (though we'll need them all in due
course).
For the Maven 1
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
Chime!
TC - 5.5.15
Matt Hogstrom wrote:
Here are the packages I'm recommending for 1.1. If I missed one please
chime in.
Axis from 1.4-356167to 1.4
jasper from 5.5.9to5.5.15
Jetty from5.1.9to5.1.10
stax from1.1.1-devto
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
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
On May 9, 2006, at 12:42 PM, Matt Hogstrom wrote:
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
You are correct Kevan. Thanks
Kevan Miller wrote:
On May 9, 2006, at 12:42 PM, Matt Hogstrom wrote:
Consolidated list so far is:
Axis from 1.4-356167 to 1.4
commons-fileupload1.1-devto1.1
jasper from 5.5.9 to 5.5.15
Jetty
I've built locally using HOWL 1.0.1 and it seems to work fine with no
geronimo changes. I think the main problem will be getting it onto a
suitable maven repo: I haven't found it to be released anywhere.
Is pushing it into a m2 repo sufficient, are jars auto-backported
into m1?
Moving to Commons-Fileupload 1.1 also requires upgrading to commons-io 1.2.
Also, why are we upgrading to STAX 1.1.1, when all we need is just the
STAX API?
-Donald
David Jencks wrote:
I've built locally using HOWL 1.0.1 and it seems to work fine with no
geronimo changes. I think the
27 matches
Mail list logo
