Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://jira.codehaus.org/browse/MAVEN-1296 Here is an overview of the issue: --------------------------------------------------------------------- Key: MAVEN-1296 Summary: Multiproject property inheritance Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Versions: 1.0-rc3 Assignee: Reporter: Winston Rast Created: Thu, 27 May 2004 11:10 AM Updated: Thu, 27 May 2004 11:10 AM Description: I'm trying to generate "1.4 friendly" compiled classes. I'm getting failures on the assert keyword. Here's a rundown of my multiproject structure: root/ project.xml (extends root/service/project.xml) project.ent common/ maven/ project.properties project.xml (Parent) entities/ versions.ent dependencies.ent developers.ent service/ maven.xml project.properties project.xml (extends root/common/maven/project.xml) ejb/ project.ent project.properties project.xml (extends root/project.xml) I have the maven.compile.source and maven.compile.target properties set in root/service/project.properties. Yet when I run "maven multiproject:install" from my root directory I get a warning and error regarding the assert keyword. If I put these properties in a root/project.properties file it works fine. Can anyone tell me if this is a bug or if I'm doing something wrong? ---------------------------------- Just to follow up with some more info that I discovered... I created a root/maven.xml to echo the maven.compile.* properties during the build. Somewhere along the way my property values are being lost: build: [echo] maven.compile.source=1.4 [echo] maven.compile.target=1.4 multiproject:install: multiproject:projects-init: [echo] Gathering project list Starting the reactor... <snip> xdoclet:ejbdoclet: java:prepare-filesystem: java:compile: [echo] maven.compile.source=1.3 [echo] maven.compile.target=1.1 So is the problem in the property inheritance, the java plugin, or the multiproject plugin? Your help is greatly appreciated. ----------------------------------- I've been doing a lot of trial and error with this problem and I've narrowed it down to what I think is a problem in multiproject environments with inherited properties. It is *not* an issue strictly with the maven.compile.* properties as I've previously mentioned. I'm attaching a jar file of my stripped down example to demonstrate. In my example, I'm demonstrating the problem with the maven.repo.remote property. To replicate the problem, do the following: * Edit project.properties under test/ and change maven.repo.remote to something other than ibiblio. * Edit test/service/myservice/ejb/project.xml with a dependency (something NOT on ibiblio, but on the remote repo specified previously) * Remove this dependent jar from your local repository so it's forced to download it again * From test/service/myservice, execute a maven goal (I generally do clean) This should fail to download. Strangely, if I run the same maven goal from test/service/myservice/ejb, it DOES download! Anyone have a clue what's happening here? --------------------------------------------------------------------- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
