myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Kind (JIRA)" <...@myfaces.apache.org>
Subject [jira] Created: (TRINIDAD-871) Without this new project.xml, the maven-jdev-plugin requires project migration on each usage.
Date Mon, 17 Dec 2007 17:38:43 GMT
Without this new project.xml, the maven-jdev-plugin requires project migration on each usage.
---------------------------------------------------------------------------------------------

                 Key: TRINIDAD-871
                 URL: https://issues.apache.org/jira/browse/TRINIDAD-871
             Project: MyFaces Trinidad
          Issue Type: Improvement
    Affects Versions: 1.2.5-plugins
            Reporter: Gary Kind
         Attachments: jdev-plugin.patch

JDev had a bug where 2 of  the installed components version breadcrumbs changed on each new
build of JDev.  This made it impossible for the maven-jdev-plugin's project.xml file, used
to create a .jpr (jdev project) file, to be used in JDev without migration to the "present"
version.  In a large workspace with multiple projects, this is very time-consuming.  The major
goal of the maven-jdev-plugin is to avoid this time-consuming migration.  JDev has now fixed
this problem and the attached patch file corrects the maven-jdev-plugin's project.xml file
so that the migration does not occur.  This patch is really a MUST in the next version of
the maven-jdev-plugin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message