[jira] Updated: (MAVEN-1017) prereq for java:compile throws off line numbers.

[ji...@codehaus.org]

The following issue has been updated:

    Updater: dion gillard (mailto:dion@apache.org)
       Date: Mon, 10 Nov 2003 10:12 AM
    Changes:
             Fix Version changed to 1.1
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1017&page=history

---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1017


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1017
    Summary: prereq for java:compile throws off line numbers.
       Type: Bug

     Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
 Components: 
             plugin-jalopy
   Fix Fors:
             1.1
   Versions:
             1.0-rc1

   Assignee: 
   Reporter: Joakim Erdfelt

    Created: Mon, 10 Nov 2003 7:56 AM
    Updated: Mon, 10 Nov 2003 10:12 AM
Environment: solaris 2.8 / j2sdk 1.4.2_01 / maven 1.0rc1

Description:
Why is there a preReq for the maven-jalopy-plugin to perform a 'java:compile' before running jalopy on the source files?

I find this annoying when attempting to debug stuff.  As the line numbers are all off in this situation.

The project I'm working on has many generated source files.  

The process (in straight ant) that works for us is ...

1) get latest xml definition of old legacy socket protocol.
2) perform xslt transform against legacy.xml to generate optimum java source to read/write against protocol.
3) perform xslt transform against legacy.xml to generate some integration tests for the protocol to ensure that the spec and reality mesh.
3) jalopy the source to make source readable.
4) compile sources.
5) test.

Now, if we use the maven with the maven-jalopy-plugin step #4 moves up to between #1 and #2.

If we have to debug the code, then the line numbers in the compiled classes do not match the line numbers in the source files. 

Which is annoying to say the least.

Can we either make the java:compile prereq optional or remove it entirely?



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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