[jira] Closed: (MAVEN-1275) ant properties are not created correctly with the current 1.0-HEAD (breaks torque plugin)

[ji...@codehaus.org]

Message:

   The following issue has been closed.

   Resolver: Brett Porter
       Date: Tue, 11 May 2004 5:37 AM

applied with modifications.
---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1275

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1275
    Summary: ant properties are not created correctly with the current 1.0-HEAD (breaks torque plugin)
       Type: Bug

     Status: Closed
   Priority: Blocker
 Resolution: FIXED

 Original Estimate: 30 minutes
 Time Spent: Unknown
  Remaining: 30 minutes

    Project: maven
 Components: 
             core
   Fix Fors:
             1.0-rc3
   Versions:
             1.0-rc3

   Assignee: Brett Porter
   Reporter: Henning Schmiedehausen

    Created: Sun, 9 May 2004 6:14 PM
    Updated: Tue, 11 May 2004 5:37 AM
Environment: Fedora Core 1 Linux
Sun java version "1.4.2_04"
maven 1.0-rc3-dev (HEAD as of 2004-05-09)

Description:
[I assigned this "blocker" priority because the current HEAD can't build projects that need the torque plugin like the Turbine 2.3 code base. So using this maven stops work on these projects ]

Due to some change in jelly, maven or somewhere else between the
1.0-rc2 and the current 1.0 HEAD version (which identifies itself as
1.0-rc3-dev), the Torque Plugin, which relies on using the Ant Task
interface no longer works.

The reason for this is in the JellyPropsHandler class which interfaces
the JellyContext onto ant Properties. For this, it calls toString() on
values in the JellyContext. 

Up to some points, expression elements in this context returned its
evaluated value. At some point this seem to have changed and the
elements now return

classname@location[value=myvalue]

so code that uses these elements starts to use really scary stuff. 

I wasn't able to pinpoint the exact location where the problem crept
in, because I simply didn't want to try to understand the "inner
workings" of the maven code. It might have to do with the changes in
the MavenExpressionFactory; it could simply be because a newer
jelly version is used.


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