DO NOT REPLY [Bug 29683] Jar task with zipgroupfileset always builds the jar file

2009-01-29 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=29683


Stefan Bodewig bode...@apache.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE




--- Comment #6 from Stefan Bodewig bode...@apache.org  2009-01-29 07:03:22 
PST ---
I known bug 45902 is way newer, but that one is currently actively tracked
while this one has long been forgotten.

*** This bug has been marked as a duplicate of bug 45902 ***


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.


DO NOT REPLY [Bug 29683] Jar task with zipgroupfileset always builds the jar file

2008-09-23 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=29683


Emmanuel Bourg [EMAIL PROTECTED] changed:

   What|Removed |Added

Version|1.6.1   |1.7.1




--- Comment #4 from Emmanuel Bourg [EMAIL PROTECTED]  2008-09-23 03:45:37 PST 
---
Here is the trace when Ant is run with the -v option:

[jar] foo omitted as C:\anttest\foo.jar:foo/ is up to date.
[jar] foo\Bar.java omitted as C:\anttest\foo.jar:foo/Bar.java is up to date.
[jar] foo added as foo/ is outdated.
[jar] foo\BarTest.java omitted as C:\anttest\foo.jar:foo/BarTest.java is up to
date.
[jar] Building jar: C:\anttest\foo.jar
[jar] adding directory META-INF/
[jar] adding entry META-INF/MANIFEST.MF
[jar] adding directory foo/
[jar] adding entry foo/Bar.java
[jar] adding entry foo/BarTest.java
[jar] No Implementation-Title set.No Implementation-Version set.No
Implementation-Vendor set.
[jar] Location: C:\anttest\build.xml:6:


The foo directory in src/test is more recent than foo in src/main, that may
explain why the task thinks it has been updated and rebuilds the jar. If the
two fileset are inverted the jar is no longer rebuild.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.


DO NOT REPLY [Bug 29683] Jar task with zipgroupfileset always builds the jar file

2008-09-23 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=29683


Emmanuel Bourg [EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]




--- Comment #3 from Emmanuel Bourg [EMAIL PROTECTED]  2008-09-23 03:35:17 PST 
---
This is not specific to zipfileset, it also happens with filesets having
similar directory structures.

For example, considering this simple project layout:

/src/main/foo/Bar.java
/src/test/foo/BarTest.java

The following build file will always build the jar file:

?xml version=1.0 encoding=iso-8859-1?
project name=Bug 29683 testcase default=jar basedir=.
  target name=jar
jar jarfile=foo.jar
  fileset dir=src/main/
  fileset dir=src/test/
/jar
  /target
/project

This was verified on Windows XP with Ant 1.7.1 and Java 5


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.


DO NOT REPLY [Bug 29683] Jar task with zipgroupfileset always builds the jar file

2008-09-23 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=29683





--- Comment #5 from Emmanuel Bourg [EMAIL PROTECTED]  2008-09-23 04:23:23 PST 
---
Another workaround is to set the filesonly attribute to 'true' on the jar task:

jar jarfile=foo.jar filesonly=true
  fileset dir=src/main/
  fileset dir=src/test/
/jar


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.


DO NOT REPLY [Bug 29683] Jar task with zipgroupfileset always builds the jar file

2008-04-30 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=29683


Ivan Todoroski [EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]




--- Comment #2 from Ivan Todoroski [EMAIL PROTECTED]  2008-04-30 02:41:55 PST 
---
Just a gentle reminder, this almost 4-year old bug is still present in 1.7.0,
and it's really annoying to have to create workarounds with uptodate each
time you need to use zipgroupfileset. Are there any plans to fix it?

I tried to fix it myself, thinking that the timestamp check was simply missing
for zipgroupfilesets, but unfortunately it looks like it's a bit more subtle
than that and I quickly got lost in the code.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.