Application: gvSIG desktop » Library: org.gvsig.tools

Add support for the m2eclipse 1.0 plugin (eclipse indigo)

Use a separate property for the eclipse project name, for easy setting on each project, and default it to the artifactId.

Create packages in the install folder with the server structure (pool/artifactId)

Add support to create the package.info file in the initial phases, so it doesn't have to be created manually beforehand.

[maven-release-plugin] copy for tag 1.0.7

Subido por error

[maven-release-plugin] prepare release 1.0.7

[maven-release-plugin] prepare for next development iteration

[maven-release-plugin] prepare release 1.0.7

[maven-release-plugin] prepare for next development iteration

[maven-release-plugin] prepare release 1.0.7

Update scm information

Update base tools version dependency

[maven-release-plugin] copy for tag org.gvsig.maven.base-1.0.6

Change slf4j-log4j implementation scope to runtime

Add more xmlschema dependencies

Add some more needed dependencies

Downgrade eclipse plugin version to the 2.6, as the newer available ones (2.7 and 2.8) have a bug when you use resource filtering.

Add the properties-maven-plugin to the pluginManagement section

Add dependencies needed by the scripting library

Updating the mobile repository URL

Upgrade maven-clean-plugin version which solves:
- Other files not being deleted, as the gvsig plugin installed files.
- Error deleting the .depman folder contents in linux, because of some file links

Solve checkstyle plugin configuration

Build file download folder has to be created beforehand

Plugins management refactoring

Add some used plugins to the plugins management to lock the version used

Add javadoc package links auto detection

Create the target folder when downloading the maven base build jar file

Add wagon-ssh so deploy works with the m2eclipse plugin and maven 3

Set versions for all plugins so we don't have problems in the future with non stable ones

Remove eclipse project file

The org.gvsig.maven.base.tools dependence had an old version

Configure the gvsig installer maven plugin

Remove maven-jar-plugin config as it somehow badly influences in the childs configurations (projects with many generated jars)

Move taskdef declaration into a target, as the dependencies required are downloaded by other task.

Update jpedal version

Change gvsig repository snapshots update interval from daily to hourly

Add the new batik-ext-gvsig-custom dependence

Don't unpack natives tar.gz files if not newer and already unpacked

Upgrade PostgreSQL JDBC driver to the 8.4 version

Add source dependencies to all gvSIG projects and environment variables needed by the native dependencies

Update GPE versions

Add chmod configuration with permission to all people while OSOR IT guys try to solve the group related permissions issue.

[maven-release-plugin] prepare for next development iteration

[maven-release-plugin] prepare release 1.0.5

Checkstyle finetunning to comply with gvSIG code conventions

Solve some site generation errors:
- New checkstyle version configuration incompatibilities
- Tags plugin needs to be run after the JXR one

Add two new mvn tasks and launchers: dependency:tree and any maven goal

removing user's cancel panel

check path