Specify -Declipse.downloadSources=true to do so.
o WarMojo produces an artifact, even if exploded is specified. This makes sure
that the install phase doesn't fail because there's no artifact.
o DependenciesReport: add caught exception to the new thrown exception
for better messages.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@289353 13f79535-47bb-0310-9956-ffa450edef68
confusion as to which project is used.
o Use executedProject everywhere except for acquiring the artifact list; the
executedProject misses that list (that's because no deps are resolved in
the forked lifecycle execution; it's delayed until the plugin is encountered
and it's requiresDependencyResolution is seen.)
o Added flag -Declipse.downloadSources=true|false to skip source downloading
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@289188 13f79535-47bb-0310-9956-ffa450edef68
o Added testcase to check generation of eclipse files in
different location; modified the testcase to support this,
and deal with the absolute paths.
o Neatified the addSourceLinks/addResourceLinks: using
a map to keep track of duplicate source folders has the side
effect of only needing one of those methods; it should
also be faster :)
o Tried to add support for includes/excludes, but eclipse only
supports unique source directories; this is typically not the
case in maven, filters are used to split one resourcedir
up. Left the code in for future reference.
TODO: find a way to merge includes/excludes. If only
the dir where in/excludes are specified is unique, they
could be written without problem. This requires a preprocessing
pass.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@240143 13f79535-47bb-0310-9956-ffa450edef68
and did some more code cleanup.
o Tracking with projects have been referenced in order to stop adding the same
project twice if there's a dep on more than one artifact attachment from a
project.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@239392 13f79535-47bb-0310-9956-ffa450edef68
Fixing profile application to separate profiles discovered in and around POM from those in settings.xml, and apply them separately in the order:
for-each-project-in-inheritance:{POM, profiles.xml}, settings.xml
Added common interface for accumulating, explicitly activating and deactivating, and retrieving profiles to be applied to a given project. This manager interface (ProfileManager) is general enough to be applicable to both the project-level and settings-level profiles.
Added 'performRelease'-keyed profile to super-POM which will be used by the release plugin and anyone using a parallel process, and which will enable '-DupdateReleaseInfo=true' for the deploy mojo, along with enabling the source attachment for the project.
Added 'attach' parameter to JarSourceMojo to allow local POM to turn off source attachments, overriding release profile in super-pom.
Updated the release:perform mojo to use '-DperformRelease=true' for switching on the new release profile, rather than just using '-DupdateReleaseInfo=true'...
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@233013 13f79535-47bb-0310-9956-ffa450edef68
can calculate the build order - no more rebuilds needed to fix this!
o Added a switch -Declipse.workpace=/path/to/workspace that allows for the
.classpath and .project files to be written to a new directory:
- For each project a new directory is created.
- Eclipse 'Links' are created to the original project location for the
sources and resources directories.
- The target directory will be in the new workspace location, not in
the original project tree.
This offers the following advantages:
- Project trees that normally couldn't be imported into eclipse
because of the overlap error now can be imported succesfully
(m2 works now!)
- Projects that reside on a ClearCase SMB mounted drive (which are
very slow) can now have a target directory on a local drive without
modifying the pom, greatly improving build speed in eclipse.
o Fixed some minor bugs where the wrong project instance was used.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@226669 13f79535-47bb-0310-9956-ffa450edef68
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)
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@191667 13f79535-47bb-0310-9956-ffa450edef68
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
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@191634 13f79535-47bb-0310-9956-ffa450edef68
John Dennis Casey
Brett Leslie Porter
Kenney Westerhof
Emmanuel Venisse
Jason van Zyl