Can we bind it to multiple phases?
I'm not sure if binding to just the package phase is a good solution because that could cause issues if the build stops before it makes it to the package phase, and if clean stops working it wouldn't be obvious to the user they need to manually cleanup.
Thanh
On 14/02/2013 2:15 PM, Dave Hughes wrote:
 
The maven-clean-plugin’s execution can be bound to a different phase:
       <plugin>
        <artifactId>maven-clean-plugin</artifactId>
        <version>2.5</version>
       
<phase>package</phase>
        <configuration>
          […]
        </configuration>
      </plugin>
 
This is odd though, as you should really only be cleaning when the
clean lifecycle is active.  It would also mean that “mvn clean” wouldn’t actually clean up the specified files.
 
 
Dave
 
 
Elastic Path Software, Inc.
Web elasticpath.com
| Blog
getelastic.com
| Twitter
twitter.com/elasticpath
Careers 
elasticpath.com/jobs | Community
grep.elasticpath.com
Confidentiality Notice: This message is intended only for the use of the designated addressee(s), and may contain information that is privileged, confidential and exempt from disclosure.
 Any unauthorized viewing, disclosure, copying, distribution or use of information contained in this e-mail is prohibited and may be unlawful. If you received this e-mail in error, please reply to the sender immediately to inform us you are not the intended
 recipient and delete the email from your computer system. 
 
Hi Lars,
This is the error you ran into in discussion [1] we resolved it with Bug 400007 [1]. However the resolution used the maven clean plugin to clean this up. So if you don't pass the clean option cleanup won't happen here causing the issue to come back.
If anyone knows of another way we can get this cleanup to work such that we don't need to pass the "clean" option please let me know and I'd be happy to submit a patch.
Thanh
[1] http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg00946.html
[2] http://bugs.eclipse.org/400007
On 14/02/13 01:55 PM, Lars Vogel wrote:
 
I can run several times a "mvn clean install" build without issues but
without clean the build fails with the following error message:
 
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.7:run (normal) on
project org.eclipse.swt.gtk.linux.x86: An Ant BuildException has
occured: /home/vogella/eclipse.platform.releng.aggregator/eclipse.platform.swt.binaries/bundles/org.eclipse.swt.gtk.linux.x86/temp.folder/@dot.src/org
does not exist.
[ERROR] around Ant part ...<copy toDir="src/org/">... @ 11:26 in
/home/vogella/eclipse.platform.releng.aggregator/eclipse.platform.swt.binaries/bundles/org.eclipse.swt.gtk.linux.x86/target/antrun/build-main.xml
 
Here is my full clean install command
 
mvn -o clean install  -Pno-bree-libs -Dmaven.test.skip=true
 
Here is my install without clean
 
mvn -o install  -Pno-bree-libs -Dmaven.test.skip=true
 
For building the Eclipse IDE with  contributed patches it would be
nice to have the option to do delta builds with CBI.
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev
 
 
 
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev