maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joerg Schaible (JIRA)" <>
Subject [jira] Commented: (MECLIPSE-344) connecting existing workspace artifact-projects
Date Fri, 01 Feb 2008 12:45:57 GMT


Joerg Schaible commented on MECLIPSE-344:

Will it link always all projects or is it possible to link only the SNAPSHOTs? The difference
is, that with the information from the Eclipse workspace you don't have to rebuild all Eclipse
files at once to get the SNAPSHOTs linked. You will have the information now to rebuild the
Eclipse projects for a single submodule only, but have the SNAPSHOTs still linked. Therefore
it would be really nice to have both operation modes.

> connecting existing workspace artifact-projects
> -----------------------------------------------
>                 Key: MECLIPSE-344
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: New Feature
>          Components: Dependencies resolution and build path
>    Affects Versions: 2.4
>            Reporter: Richard van Nieuwenhoven
>            Assignee: Arnaud Heritier
>             Fix For: 2.5
>         Attachments: MECLIPSE-344+rad7.patch, MECLIPSE-344+rad7.tgz, MECLIPSE-344.patch,
MECLIPSE-344.tgz, workspace-new-files.tgz, workspace.patch, workspace_with_limit.patch
> This patch enables you to specify your workspace, and all dependent artefacts  that are
available in your eclipse-workspace will be attached  as project references even if they are
not in the reactor.
> the property can be set with -DworkspaceToConnect=.....
> I did not have the time to create Test cases but, i maybe someone can help with that!
> The patch is based on the MECLIPSE-333 branch.
> as usual the new files are in the extra tgz.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message