Parent Directory
| 
Revision Log
| Links to HEAD: | (view) (annotate) |
| Sticky Revision: |
[maven-release-plugin] copy for tag maven-eclipse-plugin-2.7
[maven-release-plugin] prepare release maven-eclipse-plugin-2.7
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.7
rolling back for release take 3
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.7
rolling back version to fix release issues
added assembly for source-release
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.7
Revert release done by Barrie. He cannot continue it.
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.7
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.7
bumping to 2.7 as per email that fixing regression with a new feature shouldn't be a .z version update.
[MECLIPSE-104] - Add the ability to specify source inclusions/exclusions Submitted by: Richard van der Hoff The configuration for EclipsePlugin now accepts <sourceInclusions> <sourceInclusion>XXX</sourceInclusion> <sourceInclusions> (same for sourceExclusions) to modifiy the classpath entries for source directories. **/*.java is always added if it is a java (or pde) project **/*.aj is always added if it is an ajdt project.
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.6
[maven-release-plugin] rollback the release of maven-eclipse-plugin-2.6
[maven-release-plugin] prepare release maven-eclipse-plugin-2.6
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.6
used http://maven.apache.org/xsd/* for schema location
o Inherited from maven-plugins:13
use the latest parents
[MECLIPSE-504] Add a new mojo eclipse:remove-cache - Moved delete(File) from EclipseCleanMojo into IdeUtils.java - Added RemoveCacheMojo - Added IT tests for RemoveCacheMojo - added commons-io:commons-io:1.4 as a dependency
o Formatted/reordered POM
o Inherited from maven-plugins:12
Removed bundleVersion parameter from formatEclipsePluginName() as not being used. Refactored and fixed tests for InstallPluginsMojoTest.java Added "org.eclipse.core:runtime:3.2.0-v20060603" into test repo m2repo/eclipseinstall for use by tests.
Added xmlunit to test infrastructure. Added back in wb-resource for src paths in project-36 expected file org.eclipse.wst.common.component. Not sure why it is now included again... AbstractEclipsePluginIT.java - XmlUnit EntityResolver added as part of setup to ignore DTDs as behind a firewall these tests fail. - refactored assertFileEquals to call assertTextFileEquals after preprocessing the expected and actual file contents including variable text replacement - in assertFileEquals if the file content is XML then delegates to assertXmlFileEquals - all hacks/text manipulation done in preprocess, preferably delegating to method calls. - changed getLines to accept String instead of File as the contents are read in preprocess. - added isXml which checks the first line for the XML_HEADER <?xml to determine whether file is xml content. Note: Not all files being tested have this as a header but are still xml content.
[MECLIPSE-486] fixing ITs to support multi-module expected file checking. pom.xml: Fixed the phase "test" to not include "projects/**" as this directory is copied from src/test/resources into target/test-classes and surefire will attempt to compile any *Test*.java files - which will fail since they are not in the correct location relative to their package declaration. See http://www.nabble.com/Plugins%3A-execution-configuration-does-not-add-to-configuration-td19425025.html Fixed the run-its profile so that it overrides the excludes inherited from the "test" phase configuration. IdeUtils: Refactored code to create fixSeparator() method. AbstractEclipsePluginIT: Changed compareDirectoryContent to no longer accept a directory to use as check contents. Instead ${basedir} is searched for EXPECTED_DIRECTORY_NAME ("expected") and all occurrences of this directory are used in the comparison processes. This has simplified checking in code as you no longer need to specify additional calls for multiple directories and made it easier to support multi-module checking as previously only ${basedir}/expected was checked, module directories where ignored. The actual files checked are relative to the parent directory of the matching "expected" directory. IOExceptions are no longer thrown instead MojoExecutionException are used mainly by delegating to IdeUtils.getCanonicalPath() instead of calling File.getCanonicalPath() directly. RadPluginIT: Updated to use new compareDirectoryContent() src/test/resources/projects/*: Fixed files that were never previously checked to use the contents of the actual maven-eclipse-plugin output. On the assumption that the plugin is generating the correct output and nothing in this change set has altered that behaviour.
Bump to 2.6-SNAPSHOT. I added a new feature (aspectJ support)
Launch ITs in integration-test phase
[MECLIPSE-318] test classes and resources need to be first in .classpath file
o Synced id and activation of integration-tests with core ITs
Execute also unit tests when integration-tests profile is activated
MECLIPSE-345 : Split unit tests and integration tests MECLIPSE-349 : Move integration tests in the integration-tests profile
Reorg dependencies
Remove plugins versions already defined in parent
Try to use the 12-SNAPSHOT parent
o Added project description
o Reordered POM
o Inherited from maven-plugins:11 o Updated to plexus-utils:1.5.6 o Disabled helpmojo generation to workaround failures during IT preparation
Fix build by : - Downgrading to maven-plugins 10 - Re-adding compiler plugin 2.0.2 with Java 1.4 settings - Setting version of surefire 2.3.1 - Downgrading plexus-utils from 1.5.3 to 1.4.5
- Use maven-plugins 12-SNAPSHOT as parent - Remove duplicated setting with parents (compiler, surefire)
Trying to fix CI by upgrading plexus-utils...not sure why the tests in this plugin are causing an OOME, even with 512M of heap.
Bumping all parent versions to 11, to allow deployment to alternative locations.
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.5.1
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.5
MECLIPSE-399: URL for javadoc attachments on Unix is invalid Thanks for the patch from Benjamin. I had o change a little bit the test case to pass it on MacOS and I had to fix the project testcase #10
MECLIPSE-395 : revert fix. It doesn't work if properties aren't defined.
MECLIPSE-395 : Plugin tests are failing due to a wrong local repository path. We have to pass system properties org.apache.maven.user-settings and org.apache.maven.global-settings to surefire.
Do not use a scope in a plugin dependency to avoid resolution problems in the future
MECLIPSE-219 : Allow file contents to be obtained from url Patch provided by Daniel Kulp
MECLIPSE-344 : connecting existing workspace artifact-projects Patch submitted by Richard van Nieuwenhoven Merge the branch now that tests are fixed.
- Use maven-surefire-plugin 2.3.1 instead of 2.3 - Upgrade dependency org.apache.maven.shared:maven-plugin-testing-tools:1.0-alpha-3-SNAPSHOT -> 1.0-alpha-3 - Upgrade dependency org.apache.maven.shared:maven-osgi:0.2.0-SNAPSHOT -> 0.2.0
[MECLIPSE-56] added a testcase for non-ascii characters in pom.xml
[MECLIPSE-358] Plugin installed via eclipse:install-plugins has the wrong name
Add SCM settings required with the parent pom for plugins version 10
Add version of plugins and some others settings to improve the build stability
Update to the last parent
use an alternate home for more portability
remove accidental committed info in the pom.xml
MECLIPSE-129&296. Add eclipse:configure-workspace goal
MECLIPSE-291: updated to use new tools and new invoker to pick up fix for MNG-3096
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.4
bumped up the the version of p-u provided by maven and the new required release of the plugin tools
MECLIPSE-295: jar has incorrect version in META-INF/maven/plugin.xml
rolling back the failed release
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.4
eclipse doesn't actually need the latest tools
rolling back
rolled to non snapshot of tools for release staging
Refactoring : move WTP classes into a sub-package
[MECLIPSE-262] Upgrade maven dependencies
Refactor the usage of exploded/packaged plugins adding some model objects Use constants from bndlib for Manifest entries
Add license
use released parent
- move plugin-plugin out of 'reporting' for plugins. It's a required part of the site, and does not cause any issues with the reactor or site generation - update to snapshots
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.3
o updating to latest released parent
o prepare Eclipse plugin for release with the directRelease profile
no more snapshots here, nearly ready for a real release.
revert to a released version of maven-plugin-testing-harness
license header
fix j2ee multiproject test: update expected files (minor modifications), run it using the buildTool, move expected results to the "expected" dir, re-enable test in pom.xml
Fixing EclipsePlugin unit tests.
[MECLIPSE-137] Merging MECLIPSE-137 branch back to the trunk.
MECLIPSE-48 handle includes and excludes in source dirs
Process exploded plugins in make-artifacts
update all parents
Ensuring that codebase works with JDK 1.4
Adding mojo to install a set of eclipse plugins fromthe project's resolved dependencies into the eclipse/plugins directory. Unit tests are included, and the mojo is javadoc'ed, but not documented for the website.
use a stable parent version
Update groupId/version for maven-plugin-testing-harness as 1.0-SNAPSHOT was never deployed
first drop for an utility mojo that installs eclipse plugins to the local repo by scanning an eclipse installation dir. Pom info are extracted from OSGI manifests and plugin dependencies are generated from the Require-Bundle entry.
MECLIPSE-98 move maven prerequisite to 2.0.1
PR: MECLIPSE-64 - completed plugin docs - added some examples - added faqs
PR: MECLIPSE-101 Added default test for the add-maven-repo goal.
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.2
Major refactoring of the plugin, aiming to spin off any generic IDE related util that can be used by others similar mojos (e.g. the Idea one). All the common stuff is now done in a generic abstract IdeSupportMojo which takes care of manual dependency resolution, source and javadocs downloading, sorting of referenced projects, handling of common messages and flags. Integrating some bits from the Idea plugin for artifact resolution, and fix it so it doesn't require reactor projects to have installed artifacts at all. All the existing unit tests work without problems after the refactoring (also with the removal of a reactor artifact from the test repo). Test #7 is commented out at the moment since it randomically fails due to the random order used in .classpath and .wtpmodules (test does line by line comparison).
adjust parent POMs
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.1
set maven-plugin-parent version to 2.0.1 (2.0 has an old scm url) and update embedder to 2.0.1
MECLIPSE-51 Issue Tracking on website points to generic MNG instead of MECLIPSE
removing wrong scm connection (tags)
preparing new development version
[maven-release-plugin] prepare release maven-eclipse-plugin-2.0
add correct scm links MNG-1688 (fixed in plugin-parent 2.1, but we don't want to update the dependency now)
move plugins
fix missing optional dependencies in .wtpmodules, cleanup test and introduce a test using MavenEmbedder (currently disabled due to a couple of issues, but it should replace the command line test)
o fixing broken eclipse build, the model is required to compile
adding scheleton for a real complete testcase. This test works using a 2-modules project and contains any direct and transitive dependency type. Mvn is executed using a command line, so the test is actually disabled in pom.xml until a better solution is found (the test works with the latest installed version of the eclipse plugin). Note that expected files for module-2 are not correct yet (first of all, test #8 need to be fixed)
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.0-beta-2
update versions in plugins
upgrade plexus utils to 1.0.4-SNAPSHOT. The group ID has changed, so add a bunch of exclusions to ensure the old is not picked up fix bugs in mboot that wasn't honoring excludes.
PR: MNG-1110 differentiate between an artifact that is not found, and failure to obtain an artifact
use released versions
line up test and used version
upgrade to plexus 1.0-alpha-7 container, switching to new group ID
lining up versions. still use beta-1 where appropriate
PR: MNG-788 add filtering to the build element
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-eclipse-plugin-2.0-beta-1
update dependency and parent versions
o Put all m2 core dependencies (plexus-container-default and plexus-utils) under dependencyManagement of m2 and maven-plugins, and removed versions in all poms having either as a parent. Used version 1.0.2-SNAPSHOT for plexus-utils as that was used in maven-core and is not overridable. o Bumped maven-archiver version to 2.0-beta-1-SNAPSHOT for maven-ear-plugin
PR: MNG-596 add XSD definition to m2 poms and archetypes
Bumping plexus-utils version to 1.0.1
Update all versions to beta-1-SNAPSHOT
[maven-release-plugin] prepare for development 2.0-alpha-4-SNAPSHOT
[maven-release-plugin] prepare release 2.0-alpha-3
preparing for re-release to fix version.
preparing for re-release to fix version.
Resolving: MNG-495 o Pressing [ENTER] at a plugin update prompt should result in the plugin being registered, as indicated by the prompt. o Use CLI switch '--no-plugin-updates' to suppress usage of the plugin registry o Use CLI switch '--update-plugins' to force updated/resolved plugin versions to be registered o Neither of these has a short CLI option, since we're starting to run out of sensible char options for these types of things.
Updating non-maven, non-modello deps to get rid of snapshots. Also removed marmalade stuff from mboot.
refactoring of the resolveTransitiveDependencies call. simplified by removing a bunch of duplicated code in addArtifacts - no need to merge, you have the full list. separated the original artifacts (dependency artifacts) from the resolved artifacts (getArtifacts)
PR: MNG-140 split artifact impl from api so that dep resolution can be used independently of wagon only the first step in making maven-artifact more useful as a public api - more changes to be made
update api
update parent references to get access to the ci settings
o upgrade plexus-container to alpha-4-SNAPSHOT o upgrade plexus-utils to alpha-3 until xpp stuff is fix in 1.0.0
bump versions
use released versions
update to released versions
eclipse plugin imported
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
| apache@apache.org | ViewVC Help |
| Powered by ViewVC 1.1.2 |