If it's th exact same version of the plugin (I believe there is only one), I'd say it's a maven 3 regression and might need to be fixed there (and not in the plugin). Creating a ticket for both projects and linking them together would probably be a good idea.
/Anders On Thu, Aug 19, 2010 at 19:49, Jesse Farinacci <[email protected]> wrote: > Hi, > > On Thu, Aug 19, 2010 at 1:41 PM, EJ Ciramella <[email protected]> > wrote: > > What's really weird is with maven 2.2.1, this rule is just fine. > > I literally just setup m3 just to see what would break, this is the first > thing that jumps out. > > The java version is reported like this: > > > > That is weird. Perhaps you should open a JIRA with the enforcer > plugin[1]? To get past this issue for the time being, you should > create m2 vs m3 profiles with different executions of the m-enforcer-p > which use the _ vs - formats for JDK normalization. > > [1] http://jira.codehaus.org/browse/MENFORCER > > -Jesse > > -- > There are 10 types of people in this world, those > that can read binary and those that can not. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
