>Do you want me to file a JIRA issue?
>
>
Yep, I'll take a look tomorrow. Sorry about that.
- Brett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Brett Porter wrote:
> Carsten Ziegeler wrote:
>
>
>>How do I specify this?
>>[1.3.02] creates a NPE.
>>
>>
>
> Another bug?!
It seems so :(
I get this stack trace:
java.lang.NullPointerException: version was null for xml-apis:xml-apis
at
org.apache.maven.artifact.DefaultArtifact.getBas
Brett Porter wrote:
> That's actually a bug we need to fix. While the resolution technique
> might be "latest" instead of "nearest", I think the version in the
> current POM should always win.
Yes :)
> You could actually do this by using
> [1.3.02] in the mean time,
How do I specify this?
[1.3.02
Carsten Ziegeler wrote:
>How do I specify this?
>[1.3.02] creates a NPE.
>
>
Another bug?!
Does [1.3.02,1.3.02] work?
>I was thinking about using a new name like xml-commons-apis as it is a
>sub project of the xml-commons project. This would solve the mess but
>introduce a new name.
>
>
Even
That's actually a bug we need to fix. While the resolution technique
might be "latest" instead of "nearest", I think the version in the
current POM should always win. You could actually do this by using
[1.3.02] in the mean time, or you can add exclusions for those
introducing the other xml-apis (t
(This time with log attached)
Carsten Ziegeler wrote:
> Brett Porter wrote:
>
>>This be related to the compiler changes that have been going on.
>>
>>Carsten - can you svn up with th elogging I just added and check the
>>library is passed in?
>>
>
> Sure, I can't at the moment, but I'll try toni
Carsten Ziegeler wrote:
> Brett Porter wrote:
>
>>This be related to the compiler changes that have been going on.
>>
>>Carsten - can you svn up with th elogging I just added and check the
>>library is passed in?
>>
>
> Sure, I can't at the moment, but I'll try tonight and report back tomorrow.
>
On Wed, Aug 24, 2005 at 12:03:55PM +0200, Carsten Ziegeler wrote:
> After updating from alpha-3 to the latest from SVN I can't compile
> Cocoon anymore. I think the problem is related to classloading or
> handling of classes.
> As one dependency we have the xml-apis-1.3.02 implementing DOM level 3
Brett Porter schrieb:
> This be related to the compiler changes that have been going on.
>
> Carsten - can you svn up with th elogging I just added and check the
> library is passed in?
>
Sure, I can't at the moment, but I'll try tonight and report back tomorrow.
Carsten
--
Carsten Ziegeler -
This be related to the compiler changes that have been going on.
Carsten - can you svn up with th elogging I just added and check the
library is passed in?
Thanks,
Brett
Carsten Ziegeler wrote:
>I think I picked up a wrong subject, of course I don't mean that I have
>problems compiling m2 itsel
I think I picked up a wrong subject, of course I don't mean that I have
problems compiling m2 itself. I have problems while using m2 to compile
my own project.
Carsten
Carsten Ziegeler wrote:
> After updating from alpha-3 to the latest from SVN I can't compile
> Cocoon anymore. I think the proble
After updating from alpha-3 to the latest from SVN I can't compile
Cocoon anymore. I think the problem is related to classloading or
handling of classes.
As one dependency we have the xml-apis-1.3.02 implementing DOM level 3
interfaces. Although we have declared this dependency in the POM and the
j
12 matches
Mail list logo
