maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Closed: (MNG-4441) Profile Activation Regression in Maven3
Date Sat, 02 Jan 2010 15:45:55 GMT


Benjamin Bentmann closed MNG-4441.

    Resolution: Cannot Reproduce
      Assignee: Benjamin Bentmann

Please re-open with a reproducible test case if the issue persists.

> Profile Activation Regression in Maven3
> ---------------------------------------
>                 Key: MNG-4441
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Profiles
>    Affects Versions: 3.0-alpha-3
>            Reporter: Markus Heberling
>            Assignee: Benjamin Bentmann
>         Attachments: pom.xml
> As written here
I have a problem with profile activation in Maven3.
> I have a profile that activates if target/generated-sources/castor is missing and includes
castor in the build process that will create that directory and generate the sources into
> If the directory exists and I do mvn clean install, the build fails with maven 3. Maven
does not activate the profile since the directory exists at the beginning. But the clean step
will delete it of course and so the sources are missing and the build fails. With maven 2
this works.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message