The following issue has been updated:
Updater: David Zeleznik (mailto:[EMAIL PROTECTED])
Date: Tue, 24 Jun 2003 1:48 PM
Comment:
- Added support for JBuilder 9
- Added maven.jbuilder.verbose property
- Library files that are automatically generated from versioned (not snapshot)
artifact dependencies are now versioned themselves. This is also true for snapshot
dependencies where an unversioned library file has not been created yet from the
corresponding artifact. As before, if an unversioned library file has already been
created for a snapshot dependency, the unversioned library will be referenced.
Changes:
Attachment changed from to plugin.properties
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-461&page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-461
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-461
Summary: Patches for JBuilder plugin
Type: Improvement
Status: Unassigned
Priority: Major
Time Spent: Unknown
Estimate: 1 day
Project: maven
Components:
plugin-other
Versions:
1.0-beta-9
Assignee:
Reporter: David Zeleznik
Created: Tue, 3 Jun 2003 5:08 PM
Updated: Tue, 24 Jun 2003 1:48 PM
Description:
- The plugin attempts to find JBuilder's "HOME" directory where it will read
the user's default project properties file.
- The JBuilder "HOME" directory is also where library files are generated.
This is a major rewrite of the JBuilder plugin that keeps backwards compatibility,
while adding much more complete generation of project and library files. Some of the
ideas have been borrowed from the latest versions of the IDEA and Eclipse plugins.
Here is a short summary that covers some of the highlights:
- The plugin attempts to find JBuilder's "HOME" directory where it will read the
user's default project properties file. The JBuilder "HOME" directory is also where
library files are generated.
- When you generate a JBuilder project file, the plugin iterates through its
dependencies. For each dependency, a library definition file is generated for the
dependency jar in the local repo. This dependent library file is generated if, and
only if, the library file does not already exist or the library file was previously
generated the same way (as a dependency on a jar in the local repo).
- The previous point means that when you generate a jbuilder library
definition file directly from a Maven project (using the jbuilder:generate-library
goal) you will replace any previous definition of the library that was generated as a
jar-only dependency with a library definition that references both the source and
class files.
- For library definitions that remain jar-only references to the local repo, you can
specify a path to the corresponding source code via properties.
- Support has been added for generating JBuilder application and applet runtime
configurations from properties.
- Any resources are added to the JBuilder project source path.
- Using an optional property, you can specify a list of explicit files that will be
included in the JBuilder project if they exist. The default list are project.xml,
project.properties, and maven.xml.
---------------------------------------------------------------------
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/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]
