Type | Changes | By |
|
Fix MAVEN-781.
Thanks to David Zeleznik.
|
evenisse |
|
Fix MAVEN-668.
|
evenisse |
|
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.
Thanks to David Zeleznik.
|
evenisse |
|
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).
Thanks to David Zeleznik.
|
evenisse |
|
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.
Thanks to David Zeleznik.
|
evenisse |
|
For library definitions that remain jar-only references to the local repo, you can specify a path to the corresponding source code via properties.
Thanks to David Zeleznik.
|
evenisse |
|
Support has been added for generating JBuilder application and applet runtime configurations from properties.
Thanks to David Zeleznik.
|
evenisse |
|
Any resources are added to the JBuilder project source path.
Thanks to David Zeleznik.
|
evenisse |
|
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.
Thanks to David Zeleznik.
|
evenisse |
|
Added support for JBuilder 9
Thanks to David Zeleznik.
|
evenisse |
|
Added maven.jbuilder.verbose property
Thanks to David Zeleznik.
|
evenisse |
|
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.
Thanks to David Zeleznik.
|
evenisse |