Hi all,
Hope all has been going well. I've still been actively using everything
as is with a few
dev jars. It would be great to get a release out. I have not yet
gotten up to speed
with Maven2. But let me know if you run into any problems I can help
out with.
Background:
Quite a while ago (last year? The year before??) When we had been
working on
another release, I had brought up doing a final release of the i18n jar
which included
all of the changes that were in the source at the time that it was
deprecated.
To make that possible, I had created the following branch:
https://svn.apache.org/viewvc/excalibur/branches/i18n-Delete/
I don't remember all the details of why it was deleted rather than
simply deprecated,
but it is still being used. I know there are other projects that do the
same thing, but
this one was used quite widely in a number of my projects.
Questions:
1) I am still using a dev release of the i18n jar. Would it be possible
to put out a
final(?) release of the latest code along with this release?
2) Would anyone have any objections to moving the i18n source from the
deleted
status back to the deprecated status by placing it under the following
directory
with things like "event"?
https://svn.apache.org/viewvc/excalibur/trunk/deprecated/
If this is Ok then I will take care of it.
Thanks,
Leif
Jorg Heymans wrote:
On 01 Sep 2006, at 22:29, Vadim Gritsenko wrote:
Ok, I fixed the NPE which I introduced, so 'mvn install' from within
components/xmlutil works just fine now.
But, for me, it fails if I invoke 'mvn install' from excalibur
root... What's up with that? Is it something with me, maven, or
something else? :)
it fails on both occasions for me. Are you sure it works from
components/xmlutil ? try doing "mvn clean test"
Jorg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
