multi-module build dependency not found - linux only
----------------------------------------------------

                 Key: MASPECTJ-89
                 URL: http://jira.codehaus.org/browse/MASPECTJ-89
             Project: Mojo AspectJ Plugin
          Issue Type: Bug
         Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_12
Java home: /usr/lib/jvm/jdk1.6.0_12/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.35-22-generic" arch: "amd64" Family: "unix"
Aspectj plugin 1.6.4
            Reporter: Matthew Sandoz


linux env:
Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_12
Java home: /usr/lib/jvm/jdk1.6.0_12/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.35-22-generic" arch: "amd64" Family: "unix"
Aspectj plugin 1.6.4

windows env:
Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_12
Java home: c:\Program Files\Java\jdk1.6.0_12\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
Aspectj plugin 1.6.4

I included environmental information for both windows and linux to show the 
similarities and differences between systems.

When building my multi-module project in windows, everything works fine. when I 
build under Linux, the aspectJ mojo doesn't seem to be able to find one of the  
project dependencies. The project is dependent upon another module in the 
multimodule build. the build goes through the data model module and then errors 
out on the DAO module saying it can't find the classes that were just built in 
the data module.

Two more interesting facts. First,  I get this error message:
[INFO] [aspectj:compile {execution: c}]
[ERROR] The import com.ihg.crm.fmds cannot be resolved

but my imports are for com.ihg.crm.fmds.model.*, not com.ihg.crm.fmds.

Second, if i build the dao on its own (not from the parent module) then I don't 
have the same problem. 

In summary, this only seems to happen on linux with a multi-module build where 
there is a dependency upon a previously built sibling module.


-- 
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

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to