-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Nick,
On Wed, 25 Apr 2007, Joerg Hohwiller wrote:
But from what I see in your subversion, you still need to replace
issueTrackingUrl with issueManagement.
Done
I also went through your ant build and have seen that you do not
modify the
On Wed, 25 Apr 2007, Joerg Hohwiller wrote:
But from what I see in your subversion, you still need to replace
issueTrackingUrl with issueManagement.
Done
I also went through your ant build and have seen that you do not modify
the root tag metadata. The also needs to be changed to project,
On Tue, 24 Apr 2007, Joerg Hohwiller wrote:
issueManagement
systembugzilla/system
urlhttp://issues.apache.org/bugzilla//url
/issueManagement
Thanks, I've updated that
BTW: I assume that we are just talking about maven2 here and NOT about
maven1.
Since that seems to be the version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Nick,
On Tue, 24 Apr 2007, Joerg Hohwiller wrote:
issueManagement
systembugzilla/system
urlhttp://issues.apache.org/bugzilla//url
/issueManagement
Thanks, I've updated that
okay.
But from what I see in your subversion, you still
No you clarified that Maven is an even more convoluted clusterfsck than
I remembered.
Joerg Hohwiller wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Nick,
On Tue, 24 Apr 2007, Joerg Hohwiller wrote:
issueManagement
systembugzilla/system
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Nick,
So bug #39977 is not an issue anymore?
The groupId bit isn't. Now we understand what it should be, we can use
the java package, and all will be fine.
Comment #2 (http://issues.apache.org/bugzilla/show_bug.cgi?id=39977#c2)
still needs
On Thu, 19 Apr 2007, Joerg Hohwiller wrote:
So bug #39977 is not an issue anymore?
The groupId bit isn't. Now we understand what it should be, we can use the
java package, and all will be fine.
Comment #2 (http://issues.apache.org/bugzilla/show_bug.cgi?id=39977#c2)
still needs looking at,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Nick,
Are you planning to put the 3.0 release into the maven repository as
soon as it is out?
As part of the release process, I'll copy them onto people.apache.org,
as per
http://www.apache.org/dev/release-publishing.html#repository-guide
On Tue, 17 Apr 2007, Joerg Hohwiller wrote:
Are you planning to put the 3.0 release into the maven repository as
soon as it is out?
As part of the release process, I'll copy them onto people.apache.org, as
per http://www.apache.org/dev/release-publishing.html#repository-guide .
Apparently
to put the 3.0 release into the maven repository as soon as it
is out? I would be very pleased if this could happen quickly. If I can help
anyhow on this task, just let me know.
Is there something to discuss, that could be done now rather than after the
release has been pulled out? E.g. if the goupId
incompatibility of HSSF
(was it
UnicodeString instead of String as return-type? cant remember) but
that does not
matter for me.
The WordExtractor is also very useful and will allow me to kick out
tm-extractors.
Are you planning to put the 3.0 release into the maven repository
as soon
11 matches
Mail list logo