Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] plexus-build-api

See inlines.

On 12/05/2011 12:18 PM, Igor Fedorenko wrote:
This does not answer my question.

What does "executed as part of the normal build cycle (incremental) but
in a way that it doesn't run on no change" actually mean for remote
resources and resources outside of workspace in general?

I expect the truezip-maven-plugin to participate in the build.

Does it mean dependency:copy-dependencies should contact remote
repositories during each incremental build to see if there are changes,
for example?


No.

The source of dependency:copy and truezip:copy is never remote. As for dependency:copy-dependencies there shouldn't be the need to contact the remote. The dependencies used are the one maven resolves
and are available.

Should dependency:copy-dependencies check if files under project target/
directory were modified or removed since last build or recreate them?


Yes, that is why I was thinking of using "markers", this is what I proposed for truezip.

In the case of copy, either truezip:copy or dependency:copy. The plugin participates when the destination doesn't exist, the source last changed time is different than the marker
and the buildContext hasDelta.

Should dependency:copy-dependencies behave differently during full and
incremental builds?


Maybe, I didn't think too much about it. My first impression is no.

--
Regards,
Igor

On 11-12-05 11:53 AM, Pino Silvaggio wrote:
Take the resources for examples...

They are copied on resources changes.

We use truezip to copy (extract) an sql script from an artifact
to ${project.build.outputDirectory}.

I would expect the truezip-maven-plugin:copy to be executed
as part of the normal build cycle (incremental) but in a way
that it doesn't run on no change. This works as expected if
the source is in the workspace.

dependency:copy should behave the same way as truezip:copy

I am thinking about markers, similar to dependency:copy-dependencies

My submitted patch (http://jira.codehaus.org/browse/MOJO-1791) works
pretty good
and I think gives the expected results.

-

p


On 12/05/2011 11:40 AM, Igor Fedorenko wrote:
Can you describe desired behaviour for dependency:copy inside Eclipse
workspace? When do you expect it to run and what you expect it to do?

--
Regards,
Igor

On 11-12-05 11:30 AM, Pino Silvaggio wrote:
Well, I am trying to add support to truezip-maven-plugin, I briefly
discuss
the problematics here: http://jira.codehaus.org/browse/MOJO-1791

Take dependency:copy for example, how would you implement a sensible
build trigger?

At this point, dependency:copy is not supported by m2e but why not?


On 12/05/2011 10:13 AM, Igor Fedorenko wrote:
I need to understand the usecase better before I can suggest anything.
Can you provide an example project that uses such external resources?

--
Regards,
Igor

On 11-12-02 4:48 PM, Pino Silvaggio wrote:
So I'm using the plexus-build-api and it's ok.

However, I would like to get your opinion on something.

It probably was discuss in some thread but I don't think there's
was a consensus...

I am using buildContext in the truezip plugin but what is the accept
way of dealing "external" resources (external to the workspace for
example)?

At this point resources that are not in the workspace are always
considered changed
and therefore the build is triggered which can be very intensive.

Is there some plugin with the same use case?
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev


Back to the top