Hi John,
Sorry for the late reply.
On 9/8/05, John Fallows <[EMAIL PROTECTED]> wrote:
> Where is the default implementation class for the ArtifactInstaller
> interface?
DefaultArtifactInstaller (consult components.xml to find this) in
maven-artifact-manager.
> It may very well already be implem
On 9/8/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> We were planning a more generic technique for this (letting Maven handle it
> by declaring your inputs and only executing mojos that had their inputs
> changed). This isn't scheduled for 2.0, however.
That doesn't seem to cover the case where t
Hi John,
We were planning a more generic technique for this (letting Maven handle it
by declaring your inputs and only executing mojos that had their inputs
changed). This isn't scheduled for 2.0, however.
If you have a solution to add to jar:jar and install:install then I'd be
happy to apply
I'm developing a source generation plugin as a project module with the
following structure:
project/
plugin/
api/
impl/
where the plugin is part of the reactor build process. The plugin
builds first and is used by the api and impl builds.
As a good plugin developer citizen, I'd like to ma
http://jira.codehaus.org/browse/MNG-326
I need to note the plugin as a dependency requirement.
- Brett
On 7/19/05, John Fallows <[EMAIL PROTECTED]> wrote:
> On 7/16/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > I think you had a pretty good handle on everything else in here, but
> > on this po
On 7/16/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> I think you had a pretty good handle on everything else in here, but
> on this point:
>
> On 7/8/05, John Fallows <[EMAIL PROTECTED]> wrote:
> > But, the reactor does not seem to notice that one of the modules is
> > actually a plugin that is u
I think you had a pretty good handle on everything else in here, but
on this point:
On 7/8/05, John Fallows <[EMAIL PROTECTED]> wrote:
> But, the reactor does not seem to notice that one of the modules is
> actually a plugin that is used by the other modules, so it does not
> ensure that the plugi
When using Maven1, we had four subprojects; api, impl, demo and tools,
where tools created various utilities that were used during the build
by the maven.xml files of the other subprojects.
Now that we are putting in the effort to migrate to Maven2, we want to
tidy up this tools project and turn i
