How to influence the build cycle so that generate-sources recognises changing files?

[Leonardo Freitas <le...@gmail.com>]

Hello,

I have a parser project for multiple languages. A file Parser.xml is used to
generate a series
of Parser.cup files through the generate-sources phase. This generation
actually cuts the
right bits from the .xml into a .cup file.

Next, the .cup file is processed-sources with the maven cup plugin to
generate a Parser.java
file. Next, something ismilar happens for the jflex (lexer) files. Finally,
this java files are compiled accordingly.

The problem is that when I change the xml file, maven does not know
something has changed
and that the cup file needs to be regenerated. It simply ignores the build
saying that "Parser.cup is upto date",
when in fact it should be because the .xml file has changed.

Any suggestions on how to ammend this, please? In fact, could any one point
out a clear
place that explains how to influence/interact with the various lifecycle
phases?

Best
Leo

Re: How to influence the build cycle so that generate-sources recognises changing files?

[franz see <fr...@gmail.com>]

Good day to, Leonardo,

I don't have experience in what you are doing but I think the root of the
problem is that the maven plugin you are using to generate the cup files
given the xml files are not regenerating the cup files. 

You may want to check that  plugin documentation and see whether it has
something to say about that.

Cheers,
Franz


Leonardo Freitas wrote:
> 
> Hello,
> 
> I have a parser project for multiple languages. A file Parser.xml is used
> to
> generate a series
> of Parser.cup files through the generate-sources phase. This generation
> actually cuts the
> right bits from the .xml into a .cup file.
> 
> Next, the .cup file is processed-sources with the maven cup plugin to
> generate a Parser.java
> file. Next, something ismilar happens for the jflex (lexer) files.
> Finally,
> this java files are compiled accordingly.
> 
> The problem is that when I change the xml file, maven does not know
> something has changed
> and that the cup file needs to be regenerated. It simply ignores the build
> saying that "Parser.cup is upto date",
> when in fact it should be because the .xml file has changed.
> 
> Any suggestions on how to ammend this, please? In fact, could any one
> point
> out a clear
> place that explains how to influence/interact with the various lifecycle
> phases?
> 
> Best
> Leo
> 
> 

-- 
View this message in context: http://www.nabble.com/How-to-influence-the-build-cycle-so-that-generate-sources-recognises-changing-files--tf3175590s177.html#a8819842
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org