Benjamin Bentmann wrote:
> Dennis Lundberg wrote:
>
>> -1
>>
>> I tried these POMs with Java 1.4. Unfortunately the changes made in
>> r830510 by Vincent has created a Java 1.5 dependency on Maven Parent.
>>
>> That's because Cobertura Maven Plugin 2.3 (specified in reporting
>> section of Maven P
Lukas Theussl wrote:
>
> Thanks Dennis for the initiative. Unfortunately it comes at a bad time
> for me, I'm afraid I won't be able to help much in the next weeks (new
> job, new country, new home...) but I fully endorse your plan of action.
> See my comments below.
No problem, we'll try to mana
Dennis Lundberg wrote:
-1
I tried these POMs with Java 1.4. Unfortunately the changes made in
r830510 by Vincent has created a Java 1.5 dependency on Maven Parent.
That's because Cobertura Maven Plugin 2.3 (specified in reporting
section of Maven Parent)
Is something preventing us from build
-1
I tried these POMs with Java 1.4. Unfortunately the changes made in
r830510 by Vincent has created a Java 1.5 dependency on Maven Parent.
That's because Cobertura Maven Plugin 2.3 (specified in reporting
section of Maven Parent) depends upon Cobertura 1.9.2 which was compiled
with Java 1.5 cla
+1
--
Olivier
2009/10/29 Stephen Connolly :
> Hi,
>
> This is the first official release.
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=12063&resolution=-1&sorter/field=updated&sorter/order=DESC
>
> Staging repo:
Stephen Connolly wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-004
Staging site:
http://maven.apache.org/plugins/maven-toolchains-plugin-1.0
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubsc
On 2009-10-31, at 12:10 AM, Mark Struberg wrote:
1) Pretty simple, and works with repository managers.
Not sure about that. I'm not into RepoManagers that deep, but don't
they have the exact same problem?
Right now yes. But the difference the person doing it the first time
finds the re
> 1) Pretty simple, and works with repository managers.
Not sure about that. I'm not into RepoManagers that deep, but don't they have
the exact same problem?
Means the RepoManager only sees this if the repo got added manually to the
manager, or if a project with that missing repo
got picked up
