[jira] Commented: (MCOMPILER-21) compiler smarts

2011-09-23 Thread Narendra (JIRA)

[ 
https://jira.codehaus.org/browse/MCOMPILER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=279787#comment-279787
 ] 

Narendra commented on MCOMPILER-21:
---

I have following directory for java source code 
--lion
 --com
  test1 -- contains pom.xml and java source code with package com.test1
  test2 - contains pom.cml and java source code with pakage com.test2
when compiler plugin compiles it does directory scanning and compiles only java 
code that are modified from previous build. But In above directory structure 
case it recompiles the all source code in subsequent builds. How to overcome 
this ? I found that it is because of basedirectory do not follow maven standard 
direcotry layout. Please advise.


 compiler smarts
 ---

 Key: MCOMPILER-21
 URL: https://jira.codehaus.org/browse/MCOMPILER-21
 Project: Maven 2.x Compiler Plugin
  Issue Type: Bug
Reporter: Brett Porter
Priority: Minor
 Fix For: 2.4


 there are probably other ways we can make the compiler stale check smarter. 
 List them out here if you think of them.
 1) if a snapshot was resolved to a newer version, rebuild everything.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MCOMPILER-21) compiler smarts

2010-02-05 Thread Andreas Christoforides (JIRA)

[ 
http://jira.codehaus.org/browse/MCOMPILER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=209321#action_209321
 ] 

Andreas Christoforides commented on MCOMPILER-21:
-

I think the priority of this issue should be higher. 

In the case of a file deletion the file is not removed and still packaged. In 
the case of a rename, both file versions are packaged. In my experience when 
developers see these problems they start doing clean builds every time making 
the build time several times slower. Imagine making a single file change and 
rebuilding everything from scratch. It is issues like this that makes users get 
the perception that Maven is slow.

These is not a problem only with the Maven compiler plugin because I believe it 
also happens with the resources plugin.

 compiler smarts
 ---

 Key: MCOMPILER-21
 URL: http://jira.codehaus.org/browse/MCOMPILER-21
 Project: Maven 2.x Compiler Plugin
  Issue Type: Bug
Reporter: Brett Porter
Priority: Minor
 Fix For: 2.3


 there are probably other ways we can make the compiler stale check smarter. 
 List them out here if you think of them.
 1) if a snapshot was resolved to a newer version, rebuild everything.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MCOMPILER-21) compiler smarts

2007-03-29 Thread Michael Tamm (JIRA)

[ 
http://jira.codehaus.org/browse/MCOMPILER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91542
 ] 

Michael Tamm commented on MCOMPILER-21:
---

(Re-)Use the depend task from Ant

 compiler smarts
 ---

 Key: MCOMPILER-21
 URL: http://jira.codehaus.org/browse/MCOMPILER-21
 Project: Maven 2.x Compiler Plugin
  Issue Type: Bug
Reporter: Brett Porter
Priority: Minor
 Fix For: 2.1


 there are probably other ways we can make the compiler stale check smarter. 
 List them out here if you think of them.
 1) if a snapshot was resolved to a newer version, rebuild everything.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MCOMPILER-21) compiler smarts

2007-01-09 Thread Christian Goetze (JIRA)
[ http://jira.codehaus.org/browse/MCOMPILER-21?page=comments#action_84589 ] 

Christian Goetze commented on MCOMPILER-21:
---

3) Track inventory. If files are removed, remove associated class files and 
force jar repacking/

4) Track timestamps. If file timestamp changes (e.g. to an -older- version), 
rebuild.

5) Track hash signatures for source files. Recompute signature if file 
timestamp changes, rebuild only if signature changes.

6) Track hash signatures for class files. Repack jars only if hash signatures 
change.

 compiler smarts
 ---

 Key: MCOMPILER-21
 URL: http://jira.codehaus.org/browse/MCOMPILER-21
 Project: Maven 2.x Compiler Plugin
  Issue Type: Bug
Reporter: Brett Porter
Priority: Minor
 Fix For: 2.1


 there are probably other ways we can make the compiler stale check smarter. 
 List them out here if you think of them.
 1) if a snapshot was resolved to a newer version, rebuild everything.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira