RE: [jdt-apt-dev] path bug?

["Jess Garms" <jgarms@xxxxxxx>]

Ah yes, now I understand. We (BEA) ran into the same problem with the
Filer API: no way to perform a final, project-wide build step. For our
particular case, we ended up having a separate, non-apt based eclipse
extension that performs the final packaging step. It's triggered by a
deployment from WTP (another eclipse project), but isn't part of the APT
plugin at all.

Because the Filer interface is defined by Sun, we can't change it
directly. JSR 269 (http://www.jcp.org/en/jsr/detail?id=269) is deciding
on new public APIs to replace the ones in com.sun.mirror. Hopefully it
can provide a reasonable solution.

On a different note, I just checked in a fix for the issue you were
seeing: we now provide absolute paths for all the file-based options
that the environment provides.

Thanks,
Jess

-----Original Message-----
From: jdt-apt-dev-bounces@xxxxxxxxxxx
[mailto:jdt-apt-dev-bounces@xxxxxxxxxxx] On Behalf Of Juraj Burian
Sent: Monday, August 29, 2005 3:12 AM
To: Eclipse JDT Apt developers list.
Subject: Re: [jdt-apt-dev] path bug?

Thank  you Jess,

I can help fix this problem if you are interested ....

About my p.s. : Filler api has methods oriented only on the process of 
creation of the files,
but we need to merge files and so on ..., so we can't  do everything 
what we need to.
Typical use case is generation of the (ejb) deployment descriptors,
because apt works with "compilation increments"  => that we must merge 
generated files,
especially  if one generated file is a result of parsing of the many 
source files ...

Best regards,
J.B.

p.s. sorry for my ugly English ...

Jess Garms wrote:

>Yes, that definitely sounds like a bug in our implementation. I've
filed
>the following bug in bugzilla to track it:
>
>https://bugs.eclipse.org/bugs/show_bug.cgi?id=108137
>
>WRT your post-script, I've afraid I don't understand the issue. You
>said, "We can't handle all of the existing states with a Filler API". 
>
>Thanks,
>Jess
>
>-----Original Message-----
>From: jdt-apt-dev-bounces@xxxxxxxxxxx
>[mailto:jdt-apt-dev-bounces@xxxxxxxxxxx] On Behalf Of Juraj Burian
>Sent: Friday, August 26, 2005 7:02 AM
>To: jdt-apt-dev@xxxxxxxxxxx
>Subject: [jdt-apt-dev] path bug?
>
>Hello ladies and gentlemen,
>thanks for great job.
>
>I have one little problem:
>only a project relative part of the path is returned by -s option.
>The original implementation gives a full path.
>Is there a possibility to fix this "bug" ?
>I think that it is a bug, because there doesn't exist the  possibility 
>to retrieve the missing part of the path.
>
>Please let me know your opinion.
>
>best regards
>J.Burian
>
>p.s. we can't handle all of the existing states with a Filler API.
>_______________________________________________
>jdt-apt-dev mailing list
>jdt-apt-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/jdt-apt-dev
>
>
>_______________________________________________
>jdt-apt-dev mailing list
>jdt-apt-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/jdt-apt-dev
>
>
>  
>

_______________________________________________
jdt-apt-dev mailing list
jdt-apt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-apt-dev