Hi, Following the switch to Java 7+, many users have problem with the Maven-style jobs: they are forbidden to execute them with a version of Java inferior to 7. See for example https://issues.jenkins-ci.org/browse/JENKINS-28294.
The common solution proposed by people is to switch to Freestyle project: there is more configuration to do, but the behaviour of the build will be more deterministic (see http://javaadventure.blogspot.de/2013/11/jenkins-maven-job-type-considered-evil.html for example for more explanation of why anyway maven-style jobs apparently sucks). So, my question now is: how do I properly switch to a freestyle project? In particular, my main concern is with dependencies and build triggering: - I want to be able to see the tree of builds like this: http://jenkins.petalslink.com/job/Petals%20Components%20-%20BC%20SOAP/265/ - I want to see upstream and downstream projects like this: http://jenkins.petalslink.com/job/Petals%20Components%20-%20BC%20SOAP/ - I want my jobs to be triggered when one of its dependencies was built (and not by checking every hours if a dependency has changed as one of the jenkins plugins do). Anybody has good suggestion to either do that, or to convince me I don't need it? Thank you :) Victor -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/28ee3f3b-4dec-4a7c-aac0-f352fbf9a349%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
