maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (MPJBUILDER-8) generate-project goal does not generate relative paths
Date Thu, 18 Dec 2003 08:45:54 GMT
The following comment has been added to this issue:

     Author: Emmanuel Venisse
    Created: Thu, 18 Dec 2003 2:44 AM
My personal opinion is that ide project files are personal and they never add to a scm repository
because each developer can work with his preferred ide.
But if you have a correct patch that satisfy everyone, I can apply it.
View the issue:

Here is an overview of the issue:
        Key: MPJBUILDER-8
    Summary: generate-project goal does not generate relative paths
       Type: Bug

     Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-jbuilder-plugin

   Assignee: Emmanuel Venisse
   Reporter: Charles Overbeck

    Created: Wed, 17 Dec 2003 6:49 PM
    Updated: Thu, 18 Dec 2003 2:44 AM
Environment: All platforms

A JBuilder project file created by JBuilder stores paths relative to the project file's directory,
unless the path is on a different root. The jbuilder-maven plugin always stores absolute paths.
Relative paths are stored so that if the whole project, JPX and source, is checked in to a
Version Control System and another user pulls the project to another machine, the path references
will continue to work.

For example, I pulled Jelly into c:\Documents and Settings\coverbeck\jbproject\jelly, and
ran maven jbuilder:generate-project. For the outpath, the generated JPX file had:

<property name="OutPath" category="sys" value="C:\Documents and Settings\coverbeck\jbproject\jelly/target/classes">

If I manually create the same setting with the JBuilder GUI when the JPX is located in C:\Documents
and Settings\coverbeck\jbproject\jelly, the resulting JPX will have:

<property name="OutPath" category="sys" value="target/classes">

DefaultPath, DocPath, SourcePath, and TestPath all have the same issue.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message