Hi Jason,
did you had a chance to take a second look, following my instructions in my
first reply?
Thanks,
Jörg
Jason van Zyl wrote:
> I unpacked your example and ran your preparation script and it fails in
> 2.2.1 as well:
>
> https://gist.github.com/jvanzyl/5824206
>
> What's the overall u
Hello,
I did the tests wrongly for extra-enforcer-rules, the new version of
enforcer is backwards incompatible:
org.apache.maven.plugins.enforcer.AbstractStandardEnforcerRule had a
public message field in 1.2, this is now (1.3) private and uses
getMessage and setMessage methods.
This would mean a
Yes, just pointing out the current sisu/aether issues. All to be expected given
the significant movement of projects to different organizations and the
commensurate package changes. In Aether's case, significant API changes as well.
jvz
On 2013-06-23, at 11:38 AM, Stuart McCulloch wrote:
> Ac
Actually the error in JENKINS-15935 is because MavenLoggerManager was removed
in:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=a23f7cfd10c04da702c7efb299cce6b3499c18ab
and the Jenkins maven-plugin depends on that class, hence the NCDFE.
Regarding event spy compatibili
The Jenkins and Hudson integration require changes with anything related to
event spies that use Sisu or Aether specific classes. Existing versions of
Hudson don't work either because of the event spy implementation requiring bits
of Sisu in the sonatype space.
This is expected. It's a major A
Hi Jason
I've installed 3.1.0-alpha-1 into my local Jenkins 1.512 instance running
on Windows. After that I tried a simple build and ran into an exception
that others apparently had also seen:
https://issues.jenkins-ci.org/browse/JENKINS-15935
Is that a problem in the Maven Integration plugin fo
I'm just going to cut the 3.1.0. Almost zero people have given feedback and I
don't think anyone is going to look at this until it's released and then I
think all sort of issues are going to surface and I will prepare to fix those.
I believe there will be many issues but this process isn't going
Hi,
No problem, I'll see how I can fix that.
FWIW, I've just run the ITs of mojo's extra-enforcer-rules project with
m-enforcer-p:1.3.
This gives:
[ERROR] The following builds failed:
[ERROR] * enforce-bytecode-version-jdkVersionOption\pom.xml
[ERROR] * enforce-bytecode-version-with-banned-deps
Hi Baptiste,
you're hitting the result of the changes due to MENFORCER-42[1]
Up until 1.2 the dependencies were resolved instead of calculated.
So if you run 'mvn validate' you can't use the results of the reactor,
since those files aren't available yet. So the build will fail or it will
use
-0.9 (non binding).
I just tested on a local project, codehaus mojo EnforceBytecodeVersion
fails with an NPE with m-enforcer-p 1.3 but correctly thows an
EnforcerRuleException with 1.2.
That is, as I am the one who wrote that rule, that's perfectly possible I'm
doing something stooopid in the code
10 matches
Mail list logo
