looking good.
however I see some annoying warnings like
[WARNING] Unable to process class
com/ibm/icu/impl/data/LocaleElements_zh__PINYIN.class in JarAnalyzer
File c:\dev\repository\com\ibm\icu\icu4j\2.6.1\icu4j-2.6.1.jar
org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in
constan
done
On 25/09/2007, at 11:29 AM, Ralph Goers wrote:
I created an issue in Jira but it seems I can't assign it to
myself. Can someone with permission grant me rights to do that?
Thanks,
Ralph
-
To unsubscribe, e-mail: [EMAIL
I created an issue in Jira but it seems I can't assign it to myself. Can
someone with permission grant me rights to do that?
Thanks,
Ralph
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROT
+1
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Monday, September 24, 2007 4:55 PM
To: Maven Developers List
Subject: [VOTE] Release maven-gpg-plugin 1.0-alpha-4
All but one bug for GPG plugin is now fixed (and that bug is really a
bug
in the release plugin) so
On 25/09/2007, at 6:14 AM, Dennis Lundberg wrote:
It turned out I had some local changes that I had forgotten to
commit. After committing those Continuum seems happy. Can you try
again locally, just to make sure?
That did the trick - thanks!
- Brett
---
+1
On 24 Sep 07, at 1:55 PM 24 Sep 07, Daniel Kulp wrote:
All but one bug for GPG plugin is now fixed (and that bug is really
a bug
in the release plugin) so it's time to do a release. :-)
Staging area:
http://people.apache.org/~dkulp/stage_gpg/
Tag:
http://svn.apache.org/repos/asf/mave
All but one bug for GPG plugin is now fixed (and that bug is really a bug
in the release plugin) so it's time to do a release. :-)
Staging area:
http://people.apache.org/~dkulp/stage_gpg/
Tag:
http://svn.apache.org/repos/asf/maven/plugins/tags/maven-gpg-plugin-1.0-alpha-4/
Release Notes - M
It turned out I had some local changes that I had forgotten to commit.
After committing those Continuum seems happy. Can you try again locally,
just to make sure?
Brett Porter wrote:
I get this locally too - anyone else seen it?
- Brett
On 24/09/2007, at 11:55 PM, [EMAIL PROTECTED] wrote:
O
On 9/24/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
> For 1.0.3 doc, we'll let it as is but we must remove specific 1.1 doc in it.
How will this be handled? Do we need continuum/1.0.3 and
continuum/1.1 on the website?
--
Wendy
Agree on this comments.
User Guide could be the second entry.
The structure is fine. (now we have to populate this)
--
Olivier
2007/9/24, Joakim Erdfelt <[EMAIL PROTECTED]>:
>
> The order is a little odd.
> I would personally put the User's Guide as more important than the
> Developer's Guides.
OK. My mistake for not making it clear where I wanted to add this. I'll
try to revert this tonight (I'm in California). I'll look at the other
options you've presented for moving this forward.
I should make it clear that I'm not just doing this for my employer (if I
was I'd be doing the work on
The order is a little odd.
I would personally put the User's Guide as more important than the
Developer's Guides.
The FAQ should be higher in the list too.
- Joakim
Emmanuel Venisse wrote:
Hi,
Here is the structure of the documentation I'd like to have for
1.1-final.
Installation/Up
I'd like to drop (or move to the archiva-sandbox) the archiva-cli and
archiva-converter modules.
Does anyone see any reason to keep these two modules around anymore?
--
- Joakim Erdfelt
[EMAIL PROTECTED]
Open Source Software (OSS) Developer
On 24 Sep 07, at 11:21 AM 24 Sep 07, Ralph Goers wrote:
Jason van Zyl said:
On 24 Sep 07, at 9:23 AM 24 Sep 07, Mark Hobson wrote:
Okay, but I do think a feature branch is the best for prototyping
new
features - it stops blocking the developer and doesn't cause
unnecessary problems for ot
Jason van Zyl said:
>
> On 24 Sep 07, at 9:23 AM 24 Sep 07, Mark Hobson wrote:
>
>> Okay, but I do think a feature branch is the best for prototyping new
>> features - it stops blocking the developer and doesn't cause
>> unnecessary problems for others. Do we really need to merge it into
>> 2.0.x?
On 24 Sep 07, at 9:23 AM 24 Sep 07, Mark Hobson wrote:
On 24/09/2007, Jason van Zyl <[EMAIL PROTECTED]> wrote:
For the trunk I think trying it is fine. I agree that I don't think
it is the best way forward and we should look at how this would
actually be used and I believe it's going to be wit
On 24 Sep 07, at 9:23 AM 24 Sep 07, Mark Hobson wrote:
On 24/09/2007, Jason van Zyl <[EMAIL PROTECTED]> wrote:
For the trunk I think trying it is fine. I agree that I don't think
it is the best way forward and we should look at how this would
actually be used and I believe it's going to be wit
Stephane,
The file is too large for the list server and is being rejected. Can I post
some excerpts from it or can you give me an email address I can send it to?
Dave.
-Original Message-
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: September 21, 2007 09:43 PM
To: Maven Deve
On 24/09/2007, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> For the trunk I think trying it is fine. I agree that I don't think
> it is the best way forward and we should look at how this would
> actually be used and I believe it's going to be within an
> organization that this happens. But Ralph is
Hi,
Is SCM meant to support JDK 1.4? I notice the API is causing build
failures on maven.zones.apache.org.
Cheers,
Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
On 24 Sep 07, at 6:49 AM 24 Sep 07, Mark Hobson wrote:
On 24/09/2007, Ralph Goers <[EMAIL PROTECTED]> wrote:
Yes, you have to specify import for the import to
happen.
The type also has to be a pom. Ideally when doing this projects
would
create a bill of materials pom for others to use and
Well, you can soon just make your own. The only hold back with
releasing the tool we're making is an agreement with yWork to
obfuscate the JAR before distributing. So we should have the source
out shortly.
On 24 Sep 07, at 3:21 AM 24 Sep 07, Mark Hobson wrote:
Good work! Glad to see some
I get this locally too - anyone else seen it?
- Brett
On 24/09/2007, at 11:55 PM, [EMAIL PROTECTED] wrote:
Online report : http://maven.zones.apache.org/continuum/
buildResult.action?buildId=24366&projectId=32
Build statistics:
State: Failed
Previous State: Failed
Started at: Mon 24 Sep 2
Ah, ok. I get the same failures on my mac.
Basically, I don't export M2_HOME from the env (and I turned it off
in Continuum today to make the ITs happy). the shell script is able
to derive it from it's location rather than using the env. var.
I'll pass the property in explicitly so the invo
On 24/09/2007, Ralph Goers <[EMAIL PROTECTED]> wrote:
> Yes, you have to specify import for the import to happen.
> The type also has to be a pom. Ideally when doing this projects would
> create a bill of materials pom for others to use and then use the import
> only in poms that they use to build
I tried but the patch no longer applies to latest code in trunk
On 9/24/07, nicolas de loof <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Can I expect any progress on MECLIPSE-172 ? There is allready a patch
> available for 1 year, but I can rely on a SNAPSHOT plugin for my
> project.
>
> Was so sory to
Brett,
Can you take a look at this? This is the same problem that occurred
before where the failure only happens in continuum. I even tried
building it manually on maven.zones and it works fine there. Not sure
what to do about it but last time it mysteriously started working one
day.
--Brian
Jason van Zyl wrote:
On 23 Sep 07, at 12:20 AM 23 Sep 07, [EMAIL PROTECTED] wrote:
Author: rgoers
Date: Sun Sep 23 00:20:24 2007
New Revision: 578553
URL: http://svn.apache.org/viewvc?rev=578553&view=rev
Log:
Allow the managed dependencies of projects to be imported into the
managed dependen
On 24/09/2007, at 1:16 PM, Jason van Zyl wrote:
We've still had no luck getting Continuum to do this as far as I
know.
http://maven.zones.apache.org/continuum/buildResult.action?
buildId=24322&projectId=514
I had to work through a few issues where the ITs were highly
dependant on the st
Good work! Glad to see some progress being made in visualising and
debugging dependency problems - it certainly saps a lot of developer
time where I work.
Looking forward to more screenshots.
Cheers,
Mark
On 24/09/2007, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've been working with
Hi,
I've been working with Oleg Gusakov to make the necessary alterations
for graph-first based dependency resolution and here are some
pictures we've come up with so far.
This is of the completely unadulterated tree with no scope
transitioning, conflict resolution, or transformation:
h
Hello,
Can I expect any progress on MECLIPSE-172 ? There is allready a patch
available for 1 year, but I can rely on a SNAPSHOT plugin for my
project.
Was so sory to see this has not been included in recent 2.4 release of
the plugin...
Nico.
-
On 23 Sep 07, at 12:20 AM 23 Sep 07, [EMAIL PROTECTED] wrote:
Author: rgoers
Date: Sun Sep 23 00:20:24 2007
New Revision: 578553
URL: http://svn.apache.org/viewvc?rev=578553&view=rev
Log:
Allow the managed dependencies of projects to be imported into the
managed dependencies of other project
33 matches
Mail list logo
